PROP not running on OPERATOR after REIPL

2008-07-18 Thread Scott Rohling
Seeing something a bit strange and wondering if anyone has any insight. When doing a SHUTDOWN REIPL (issued from the OP1 userid), we get the following message at restart: HCPUSO967I -- the help for this message indicates: HCP967I Disconnect userid - system restarted MM| SHUTDOWN and

Re: PROP not running on OPERATOR after REIPL

2008-07-18 Thread Kris Buelens
That's a security measure, otherwise one could get into OPERATOR by IPLing VM. But, no matter what, OPERATOR should have executed its PROFILE EXEC. Have a look in the SPOOLed CONSOLE of OPERATOR and look for error messages: - is there an IPL CMS in the CP directory entry for OPERATOR? - what's

Re: PROP not running on OPERATOR after REIPL

2008-07-18 Thread Huegel, Thomas
Rohling Sent: Friday, July 18, 2008 8:11 AM To: IBMVM@LISTSERV.UARK.EDU Subject: PROP not running on OPERATOR after REIPL Seeing something a bit strange and wondering if anyone has any insight. = When doing a SHUTDOWN REIPL (issued from the OP1 userid), we get the following message at restart

Re: PROP not running on OPERATOR after REIPL

2008-07-18 Thread Scott Rohling
Thanks -- we are suspecting that perhaps OP1 was SYSOPER, and I'm going to have my customer put SET SYSOPER OPERATOR in both OPERATOR and OP1 PROFILE EXEC. On the OP1 id - I'm also going to put the following in if OPERATOR is not logged on: 'XAUTOLOG OPERATOR SYNCH' 'SET SYSOPER OPERATOR'

Re: PROP not running on OPERATOR after REIPL

2008-07-18 Thread Kris Buelens
The SET SYSOPER command should not affect the starting of PROP **it will not cure the problem you are seeing.** When z/VM is IPLed, it will autolog the system operator (whose userid is indicated in SYSTEM CONFIG). The CP directory can instruct your operator to IPL CMS Then its PROFILE EXEC can

Re: PROP not running on OPERATOR after REIPL

2008-07-18 Thread Alan Altmark
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

Re: PROP not running on OPERATOR after REIPL

2008-07-18 Thread Scott Rohling
:-) I enjoyed the apt metaphors, Alan... Thanks to Kris, Thomas, and Alan for their suggestions.. I'll work with the customer to try and determine what the real scenario might have been, as there is some confusion there. I was also give a training session on this system and doing some

Re: PROP not running on OPERATOR after REIPL

2008-07-18 Thread Rob van der Heij
On Fri, Jul 18, 2008 at 4:32 PM, Alan Altmark [EMAIL PROTECTED] wrote: (Sorry - it's VM Week on the Discovery Channel.) You made my week, Sir ! Too bad it's already friday...

Re: PROP not running on OPERATOR after REIPL

2008-07-18 Thread Kris Buelens
Find the spooled console: CP collects everything, from the first message on, that is, even from before the spool is actually open. It should reveal every LOGON/LOGOFF of OPERATOR etc. 2008/7/18 Scott Rohling [EMAIL PROTECTED]: :-) I enjoyed the apt metaphors, Alan... Thanks to Kris,

Re: PROP not running on OPERATOR after REIPL

2008-07-18 Thread David Boyes
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 Lions and tigers and bears...