A fix is available
APAR status
Closed as program error.
Error description
There is an obscure timing window where a variable that is involved in the synchronization between the reload task and the sort task could get re-initialized when it should not be. This could cause the reload task (DSNURWBR) to issue a resume to the sort task, with the sort task then issuing a suspend and not detecting that it had already been resumed, causing the sort task to suspend when it should not. The reload task could then easily suspend on an different pipe, causing a hang.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * All DB2 11 for z/OS with PI73882/UI44914 * * applied and DB2 12 for z/OS users of the * * LOAD or REORG utilities with a zIIP * * configured. * **************************************************************** * PROBLEM DESCRIPTION: * * REORG or LOAD hang when run on a * * partitioned table space with multiple * * indexes and a System z Integrated * * Information Processor (zIIP) * * configured. * **************************************************************** * RECOMMENDATION: * * Apply corrective PTF when available. * **************************************************************** User ran a REORG of a partitioned table space with multiple indexes and a System z Integrated Information Processor (zIIP) configured. The job hung and had to be cancelled. A timing window exists when multiple RELOAD tasks in LOAD or REORG, running on different partitions and attempting to pass index keys to multiple sort tasks, with a zIIP configured, can issue a RESUME to a sort task before the sort task initializes a flag that controls whether the sort task issues a SUSPEND or continues processing. If the timing is right, this can cause both the sort and reload tasks to be suspended, waiting on each other, causing the hang.
Problem conclusion
The sort task initialization of the suspend/resume flags has been corrected.
Temporary fix
Comments
APAR Information
APAR number
PI83023
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
B1K
Status
CLOSED PER
PE
YesPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-06-13
Closed date
2017-07-27
Last modified date
2017-09-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI49143 UI49144
Modules/Macros
DSNUGSRP DSNURPDS
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
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":"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":"B1K","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":"B1K","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 September 2017