SESTYPE

Description

Specifies the session type, which is used by IBM Session Manager to eliminate duplicate sessions.

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).

Format

SESTYPE nnnn

Default: SESTYPE 0

Usage

A user can be associated with multiple profiles, so the ability to eliminate duplicate sessions is especially useful when assigning more than one profile to a USER definition or a TERMINAL definition. See also Rules for profile selection.

To establish the session type, the usual precedence is used - that is, IBM Session Manager searches these statements in turn:

Notes:

  1. (Applicable to existing users of a Classic configuration - that is, all configuration definitions are stored in members of PDS(s) allocated to the DDNAME of CONFIG.) If you run the OLA Enabler to implement the new OLA format configuration, session types can optionally be assigned to sessions automatically (see the Online and Batch Administration manual).
  2. The SESTYPE parameter will be ignored for users who have submenus configured.
  3. If the session number is zero (also the default if a SESTYPE is not specified) then the session is used; that is, session types of zero are not regarded as duplicates.
  4. The IBM Session Manager session variable s_sestype may be used to refer to the value of the session type for an application session; for details, see the Panels, Scripts and Variables manual.
  5. The SESTYPE parameter is important when the user-customizable 'priority' session facility is being used and a user has a common end-user parameter SESSPRIAPPL set to NO (the default) or when the user-customizable 'autostart' session facility is being used and a user has a common end-user parameter SESSAUTOSAPPL set to NO (the default). See SESSPRIAPPL for further details of the SESSPRIAPPL parameter. See SESSAUTOSAPPL for further details of the SESSAUTOSAPPL parameter. The SESTYPE parameter can be set automatically by the OLA Enabler, or by running the sample job ISZSTJOB.
  6. If a session is allocated a SESTYPE value, all the user's other session SESTYPE values will be checked for duplicates. If a user has a large number of sessions it may affect performance, especially when the user signs on to IBM Session Manager. Please bear this in mind when implementing SESTYPE, and test on a non-production system to ensure the performance is at an acceptable level. Please contact your local Support Representative if further assistance is needed.

Examples

If a user's definition contains a session with a SESTYPE of 6, and the user is associated with a profile which also contains a session with a SESTYPE of 6, then it is considered a duplicate.

Suppose a user's definition is associated with two profiles - PROFILE1 and PROFILE2. If PROFILE1 and PROFILE2 both contain a session with a SESTYPE of 25 then it is considered a duplicate.

Parent topic:

Related topics: