IJ48715: START AND END DATES TO MIDNIGHT BY ROLL PROJECT IN GRAPHICAL SCHEDULING APPLICATION.

APAR status

• Closed as program error.

Error description

• ERROR DESCRIPTION:
  Start and End Dates to midnight by Roll Project in Graphical
  Scheduling application.
  
  PROBLEM:
  When Roll Project Action is executed in Graphical Scheduling,
  Maximo is setting the Start and End Dates to midnight because
  that represents the start of the day.
  
  
  STEPS TO REPRODUCE:
  Open Maximo as maxadmin
  
  Ensure that the timezone for Maxadmin user is set as US pacific
  
  Log out maximo, log back in
  Go to Graphical Scheduling application
  Enter a new record as following:
  	Schedule=test
  	Calendar=DAY
  	Type=Work
  	Rolling Schedule=CHECKED
  	Rolling Frequency=1d
  	Duration in Days=15
  	Start Date= (ENSURE THE TIME IS SET TO ANY TIME OTHER THAN
  00:00, LIKE FOR EXAMPLE 12:34 PM)
  	End Date= (ENSURE THE TIME IS SET TO ANY TIME OTHER THAN 00:00,
  LIKE FOR EXAMPLE 20:34 PM)
  
  In the Work Queries section, enter any query, like this one:
  	Data Source=WORKORDER
  	Where Condition=	STATUS='APPR'
  
  Save Record
  Go to Actions > Roll Schedule > Run
  
  When the customer does this, Maximo is inputting midnight UTC in
  the database and displaying a time of 5 AM to users.
  
  CURRENT ERRONEOUS RESULT:
  Maximo is inputting midnight UTC in the database and displaying
  a time of 5 AM to users.
  
  EXPECTED RESULT:
  It is expected that the time displayed to the users should be
  midnight Pacific Time.
  
  ENVIRONMENT (SYSTEM INFO):
  Tivoli's process automation engine 7.6.1.3-IFIX20230628-1738
  Build 20220823-0909 DB Build V7613-344 HFDB Build HF7613-101
  IBM Maximo Calibration 7.6.1.0 Build 20220823-0909 DB Build
  V7600-08
  IBM Maximo Mobile 8.9.0 Build 20230411-1103 DB Build V8900-175
  HFDB Build HF8900-06
  IBM Maximo Asset Management Scheduler 7.6.8.2 Build
  20220823-0909 DB Build V7682-23 HFDB Build HF7682-09
  Maximo Application Framework 8.9.0 Build 20221104-2005 DB Build
  V7600-26
  IBM Maximo Anywhere 7.6.4.0 Build 20200117_195427-0500 DB Build
  V7640-12
  IBM Tpae Integration Framework 7.6.1.3 Build 20220823-0909 DB
  Build V7613-61
  IBM Maximo Asset Management 7.6.1.3 Build 20220823-0909 DB Build
  V7611-01
  IBM Maximo for Transportation 7.6.2.6-20230428-1520 Build
  20230428-1520 DB Build V7626-16 HFDB Build HF7626-34
  IBM Maximo for Oil and Gas 7.6.2.0-20230526-1411 Build
  20230526-1411 DB Build V7620-96 HFDB Build HF7620-16
  IoT Connection Utility 7.6.0.4 Build 20220303-1642 DB Build
  V7604-01
  TPAE OSLC Object Structure 7.6.4.0 Build 20200219_092917-0500 DB
  Build V7640-04
  

Local fix

Problem summary

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

Problem conclusion

• A fix fro 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

  SYSTEM CONFIG

• Fixed component ID

  5724R46S1

Applicable component levels