"historically" might be right. Certainly since Programmable Operator came along (IIRC) in VM/SP R3, running CMS on OPERATOR has been a "GOOD THING". Later, more advanced console management products (IBM Operations Manager for z/VM, VM:Operator from CA, etc.) have vastly improved automation and productivity - to say nothing of all the pretty colored messages!
These here days computer operators have much better and more advanced places to play Adventure, Zork, Pong, and all the rest. There's this cool thing called an Atari, and another - a Magnavox Odyssey (just supply your own TV as a monitor)... well, we were speaking "historically", right? :-) Mike Walter Hewitt Associates The opinions expressed herein are mine alone, not my employer's. "Dave Wade" <[email protected]> Sent by: "The IBM z/VM Operating System" <[email protected]> 03/30/2010 02:49 PM Please respond to "The IBM z/VM Operating System" <[email protected]> To [email protected] cc Subject Re: After getting PerfKit working... > -----Original Message----- > From: The IBM z/VM Operating System > [mailto:[email protected]] On Behalf Of Alan Altmark > Sent: 30 March 2010 20:40 > To: [email protected] > Subject: Re: After getting PerfKit working... > > > On Tuesday, 03/30/2010 at 03:30 EDT, Dave Wade > <[email protected]> wrote: > > I always thought allowing OPERATOR to IPL CMS was a BAD thing. Its > > been a while since I used VM but in the past issues like this were > often > > spool related. Is something flooding the spool.. > > As a general rule, the key system operation user IDs should > IPL 190, not > CMS in order to reduce the dependency on the spool. I was thinking IPL any thing as historically they didn't have a 190 or 191 and so couldn't run anything, inlcuding games. > If you're using > something like IBM Operations Manager for z/VM to create > console logs, > then you eliminate still another spool touchpoint. > > Alan Altmark > z/VM Development > IBM Endicott The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
