Previous Topic

Next Topic

Book Contents

Book Index

RUNTSEC: General Parameter

Specifies the runtime security environment for the rule.

Figure 227 RUNTSEC Parameter Format

Optional. Valid values are described in Table 169.

Table 169 RUNTSEC Values

Value

Description

NONE

Runtime security checks are not carried out for this rule.

OWNER

Runtime security checks are carried out using the user ID entered in the OWNER field of the rule. The specified value is effective only if RUNTDFT is not set to DISABLE.

TRIGGER

Runtime security checks are carried out using the user ID associated with the started task, TSO use or batch job that issued the message or command that invoked the rule. The specified value is effective only if RUNTDFT is not set to DISABLE.

blank

Runtime security is determined by Global parameter RUNTDFT (NONE,OWNER, or TRIGGER) in the CMMPARM member for CMEM and in the CTOPARM member for Control-O. By default, the value of RUNRDFT is set to DISABLE, which means that run time security is disabled and it overrides any RUNTSEC in the rules. To enable run time security a value other than DISABLE must be specified for RUNTDFT.

For CMEM: A CMMPARM member is provided in IOAENV that does not have a definition for the RUNTDFT parameter. To enable run time security, CMMPARM must be copied from IOAENV to the PARM library and a value (not DISABLE) of RUNTDFT must be specified.

For example:

SECURITY RUNTDFT=NONE,   

RUNTCACH=100 RUNTIME SECURITY CACHE specified.

Note: The value TRIGGER can be set only for rules with the following ON statements:

In all other cases, RUNTSEC is interpreted as OWNER.

Parent Topic

Rule Parameters