|
also try ending (or ending again) with LOGLMT(0). The jobs may be slowly accumulating monstrous job logs. We once has a problem with jobs unable to allocate either the QPJOBLOG printer file, or the QEZJOBLOG output queue. They remained in an END status until the object was freed. -Jim James P. Damato Manager - Technical Administration Dollar General Corporation <mailto:jdamato@xxxxxxxxxxxxxxxxx> -----Original Message----- From: William Washington III [mailto:w.washington3@xxxxxxxxxxxxx] Sent: Thursday, February 19, 2004 3:12 PM To: midrange-l@xxxxxxxxxxxx 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
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.