Chris Thank you for the suggestions. I was able to active the CDRSC on the EN, delete the CDRSC from the NN, and update the ADJCLUST table entry. That all looks good and looks like it should probably work.
However, when the local application attempts to establish a session with the remote LU it is looking for MYNET.RMTLU as opposed to RMTNET.RMTLU. And since the new CDRSC was activated, that can't be resolved. Do I need to be controlling application session request or is there something within VTAM that I can use to control either the request or the resolution? Thank you Luke -----Original Message----- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Chris Mason Sent: Tuesday, December 22, 2009 4:37 AM To: IBM-MAIN@bama.ua.edu Subject: Re: VTAM search/routing problem Luke I've taken another look at this because it should be possible to do what you want by using an adjacent cluster routing list. So I did some research in order to refresh my memory as best I could over how it all might work - but you'll have to test it, of course. First let's have a CDRSC so that we know what network identifier belongs to the remote LU: VBUILD TYPE=CDRSC NETWORK NETID=RMTNET RMTLU CDRSC NATIVE=NO,NQNMODE=NQNAME,REGISTER=YES,SUBAREA=NO Note that REGISTER=YES is specified in case the partner LU initiates the session sometimes. This should be defined in the End Node which initiates the session. After attempting the session initiation, you should display the LU name (as a CDRSC) in the Network Node (Server) to be sure it is qualified with the desired NETID. You may need to clear the CDRSC out of the Network Node by using the following command: VARY NET,INACT,ID=RMTLU,DELETE=YES Now let's set up the adjacent cluster routing list in the Network Node (Server)/Border Node so that the session setup is forbidden to go anywhere but where we want it to go: VBUILD TYPE=ADJCLUST NETWORK NETID=RMTNET RMTCP NEXTCP CPNAME=RMTNET.RMTCP,BNDYN=NONE,BNORD=DEFINED,SNVC=2 Note that BNORD=DEFINED is actually redundant given there is only one entry! The way the subnetwork visit count (SNVC) works is a bit odd. It is something like the following: 1. When the request is about to cross a subnetwork border, 1 is subtracted from the SNVC value in the request. 2. If the value is now 0, the request is not sent. Obviously if it is now more than 0, the request is sent. That explains why SNVC=1 limits you to your native subnetwork and SNVC=2 allows just one subnetwork border to be crossed. - Well, I hope that's a starting point! Let us know how you get on. Chris Mason On Mon, 21 Dec 2009 09:22:38 -0600, Rabbe, Luke <luke.ra...@countryfinancial.com> wrote: >I'm having a difficulty with routing particular process' VTAM traffic and I can't figure out how to make VTAM do what I want it to. > >My network is 1 network node and several end nodes. The application in this process resides on an end node. I have 2 Enterprise Extender nodes on the network node. One EE node is connected to an intermediate network. The other is directly connected to a business partner's network. I used to use the intermediate network to reach the business partner's network, but now I only want traffic to flow through the direct route. > >I'm able to accomplish this when the EE connection to the business parter (EEBP) is active and session initiation is attempted. When EEBP is active, the traffic flows from my end node, to my network node, through EEBP, and to the business partner's CP. That's great. However, if EEBP is made inactive, VTAM routes all new and existing sessions through the intermediate network. I don't want this to happen - I don't want to use the intermediate network any more. > >These are my VTAM defintions that I think are relavant: > >Network node: > >Adjacent cluster table: > VBUILD TYPE=ADJCLUST > NETWORK NETID=(RMTNET) >RMTCP NEXTCP CPNAME=RMTNET.RMTCP,SNVC=2 >NNCP NEXTCP CPNAME=MYNET.NNCP,SNVC=2 > >ADJSSCP table: > VBUILD TYPE=ADJSSCP > NETWORK NETID=RMTNET,SORDER=ADJSSCP >RMTCP ADJCDRM > > >End node: > >VTAMOPT SORDER=APPNFRST > >ADJSSCP table: > VBUILD TYPE=ADJSSCP > NETWORK NETID=RMTNET,SORDER=ADJSSCP >RMTCP ADJCDRM >NNCP ADJCDRM > >VBUILD TYPE=ADJSSCP > NETWORK NETID=MYNET >NNCP ADJCDRM >ENCP1 ADJCDRM >ENCP2 ADJCDRM >ENCP3 ADJCDRM > NETWORK >NNCP ADJCDRM >ENCP1 ADJCDRM >ENCP2 ADJCDRM >ENCP3 ADJCDRM > >My CDRSCs on the EN are dynamic. I don't think this matters because I tried this with statically defined CDRSCs and got the same result. > >I suspect a clue to the problem lies in the fact that when the application attempts to start a session, the remote LU is qualified with my network ID as opposed to the business partner's network ID (MYNET.LU1 vs. RMTNET.LU1). So, the EN VTAM uses the ADJSSCP table for MYNET instead of RMTNET. In doing so the APPN network is searched first because of the VTAM startup option. And because of that the remote CP is found whether the direct EE connection is active or not. And when the direct EE connection is active, VTAM chooses to use it. I don't want to change my local network ADJSSCP table or the SORDER default on the end node. > >I hope I've explained myself well enough. Does anyone have any ideas on how to establish and maintain the route through the direct EE connection? > >Luke ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
