Sean, 
first timestamp 
0100000 SYSA 2018200 00:00:00.05 A S8170 00000090 

last time stamp 


M FFFFFFF SYSA 2018200 23:59:51.85 A 


Carmen Vitullo 

----- Original Message -----

From: "Sean Gleann" <[email protected]> 
To: [email protected] 
Sent: Friday, July 20, 2018 8:44:44 AM 
Subject: Re: SYSLOG and LOGR query 

Hi Carmen 

I understand you get all 3 system logs, but what is the timestamp of the 
last record? 
Is it 07:00... (the time job is run) or is it 23:59... (the previous 
midnight)? 

Sean 

On 20 July 2018 at 14:37, Carmen Vitullo <[email protected]> wrote: 

> Sean, 
> a) I run this job every morning @ 07:00, I don't think the time is much an 
> issue, but I did start the offload process after waiting one day after a V 
> (OPERLOG,HC) 
> 
> b) I see the system logs from all my 3 systems in the sysplex. 
> 
> 
> 
> 
> 
> 
> Carmen Vitullo 
> 
> ----- Original Message ----- 
> 
> From: "Sean Gleann" <[email protected]> 
> To: [email protected] 
> Sent: Friday, July 20, 2018 8:30:34 AM 
> Subject: Re: SYSLOG and LOGR query 
> 
> Hi Carmen 
> 
> You say you use your job 'every morning'... 
> May I ask, please: 
> (a) what time of day do you run the job 
> (b) what do you see in your TS.OPERLOG.ARCHIVE(+1) file? 
> 
> If you see data up to the time the job is run, then you are getting what I 
> expect to see (and I'm doing something wrong) 
> If you see data up to midnight, then you are getting the same result as I 
> am getting, and it would appear that is the way IEAMBDLG is meant to work. 
> 
> Sean 
> 
> On 20 July 2018 at 14:09, Carmen Vitullo <[email protected]> wrote: 
> 
> > the actual working JCL is 
> > 
> > 
> > 
> > //STEP1 EXEC PGM=IEAMDBLG, 
> > //* PARM='DELETE(>000)' 
> > // PARM='HCFORMAT(CENTURY),COPY(>0),DELETE(>0)' 
> > //STEPLIB DD DSN=BCBSLIB.PROG,DISP=SHR 
> > //SYSLOG DD DSN=TS.OPERLOG.ARCHIVE(+1), 
> > // DISP=(NEW,CATLG,DELETE), 
> > // SPACE=(CYL,(100,300),RLSE), 
> > // RECFM=VB,LRECL=132,BLKSIZE=27984 
> > //SYSPRINT DD SYSOUT=* 
> > //SYSOUT DD SYSOUT=* 
> > 
> > 
> > 
> > 
> > 
> > Carmen Vitullo 
> > 
> > ----- Original Message ----- 
> > 
> > From: "John McKown" <[email protected]> 
> > To: [email protected] 
> > Sent: Friday, July 20, 2018 8:05:12 AM 
> > Subject: Re: SYSLOG and LOGR query 
> > 
> > On Fri, Jul 20, 2018 at 8:03 AM Vernooij, Kees (ITOPT1) - KLM < 
> > [email protected]> wrote: 
> > 
> > > That's clear: you changed the hardcopy device from Syslog to Operlog, 
> > > i.s.o. adding operlog. Writelog started SYSLOG as hardcopy device. 
> > > 
> > > When you see all log in SDSF's LOG O, it is available in the 
> logstream, 
> > no 
> > > doubt about that. 
> > > Getting it out seems to be a IEAMDBLG problem. Maybe someone has a 
> > working 
> > > example. Is there no utility, like IFASMFDL for SMF, to read Operlog 
> > > parameter driven? 
> > > 
> > 
> > ​This is an example from long ago. It prints and deletes all the OPERLOG 
> > information. 
> > 
> > //OPERLOG EXEC PGM=IEAMDBLG, 
> > // PARM='DELETE(>0),HCFORMAT(CENTURY)' 
> > //STEPLIB DD DSN=TSH009.LI.LINKLIB, 
> > // DISP=SHR 
> > //SYSLOG DD SYSOUT=* 
> > //​ 
> > 
> > 
> > 
> > > 
> > > Grtn, 
> > > Kees. 
> > > 
> > > 
> > > 
> > -- 
> > There is no such thing as the Cloud. It is just somebody else’s 
> computer. 
> > 
> > Maranatha! <>< 
> > John McKown 
> > 
> > ---------------------------------------------------------------------- 
> > For IBM-MAIN subscribe / signoff / archive access instructions, 
> > send email to [email protected] with the message: INFO IBM-MAIN 
> > 
> > 
> > ---------------------------------------------------------------------- 
> > For IBM-MAIN subscribe / signoff / archive access instructions, 
> > send email to [email protected] with the message: INFO IBM-MAIN 
> > 
> 
> ---------------------------------------------------------------------- 
> For IBM-MAIN subscribe / signoff / archive access instructions, 
> send email to [email protected] with the message: INFO IBM-MAIN 
> 
> 
> ---------------------------------------------------------------------- 
> For IBM-MAIN subscribe / signoff / archive access instructions, 
> send email to [email protected] with the message: INFO IBM-MAIN 
> 

---------------------------------------------------------------------- 
For IBM-MAIN subscribe / signoff / archive access instructions, 
send email to [email protected] with the message: INFO IBM-MAIN 


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to