IBM Support

PK29931: DRF STORAGE SHORTAGE DEPENDING ON READNUM AND SORTPARM SETTINGS SUB AS : ABEND069 RC OR MASTER AS : ABEND40D OR BOTH HANG/WAIT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Depending on SORTPARM(NUM) value, the result is different.
    When using the same value as the numbers of area, it is
    completed.
    READNUM(10,22) and SORTPARM(1-5) get sub AS : abend069 rc4
                                         master : abend40D
    READNUM(10,22) and SORTPARM(1-5) get master and sub go into WAIT
    dump of master a/s, FRXSTG0$+05F0 issued "BPE0041E UNABLE TO
    ALLOCATE REQUESTED STORAGE".
    
    To avoid the partial dump, customer specified REGION=40M, and
    dump with abend878 was captured. The systrace on the second dump
    
    shows FRXSTG0$+02BC getmained storage with x'1000' length
    repeatedly (up to user region top). Also it seems loop occurred
    between FRXPPRB0+037A and
    FRXPPRB0+037A and FRXPPRB0+0480.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users with IMS Database Recovery Facility    *
    *                 Version 2 Release 1 installed are affected.  *
    ****************************************************************
    * PROBLEM DESCRIPTION: Running DRF with TAPECHK(Y) and         *
    *                      CACHE(Y) results in a ABEND40D in the   *
    *                      master address space, ABEND069 in the   *
    *                      subordinate address space, or a loop.   *
    ****************************************************************
    * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
    ****************************************************************
    While using CACHE(Y) with TAPECHK(Y) DRF will attempt to
    allocate and unallocate the image copy data sets with VTS.  This
    proccess is faster than the allocate and unallocate done during
    recovery I/O.  This creates a timing issue with TAPECHK
    processing where it will attempt to make a tape device request
    before the CACHE process finishes unallocating a previous
    request.
    

Problem conclusion

  • AIDS: RIDS/UTIL RIDS/DBS DBS/UTIL
      DEP: NONE
      GEN:
    
    *** END IMS KEYWORDS ***
    FRXIDYN0 and FRXMSTR0 are changed to wait for a tape device to
    be unallocated from a subordinate address space before allowing
    that address space to make another tape device request.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK29931

  • 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

    2006-08-15

  • Closed date

    2006-09-26

  • Last modified date

    2007-02-13

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

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

    UK18327

Modules/Macros

  • FRXIDYN0 FRXMSTR0
    

Fix information

  • Fixed component name

    IMS DB RECOVERY

  • Fixed component ID

    5655I4400

Applicable component levels

  • R210 PSY UK18327

       UP06/09/29 P F609

[{"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":"210","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
13 February 2007