A fix is available
APAR status
Closed as program error.
Error description
Attempting to retrieve using a key (alphanumeric or hex) will not be accomplish unless the area is specified. Typically, the area is not known but the area is developed by the randomizer and should be used by DBRF and not requested of the user.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: IMS Database Repair Facility -Version 1.1 * * and Version 1.2 * **************************************************************** * PROBLEM DESCRIPTION: Several FP changes, and 1 non-FP * * change. Key access to DEDB will no * * longer require you to specify area. * * Dispaly of RAPS or FSE for DEDB will no * * longer be done.Key access to any DB * * will no longer display the RBA upon * * return to PS1 panel. * **************************************************************** * RECOMMENDATION: * **************************************************************** The current code requires that you enter an area number when doing key access to DEDB. This fix removes this requirement, as the area number is determined from information that DBRF gets from the randomizer when it is called to process that key. On panel FABZPS1, you still must enter area number when RBA or BLK retrieval is attempted. Also for DEDBs, FSE structure is not the same as for non-FP databases, so the panel that displays FSEs, FABZPS9 , will not work. For consistnecy, we will not allow FSE=Y or RAPS=Y entry on FABZPS1 when it is DEDB. The user can still view/modify RAPs/FSEs in panel FABZPS10, in their raw format. Finally, when key access is done on FABZPS1 panels, a return to that panel would show the RBA, this is incorrect behavior since the panel should only display what values the user had originally entered, now the RBA value will not appear if you did a key entry on this panel.
Problem conclusion
The fact that the FP randomizer would also tell you the area number for a given key was a logic oversight. Also, the difference between FP FSEs and non-FP FSEs was a logic oversight. The FP FSEs also have the high-bit on. It was not feasible to handle this difference ,and all its ramifications , in the seperate panel for FSE disply,FABZPS9. We feel that any DBA who wants to modify FP FSEs must be very experienced, and will thus be able to find and change them in the panel that displays the entire block, FABZPS10. Finally, when you enter just the key on fabzps1, it takes you to fabzps2. PF3 returns you to fabzps1, at which point it was confusing to see the key and rba appear. 110Y 120Y FABZDATA FABZDBLS FABZMAIN FABZPROC FABZPRO2 FABZPS1 FABZRANF FABZ02
Temporary fix
Comments
APAR Information
APAR number
PK04557
Reported component name
IMS DATABASE RE
Reported component ID
5655E0300
Reported release
120
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2005-04-20
Closed date
2005-06-02
Last modified date
2005-07-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK04075 UK04076
Modules/Macros
FABZDATA FABZDBLS FABZMAIN FABZPROC FABZPRO2 FABZPS1 FABZRANF FABZ02
Fix information
Fixed component name
IMS DATABASE RE
Fixed component ID
5655E0300
Applicable component levels
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":"SSCX892","label":"IMS Database Repair Facility"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1.2.0"}]
Document Information
Modified date:
14 December 2020