Disconnect/reconnect feature

When an EXEC terminates, any OSPI sessions that have been established are either terminated or disconnected.

The IMFEXEC LOGOFF command without the DISCONNECT parameter results in a termination request being sent to the VTAM application. When the DISCONNECT parameter is specified, the VTAM session is not terminated and another EXEC may resume the session (RECONNECT) by issuing an IMFEXEC LOGON command with the SESSION parameter. The application will not be aware of any DISCONNECT/RECONNECT activity.

Related topic

Customizing-OSPI-EXECs

When an EXEC tries to reconnect a session, it is important that you check the condition code (IMFCC) after the IMFEXEC LOGON command. Reconnect sometimes fails due to applications terminating OSPI sessions when no activity occurs within a specified time. If IMFCC indicates that a reconnect is not successful, you must reestablish a new session.

To make use of the DISCONNECT/RECONNECT feature, the EXEC that initially establishes the session must store the session identifier (contained in the OSISESS variable) in a shared variable. This variable can then be retrieved by subsequent EXECs to reconnect. A unique shared variable name must be used for each different session that is concurrently maintained.

If an EXEC does not issue an IMFEXEC LOGOFF command, all sessions are automatically terminated. The result is the same as if explicit IMFEXEC LOGOFF commands had been issued for each session.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*