IBM Support

PQ80121: USING DRF TO RESTORE A DATABASE THAT USES IC2, THE SUMMARY AND DATASET I/O REPORT TOTALS ARE ZERO.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Using DRF to restore a database that uses IC2 - Image Copy 2,
    the Summary report and the Dataset I/O report both show zeros
    for the totals.  This is because DFDSS does the restore of the
    IC2 datasets.  DRF should report the record count for IC2 data-
    sets.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of Database Recovery Facility      *
    *                 V2R1 who use image copies created by the     *
    *                 IMS Image Copy 2 utility.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: When restoring databases from image     *
    *                      copies created by the IMS Image         *
    *                      Copy 2 utility, the Summary Report and  *
    *                      Data Set I/O Report show 0 image copy   *
    *                      records read.                           *
    ****************************************************************
    * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
    ****************************************************************
    DFSMSdss is invoked by DRF during the data set restore process
    to restore image copies created by the IMS Image Copy 2
    utility.  Because of this, DRF does not keep track of an
    accurate count of image copy records processed.  The user exit
    from DFSMSdss does provide an EIOP04 exit that will return each
    time it reads a record off the image copy.  It is possible to
    include a count each time we enter EIOP04, however, due to the
    nature of Image Copy 2 DFSMSdss treats a tape track as a record
    off the image copy.  This record is not equivalent to a database
    record as DRF understands it.
    -
    Even if the Image Copy 2 record count is included, its value
    cannot be included as part of the overall product in the Records
    Written column in the Database Recovery Facility Summary Report.
    The Records Written value is the progressive increment of
    records being written out to the database data set during data
    set restore I/O.  Since this type of image copy is restored
    before data set restore I/O starts, this value will not be
    included in the count.
    -
    During testing of this fix a problem was discovered in which
    random errors can occur in the Data Set Summary Report.
    -
    Another problem was discovered during testing in which recovery
    would fail with MSGFRD4301I DATA SET RESTORE FAILED if the
    recovery list contains only a partial list of entries in a
    SAMEDS image copy.
    

Problem conclusion

  •  AIDS: RIDS/UTIL RIDS/DBS DBS/UTIL
      DEP: NONE
      GEN:
    
    *** END IMS KEYWORDS ***
    Changes are made to include a count of records read by DFSMSdss
    during a restore of IC2 image copies.  Since this is actually a
    count of tape tracks, the report generator is changed to include
    a T next to the image copy record count.  This count will not be
    included in the Records Written value in the Database Recovery
    Facility Summary Report.
    -
    FRXRVRU adds a new rvru_rec_cnt field to keep track of how many
    IC2 records were read by DFSMSdss during IC2 restore.
    -
    FRXISMS0 is changed to ignore the return code passed back from
    DFSMSdss.  Error conditions are checked in FRXISMU0.
    -
    FRXISMU0 is changed to increment rvru_rec_cnt each time DFSMSdss
    reads an image copy record during IC2 restore.  The final count
    is saved in rwcc_entry_icrec to be sent to the report generator.
    -
    FRXGRDS0 adds a T descriptor next to the image copy data set
    read count in the Database Recovery Facility Data Set I/O
    Report.  Since DFSMSdss treats a tape track as a record of the
    image copy, T indicates that the record read was actually a
    track.  SAVE_RC is initialized to eliminate random errors.
    -
    The following Doc change is required:
    IMS Database Recovery Facility for z/OS, V2R1,
      User's Guide (SC18-7016-01)
    Appendix A. Sample Reports
    Output Content
    -
    
    Delete the paragraph that says...
     Note: The image copy record read count will be 0 for image
           copy data sets which are created via the IMS Image Copy 2
           Utility Since IMS Database Recovery Facility invokes
           DFSMS to restore such image copies.
    -
    Replace with ...
     Note: The image copy record read count is a number followed by
           a T if the image copy is restored by DFSMSdss.  The count
           represents the number of tracks restored by DFSMSdss.
           Otherwise, the count represents the number of records
           read from a non-DFSMSdss image copy data set.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PQ80121

  • Reported component name

    IMS DB RECOVERY

  • Reported component ID

    5655I4400

  • Reported release

    210

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2003-10-28

  • Closed date

    2004-01-23

  • Last modified date

    2004-07-12

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

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

    UQ84406

Modules/Macros

  •    FRXGRDS0 FRXISMS0 FRXISMU0 FRXRVRU
    

Publications Referenced
SC18701601    

Fix information

  • Fixed component name

    IMS DB RECOVERY

  • Fixed component ID

    5655I4400

Applicable component levels

  • R210 PSY UQ84404

       UP04/02/25 P F402

[{"Line of Business":{"code":null,"label":null},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCX88Z","label":"IMS Database Recovery Facility"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"210"}]

Document Information

Modified date:
09 November 2020