StopServiceabilityTracing IBM data server driver configuration keyword
Specifies whether to stop serviceability logging when an SQLCODE specified through db2dumpSQLCodes is hit.
- Equivalent CLI keyword
- None
- Equivalent IBM® data server provider for .NET connection string keyword
- StopServiceabilityTracing
- IBM data server driver configuration file (db2dsdriver.cfg) syntax
parameter name="StopServiceabilityTracing" value="0 | 1"/>- Default setting:
- The default is 0. Serviceability logging for SQLCODEs configured via db2dumpSQLCodes is enabled at all times.
- Equivalent connection attribute:
- None
- Usage notes:
-
You can stop serviceability logging when certain SQLCODE's are hit by setting StopServiceabilityTracing to 1. Ensure that you have configured the SQLCODE's via db2dumpSQLCodes. Serviceability logging will not be stopped for specified SQLCODEs that do not occur when the logs are dumped. If the serviceability logging is stopped, you can restart it only when the application restarts.
- 1 - Serviceability logging is stopped for SQLCODE's specified via db2dumpSQLCodes.
- 0 - Serviceability logging is always enabled.
To stop serviceability logging when the SQLCODE's 30108 or 20542
occur:
<parameter name="db2dumpSQLCodes" value="30108,20542"/>
<parameter name="StopServiceabilityTracing" value="1"/>