IO03318: CM DOES NOT RELEASE THE TSM SESSION WHEN THE TSM MEDIA IS UNAVAILABLE

APAR status

• Closed as program error.

Error description

• When the Resource Manager requests an object from TSM for which
  the media is unavailable, TSM signals an error, rc=14, that the
  data is not available. CM, in turn, also signals an error
  (ICM9862: dsmGetObj failed, return code: 14) but doesn't release
  the corresponding TSM session. This blocks the related tape
  driver until it is timed out by the TSM server.
  
  The ICM9862 message may also be followed by this message:
  ICM9850: dsmInit failed, return code: 102
  

Local fix

• Set the TSM server option 'idletimeout' to something lower than
  the default value of 15 minutes. This will cause the session to
  be cancelled, and the resource manager correctly handles a
  'session cancelled' return from TSM as opposed to a 'media
  unavailable' return.
  

Problem summary

• When the resource manager requests an object from Tivoli Storage
  Manager for which
  the media is unavailable, TSM signals an error, rc=14, that the
  data is not available. In turn, DB2 Content Manager signals an
  error (ICM9862: dsmGetObj failed, return code: 14) but does not
  release the corresponding TSM session.  If this TSM Server error
  persists, then the TSM Server session pool might reach its
  maximum limit and block all other client connections.
  

Problem conclusion

• The DB2 Content Manager resource manager does not close the TSM
  Session when processing media errors from TSM.
  
  The resource manager now correctly closes the TSM API session
  handle for these type of errors.
  

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

  RESOURCE MGR

• Fixed component ID

  5724B1904

Applicable component levels

• R830 PSY

     UP