|
> on 08/12/97 at 08:33 AM, John Cirocco <JCirocco@gw.ctg.com> said: > > What is your sysval for QDEVRCYACN? I had similar problems and set my > system to *ENDJOB and I have not seen the error since. > We had a similar occurance once. The QDEVRCYACN value solved the problem. It was rooted in a bug within a message forwarding routine at the end of a CL program which went into a loop on device failure. Suddenly the system went to it's knees and huge (we're talking really big!) job logs were created. Since it was such a tight loop, even QSYSOPR at priority 10 had quite a wait to perform a WRKACTJOB then cancel *IMMED. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This is the Midrange System Mailing List! To submit a new message, * * send your mail to "MIDRANGE-L@midrange.com". To unsubscribe from * * this list send email to MAJORDOMO@midrange.com and specify * * 'unsubscribe MIDRANGE-L' in the body of your message. Questions * * should be directed to the list owner / operator: david@midrange.com * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
