IBM DB2 Manual page 456

|
440
Application Programming Guide and Reference for Java
6. On DB2 for z/OS, enable the DB2-supplied stored procedures and define the
tables that are used by the IBM Data Server Driver for JDBC and SQLJ.
7. In z/OS UNIX System Services, run the DB2Binder utility to bind the
packages for the IBM Data Server Driver for JDBC and SQLJ.
8. Optional: In DB2 for z/OS, bind the IBM Data Server Driver for JDBC and
SQLJ packages into a plan.
One reason that you might continue to use a plan is that you want to continue
to use plan-level authorization. For example, suppose that when you ran the
DB2Binder utility, you specified a -collection parameter of JDBCCLID. You
bind your SQLJ packages into a package collection named SQLJJCLID. You
can use a BIND command like this to bind the packages into a plan:
BIND PLAN(JDBCPLAN) -
QUALIFIER(JDBCUSER) -
PKLIST(SQLJCLID.*, -
JDBCCLID.*)
ACTION(REPLACE)
RETAIN
VALIDATE(BIND)
After you bind the plan, you need to execute the SQL GRANT statement to
give JDBC and SQLJ users authorization to execute the plan. For example:
GRANT EXECUTE ON PLAN JDBCPLAN TO USER1;
9. If you plan to use IBM Data Server Driver for JDBC and SQLJ type 4
connectivity to implement distributed transactions against DB2 UDB for
OS/390 and z/OS Version 7 servers: In z/OS UNIX System Services, run the
DB2T4XAIndoubtUtil against each of those servers.
10. If you plan to use LOB locators to access DBCLOB or CLOB columns in DB2
tables on DB2 for z/OS servers: Create tables on the database servers that are
needed for fetching data from DBCLOB or CLOB columns using LOB locators.
Use one of the following techniques.
v On the DB2 for z/OS servers, customize and run job DSNTIJMS. That job is
located in data set prefix.SDSNSAMP.
v On the client, in z/OS UNIX System Services, run the
com.ibm.db2.jcc.DB2LobTableCreator utility against each of the DB2 for
z/OS servers.
11. Verify the installation by running a simple JDBC application.
12. For Java routines (stored procedures and user-defined functions):
a. In the JAVAENV data sets for your WLM environments, delete the
DB2_HOME environment variable and add a JCC_HOME environment
variable.
JCC_HOME must specify the highest-level directory in the set of
directories that contain the IBM Data Server Driver for JDBC and SQLJ
code. For example, if you install the IBM Data Server Driver for JDBC and
SQLJ in the default location of /usr/lpp/db2910/jcc, set JCC_HOME to
/usr/lpp/db2910/jcc.
b. If you specify JDBC/SQLJ Driver for OS/390 and z/OS driver-wide
properties for the stored procedure environment, you need to change to
comparable properties for the IBM Data Server Driver for JDBC and SQLJ.
For the IBM Data Server Driver for JDBC and SQLJ, you specify the
driver-wide properties by specifying the -Ddb2.jcc.propertiesFile=path
option in a file whose name you specify in the JVMPROPS environment
variable. You specify the JVMPROPS options in the ENVAR option of the
Language Environment options string. The Language Environment options
string is in a data set that is specified in a JAVAENV data set.
-
-
-
™