RSC/MP 7.3 Installation and Configuration Guide

Configuring the RSC/MP Transport (Piccolo)
HP NonStop Remote Server Call (RSC/MP) Installation and Configuration Guide522358-011
5-3
Overview of Piccolo
Overview of Piccolo
Piccolo consists of a single manager process (Pipeman) and one or more network
interface processes (NIFSOCK, NIFNB, NIFASY, and so on). These processes running
together provide the communications mechanism that connects the RSC/MP
application running on the workstation to the TDP running on the NonStop host,
through RSCPIPE (which also runs on the workstation). A single instance of Piccolo
can support multiple TDP processes on the NonStop host or multiple instances of
RSCPIPE and RSC/MP applications on a workstation as shown in Figure 5-1:
Configuration information for the Piccolo components (Pipeman and the NIF programs)
is read from a single Piccolo configuration file which is required to exist and to be
readable by the Piccolo components at all times while the system is running. Along
with other information, the configuration file contains the unique name of the machine
on which Piccolo is running. This means that every Piccolo configuration file on the
host and workstation must be different.
Figure 5-1. The Piccolo Components
Note. Do not alter the Piccolo configuration file while Piccolo is running. On Windows and
NonStop platforms, the PIPEMAN process locks its configuration file for read access, and
holds that lock for as long as Piccolo continues running. On UNIX platforms, the file is not
locked by Piccolo; changing the file while Piccolo is running will result in unpredictable
behavior.
TDP
TDP
PIPEMAN
PIPEMAN
RSCPIPE
RSCPIPE
NIF NIF
RSC/MP
application
RSC/MP
application
Workst at ionNonStop Host
CDT003