HE11447: Weekly scheduled tasks in IBM Content Collector 2.2 do not start at the expected day and time

IBM Content Collector V3.0
IBM Content Collector V2.2 Fix Pack 3

APAR status

• Closed as fixed if next.

Error description

• Weekly scheduled tasks do not start if the local start time is
  converted to UTC time after midnight.
  
  For example, if a job is configured to start on Mondays at
  9 p.m. EST (UTC-5), the UTC time is 2 a.m., thus after midnight,
  and the job does not start. If the job is configured to start
  at 6 p.m. EST, the UTC time is 11 p.m., thus before midnight,
  and the job starts as scheduled.
  

Local fix

• Tasks can be scheduled to run at an earlier time in the day,
  but this is not viable for long term use as it impacts other
  business processes for client.
  

Problem summary

• If IBM Content Collector tasks were configured to run once per
  week and the scheduled start time in local time corresponded to
  a UTC time after midnight, the tasks did not start.
  
  Starting with this fix, scheduled tasks in IBM Content
  Collector 3.0 start at the expected day and time.
  

Problem conclusion

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

Applicable component levels

• R300 PSY

     UP