APAR status
Closed as program error.
Error description
PROBLEM: Daylight Saving issue the system timezone is different from user's timezone where work is to be performed PERFORMANCE ISSUE: N STEPS TO REPRODUCE: 1. Change the system's timezone to (UTC+10:00) Canberra, Melbourne, Sydney Control Panel - Date and Time - Change Timezone This is in Daylight savings time until April. 2. In Maximo, login as maxadmin/maxadmin, from Default Information, change timezone to Australia/NSW (GMT +10 DST/Y) 3. Go to the Organizations application, bring up organization EAGLENA and go to the Sites tab Click the "associate Time Zone" icon besides site BEDFORD specify "Australia/Brisbane" (GMT +10 DST/N) as the timezone for the site. Note the only difference between this timezone and the system/maxadmin user's timezone is one is DST/Y and one is DST/N. 4.Go to the Time Zone Rules application. (Note: this is saying when generating workorder from PM, use the ASSET.SITE's timezone first if ) found). Add 2 time zone rules: 1). Process = PMWOGEN Process Rule = LOCATIONS,LOCATIONS.SITE 2). Process = PMWOGEN Process Rule = ASSET.SITE Organization = EAGLENA Site = BEDFORD site Save the record 5. Go to the PM application. (Bring up an existing PM or this) create a new PM go to the frequency tab, set the "Target Start time" to 7:00 AM Change the PM status to ACTIVE 6. Generate Work Order action, uncheck "Use Frequency Criteria", OK. Note the work order number generated. 7. Go to Work Order Tracking app, bring up the newly generated workorder. Target Start Date should be 8am. Because work is scheduled to be at 7am at the asset.site (BEDFORD) timezone(GMT+10 DST/N), and maxadmin user is at (GMT+10 DST/Y) But Target Start shows 3/15/18 7:00 AM 8. Change maxadmin's timezone to "Australia/Brisbane" (GMT +10 DST/N), log out and log back in now should see 7am for Target Start Date for the work order. but Target Start shows 3/15/18 6:00 AM CURRENT ERRONEOUS RESULT: Target Start is incorrect EXPECTED RESULT: Target start should be correct ADDITIONAL INFO: Daylight saving issue ENVIRONMENT (SYSTEM INFO): TPAE 7.6.0.8 IFIX 5 LOCAL FIX: N/A SECURITY IMPACT (Y/N): N
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: * * Users with a timezone rule. * **************************************************************** * PROBLEM DESCRIPTION: * * When Maximo performs a timezone conversion from a timezone * * with DST to a timezone without DST, and both timezones share * * the same UTC offset, the conversion is not performed * * correctly. In addition, Maximo does not perform the correct * * conversion when moving from a timezone with a positive, UTC * * offset to a timezone with a smaller, positive, UTC offset. * **************************************************************** * 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 number
IJ05211
Reported component name
WORK ORDERS
Reported component ID
5724R46WO
Reported release
760
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-03-25
Closed date
2018-05-01
Last modified date
2018-05-01
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
WORK ORDERS
Fixed component ID
5724R46WO
Applicable component levels
R760 PSY
UP
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCHPPU","label":"Work Order Tracking"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"760","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
01 May 2018