NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.
1 reply Latest Post - 2013-03-08T18:07:26Z by RDzJohn
Pinned topic NJE connections using TCP/IP
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
We tried doing NJE connections using TCP/IP but ran into an interesting situation with our z/OS LPARs. It appeared that as we activated our NODEs we ended up with RD&T able to xmit stuff out of RD&T to a remote JES2 system in which all the dynamic commands were issued – but the node stayed unconnected on the remote z/OS LPAR for RD&T node. That z/OS LPAR would receive the data from RD&T but couldn’t sent from that remote location to RD&T. Also we tried setting up another NJE connection to another node which was JES3 but wanted to know if we have to piggy back on to the LOCAL Socket from RD&T as documented in manual or can we create new sockets and NETSRVs?
Updated on 2013-03-08T18:07:26Z at 2013-03-08T18:07:26Z by RDzJohn
RDzJohn 060000E02P268 PostsACCEPTED ANSWER
Re: NJE connections using TCP/IP2013-03-08T18:07:26Z in response to wilbertWilbert,
I'm afraid we can't provide any guidance in this area. While theoretically possible, I don't know of anyone that has tried this in the recent past. The only history I know of on this is at one time it was tried and performance was so abysmal that we for all intent and purposes declared in unsupported.