UNBINDAPPL

Description

Used in conjunction with the UNBIND=WAIT specification (see UNBIND), which causes each UNBIND from secondary level applications to be treated as UNBIND with BIND forthcoming.

This common session parameter is applicable to these control statements: PROFILE (see PROFILE statement), USER (see USER statement), TERMINAL (see TERMINAL statement), and APPL (see APPL statement). It is not applicable to the SYSTEM control statement.

Format

UNBINDAPPL applid

Usage

In some instances, a secondary application may validly issue an UNBIND to cause a logoff, but if UNBIND=WAIT is specified, IBM Session Manager maintains the session for one minute.

UNBINDAPPL specifies the name of a secondary application for which UNBIND will not be treated as UNBIND with BIND forthcoming, and so an UNBIND will cause immediate session termination.

For further explanation and examples, see the section 'UNBIND WAIT applications' in the chapter 'Setting up applications' of the Installation and Customization manual.

See also STOPINH and STOP_INHERIT keywords.

Parent topic:

Related topics: