Re: Problems at DR test
I just made a test with a secondlevel z/VM system (it has 600-605, SYSG and SYSC as consoles in SYSTEM CONFIG) - #CP TERM CONMODE 3270#IPL LOADPARM CONS0009 - I DIAL to the secondlevel as 601, and logon to MAINT there - on the firstlevel system, I issue #CP DEF 9 1F - in the secondlevel's MAINT: SHUTDOWN REIPL == wait 1010 This proves that at SHUTDOWN REIPL CP did no longer look at the list of consoles in its SYSTEM CONFIG, it wanted 0009 and nothing else. 2011/6/22 Alan Altmark alan_altm...@us.ibm.com On Tuesday, 06/21/2011 at 02:40 EDT, gclo...@br.ibm.com wrote: Is SYSC the unique restriction? Another legacy of the last millennium? Restriction against what? It is the one unifying console interface. It works for all the OSes. If you know how to use it for one OS, you know how to use it for the others, both on the HMC and via #CP VINPUT VMSG. And it operates whether the guest is running in 3270 mode or 3215. Ideally, you shouldn't even have to code it in SYSTEM CONFIG. System_3270 (SYSG) and System_Console (SYSC) should be the consoles of last resort. If you don't specify any operator or emergency consoles, SYSG and SYSC are what you get. If the 3270 session is started, you get that. If not, you get the linemode console. Easy. The only time a 1010 would be given would be if an explicitly specified console at IPL wasn't available for use. And I have to think about whether I believe that SAPL parms or LOADPARM that are re-used on SHUTDOWN REIPL constitute explicitly specified -- I don't think so. IMO, for the purposes of abend restart and SHUTDOWN REIPL, that stored value is simply prepended to the operator and emergency console lists. Just come up on the next available operator console with a message that says PREVIOUS CONSOLE DEVICE 01F IS NO LONGER AVAILABLE. While we're Wishing, I would also wish that CP would accompany all IPL wait states with a message to the integrated console, including SPECIFIED CONSOLE DEVICE 009 IS NOT A 3270. (Natch, the system has to be able to come up far enough to allow CP to connect to SYSC!) The one wait state with no message would be the one for I can't establish a connection with the integrated console - something is seriously wrong. (If SYSC doesn't exist at all, that's a horse of a different color.) An always-on, always-there console changes the nature of traditional CP error reporting. Alan Altmark z/VM and Linux on System z Consultant IBM System Lab Services and Training ibm.com/systems/services/labservices office: 607.429.3323 mobile; 607.321.7556 alan_altm...@us.ibm.com IBM Endicott -- Kris Buelens, IBM Belgium, VM customer support
Re: Problems at DR test
Kris, I wasn't disputing the current state of affairs, but was expressing my opinion on how it *should* work. Regards, Alan Altmark IBM Lab Services - Sent from my BlackBerry Handheld.
Re: Problems at DR test
Have you submitted requirements? :-) Regards, Richard Schuh -Original Message- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Alan Altmark Sent: Wednesday, June 22, 2011 3:25 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Problems at DR test Kris, I wasn't disputing the current state of affairs, but was expressing my opinion on how it *should* work. Regards, Alan Altmark IBM Lab Services - Sent from my BlackBerry Handheld.
Re: Problems at DR test
On Wednesday, 06/22/2011 at 11:41 EDT, Schuh, Richard rsc...@visa.com wrote: Have you submitted requirements? :-) Why, no. I just figured I'd post here like everyone else and hope for a miracle. :-) [Certain People in the Lab will be disappointed to the know that I will be back in the office on Friday!] Alan Altmark Senior Managing z/VM and Linux Consultant IBM System Lab Services and Training ibm.com/systems/services/labservices office: 607.429.3323 mobile; 607.321.7556 alan_altm...@us.ibm.com IBM Endicott
Re: Problems at DR test
Frank M. Ramaekers writes: 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: [...] CP IPL 06F8 CLEAR LOADPARM 0009 [...] Yet, they IPL differently (VMNEW is 6.1 and VMTEST is 5.4 @ 1003): CP choose what operator console to use by looking through the devices listed in the Operator_Consoles statement in SYSTEM CONFIG (or overriden by CONS=nnn via SAL). The difference you saw would happen if VMTEST had your console address listed in Operator_Consoles (or CONS=0009 stamped into the SAL settings via SALIPL) and VMNEW did not. VMNEW would then fall through to the System_Console which usually sits at the end of the Operator_Console list and prompt you via SCLP/VINPUT. --Malcolm -- Malcolm Beattie Mainframe Systems and Software Business, Europe IBM UK
Re: Problems at DR test
I'm thinking, 'AUTO_IPL parameter on FEATURES statement missing in SYSTEM CONFIG on the 6.1 system' IIRC, the system does not ship with AUTO_IPL enabled - you have to make that change yourself. Example (fragment) from a SYSTEM CONFIG near me ... /**/ /* Features Statement */ /**/ Features , Auto_IPL WARM DRAIN, Auto_IPL_After_Restart WARM DRAIN, /* After RESTART ... */ Auto_IPL_After_Shutdown_Reipl WARM DRAIN, /* and SHUTDOWN REIPL */
Re: Problems at DR test
Ahhh, I knew there was a reason for it, just couldn't see it. VMTEST SYSTEM CONFIG: Operator_Consoles 6F00 6F20 6F01 6F21 0009, System_3270 System_Console Emergency_Message_Consoles 6F00 6F20 6F01 6F21 0009, System_Console (This is basically what we used at the DR site, but they have their VM console defined at 0001.) The VMNEW (as it was shipped) had the following (notice no console at 0009): Operator_Consoles 0020 0021 0022 0023 0E20 0E21 1020 , System_3270 System_Console Emergency_Message_Consoles 0020 0021 0022 0023 0E20 0E21 1020 , System_Console That completely explains it, THANKS! Frank M. Ramaekers Jr. -Original Message- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Malcolm Beattie Sent: Tuesday, June 21, 2011 2:48 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Problems at DR test Frank M. Ramaekers writes: 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: [...] CP IPL 06F8 CLEAR LOADPARM 0009 [...] Yet, they IPL differently (VMNEW is 6.1 and VMTEST is 5.4 @ 1003): CP choose what operator console to use by looking through the devices listed in the Operator_Consoles statement in SYSTEM CONFIG (or overriden by CONS=nnn via SAL). The difference you saw would happen if VMTEST had your console address listed in Operator_Consoles (or CONS=0009 stamped into the SAL settings via SALIPL) and VMNEW did not. VMNEW would then fall through to the System_Console which usually sits at the end of the Operator_Console list and prompt you via SCLP/VINPUT. --Malcolm -- Malcolm Beattie Mainframe Systems and Software Business, Europe IBM UK _ 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.
Re: Problems at DR test
Hi, This thread has brought up a question in my mind (maybe it's a dumb one, but I'll ask it anyway :)) Assumptions: 1) This is the default value for Operator_Consoles in the SYSTEM CONFIG file (and probably most shops do not delete or change the last two entries): Operator_Consoles 0020 0021 0022 0023 0E20 0E21 1020 , System_3270 System_Console 2) System_3270 == the Integrated 3270 console == the mnemonic SYSG 3) System_Console == the Operating System Messages window == the mnemonic SYSC As I understand it, the Operating System Messages window is always available to each LPAR. So if it is in most paths for z/VM to find a console, why should we ever see PSWs of 1010? Shouldn't z/VM always find the Operating System Messages window as a last resort? (I must have one of my assumptions wrong, because we do see 1010s). Thanks. Mike MacIsaac mike...@us.ibm.com (845) 433-7061
Re: Problems at DR test
On a 2nd level z/VM, these consoles don't exist -- so a wait 1010 is very possible... on a 1st level system, I agree with you - we'd have to hear more to figure it out, I think. I'm actually not seeing why console definitions are explaining why one of the Frank's guests IPL without a prompt, and the other stops at the prompt. To me, this is clearly due to the use of Auto_IPL in the SYSTEM CONFIG. If the prompt cannot be responded to - ok - that's about consoles ... but the original question is likely about a difference in the Features Auto_IPL setting.. which I suggesed pretty early on in this thread. Scott Rohling On Tue, Jun 21, 2011 at 6:57 AM, Michael MacIsaac mike...@us.ibm.comwrote: Hi, This thread has brought up a question in my mind (maybe it's a dumb one, but I'll ask it anyway :)) Assumptions: 1) This is the default value for Operator_Consoles in the SYSTEM CONFIGfile (and probably most shops do not delete or change the last two entries): Operator_Consoles 0020 0021 0022 0023 0E20 0E21 1020 , System_3270 System_Console 2) System_3270 == the Integrated 3270 console == the mnemonic SYSG 3) System_Console == the Operating System Messages window == the mnemonic SYSC As I understand it, the Operating System Messages window is always available to each LPAR. So if it is in most paths for z/VM to find a console, why should we ever see PSWs of 1010? Shouldn't z/VM always find the Operating System Messages window as a last resort? (I must have one of my assumptions wrong, because we do see 1010s). Thanks. Mike MacIsaac mike...@us.ibm.com (845) 433-7061
Re: Problems at DR test
Oh, it just cannot be responded to normally when 'HCPSED6013A A CP read is pending' is displayed. Instead all responses must be prefixed with #CP VINPUT VMSG '. Frank M. Ramaekers Jr. From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Scott Rohling Sent: Tuesday, June 21, 2011 8:10 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Problems at DR test On a 2nd level z/VM, these consoles don't exist -- so a wait 1010 is very possible... on a 1st level system, I agree with you - we'd have to hear more to figure it out, I think. I'm actually not seeing why console definitions are explaining why one of the Frank's guests IPL without a prompt, and the other stops at the prompt. To me, this is clearly due to the use of Auto_IPL in the SYSTEM CONFIG. If the prompt cannot be responded to - ok - that's about consoles ... but the original question is likely about a difference in the Features Auto_IPL setting.. which I suggesed pretty early on in this thread. Scott Rohling On Tue, Jun 21, 2011 at 6:57 AM, Michael MacIsaac mike...@us.ibm.com wrote: Hi, This thread has brought up a question in my mind (maybe it's a dumb one, but I'll ask it anyway :)) Assumptions: 1) This is the default value for Operator_Consoles in the SYSTEM CONFIG file (and probably most shops do not delete or change the last two entries): Operator_Consoles 0020 0021 0022 0023 0E20 0E21 1020 , System_3270 System_Console 2) System_3270 == the Integrated 3270 console == the mnemonic SYSG 3) System_Console == the Operating System Messages window == the mnemonic SYSC As I understand it, the Operating System Messages window is always available to each LPAR. So if it is in most paths for z/VM to find a console, why should we ever see PSWs of 1010? Shouldn't z/VM always find the Operating System Messages window as a last resort? (I must have one of my assumptions wrong, because we do see 1010s). Thanks. Mike MacIsaac mike...@us.ibm.com (845) 433-7061 tel:%28845%29%20433-7061 _ 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.
Re: Problems at DR test
Oh, it just cannot be responded to normally when ‘HCPSED6013A A CP read is pending’ is displayed. Instead all responses must be prefixed with “#CP VINPUT VMSG ‘. ** ** Frank M. Ramaekers Jr. ** ** ** ** -- * * Ok - that explains the console statements. If you want the systems to IPL identically then check out the Features statement in SYSTEM CONFIG. One appears to have Auto_IPL WARM DRAIN -- the other doesn't and you get HCPSED6013A and have to respond to a prompt. Glad you got through it all! Scott Rohling
Re: Problems at DR test
Hi, Mike. My own perception (of course, I can be wrong ;-) ) SYSC emules something like a 3215, not a 3270. When opened, SYSG emules a 3270. Depending of definitions on SYSTEM CONFIG, VM needs to send a 3270 screen, not possible on SYSC. Generate some Wait code, as the 1010. Example: IPL xxx LOADPARM SYSC will never be possible, SALIPL needs a 3270 screen. If the reply don't need a screen, only one line, the SYSC can be used, and the ipl continues. Regards, __ Clovis From: Michael MacIsaac mike...@us.ibm.com To: IBMVM@listserv.uark.edu Date: 21/06/2011 09:58 Subject: Re: Problems at DR test Sent by: The IBM z/VM Operating System IBMVM@listserv.uark.edu Hi, This thread has brought up a question in my mind (maybe it's a dumb one, but I'll ask it anyway :)) Assumptions: 1) This is the default value for Operator_Consoles in the SYSTEM CONFIG file (and probably most shops do not delete or change the last two entries): Operator_Consoles 0020 0021 0022 0023 0E20 0E21 1020 , System_3270 System_Console 2) System_3270 == the Integrated 3270 console == the mnemonic SYSG 3) System_Console == the Operating System Messages window == the mnemonic SYSC As I understand it, the Operating System Messages window is always available to each LPAR. So if it is in most paths for z/VM to find a console, why should we ever see PSWs of 1010? Shouldn't z/VM always find the Operating System Messages window as a last resort? (I must have one of my assumptions wrong, because we do see 1010s). Thanks. Mike MacIsaac mike...@us.ibm.com (845) 433-7061
Re: Problems at DR test
1) This is the default value for Operator_Consoles in the SYSTEM CONFIG file (and probably most shops do not delete or change the last two entries): Operator_Consoles 0020 0021 0022 0023 0E20 0E21 1020 , System_3270 System_Console As I understand it, the Operating System Messages window is always available to each LPAR. So if it is in most paths for z/VM to find a console, why should we ever see PSWs of 1010? Shouldn't z/VM always find the Operating System Messages window as a last resort? (I must have one of my assumptions wrong, because we do see 1010s). Related question: given the addresses listed in the default list seem kinda random, is there any reason why 009 *isn't* listed?
Re: Problems at DR test
my 2 cents: because most 009 consoles are defined as 3215 on z/VM guests. (as for the ones that are listed.. ummm.. darts? :-) Scott Rohling On Tue, Jun 21, 2011 at 8:09 AM, David Boyes dbo...@sinenomine.net wrote: 1) This is the default value for Operator_Consoles in the SYSTEM CONFIGfile (and probably most shops do not delete or change the last two entries): Operator_Consoles 0020 0021 0022 0023 0E20 0E21 1020 , System_3270 System_Console As I understand it, the Operating System Messages window is always available to each LPAR. So if it is in most paths for z/VM to find a console, why should we ever see PSWs of 1010? Shouldn't z/VM always find the Operating System Messages window as a last resort? (I must have one of my assumptions wrong, because we do see 1010s). Related question: given the addresses listed in the default list seem kinda random, is there any reason why 009 **isn’t** listed?
Re: Problems at DR test
Well, as has been mentioned ages ago here: when you IPL with an override for CONS, the list of consoles in SYSTEM CONFIG is replaced by the overide. So, if after an IPL with override VM is restarted (with SHUTDOWN REIPL or after an abend), and at that time that console isn't theren, you get wait 1010. (you get the override by typing CONS= in SAPL or coding CONS as LOADPARM). Some other point: the SYSC is always there: at first level it is on the HMC, at second level, the first level VM simulated the SYSC on the logon screen (and you use #CP VINPUT to respond). 2011/6/21 Michael MacIsaac mike...@us.ibm.com Hi, This thread has brought up a question in my mind (maybe it's a dumb one, but I'll ask it anyway :)) Assumptions: 1) This is the default value for Operator_Consoles in the SYSTEM CONFIGfile (and probably most shops do not delete or change the last two entries): Operator_Consoles 0020 0021 0022 0023 0E20 0E21 1020 , System_3270 System_Console 2) System_3270 == the Integrated 3270 console == the mnemonic SYSG 3) System_Console == the Operating System Messages window == the mnemonic SYSC As I understand it, the Operating System Messages window is always available to each LPAR. So if it is in most paths for z/VM to find a console, why should we ever see PSWs of 1010? Shouldn't z/VM always find the Operating System Messages window as a last resort? (I must have one of my assumptions wrong, because we do see 1010s). Thanks. Mike MacIsaac mike...@us.ibm.com (845) 433-7061 -- Kris Buelens, IBM Belgium, VM customer support
Re: Problems at DR test
On 6/21/2011 9:18 AM, Scott Rohling wrote: my 2 cents: because most 009 consoles are defined as 3215 on z/VM guests. (as for the ones that are listed.. ummm.. darts? :-) Scott Rohling On Tue, Jun 21, 2011 at 8:09 AM, David Boyes dbo...@sinenomine.net mailto:dbo...@sinenomine.net wrote: 1) This is the default value for Operator_Consolesin the SYSTEM CONFIGfile (and probably most shops do not delete or change the last two entries): Operator_Consoles 0020 0021 0022 0023 0E20 0E21 1020 , System_3270 System_Console As I understand it, the Operating System Messages window is always available to each LPAR. So if it is in most paths for z/VM to find a console, why should we ever see PSWs of 1010? Shouldn't z/VM always find the Operating System Messages window as a last resort? (I must have one of my assumptions wrong, because we do see 1010s). Related question: given the addresses listed in the default list seem kinda random, is there any reason why 009 **isn’t** listed? The other addresses listed are the default addresses of so 3274 and 3174 terminal controllers that were popular in the 1970's and 1980's. -- Stephen Frazier Information Technology Unit Oklahoma Department of Corrections 3400 Martin Luther King Oklahoma City, Ok, 73111-4298 Tel.: (405) 425-2549 Fax: (405) 425-2554 Mobile: (405) 464-7818 email: stevef%doc.state.ok.us
Re: Problems at DR test
On 6/21/2011 9:18 AM, Scott Rohling wrote: my 2 cents: because most 009 consoles are defined as 3215 on z/VM guests. (as for the ones that are listed.. ummm.. darts? :-) There's no reason why CP could not issue TERM CONMODE 3270, as Linux does when instructed to use a 3270 console. Even CMS issues TERM CONMODE 3215 when it IPLs. Alan Altmark z/VM and Linux on System z Consultant IBM System Lab Services and Training ibm.com/systems/services/labservices office: 607.429.3323 mobile; 607.321.7556 alan_altm...@us.ibm.com IBM Endicott
Re: Problems at DR test
There's no reason why CP could not issue TERM CONMODE 3270, as Linux does when instructed to use a 3270 console. Even CMS issues TERM CONMODE 3215 when it IPLs. I mean, really, mom... all the cool OSes do itwhine 8-) -- db PS- it's been one of those days. Laugh it up.
Re: Problems at DR test
Is SYSC the unique restriction? Another legacy of the last millennium? __ Clovis From: Alan Altmark alan_altm...@us.ibm.com To: IBMVM@LISTSERV.UARK.EDU Date: 21/06/2011 15:14 Subject: Re: Problems at DR test Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU On 6/21/2011 9:18 AM, Scott Rohling wrote: my 2 cents: because most 009 consoles are defined as 3215 on z/VM guests. (as for the ones that are listed.. ummm.. darts? :-) There's no reason why CP could not issue TERM CONMODE 3270, as Linux does when instructed to use a 3270 console. Even CMS issues TERM CONMODE 3215 when it IPLs. Alan Altmark z/VM and Linux on System z Consultant IBM System Lab Services and Training ibm.com/systems/services/labservices office: 607.429.3323 mobile; 607.321.7556 alan_altm...@us.ibm.com IBM Endicott
Re: Problems at DR test
On Tuesday, 06/21/2011 at 02:40 EDT, gclo...@br.ibm.com wrote: Is SYSC the unique restriction? Another legacy of the last millennium? Restriction against what? It is the one unifying console interface. It works for all the OSes. If you know how to use it for one OS, you know how to use it for the others, both on the HMC and via #CP VINPUT VMSG. And it operates whether the guest is running in 3270 mode or 3215. Ideally, you shouldn't even have to code it in SYSTEM CONFIG. System_3270 (SYSG) and System_Console (SYSC) should be the consoles of last resort. If you don't specify any operator or emergency consoles, SYSG and SYSC are what you get. If the 3270 session is started, you get that. If not, you get the linemode console. Easy. The only time a 1010 would be given would be if an explicitly specified console at IPL wasn't available for use. And I have to think about whether I believe that SAPL parms or LOADPARM that are re-used on SHUTDOWN REIPL constitute explicitly specified -- I don't think so. IMO, for the purposes of abend restart and SHUTDOWN REIPL, that stored value is simply prepended to the operator and emergency console lists. Just come up on the next available operator console with a message that says PREVIOUS CONSOLE DEVICE 01F IS NO LONGER AVAILABLE. While we're Wishing, I would also wish that CP would accompany all IPL wait states with a message to the integrated console, including SPECIFIED CONSOLE DEVICE 009 IS NOT A 3270. (Natch, the system has to be able to come up far enough to allow CP to connect to SYSC!) The one wait state with no message would be the one for I can't establish a connection with the integrated console - something is seriously wrong. (If SYSC doesn't exist at all, that's a horse of a different color.) An always-on, always-there console changes the nature of traditional CP error reporting. Alan Altmark z/VM and Linux on System z Consultant IBM System Lab Services and Training ibm.com/systems/services/labservices office: 607.429.3323 mobile; 607.321.7556 alan_altm...@us.ibm.com IBM Endicott
Problems at DR test
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.
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 To make it easier: before you IPL, issue CP Q V CONS note the address, often 009 CP TERM CONMODE 3270 CP IPL LOADPARM CONS= ( is the disk your VM resident is on; 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
Re: Problems at DR test
If you're not getting the prompt - you likely have Auto_IPL Warm or Auto_IPL Force configured in your SYSTEM CONFIG... I use Auto_IPL FORCE on my test systems so that they come up without the need for operator response. Scott Rohling On Mon, Jun 20, 2011 at 7:07 AM, Frank M. Ramaekers framaek...@ailife.comwrote: ** ** ** ** ** ** 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.
Re: Problems at DR test
Ideas? Do a TERM CONMODE 3270 before the IPL. Mike MacIsaac mike...@us.ibm.com (845) 433-7061
Re: Problems at DR test
I'm getting 'HCPCLT1013E An invalid operand was supplied for LOADPARM - CONS-0001. 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 To make it easier: before you IPL, issue CP Q V CONS note the address, often 009 CP TERM CONMODE 3270 CP IPL LOADPARM CONS= ( is the disk your VM resident is on; 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.
Re: Problems at DR test
I think it's just LOADPARM ccuu, so if your consoles is at virtual address 0001: CP IPL LOADPARM 0001 Of course, you can avoid this all together by making your virtual machine console address the same as your Operator Console address (as specified in your SYSTEM CONFIG). So let's say you have a 3270 console at address 0320 at your production site, and it is listed in your SYSTEM CONFIG under OPERATOR_CONSOLES, when you IPL your RES pack it will find 0320 and write its messages there without manually specifying the console address on the IPL command. -Mike From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Frank M. Ramaekers Sent: Monday, June 20, 2011 9:41 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Problems at DR test I'm getting 'HCPCLT1013E An invalid operand was supplied for LOADPARM - CONS-0001. 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 To make it easier: before you IPL, issue CP Q V CONS note the address, often 009 CP TERM CONMODE 3270 CP IPL LOADPARM CONS= ( is the disk your VM resident is on; 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.
Re: Problems at DR test
That's because your console address is not 1. From you running system do: Q OPERATOR The oPerator console address is your console address or from your system config operator console statement. And, do give loadparm. Define 9 xxx (the console address) Term mode 3270 IPL Tom 1-646-452-3359 From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Frank M. Ramaekers Sent: Monday, June 20, 2011 9:41 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Problems at DR test I'm getting 'HCPCLT1013E An invalid operand was supplied for LOADPARM - CONS-0001. 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 To make it easier: before you IPL, issue CP Q V CONS note the address, often 009 CP TERM CONMODE 3270 CP IPL LOADPARM CONS= ( is the disk your VM resident is on; 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. Image removed by sender. 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.
Re: Problems at DR test
Ooops, incomplete thought - so regarding changing your virtual machine console, assume your virtual machine console is presently at 009 (the default, issue CP Q V CONS to find out), change it to 0320: CP DEFINE 009 0320 Ask your DR provider to make the change permanently in the CP directory, so you don't have to remember to change it. -MC From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Michael Coffin Sent: Monday, June 20, 2011 9:48 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Problems at DR test I think it's just LOADPARM ccuu, so if your consoles is at virtual address 0001: CP IPL LOADPARM 0001 Of course, you can avoid this all together by making your virtual machine console address the same as your Operator Console address (as specified in your SYSTEM CONFIG). So let's say you have a 3270 console at address 0320 at your production site, and it is listed in your SYSTEM CONFIG under OPERATOR_CONSOLES, when you IPL your RES pack it will find 0320 and write its messages there without manually specifying the console address on the IPL command. -Mike From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Frank M. Ramaekers Sent: Monday, June 20, 2011 9:41 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Problems at DR test I'm getting 'HCPCLT1013E An invalid operand was supplied for LOADPARM - CONS-0001. 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 To make it easier: before you IPL, issue CP Q V CONS note the address, often 009 CP TERM CONMODE 3270 CP IPL LOADPARM CONS= ( is the disk your VM resident is on; 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.
Re: Problems at DR test
Frank, After runs Kris' instructions, to prevent this problem: Check the CONSOLEs defined in SYSTEM CONFIG. At first level VM, define the CONSOLE xxx 3270 card into USER DIRECT for the second level machine, matching one of the address you saw in SYSTEM CONFIG. Remember: all in first level USER DIRECT, looks like physical to second level VM. Including console. Best regards, __ Clovis From: Kris Buelens kris.buel...@gmail.com To: IBMVM@LISTSERV.UARK.EDU Date: 20/06/2011 10:13 Subject: Re: Problems at DR test Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 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 To make it easier: before you IPL, issue CP Q V CONS note the address, often 009 CP TERM CONMODE 3270 CP IPL LOADPARM CONS= ( is the disk your VM resident is on; 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
Re: Problems at DR test
The problem is the - in LOADPARM CONS-0009, sorry, I made a typo. Just enter IPL LOADPARM CONS0009 Changing the CONSOLE statement in the virtual machine definition of your DR second level machine is OK too off course. Summary - *IPL *IPLs, but the defaults of SAPL SYSTEM CONFIG on disk must match what you want - *IPL LOADPARM v* displays the SAPL screen on v, which must be a 3270; if v is the logon screen, it must be in TERM CPNMODE 3270 on the SAPL screen you can enter overrides, like CONS=v - *IPL LOADPARM CONS* starts CP with an override of CONS=v 2011/6/20 Michael Coffin michaelcof...@mccci.com Ooops, incomplete thought – so regarding changing your virtual machine console, assume your virtual machine console is presently at 009 (the default, issue CP Q V CONS to find out), change it to 0320: ** ** CP DEFINE 009 0320 ** ** Ask your DR provider to make the change permanently in the CP directory, so you don’t have to remember to change it. ** ** -MC ** ** *From:* The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] *On Behalf Of *Michael Coffin *Sent:* Monday, June 20, 2011 9:48 AM *To:* IBMVM@LISTSERV.UARK.EDU *Subject:* Re: Problems at DR test ** ** I think it’s just LOADPARM ccuu, so if your consoles is at virtual address 0001: ** ** CP IPL LOADPARM 0001 ** ** Of course, you can avoid this all together by making your virtual machine console address the same as your Operator Console address (as specified in your SYSTEM CONFIG). So let’s say you have a 3270 console at address 0320 at your production site, and it is listed in your SYSTEM CONFIG under OPERATOR_CONSOLES, when you IPL your RES pack it will find 0320 and write its messages there without manually specifying the console address on the IPL command. ** ** -Mike ** ** *From:* The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] *On Behalf Of *Frank M. Ramaekers *Sent:* Monday, June 20, 2011 9:41 AM *To:* IBMVM@LISTSERV.UARK.EDU *Subject:* Re: Problems at DR test ** ** I’m getting ‘HCPCLT1013E An invalid operand was supplied for LOADPARM – CONS-0001. ** ** 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 To make it easier: before you IPL, issue CP Q V CONS note the address, often 009 CP TERM CONMODE 3270 CP IPL LOADPARM CONS= ( is the disk your VM resident is on; 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
Re: Problems at DR test
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=15x CP SET RUN ON Cmd=CP TERM CONMODE 3270nl||, CP IPL 06F8 CLEAR LOADPARM 0009 Queue Cmd Exit VMTEST: /* */ Trace O Address COMMAND nl=15x CP SET RUN ON Cmd=CP TERM CONMODE 3270nl||, 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 To make it easier: before you IPL, issue CP Q V CONS note the address, often 009 CP TERM CONMODE 3270 CP IPL LOADPARM CONS= ( is the disk your VM resident is on; 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
