RSC/MP 7.3 Installation and Configuration Guide

Configuring the RSC/MP Transport (Piccolo)
HP NonStop Remote Server Call (RSC/MP) Installation and Configuration Guide—522358-011
5-6
Configuring Multiple Instances of Piccolo (for
advanced installations)
•
On the NonStop host, the IPC key is the process name of the Pipeman process —
for example, $PIPE1, $PIPE2, and so on. The default IPC key is $PIPE.
•
On UNIX workstations, the IPC key is the full name of an existing file or directory
that will not change while Pipeman is running — for example,
/usr/users/rsc_production, /usr/users/rsc_debug, /usr/users/rsc_run/pipe.ini, and so
on. The default IPC key is /etc.
•
On Windows workstations, the IPC key names a Windows kernel object that
Piccolo will create in the global namespace. The IPC key is a case-sensitive string
of up to 255 characters that must not contain a backslash character (\). The default
IPC key is piccolo.
When the IPC key is missing from the configuration file — or the configuration file
cannot be read — the default IPC key is used. Therefore, in multi-instance
installations, all Piccolo configuration files must contain the correct IPC keys, and all
RSC/MP components must have access to the correct Piccolo configuration files. The
Piccolo Control Program (PIPECP) will indicate which configuration file it found when it
starts.
RSC/MP components use the following search sequence to locate Piccolo
configuration files:
1. Expand the PIPEINI environment variable, if it exists, and use the result as the fully
qualified path and file name of the configuration file. (Do not confuse this
environment variable name with the default Piccolo configuration file name for
NonStop host, which is also PIPEINI.)
2. If the PIPEINI environment variable is not set, then attempt to open the default
configuration file PIPEINI (on the NonStop host) or PIPE.INI (on all workstation
platforms) located in the current directory.
3. If the default configuration file is not found in the current directory, then search for
the default configuration file in other directories according to the PATH environment
variable.
The recommended approach is to use the PIPEINI environment variable to guide each
TDP, RSCPIPE, or RSC/MP application directly to the correct configuration file in all
cases where one must be found. Compared with PATH searches, this approach is less
error-prone from a maintenance viewpoint.
Note. When RSC/MP is installed as a service on the WIndows platform, only one Piccolo
instance is allowed. The Piccolo configuration file is required to be named pipe.ini and to
reside in the bin subdirectory under the RSC/MP product installation directory. The default
IPC key must be used. The following discussion of Multiple Instances of Piccolo is applicable
only when RSC/MP is installed but NOT run as a service.