NET/MASTER Management Services (MS) System Management Guide

Regulating Intersystem Message Flows
Supporting Remote Operations
9–32 105744 Tandem Computers Incorporated
For example, the following command enables the local system to exchange unsolicited
messages with a link named “TANGIERS”:
ISR ENABLE LINK=TANGIERS UNSOLICIT=YES
You can qualify direction of message flow by using the INBOUND and OUTBOUND
operands of the SOLICIT and UNSOLICIT options. Consider the example of the
network depicted in Figure 9-5. Suppose that you want \NODEA to receive
unsolicited messages from each of the satellite nodes. Issue this command from the
NonStop NET/MASTER MS system running on \NODEA:
ISR ENABLE UNSOLICIT=INBOUND
Since the command is not qualified by the LINK operand, the command enables
receipt of unsolicited messages from all other nodes with active links to \NODEA.
The command on \NODEA does not unilaterally start the flow of messages. The flow
becomes active only after both ends of the link have enabled flow. The end of the link
that sends messages must enable the flow of outbound messages, and the receiving
end of the link must enable the flow of inbound messages. Accordingly, to continue
with the example of Figure 9-5, you must also configure the ISR flow on the satellite
nodes by issuing this command from the NonStop NET/MASTER MS system running
on each satellite node:
ISR ENABLE LINK=NODEA UNSOLICIT=OUTBOUND
The example assumes that each satellite has the name NODEA for the link between
itself and \NODEA.
Message Traffic Planning
Considerations
Advance planning of message traffic patterns helps you prevent flow problems,
economize use of resources, and otherwise spare aggravation. Although shutting off
message flow can reduce network traffic, ensure that all nodes managed by NonStop
NET/MASTER MS send messages to at least one operations node.