Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see CHECK PLUS for DB2 13.1.

Running CHECK PLUS jobs


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

Invoking CHECK PLUS

You normally invoke CHECK PLUS as a batch job by specifying 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 preceding sections. Ensure 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

Because CHECK PLUS has only one major phase (CHECK) and the UTILINIT phase is executed even for restart, restarting the check utility has no particular significance.

Terminating or canceling a job

You can terminate a CHECK PLUS job by deleting the corresponding row from the BMCUTIL 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.

If you want 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*