A fix is available
APAR status
Closed as program error.
Error description
A logical unload specifying a SELECT statement that involves the use of CURRENT_DATE, CURRENT_TIME and CURRENT_TIMESTAMP special registers and that is performed in native mode produces incorrect unloaded data when run in z/OS 3.2. This problem can affect any logical unload that uses SQL expressions involving any of the three aforementioned special registers, whether to define the selected items or in a predicate of a WHERE clause. The incorrectness of the unloaded data can consist in improperly filtered rows and/or in incorrect data for the output fields related to columns defined with SQL expressions using the special registers listed above. This occurs because Db2 HPU unduly detects an error when retrieving the system time value needed to calculate the value of the CURRENT_DATE, CURRENT_TIME or CURRENT_TIMESTAMP SQL special registers which triggers the erroneous error processing described by APAR PH67989.
Local fix
- If applicable, consider performing the unload in SQL mode by specifying the DB2 FORCE option. - If Db2 HPU is at the maintenance level UO04514, apply the following ZAP: NAME INZUTILK IX6TGTIM#C B_TEXT31 VER 0092 A774,0031 VER 00E2 A774,0009 REP 0092 B902,00FF REP 00E2 B902,00FF
Problem summary
**************************************************************** * USERS AFFECTED: Users of Db2 High Performance Unload for * * z/OS * **************************************************************** * PROBLEM DESCRIPTION: A logical unload specifying a SELECT * * statement that involves the use of * * CURRENT_DATE, CURRENT_TIME and * * CURRENT_TIMESTAMP special registers and * * that is performed in native mode * * produces incorrect unloaded data when * * run in z/OS 3.2. * * * * This problem can affect any logical * * unload that uses SQL expressions * * involving any of the three * * aforementioned special registers, * * whether to define the selected items or * * in a predicate of a WHERE clause. The * * incorrectness of the unloaded data can * * consist in improperly filtered rows * * and/or in incorrect data for the output * * fields related to columns defined with * * SQL expressions using the special * * registers listed above. * * * * This occurs because Db2 HPU unduly * * detects an error when retrieving the * * system time value needed to calculate * * the value of the CURRENT_DATE, * * CURRENT_TIME or CURRENT_TIMESTAMP SQL * * special registers which triggers the * * erroneous error processing described by * * APAR PH67989. * * * * Local Fix: * * - If applicable, consider performing * * the unload in SQL mode by specifying * * the DB2 FORCE option. * * * * - If Db2 HPU is at the maintenance * * level UO04514, apply the following * * ZAP: * * NAME INZUTILK IX6TGTIM#C B_TEXT31 * * VER 0092 A774,0031 * * VER 00E2 A774,0009 * * REP 0092 B902,00FF * * REP 00E2 B902,00FF * **************************************************************** * RECOMMENDATION: Apply the PTF * **************************************************************** Incorrect evaluation of CURRENT_DATE, CURRENT_TIME and CURRENT_TIMESTAMP in native mode in z/OS 3.2
Problem conclusion
Code has been changed to fix this problem
Temporary fix
Comments
APAR Information
APAR number
PH67993
Reported component name
DB2 HI PERF UNL
Reported component ID
5697F4400
Reported release
520
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2025-09-04
Closed date
2025-10-08
Last modified date
2025-11-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
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":"520","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
03 November 2025