I saw the same, or a similar problem a couple of years ago. It had something to do with the terminal emulator I was using. I had the problem with Vista emulator from Tom Brennan Software. Switching to a different emulator for the 2nd level system cured it and after installing an RSU or something, the problem went away and I could go back to Vista.

Sorry, but I don't remember any details about the problem.

Jim

On 7/18/2011 12:14 PM, Mike Walter wrote:
Wolfgang,

That certainly helps! =20
Counting the number of lines, I see that your OPERATOR goes into HOLDING at=
  the 30th displayed line:
   17:19:36 HCPIOP952I 0064M system storage  =20

Meanwhile, our OPERATOR continues on without HOLDING where the 36th message=
  at logon (last night) was:
   20:27:39 HCPIOP952I 15488M system storage                                =
       =20

I'm guessing that on your system, the OPERATOR virtual machine had logged o=
n, but there was a timing "race" between the IPL messages being issued, and=
  OPERATOR's "COMMAND" statement being processed as the virtual machine was =
being built and connected.

But then why does our OPERATOR consistently IPL (every week) without droppi=
ng into HOLDING? =20

Perhaps, just perhaps, it is because we being up OPERATOR on a model 4 term=
inal (42 lines x 80 wide).  That may be permitting the 36+ lines to display=
  before the PROFILE EXEC on our OPERATOR execute the command:
   'CP TERMINAL MORE 15 0 HOLD OFF'
Note: that is not present in the directory as a COMMAND statement.  Our OPE=
RATOR's directory COMMAND statements contain only:
   COMMAND SPOOL CONSOLE * CLASS C START NAME OPERATOR CONSOLE=20
   COMMAND SET SYSOPER *                                      =20

Can you try again with a model 4 terminal for OPERATOR?  There may be other=
  ways to resolve this, but again, it can't hurt until a better solution is =
devised.

It might be worth opening a PMR with IBM requesting a means in SYSTEM CONFI=
G to force the IPL console into "TERMINAL HOLD OFF MORE n n" immediately, e=
ven before OPERATOR logs on.

Could this be a 2nd level system?  That could present a whole different set=
  of circumstances.

Mike Walter
Aon Corporation
The opinions expressed herein are mine alone, not my employer's.







-----Original Message-----
From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Beh=
alf Of Buettner, Wolfgang
Sent: Monday, July 18, 2011 10:26 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Behaviour after restart

Mike,

I have changed the COMMAND TERM statement as suggested ... unfortunately no=
thing has changed.

Meanwhile, our system


Here is that screen in question:

  17:19:33 z/VM SYSTEM RESTART FROM SHUTDOWN REIPL                          =
     =20
  17:19:33 z/VM  V6 R1.0  SERVICE LEVEL 1003 (64-BIT)                       =
     =20
  17:19:33 SYSTEM NUCLEUS CREATED ON 2011-07-15 AT 17:54:28, LOADED FROM VZG=
61R =20
17:19:33                                                                   =
     =20
17:19:33 ****************************************************************  =
     =20
17:19:33 * LICENSED MATERIALS - PROPERTY OF IBM*                        *  =
     =20
17:19:33 *                                                              *  =
     =20
17:19:33 * 5741-A07 (C) COPYRIGHT IBM CORP. 1983, 2009. ALL RIGHTS      *  =
     =20
17:19:33 * RESERVED. US GOVERNMENT USERS RESTRICTED RIGHTS - USE,       *  =
     =20
17:19:33 * DUPLICATION OR DISCLOSURE RESTRICTED BY GSA ADP SCHEDULE     *  =
     =20
17:19:33 * CONTRACT WITH IBM CORP.                                      *  =
     =20
17:19:33 *                                                              *  =
     =20
17:19:33 * * TRADEMARK OF INTERNATIONAL BUSINESS MACHINES.              *  =
     =20
17:19:33 ****************************************************************  =
     =20
17:19:33                                                                   =
     =20
  17:19:33 HCPZCO6718I Using parm disk 1 on volume VZG61R (device 5364).    =
     =20
  17:19:33 HCPZCO6718I Parm disk resides on cylinders 39 through 158.       =
     =20
17:19:33 The directory on volume VZG61R at address 5364 has been brought on=
line.
  17:19:35 HCPWRS2513I                                                      =
     =20
  17:19:35 HCPWRS2513I Spool files available      575                       =
     =20
  17:19:36 HCPWRS2512I Spooling initialization is complete.                 =
     =20
17:19:36 DASD 5139 dump unit CP IPL pages 7696                             =
     =20
17:19:36 HCPAAU2700I System gateway DAEZ identified.                       =
     =20
17:19:36 z/VM Version 6 Release 1.0, Service Level 1003 (64-bit),          =
     =20
17:19:36 built on IBM Virtualization Technology                            =
     =20
17:19:36 There is no logmsg data                                           =
     =20
17:19:36 FILES: 0044 RDR, 0040 PRT,   NO PUN                               =
     =20
17:19:36 LOGON AT 17:19:36 CES MONDAY 07/18/11                             =
     =20
17:19:36 GRAF  0009 LOGON  AS  OPERATOR USERS =3D 1                        =
       =20
17:19:36 HCPIOP952I 0064M system storage                                   =
     =20
                                                                            =
     =20
                                                             HOLDING   DAEZ =
     =20
___________________________________________________________________________=
_____
The indented lines above appear highlighted on the screen.

Wolfgang

  =20

-----Original Message-----
From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Beh=
alf Of Mike Walter
Sent: Monday, July 18, 2011 5:09 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Behaviour after restart

Wolfgang,

Can you copy/paste the held screen so that we have a better idea of which m=
essages might be causing the problem?

Could you change the CP directory entry's "COMMAND TERM HOLD OFF" to be "CO=
MMAND TERM HOLD OFF MORE 0 0"?=20
Then, in the OPERATOR's PROFILE EXEC change it to "CP TERM MORE n n" with m=
ore appropriate "MORE" times? =20

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 Beh=
alf Of Buettner, Wolfgang
Sent: Monday, July 18, 2011 9:54 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Behaviour after restart

After a system restart=A0OPERATOR's console hangs on its very=A0first=A0scr=
een in HOLDING status (I guess=A0due to the fact that=A0some system=A0messa=
ges are highlighted) and is waiting until the screen is cleared manually. T=
hough=A0there is not any other prompt to be answered and the system itself=
=A0continues to start-up, that HOLDING=A0seems=A0to prevent=A0OPERATOR from=
  loading CMS and/or starting its profile and other automatic processes=A0im=
mediately after the virtual machine OPERATOR was started by system.
=A0
It appears it's not yet the turn of=A0"COMMAND TERM HOLD OFF"=A0which=A0is =
defined=A0in=A0the CP Directory.
=A0
So, is there a CONFIG statement or anything else to manage that?
=A0
Thank you,
Wolfgang Buettner

Software AG - Group Executive Board: Karl-Heinz Streibich (Vorsitzender/Cha=
irman), Arnd Zinnhardt, Mark Edwards, David Broadbent, Dr. Hans Kraus, Dr. =
Wolfram Jost, Kamyar Niroumand, Ivo Totev=20

Sitz/Registered office: Uhlandstra=DFe 12, 64297 Darmstadt, Germany, - Regi=
stergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/ Management =
Board: Karl-Heinz Streibich (Vorsitzender/Chairman), David Broadbent, Dr. W=
olfram Jost, Arnd Zinnhardt; - Aufsichtsratsvorsitzender/ Chairman of the S=
upervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com=20

--
James Bohnsack
(972) 596-6377 home/office
(972) 342-5823 cell

Reply via email to