How to change Control-M/Server default behavior from marking jobs as "ENDED NOTOK" after the job stayed as UNKNOWN (white) for 120 minutes?

Version 4
    Share This:

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


    PRODUCT:

    Control-M/Server for UNIX and Microsoft Windows


    COMPONENT:

    Control-M/Server for UNIX and Microsoft Windows


    APPLIES TO:

    Control-M/Server for UNIX and Microsoft Windows (all versions)



    QUESTION:

    Is there a way to change Control-M/Server default behavior from marking jobs as "ENDED NOTOK" after the job stayed as unknown (white) for 120 minutes?

    Control-M/Server will mark the job as "ENDED NOTOK" after the job stayed as unknown status (white) for 120 minutes.  This is the Control-M way to warn the customer about the problem and potential break of the work flow.

    For example:

       
        
    • Job A is executing on Agent B (yellow color in Workload Automation GUI)
    •   
    • Agent B crashed
    •   
    • Job A gets the status Unknown (white color in Workload Automation GUI)
    •   
    • After exactly two hours you will find in the job log Disappeared and the job will change to status Ended NOTOK  (red color in Workload Automation GUI)
    •  


    ANSWER:

     

    When a connection failure with Agent occurs the Server changes the jobs to Unknown and after two hours (by default) they are set to a Disappeared state and then ended as NOTOK.

      

    This is the Control-M way to warn about the problem and the potential break in work flow.

      

    The timeout is handled by the Control-M/Server parameter UNKNOWN_TIMEOUT <value in seconds>
    The default is 2 hours (120 * 60 or 7200)
    To have Control-M/Server wait forever, set this parameter in the ctm_server/data/config.dat file to 0 for "never".  Backup the file first.
    To have Control-M/Server use the default, remove UNKNOWN_TIMEOUT if it exists.
    Otherwise the value is in seconds.
    For example if set to 120, when the Agent is unavailable for more than 120 seconds, the jobs will be set to Disappeared, then NOTOK

    Control-M/Server needs to be recycled for any change to this parameter to take effect.

      

    The parameter need to be added into the config.dat file on the CONTROL-M/Server side and a recycle of Control-M/Server is needed (Please backup configuration file before making the change).

      


    Additional information:
    Decreasing this interval could have a negative impact on the NS process/thread performance, reflecting as a delay in job submission and Agent check cycle.
    On the other hand, if the timeout has been set to "never", manual action for handling the problematic jobs will be required.
    Currently it is not possible to change the status of a job that goes to an Unknown state.
    The following Request For Enhancement has been created in order to change the status of a specific job that keeps in Unknown status without waiting UNKNOWN_TIMEOUT expires:
    QM001891177: "Ability to change the status of a job that entered to an unknown state "

      

     

     


    Article Number:

    000022064


    Article Type:

    FAQ/Procedural



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