On Wed, 9 Aug 2006 12:42:21 -0700, Gabe Torres <[EMAIL PROTECTED]> wrote:
>... > To prepare for the new configuration, I defined a new set of CTC/CNC's >definitions without the Director involved, but keeping the old >definitions inplace. I then disable (INACT) the old CTC/CNC links, and >activate the new CTC/CNC links on both the Lpars I want communicating >with each other. I am able to get the Sysplex to use these new >signaling links,. That means PATHIN / PATHOUT defs in a COUPLE member? >... But I can not get COMMSERV to use them for the Cross >Domain communication. >... Assuming you've picked addresses for VTAM that are actually under the same CU as your XCF links (not just conveniently close addresses) there is no reason it should not work. Does a D U,.. show the device addrs online? Allocated to VTAM? I use the same technique. Find XCF links that already work; then take some unused addresses under those CUs and give them to VTAM. I use MPC+ rather than standard CTC defs, but that's not significant. Of course there is an easier technique if your VTAMs are APPN nodes. Set XCFINIT=YES in VTAM and the VTAM s will automatically set up cross- domain connections using the XCF signalling that already exists. Such things are MUCH easier if you migrate from subarea to APPN. Very different, but easier. Pat O'Keefe ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
