The seventh table, IVP6, executes a series of CTMAPI (Control‑M Application Program Interface) batch utilities.

These jobs verify several online functions in the Control‑M Active Environment (Screen 3) and in the IOA Global Variable database.

Each of these jobs is separated by a run of the IOATEST utility, which causes Control‑M to wait for 5 seconds, to allow time for each job to end before continuing.

The first job uses the CTMAPI to issue a FORCE OK command in relation to the job in the IVP1 table that ended NOTOK. To identify the failing job, it uses the order ID that was placed in the IOA Global Variable database by that job when it failed.

The next job searches for the job that was FORCEd OK by the previous job. The job that was FORCEd OK has the status END_OK_FOK.

The following series of jobs operate on the same job, that is, the one that was FORCEd OK. In turn, the following happens:

• its status is changed to HOLD
• it is DELETEd
• it is UNDELETEd
• it is placed back into FREE status

You can use Screen 3 to watch these processes happening.

Several of these jobs verify the operation of the IF selection function of the CTMAPI.

The next job is @#$DUMY. This is a dummy job, and is ordered with WAIT CONFIRMATION status. This job is followed by a CTMAPI task that checks whether @#$DUMY is present in the Active Jobs file, and, if it finds that it is, CONFIRMs it.

The last task in the table invokes CTMAPI, which uses the SETCKP command to add a Global variable to the IOA Global Variable database. This variable is %%\M\NO_APPL\NO_GROUP\API\GBL_SET, and the value assigned to it is API. To ensure that this has been successfully performed, use the IOA option IV, and examine the contents of the IOAVAR pool to see if this is present.