RSC/MP Installation and Configuration Guide

Configuring the RSC/MP Transport (Piccolo) Creating the [PIPEMAN] Section (for all installations)
Creating the [PIPEMAN] Section (for all
installations)
System Names and Addresses
Every instance of Pipeman in a network is considered a Piccolo system. Each Piccolo
system must have a unique system address. The system address of a Pipeman
instance is derived by Piccolo by combining the system name and domain name in its
configuration file.
The SystemName option is required, except for Windows systems where it can be
automatically generated at run-time. The DomainName option is optional. For
configurations using network name resolution services (such as Domain Name
Services with TCP/IP), these two entries together should give the network node name
of the machine when joined with a dot. For example, a NonStop host at
myhost.mycompany.com would use:
SystemName=myhost
DomainName=mycompany.com
These names must uniquely identify this machine among all machines connected by
Piccolo as part of an RSC/MP installation. In particular, be sure that each workstation
has a unique name; two workstations havi ng the same name will fail on attempting to
connect with a common host. (The system name generated automatically on Windows
workstations is derived from the network interface card‘s identity; therefore, the
generated names should be inherently unique.)
Configuring Network Connections
A network connection is defined by the Network Interface (NIF) section
([NIF-nifname]). Each NIF section supplies the parameters needed to make and/or
receive connections. The information supplied in a NIF section identifies the low-level
protocol (TCP/IP for example) and the information needed by the protocol to
communicate over the network. For instance, a NIF section for a TCP/IP connection
would, as a minimum, state that TCP/IP is the protocol and supply the service port.
One or more NIF sections may be defined.
The NifList option entry in the [PIPEMAN] section lists the name of one or more
network interfaces that should be started when Pipeman starts. Each NIF is identified
by an arbitrary name that must match the name in the [NIF-nifname] section header.
NIF sections not included in the NifList must be started manually using the PIPECP
START nifname command in order to be operable.
HP NonStop Remote Server Call (RSC/MP) Installation and Configuration G uide — 52235 8- 013
5 -1 2