02.12.2012 Views

OpenVMS Cluster Systems - OpenVMS Systems - HP

OpenVMS Cluster Systems - OpenVMS Systems - HP

OpenVMS Cluster Systems - OpenVMS Systems - HP

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Cluster</strong> System Parameters<br />

A.1 Values for Alpha and VAX Computers<br />

Table A–2 (Cont.) <strong>Cluster</strong> System Parameters Reserved for <strong>OpenVMS</strong> Use Only<br />

Parameter Description<br />

PASANITY PASANITY controls whether the CI and DSSI port sanity timers are enabled<br />

to permit remote systems to detect a system that has been hung at IPL 8 or<br />

higher for 100 seconds. It also controls whether virtual circuit checking gets<br />

enabled on the local system. The TIMVCFAIL parameter controls the time<br />

(1–99 seconds).<br />

PASANITY is normally set to 1 and should be set to 0 only if you are<br />

debugging with XDELTA or planning to halt the CPU for periods of 100<br />

seconds or more.<br />

PASANITY is only semidynamic. A new value of PASANITY takes effect on<br />

the next CI or DSSI port reinitialization.<br />

If CI or DSSI devices are not configured on your system, this parameter is<br />

ignored.<br />

PASTDGBUF The number of datagram receive buffers to queue initially for each CI or<br />

DSSI port driver’s configuration poller; the initial value is expanded during<br />

system operation, if needed.<br />

If no CI or DSSI devices are configured on your system, this parameter is<br />

ignored.<br />

PASTIMOUT The basic interval at which the CI port driver wakes up to perform timebased<br />

bookkeeping operations. It is also the period after which a timeout<br />

will be declared if no response to a start handshake datagram has been<br />

received.<br />

If no CI or DSSI device is configured on your system, this parameter is<br />

ignored.<br />

PRCPOLINTERVAL Specifies, in seconds, the polling interval used to look for SCS applications,<br />

such as the connection manager and MSCP disks, on other computers. Each<br />

computer is polled, at most, once each interval.<br />

This parameter trades polling overhead against quick recognition of new<br />

computers or servers as they appear.<br />

SCSMAXMSG The maximum number of bytes of system application data in one sequenced<br />

message. The amount of physical memory consumed by one message is<br />

SCSMAXMSG plus the overhead for buffer management.<br />

If an SCS port is not configured on your system, this parameter is ignored.<br />

SCSMAXDG Specifies the maximum number of bytes of application data in one datagram.<br />

If an SCS port is not configured on your system, this parameter is ignored.<br />

SCSFLOWCUSH Specifies the lower limit for receive buffers at which point SCS starts to<br />

notify the remote SCS of new receive buffers. For each connection, SCS<br />

tracks the number of receive buffers available. SCS communicates this<br />

number to the SCS at the remote end of the connection. However, SCS does<br />

not need to do this for each new receive buffer added. Instead, SCS notifies<br />

the remote SCS of new receive buffers if the number of receive buffers falls<br />

as low as the SCSFLOWCUSH value.<br />

If an SCS port is not configured on your system, this parameter is ignored.<br />

A–14 <strong>Cluster</strong> System Parameters

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!