We are just now beginning to experiment with the RSCS TCPNJE link to z/OS (had to wait for z/OS to provide a TCPNJE link for JES2). When we start an SNANJE link on RSCS, it will wait patiently for the remote side to start up.
But when attempting to start an RSCS TCPNJE line driver (link name "UTR" in this case) when the remote (JES2) side is not already started and listening, we get the following msgs: rscs start utr VMYINI006I 0.001 Ready; 09:31:17 DMTCMY700I Activating link UTR TCPNJE line=0000 class=* queueing=priority DMTCMY700I Activating link UTR TCPNJE line=0000 class=* queueing=priority DMTTNE181I Link UTR ready for session initiation DMTTNE185E Link name mismatch -- link UTR deactivated DMTTNE183I Link UTR session terminated DMTMAN002I Link UTR deactivated rscs q sys links VMYINI006I 0.001 Ready; Link Line Name Status Type Addr LU Name Logmode Queueing HALINMA1 connect SNANJE 0000 HALINMA1 ... priority UTR inactive TCPNJE 0000 ... ... priority ... a couple other links removed to reduce clutter... Side issue: why do we get "DMTTNE185E Link name mismatch" when there does not appear to be a mismatch (the link name and JES2 node name are both "UTR"), and "UTR" starts up and connects perfectly when the JES2 side is started and waiting. Perhaps it is because our RSCS is a wee bit behind in maintenance? rscs q sys level RSCS Networking Version 3, Release 2.0-9902 I could bring RSCS up to current maintenance if it would help. But it did not seem worth the effort since we only use RSCS for a single NJE link (one of the reasons to switch to the TCPNJE driver, as well as to eliminate VM/VTAM). We *could* just automate frequent "RSCS START tcpnje_linkname" commands, but it would be cleaner to just teach RSCS to keep listening for the remote side to connect. Any clues would be appreciated. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited.
