How to define and schedule a series of jobs in a flow to run cyclic on Control-M/Enterprise Manager?

Version 5
    Share:|

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    Control-M/Enterprise Manager


    COMPONENT:

    Control-M/Enterprise Manager


    APPLIES TO:

    All versions of Control-M/Enterprise Manager



    QUESTION:

    - How to define and schedule a series of jobs in a flow to run cyclic on Control-M/Enterprise Manager?
    - How can I schedule a series of jobs to all run in sequence multiple times in a day on Control-M/Enterprise Manager??
    - How to define a series of jobs that will run in a continuous cyclic on Control-M/Enterprise Manager??


    ANSWER:

    1. There is no parameter to define a folder to be cyclic.
    2. The way to accomplish this task is to make each job in the series cyclic and set the In Conditions in the Prerequisites tab to "Delete Condition After Job Ends".
    3. These are the steps:
    - Define a IN-Condition for the 1st Job where the IN-Condition will be created by the last job
    - Define a series of jobs with IN condition created by precedence job so the jobs will run in series
    - Define each job to delete the IN-Condition after executing
    - Define a job to create the IN-Condition used by the 1st job to start the flow
    For example:
    - JobSTART: OUT-Condition COND_C
    - JobA: IN-Condition COND_C / OUT-Condition COND_A(+) COND_C(-)
    - JobB: IN-Condition COND_A / OUT-Condition COND_B(+) COND_A(-)
    - JobC: IN-Condition COND_B / OUT COND_C(+) COND_B(-)
    In this way,
    - JOBSTART will create COND_C (forJobA to run)
    - JobA will start when JOBSTART ended and COND_C is created
    - JobA will delete COND_C and create COND_A (for JobB to run)
    - JobB will start when JobA ended and COND_A is created
    - JobB will delete COND_A and create COND_B (for JobC to run)
    - JobC will start when JobB ended and COND_B is created

    - JobC will delete COND_B and create COND_C (for JobA to run)


    Article Number:

    000119146


    Article Type:

    FAQ/Procedural



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles