|
The problem is the logging level (the first 0 in 0/0/*SECLVL). Change the logging level to 4 and you will get the maximum amount of information in the job log the system can provide. The other three options are likely explained in the help text for the CHGJOB command and in the CL reference manual. Hope that helps. Donald R. Fisher, III Project Manager Roomstore Furniture Company (804) 784-7600 extension 2124 DFisher@xxxxxxxxxxxxx <clip> I've seen a few batch jobs myself, that I should be able to see joblog information on, but couldn't; neither he nor I can explain why the job, which is obviously doing something, and requiring CPU attention to do it, isn't producing any visible joblog information. Message logging for the job is 0/0/*SECLVL. System is running V4R5. <clip>
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
