Re: Jobs in subsystems with status END -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Caution*** - avoid ENDJOBABN if at all possible - it makes your next IPL assume an abnormal end of the system the next time and takes more time to come back up. Use the ENDSBS instead, if feasible. It's not fatal but is not recommended. Check the help for warnings.

Vern

At 04:24 PM 2/19/2004 -0500, you wrote:

Check out the End Job Abnormal (ENDJOBABN) comand...Maybe this can help

<FON color=#990099> ----midrange-l-bounces@xxxxxxxxxxxx wrote: -- ---

   To: midrange-l@xxxxxxxxxxxx
   From: William Washington II <w.washington3@xxxxxxxxxxxxx>
   Sent by: midrange-l-bounces@xxxxxxxxxxx
   Date: 02/19/2004 04:11PM
   Subject: Jobs in subsystems with staus END

   There are a number of jobsn our system that have a status of END, but
   they are not dropping off of he WRKACTJOB screen.  They are getting
   zero cpu.  They have no IO.

   I cancelled a batch job yesterday, and it is still in the QBATC
   subsystem with status of END.

   Has anyone had this problem efore?  Do I need to stop and restart the
   subsystem to get rid of thee jobs?  Of must I do something more
   drastic? (e.g. IPL the system...

William

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.