A fix is available
APAR status
Closed as program error.
Error description
ABEND0C4 DSNX9CAC +0e42 or ABEND0C4 DSNXEUF0 +0894 DURING SQL PARALLELISM
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of sql query parallelism * **************************************************************** * PROBLEM DESCRIPTION: Users may encounter * * . * * ABEND0C4 RC00000011 at DSNX9CAC +0326 * * ABEND0C4 RC00000010 at DSNX9CAC +0E34 * * ABEND0C4 RC00000010 at DSNX9CAC +0E2E * * ABEND0C4 RC00000011 at DSNX9CAC +2C9E * * during normal or abnormal termination * * of a DB2 subsystem on which a query * * participated in sql query parallelism * * and referenced a user defined function * * . * * and / or * * . * * ABEND0C4 RC0000003B at DSNXEUF0 +0894 * * ABEND0C4 RC0000003B at DSNXEUF0 +09AA * * during execution of a query that * * participated in sql query parallelism. * **************************************************************** * RECOMMENDATION: * **************************************************************** When a query participated in CPU or sysplex query parallelism, each child task runs under its own agent. Upon completion of the work, the agents for those child tasks must be cleaned up. The clean up code includes searching for udf-related clean up, which may be necessary if the child tasks invoke user defined functions as part of their work. If DB2 does not perform udf clean up, then certain structures will remain allocated incorrectly. Those residual structures may cause the DSNX9CAC abends when DB2 is ending normally or abnormally. The abends in DSNX9CAC do not prevent DB2 from ending. . There are also some reported cases in which the child task clean up code itself encountered abends as a result of either looking at storage which had already been freed, or attempting to clean up structures which had never fully established in the first place. These errors can lead to the abends in DSNXEUF0 listed above and, because these abends prevent child task clean up from proceeding normally, may also result in the DSNX9CAC abends the next time the DB2 subsystem is ended. . In most cases, these errors are preceded by a cancel of the parallel child tasks by the user.
Problem conclusion
DB2 code has been modified to correctly handle clean up of sql parallel child tasks to prevent the udf-related cleanup from being incorrectly skipped. . . ADDITIONAL KEYWORDS: sqlcpup sysplex sqlsysplexp sqlparallelism DB2PARALL/K sqludf
Temporary fix
********* * HIPER * *********
Comments
ž**** PE12/08/23 FIX IN ERROR. SEE APAR PM71490 FOR DESCRIPTION
APAR Information
APAR number
PM48950
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
A10
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt
Submitted date
2011-09-28
Closed date
2011-11-03
Last modified date
2012-10-09
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK73548 UK73549
Modules/Macros
DSNTTRUN DSNXEET DSNXEUF0
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":"10.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":"10.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
09 October 2012