IT34726: INSTRUMENTATION LOG FILE IS NOT PRUNED AFTER REACHING INSTRLOGMAX

APAR status

• Closed as program error.

Error description

• On backup-archive client the dsminstr.log file that reached the
  limit specified by instrlogmax cannot be pruned if the CAD
  or scheduler service is running. The messages reported in a
  client service trace misleadingly show
  that the file has been renamed to dsminstr.log.bak:
  10/16/2020 19:42:32.146 [004536] [4692] :
  ..\..\common\ut\instr.cpp( 864): openFileAppendMode ENTRY:
  filename='C:\Program Files\Tivoli\TSM\baclient\dsminstr.log'.
  10/16/2020 19:42:32.146 [004536] [4692] :
  ..\..\common\ut\instr.cpp( 895): openFileInAppendMode EXIT with
  rc=0.
  10/16/2020 19:42:32.147 [004536] [4692] :
  ..\..\common\ut\instr.cpp( 644): instrStop: The current full
  report file was renamed from C:\Program
  Files\Tivoli\TSM\baclient\dsminstr.log to C:\Program
  Files\Tivoli\TSM\baclient\dsminstr.log.bak.
  10/16/2020 19:42:32.147 [004536] [4692] :
  ..\..\common\ut\instr.cpp( 864): openFileAppendMode ENTRY:
  filename='C:\Program Files\Tivoli\TSM\baclient\dsminstr.log'.
  
  However, when looking at the instrumentation log path,
  dsminstr.log.bak is not found and the original dsminstr.log
  still exists with the same size that exceeds the instrlogmax
  
  IBM Spectrum Protect versions affected:
  All 7.1 and 8.1 Windows backup-archive clients
  
  Initial Impact:
  Medium
  

Local fix

• Prune the file manually when needed
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Backup-archive clients versions 7.1.8 and 8.1.x for Windows  *
  * platform                                                     *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See "Error Description"                                      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available. This problem is currently *
  * projected to be fixed in level 8.1.12.                       *
  * Note that this is subject to change at the discretion of     *
  * IBM.                                                         *
  ****************************************************************
  *
  

Problem conclusion

• The backup client instrumentation log file could be not renamed
  to dsminstr.log.bak
  when reaching the limit of instrumentation file when scheduler
  run under CAD.
  The additional trace messages are added when renaming is not
  possible.
  

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

• DSMC
  

Fix information

• Fixed component name

  TSM CLIENT

• Fixed component ID

  5698ISMCL

Applicable component levels