IJ00499: NEXT RUN TIME DISPLAYED INCORRECTLY FOR SCHEDULED RECURRING REPORTS

APAR status

• Closed as program error.

Error description

• We noticed that the next run time for scheduled recurring
  reports is displaying incorrectly on the screen. The actual
  emails with the reports are however being sent on the correct
  date and time, so this seems to be a display issue only.
  Maximo scheduled reports in WOTRACK:
  The times are exactly the times that the reports should run. The
  runtime is also very short. So this is OK.
  The problem is the graphical visualization of the schedules.
  When 1 report has run on the specified time, the next run date
  (only
  date, not the time) of all the other schedules is changed
  automatically
  to the same date.
  Example:
  A report is scheduled as Recurring runtime every 10 days
  This instance should run once in the 10 days.
  so if run on 8th September:
  8 h> 18th > 28th > 7th. This is OK.
  The next date should be 17th!
  In the screenshot it says 22th should be the next run date.
  For one or another reason the schedule shows 10 days further:
  22th.
  But this is only graphical, because the reports will come out
  on the 17th.
  STEPS TO REPLICATE:
  Replicated by L2 on TPAE 76.0.5 environment on 20th September.
  Also reproduced on TPAE 7.6.0.8
  1. Go to Maximo Application (i.e. Work Order Tracking)
  2. Go to Actions (or Select Action), and choose Run Reports.
  3. Click on the report in the list view
  i.e. Work Order List report
  4. Set as follows:
  Recurring: 1 day(s)
  Email: m.wilson@helwig.com (wilson demo user)
  Next run is expected to be in the following order:
  Date Preview (list of dates)
  20/09/17 07:00 AM
  21/10/17  07:00 AM
  22/10/17  07:00 AM
  ... and so on...
  5. Repeat steps 1 to 4 for Recurring 10 Days
  Date Preview (list of dates)
  30/09/17 08:00 AM
  10/10/17  08:00 AM
  20/10/17  08:00 AM
  ... and so on...
  6.  Select the Schedules tab to see all of the reports
  scheduled run dates.
  - Go to Work Order Tracking application
  - Select Action -> Run Reports
  - Click on Schedules tab when "Reports and Schedules" window is
  displayed
  7. Perform same steps  1 to 6 the next day or any day ahead,
  i.e. 21st September.
  8. Check the report Schedules on the 3rd day i.e. 22nd September
  At least one 10 day Recurring report will show the wrong date
  in the "Next Run Time" field.
  i.e. Instead of displaying:
   30th Sept 08:00 AM
  it will show the wrong date:
  22nd Sept  08:00 AM
  It appears to have taken the date of the other scheduled report.
  Also checked Report Administration -> View Scheduled Reports
  ENVIRONMENT:
  App Server IBM WebSphere Application Server 8.5_5.3
  Server OS Wndows 6.3
  Server DB Oracle 12.1 (Oracle Database 12c Enterprise Edition
  Release 12.1.0.2.0 - 64bit Production With the Partitioning,
  OLAP, Advanced Analytics and Real Application Testing options)
  PRODUCT VERSION:
  Tivoli's process automation engine 7.6.0.5 Build 20160611-0100
  DB Build V7605-45
  IBM TPAE Integration Framework 7.6.0.5 Build 20160610-2330 DB
  Build V7605-50
  IBM Maximo Asset Management Work Centers 7.6.0.0 Build
  20160610-1318 DB
  Build V7600-38
  IBM Maximo Asset Management 7.6.0.5 Build 20160611-0100 DB Build
  V7604-01
  

Local fix

• Dev to provide fix
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Users with scheduled reports.                                *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Recurring reports scheduled dates are generated using the    *
  * current server datetime instead of the taskschedule's last   *
  * run datetime.                                                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• The fix for this APAR is included in the following package:
                          | Release 7.6.1.0 of Base Services.
  

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

  BIRT INTEG-SYST

• Fixed component ID

  5724R46B2

Applicable component levels