IBM DB2 User Manual

Table 95. DB2Binder return codes when the target operating system is Windows (continued)
Return
code Meaning
-401 The Binder class was not found.
-402 Connection to the database server failed.
-403 DatabaseMetaData retrieval for the database server failed.
-501 No more packages are available in the cluster.
-502 An existing package is not valid.
-503 The bind process returned an error.
-999 An error occurred during processing of an undocumented bind option.
Related tasks
“Installing the z/OS Application Connectivity to DB2 for z/OS feature” on
page 435
Chapter 9, “Migrating from the JDBC/SQLJ Driver for OS/390 and z/OS to the
IBM Data Server Driver for JDBC and SQLJ,” on page 439
“Upgrading the IBM Data Server Driver for JDBC and SQLJ to a new version”
on page 434
″Keeping prepared statements after commit points″ (DB2 Application
Programming and SQL Guide)
DB2T4XAIndoubtUtil for distributed transactions with DB2
UDB for OS/390 and z/OS Version 7 servers
If you plan to implement distributed transactions using IBM Data Server Driver for
JDBC and SQLJ type 4 connectivity that include DB2 UDB for OS/390 and z/OS
Version 7 servers, you need to run the DB2T4XAIndoubtUtil utility against those
servers.
DB2T4XAIndoubtUtil allows Version 7 servers, which do not have built-in support
for distributed transactions that implement the XA specification, to emulate that
support.
DB2T4XAIndoubtUtil performs one or both of the following tasks:
v Creates a table named SYSIBM.INDOUBT and an associated index
v Binds DB2 packages named T4XAIN01, T4XAIN02, T4XAIN03, and T4XAIN04
You should create and drop packages T4XAIN01, T4XAIN02, T4XAIN03, and
T4XAIN04 only by running DB2T4XAIndoubtUtil. You can create and drop
SYSTEM.INDOUBT and its index manually, but it is recommended that you use
the utility. See DB2T4XAIndoubtUtil usage notes for instructions on how to create
those objects manually.
DB2T4XAIndoubtUtil authorization
To run the DB2T4XAIndoubtUtil utility to create SYSTEM.INDOUBT and bind
packages T4XAIN01, T4XAIN02, T4XAIN03, and T4XAIN04, you need SYSADM
authority.
To run the DB2T4XAIndoubtUtil only to bind packages T4XAIN01, T4XAIN02,
T4XAIN03, and T4XAIN04, you need BIND authority on the packages.
428 Application Programming Guide and Reference for Java
™

IBM DB2 Specifications

General

Developer	IBM
Initial Release	1983
License	Proprietary
Written in	C, C++
Category	Database Management System (RDBMS)
Operating System	Linux, Windows
Programming Languages	C, C++
Data Models	Relational
Editions	Community, Standard, Advanced
Key Features	high availability, scalability