Decides how IBM Session Manager handles an UNBIND request from an application.
This common session parameter is applicable to these control statements: SYSTEM (see SYSTEM statement), PROFILE (see PROFILE statement), USER (see USER statement), TERMINAL (see TERMINAL statement), and APPL (see APPL statement).
IMMEDIATE causes each UNBIND to be processed as it is.
WAIT causes each UNBIND received from the application to be treated as UNBIND with BIND forthcoming.
WAIT may be used for applications such as Logon Managers which transfer between different secondary applications. This is usually achieved by the Logon Manager issuing an UNBIND with BIND forthcoming, and the secondary application issuing an unsolicited BIND.
The problem occurs at log off from the secondary application if it issues an UNBIND without BIND forthcoming. IBM Session Manager assumes that the session has ended, so the unsolicited BIND from the Logon Manager cannot be matched and message 268I is issued. When UNBIND WAIT is specified, IBM Session Manager maintains the session for one minute and waits for a BIND.
When a primary application issues an UNBIND, IBM Session Manager makes no change, even when WAIT is specified.
If the final UNBIND which terminates the session is not issued by the primary application, then the name of the application can be specified on the UNBINDAPPL parameter so that IBM Session Manager processes the UNBIND immediately. If this is not done, the session would hang for one minute until the UNBIND timed out and the session would then terminate.