What is the Cyclic job behavior during the DST time change for a job submitted via Control-M/Server version 8.0.00?

Version 12
    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 version 8.0.00 and higher



    PROBLEM:

     

    In Control-M/Server v8 there is a new IPC trigger that was added which prints any conflicts that have arisen because of DST changes. The alert that is generated by this new feature cannot be turned off.

      

    "Encountered error while handling some of the job times, probably as a result of DST change")

      

    This alert is sent only on the day of the DST change, when the Control-M/Server detects a problem with calculating the next run of a job due to the DST change.

      

    For example, the alert is sent if a job will miss some execution cycles due to the DST time change.

      

    If the message is generated on days other than the DST day the cause can be due to a value of "24:00" in one of the time fields of the job instead of "00:00".

     


    SOLUTION:

     

    As a result of a DST change, the behavior in version 8.0.00 is as follows: 

    a.       Specific time job with hours within the DST won’t run at those specific times.   
    For example DST is at 02:00 => 03:00, if job specific times are 01:30, 02:30, 03:15. The job will not run at 02:30 (even if the tolerance is big enough like 60 minutes). The job will run at 01:30 and then at 03:15. 
    If the clock moves backwards (02:00=>01:00), we will not run the same specific time twice. We will run at 01:30 only once. 
    b.      In case of a job with from and until time, if the time window is within the DST the job will not run at this time.  
    For example DST is at 02:00 => 03:00, if from time = 02:20 and until time is 02:40, job will not run at all at this day.  
    Another example, if from time = 02:20 and until time = 03:30, job will run from 03:00 to 03:30. 
    If the clock moves backwards (03:00=>02:00), we will run twice in the same hour (once at 02:30 winter time and once at 02:30 summer time). 
    c.       In case of from target interval with from time within the DST, the start point for this job will be current time after DST change. 
    For example DST is at 02:00 => 03:00, the job is from target interval with from time = 02:30 and interval of one hour. The job will run at 03:00, 04:00, 05:00 etc’. 
    d.       In case of cyclic job with interval (sequence, from start, from end) the job will run each interval.  
    For example DST is at 02:00 => 03:00, job is with from start interval of 20 minutes. Job will run at: 01:30, 01:50, 03:10, 03:20… 
    If the clock moves backwards for Winter DST (03:00=>02:00), the job will not run twice in the same hour. The Job will run at: 02:30, 02:50, (it will not run during the second occurrence of the hour when the clock is moved back from 3:00 to 2:00), then at 03:10. 
    e.       In any event we are identifying that one or more jobs should run in an hour within the DST, we will alert the user.  If the user wants to check the list of jobs for which the scheduling may be affected as a result of DST change, the following command may be used: 

    ctmipc –dest CE –msgid ctl –data “InvalidTimes print” 

    Please see the attachment for an example of the output. 

     


    Article Number:

    000106264


    Article Type:

    Solutions to a Product Problem



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