Version 9.6
 —  Broker  —

Broker Quick Reference

This document covers the following topics:

Functionality: Communication Models

The table below shows which functionality of EntireX Broker is supported by each of the two communication models: Client and Server and Publish and Subscribe.

Functionality Client and Server Publish and Subscribe
Application bindings (stubs) x x
Command and Information Services x x
Accounting x  
Data compression x x
Codepage conversion x x
Persistent store x x
Security x x
Units of work x  

Top of page

ACI Syntax of Messaging Model

This table provides the ACI syntax used in both of EntireX Broker's communication models Client and Server and Publish and Subscribe

Messaging Term Client and Server Publish and Subscribe
Client Server Publish Subscribe


Synchronous not applicable not applicable
Asynchronous (3)


Conversational (3) not applicable not applicable
Non-conversational (3)  


  1. The synchronous SEND, WAIT=YES command contains an implied RECEIVE command.
  2. The subscriber has the option of specifying WAIT=YES.
    Example: The subscriber uses a repeat loop that issues a RECEIVE_PUBLICATION. The advantage is that the program runs continuously, processing publications arising as random events, which simplifies programming effort.
  3. Persistence available. See Concepts of Persistent Messaging.

Top of page

Location of Broker Kernel and Stubs

This graphic shows the locations where the broker kernel and broker stubs can be installed. See Architecture of Broker Kernel and Architecture of Broker Stub.


Top of page

Transport: Broker Stubs and APIs

This table gives an overview of the transport methods supported by EntireX Broker stubs.

Operating System Environment Module Transport to Broker
z/OS (2) Batch, TSO, IMS (BMP) BROKER x x x  
Com-plete COMETB x (3) x  
CICS CICSETB x (3) x  
IMS (MPP) MPPETB x x x  
IDMS/DC (4) IDMSETB x (3)    
Natural NATETB23 x x x  
UNIX System Services Java ACI x x   x
UNIX x x    
Java ACI x x   x
Windows broker.dll (5) x x    
Java ACI x x   x
BS2000/OSD Batch, Dialog (formerly TIAM) BROKER x x x  
z/VSE Batch BKIMB x   x  
CICS BKIMC x   x  
z/VM BKIMBCMS x   x  
IBM i EXA x      
OpenVMS BROKER x x    


  1. NET is available for transport to a broker running under mainframe platforms only; not to a broker running under UNIX or Windows.
  2. Under z/OS you can use IBM's Application Transparent Transport Layer Security (AT-TLS) as an alternative to direct SSL support inside the broker stub. Refer to the IBM documentation for more information.
  3. Use AT-TLS. See Note 2.
  4. Tracing and transport timeout are not supported in this environment.
  5. Stub broker32.dll is supported for reasons of backward compatibility. The functionality is identical to broker.dll.
  6. Via Broker HTTP(S) Agent; see Settting up and Administering the Broker HTTP(S) Agent under UNIX | Windows.

See also:

Top of page