RE: Qbatch won't end.

["Carley, Neil" <carleyn1@xxxxxxxxxxxxxxxx>]

Not 100% relevant to qbatch, but I have experienced a somewhat similar type
problem with regards to ending a job.
Recently on a couple of occasions we have had users end their CA sessions
while using the interactive debug facility (STRISDB) and this has caused the
machine to go into a tight CPU loop (the job utilizing about 75% of the
CPU). From system console I have tried ending the job with no success, then
later trying the ENDJOBABN still had no effect on the job, I eventually had
to end some of the subsystems to recover the system. On one ocasion the only
thing that worked was an IPL. Has anyone ever had a similar experience with
regards to ISDB ?, any suggestions to preventing the problem or a means to
recover appriciated. 

Neil     

> -----Original Message-----
> From: Allen, Stuart [SMTP:sallen@fellowes.com]
> Sent: Wednesday, March 01, 2000 10:54 AM
> To:   'MIDRANGE-L@midrange.com'
> Subject:      RE: Qbatch won't end.
> 
> not sure what could have caused it to hang, but 10 minutes after doing an
> ENDJOB *IMMED you could have done an ENDJOBABN to forcibly end the job
> without having to power down.
> 
> Regards,
> Stuart
>                                      
> Stuart Allen
> European Systems Analyst
> Fellowes
> 
> mailto:sallen@fellowes.com
> 
> 
> > -----Original Message-----
> > From:       Arnold, Robert [SMTP:RMArnold@hpproducts.net]
> > Sent:       Wednesday, March 01, 2000 10:20 AM
> > To: 'Midrange-l@midrange.com'
> > Subject:    Qbatch won't end.
> > 
> > We had an interesting situation occur last evening.  Durring month end
> > close, we had a backup job hang in qbatch.  My operator performed an end
> > with *IMMED.  The job would not terminate.  Rather than seek assistance,
> > the
> > operator then ended Qbatch *immed.  At that point Qbatch was hung for
> > several hours.  Being month end, time is somewhat of the essence, a
> > controlled powerdown *immed restart *yes was then performed.  Every
> thing
> > but Qbatch and the job in question was ended prior to the poerdown.  Out
> > of
> > all this I have two questions, 1 - what should have been done to
> terminate
> > the job that was not ending? (No job log was being produced nor was
> there
> > any run time.  2 - what would cause a job to hang like that?  (We
> harrass
> > the NT guy here for the instability from Microsoft on a PC touting the
> > very
> > stable 400 platform) 
> > 
> > Any assistance and or guidance would be greatly appreciated.
> > 
> > We're running a 720 with 4.4.
> > 
> > TIA,
> > 
> > Bob
> >  
> > 
> +---
> | 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
+---