RSC/MP Installation and Configuration Guide

Installing RSC/MP on Windows Workstations Running RSC/MP From a File Server
Running RSC/MP From a File Server
In order to run RSC/MP from a file server, the RSC/MP product must be installed to a
directory on a mapped drive (for example, NET USE R: \\SERVER\RSCSHARE) so
that the BIN subdirectory can be added to the PATH (for example,
PATH=%PATH%;R:\BIN). During installation to a file server, answer ―No‖ to the
question ―Do you want to run RSC/MP as a service?‖.
When sharing configuration files stored on the file server, use the automatic
SystemName generation function and follow the rules by which the Pipeman process
and the Piccolo API locate the Piccolo configuration file (see RSC/MP components use
the following search sequence to locate Piccolo configuration files: on page 5-6). Also
consider that the Pipeman process will hold a read lock on its configuration file while it
runs; this means that a shared configuration file cannot be altered until Piccolo is
stopped on every user's machine.
The Pipeman process, the RSCPIPE process, and the RSC/MP API all provide
diagnostic logging capabilities. To avoid contention for output files, do one of the
following :
Specify different names for output files on the file server.
Direct output files to the local workstations. For example, in the PIPE.INI file use
―LogFileName=C:\RSC_LOG\PIPELOG‖, which will cause the Piccolo diagnostic
output to be written to a local file on the C: drive of each workstation.
HP NonStop Remote Server Call (RSC/MP) Installation and Configuration G uide — 52235 8- 013
4 -1 4