Re: set run on
And, the last piece of information that was not yet added: CP SET RUN ON tells that the virtual machine keeps running when it is in CP READ state. 2007/5/22, Ray Mansell [EMAIL PROTECTED]: Duane Weaver wrote: The Operator on my system has SET RUN ON. Yet it still shows a VM READ all the time. Why? The other appenders are correct - you should include the CMS command SET AUTOREAD OFF in the operator's PROFILE EXEC. Note that SET AUTOREAD is a CMS command, while SET RUN is a CP command. AUTOREAD is a feature that harks back to 2741 (i.e. typewriter) terminal days when the terminal was either in receive or transmit mode. AUTOREAD ON meant that when CMS was ready to accept input it would send a READ to the terminal, enabling you to type. However, in this mode, any output from the system could not be sent until the next time you pressed the ENTER (or some other interrupt) key. With AUTOREAD OFF, such system output could be sent immediately, but the keyboard was disabled and you had to press the ATTN key to unlock it. Fun times. With the advent of the 3270 screen, there was no longer a need for this feature, since whatever you typed on the keyboard was buffered in the terminal. When you pressed ENTER, an attention was sent to the system, which in turn would issue a read to the terminal, which in its turn would send the contents of it buffer to the system. Even though AUTOREAD was no longer required, it was retained for compatibility (just like SET BLIP :-) ) For historical reasons, the default for AUTOREAD is ON if the virtual machine is autologged, and OFF if you logon from a terminal (I forget why). If you have a userid which is ever likely to be autologged, you'll probably want to include SET AUTOREAD OFF in its profile exec. Ray Mansell -- Kris Buelens, IBM Belgium, VM customer support
Re: set run on
Try doing a 'SET AUTOREAD OFF'. If it goes to 'RUNNING' then maybe you ca n add it to the PROFILE EXEC. /Tom Kern On Tue, 22 May 2007 08:56:11 -0400, Duane Weaver [EMAIL PROTECTED] wrot e: The Operator on my system has SET RUN ON. Yet it still shows a VM READ all the time. Why?
Re: set run on
Try, SET AUTOREAD OFF Rick Bourgeois, President Virtual Software Systems, Inc. 7715 Browns Bridge Rd Gainesville, GA 30506 [EMAIL PROTECTED] 770-781-3200 -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Duane Weaver Sent: Tuesday, May 22, 2007 8:56 AM To: IBMVM@LISTSERV.UARK.EDU Subject: set run on The Operator on my system has SET RUN ON. Yet it still shows a VM READ all the time. Why?
Re: set run on
I see that all of the time on OPERATOR ids. Enter SET AUTOREAD OFF in addition to SET RUN ON. Why?? Who knows. Jim Duane Weaver wrote: The Operator on my system has SET RUN ON. Yet it still shows a VM READ all the time. Why? -- Jim Bohnsack Cornell University (607) 255-1760 [EMAIL PROTECTED]
Re: set run on
Thanks guys. I am not sure what caused AUTOREAD to be set on. I even logged Operator off and back on to make sure there was something setting autoread on. Now that I know, I will keep watch to see what happens. duane At 09:09 AM 5/22/2007, you wrote: I see that all of the time on OPERATOR ids. Enter SET AUTOREAD OFF in addition to SET RUN ON. Why?? Who knows. Jim Duane Weaver wrote: The Operator on my system has SET RUN ON. Yet it still shows a VM READ all the time. Why? -- Jim Bohnsack Cornell University (607) 255-1760 [EMAIL PROTECTED]
Re: set run on
Duane Weaver wrote: The Operator on my system has SET RUN ON. Yet it still shows a VM READ all the time. Why? The other appenders are correct - you should include the CMS command SET AUTOREAD OFF in the operator's PROFILE EXEC. Note that SET AUTOREAD is a CMS command, while SET RUN is a CP command. AUTOREAD is a feature that harks back to 2741 (i.e. typewriter) terminal days when the terminal was either in receive or transmit mode. AUTOREAD ON meant that when CMS was ready to accept input it would send a READ to the terminal, enabling you to type. However, in this mode, any output from the system could not be sent until the next time you pressed the ENTER (or some other interrupt) key. With AUTOREAD OFF, such system output could be sent immediately, but the keyboard was disabled and you had to press the ATTN key to unlock it. Fun times. With the advent of the 3270 screen, there was no longer a need for this feature, since whatever you typed on the keyboard was buffered in the terminal. When you pressed ENTER, an attention was sent to the system, which in turn would issue a read to the terminal, which in its turn would send the contents of it buffer to the system. Even though AUTOREAD was no longer required, it was retained for compatibility (just like SET BLIP :-) ) For historical reasons, the default for AUTOREAD is ON if the virtual machine is autologged, and OFF if you logon from a terminal (I forget why). If you have a userid which is ever likely to be autologged, you'll probably want to include SET AUTOREAD OFF in its profile exec. Ray Mansell
