|
Ending the subsystem will definitely do it. ENDSBS QBATCH *IMMED. Just
make sure that nobody's going to submit something they need at the same
time. It's always smart to hold that subsystem's job queues first.
Paul Nelson
Arbor Solutions, Inc.
708-670-6978 Cell
pnelson@xxxxxxxxxx
William Washington III <w.washington3@xxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
02/19/2004 03:11 PM
Please respond to Midrange Systems Technical Discussion
To: midrange-l@xxxxxxxxxxxx
cc:
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.