Design overview

The CICS® support that enables connection to DBCTL, via the database resource adapter (DRA), is based on the CICS resource manager interface (RMI), also known as the task-related user exit interface. However, because it is necessary to provide compatibility with the existing CICS-DL/I implementation (in terms of link-edit stubs, API return codes, and so on), a limited amount of support within CICS itself is provided, but there are no DBCTL release dependencies within the CICS modules.

The main components of the CICS-DBCTL interface are shown in Figure 1:
Figure 1. The major components of the CICS-DBCTL interface
In the CICS address space are: MENU, CONN, DISC, INQ and CONTROL transactions. User DL/I transactions, with the RMI stub. CICS itself (which has a log). All these can interface with DBCTL through the RMI or exits, the adapter, and DRA (as explained below). In the IMS/ESA address space are: DBCTL (with a log), DL/I, DBRC, and IRLM.
  • The connection process (CICS-DBCTL)
    CICS-DBCTL connection and disconnection programs
    These programs are used for establishing and terminating the connection with the DRA.
    CICS-DBCTL control program
    This program is responsible for resolving indoubt units of work after a CICS or DBCTL failure. It also outputs messages when DBCTL notifies CICS of a change in the status of the CICS-DBCTL interface.

    When the CICS disconnects from DBCTL, the control program is responsible for invoking the disable program which performs clean up.

    DRA control exit
    This exit is invoked by the DRA, when connection has been established with the DBCTL address space, to initiate the resynchronization process, that is, to initiate the resolution of indoubt units of work. It is also invoked to handle cases where connection to DBCTL cannot be achieved or when the connection has failed.
    DBCTL user-replaceable program
    This program is invoked whenever CICS successfully connects to DBCTL and whenever CICS disconnects from DBCTL.
    Disable program
    This program is invoked when CICS disconnects from DBCTL.
  • The DBCTL call processor program

    The function of this program is to issue an RMI call to DBCTL and to maintain compatibility with the existing CICS-DL/I interface in areas such as application program return codes, and so on.

  • The interface layer
    The adapter
    The adapter’s primary responsibility is interfacing the RMI and DRA parameter lists. Other responsibilities include the issuing of DRA initialization and termination calls, when invoked by the CICS connection and disconnection programs, and the management of CICS tasks, in order to effect an orderly shutdown of the CICS-DBCTL interface.
    DRA suspend and resume exits
    These exits are invoked by the DRA in order to suspend and resume a CICS task while a DL/I call is processed by DBCTL.
    Adapter exits
    There are four exits for use by the adapter:
    • The statistics exit
    • The token exit
    • The monitoring exit
    • The status exit.

Details of these components are described in the following sections.

Note: CICS documentation uses the term “connecting and disconnecting from DBCTL”. The DRA documentation refers to “initializing and terminating the CICS-DBCTL interface”. In general, these two terms are synonymous.


dfhs3c00220.html | Timestamp icon Last updated: Monday, 5 June 2017