Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 8 Using the TIBCO Service Gateway for IMS TM : How to Run IMS TM Applications

How to Run IMS TM Applications
Functional Overview
You can run IMS TM applications using the Service Gateway for IMS TM which enables you to use IMS TM clients to run IMS TM applications that access TIBCO Object Service Broker from an IMS TM Message Processing Region (MPR). You can start the clients by either conversational or non-conversational IMS TM transactions.
Using TIBCO Object Service Broker IMS TM Client Programs
When an IMS TM MPR has established communication with a Native Execution Environment, you can establish a TIBCO Object Service Broker session by scheduling an IMS TM transaction associated with one of the TIBCO Object Service Broker IMS TM client programs. There are eight client programs with the format S6BIMxxx. These are described in Selecting a TIBCO Object Service Broker IMS TM Program Style.
Each S6BIMxxx program takes its messages from the IMS Message Queue and sends these, together with session parameters, to the Native Execution Environment, where a session is started. The session runs the application as determined by the startup rule and, upon completion, returns output messages and session and client directives to the TIBCO Object Service Broker IMS TM client S6BIMxxx. The client terminates and the MPR schedules another transaction.
How a Client Session is Established
When a client session is being established, the IMS TM client program in the MPR first locates the Native Execution Environment and passes it the session start request. Since IMS TM is a multiple-session TP monitor, the Native Execution Environment is established separately, typically under operational control.
The following illustration shows how a typical supplied IMS TM client establishes a session from the MPR in a Native Execution Environment:
IMS TM and TIBCO Object Service Broker Interaction
A user IMS transaction can start a TIBCO Object Service Broker based IMS transaction and its associated IMS TM client by sending an output message to the TIBCO Object Service Broker based IMS transaction, as shown below:
Similarly, a terminating TIBCO Object Service Broker session can pass data to a subsequent IMS transaction or Message Formatting Services (MFS) MODname to be scheduled in the IMS environment. Facilities are provided in the rules language to specify the next IMS transaction or MFS MODname and the output message segments.
Replacing IMS TM Programs with TIBCO Object Service Broker Rules
Existing IMS TM programs can be replaced by TIBCO Object Service Broker rules without changing interfaces to the previous and succeeding programs.
Using this example, transaction A invokes transaction B and transaction B invokes transaction C. Initially, these are all IMS transactions. Over time, these transactions can be replaced by TIBCO Object Service Broker rules that implement the same, or enhanced functionality. For example, in the illustration above, the program in transaction B is replaced with a TIBCO Object Service Broker IMS TM client.
See Also
TIBCO Object Service Broker for z/OS Installing and Operating about installing the IMS TM component of TIBCO Object Service Broker.
TIBCO Object Service Broker Programming in Rules about writing rules.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved