IBM Support

PQ80355: CHECKING OF SYMBOLIC POINTERS IN HD POINTER CHECKER

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • Introduction of new function in HPPC - checking of symbolic
    pointers.
    

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 newly supports       *
    *                      symbolic pointers checking by this      *
    *                      APAR. The symbolic pointers are         *
    *                      checked with HASH=NO.                   *
    ****************************************************************
    * RECOMMENDATION: Apply the maintenance for this APAR.         *
    ****************************************************************
    The symbolic pointer checking can run in the FULL checking.
    The FULL checking means the check done when HASH=NO
    is specified.
    
    The restrictions of the symbolic pointer checking are
    as follows:
    - The symbolic pointer checking can run when the target is
      a root segment, but it cannot run when the target is
      not the root segment.
    - The symbolic pointer checking cannot be run
      when either HASH=YES is specified for the PROCCTL data set
      or
      in the HASH Checking that is called from ICE V2 or HPIC V3.
    
    The symbolic pointer checking has the following functions:
    - Checks each value of the symbolic pointer in secondary
      indexes and the sequence key in the index target segment
      (ITS). The check is activated by the new option
      SYMIXCHK=YES.
    - Checks each LPCK value of the symbolic Logical Parent
      pointer and the sequence key of the logical parent segment.
      This check is activated by the new option SYMLPCHK=YES.
    - Checks that the number of index pointer segments is equal
      to the number of index source segments for symbolic index
      pointers.
    - Checks that the sum of CTR values of logical parents is
      equal to the number of logical child segments even if they
      have symbolic pointers. Before this APAR, this check could
      not be done when symbolic pointers were defined
      in the logical child segments.
    - Checks the numbers of occurrences among the paired logical
      children in Bidirectional Physically Paired Logical
      Relationship and that they have symbolic pointers.
      Before this APAR, this check could not be done when symbolic
      pointers were defined.
    
    For more details of SYMIXCHK and SYMLPCHK, see the
    documentation changes in COMMENTS.
    
    FABPIVP1--one of the installation verification programs--is
    changed.If the old version of FABPIVP1 is used after this
    APAR applied, message FABP0327E is issued in the FABPIVP2
    job. The new FABPIVP1 corrects this error.
    The layout of the history record is changed. A new field is
    added and FABGHIR--DSECT macro of the history record--is
    changed.
    However, the old history data set can be used as it is.
    
    The following reports are changed for the symbolic pointers
    and the CTR information:
    - HD Pointer Checker
        (STATIPRT data set) Separator page for DB/DSG
        (STATIPRT data set) Database Statistics report
        (VALIDPRT data set) Scan of Index Database report
        (VALIDPRT data set) Validation of a Pointer to a Target at
                            Scan report
        (VALIDPRT data set) Scan of HISAM Database report
        (VALIDPRT data set) HISAM Segment Level Statistics report
        (VALIDPRT data set) Legend for SCAN / Validation report
        (EVALUPRT data set) CHECK Process Total report
    - DB Historical Data Analyzer
         HD Analysis report
    
    The following new report is produced when PROC SYMIXCHK=YES
    and/or SYMLPCHK=YES are specified.
        (EVALUPR2 data set) Evaluation of Symbolic Pointers report
    

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 (SC18725700)
    ==============================================================
    2.0       HD Pointer Checker
    2.1       Operating Instructions
    2.1.1.4 Restrictions
    --------------------------------------------------------------
    Delete the following statements.
    
      HD Pointer Checker verifies direct pointers only.
      It does not check symbolic pointers.
    
    Add the following restriction to the HASH checking:
    
      Symbolic pointers cannot be checked.
    
    Remove the following restriction from the checking of the
    suppressed index pointer segment:
    
      When a symbolic pointer is used as the index pointer,
      the suppressed segment of the index pointers are not checked.
    
    --------------------------------------------------------------
    2.1.6     Input
    2.1.6.1   FABTMAIN PROCCTL Data Set
    2.1.6.1.4 PROC Statement
    --------------------------------------------------------------
    Add the following new options to the PROC statement.
    
     SYMIXCHK=
      Specifies whether you want to validate the symbolic pointers
      in secondary index databases and the key data. This option
      can be specified when TYPE=ALL and HASH=NO are specified.
      The symbolic pointers can be validated when the target is
      a root segment.
    
      YES
       Specifies that the symbolic pointers are to be validated.
       Index databases and associated primary databases must be
       specified in the DATABASE statements.
    
      NO
       Specifies that the symbolic pointers are not to be validated.
       This is the default value.
    
     SYMLPCHK=
      Specifies whether you want to check the symbolic LP pointers.
      In case both direct LP and symbolic LP pointers are defined
      in the logical child, both the pointers can be validated.
      This option can be specified when TYPE=ALL and HASH=NO is
      specified. The symbolic LP pointers can be validated when the
      logical parent is a root segment.
    
      YES
       Specifies that the symbolic LP pointers are to be validated.
       Both the databases having logical parent segment and
       logical child segments must be specified in the DATABASE
       statements.
    
      NO
       Specifies that the symbolic pointers are not to be validated.
       This is the default value.
    
    --------------------------------------------------------------
    APPENDIX1.13     Messages and Codes
    APPENDIX1.13.1   HD Pointer Checker
    APPENDIX1.13.1.3 Messages
    --------------------------------------------------------------
    The following messages are deleted:
    
     FABP1120W SYMBOLIC PTRS CANNOT BE VALIDATED
     FABP1130I PROCEEDING TO NEXT CTL STATEMENT
     FABP1435I SCAN OF DB: dbdname DSG: XX SYMBOLIC PNTRS
    
    The following messages are added.
    
     FABP0051E THE SUM OF THE CTR FIELDS(count1) IN LP SEGMENT
     segname1 DOES NOT EQUAL TO THE NUMBER OF LC (count2)
     Explanation:
      The sum of CTR values in logical parent segments
      (count1) does not equal to the number of logical
      child segment occurrences (count2).
     System Action:  Processing continues.
     Programmer Response:
      The database is probably corrupted. Correct the database.
     Problem Determination:  See Appendix B.
    
     FABP0541E THE OCCURRENCES OF THE PHYSICALLY PAIRED SEGMENT
     ARE DIFFERENT.  segname1 (count1) :  segname2 (count2)
     Explanation:
      The numbers of logical child segment occurrences and
      paired logical child segment occurrences are not the same
      among the Bidirectional Physically Paired Logical
      Relationship.
     System Action:  Processing continues.
     Programmer Response:
      The database is probably corrupted. Correct the database.
     Problem Determination:  See Appendix B.
    
     FABP2035E TARGET OF SYMBOLIC INDEX POINTER NOT FOUND
     Explanation:
      A symbolic pointer in secondary index was found
      but the target segment having the corresponding key,
      was not found.
     System Action:  Processing continues.
     Programmer Response:
      The database is probably corrupted. Correct the database.
     Problem Determination:  See Appendix B.
    
     FABP2036E TARGET OF SYMBOLIC LP POINTER NOT FOUND
     Explanation:
      A symbolic LP pointer was found, but the target segment
      having the corresponding key was not found.
     System Action:  Processing continues.
     Programmer Response:
      The database is probably corrupted. Correct the database.
     Problem Determination:  See Appendix B.
    
     FABP2096W SOME SYMBOLIC LP POINTERS IN DB: dbdname
     ARE NOT CHECKED
     Explanation:
      The symbolic LP pointers that point to dependent segments
      are not checked. Only symbolic LP pointers that point to root
      segments can be checked by SYMLPCHK=YES.
     System Action:  Processing continues.
     Programmer Response:  None.
     Problem Determination:  None.
    
     FABP2097W SYMBOLIC INDEX POINTER IN DB: dbdname IS NOT CHECKED
     Explanation:
      The symbolic pointers in the secondary index database are
      not checked because they are point to dependent segments.
      Only symbolic pointers that point to the root segments can be
      checked by SYMIXCHK=YES.
     System Action:  Processing continues.
     Programmer Response:  None.
     Problem Determination:  None.
    
    The following message text is added to FABP3609E:
    FABP3609E SORT FOR SYMBOLIC POINTER CHECK FAILED
    
    The message code of FABP1080W is changed to FABP1080I.
    
    The following messages are changed as follows:
    
     FABP1110W THE SYMBOLIC INDEX POINTERS HAVE NOT BEEN CHECKED
     Explanation:
      The symbolic index pointers in the secondary index are
      not checked because of one of the following conditions:
      - The target is not a root segment.
      - SYMIXCHK=YES is not specified in the PROCCTL statement.
      - TYPE=ALL is not specified in the PROCCTL statement
     System Action:  Processing continues.
     Programmer Response:  None.
    
     FABP1210I EXPECTED COUNT OF SYMBOLIC LP POINTERS THAT POINT
     TO THE DATA SET IN THE SAME DB AND/OR OTHER DB(S) = nnn
     Explanation:
      nnn is the number of logical child segments that have
      symbolic logical parent pointers that point to segments
      checked by the HD Pointer Checker.
     System Action: Processing continues.
     Programmer Response: None.
     Problem Determination: None.
    
    "IXKEYCHEK" in the message text and the explanation of message
     FABP2068E are changed to "parm-name".
    

APAR Information

  • APAR number

    PQ80355

  • Reported component name

    IMS POINTER CHE

  • Reported component ID

    5655E0900

  • Reported release

    210

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2003-11-03

  • Closed date

    2003-11-13

  • Last modified date

    2005-04-21

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

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

    UQ82245

Publications Referenced
SC18725700    

Fix information

  • Fixed component name

    IMS POINTER CHE

  • Fixed component ID

    5655E0900

Applicable component levels

[{"Line of Business":{"code":null,"label":null},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCX89G","label":"IMS HP Pointer Checker"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"210"}]

Document Information

Modified date:
04 October 2020