If you need to talk to the actual 1st level CP, then the only means I know
of is through an actual physical CTC connection. Talking between two
machines is what the physical CTC is all about; without it, what means would
you actually use to reach the other system? Mainframes don't support
Bluetooth.
For the first to second level CTC, looping a CTC connection back into
another port works; then you can give one side of the connection to the 2nd
level system, and the other side to the 1st level system.
Virtual anything isn't a solution to all problems. When you start talking
about multiple boxes, or about connections directly into CP, without a
service guest, start thinking about real connections. The virtual ones
aren't there.
--
.~. Robert P. Nix Mayo Foundation
/V\ RO-OE-5-55 200 First Street SW
/( )\ 507-284-0844 Rochester, MN 55905
^^-^^ -----
"In theory, theory and practice are the same, but
in practice, theory and practice are different."
On 10/10/07 8:54 AM, "Wakser, David" <[EMAIL PROTECTED]> wrote:
> Jim:
>
> I think you misunderstood my question: the zVM "system" must
> "own" one side of the CTC - otherwise an ACTIVATE ISLINK cannot succeed.
> There is no SVM involved. Defining the side belonging to the guest
> machine is the piece that I know; defining the side for the "system" is
> the part I cannot figure out.
>
> As a further complication, we also need to use a virtual CTC
> between two VMs running on different processors - is that doable?
>
> David Wakser
>
> -----Original Message-----
> From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
> Behalf Of Stracka, James (GTI)
> Sent: Wednesday, October 10, 2007 9:48 AM
> To: [email protected]
> Subject: Re: Defining virtual CTCAs
>
> In the directory for your 2nd level guest you would have:
> SPECIAL 0D90 FCTC 1stlevelSVM
>
> For your other 1st level SVM:
> SPECIAL 0F11 FCTC 2ndlevelguestid
>
> The on both issue a COUPLE command because you may not know which is
> second:
> CP COUPLE 0D90 1stlevelSVM 0F11
> And
> CP COUPLE 0F11 2ndlevelguestid 0D90
>
> The on the 2nd level system ATTACH the CTC to the SVM needing it.
>
> You need not do FCTC, look at the DEFINE command for the type of CTC you
> desire.
>
> -----Original Message-----
> From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
> Behalf Of Wakser, David
> Sent: Wednesday, October 10, 2007 9:34 AM
> To: [email protected]
> Subject: Defining virtual CTCAs
>
>
> All:
>
> I have the need to define a virtual CTC between a first-level
> zVM machine and a 2nd-level zVM machine. This is in order to activate
> ISLINK between those two machines.
>
> Since the virtual CTCs need to "belong" to the z/VM "system" I
> am at a loss as to how to do this. Can anyone help lift the fog?
>
> David Wakser
> InfoCrossing
> --------------------------------------------------------
>
> This message w/attachments (message) may be privileged, confidential or
> proprietary, and if you are not an intended recipient, please notify the
> sender, do not use or share it and delete it. Unless specifically
> indicated, this message is not an offer to sell or a solicitation of any
> investment products or other financial product or service, an official
> confirmation of any transaction, or an official statement of Merrill
> Lynch. Subject to applicable law, Merrill Lynch may monitor, review and
> retain e-communications (EC) traveling through its networks/systems. The
> laws of the country of each sender/recipient may impact the handling of
> EC, and EC may be archived, supervised and produced in countries other
> than the country in which you are located. This message cannot be
> guaranteed to be secure or error-free. This message is subject to terms
> available at the following link:
> http://www.ml.com/e-communications_terms/. By messaging with Merrill
> Lynch you consent to the foregoing.
> --------------------------------------------------------
