On Friday, 07/18/2008 at 10:00 EDT, Kris Buelens <[EMAIL PROTECTED]> wrote:
> When the operator logs off for some reason, the first user logging on > with CLASS A becomes "system operator". Including a CP SET SYSOPER > OPERATOR in the PROFILE EXEC of OPERATOR is handy indeed: it makes > that an XAUTOLOG OPERATOR is sufficient to to re-assign the "system > operator" task to OPERATOR. When the current sysoper logs off, CP goes into "hunt mode" and will check to see if any of the ALTERNATE_OPERATORS are logged on. If you are in the list, you are given the privilege of being the system operator. If no alternate is available, only then will CP lie low in the grass, waiting for an unsuspecting or weak sysprog to wander by, separated from the herd. You can hear the screams as the sysprog discovers (a) TERM MODE CP is in effect and commands aren't working right (b) there's an odd timestamp on every message (c) realizes what's happened (d) finally remembers "TERM MODE VM" (e) the system is having I/O errors she didn't know about (HCPERPxxxx) and that no one reported (f) her plans to go home in 5 minutes are busted (g) remembers whose dumb idea it was to put his or her own userid in the ALTERNATE_OPERATORS list At his point, CP, bloodlust sated, settles down to watch over his harem of virtual machines, secure in the knowledge The Operator will maintain order in the universe. (Sorry - it's "VM Week" on the Discovery Channel.) Alan Altmark z/VM Development IBM Endicott
