RE: errors

["Kahn, David [JNJFR]" <DKahn1@xxxxxxxxxxxxx>]

James,

Good track record or not, if a job can get into a state where the OS cannot
flush it, that's a problem with the OS. The problem may originate in our
code, but their code should be able to deal with that. If we're prepared to
accept that a re-IPL might be needed because of an application programming
error we might as well give up and switch to Windows. Applications have
bugs. OS/400 is meant to keep going.

Dave Kahn
Johnson & Johnson International (Ethicon) France
Phone : +33 1 55 00 3180
Email :  dkahn1@jnjfr.jnj.com (work)
           dkahn@cix.co.uk      (home)


-----Message d'origine-----
De: email@james-w-kilgore.com [mailto:email@james-w-kilgore.com]
Date: 24 September 1999 08:55
À: MIDRANGE-L@midrange.com
Objet: Re: errors


I hate to admit it, but I've created a runaway job that just sucked the
life out of the machine.  We couldn't do squat to cancel it and it
created an 8k page looping job log within minutes.

Within the CL program, there is a MONMSG that does a GOTO to a message
feedback program.

The message feedback program did not exist, thus creating an error, thus
causing a GOTO, and off we go.

Well, we revised our install script.

In my 25+ years of dealing with Big Blue, if there is a problem, it's
usually something in my code. Not theirs.  I've only had a problem twice
(short term) with theirs.  IMO, that's a pretty good track record.
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---