There is surely no advantage to varying OPERLOG off at shutdown. However, we should note that syslog also captures early messages from NIP onwards because they get buffered until JES starts. Nothing gets lost as long as JES starts in the same IPL.
OTOH, it's not clear what happens to OPERLOG messages after JES terminates. They're probably captured in a CF structure, but would we have access to that data after system shutdown? . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Vernooij, CP (ITOPT1) - KLM Sent: Monday, February 09, 2015 11:40 PM To: [email protected] Subject: Re: Vary OPEERLOG offline before IPLing the system? I see no reason and no negative impact, on the contrary: if you keep it running, you can see what's happening after JES and Syslog have stopped. The same applies to activities before JES2 starts. Kees. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Peter Hunkeler Sent: 10 February, 2015 8:37 To: [email protected] Subject: Vary OPEERLOG offline before IPLing the system? I found that automation is setup to vary operlog offline just before stopping JES2. I was trying to find a reference in the FMs recommending this. But no success. Why would we do this? If operlog is stopped, then we would loose all hardcopy messages from the time JES was brougt down until the system is brought doen (V XCF,....,OFFLINE), right? What (negative) impact is there if we don't stop operlog? -- Peter Hunkeler ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
