IMS Connect support for access to IMS DB

For IMS Connect clients, such as the IMS Universal drivers, that access databases that are managed by IMS DB in DBCTL and DB/TM environment, IMS Connect manages TCP/IP connections and routes incoming access requests among the instances of the CSL Open Database Manager (ODBM) and the IMS DB systems in an IMSplex.

IMS Connect is the TCP/IP server and front-end IMSplex message router for the IMS Universal drivers, which include:
  • IMS Universal Database resource adapter for the Java™ EE platform
  • IMS Universal JDBC driver
  • IMS Universal DL/I driver

The IMS Universal drivers provide direct, non-transactional access to IMS databases through TCP/IP connections for distributed application programs or local z/OS® application programs.

The IMS Universal drivers simplify the development of IMS Connect client application programs that access IMS DB through TCP/IP connections. The IMS Universal drivers do not use the IMS Connect IMS Request Message (IRM) communications protocol. The IMS Universal drivers also shield application developers from the underlying Distributed Relational Database Architecture™ (DRDA) that is used internally for communications between the IMS Universal drivers and IMS Connect.

Because IMS Connect supports the DRDA protocol and, with ODBM, is a complete DRDA target server, you can write application programs to the DRDA protocol directly; however, the IMS Universal Database resource adapter for the Java EE platform is the recommended API for accessing IMS databases through TCP/IP from a distributed environment.

IMS Connect support for the IMS Universal drivers includes support for global two-phase commit transactions.

IMS Connect supports communication with the IMS Universal drivers only on dedicated DRDA ports and only through shareable persistent sockets.

IMS Connect security support includes the IMS Connect DB Security user exit routine (HWSAUTH0), which can be used for greater control over the authentication of user IDs on connections that access IMS DB. RACF® is also supported.

IMS Connect support for the IMS Universal drivers is defined by the ODACCESS configuration statement in the IMS Connect configuration PROCLIB member and requires at least one instance of ODBM running in the same IMSplex as IMS Connect.