IJ50876: THE SCHEDULING ROLLING RESULTING DATE IS NOT CALCULATING CORRECTLY WHEN FUNCTIONALITY RECURRING AND OFFSET IS USED

APAR status

• Closed as program error.

Error description

• The scheduling rolling resulting date is not calculating
  correctly when functionality Recurring is used with an Offset
  This issue occurs on top of the issue tracked in APAR:IJ49089
  This also works if the Offset is a negative value, however, a
  positive value Offset produced incorrect results
  
  
  Steps to replicate:
  
  User s Default time zone - Canada/Pacific (UTC-8)
  Current System Date- November 14th 3:45 pm
  1. Create a new scheduler record, add a name for the record, add
  
  a calendar and a shift
  Set the start date to 3/7/2024 03:45 pm, End date of 4/17/24
  3:45 PM and place a checkmark in the Rolling Schedule checkbox
  and Save.
  
  2. From the common actions menu open the Roll Scheduler dialogue
  window. The duration in days will default to 41
  On Roll Schedule dialog, set the rolling offset to 5 days.
  Click on the magnifying glass of field Roll Date Schedule
  Roll Schedule   Every 1 week(s), on day Wednesday at 10:50 AM
  (current system date/time is 3rd April 10:48 AM)
  Click on the Preview button and note the Next Scheduled Start
  Dates, specifically the first entry
  Click on the magnifying glass for field Recurring, the same will
  be copied over to the Recurring schedule
  
  Then click on the Preview button and note the Next Scheduled
  Start Dates, specifically the first entry
  NOTE: the entries on the Preview for the Roll Date Schedule and
  Preview for the REcurring are NOT the same, this is due to the
  Offset value
  Save the schedule and wait for the cron to run.
  The cron ran
  
  RESULTS
  Currently Start Date populated is on 15th  April 3:45 pm which
  appears to be the following formula: sys date + roll offset +
  rolling frequency
  
  EXPECTED RESULTS
  Expected Date : 10th April 3:45 PM
  Expected Calculation: Schedule Start Date   Current Sys Date +
  Roll Offset
  .
  Reported Version
  
  Tivoli's process automation engine 7.6.1.3
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Scheduler users                                              *
  ****************************************************************
  

Problem conclusion

• A fix for this APAR will be included in a future release.
  

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

  MAXIMO SCHEDULE

• Fixed component ID

  5724R46SE

Applicable component levels