Legend for Check Process Validation report

This report contains a brief description of the headings and abbreviations used in the Validation of a Pointer to a Target at CHECK report.

The following figure shows an example of the report.

Figure 1. VALIDPRT: Legend for Check Process Validation report

IMS HIGH PERFORMANCE POINTER CHECKER FOR z/OS             "LEGEND FOR CHECK PROCESS VALIDATION REPORT"                   PAGE:     1
5655-U09                                                   DATE: 07/06/2021  TIME: 15.50.57                         FABPMAIN - V3.R1


TP ...... RECORD TYPE (T1, T2, ETC.)

TARGET OF POINTER:

DB ...... DATABASE NUMBER OF TARGET SEGMENT
DG ...... DATA SET GROUP NUMBER OF TARGET SEGMENT
RBA ..... RELATIVE BYTE ADDRESS OF TARGET SEGMENT
SC ...... ACTUAL SEGCODE OF TGT (IF TP=T1), ELSE EXPECTED TGT SC

SOURCE OF POINTER:

DB ...... DATABASE NUMBER OF SEGMENT CONTAINING POINTER
DG ...... DATA SET GROUP NUMBER OF SEGMENT CONTAINING POINTER
RBA ..... RELATIVE BYTE ADDRESS OF SEGMENT CONTAINING POINTER
SC ...... SEGMENT CODE OF SEGMENT CONTAINING POINTER

DISK ADDRESS OF POINTER:

BLOCK# .. BLOCK CONTAINING POINTER
VOLUME .. DIRECT ACCESS VOLUME ID
cccCCCCHRR OFST .. ADDR OF PTR IN ERROR (IF YOU REFER OR CHANGE THE DATABASE CONTENTS BY AMASPZAP, CONVERT THE VALUE FORM THE
                   cccCCCCHRR FORMAT INTO TO THE CCCCHHHHRR FORMAT.)

PTR ..... POINTER TYPE
RBA ..... RBA OF POINTER IN ERROR

ERROR MESSAGES:

NUMBER ... ERROR MESSAGE NUMBER
DESCRIPTION .. SHORT DESCRIPTION OF ERROR

***** SNAP OF BLOCKS CONTAINING ERRORS, WHERE TGT AND PTR TO TGT ARE NOT IN THE SAME BLOCK

      1. USE BLOCK DUMP OPTION BY SPECIFYING BLOCKDUMP PARAMETER IN DATABASE STATEMENT
      2. OS UTILITIES
      3. VSAM ACCESS METHOD SERVICES

***** CTL RECORDS ARE WRITTEN TO BLKMAP PROCESS FOR:

      1. ALL POINTERS POINTING TO A SEG CONTAINING BAD POINTERS
      2. ALL POINTERS POINTING TO THE SEG WHICH IS POINTED AT BY A BAD POINTER
      3. ALL POINTERS POINTING TO A SEG WITH BAD CTR VALUES

***** PSEUDO ERROR MESSAGES MAY BE GENERATED WHEN INDEX OVERFLOW DATA SET PTR'S ARE VALIDATED/EVALUATED

CAUSE: DL/I DOES NOT SET THE DELETE FLAG IN INDEX OVERFLOW RECORD AFTER ROOT DELETION
       THESE RECORDS ARE LOCATED BY THE PTR CHECKER AS 'ACTIVE', ALTHOUGH THEY ARE INACTIVE TO DL/I