Activating a rule set

You must activate a rule set before RUV can use it. RUV supports two levels of activation, subsystem-level and job-level. The subsystem-level rule set controls all jobs running in the z/OS system. A job-level rule set applies to a single batch job only. Only one rule set may be active at the subsystem level, but each batch job may have its own unique rule set.

Normal RUV operation is best controlled by a subsystem-level rule set. Job-level rule sets should be used for testing purposes and special situations that may require you to override the system-level rule set. It is suggested that you test all changes to rule sets before activating them at the subsystem level.

After you activate a rule set, RUV searches the rule set when a VSAM file is opened to determine the action to take (if any action is needed).

Note

You must reactivate your rule set after you update any user variables.

Using the ACTIVATE RULE_SET command

This part describes how to use the ACTIVATE RULE_SET command.

Job-level rule sets

To active a job-level rule set, execute the RUVZSM0 program with the ACTIVATE RULE_SET command, as shown in the following example. Use the value of the RULE_SET keyword to define the name of the rule set to activate. (This name is the same name you use as the value of the RULE_SET keyword on an ADD RULE_SET statement.)

ACTIVATE RULE_SET(TESTING);

System-level rule sets

You can activate the subsystem-level rule set only with the ISPF interface. For more information, see Using-the-ISPF-interface-to-work-with-rule-sets.

Using the TRACE_ON keyword

You can include the optional TRACE_ON keyword on the ACTIVATE RULE_SET command to view rules as you test them with the TRY command. The TRACE_ON keyword has no values. For more information about the TRY command, see Testing-a-rule-set.

Processing the ACTIVATE RULE_SET command

RUV establishes an association between a batch job and a rule set whenever one of the rules in the rule set is matched. Once RUV establishes this association, the job completes under the same rule sets that it started under.

In response to the ACTIVATE RULE_SET command, RUV reads the named rule set from the RUV repository and loads into memory the user variables and the rules that correspond to the named VSAM sets and job sets. RUV loads into memory the internal reader and job JCL entries at the beginning of a job step when the rule/job association is made. RUV reads journal models as they are needed to allocate journals or logs. The following table shows rule set processing:

Rule set entry	Loaded into memory	RUV variables expanded	Action if not in repository	Changes to entry in repository take effect
VSAM set	During ACTIVATE command	No	Skipped	During next ACTIVATE command
Job set	During ACTIVATE command	No	Skipped	During next ACTIVATE command
User variable set	During ACTIVATE command	No	Skipped	During next ACTIVATE command
Internal reader	Beginning of job step when interest in a VSAM file has been established	Yes	Search for $DEFAULT	Beginning of next job step after interest in a VSAM file has been established
Skeleton JCL	Beginning of job step when interest in a VSAM file has been established	Yes	Search for $DEFAULT	Beginning of next job step after interest in a VSAM file has been established
Journal model	At journal or log allocation time	Yes	Search for $DEFAULT	At next use
External vendor	During ACTIVATE command	No	Skipped	During next ACTIVATE command

Coding the ACTIVATE RULE_SET statement

To code an ACTIVATE RULE_SET statement, use the following syntax.

Note

This command activates a job-level rule set. You activate a subsystem-level rule set from the ISPF interface or from a z/OS console.

ACTIVATE RULE_SET(name32)
{ TRACE_ON }
;