Administration and Programming Guide for OS/390
The SQL language environment (DTW_SQL) and the ODBC language environment
(DTW_ODBC) use the DB2 load module library SDSNLOAD. The
Net.Data SQL and ODBC language environments require that this library
reside in LINKLIST or that it be specified in the STEPLIB DD statement of the
Web server start-up procedure. The name and location of the Web server
start-up procedure depends on your system configuration.
Required:
- Create a plan for Net.Data before using the Net.Data SQL and
ODBC language environments to call stored procedures or to execute other types
of SQL statements. The binds required for creating this plan depend on
the language environments that you plan to use and the version of DB2 you are
using.
- The SQL and ODBC Language Environments require RRS Attach Facility when
using Net.Data with ICAPI, GWAPI, and Net.Data Servlets.
Make sure the RRS Attach Facility is installed for DB2 and OS/390 RRS is
installed and configured properly.
Use one of the following approaches to bind the Net.Data DBRM into a
package.
- Use the sample JCL for binding the Net.Data. The samples
bind DBRM into a package, create a Net.Data plan that supports the use
of the SQL language environment, and grant EXECUTE authority on the plan to
PUBLIC. The sample JCL can be found in one of the following jobs:
- DTWBIND
- For the use of the SQL language environment with DB2 for OS/390 V5
- DTWBIND6
- For the use of the SQL language environment with DB2 UDB Server for OS/390
V6
- DTWOBIND
- For the use of the ODBC language environment, or both the ODBC language
environment and the SQL language environment, with DB2 for OS/390 V5
- DTWOBND6
- For the use of the ODBC language environment, or both the ODBC language
environment and the SQL language environment, with DB2 UDB Server for OS/390
V6
- If you plan to use both the SQL and ODBC language environments, bind the
DBRMs for DB2 CLI into the same plan as the Net.Data DBRM.
Sample JCL for binding the Net.Data DBRM and the DB2 CLI DBRMs into a
package, for creating a Net.Data plan that supports the use of the SQL
and ODBC language environments, and for granting EXECUTE authority on the plan
to PUBLIC can be found in DTW220.SDTWBASE(DTWOBIND).
You might need to make some minor changes to the sample JCL in order to
successfully execute the JCL within your environment:
- The prefix of the SDSNEXIT and SDSNLOAD dataset names specified in the
STEPLIB DD statement depend on the version of DB2 that you are using and might
be incorrect for your installation.
- The values specified by the SYSTEM option of the DSN command and the PLAN
option of the RUN command might also be incorrect for your
installation. The SYSTEM option of the DSN command specifies the name
of the DB2 subsystem and should be identical to the subsystem ID used for your
applications.
- The PLAN option of the RUN command specifies the name of the application
plan for the DSNTIAD program. If you plan to use stored procedures, you
might also need to bind the packages for the stored procedures into the
Net.Data plan.
Make whatever modifications are appropriate and submit the JCL.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]