RE: JobLog Creation

["Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>]

From what I recall, has always been that way, back to S/38 days.

The other issue for long running jobs, with a large amount of logging is when the joblog wraps, you also lose joblog info.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Joe Pluta
Sent: Thursday, October 18, 2018 8:59 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: JobLog Creation

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.