PM02504: DFS0427I V9C + U0427 AFTER OLR OF PHIDAM VSAM HALDB

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• DFS0427I LOGICAL ERROR ON xxxxxxxx ERROR CODE V9C plus U0427
  abend shortly after OLR of a PHIDAM/VSAM partition.
  ..
  If the process that encounters the DFS0427I is a BMP without
  PARDLI=1, the IMS control region also abends U0113.
  ..
  The problem occurs in this scenario (much-simplified from that
  of the reporting customer):
    - partition #2 (of 3) is open in both IMSA & IMSB
    - IMSA: OLR of partition #2, after which:
            - datasets A-J in use   (perhaps not relevant)
            - only 1 CI in use of the final cylinder
            - bitmap says no relevant CIs have free space
    - IMSB: ISRT a new root into partition #2, after which:
            - 2 CIs now in use of the final cylinder
    - IMSA: ISRT a new root into partition #2.  This should use
            the 3rd CI of the final cylinder, but instead results
            in DFS0427I V9C
  ..
  The database itself is not corrupted, and a retry of the failing
  process is successful after /ERE or a recycle of IMS.
  ..
  The problem also occurs in IMS version 10
  ..
  Additional symptoms:
  IDCAMS REPRO or PRINT of the final CIs of the partition, if
  submitted before /ERE or IMS restart, fails:
  IDC3302I  ACTION ERROR ON <partition ESDS>
  IDC3351I ** VSAM I/O RETURN CODE IS 156 - RPLFDBWD = X'9A08009C'
  ..
  Additional search keywords:
  ABENDU0427 ABENDU427 ABEND427 U427 HIURBA unformatted DMBPFLLR
  ABENDU0850 PHIDAM VSAM after OLR PSTGTDS
  

Local fix

• Restart or recycle IMS and resubmit the failed process.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: IMS V11 users who run HALDB Online           *
  *                 Reorganization ( OLR OLREORG ) using VSAM    *
  *                 as an access method.                         *
  ****************************************************************
  * PROBLEM DESCRIPTION: A BMP suffered an ABENDU0427 V9C on     *
  *                      a PHIDAM database that was recently     *
  *                      reorganized by OLR.                     *
  ****************************************************************
  * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
  ****************************************************************
  A BMP suffered an ABENDU0427 V9C doing an insert on a PHIDAM
  database that was recently reorganized by OLR. During OLR the
  last inserted data record was at the end of a control area
  ( CA ). Because this is a PHIDAM database, the all 'FF' key
  will be inserted in the first CI of the next CA.
  
  OLR uses PROCOPT 'H' for its output DBPCB and switches to 'L'
  for the all "FF" key. Because the PROCOPT is 'L', the code
  in module DFSDVSM0 after label JRNAD2C skipped formatting the
  first CI in the new CA to all F's. VSAM propogated all zeros
  from the first CI throughout the rest of the CIs in this new
  CA with no RDF/CIDFs.
  
  After OLR, when an application issues a DL/I insert call and
  uses CI number two in this CA, space management recognizes this
  as the beginning of an extent and formats that CI with FSEAP,
  FSE, and RDF/CIDF.
  
  When some subsequent DL/I insert call tries to use CI number
  three in this CA, VSAM finds no RDF/CIDF, causing an ABENDU0427
  V9C.
  
  Additional symptoms: MSGDFS0427I DFS0427I V9C U0427 ABENDU0427
                       ALLFF
  

Problem conclusion

• GEN:
  KEYWORDS:
  
  *** END IMS KEYWORDS ***
  
  DFSDVSM0 : Code was added after labels IESD4000 and JR2C0100
             to check if OLR is active and the data set is the
             output, then skip the check for PROCOPT=L and allow
             the first CI in the new CA to be formatted with
             all F's with a valid RDF/CIDF. VSAM will propagate
             that into the rest of the CIs in the new CA.
  

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:

  PM06221 PM06222 UK56945

Modules/Macros

• DFSDVSM0
  

Fix information

• Fixed component name

  IMS V11

• Fixed component ID

  5635A0200

Applicable component levels

• R100 PSY UK56945

     UP10/05/20 P F005 Ž

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.