Parameters for rvd

This section describes VMS parameters affect Rendezvous daemon operation.

High message rates consume significant space in non-paged storage.

The byte limit parameter restricts the amount of non-paged storage that a VMS process can use. If rvd fails during accept(), exceeding its byte count quota, raise this resource limit.

The Rendezvous daemon requires sufficient non-paged buffer space for messages. The actual requirement depends on the speed of the network, the network card, the processors, and the message data rate. We recommend a value of 6000000.

Boot Time

When starting the Rendezvous daemon at boot time, the SYSTEM account’s bytlm parameter controls this resource limit. To set this parameter, modify these commands appropriately:

$ set def sys$system

$ run authorize

UAF> mod SYSTEM /bytlm=6000000

Automatic Start

When programs start the Rendezvous daemon automatically, the SYSGEN parameter PQL_DBYTLM specifies this resource limit. Set an appropriate value using the AUTOGEN tool.

Total Non-Paged Storage

The SYSGEN parameters NPAGEDYN and NPAGEDYNVIR specify the total pool of non-paged storage. (In contrast, the byte limit specifies the fraction of this pool that each process may use.)

The pool begins at boot time with size NPAGEDYN, and automatically expands as needed, up to a limit of NPAGEVIR. We recommend that you monitor the pool to ensure sufficient space. For example:

$ show memory

$ show memory /pool /full

If the pool is too small, use the AUTOGEN tool to set an appropriate size.

Page File Quota

The Rendezvous daemon process requires sufficient virtual address buffer space to retain outbound messages for the duration of the reliability interval. To calculate the actual requirement, estimate the maximum number of bytes per reliability window for all Rendezvous message activity, add space for future expansion, then divide by 512 (the number of bytes per block).

(The factory default reliability interval is 60 seconds. For a complete discussion the concept of reliability, the various ways to control it, the interaction among those ways, and reasonable values, see Reliability and Message Retention Time on in TIBCO Rendezvous Administration.)

Boot Time

When starting the Rendezvous daemon at boot time, the SYSTEM account’s pgflquo parameter controls this resource limit. To set this parameter, modify these commands appropriately:

$ set def sys$system

$ run authorize

UAF> mod SYSTEM /pgflquo=1000000

Automatic Start

When programs start the Rendezvous daemon automatically, the SYSGEN parameter PQL_DPGFLQUOTA controls this resource limit. Set an appropriate value using the AUTOGEN tool.

Channel Count

In addition to the usual requirements for I/O channels, rvd uses I/O channels in two more ways:

•

Each client connection from a network transport object consumes one channel.

•

Each UDP service that those clients access consumes one channel.

The special SYSGEN parameter CHANNELCNT determines the maximum number of I/O devices that a process can access. Although most systems set a sufficiently high value, we recommend that you estimate the number of channels that rvd requires, and verify that the limit is significantly larger than your estimate. For example:

$ mc sysgen

SYSGEN> show channelcnt

If rvd fails during accept(), reporting invalid I/O channels, raise this resource limit using the AUTOGEN tool.