Basic mapping support (BMS)

The mapping operations of BMS are performed in the system on which the user’s transaction is running; that is, in the application-owning region. The mapped information is routed between the terminal and this transaction via the relay transaction, as for terminal control operations.

For BMS page building and routing requests, the pages are built and stored in the application-owning region. When the logical message is complete, the pages are shipped to the terminal-owning region (or regions, if they were generated by a routing request), and deleted from the application-owning region. Page retrieval requests are processed by a BMS program running in the system to which the terminal is connected.

BMS message routing to remote terminals and operators

You can use the BMS ROUTE command to route messages to remote terminals. For programming information about the BMS ROUTE command, see the CICS® Application Programming Reference manual. You cannot, however, route a message to a selected remote operator or operator class unless you also specify the terminal at which the message is to be delivered.

Table 2 shows how the possible combinations of route list entries and OPCLASS options govern the delivery of routed messages to remote terminals. In all cases, the remote terminal must be defined in the system that issues the ROUTE command (or a shipped terminal definition must already be available; see Shipping terminal and connection definitions). Note that the facility described in Shipping terminals for automatic transaction initiation does not apply to terminals addressed by the ROUTE command.

Table 2. BMS message routing to remote terminals and operators
LIST entry OPCLASS Result
None specified Not specified

The message is routed to all the remote terminals defined in the originating system.

Entries specifying a terminal but not an operator Not specified

The message is routed to the specified remote terminal.

Entries specifying a terminal but not an operator Specified

The message is delivered to the specified remote terminal when an operator with the specified OPCLASS is signed on.

None specified Specified

The message is not delivered to any remote operator.

Entries specifying an operator but not a terminal (Ignored)

The message is not delivered to the remote operator.

Entries specifying both a terminal and an operator (Ignored)

The message is delivered to the specified remote terminal when the specified operator is signed on.

Related concepts
Introduction to CICS dynamic routing
Overview of transaction routing
Terminal-initiated transaction routing
Traditional routing of transactions started by ATI
Allocation of remote APPC connections
The relay program
Defining indirect links for transaction routing
Related tasks
Routing transactions invoked by START commands
Using the routing transaction (CRTE)
System programming for transaction routing
Defining remote resources for transaction routing
Application programming for CICS transaction routing
Related reference
Appendix A. Intercommunication rules and restrictions checklist
[[ Contents Previous Page | Next Page Index ]]