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 ROUTE. 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.

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 1. 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.



dfht1c0068.html | Timestamp icon Last updated: Sunday, 4 June 2017