|
View previous topic :: View next topic
|
| Author |
Message |
dineshchaudhry
New User
Joined: 26 Mar 2009
Posts: 9
Location: India
|
|
|
|
Hi,
I am pretty new to DB2 WLM and Stored procedures. We have defined new WLM and few DB2 stored procedures (using Cobol) on z/OS. The stored procedures are called using Java client. We are facing some problems in bouncing (bring-down and bring-up) of WLM. Sometimes even after the call to stored procedure is complete, DB2 threads are still active. This hinders new bind to stored procedures and also bring down of WLM. How can this issue be addressed ? Can there any timeout parameter defined at SP level ?
Dinesh. |
|
| Back to top |
|
 |
a027412
New User
Joined: 05 Jul 2007
Posts: 40
Location: Minneapolis, MN
|
|
|
|
The timeout parameter can be defined at the ROUTINE level using "ASUTIME LIMIT <time in mill sec>"
| Code: |
.
.
COLLID TGTT8
WLM ENVIRONMENT DB2TSP2
ASUTIME LIMIT 500000
STAY RESIDENT NO
.
.
|
|
|
| Back to top |
|
|
|
|
