IT15607: FFDC MESSAGES/ENTRIES CONCERNING NON ERROR SITUATIONS ARE TAGGED AS ERROR WHEN NO ACTUAL ERROR HAS OR WILL OCCUR.

7.1.7.000-TIV-TSMSRV-SolarisSPARC
7.1.7.000-TIV-TSMSRV-Linuxs390x
7.1.7.000-TIV-TSMSRV-Linuxppc64
7.1.7.000-TIV-TSMSRV-WIN
7.1.7.000-TIV-TSMSRV-Linuxx86_64
7.1.7.000-TIV-TSMSRV-HP-UX
7.1.7.000-TIV-TSMSRV-AIX
IBM Spectrum Protect Server V7.1 Fix Pack 7 (7.1.7.000) Downloads

APAR status

• Closed as program error.

Error description

• With IBM Spectrum Protect 7.1.3 the dsmffdc.log was added to
  have messages and information logged into it which may or may
  not lead to a subsequent hard failure/error. The purpose of
  logging this type of information was to improve first failure
  data capture (ffdc) by logging lower level root situations that
  may or may not lead to and actual processing errors or failures.
  APAR IT04997 added the following to message as the fix needed to
  determine when the startup performance issue discussed in that
  APAR was occurring:
   [ FFDC_GENERAL_SERVER_ERROR ]: (dsalloc.c:574) Building
   freelist for volid 32
   [ FFDC_GENERAL_SERVER_ERROR ]: (dsalloc.c:869) Built freelist
   for volid 32 from 0 database rows.
  The tagging of these entries in the dsmffdc.log is somewhat
  misleading as no actual error has occurred. These messages are
  informational to confirm or understand if the performance
  situation documented in IT04997 is occurring. Rather than being
  tagged as "ERROR" messages, these should be tagged as
  informational or warning. Additionally, a diag or logging level
  should be available as a server option to toggle the info or
  warning message level  written to the dsmffdc.log. This APAR is
  being opened to address the need to tag informational or warning
  messages as such and to allow for an option that a server Admin
  can use to set the diag or logging level such that these non
  ERROR messages are not written to the dsmffdc.log.
  
  Tivoli Storage Manager Versions Affected: TSM/IBM Spectrum
  Protect 7.1.3 and above.
  
  Initial Impace: Low
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Tivoli Storage Manager server users.                     *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See error description.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available. This problem is currently *
  * projected to be fixed in level 7.1.7.  Note that this is     *
  * subject to change at the discretion of IBM.                  *
  ****************************************************************
  

Problem conclusion

• This problem was fixed.
  
  The first failure data capture (FFDC) message category
  FFDC_GENERAL_SERVER_ERROR has been divided into three separate
  cagetories:  FFDC_GENERAL_SERVER_INFO,
  FFDC_GENERAL_SERVER_WARNING, and FFDC_GENERAL_SERVER_ERROR.  The
  server will now write messages to the FFDC log with each of
  these categories to allow administrators to more easily identify
  which messages are of concern, and which can be safely ignored.
  
  
  A new server option, FFDCLOGLEVEL, has been added.
  
  The FFDCLOGLevel option specifies the type of general server
  messages that are to be written to the first failure data
  capture (FFDC) log.
  
  Note that the FFDCLOGLEVEL option only affects general server
  message -- that is messages in the FFDC_GENERAL_SERVER_INFO,
  FFDC_GENERAL_SERVER_WARNING, or FFDC_GENERAL_SERVER_ERROR
  categories.  Messages written with other categories such as
  FFDC_MSG_FROM_NDMP_DEVICE, FFDC_REPLICATION and
  FFDC_PROTECTSTGPOOL are not affected.
  
  Refer to the first failure data capture technote for more
  information on using the FFDCLOGLEVEL option.
  http://www.ibm.com/support/docview.wss?uid=swg21639703
  
  Affected platforms:  AIX, HP-UX, 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

• R71A PSY

     UP

• R71H PSY

     UP

• R71L PSY

     UP

• R71S PSY

     UP

• R71W PSY

     UP