A fix is available
APAR status
Closed as program error.
Error description
After the Partition DBD name and the Root key of the root segment that exists in the partition are entered in the Initial selection panel for PHIDAM and PHDAM databases (FABZPS1P), DBRF issues FABZ033I that shows the wrong partition ID and partition name, and then issues FABZ028E incorrectly. FABZ033I: Key found in partition # nnnnn (DBD=partname). FABZ028E: Invalid key specified or key not found. This error occurs when the sequence of partition names sorted in EBCDIC order is not the same as that sorted in partition high key order.
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: IBM IMS Database Repair Facility (DBRF) for * * z/OS Version 3 Release 1 (FMID=H22K310) * * users who repair a PHDAM or PHIDAM database * * by using the Repair Facility interactively. * **************************************************************** * PROBLEM DESCRIPTION: MSGFABZ033I with the wrong partition ID * * and name and MSGFABZ028E incorrectly * * when the interactive DBRF processes a * * PHDAM or PHIDAM database is processed. * **************************************************************** * RECOMMENDATION: Apply the maintenance for this APAR. * **************************************************************** When you try to repair a PHDAM or PHIDAM database by using IMS Database Repair Facility (DBRF) interactively and you enter the Partition DBD name and the Root key of the root segment existing in the partition in the Initial selection panel for PHIDAM and PHDAM databases (FABZPS1P), DBRF issues MSGFABZ033I that shows the wrong partition ID and partition name and issues MSGFABZ028E incorrectly: FABZ033I: Key found in partition # nnnnn (DBD=partname). FABZ028E: Invalid key specified or key not found. This error occurs when any of the following conditions is met: - The sequence of the partition names of the database that are sorted in EBCDIC order is not the same as the sequence of the partition names that are sorted in partition high key order. - The the Root key is entered as the hex character string.
Problem conclusion
FABZPRO2 and FABZMAIN have been modified to fix the error. 310Y FABZMAIN FABZPRO2
Temporary fix
Comments
APAR Information
APAR number
PM47684
Reported component name
IMS DATABASE RE
Reported component ID
5655E0300
Reported release
310
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2011-09-13
Closed date
2011-09-26
Last modified date
2011-10-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
010PC2 UK72267 010PC2
Modules/Macros
FABZMAIN FABZPRO2
Fix information
Fixed component name
IMS DATABASE RE
Fixed component ID
5655E0300
Applicable component levels
R310 PSY UK72267
UP11/09/28 P F109
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.
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"3.1.0","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
14 December 2020