PK76374: INTERMITTENT STORE FAILURES WITHOUT AN ERROR MESSAGE OR CODE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• In certain store situations, the resource manager is incorrectly
  handling an error situation returned by OAM and stores the
  object under a temporary object name (such as
  A1001001.A08K17.B14750.F43030.V001259) rather than the original
  object name (such as A1001001.A08K17.B14750.F43030.V001). No
  error is returned by the resource manager in this case, so the
  metadata is committed in the library server. As such, a search
  for the document yields a hit, but retrieve fails because only
  the temporary object name exists in OAM, not the original object
  name.
  
  Errors similar to the following appear in the RM SYSPRINT when
  this problem occurs:
  
  Fail on:
       Collection    <OAM.SGROUP40.CLLCT>
       ExtObjectName <A1001001.A08F26.B11404.A55251.V001OSRQ-..>
  ICMMOSOM OAM_Delete                        01706
  2008-06-26-11.14.04.684697 2143E4 Message rc=8, reason=2C060100
  
  Fail on:
       Collection    <OAM.SGROUP40.CLLCT>
       ExtObjectName <A1001001.A08F26.B11404.A55251.V001>
  ICMMOSOM OAM_Retrieve                      01540
  2008-06-26-12.43.58.171393 A43BC Message rc=8, reason=2C030100
  ICM024E OAM Retrieve Failed RC=8 Reason=2C030100
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of DB2(R) Content Manager for z/OS(R)  *
  *                 resource manager V8.3.                       *
  ****************************************************************
  * PROBLEM DESCRIPTION: Users might see that some Store         *
  *                      failures into OAM go unreported when    *
  *                      first found; however, the end           *
  *                      transaction processing fails because    *
  *                      the object is not found at that point.  *
  *                      (i.e. there is no data loss.)           *
  ****************************************************************
  * RECOMMENDATION: APPLY CORRECTIVE SERVICE                     *
  ****************************************************************
  Store processing was incorrectly interpreting certain OAM
  return/reason codes as "object already exists". These reason
  codes really meant that the object could not be stored for other
  reasons. Hence, an incorrect path was taken, resulting in a
  failure during End Transaction processing, instead of at the
  time of the original error during Store. Furthermore, End
  Transaction processing did not report the original
  return/reason code.
  

Problem conclusion

• The resource manager's Store processing was corrected to
  correctly interpret "object already exists" return/reason codes
  from OAM, report other errors as such, and fail the request at
  that point.
  

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:

  UK44088

Modules/Macros

•    ICMMOSOM
  

Fix information

• Fixed component name

  CM390 LIB SER R

• Fixed component ID

  5697H6000

Applicable component levels

• R831 PSY UK44088

     UP09/02/20 P F902

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.