Ok - this is an extremely basic question and I'm slightly embarrassed to ask
it - but here goes:

OPERATOR is not running PROP at this installation --  There was also no IPL
statement in OPERATOR directory until I started futzing around -- creating a
PROFILE EXEC to make sure OPERATOR console was spooled to the logs
collector  - and putting an IPL 190 PARM AUTOCR in the directory entry.

However - once the PROFILE EXEC is executed --   OPERATOR goes into a VM
READ  (I'm watching via SECUSER) and eventually gets forced off by the
system.

I just realized that OPERATOR was not SYSOPER as I was doing this -- but it
still doesn't seem normal that it would end up in VM READ ..

Can anyone tell me if this is normal behaviour - or if I really need to
execute something (do forever;"CP SLEEP 1 MIN";end) to get it to stay out of
VM READ?

Thanks for any assistance..

Scott Rohling

Reply via email to