Accessing IMS databases through the ODBA interface
Open Database Access (ODBA) provides a callable interface that enables any z/OS® recoverable, resource-managed z/OS address space to issue DL/I database calls to an IMS DB subsystem.
The interface provides z/OS application programs (hereafter called ODBA applications) access to full-function DL/I databases and data entry databases (DEDBs). The ODBA application and IMS must coexist on the same z/OS image.
Application programs that use the ODBA interface can use the
APPLCTN macro or, if dynamic resource definition is enabled, the CREATE PGM
command or the Program Creation user exit routine (PGMCREAT) to define the PSB names required by the
ODBA applications.
The ODBA interface allows IMS DB and ODBA application programs to be developed, installed, and maintained independently. This independence provides failure isolation and resource recovery by using z/OS Resource Recovery Services (RRS).
You can achieve further failure isolation by configuring ODBA to use the CSL Open Database Manager (ODBM). ODBM can prevent an IMS abend 0113 from occurring if an ODBA application terminates unexpectedly during DL/I processing. You can configure ODBA to use ODBM by specifying the ODBMNAME and IMSPLEX parameters with the other IMS database resource adapter (DRA) interface startup parameters in the DFSxxxx0 member. The ODBA interface uses the DRA interface to communicate with IMS DB.
If you use WebSphere Application Server or WebSphere Liberty Profile Server and access IMS databases with type-2 IMS Universal Database resource adapter connectivity, you must run ODBM with Resource Recovery Services (RRS). To learn more, see IMS Universal drivers: WebSphere Application Server Liberty type-2 connections.
The ODBA interface resides in the z/OS address space and is recognized by IMS as an application region (hereafter called the z/OS application region).