OPERATOR insists on VM READ ?
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
Re: OPERATOR insists on VM READ ?
Add 'CP SET RUN ON' to the PROFILE. Regards, Richard Schuh From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Scott Rohling Sent: Monday, September 29, 2008 8:42 AM To: IBMVM@LISTSERV.UARK.EDU Subject: OPERATOR insists on VM READ ? 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
Re: OPERATOR insists on VM READ ?
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=ltrOk - this is an extremely basic question and I#39;m slightly embarrassed to ask it - but here goes:brbrOPERATOR is not running PROP at this installation --nbsp; 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 collectornbsp; - and putting an IPL 190 PARM AUTOCR in the directory entry.br brHowever - once the PROFILE EXEC is executed --nbsp;nbsp; OPERATOR goes into a VM READnbsp; (I#39;m watching via SECUSER) and eventually gets forced off by the system.nbsp;nbsp; brbrI just realized that OPERATOR was not SYSOPER as I was doing this -- but it still doesn#39;t seem normal that it would end up in VM READ .. br brCan anyone tell me if this is normal behaviour - or if I really need to execute something (do forever;quot;CP SLEEP 1 MINquot;;end) to get it to stay out of VM READ?brbrThanks for any assistance..brbrScott Rohlingbr /div --=_Part_42470_28892394.1222702898551-- -- Jim Bohnsack Cornell University (972) 596-6377 home/office (972) 342-5823 cell [EMAIL PROTECTED]
Re: OPERATOR insists on VM READ ?
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=ltrOk - this is an extremely basic question and I#39;m slightly embarrassed to ask it - but here goes:brbrOPERATOR is not running PROP at this installation --nbsp; 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 collectornbsp; - and putting an IPL 190 PARM AUTOCR in the directory entry.br brHowever - once the PROFILE EXEC is executed --nbsp;nbsp; OPERATOR goes into a VM READnbsp; (I#39;m watching via SECUSER) and eventually gets forced off by the system.nbsp;nbsp; brbrI just realized that OPERATOR was not SYSOPER as I was doing this -- but it still doesn#39;t seem normal that it would end up in VM READ .. br brCan anyone tell me if this is normal behaviour - or if I really need to execute something (do forever;quot;CP SLEEP 1 MINquot;;end) to get it to stay out of VM READ?brbrThanks for any assistance..brbrScott Rohlingbr /div --=_Part_42470_28892394.1222702898551-- -- Jim Bohnsack Cornell University (972) 596-6377 home/office (972) 342-5823 cell [EMAIL PROTECTED]
Re: OPERATOR insists on VM READ ?
Does your IPL statement have parm autocr specified? Jim Hughes 603-271-5586 Its kind of fun to do the impossible. (Walt Disney) From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Scott Rohling Sent: Monday, September 29, 2008 11:42 AM To: IBMVM@LISTSERV.UARK.EDU Subject: OPERATOR insists on VM READ ? 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
Re: OPERATOR insists on VM READ ?
On Monday, 09/29/2008 at 12:46 EDT, Hughes, Jim [EMAIL PROTECTED] wrote: Does your IPL statement have parm autocr specified? From Scott's post, yes. However, CMS users that are XAUTOLOGed should NOT have PARM AUTOCR on the IPL statement. The reason is that XAUTOLOG will stack an ENTER to the virtual console on the assumption that CMS is going to issue a VM READ. The intent was for CP to automatically press ENTER. If CMS doesn't issue the read because of the PARM AUTOCR, however, the enter remains pending and the console is stuck with console input waiting or NOT ACCEPTED. At #CP ATTN will cause CMS to issue a VM READ, satisfying the pending console data and allowing additional console traffic. Unlike XAUTOLOG, LOGON does not stack the ENTER, so PARM AUTOCR is needed to avoid the VM READ at IPL. The PROFILE EXEC for OPERATOR would typically have - CP TERM MODE VM (system operator defaults to MODE CP) - SET AUTOREAD OFF The queued() and externals() functions provide the means necessary to build a PROFILE EXEC that can deal with PARM AUTOCR without regard to XAUTOLOG or LOGON. Alan Altmark z/VM Development IBM Endicott
Re: OPERATOR insists on VM READ ?
Yes it does -- And the answer appears to be issuing SET AUTOREAD OFF ! So a big thanks to Jim Bohnsack for that tidbit!! Thanks again to all who responded.. I love this mailing list :-) Scott Rohling On Mon, Sep 29, 2008 at 10:05 AM, Hughes, Jim [EMAIL PROTECTED]wrote: Does your IPL statement have parm autocr specified? Jim Hughes 603-271-5586 Its kind of fun to do the impossible. (Walt Disney) -- *From:* The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] *On Behalf Of *Scott Rohling *Sent:* Monday, September 29, 2008 11:42 AM *To:* IBMVM@LISTSERV.UARK.EDU *Subject:* OPERATOR insists on VM READ ? 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
Re: OPERATOR insists on VM READ ?
Aw shucks. Twarnt nothin. Jim Scott Rohling wrote: --=_Part_44881_7503930.1222708149051 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Yes it does -- And the answer appears to be issuing SET AUTOREAD OFF ! So a big thanks to Jim Bohnsack for that tidbit!! Thanks again to all who responded.. I love this mailing list :-) Scott Rohling On Mon, Sep 29, 2008 at 10:05 AM, Hughes, Jim [EMAIL PROTECTED]wrote: Does your IPL statement have parm autocr specified? Jim Hughes 603-271-5586 Its kind of fun to do the impossible. (Walt Disney) -- *From:* The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] *On Behalf Of *Scott Rohling *Sent:* Monday, September 29, 2008 11:42 AM *To:* IBMVM@LISTSERV.UARK.EDU *Subject:* OPERATOR insists on VM READ ? 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_44881_7503930.1222708149051 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline div dir=ltrYes it does --nbsp;nbsp; brbrAnd the answer appears to be issuing SET AUTOREAD OFF !nbsp;nbsp; So a big thanks to Jim Bohnsack for that tidbit!!brbrThanks again to all who responded..nbsp;nbsp; I love this mailing listnbsp; :-)br brScott Rohlingbrbrdiv class=gmail_quoteOn Mon, Sep 29, 2008 at 10:05 AM, Hughes, Jim span dir=ltrlt;a href=mailto:[EMAIL PROTECTED][EMAIL PROTECTED]/agt;/span wrote:brblockquote class=gmail_quote style=border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex; div bgcolor=white link=blue vlink=purple lang=EN-US div pfont color=blue size=1 face=Arial Unicode MSspan style=font-size: 9pt; color: blue;Does your IPL statement have parm autocr specified?/span/font/p pfont color=blue size=1 face=Arial Unicode MSspan style=font-size: 9pt; color: blue;nbsp;/span/font/p div p style=margin-bottom: 12pt;font color=blue size=2 face=Times New Romanspan style=font-size: 10pt; color: blue;br Jim Hughesbr 603-271-5586br quot;Its kind of fun to do the impossible.quot; (Walt Disney)/span/font/p /div div style=border-style: none none none solid; border-color: -moz-use-text-color -moz-use-text-color -moz-use-text-color blue; border-width: medium medium medium 1.5pt; padding: 0pt 0pt 0pt 4pt; div div style=text-align: center; align=centerfont size=3 face=Times New Romanspan style=font-size: 12pt; hr align=center size=3 width=100% /span/font/div pbfont size=2 face=Tahomaspan style=font-size: 10pt; font-family: Tahoma; font-weight: bold;From:/span/font/bfont size=2 face=Tahomaspan style=font-size: 10pt; font-family: Tahoma; The IBM z/VM Operating System [mailto:a href=mailto:IBMVM@LISTSERV.UARK.EDU; target=_blankIBMVM@LISTSERV.UARK.EDU/a] bspan style=font-weight: bold;On Behalf Of /span/bScott Rohlingbr bspan style=font-weight: bold;Sent:/span/b Monday, September 29, 2008 11:42 AMdiv class=Ih2E3dbr bspan style=font-weight: bold;To:/span/b a href=mailto:IBMVM@LISTSERV.UARK.EDU; target=_blankIBMVM@LISTSERV.UARK.EDU/abr bspan style=font-weight: bold;Subject:/span/b OPERATOR insists on VM READ ?/div/span/font/p /div pfont size=3 face=Times New Romanspan style=font-size: 12pt;nbsp;/span/font/p div pfont size=3 face=Times New Romanspan style=font-size: 12pt;Ok - this is an extremely basic question and I#39;m slightly embarrassed to ask it - but here goes:divdiv/divdiv class=Wj3C7cbr br OPERATOR is not running PROP at this installation --nbsp; 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 collectornbsp; - and putting an IPL 190 PARM AUTOCR in the directory entry.br br However - once the PROFILE EXEC is executed --nbsp;nbsp; OPERATOR goes into a VM READnbsp; (I#39;m watching via SECUSER) and eventually gets forced off by the system.nbsp;nbsp; br br I just realized that OPERATOR was not SYSOPER as I was doing this -- but it still doesn#39;t seem normal that it would end up in VM READ .. br br
