A fix is available
APAR status
Closed as program error.
Error description
HDPC incorrectly issues MSGFABP2023E and MSGFABP2024E on the following conditions: 1. HDPC runs for an HDAM or a HIDAM database and its associated index databases. 2. HASH=NO and IXKEYCHK=YES are specified in the PROCCTL data set. 3. The HDAM or HIDAM database uses OSAM access method and the database data set has an even-length block size. 4. The HDAM or HIDAM database is used with the following two kind of index databases: 1). A HIDAM primary index, or a secondary index using a direct pointer(The index target segment and the index source segment are the same segment.) 2). A secondary index using a symbolic pointer, or a secondary index using a direct pointer(The index target segment and the index source segment are different segments.) 5. Some index source segments are split into the prefix and the data portions. 6. The prefix and the data portions reside in blocks that are beyond the 4 GB and they do not reside in the same block or the adjacent blocks.
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: IBM IMS High Performance Pointer Checker for * * z/OS Version 3 Release 1 (FMID=HPC2310) * * users who run HD Pointer Checker (HDPC) in * * stand-alone (FABPMAIN) jobs. * **************************************************************** * PROBLEM DESCRIPTION: MSGFABP2023E and MSGFABP2024E are * * wrongly issued when running HDPC with * * HASH=NO and IXKEYCHK=YES. * **************************************************************** * RECOMMENDATION: Apply the maintenance for this APAR. * **************************************************************** HDPC incorrectly issues MSGFABP2023E and MSGFABP2024E when the following conditions are met: 1. HDPC runs for an HDAM or HIDAM database and its associated index databases. 2. HASH=NO and IXKEYCHK=YES are specified in the PROCCTL data set. 3. The HDAM or HIDAM database uses OSAM access method and the database data set has an even-length block size. 4. The HDAM or HIDAM database is used with the following two kind of index databases: 4-1. A HIDAM primary index, or a secondary index using a direct pointer(The index target segment and the index source segment are the same segment.) 4-2. A secondary index using a symbolic pointer, or a secondary index using a direct pointer(The index target segment and the index source segment are different segments.) 5. Some index source segments are split into the prefix and the data portions. 6. The prefix and data portions reside in blocks that are beyond 4 GB and they do not reside in the same block or the adjacent blocks.
Problem conclusion
The FABPUGET module has been modified to fix the error.
Temporary fix
Comments
APAR Information
APAR number
PI31407
Reported component name
IMS POINTER CHE
Reported component ID
5655E0900
Reported release
310
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-12-11
Closed date
2014-12-22
Last modified date
2015-02-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI24092
Modules/Macros
FABPUGET
Fix information
Fixed component name
IMS POINTER CHE
Fixed component ID
5655E0900
Applicable component levels
R310 PSY UI24092
UP15/01/06 P F501
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":"3.1.0"}]
Document Information
Modified date:
03 October 2020