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 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.
In IMS 15, the IMS Universal drivers provide the IMS
Java drivers and database resource adapters.
Note: The IMS Java dependent region (JDR) resource adapter reuses some of the interfaces and classes in the IMS Universal drivers. As a result, it is packaged as part
of the IMS Universal drivers
and has the same software
requirements as the IMS Universal drivers.
The IMS Universal drivers have the following runtime software requirements:
- IBM® SDK, Java Technology Edition, Version 8.0.2.10 or later (31-bit or 64-bit), 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.1 (5655-Y04) or later, as determined by the JDK version
- For Db2® stored procedures, Db2 11 for z/OS (5615-DB2®) or later
- For WebSphere® applications, WebSphere Application Server for z/OS (5655-W65) or WebSphere Application Server for distributed platforms (5724-J08), Version 8.5.5 or later, as determined by the supported JDK level.
- RACF® or an equivalent product
- The software requirements for the JDR resource adapter are the same as for the IMS Universal drivers.
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.
Note: Use binary-mode FTP to transfer the IMS Universal drivers JAR or RAR files to another
system.
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/ims15/imsjava/imsudb.jar |
| IBM IMS Universal JDBC driver | pathprefix/usr/lpp/ims/ims15/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/ims15/imsjava/imsudb.jar |
| IMS Universal JDBC driver | pathprefix/usr/lpp/ims/ims15/imsjava/imsudb.jar |
| IMS Universal Database resource adapter | For use within WebSphere Application Server (both z/OS and distributed platforms):
|
When DriverType=2:
- 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:
When DriverType=2_CTX:
- 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.