A fix is available
APAR status
Closed as program error.
Error description
After the application of the fix for PH64299, the issues described below occur. Fix for PH64299 not efficient Some use cases affected by PH64299 remain not corrected despite the fix enablement. This occurs if all the following conditions are fulfilled: - the conditions triggering PH64299 apply - the fix of PH64299 is enabled (i.e. the value of VUU030/ULOPTNS contains FIX(APAR_PH64299)) - the first unload statement involves a table that is not in EBCDIC In this case, the symptom described by PH64299 occur. New issues One or several of the following new issues occur if all the common following conditions are fulfilled: - there are multiple SELECT statements in a single UNLOAD statement - the select statements are not against a single tablespace (in other words, the set of SELECT statement involve at least two tablespaces) and the additional conditions specific to each issue, and detailed below, also apply. issue 1) the unloaded data is incorrect if the following additional conditions are fulfilled: - the unload is run in native mode - the involved tablespaces don't share a unique encoding scheme - a SELECT statement (except the first one) specifies the ASIS option In this case, the data unloaded for the unload specifying ASIS is unduly unloaded in the CCSID of the tablespace involved in the first unload. issue 2) the unloaded data is incorrect if the following conditions are fulfilled: - the unload is run in SQL mode - the involved tablespaces don't share a unique encoding scheme - a SELECT statement (except the last one) specifies the ASIS option In this case, the data unloaded for the unload specifying ASIS is unduly unloaded in the CCSID of the tablespace involved in the last unload. issue 3) the message INZI012E DUPLICATE KEYWORD OR STATEMENT CCSID_TABLESPACE is unduly issued, if the following additional condition is fulfilled: - the unload is run in native mode In this case, the unloads end without failing and produce correct unloaded data unless the conditions for issue 1 also apply.
Local fix
Split the unload statement into as many unload statement as the number of involved tablespaces. For example, replacing the following unload statement affected by the issue UNLOAD TABLESPACE DB2 NO SELECT CHAR(MYINT) FROM MZLFDE.DEPT OUTDDN OUT1 FORMAT DSNTIAUL ASIS SELECT CHAR(MYINT) FROM MZLFDE.DEPTEBC OUTDDN OUT2 FORMAT DSNTIAUL ASIS by UNLOAD TABLESPACE DB2 NO SELECT CHAR(MYINT) FROM MZLFDE.DEPT OUTDDN OUT1 FORMAT DSNTIAUL ASIS ; UNLOAD TABLESPACE DB2 NO SELECT CHAR(MYINT) FROM MZLFDE.DEPTEBC OUTDDN OUT2 FORMAT DSNTIAUL ASIS solves the issue. Note that the tablespaces with the same encoding scheme can be kept in the same unload statement.
Problem summary
**************************************************************** * USERS AFFECTED: Users of Db2 High Performance Unload for * * z/OS * **************************************************************** * PROBLEM DESCRIPTION: After the application of the fix for * * PH64299, the issues described below * * occur. * * Fix for PH64299 not efficient * * Some use cases affected by PH64299 * * remain not corrected despite * * the fix enablement. This occurs if all * * the following conditions are fulfilled: * * - the conditions triggering PH64299 * * apply * * - the fix of PH64299 is enabled * * (i.e. the value of * * VUU030/ULOPTNS contains * * FIX(APAR_PH64299)) * * - the first unload statement * * involves a table that is not in * * EBCDIC * * In this case, the symptom described by * * PH64299 occur. * * * * New issues * * One or several of the following new * * issues occur if all the common * * following conditions are fulfilled: * * - there are multiple SELECT * * statements in a single UNLOAD * * statement * * - the select statements are not * * against a single tablespace * * (in other words, the set of * * SELECT statement involve at least * * two tablespaces) * * and the additional conditions specific * * to each issue, and detailed below, * * also apply. * * * * issue 1) the unloaded data is * * incorrect if the following additional * * conditions are fulfilled: * * - the unload is run in native mode * * - the involved tablespaces don't * * share a unique encoding scheme * * - a SELECT statement (except the * * first one) specifies the ASIS * * option * * * * In this case, the data unloaded for * * the unload specifying ASIS is unduly * * unloaded in the CCSID of the * * tablespace involved in the first * * unload. * * * * issue 2) the unloaded data is * * incorrect if the following conditions * * are fulfilled: * * - the unload is run in SQL mode * * - the involved tablespaces don't * * share a unique encoding * * scheme * * - a SELECT statement (except the last * * one) specifies the ASIS * * option * * * * In this case, the data unloaded for * * the unload specifying ASIS is unduly * * unloaded in the CCSID of the * * tablespace involved in the last unload. * * * * issue 3) the message INZI012E * * DUPLICATE KEYWORD OR STATEMENT * * CCSID_TABLESPACE is unduly issued, if * * the following additional condition is * * fulfilled: * * - the unload is run in native mode * * * * In this case, the unloads end without * * failing and produce correct unloaded * * data unless the conditions for issue 1 * * also apply. * * * * Local fix: Split the unload statement * * into as many unload statement as the * * number of involved tablespaces. * * For example, replacing the following * * unload statement affected by the issue * * * * UNLOAD TABLESPACE * * DB2 NO * * SELECT CHAR(MYINT) * * FROM MZLFDE.DEPT * * OUTDDN OUT1 * * FORMAT DSNTIAUL * * ASIS * * SELECT CHAR(MYINT) * * FROM MZLFDE.DEPTEBC * * OUTDDN OUT2 * * FORMAT DSNTIAUL * * ASIS * * * * by * * * * UNLOAD TABLESPACE * * DB2 NO * * SELECT CHAR(MYINT) * * FROM MZLFDE.DEPT * * OUTDDN OUT1 * * FORMAT DSNTIAUL * * ASIS ; * * UNLOAD TABLESPACE * * DB2 NO * * SELECT CHAR(MYINT) * * FROM MZLFDE.DEPTEBC * * OUTDDN OUT2 * * FORMAT DSNTIAUL * * ASIS * * * * solves the issue. * * Note that the tablespaces with the * * same encoding scheme can be kept in * * the same unload statement. * **************************************************************** * RECOMMENDATION: Apply the PTF * **************************************************************** after the fix for PH64299, incorrect unloaded data (incorrout) and/or undue INZI012E message
Problem conclusion
Code has been changed to fix this problem
Temporary fix
Comments
APAR Information
APAR number
PH65475
Reported component name
DB2 HI PERF UNL
Reported component ID
5697F4400
Reported release
510
Status
CLOSED PER
PE
YesPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2025-02-28
Closed date
2025-04-07
Last modified date
2025-05-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UO02741
Modules/Macros
INZUTILK
Fix information
Fixed component name
DB2 HI PERF UNL
Fixed component ID
5697F4400
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.
[{"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":"5.1.0","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
05 May 2025