RSC/MP 7.3 Installation and Configuration Guide

Migration to RSC/MP 7.2
HP NonStop Remote Server Call (RSC/MP) Installation and Configuration Guide—522358-011
A-13
Method 2: Using Compatibility Mode
On the host, Piccolo must be configured with a NIFASY for each device through which
RSC/MP clients will connect.
Piccolo Configuration File Example (host):
[nif-example]
ProgramFile=nifasy
ComDevice=COM2
Piccolo Configuration File Example (client):
[nif-example]ProgramFile=nifasy
ComDevice=COM2
Use of Multiple NIFs
The following discussion applies to RSC/MP clients on which the Piccolo transport has
been configured to run multiple NIF processes. The RSC layer will push Compatibility
Mode settings to the Piccolo layer and Piccolo will use every running NIF to attempt a
connection until one NIF succeeds or all NIFs have failed. For example, if both the
HOST_INET_ADDRESS option and the asynchronous options (COM_PORT, BAUD
RATE, and so on) have been set, and Piccolo is running with a NIFSOCK and a
NIFASY, then the connection will be attempted by both TCP/IP and asynchronous
means.
In certain situations, it may be desirable to constrain RSCPIPE to use a specific NIF.
For example, suppose that a TCP/IP transport and an asynchronous transport were
configured in the RSC Classic application (TCP and ASYNC). If the application is
programmatically setting the SUBSYSTEM_NAME to select which port will be used,
then it would be inefficient to allow Piccolo to disregard the distinction and try both
ports anyway. In such a case, RSCPIPE should be invoked with the special flag
-nifname which causes RSCPIPE to push an internal directive to Piccolo which
constrains connection requests to be processed by only a single NIF:
rscpipe -nifname name (
command line
)
SUBSYSTEM_CMDLINE="-nifname name" (
in RSC.INI for auto start of RSCPIPE
)
The example on the next page shows the relationship between the application code,
Piccolo configuration files and RSCPIPE invocation to direct NIF selection.