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-11
Creating the Configuration File (for all installations)
running) and at least one network interface. This sample configuration file is for a
workstation myworkstation.mycompany.com that will connect to NonStop hosts using
TCP/IP service port 5001:
[PIPEMAN]
SystemName=myworkstation
DomainName=mycompany.com
NifList=tcp
[NIF-tcp]
ProgramFile=nifsock
ServicePort=5001
The NifList entry appears in the [PIPEMAN] section of the configuration file, and gives
the names of the network interfaces that should be started automatically when
Pipeman is started.
The NifList setting can span multiple lines as in the following example:
NifList=nif1,nif2,nif3,nif4,nif5
NifList1=nif6,nif7,nif8,nif9,nif10
NifList2=
NifList3=nif11,nif12
The number of NIFs that can be specified (horizontally) in any one line is limited to 32
by Piccolo, and effectively to a lesser number if the operating system limits the number
of characters per line in the configuration file.
NifList=nif1,nif2,nif3,nif4,nif5 ... nif32
The number of NifList configuration entries (vertically) is limited to 32. These lines must
be numbered sequentially; without skipping a value, even if no nifname is listed:
NifList=nif1
NifList1=nif2
NifList2=
NifList3=nif4
.
.
.
NifList31=nif32
In performing the automatic NIF startup, Pipeman continues processing NifListn lines
with increasing n, until it fails to find a line. Existing lines that have empty lists (as with
NifList2 in the example above) do not stop this search (in the example, the NIF listed in
NifList3 will be started). If the whole line containing NifList2 were omitted, Pipeman
would stop searching for additional NIFs to start up. Therefore, nif4 would not be
automatically started when Pipeman starts.