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
