Wolfgang, Can you copy/paste the held screen so that we have a better idea of which messages might be causing the problem?
Could you change the CP directory entry's "COMMAND TERM HOLD OFF" to be "COMMAND TERM HOLD OFF MORE 0 0"? Then, in the OPERATOR's PROFILE EXEC change it to "CP TERM MORE n n" with more appropriate "MORE" times? It's worth a try until we better understand the root cause. Mike Walter Aon Corporation The opinions expressed herein are mine alone, not my employer's. From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Buettner, Wolfgang Sent: Monday, July 18, 2011 9:54 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Behaviour after restart After a system restart OPERATOR's console hangs on its very first screen in HOLDING status (I guess due to the fact that some system messages are highlighted) and is waiting until the screen is cleared manually. Though there is not any other prompt to be answered and the system itself continues to start-up, that HOLDING seems to prevent OPERATOR from loading CMS and/or starting its profile and other automatic processes immediately after the virtual machine OPERATOR was started by system. It appears it's not yet the turn of "COMMAND TERM HOLD OFF" which is defined in the CP Directory. So, is there a CONFIG statement or anything else to manage that? Thank you, Wolfgang Buettner Software AG - Group Executive Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Arnd Zinnhardt, Mark Edwards, David Broadbent, Dr. Hans Kraus, Dr. Wolfram Jost, Kamyar Niroumand, Ivo Totev Sitz/Registered office: Uhlandstraße 12, 64297 Darmstadt, Germany, - Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/ Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), David Broadbent, Dr. Wolfram Jost, Arnd Zinnhardt; - Aufsichtsratsvorsitzender/ Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com
