Re: COMMSERV using CTC CNCs
Pat, Yes, the new links are allocated by XCF (Pathin/Pathout) and COMMSERV (CTC;s). I did a dynamic PATHIN/PATHOUT add for the Sysplex links. Will need to update PARMLIB to make them permanent. It just seems I need to tap COMMSERV on the shoulder to use the new links..but not sure how. I can not bounce COMMSERV because its production. .. And of course, no test time before we go live. Mentioned in another response to Listserv.. We are a combination of SUBAREA and APPN. Thanks, gabe - That means PATHIN / PATHOUT defs in a COUPLE member? 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? 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 -- 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
Re: COMMSERV using CTC CNCs
Yes, the new links are allocated by XCF (Pathin/Pathout) and COMMSERV (CTC;s). It just seems I need to tap COMMSERV on the shoulder to use the new links..but not sure how. I can not bounce COMMSERV because its production. .. And of course, no test time before we go live. Mentioned in another response to Listserv.. We are a combination of SUBAREA and APPN. Thanks, gabe -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Patrick O'Keefe Sent: Wednesday, August 09, 2006 7:33 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: COMMSERV using CTC CNCs 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 -- 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
Re: COMMSERV using CTC CNCs
Gabe Torres wrote: -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] Behalf Of Gabe Torres Sent: Wednesday, August 09, 2006 12:42 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: ESTAE control block chain. (from assembler-list) Hello List, We are dropping our Escon Directors from our mainframe configuration. We have CTC/CNCs using an Escon Director to communicate between COMMSERV's on two Lpars on a single processor. We will be moving to CTC/CNC's without an Escon Director. Our Sysplex also uses these for PATHIN and PATHOUT signaling links between the Lpars. 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,. But I can not get COMMSERV to use them for the Cross Domain communication. A display of the new links show they are active and available: D NET,E,ID=CTCXP2 IST097I DISPLAY ACCEPTED IST075I NAME = CTCXP2, TYPE = CA MAJOR NODE 100 IST486I STATUS= ACTIV, DESIRED STATE= ACTIV IST654I I/O TRACE = OFF, BUFFER TRACE = OFF IST170I LINES: IST232I CTC9214L ACTIVE CUA = 9214 IST232I CTC9215L ACTIVE CUA = 9215 IST232I CTC8224L ACTIVE CUA = 8224 IST232I CTC8225L ACTIVE CUA = 8225 How do I get COMMSERV to use the new links ? What am I missing ? TIA,. ..any help is appreciated, Gabe Do you have paths coded? Are you setup for SA or APPN, or both? -- 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
Re: COMMSERV using CTC CNCs
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
COMMSERV using CTC CNCs
-Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Gabe Torres Sent: Wednesday, August 09, 2006 12:42 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: ESTAE control block chain. (from assembler-list) Hello List, We are dropping our Escon Directors from our mainframe configuration. We have CTC/CNCs using an Escon Director to communicate between COMMSERV's on two Lpars on a single processor. We will be moving to CTC/CNC's without an Escon Director. Our Sysplex also uses these for PATHIN and PATHOUT signaling links between the Lpars. 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,. But I can not get COMMSERV to use them for the Cross Domain communication. A display of the new links show they are active and available: D NET,E,ID=CTCXP2 IST097I DISPLAY ACCEPTED IST075I NAME = CTCXP2, TYPE = CA MAJOR NODE 100 IST486I STATUS= ACTIV, DESIRED STATE= ACTIV IST654I I/O TRACE = OFF, BUFFER TRACE = OFF IST170I LINES: IST232I CTC9214L ACTIVE CUA = 9214 IST232I CTC9215L ACTIVE CUA = 9215 IST232I CTC8224L ACTIVE CUA = 8224 IST232I CTC8225L ACTIVE CUA = 8225 How do I get COMMSERV to use the new links ? What am I missing ? TIA,. ..any help is appreciated, Gabe -- 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 -- 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
