Shimon
Thanks for the assistance. After pulling a little more hair out
I finally got the LPAR CTC links to
work. In the process I ran into a few things I still don't
quite understand.
When I got the CTC's properly defined, I ran into a situation
where I could get both sides to bring the links ready and
set up the gateways between them but could not Ping across the
LINK. After trying about every order of bringing up the links
I restarted both stacks and took the START statements for the
DEVICEs out of the PROFILE TCPIP files on both systems. I was
then able to run an OBEYFILE on both sides to START the
DEVICEs and things worked fine.
I've never run into a case where order of starting the LINKs
gave problems. BTW, the first TCp/IP was at Z/VM 4.4 level and
the second was as Z/VM 5.2 level. (It took me a while to notice
the syntax in the 5.2 Gateway statement had changed.)
Is there a command to stop a DEVICE so you can reissue a START again
without restarting TCP/IP? Z/OS TCP/IP has a VARY command for this
sort of thing.
---------------------
Also , on the redundant paths mentioned below.
>
>Ok, all CUs and DEVs defined on channel 02 and channel 03 will be
>accessable from all three LPARs. So we will have something that 'looks like'
>two separate systems, each with 3 LPARs, talking to each other:
>
> SYS-A SYS-B
>|--------| |--------|
>| ESA11 | | ESA11 |
>|--------| |--------|
>| ESA12 | | ESA12 |
>|--------| |--------|
>| IFL | | IFL |
>+--------+ +--------+
> | | 03| |
> | +-----------------+ |
> |02 |
> +---------------------------+
>
>Use monospace font for the diagram, or paste into monospace editor.
>
>I am calling the 02 side SYS-A, and the 03 side SYS-B.
>
>You are trying to connect LPAR 1 to LPAR 3, but as
>we see in the diagram, there are two ways to do this:
>LPAR1(SYS-A) <----> LPAR3(SYS-B) and
>LPAR1(SYS-B) <----> LPAR3(SYS-A)
>
>(This really means you didn't follow the howto,
>which would have removed redundant connections,
>but never mind.. its your HMC storage) ;-)
>
Would this IOCP entry remove the redundant paths or have I
misread your examples again?
CHPID PATH=02,TYPE=CNC,PARTITION=(ESA11,ESA12,IFL),SHARED
CHPID PATH=03,TYPE=CTC,PARTITION=(ESA11,ESA12,IFL),SHARED
CNTLUNIT CUNUMBR=0401,PATH=(02),UNIT=SCTC,UNITADD=((00,32)),CUADD=1
CNTLUNIT CUNUMBR=0501,PATH=(03),UNIT=SCTC,UNITADD=((00,32)),CUADD=1
CNTLUNIT CUNUMBR=0402,PATH=(02),UNIT=SCTC,UNITADD=((00,32)),CUADD=2
CNTLUNIT CUNUMBR=0502,PATH=(03),UNIT=SCTC,UNITADD=((00,32)),CUADD=2
CNTLUNIT CUNUMBR=0403,PATH=(02),UNIT=SCTC,UNITADD=((00,32)),CUADD=3
CNTLUNIT CUNUMBR=0503,PATH=(03),UNIT=SCTC,UNITADD=((00,32)),CUADD=3
IODEVICE ADDRESS=(0400,32),CUNUMBR=(0401),UNITADD=00, X
UNIT=SCTC,PART=(ESA11)
IODEVICE ADDRESS=(0420,32),CUNUMBR=(0402),UNITADD=00, X
UNIT=SCTC,PART=(ESA11,ESA12)
IODEVICE ADDRESS=(0440,32),CUNUMBR=(0403),UNITADD=00, X
UNIT=SCTC,PART=(ESA11,ESA12,IFL)
IODEVICE ADDRESS=(0500,32),CUNUMBR=(0501),UNITADD=00, X
UNIT=SCTC,PART=(ESA11,ESA12,IFL)
IODEVICE ADDRESS=(0520,32),CUNUMBR=(0502),UNITADD=00, X
UNIT=SCTC,PART=(ESA12,IFL)
IODEVICE ADDRESS=(0540,32),CUNUMBR=(0503),UNITADD=00, X
UNIT=SCTC,PART=(IFL)
>
Again, thanks for the help in getting this thing connected.
Its been a while since we've run LPARs. The IFL and some isolation
issues on Z/OS forced us back to LPAR's again.
Ron Greve
SDSU Admin and Research Computing
>--
>************************************************************************
>Shimon Lebowitz mailto:[EMAIL PROTECTED]
>VM System Programmer mailto:[EMAIL PROTECTED]
>Israel Police National HQ. http://www.poboxes.com/shimonpgp
>Jerusalem, Israel phone: +972 2 530-9877 fax: 530-9308
>************************************************************************
