Between the production and AD sysplex there had historically been an NJE
connection. Originally that was NJE/SNA. A few years ago that stopped working
(I was told due to misconfiguration of EE), so NJE was switched to NJE/TCP. At
the same time NJE/TCP connections were defined to the three other sysplexes we
have. The definitions were left in the JES2 deck despite the fact that due to
almost completely missing RACF definitions ('free for all') I had those NJE/TCP
connections to the three other plexes terminated.
For various reasons we decided to go back to NJE/SNA via EE (don't ask). We
tried to test-connect two of the sysplexes using SNA. It's fairly easy: Define
a SNA line, define a logon, define the appropiate appl to both JES and VTAM,
start everything and start the node. We failed spectacularly to get the node
active. Despite LOGON1 showing 'inactive' and the line being active, the sn
command always returned 'JES/VTAM interface not active' when used with the SNA
version.
If I used SDSF node panel to start the node, it always told me 'NETSRV1 not
active'. True, since there wasn't any JES2S001 active and should not be since
we wanted to use NJE/SNA.
Eventually I decided to reIPL the sysprog sandplex and the AD plex *without*
the NJE/TCP parms in the JES deck. It took 20 minutes to get NJE/SNA up and
running (including using SN from the SDSF node panel).
Has anyone had a similar experience? Is it described somewhere I did not find
that you cannot start an NJE/SNA connection after years of IPLs with NJE/TCP
keywords in the jes deck, but no actual connection started during that IPL and
the necessary lines/sockets/netsrv having been inactive for the life of the
IPL? Is it described somewhere that NJE/TCP takes precedence? Or have we run
into a bug?
Regards, Barbara
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
