|
William, have you already tried ENDJOBABN on the the first job that had a problem, sometimes this gets them. I have seen this happen only a couple of times in my time on a '400. If the ENDJOBABN doesnt get it, its IPL time I think, unless someone else has another method cheers Colin.W ----- Original Message ----- From: "William Washington III" <w.washington3@xxxxxxxxxxxxx> To: <midrange-l@xxxxxxxxxxxx> Sent: Thursday, February 19, 2004 9:11 PM Subject: Jobs in subsystems with status END > There are a number of jobs on our system that have a status of END, but they are not dropping off of the WRKACTJOB screen. They are getting zero cpu. They have no I/O. > > I cancelled a batch job yesterday, and it is still in the QBATCH subsystem with status of END. > > Has anyone had this problem before? Do I need to stop and restart the subsystem to get rid of these jobs? Of must I do something more drastic? (e.g. IPL the system...) > > William > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > 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-2025 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.