• Subject: RE: errors
  • From: "Stone, Brad V (TC OASIS)" <bvstone@xxxxxxxxxxxxxx>
  • Date: Thu, 23 Sep 1999 10:42:32 -0500

If you can get to the job to end it with *IMMED, don't forget to change the
maximum log entries to zero.  This may help.

Another option, and maybe a better one, if you can get to the job, is to put
it on hold.  This will halt operations so that the system is easier to work
with.

Bradley V. Stone
BVS/Tools
http://www.bvstools.com




> -----Original Message-----
> From: Kahn, David [JNJFR] [mailto:DKahn1@JNJFR.JNJ.com]
> Sent: Thursday, September 23, 1999 7:48 AM
> To: 'MIDRANGE-L@midrange.com'
> Subject: RE: errors
> 
> 
> Debbie,
> 
> I don't know BPCS but it looks suspiciously like a classic 
> bug in an error
> handling routine causing the program to jump into the error 
> routine where it
> again errors, jumps back into the routine and so on ad infinitum.
> 
> Occasionally you get this kind of thing being triggered off by an
> interactive job losing contact with a 5250 emulation session. As this
> happened to 5 jobs simultaneously you may have had some kind of
> communications glitch(?).
> 
> When you can't cancel run-away jobs you can sometimes contain them by
> changing their priority to 99. 10 minutes after they were 
> "ended" with the
> *IMMED option, you can should be able to clobber them with 
> the ENDJOBABN
> command. This usually, but not always, gets rid of them. If 
> that doesn't
> work then you're generally stuck with them until the next 
> IPL. Did you try
> these steps?
> 
> It's one thing for IBM to say it's a BPCS problem, but no 
> matter what the
> bug if you can't flush a problem job out of your system that 
> has to be an
> OS/400 problem, surely?
> 
> 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: Debbie Helms [mailto:DHelms@Lance.com]
> Date: 22 September 1999 22:53
> : 'MIDRANGE-L@midrange.com'
> Objet: errors
> 
> 
> I had an interesting problem (opportunity) today.  Our 640 
> locked up around
> 10:30 this morning.  We had about 5 jobs in QINTER that 
> brought the system
> to its knees.  We could not cancel the jobs in any form.  IBM 
> could not help
> us cancel the jobs.  Finally we decided the only option was 
> to IPL.   The
> joblogs wrapped so we do not know what exactly happened.  
> Listed below is a
> portion of the joblog that repeated itself.  In 40 seconds it 
> had repeated
> this 8,400 pages.  IBM thinks the problem is in BPCS.  I 
> don't know what to
> think.  If anyone has ever heard or seen this please let me know.   
> +---
> | 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
> +---
> 
+---
| 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
+---

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].