EasyManua.ls 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 #265 background image
You should set the trace properties under the direction of IBM Software
Support.
db2.jcc.traceLevel or db2.jcc.override.traceLevel
Specifies what to trace.
The db2.jcc.override.traceLevel property overrides the traceLevel property for
a Connection or DataSource object.
You specify one or more trace levels by specifying a decimal value. The trace
levels are the same as the trace levels that are defined for the traceLevel
property on a Connection or DataSource object.
To specify more than one trace level, do an OR (|) operation on the values,
and specify the result in decimal in the db2.jcc.traceLevel or
db2.jcc.override.traceLevel specification.
For example, suppose that you want to specify TRACE_DRDA_FLOWS and
TRACE_CONNECTIONS for db2.jcc.override.traceLevel.
TRACE_DRDA_FLOWS has a hexadecimal value of X’40’.
TRACE_CONNECTION_CALLS has a hexadecimal value of X’01’. To specify
both traces, do a bitwise OR operation on the two values, which results in
X’41’. The decimal equivalent is 65, so you specify:
db2.jcc.override.traceLevel=65
db2.jcc.ssid
Specifies the DB2 for z/OS subsystem to which applications make connections
with IBM Data Server Driver for JDBC and SQLJ type 2 connectivity on DB2
for z/OS.
The db2.jcc.ssid value can be the name of the local DB2 subsystem or a group
attachment name.
For example:
db2.jcc.ssid=DB2A
The ssid Connection and DataSource property overrides db2.jcc.ssid.
If you specify a group attachment name, and the DB2 subsystem to which an
application is connected fails, the connection terminates. However, when new
connections use that group attachment name, DB2 for z/OS uses group
attachment processing to find an active DB2 subsystem to which to connect.
If you do not specify the db2.jcc.ssid property, the IBM Data Server Driver for
JDBC and SQLJ uses the SSID value from the DSNHDECP data-only load
module. When you install DB2 for z/OS, a DSNHDECP module is created in
the prefix.SDSNEXIT data set and the prefix.SDSNLOAD data set. Other
DSNHDECP load modules might be created in other data sets for selected
applications.
The IBM Data Server Driver for JDBC and SQLJ must load a DSNHDECP
module before it can read the SSID value. z/OS searches data sets in the
following places, and in the following order, for the DSNHDECP module:
1. Job pack area (JPA)
2. TASKLIB
3. STEPLIB or JOBLIB
4. LPA
5. Libraries in the link list
You need to ensure that if your system has more than one copy of the
DSNHDECP module, z/OS finds the data set that contains the correct copy for
the IBM Data Server Driver for JDBC and SQLJ first.
Chapter 7. JDBC and SQLJ reference information 249

Table of Contents

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

Summary

JDBC application programming

How JDBC applications connect to a data source

Explains how JDBC applications establish a connection to a data source.

Connecting to a data source using the DataSource interface

Details on connecting to a data source using the DataSource interface for portability.

How to determine which type of IBM Data Server Driver for JDBC and SQLJ connectivity to use

Guidance on selecting the appropriate IBM Data Server Driver connectivity type.

JDBC interfaces for executing SQL

Explains the JDBC interfaces used for executing SQL statements.

Data retrieval in JDBC applications

Explains how to retrieve data from tables using ResultSet objects.

SQLJ application programming

Connecting to a data source using SQLJ

Explains how to connect to a data source in an SQLJ program.

SQLJ connection technique 1: JDBC DriverManager interface

Details SQLJ connection using the JDBC DriverManager interface.

SQLJ connection technique 2: JDBC DriverManager interface

Details SQLJ connection using the JDBC DriverManager interface.

SQLJ connection technique 3: JDBC DataSource interface

Details SQLJ connection using the JDBC DataSource interface.

SQLJ connection technique 4: JDBC DataSource interface

Details SQLJ connection using the JDBC DataSource interface.

SQL statement execution in SQLJ applications

Describes executing SQL statements within SQLJ.

Performing positioned UPDATE and DELETE operations in an SQLJ application

Details performing positioned UPDATE and DELETE operations in SQLJ.

Data retrieval in SQLJ applications

Explains how to retrieve result sets using SQLJ iterators.

Controlling the execution of SQL statements in SQLJ

Describes how to control SQL statement execution in SQLJ.

Handling SQL errors and warnings in SQLJ applications

Details handling SQL errors and warnings in SQLJ.

Handling SQL errors in an SQLJ application

Explains how to handle SQL errors in SQLJ applications.

Java stored procedures and user-defined functions

Setting up the environment for Java routines

Details on setting up the WLM and Java environments for Java routines.

Setting up the WLM application environment for Java routines

Describes setting up WLM application environments for Java routines.

WLM address space startup procedure for Java routines

Provides an example of a WLM address space startup procedure for Java routines.

Run-time environment for Java routines

Explains the run-time environment setup for Java routines.

Definition of a Java routine to DB2

Explains how to define a Java routine to DB2.

Writing a Java stored procedure to return result sets

Explains how to write Java stored procedures that return multiple result sets.

Preparing and running JDBC and SQLJ programs

Program preparation for JDBC programs

Details the preparation process for JDBC programs.

Program preparation for SQLJ programs

Outlines the preparation process for SQLJ programs.

Binding SQLJ applications to access multiple database servers

Explains how to bind SQLJ applications to multiple DB2 servers.

Preparing Java routines with no SQLJ clauses to run from a JAR file

Steps to prepare Java routines from JAR files.

Preparing Java routines with SQLJ clauses to run from a JAR file

Recommended method for preparing SQLJ routines from JAR files.

Running JDBC and SQLJ programs

Explains how to run JDBC and SQLJ programs.

JDBC and SQLJ reference information

Data types that map to database data types in Java applications

Summarizes mappings of Java data types to database data types.

Properties for the IBM Data Server Driver for JDBC and SQLJ

Defines how connection properties define the connection to a data source.

currentQueryOptimization

Specifies a value that controls the class of query optimization.

Common IBM Data Server Driver for JDBC and SQLJ properties for DB2 for z/OS and IDS

Lists properties specific to DB2 for z/OS and IDS database servers.

Common IBM Data Server Driver for JDBC and SQLJ properties for DB2 Database for Linux, UNIX, and Windows

Lists properties specific to DB2 Database for Linux, UNIX, and Windows servers.

Installing the IBM Data Server Driver for JDBC and SQLJ

Installing the IBM Data Server Driver for JDBC and SQLJ as part of a DB2 installation

Details on installing the driver as part of DB2 installation.

Jobs for loading the IBM Data Server Driver for JDBC and SQLJ libraries

Describes jobs for loading the driver libraries.

Environment variables for the IBM Data Server Driver for JDBC and SQLJ

Lists required environment variables for the driver.

Customization of IBM Data Server Driver for JDBC and SQLJ configuration properties

Explains how to customize driver configuration properties.

DB2Binder utility

Explains the DB2Binder utility for binding DB2 packages.

Migrating from the JDBC/SQLJ Driver for OS/390 and z/OS to the IBM Data Server Driver for JDBC and SQLJ

To migrate to the IBM Data Server Driver for JDBC and SQLJ, follow these steps

Provides steps for migrating to the IBM Data Server Driver.

Security under the IBM Data Server Driver for JDBC and SQLJ

User ID and password security under the IBM Data Server Driver for JDBC and SQLJ

Details user ID and password security for JDBC connections.

User ID-only security under the IBM Data Server Driver for JDBC and SQLJ

Explains user ID-only security for JDBC connections.

Kerberos security under the IBM Data Server Driver for JDBC and SQLJ

Details Kerberos security support for JDBC and SQLJ.

Configuring the Java Runtime Environment to use SSL

Explains how to configure the Java Runtime Environment for SSL.

JDBC connection concentrator and workload balancing

Problem diagnosis with the IBM Data Server Driver for JDBC and SQLJ

Collecting JDBC trace data

Explains procedures for starting JDBC trace collection.

System monitoring for the IBM Data Server Driver for JDBC and SQLJ

Glossary