IC82565: CANCELLATION OF EXPIRATION PROCESS MIGHT TAKE LONGER THAN EXPECTED

APAR status

• Closed as program error.

Error description

• Under certain conditions, the cancellation of an expiration
  process might take longer than expected. This will typically
  occur when system state grouped objects are being processed.
  The system state group(s) are nested such that they have to be
  analyzed/deleted under one transaction. Depending on the size of
  the group and how they were stored this can take some time to
  complete. The expiration cancel recognition is currently limited
  in that it will be checked once the entire group has been
  processed.
  L2 DIAGNOSTICS:
  The following thread callstack is a good indicator that the
  expiration process is processing a group in which case the
  cancel recognition will be delayed. The key function will be
  ImDeleteDependents:
  .
   Thread 124479, Parent 118266: ExpirationProcessThread, Storage
  128299884, AllocCnt 10259185 HighWaterAmt 151735085
    tid=1f3f, ptid=1efa, det=1, zomb=0, join=0, result=0, sess=0
     Holding mutex txnP->mutex (0x113ab7f38), acquired at
  tbcli.c(1027)
     Stack trace:
       .
       .
       0x00000001000abc90 tbCliSRInsDel
       0x00000001004340fc IPRA.$ImDeleteBackupObjectExt
       0x000000010044976c ImDeleteBackupObjectExt
       0x000000010047208c IPRA.$ImDeleteDependents
       0x0000000100472c38 IPRA.$ImDeleteDependents
       0x0000000100472c38 IPRA.$ImDeleteDependents
       0x0000000100476ebc ImDeleteDependents
       0x00000001004315fc IPRA.$imDeleteObject
       0x0000000100449480 imDeleteObject
       0x00000001009ef7e0 ExpireBackupData
       0x00000001009eb340 ExpirationProcessThread
       .
       .
  .
  The transaction list can also be checked to see if grouped
  objects are being processed. The imgroup.c file reference is
  key:
   slot -> X:
   Tsn=0:XXXXXXX, Resurrected=False, InFlight=True,
  Distributed=False, Persistent=True, Addr XXXXXX
     Start ThreadId=XXXXX, Timestamp=XX/XX/XX XX:XX:XX,
  Creator=imgroup.c(4107)
     Last known in use by ThreadId=XXXXX
  

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 levels 6.2.5 and 6.3.3.             *
  *                 Note that this is subject to change at       *
  *                 the discretion of IBM.                       *
  ****************************************************************
  *
  
  AFFECTED PLATFORMS:
  AIX, HP-UX, Solaris, Linux, and Windows.
  

Problem conclusion

• The described problem has been resolved.
  

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

• R62A PSY

     UP

• R62H PSY

     UP

• R62L PSY

     UP

• R62S PSY

     UP

• R62W PSY

     UP

• R63A PSY

     UP

• R63H PSY

     UP

• R63L PSY

     UP

• R63S PSY

     UP

• R63W PSY

     UP