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.

The IMS Universal drivers have the following runtime software requirements:

  • IBM® SDK, Java Technology Edition, Version 6.0.1 or later (31-bit or 64-bit)
  • One or more of the following conditional requirements:
    • For CICS® applications, IBM CICS Transaction Server for z/OS® Version 4.1 (5655-S97) or later
    • For Db2® stored procedures:
      • Start of changeDb2 11 for z/OS (5615-DB2®) or laterEnd of change
      • Db2 10 for z/OS (5605-DB2)
      • Db2 for z/OS Version 9.1 (5635-DB2)
    • For WebSphere® applications, WebSphere Application Server for z/OS (5655-N02) or WebSphere Application Server for distributed platforms (5724-J08), Version 7.0.1 or later. You must use the fix pack that contains WebSphere Application Server APAR PK89274 installed in the system.
  • 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: Start of changeUse binary-mode FTP to transfer the IMS Universal drivers JAR or RAR files to another system.End of change

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:

Table 1. Type-4 connectivity JAR and RAR files for Java applications that use the IMS Universal drivers
Driver JAR or RAR file
IBM IMS Universal DL/I driver pathprefix/usr/lpp/ims/ims13/imsjava/imsudb.jar
IBM IMS Universal JDBC driver pathprefix/usr/lpp/ims/ims13/imsjava/imsudb.jar
IBM IMS Universal Database resource adapter For use within WebSphere Application Server (both z/OS and distributed platforms):
  • pathprefix/usr/lpp/ims/ims13/imsjava/rar/imsudbJLocal.rar for JCA/JDBC local transaction processing only
  • pathprefix/usr/lpp/ims/ims13/imsjava/rar/imsudbJXA.rar for JCA/JDBC two-phase (XA) commit processing or local transaction processing
  • pathprefix/usr/lpp/ims/ims13/imsjava/rar/imsudbLocal.rar for CCI local transaction support
  • pathprefix/usr/lpp/ims/ims13/imsjava/rar/imsudbXA.rar for CCI two-phase commit (XA) transaction support

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:

Table 2. Type-2 connectivity JAR and RAR files for Java applications that use the IMS Universal drivers
Driver JAR file
IMS Universal DL/I driver pathprefix/usr/lpp/ims/ims13/imsjava/imsudb.jar
IMS Universal JDBC driver pathprefix/usr/lpp/ims/ims13/imsjava/imsudb.jar
IMS Universal Database resource adapter For use within WebSphere Application Server (both z/OS and distributed platforms):
  • pathprefix/usr/lpp/ims/ims13/imsjava/rar/imsudbLocal.rar for CCI programming interface to perform SQL or DL/I data operations
  • pathprefix/usr/lpp/ims/ims13/imsjava/rar/imsudbJLocal.rar for JDBC programming interface to perform SQL data operations
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.
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.
Parent topic: Software requirements for Java applications that access IMS databases