Remember that the LINKDEFINE for RSCS contains both a Link Name and a Node Name. Could it be a mismatch with one of these? According to the RSCS code we have received a reason code of 1 in the CRR control record. This indicates a node mismatch. If reviewing your configuration doesn't find the problem, I would suggest an RSCS Link trace when you are starting the link.
Colleen M Brown IBM z/VM and Related Products Development and Service Kris Buelens <[EMAIL PROTECTED]> Sent by: The IBM z/VM Operating System <[email protected]> 01/15/2007 01:42 PM Please respond to The IBM z/VM Operating System <[email protected]> To [email protected] cc Subject Re: Can RSCS start a TCPNJE link and keep listening for the remote side to start? Note too that when a TCPNJE links breaks, RSCS will not attempt to restart, unless... your create a "LinkName GCS" Rexx exec and place an Address RSCS 'START linkname' inside it. Still not 100% perfect I learned, but it helps. Yes, SNA links has fewer start problems. 2007/1/15, Mike Walter <[EMAIL PROTECTED]>: 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. -- Kris Buelens, IBM Belgium, VM customer support
