Why do I get this error "Encountered error while handling some of the job times, probably as a result of DST change" in Control-M/Server during DST change?

Version 1
    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 V8 and above



    QUESTION:

    Question:
    -
    Why do I get the following error during DST change?
      Error:
      Encountered error while handling some of the job times, probably as a result of DST change. These jobs should be manually adjusted.
      To view the list of jobs please use the following command line: ctmipc -dest CE -msgid CTL -data 'InvalidTimes print'


     


    ANSWER:

     

    Answer:
    - The message indicated that Control-M has detected some jobs could have a not correct timing set inside job definition and will not fit after DST change.
    - Recommendation: Refer to the following article to update the affected files before DST change:
       000028594: Which files need to be updated on Control-M when the TimeZone information changes?

    Additional Information:
    - In the alert is provided a command to get the list of detected jobs: ctmipc -dest CE -msgid CTL -data 'InvalidTimes print'
      Error:
      Encountered error while handling some of the job times, probably as a result of DST change. These jobs should be manually adjusted.
      To view the list of jobs please use the following command line: ctmipc -dest CE -msgid CTL -data 'InvalidTimes print'

    - How to use this command, ctmipc –dest CE –msgid ctl –data “InvalidTimes print”?
      To allow the user to check and produce the list of jobs for which the scheduling may be affected as a result of DST change.

    - Usage for "
    ctmipc -dest CE -msgid CTL -data 'InvalidTimes print':
      ctmipc -dest CE -msgid CTL -data 'InvalidTimes print'
      message 'CTL' sent to CE successfully
      InvalidTimes:
      Job Invalid times
      Job dinsql12SQL2012DailyBackup (1803455/12njz) 0200
      Job taltsql01SQL2008DailyBackup (1803437/12njh) 0230
      Job FI_BW_CO_DAILY (1803379/12nhv) 0230
      Job dvdisqlclSQL2012DailyBackup (1803498/12nl6) 0225


    - What to do with the output of this command,
    ctmipc -dest CE -msgid CTL -data 'InvalidTimes print'?
      The listed jobs are jobs that might be affected by the DST change and it is recommended to verify them.
      If no jobs are listed after running the command,  it means there is no questionable job.


    - If the error message continues to appear every New Day with no jobs listed by the ctmipc command, check the CE logs for a line that shows that error message and includes a specific job name like the following example:
    1005_08:05:37.954, "_D<< insert into CMR_DBLOG (KEYSTMP,DBULVL,DBMESSAGE,MSGSIZE,DBMESSAGE_1_32) VALUES(?,?,?,?,?); [1=147567273795499999996h, 2=0, 3=U80537007200000101MWSWSUSERIDT RT2016100508053700000001U                                                                00000                161005080537                           000000000000249Encountered error while handling some of the job times, probably as a result of DST change. These jobs should be manually adjusted. To view the list of jobs please use the following command line: ctmipc -dest CE -msgid CTL -data 'InvalidTimes print'0000, 4=448, 5=UT]", [CONFIG], T@40385, T:ctm.Selector.IO.40385, "SL Job BIM03377A01 (9607021/5pwtp)", DB, CtmDBPreparedStatement::logit, , 
        * In the above example, "BIM03377A01" is the job name.
        * If that job is defined with a time field set to midnight, you may also find in the CE logs a warning associated with that job name like the following:
    Invalid times are:2400", [WARNING], T@40385, T:ctm.Selector.IO.40385, "SL Job BIM03377A01 (9607021/5pwtp)", com.bmc.ctms.selector.InvalidTimes, InvalidTimes::add, , 
        * If you see the above warning in the CE logs, find that job and if there is any time field in its definition set to "2400", change it to "0000".
        * If that does not stop the error message from appearing every day, change any time field set to "0000" to "2359".

     


    Article Number:

    000105679


    Article Type:

    FAQ/Procedural



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