On Thu, 10 Mar 2011 16:58:03 +0800, ibmnew <[email protected]> wrote: >Hi all > > Our shop is a single image on z/OS 1.11 > > Do we need to issue 'VARY OPERLOG,HARDCPY' command? > > Do the single image need OPERLOG? > >Any suggestion would be helpful! >
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. Regards, Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:[email protected] Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ *** Please note the new URL for Mark's MVS Utilities *** ---------------------------------------------------------------------- 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
