5When connecting to an OS/390 system using SNA, the host VTAM layer 5automatically flows a commit when a new connection is made. The 5automatic commit allows the host side thread state to be inactive, and the 5thread immediately becomes inactive.
5However, when connecting to an OS/390 system using TCP/IP, there is no 5automatic commit. The application itself must flow an explicit commit 5after the connection to allow the thread to be inactive on the host. 5Without the explicit commit, the thread is subject to an idle thread time 5out.
5The suggested workaround is to rewrite the application so that it will 5perform an explicit commit if the connection goes idle after the 5connection.