Post Conversion Steps: Dollar Universe HDP jobs

Before running Dollar Universe HDP ("HDP") jobs you need to configure Control-M otherwise these jobs cannot run correctly. For more information, see Control-M configuration HDP job.

After you have converted your HDP jobs, the jobs are loaded into Control-M. When you open Control-M client, you see all the converted jobs in a Workspace in the Planning domain. If you have selected Append conditions for viewing links between jobs in Control-M in the Conversion Tool HDP options, you see how the jobs are linked together in the Planning and Monitoring domains in Control-M client. For more information about the Conversion Tool HDP options, see HDP Options parameters.

Control-M links HDP jobs through the following Job Prerequisites and job actions in Control-M client:

• In Conditions: Specifies one or more In conditions which correspond to the successful completion of another job. An In Condition is usually associated with an Out Condition of a successful completion of a predecessor job. For more information, see In Conditions in Using Control-M.
• Out Conditions: Defines conditions which are added or deleted to the Conditions table when the job ends for a predecessor job. For more information, see Out Conditions in Using Control-M.
• On Do Action: Defines automatic interventions such as rerunning a job or ordering a remedial job. For more information, see Job Actions in Using Control-M.

If you want to add or delete an HDP job, see HDP job management.

When a job runs on several hosts, a message is sent to Control-M script, using the Shout to Program functionality.

EXAMPLE:

-host_group T_1 -job_to_order HDP_TEST_02#0002 -folder EXP_HDP_SES_01_T_1 -MU_type T -relationship CHILDREN -condition_variable %%ORDERID

NOTE: All parameters are mandatory. –condition_variable must be defined as %%ORDERID. For further information about the parameters, see Message parameters.

When the script receives the message, it finds host groups that match the criteria by scanning the MUdependencies.txt file (which contains relations between hosts). The script then performs CTM order on every host group that matches the criteria. The MUdependencies are performed according to the following parameters:

• -host_group
• -MU_type
• -Relationship

EXAMPLE: MUdependencies.txt contains the following values:

HOSTGRP CHILD

----------------------------------------------------------------

T_1 T_2

T_1 T_3

T_1 K_1

T_1 T_4

T_2 T_5

T_2 T_6

T_4 T_7

The script contains the following message:

-host_group T_1 -job_to_order HDP_TEST_02#0002 -folder EXP_HDP_SES_01_T_1 -MU_type T -relationship CHILDREN -condition_variable %%ORDERID

The script performs ctmorder on the Child relationship with Type T, related to Host T_1. The script starts scanning the MUdependcies.txt and then performs ctmorder for Job HDP_TEST_02#0002 from Folder EXP_HDP_SES_01_T_1 on 3 host groups:

T_2 , T_3 , T_4 but not on K_1 that has a different type.