IV80147: ERROR MESSAGE BMXAA0277E DISPLAYS DATE TIME STAMPS IN THE WRONG TIMEZONE AND WRONG DATE TIME FORMAT

APAR status

• Closed as program error.

Error description

• PROBLEM:
  The issue is that a time stamp displayed in an error message is
  not in the same format as what the user time setting is AND not
  in the same timezone as the users.  This leads to confusion for
  the user trying to understand what they need to correct the
  time value to.  Instead it uses the system timezone instead of
  the user's timezone; and the default displaytime format instead
  of the system property's configured displaytime.
  
  Our customer writes:
  When resolving an Incident, we are not able to backdate the
  Status Date when changing the Status to Resolved.
  It looks like the system is checking with a GMT time instead of
  the local time.
  
  Image of error saying:
  You entered: 7/31/14 18:20:00
  This status change cannot occur before the date of the last
  status change of 7/31/14 10:21 PM. (BMXAA0277E)
  
  The actual time was 7/31/14 18:27:00  (6:27 PM) and I was
  trying a backdate of 7 minutes.  The system is checking with a
  GMT timestamp of 7/31/14 22:21 (10:21 PM) and it refuses the
  modification.  My profile locale was en_US.
  
  
  PERFORMANCE ISSUE:  no
  
  
  STEPS TO REPRODUCE:
  1)  Prep.  The issue is easier to see if your user account's
  timezone is set to be different than the system's timezone.
  Also, it helps to change the time display format to see that
  aspect.  To do so, do these steps:
  1.1) Add or change the System Property called
  setting.DISPLAYTIME and set the value to   "HH:mm:ss"   save
  and do a Live Refresh.
  1.2) Enter the user profile for your user and set the timezone
  to one that is different than the server's.  Save.
  1.3)  Just to be sure, log out and back in.
  2) Create an Incident record or a WO record.
  3) Click change status to get the Change Status dialog to open.
  In Incident choose a status.  If in WO, you already choose a
  status to get the dialog opened.
  4) In the dialog edit the year to be one year earlier.  Really
  any time earlier than the previous status change will work.
  Then click OK.
  
  Here is where Incident/SR/Problem differ from WO.
  
  Incident:
  5) Now you get an error message.  This message is not our
  focus, so hit the OK button.
  6) Notice in the change status dialog there is now a red X on
  the date time entry field.  Click on the X.
  7) Now you get an error message with both the date time of what
  you entered (in your timezone and using system format as per
  DISPLAYTIME) and the date time of the last status change (in the
  system's timezone and using a default format).
  
  WorkOrder:
  5) Now you get an error showing the last status change's date
  time of the last status change (in the system's timezone and
  using the default format).  Instead it should be using the
  user's timezone and the system format.
  
  
  CURRENT ERRONEOUS RESULT:
  Error dialogs display date/time in the wrong timezone and wrong
  format
  
  EXPECTED RESULT:
  Error dialogs display date/time with the user profile's chosen
  timezone and chosen system property time format
  
  ADDITIONAL INFO:
  This is not about preventing getting the errors.
  
  ENVIRONMENT:
  - SCCD:  7502
  - TPAE:  7504
  - Base Language:  English
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Maximo Users                                             *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Error message BMXAA0277E displays date time stamps in the    *
  * wrong timezone and wrong date time format.                   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to latest release                                    *
  ****************************************************************
  PROBLEM:
  The issue is that a time stamp displayed in an error message is
  not in the same format as what the user time setting is AND not
  in the same timezone as the users.  This leads to confusion for
  the user trying to understand what they need to correct the time
  value to.  Instead it uses the system timezone instead of the
  user's timezone; and the default displaytime format instead of
  the system property's configured displaytime.
  
  Our customer writes:
  When resolving an Incident, we are not able to backdate the
  Status Date when changing the Status to Resolved. It looks like
  the system is checking with a GMT time instead of the local
  time.
  
  Image of error saying:
  You entered: 7/31/14 18:20:00
  This status change cannot occur before the date of the last
  status change of 7/31/14 10:21 PM. (BMXAA0277E)
  
  The actual time was 7/31/14 18:27:00  (6:27 PM) and I was trying
  a backdate of 7 minutes.  The system is checking with a GMT
  timestamp of 7/31/14 22:21 (10:21 PM) and it refuses the
  modification.  My profile locale was en_US.
  
  STEPS TO REPRODUCE:
  1)  Prep.  The issue is easier to see if your user account's
  timezone is set to be different than the system's timezone.
  Also, it helps to change the time display format to see that
  aspect.  To do so, do these steps:
  1.1) Add or change the System Property called
  setting.DISPLAYTIME and set the value to "HH:mm:ss" save and do
  a Live Refresh.
  1.2) Enter the user profile for your user and set the timezone
  to one that is different than the server's.  Save.
  1.3)  Just to be sure, log out and back in.
  2) Create an Incident record or a WO record.
  3) Click change status to get the Change Status dialog to open.
  In Incident choose a status.  If in WO, you already choose a
  status to get the dialog opened.
  4) In the dialog edit the year to be one year earlier.  Really
  any time earlier than the previous status change will work. Then
  click OK.
  
  Here is where Incident/SR/Problem differ from WO.
  
  Incident:
  5) Now you get an error message.  This message is not our focus,
  so hit the OK button.
  6) Notice in the change status dialog there is now a red X on
  the date time entry field.  Click on the X.
  7) Now you get an error message with both the date time of what
  you entered (in your timezone and using system format as per
  DISPLAYTIME) and the date time of the last status change (in the
  system's timezone and using a default format).
  
  WorkOrder:
  5) Now you get an error showing the last status change's date
  time of the last status change (in the system's timezone and
  using the default format).  Instead it should be using the
  user's timezone and the system format.
  
  CURRENT ERRONEOUS RESULT:
  Error dialogs display date/time in the wrong timezone and wrong
  format
  
  EXPECTED RESULT:
  Error dialogs display date/time with the user profile's chosen
  timezone and chosen system property time format
  

Problem conclusion

• Error message BMXAA0277E displays date time stamps in the
  correct timezone and correct date time format.
  
  The fix for this APAR is contained in the following maintenance
  package:
  	 | release\fix pack | Fix Pack Release 7.5.0.10 TPAE
  

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:

Modules/Macros

• MAXIMO
  

Fix information

• Fixed component name

  ADMINISTRATION

• Fixed component ID

  5724R46A1

Applicable component levels

• R750 PSY

     UP