AVS does, but TSAF does not.
Marcy Cortes "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Wakser, David Sent: Wednesday, October 10, 2007 8:07 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] Defining virtual CTCAs Marcy: Unless I am mistaken, TSAF requires VTAM - which is not running in the 2nd-level VM. David Wakser -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Marcy Cortes Sent: Wednesday, October 10, 2007 11:04 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Defining virtual CTCAs Can you use TSAF for what you want to do? I've used that to shared SFS between 1st and 2nd level without a real CTC, only virtual. Marcy Cortes "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Wakser, David Sent: Wednesday, October 10, 2007 7:04 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] Defining virtual CTCAs Mark: That is what I was afraid of - that first level needed a REAL CTC. Thanks for the confirmation. David Wakser -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Mark Wheeler Sent: Wednesday, October 10, 2007 10:01 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Defining virtual CTCAs The 1st level system (CP) needs to use a real CTC device, so the 2nd level system will need to have another real CTC device attached to it, capable of connecting (via IOCP defs) to the first. Or wo a third system in your CS collection which itself has an ISLINK to the first. Mark L. Wheeler IT Infrastructure, 3M Center B224-4N-20, St Paul MN 55144 Tel: (651) 733-4355, Fax: (651) 736-7689 mlwheeler at mmm.com "Extraordinary claims require extraordinary evidence." Carl Sagan "Science is organized common sense where many a beautiful theory was killed by an ugly fact." Thomas Henry Huxley "Stracka, James (GTI)" <[EMAIL PROTECTED] To .com> IBMVM@LISTSERV.UARK.EDU Sent by: The IBM cc z/VM Operating System Subject <[EMAIL PROTECTED] Re: Defining virtual CTCAs ARK.EDU> 10/10/2007 08:48 AM Please respond to The IBM z/VM Operating System <[EMAIL PROTECTED] ARK.EDU> 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: IBMVM@LISTSERV.UARK.EDU 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. --------------------------------------------------------
