![]() |
![]() HP OpenVMS Systems Documentation |
![]() |
HP OpenVMS System Management Utilities Reference Manual
On VAX systems, SYSTEM_CHECK is a special parameter, which is subject to change at any time and should be modified only if recommended by HP. 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.The TAPE_ALLOCLASS parameter can also be used to generate a unique clusterwide name for tape devices with identical unit numbers. 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.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 (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. For information about setting the TMSCP_LOAD parameter, see HP OpenVMS Cluster Systems.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:
If the TMSCP_LOAD system parameter is 0, TMSCP_SERVE_ALL is ignored. 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.The default value is usually adequate. Do not exceed the maximum value of 32767 when setting this parameter. 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. The upper byte is the page length. The default characteristics are 24 lines per page, terminal synchronization, wraparound, lowercase, scope, and full-duplex. 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:
The defaults are AUTOBAUD and EDITING. TTY_DEFCHAR3(Alpha and I64) TTY_DEFCHAR3 allows a user to set a bit so that the OpenVMS terminal driver remaps CTRL/H to Delete. HP recommends that you not set this bit as a systemwide default.
For more information, see the SET TERM and SHOW TERM commands in the HP OpenVMS DCL Dictionary. TTY_DEFPORTTTY_DEFPORT provides flag bits for port drivers. Bit 0 set to 1 indicates that the terminal controller does not provide automatic XON/XOFF flow control. This bit should not be set for HP controllers, but it is needed for some foreign controllers. Currently only the YCDRIVER (DMF32, DMZ32) uses this bit. The remaining bits are reserved for future use. This special parameter should be modified only if recommended by HP.TTY_DIALTYPETTY_DIALTYPE provides flag bits for dialups. Bit 0 is 1 for United Kingdom dialups and 0 for all others. Bit 1 controls the modem protocol used. Bit 2 controls whether a modem line hangs up 30 seconds after seeing CARRIER if a channel is not assigned to the device. The remaining bits are reserved for future use. See the HP OpenVMS I/O User's Reference Manual for more information about flag bits.TTY_DMASIZE (D)TTY_DMASIZE specifies a number of characters in the output buffer. Below this number, character transfers are performed; above this number, DMA transfers occur if the controller is capable of DMA I/O.TTY_PARITYTTY_PARITY sets terminal default parity.TTY_RSPEEDTTY_RSPEED defines the receive speed for terminals. If TTY_RSPEED is 0, TTY_SPEED controls both the transmit and the receive speed. Maximum value is 20. This parameter is only applicable for controllers that support split-speed operations, such as the DZ32 and the DMF32.TTY_SCANDELTATTY_SCANDELTA sets the interval for polling terminals for dialup and hangup events. Shorter intervals use more processor time; longer intervals may result in missing a hangup event.TTY_SILOTIMETTY_SILOTIME defines the interval at which the DMF32 hardware polls the input silo for received characters. The DMF32 asynchronous terminal controller can delay the generation of a single input interrupt until multiple characters have accumulated in the input silo. TTY_SILOTIME specifies the number of milliseconds that the characters are allowed to accumulate prior to the generation of an input interrupt by the hardware.
TTY_SILOTIME controls latency, trading throughput and system overhead for latency. The default value for TTY_SILOTIME is 8. This value is multiplied by 100 and is used as a count of the number of times to send a query to the device for more data after a character transmit or receive is performed. If no input (or no subsequent output) is seen after 800 responses to the query, the driver stops sending queries to the device and waits for an input interrupt. Reducing the TTY_SILOTIME value allows the device to buffer more data, with slightly higher latency. Increasing the value of TTY_SILOTIME makes the device more sensitive to latency but decreases buffering and overall throughput; it also adds more system and USB overhead. Setting TTY_SILOTIME to zero causes the driver to send input queries to the device continually. This setting causes the lowest latency, the highest system overhead, and the lowest throughput possible. TTY_SPEEDTTY_SPEED sets the systemwide default speed for terminals. Low byte is transmit speed, and high byte is receive speed. If high byte is set to 0, receive speed is identical to transmit speed. Maximum value is 20. Baud rates are defined by the $TTDEF macro.TTY_TIMEOUT (D)TTY_TIMEOUT sets the number of seconds before a process associated with a disconnected terminal is deleted. The default value (900 seconds) is usually adequate. Note that using values for TTY_TIMEOUT greater than one year (value %X01E13380) can cause overflow errors and result in a disconnected device timing out immediately.TTY_TYPAHDSZTTY_TYPAHDSZ sets the size of the terminal type-ahead buffer. The default value is usually adequate. Do not exceed the maximum value of 32767 when setting this parameter.UAFALTERNATE (G,M)UAFALTERNATE enables or disables the assignment of SYSUAF as the logical name for SYSUAFALT, causing all references to the user authorization file (SYSUAF) to be translated to SYS$SYSTEM:SYSUAFALT. Use of the normal user authorization file (SYS$SYSTEM:SYSUAF) can be restored by deassigning the system logical name SYSUAF. This parameter should be set on (1) only when the system is being used by a restricted set of users. You must create a user authorization file named SYSUAFALT prior to setting UAFALTERNATE to 1.USERD1 (D)USERD1 is reserved for definition at the user's site. The reserved longword is referenced by the symbol SGN$GL_USERD1.On Alpha and I64 systems, this symbol is in the SYS$LOADABLE_IMAGES:SYS$BASE_IMAGE module. On VAX systems, the symbol is in the SYS$SYSTEM:SYS.STB module. USERD2 (D)USERD2 is reserved for definition at the user's site. The reserved longword is referenced by the symbol SGN$GL_USERD2.On Alpha and I64 systems, this symbol is in the SYS$LOADABLE_IMAGES:SYS$BASE_IMAGE module. On VAX systems, the symbol is in the SYS$SYSTEM:SYS.STB module. USER3USER3 is a parameter that is reserved for definition at the user's site. The reserved longword is referenced by the symbol SGN$GL_USER3.On Alpha and I64 systems, this symbol is in the SYS$LOADABLE_IMAGES:SYS$BASE_IMAGE module. On VAX systems, the symbol is in the SYS$SYSTEM:SYS.STB module. USER4USER4 is a parameter that is reserved for definition at the user's site. The reserved longword is referenced by the symbol SGN$GL_USER4.On Alpha and I64 systems, this symbol is in the SYS$LOADABLE_IMAGES:SYS$BASE_IMAGE module. On VAX systems, the symbol is in the SYS$SYSTEM:SYS.STB module. VAXCLUSTER (A)VAXCLUSTER controls loading of the cluster code. Specify one of the following:
VBN_CACHE_S(VAX only) This special parameter is used by HP and is subject to change. Do not change this parameter unless HP recommends that you do so.The static system parameter VBN_CACHE_S enables or disables file system data caching. By default its value is 1, which means that caching is enabled and the Virtual I/O Cache is loaded during system startup. Setting the value to 0 disables file system data caching on the local node and throughout the OpenVMS Cluster. In an OpenVMS Cluster, none of the other nodes in the cluster can cache any file data until this node either leaves the cluster or reboots with VBN_CACHE_S set to 1. VBSS_ENABLE (A)(VAX only) This special parameter is used by HP and is subject to change. Do not change this parameter unless HP recommends that you do so.This parameter enables virtual balance slots (VBS) to be created. A virtual balance slot holds the mapping for a memory-resident process that does not currently own a real balance slot (RBS). The set of real balance slots is timeshared among all memory-resident processes. With VBS enabled, the quantity of memory-resident processes is limited by the system parameter MAXPROCESSCNT. With VBS disabled, the quantity of memory-resident processes is limited by the system parameter BALSETCNT. When creating a new process, if the set of real balance slots is allocated, then a virtual balance slot is created and the owner of a real balance slot is selected and transitioned to the virtual balance slot. The new process is created in the real balance slot. Processes are transitioned (faulted) back to a real balance slot as they are scheduled to execute on a CPU.
VBSS_ENABLE2(VAX only) This special parameter is used by HP and is subject to change. Do not change this parameter unless HP recommends that you do so.
|