PM07289: VARIOUS DFR PROBLEMS THAT NEED TO BE ADDRESSED - SEE LIST BELOW

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• This APAR is created for errors detected by testing and code
  review.
  Here is a list of items being addressed:
  1. If the OLDS that was in use when IMS failed was dual and one
     of the OLDS caused a dynamic allocation error, DFR ends with
     return code 0 and does not generate warning messages in
     'OLDS/SLDS LIST'.
  2. If DBRC=N was specified and the OLDS that was in use when
     IMS failed was dual and one of the OLDS caused a dynamic
     allocation error, DFR sets null to DSNAME in 'OLDS/SLDS
     LIST'.
  3. If the OLDS that was in use when IMS failed was dual and the
     primary OLDS caused a write error, DFR ends with abend code
     of S002.
  4. If the OLDS that was in use when IMS failed was dual and
     the secondary OLDS caused a write error, DFR ends with abend
     code of SC03 after recovery is completed with message
     MSGDFR3509I. And DFR does not generate warning messages in
     'OLDS/SLDS LIST'.
  
  Keywords: ABENDC03 ABENDSC03 ABEND002 ABENDS002 DFR3509I
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All IMS DEDB FAST RECOVERY Version 2         *
  *                 Release 2 (FMID=H1J2220) users who use       *
  *                 IMS V9, IMS V10 or IMS V11.                  *
  ****************************************************************
  * PROBLEM DESCRIPTION: Various problems of DFR for the OLDS    *
  *                      process detected as the results of an   *
  *                      additional code review and tests.       *
  ****************************************************************
  * RECOMMENDATION: Apply the maintenance for this APAR.         *
  ****************************************************************
  The following problems under IMS V9, IMS V10 and IMS V11 are
  fixed by this APAR:
  *
  1. If the OLDS that was in use when IMS failed was dual and one
     of the OLDS caused a dynamic allocation error, DFR ends with
     return code 0 and does not generate warning messages in
     'OLDS/SLDS LIST'.
  2. If DBRC=N was specified and the OLDS that was in use when
     IMS failed was dual and one of the OLDS caused a dynamic
     allocation error, DFR sets null to DSNAME in 'OLDS/SLDS
     LIST'.
  3. If the OLDS that was in use when IMS failed was dual and the
     primary OLDS caused a write error, DFR ends with abend code
     of S002.
  4. If the OLDS that was in use when IMS failed was dual and
     the secondary OLDS caused a write error, DFR ends with abend
     code of SC03 after recovery is completed with message
     MSGDFR3509I. And DFR does not generate warning messages in
     'OLDS/SLDS LIST'.
  

Problem conclusion

• The following modules have been modified.
  (x = 9, A and B)
  *
  DFRGAL1x - This module was changed as follows.
             . Only when the target log data set is found in 'LOG
               D/S DETERMINATION' processing and is available,
               GALEDYNA which is the bit to indicate the dynamic
               allocation error is cleared for the flag (LOGGALEP
               or LOGGALES) of the allocation error.
             . In OLDSALLC sub-routine and SLDSALLC sub-routine,
               when the primary log data set is available,
               LOGTPRIP which is the bit to indicate that the
               primary log data set is in process is set to the
               flag (LOGSTAT1). And the bit is cleared when the
               primary log data set is unavailable.
  DFRGDALx - This module was changed so that DSNAME of OLDS is
             saved to DSWK or to the OLDS/SLDS descriptor table
             after the MSGDFR3114E message is issued if the
             allocation error occurred at the time of the
             allocation request of OLDS.
  DFRGRD1x - This module was changed so that the following fields
             are initialized only if the target log data set is
             available.
              .LOGRDEP, LOGRDES, LOGRDEP1, LOGRDES1
  DFRNDSLx - This module was changed so that '*** DSNAME NOT FOUND
             ***' is set to the OLDSDDSN field after initializing
             with blank if the OLDSDDSN field has null.
  DFRNGCLx - This module was changed so that DFR closes OLDS even
             if the write error occurred.
             However, the MSGDFR3103I message is not issued for
             OLDS that the write error occurred.
  *
  ========================
  = DOCUMENTATION CHANGE =
  ========================
  IMS DEDB Fast Recovery for z/OS Version 2 Release 2 User's Guide
  and Reference (Document Number: SC27-0928-03) should be changed
  as follows.
  ================================================================
   4.0 Input and output for DFR under IMS V8 and IMS V9
    4.2 Understanding the output produced
     4.2.3 OLDS/SLDS list
       :
       :
       :
     If the OLDS that was in use when IMS failed was dual and one
     of the OLDS caused an open error, an I/O error, or a dynamic
     allocation error, DFR generates messages as shown in Figure
     40, and continues processing.
  |
  |      Note: If DFR cannot get the data set name of the OLDS
  |            caused a dynamic allocation error, you may see
  |            '*** DSNAME NOT FOUND ***' for the DSNAME= in the
  |            list.
  |
     In this case, recover the data set in error by using the
     normal OLDS after the DFR execution, or use the
     DBRC CHANGE.PRILOG or CHANGE.SECLOG command to register the
     error status to DBRC.
       :
  *
  ================================================================
   5.0 Input and output for DFR under IMS V10 and IMS V11
    5.2 Understanding the output produced
     5.2.3 OLDS/SLDS list
       :
       :
       :
     If the OLDS that was in use when IMS failed was dual and one
     of the OLDS caused an open error, an I/O error, or a dynamic
     allocation error, DFR generates messages as shown in Figure
     57, and continues processing.
  |
  |      Note: If DFR cannot get the data set name of the OLDS
  |            caused a dynamic allocation error, you may see
  |            '*** DSNAME NOT FOUND ***' for the DSNAME= in the
  |            list.
  |
     In this case, recover the data set in error by using the
     normal OLDS after the DFR execution, or use the
     DBRC CHANGE.PRILOG or CHANGE.SECLOG command to register the
     error status to DBRC.
       :
  *
  

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:

  UK54454

Modules/Macros

• DFRGAL1A DFRGAL1B DFRGAL19 DFRGDALA DFRGDALB
  DFRGDAL9 DFRGRD1A DFRGRD1B DFRGRD19 DFRNDSLA DFRNDSLB DFRNDSL9
  DFRNGCLA DFRNGCLB DFRNGCL9
  

Fix information

• Fixed component name

  DEDB FAST RECOV

• Fixed component ID

  5655E3200

Applicable component levels

• R220 PSY UK54454

     UP10/02/22 P F002

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.