Les, We have a Keepalive interval of 20 with sendgarbage true in our TCP/IP definitions and have let the Inactivity Time Out Parm for the TCPNJE link default to 100, which means there will be no inactivity time out from our side. These parameters work nicely when used on VM-VM links.
The timing makes it appear as though the connection is being broken from the z/OS side some time before the Keepalive interval expires. When it does expire, the Garbage packet is transmitted. There is a time out on the garbage packet, which triggers the connection time out messages and action. Does this seem a plausible scenario? Regards, Richard Schuh -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Les Geer (607-429-3580) Sent: Wednesday, March 14, 2007 7:16 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: TCPNJE >All of the DMTTNE083E messages from this link have been due to the >connection timing out. Is this timeout something that is or can be >defined in TCP/IP? I see no parameters for it in RSCS and the MVS >sysprog says the same about JES. > > >An update to the above. The timeouts are occurring at very regular >intervals of between 00:22:36 to 00:22:39. The keepalive interval in >our TCPIP is 20 minutes. It appears that the timeouts are related to >the keepalive message. > Are you using the KEEPALIVE TCPNJE link parm? Best Regards, Les Geer IBM z/VM and Linux Development
