Service Gateway for IMS/DB is a server interface that provides concurrent, real-time access to IMS data from TIBCO Object Service Broker. It ensures that data is presented to TIBCO Object Service Broker rules in a manner consistent with TIBCO Object Service Broker behavior. The navigation of the IMS database is defined in the IMS table definition and is therefore not required in each application that accesses IMS data.
The DRA interface provides a multi-user, single address space environment for TIBCO Object Service Broker access to IMS data. In addition, you can access DB2 data concurrently through the IMS External Subsystem Attach Facility (ESAF). Your DB2 data must be defined to TIBCO Object Service Broker using the TIBCO Object Service Broker interface to DB2 data. Refer to
Chapter 2, Operating the Service Gateway for IMS/DB and
TIBCO Service Gateway for DB2 Installing and Operating for more information.
You can also access IMS data concurrently through the IMS OTMA Callable Interface using the TIBCO Object Service Broker $OTMA tool and the @OTMA_MAP tool, which is a system interpreted table. Refer to
TIBCO Object Service Broker for z/OS External Environments and
TIBCO Object Service Broker Shareable Tools for information about this interface and these tools.
TIBCO Object Service Broker uses IMS services to provide retrieval and update access, and to ensure data integrity. Service Gateway for IMS/DB executes within the following Execution Environments:
When a Gateway is started, it establishes communication with the Data Object Broker. TIBCO Object Service Broker is passed a SYSIN parameter file, which identifies the type of Gateway and the number of Gateway tasks to initialize. The SYSIN parameter file (identified by the IMSSRV00 DDname) specifies additional gateway parameters such as SERVERID and IDPREFIX.
When the Execution Environment requests access to IMS data, the appropriate DL/I call is built and sent to IMS TM or CICS. The illustration following shows how data is sent to the Data Object Broker in variable length buffers up to a maximum of 31 KB. If a single request requires more than 31 KB of data, multiple 31 KB buffers are sent until the request is complete.
You can configure the Data Object Broker and the Service Gateway for IMS/DB to reside on different hosts and/or operating systems (z/OS, Windows, or Solaris). Service Gateway for IMS/DB must be in the same domain as the IMS database system. See
Connecting the Gateway to a Windows or Solaris Data Object Broker for additional information.
TIBCO Object Service Broker for z/OS Installing and Operating or
TIBCO Object Service Broker for Open Systems Installing and Operating for more information on communications requirements.