IT31434: DSMC SET EVENT -SUBDIR=YES DOESN'T SEND ALL OBJECT IDS TO BE UPDATED IN THE SERVER EVENT-BASED POLICY

APAR status

• Closed as program error.

Error description

• The IBM Spectrum Protect Client SET Event command with
  Subdir=yes looks to process all Object IDs to the server to
  activate the Event-based policy.  The server's expiration count
  down has not started for most of the objects that the client
  processed.
  
  Diagnostics:
  Get the client Query ARchive output for the same directory the
  subdir command processed.  Example:
  dsmc q ar -detail -su=yes /path/of/data
  
  This will display that most of the objects are still in:
  "RetInit:PENDING ObjHeld:NO"
  Example of output:
  Filesize date/time /path/and/object.name
  RetInit:PENDING ObjHeld:NO
  Modified: date/time Accessed: date/time Inode changed: date/time
  
  Initial Impact: Low
  IBM Spectrum Protect versions affected:
  Client versions 7.1.x and 8.1.x on all supported platforms
  Keywords:
  TSM TS002590980 Event based policy
  

Local fix

• Set the TxnGroupMax server option to 8191 or any lower value.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * IBM Spectrum Protect backup-archive client versions 7.1.x    *
  * and 8.1.x on all platforms.                                  *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See ERROR DESCRIPTION.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available. This problem is projected *
  * to be fixed in levels 7.1.8.9 and 8.1.10. Note that this is  *
  * subject to change at the discretion of IBM.                  *
  ****************************************************************
  

Problem conclusion

• If the TxnGroupMax server option setting was set to 8192 or a
  higher value, the "dsmc set event -su=yes -type=a" command could
  not start the expiration count down for all processed objects as
  it should.
  The problem has been fixed, so that the dsmc set event command
  works correctly regardless of the actual TxnGroupMax server
  option setting.
  

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