Invoking Control-M/Analyzer Using a Direct Call

The Control‑M/Analyzer Runtime environment can be invoked by a direct call from any of the following:

• application program

  The name of the rule to be invoked is specified by the application program’s call to Control‑M/Analyzer. For additional information, see the section about calling user routines in the Control‑M/Analyzer User Guide.

  The syntax is

  CALL CONTROLB(<rule name>)

• job step

  The rule to be invoked is specified by the JCL statement of the job step (in the balancing job). This is the most frequently used method.

  The syntax is

  // EXEC CONTROLB,RULE=rulename,GROUP=group,ARG=(arg1,...argn)

  Note: The GROUP argument is mandatory only if the rule definition does not contain a value for parameter GROUP. If parameter GROUP is specified in the rule definition, the GROUP argument is optional.

  The ARG specification allows up to 50 arguments. For more information, see Passing Arguments While Invoking Control-M/Analyzer.

• another INCONTROL product

  The rule to be invoked is specified by parameter DO CTBRULE in a Control‑M job scheduling definition or a Control‑D decollating mission definition.

When Control‑M/Analyzer starts processing, it searches for the specified rule in the libraries referenced by DD statement DABRULE.

If the rule is found, it is invoked. If the rule is not found, a runtime error occurs.

This flexibility allows the Control‑M/Analyzer user to select one or more appropriate points in the life cycle of a particular data source during which balancing activities must be performed. For example:

• Control‑M/Analyzer can be invoked before the creation of a report to check the validity of the report job input.
• Control‑M/Analyzer can be invoked before updating a database (for example, a DB2 table) or an important file in the system. Control‑M/Analyzer checks the validity of the input used for the update.
• After a report is created, it can be checked during the current job before executing other steps in the job and before the report is distributed.
• Control‑D can invoke a Control‑M/Analyzer rule to validate a decollation process.
• Control-M can invoke Control-M/Analyzer to perform balancing actions that verify the input and/or output of a job run. Job flow can be controlled by Control-M based on the results of these balancing actions.