Software requirements for Java application programs that use the IMS Universal drivers or JDR resource adapter
The IMS Universal drivers that Java™ application programs can use to access IMS data have software requirements.
IMS 15.5 requires the following software:
- z/OS® UNIX System Services available at run time.
- Hierarchic File System (HFS) or zFS. For information on preparing HFS, see z/OS UNIX System Services File System Interface Reference.
The IMS Universal drivers and JDR resource adapter have the following runtime software requirements:
- IBM® SDK, Java Technology Edition, version 8.0.2.10, Java 11, Java 17, and Java 21, available from IBM Support Fix Central.
- One or more of the following conditional requirements:
- For CICS® applications, IBM CICS Transaction Server for z/OS Version 5.5 (5655-Y04), or later, as determined by the SDK version.
- For Db2® stored procedures, Db2 12 for z/OS (5650-DB2®) or later.
- For WebSphere® Application Server for z/OS (5655-W65) or WebSphere Application Server for distributed platforms (5724-J08), version 8.5.5 or later is required, as determined by the supported SDK level.
- RACF® or an equivalent product.
Java application programs that use the IMS Universal drivers also require a way to generate the IMS database metadata, such as using the IMS Enterprise Suite Explorer for Development.
JAR and RAR files for type-4 connectivity
The following table describes the JAR and RAR files that provide type-4 connectivity for the IMS Universal drivers:
Driver | JAR or RAR file |
---|---|
IBM IMS Universal DL/I driver | pathprefix/usr/lpp/ims/ims155/imsjava/imsudb.jar |
IBM IMS Universal JDBC driver | pathprefix/usr/lpp/ims/ims155/imsjava/imsudb.jar |
IBM IMS Universal Database resource adapter |
|
JAR and RAR files for type-2 connectivity
The following table describes the JAR and RAR files that provide type-2 connectivity for the IMS Universal drivers:
Driver | JAR file |
---|---|
IMS Universal DL/I driver | pathprefix/usr/lpp/ims/ims155/imsjava/imsudb.jar |
IMS Universal JDBC driver | pathprefix/usr/lpp/ims/ims155/imsjava/imsudb.jar |
IMS Universal Database resource adapter | For use within WebSphere Application Server (both z/OS and distributed platforms):
|
- The transaction scope is local (a unit of work is scoped to a particular connection). Multiple connections can have independent units of work associated with each connection.
- Application programs can issue local commit and rollback calls through either the JDBC Connection interface or the CCI LocalTransaction interface.
- ContainerManaged beans are supported, but require the following properties to be set in the EJB
Deployment Descriptor:
- In the Bean tab, specify the following properties under the LocalTransaction heading:
- Boundary = BeanMethod
- Resolver = ContainerAtBoundary
- Unresolved action = Rollback
- In the Assembly tab, set the transaction scope to NotSupported.
- In the Bean tab, specify the following properties under the LocalTransaction heading:
- Specifies a global scope transaction model in which a unit of work can span multiple bean methods. RRS-managed transaction applications use this driver type. The container coordinates commit and rollback processing through RRS.
- Application programs can use the UserTransaction interface for explicit commit and rollback calls.