Product Overview

With TIBCO® EMS Client for z/OS (CICS), you can run applications in CICS Transaction Server to produce and consume messages that are transported by TIBCO EMS servers.

Messages are structured data that one application sends to another. TIBCO EMS servers, running on platforms outside the traditional CICS environment under z/OS, act as intermediaries for messages and route them to recipients. The following picture shows the message flow.

A CICS application participates in this messaging environment as follows:
  1. The CICS application embeds TIBCO EMS API function calls to facilitate message communication.
  2. TIBCO EMS Client for z/OS (CICS) establishes connections to a TIBCO EMS server using standard TCP/IP (not CICS sockets).
  3. The CICS application sends messages to or receives messages from the TIBCO EMS server using destinations for message routing.
  4. Other TIBCO EMS clients exchange messages with the CICS application by the TIBCO EMS server.

TIBCO EMS API function calls are coded by programmers and included into the CICS application at compilation time. The product <USERHLQ>.LIBRARY data set contains the objects that are included during the pre-link step of a compilation.

For details on the components that comprise TIBCO EMS Client for z/OS (CICS), see System Architecture.

See TIBCO Enterprise Message Service User’s Guide for a complete description of TIBCO EMS operations.

Note: This version of the TIBCO EMS Client for z/OS (CICS) does not support the following functions:
  • SSL (Secure Sockets Layer)
  • Asynchronous message consumption
  • Administration
  • Assembler language