The scenario is:
- user is on a wired LAN connection
- starts windows Emulation session to the mainframe
- starts a TPX application session
- disconnects from the wired LAN Connection and goes to a wireless connection.
- the previous windows emulation session was terminated
- restarts the windows emulation session
- starts a TPX application session and gets the error saying "already signed on".
This is different than clicking on the Windows "X" to close the session. TPX does terminate all active sessions and user can subsequently sign on.
However, when the session just drops from Wired -> Wireless, no errors are seen yet users cannot sign on again.
When the emulator is closed with the X, VTAM is aware that the connection has closed and, in turn, TPX is also aware.
When the wired connection is disabled (wire is pulled), the connection is still considered active by VTAM since no 'action' is requested by the 'user'.
In other words, when X is selected, this is a user 'action' and is passed to VTAM. Pulling the cable is not a user 'action' that is passed to VTAM.
When the user reconnects with a wireless connection this is a different network path, with a 'new' session from VTAM perspective.
Since the wired connection is still considered 'active' for all sessions previously started, VTAM correctly returns an "Already logged on" message.