|
Yes - waiting jobs. Possibly all of the below - MSGW is the most common. It does not make a difference - if the job has not used any resources in a given period of time, I want to the job to end. There is no issue here with terminating in the middle of a process. ----- Original Message ----- Subject: RE: Terminating an idle batch job > What do you mean by an idle batch job? What are your batch jobs waiting on? > Are you talking about failed jobs with error messages on QSYSOPR? I can't > imagine an idle job where the code has not been specifically written to wait > on some sort of logic (monitoring a message queue or data queue, or in a > wait or DLYJOB loop...) > > -Jim > > James P. Damato > Manager - Technical Administration > Dollar General Corporation
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.