PK04598: ADD CHECKING OF DIRECT-ADDRESS POINTERS IN HISAN DATA BASE(S) TO HD POINTER CHECKER

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• By this APAR, HD Pointer Checker can check
  the direct-address pointers in HISAM database.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: IBM IMS High Performance Pointer Checker for *
  *                 z/OS Version 2 Release 1 (FMID=HPC2210)      *
  *                 users.                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION: HD Pointer Checker is enhanced to check *
  *                      the direct-address pointers in the      *
  *                      HISAM databases. The direct-address     *
  *                      pointer points a logical record in an   *
  *                      overflow data set of HISAM database.    *
  ****************************************************************
  * RECOMMENDATION: Apply the maintenance for this APAR.         *
  ****************************************************************
  The checking of direct-address pointers in the HISAM database
  is supported in the following environment:
  - HD Pointer Checker runs as a stand alone job.
  - HD Pointer Checker runs as a single-step HASH checking option
    with IMS High Performance Image Copy (HPIC)
    Version 3 Release 1 (FMID=H1J0310) or
    Version 3 Release 2 (FMID=H1J0320).
  
  To invoke this checking as a stand alone job, specify
  the HISAM database to the DATABASE control statement in the
  PROCCTL data set.
  
  To invoke this checking with HPIC, specify HDPC=Y to the HISAM
  database data set or GLOBAL statement in the ICEIN data set.
  
  +------------------------------------------------------------+
  | NOTE:                                                      |
  | The direct-address pointers in the HISAM databases cannot  |
  | be validated correctly, if any segment data has been       |
  | deleted after an initial load or a reorganization.         |
  | REASON:                                                    |
  | - DL/I does not set the delete flag in the logical records |
  |   in the overflow data set after records are deleted.      |
  |   These records are located by the HD Pointer Checker as   |
  |  "ACTIVE", although they are inactive to DL/I.             |
  +------------------------------------------------------------+
  

Problem conclusion

Temporary fix

Comments

• ==============================================================
  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 Processor
  2.1.1 Overview
  2.1.1.4 Restrictions
  --------------------------------------------------------------
  Remove the following description of restriction regarding the
  HISAM database:
    The following database types cannot be analyzed by the HASH
    Check function:
  
    - The HISAM database which does not have a logical relation
      to the HD database
  
  And, add the following new descriptions of restrictions.
  
  |  - The direct-address pointers in the HISAM databases can
  |    be validated correctly only after an initial load or a
  |    reorganization.
  |    HD Pointer Checker can detect pointer errors,
  |    if all segment data is deleted after an initial load
  |    or a reorganization. This is because DL/I does not set
  |    the delete flag in the logical records in the
  |    overflow data set when the records are deleted.
  |    These records are located by the HD Pointer Checker as
  |    "ACTIVE", although they are inactive to DL/I.
  
  --------------------------------------------------------------
  APPENDIX1.13     Appendix M.  Messages and Codes
  APPENDIX1.13.1   HD Pointer Checker
  APPENDIX1.13.1.3 Messages
  --------------------------------------------------------------
  The following new messages are added:
  
  | FABP0971E TARGET ISN'T A VALID LOGICAL RECORD
  |
  | Explanation:
  |   The HISAM database is damaged. The logical record
  |   corresponding to the direct-address pointer does not exist
  |   in the overflow data set.
  |   Note that this message can be issued for a normal
  |   database if some segments have been deleted from
  |   the database.
  | System Action:
  |   Processing continues.
  | Programmer Response:
  |   Repair the database, and rerun the HD Pointer Checker job.
  | Problem Determination:
  |   See Appendix B. Database Repair Guidelines.
  
  
  | FABP0972E MORE THAN 1 POINTER TO THE SAME RECORD
  |
  | Explanation:
  |   The HISAM database is damaged. More than one direct-address
  |   pointer points to the same logical record in the overflow
  |   data set.
  |   Note that this message can be issued for a normal
  |   database if some segments have been deleted from
  |   the database.
  | System Action:
  |   Processing continues.
  | Programmer Response:
  |   Repair the database, and rerun the HD Pointer Checker job.
  | Problem Determination:
  |   See Appendix B. Database Repair Guidelines.
  
  
  | FABP0973E NO POINTER TO THIS OVERFLOW LOGICAL RECORD
  |
  | Explanation:
  |   The HISAM database is damaged. No direct-address pointer
  |   points to the logical record in the overflow data set.
  |   Note that this message can be issued for a normal
  |   database if some segments have been deleted from
  |   the database.
  | System Action:
  |   Processing continues.
  | Programmer Response:
  |   Repair the database, and rerun the HD Pointer Checker job.
  | Problem Determination:
  |   See Appendix B. Database Repair Guidelines.
  
  
  
  | FABP1993E THE NUMBER OF DIRECT-ADDRESS POINTERS IS DIFFERENT
  |           FROM THE NUMBER OF LOGICAL RECORDS IN THE OVERFLOW
  |           DATA SET
  | Explanation
  |   The HISAM database is damaged. The number direct-address
  |   pointers in the HISAM data base is not equal to the number
  |   of logical records in the overflow data set.
  |   Note that this message can be issued for a normal
  |   database if some segments have been deleted from
  |   the database.
  | System Action:
  |   Processing continues.
  | Programmer Response:
  |   Repair the database, and rerun the HD Pointer Checker job.
  | Problem Determination:
  |   See Appendix B. Database Repair Guidelines.
  
  
  
  | FABP1994E THE SUM OF DIRECT-ADDRESS POINTER VALUES IS
  |           DIFFERENT FROM THE SUM OF LOGICAL RECORD RBAS IN THE
  |           OVERFLOW DATA SET
  | Explanation:
  |   The HISAM database is damaged. The direct-address pointer
  |   values are not equal to the RBAs of the logical record in
  |   the overflow data set.
  |   Note that this message can be issued for a normal
  |   database if some segments have been deleted from
  |   the database.
  | System Action:
  |   Processing continues.
  | Programmer Response:
  |   Repair the database, and rerun the HD Pointer Checker job.
  | Problem Determination:
  |   See Appendix B. Database Repair Guidelines.
  ×**** PE05/06/25 FIX IN ERROR. SEE APAR PK07981  FOR DESCRIPTION
  

APAR Information

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

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

  UK02802

Modules/Macros

•    FABPECTL FABPHEVL FABPHPUT FABPHRCK FABPHSHI
  FABPLBLD FABPMSGT FABPPTRT FABPRDEF FABPSHI0 FABPTRC
  

Fix information

• Fixed component name

  IMS POINTER CHE

• Fixed component ID

  5655E0900

Applicable component levels

• R210 PSY UK02802

     UP05/04/27 P F504

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.