loopdetecttool

The loopdetecttool utility checks job processing definitions to determine if conditions are defined in a way that would cause loops. A loop in this context means:

• A chain of jobs never run because the In condition needed to start the first job in the chain is only created by the last job in the chain.
• Any combination of jobs, groups, and conditions between them, because it is not clear which job in the group runs first or last, creating or deleting the relevant conditions.

To check for loops in a number of jobs, see Detecting loops in jobs using the loopdetecttool utility.

The loopdetecttool parameter of the emdef utility reads an argument file (in XML format) that contains criteria that determine which job processing definitions and SMART Folder the utility should analyze. For more information, see loopdetecttool arguments file rules. The utility checks for definitions whose conditions could potentially cause a loop. After the utility runs, it summarizes the problematic jobs and conditions in an XML format file.

The loopdetecttool utility validates the XML rules folder according to the validation process in Control-M/EM version 9.0.19 and above. By adding the switch -vv 2, the utility validates the jobs/folders, which is similar to job/folder validations in Control-M client/Control-M Web. It also validates site standards (includes warnings based on strictness levels), improved error messages descriptions, and updated field names.

NOTE: By default, the utility validates the XML file in accordance with the EmdefValidationVersion system parameter in the CCM (Validation version 2). You can change the value in the CCM without the need to add the switch to the command, which may be preferable if you have many scripts that use a particular validation version.

For an example of the two validation processes see emdef validation service error message example.