EasyManuals Logo

IBM DB2 User Manual

IBM DB2
585 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Page #262 background imageLoading...
Page #262 background image
The following example specifies a package list for a IBM Data Server Driver
for JDBC and SQLJ instance whose packages are in collection JDBCCID. SQLJ
applications that are prepared under this driver instance are bound into
collections SQLJCID1, SQLJCID2, or SQLJCID3.
db2.jcc.pkList=JDBCCID.*,SQLJCID1.*,SQLJCID2.*,SQLJCID3.*
db2.jcc.planName
Specifies a DB2 for z/OS plan name that is used for the underlying RRSAF
CREATE THREAD call when a JDBC or SQLJ connection to a data source is
established. Specify this property if you bind plans for your SQLJ programs
and for the JDBC driver packages. If you specify this property, do not specify
db2.jcc.pkList.
db2.jcc.planName applies only to IBM Data Server Driver for JDBC and SQLJ
type 2 connectivity on DB2 for z/OS. db2.jcc.planName does not apply to
applications that run under CICS or IMS, or to Java stored procedures. The
JDBC driver ignores the db2.jcc.planName setting in those cases.
If you do not specify this property or the db2.jcc.pkList property, the IBM Data
Server Driver for JDBC and SQLJ uses the db2.jcc.pkList default value of
NULLID.*.
If you specify db2.jcc.planName, you need to bind the packages that you
produce when you run com.ibm.db2.jcc.DB2Binder into a plan whose name is
the value of this property. You also need to bind all SQLJ packages into a plan
whose name is the value of this property.
You can override db2.jcc.planName by setting the planName property for a
Connection or DataSource object.
The following example specifies a plan name of MYPLAN for the IBM Data
Server Driver for JDBC and SQLJ JDBC packages and SQLJ packages.
db2.jcc.planName=MYPLAN
db2.jcc.progressiveStreaming or db2.jcc.override.progressiveStreaming
Specifies whether the JDBC driver uses progressive streaming when
progressive streaming is supported on the data source.
With progressive streaming, also known as dynamic data format, the data
source dynamically determines the most efficient mode in which to return LOB
or XML data, based on the size of the LOBs or XML objects.
Valid values are:
1 Use progressive streaming, if the data source supports it.
2 Do not use progressive streaming.
db2.jcc.rollbackOnShutdown
Specifies whether DB2 for z/OS forces a rollback operation and disables
further operations on JDBC connections that are in a unit of work during
processing of JVM shutdown hooks.
db2.jcc.rollbackOnShutdown applies to IBM Data Server Driver for JDBC and
SQLJ type 2 connectivity only.
db2.jcc.rollbackOnShutdown does not apply to the CICS, IMS, stored
procedure, or WebSphere Application Server environments.
Possible values are:
yes or true
The IBM Data Server Driver for JDBC and SQLJ directs DB2 for z/OS
246 Application Programming Guide and Reference for Java
â„¢
|
|
|
|
|
|
|
||
||
|
|
|
|
|
|
|
|
|
|
|

Table of Contents

Questions and Answers:

Question and Answer IconNeed help?

Do you have a question about the IBM DB2 and is the answer not in the manual?

IBM DB2 Specifications

General IconGeneral
DeveloperIBM
Initial Release1983
LicenseProprietary
Written inC, C++
CategoryDatabase Management System (RDBMS)
Operating SystemLinux, Windows
Programming LanguagesC, C++
Data ModelsRelational
EditionsCommunity, Standard, Advanced
Key Featureshigh availability, scalability