A fix is available
APAR status
Closed as program error.
Error description
This PTF addresses the following internal issues: 1. Build message HAAB577W is changing: FROM: HAAB577W Pending changes for dropped columns will not be materialized with SHRLEVEL <Change|Reference> and FASTSWITCH NO. TO: HAAB577W REORG with SHRLEVEL NONE or FASTSWITCH NO does not apply pending definition changes. This will occur for any pending definition status when either SHRLEVEL=NONE or FASTSWITCH=NO is specified. 2. TS REORG - When a PART with Pending Definition Changes is not specified, new Build message HAAB752I will be displayed. HAAB752I - <DBNAME.TSNAME.PART> Not all pending definition changes are applied because this affected partition is missing. Explanation: Pending ALTER PARTITION changes will not be materialized via REORG unless all affected partitions are included. User response: Include the missing part as described in the message text and REBUILD the job. 3. Job Build will now result in new message HAAB754I stating that "SORTDATA NO" keyword is invalid when TS is in REORG PENDING state. HAAB754I - SORTDATA set to YES to materialize ALTER PARTITION pending changes for REORG TS. Explanation: SORTDATA NO was specified, and pending ALTER PARTITION changes were detected for this object. This will cause a RC8 at run time. SORTDATA will be set to YES in this case. User Response: None required. 4. REORG TS Job Build - Issue warning message HAAB753W when ALL PARTS are **NOT** specified and the TS is in AREOR status due to a pending DROP Column. HAAB753W - <DBNAME.TSNAME.PART> Pending definition changes were not applied because the entire object was not specified. Explanation - Db2 will not materialize pending definition changes due to a DROP COLUMN statement unless all parts are being REORG'd together. User response: Include all partitions to materialize the DROP COLUMN pending status. 5. Job Build Message HAAB502I generated incorrectly. For Reorg TS, HAAB502I is generated to explain that LISTDEFs are not allowed with DISCARD only when DISCARD TEXT is included. As a result, message HAAB502I is being modified as follows: OLD message text: HAAB502I - Listdef=Y overridden for TS REORG, discard=Y NEW message text: HAAB502I - LISTDEFs were overridden because the DISCARD FROM clause was defined for REORG TS. Explanation: LISTDEFs are not supported when discarding rows from a table. When this combination occurs, the job will fail with return code 8 and the following message will be displayed: DSNU070I KEYWORD OR OPERAND 'DISCARD FROM TABLE' IS INVALID WITH 'LIST' User response: LISTDEFs will automatically be turned off. 6. Job Build: Some objects can be omitted from the REORG Control Cards if an object that does not support DISCARD (e.g., XML space) is included in the same job build with other objects that DO support DISCARD. 7. REORG TS - DISCARD invalid with LOB tablespaces. When a LOB TS is included in a REORG TS, and DISCARD is set to Yes in the utility profile, the HAA build will result in a new warning message: HAAB755W - DISCARD has been set to no because it is not allowed on a LOB Tablespace. Explanation: If DISCARD is generated for a LOB, the job will fail with RC8 at run time. User response: None required. Automation Tool will automatically turn off Discard in this case. 8) TS REORG: When DISCARD is turned off for the last object in the generated control cards - and TEMPLATES are also turned off - some qualifiers in the DISC DD dataset name may not be resolved properly. 9) HAAB078E can erroneously occur when building a job with template DSNs immediately after building a Recovery Expert Image Copy Job. 10) REORG: Empty JOB Template DD results in empty template DSN REORG TS - When earlier job builds with the Setup templatedd settings in place were successful, subsequent job builds now result in an empty template DSN after removing the setup templatedd settings. Given the situations described in each, the following new build messages will be displayed when templateDD information is not found: HAAB756I - Inline copy for Reorg Tablespace Utility has been turned off since no copy options are selected. Explanation: If no copy options are selected, Image copies for REORG will be turned off. User response: none HAAB757I - Reorg SHARELEVEL(CHANGE|REFERENCE) requires an inline copy. Share level changed to None. Explanation: Reorg SHARELEVEL Change or Reference requires Copy. If copy is turned off during the build process, SHRLEVEL will be set to None. User response: none
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All Users * **************************************************************** * PROBLEM DESCRIPTION: JAN 2023 Bug Fixes for Internal Issues * * * * This PTF addresses the following * * internal issues: * * * * 1) Build message HAAB577W is changing: * * * * FROM: HAAB577W Pending changes for * * dropped columns will not be * * materialized with SHRLEVEL * * <Change|Reference> and FASTSWITCH * * NO. * * * * TO: HAAB577W REORG with SHRLEVEL * * NONE or FASTSWITCH NO does not apply * * pending definition changes. * * * * This will occur for any pending * * definition status when either * * SHRLEVEL=NONE or FASTSWITCH=NO is * * specified. * * * * 2) TS REORG - When a PART with Pending * * Definition Changes is not specified, * * new Build message HAAB752I will be * * displayed. * * * * HAAB752I - <DBNAME.TSNAME.PART> Not * * all pending definition changes are * * applied because this affected * * partition is missing. * * * * Explanation: Pending ALTER PARTITION * * changes will not be materialized via * * REORG unless all affected partitions * * are included. * * User response: Include the missing * * part as described in the message * * text and REBUILD the job. * * * * 3) Job Build will now result in new * * message HAAB754I stating that * * "SORTDATA NO" keyword is invalid * * when TS is in REORG PENDING state. * * * * HAAB754I - SORTDATA set to YES to * * materialize ALTER PARTITION pending * * changes for REORG TS. * * * * Explanation: SORTDATA NO was * * specified and pending ALTER * * PARTITION changes were detected for * * this object. This will cause a RC8 * * at run time. SORTDATA will be set to * * YES in this case. * * * * User Response: None required. * * * * 4) REORG TS Job Build - Issue warning * * message HAAB753W when ALL PARTS are * * **NOT** specified and the TS is in * * AREOR status due to a pending DROP * * Column. * * * * HAAB753W - <DBNAME.TSNAME.PART> * * Pending definition changes were not * * applied because the entire object * * was not specified. * * * * Explanation - Db2 will not * * materialize pending definition * * changes due to a DROP COLUMN * * statement unless all parts are being * * REORGed together. * * * * User response: Include all * * partitions to materialize the DROP * * COLUMN pending status. * * * * 5) Job Build Message HAAB502I generated * * incorrectly. * * * * For Reorg TS, HAAB502I is generated * * to explain that LISTDEFs are not * * allowed with DISCARD only when * * DISCARD TEXT is included. * * * * As a result, message HAAB502I is * * being modified as follows: * * * * OLD message text: HAAB502I - * * Listdef=Y overridden for TS REORG, * * discard=Y * * * * NEW message text: HAAB502I - * * LISTDEFs were overridden because the * * DISCARD FROM clause was defined for * * REORG TS. * * * * Explanation: LISTDEFs are not * * supported when discarding rows from * * a table. When this combination * * occurs, the job will fail with * * return code 8 and the following * * message will be displayed: * * * * DSNU070I - KEYWORD OR OPERAND * * 'DISCARD FROM TABLE' IS INVALID * * WITH 'LIST' * * * * User response: LISTDEFs will * * automatically be turned off. * * * * 6) Job Build: Some objects can be * * omitted from the REORG control cards * * if an object that does not support * * DISCARD (e.g. XML space) is included * * in the same job build with other * * objects that DO support DISCARD. * * * * 7) REORG TS - DISCARD invalid with LOB * * tablespaces. When a LOB TS is * * included in a REORG TS, and DISCARD * * is set to Yes in the utility * * profile, the HAA build will result * * in a new warning message: * * * * HAAB755W - DISCARD has been set to * * no because it is not allowed on a * * LOB Tablespace. * * Explanation: If DISCARD is generated * * for a LOB, the job will fail with * * RC8 at run time. * * User response: None required. * * * * Automation Tool will automatically * * turn off Discard in this case. * * * * 8) TS REORG: When DISCARD is turned off * * for the last object in the generated * * control cards - and TEMPLATES are * * also turned off - some qualifiers in * * the DISC DD dataset name may not be * * resolved properly. * * * * 9) HAAB078E can erroneously occur when * * building a job with template DSNs * * immediately after building a * * Recovery Expert Image Copy Job. * * * * 10) REORG: Empty JOB Template DD * * results in empty template DSN * * REORG TS - When earlier job builds * * with the Setup templatedd settings * * in place were successful, subsequent * * job builds now result in an empty * * template DSN after removing the * * setup templatedd settings. * * * * Given the situations described in * * each, the following new build * * messages will be displayed when * * templatedd information is not found: * * * * HAAB756I - Inline copy for Reorg * * Tablespace Utility has been turned * * off since no copy options are * * selected. * * Explanation: If no copy options are * * selected, Image copies for REORG * * will be turned off. * * User response: none * * * * HAAB757I - Reorg SHARELEVEL * * (CHANGE|REFERENCE) requires an * * inline copy. Share level changed to * * None. * * Explanation: Reorg SHARELEVEL Change * * or Reference requires Copy. If copy * * is turned off during the build * * process, SHRLEVEL will be set to * * None. * * User response: none * **************************************************************** * RECOMMENDATION: APPLY the PTF * **************************************************************** .
Problem conclusion
Temporary fix
Comments
APAR Information
APAR number
PH52039
Reported component name
DB2 AUTOMATION
Reported component ID
5697G6300
Reported release
430
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2023-01-19
Closed date
2023-02-14
Last modified date
2023-03-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI90519
Modules/Macros
HAA#BTMP HAA#OBEX HAA#PEND HAA#UTED HAA$BDSN HAA$BMSG HAA$BUTR HAAREORC
Fix information
Fixed component name
DB2 AUTOMATION
Fixed component ID
5697G6300
Applicable component levels
R430 PSY UI90519
UP23/02/18 P F302
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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSZJXP","label":"DB2 Tools for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.3.0","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
01 March 2023