A fix is available
APAR status
Closed as program error.
Error description
MISCELLANEOUS MINOR BUGS AND ENHANCEMENTS
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: IMS Database Repair Facility -Version 1 * * Release 1 * **************************************************************** * PROBLEM DESCRIPTION: * * 1-For an Index db with symbolic * * pointers, ps3i shows an rba field * * incorrectly. * * 2-For a PSINDEX db, panel=fabzps3p * * incorrectly removes blanks from the * * rootkey field. * * 3-Undo may fail,if you had done * * segment retrieval via a hex key * * value. * * 4-New requirement,save changes in * * a format suitable for input to * * batch DBR. The idea is, if you * * make a specifc change to a db, you * * want to capture that change in * * a batch job. Then you can run * * that batch job to apply the * * same change to an exact copy of * * that database in another * * dataset. * * * **************************************************************** * RECOMMENDATION: * **************************************************************** 1-For an index db with symbolic pointers,the segments do NOT have an rba pointer in the segment, so the rba field on ps3i should not appear 2-For a PSINDEX db, panel=fabzps3p incorrectly removes blanks from the rootkey field. 3-If you access a segment via a hex key value, then make a change, a subsequent UNDO may fail. 4-New requirement, DBR saves all current changes in an UNDO table,and when you 'undo' them,they are removed from this table. A new option on main menu, will use the current UNDO table entries to create batch job SYSIN file that will duplicate these current changes.
Problem conclusion
The first three problems in the summary section were resolved via simple logic corrections. The 4th item,the new requirement has these highlights,and will be fully documented in the users guide. DBR saves all current changes in an UNDO table,and when you 'undo' them,they are removed from this table. A new option on main menu, will use the current UNDO table entries to create batch job SYSIN file that will duplicate these current changes. This option is option 5, "Save changes in batch format" This option will create a file named userid.prodid.dbd.batchinp, where userid,prodid,dbd are all variables. Below, is a sample of this file. //* DBR ONLINE UPDATED DATASET= //* GKRAUSE.HPPC.DB.DSCRSDV0 //* COPY THESE RECORDS TO SYSIN //* IN THE VSAM BATCH JOB CNV 4096 VER 0000 108400000000100C00000000010000000004000010460 REP 0000 108400000000100C00000000010000000004000000000 The comment lines tell the user which DB was changed,and its type VSAM/OSAM. These lines need not be copied to the appropriate batch job. THe CNV,VER,REP lines are to be copied to the batch jobs SYSIN. FABZ097I: Batch Input created in &LOG Explanation: The batch input was successfully created,and saved file=&LOG System Action: processing continues Problem determination: none Programmer response: User can copy records in &LOG to their DBR jobs 110Y FABZMAIN FABZOBAT FABZOSMB FABZPROC FABZPRO2 FABZPS3I FABZP00 FABZ08 FABZ09
Temporary fix
Comments
APAR Information
APAR number
PQ89725
Reported component name
IMS DATABASE RE
Reported component ID
5655E0300
Reported release
110
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2004-06-04
Closed date
2004-07-12
Last modified date
2004-08-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UQ90553
Modules/Macros
FABZMAIN FABZOBAT FABZOSMB FABZPROC FABZPRO2 FABZPS3I FABZP00 FABZ08 FABZ09
Fix information
Fixed component name
IMS DATABASE RE
Fixed component ID
5655E0300
Applicable component levels
R110 PSY UQ90553
UP04/07/13 P F407
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":"110"}]
Document Information
Modified date:
14 December 2020