A fix is available
APAR status
Closed as new function.
Error description
DB2 UTILITY SUPPORT (COPY AND RECOVER) FOR VERSIONED INDEXES WITH COMPRESSION
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All DB2 9 for z/OS users of * * index compression who run DB2 * * utilities. * **************************************************************** * PROBLEM DESCRIPTION: COPY and RECOVER utility support * * for PK79312. * **************************************************************** * RECOMMENDATION: * **************************************************************** PM00088 provides COPY and RECOVER utility support for PK79312. PK79312 provides the ability to make certain schema changes to a compressed index without marking the index REBUILD-pending. Please see PK79312 for complete information about this enhancement including details about all prerequisite and preconditioning PTFs.
Problem conclusion
Temporary fix
********* * HIPER * *********
Comments
The PTF for APAR PM00088 provides DB2 utility support for PK79312. COPY and RECOVER utility changes are provided to support PK79312. COPY utility is changed to support recovery of indexes with the COPY YES attribute which can be altered without REBUILD-pending being set with PK79312 applied. RECOVER utility is changed to support indexes which have been altered in this way and image copies made of them. Copies of indexes made with this fix applied are indicated by the setting of 'S' in the first byte of the TTYPE column of the SYSIBM.SYSCOPY record created by the COPY. The resulting output data set may contain pages out of numerical sequence, pages with 'V' or '8' in the last byte, and/or pages appearing more than once. RECOVER of indexes checks the TTYPE column of SYSCOPY during RESTORE phase to make sure that if certain ALTER activity was previously done, the image copy being used has the proper support (i.e., the fix was applied at the time of the COPY). If it is not, MSGDSNU556I (RECOVER CANNOT PROCEED...) is issued and rc8 is set. DB2 for z/OS publications will be updated to reflect the relevant changes. Users are advised of the following when applying the fix for PM00088: Although there is no general requirement that the fix for PM00088 be applied any particular length of time before the fix for PK79312, to exploit the enhanced function provided by PK79312 users might be required to follow certain recommendations to ensure the function can be properly utilized. Any such recommendations will be clearly documented and made available to users applying the PTF for PK79312. A simultaneous group-wide outage of all members of a data sharing group is NOT required, whether the enhanced schema functionality delivered by PK79312 is to be used or not. However, users should be aware of the following potential situation involving PM00088 and PK79312. (In the following example, 'properly applied' means the PTF is active and running in all appropriate address spaces and DB2 has been restarted as necessary.) If ALL of the following conditions are true: (1) An image copy exists or is taken of an index with both the COPY YES and COMPRESS YES attributes, AND, (2) An ALTER statement is performed with the fix for PK79312 properly applied, resulting in REBUILD-pending status NOT being set on that index as a result of the exploitation of the support provided, AND, (3) RECOVER utility is subsequently run on the index on the same system after the fix has been removed, or on a different member of a data sharing group where the fix is not properly applied, the RECOVER utility job may abend with one of the following: ABEND04E RC00C90101 ERQUAL5006 in DSNKPGCM, ABEND04E RC00C90101 ERQUAL5008 in DSNKPGCM, or other abends, and MSGDSNU086I (I/O ERRORS...) may be issued. If this should occur, one of the following actions should be taken: (1) Run RECOVER utility from a system where the fix is properly applied, or, (2) Run REBUILD INDEX utility from any system.
APAR Information
APAR number
PM00088
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
910
Status
CLOSED UR1
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt
Submitted date
2009-10-29
Closed date
2009-11-30
Last modified date
2010-01-05
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK52414
Modules/Macros
DSNDUIC DSNDURCB DSNIPPS DSNIPSP DSNUBAID DSNUBASA DSNUBAUS DSNUCAIN DSNUCASA DSNUCAWR DSNUCAWT DSNUCBAL DSNUCBMD DSNUCBRT DSNUGRSP DSNUGRST
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
R910 PSY UK52414
UP09/12/16 P F912
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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
05 January 2010