× 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.



I once got the impression that while a job is running, it is always 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?



On 10/18/2018 7:43 AM, Jim Oberholtzer wrote:
Only if the log limit is set to collect the data.


--
Jim Oberholtzer
Agile Technology Architects

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx> On Behalf Of Evan Harris
Sent: Wednesday, October 17, 2018 4:36 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: JobLog Creation

Would the DSPJOBLOG OUTPUT*PRINT) command help at all ?

I often use it if I am doing where I think an audit trail of the session
would be helpful.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.