So now I'm trying to define a shared CTC environment so that I can connect a
real CTC to a 2nd level vm.
It was working when I dedicated the CHPID to each partition.  Now that I am
sharing the CHPIDs between LPARS the the 2400 range will not come online to
either LPAR.   Messages and relevant pieces of IOCDS is below.

q chpid 24

Path 24 offline to devices 2400 2401 2402 2403 2404 2405 2406 2407

Path 24 offline to devices 2408 2409 240A 240B 240C 240D 240E 240F

Path 24 offline to devices 2410 2411 2412 2413 2414 2415 2416 2417

Path 24 offline to devices 2418 2419 241A 241B 241C 241D 241E 241F

Ready; T=0.01/0.01 11:13:41

q path 2400

Device 2400, Status OFFLINE

 CHPIDs to Device 2400 (PIM)  : 24

  Physically Available (PAM)  : +

  Online               (LPM)  : -

                       Legend     + Yes - No

Ready; T=0.01/0.01 11:13:44

vary on 2400

HCPCPN6283I Device 2400 cannot be varied online because no channel path is
available.
HCPCPN6785E Unable to identify device 2400 dynamically.

1 device(s) specified; 0 device(s) successfully varied online

Ready(06785); T=0.01/0.01 11:14:00



CHPID PATH=(CSS(0),14),SHARED,PARTITION=((BP,IT),(=)),        *
      PCHID=271,TYPE=CTC
CHPID PATH=(CSS(0),24),SHARED,PARTITION=((BP,IT),(=)),        *
      PCHID=272,TYPE=CNC
CNTLUNIT CUNUMBR=1400,PATH=((CSS(0),14)),UNITADD=((00,032)),  *
      UNIT=SCTC
IODEVICE ADDRESS=(1400,032),CUNUMBR=(1400),STADET=Y,UNIT=SCTC
CNTLUNIT CUNUMBR=2400,PATH=((CSS(0),24)),UNITADD=((00,032)),  *
      UNIT=SCTC
IODEVICE ADDRESS=(2400,032),CUNUMBR=(2400),STADET=Y,UNIT=SCTC


On Tue, Oct 5, 2010 at 1:25 PM, O'Brien, Dennis L <
dennis.l.o'br...@bankofamerica.com <dennis.l.o%27br...@bankofamerica.com>>wrote:

>  Mark,
>
> You need a real CTC with both ends connected to the same system.  You
> ACTIVATE ISLINK for one end on the first-level system.  You ATTACH or
> DEDICATE the other end on first level to the virtual machine for the
> second-level system.  You then ACTIVATE ISLINK for that device on the
> second-level system.
>
>
>
>
>                       Dennis
>
>
>
> "Decision" is not a verb.
>
>
>
> *From:* The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] *On
> Behalf Of *Mark Pace
> *Sent:* Tuesday, October 05, 2010 09:57
>
> *To:* IBMVM@LISTSERV.UARK.EDU
> *Subject:* Re: [IBMVM] z/VM ISFC links
>
>
>
> Hi, Clovis -
>
> Thanks, but I knew how to do that.  I've used VCTC between guests for
> years.  What I needed, but apparently is not supported is a VCTC, connecting
> CP to a virtual machine for ISFC links.
>
> On Tue, Oct 5, 2010 at 12:40 PM, <gclo...@br.ibm.com> wrote:
>
> > Now I'm trying to figure out how to define a virtual CTC between CP and
> the 2nd level VM.
>
> Mark, it is easy.
>
> On first level, define one Virtual CTC (FCTC, SCTC) into TCPIP (or another
> capable machine) to connect to second level VM.
>
> On second level VM, *define* and *couple* the Virtual CTC to first level
> TCPIP *before* his IPL (COMMAND into Directory is a good place to set it).
> After the IPL, DEDICATE the CTC (the second level thinks it is a REAL CTC)
> to his TCPIP machine.
> Done, you have the two TCPIPs connected by CTCs...
>
> Work fine also for VTAM machines, RSCS, PVM, zOS and so long...
>
> ______________________________________________
> Clovis Pereira
>
>
> *Error! Filename not specified.*Mark Pace ---04/10/2010 10:06:05---Real
> CTC link are working between LPARs. I have a 2nd level VM that I dedicated a
> CTC address to tha
>
>   *Error! Filename not specified.*
> From:
>
> *Error! Filename not specified.*
>
> Mark Pace <pacemainl...@gmail.com>
>
>   *Error! Filename not specified.*
> To:
>
> *Error! Filename not specified.*
> IBMVM@LISTSERV.UARK.EDU
>
> *Error! Filename not specified.*
> Date:
>
> *Error! Filename not specified.*
>
> 04/10/2010 10:06
>
>   *Error! Filename not specified.*
> Subject:
>
> *Error! Filename not specified.*
>
> Re: z/VM ISFC links
>
>   *Error! Filename not specified.*
> Sent by:
>
> *Error! Filename not specified.*
>
> The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU>
>
>   ------------------------------
>
>
>
>
> Real CTC link are working between LPARs.
> I have a 2nd level VM that I dedicated a CTC address to that is also
> talking to the other LPAR.
>
> Now I'm trying to figure out how to define a virtual CTC between CP and the
> 2nd level VM.
> CP DEFINE CTC is for a virtual machine.
> VMA = LPAR
> VMB = 2nd level VMA guest
> VMC = LPAR
>
>
> VMA -------- VMC
>        ctc    |
>  ?            |
> VMB ----------+
>         ctc
>
> On Fri, Oct 1, 2010 at 10:14 AM, Mark Wheeler <mwheele...@hotmail.com>
> wrote:
>
> In the Better Late (for John) Than Never department, the Redbook "FICON CTC
> Implementation" was published in 2001. Find it at
> http://www.redbooks.ibm.com/redpapers/pdfs/redp0158.pdf
>
>
> Mark Wheeler
> UnitedHealth Group
>
> --
>
> "Excellence. Always. If Not Excellence, What? If Not Excellence Now,
> When?"
> Tom Peters, author of "The Little BIG Things"
>
>
>
>
>
> > Date: Thu, 30 Sep 2010 19:25:24 +0200
> > From: jphartm...@gmail.com
>
> > Subject: Re: z/VM ISFC links
> > To: IBMVM@LISTSERV.UARK.EDU
> >
> > When I set up something similar in a 6-lpar VM system almost 10 years
> > ago, it took me quite some time to get the CTC defined correctly in
> > the IOCP so that I had n-to-n connectivity. Of course this was in the
> > days of stand-alone IOCP. I hope you have better tools.
> >
> > j.
> >
> > On 30 September 2010 19:00, Mark Pace <pacemainl...@gmail.com> wrote:
> > > I see that now.
> > > 1st criteria for this test is to share SFS across LPARs.
> > > 2nd was to start learning about what will be involved with SSI.
> > > So I guess I'm sticking to ISFC.
> > > Glad I have extra ESCON and FICON CHPIDs.  Guess I'll start with ESCON
> as I
> > > also have extra cables, no extra FICON cables.
> > >
> > > On Thu, Sep 30, 2010 at 12:49 PM, Rob van der Heij <rvdh...@gmail.com>
> > > wrote:
> > >>
> > >> On Thu, Sep 30, 2010 at 6:21 PM, Mark Pace <pacemainl...@gmail.com>
> wrote:
> > >>
> > >> > I think I'll also look into IPGATE.
> > >>
> > >> But that does not do ISFC ...
> > >
> > >
> > >
> > > --
> > > Mark D Pace
> > > Senior Systems Engineer
> > > Mainline Information Systems
> > >
> > >
> > >
> > >
>
>
>
>
> --
> Mark D Pace
> Senior Systems Engineer
> Mainline Information Systems
>
>
>
>
>
>
>
> --
>
> Mark D Pace
>
> Senior Systems Engineer
>
> Mainline Information Systems
>
>
>
>
>
>
>
>
>



-- 
Mark D Pace
Senior Systems Engineer
Mainline Information Systems

Reply via email to