IC53497: EXPIRE INVENTORY PROCESS MAY CRASH WHEN ATTEMPTING TO DELETE A LOGICAL FILE WITH A LENGTH OF 0

APAR status

• Closed as program error.

Error description

• An Expiration process may cause a TSM Server crash if
  it encounters a logical file that had a length of 0 in all
  aggregates. The following diagnostic message will be
  issued just prior to the crash:
  .
  ANR9999D bfcreate.c(743): ThreadId <XX> Logical file 0
  .XXXXXXXX has length of 0 in all aggregates. (SESSION:
  XXXXXX, PROCESS: XXX)
  .
  The root cause of the zero length file is being addressed by
  APAR IC53498. Please see this APAR for more details.
  .
  NOTE: Expiration will be the most common process
  associated with the crash but it could also happen under
  any process/utility that attempts to delete a file that has
  a length of 0 in all aggregates. The ANR9999D message
  will be the same regardless of which process/utility is
  driving the deletion request and subsequent crash.
  .
  Customer/L2 Diagnostics:
  The following are examples of the callstack that may be
  available for this problem:
  .
  pkmemory.pkFreeTracked
  bftxn.bfEndTxn
  tmtxn.AbortTxn
  tmtxn.tmAbort
  imexp.DeleteFilesThread
  pkthread.StartThread
  .
  -or-
  tbFetchNext
  DetermineBackupRetention
  ExpirationQualifies
  ExpirationProcess
  ImDoExpiration
  StartThread
  .
  The callstacks will vary since the issue is that memory is being
  invalidated after failing to delete a particular file.
  .
  Platforms affected: All 5.4.X TSM Servers
  .
  Initial Impact: Medium
  .
  Additional Keywords: adp active data pools pkfree newList
                       updlist txnp bfdestroy imexp ANR9999D
                       crash core dump terminate stop fail
  .
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: TSM Server customers using the command       *
  *                 EXPIRE INVENTORY.                            *
  ****************************************************************
  * PROBLEM DESCRIPTION: See ERROR DESCRIPTION.                  *
  ****************************************************************
  * RECOMMENDATION: Apply fixing level when available.           *
  *                 This problem is currently projected to be    *
  *                 fixed in levels 5.4.1.2 and 5.4.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:

  PK52452

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