IBM DB2 Manual page 459

When you use the planName property, you bind plans for your SQLJ programs
and the JDBC driver. When you use the pkList property, you bind packages for
your SQLJ programs and the JDBC driver. This means that if you move from using
SQLJ and JDBC plans to packages, you need to grant execution privileges on the
SQLJ and JDBC packages to users.
Driver-level properties
With the IBM Data Server Driver for JDBC and SQLJ, you set driver-level
properties by setting configuration properties, rather than setting properties in an
SQLJ/JDBC run-time properties file. There are a number of differences between
those driver-level properties. The following table lists the driver-level JDBC/SQLJ
Driver for OS/390 and z/OS properties and their IBM Data Server Driver for JDBC
and SQLJ equivalents. If you specify any of the JDBC/SQLJ Driver for OS/390 and
z/OS properties, you need to set the equivalent IBM Data Server Driver for JDBC
and SQLJ configuration property when you migrate.
Table 96. JDBC/SQLJ Driver for OS/390 and z/OS properties and their IBM Data Server Driver for JDBC and SQLJ
equivalents
JDBC/SQLJ Driver for OS/390 and z/OS
property
DB2SQLJSSID
DB2SQLJPLANNAME
db2.sqlj.profile.caching
DB2ACCTINTERVAL
Chapter 9. Migrating from the JDBC/SQLJ Driver for OS/390 and z/OS to the IBM Data Server Driver for JDBC and SQLJ
IBM Data Server Driver for JDBC
and SQLJ equivalent
db2.jcc.ssid
db2.jcc.planName
db2.jcc.disableSQLJProfileCaching
db2.jcc.accountingInterval
Notes
Property values are the same in the
JDBC/SQLJ Driver for OS/390 and
z/OS and the IBM Data Server Driver
for JDBC and SQLJ.
v The default for DB2SQLJPLANNAME
is DSNJDBC. The default for
db2.jcc.planName is null.
v db2.jcc.pkList is the preferred
alternative to db2.jcc.planName. Use
of db2.jcc.pkList results in
package-level authorization, rather
than plan-level authorization.
v If you specify db2.jcc.planName, you
need to bind the JDBC driver
packages into a plan after you migrate
to the IBM Data Server Driver for
JDBC and SQLJ.
v Both properties have possible values
of YES and NO, but the meanings of
the same value are opposite.
v A db2.sqlj.profile.caching value of YES
is equivalent to a
db2.jcc.disableSQLJProfileCaching
value of NO.
v A db2.sqlj.profile.caching value of NO
is equivalent to a
db2.jcc.disableSQLJProfileCaching
value of YES.
v The default for db2.sqlj.profile.caching
is YES, and the default for
db2.jcc.disableSQLJProfileCaching
value of NO.
Property values are the same in the
JDBC/SQLJ Driver for OS/390 and
z/OS and the IBM Data Server Driver
for JDBC and SQLJ.
443