The NJE connection between nodes Y (JES3)and Z (JES2) use the AT&T Advantis SNA network, so there is no IP connection between them. Note, in our case node Z is a business partner. Mark T. Regan, K8MTR CTO1 USNR-Retired (1969-1991)
________________________________ From: "Staller, Allan" <[email protected]> To: [email protected] Sent: Thursday, January 8, 2009 2:30:43 PM Subject: Re: Routing a NJE connection via another NJE node Why go through Node Y at all? Use JES2/TCPIP and connect directly to JES3/TCPIP on Node Z. Or am I missing something here? <snip> Subject: Routing a NJE connection via another NJE node We have two companies (nodes X and Y) that connect to the same remote NJE node (Z) via SNA, using the old Advantis SNA network. For one of the companies (X), we want to eliminate its SNA connection to Advantis. For node X to continue get to the remote NJE node (Z)site, we want to set up a TCP/NJE connection between nodes X and Y and then tell node X that to get to node Z, you have to route via node Y. Both nodes X and Z are JES2 sites and node Y is JES3. Not being a JES2 sysprog, what do we have to change in the JES2 NJE set ups to tell them that to get to X or Z, they need to route through their existing connections with node Y? Going from: X ---> SNA/NJE ---> Z to: X ---> TCP/NJE ---> Y ---> SNA/NJE ---> Z </snip> ---------------------------------------------------------------------- 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
