A fix is available
APAR status
Closed as new function.
Error description
HD Pointer Checker has added the following functions on the single-step HASH Checking invoked from HPIC: - Accepting secondary indexes in HPIC HASH Checking and checking the number of index pointer segments. If the index has direct pointers, total RBAs of direct pointer are also to be checked. - Checking the number of LC segments that have symbolic LP PTRs - Checking the number of paired LC segments linked by " " a bidirectional physically paired relationship. . This new function has the following restrictions: - It is only available when HPPC runs with HPIC V3 (HP Image Copy Version 3). - It is not available in the multiple-step HASH Checking. - It is not available when HPPC runs separately from HPIC V3. - It is not available when Image Copy Extensions (ICE) is used.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: IBM IMS High Performance Pointer Checker for * * z/OS Version 2 Release 1 (FMID=HPC2210) * * users invoking HASH checking via * * IMS High Performance Image Copy * * Version 3 Release 1(FMID=H1J0310). * **************************************************************** * PROBLEM DESCRIPTION: By the maintenance provided by this * * APAR, IMS High Performance Pointer * * Checker for z/OS Version 2 Release 1 * * is enabled to support a secondary index * * database on the single-step HASH * * Checking invoked from IMS High * * Performance Image Copy Version3 * * Release1(FMID=H1J0310). * **************************************************************** * RECOMMENDATION: Apply the maintenance for this APAR. * **************************************************************** HD Pointer Checker is added the following functions on the single-step HASH Checking invoked from IMS High Performance Image Copy (HPIC) Version 3: - Secondary index database support - Symbolic LP pointers support - Bidirectional physically paired logical relationship support NOTE ==== These new functions have the following restrictions: - They are only available when HPPC runs with HPIC V3 (HP Image Copy Version 3). - They are not available in the multiple-step HASH Checking. - They are not available when HPPC runs separately from HPIC V3. - They are not available when Image Copy Extensions (ICE) is used. - They are not available only for non-HALDB. A PSINDEX database cannot be checked. The symbolic LP pointers and the bidirectional physically paired logical relationship are not verified for HALDB. Descriptions ============ - Secondary index database support - The secondary index database indexes a HDAM, HIDAM, or HISAM database are verified by the following two checking - the number of pointer segments is checked with the number of the source segments. - the sum of RBA values in pointer segments is checked with the sum of RBA of the target segments. - There is no special keyword to activate the secondary index database checking and just specify HDPC=Y to the secondary index database in the ICEIN control statement. - Consideration for the secondary index database support: - If a secondary index database maintenance exit routine is defined to the source segment, store the load module in the IMS2 DD data set. If no load module is in the IMS2 DD data set, only the statistics report are printed but no pointer segment is checked - Only the statistics report are printed but no pointer segment is checked for one of the following conditions: - A segment edit/compression exit routine and a sparse indexing are defined to the source segment. - The source segment is a variable length and a segment edit/compression exit routine is defined to it. - Some of the source segments are suppressed, split to prefix and data portions, and physically deleted. - The sum of RBA values in pointer segments is checked with the sum of RBA of the target segments when one of the following conditions is satisfied: - The source segment equals to the target segment. - The index target segment is a parent of the source segment and the source segment has PP pointer. However, if the source segment is split into the prefix and data and sparsing indexing is defined to the source segment, only the number of pointer segment is checked. The RBA values are not checked. - Symbolic LP pointers support - Before this APAR, only the number of logical children that have direct pointers was checked. The number of logical children having symbolic pointers is checked with the counter information in logical parent segment prefix. - The logical parents in a HDAM, HIDAM, or HISAM database are verified. - Bidirectional physically paired logical relationship support - The number of logical child segments is checked with the number of paired segments related by "Bidirectional physically paired logical relationship". - The logical child segments in a HIDAM, HDAM or HISAM database are verified.
Problem conclusion
Temporary fix
Comments
Documentation Changes: The documentation is modified as follows: ============================================================== IMS High Performance Image Copy for z/OS, V3R1, User's Guide (SC18-7617-00) ============================================================== 7.0 Using the Full-Function Database HASH Check Option 7.1 Single-Step HASH check 7.1.2 Restrictions 7.1.2.1 Restrictions on both Single-Step and Multiple-Step HASH Checks -------------------------------------------------------------- - The HASH check option does not provide the ability to analyze databases of the following types: Delete: - A secondary index database - A HISAM database that has no logical relation to an HD database Add: - The HASH check option does not provide the ability to analyze databases of the following types: | - A SHISAM database | - A SHISAM database | - A PSINDEX database - A PHIDAM primary index database Note: If you need to analyze a PHIDAM primary index database, use the High Performance Pointer Checker HD Pointer Checker utility. -------------------------------------------------------------- 7.0 Using the Full-Function Database HASH Check Option 7.1 Single-Step HASH check 7.1.2 Restrictions 7.1.2.2 Restrictions for Single-Step HASH Check -------------------------------------------------------------- Add: - IMS-compatible JCLs have no single-step HASH check function. - In an image copy job, the maximum number of tasks for a HASH check 99. | - A HISAM database cannot be checked. However, if a HISAM | database has logical relation or indexed by a secondary | indexdata base, it can be checked. | - Consideration for the secondary index database support | is as follows: | - If a secondary index database maintenance exit routine | is defined to the source segment, store the load module | in the IMS2 DD data set. | If no load module is in the IMS2 DD data set, only | the statistics report are printed but no pointer segment | is checked | - Only the statistics report are printed but no pointer | segment is checked for one of the following conditions: | - A segment edit/compression exit routine and a sparse | indexing are defined to the source segment. | - The source segment is a variable length and a segment | edit/compression exit routine is defined to it. | - Some of the source segments are suppressed, split to | prefix and data portions, and physically deleted. | - The sum of RBA values in pointer segments is checked with | the sum of RBA of the target segments when one of | the following conditions is satisfied: | - The source segment equals to the target segment. | - The index target segment is a parent of the source | segment and the source segment has PP pointer. | However, if the source segment is split into the prefix | and data and sparsing indexing is defined to the source | segment, only the number of pointer segment is checked. | The RBA values are not checked. -------------------------------------------------------------- 7.0 Using the Full-Function Database HASH Check Option 7.1 Multiple-Step HASH check 7.2.2 Restrictions 7.2.2.1 Restrictions for Multiple-Step HASH check -------------------------------------------------------------- Add: - To process HALDB, run program FABPHCTL (by specifying PGM=DFSRRC00) in the DLI region. Specify Y for DBRC. // EXEC PGM=DFSRRC00, // PARM='DLI,FABPHCTL,psbname,,,,,,,,,,,Y,N' | - A secondary index database cannot be checked. | - A HISAM database cannot be checked. However, if a HISAM | database has logical relation to HD database, it can be | checked. - The multiple-step HASH check cannot be run in a parallel image copy process. ============================================================== IMS High Performance Pointer Checker for z/OS, V2R1, User's Guide Vol.1 (SC18725700) ============================================================== APPENDIX1.13 Messages and Codes APPENDIX1.13.1 HD Pointer Checker APPENDIX1.13.1.3 Messages -------------------------------------------------------------- Following messages are added |FABP1503E nnn ERRORS FOUND IN HASH CHECK OF DB: dbdname | PID: xxxxx DSG: xx TIME=hh.mm.ss |Explanation: | The HASH Check process of data set group xx in partition ID | xxxxx, database dbdname has completed at hh.mm.ss. and nnn | errors were found. | The nnn errors are issued during the HASH evaluation process. | Errors issued during scan processes are reported in separate | messages. |System Action: Processing continues. |Programmer Response: None. |Problem Determination: None. |FABP1995E MISMATCH BETWEEN THE NUMBERS OF PAIRED SEGMENTS | (DB: dbdname1 SEGMENT: segment1 AND DB: dbdname1 | SEGMENT: segment2) |Explanation: | The database is corrupted . The number occurrences of logical | child segment is not equal to the occurrences of paired | logical child segment in physically paired bidirectional | logical relationship. | This message is issued for every physically paired | bidirectional logical relationship. |System Action: Processing continues. |Programmer Response: | Repair the database, and rerun the HD Pointer Checker job. |Problem Determination: See Appendix B. |FABP1996E COUNTER VALUE IN LP (SEGMENT: segment) IS NOT EQUAL | TO THE NUMBER OF LOGICAL CHILDREN |Explanation: | The database is corrupted. The actual number of logical child | segments is not equal to the counter in the logical parent. |System Action: Processing continues. |Programmer Response: | Repair the database, and rerun the HD Pointer Checker job. |Problem Determination: See Appendix B. |FABP1997E MISMATCH BETWEEN LP POINTERS AND LOGICAL PARENT RBA | VALUES (DB: dbdname SEGMENT: segname) |Explanation: | The database is corrupted. The sum of direct LP pointers is | not consistent with the counter value and RBA value. |System Action: Processing continues. |Programmer Response: | Repair the database, and rerun the HD Pointer Checker job. |Problem Determination: See Appendix B. |FABP1998E THE NUMBER OF INDEX SOURCE SEGMENTS (DB: dbname | SEGMENT: segment) IS NOT EQUAL TO THE NUMBER OF | INDEX POINTER SEGMENTS |Explanation: | The database is corrupted. The number of index source | segments is not equal to the number of index pointer | segments. NUMBER OF INDEX SOURCE means the number of index | source segments excluding the number of segments that meet | the conditions of suppressing index pointer segment. |System Action: Processing continues. |Programmer Response: | Repair the database, and rerun the HD Pointer Checker job. |Problem Determination: See Appendix B. |FABP1999E MISMATCH BETWEEN INDEX POINTERS AND TARGET RBA | VALUES (DB: dbname SEGMENT: segment) |Explanation: | The database is corrupted. The pointer values in the index | pointer segment are not equal to the target segment RBAs. |System Action: Processing continues. |Programmer Response: | Repair the database, and rerun the HD Pointer Checker job. |Problem Determination: See Appendix B. |FABP2007E ERRORS WERE DETECTED IN SECONDARY INDEX RELATIONSHIP |Explanation: | Errors were detected in the HASH check of secondary index | relationship. |System Action: Processing continues. |Programmer Response: | Run the HD Pointer Checker job to check the error in detail. |Problem Determination: None. |FABP4025W SECONDARY INDEX DB: dbdname CANNOT BE CHECKED WITH | HASH=YES |Explanation: | The pointer of the secondary index database cannot be | checked for one of the following reasons: | - A secondary index database maintenance exit routine | is defined to the source segment, but no load module | is in the IMS2 DD data set. | - A segment edit/compression exit routine and a sparse | indexing are defined to the source segment. | - The source segment is a variable length and a segment | edit/compression exit routine is defined to it. | - Some of the source segments are suppressed, split to | prefix and data portions, and physically deleted. | The secondary index database is scanned, but the index | pointer is not checked. Only statistics data is written in a | report. |System Action: Processing continues. |Programmer Response: | If you do not need to check the secondary index nor to have | the statistics data, This message can be ignored. ============================================================== Reports: (Single-step HASH Checking of HPIC V3 hash check) If a secondary index database is checked, the following reports are printed. (STATIPRT data set) Separator Page for DB/DSG (VALIDPRT data set) SCAN OF Index Database Report If a secondary index database is checked, the following reports are changed. (EVALUPRT data set) HASH Evaluation Report (SUMMARY data set) HD Pointer Checker Summary Report
APAR Information
APAR number
PQ85897
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
2004-03-11
Closed date
2004-03-26
Last modified date
2004-04-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UQ86645
Modules/Macros
FABPDATE FABPDRT FABPHEVL FABPHEXM FABPHINI FABPHPSD FABPHPUT FABPHRCK FABPHSDA FABPHSHI FABPHSIX FABPHTRM FABPIST FABPLBLD FABPLBLX FABPLINK FABPMSGS FABPSIT FABPSSUP FABPSTS FABPSUMM FABPUHDR HPC2210J
| SC18725700 | SC18761700 |
Fix information
Fixed component name
IMS POINTER CHE
Fixed component ID
5655E0900
Applicable component levels
R210 PSY UQ86645
UP04/03/29 P F403
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.
[{"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:
03 October 2020