IZ88935: TIMEZONE PROBLEM IN MAXIMO INTEGRATION FRAMEWORK

APAR status

• Closed as program error.

Error description

• The problem is Timezone Problem in Maximo Integration Framework.
  In the case that current date is between the daylight saving
  start date in Oct ( first sunday) and last sunday in Oct ,
  When running inbound interface ( simply you can test with data
  import func ) with the date field value ( 2010-10-10T12:00:00.0Z
  )  date is loaded as GMT+10 even if it should be GMT+11 because
  daylight saying is started.
  
  Env : BS 7115 ( with/without HF )
  
  Steps to replicate
  1.Set DB Server / App Server TIMEZONE : AUS Eastern Daylight
  Time ( It's on GMT+10. For daylight saving , it's on GMT+11 )
  
  2.Set current date with one date between the daylight saving
  start date in Oct ( first sunday) and last sunday in Oct .
  ex.current date is 18/10/2010
  
  3.Set any inbound interface and try to import flatfile simply
    When testing , use 2010-10-10T12:00:00.0Z for one date field
  
    Imported date field's value got to be 2010-10-10 22:00:00 (
  GMT+10 applied )
  
  The expected result is that date field's value should be
  2010-10-10 23:00:00 ( GMT+11 should be applied )
  
  P.S : I tested this problem in BS7115 with/without HF and could
  replicate this problem.
  But, In BS7117 HF , I couldnot replicate that problem. it seems
  fixed .
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: any user using the MIF to import xml data    *
  ****************************************************************
  * PROBLEM DESCRIPTION: loosing an hour while doing the date    *
  *                      conversion in aus timezone when         *
  *                      daylight savings is on                  *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  *                                                              *
  *                                                              *
  *                                                              *
  ****************************************************************
  loosing an hour while doing the date conversion in aus timezone
  when daylight savings is on
  

Problem conclusion

• there are only 2 things to resolve here - is it a jdk bug or is
  it a MIF code bug. The test results from client show that its
  bug in neither. Tests from L2 showed there is a bug in sun jdk
  but customer is using IBM jdk. So at this point this issue
  cannot be reproduced and hence we are closing it until further
  notice from customer.
  
  
  
  
  
  The fix for this APAR is contained in the following maintenance
  package:
  
    | release\fix pack | THRASHER
  

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

  MAXIMO INTEGRAT

• Fixed component ID

  5724R46I1

Applicable component levels

• R711 PSY

     UP