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 the link mode on the 191 MDISK of OPERATOR? 2008/7/18 Scott Rohling <[EMAIL PROTECTED]>: > 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 <MMMMMM| SHUTDOWN> and > system > console not VM operator console. > > Explanation: This message appears at system restart after a CP system > failure > or SHUTDOWN REIPL command. This occurs only if the system operator was not > logged onto the primary system console at the time the system failure or > SHUTDOWN REIPL occurred. > > OPERATOR was running disconnected when the reipl occurred. The result is > that PROP is no longer running on OPERATOR when the system reipls as it > appears the PROFILE EXEC for OPERATOR is not executed. > > Since it's typical to run OPERATOR disconnected and not logged into the > system console - this doesn't really make sense to me. Why is OPERATOR > 'reconnected' instead of doing a full login? > > Has anyone run into this? How do you keep PROP running on OPERATOR after a > SHUTDOWN REIPL? > > Thanks for any insight! > > Scott Rohling > -- Kris Buelens, IBM Belgium, VM customer support
