Running CHECK PLUS jobs

This topic contains information about invoking, restarting, terminating, and canceling CHECK PLUS jobs.

Related topics

Installing

Building-CHECK-PLUS-jobs

STEPLIB DD statement

SQL-batch-execution-program

Invoking CHECK PLUS

You normally invoke CHECK PLUS as a batch job by specifying the execution of the module ACKUMAIN on the  EXEC statement of your JCL and including the required EXEC statement parameters. You must also specify any required DD statements, as described in the CHECK-PLUS-DD-statements. Make sure that all required libraries are available and APF authorized as described in STEPLIB DD statement. 

Important

If you plan to use the ACKESQL program to delete rows with constraint violations, review SQL-batch-execution-program for additional CHECK PLUS options that you might need to set before running the check job.

Restarting CHECK PLUS

Restarting CHECK PLUS has no particular significance because CHECK PLUS has only one major phase (CHECK) and the UTILINIT phase is run even for restart.

Terminating or canceling a job

You can terminate a CHECK PLUS job by deleting the corresponding row from the BMCUTIL, (BMC.DB2.SPE2404)BMCUTIL2, and BMCSYNC tables or by specifying TERM on the restart parameter of the utility. If the job is currently running, it is terminated at the next sync point.

To end the utility immediately, use the MVS or TSO CANCEL command to cancel the job.

If CHECK PLUS terminates (normally or abnormally) at any point before completion of the UTILTERM phase, the objects being checked are started in the same status they were in when checking began.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*