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-7
Managing Multiple Instances of Piccolo (for
advanced installations)
Managing Multiple Instances of Piccolo (for
advanced installations)
For platforms that support instances of Piccolo, changing the configuration file name
allows for convenient management of the multiple configurations. For example, you
can name each configuration differently, such as PIPEINI1, PIPEINI2, and so on.
The CFGSW command facilitates the management of multiple Piccolo instances on
UNIX workstations and the NonStop host. This command switches the configuration
file to be used by PIPECP for subsequent commands. Use of the CFGSW configfile-
name command is equivalent to quitting from PIPECP, setting the environment variable
PIPEINI to configfile-name, and restarting PIPECP.
The syntax of the CFGSW command is:
CFGSW [configfile-name]
or
CF [configfile-name]
The single, optional argument specifies the fully qualified file name of the desired
configuration file. If this file name is omitted, CFGSW reports the name of the current
configuration file.
The following example shows that the current configuration file is PIPEINI, and that the
Piccolo instance described by that file is not running:
pipecp> cfgsw
PIPEINI: \SYSA.$DISKA.VOL1.PIPEINI
IPC Key: $PIPE
Piccolo is not running.
To switch to use a different configuration file for subsequent commands, enter the fully
qualified file name:
pipecp> cfgsw \sysa.$diska.vol1.pipeini2
PIPEINI: \SYSA.$DISKA.VOL1.PIPEINI2
IPC Key: $PIPE2
Piccolo is running.
In this example, the output indicates that the alternate Piccolo instance configured by
PIPEINI2 is already running. Subsequent PIPECP commands will refer to this instance.
Figure 5-3 shows an example configuration in which a production environment is using
the default Piccolo instance, and a second Piccolo instance has been set up for
development purposes.