On 5 Nov, 18:14, db2admin <jag...@gmail.comwrote:
Quote:
On Nov 4, 12:37*pm, Salvatore Vacca <s.va...@gmail.comwrote:
>
Quote:
On 4 Nov, 18:10, db2admin <jag...@gmail.comwrote:
>
>
Quote:
Quote:
Sometime, clients disconnect after starting sql and sql keep running
in the db2 engine making it a runaway sql.
is there something in DB2 which can avoid this behavior i.e. clean any
agents/subagents/sqls when client is no longer connected ?
>
Quote:
I’m not sure if SET CLIENT command can help you; see following link:
>
>
Quote:
Regards
Salvatore Vacca
>
thankyou,
i am going to look into that
i also noticed this DB2CHECKCLIENTINTERVAL parameter
is this something which can also help to clean runaway sql ?
It depends on which version of db2 are you using; as you can see from
documentation the default value of DB2CHECKCLIENTINTERVAL is 50 for
version >= 8.1.4, prior to version 8.1.4, the default value was 0 (no
client connection verifications is performed).
http://publib.boulder.ibm.com/infoce.../r0005660.html 
