IV53978: RAS1 LOG TIMES WHEN DISPLAYED IN THE UTC+9:00 OSAKA, SAPPONO, TOKYO TIME ZONE ARE OFF BY 1 HOUR.

IBM Tivoli Monitoring 6.3.0 Fix Pack 4 (6.3.0-TIV-ITM-FP0004)

APAR status

• Closed as program error.

Error description

• Environment:
  Any Windows machine that uses time zone UTC+9:00 Osaka,
  Sappono, Tokyo
  
  
  
  Problem Description:
    The time shown in the Select Log File dialog box of
  Kinconfg.exe shows the time as GMT+8:00. The correct time is
  GMT+9:00. The time shown in the detail of KinLogs.exe also show
  the incorrect time as GMT+8:00.
  
  
  
  Recreate Instructions:
    1. Set the time zone on any Windows machine to UTC+9:00 Osaka,
  Sappono, Tokyo.
    2. Install the Log File Agent 6.2.3 or the NT agent 6.2.3 FP3.
    3. Start the agents and notice the time started.
    4. From Kinconfg.exe (Manage Tivoli Enterprise Monitoring
  Services) select either agent and right click. Select Advanced
  then View Trace Log. A Select Log File box appears. Notice that
  the time shown is GMT+8:00. The time zone is UTC+9:00 so the
  time shown should be GMT+9:00.
    5. Proceed to select a log and Kinlogs.exe will be launched.
  In the logviewing area the time stamps are all displayed as
  GMT+8:00 not GMT+9:00. The time shown as Start Time for the
  agent is correct.
  

Local fix

• N/A
  

Problem summary

• Time displayed by Manage Tivoli Enterprise Services in the
  Select Log File dialog box and KinLogs for the detail log file
  records is incorrect for GMT+09:00 Osaka, Sapporo, and Tokyo
  timezone.  The time displayed for GMT+09:00 was off by 1 hour.
  During evaluation the time was also incorrect for GMT+08:00
  Beijing, Chongging, Hong Kong, Urumgi.  It was also off by 1
  hour.
  

Problem conclusion

• Changed code to use CTime API on Windows.  The format of the
  selection time displayed by Manage Tivoli Enterprise Services
  changes a little, but it still has the basic time, timezone and
  log file name.  Detail log times displayed by KinLogs no longer
  has the day of the week spelled out.  It only has the date and
  time stamp like other logs.
  
  
  The fix for this APAR is contained in the following maintenance
  packages:
  | fix pack | 6.3.0-TIV-ITM-FP0004
  

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

  OMEG DIST INSTA

• Fixed component ID

  5608A41CI

Applicable component levels

• R630 PSY

     UP