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: [email protected]
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 ACTIV----E CUA = 9214
IST232I CTC9215L ACTIV----E CUA = 9215
IST232I CTC8224L ACTIV----E CUA = 8224
IST232I CTC8225L ACTIV----E 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
