EGL Reference Guide for iSeries
In a Java run unit, the details are as follows:
- When any of the Java programs ends with a hard error, the effect is
equivalent to performing rollbacks, closing cursors, and releasing
locks.
- When the run unit ends successfully, EGL performs a commit, closes
cursors, and releases locks.
- You can use multiple connections to read from multiple databases, but you
should update only one database in a unit of work because only a one-phase
commit is available. For related information, see
sysLib.connectionService.
- When an EGL-generated program is accessed by way of an EGL-generated EJB
session bean, transaction control may be affected by a transaction attribute
(also called the container transaction type), which is in the deployment
descriptor of the EJB session bean. The transaction attribute affects
transaction control only when the linkage options part, callLink element,
property remoteComType for the call is direct, as described in
remoteComType in callLink element.
The EJB session bean is generated with transaction attribute REQUIRED, but
you can change the value at deployment time. For details on the
implications of the transaction attribute, see your Java documentation.
Related concepts
MQSeries support
Run unit
SQL support
Related tasks
Setting up a J2EE JDBC connection
Understanding how a standard JDBC connection is made
Related reference
Default database
sysLib.commit
sysLib.connectionService
sysLib.rollback
Java wrapper classes
luwControl in callLink element
remoteComType in callLink element
sqlDB
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]
(C) Copyright IBM Corporation 1992, 2005. All Rights Reserved.