Thanks, I will activate a new Iocds 6.December since this is not a dynamically
issue as long is z/VSE Native is involved.

I guess you would prefer to see this in the genned Iocds?

                                     CONTROL        PATH                        
 DEVICE      UNIT     DEVICE          UNIT    CHPID.LINK.CUADD              MIF 
 NUMBERS     ADDRS  TYPE-MODEL  CSS  NUMBER      !__.__.__!    SWITCH  !1!2!3!4!
_________    _____  __________  ___  _______                   ______  _________
--------------------------------------------------------------------------------
 100-11F     00-1F  SCTC         0                                     !*!*!*!*!
                                      3000        60.**.3       NONE   !A!C!A!C!
--------------------------------------------------------------------------------
 400-41F     00-1F  SCTC         0                                     !*!*!*!*!
                                      3010        61.**.1       NONE   !A!C!A!C!
--------------------------------------------------------------------------------

Previous it looked like this, as without CUADD:
--------------------------------------------------------------------------------
 100-11F     00-1F  SCTC         0                                     !*!*!*!*!
                                      3000        60            NONE   !A!C!A!C!
--------------------------------------------------------------------------------
 400-41F     00-1F  SCTC         0                                     !*!*!*!*!
                                      3010        61            NONE   !A!C!A!C!
--------------------------------------------------------------------------------


Regards Geir Fladby
AutoData Norge AS
tlf 23 17 20 34

-----Opprinnelig melding-----
Fra: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] På vegne av 
Rob van der Heij
Sendt: 27. november 2009 11:52
Til: IBMVM@LISTSERV.UARK.EDU
Emne: Re: Channel to Channel and IBM Communication Server on z/VM Linux

On Fri, Nov 27, 2009 at 11:37 AM, Geir Fladby <g...@autodata.no> wrote:

> RESOURCE PART=((CSS(0),(AUTO1,1),(AUTO2,2),(ZVMLNX,3),(ZVMLNX2,4)))
> CHPID PCHID=160,PATH=(CSS(0),60),TYPE=CNC,PART=(AUTO1,ZVMLNX),SHARED
> CHPID PCHID=161,PATH=(CSS(0),61),TYPE=CTC,PART=(AUTO1,ZVMLNX),SHARED
> **********************************************************
> * CHANNEL    PCHID 160 og 161   Channel to Channel       *
> *                            between z/VSE PROD og z/VM  *
> **********************************************************
>  CNTLUNIT CUNUMBR=3000,PATH=(60),UNITADD=((00,32)),UNIT=SCTC
>  IODEVICE ADDRESS=(100,32),CUNUMBR=(3000),UNIT=SCTC
>  CNTLUNIT CUNUMBR=3010,PATH=(61),UNITADD=((00,32)),UNIT=SCTC
>  IODEVICE ADDRESS=(400,32),CUNUMBR=(3010),UNIT=SCTC
>
> It's genned without errors and what I can see from the HMC console is that
> Both channels 60 and 61 is online.

Hej, Geir.

I believe you need to add the CUADD=n parameter to the CNTLUNIT macro.
The "n" would be the EMIF partition number of the target LPAR you
connect to, so light shines in the right direction. Like this:

CNTLUNIT CUNUMBR=3000,PATH=(60),UNITADD=((00,32)),UNIT=SCTC,CUADD=3
IODEVICE ADDRESS=(100,32),CUNUMBR=(3000),UNIT=SCTC
CNTLUNIT CUNUMBR=3010,PATH=(61),UNITADD=((00,32)),UNIT=SCTC,CUADD=1
IODEVICE ADDRESS=(400,32),CUNUMBR=(3010),UNIT=SCTC

Now you should find 100-11F in LPAR AUTO1 connect to 400-41F in ZVMLNX.

My preference would be to use PART= on the IODEVICE macro as well to
keep the devices out of the LPARs where they don't make sense. But
also when coding an IOCP, beauty is in the eye of the beholder.

Hilsen, Rob

Reply via email to