IC67093: SELECT OUTPUT NOT IN CHRONOLOGICAL ORDER

APAR status

• Closed as program error.

Error description

• Select command on date and time column is no longer in
  chronological order.
  
  Customer/L2 Diagnostics
  Command example:
  dsmadmc -id=admin -password=admin -noconfirm -dataonly=yes
  -displ=tab "select 'ROW', cast(date_time as time) start,' ',
  message,'#SESSID#' || cast(sessid as char(10)) from actlog where
  date_time \> timestamp(cast(current_date-1 days as varchar(10)),
  ' 01:00' ) and date_time < timestamp(cast(current_date-1 days as
  varchar(10)), ' 05:00')"
  
  The example output:
  ...
  ROW            04:56:38                     ANR0136I Table
  updating statistics performed successfully for 6 of 6.
  ROW            01:25:39                     ANR2017I
  Administrator MONITOR_AGENT issued command: select
  SCHEDULE_NAME, NODE_NAME, SCHEDULED_START, ACTUAL_START, STATUS,
  RESULT, REASON, DOMAIN_NAME, 'SERVER' from EVENTS where
  NODE_NAME IS NULL (SESSION: 2877)
  ...
  
  The 1:25:39 for this select should be listed before 4:56:38.
  
  Adding the SQL ORDER BY clause does not correct the
  chronological order down to the 100th seconds, so messages are
  still not in the correct chronological order.
  
  Initial Impact: Low
  Additional Keywords: TSM zz61
  

Local fix

• Apply the fixing level once available and then it will also be
  necessary to use 'ORDER BY DATE_TIME, UNIQUE' in the select.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Tivoli Storage Manager server users      *
  *                 of the SELECT command from Actlog table.     *
  ****************************************************************
  * PROBLEM DESCRIPTION: See ERROR DESCRIPTION.                  *
  ****************************************************************
  * RECOMMENDATION: Apply fixing level when available.           *
  *                 This problem is currently projected          *
  *                 to be fixed in level 6.1.4 and 6.2.2.        *
  *                 Note that this is subject                    *
  *                 to change at the discretion of IBM.          *
  ****************************************************************
  *
  

Problem conclusion

• This problem was fixed.
  Affected platforms:  AIX, HP-UX, Sun Solaris, Linux,
  and Windows.
  

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

  TSM SERVER

• Fixed component ID

  5698ISMSV

Applicable component levels

• R61A PSY

     UP

• R61H PSY

     UP

• R61L PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R62A PSY

     UP

• R62H PSY

     UP

• R62L PSY

     UP

• R62S PSY

     UP

• R62W PSY

     UP