IBM Support

PQ48976: INCORRECT RAP CHAIN BUILT WHEN USING SEARCH<0.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Incorrect RAP chain built when using SEARCH<0.
    

Local fix

  • Specify SEARCH=0 or -0 to bypass the space search logic.
    0 and -0 have the same meaning, bypassing the space search
    and putting the segment not fitting in its home block into
    the overflow area.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of IMS High Performance Load       *
    *                 ( HP Load ) Release 1. (FMID=H1IM110)        *
    ****************************************************************
    * PROBLEM DESCRIPTION: Incorrect RAP chain of HDAM/PHDAM       *
    *                      database built by HP Load when using    *
    *                      SEARCH<0, a negative value for the      *
    *                      SEARCH parameter.                       *
    *                                                              *
    *                      Even when using the SEARCH>0, same      *
    *                      problem might occur for the root        *
    *                      segments randomized to the last         *
    *                      block/CI in RAA. Because HP Load        *
    *                      cannot perform forward search at the    *
    *                      last block in the HDAM/PHDAM RAA.       *
    ****************************************************************
    * RECOMMENDATION: Apply the maintenance for this APAR.         *
    ****************************************************************
    The incorrect RAP chain resulted from the retry process in the
    SRCHBLK subroutine. When the space search returns a candidate
    block/CI but the actual segment does not fit into the candidate,
    HP Load turns off the bit in the space map associated to the
    block/CI so that the subsequent space search no longer selects
    the block/CI, and does retry to search for the new candidate
    block/CI. In this process, HP Load updates only the RBN value
    of the current block/CI with the RBN of home block, and any
    other values are unchanged.
    (This RBN trick is required for the retry process. But it should
    have changed other values at the same time.)
    In the subsequent root segment process, this discrepancy causes
    misunderstanding of the block/CI (candidate before the retry) as
    the home block. HP Load just uses the block/CI when it has
    enough space to keep the root. It causes the incorrect synonym
    chain.
    

Problem conclusion

  • The module HPSRHDLD and HPSRRLDM have been modified to regain
    the complete information of the home block before the retry
    process.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PQ48976

  • Reported component name

    IMS HIGH PERF L

  • Reported component ID

    5655E0700

  • Reported release

    110

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2001-05-21

  • Closed date

    2001-05-31

  • Last modified date

    2001-06-05

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

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

    UQ54712

Modules/Macros

  •    HPSRHDLD HPSRHDL5 HPSRHDL6 HPSRHDL7 HPSRRLDM
    HPSRRLD7
    

Fix information

  • Fixed component name

    IMS HIGH PERF L

  • Fixed component ID

    5655E0700

Applicable component levels

  • R110 PSY UQ54712

       UP01/06/01 P F105

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.

[{"Line of Business":{"code":null,"label":null},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCX89F","label":"IMS HP Load"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"110"}]

Document Information

Modified date:
03 October 2020