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-13

Automatic Startup of Piccolo

Piccolo must be running in order for RSC/MP to be usable. Piccolo can be started

directly by using the PIPECP START command, or it can be configured to start

automatically when needed by RSC/MP. To use automatic startup, set the AutoStart

entry in the [PIPEMAN] section to 1:

AutoStart=1

Automatic startup can be used on the host, the workstation, or both. If used on the

host, the TDP starts Piccolo. If used on the workstation, Piccolo will be started by the

RSC/MP API library when an RSC/MP application makes its first call to RscConnect().

The following conditions must be met:

1. The TDP (on the host) or RSC/MP application process (on the workstation) must

be able to locate and read the Piccolo configuration file. Therefore, you should set

the PIPEINI environment variable to contain the fully qualified file name of the

Piccolo configuration file before running the TDP or the RSC/MP application. The

TDP or RSC/MP application must have “read” access to the Piccolo configuration

file (see Figure 5-2 and consider the access marked “optional” to be “required” for

automatic startup).

2. The TDP or RSC/MP application process must be able to execute the Piccolo

PIPEMAN executable.

•

On the host, PIPEMAN should be installed to the same subvolume that holds

the TDP executable. This is its default installation location.

•

On the workstation, the PIPEMAN executable (“pipeman” on UNIX,

“pipeman.exe” on Windows) must be present in the RSC/MP application

process's current working directory, or must be found in a directory named in

the PATH environment variable. In this regard, automatic startup of PIPEMAN

works just the same as the automatic startup of RSCPIPE. Therefore, the

PIPEMAN and RSCPIPE executables should generally be located in the same

directory, as they are in a default installation of the RSC/MP product.

3. On Windows, RSC/MP must not be installed as a service. (Instead of using the

AutoStart option, RSC/MP can be installed as a service and configured to start

automatically when the system starts up. See Running RSC/MP as a Service on

page 4-7 for information on installing RSC/MP as a service.)

Large-Message Support

In its default configuration, Piccolo provides the support necessary for RSC/MP to

transfer messages of up to 31000 bytes, which was the maximum message size for

RscWrite, RscWriteRead, and UMS message traffic in all versions prior to RSC/MP

7.0.