v For user packages, -action drop indicates that the specified package
should be dropped.
-action drop applies only if the target database server is DB2 for z/OS.
-size
Controls the number of Statement, PreparedStatement,orCallableStatement
objects that can be open concurrently, or the number of IBM Data Server
Driver for JDBC and SQLJ packages that are dropped.
The meaning of the -size parameter depends on the -action parameter:
v If the value of -action is add or replace, the value of -size is an integer that
is used to calculate the number of DB2 packages that the IBM Data Server
Driver for JDBC and SQLJ binds. If the value of -size is integer, the total
number of packages is:
number-of-isolation-levels*
number-of-holdability-values*
integer+
number-of-packages-for-static-SQL
= 4*2*integer+1
The default -size value for -action add or -action replace is 3.
In most cases, the default of 3 is adequate. If your applications throw
SQLExceptions with -805 SQLCODEs, check that the applications close all
unused resources. If they do, increase the -size value.
If the value of -action is replace, and the value of -size results in fewer
packages than already exist, no packages are dropped.
v If the value of -action is drop, the value of -size is the number of packages
that are dropped. If -size is not specified, all IBM Data Server Driver for
JDBC and SQLJ packages are dropped.
v If the value of -action is rebind, -size is ignored.
-collection
Specifies the collection ID for IBM Data Server Driver for JDBC and SQLJ or
user packages. The default is NULLID. DB2Binder translates this value to
uppercase.
You can create multiple instances of the IBM Data Server Driver for JDBC and
SQLJ packages on a single database server by running
com.ibm.db2.jcc.DB2Binder multiple times, and specifying a different value for
-collection each time. At run time, you select a copy of the IBM Data Server
Driver for JDBC and SQLJ by setting the currentPackageSet property to a
value that matches a -collection value.
-tracelevel
Specifies what to trace while DB2Binder runs.
-reopt
Specifies whether DB2 for z/OS database servers determine access paths at run
time. This option is valid only for connections to DB2 for z/OS database
servers. This option is not sent to the database server if it is not specified. In
that case, the database server determines the reoptimization behavior.
none Specifies that access paths are not determined at run time.
always
Specifies that access paths are determined each time a statement is run.
once Specifies that DB2 determines and caches the access path for a
dynamic statement only once at run time. DB2 uses this access path
Chapter 8. Installing the IBM Data Server Driver for JDBC and SQLJ 423
|
|
|
|
|
||
|
|
||
|
To Next Page
Loading...
Need help?
General