Hi Kevin,
Is there a sample that does include the OPERLOG info that does not fit into the SYSLOG format? Thanks, Linda ----- Original Message ----- From: "W. Kevin Kelley" <[email protected]> To: [email protected] Sent: Thursday, March 10, 2011 5:26:47 PM Subject: Re: operlog On Thu, 10 Mar 2011 12:11:55 -0600, Mark Zelden <[email protected]> wrote: > >You never "need" OPERLOG - be it monoplex or in a sysplex. > >Even though the main benefit of OPERLOG is thought to be a single >source of "syslog" data from multiple systems in a sysplex, there can >still be benefits in a monoplex. Some benefits are: > >1) An extra source of "syslog" data in case the JES2 syslog is lost >for some reason (purged, save process error, catastrophic error that >forces a JES2 cold start, etc.). > >2) Data gets written to the operlog even after JES2 is brought down. >You will never see that data in the JES2 syslog. > >3) SDSF provides use of the FILTER command for OPERLOG, but does >not have any filter capability for syslog. > >VARY OPERLOG,HARDCPY is the way to activate the OPERLOG on a running >system assuming you have met the prerequisites. The prerequisite is >having the system logger configured. You would need to define a >DASD ONLY logstream for the operlog. > >After it is activated via command, you would add this to your PARMLIB's >CONSOLxx member so activates at the next IPL: > >HARDCOPY DEVNUM(SYSLOG,OPERLOG) > >Hope this helps. > A few other considerations: 1) The OPERLOG contains some information which is not available in the SYSLOG (we ran out of columns in the SYSLOG in which to place any more information). In particular, the message descriptor codes are available in the OPERLOG; they are not available in the SYSLOG. You can see what information is stored in the OPERLOG by taking a look at the MDB (Message Data Block) mapping. This is the same block we use to pass information to EMCS consoles. 2) The OPERLOG typically takes up more space than an equivalent SYSLOG for the same number of messages. 3) The OPERLOG is stored in binary form and must be formatted to be read. We provide a sample program in SYS1.SAMPLIB for formatting the OPERLOG into (readable) SYSLOG format. Note that information which cannot be fit into the SYSLOG format is ignored by the program. W. Kevin Kelley -- IBM POK Lab -- z/OS Core Technical Development ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
