>That is a minor benefit. Not to me, it isn't. To me this is a HUGE benefit. I am the one who is supposed to figure out why 'automation didn't work' during system shutdown, especially when the operator forced down Jes2 after he couldn't see the jobs/stcs that hadn't come down *before* JES. Or when they say 'automation didn't terminate'. Try to find out why when there is no syslog, no automation log, no joblog (the thing is started sub=mstr)....
They are especially fond of saying 'the system doesn't come down' on the monoplexes (where we didn't have operlog) until I got so fed up that I forced the setup of operlog even on the monoplexes. >The big benefit is having all the logs for the sysplex >combined in one place when trying to diagnose a problem. *That* is considered a big drawback here! When I established operlog here, I got temporary update access to all ISPF profiles for the company to change the default log a in SDSF to log s to not 'irritate everybody'. I admit that I go to syslog, too, when I have to check for a problem that I know is limited to one system, mostly when that system doesn't output a lot of lines. Scrolling past all the stuff from other systems that output a lot is tiresom. (And yes, I know about operlog viewer...) The thing that I really hate is that it also takes just about forever when I look into syslog - log s (even on the same system). Barbara -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger ---------------------------------------------------------------------- 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
