You can set the maximum idle time that the TCP protocol will allow before sending a probe to test for an inactive session using the TCP keep-alive parameter.
The protocol will send keep-alive requests to the remote client any time the session remains idle for periods longer than the the keep-alive value. The idle period is defined by the Session keep alive timeout parameter in Telnet properties in iSeries™ Navigator or a parameter in the CHGTELNA command. When a session is deemed to be inactive (no response from the remote client to any keep-alive probe), that session is ended; the virtual device associated with the session is returned to the free pool of virtual devices; and the iSeries operating system performs the action set in the QDEVRCYACN system value on the interactive job running on the virtual device. This action affects (only) named virtual devices. For automatically selected virtual devices (QPADEVxxxx), the interactive job always ends.
The Telnet server defines the keep-alive setting to 600 seconds by default.
The setting takes effect at server startup. In addition to the session keep-alive timeout parameter, you might also want to review the Time out interval settings in the Inactive Jobs System Values in iSeries Navigator. This timeout parameter is used to limit the amount of time that any interactive job is allowed to be idle before the iSeries operating system performs the action set in the QINACTMSGQ system value on the interactive job. In the case of Telnet connected interactive jobs, an action of *DSCJOB is only honored for named virtual devices. For automatically selected virtual devices (QPADEVxxxx), an action of *DSCJOB will cause the interactive job to be ended.
To set the keep-alive parameter for Telnet in iSeries Navigator, follow these steps:
What to do next:
Assign devices to subsystems