IJ12595: TASKSCHEDULER LASTRUN AND LASTEND VALUES ARE IN LOCAL TIMEZONE CAUSING THE CRONTASK TO STOP AFTER DAYLIGHT SAVING TIME

APAR status

• Closed as program error.

Error description

• ERROR DESCRIPTION:
  TASKSCHEDULER.LASTRUN and TASKSCHEDULER.LASTEND values are
  written in the local timezone causing the crontask to stop
  after daylight savings time.
  PROBLEM:
  Having issues with critical business processes not triggering
  due to daylight savings time changes preventing cron tasks from
  scheduling properly.
  The issue is that the TASKSCHEDULER.LASTRUN and
  TASKSCHEDULER.LASTEND values are written in the local timezone
  so if a cron task starts at 01:59 AM (MDT) and ends at 01:01 AM
  (MST) then the cron will never run again as LASTEND < LASTRUN.
  We have resolved this issue by clearing out the TASKSCHEDULER
  table and reloading affecting cron task instances, but this
  shouldn't be required. The very simple solution to this is that
  the dates in this table should be written in UTC which would
  prevent these issues.
  The work around is to clear the TASKSCHEDULER table.
  PERFORMANCE ISSUE: No.
  STEPS TO REPRODUCE:
  The issue is that the TASKSCHEDULER.LASTRUN and
  TASKSCHEDULER.LASTEND values are written in the local timezone
  so if a cron task starts at 01:59 AM (MDT) and ends at 01:01 AM
  (MST) then the cron will never run again as LASTEND < LASTRUN.
  CURRENT ERRONEOUS RESULT:
  Cron will never run again as LASTEND < LASTRUN.
  EXPECTED RESULT:
  LASTEND should not be lower than LASTRUN.
  ENVIRONMENT (SYSTEM INFO):
  Tivoli's process automation engine 7.6.0.9-IFIX20180314-1711
  Build 20171127-0100 DB Build V7609-45 HFDB Build HF7609-03
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * MAXIMO                                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * TASKSCHEDULER LASTRUN AND LASTEND VALUES ARE IN LOCAL        *
  * TIMEZONE CAUSING THE CRONTASK TO STOP AFTER DAYLIGHT SAVING  *
  * TIME                                                         *
  ****************************************************************
  

Problem conclusion

• The fix for this APAR is contained in the following maintenance
  package: release\fix pack for Release 7.6.1.3 Product
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  SYSTEM CONFIG

• Fixed component ID

  5724R46S1

Applicable component levels