PK24223: ABEND0C4 DFSDLMP0 UNDER LABEL LOOPCB 06/05/16 PTF PECHANGE

APAR status

• Closed as program error.

Error description

• Bit (PSTCMDPD,PSTCODE1) was being set by DFSDBLI0.
  This indicates that PSB VR5050 cannot be scheduled
  as one of the databases it has access intent is being
  DBDed or DBRed.  Upon return from DFSDBLI0 with a RC of 20,
  DFSDBLM0 calls DFSDLMP0 to free the PSB. At this point, space
  has been obtained for PSB VR5050, but the PSB has not been
  loaded in storage yet. What we see at the corresponding address
  is residual data. Henve, we are reading residual data which
  causes the abend0c4. We should skip the release of the partition
  isolation control block in this case.
  

Local fix

• Non
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All IMS R910 users with HALDB who want to    *
  *                 restrict processing to range of partitions,  *
  *                 and with apar/PTF PK04880/UK10124 applied.   *
  ****************************************************************
  * PROBLEM DESCRIPTION: Abend0C4 DFSDLMP0 under label LOOPCB    *
  *                      when an application failed scheduling   *
  *                      due to /DBR command being in progress.  *
  ****************************************************************
  * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
  ****************************************************************
  An application failed to be scheduled because one of the HALDB
  master databases it intended to use was being DBDed or DBRed.
  Upon return from DFSDBLI0 with a return code of 20, DFSDBLM0
  called DFSDLMP0 to free the PSB.  At this point, space had been
  obtained for the PSB, but the PSB has not been loaded in storage
  yet, and the partition isolation storage had not yet been
  acquired.  From the dump, what was seen at the corresponding PSB
  address was residual data.  Hence, DFSDLMP0 was reading residual
  data when it attempted to loop through all the DB PCBs to
  release the partition isolation storage that was obtained from
  DFSPSEL PART=PRSET. This then led to the abend0c4 in DFSDLMP0.
  *
  The logic to release the partition isolation storage should be
  skipped in this case.
  *
  Additional keywords: ABENDS0C4 S0C4.
  

Problem conclusion

• AIDS: RIDS/SYS RIDS/SCHD SYS SCHD
    DEP: NONE
    GEN:
  
  *** END IMS KEYWORDS ***
  DFSDLMP0
  Modify code to skip the release of the partition
  isolation storage if it has not been acquired.
  

Temporary fix

• *********
  * HIPER *
  *********
  

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UK15188

Modules/Macros

• DFSDLMP0
  

Fix information

• Fixed component name

  IMS V9

• Fixed component ID

  5655J3800

Applicable component levels

• R900 PSY UK15188

     UP06/06/09 P F606 «