A fix is available
APAR status
Closed as program error.
Error description
Support to start and maintain a minimum number of WLM stored procedure address spaces
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of DB2 9 and DB2 10 stored * * procedures and udf. * **************************************************************** * PROBLEM DESCRIPTION: WLM-SPAS start up is a big overhead * * and sometimes on production it leads * * to sp request time-outs if an address * * space needs to be started. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 WLM-SPAS tasks are managed by WLM and WLM controls when a new address space needs to be started. The request is to use WLM service to start and keep a minimum number of WLM-SPAS so that a spike on SP request does not incur a heavy overhead in middle of operation.
Problem conclusion
A new option to be specified on the parameter to DSNX9WLM on the WLM startup JCL is introduced so user can specify a minimum number of address spaces to be kept for that particular environment. If this parameter is not specified, existing behavior prior to this change applies and WLM controls how many WLM-SPAS to keep. This new option will be implemented as new parameter to DSNX9WLM to the WLM start up JCL. For example: //DSN8WLMP PROC DB2SSN=DSN,NUMTCB=5,APPLENV=WLMTPSMP,MNSPAS=3 ... //WLMTPSMP EXEC PGM=DSNX9WLM,TIME=1440, // PARM='&DB2SSN,&NUMTCB,&APPLENV,&MNSPAS', // REGION=0M In the above example, a minimum of 3 WLM-SPAS will be started each with NUMTCB = 5. WLM will start the minimum number of address spaces on the first stored procedure request on that WLM environment. The valid number specified for the values of MNSPAS is between 0 to 50. A value of 0 means no minimum is specified and old behavior will apply. If the value of MNSPAS is invalid, message DSNX981E will be issued. If the new parameter is not specified, there will be no impact to the existing user base.
Temporary fix
Comments
APAR Information
APAR number
PM27097
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
YesSpecatt / New Function
Submitted date
2010-11-18
Closed date
2011-03-16
Last modified date
2012-01-16
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK65858 UK65859
Modules/Macros
DSNX9WLM
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:
16 January 2012