PK05745: HD POINTER CHECKER DOES NOT DETECT KEY ERRORS IN A SECONDARY INDEX DATABASE.

Obtain the fix for this APAR.

APAR status

• Closed as unreproducible in next release.

Error description

• When the secondary index has symbolic pointers, HD Pointer
  Checker does not detect any error even if the keys in the
  secondary index data base are broken.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: IBM IMS High Performance Pointer Checker for *
  *                 z/OS Version 2 Release 1 (FMID=HPC2210)      *
  *                 users.                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION: This APAR adds HD Pointer Checker to    *
  *                      check the index key, when the secondary *
  *                      index has a symbolic index pointer.     *
  ****************************************************************
  * RECOMMENDATION: Apply the maintenance for this APAR.         *
  ****************************************************************
  By this APAR, IXKEYCHK=YES can be specified for the
  secondary index database having the symbolic pointer.
  IXKEYCHK is an option for evaluate whether or not the index
  keys are consistent with the index source segment keys.
  
  + NOTE -------------------------------------------------------+
  | IXKEYCHK is not available in the HASH Checking.             |
  | So, it cannot be specified when                             |
  |  - HASH=YES is specified in the PROCCTL statement.          |
  |  or                                                         |
  |  - HD Pointer Checker is run with ICE or HPIC.              |
  +-------------------------------------------------------------+
  

Problem conclusion

Temporary fix

Comments

• The following modules are changed to support ths new function:
   FABPESTM FABPHSHI FABPIST  FABPLBLD FABPLINK FABPPSDA FABPRDEF
   FABPSDA0 FABPSHI0 FABPSTAP FABPXRCK FABPXCTL HPC2210J
  
  
  ==============================================================
  Documentation Changes:
  The documentation is modified as follows:
  ==============================================================
  IMS High Performance Pointer Checker for z/OS, V2R1, User's
  Guide Vol. 1 (SC18725701)
  ==============================================================
  ----------------------------------------
  2.0       HD Pointer Checker
  2.1       Operating Instructions for the HD Pointer Checker Proc
  2.1.1     Overview
  2.1.1.1   Program Functions
  2.1.1.1.1 Detecting Errors in a Database
  ----------------------------------------
   HD Pointer Checker detects the missing primary or the secondary
   index pointers, incorrect index keys,  and incorrect pointers
   for the following databases with the Index Key Check function:
  
    - HIDAM and PHIDAM primary index database
  | - Secondary index database for HISAM, HDAM, HIDAM, PHDAM, and
      PHIDAM.
  
  
  -------------------------------------------
  2.1.2 Standard HD Pointer Checker Processes
  -------------------------------------------
  
   2. CHECK Process
    Index Key Check:
     This process matches key data between index pointer segments
  |  and HIDAM/PHIDAM root segments, or HISAM, HDAM, HIDAM,
     PHDAM or PHIDAM pointer source segments.
     This process also prints database error messages.
  
  
  -----------------------
  2.1.5     Job Control Language
  2.1.5.1   FABPMAIN JCL
  2.1.5.1.2 DD Statements
  -----------------------
  
    SORTE2nn DD
    This is an optional work data set that is generated by the
  |  scan process of the index source segment in HISAM, HDAM,
    HIDAM, PHDAM, PHIDAM, and the index database when PROC
    TYPE=ALL or TYPE=SCAN is specified with IXKEYCHK=YES. It
    becomes an input for the CHECK process.
  
  
  ---------------------------------------
  2.1.7     Output
  2.1.7.4   VALIDPRT Data Set
  2.1.7.4.3 Scan of HISAM Database Report
  ---------------------------------------
  A new record, TA is added to the VALIDPRT scan of HISAM
  database report (overflow part).
  And the following description are added to Figure 38.
  
  | TA
  |   The number of keys of index source segment that were
  |   detected by the SCAN processor.
  
  
  ------------------------------------------------------
  2.1.7.5   EVALUPRT Data Set
  2.1.7.5.7 Evaluation of Index Pointers and Keys Report
  ------------------------------------------------------
  
  Following descriptions are changed:
  
  |The follwing errors could be detected and reported with the
  |messages in this report, when the index database is
  |  a primary index database of HIDAM,
  | or
  |  a secondary index database using a direct pointing, and the
  |  segment type of an index source segment (ISS) is same as one
  |  of index target segments (ITS)
  
   -Missing index pointer
    If there is no index pointer segment whose pointer value
    is equal to the RBA of the index target segment, this segment
    is missing an index pointer. This segment is reported by
    the message FABP2020E with its key value.
   -Invalid index key
    If the pointer value of the index pointer segment is equal to
    the RBA of the index target segment, and the key value of the
    index pointer segment is not equal to the key value of source
    segment or the root key value of HIDAM root segment, this
    index pointer segment contains an invalid index key.
    This segment and index pointer segment are reported by
    the message FABP2021E with its key value.
   -Invalid index pointer
    If there is no index target segment pointed by the index
    pointer segment, this index pointer segment contains an
    invalid index pointer.
    This segment is reported by the message FABP2022E
    with its key value.
   - Invalid index key length
    If the length of the index key from DBD (SRCH field and
    SUBSEQ field) is unmatched with the length of index key in T6,
    T7, or TA record, this record is reported by the message
    FABP2025E, and index key checking is skipped for the
    remaining sort records within the same database data set group
    with the message FABP2027E.
  
  
  |The follwing errors could be detected and reported with the
  |messages in this report, when the index database is
  |  a secondary index database using a symbolic pointing
  |  a secondary index database using a direct pointing, and the
  |  segment type of an ISS is not the same as one of ITS
  
   - Invalid index key, Missing index pointer, or Invalid index
   pointer
    If the number of index source segments is not equal to one of
    index pointer segments which contain the same key value, there
    is a missing index pointer, an invalid index key, or an invali
    index pointer in the database.
    These segments which contain the same index key are reported
    by the message FABP2023E or FABP2024E.
   - Invalid index key length
    If the length of the index key from DBD (SRCH filed and
    SUBSEQ field) is unmatched with the length of index key in T6,
    T7, or TA record, this record is reported by the message
    FABP2025E, and index key checking is skipped for the remaining
    sort records within the same database data set group with
    the message FABP2027E.
  
  
  ------------------------------------------------------
  APPENDIX1.13         Appendix M.  Messages and Codes
  APPENDIX1.13.1       HD Pointer Checker
  APPENDIX1.13.1.3     Messages
  APPENDIX1.13.1.3.265 FABP2072W
  APPENDIX1.13.1.3.266 FABP2072W
  APPENDIX1.13.1.3.267 FABP2072W
  APPENDIX1.13.1.3.268 FABP2072W
  APPENDIX1.13.1.3.269 FABP2072W
  ------------------------------------------------------
  The following message is removed from FABP2072W messages:
  
  FABP2072W INDEX KEY CHECK NOT ALLOWED FOR DBNAME: dbdname
            REASON: INDEX POINTER IS SYMBOLIC
  ×**** PE05/08/22 FIX IN ERROR. SEE APAR PK10506  FOR DESCRIPTION
  

APAR Information

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

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

  UK04928

Modules/Macros

•    FABPESTM FABPHSHI FABPIST  FABPLBLD FABPLINK
  FABPPSDA FABPRDEF FABPSDA0 FABPSHI0 FABPSTAP FABPXCTL FABPXRCK
  HPC2210J
  

Fix information

• Fixed component name

  IMS POINTER CHE

• Fixed component ID

  5655E0900

Applicable component levels

• R210 PSY UK04928

     UP05/06/30 P F506

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.