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 start PROP 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. New question: was user OPERATOR still logged on when you detected the problem? The PROP software can not only run in user OPERATOR, it can run in any CMS user. PROP will filter all messages that that user would get on its screen. If you are a general user, there will probably not be many messages to filter, if however your PROP-running user is "secondary" user of some other server, this PROP will handle those; as "system operator" it will get the LOGON/LOGOFF/etc messages you are used to. So, second question: you can verify that PROP did indeed start after the REIPL. Look in its log file for a line telling that PROP was started: PROP running with routing table ..... shortly after the REIPL (CP Q CPLEVEL should tell you the IPL time in case you no longer remember). 2008/7/18 Scott Rohling <[EMAIL PROTECTED]>: > > 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' > > We'll see how that works out.. Thanks again for the speedy responses! > > Scott Rohling > > > -- Kris Buelens, IBM Belgium, VM customer support
