Thanks, the "#CP VINPUT VMSG ...." helped me to get our system up!

 

But I'm still confused.  Back at home I have to 2nd level VMs named
VMTEST and VMNEW.  They IPL CMS and run an PROFILE EXEC.  Both are
exactly the same:

 

VMNEW:

/* */                                         

  Trace "O"                                   

  Address "COMMAND"                           

  nl="15"x                                    

  "CP SET RUN ON"                             

  Cmd="CP TERM CONMODE 3270"nl||,             

      "CP IPL 06F8 CLEAR LOADPARM 0009"       

  Queue Cmd                                   

Exit                                          

 

VMTEST:

/* */                                         

  Trace "O"                                   

  Address "COMMAND"                           

  nl="15"x                                    

  "CP SET RUN ON"                             

  Cmd="CP TERM CONMODE 3270"nl||,             

      "CP IPL 06F8 CLEAR LOADPARM 0009"       

  Queue Cmd                                   

Exit                                          

 

Yet, they IPL differently (VMNEW is 6.1 and VMTEST is 5.4 @ 1003):

 

VMNEW:

17:37:06 z/VM  V6 R1.0  SERVICE LEVEL 0901 (64-BIT)


17:37:06 SYSTEM NUCLEUS CREATED ON 2009-09-11 AT 16:51:48, LOADED FROM
610RES

17:37:06


17:37:06
****************************************************************    

17:37:06 * LICENSED MATERIALS - PROPERTY OF IBM*
*    

17:37:06 *
*    

17:37:06 * 5741-A07 (C) COPYRIGHT IBM CORP. 1983, 2009. ALL RIGHTS
*    

17:37:06 * RESERVED. US GOVERNMENT USERS RESTRICTED RIGHTS - USE,
*    

17:37:06 * DUPLICATION OR DISCLOSURE RESTRICTED BY GSA ADP SCHEDULE
*    

17:37:06 * CONTRACT WITH IBM CORP.
*    

17:37:06 *
*    

17:37:06 * * TRADEMARK OF INTERNATIONAL BUSINESS MACHINES.
*    

17:37:06
****************************************************************    

17:37:06


17:37:06 HCPZCO6718I Using parm disk 1 on volume 610RES (device 06F8).


17:37:06 HCPZCO6718I Parm disk resides on cylinders 39 through 158.


17:37:06 Start ((Warm|Force|COLD|CLEAN) (DRain) (DIsable)  (NODIRect)


17:37:06       (NOAUTOlog)) or (SHUTDOWN)


H HCPSED6013A A CP read is pending.


 

VMTEST:

16:34:59 z/VM  V5 R4.0  SERVICE LEVEL 1003 (64-BIT)


 16:35:00 SYSTEM NUCLEUS CREATED ON 2011-03-31 AT 08:03:20, LOADED FROM
54BRES

16:35:00


16:35:00
****************************************************************     

16:35:00 * LICENSED MATERIALS - PROPERTY OF IBM*
*     

16:35:00 *
*     

16:35:00 * 5741-A05 (C) COPYRIGHT IBM CORP. 1983, 2008. ALL RIGHTS
*     

16:35:00 * RESERVED. US GOVERNMENT USERS RESTRICTED RIGHTS - USE,
*     

16:35:00 * DUPLICATION OR DISCLOSURE RESTRICTED BY GSA ADP SCHEDULE
*     

16:35:00 * CONTRACT WITH IBM CORP.
*     

16:35:00 *
*     

16:35:00 * * TRADEMARK OF INTERNATIONAL BUSINESS MACHINES.
*     

16:35:00
****************************************************************     

16:35:00


 16:35:00 HCPZCO6718I Using parm disk 1 on volume 54BRES (device 06F8).


 16:35:00 HCPZCO6718I Parm disk resides on cylinders 39 through 158.


 16:35:00 HCPZPQ6809E This processor does not support dynamic I/O
changes     

16:35:00 Start ((Warm|Force|COLD|CLEAN) (DRain) (DIsable)  (NODIRect)


16:35:00       (NOAUTOlog)) or (SHUTDOWN)


16:35:36 WARM DR NOAUTO


16:35:36 NOW 16:35:36 CDT MONDAY 2011-06-20


16:35:36 Change TOD clock (Yes|No)


 

 

Frank M. Ramaekers Jr.

 

 

________________________________

From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On
Behalf Of Kris Buelens
Sent: Monday, June 20, 2011 8:12 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Problems at DR test

 

You z/VM system didn't find a 3270 console, so it is using the "System
console"  As you run second level, you an respond to VM questions using
   #CP VINPUT VMSG xxxx
To make it easier:
before you IPL, issue
   CP Q V CONS
   note the address, often 009
   CP TERM CONMODE 3270
   CP IPL xxxx LOADPARM CONS=yyyy
(xxxx is the disk your VM resident is on; yyyy is the address you found
in Q V CONS)

2011/6/20 Frank M. Ramaekers <framaek...@ailife.com>

I'm attempting to bring up our VM system under 2nd level at the DR site.
The problem that I'm running into is:

 

08:58:10 HCPZCO6718I Using parm disk 1 on volume 610RES (device 06F8)

08:58:10 HCPZCO6718I Parm disk resides on cylinders 39 through 158.  

08:58:10 Start ((Warm|Force|COLD|CLEAN) (DRain) (DIsable)  (NODIRect)

08:58:10       (NOAUTOlog)) or (SHUTDOWN)                            

H HCPSED6013A A CP read is pending.                                  

 

The HCPSED6013A seems to be the problem.  At our site, I have two VMs
that I can IPL under our z/VM 5.4.   One will IPL just fine (i.e. no
HCPSED6013A) the other doesn't' and displays this message.  Both VMs are
configured (DIRECT) the same.  I'm at a loss as to why this happens with
one and not the other.

 

We had no problems during the last DR, but we've applied z/VM 5.4
maintenance since then (1003).

 

Ideas?

 

 

 Frank M. Ramaekers Jr.

 



Systems Programmer

MCP, MCP+I, MCSE & RHCE

 

American Income Life Insurance Co.

Phone: (254)761-6649

 

1200 Wooded Acres Dr.

Fax: (254)741-5777

 

Waco, Texas  76701

 

 

 

_____________________________________________________ This message
contains information which is privileged and confidential and is solely
for the use of the intended recipient. If you are not the intended
recipient, be aware that any review, disclosure, copying, distribution,
or use of the contents of this message is strictly prohibited. If you
have received this in error, please destroy it immediately and notify us
at privacy...@ailife.com. 




-- 
Kris Buelens,
IBM Belgium, VM customer support


_____________________________________________________
This message contains information which is privileged and confidential and is 
solely for the use of the
intended recipient. If you are not the intended recipient, be aware that any 
review, disclosure,
copying, distribution, or use of the contents of this message is strictly 
prohibited. If you have
received this in error, please destroy it immediately and notify us at 
privacy...@ailife.com.

Reply via email to