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
