Each multiplex connection must be described with a MUX statement. It is not possible to enter multiplex connections dynamically.
When multiplexing, the communication between the Session Manager and the application takes place using the PUTMMUX protocol. The task of this protocol is to enable several sessions to be processed via one transport connection and to provide the Session Manager with status information on the UTM application on BS2000 system.
A PUTMMUX connection can exist between a UTM application on BS2000 system and OMNIS as the Session Manager. PUTMMUX connections, also called “multiplex connections”, are defined by the MUX statement when generating the UTM application.
| MUX statement in section "MUX - define a multiplex connection (BS2000 systems)" |
name
Name of the multiplex connection.
BCAMAPPL=
Local application name of the UTM application, used by the Session Manager to establish the connection to the UTM application.
CONNECT=
Establishment of a transport connection to the Session Manager when the application starts.
MAXSES=
Maximum number of simultaneously active sessions between the Session Manager and the UTM application.
When establishing a multiplex connection, openUTM and OMNIS negotiate which MUX protocol versions are supported by both sides of the connection. If there are no MUX protocol versions supported by both partners, the multiplex connection is not established (UTM messages K140 and K141).
The following restrictions apply with the current definition of the protocol:
connections between two UTM applications are not supported
printers are not supported
only the Session Manager can open a session to a UTM application.
The add-on product OMNIS-MENU is available if you are using OMNIS in menu-driven mode. OMNIS-MENU enables you to communicate with various UTM applications via a user-friendly, menu-driven interface. For further details, see the manuals “OMNIS/OMNIS-MENU Functions and Commands” and “OMNIS/OMNIS-MENU Administration and Programming”.