RSC/MP Installation and Configuration Guide

Configuring the RSC/MP Transport (Piccolo) Large-Message Support
Starting with RSC/MP 7.0, the maximum message size has been increased from
31000 bytes to 56000 bytes for RscWrite and RscWriteRead to a named server. Where
applications require the new expanded maximum message size, Piccolo must be
explicitly configured on both the host and the workstation to provide large-message
support. If either the host or the workstation is not configured to allow large messages,
then the lesser limit of 31000 bytes will apply to RscWrite and RscWriteRead traffic,
and attempts to send UMS messages larger than 31000 bytes will cause incorrect
operation.
To configure Piccolo for large-message support, set the EnableLargeMessages entry in
the [PIPEMAN] section to 1:
EnableLargeMessages=1
The following conditions must be met in order to use large messages successfully:
Piccolo must be configured for large-message support on both the host and the
workstation. This configuration can be verified by using the PIPECP utility. If the
correct configuration setting has been made, the output of the PIPECP STATUS
should include the following line:
Large Messages: Enabled
The TDP (on the host), RSCPIPE, and RSC/MP application processes (on the
workstation) all must be able to locate and read the Piccolo configuration file.
Therefore, set the PIPEINI environment variable to contain the fully qualified file
name of the Piccolo configuration file before any TDP or client-side processes are
run. The TDP (on the host), RSCPIPE, and RSC/MP application processes (on the
workstation) must have read access to the Piccolo configuration file (see
Components in a Single Instance of Piccolo on page 5-5 and consider the access
marked ―optional‖ to be ―required‖ when large messages will be used).
The NonStop operating system must be RVU D48 or higher. If the NonStop RVU is
insufficient to allow Piccolo to provide large-message support, and
EnableLargeMessages=1 is added to the [PIPEMAN] section of the Piccolo
configuration file,the output of PIPECP STATUS will include the following:
Large Messages: Not available
Failure to meet any of these conditions will result in incorrect operation. In particular, if
the TDP does not run with a correct PARAM PIPEINI or if a workstation-side RSC/MP
process (either RSCPIPE or the RSC/MP application) does not run with a correct
PIPEINI environment variable value, RSC/MP will fail to transfer large messages even
when the PIPECP STATUS output indicates that large messages are enabled.
HP NonStop Remote Server Call (RSC/MP) Installation and Configuration G uide — 52235 8- 013
5 -1 4