Re: z/VM & OSA with z/OS guest
On 7/30/10 12:02 PM, "Ray Waters" wrote: > David, > > I believe you have your DEDICATE statements backwards: > > DEDICATE VIRTCUU REALCUU *sigh* It's been that sort of day. You are correct. Please transpose in my examples.
Re: z/VM & OSA with z/OS guest
David, excellent explanation. But the syntax of DEDICATE are inverted: must be "virtual on real" ( I think V=R when define DEDicate, to never forget). So: In the directory for z/OS 2: DEDICATE 7D0 7D3 DEDICATE 7D1 7D4 DEDICATE 7D2 7D5 Regards, Clovis From: David Boyes To: IBMVM@LISTSERV.UARK.EDU Date: 30/07/2010 11:58 Subject: Re: z/VM & OSA with z/OS guest Sent by:The IBM z/VM Operating System If you want to stick to dedicating the adapters, you¹ll need to use different real addresses (eg, 7D0,7D1,7D2, 7D3, 7D4, 7D5, etc), but dedicate them to the same virtual address (eg 7D0, 7D1, 7D2) in the CP directory for the zOS guests. In the directory for z/OS 1: DEDICATE 7D0 7D0 DEDICATE 7D1 7D1 DEDICATE 7D2 7D2 (the easy case). In the directory for z/OS 2: DEDICATE 7D3 7D0 DEDICATE 7D4 7D1 DEDICATE 7D5 7D2 (z/OS 2 still sees addresses 7D0-7D2, but the real hardware uses a different OSA triplet so everyone plays nice). Do the same with z/OS 3. If you¹re willing to experiment and get a MUCH niftier way of doing it (dedicating devices is SO old-skool z/OS... Sniff), use a VSWITCH. Define the VSWITCH with real device 7D0 as the real device in DEFINE VSWITCH. Grant ZOS1, ZOS2, and ZOS3 access to the VSWITCH. Then in the CP directory use NIC statements for 7D0 connected to the VSWITCH. Slick, easy to manage, and MUCH more flexible in how you use the hardware. > At current time, I have each z/OS guest with his own triplet of unique OSA > addresses. Each one will work fine UNTIL they are all up and running, at which > time, we start seeing ³console hangs² and what appears to be machine lockups. > Some times they will eventually clear themselves, sometimes not. And it > rotates as to which z/OS guest system hangs. This sounds more like resource exhaustion than a network-related issue. Look at the recommendations for system resource management sessions that are in the Linux guides and in the "running guest OS" manual. A lot of the problems are similar (but zOS is even more ill-behaved in some ways).
Re: z/VM & OSA with z/OS guest
David, I believe you have your DEDICATE statements backwards: DEDICATE VIRTCUU REALCUU Ray -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of David Boyes Sent: Friday, July 30, 2010 10:05 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: z/VM & OSA with z/OS guest If you want to stick to dedicating the adapters, you¹ll need to use different real addresses (eg, 7D0,7D1,7D2, 7D3, 7D4, 7D5, etc), but dedicate them to the same virtual address (eg 7D0, 7D1, 7D2) in the CP directory for the zOS guests. In the directory for z/OS 1: DEDICATE 7D0 7D0 DEDICATE 7D1 7D1 DEDICATE 7D2 7D2 (the easy case). In the directory for z/OS 2: DEDICATE 7D3 7D0 DEDICATE 7D4 7D1 DEDICATE 7D5 7D2 (z/OS 2 still sees addresses 7D0-7D2, but the real hardware uses a different OSA triplet so everyone plays nice). Do the same with z/OS 3. If you¹re willing to experiment and get a MUCH niftier way of doing it (dedicating devices is SO old-skool z/OS... Sniff), use a VSWITCH. Define the VSWITCH with real device 7D0 as the real device in DEFINE VSWITCH. Grant ZOS1, ZOS2, and ZOS3 access to the VSWITCH. Then in the CP directory use NIC statements for 7D0 connected to the VSWITCH. Slick, easy to manage, and MUCH more flexible in how you use the hardware. > At current time, I have each z/OS guest with his own triplet of unique OSA > addresses. Each one will work fine UNTIL they are all up and running, at which > time, we start seeing ³console hangs² and what appears to be machine lockups. > Some times they will eventually clear themselves, sometimes not. And it > rotates as to which z/OS guest system hangs. This sounds more like resource exhaustion than a network-related issue. Look at the recommendations for system resource management sessions that are in the Linux guides and in the "running guest OS" manual. A lot of the problems are similar (but zOS is even more ill-behaved in some ways). NOTICE: This e-mail is intended solely for the use of the individual to whom it is addressed and may contain information that is privileged, confidential or otherwise exempt from disclosure. If the reader of this e-mail is not the intended recipient or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify us by replying to the original message at the listed email address. Thank You.
Re: z/VM & OSA with z/OS guest
If you want to stick to dedicating the adapters, you¹ll need to use different real addresses (eg, 7D0,7D1,7D2, 7D3, 7D4, 7D5, etc), but dedicate them to the same virtual address (eg 7D0, 7D1, 7D2) in the CP directory for the zOS guests. In the directory for z/OS 1: DEDICATE 7D0 7D0 DEDICATE 7D1 7D1 DEDICATE 7D2 7D2 (the easy case). In the directory for z/OS 2: DEDICATE 7D3 7D0 DEDICATE 7D4 7D1 DEDICATE 7D5 7D2 (z/OS 2 still sees addresses 7D0-7D2, but the real hardware uses a different OSA triplet so everyone plays nice). Do the same with z/OS 3. If you¹re willing to experiment and get a MUCH niftier way of doing it (dedicating devices is SO old-skool z/OS... Sniff), use a VSWITCH. Define the VSWITCH with real device 7D0 as the real device in DEFINE VSWITCH. Grant ZOS1, ZOS2, and ZOS3 access to the VSWITCH. Then in the CP directory use NIC statements for 7D0 connected to the VSWITCH. Slick, easy to manage, and MUCH more flexible in how you use the hardware. > At current time, I have each z/OS guest with his own triplet of unique OSA > addresses. Each one will work fine UNTIL they are all up and running, at which > time, we start seeing ³console hangs² and what appears to be machine lockups. > Some times they will eventually clear themselves, sometimes not. And it > rotates as to which z/OS guest system hangs. This sounds more like resource exhaustion than a network-related issue. Look at the recommendations for system resource management sessions that are in the Linux guides and in the "running guest OS" manual. A lot of the problems are similar (but zOS is even more ill-behaved in some ways).
Re: z/VM & OSA with z/OS guest
Look into setting up a single VSWITCH that is owned by DTCVSW1 and DTCVSW2 and connect each of the z/OS systems to the switch using the NICDEF statement in the user directory Larry Davis From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Charles Grady Sent: Friday, July 30, 2010 10:31 AM To: IBMVM@LISTSERV.UARK.EDU Subject: z/VM & OSA with z/OS guest Hello Fellow Listers; In need of some help with z/VM and TCPIP for z/OS guest. Here's the backgroung: 1) When running 5 z/OS LPARs the z/OS systems use the same OSA address, such as 7D0 but have different IP addresses in their IP Parms. This works and has worked well for a long period of time here. 2) We now need to have three z/OS guest machines up and running under z/VM with full IP capability. My communication wiz guy has been in touch with IBM and has been told that you have to set the OSA up that way under z/VM too. How can I dedicate 7E0-7E2 to three guest at one time? It sounds like a communications disconnect to me, but what do I know. At current time, I have each z/OS guest with his own triplet of unique OSA addresses. Each one will work fine UNTIL they are all up and running, at which time, we start seeing "console hangs" and what appears to be machine lockups. Some times they will eventually clear themselves, sometimes not. And it rotates as to which z/OS guest system hangs. Thanks in advance. ** GDOL CONFIDENTIALITY NOTICE: This transmission may contain confidential information protected by state or federal law. The information is intended only for use consistent with the state business discussed in this transmission.If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action based on the contents is strictly prohibited. If you have received this transmission in error, please delete this email and notify the sender immediately.Your cooperation is appreciated. **
Re: z/VM & OSA with z/OS guest
>How can I dedicate 7E0-7E2 to three guest at one time? You can't. You would need a triplet for each z/OS guest. You can attach/dedicate each triple as v addresses 7E0-7E2. OR use a VSWITCH using 7E0-7E2 - then define a virtual NIC to each z/OS as 7E0-7E2 connected to the vswitch. On Fri, Jul 30, 2010 at 10:30 AM, Charles Grady < charles.gr...@dol.state.ga.us> wrote: > Hello Fellow Listers; > > In need of some help with z/VM and TCPIP for z/OS guest. > > Here’s the backgroung: > > 1) When running 5 z/OS LPARs the z/OS systems use the same OSA > address, such as 7D0 but have different IP addresses in their IP Parms. This > works and has worked well for a long period of time here. > > 2) We now need to have three z/OS guest machines up and running under > z/VM with full IP capability. > > My communication wiz guy has been in touch with IBM and has been told that > you have to set the OSA up that way under z/VM too. > > How can I dedicate 7E0-7E2 to three guest at one time? > > It sounds like a communications disconnect to me, but what do I know. > > At current time, I have each z/OS guest with his own triplet of unique OSA > addresses. Each one will work fine UNTIL they are all up and running, at > which time, we start seeing “console hangs” and what appears to be machine > lockups. Some times they will eventually clear themselves, sometimes not. > And it rotates as to which z/OS guest system hangs. > > Thanks in advance. > > > > > ** > > GDOL CONFIDENTIALITY NOTICE: This transmission may contain confidential > information protected by state > > or federal law. The information is intended only for use consistent with the > state business discussed in this > > transmission.If you are not the intended recipient, you are hereby notified > that any disclosure, copying, > > distribution, or the taking of any action based on the contents is strictly > prohibited. If you have received this > > transmission in error, please delete this email and notify the sender > immediately.Your cooperation is > appreciated. > > ** > -- Mark D Pace Senior Systems Engineer Mainline Information Systems
