IC59770: SESSION NUMBERS MISSING FROM END OF TSM SERVER MESSAGE TAG AREA.

IBM Tivoli Storage Manager V6.1 Fix Pack 2 (6.1.2) Server Downloads

APAR status

• Closed as program error.

Error description

• TSM messages associated with a session should include the
  session number at the end in the message tag area. In certain
  cases a timing problem can occur between the start of the
  session and the thread for that session such that the session
  number does not get associated with the thread for output
  in the message tag area. In these cases any messages
  associated with the session, including the session start
  and stop messages will not include this session reference
  in the tag area. For example in the messages below the
  tag, (SESSION: 141) is missing from the end of each message.
  01/22/2009 06:13:05  ANR0407I Session 141 started for
  administrator ADMIN1 (AIX)(Tcp/Ip 192.168.1.1(34532)).
                        (Tcp/Ip 192.168.1.1(34532)).
  01/22/2009 06:13:05  ANR2017I Administrator ADMIN1 issued
  command: QUERY MOUNT
  01/22/2009 06:13:05  ANR8333I FILE volume
  /tsml2_doc/dir1/00000011.BFS is
                        mounted R/O, status: IN USE.
  01/22/2009 06:13:05  ANR8333I FILE volume
                        mounted R/O, status: IN USE.
  01/22/2009 06:13:05  ANR8334I   2 matches found.
  01/22/2009 06:13:05  ANR0405I Session 141 ended for
  administrator ADMIN1 (AIX).
  TSM Versions Affected: 5.4 and 5.5
  L2 Diagnostics: The following SQL statement will list
  message numbers where session tags may be
  expected but not found:
  SELECT distinct MSGNO FROM actlog WHERE MSGNO
  in (SELECT distinct MSGNO FROM actlog WHERE MESSAGE
  like '%SESSION%') and MESSAGE not like '%SESSION%'
  order by 1
  Initial Impact: Low
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of TSM Server.                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: See ERROR DESCRIPTION.                  *
  ****************************************************************
  * RECOMMENDATION: Apply fixing level when available.           *
  *                 This problem is currently projected          *
  *                 to be fixed in level 5.4.6, 5.5.3            *
  *                 and 6.1.2. Note that this is subject         *
  *                 to change at the discretion of IBM.          *
  ****************************************************************
  *
  

Problem conclusion

• The TSM server has been corrected.
  

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

• R54A PSY

     UP

• R54H PSY

     UP

• R54L PSY

     UP

• R54S PSY

     UP

• R54W PSY

     UP

• R55A PSY

     UP

• R55H PSY

     UP

• R55L PSY

     UP

• R55S PSY

     UP

• R55W PSY

     UP