Thanks, Dave - but your being able to do it does not explain why we get the error msgs when attempting to start the TCPNJE link (not SNANJE) and let it wait for the JES2 side to start. Perhaps it is old maintenance? But an IBMLink "SIS" search did not turn up anything.
Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. "Dave Jones" <[EMAIL PROTECTED]> Sent by: "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU> 01/15/2007 09:58 AM Please respond to "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU> To IBMVM@LISTSERV.UARK.EDU cc Subject Re: Can RSCS start a TCPNJE link and keep listening for the remote side to start? Hi, Mike. RSCS will keep listening for the remote side of the connection to come up and when it does, RSCS will finish making the connection. You don't need to do anything else on your end..... I have a number of RSCS links here to other z/VM sites that come and go at unpredictable times, and RSCS will start the links automatically when it sees the other side is up. Hope this helps. DJ Mike Walter wrote: > 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 [snip....] > 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. > > > 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.
