System Architecture

Within a CICS region, product components are located in two separate environments – an application environment, and an EMS execution environment.

The following picture shows the main components and architecture of TIBCO EMS Client for z/OS (CICS).

Note: The CICS EMS Execution Environment provides a task that is referred to by the acronym CEET (CICS EMS Execution Task).

CICS Application Environment

These product components perform the following functions:
  • S7MASTUB: takes a TIBCO EMS function call and hands the call request to the S7M3PASS module.
  • S7M3PASS: manages the interactions between CICS transactions and the CEET; also manages the runtime interactions to the CEET Work Threads.
  • S7MATRUE: releases CEET Work Threads upon transaction end.
  • S7M3CLUP: an independent cleanup routine tied to transaction S7ML.

CICS EMS Execution Environment

This environment provides the CEET, the primary component of which is module S7M3EMSS. This module executes all TIBCO EMS Client requests received from CICS transactions. Messages from the CEET are written to an output file called the CEET log. In the CICS JCL, it is either DDNAME SYSPRINT or SYSxxxxx, where xxxxx represents an auto-generated number.