STOPINH and STOP_INHERIT keywords

Description

The majority of common session parameters have a mechanism to prevent inheritance of a value from the SYSTEM (see SYSTEM statement), PROFILE (see PROFILE statement), USER (see USER statement), and TERMINAL (see TERMINAL statement) control statements, by specifying No or OFF to take the default value instead.

For the common session parameters that do not have this mechanism (see below), you can use the STOPINH and STOP_INHERIT keywords for this purpose.

Usage

These common session parameters do not have the mechanism to prevent inheritance of a value from the SYSTEM, PROFILE, USER, and TERMINAL statements:

ACB
ADDSID
APPLSEL
AUTOSCRIPT
BLANKSCRIPT
BRDVAR
DATA
DESCRIPTION
ENDSCRIPT
ENVIRONSCRIPT
INITSCRIPT
LOGMODE
NETID
PSTKAPPL
PSTKUSER
REMOTE
SAUTOSEQ
SESSDATA1 - SESSDATA5
STARTSCRIPT
TERMSCRIPT
UNBINDAPPL

STOPINH

Will stop the value of a keyword from being inherited and revert to the default. For example:

ACB STOPINH

specified on a session definition will stop the inheritance of an ACB value specified on a USER statement and revert to the SESACB value on the SYSTEM statement (the default).

STOP_INHERIT

This keyword can be used for the ADDSID and SAUTOSEQ parameters. For the ADDSID parameter, in the IBM Session Manager Administration Plug-in (and in OLA), STOP_INHERIT is specified on the INHERIT subparameter.

The ADDSID and SAUTOSEQ parameters can have multiple values when you want to suppress some while keeping others. For example, consider the following definitions on a SYSTEM statement:

SAUTOSEQ gb1 n cmd1
SAUTOSEQ gb2 n cmd2
SAUTOSEQ gb3 n cmd3

By specifying:

SAUTOSEQ gb3 STOP_INHERIT

on a USER, PROFILE or session definition, the sequence gb3 will be suppressed while the sequences gb1 and gb2 will be retained.

Parent topic:

Related topics: