CP SET RUN ON is already in the PROFILE EXEC - but I'll try out AUTOREAD OFF -- Thanks!
Scott Rohling On Mon, Sep 29, 2008 at 10:16 AM, Jim Bohnsack <[EMAIL PROTECTED]> wrote: > If you include SET AUTOREAD OFF at the end of your PROFILE EXEC that should > take care of it. It's a CMS command so don't precede it with CP. Take a > look at HELP. > > Jim > > Scott Rohling wrote: > >> ------=_Part_42470_28892394.1222702898551 >> Content-Type: text/plain; charset=ISO-8859-1 >> Content-Transfer-Encoding: 7bit >> Content-Disposition: inline >> >> 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 >> >> ------=_Part_42470_28892394.1222702898551 >> Content-Type: text/html; charset=ISO-8859-1 >> Content-Transfer-Encoding: 7bit >> Content-Disposition: inline >> >> <div dir="ltr">Ok - this is an extremely basic question and I'm >> slightly embarrassed to ask it - but here goes:<br><br>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.<br> >> <br>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. <br><br>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 .. <br> >> <br>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?<br><br>Thanks for any assistance..<br><br>Scott >> Rohling<br> >> </div> >> >> ------=_Part_42470_28892394.1222702898551-- >> >> >> > > -- > Jim Bohnsack > Cornell University > (972) 596-6377 home/office > (972) 342-5823 cell > [EMAIL PROTECTED] >
