A fix is available
APAR status
Closed as program error.
Error description
AE PI84430 FIX COMPLETION ESTAI routine abends with S0C4 RC04 in DSNUGSAT
Local fix
n/a
Problem summary
**************************************************************** * USERS AFFECTED: * * All DB2 11 for z/OS with PI73882/UI44914 * * applied and DB2 12 for z/OS users of the * * LOAD and REORG utilities and a zIIP * * configured and all DB2 12 for z/OS users * * of LOAD PARALLEL with CONSTANT. * **************************************************************** * PROBLEM DESCRIPTION: * * AE PI84430 FIX COMPLETION * * With a System z Integrated * * Information Processor (zIIP) * * configured and the REORG or * * LOAD utilities are run on DB2 12 * * for z/OS or DB2 11 for z/OS with * * PI73882/UI44914 applied, two problems * * can occur: * * * * 1. REORG or LOAD hang when run on a * * table space using partition * * parallelism with an embedded copy. * * * * 2. REORG hang when run on a * * non-partitioned table space and a * * STOP DB2 command is issued during * * the UNLOAD phase. * * * * Also, on DB2 12 for z/OS, LOAD * * PARALLEL using CONSTANT on a * * field-specification results in * * ABEND0C4 RC00000038 * * LOC=DSNUTILA.DSNUGSTA and ABEND04E * * RC00E20005 LOC=DSNUGSTA.DSNSVBK * * * * ABEND0C4 DSNUGSAT following ABEND04E * * RC00E40347 during REORG TABLESPACE * **************************************************************** * RECOMMENDATION: * * Apply corrective PTF when available * **************************************************************** AE PI84430 FIX COMPLETION User ran a REORG of a partitioned table space with an embedded copy, a System z Integrated Information Processor (zIIP) configured, and PI73882/UI44914 applied. The job hung and had to be cancelled. A timing window exists where there are multiple RELOAD tasks in LOAD or REORG, running on different partitions and attempting to write data pages to the embedded copy, with a zIIP configured. In this timing window the embedded copy subtask can issue a RESUME to wake up a suspended RELOAD task but issue it to the wrong task, causing the next task that suspends to miss a resume and hang. User ran a REORG of a non-partitioned table space with multiple indexes, a System z Integrated Information Processor (zIIP) configured, and PI73882/UI44914 applied. A STOP DB2 command was issued while the job was in the UNLOAD phase. MSGDSNU006I DB2 SYSTEM xxxx HAS NOT BEEN STARTED was issued as each index sort and build task were started in the RELOAD phase, but the job hung and had to be cancelled. When a REORG running on a non-partitioned table space, or not using unload/reload parallelism for any other reason, and is in the UNLOAD phase when a STOP DB2 command is issued, the subtasks attached in the RELOAD phase to sort the index keys cannot connect to DB2. The main task was not detecting that those tasks had never started, and was suspending, causing the hang. LOAD PARALLEL using CONSTANT on a field-specification failed to initialize an internal flag for subtask processing resulting in ABEND0C4 RC00000038 DSNUTILA.DSNUGSTA +22B8 OFFSET22B8 or ABEND04E RC00E20005 DSNUGSTA.DSNSVBK +1AEE OFFSET1AEE. A REORG TABLESPACE was run on a segmented table space and abended with an ABEND04E RC00E40347 due to the segmented table space being full. This is a normal and expected abend for this condition. During the recovery routine process for this abend, an ABENDS0C4 RC4 occurred in DSNUGSAT. This error was caused by the recovery routine attempting to write into the System Diagnostic Work Area (SDWA) from the wrong storage key.
Problem conclusion
AE PI84430 FIX COMPLETION LOAD and REORG have been modified to ensure that the embedded copy subtask issues a resume to the correct suspended task. REORG has been modified to check that the index key sort tasks have not prematurely terminated before suspending. Code has been changed to correct the problem in LOAD PARALLEL with CONSTANT. The recovery routine has been changed to set the proper storage key.
Temporary fix
Comments
APAR Information
APAR number
PI86574
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
B10
Status
CLOSED PER
PE
YesPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-08-29
Closed date
2017-09-29
Last modified date
2017-11-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI50747 UI50749
Modules/Macros
DSNUREPG DSNUSSIT DSNURSIT DSNUGUCA DSNURISI DSNURPCT DSNURMPG DSNURWBR DSNURIS2 DSNURPIB DSNUGUTC DSNUGBAC DSNUGSAT DSNUCRIB DSNURWBF
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":"11.0","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":"11.0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
01 November 2017