IBM Support

Updates to IMS High Performance Pointer Checker for z/OS V3.1 User's Guide

Product Documentation


Abstract

Updates that apply to IMS High Performance Pointer Checker for z/OS V3.1 User's Guide (SC19-2401-04).

Content

The most recent updates appear at the top of the list.


Update 6

Date of change: June 2019

Change description: User's guide updates.

Topics: Changes apply to multiple topics.

------------------------------

Topic: HD Pointer Checker utility > Using the HD Pointer Checker processor > Restrictions and considerations > Restrictions when using image copy data sets as input

This topic has been updated as follows:

The following restrictions apply when the input to the HD Pointer Checker is an image copy data set.

  • HD Pointer Checker accepts the following types of image copy as input to the database data set:
    • A batch image copy
    • A compressed batch image copy taken with IMS HP Image Copy
    • An SMSNOCIC type image copy and an SMSOFFLC type image copy (Exception: SMSNOCIC type image copy of an encrypted database data set is not supported.)
    • A Fast Recovery image copy taken with IMS HP Image Copy Version 4 or later
  • HD Pointer Checker can process the following image copies. However, if the database is updated while image copy is being taken, HD Pointer Checker might detect pointer errors even if there are actually no pointer errors.
    • An online image copy
    • A concurrent image copy taken by a batch image copy or IMS HP Image Copy
    • An SMSCIC type image copy and an SMSONLC type image copy (Exception: SMSCIC type image copy of an encrypted database data set is not supported.)
  • HD Pointer Checker does not support a Database Image Copy 2 (IC2) image copy data set that contains multiple image copies. For more information about the online image copy and the concurrent image copy, see HD Pointer Checker online considerations.

------------------------------

Topic: HD Pointer Checker utility > Using the HD Pointer Checker processor > Input > FABPMAIN PROCCTL data set > DATABASE statement

This topic has been updated as follows:

Keywords

...

DATASET=

Specifies the type of input database.
Abbreviations DS for DATASET, and IC and ICOPY for IMAGECOPY can be used.
REAL
Specifies that your input database is a real database. DATASET=REAL is the default value.
IMAGECOPY
Specifies that your input database is an image copy. The image copy can be one of following types:
  • A batch image copy created by the IMS Database Image Copy utility (RECFM=VB)
  • A compressed batch image copy created by IMS HP Image Copy (RECFM=VB)
  • An SMSNOCIC type image copy created by the IMS Database Image Copy 2 utility (RECFM=U)
    HD Pointer Checker identifies the image copy type by checking its record format (RECFM).
When the input database is an image copy, you must specify this parameter even if TYPE=CHECK or BLKMAP is specified.
For the types of image copies that HD Pointer Checker accepts as input, see "Restrictions when using image copy data sets as input".

Notes:
  • If the image copy supplied as an input is any of the following types, HD Pointer Checker identifies the type of image copy by checking its record format (RECFM):
    • A batch image copy created by the IMS Database Image Copy utility (RECFM=VB)
    • A compressed batch image copy created by IMS HP Image Copy (RECFM=VB)
    • An SMSNOCIC type image copy created by the IMS Database Image Copy 2 utility (RECFM=U)
  • An SMSNOCIC type image copy has no DBD name or DD name information in the header record. Therefore, HD Pointer Checker cannot verify the image copy with it. The HD Pointer Checker issues the message FABP1365I with the name of the dumped data set name in the image copy so that you can verify the image copy with it.


Update 5
Date of change: February 2019
Change description: Documentation changes by APAR PH07469. This APAR adds a new keyword (GROUPDIGITS) for the HD Pointer Checker utility to enable or disable digit grouping for numeric values printed in HD Pointer Checker reports.
Topics: Changes apply to multiple topics.

------------------------------

Topic: HD Pointer Checker utility > Using the HD Pointer Checker processor > Input > FABPMAIN PROCCTL data set > PROC statement

A new keyword, GROUPDIGITS has been added after the SEP keyword, as follows:

Syntax

image-20190220133950-1

Keywords
...
GROUPDIGITS=
Specifies whether to enable or disable digit grouping for the numeric values printed in Database Statistics reports and Partition Statistics reports. This option can be specified when TYPE=ALL or TYPE=SCAN is specified.
YES: Enables digit grouping and uses comma (,) as the digit grouping symbol. For example, a value of 1,000,000 is printed as 1,000,000.
GROUPDIGITS=YES is the default value.
(NO,DBSTAT): Disables digit grouping. For example, a value of 1,000,000 is printed as 1000000. This option allows to print numeric values that are greater than the maximum value a report field can display when digit grouping is enabled.

------------------------------

Topic: HD Pointer Checker utility > Using the HD Pointer Checker processor > Output > STATIPRT data set > Separator page for DB/DSG reports

Report example has been replaced with the following figure:

Figure. STATIPRT: Separator page for DB/DSG reports (General format)

(Figure 53 in PDF)

image-20190220134320-2

------------------------------

Topic: HD Pointer Checker utility > HD Pointer Checker Site Default Generation utility > FABPTGEN PROCCTL data set >  PROC statement

New keyword, GROUPDIGITS, has been added to the following table:

PROC statement

This statement is required. The following table shows the keywords that are available for this statement.

Table. Keywords available for the site default in the PROC statement

(Table 30 in PDF)

Keyword System default value of HD Pointer Checker Can specify site default value?
... ... ...
SEP ... ...
GROUPDIGITS YES Yes
... ... ...

------------------------------

Topic: Troubleshooting > Messages and codes > HD Pointer Checker messages and codes >  HD Pointer Checker messages

The following new message has been added:

FABP2165W '*OVERFLOW' INDICATES THAT THE VALUE EXCEEDED THE MAXIMUM VALUE THAT CAN BE DISPLAYED.

Explanation: One or more numeric values in HD Pointer Checker reports exceeded the maximum value that can be displayed in the report fields. Those values are not printed in the report but instead printed as "*OVERFLOW" in the corresponding report fields.
System action:  Processing continues.
User response: To print large values, specify GROUPDIGITS=(NO,DBSTAT) for the PROC statement in the PROCCTL data set and rerun the job. This option disables digit grouping and allows to print values that are greater than the maximum value a report field can display when digit grouping is enabled.



Update 4

Date of change: October 2018

Change description: User's guide update.

Topic: DB Historical Data Analyzer utility > JCL examples for DB Historical Data Analyzer > Example 5: Creating the predefined flat records

JCL example has been replaced with the following figure:

image-20181031101708-1

Figure. Export utility example: Creating predefined flat records

(Figure 234 in PDF)


Update 3

Date of change: September 2018

Change description: Documentation change by APAR PH02047.

Topic: HD Pointer Checker utility > Using the HD Pointer Checker processor > Input > FABPMAIN PROCCTL data set > PROC statement

A restriction item has been added to the explanation of the SENSOR_HOME keyword as follows:

...

SENSOR_HOME=

Specifies whether to collect the data elements that are related to root segment distribution and store them in the Sensor Data repository of IMS Tools KB.

If SENSOR=YES is not specified, this keyword is ignored.

...

Restrictions:

  • If the key compression option of the Segment Edit/Compression exit routine is specified for the root segment, these data elements are not collected even when SENSOR_HOME=YES is specified.
  • If you specify RMNAME=(rand,rap,0,bytes) or if you omit the third operand of the RMNAME parameter in the DBD macro, the number of root addressable area (RAA) blocks is defined as zero in the HDAM or PHDAM DBD. In this case, these data elements are not collected even when SENSOR_HOME=YES is specified.


Update 2

Date of change: August 2018

Change description: Documentation changes by APAR PI93975. This APAR enhances the HD Tuning Aid utility to support IMS-managed ACBs.

Topics: Changes apply to multiple topics.

Topic: Introduction and product setup > Configuring IMS HP Pointer Checker > Processing environment

The HD Tuning Aid utility section under Software requirements has been updated as follows:

Software requirements

...

HD Tuning Aid utility

  • DFSORT (Data Facility Sort), which is a part of z/OS, or a functionally equivalent sort and merge program is required.
  • If the IMS management of ACBs is enabled, IBM IMS Tools Base for z/OS, Version 1 Release 6 or later must be installed.

------------------------------

Topic: HD Tuning Aid utility > Overview of HD Tuning Aid >  Program structure

This topic has been updated as follows:

...

If a HALDB is processed, FABTROOT program needs to run under the IMS batch region controller. FABTROOT program must be run under the IMS batch region controller, if a user randomizing routine requires to access IMS control blocks for non-HALDB.

If any of the following conditions are met, the FABTROOT program must be run under the IMS batch region controller:

  • The database a HALDB.
  • The database is a non-HALDB and a user randomizing routine requires to access IMS control blocks.
  • The IMS management of ACBs is enabled

Otherwise, both programs (FABTROOT and FABTRAPS) run as standard batch jobs.

------------------------------

Topic: HD Tuning Aid utility > Overview of HD Tuning Aid >  Data flow

This topic has been updated as follows:

Data flow for non-HALDB

Figure. HD Tuning Aid data flow for non-HALDB 

(Figure 155 in PDF)

image-20180803093916-4

The HD Tuning Aid reads control statements from the CTL data set, root keys from a data set that is created by the SCAN process of HD Pointer Checker, and information about processing databases from the DBD/PSB library of IMS or from the IMS directory. The process consists of three JOB steps. Some of the reports are generated by the first step. To create the rest of the reports, the first step writes data into a work data set, which is passed to DFSORT utilities to be sorted and fed to the last step.

Data flow for HALDB

...

Figure. HD Tuning Aid data flow for HALDB

(Figure 156 in PDF)

fabpta02 June2018

------------------------------

Topic: HD Tuning Aid utility > Using HD Tuning Aid >  Restrictions and considerations

This topic has been updated as follows:

Certain restrictions and considerations apply to using the HD Tuning Aid utility.

...

Your randomizing routine may have its own restrictions that can affect the way you must run HD Tuning Aid. It must be capable of processing the key values that you provide as input. If your randomizer refers to IMS control blocks, you are required to run HD Tuning Aid under the IMS batch region controller.

If the IMS management of ACBs is enabled, you must run HD Tuning Aid under the IMS batch region controller.

Keep in mind the following points when processing HALDBs:

...

------------------------------

Topic: HD Tuning Aid utility > Using HD Tuning Aid > Job control language > FABTROOT JCL

The following two tables have been updated as follows:

Table. FABTROOT DD statements for all runs

(Table 39 in PDF)

DDNAME Use Format Need
IMS Input PDS Optional
... ... ... ...

Table. Additional FABTROOT DD statements for IMS runs

(Table 40 in PDF)

DDNAME Use Format Need
... ... ... ...
DFSHDBSC Input PDS

Optional

Explanations for the EXEC statement and some DD statements have been updated as follows:

EXEC

If you are running this program as a standard MVS batch program, code as follows:

...

The following subparameters can be specified for PARM:

...

DBRCGRP=...

Additional requirement when the IMS management of ACBs is enabled

When the IMS management of ACBs is enabled, run HD Tuning Aid under the IMS batch region controller and specify the DFSDF= parameter for the PARM= parameter. The value must be the 3-character suffix (xxx) of the DFSDFxxx member (in IMS.PROCLIB data set) that enables IMS-managed ACBs.

For example:

//        EXEC PGM=DFSRRC00,
//             PARM='DLI,FABTROOT,psbname,,,,,,,,,,,dbrc,N,  
//             ,,,,,,,,,,,,DFSDF=xxx'

If you specify the library that contains the Catalog Definition exit routine (DFS3CDX0) in the STEPLIB DD statement, you do not need to specify the DFSDF=xxx parameter.

IMS DD

This required input data set is a library (partitioned data set) that contains your PSB and DBD load modules. It must contain all DBDs that are referenced (either directly or indirectly) by your PSB. If your PSB and DBDs are not in the same library, all appropriate libraries must be concatenated.

If the IMS management of ACBs is enabled, you do not need to specify this DD statement.  If the HD Tuning Aid utility finds this DD statement, the utility ignores the statement.

STEPLIB DD

This optional input data set is a library (partitioned data set) containing HD Tuning Aid modules. If a partition selection exit is defined to your input PHDAM or PHIDAM database in the RECON data sets, STEPLIB data set must contain the partition selection exit module.

When the utility runs as a standard MVS batch program, this statement defines the IMS HP Pointer Checker production library (required).

When the utility runs as an IMS batch program, this statement defines the following input data sets:

  • IMS HP Pointer Checker production library (required)
  • IMS RESLIB  (required)
  • The library that contains the DFSMDA members for dynamic allocation (optional)
  • The library that contains the partition selection exit routine if a partition selection exit is defined to your input PHDAM or PHIDAM database in the RECON data sets
  • IMS Tools Base library (SGLXLOAD) of IMS Tools Base Version 1 Release 6 or later if the IMS management of ACBs is enabled
  • The library that contains the Catalog Definition exit routine (optional)

...

PROCLIB DD

This statement defines the library that contains all IMS-generated cataloged procedures and jobs. This statement is applicable only if you are running this program as an IMS batch program, in which case it is optional. If it is omitted, a warning message may be issued by IMS. You may ignore this warning message.

If you specify the DFSDF=xxx subparameter on the EXEC PARM parameter, you must specify the IMS PROCLIB data set that contains the DFSDFxxx member.

DFSHDBSC DD

This optional input DD statement points to the IMS catalog partition definition data set.  When the IMS management of ACBs is enabled and an IMS catalog database is not registered in the RECON data set, you must specify the IMS catalog partition definition data set in which the IMS catalog database is defined. If you omit this DD statement, the DFSHDBSC data set is allocated dynamically by the DFSMDA member.

------------------------------

Topic: HD Tuning Aid utility > Using HD Tuning Aid > Output > FABTRAPS PR9X data set > Assigned Roots per Block report

Report example has been updated as follows:

Figure. FABTRAPS: Assigned Roots per Block report

(Figure 169 in PDF)

IMS HIGH PERFORMANCE POINTER CHECKER FOR z/OS - HDTA           "ASSIGNED ROOTS PER BLOCK REPORT"                         PAGE:     1
5655-U09                                                   DATE: 05/10/2018  TIME: 15.21.06                         FABTRAPS - V3.R1


***  DBNAME: TPFOH1    ***

             DBDNAME................. TPFOH1                  DIRECT ALGORITHM NAME...     (PART)
             DATABASE ORGANIZATION...    PHDAM                HIGH BLOCK NUMBER.......     (PART)
             ACCESS METHOD...........     VSAM                RAPS PER BLOCK..........     (PART)
             BLOCK SIZE..............   (PART)                TOTAL RAPS..............     (PART)
             PARTITION SELECTION EXIT NAME
                                .....    N / A

             (PART) : NO VALUE ASSIGNED BECAUSE OF HIGH AVAILABILITY LARGE DB

FOLLOWING PARTITION REPORTS ARE PRINTED IN ORDER OF PARTITION SELECTION

***  PARTITION NAME: TPFOH1A  ***

             PARTITION ID............        1                DIRECT ALGORITHM NAME...   DFSHDC40
             BLOCK SIZE..............      512                HIGH BLOCK NUMBER.......       4500
                                                              RAPS PER BLOCK..........          1
             PARTITION HIGH KEY............                   TOTAL RAPS..............       4500
             X'FFFFFFFFFFFFFFFF'

COUNT OF 0-35 REPRESENTED AS FOLLOWS:
  SYMBOL:     1  2  3  4  5  6  7  8  9  A  B  C  D  E  F  G  H  I  J  K  L  M  N  O  P  Q  R  S  T  U  V  W  X  Y  Z
  COUNT : 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35
COUNT GREATER THAN 35 =  *
END OF DATA BLOCKS    =  $

         EACH ENTRY IN THE TABLE BELOW REPRESENTS THE NUMBER OF ROOTS THAT HAVE RANDOMIZED TO THE CORRESPONDING BLOCK
                                                                -----
 BLOCK #  0........1.........2.........3.........4.........5.........6.........7.........8.........9.........0
          1234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890

       0 | 1 13113232531442232111 12116322222123212 421 332232515143232312511323131411421341214511131214333134
     100 |5 5432114 34323242 113117333122223232124143516 21343252354311241245233231132123542537 222223 2123352
     200 |11433 24223 33413 23251322132124222112163212334 12 321322241 1325212 121115  1263  15532511241124114

------ For formatting purposes, several lines have been deleted.------

    4300 |54231311133362143 22524 13623225232116313431236 34255332323333  3144151 23334 2122123 23 51732232242
    4400 |11 344  44134114423221434323241121 52131 431611211357234246222512332335211 24 26232 162436245341333
    4500 |$

          COUNT OF BLOCKS WITHOUT ROOTS        =      410          COUNT OF BLOCKS WITH MORE THAN 35 ROOTS =        0

          AVG. COUNT OF ROOTS PER ACTIVE BLOCK =      2.6          MAX. COUNT OF ROOTS IN ONE BLOCK        =        9

FABT3601I         70 TYPE K RECORDS PROCESSED

FABT3602I         70 TYPE R RECORDS CREATED

FABT3525I PROCESSING COMPLETED FOR THIS DATABASE

------------------------------

Topic: HD Tuning Aid utility >  JCL examples for HD Tuning Aid

The following new topic has been added:

Example 7: Running HD Tuning Aid in an IMS-managed ACBs environment


This example JCL shows how to run HD Tuning Aid to evaluate data distribution of databases when the IMS management of ACBs is enabled.

Points to be considered:

  • The HD Tuning Aid utility must be executed under the IMS batch region controller.
  • Specify the DFSDF=CAT parameter for the PARM= parameter on the EXEC statement. In this example, it is assumed that the DFSDFCAT member enables IMS-managed ACBs and that this member exists in the data set (HPS.TEST.PROCLIB) that is specified to the PROCLIB DD.
  • The IMS Tools Base library (SGLXLOAD) of IMS Tools Base Version 1 Release 6 or later is specified on the STEPLIB DD statement.
  • In this example, it is assumed that the KEYSIN data set (HPS.TEST.KEYSIN) has been created in an earlier HD Pointer Checker job and contains root keys for the databases to be analyzed.
//STEP1   EXEC PGM=DFSRRC00,                                        
//     PARM='DLI,FABTROOT,P33J001G,,,,,,,,,,,Y,N,,,,,,,,,,,,DFSDF=CAT',
//             REGION=1000K,TIME=(,30)                               
//STEPLIB   DD DSN=HPS.SHPSLMD0,DISP=SHR                                
//          DD DSN=ITKBHLQ.SGLXLOAD,DISP=SHR                          
//          DD DSN=IMSVS.RESLIB,DISP=SHR   
//SYSUDUMP  DD SYSOUT=A                                              
//RAPSIN    DD DSN=&&RAPSIN,DISP=(,PASS,DELETE),                     
//             UNIT=SYSDA,SPACE=(CYL,(10,10)),                         
//             DCB=BLKSIZE=8400                                      
//IMS2      DD DSN=IMSVS.RESLIB,DISP=SHR                                 
//IEFRDER   DD DUMMY,DCB=BLKSIZE=1408                                
//DFSRESLB  DD DSN=IMSVS.RESLIB,DISP=SHR                                 
//DFSVSAMP  DD DSN=HPS.SHPSSAMP(FABPVSAM),DISP=SHR                      
//PR8       DD SYSOUT=A,DCB=BLKSIZE=6118                             
//PR10      DD SYSOUT=A,DCB=BLKSIZE=6118                             
//KEYSIN    DD DSN=HPS.TEST.KEYSIN,DISP=OLD           
//PROCLIB   DD DSN=HPS.TEST.PROCLIB,DISP=SHR                                 
//RECON1    DD DSN=HPS.TEST.RECON1,DISP=SHR                               
//RECON2    DD DSN=HPS.TEST.RECON2,DISP=SHR                               
//RECON3    DD DSN=HPS.TEST.RECON3,DISP=SHR  
//*-------------------------------------------------------------     
//STEP2   EXEC PGM=SORT,PARM='',COND=(0,LT,STEP1)                    
//SORTIN    DD DSN=*.STEP1.RAPSIN,DISP=(OLD,DELETE,DELETE),          
//             DCB=(LRECL=42,BLKSIZE=8400,RECFM=FB)                  
//SORTOUT   DD DSN=&&KEYSOUT,DISP=(,PASS,DELETE),                    
//             UNIT=SYSDA,SPACE=(CYL,(10,10)),                         
//             DCB=(LRECL=42,BLKSIZE=8400,RECFM=FB)                  
//SORTWK01  DD UNIT=SYSDA,SPACE=(CYL,(10,10))                          
//SORTWK02  DD UNIT=SYSDA,SPACE=(CYL,(10,10))                          
//SORTWK03  DD UNIT=SYSDA,SPACE=(CYL,(10,10))                          
//SORTWK04  DD UNIT=SYSDA,SPACE=(CYL,(10,10))                          
//SORTWK05  DD UNIT=SYSDA,SPACE=(CYL,(10,10))                          
//SORTWK06  DD UNIT=SYSDA,SPACE=(CYL,(10,10))                          
//SYSOUT    DD SYSOUT=A                                              
//SYSIN     DD DSN=HPS.SHPSSAMP(FABPSORT),DISP=SHR                        
//*-------------------------------------------------------------     
//STEP3   EXEC PGM=FABTRAPS,COND=(0,LT,STEP2)                        
//STEPLIB   DD DSN=HPS.SHPSLMD0,,DISP=SHR     
//SYSUDUMP  DD SYSOUT=A                                              
//PR9       DD SYSOUT=A,DCB=BLKSIZE=6118                             
//PR9X      DD SYSOUT=A,DCB=BLKSIZE=6118                             
//KEYSOUT   DD DSN=*.STEP2.SORTOUT,DISP=(OLD,DELETE,DELETE),         
//             DCB=(LRECL=42,BLKSIZE=8400,RECFM=FB)     

Figure. HD Tuning Aid JCL example: IMS-managed ACBS environment

------------------------------

Topic: Troubleshooting > Messages and codes > HD Tuning Aid messages and codes >  HD Tuning Aid messages

The following new messages have been added:

FABT3580E ERROR RETURNED FROM IMS TOOLS CATALOG INTERFACE (text)


Explanation: HD Tuning Aid received an error return code from the IMS Tools Catalog Interface. text provides additional information:

  •  FUNC=OPEN RC=return_code RSN=reason_code
  •  FUNC=CLOSE RC=return_code RSN=reason_code
  •  FUNC=GET DBD=dbdname RC=return_code RSN=reason_code

return_code and reason_codes are the codes returned from the IMS Tools Catalog Interface.

System action: HD Tuning Aid ends with an abend code of 3580.
User response: See IMS Tools Catalog Interface messages (GEX3xxxx) to determine the cause of the error.

If the function is OPEN, ensure that the SGLXLOAD library of IMS Tools Base Version 1 Release 6 or later is specified on the STEPLIB DD statements. Otherwise, contact IBM Software Support.

---

FABT3581E DBD dbdname IS NOT FOUND IN THE IMS DIRECTORY DATA SETS


Explanation: HD Tuning Aid could not obtain the indicated DBD from the IMS directory data sets.
System action: HD Tuning Aid ends with an abend code of 3581.
User response: Ensure that the high-level qualifier of the bootstrap data set indicated by message FABT3582I is correct and that the DBD identified by dbdname exists in the IMS directory data sets. Then correct the error and rerun the job.


---

FABT3582I HD Tuning Aid is running in an IMS-managed ACBs environment. BSDS HLQ=bsds_hlq


Explanation: HD Tuning Aid is running in an IMS managed ACBs environment and is referring to the database definitions in the IMS catalog directory data set instead of the DBD library. bsds_hlq is the high-level qualifier of the bootstrap data set (BSDS) that is used for this run.
System action: Processing continues.
User response: None. This message is informational.


Update 1

Date of change: July 2018

Change description: Documentation changes by APAR PH00083. This APAR enhances HD Pointer Checker to support secondary index databases with an overflow data set under IMS Database Recovery Facility.

Topics: Changes apply to multiple topics.

------------------------------

Topic: HD Pointer Checker utility > Using the HD Pointer Checker processor > Restrictions and considerations

The following new topic has been added after "Considerations for calling HD Pointer Checker from IMS Database Reorganization Facility":

Restrictions and considerations for calling HD Pointer Checker from IMS Database Recovery Facility


The following restriction and consideration apply when the HD Pointer Checker utility is called from IMS Database Recovery Facility.

  • If HIDAM primary index databases and secondary index databases are built by IMS Index Builder during the IMS Database Recovery Facility job, the word "N/A" is set to the index database data set name fields in the HD Pointer Checker reports. For the data set names, see IMS Index Builder reports.
  • If secondary index databases with an overflow data set are built by IMS Index Builder during the IMS Database Recovery Facility jobs, HASH Check cannot be done for the pointers that point to logical records in the overflow data set.

------------------------------

Topic: HD Pointer Checker utility > Using the HD Pointer Checker processor > Input > FABPMAIN PROCCTL data set > Summary of index database checking

Table "Secondary index of non-HALDB" has been updated as follows:

 Table. Secondary index of non-HALDB

(Table 20 in PDF)

Function ... ... HASH Check option run from IMS Database Recovery Facility
... ... ... ADD PC()
Basic Check ... ...

Yes (Specify the index database or the BLD_SECONDARY() option)

(See notes 1, 3, and 9)

Index Key Check ... ... No
Symbolic Pointer Check ... ... No
Suppressed Segment Check ... ... No

Notes:

1. ...

2. ...

...

9. When secondary index databases with an overflow data set are built by IMS Index Builder during the IMS Database Recovery Facility job, only the following factors are checked by the Basic Check:

  • The numbers of the index source segments and the index pointer segments
  • The values of the pointers that point to the index target segments

Publication Number

SC19-2401-04

Copyright Date

2000, 2018

Original Publication Date

2018-07-25


Cross reference information
Product Component Platform Version Edition
IMS Tools IMS Database Solution Pack z/OS 2.1.0, 2.2.0
IMS Tools IMS Database Utility Solution z/OS 2.1.0

Document information

More support for: IMS Tools

Component: IMS High Performance Pointer Checker

Software version: 3.1.0

Operating system(s): z/OS

Reference #: 0718725

Modified date: 20 June 2019