|
Fiona I have had jobs that can't be ended by ENDJOBABN, as you found. I like your solution, to ENDSBS. But until that is possible, maybe the job can be held, so it stops taking CPU. Vern > > Steady on, guys, you don't need to IPL to zap a job ! > Ron, we had a similar rogue job which ran & ran - & that evenng I just > ended QINTER sbs to get rid of it. > Not only was it taking CPU, it had disappeared from most job displays but > was holding object locks which would impede the backup. Again, a comms > issue had caused the job to hang; the help desk had killed it *IMMED & > thought it had gone. > > Before this, I tried EndJob, EndJobAbn, and ENDJOB OPTION(*IMMED) SPLFILE > (*YES) LOGLMT(0) > > Fiona > fiona.fitzgerald@notes.royalsun.com > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.