One thing that I noticed immediately is that your CNTLUNIT macro had
CUADDR=0 on both of them. This is wrong. Here is our defination:

         CHPID PATH=(32),SHARED,                                       *
               PARTITION=((LP1,MAIN,RDC1,SMC1,TECH,ZVM),(LP1,MAIN,RDC1,*
               SMC1,TECH,ZVM)),TYPE=CTC
         CHPID PATH=(3F),SHARED,                                       *
               PARTITION=((LP1,MAIN,RDC1,SMC1,TECH,ZVM),(LP1,MAIN,RDC1,*
               SMC1,TECH,ZVM)),TYPE=CNC
*
* IN THE FOLLOWING CNTLUNIT MACROS, THE CUADDR=N IS THE LPAR NUMBER
* 1 = MAIN
* 2 = LP1
* 3 = SMC1
* 4 = RDC1
* 5 = TECH
         CNTLUNIT CUNUMBR=3201,PATH=(32),UNITADD=((40,064)),CUADD=1,   *
               UNIT=SCTC
         CNTLUNIT CUNUMBR=3202,PATH=(32),UNITADD=((40,064)),CUADD=2,   *
               UNIT=SCTC
         CNTLUNIT CUNUMBR=3203,PATH=(32),UNITADD=((40,064)),CUADD=3,   *
               UNIT=SCTC
         CNTLUNIT CUNUMBR=3204,PATH=(32),UNITADD=((40,064)),CUADD=4,   *
               UNIT=SCTC
         CNTLUNIT CUNUMBR=3205,PATH=(32),UNITADD=((40,064)),CUADD=5,   *
               UNIT=SCTC
         CNTLUNIT CUNUMBR=3F01,PATH=(3F),UNITADD=((40,064)),CUADD=1,   *
               UNIT=SCTC
         CNTLUNIT CUNUMBR=3F02,PATH=(3F),UNITADD=((40,064)),CUADD=2,   *
               UNIT=SCTC
         CNTLUNIT CUNUMBR=3F03,PATH=(3F),UNITADD=((40,064)),CUADD=3,   *
               UNIT=SCTC
         CNTLUNIT CUNUMBR=3F04,PATH=(3F),UNITADD=((40,064)),CUADD=4,   *
               UNIT=SCTC
         CNTLUNIT CUNUMBR=3F05,PATH=(3F),UNITADD=((40,064)),CUADD=5,   *
               UNIT=SCTC
*
* NOTE THAT THERE ARE TWO IODEVICE MACROS FOR EVERY ADDRESS. ONE IS
* FOR ONE SIDE, THE OTHER IS FOR THE OTHER SIDE. PLEASE NOTE THAT
* THE PARTITION= ASSIGNED TO THE IODEVICE MUST BE THE OPPOSITE SIDE
* FROM THE PARTITION ASSIGNED VIA THE CUADDR= ON THE CNTLUNIT
* MACRO.
         IODEVICE ADDRESS=(F40,008),CUNUMBR=(3202),STADET=Y,           *
               PARTITION=(MAIN),UNIT=BCTC
         IODEVICE ADDRESS=(F40,008),CUNUMBR=(3F01),STADET=Y,           *
               PARTITION=(LP1),UNIT=BCTC
         IODEVICE ADDRESS=(F48,008),CUNUMBR=(3205),STADET=Y,           *
               PARTITION=(MAIN),UNIT=BCTC
         IODEVICE ADDRESS=(F48,008),CUNUMBR=(3F01),STADET=Y,           *
               PARTITION=(TECH),UNIT=BCTC
         IODEVICE ADDRESS=(F50,008),CUNUMBR=(3203),STADET=Y,           *
               PARTITION=(MAIN),UNIT=BCTC
         IODEVICE ADDRESS=(F50,008),CUNUMBR=(3F01),STADET=Y,           *
               PARTITION=(SMC1),UNIT=BCTC
         IODEVICE ADDRESS=(F60,008),CUNUMBR=(3204),STADET=Y,           *
               PARTITION=(MAIN),UNIT=BCTC
         IODEVICE ADDRESS=(F60,008),CUNUMBR=(3F01),STADET=Y,           *
               PARTITION=(RDC1),UNIT=BCTC
         IODEVICE ADDRESS=(F68,008),CUNUMBR=(3202),STADET=Y,           *
               PARTITION=(SMC1),UNIT=BCTC
         IODEVICE ADDRESS=(F68,008),CUNUMBR=(3F03),STADET=Y,           *
               PARTITION=(LP1),UNIT=BCTC
         IODEVICE ADDRESS=(F70,008),CUNUMBR=(3203),STADET=Y,           *
               PARTITION=(RDC1),UNIT=BCTC
         IODEVICE ADDRESS=(F70,008),CUNUMBR=(3F04),STADET=Y,           *
               PARTITION=(SMC1),UNIT=BCTC

--
John McKown
Senior Technical Specialist
UICI Insurance Center
Applications & Solutions Team
+1.817.255.3225


> -----Original Message-----
> From: Eric Bielefeld [mailto:[EMAIL PROTECTED]
> Sent: Monday, March 17, 2003 2:54 PM
> To: [EMAIL PROTECTED]
> Subject: IOCDS For an Escon CTC Connection
>
>
> Saturday, I was in to install my new IOCDS for Linux with a
> CTC definition so I can communicate with my Linux Lpar from
> my production TCPIP.  The devices on one side of the
> connection, the one defined as a CNC Chpid, do not come up
> online.  Here are my IOCDS definitions:
>
> CHPID PATH=(04),SHARED,
>       PARTITION=((LINUX1,PROD,TEST),(LINUX1,PROD,TEST)),
>       TYPE=CNC
> CHPID PATH=(05),SHARED,
>       PARTITION=((LINUX1,PROD,TEST),(LINUX1,PROD,TEST)),
>       TYPE=CTC
> CHPID PATH=(06),SHARED,PARTITION=((PROD,TEST),(PROD,TEST)),
>       TYPE=CNC
> CNTLUNIT CUNUMBR=0D00,PATH=(04),UNITADD=((00,008)),CUADD=0,
>       UNIT=SCTC
> CNTLUNIT CUNUMBR=0E00,PATH=(05),UNITADD=((00,008)),CUADD=0,
>       UNIT=SCTC
> IODEVICE ADDRESS=(D00,008),CUNUMBR=(0D00),STADET=Y,UNIT=SCTC
> IODEVICE ADDRESS=(E00,008),CUNUMBR=(0E00),STADET=Y,
>       PARTITION=(LINUX1,PROD,TEST),UNIT=SCTC
>
> The 8 IODEVICEs starting at E00 come up online, or I should
> say can be varied online.  The devices at D00 will not come
> up online.  If I issue  V E00,ONLINE   I get the following:
>
> RESPONSE=PROD
>  IEE103I UNIT 0D00     NOT BROUGHT ONLINE
>  IEE763I NAME= IECVIOPM CODE= 0000000400000000
>  IOS551I NO PATHS PHYSICALLY AVAILABLE
>  IEE764I END OF IEE103I    RELATED MESSAGES
>
> Why won't the E00 devices come up online.  Before I installed
> the new IOCDS, I went into the back of our MP3000-H50 and
> plugged an Escon cable between Chpids  04 and 05.  Hopefully
> someone knows if my coding is correct, or why the devices
> defined don't come up online.  Maybe this is normal.  I don't
> have my Linux1 Lpar running.  We don't have VM.
>
> I did notice that the E00 devices have the PARTITION keyword,
> and the D00 devices don't.  I didn't notice that before today
> when I looked at the IOCP deck I generated on Friday.  I
> don't think that should have anything to do with it, because
> both Chpid 04 and 05 have the PARTITION keyword for all Lpars.
>
>
>
> Eric Bielefeld
> Sr. MVS Systems Programmer
> P&H Mining Equipment
> Milwaukee, WI
> 414-671-7849
> [EMAIL PROTECTED]
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> +++++++++++++++++++++++++++
> This electronic mail transmission contains information from P
> & H Mining Equipment
> which is confidential, and is intended only for the use of
> the proper addressee.
> If you are not the intended recipient, please notify us
> immediately at the return
> address on this transmission, or by telephone at (414)
> 671-4400, and delete this
> message and any attachments from your system.  Unauthorized
> use, copying,
> disclosing, distributing, or taking any action in reliance on
> the contents of this
> transmission is strictly prohibited and may be unlawful.
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> +++++++++++++++++++++++++++
>

Reply via email to