The ctmudchk utility checks if all jobs that should have been ordered by a User Daily name job are in the Active Jobs database. This utility facilitates recovery from the interruption of a User Daily job. If a User Daily job is interrupted for any reason (for example, operating system crashes, User Daily job errors), the ctmudchk utility can determine which jobs in the affected user daily ended okay, which jobs had interruptions, and which jobs had not yet run. You can examine the outputs and logs related to the jobs that were in process to decide what to do, but the utility can reorder the jobs that did not yet run.
If ctmudchk is executed before the order is complete by a User daily Name (ctmudly), ctmudchk will wait for the order to complete. By default, it will wait up to 200 seconds. If the wait time had passed, the ctmudchk exits with return code 1. The wait time can be configured by adding and setting the CTMUDCHK_RETRIES and CTMUDCHK_RETRIES_WAIT parameters, as described in Utility parameters .
Return Code |
Description |
|---|---|
0 |
Success |
1 |
User daily Name (ctmudly) is currently running. |
2 |
Cannot determine if the User daily Name (ctmudly) is currently running, because ctmudchk did not receive any response from the Control-M/Server CE process (APIGTW). |
Other |
Failure |
Before ordering the job, ctmudchk verifies that a job is not already present in the Active Jobs database. When using the ctmudchk utility, the New Day procedure must not be running.
To handle an interruption in User Daily processing, run the ctmudchk utility for the affected User Daily to order jobs that were not ordered because of the interruption. To run the ctmudchk utility, see Checking and ordering jobs using the ctmudchk utility.
Parent Topic |