Previous Topic

Next Topic

Book Contents

Book Index

RUNTSEC (CMEM): General Parameter

Specifies the runtime security environment for the rule.

Figure 369 RUNTSEC (CMEM) Parameter Format

Optional. The abbreviation, that is, the first letter, of the desired value can be entered. Valid values are:

Table 246 Valid RUNTSEC (CMEM) Values

Value

Description

NONE

Runtime security checks are not performed for this rule.

OWNER

Runtime security checks are performed 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 performed using the user ID associated with the started task, TSO user, or batch job 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: Value TRIGGER applies only to ON DSNEVENT, ON STEP, or ON JOBEND event rules. If the value TRIGGER is entered for an ON JOBARRIV event rule, the value is treated as OWNER.

Parent Topic

Control-M Event Manager (CMEM)