HP OpenVMS Systems Documentation
HP OpenVMS System Management Utilities Reference Manual
This parameter applies only to members of the system disk shadow set. All nodes using a particular system disk shadow set should have their SHADOW_SYS_TMO parameter set to the same value once normal operations begin.
The default value is 120 seconds. Change this parameter to a higher value if you want the system to wait more than the 120-second default for all members to join the shadow set. You can set the parameter value to 120 through 65,535 seconds.
SHADOW_SYS_UNITUse this parameter for Phase II shadowing only. The SHADOW_SYS_ UNIT parameter is an integer value that contains the virtual unit number of the system disk. The default value is 0. The maximum value allowed is 9999. This parameter is effective only when the SHADOW_SYS_DISK parameter has a value of 1. This parameter should be set to the same value on all nodes booting off a particular system disk shadow set. See HP Volume Shadowing for OpenVMS for more information about setting system parameters for volume shadowing.
SHADOW_SYS_WAITThe SHADOW_SYS_WAIT parameter extends the time a booting system waits for all current members of a mounted shadowed system disk to become available to this node. The shadow set must already be mounted by at least one other cluster node for this parameter to take effect.
The default value is 480 seconds. Change this parameter to a higher value if you want the system to wait more than the 480-second default for all members to join the shadow set. You can set the parameter value to 1 through 65,535 seconds.
SMCI_FLAGS (D)(Alpha Galaxy platforms only) The SMCI_FLAGS parameter controls operational aspects of SYS$PBDRIVER, the Galaxy Shared Memory Cluster Interconnect (SMCI).
Bits in the bit mask are the following:
SMCI_PORTS(Alpha Galaxy platforms only) The Shared Memory Cluster Interconnect (SMCI) system parameter SMCI_PORTS controls initial loading of SYS$PBDRIVER. This parameter is a bit mask; bits 0 through 25 each represent a controller letter. If bit 0 is set, which is the default setting, PBAx is loaded (where x represents the Galaxy Partition ID). If bit 1 is set, PBBx is loaded, and so on up to bit 25, which causes PBZx to be loaded. For OpenVMS Alpha Version 7.2 and later versions, HP recommends leaving this parameter at the default value of 1.
Loading additional ports allows multiple paths between Galaxy instances. In the initial release of the Galaxy software, having multiple communications channels is not an advantage because SYS$PBDRIVER does not support fast path. A future release of OpenVMS will provide Fast Path support for SYS$PBDRIVER, when multiple CPUs improve throughput by providing multiple communications channels between instances.
SMP_CPUSSMP_CPUS identifies which secondary processors, if available, are to be booted into the multiprocessing system at boot time. SMP_CPUS is a 32-bit mask; if the value of a bit in the mask is 1, the processor with the corresponding CPU ID is booted into the multiprocessing system (if it is available). For example, if you want to boot only the CPUs with CPU IDs 0 and 1, specify the value 3 (both bits are on).
The default value of SMP_CPUS, --1, boots all available CPUs into the multiprocessing system.
Note that although a bit in the mask corresponds to the primary processor's CPU ID, the primary processor is always booted. That is, if the mask is set to 0, the primary CPU still boots. Any available secondary processors are not booted into the multiprocessing system.
This parameter is ignored if the MULTIPROCESSING parameter is set to 0.
SMP_CPUSHSMP_CPUSH is a special parameter reserved for HP use only. HP recommends that you use the default value.
SMP_LNGSPINWAITCertain shared resources in a multiprocessing system take longer to become available than allowed by the SMP_SPINWAIT parameter. SMP_LNGSPINWAIT establishes, in 10-microsecond intervals, the length of time a processor in a multiprocessing system waits for these resources. A timeout causes a CPUSPINWAIT bugcheck.
SMP_SANITY_CNTSMP_SANITY_CNT establishes, in 10-millisecond intervals, the timeout period for each CPU in a symmetric multiprocessing (SMP) system. Each CPU in an SMP system monitors the sanity timer of one other CPU in the configuration to detect hardware or software failures. If allowed to go undetected, these failures could cause the cluster to hang. A timeout causes a CPUSANITY bugcheck.
SMP_SPINWAITSMP_SPINWAIT establishes, in 10-microsecond intervals, the amount of time a CPU in an SMP system normally waits for access to a shared resource. This process is called spinwaiting.
A timeout causes a CPUSPINWAIT bugcheck.
SMP_TICK_CNTSMP_TICK_CNT sets the frequency of sanity timer checks by each CPU in a multiprocessing system.
SPTREQ (A)(VAX only) SPTREQ sets the number of system page table (SPT) entries required for mapping the following components:
SSINHIBITSSINHIBIT controls whether system services are inhibited (1) (on a per-process basis). By default, system services are not inhibited (0).
STARTUP_P1--8The following table describes possible values of STARTUP_P1 through _P8:
SWP_PRIOSWP_PRIO sets the priority of I/O transfers initiated by the swapper.
SWPALLOCINC(VAX only) SWPALLOCINC sets the size (in blocks) to use to back up swap file space allocation in the swap or page file. Space in the file is allocated in multiples of this unit (up to WSQUOTA) to guarantee swap space.
SWPFAILSWPFAIL sets the number of consecutive swap failures allowed before the swap schedule algorithm is changed to ignore the swap quantum protection.
SWPFILCNTOn VAX systems, SWPFILCNT defines the maximum number of swap files that can be installed.
SWPOUTPGCNT (A on VAX,D)This parameter allows the swapper an alternative mechanism before actually performing swaps.
On VAX systems, SWPOUTPGCNT defines the minimum number of pages to which the swapper should attempt to reduce a process before swapping it out. The pages taken from the process are placed into the free-page list.
On Alpha and I64 systems, SWPOUTPGCNT defines the minimum number of pagelets to which the swapper should attempt to reduce a process before swapping it out. The pagelets taken from the process are placed into the free-page list.
SWPRATESWPRATE sets the swapping rate (in 10-millisecond units). This parameter limits the amount of disk bandwidth consumed by swapping.
SYSMWCNT (A,G,M)SYSMWCNT sets the quota for the size of the system working set, which contains the pageable portions of the system, the paged dynamic pool, RMS, and the resident portion of the system message file.
While a high value takes space away from user working sets, a low value can seriously impair system performance. Appropriate values vary, depending on the level of system use. When the system is running at full load, check the rate of system faults with the MONITOR PAGE command of the Monitor utility. An average system page fault rate of between 0 and 3 page faults per second is desirable. If the system page fault rate is high, and especially if the system seems to be slow, you should increase the value of SYSMWCNT. However, do not set this parameter so high that system page faulting never occurs.
SYSPFCSYSPFC sets the number of pages to be read from disk on each system paging operation.
SYSSER_LOGGING (D)(Alpha and I64) A value of 1 for SYSSER_LOGGING enables logging of system service requests for a process. The default is 1.
SYSTEM_CHECKSYSTEM_CHECK investigates intermittent system failures by enabling a number of run-time consistency checks on system operation and recording some trace information.
Enabling SYSTEM_CHECK causes the system to behave as if the following system parameter values are set (although the values of the following parameters are not actually changed):
While SYSTEM_CHECK is enabled, the previous settings of the BUGCHECKFATAL and MULTIPROCESSING parameters are ignored. However, setting the parameter POOLCHECK to a nonzero value overrides the setting imposed by SYSTEM_CHECK.
Setting SYSTEM_CHECK creates certain image files that are capable of the additional system monitoring. These image files are located in SYS$LOADABLE_IMAGES and can be identified by the suffix _MON. For information about the type of data checking performed by SYSTEM_CHECK, see the description of the ACP_DATACHECK parameter. For information about the performance implications of enabling SYSTEM_CHECK, see OpenVMS Performance Management.
TAPE_ALLOCLASSTAPE_ALLOCLASS determines the tape allocation class for the system. The tape allocation class creates a unique clusterwide device name for multiple access paths to the same tape.
TAPE_MVTIMEOUT (D)TAPE_MVTIMEOUT is the time in seconds that a mount verification attempt continues on a given magnetic tape volume. If the mount verification does not recover the volume within that time, the I/O operations outstanding to the volume terminate abnormally.
TBSKIPWSLTBSKIPWSL specifies the maximum number of working set list entries that may be skipped while scanning for a "good" entry to discard. Setting this parameter to 0 disables skipping.
TIME_CONTROL (D)This special parameter is used by HP and is subject to change. Do not change this parameter unless HP recommends that you do so.
TIME_CONTROL is an SMP bit mask parameter that controls debugging functions. The following bits are defined:
TIMEPROMPTWAITTIMEPROMPTWAIT defines the number of seconds that you want a processor to wait for the time and date to be entered when a system boot occurs, if the processor's time-of-year clock does not contain a valid time. (The time unit of micro-fortnights is approximated as seconds in the implementation.) If the time specified by TIMEPROMPTWAIT elapses, the system continues the boot operation, and the date and time are set to the last recorded time that the system booted.
Depending on the value specified for the TIMEPROMPTWAIT parameter, the system acts in one of the following ways:
TIMVCFAIL (D)TIMVCFAIL specifies the time required for an adapter or virtual circuit failure to be detected. HP recommends that the default value be used. HP also recommends that this value be lowered only in OpenVMS Cluster of three CPUs or less, that the same value be used on each computer in the cluster, and that dedicated LAN segments be used for cluster I/O.
TMSCP_LOAD (A)TMSCP_LOAD allows the loading of the tape mass storage control protocol server software. The TMSCP_LOAD parameter also sets locally connected tapes served. Refer to HP OpenVMS Cluster Systems for information about setting the TMSCP_LOAD parameter.
Setting TMSCP_LOAD to 0 inhibits the loading of the tape server and the serving of local tapes. Setting TMSCP to 1 loads the tape server into memory at the time the system is booted and makes all directly connected tape drives available clusterwide. The following table describes the two states of the TMSCP_LOAD parameter:
TMSCP_SERVE_ALLTMSCP_SERVE_ALL is a bit mask that controls the serving of tapes. The settings take effect when the system boots. You cannot change the settings when the system is running.
Starting with OpenVMS Version 7.2, the serving types are implemented as a bit mask. To specify the type of serving your system will perform, locate the type you want in the following table and specify its value. For some systems, you may want to specify two serving types, such as serving all tapes except those whose allocation class does not match. To specify such a combination, add the values of each type, and specify the sum.
In a mixed-version cluster that includes any systems running OpenVMS Version 7.1-x or earlier, serving all available tapes is restricted to serving all tapes except those whose allocation class does not match the system's allocation class (pre-Version 7.2 meaning). To specify this type of serving, use the value 9, which sets bit 0 and bit 3. The following table describes the serving type controlled by each bit and its decimal value:
Although the serving types are now implemented as a bit mask, the values of 0, 1, and 2, specified by bit 0 and bit 1, retain their original meanings:
TTY_ALTALARMTTY_ALTALARM sets the size of the alternate type-ahead buffer alarm. This value indicates at what point an XOFF should be sent to terminals that use the alternate type-ahead buffers with the size specified by the TTY_ALTYPAHD parameter.
TTY_ALTYPAHDTTY_ALTYPAHD sets the size of the alternate type-ahead buffer. Use this parameter to allow the block mode terminals and communications lines to operate more efficiently.
TTY_AUTOCHAR (D)TTY_AUTOCHAR sets the character the terminal driver echoes when the job controller has been notified.
TTY_BUFTTY_BUF sets the default line width for terminals.
TTY_CLASSNAMETTY_CLASSNAME provides the 2-character prefix for the terminal class driver name that is required when booting. Changing the prefix can be useful when debugging a new terminal driver.
TTY_DEFCHARTTY_DEFCHAR sets the default characteristics for terminals, using a code derived by summing the following hexadecimal values:
1Do not set this characteristic as the default in TTY_DEFCHAR.
Where a condition is false, the value is 0.
TTY_DEFCHAR2TTY_DEFCHAR2 sets a second longword of default terminal characteristics. The default characteristics are represented as a code that is derived by summing the following hexadecimal values:
1This manual has been archived.