Thanks Alan. I will do some research to see what exactly is defined.  

Thank You,

Terry Martin
Lockheed Martin - Citic
z/OS and z/VM Performance Tuning and Operating Systems Support
Office - 443 348-2102
Cell - 443 632-4191

-----Original Message-----
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Alan Altmark
Sent: Monday, April 05, 2010 11:52 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: HiperSocket UCBs

On Monday, 04/05/2010 at 10:42 EDT, "Martin, Terry R. (CMS/CTR) (CTR)" 
<terry.mar...@cms.hhs.gov> wrote:
> Each guest that needs to talk to z/OS needs a Triplet UCB definition
on
> a HiperSocket CHPID defined to it. The more guest I have that require
> this the more UCBs I need to use, eventually I hit the max UCBs
allowed
> on a CHPID. For the best performance a HiperSocket interface is
defined
> on the z/Linux guest without going through the VLAN.  This interface
> connects to the HiperSocket network defined on the z/OS system and
data
> is passed at memory speeds.

Terry, I'm still having trouble believing that you have 4096 NICs
(12,228 
UAs/subchannels/UCBs) defined for your HiperSockets chpids.  Can you 
confirm?

> To get around this I could create another LPAR since the same spanned
> HiperSockets UCB can be used on different LPARS just not on the same
> LPAR.

If you *have* maxed out HiperSockets, new LPARs aren't going to help.
You 
can't have more than 12K HiperSocket subchannels on the box.

I suspect your problem is that you're wasting subchannels across all 
LPARs.

(1) Make sure you are coding PARTITION= on the CHPID to limit subchannel

definition to only the LPARs that are permitted to use the chpid.
(2) Create as many CNTLUNITs for your HiperSocket chpids as you need. 
Remember that all the devices on a single CU must be shared or unshared.

z/OS will need access to one CNTLUNIT per HiperSocket chpid it needs 
access to.  The other 48 control units will be given to z/VM.
(3) On the CUs for z/OS, use PARTITION= on the IODEVICE to limit the 
definition to z/OS.
(4) For the remaining HiperSocket CUs, use PARTITION=
(5) Define only 3 IODEVICEs for each z/OS CNTLUNIT

Do the UNITADD math.

> I am still on a z9 but our new z10 was just delivered and I understand
> that the z10 allows for more HiperSocket UCBs so maybe this will be a
> non issue with the z10. I am still trying to nail this down.

z9 and z10 are the same, both having 16 HiperSocket chpids.  When in 
doubt, check the Machine Limits appendix in the IOCP book.

Alan Altmark
z/VM Development
IBM Endicott

Reply via email to