Introduction

The reformatting, enforcement, and site standards features ensure that JCL statements comply with required enterprise standards. The user defines rules that specify the required formats, values, or standards, and then runs Control-M JCL Verify to apply the rules. The rules are independent of each other and are invoked separately.

The rules are based on an event-action triggering process using ON (for detecting events) and DO (for performing actions) statements. This mechanism is similar to the one implemented in other IOA products such as Control-M (CMEM), Control-M/Tape, and Control-O.

For each rule the user defines one or more

• ON statements - to specify what events trigger the process
• DO statements - to specify what actions are taken after the process is triggered

There are several available types of ON statements, described later in the chapter, each of which handles a specific JCL statement type (for example, JOB, EXEC, and DD) or other JCL parameter.

ON statements have a set of one or more selection fields for matching the appropriate rule to the JCL statements requiring testing.

DO statements are contained in a DO block, which supports a set of commands and built-in functions.

The data, from JCL statements or external resources (such as member name, library name, and environment) is stored in variables by the system. The user can also define temporary variables and store data in them.

For overviews of the various available types of rules, see

• Site standards (STDR) overview
• Reformatting (REF) overview
• Enforcement (ENF) overview

For a guide to which interfaces and utilities to use for the various rule tasks, see Creating, managing, and applying rules.