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
RACF Audit for VM
We are in the process of going live with our z/VM environment next month. Does anyone have a checklist for a RACF audit? Regards, Scott Shumate Software Systems Prog Spec Branch Bank Trust Assistant Vice President Mainframe Support Mail Code: 100-99-09-10 Work: (252) 246-2306 Cell:(252) 373-9605 -- .~. /\/\ /( )\ ^^-^^ Linux on Systems Z -
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: Backup and Restore Manager V1.2 startup problem
*** Received device 0181, a 3590-11 which is empty or not ready. write-enabled, and positioned at load point. *** Return code 32 attempting to obtain VOL1 label. *** TAPE DVOL1 replied: DMSP2C431E TAP1(181) VOL1 label missing You gave it a unlabeled tape. BRM expects IBM SL tapes. You need to label the tape with TAPE WVOL1 before you can use it with BRM.
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
