A fix is available
APAR status
Closed as program error.
Error description
After applying maintenance (from: 9/28/07UK29774 - to:02/25/08UK34034> 1. When 'SORTKEYS' or 'SORTKEYS 0' is specified in load statement, loads abend in term phase: ABEND=S0C4 U0000 REASON=00000011 the problem can be recreated at will. 2. When SORTKEYS parameter is omitted or if a DD DUMMY SYSREC is provided, Load works ok. Additional symptom: Abend0c4 in DSNUGDAL offset 035C on CLC inst. Reg9 was bad.
Local fix
n/a
Problem summary
**************************************************************** * USERS AFFECTED: All DB2 for z/OS V8 and DB2 9 for z/OS * * utility users with PK45916/UK33692 or * * PK41899/UK33636 applied who use template * * data sets and dynamically allocated sort * * work data sets in utilities with subtasks * **************************************************************** * PROBLEM DESCRIPTION: The LOAD utility was invoked with all * * required DD cards in JCL except for the * * sort work data sets. SYSTEMPL DD was * * also specified which caused an ABEND04E * * RC00E40345 after ABEND0C4 RC00000011 * * when subtasks were attached as a result * * of the SORTKEYS option with PK45916/ * * UK33692 or PK41899/UK33636 applied. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** After applying PK45916 (UK33692) or PK41899 (UK33636) the subtask was checking for existance of sort work data set DD cards. Since no DD card was found, the routine was then looking for a template with the same name though no templates are supported for sort work data sets. The initialization of the template structures however cannot be called from a subtask but only from the main task which caused the access violation (ABENDS0C4) during utility termination. Similar failures may also occur with other utilities using subtasks: REBUILD INDEX, REORG TABLESPACE, RUNSTATS
Problem conclusion
Code was changed to no longer search templates when looking for the existance of sort work data set DD cards. PK45916/PK41899 added a new utility reason code. The change will be documented in the next refresh of the DB2 Codes manual (GC18-9603 and GC18-9843). The new reason code is: 00E40800 Explanation: When the utility performs dynamic allocation of sort data sets, the total number of data sets in each sort group must be less than 255. This reason code may be issued after message DSNU3341I CANNOT ALLOCATE SORT DATASETS WITHIN 255 LIMIT. System action: Utility processing abends. System programmer response: Provide more disk space for sort work data sets by either adding additional volumes to the sort pool or by defragmenting the existing sort volumes, then resubmit the job. Problem determination: Sort work data sets are allocated in primary quantities only, so this error occurs when the sort volumes are very fragmented or are used to their full capacity. Verify the number of free tracks and the size of the largest contiguous block of tracks on your sort volumes to see whether more volumes need to be added to the sort pool or if defragmentation is necessary. Defragmentation might be required if many tracks are still available on each volume but the largest contiguous block is very small. The description for message DSNU3341I has been changed. The change will be documented in the next refresh of the DB2 Messages manual (GC18-9602 and GC18-9849). The changed description is: DSNU3341I csect-name CANNOT ALLOCATE SORT DATASETS WITHIN 255 LIMIT Explanation: When the utility performs dynamic allocation of sort data sets, the total number of data sets | in each sort group must be less than 255. Severity: 8 (error) | System action: Utility processing terminates with RC=8 or | abends with reason code X'00E40800'. Programmer response: No action is required. | System programmer response: | Provide more disk space for sort work data sets by either | adding additional volumes to the sort pool or by | defragmenting the existing sort volumes, then resubmit the | job. | Problem determination: | Sort work data sets are allocated in primary quantities | only, so this error occurs when the sort volumes are very | fragmented or are used to their full capacity. | | Verify the number of free tracks and the size of the | largest contiguous block of tracks on your sort volumes to | see whether more volumes need to be added to the sort pool | or if defragmentation is necessary. Defragmentation might | be required if many tracks are still available on each | volume but the largest contiguous block is very small.
Temporary fix
Comments
APAR Information
APAR number
PK66597
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
810
Status
CLOSED PER
PE
YesPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-05-25
Closed date
2008-07-03
Last modified date
2009-05-08
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK37865 UK37866 PK68885
Modules/Macros
DSNDUCOM DSNUCRIB DSNUCSOR DSNUGCDD DSNUGLSR DSNUGSOR DSNUGSRT DSNUGSUP DSNUKPIK DSNURPCT DSNURPIB DSNURSOR DSNUSSOR
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":"8.1","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":"8.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
08 May 2009