PM42339: ABEND0C4 IN DFSDBLD0 BECAUSE DDIRPNT=0.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• ABEND0C4 in DFSDBLD0 because DDIRPNT=0.
  The 0C4 occurred because DDIRPNT was zero. DDIRPNT=0 indicates
  that the partition structure was not initialized/active, but
  because there is no check for DDIRPNT=0, DFSOPSB0 continues to
  process using this invalid/zero DDIRPNT. We eventually call
  DFSDBLD0 where the 0C4 occurs because we attempt to continue
  processing with an invalid intent list.
  

Local fix

• No.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All IMS V11 HALDB users who run Online       *
  *                 Reorganization ( OLR ).                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: An ABENDS0C4 / ABEND0C4 occurred in     *
  *                      module DFSDBLD0 during /ERE because the *
  *                      HALDB master DDIR address was zero. The *
  *                      master DDIR address was zero because    *
  *                      the DDIRPNT ( DDIR partition name table *
  *                      address ), which was also zero, was     *
  *                      used to get the master DDIR address.    *
  ****************************************************************
  * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
  ****************************************************************
  During /ERE, an ABEND0C4 occurred in module DFSDBLD0 because the
  master DDIR address was zero.  The 0C4 occurred while attempting
  to build the OLR PSB related blocks for resuming an OLR during
  /ERE.  The save flow was DFSIRST0 -> DFSRST00 -> DFSRLP00 ->
  DFSRDBP0 -> DFSDBLM0 -> DFSOPSB0 -> OLRDMB0 -> DFSDBLD0.  Module
  DFSOPSB0 loaded the partition name table address from DDIRPNT.
  DDIRPNT was zero.  This zero address was used to get the HALDB
  master DDIR address, which was again zero.  This zero master
  DDIR address was passed to DFSDBLD0 which eventually caused the
  ABEND0C4.
  

Problem conclusion

• GEN:
  KEYWORDS:
  
  *** END IMS KEYWORDS ***
  The following module has been modified to correct the reported
  problem:
  
  ************
  * DFSOPSB0 *
  ************
  Code has beed added to check DDIRPNT for zero to determine if
  the HALDB master structure was built before continuing to
  attempt to build the OLR PSB related blocks.  If the HALDB
  master structure was not built ( DDIRPNT = 0 ), message
  DFS2972E ( MSGDFS2972E ) with error text HALDB STRUCTURE NOT
  ACTIVE will be issued and the OLR / OLR resume will fail.
  
  
  The following documentation change will also be made:
  
  IMS V11 Messages and Codes, Volume 1 : DFS Messages
  ( GC18971202 )
  
  Under message DFS2972E, add the following 5th error text:
  
  HALDB STRUCTURE NOT ACTIVE
  
  Under Programmer Response, add:
  
  For HALDB STRUCTURE NOT ACTIVE, if the OLR is being resumed
  during IMS /ERE, ensure that the ACBLIB used at restart is the
  same ACBLIB used by IMS prior to IMS termination.
  

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:

  UK70098

Modules/Macros

• DFSOPSB0
  

Fix information

• Fixed component name

  IMS V11

• Fixed component ID

  5635A0200

Applicable component levels

• R100 PSY UK70098

     UP11/07/26 P F107 Ž

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.