IBM DB2 Manual page 457

|
|
|
|
|
|
Chapter 9. Migrating from the JDBC/SQLJ Driver for OS/390 and z/OS to the IBM Data Server Driver for JDBC and SQLJ
c. Check the routine definitions in the DB2 catalog.
If the value of COLLID in SYSIBM.SYSROUTINES is DSNJDBC, you need
to take one of the following actions:
v Bind the IBM Data Server Driver for JDBC and SQLJ packages into a
collection with the DSNJDBC collection ID.
v Redefine the routines with a COLLID value that matches the collection
ID for the IBM Data Server Driver for JDBC and SQLJ packages. That
value is the -collid value that you specified in the DB2Binder utility. If
you did not specify a value, the collection ID is NULLID.
If the COLLID value in SYSIBM.SYSROUTINES is blank, the collection ID
of the stored procedure is the same as the collection ID of the programs
that call it. You need to take one of the following actions:
v Redefine the routines with a COLLID value that matches the collection
ID for the IBM Data Server Driver for JDBC and SQLJ packages. That
value is the -collid value that was specified in the DB2Binder utility.
v Modify the invoking programs:
– If the invoking programs use packages, bind those packages into a
collection with a collection ID that matches the collection ID for the
IBM Data Server Driver for JDBC and SQLJ packages.
– If the invoking programs do not use packages, change the invoking
programs to specify the package collections that include the routine
procedure packages and the IBM Data Server Driver for JDBC and
SQLJ packages. DB2 resolves the packages by using the CURRENT
PACKAGE PATH special register, the CURRENT PACKAGESET
special register, or the PKLIST bind option (in this order).
v Modify the routines to specify the package collections that include any
packages that the routine invokes, and the IBM Data Server Driver for
JDBC and SQLJ packages.
13. If differences between the JDBC/SQLJ Driver for OS/390 and z/OS and the
IBM Data Server Driver for JDBC and SQLJ make application changes
necessary, make those changes.
14. Choose one of the following methods to migrate your SQLJ serialized profiles
and packages from the JDBC/SQLJ Driver for OS/390 and z/OS to the IBM
Data Server Driver for JDBC and SQLJ:
v Recommended method: Translate, customize, and bind packages for all of
your SQLJ applications that use the IBM Data Server Driver for JDBC and
SQLJ. Use the IBM Data Server Driver for JDBC and SQLJ sqlj utility to
translate the source code. Then use the db2sqljcustomize utility to
customize the serialized profiles and bind the DB2 packages.
(db2sqljcustomize binds DB2 packages as well as customizes the serialized
profiles if you use the default setting of -automaticbind YES. If you set
-automaticbind to NO, you need to run db2sqljbind to bind the DB2
packages.)
v Alternative method: In z/OS UNIX System Services, run the
db2sqljupgrade utility. If you choose this method, you do not need to bind
new packages for your SQLJ applications.
Important: When the db2sqljupgrade utility creates serialized profiles for
the IBM Data Server Driver for JDBC and SQLJ, db2sqljupgrade retrieves
the information about input and output host variables and parameters, such
as the data type, length, name, and encoding scheme, from the serialized
profiles that were created under the JDBC/SQLJ Driver for OS/390 and
z/OS. Information that is provided by the JDBC/SQLJ Driver for OS/390
441