|
I once got the impression that while a job is running, it is alwaysI remember this as S/38 behaviour. I believe that LOGLVL is not a filter for reading messages out of the job log; it is a filter for putting them into the job log.
capturing all the log information and that you could change the job's
logging and see that data. So, even though the job is currently at (0
00 *NOLIST), you could change it to (4 00 *SECLVL) and see all the old
data.
Subsequent testing has indicated that to not be the case. As far as I
can tell, if you turn off logging, that information is lost forever.
Does anybody remember it being any different in "the old days"? Or is
this just something I misremembered?
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.