A fix is available
APAR status
Closed as program error.
Error description
An unload terminates in abend if all the following conditions are fulfilled: - zIIP usage is active - at least one of the following conditions is true: - the data are unloaded to a sequential dataset and the BSAM method is used for OUTPUT datasets (as reported by the INZ666I message) - (in HPU 6.1 only) a dataset is alloacted for the INDEXSCAN feature (as reported by the INZX111 message) is used to process the unload and the BSAM method is used for the INDEXSCAN datasets (as reported by the INZ666I message) - a very precise timing condition between Db2 HPU internal threads is fulfilled The required timing condition makes this issue very rare and intermittent. Local fix: A new run of the failing unload can terminate successfully but the issue may be completely avoided by request the QSAM method for the concerned type of dataset (OUTPUT or INDEXSCAN). For example, specify IO_SEQ_METHOD OUTPUT(QSAM),INDEXSCAN(QSAM) in the GLOBAL option block.
Local fix
A new run of the failing unload can terminate successfully but the issue may be completely avoided by request the QSAM method for the concerned type of dataset (OUTPUT or INDEXSCAN). For example, specify IO_SEQ_METHOD OUTPUT(QSAM),INDEXSCAN(QSAM) in the GLOBAL option block.
Problem summary
**************************************************************** * USERS AFFECTED: Users of Db2 High Performance Unload for * * z/OS * **************************************************************** * PROBLEM DESCRIPTION: An unload terminates in abend if all * * the following conditions are fulfilled: * * - zIIP usage is active * * - at least one of the following * * conditions is true: * * - the data are unloaded to a * * sequential dataset and the BSAM * * method is used for OUTPUT datasets * * (as reported by the INZ666I * * message) * * - (in HPU 6.1 only) a dataset is * * alloacted for the INDEXSCAN * * feature (as reported by the * * INZX111 message) is used to * * process the unload and the BSAM * * method is used for the INDEXSCAN * * datasets (as reported by the * * INZ666I message) * * - a very precise timing condition * * between Db2 HPU internal threads is * * fulfilled * * * * The required timing condition makes * * this issue very rare and intermittent. * * * * * * Local fix: A new run of the failing * * unload can terminate successfully but * * the issue may be completely avoided by * * request the QSAM method for the * * concerned type of dataset (OUTPUT or * * INDEXSCAN). For example, specify * * IO_SEQ_METHOD OUTPUT(QSAM), * * INDEXSCAN(QSAM) in the GLOBAL option * * block. * **************************************************************** * RECOMMENDATION: Apply the PTF * **************************************************************** Unpredictable and intermittent ABEND during an unload using BSAM method
Problem conclusion
Code has been changed to fix this problem
Temporary fix
Comments
APAR Information
APAR number
PH71572
Reported component name
DB2 HI PERF UNL
Reported component ID
5697F4400
Reported release
610
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2026-06-02
Closed date
2026-06-03
Last modified date
2026-07-02
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
R610 PSY UO08108
UP26/07/02 P F606
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":"610","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
02 July 2026