Since the JES link apparently has taken the link down, has done a restart, and is in the active state, waiting for us to come back on. The connection is immediate when RSCS does its restart.
BTW, the KEEPALIV=YES in the PARM for the link had no effect. The full parm specification was "host=ipaddr ito=100 keepaliv=yes". Is there someone who has a working TCPNJE link between z/OS and VM who would be willing to share their definitions for both RSCS and JES? Regards, Richard Schuh -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Les Geer (607-429-3580) Sent: Thursday, March 15, 2007 4:46 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: TCPNJE >As far as I know, JES is aware of the state. Their side apparently has >an autostart because whenever the link drops and RSCS restarts it from >the VM side, the signs are done and the link reestablished for another >22 minutes. > But what is causing the JES side to drain? Is it the keepalive (like is causing RSCS to drain), or is the JES side going down first then the keepalive takes down RSCS? Best Regards, Les Geer IBM z/VM and Linux Development
