IBM Support

PK40848: STORAGE UTILIZATION INCREASED IN DRF MASTER REGION AFTER APPLYING PK24575

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • STORAGE SIZE CALCULATED INCORRECTLY.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of DRF V3R1 might be affected.     *
    ****************************************************************
    * PROBLEM DESCRIPTION: Buffer release failure from DRFB        *
    *                      buffer pool.                            *
    ****************************************************************
    * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
    ****************************************************************
    DRF gets the buffers from two different buffer pools, read
    buffer pool or send buffer pool. However we got some buffers
    from the wrong buffer pool, and when we tried to release them,
    BPE release buffer failed.
    

Problem conclusion

  • AIDS: RIDS/UTIL RIDS/DBS DBS/UTIL
      DEP: NONE
      GEN:
    
    *** END IMS KEYWORDS ***
    FRXHBUF0, FRXRCTL0, FRXPDSS0,FRXUORM0 AND FRXRBUF0 are modified
    to make sure that we get and release the buffers from correct
    buffer pools.
    FRXMSTR0 and FRXMINI1 are modified to change buffer pools upper
    limit size.
    ---------------------------------------------------------------
    THE FOLLOWING TEXT DESCRIBES THE DOC CHANGE:
    -
    This is placed as a new section just before the Specifying
    Primary Address Space Basic JCL section in the DRF User's Guide
    V3R1 SC18-9407-01.
    
    Region Size Considerations
    
    The region size used in production environments for database
    recovery will typically be larger than what is shown in the
    examples.  For recoveries that process large amounts of data an
    increase for the region size may be required to avoid abnormal
    or early termination due to storage shortages.  The user should
    take the following under consideration when setting the region
    size parameter in the startup JCL for both the primary and
    subordinate address spaces:
    
    Use the following procedure to determine the likely number of
    log records to be processed during the recovery and to set a
    region size for the primary and secondary DRF address spaces.
    
    1.  Check the summary report for a prior recovery of the
    database data sets being recovered.  If a summary report is not
    available for the database data sets being recovered, you can
    use a report from recoveries of other database data sets.  If
    you do so, you should take the following into consideration.
    You should use reports from recoveries of database data sets
    with similar update patterns as the ones being recovered.  You
    should also use reports from recoveries of other HIDAM, PHDAM,
    or fast path areas, for example, instead of databases with
    radically different database organizations than the ones being
    recovered.
    
    2.  Add records processed for log data sets listed in the
    summary report
    
    3.  Determine the average of the records that were processed
    
    4.  Run a recovery with the VERIFY function to determine the
    number of log data sets to be processed
    
    5.  Multiply the average number of records found in step 3 by
    The number of log data sets found in step 4
    
    6.  Use the following table to determine what value to set in
    the region size.
    
    ================================================
    |Number of Records Processed |   Region Size   |
    |============================|=================|
    | <35 million log records    |  32M - 256M     |
    |----------------------------|-----------------|
    | Between 35 million and 50  |  At least 256M  |
    | million log records        |                 |
    |----------------------------|-----------------|
    | >50 million log records    |  At least 512M  |
    ================================================
    
    ---------------------------------------------------------------
    Replace the description of the ABENDU0384 Reason Code 004 with
    the following:
    
    Abend Codes:
    
    Logic Error Abends (ABENDU0384)
    
    004 - Obtain fixed length storage
          IMS Database Recovery Facility is unable to obtain fixed
          length storage.  Register 14 contains the return code
          from the load service.  Refer to the Region Size
          Considerations section to set a new region size in the
          JCL for this address space.  Once a new region size is
          determined and set, run the recovery job again.
    
          Modules:
          FRXICTL0, FRXUORM0
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK40848

  • Reported component name

    IMS DB RECOVERY

  • Reported component ID

    5655I4400

  • Reported release

    310

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2007-03-08

  • Closed date

    2007-07-05

  • Last modified date

    2008-04-30

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

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

    UK26867

Modules/Macros

  • FRXHBUF0 FRXMINI1 FRXMSTR0 FRXPDSS0 FRXRBUF0
    FRXRCTL0 FRXUORM0
    

Publications Referenced
SC18940701    

Fix information

  • Fixed component name

    IMS DB RECOVERY

  • Fixed component ID

    5655I4400

Applicable component levels

  • R310 PSY UK26867

       UP07/07/07 P F707

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCX88Z","label":"IMS Database Recovery Facility"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
30 April 2008