A fix is available
APAR status
Closed as program error.
Error description
Job with distributed stored procedure call executes fine on first run. However, on the second run, the same job performing same SQL operation abends due to RC00C90089 EDMPool full.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All DB2 users of stored procedure packages. * **************************************************************** * PROBLEM DESCRIPTION: An EDM POOL FULL condition occurred * * with the following console message: * * DSNT500I DSNGEPLC RESOURCE * * UNAVAILABLE * * REASON 00C90089 * * TYPE 00000600 * * NAME EDM POOL SPACE * **************************************************************** * RECOMMENDATION: * **************************************************************** An application was designed to make several updates to a table without a commit. The table has an update trigger that invokes a stored procedure to make an update to a similar table on a remote DB2. The first time the application would run without any problems. The second time the application was run the application would fail with a resource unavailable on the remote system: DSNT500I DSNGEPLC RESOURCE UNAVAILABLE REASON 00C90089 TYPE 00000600 NAME EDM POOL SPACE
Problem conclusion
When a stored procedure accesses a remote DB2 it can cause multiple copies of package sections to be loaded into the EDM pool until a commit is issued to release the storage. DB2 code looks at the storage used during each run of a package to optimize future executions. This code incorrectly caused larger blocks of storage to be used for each section on the subsequent runs causing the full condition. The storage would be freed on commit. Multiple copies of packages sections can also occur at the local DB2 by repeated calls to a stored procedure when the stored procedure result sets are left open. Subsequent runs of the same workload could also cause the resource unavailable error. A second problem was discovered on a DB2 V9. The type was incorrectly displayed as 600 in the DSNT500I message . It should have shown a type of 605. The code has been updated to correct both problems. Additional Keywords: MSGDSNT500I RC00C90089 SQLSP SQLSTOREDPROC
Temporary fix
Comments
APAR Information
APAR number
PM61344
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-03-27
Closed date
2012-05-04
Last modified date
2012-06-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK78723 UK78724
Modules/Macros
DSNGEPLC DSNGESFR DSNXELX
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":"9.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":"9.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
03 June 2012