NET/MASTER Management Services (MS) System Management Guide

Process-to-Process Connection Guidelines
Supporting Remote Operations
105744 Tandem Computers Incorporated 9–19
Process-to-Process
Connection Guidelines
This subsection provides guidelines for adding session and unit definitions used for
process-to-process (PTP) connections. Use the PTP connection to link NonStop
NET/MASTER MS systems under two circumstances:
The NonStop NET/MASTER MS systems reside on the same node
The nodes are connected by one or more Expand lines (although not necessarily
adjacent)
Be sure to start the link on the node designated secondary in the unit definition before
starting the link on the node designated primary. Also, define remote passwords to
allow access to both ends of the link. Refer to “Example 2: Expand Star,” later in this
section, for an example of how the commands and operands are used.
PTP Session Definition
Guidelines
Add a session definition for each PTP connection between NonStop NET/MASTER
MS systems. A PTP connection can be used to link two NonStop NET/MASTER MS
systems. Table 9-8 provides guidelines for defining PTP sessions.
Table 9-8. PTP Session Definition Guidelines
SESSION DEFINE
Operand Definition Guidelines
session-name Specifies the name of the session, from 1 to 12 displayable characters;
alphabetic characters are shifted to uppercase.
LINK Specifies the name of the link to which the session belongs.
TYPE PTP, to specify a PTP link.
COMMENT An optional text string of up to 50 characters.
None of the other SESSION DEFINE command operands apply to PTP links.
PTP Unit Definition
Guidelines
The unit in a PTP session identifies a file, known as a mailbox file, that is used to
establish a session with the process responsible for INMC processing in a remote
NonStop NET/MASTER MS system. The session is established after the following
steps are executed:
1. The secondary process creates the mailbox file.
2. The primary process reads the file to determine the name of the secondary process
with which it should exchange data blocks.
3. The secondary process then derives information about the primary process from
the primary process’s contact message.