% Librarian I01-42В[ֻ0}\ֻ 5CREATE& DEINSTALL DISABLE ENABLE INSTALL JSET2SHOWSYSGEN(Sys_ParametersvTERMINALUSE"WRITE[ֻ 1 SYSGEN @ The System Generation utility (SYSGEN) is a system managementD tool used to tailor a system for a specific hardware and software configuration.1 The SYSGEN utility provides the capability to:8 - Create and edit boot-time system parameter files( - Modify dynamic system parameters+ - Load and connect I/O device drivers, - Initialize and connect shared memoryD To invoke SYSGEN, enter the following command in response to the DCL prompt: $ RUN SYS$SYSTEM:SYSGEN) The utility responds with the prompt: SYSGEN> $ To obtain help on a topic, type:- HELP command [/qualifers or parameters] ww\ֻ 1 CREATEA Creates a file that can be used as a page, swap, or dump file.= Normally, this command is used indirectly by executing the* command procedure SYS$UPDATE:SWAPFILES. Format CREATE file-spec 2 Parameter file-spec& The name of the file to be created. 2 Qualifiers /CONTIGUOUS /CONTIGUOUS /NOCONTIGUOUS= Specifies that the created file is either to be contiguous< (/CONTIGUOUS) or contiguous-best-try (/NOCONTIGUOUS). TheA Primitive File System used during OpenVMS bootstrap limits theA page, swap, and dump files to one file header. Because of thisD restriction, OpenVMS cannot be reliably bootstrapped from a bound9 volume set and is not supported on a bound volume set. /SIZE /SIZE=block-count: Specifies the size in blocks of the file to be created. 2 Example; SYSGEN> CREATE DISK$PAGE:[NODE1]PAGEFILE.SYS /SIZE=200000@ This command creates a file called PAGEFILE.SYS on the disk? DISK$PAGE: in directory [NODE1]. This file is created as aC contiguous-best-try file, which is the default. SYSGEN createsA the file with 200,000 blocks, or allocates as many blocks onD the disk as it can and displays a message warning that the file@ does not have the full allocation specified with the CREATE command.C The file will not be used for paging or swapping until you useD the SYSGEN command INSTALL specifying the file and how it is to be used. ww\ֻ 1 DEINSTALL= Deinstalls a page or swap file. Requires CMKRNL privilege.< Any file installed with the SYSGEN command INSTALL can be deinstalled.B If the specified file is being acti vely used by processes, this= command simply marks the file as "deinstall pending". This@ prevents any new assignments or reservations to the file fromC occurring. When all outstanding references to the file have been- removed, the deinstallation will complete.A Files in the deinstall pending state are identified in the DCL% command SHOW MEMORY/FILES display. Format DEINSTALL file-spec DEINSTALL/ALL DEINSTALL/INDEX=n 2 Parameter  file-specC Specifies the name of a file that is to be deinstalled as a page or swap file. 2 Qualifiers /PAGEFILE< Specifies that the file to be deinstalled is a page file. /SWAPFILE< Specifies that the file to be deinstalled is a swap file. /ALL@ Deinstalls all page and swap files currently installed on the? system. This command is most useful during an orderly systemB shutdown procedure where all disk volumes are being dismounted.1  No other parameters or qualifiers are allowed. /INDEX /INDEX=n? Deinstalls a page or swap file specified by page file index.; The page file index is presented in the DCL command SHOW3 MEMORY/FILES/FULL display as "Page File Number."1 No other parameters or qualifiers are allowed. 2 Example7 SYSGEN> DEINSTALL DRA1:[SYSEXE]PAGEFILE.SYS /PAGEFILE ww\ֻ 1 DISABLEB Inhibits the checking that SYSGEN performs on parameter values.' ) By default, range checking is enabled. Format DISABLE CHECKS 2 Parameters None. 2 Qualifiers None. ww\ֻ 1 ENABLEB Requests that SYSGEN ensure that parameter values changed usingA the SET command remain in the allowable range. By default, the range checking is enabled. Format ENABLE CHECKS 2 Parameters None. 2 Qualifiers None. ww\ֻ 1 INSTALL< Ins talls an additional page or swap file. Requires CMKRNL privilege. Format INSTALL file-spec 2 Parameter file-specA Specifies the name of a file that is to be installed as a pageC or swap file. This file can reside on any volume that is mounted? /SYSTEM. The file should be contiguous for best performance. 2 Qualifiers /PAGEFILEC Specifies that the file is to be installed as an additional pageC file. This page file will augment any page file installed during the boot process. /SWAPFILEC Specifies that the file is to be installed as an additional swapC file. This swap file will augment any swap file installed during the boot process. 2 Example5 SYSGEN> INSTALL DRA1:[SYSEXE]PAGEFILE.SYS /PAGEFILE ww\ֻ1 SETA Assigns a value to a system parameter in the SYSGEN work area.C This command does not modify parameter files, the current system@ parameter file on disk, or the active system; for information? about performing these modifications, see the WRITE command. Format SET parameter-name value 2 Parameters parameter-nameB Specifies the name of a system parameter. If you enter a period@ (.), it is interpreted as a request for the system parameterD specified in the last SET or SHOW command. See the description ofC the SHOW parameter-name command for an example of the use of the' period in place of a parameter name. value? Usually specifies an integer or the keyword DEFAULT. Integer? values must be within the defined minimum and maximum valuesA for the parameter unless the SYSGEN command DISABLE CHECKS was specified.: The keyword DEFAULT specifies the default value for the? parameter. You can display the maximum, minimum, and defaultC values for any parameter with the SYSGEN command SHOW parameter- name.: You can specify values for certain SYSGEN parameters inB hexadecimal or octal radixes and for others as an ASCII string.@ To specify a value in octal or hexadecimal, precede the valueD with %O or %X, respectively. To specify a value in ASCII, enclose- the value string in quotation marks (" "). 2 Qualifiers None. 2 Examples 1.SYSGEN> SET PFCDEFAULT 20D This command assigns a value of 20 to the PFCDEFAULT parameter.$ 2.SYSGEN> SET GBLSECTIONS DEFAULTC This command assigns the default value (40) to the GBLSECTIONS parameter. 2 /OUTPUT? Establishes a file to be used for output during the session.B By default the output is written to SYS$OUTPUT, but you can use' SET/OUTPUT to designate a disk file.D At any time you can direct the output back to SYS$OUTPUT by using% the SET/OUTPUT=SYS$OUTPUT command. Format SET/OUTPUT[=] file-spec 3 Parameter file-specB The name of the output file. The default file type is .LIS. The equal sign (=) is optional. 3 Example SYSGEN> SET/OUTPUT=PARAMS.LIS SYSGEN> SHOW/ALL SYSGEN> SHOW/SPECIAL SYSGEN> EXITB In this example, output is directed to the file PARAMS.LIS toD capture a complete list of all the system parameters (includingC the SPECIAL parameters reserved for VSI use) and their values. 2 /STARTUP= Names the site-independent startup command procedure to be< associated with a parameter file for subsequent bootstrap operations. Format SET/STARTUP file-spec 3 Parameter file-spec? The file specification of a startup command procedure on the< system disk (maximum of 31 characters). The initial site-B independent startup command procedure (as named in the software/ distribution kit) is SYS$SYSTEM:STARTUP.COM. 3 Example- SYSGEN> SET/STARTUP SYS$SYSTEM:XSTARTUP.COM@ This command assigns SYS$SYSTEM:XSTARTUP.COM as the current0 site-independent startup command procedure. ww/\ֻ1 SHOWD Displays the values of system parameters in the SYSGEN work area,B plus the default, minimum, and maximum values of the parameters and their units of measure. Format SHOW parameter-name 2 Parameter parameter-nameB Specifies the name of a system parameter. If you enter a period@ (.), it is interpreted as a request for the system parameterB specified in the last SET parameter-name or SHOW parameter-name command.D Beginning in OpenVMS Version 8.2, specifies OBSOLETE in the Units7 column for any specified parameter that is obsolete. 2 Qualifiers /ACP9 Specifies that all ACP parameter values are displayed. /ALLC Specifies that all parameter values other than SPECIAL parameter values are displayed. /BIC Specifies that device addresses that are currently mapped in the- I/O space for the VAXBI bus are displayed. /CLUSTER= Specifies that all CLUSTER parameter values are displayed. /DYNAMIC= Specifies that all DYNAMIC parameter values are displayed. /GEN9 Specifies that all GEN parameter values are displayed. /HEX: Specifies that the values of parameters be displayed in@ hexadecimal representation. Specify the /HEX system parameter@ name or the parameter type. If you specify the /HEX qualifier. with the /NAMES qualifier, /HEX is ignored. /JOB!9 Specifies that all JOB parameter values are displayed. /LGI9 Specifies that all LGI parameter values are displayed. /MAJOR; Specifies that all MAJOR parameter values are displayed. /MULTIPROCESSING? Specifies that all MULTIPROCESSING parameters are displayed. /NAMES< Specifies that the names of all parameters are displayed. /OBSOLETE: Specifies that the names of all obsolete parameters are displayed. /PQL9 Specifi es that all PQL parameter values are displayed. /RMS9 Specifies that all RMS parameter values are displayed. /SCS9 Specifies that all SCS parameter values are displayed. /SPECIAL? Specifies that all parameter values reserved for VSI use are displayed. /STARTUPB Specifies that the name of the current site-independent startup" command procedure is displayed. /SYS9 Specifies that all SYS parameter values are displayed. /TTY> Specifies that all terminal parameter values are displayed. /XMI /XMI[=BIindex]? Specifies that device addresses that are currently mapped inB the I/O space for the XMI bus are displayed. The /XMI qualifier@ also displays node and nexus numbers and generic names of all@ processors, adapters, VAXBI adapters, memory controllers, and* interconnection devices such as the NI.: Use of the SHOW/XMI=BIindex command requires the CMEXEC privilege. 2 Descr iption< Parameter values are displayed in decimal unless the /HEX? qualifier is specified. Note that ASCII values are displayed in ASCII by default.D When parameter names are abbreviated on a VAX platform, the first? parameter matching the abbreviation is selected for display.A No ambiguity checks are made. On an Alpha or I64 platform, all= parameters whose names match the abbreviation are printed.D For example, a specification of SHOW GBL on a VAX system displays;  only the GBLSECTIONS parameter. To display the GBLPAGFIL= parameter, you must specify SHOW GBLPAGF (to avoid further= ambiguity with the GBLPAGES parameter). On an Alpha or I64D system, the same SHOW GBL command displays GBLSECTIONS, GBLPAGES, and GBLPAGFIL.@ You can enter a period (.) to indicate that you want to work? with the system parameter that was specified in the last SET1 parameter-name or SHOW parameter-name command.  2 /STARTUPD Displays the name  of the current site-independent startup command procedure. Format SHOW/STARTUP 3 Parameters None. 3 Qualifiers None. 3 Example SYSGEN> SHOW/STARTUP. Startup command file = SYS$SYSTEM:STARTUP.COMC This command displays the name of the site-independent startup command procedure.  ww V\ֻ 1 TERMINALD Modifies the Ctrl/C, Ctrl/O, Ctrl/Y, and Ctrl/Z echo strings on a systemwide basis. Format TERMINAL/ECHO 2 Parameters None. 2 Qualifiers None. 2 DescriptionD Before entering the TERMINAL command, edit the file SYSGTTSTR.MSGC in SYS$EXAMPLES. The file contains detailed instructions for the editing procedure.B When you enter the TERMINAL command after editing the file, the4 modifications you have specified are carried out. ww V\ֻ1 USE@ Initializes the SYSGEN work area with system parameter valuesB and the name of the site-independent startup command procedure,@ overwriting existing values. The initial values of the SYSGEN? work area when the utility is invoked are the active values.; Specify the source for both the parameter values and the? procedure name. They can be retrieved from a parameter file,B the current system parameter file on disk, the active system in memory, or the default list. Format USE file-spec 2 Parameters file-spec ? The file specification of a system parameter file from whichC data is to be retrieved. You can use the SYSGEN command WRITE to< create the parameter file. The default file type is .PAR.? In place of a file specification, you can specify one of the following keywords: CURRENT@ Specifies that source information is to be retrieved from the) current system parameter file on disk.1 On Alpha systems, the system parameter file is SYS$SYSTEM:ALPHAVMSSYS.PAR.!5 On Integrity servers, the system parameter file is SYS$SYSTEM:IA64VMSSYS.PAR. ACTIVE@ Specifies that source information is to be retrieved from the active system in memory. DEFAULT@ Specifies that source information is to be retrieved from the? default list. The USE DEFAULT command initializes the SYSGEN> work area with parameter values that are built into SYSGEN;B these values allow the operating system to boot on any standard configuration.A" To avoid starting all layered products on a system that is not? tuned for them, possibly causing the system to hang, set the* STARTUP_P1 system parameter as follows: SYSGEN> SET STARTUP_P1 "MIN" 2 Qualifiers None. 2 Examples# 1.SYSGEN> USE SYS$SYSTEM:SPECIAL2 This command uses the existing parameter file SYS$SYSTEM:SPECIAL.PAR. 2.SYSGEN> USE DEFAULT! SYSGEN> SET STARTUP_P1 "MIN"D The first command initializes the SYSGEN wo#rk area with defaultD parameter values. The second command sets the STARTUP_P1 system parameter to "minimum." ww0}\ֻ1 WRITE? Writes the system parameter values and the name of the site-B independent startup command procedure from the SYSGEN work areaB to a parameter file, the current system parameter file on disk," or the active system in memory. Format WRITE file-spec 2 Parameters file-specD The file specificatio$n of a new parameter file to be created. The default file type is .PAR.? In place of a file specification, you can specify one of the following keywords: CURRENTD Specifies that source information is to be written to the current! system parameter file on disk.1 On Alpha systems, the system parameter file is SYS$SYSTEM:ALPHAVMSSYS.PAR.5 On Integrity servers, the system parameter file is SYS$SYSTEM:IA64VMSSYS.PAR.B Use of the WRITE CURRENT comman%d requires the SYSPRV privilege.ACTIVEC Specifies that source information is to be written to the activeC system in memory. (Only the dynamic parameter values are written to the active system.)A Use of the WRITE ACTIVE command requires the CMKRNL privilege. 2 Qualifiers None. 2 DescriptionA On VAX systems, the implementation of security auditing withinB SYSGEN has altered the reporting of modifications to the system< parameter file VAXVMSSYS. &PAR. System managers can receive? notification of a change to the file by setting up an accessD control list (ACL) on the file to signal such an event, as in the following example:D $ SET SECURITY/ACL=(ALARM=SECURITY,ACCESS=WRITE+FAILURE+SUCCESS)- _$ SYS$SYSTEM:VAXVMSSYS.PAR@ For more information about setting ACLs, refer to the OpenVMS> User's Manual and the VSI OpenVMS Guide to System Security.I On Alpha and Interity servers, both the WRITE ACTIVE and WRITE CURRENT'6 commands send a message to OPCOM and log the event.& NOTE> Prior to Version 7.3-2, enabling SYSGEN audits or alarms= did not provide audits or alarms with information about@ the parameters being modified. Beginning in Version 7.3-2,? audits or alarms provide a list of the changed parameters* along with their old and new values. 2 Examples% 1.SYSGEN> WRITE SYS$SYSTEM:SPECIAL= This command creates a new para(meter specification file, SYS$SYSTEM:SPECIAL.PAR. 2.SYSGEN> WRITE CURRENT? On Alpha systems, this command modifies the current system- parameter file on disk, ALPHAVMSSYS.PAR.C On Integrity servers, this command modifies the current system, parameter file on disk, IA64VMSSYS.PAR.I! *********************************************************************** ! PARAM-STARTI! Start of help on SYSGEN parameters. Please leave this marker in place.F! It is requir)ed to permit the parameters help text to be removed from,! this file and made part of the SYSMAN helpI! ***********************************************************************ww0}\ֻ1 Sys_Parameters; Help is provided for the system parameters listed below. 2 ACP_BASEPRIOD ACP_BASEPRIO sets the base priority for all ACPs. The DCL commandC SET PROCESS/PRIORITY can be used to reset the base priorities of< individual ACPs. ACP_BASEPRIO is not applicable f*or XQPs.' ACP_BASEPRIO is a DYNAMIC parameter. 2 ACP_DATACHECKC ACP_DATACHECK controls the consistency checks that are performed9 on internal file system metadata such as file headers.B ACP_DATACHECK is a bit mask. The following table shows the bits that are defined currently: Bit Description@ 0 Set this bit to perform consistency checks on read operations.? When this bit is set, the IO$M_DATACHECK functionB + modifier is automatically set on all subsequent IO$_E READLBLK operations that read file system metadata (see7 the OpenVMS I/O User's Reference Manual).A 1 Set this bit to perform consistency checks on write operations.? When this bit is set, the IO$M_DATACHECK functionB modifier is automatically set on all subsequent IO$_A WRITELBLK operations that read file system metadata< , (see the OpenVMS I/O User's Reference Manual).B 2 Set this bit to perform read-after-write consistency checks.C This is similar to setting bit 1, except that in thisA case the file system does the checks, not the lower* level device or disk driver.C Note that read-after-write consistency checks are notD allowed on deferred writes. Deferred writes are turned% off if this bit is - set.6 3 reserved for VSI use only; must be zero.6 4 reserved for VSI use only; must be zero.E 5 and 6 These two bits control the checks that are performed onB reads and writes of directory blocks. You can select+ one of four different levels:2 By7 Select SettingC This Bit 6 And Bit 5? .To Check That... Level... to... to...; The block is a valid 0 0 0 directory block (reads only); The block is a valid 1 0 1 directory block (reads and writes); The block is a valid 2 1 0 directory block and contains valid entries (reads and writes); / The block is a valid 3 1 1 directory block and contains valid entries in correct alphanumeric order (reads and writes)B When you set the SYSTEM_CHECK system parameter to 1,> you enable level 3 checking of directory blocks.D Write errors result in BUGCHECK and crash your system;B read errors exit with error status SS$_BADDIRECTORY.6 7 0 reserved for VSI use only; must be zero. 2 ACP_DINDXCACHE@ ACP_DINDXCACHE controls the size of the directory index cache= and the number of buffers used on a cachewide basis. Also,= ACP_DINDXCACHE builds a temporary index into the directoryA file, thereby reducing search time and directory header lookup operations.A ACP_DINDXCACHE is an AUTOGEN, DYNAMIC, and FEEDBACK parameter. 2 ACP_DIRCACHE> ACP_DIRCACHE sets the number of pages for caching directory 1A blocks. Too small a value causes excessive XQP I/O operations,A while too large a value causes excessive physical memory to be. consumed by the directory data block cache.? ACP_DIRCACHE is an AUTOGEN, DYNAMIC, and FEEDBACK parameter. 2 ACP_EXTCACHE? ACP_EXTCACHE sets the number of entries in the extent cache.B Each entry points to one contiguous area of free space on disk.@ A specification of 0 means no cache. Too small a value causes? excessive XQP I/O operati2ons, while too large a value causes@ excessive physical memory to be consumed by the extent cache.4 ACP_EXTCACHE is a DYNAMIC and FEEDBACK parameter. 2 ACP_EXTLIMIT= ACP_EXTLIMIT specifies the maximum amount of free space to@ which the extent cache can point, expressed in thousandths of@ the currently available free blocks on the disk. For example,: if available free space on the disk is 20,000 blocks, a= specification of 10 limits the extent cache to 200 blocks.@3 The computed, installed value is usually adequate. Users withA four or more OpenVMS Cluster node systems might want to adjust this parameter.' ACP_EXTLIMIT is a DYNAMIC parameter. 2 ACP_FIDCACHED ACP_FIDCACHE sets the number of file identification slots cached.@ A specification of 1 means no cache. Too small a value causes? excessive XQP I/O operations, while too large a value causes> excessive physical memory to be consumed by the FID caches.4 ACP_FIDCACHE 4is a DYNAMIC and FEEDBACK parameter. 2 ACP_HDRCACHE@ ACP_HDRCACHE sets the number of pages for caching file headerA blocks. Too small a value causes excessive XQP I/O operations,A while too large a value causes excessive physical memory to be& consumed by the file header caches.? ACP_HDRCACHE is an AUTOGEN, DYNAMIC, and FEEDBACK parameter. 2 ACP_MAPCACHE? ACP_MAPCACHE sets the number of pages for caching index file< bitmap blocks. Too small a value causes e5xcessive XQP I/O@ operations, while too large a value causes excessive physical- memory to be consumed by the bitmap cache.? ACP_MAPCACHE is an AUTOGEN, DYNAMIC, and FEEDBACK parameter. 2 ACP_MAXREADB ACP_MAXREAD sets the maximum number of directory blocks read in one I/O operation.& ACP_MAXREAD is a DYNAMIC parameter. 2 ACP_MULTIPLED ACP_MULTIPLE enables (1) or disables (0) the default creation ofC a separate disk XQP cache for each volume mounted on 6a different@ device type. Prior to Version 4.0, a separate ACP process was> created for each device type if this parameter was enabled.A Because ACP operations are now handled by the per process XQP,D such separate processes are no longer created. In general, havingD multiple caches is unnecessary. One large cache is more efficient@ than several small ones. ACP_MULTIPLE can be overridden on an6 individual-volume basis with the DCL command MOUNT.4 ACP_MULTIPLE is an AUTOGEN 7and DYNAMIC parameter. 2 ACP_QUOCACHE? ACP_QUOCACHE sets the number of quota file entries cached. A> specification of 0 means no cache. Too small a value causes? excessive XQP I/O operations, while too large a value causes@ excessive physical memory to be consumed by the quota caches.? ACP_QUOCACHE is an AUTOGEN, DYNAMIC, and FEEDBACK parameter. 2 ACP_REBLDSYSDD ACP_REBLDSYSD specifies whether the system disk should be rebuiltC if it was improperly dismounted 8 with extent caching, file numberD caching, or disk quota caching enabled. The ACP_REBLDSYSD defaultB value (1) ensures that the system disk is rebuilt. Setting the, value to 0 means the disk is not rebuilt.; Depending on the amount of caching enabled on the volume@ before it was dismounted, the rebuild operation may consume aB considerable amount of time. Setting the value of ACP_REBLDSYSDD to 0 specifies that the disk should be returned to active serviceD immediately. If9 you set ACP_REBLDSYSD to 0, you can enter the DCL> command SET VOLUME/REBUILD at any time to rebuild the disk. 2 ACP_SHAREB ACP_SHARE enables (0) or disables (1) the creation of a globalD section for the first ACP used, enabling succeeding ACPs to shareC its code. This parameter should be set to 0 when ACP_MULTIPLE is on.$ ACP_SHARE is a DYNAMIC parameter. 2 ACP_SWAPFLGS? ACP_SWAPFLGS enables or disables swap through the value of a7 4-bit number for the :following four classes of ACPs: Bit Class of ACP' 0 Disks mounted by MOUNT/SYSTEM& 1 Disks mounted by MOUNT/GROUP 2 Private disks 3 Magnetic tape ACP@ If the value of the bit is 1, the corresponding class of ACPsB can be swapped. The value of decimal 15 (hexadecimal F-all bits> on) enables swap for all classes of ACP. A value of decimalA 14 disables swap for ACPs for volumes mounted with the /SYSTEMB qualifier but leaves swap ena ;bled for all other ACPs. Note thatD one has only disk ACPs present if they are specifically requestedC at mount time or if a Files-11 On-Disk Structure Level 1 disk isD mounted. In general, only bit 3 is significant because usually no file ACPs exist.4 ACP_SWAPFLGS is an AUTOGEN and DYNAMIC parameter. 2 ACP_SYSACC> ACP_SYSACC sets the number of directory file control blocks< (FCBs) that are cached for disks mounted with the /SYSTEMD qualifier. Each directory FCB c<ontains a 16-byte array containingD the first letter of the last entry in each block of the directoryA (or group of blocks if the directory exceeds 16 blocks). SinceC entries in a directory are alphabetical, the cached FCB providesC quick access to a required directory block. This parameter valueA should be roughly equivalent to the number of directories that= are in use concurrently on each system volume. It might be@ overridden on a per-volume basis with the /ACCESSED quali=fierD to the DCL command MOUNT. The value should be kept low in systems? with small physical memory and little file activity, becauseA the FCBs require a significant amount of space in the nonpaged dynamic pool.C Too small a value causes excessive XQP I/O operations, while tooC large a value causes excessive physical memory to be consumed by the FCB caches.2 ACP_SYSACC is an AUTOGEN and DYNAMIC parameter. 2 ACP_WINDOW> ACP_WINDOW sets the default number of > window pointers to be= allocated in a window for a default file access, for disks& mounted with the /SYSTEM qualifier.% ACP_WINDOW is a DYNAMIC parameter. 2 ACP_WORKSETA ACP_WORKSET sets the default size of a working set for an ACP.C A specification of 0 permits the ACP to calculate the size. This@ value should be nonzero only on small systems where memory is@ tight. Too small a value causes excessive ACP page, while too@ large a value causes excessive physical m?emory to be consumedA by the ACP. Note that this parameter has no effect on the per- process XQP.& ACP_WORKSET is a DYNAMIC parameter. 2 ACP_WRITEBACKD ACP_WRITEBACK is a dynamic system parameter that controls whetherD deferred writes to file headers are enabled. The default value isC 1, which enables deferred writes to file headers. To disable the# feature, set ACP_WRITEBACK to 0.A This system parameter affects only applications like PATHWORKS> that can re @quest deferred writes to file headers. Note that@ the deferred write feature is not available on Files-11 ODS-1 volumes.( ACP_WRITEBACK is a DYNAMIC parameter. 2 ACP_XQP_RES? ACP_XQP_RES controls whether the XQP is currently in memory.A The default value (1) specifies that the XQP is permanently in? memory. Change the default only on restricted memory systemsC with a small number of users and little or no file activity that@ requires XQP intervention. Such activAity includes file opens,/ closes, directory lookups, and window turns. 2 AFFINITY_SKIP@ AFFINITY_SKIP controls the breaking of implicit affinity. TheB value indicates the number of times a process is skipped before being moved.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 AFFINITY_TIME@ AFFINITY_TIME controls the breaking of implicit affinity. TheC value indicates how lBong a process remains on the compute queue.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 ALLOCLASSC ALLOCLASS determines the device allocation class for the system.> The device allocation class is used to derive a common lock> resource name for multiple access paths to the same device. 2 ARB_SUPPORT> (Alpha and Integrity servers) The Access Rights Block (ARB)= compatibility C option, the ARB_SUPPORT system parameter, isC provided specifically to support products that have not yet beenD updated to use the new per-thread security Persona Security BlockA (PSB) data structure instead of the ARB. Changing the value of? ARB_SUPPORT from 2 or 3 (the default) to any other value can* affect the operation of these products.& NOTE< VSI recommends that all Version 7.3-1 systems have theA ARB_SUPPORT parameter set to D 3 (the default). Do not change< the ARB_SUPPORT parameter to any other value until all= products dependent on the ARB and associated structures1 have been modified for the new environment.8 The following table describes ARB_SUPPORT parameters: ARB_SUPPORT& Parameter Value BehaviorD ISS$C_ARB_NONE 0 The obsolete kernel data cells are notB maintained by the system. Fields areD initia Elized to zero (or set to invalid< pointers) at process creation.@ ISS$C_ARB_CLEAR 1 The obsolete kernel data cells areB cleared (or set to invalid pointers)D when the code would have set up values9 for backward compatibility.A ISS$C_ARB_READ_ 2 The obsolete cells are updated with@ ONLY corresponding security information> F stored in the current PSB when a8 $PERSONA_ASSUME is issued.C ISS$C_ARB_FULL 3 (de- Data is moved from the obsolete cells@ fault) to the currently active PSB on any7 security-based operation.& ARB_SUPPORT is a DYNAMIC parameter. 2 AUTO_DLIGHT_SAV= AUTO_DLIGHT_SAV is set to either 1 or 0. The default is 0.B If AUTO_DLIGHT_SAV is set to 1, OpenVMS automatically makesG the+ change to and from daylight saving time. 2 AWSMIN@ On Alpha and Integrity servers, AWSMIN establishes the lowestC number of pagelets to which a working set limit can be decreased. by automatic adjustment of the working set.! AWSMIN is a DYNAMIC parameter. 2 AWSTIME> AWSTIME specifies the minimum amount of processor time that@ must elapse for the system to collect a significant sample ofB a working set's page fault rate. The time is expressed in unitsHA of 10 milliseconds. The default value of 5, for example, is 50 milliseconds.> Some application configurations that have a large number ofB memory-intensive processes may benefit if the value is reduced. The value can be as low as 4.B AWSTIME expiration is checked only at quantum end. Reducing its? value and not reducing QUANTUM effectively sets the value of) AWSTIME equal to the value of QUANTUM." AWSTIME is a DYNAMIC parameter. 2 BALSETCNTD BALSETCNT I sets the number of balance set slots in the system pageC table. Each memory-resident working set requires one balance set slot.> You can monitor the active system with the DCL command SHOWD MEMORY or the MONITOR PROCESSES command of the Monitor utility toD determine the actual maximum number of working sets in memory. IfB this number is significantly lower than the value of BALSETCNT,B this parameter value could be lowered. If all balance set slots0 are being used, raise t Jhe value of BALSETCNT.9 Never set BALSETCNT to a value higher than 2 less than< MAXPROCESSCNT. If physical memory is a significant systemB constraint, consider lowering this value even further. However,A if your system runs with a number of processes nearly equal toD MAXPROCESSCNT, lowering BALSETCNT forces swapping to occur, which! can affect system performance.; BALSETCNT is no longer a strict setting of the number of@ processes that might be resident in memory. The s Kwapper tries@ to reduce the number of resident processes down to BALSETCNT.A However, if the total number of active processes and processesB that have disabled swapping exceeds BALSETCNT, the swapper does? not force processes out of memory just to meet the BALSETCNT setting.> BALSETCNT is an AUTOGEN, GEN, DYNAMIC, and MAJOR parameter. 2 BORROWLIM@ BORROWLIM defines the minimum number of pages required on theA free-page list before the system permits process growth L beyondB the working set quota (WSQUOTA) for the process. This parameter) should always be greater than FREELIM.B This parameter allows a process to grow beyond the value set byB the working set quota (WSQUOTA) to the working set quota extentD (WSEXTENT) on a system that has a substantial memory on the free-@ page list. This automatic working set adjustment also depends< upon the values of parameters WSINC, PFRATH, and AWSTIME.C Working set growth attempts to alleviate he Mavy page faulting. ToA make use of this growth, you must also set the user's WSEXTENTA authorization quota to a larger number than the WSQUOTA value.8 BORROWLIM is an AUTOGEN, DYNAMIC and MAJOR parameter. 2 BREAKPOINTS? If XDELTA is loaded, BREAKPOINTS enables additional built-inB calls for XDELTA during the boot sequence. The breakpoints that= are enabled may change from release to release of OpenVMS.D This special parameter is use by VSI and is subject to changeN. DoB not change this parameter unless VSI recommends that you do so.& BREAKPOINTS is a DYNAMIC parameter. 2 BUGCHECKFATAL? BUGCHECKFATAL enables or disables the conversion of nonfatalC bugchecks into fatal bugchecks. The system must be rebooted on aB fatal bugcheck. A nonfatal bugcheck places an entry only in the3 error log and deletes the corresponding process.C This parameter should normally be OFF (0); you should set it ON2 (1) only when the executive is bOeing debugged.D Setting the SYSTEM_CHECK parameter to 1 has the effect of setting BUGCHECKFATAL to ON (1).( BUGCHECKFATAL is a DYNAMIC parameter. 2 BUGREBOOTB BUGREBOOT enables or disables automatic rebooting of the systemC if a fatal bugcheck occurs. This parameter should normally be onB (1); set it off (0) only when the executive is being debugged.$ BUGREBOOT is a DYNAMIC parameter. 2 CHANNELCNTD CHANNELCNT specifies the maximum number of I/O channe Pls available> to processes and to the system. The FILLM quota can be used@ to reduce the maximum number of I/O channels for a process. AD process with a FILLM quota larger than CHANNELCNT is nevertheless= limited to the maximum number of I/O channels specified by CHANNELCNT. 2 CLASS_PROT: CLASS_PROT performs the nondiscretionary classification> checks. CLASS_PROT is also checked by XQP to determine if aD classification block should be added to the header of any creatQed files.% CLASS_PROT is a DYNAMIC parameter. 2 CLISYMTBLC CLISYMTBL sets the size of the command interpreter symbol table,@ which controls the number of DCL symbols that can be created.$ CLISYMTBL is a DYNAMIC parameter. 2 CLUSTER_CREDITSC CLUSTER_CREDITS specifies the number of per-connection buffers a= node allocates to receiving VMS$VAXcluster communications.? If the SHOW CLUSTER command displays a high number of credit> waits for the VMS$VAX Rcluster connection, you might consider= increasing the value of CLUSTER_CREDITS on the other node.? However, in large cluster configurations, setting this valueA unnecessarily high consumes a large quantity of nonpaged pool.D Each receive buffer is at least SCSMAXMSG bytes in size but mightA be substantially larger depending on the underlying transport.C It is not required for all nodes in the cluster to have the same value for CLUSTER_CREDITS.> The default value is Scurrently 32. Unless a system has veryA constrained memory available, VSI recommends that these values not be increased. 2 CONCEAL_DEVICESD CONCEAL_DEVICES enables or disables the use of concealed devices.@ By default, this parameter is set to enable concealed devices (1).D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 CPU_POWER_MGMT_(D)@ On Integrity servers, a CPU can T be placed in "low-power mode"= when it is idle. This minimizes power consumption, therebyB reducing energy costs for the system. Beginning in Version 8.2-B 1, OpenVMS Integrity servers supports this feature based on theC settings of two system parameters: CPU_POWER_MGMT and CPU_POWER_ THRSH.B A value of 1 for CPU_POWER_MGMT means on (the default); a valueB of 0 means off. Whenever the CPU_POWER_THRSH parameter value isB exceeded, the operating system places an Integrity Uprocessor inD low-power mode if it is idle. OpenVMS Integrity servers does thisC only if CPU_POWER_MGMT is on. A CPU returns to normal power when it receives an interrupt.) CPU_POWER_MGMT is a DYNAMIC parameter. 2 CPU_POWER_THRSH_(D)A On Integrity servers, CPU_POWER_THRSH is a parameter expressedA as a percentage. OpenVMS Integrity servers monitors how active@ each CPU is over a fixed time period. If CPU_POWER_MGMT is onA and a CPU is idle for a period of time in Vdicated by CPU_POWER_D THRSH, the CPU is placed in a low-power mode if it is idle. A CPU9 returns to normal power when it receives an interrupt.A For systems supporting real-time operations that require quickE response time, VSI recommends that this feature be turned off. UseA of this feature can result in a small performance degradation.B For more information, see the Intel IA-64 Architecture Software; Developer's Manual, Volume 2: IA-64 System Architecture.) See aWlso the CPU_POWER_MGMT parameter.* CPU_POWER_THRSH is a DYNAMIC parameter. 2 CRD_CONTROLA This special parameter is use by VSI and is subject to change.E Do not change this parameter unless VSI recommends that you do so.D On Alpha and Integrity servers, CRD_CONTROL can be used to expand% the function defined by CRDENABLE.? CRD_CONTROL is a bit mask for corrected read data (CRD) soft? error control flags. These flags control the use of CRDERROR routines.B X On Alpha and Integrity servers, the following bits are defined: Bit Description1 0 Enables CRD processing for all systems.C 1 Enables scrubbing (rewriting) of the memory location that induced the CRD.< 2 Enables page replacement of the pages that exhibit repeated CRD errors.; 3 Forces all memory pages to be included in the PFNC database. On systems that contain more than 512 megabytes@ of memory, all memorYy is mapped by the PFN database byB default. This bit allows the mapping to occur on systems1 with less than 512 megabytes of memory.6 4 Enables extended CRD handling, if available.C 5 Enables loading of driver and process for handling server@ management events. Platform-specific code usually setsD this bit if the required hardware and firmware support are available." 6 Disables CRD throttling.2 7 Disables SysZtem Event Log (SEL) polling.@ 16-31 Reserved for platform-specific error-handling control.C On Alpha and Integrity servers, the default setting is 22, whichB enables scrubbing, page replacement, and extended CRD handling. 2 CRDENABLE> (Alpha and Integrity servers) CRDENABLE enables or disablesD detection and logging of memory-corrected read data (ECC) errors.0 This parameter should normally be set to (1).A Beginning with OpenVMS Version 7.2, CRD_CONTROL can expand [the, function of CRDENABLE. (See CRD_CONTROL.) 2 CTLIMGLIMA CTLIMGLIM specifies the size of the default image I/O segment;B that is channel table and initial buffer pool for image-related file and RMS I/O.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 CTLPAGESD CTLPAGES specifies the size of P1 pool. CTLPAGES is automaticallyD changed only when the process logical name \table, DCL symbols, orB some layered products require an increase in the size of the P1 pool area.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so.$ CTLPAGES is an AUTOGEN parameter. 2 CWCREPRC_ENABLEC CWCREPRC_ENABLE controls whether an unprivileged user can createD a process on another OpenVMS Cluster node. The default value of 1D allows an unprivileged user to create a detached ]process with theC same UIC on another node. A value of 0 requires that a user haveB DETACH or CMKRNL privilege to create a process on another node. 2 DBGTK_SCRATCHA (Alpha and Integrity servers) DBGTK_SCRATCH specifies how many> pages of memory are allocated for the remote debugger. ThisC memory is allocated only if remote debugging is enabled with theB 8000 boot flag. Normally, the default value is adequate, but ifC the remote debugger issues an error message, you shou ^ld increaseD this value. See Writing OpenVMS Alpha Device Drivers in C (MargieB Sherlock and Lenny S. Szubowicz, Digital Press, 1996). for more0 information. (This manual has been archived.) 2 DCL_CTLFLAGS> DCL_CTLFLAGS is a bit mask that alters default behavior for@ certain DCL-related functions on a systemwide basis. However,8 the default values satisfy the needs of most systems.C Bits 0 and 2 control the formulation of system-generated processC names for process _es created using the SPAWN command or LIB$SPAWN< library routine. They are provided for compatibility withB behavior of prior OpenVMS versions. Note that you can eliminateB the use of system-generated names by supplying your own process names.- Bit 1 controls the token size used by DCL.@ Bit 3 controls the maximum number input parameters to command procedure.D Bit 4 controls the the maximum length for an user name, for which* OpenVMS mail forwarding address is se`t.: DCL_CTLFLAGS bits are described in the following table. Bit DescriptionA Bit If clear (the default), the numeric portion of a system-A 0 generated spawned process name is generated randomly. IfD set, the numeric portion is generated sequentially starting with sequence number 1.< The option of sequential generation is provided for= compatibility with OpenVMS versions prior to Version= 7.3-1. However, this choice can be ve ary expensive in? performance terms because of the mechanism for findingD the next available process name. This mechanism attempts toB create all process names beginning with sequence number 1+ until it finds one that is unused.= Random generation is the preferred choice because it? results in a very high probability of finding a unique name on the first try.; Bit Controls the token size used by DCL. If clear (the@ 1 b default), this bit instructs DCL to use the traditionalB token size. A token cannot exceed 255 characters. If thisB bit is set, extended tokens are used. Extended tokens are 4000 characters.7 Note that if you turn on extended tokens, file> specifications can exceed 255 characters, which mightC require larger structures for parsing file specifications.A Bit If clear (the default), the numeric portion of a system-> 2 generated c spawned process name has a maximum value of= 65535. If set, the numeric portion of the name has a maximum value of 255.7 The option of a maximum of 255 is provided forB compatibility with OpenVMS versions prior to Version 8.3,D when it was the only choice. The larger maximum allows many? more unique spawned process names for a given process.> For this reason, it is the preferred choice. However,? the larger maximum uses two d additional characters from@ the process name, which might make it more difficult toD identify users uniquely by looking at their spawned processA names. If this is an issue on your system, setting bit 2" might be a better choice.? Bit If clear (the default), command procedure supports theD 3 default eight optional parameters (that is, (P1,P2,...P8)).B If set, command procedure supports up to sixteen optional; parameters (that is e, (P1,P2,...P16)). This is alsoC applicable when using the CALL command to transfer control to a subroutine.C Bit This bit controls the the maximum length for an user name,C 4 for which OpenVMS mail forwarding address is set. If clearC (the default), user name string length is set to a maximumD length of 31 characters. If set, user name string length is, set to a maximum of 255 characters.? Note: Once this bit is set, user fname length is set to@ maximum of 255 characters. Even if this bit is cleared,D the behavior remains unchanged, that is, supports user nameB length of 255 characters, but there is no way to reset it to 31 characters. 2 DEADLOCK_WAITB DEADLOCK_WAIT defines the number of seconds that a lock requestD must wait before the system initiates a deadlock search on behalf@ of that lock. Setting DEADLOCK_WAIT to zero disables deadlock? checking. Setting D gEADLOCK_WAIT to a value greater than zeroA and less than the default setting provides faster detection of) deadlocks but requires more CPU usage.B The DEADLOCK_WAIT value is expressed in seconds; therefore, theC smallest value you can set is 1 second. Beginning in VSI OpenVMS? Version 8.3, a subsecond deadlock wait time, which is set inB the system service $SET_PROCESS_PROPERTIESW item code $PPROP$C_D DEADLOCK_WAIT, overrides DEADLOCK_WAIT. For more information, seeD theh $SET_PROCESS_PROPERTIESW system service in VSI OpenVMS System Services Reference Manual.( DEADLOCK_WAIT is a DYNAMIC parameter. 2 DEFGID0 Default POSIX GID used internally by OpenVMS. 2 DEFMBXBUFQUOB DEFMBXBUFQUO sets the default for the mailbox buffer quota size@ in bytes when this value is not specified in a Create Mailbox! ($CREMBX) system service call.' DEFMBXBUFQUO is a DYNAMIC parameter. 2 DEFMBXMXMSGD DEFMBXMXMSG sets the default for thie mailbox maximum message size@ in bytes when this value is not specified in a Create Mailbox! ($CREMBX) system service call.& DEFMBXMXMSG is a DYNAMIC parameter. 2 DEFPRI7 DEFPRI sets the base default priority for processes.! DEFPRI is a DYNAMIC parameter. 2 DEFQUEPRIA DEFQUEPRI establishes the scheduling priority for jobs enteredB in batch and output (printer, server, and terminal) queues whenA no explicit scheduling priority is specified by the submijtter.C The value of this parameter can range from 0 to 255; the default value is 100.D The value of DEFQUEPRI should be less than or equal to MAXQUEPRI.& NOTEA DEFQUEPRI refers to relative queue scheduling priority, not( the execution priority of the job.$ DEFQUEPRI is a DYNAMIC parameter. 2 DEFUID0 Default POSIX UID used internally by OpenVMS. 2 DELPRC_EXITD DELPRC_EXIT can be used to control $DELPRC system skervice optionsC that call exit handlers prior to final cleanup and deletion of a8 process. The following table describes these options: Option Description= 0 Disable the exit handler functionality with $DELPRC.4 4 Execute kernel mode exit handlers.< 5 (default) Execute exec and more privileged mode exit handlers.B 6 Execute supervisor and more privileged mode exit l handlers.< 7 Execute user and more privileged mode exit handlers.& DELPRC_EXIT is a DYNAMIC parameter. 2 DEVICE_NAMING< (Alpha and Integrity servers) DEVICE_NAMING is a bit maskA indicating whether port allocation classes are used in forming SCSI device names.# Following is the bit definition: Bit Definition! 0 If 1, enable new naming.8 1 Must be 0. This bit is Reserved for use by VSI.E 2 If m1, cloned device unit numbers wrap after 9999(not 65472). F 3 If 1, cloned device unit numbers wrap after 32767(not 65472).G Note that even if both bits are zero, device unit numbers willF wrap after 9999 if "nodename$" is prefixed to the name of theH device in question (e.g. VMS123$DKA100:); devices whose driversF support larger device numbers will wrap after 65472 (or 32767D if bit 3 is set) only if the nodename is not built into the n device name. B For more information about port allocation classes, see the VSI" OpenVMS Cluster Systems manual. 2 DISABLE_UPCALLS> DISABLE_UPCALLS is primarily a debugging aid. It allows the> system manager to disable threads upcalls of specific types@ for the entire system. The value is a bit mask, with the bitsB corresponding to the upcall types. The upcall types are defined# in the definition macro $TMCDEF.D This special parameter is use by VSI and is suboject to change. DoB not change this parameter unless VSI recommends that you do so.* DISABLE_UPCALLS is a DYNAMIC parameter. 2 DISK_QUORUMC The DISK_QUORUM parameter is the name of an optional quorum disk? in ASCII. ASCII spaces indicate that no quorum disk is being used. 2 DISMOUMSGD DISMOUMSG controls whether the messages that log volume dismountsC appear on the operator's terminal and in the operator's log. The; default value of 0 disables reporting of pthese messages.$ DISMOUMSG is a DYNAMIC parameter. 2 DNVOSI1? DNVOSI1 is reserved to DECnet-Plus for OpenVMS. This specialB parameter is use by VSI and is subject to change. Do not change7 this parameter unless VSI recommends that you do so. 2 DORMANTWAITA DORMANTWAIT specifies, in seconds, the amount of time that can> elapse without a significant event before the system treats= a low-priority computable process as a DORMANT process forB scheduling purpos qes. (A low-priority process is a non real-timeD process whose current priority is equal to or less than the value? specified by the system parameter DEFPRI [default=4].) AfterD SUSP (suspended) processes, DORMANT processes are the most likely4 candidates for memory reclamation by the swapper.@ Increasing the value of DORMANTWAIT can increase the interval@ that a low priority process blocks a high priority process ifC that low priority process is holding a lock or resource that rthe* higher priority process is waiting for.& DORMANTWAIT is a DYNAMIC parameter. 2 DR_UNIT_BASE@ (Alpha only) DR_UNIT_BASE specifies the base value from whichC unit numbers for DR devices (DIGITAL StorageWorks RAID Array 200+ Family logical RAID drives) are counted.@ DR_UNIT_BASE provides a way for unique RAID device numbers toC be generated. DR devices are numbered starting with the value ofB DR_UNIT_BASE and then counting from there. For example, setting= s DR_UNIT_BASE to 10 produces device names such as $1$DRA10, $1$DRA11, and so on.D Setting DR_UNIT_BASE to appropriate, nonoverlapping values on allA cluster members that share the same (nonzero) allocation class< ensures that no two RAID devices are given the same name.# DR_UNIT_BASE is a GEN parameter. 2 DUMPBUG@ DUMPBUG enables (1) or disables (0) the writing of error log? buffers and memory contents to SYS$SYSTEM:SYSDUMP.DMP when a@ fatal bugcheck occurs. tThis parameter should be off (0) only( when the executive is being debugged. 2 DUMPSTYLE: DUMPSTYLE specifies the method of writing system dumps.? DUMPSTYLE is a 32-bit mask, with the following bits defined.= Each bit can be set independently. The value of the system@ parameter is the sum of the values of the bits that have beenD set. Remaining or undefined values are reserved for VSI use only.* Bit Mask Description? 0 00000001 u 0 = Full dump (SYSGEN default).C The entire contents of physicalB memory are written to the dump) file.C 1 = Selective dump. The contents ofB memory are written to the dump@ file selectively to maximizeC the usefulness of the dump file@ v while conserving disk space.; 1 00000002 0 = Minimal console output.A 1 = Full console output (includesB stack dump, register contents,/ and so on).8 2 00000004 0 = Dump to system disk.B 1 = Dump off system disk (DOSD) toC an alternate disk. (see the VSIC w OpenVMS System Manager's Manual1 for details.)4 3 (Alpha and 00000008 0 = Do not compress. Integrity servers)A 1 = Compress. (VAX systems do not> support dump compression.)7 4 (Alpha and 00000010 0 = Dump shared memory. Integrity servers)C 1 = Do not dump shared memory. (VAXA x systems do not support shared, memory.)> 5 - 14 reserved for VSI use only.@ 15 (VAX only) 00008000 0 = Disable use of bits 16 - 27.< (Specific to VAX 7000s.)? 1 = Enable use of bits 16 - 27.D 16 - 27 (VAX 0FFF0000 Range of DOSD unit numbers. (VAXA only) systems do not support shared, y memory.)> 28 - 31 reserved for VSI use only.B If you plan to enable the Volume Shadowing minimerge feature onD an Alpha or Integrity servers disk, be sure to specify DOSD to an alternate disk.& NOTE; On Alpha and Integrity servers, you can save space on= the system disk and, in the event of a crash, save time= recording the system memory, by using the OpenVMS Alpha< z and Integrity servers dump compression feature. Unless? you override the default AUTOGEN calculations (by setting= DUMPSTYLE in MODPARAMS.DAT), AUTOGEN uses the following algorithm:@ o On a system with less than 128 MB of memory, the systemA sets the DUMPSTYLE to 1 (a raw selective dump) and sizes% the dump file appropriately.A o On a system with 128 MB of memory or greater, the system? sets the DUMPSTYLE to 9 (a compressed selecti{ve dump),A and creates the dump file at two-thirds the value of the corresponding raw dump. Examples:D The mask of 00000006 directs the system to send a full dump, withD full console output, off the system disk (to the alternate disk).B For a VAX 7000, a mask of 00098006 directs the system to send aC full dump with full console output to the DOSD whose unit number is 9.C On Alpha and Integrity servers, the mask of 00000009 directs theC system to| compress a selective dump with minimal console output.0 DUMPSTYLE has AUTOGEN and DYNAMIC attributes. 2 ERLBUFFERPAG_S2= ERLBUFFERPAG_S2 specifies the amount of S2 space memory to? allocate for each S2 space error log buffer requested by the ERRORLOGBUFF_S2 parameter.B If you increase ERLBUFFERPAG_S2, you must either run AUTOGEN orB manually increase the size of both the system dump file and the error log dump file.A ERLBUFFERPAG_S2 is an AUTOGEN parameter} on Alpha and Integrity servers. 2 ERLBUFFERPAGES< ERLBUFFERPAGES specifies the amount of S0 space memory to? allocate for each S0 space error log buffer requested by the ERRORLOGBUFFERS parameter.@ ERLBUFFERPAGES is an AUTOGEN parameter on Alpha and Integrity servers. 2 ERRORLOGBUFF_S2= ERRORLOGBUFF_S2 specifies the number of S2 space error log= buffers reserved for system error log entries. Each buffer? is ERLBUFFERPAG_S2 in length. If ERRORLOG~BUFF_S2 is too low,D messages might not be written to the error log file. If it is too< high, the buffers can consume unnecessary physical pages.B If you increase ERRORLOGBUFF_S2, you must either run AUTOGEN orB manually increase the size of both the system dump file and the error log dump file.A ERRORLOGBUFF_S2 is an AUTOGEN parameter on Alpha and Integrity servers. 2 ERRORLOGBUFFERS= ERRORLOGBUFFERS specifies the number of S0 space error log@ buffers reserved for system error log entries. Each buffer isD ERLBUFFERPAGES in length. If ERRORLOGBUFFERS is too low, messagesA might not be written to the error log file. If it is too high,6 the buffers can consume unnecessary physical pages.A ERRORLOGBUFFERS is an AUTOGEN parameter on Alpha and Integrity servers. 2 EXECSTACKPAGESC (Alpha and Integrity servers) EXECSTACKPAGES controls the number. of pages allocated for each RMS exec stack.) EXECSTACKPAGES is a DYNAMIC parameter. 2 EXPECTED_VOTESC EXPECTED_VOTES specifies the maximum number of votes that can beD present in a cluster at any given time. Set it to a value that isB equal to the sum of the vote parameters of all cluster members,? plus any votes that are contributed by the quorum disk. ThisA value is used to automatically derive the number of votes that8 must be present for the cluster to function (quorum).4 EXPECTED_VOTES is an AUTOGEN attribute parameter. 2 EXTRACPUC EXTRACPU sets the time, in units of 10 ms, allotted to each of aC process's exit handlers (for each access mode) after the process3 times out (that is, reaches its CPU time limit).- EXTRACPU is a DYNAMIC attribute parameter. 2 FAST_PATH= (Alpha and Integrity servers) FAST_PATH is a static system; parameter that enables (1) or disables (0) the Fast Path8 performance features for all Fast Path-capable ports.D Starting in OpenVMS Version 7.2, FAST_PATH is enabled by default.> In Versions 7.0 and 7.1, FAST_PATH was disabled by default.3 For additional information, see FAST_PATH_PORTS. 2 FAST_PATH_PORTS< (Alpha and Integrity servers) FAST_PATH_PORTS is a static= parameter that deactivates Fast Path for specific drivers.A FAST_PATH_PORTS is a 32-bit mask, with a bit assigned for each? Fast Path port driver. The following table describes the bit values: Bit Value DescriptionC 1 Indicates that Fast Path is disabled for ports serviced( by the corresponding driver.> 0 Indicates that Fast Path is not disabled for ports1 serviced by the corresponding driver.= Beginning in OpenVMS Version 7.3-1, values of specific bit8 positions are those described in the following table: Bit Position DescriptionA 0 Controls Fast Path for PKQDRIVER (for parallel SCSI).@ 1 Controls Fast Path for FGEDRIVER (for Emulex LP7000,:  LP8000, LP9002, LP9802, LP10000 FibreChannel).B 2 Controls Fast Path for PKADRIVER (for Adaptec AIC-78xx Ultra3 SCSI).6 3 Controls Fast Path for PEDRIVER (for LAN).D 4 Controls Fast Path for PKRDRIVER (for SMART Array 5300).; 5 Controls Fast Path for PKMDRIVER, the LSI Logic( LSI53C1030 SCSI port driver.@ 6 Controls Fast Path for PGQDRIVER, the Qlogic ISP23xx% FibreChannel port driver.A C urrently, the default setting for FAST_PATH_PORTS is 0, whichA means that Fast Path is enabled for all drivers that appear in the table.# In addition, note the following:A o CI drivers are not controlled by FAST_PATH_PORTS. Fast PathA for CI is enabled and disabled exclusively by the FAST_PATH system parameter.> o FAST_PATH_PORTS is relevant only if the FAST_PATH systemB parameter is enabled (equal to 1). Setting FAST_PATH to zeroD has the same e ffect as setting all the bits in FAST_PATH_PORTS to 1.C For additional information, see FAST_PATH. For an explanation ofD how to set the bits, see the OpenVMS I/O User's Reference Manual. 2 FREEGOAL< FREEGOAL establishes the number of pages that you want to> reestablish on the free-page list following a system memoryC shortage. Memory shortages occur when the system drops below theD minimum number of pages required on the free-page list (FREELIM).D The value of FREEGOAL must always be greater than or equal to the value of FREELIM.; FREEGOAL has the AUTOGEN, DYNAMIC, and MAJOR attributes. 2 FREELIM? FREELIM sets the minimum number of pages that must be on the free-page list.A The system writes pages from the modified-page list, swaps outD working sets, or reduces the size of the working sets to maintain the minimum count.D While the larger free-page list generally means less page I/O, itC also means less space for the balance set, which tends to resultD in more swap I/O. You can monitor the size of the free-page list,A the amount of page, and the amount of swap with the MONITOR IO" command of the Monitor utility.0 FREELIM has the AUTOGEN and MAJOR attributes. 2 GALAXYA (Alpha Galaxy platforms only) The GALAXY parameter sets memory sharing. Specify one of the following: Value Description@ 0 The default. Do not participate in a memory sharing., 1 Participate in a memory sharing.B When you set GALAXY to 1 in a hard partition, OpenVMS instances= will share memory between soft partitions within that hardB partition. (You can run more than two soft partitions in a hardD partition, and you might might not want to share memory among allB of them.) Note that GALAXY specifies only if a node uses shared? memory. You do not need to use the parameter to run multipleD cooperative instances of OpenVMS; you do this by co nsole setup of( the configuration tree that you want. 2 GBLPAGESB GBLPAGES sets the number of global page table entries allocated@ at bootstrap time. Each global section requires 1 global page? table entry per section page, plus 2 entries, with the total rounded up to an even number.= Users with CMKRNL privilege can change this parameter on a@ running system. Increasing the value of this parameter allows@ the global page table to expand, on demand, up to the maxim um size.D The default value is sufficient for the images normally installed? as shared in the system startup command procedures. Once theA system is running and all global sections are created, you can@ examine the actual requirements with the /GLOBAL qualifier ofA the Install utility (INSTALL) and reduce the value of GBLPAGES? accordingly. However, do not set the value of this parameterA too low, because the page table entries use little permanently> resident memory . If you plan to install many user images as? shared, or if user programs are likely to create many global; sections, you must increase the value of this parameter.> GBLPAGES has the AUTOGEN, DYNAMIC, FEEDBACK, GEN, and MAJOR attributes. 2 GBLPAGFILC GBLPAGFIL defines the maximum number of systemwide pages allowedB for global page-file sections (scratch global sections that can> be used without being mapped to a file). These global page-? file sections can be temp orary, permanent, system, or group,? and are allocated from the page file specified in the system= process header at bootstrap time. When you allow pages for? global page-file sections, you must increase the size of the@ page file accordingly. Users with CMKRNL privilege can change, this parameter value on a running system.@ Global page-file sections are created with the Create and MapA Section system services ($CREATE_GPFILE, $CRMPSC, and $CRMPSC_D GPFILE_64) without an explicit disk file. These sections are usedA for the RMS global buffers required for shared files. Users of@ shared files should note that global page-file sections cause> both the global page table and the default system page file> (PAGEFILE.SYS) to be used. If the value of GBLPAGFIL is tooD small, $CRMPSC issues an error message when you attempt to create global page-file sections.> You must have scratch global sections if you use RMS globalB buffers. Each file using gl obal buffers requires, in the system@ page file, the file's bucket size multiplied by the number ofB global buffers for that file. If the file's bucket size varies,> as with RMS indexed files, use the maximum bucket size. ForA shared sequential files, use the multiblock count of the first@ stream to perform the $CONNECT service in place of the file's bucket size.< The default value for this parameter is adequate for most@ systems. However, if your site uses RMS global buff ering to aD significant extent, you may need to raise the value of GBLPAGFIL.> Use the /GLOBAL qualifier of the Install utility to examineA the number of pages consumed by RMS global buffers. The global? sections used by RMS for global buffers have the prefix RMS$$ followed by 8 hexadecimal digits.6 Global buffers are enabled with the DCL command SETA FILE/GLOBAL_BUFFERS, which is described in the VSI OpenVMS DCL Dictionary.; GBLPAGFIL is an AUTOGEN-altered and a DYN AMIC parameter. 2 GBLSECTIONS< GBLSECTIONS sets the number of global section descriptors@ allocated in the system header at bootstrap time. Each globalB section requires one descriptor. Each descriptor takes 32 bytes" of permanently resident memory.D The default value is sufficient for the images normally installed? as shared in the system startup command procedures. Once theA system is running and all global sections are created, you canD examine the actual requir ements with the /GLOBAL qualifier of theC Install utility and reduce the value of GBLSECTIONS accordingly.B However, the value of this parameter should not be set too low.@ If you plan to install many user images as shared, or if user? programs are likely to create many global sections, you must( increase the value of this parameter.B If the value of GBLSECTIONS is too small, you receive a message> from the Install utility at system startup time or whenever? you install images manually. Note that too large a value for& GBLSECTIONS wastes physical memory.D GBLSECTIONS has the AUTOGEN, FEEDBACK, GEN, and MAJOR attributes. 2 GB_CACHEALLMAXC (Alpha and Integrity servers) If a file is connected to RMS withA the RMS global buffer DEFAULT option enabled, the number of ofD blocks cached is either a maximum of the GB_CACHEALLMAX parameterD or a percentage of the file, whichever results in a larger global count.; Note that although a maxi mum cache size of %x7FFFFFFF is> supported for an indexed file, sequential and relative fileA organizations are restricted to a maximum cache size of 32767.) GB_CACHEALLMAX is a DYNAMIC parameter. 2 GB_DEFPERCENTC (Alpha and Integrity servers) If a file is connected to RMS withD the RMS global buffer DEFAULT option enabled, either a percentage@ (GB_DEFPERCENT) of the file is cached or up to GB_CACHEALLMAX@ blocks of it are cached, whichever results in a larger global= buffer count. A percentage greater than 100 percent can beA specified for GB_DEFPERCENT to provide growing room for a file in the global cache.; Note that although a maximum cache size of %x7FFFFFFF is> supported for an indexed file, sequential and relative fileA organizations are restricted to a maximum cache size of 32767.( GB_DEFPERCENT is a DYNAMIC parameter. 2 GH_EXEC_CODEC (Alpha and Integrity servers) GH_EXEC_CODE specifies the size in5 pages of the execlet code granularity hint region.8 GH_EXEC_CODE has the AUTOGEN and FEEDBACK attributes. 2 GH_EXEC_DATAC (Alpha and Integrity servers) GH_EXEC_DATA specifies the size in5 pages of the execlet data granularity hint region.8 GH_EXEC_DATA has the AUTOGEN and FEEDBACK parameters. 2 GH_RES_CODEB (Alpha and Integrity servers) GH_RES_CODE specifies the size in< pages of the resident image code granularity hint region.7 GH_RES_CODE has the AUTOGEN and FEEDBACK attributes. 2 GH_RES_CODE_S2> Specifies the size in pages of the resident 64-bit S2 space/ resident image code granularity hint region. 2 GH_RES_DATAB (Alpha and Integrity servers) GH_RES_DATA specifies the size in< pages of the resident image data granularity hint region.> If bit 2 of the LOAD_SYS_IMAGES parameter is set, the image? LDR$WRAPUP releases all unused pages in the granularity hintC region at the the end of system startup. The unused pages of theA resident image granularity hint region are either reserved for5 future use, or given back to the free memory list.7 GH_RES_DATA has the AUTOGEN and FEEDBACK attributes. 2 GH_RSRVPGCNTC GH_RSRVPGCNT specifies the number of pages in the resident image@ code granularity hint region that the Install utility can use) after the system has finished booting.> If bit 2 of the LOAD_SYS_IMAGES parameter is set, the image? LDR$WRAPUP releases all unused pages in t he granularity hintC region at the the end of system startup. The unused pages of theA resident image granularity hint region are either reserved for5 future use, or given back to the free memory list.= GH_RSRVPGCNT specifies the number of pages that LDR$WRAPUP@ attempts to leave in the resident image code granularity hintA region. If the GH_RSRVPGCNT number of pages is larger than theA unused pages in the granularity hint region, the region is not9 expanded to accommodate the number of pages requested.2 GH_RSRVPGCNT is a FEEDBACK attribute parameter. 2 GLX_INST_TMO= (Alpha Galaxy platforms only) GLX_INST_TMO is the time (inB milliseconds) that an instance in a Galaxy sharing set can failD to increment its timeout value before the other sharing instancesB presume that the instance failed and remove it from the sharing set.) The default is 20,000 ms (20 seconds). 2 GLX_SHM_REG@ For Alpha Galaxy systems, GLX_SHM_REG i s the number of sharedA memory region structures configured into the Galaxy ManagementD Database (GMDB). If set to 0, the default number of shared memory regions are configured.> If the condition value SS$_INSF_SHM_REG is returned for theD $CRNMPSC_GDZRO_64 system service with the flag SEC$M_SHM_REG, theA Galaxy shared memory code has run out of internal SHM_REG dataD structures. You need to increase the system parameter GLX_SHM_REGD and reboot all Galaxy instances with this larger parameter value. 2 GROWLIMD GROWLIM sets the number of pages that the system must have on theA free-page list so that a process can add a page to its workingC set when it is above quota. GROWLIM has no effect if the processA is below its working set quota. GROWLIM acts as a fast shutoffA to the working set extent mechanism based on the system's free memory.6 GROWLIM has AUTOGEN, DYNAMIC, and MAJOR attributes. 2 IEEE_ADDRESS- IEEE_ADDRESS is reserved for VSI use only. 2 IEEE_ADDRESSH. IEEE_ADDRESSH is reserved for VSI use only. 2 IJOBLIMB IJOBLIM sets the maximum number of interactive jobs that can beD on the system concurrently. You can control the maximum number ofB concurrent interactive users on the system with the DCL command SET LOGINS/INTERACTIVE." IJOBLIM is a DYNAMIC parameter. 2 IMGIOCNT> IMGIOCNT specifies the default number of pages of image I/O? address space to be allocated f or the image activator if not" specified at program link time.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 IMGREG_PAGES> (Alpha and Integrity servers) IMGREG_PAGES is the number of? pages to reserve in P1 space for images to be installed withA shareable address data. If IMGREG_PAGES is set to 0, no images@ are installed with shared address data. The default is 10,000 pages.C For more information, see the INSTALL section in the VSI OpenVMS0 System Management Utilities Reference Manual. 2 IO_PRCPU_BITMAP; (Alpha and Integrity servers) This parameter is a bitmap< representing up to 1024 CPUs. Each bit set in this bitmapA indicates that the corresponding CPU is available for use as a Fast Path preferred CPU.D IO_PRCPU_BITMAP defaults to all bits set. (CPU 0 through CPU 10232 are all enabled for Fast Path port assignment.)> You might want to disable the primary CPU from serving as aC preferred CPU by leaving its bit clear in IO_PRCPU_BITMAP, whichC reserves the primary CPU for non-Fast Path IO operations to use.? To change the value of IO_PRCPU_BITMAP in SYSBOOT or SYSGEN,B specify a list of individual bits or contiguous groups of bits. For example:+ SYSGEN> SET IO_PRCPU_BITMAP 0,5,17-21D This command sets bits 0, 5, 17, 18, 19, 20, and 21 in the bitmap and clears all other bits.C Changing the value of IO_PRCPU_BITMAP causes the FASTPATH_SERVERA process to run the automatic assignment algorithm that spreads; Fast Path ports evenly among the new set of usable CPUs.A For additional information, see FAST_PATH and FAST_PATH_PORTS.) This parameter replaces IO_PREFER_CPU. 2 IOTAA IOTA specifies the amount of time (in 10-millisecond units) toC charge to the current residence quantum for each voluntary wait.C The correct value approximates the cost of a disk I/O neglecting wait time.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 IRPCOUNT@ IRPCOUNT sets the number of preallocated intermediate requestB packets. Each packet requires 160 bytes of permanently resident? memory. If IRPCOUNT is too large, physical memory is wasted.; If IRPCOUNT is too small, the system increases its value: automatically, as needed, to permit proper performance.@ However, the system cannot increase IRPCOUNT beyond the value of IRPCOUNTV.< Allowing this growth causes a physical memory penalty. IfD IRPCOUNT is underconfigured, the penalty is 4 percent of physical> memory from the configured value to the actual value on the running system.A You can use the DCL command SHOW MEMORY/POOL/FULL to determine IRPCOUNT usage.- IRPCOUNT has the GEN and MAJOR attributes. 2 IRPCOUNTVA IRPCOUNTV establishes the upper limit to which IRPCOUNT can be) automatically increased by the system.> If this parameter is set too low, system performance can beC adversely affected because IRPCOUNTV cannot be used for nonpaged pool requests.@ A physical memory penalty of 1 percent results for any unusedC growth space (1 longword for every 3 unused intermediate request packets).# IRPCOUNTV has the GEN attribute. 2 JBOBLIM& This parameter is no longer in use. 2  JOBCTLDC System managers do not usually alter JOBCTLD; this word of debugA flags is used in rolling upgrades of OpenVMS. If bit 0 is set,6 the queue manager does not start. The default is 0.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 KSTACKPAGESC (Alpha and Integrity servers) KSTACKPAGES controls the number of- pages allocated for process kernel stacks. 2 LAN_FLAGS@  (Alpha and Integrity servers) LAN_FLAGS is a bit mask used to> enable features in the local area networks port drivers and6 support code. The default value for LAN_FLAGS is 0.& The bit definitions are as follows: Bit DescriptionC 0 The default of zero indicates that ATM devices run inE SONET mode. If set to 1, this bit indicates ATM devices run in SDH mode.@ 1 If set, this bit enables a subset of the ATM traceD and debug messages in the LAN port drivers and support code.> 2 If set, this bit enables all ATM trace and debug@ messages in the LAN port drivers and support code.B 3 If set, this bit runs UNI 3.0 over all ATM adapters.E (Auto-sensing of the ATM UNI version is enabled if both+ bit 3 and bit 4 are off (0).)B 4 If set, this bit runs UNI 3.1 over all ATM adapters.E (Auto-sensing of the ATM UNI version is enabled if both+ bit 3 and bit 4 are off (0).)@ 5 If set, disables auto-negotiation over all Gigabit Ethernet Adapters.> 6 If set, enables the use of jumbo frames over all( Gigabit Ethernet Adapters. 7 Reserved.C 8 If set, disables the use of flow control over all LAN1 adapters that support flow control. 9 Reserved. 10 Reserved. B 11 If set, disables the logging of error log entries by LAN drivers.B 12 If set, enables a fast timeout on transmit requests,A usually between 1 and 1.2 seconds instead of 3 to 4, seconds, for most LAN drivers.@ 13 If set, transmits that are given to the LAN deviceA and never completed by the device (transmit timeoutD condition) are completed with error status (SS$_ABORT)6 rather than success status (SS$_NORMAL).$ LAN_FLAGS is a DYNAMIC parameter. 2 LCKMGR_CPUIDC (Alpha and Integrity servers) LCKMGR_CPUID controls the CPU thatC the Dedicated CPU Lock Manager runs on. This is the CPU that theB LCKMGR_SERVER process utilizes if you turn this feature on with$ the LCKMGR_MODE system parameter.9 If the specified CPU ID is either the primary CPU or aA nonexistent CPU, the LCKMGR_SERVER process utilizes the lowestC nonprimary CPU. For more information, see the LCKMGR_MODE system parameter.' LCKMGR_CPUID is a DYNAMIC parameter. 2 LCKMGR_MODEC (Alpha and Integrity servers) The LCKMGR_MODE parameter controlsB use of the Dedicated CPU Lock Manager. Setting LCKMGR_MODE to aA number greater than zero (0) indicates the number of CPUs thatA must be active before the Dedicated CPU Lock Manager is turned on.A The Dedicated CPU Lock Manager performs all locking operationsA on a single dedicated CPU. This can improve system performanceC on large SMP systems with high MP_Synch associated with the lock manager.C If the number of active CPUs is greater than or equal to LCKMGR_> MODE, a LCKMGR_SERVER process is created to service lockingB operations. This process runs at a real-time priority of 63 and is always current.C In addition, if the number of active CPUs should ever be reducedB below the required threshold by either a STOP/CPU command or byB a CPU reassig nment in a Galaxy configuration, the Dedicated CPUB Lock Manager automatically turns off within one second, and theA LCKMGR_SERVER is placed in a hibernate state. If the number of@ active CPUs is increased, the LCKMGR_SERVER resumes servicing locking operations. Specify one of the following:C o Zero (0) indicates that the Dedicated CPU Lock Manager is off (the default).A o A number greater than zero (0) indicates the number of CPUsD that must be active before the Dedicated CPU Lock Manager will turn on.> When the Dedicated CPU Lock Manager is turned on, fast path@ devices are not assigned to the CPU used by the Dedicated CPU Lock Manager.> When the Dedicated CPU Lock Manager is turned on, fast path@ devices are not assigned to the CPU used by the Dedicated CPU Lock Manager.D For more information about use of the Dedicated CPU Lock Manager,1 see the OpenVMS Performance Management manual.& LCKMGR_MODE is a DYNAMIC parameter. 2 LGI_BRK_DISUSERC LGI_BRK_DISUSER turns on the DISUSER flag in the UAF record when> an attempted break-in is detected, thus permanently locking> out that account. The parameter is off (0) by default. YouB should set the parameter (1) only under extreme security watch= conditions, because it results in severely restricted user service.* LGI_BRK_DISUSER is a DYNAMIC parameter. 2 LGI_BRK_LIMA LGI_BRK_LIM specifies the number of failures th at can occur at? login time before the system takes action against a possibleA break-in. The count of failures applies independently to loginA attempts by each user name, terminal, and node. Whenever login> attempts from any of these sources reach the break-in limitB specified by LGI_BRK_LIM, the system assumes it is under attack? and initiates evasive action as specified by the LGI_HID_TIM parameter.A The minimum value is 1. The default value is usually adequate.& LGI_BRK_LIM is a DYNAMIC parameter. 2 LGI_BRK_TERM: LGI_BRK_TERM causes the terminal name to be part of theB association string for the terminal mode of break-in detection.@ When LGI_BRK_TERM is set to off (0), the processing considers? the local or remote source of the attempt, allowing break-in@ detection to correlate failed access attempts across multipleB terminal devices. When set to on (1), LGI_BRK_TERM assumes that> only local hard-wired or dedicated terminals are in use andD causes breakin detection processing to include the specific localB terminal name when examining and correlating break-in attempts.B Ordinarily, LGI_BRK_TERM should be set to off (0) when physical? terminal names are created dynamically, such as when network, protocols like LAT and Telnet are in use.' LGI_BRK_TERM is a DYNAMIC parameter. 2 LGI_BRK_TMO= LGI_BRK_TMO specifies the length of the failure monitoringC period. This time increment is added to the suspect's expirationD time each time a login failure occurs. Once the expiration periodC passes, prior failures are discarded, and the suspect is given a clean slate.& LGI_BRK_TMO is a DYNAMIC parameter. 2 LGI_CALLOUTSD LGI_CALLOUTS specifies the number of installation security policyD callout modules to be invoked at each login. LGI_CALLOUTS must be/ set to 0 unless callout modules are present.' LGI_CALLOUTS is a DYNAMIC parameter. 2 LGI_HID_T IMB LGI_HID_TIM specifies the number of seconds that evasive actionC persists following the detection of a possible break-in attempt.B The system refuses to allow any logins during this period, even3 if a valid user name and password are specified.& LGI_HID_TIM is a DYNAMIC parameter. 2 LGI_PWD_TMO? LGI_PWD_TMO specifies, in seconds, the period of time a userB has to enter the correct system password (if used). LGI_PWD_TMO? also establishes the timeout period for u sers to enter theirA personal account passwords at login time. Also, when using theA SET PASSWORD command, LGI_PWD_TMO specifies the period of time@ the system waits for a user to type in a new password, an old+ password, and the password verification.& LGI_PWD_TMO is a DYNAMIC parameter. 2 LGI_RETRY_LIM? LGI_RETRY_LIM specifies the number of retry attempts allowedC users attempting to log in. If this parameter is greater than 0,D and a legitimate user fails to log in correctly because of typingD errors, the user does not automatically lose the carrier. InsteadA (provided that LGI_RETRY_TMO has not elapsed), by pressing the> Return key, the user is prompted to enter the user name andA password again. Once the specified number of attempts has been? made without success, the user loses the carrier. As long as@ neither LGI_BRK_LIM nor LGI_BRK_TMO has elapsed, the user can% dial in again and reattempt login.( LGI_RETRY_LIM is a DYNAMIC parameter. 2 LGI_RETRY_TMO@ LGI_RETRY_TMO specifies the number of seconds allowed between< login retry attempts after each login failure. (Users can; initiate login retries by pressing the Return key.) This: parameter is intended to be used with the LGI_RETRY_LIM@ parameter; it allows dialup users a reasonable amount of timeA and number of opportunities to attempt logins before they lose the carrier.( LGI_RETRY_TMO is a DYNAMIC parameter. 2 LNMPHASHTBL D LNMPHASHTBL sets the size of the process logical name hash table.? Logical names are hashed using a function of the name length@ and contents. The LNMPHASHTBL parameter determines the number@ of entries for process-private logical names. The recommendedB setting is the average number of process-private logical names.B Note that the hashed values are rounded up to the nearest power of 2.D LNMPHASHTBL has the GEN attribute. On VAX systems, LNMPHASHTBL is% also an AUTOGEN -altered parameter. 2 LNMSHASHTBLC LNMSHASHTBL sets the size of the system logical name hash table.? Logical names are hashed using a function of the name length@ and contents. The LNMSHASHTBL parameter determines the numberB of entries for shareable logical names. These names include allA names from the system, group, and job logical name tables. The@ recommended setting allows one to four logical names per hash? table entry. The default setting is usually adequate, u nlessC your installation has a large number of groups, or many jobs areC active simultaneously. In that case, an increase in the value ofD the next higher power of 2 might improve logical name translationA performance. Note that the hashed values are rounded up to the nearest power of 2.= LNMSHASHTBL has the AUTOGEN, FEEDBACK, and GEN attributes. 2 LOAD_PWD_POLICY< LOAD_PWD_POLICY controls whether the SET PASSWORD command@ attempts to use site-specific password policy routines, whichA are contained in the shareable image SYS$LIBRARY:VMS$PASSWORD_B POLICY.EXE. The default is 0, which indicates not to use policy routines. 2 LOAD_SYS_IMAGESD This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so.B LOAD_SYS_IMAGES controls the loading of system images describedC in the system image data file, VMS$SYSTEM_IMAGES. This parameter is a bit mask.B On Alpha and Integrity servers, the following bits are defined:* Bit DescriptionA 0 (SGN$V_LOAD_SYS_IMAGES) Enables loading alternate execletsC specified in VMS$SYSTEM_IMAGES.DATA.9 1 (SGN$V_EXEC_SLICING) Enables executive slicing.C 2 (SGN$V_RELEASE_PFNS) Enables releasing unused portions ofC the Alpha and Integrity servers huge% pages.D These bits are on by default. Using conversational bootstrap exec slicing can be disabled.@ On Alpha and Integrity servers, LOAD_SYS_IMAGES is an AUTOGEN parameter. 2 LOCKDIRWTB LOCKDIRWT determines the portion of lock manager directory that> this system handles. The default value is usually adequate.% LOCKDIRWT is an AUTOGEN parameter. 2 LOCKIDTBLB LOCKIDTBL sets the initial number of entries in the system Lock@ ID table and defines the amount by which the Lock ID table isA extended whenever the system runs out of locks. One entry mustB exist for each lock in the system; each entry requires 4 bytes.A For simple timesharing systems, the default value is adequate.C If your application uses many locks, as in the case of heavy RMS@ file sharing or a database management application, you shouldC increase this parameter. When you change the value of LOCKIDTBL,> examine the value of RESHASHTBL and change it if necessary.? The OpenVMS Lock Management facility is described in the VSIB OpenVMS Programming Concepts Manual. You can monitor locks with3 the MONITOR LOCK command of the Monitor utility.= LOCKIDTBL has the AUTOGEN, FEEDBACK, and MAJOR attributes. 2 LOCKIDTBL_MAX@ LOCKIDTBL_MAX is obsolete beginning with OpenVMS Version 7.1. 2 LOCKRETRY> LOCKRETRY establishes the number of attempts made to lock a! multiprocessor data structure.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 LOCKRMWT& NOTE? On OpenVMS Version 8.3 systems, LOCKRMWT does not control& lock remastering. See LOCKDIRWT.? LOCKRMWT can have a value from zero to 10. The default is 5.B Remaster decisions are based on the difference in lock remasterA weights between the master and a remote node. When weights areB equal, the remote node needs about 13% more a ctivity before theB tree is remastered. If a remote node has a higher lock remasterC weight, the amount of activity is less. If the remote node has aB lower lock remaster weight, the additional activity required to! move the tree is much greater.A Lock remaster weights of zero and 10 have additional meanings.@ A value of zero indicates that a node does not want to masterA trees and always remasters to an interested node with a higher= LOCKRMWT. Lock trees on an interested node with a LOCKRMWT? lower than 10 are remastered to the node with a weight of 10 for LOCKRMWT.# LOCKRMWT is a DYNAMIC parameter. 2 LONGWAIT? LONGWAIT defines how much real time (in seconds) must elapseA before the swapper considers a process to be temporarily idle.D This parameter is applied to local event flag (LEF) and hibernateC (HIB) waits to detect such conditions as an inactive terminal or ACP.@ LONGWAIT has the DYNAMIC, GEN, and MAJOR attributes. On Alpha= and Integrity servers, LONGWAIT is also an AUTOGEN-altered parameter. 2 MAXBOBMEM> (Alpha and Integrity servers) MAXBOBMEM defines the maximum? amount of physical memory, measured in pagelets, that can be> associated with a single buffer object created by a processA in user mode. The default value of 0 means there is no system-0 imposed limit on the size of a buffer object.$ MAXBOBMEM is a DYNAMIC parameter.? Other MAXBOB* parameters are obsolete beginning with OpenVMS Version 7.3. 2 MAXBUFA MAXBUF sets the maximum allowable size for any single buffered: I/O packet. Buffered I/O packets are allocated from the< permanently resident nonpaged dynamic pool. The terminal,= mailbox, and printer device drivers are examples of device% drivers that perform buffered I/O.D The number of bytes specified in the I/O request plus the size ofB a driver-dependent and function-dependent header area determine@ the required buffered I/O packet size. The size of the headerC area is a minimum of 16 bytes; there is no absolute upper limit.D However, this header area is usually a few hundred bytes in size.C The default value on Alpha and Integrity servers continues to be 8192.. The maximum value of MAXBUF is 64000 bytes.! MAXBUF is a DYNAMIC parameter. 2 MAXCLASSPRI? If class scheduling is enabled, MAXCLASSPRI sets the maximum< range in the priority range of class-scheduled processes.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so.& MAXCLASSPRI is a DYNAMIC parameter. 2 MAXPROCESSCNTD MAXPROCESSCNT sets the number of process entry slots allocated atC bootstrap time. One slot is required for each concurrent processD on the system. Each slot requires 6 bytes of permanently resident memory.B The default value is normally configured to allow you to create< the desired number of processes. If the following message< appears, you need to increase the value of MAXPROCESSCNT:. %SYSTEM-F-NOSLOT, No PCB to create processA On Alpha and Integrity servers beginning with Version 8.1, the default value is 32,767.: MAXPROCESSCNT has the AUTOGEN, FEEDBACK, GEN, and MAJOR attributes. 2 MAXQUEPRIC MAXQUEPRI determines the highest scheduling priority that can beA assigned to jobs entered in batch and output (printer, server,D and terminal) queues without the submitter process having OPER orD ALTPRI privilege. The value of this parameter can range from 0 toD 255; the default is 100. The value of MAXQUEPRI should be greater than or equal to DEFQUEPRI.& NOTEA MAXQUEPRI refers to relative queue scheduling priority, not+ to the execution priority of the job.$ MAXQUEPRI is a DYNAMIC parameter. 2 MAXSYSGROUPB MAXSYSGROUP sets the highest value that a group number can haveB and still be classified as a system UIC group number. Note thatD the specification is not in octal unless preceded by the %O radix> indicator. This parameter is normally left at 8 (10 octal).& MAXSYSGROUP is a DYNAMIC parameter. 2 MC_SERVICES_P0D (Alpha only) MC_SERVICES_P0 controls whether other MEMORY CHANNELA nodes in the cluster continue to run if this node bugchecks or shuts down.C A value of 1 causes other nodes in the MEMORY CHANNEL cluster toB crash with bugcheck code MC_FORCED_CRASH if this node bugchecks or shuts down.> The default value is 0. A setting of 1 is intended only for@ debugging purposes; the parameter should otherwise be left at its default value.) MC_SERVICES_P0 is a DYNAMIC parameter. 2 MC_SERVICES_P1C (Alpha only) This special parameter is reserved for VSI use. ItsC value must be the same on all nodes connected by MEMORY CHANNEL.) MC_SERVICES_P1 is a DYNAMIC parameter. 2 MC_SERVICES_P2< (Alpha only) MC_SERVICES_P2 specifies whether to load the6 PMDRIVER (PMA0) MEMORY CHANNEL cluster port driver.A PMDRIVER is a driver that serves as the MEMORY CHANNEL clusterC port driver. It works together with MCDRIVER (the MEMORY CHANNEL@ device driver and driver interface) to provide MEMORY CHANNELA clustering. If PMDRIVER is not loaded, cluster connections are1 not made over the MEMORY CHANNEL interconnect.B The default v alue is 1, which causes PMDRIVER to be loaded whenB you boot the system. When you run CLUSTER_CONFIG.COM and selectC the MEMORY CHANNEL option, PMDRIVER is loaded automatically when you reboot the system.@ VSI recommends that this value not be changed. This parameterC value must be the same on all nodes connected by MEMORY CHANNEL. 2 MC_SERVICES_P3C (Alpha only) MC_SERVICES_P3 specifies the maximum number of tagsA supported. The maximum value is 2048, and the minimum value is 100.? The default value is 800. VSI recommends that this value notA be changed. This parameter value must be the same on all nodes connected by MEMORY CHANNEL.) MC_SERVICES_P3 is a DYNAMIC parameter. 2 MC_SERVICES_P4> (Alpha only) MC_SERVICES_P4 specifies the maximum number of@ regions supported. The maximum value is 4096, and the minimum value is 100.? The default value is 200. VSI recommends that this value notA be changed. This parameter value must be the same on all nodes connected by MEMORY CHANNEL. 2 MC_SERVICES_P5D (Alpha only) MC_SERVICES_P5 is reserved for VSI use only and mustA remain at the default value of 8000000. This value must be the1 same on all nodes connected by MEMORY CHANNEL.) MC_SERVICES_P5 is a DYNAMIC parameter. 2 MC_SERVICES_P6? (Alpha only) MC_SERVICES_P6 specifies MEMORY CHANNEL messageC size, the body of an entry in a free queue, or a work queue. The8 m aximum value is 65536, and the minimum value is 544.@ The default value is 992. This value is suitable in all cases> except for systems with highly constrained memory. For suchD systems, you can reduce the memory consumptions of MEMORY CHANNELB by slightly reducing the default value of 992. The value of MC_D SERVICES_P6 must always be equal to or greater than the result of the following calculations:4 1. Select the larger of SCS_MAXMSG and SCS_MAXDG./ 2. Round that value up to the next quadword.< The value of MC_SERVICES_P6 must be the same on all nodes connected by MEMORY CHANNEL. 2 MC_SERVICES_P7? (Alpha only) MC_SERVICES_P7 specifies whether to suppress orA display messages about MEMORY CHANNEL activities on this node.6 This parameter can be set to a value of 0, 1, or 2:> o A value of 0 indicates nonverbose mode: no informational9 messages appear on the console or in the error log.A o A value of 1 indicates verbose mode: informational messagesB from both MCDRIVER and PMDRIVER appear on the console and in the error log.A o A value of 2 provides the same output as a value of 1, with> the addition of PMDRIVER stalling and recovery messages.= The default value is 0. VSI recommends that this value not? be changed except while debugging MEMORY CHANNEL problems or* adjusting the MC_SERVICES_P9 parameter.) MC_SERVICES_P7 is a DYNAMIC parameter. 2 MC_SERVICES_P8D (Alpha only) MC_SERVICES_P8 is reserved for VSI use only and mustB remain at the default value of 0. The value must be the same on) all nodes connected by MEMORY CHANNEL. 2 MC_SERVICES_P9> (Alpha only) MC_SERVICES_P9 specifies the number of initialA entries in a single channel's free queue. The maximum value is% 2048, and the minimum value is 10.@ Note that MC_SERVICES_P9 is not a dynamic parameter; you must> reboot the system after each change for that change to take effect.B The default value is 150. VSI recommends that this value not be changed.< The value of MC_SERVICES_P9 must be the same on all nodes connected by MEMORY CHANNEL. 2 MINCLASSPRI? If class scheduling is enabled, MINCLASSPRI sets the minimum< range in the priority range of class-scheduled processes.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so.& MINCLASSPRI is a DYNAMIC parameter. 2 MINWSCNT> The value specified by MINWSCNT is added to the size of the< process header to establish the minimum working set size.C On Alpha and Integrity servers, MINWSCNT sets the minimum number@ of pages required for the execution of a process. The default( value is 20; the minimum value is 10.$ MINWSCNT is an AUTOGEN parameter. 2 MMG_CTLFLAGS= MMG_CTLFLAGS is a bitmask used to enable or disable memory! management-related activities.< The first two bits, 0 and 1, control the proactive memoryB reclamation mechanisms. Bit 2 controls deferred memory testing.- The following bit mask values are defined: Bit Description@ 0 If this bit is set, reclamation is enabled by trimming: from periodically executing, but otherwise idle,? processes. This occurs when the size of the free listC plus the modified list drops below two times the value ofB FREEGOAL. This f unction is disabled if the bit is clear.C 1 If this bit is set, reclamation is enabled by outswapping@ processes that have been idle for longer than LONGWAITC seconds. This occurs when the size of the free list dropsA below FREEGOAL. This function is disabled if the bit is clear.? 2 Controls deferred memory testing (only on AlphaServerA 4100 systems). You can use this bit to speed up elapsed> bootstrap time by contro lling when memory is tested:D o If the bit is clear (the default), OpenVMS tests memory? as a background activity, which might or might not> complete before the end of the bootstrap process.; o If the bit is set, all memory is tested in the@ bootstrap process by the end of the EXEC_INIT phase6 (that is, before IPL is lowered from 31).0 3 Reserved to OpenVMS use; must be zero.< 4 If this bit is clear (the default), all page sizesB supported by hardware can be used to map resident memoryA sections on Integrity servers. If this bit is set, page? sizes on Integrity servers are limited to the maximumB GH factor available on Alpha systems (512 * )." 5-7 Reserved for future use.4 MMG_CTLFLAGS is an AUTOGEN and DYNAMIC parameter. 2 MOUNTMSG_(D)@ MOUNTMSG controls whether or not the messages that log volumeA m ounts appear on the operator's terminal and in the operator'sD log. The default value of 0 disables reporting of these messages.B This parameter does not control the messages generated by mount assistance requests.# MOUNTMSG is a DYNAMIC parameter. 2 MPDEV_AFB_INTVL> (Alpha and Integrity servers) MPDEV_AFB_INTVL specifies theA automatic failback interval in seconds. The automatic failbackD interval is the minimum number of seconds that must elapse before> the system attempts another failback from an MSCP path to a" direct path on the same device.C MPDEV_POLLER must be set to ON to enable automatic failback. YouA can disable automatic failback without disabling the poller by< setting MPDEV_AFB_INTVL to 0. The default is 300 seconds. 2 MPDEV_D*> (Alpha and Integrity servers) MPDEV_D1 through MPDEV_D4 are, reserved for use by the operating system. 2 MPDEV_ENABLEC (Alpha and Integrity servers) MPDEV_ENABLE enables the formation@ of multipath sets when set to ON (1). If MPDEV_ENABLE is setB to OFF (0), the formation of additional multipath sets and theA addition of new paths to existing multipath sets are disabled.D However, existing multipath sets remain in effect. The default is ON.D MPDEV_REMOTE and MPDEV_AFB_INTVL have no effect when MPDEV_ENABLE is set to OFF. 2 MPDEV_LCRETRIESD (Alpha and Integrity servers) MPDEV_LCRETRIES controls the numberA of times the system retri es the direct paths to the controllerA that the logical unit is online to, before moving on to directB paths to the other controller, or to an MSCP served path to theD device. The valid range for retries is 1 through 256. The default is 1. 2 MPDEV_POLLER@ (Alpha and Integrity servers) MPDEV_POLLER enables polling ofB the paths to multipath set members when set to ON (1). Polling@ allows early detection of errors on inactive paths. If a pathC becomes unavailable or returns to service, the system manager isB notified with an OPCOM message. When set to OFF (0), multipathC polling is disabled. The default is ON. Note that this parameter; must be set to ON to use the automatic failback feature. 2 MPDEV_REMOTEA (Alpha and Integrity servers) MPDEV_REMOTE enables MSCP servedA paths to become members of a multipath set when set to ON (1).D When set to OFF (0), only local paths to a SCSI or Fibre Channel@ device is used in the formati on of additional multipath sets.B However, setting this parameter to OFF does not have any effect5 on existing multipath sets that have remote paths.@ To use multipath failover to a served path, MPDEV_REMOTE must> be enabled on all systems that have direct access to shared@ SCSI/Fibre Channel devices. The first release to provide this? feature is OpenVMS Alpha Version 7.3-1. Therefore, all nodesA on which MPDEV_REMOTE is enabled must be running OpenVMS Alpha Version 7.3-1 (or later).A If MPDEV_ENABLE is set to OFF (0), the setting of MPDEV_REMOTEC has no effect because the addition of all new paths to multipath' sets is disabled. The default is ON. 2 MPW_HILIMITC MPW_HILIMIT sets an upper limit for the modified-page list. WhenD the list accumulates the number of pages specified by this limit,B writing of the list begins. The pages that are written are then% transferred to the free-page list.D If MPW_HILIMIT is too low, excessive page faulting can occur fromC the page file. If it is too high, too many physical pages can be& consumed by the modified-page list.? If you increase MPW_HILIMIT, you might also need to increase9 MPW_WAITLIMIT. Note that if MPW_WAITLIMIT is less than@ MPW_HILIMIT, a system deadlock occurs. The values for the two parameters are usually equal.2 MPW_HILIMIT has the AUTOGEN and GEN attributes. 2 MPW_IOLIMIT> MPW_IOLIMIT specifies the number of outstanding I/Os to the modified-page writer.D On Alpha and Integrity servers, MPW_IOLIMIT is an AUTOGEN-altered parameter. 2 MPW_LOLIMITB MPW_LOLIMIT sets a lower limit for the modified-page list. When@ writing of the list causes the number of pages on the list to. drop to or below this limit, writing stops.C MPW_LOLIMIT ensures that a certain number of pages are available> on the modified-page list for page faults. If the number isA too small, the caching effectiveness of the m odified-page list> is reduced. If it is too high, less memory is available for3 processes, so that swap (and page) may increase.2 MPW_LOLIMIT has the AUTOGEN and GEN attributes. 2 MPW_LOWAITLIMIT@ MPW_LOWAITLIMIT specifies the threshold at which processes in> the miscellaneous wait state MPWBUSY are allowed to resume.C MPW_LOWAITLIMIT increases system performance for fast processors? with large memories by reducing the amount of time processes# spend in the MPWBUSY wait state.: MPW_LOWAITLIMIT has the AUTOGEN and DYNAMIC attributes. 2 MPW_PRIO? MPW_PRIO sets the priority of I/O transfers initiated by theC modified page writer. The maximum value is 31, the minimum is 0, and the default is 4.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 MPW_THRESH@ MPW_THRESH sets a lower bound of pages that must exist on theD modified-page l ist before the swapper writes this list to acquire? free pages. If this requirement is met, the swapper tries toB write the modified-page list rather than taking pages away from or swapping out a process.? MPW_THRESH has the DYNAMIC attribute. On Alpha and Integrity4 servers, MPW_THRESH is also an AUTOGEN parameter. 2 MPW_WAITLIMITC MPW_WAITLIMIT sets the number of pages on the modified-page listB that causes a process to wait until the next time the modified-B p age writer writes the modified list. This parameter limits theB rate at which any single process can produce modified pages. IfA this value is less than MPW_HILIMIT, a system deadlock occurs.A The value for this parameter is normally equal to MPW_HILIMIT.8 MPW_WAITLIMIT has the AUTOGEN and DYNAMIC attributes. 2 MPW_WRTCLUSTERC MPW_WRTCLUSTER sets the number of pages to be written during one@ I/O operation from the modified-page list to the page file or@ a section fil e. The actual size of the cluster may be limited? by the number of pages available for the I/O operation. ThisB parameter can range in value from 16 to 120, in multiples of 8.D Each page in the cluster requires 6 bytes of permanently resident memory.? If MPW_WRTCLUSTER is too small, it takes many I/O operationsB to empty the modified-page list. If MPW_WRTCLUSTER is too large@ for the speed of the disk that holds the page file, other I/O; operations are held up for the modified-page list write.C On Alpha and Integrity servers, the MPW_WRTCLUSTER default valueC is 64 8192-byte pages; its maximum value is 512 8192-byte pages;/ and its minimum value is 16 8192-byte pages.5 MPW_WRTCLUSTER has the AUTOGEN and GEN attributes. 2 MSCP_BUFFERD This buffer area is the space used by the server to transfer data* between client systems and local disks.C On Alpha and Integrity servers, MSCP_BUFFER specifies the number@ of pagelets to be allocated to the MSCP server's local buffer area.4 MSCP_BUFFER is an AUTOGEN and FEEDBACK parameter. 2 MSCP_CMD_TMOC MSCP_CMD_TMO is the time in seconds that the OpenVMS MSCP server= uses to detect MSCP command timeouts. The MSCP Server must? complete the command within a built-in time of approximately; 40 seconds plus the value of the MSCP_CMD_TMO parameter.> The MSCP_CMD_TMO default value of 0 is normally adequate. A@ value of 0 provides the same behavior as in previous releasesD of OpenVMS (which did not have an MSCP_CMD_TMO system parameter).@ A nonzero setting increases the amount of time before an MSCP command times out.> If command timeout errors are being logged on client nodes,> setting the parameter to a nonzero value on OpenVMS servers> may reduce the number of errors logged. As the value of theE MSCP_CMD_TMO increases, the number of client MSCP command timeoutsB will decrease, at the cost of increased time to detect a faulty) MSCP controller or MSCP-served device.D If you need to decrease the number of command timeout errors, VSID recommends that you set an initial value of 60. If timeout errorsC continue to be logged, you can increase this value in increments of 20 seconds.' MSCP_CMD_TMO is a DYNAMIC parameter. 2 MSCP_CREDITS@ MSCP_CREDITS specifies the number of outstanding I/O requests- that can be active from one client system.> The default value is currently 32. Unless a system has veryA constrained memory available, VSI recommends that these values not be increased. 2 MSCP_LOADD MSCP_LOAD controls the loading of the MSCP server during a system- boot. Specify one of the following values: Value DescriptionA 0 Do not load the MSCP server. This is the default value.B 1 Load the MSCP server and serve disks as specified by the# MSCP_SERVE_ALL parameter.' MSCP_LOAD has the AUTOGEN attribute. 2 MSCP_SERVE_ALL@ MSCP_SERVE_ALL is a bit mask that controls disk serving in anA OpenVMS Cluster. A disk is served regardless of its allocation' class unless bit 3 has a value of 1.; Starting with OpenVMS Version 7.2, the serving types areA implemented as a bit mask. To specify the type of serving yourA system will perform, locate the type you want in the followingA table and specify its value. For some systems, you may want toA specify two serving types, such as se rving the system disk andA serving locally attached disks. To specify such a combination,4 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 disksC is restricted to serving all disks except those whose allocationA class does not match the system's node allocation class (priorD to Version 7.2). To specify this type of serving, use the value 9 (which sets bit 0 and bit 3).D The following table describes the serving type controlled by each bit and its decimal value: Bit and Value When Set Description@ Bit 0 (1) Serve all available disks (locally attached and> those connected to HSx and DSSI controllers).? Disks with allocation classes that differ fromD the system's allocation class (set by the ALLOCLASS@ parameter) are also served if bit 3 is not set.A Bit 1 (2) Serve locally attached (non-HSx and DSSI) disks.D Bit 2 (4) Serve the system disk. This is the default setting.B This setting is important when other nodes in the@ cluster rely on this system being able to serve? its system disk. This setting prevents obscureA contention problems that can occur when a systemA attempts to complete I/O to a remote system disk) whose system has failed.C Bit 3 (8) Restrict the serving specified by bit 0. All disksA except those with allocation classes that differ? from the system's allocation class (set by the1 ALLOCLASS parameter) are served.B This is pre-Version 7.2 behavior. If your clusterC includes systems running OpenVMS 7.1-x or earlier,D and you want to serve all available disks, you mustB  specify 9, the result of setting this bit and bit 0.D Although the serving types are now implemented as a bit mask, theD values of 0, 1, and 2, specified by bit 0 and bit 1, retain their original meanings:B 0 - Do not serve any disks (the default for earlier versions of OpenVMS).$ 1 - Serve all available disks.C 2 - Serve only locally attached (non-HSx and non-DSSI) disks.< If the MSCP_LOAD system parameter is 0, MSCP_SERVE_ALL is ignored. 2 MULTIPROCESSING5 MULTIPROCESSING controls the loading of the system synchronization image.' Specify one of the following values: Value Description8 0 Load the uniprocessing synchronization image+ SYSTEM_SYNCHRONIZATION_UNI.EXE.8 1 If the CPU type is capable of SMP and two or9 more CPUs are present on the system, load the9 full-checking multiprocessing synchronization8 image SYST EM_SYNCHRONIZATION.EXE. Otherwise,8 load the uniprocessing synchronization image+ SYSTEM_SYNCHRONIZATION_UNI.EXE.1 2 Always load the full-checking version< SYSTEM_SYNCHRONIZATION.EXE, regardless of system. configuration or CPU availability.= 3 If the CPU type is capable of SMP and two or more> CPUs are present on the system, load the optimized. streamlined multiprocessing image:< o On Alph a and Integrity servers, this image is. SYSTEM_SYNCHRONIZATION_MIN.EXE.C Otherwise, load the uniprocessing synchronization imageC SYSTEM_SYNCHRONIZATION_UNI.EXE. The default value is 3.= 4 Always load the streamlined multiprocessing image@ SYSTEM_SYNCHRONIZATION_MIN.EXE, regardless of system. configuration or CPU availability.D Setting the SYSTEM_CHECK parameter to 1 has the effect of setting MULTIPROCESSING to 2. 2 MULTITHREAD: MULTITHREAD controls the availability of kernel threads2 functions. Specify one of the following values: Value DescriptionC 0 Both Thread Manager upcalls and the creation of9 multiple kernel threads are disabled.D 1 Thread Manager upcalls are enabled; the creation; of multiple kernel threads is disabled.@ 2-256 (Alpha Both Thread Manager upcalls and the creation? and Integrity of multiple kernel threads are enabled. TheB servers) number specified represents the maximum number? of kernel threads that can be created for a# single process., The maximum value for MULTITHREAD is 256.3 MULTITHREAD is an AUTOGEN and DYNAMIC parameter. 2 MVSUPMSG_INTVL< (Alpha and Integrity servers) The system suppresses mount= verification start and end messages for fibre channel disk? devices i f mount verification completes on the first attemptC and if mount verification does not occur too often. MVSUPMSG_NUM+ and this parameter establish this limit.B The system issues a mount verification message after a sequenceA of MVSUPMSG_NUM mount verifications have gone unannounced on a@ specific fibre channel disk device within a span of MVSUPMSG_ INTVL seconds.A If this parameter is zero, all mount verification messages are announced.) MVSUPMSG_INTVL is a D YNAMIC parameter. 2 MVSUPMSG_NUM< (Alpha and Integrity servers) The system suppresses mount= verification start and end messages for fibre channel diskC devices if mount verification completes on the first attempt andA if mount verification does not occur too often. MVSUPMSG_INTVL+ and this parameter establish this limit.B The system issues a mount verification message after a sequenceA of MVSUPMSG_NUM mount verifications have gone unannounced on a@ specific fibre channel disk device within a span of MVSUPMSG_ INTVL seconds.A If this parameter is zero, all mount verification messages are announced.' MVSUPMSG_NUM is a DYNAMIC parameter. 2 MVTIMEOUT= MVTIMEOUT is the time in seconds that a mount verification9 attempt continues on a given disk volume. If the mountA verification does not recover the volume within that time, theA I/O operations outstanding to the volume terminate abnormally.D MVTIMEOUT is a DYNAMIC parameter. On Alpha and Integrity servers,* MVTIMEOUT is also an AUTOGEN parameter. 2 NET_CALLOUTSC NET_CALLOUTS is normally set to 0. A value of 255 indicates thatB no attempt is to be made to assign a new proxy connection to anB active server, but that a new process must be started to invokeD the installation security policy callout modules in LOGINOUT.EXE.4 Values 1 through 254 are reserved for future use.' NET_CALLOUTS is a DYNAMIC parameter. 2 NISCS_CONV_BOOT< NISCS_CONV_BOOT controls whether a conversational boot is@ permitted during a remote system boot. The default value of 09 specifies that conversational boots are not permitted. 2 NISCS_LOAD_PEA0C NISCS_LOAD_PEA0 controls whether the NI-SCS port driver PEDRIVERD is loaded during system boot. The default of 0 specifies that the PEDRIVER is not loaded. 2 NISCS_MAX_PKTSZA This parameter specifies an upper limit on the size, in bytes,C of the user data area in the largest packet sent by NISCA on any local area network (LAN).A NISCS_MAX_PKTSZ allows the system manager to change the packet@ size used for cluster communications on network communication< paths. PEDRIVER automatically allocates memory to support@ the largest packet size that is usable by any virtual circuitD connected to the system up to the limit set by this parameter. OnD Alpha and Integrity servers, to optimize performance, the defaultC value is the larges t packet size currently supported by OpenVMS.A PEDRIVER uses NISCS_MAX_PKTSZ to compute the maximum amount of& data to transmit in any LAN packet:9 LAN packet size <= LAN header (padded Ethernet format)' + NISCS_MAX_PKTSZ= + NISCS checksum (only if data checking3 is enabled)& + LAN CRC or FCSA The actual packet size automatically used by PEDRIVER might beB smaller than the NISCS_MAX_PKTSZ limit for any of the following reasons:B o On a per-LAN path basis, if PEdriver determines that the LAN@ path between two nodes, including the local and remote LAN? adapters and intervening LAN equipment, can only convey a lesser size.? In other words, only nodes with large-packet LAN adapters@ connected end-to-end by large-packet LAN equipment can useD large packets. Nodes connected to large-packet LANs but havingC an end-t o-end path that involves an Ethernet segment restrict= packet size to that of an Ethernet packet (1498 bytes).; o For performance reasons, PEDRIVER might further limit? the upper bound on packet size so that the packets can be; allocated from a lookaside list in the nonpaged pool.D The actual memory allocation includes the required data structureD overhead used by PEDRIVER and the LAN drivers, in addition to the actual LAN packet size.> The following table shows the minimum NISCS_MAX_PKTSZ valueA required to use the maximum packet size supported by specified LAN types:: Type of LAN Minimum Value for NISCS_MAX_PKTSZ Ethernet 14982 FDDI 4382 (before Version 7.3)5 4396 (Version 7.3 and later) Gigabit Ethernet 8192 ATM 7606> Note that the maximum packet size for some Gigabit Ethernet? adapters is larger than the maximum value of NISCS_MAX_PKTSZA (8192 bytes). See the LAN_FLAGS parameter for a description ofA how to enable jumbo frames on Gigabit Ethernet-that is, packet. sizes larger than those noted for Ethernet.@ On Alpha and Integrity servers, NISCS_MAX_PKTSZ is an AUTOGEN parameter. 2 NISCS_PORT_SERVA NISCS_PORT_SERV provides flag bits for PEDRIVER port services:= o Setting bits 0 and 1 (hex bitmask value 3) enables data checking.B o Setting bit 2 (hex bitmask  value 4) enables data compression9 on all virtual channels (VCs) to nodes that support compression.2 The remaining bits are reserved for future use.= Starting with OpenVMS Version 7.3-1, you can use the SCACPB command SET VC/CHECKSUMMING to specify data checking on the VCsC to certain nodes. You can do this on a running system. (For moreE information, see the SCACP documentation in the VSI OpenVMS System) Management Utilities Reference Manual.@ Starting with OpenVMS Version 8.3, you can also use the SCACP@ command SET VC/COMPRESSION to specify data compression on theB on the VCs to certain nodes. You can use SCACP to enable eitherB data checking or data compression on a running system. (See the? SCACP documentation in the the VSI OpenVMS System ManagementA Utilities Reference Manual for more information. Also startingA with OpenVMS Version 8.3, the NISCS_PORT_SERV system parameterA is dynamic, that is, changing the setting of th is parameter no@ longer requires a reboot. Furthermore, this parameter appliesB to all virtual circuits between the node on which it is set and other nodes in the cluster.: NISCS_PORT_SERV has the DYNAMIC and AUTOGEN attributes. 2 NOAUTOCONFIG> NOAUTOCONFIG controls whether all devices are automaticallyD configured when the system boots. The default value of 0 sets theB system to automatically configure all devices. Set NOAUTOCONFIGA to 1 (no automatic configuration) only for debugging purposes.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so.' NOAUTOCONFIG is a DYNAMIC parameter. 2 NOCLUSTER? NOCLUSTER controls whether page read clustering is inhibited? when the system boots. Set NOCLUSTER to 1 (inhibit page read+ clustering) only for debugging purposes.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 NOPGFLSWP; If enabled, NOPGFLSWP disables swapping into page files.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 NPAGECALCA NPAGECALC controls whether the system automatically calculates0 the initial size for nonpaged dynamic memory.? VSI sets the default value of NPAGECALC to 1 only during the@ initial boot after an ins tallation or upgrade. When the valueD of NPAGECALC is 1, the system calculates an initial value for theD NPAGEVIR and NPAGEDYN system parameters. This calculated value is8 based on the amount of physical memory in the system.D NPAGECALC's calculations do not reduce the values of NPAGEVIR andA NPAGEDYN from the values you see or set at the SYSBOOT prompt.@ However, NPAGECALC's calculation might increase these values.@ AUTOGEN sets NPAGECALC to 0. NPAGECALC should always remain  0D after AUTOGEN has determined more refined values for the NPAGEDYN" and NPAGEVIR system parameters. 2 NPAGEDYN@ NPAGEDYN sets the size of the nonpaged dynamic pool in bytes.> This figure is rounded down to an integral number of pages.@ NPAGEDYN establishes the initial setting of the nonpaged pool8 size, but the pool size can be increased dynamically.@ To set a value for this parameter, use AUTOGEN initially, and> then monitor the amount of space actually used with  the DCL! command SHOW MEMORY/POOL/FULL.? For the benefit of OpenVMS VAX systems with limited physicalC memory, AUTOGEN logs a warning message in its report if NPAGEDYNB exceeds 10 percent of physical memory or if NPAGEVIR exceeds 33 percent of physical memory.? AUTOGEN also limits its own calculated value for NPAGEDYN toB 20 percent of physical memory and limits NPAGEVIR to 50 percent? of physical memory. These calculated values are adequate for> most workstations  and systems with 16 or fewer megabytes ofC physical memory. If your system requires a larger value, you canB override the AUTOGEN calculated values by setting higher values in MODPARAMS.DAT.= NPAGEDYN has AUTOGEN, FEEDBACK, GEN, and MAJOR attributes. 2 NPAGERADD (Alpha and Integrity servers) NPAGERAD specifies the total number@ of bytes of nonpaged pool that will be allocated for ResourceA Affinity Domains (RADs) other than the base RAD. For platforms? that have  no RADs, NPAGERAD is ignored. Notice that NPAGEDYN< specifies the total amount of nonpaged pool for all RADs.@ Also notice that the OpenVMS system might round the specified? values higher to an even number of pages for each RAD, whichB prevents the base RAD from having too little nonpaged pool. For@ example, if the hardware is an AlphaServer GS160 with 4 RADs: NPAGEDYN = 6291456 bytes NPAGERAD = 2097152 bytes8 In this case, the OpenVMS system allocates a total ofB  approximately 6,291,456 bytes of nonpaged pool. Of this amount,A the system divides 2,097,152 bytes among the RADs that are not@ the base RAD. The system then assigns the remaining 4,194,304 bytes to the base RAD.& NOTE> The system actually rounds up to an even number of pages@ on each RAD. In addition, the base RAD is never assigned a@ value less than the smaller of the value of NPAGEDYN and 4 megabytes.B On AlphaServe r GS series processors on OpenVMS systems prior toD Version 7.3-1, system managers frequently saw pool expansion thatA increasing NPAGEDYN did not reduce. This problem was caused by. leaving NPAGERAD at its default value of 0.? Starting with OpenVMS Version 7.3-1, when NPAGERAD is 0 (theC default), the system calculates a value to use for NPAGERAD with the following formula:$ Base RAD memory& NPAGEDYN * (1- --------------- )" Total memoryD This calculation gives more pool to the non-base RADs than before: and, therefore, reduces the expansion of non-base RADs." NPAGERAD has the GEN attribute. 2 NPAGEVIR= NPAGEVIR defines the maximum size to which NPAGEDYN can be> increased. If this value is too small, the system can hang.? If NPAGEVIR is too large, the result is a penalty of 4 bytes@ per extra page on VAX and 8 bytes per extra page on Alpha and Integrity servers.? For the benef it of OpenVMS VAX systems with limited physicalC memory, AUTOGEN logs a warning message in its report if NPAGEDYNB exceeds 10 percent of physical memory or if NPAGEVIR exceeds 33 percent of physical memory.B AUTOGEN also limits its own calculated value for NPAGEDYN to 20@ percent of physical memory, and limits NPAGEVIR to 50 percent? of physical memory. These calculated values are adequate for> most workstations and systems with 16 or fewer megabytes ofC physical memory. If your system requires a larger value, you canB override the AUTOGEN calculated values by setting higher values in MODPARAMS.DAT.+ NPAGEVIR has AUTOGEN and GEN attributes. 2 NPAG_AGGRESSIVEB Beginning with OpenVMS Version 8.2, the default values of NPAG_? AGGRESSIVE and NPAG_GENTLE are 100. A value of 100 turns offD both gentle and aggressive reclamation of nonpaged pool lookasideB lists. In many cases, when pool reclamation moves small packetsA from the lookasid e lists back to the variable list, the resultD is fragmentation of the variable list. This fragmentation appearsD as many small packets at the front of the variable list and a few( large packets at the end of the list.A When an allocation occurs for a packet that is larger than any> of the lookaside lists, the system must find a large enoughC packet on the variable list. When heavily fragmented, the entire> variable list often must be searched to find a large enoughC packet. Because the variable list is kept in address order, whenB a large packet is deallocated, the entire list must be searched" again to deallocate the packet.= Under these conditions, system performance can be severelyC degraded. For this reason, VSI recommends that you turn off poolC reclamation but keep both NPAG_AGGRESSIVE and NPAG_GENTLE system parameters set to 100.* NPAG_AGGRESSIVE is a DYNAMIC parameter. 2 NPAG_BAP_MAXB (Alpha and Integrity servers) NPAG_BAP_MAX is the size in bytesB of the bus addressable pool (BAP) that the system creates under normal circumstances. See also NPAG_BAP_MIN. 2 NPAG_BAP_MAX_PA? (Alpha and Integrity servers) NPAG_BAP_MAX_PA is the highestC physical address in megabytes that is allowed in bus addressable pool (BAP). 2 NPAG_BAP_MINB (Alpha and Integrity servers) NPAG_BAP_MIN is the size in bytesA of the bus addressable pool (BAP) that the system creates when. memory resources are unusually constrained. 2 NPAG_BAP_MIN_PA> (Alpha and Integrity servers) NPAG_BAP_MIN_PA specifies the> lowest physical address in megabytes that is allowed in bus addressable pool (BAP). 2 NPAG_GENTLED Beginning with Version 8.2, the default values of NPAG_AGGRESSIVE@ and NPAG_GENTLE are 100. A value of 100 turns off both gentle? and aggressive reclamation of nonpaged pool lookaside lists.@ In many cases, when pool reclamation moves small packets from ? the lookaside lists back to the variable list, the result isA fragmentation of the variable list. This fragmentation appearsD as many small packets at the front of the variable list and a few( large packets at the end of the list.A When an allocation occurs for a packet that is larger than any> of the lookaside lists, the system must find a large enoughC packet on the variable list. When heavily fragmented, the entire> variable list often must be searched to find a large enoughC packet. Because the variable list is kept in address order, whenB a large packet is deallocated, the entire list must be searched" again to deallocate the packet.= Under these conditions, system performance can be severelyC degraded. For this reason, VSI recommends that you turn off poolC reclamation but keep both NPAG_AGGRESSIVE and NPAG_GENTLE system parameters set to 100.& NPAG_GENTLE is a DYNAMIC parameter. 2 NPAG_INTERVAL; NPAG_INTERVAL is the number of seconds between passes of$ nonpaged-pool gentle reclamation.( NPAG_INTERVAL is a DYNAMIC parameter. 2 NPAG_RING_SIZE> NPAG_RING_SIZE represents the number of entries in the ring buffer. 2 PAGED_LAL_SIZEA PAGED_LAL_SIZE sets the maximum size, in bytes, to use for theB page dynamic pool lookaside lists. Use of these lookaside listsD can reduce paged dynamic pool variable freelist fragmentation and> improve paged pool allocation and deallocation performance.D By default, PAGED_LAL_SIZE is set to 0, which disables the use of* the paged dynamic pool lookaside lists.= For environments experiencing paged pool variable freelist@ fragmentation a modest PAGED_LAL_SIZE, 512, has been adequateA to improve paged pool performance and reduce fragmentation. IfA this parameter is made large and later decreased in size, someD paged pool packets can be left unused until the parameter is madeC larger again, or the lookaside lists are reclaimed from due to aC paged pool shortage. The paged dynamic pool lookaside lists willC not occupy more than three-quarters of the available paged pool.9 PAGED_LAL_SIZE has DYNAMIC, GEN, and MAJOR attributes. 2 PAGFILCNTD On Alpha and Integrity servers, beginning in OpenVMS Version 7.3, this parameter is obsolete.2 PAGFILCNT has the GEN attribute on VAX systems. 2 PAGTBLPFCC PAGTBLPFC specifies (in pages) the maximum number of page tables; to read to satisfy a fault for a nonresident page table.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 PAMAXPORTC PAMAXPORT specifies the maximum port number to be polled on eachC CI and DSSI. The CI and DSSI port drivers poll to discover newlyD initialized ports or the absence/failure of previously responding remote ports.= A system does not detect the existence of ports whose por tA numbers are higher than this parameter's value. Thus, set thisD parameter to a value that is equal to or greater than the highestD port number being used on any CI or DSSI connected to the system.@ You can decrease this parameter to reduce polling activity ifC the hardware configuration has fewer than 16 ports. For example,? if the CI or DSSI with the largest configuration has a totalA of 5 ports assigned to port numbers 0 through 4, you could set PAMAXPORT to 4.@ If CI or DSSI devices are not configured on your system, this parameter is ignored.D The default for this parameter is 15 (poll for all possible portsC 0 through 15). VSI recommends that you set this parameter to the' same value on each cluster computer.$ PAMAXPORT is a DYNAMIC parameter. 2 PANOPOLLC Disables CI and DSSI polling for ports if set to 1. (The defaultA is 0.) When PANOPOLL is set, a computer does not discover thatC another computer has shut dow n or powered down promptly and doesA not discover a new computer that has booted. This parameter is@ useful when you want to bring up a computer detached from the- rest of the cluster for checkout purposes.C PANOPOLL is functionally equivalent to uncabling the system fromC the DSSI or star coupler. This parameter does not affect OpenVMS! Cluster communications by LAN.? The default value of 0 is the normal setting and is requiredA if you are booting from an HSC controller or if your system isD joining an OpenVMS Cluster. This parameter is ignored if no CI or. DSSI devices are configured on your system.# PANOPOLL is a DYNAMIC parameter. 2 PANUMPOLL> PANUMPOLL establishes the number of CI and DSSI ports to beA polled each polling interval. The normal setting for PANUMPOLL is 16.B On systems with less powerful CPUs, the parameter may be usefulB in applications sensitive to the amount of contiguous time thatD the system spends at IPL 8. Reducing PANUMPOLL reduces the amount= of time spent at IPL 8 during each polling interval, while@ increasing the number of polling intervals needed to discover new or failed ports.@ If CI or DSSI devices are not configured on your system, this parameter is ignored.$ PANUMPOLL is a DYNAMIC parameter. 2 PAPOLLINTERVALA Specifies, in seconds, the polling interval the CI port driverB uses to poll for a newly booted computer, a broken port-to-port0   virtual circuit, or a failed remote computer.C This parameter trades polling overhead against quick response toD virtual circuit failures. VSI recommends that you use the default value for this parameter.B VSI recommends that you set this parameter to the same value on each cluster computer.) PAPOLLINTERVAL is a DYNAMIC parameter. 2 PAPOOLINTERVAL? Specifies, in seconds, the interval at which the port driverB checks available nonpaged pool after a pool all!ocation failure.D This parameter trades faster response to pool allocation failuresB against increased polling overhead. VSI recommends that you use( the default value for this parameter.@ If CI or DSSI devices are not configured on your system, this parameter is ignored.* PAPOOLLINTERVAL is a DYNAMIC parameter. 2 PASANITYC PASANITY controls whether the CI and DSSI port sanity timers areD enabled to permit remote systems to detect a system that has beenC hun "g at IPL 8 or above for 100 seconds. It also controls whetherA virtual circuit checking gets enabled on the local system. The8 TIMVCFAIL parameter controls the time (1-99 seconds).A PASANITY is normally set to 1 and should be set to 0 only when@ you are debugging with XDELTA or planning to halt the CPU for" periods of 100 seconds or more.> PASANITY is only semidynamic. A new value of PASANITY takes7 effect on the next CI or DSSI port reinitialization.@ If CI or DSSI d#evices are not configured on your system, this parameter is ignored. 2 PASTDGBUFD The number of datagram receive buffers to queue initially for theC cluster port driver's configuration poller. The initial value is/ expanded during system operation, if needed.0 Memory Channel devices ignore this parameter.% PASTDGBUF is an AUTOGEN parameter. 2 PASTIMOUT= The basic interval at which the CI port driver wakes up toC perform time-based bookkeeping operations$. It is also the period> after which a timeout is declared if no response to a start( handshake datagram has been received.@ If CI or DSSI devices are not configured on your system, this parameter is ignored./ The default value should always be adequate.$ PASTIMOUT is a DYNAMIC parameter. 2 PE1-6D PE1, PE2, PE3, PE4, PE5, PE6 are reserved for VSI use only. TheseD parameters are for cluster algorithms and their usages can changeC from release to release. VSI %recommends using the default values for these special parameters. 2 PFCDEFAULT? On Alpha and Integrity servers during execution of programs,= PFCDEFAULT controls the number of image pagelets read fromB disk per I/O operation when a page fault occurs. The PFCDEFAULTA maximum default value is 2032 512-byte pagelets (127 8192-byte% Alpha and Integrity server pages).? The read I/O operations can take place from an image file orA from the page file. The actual size & of the cluster can be lessC than PFCDEFAULT, depending on the size of image sections and the pattern of page references.C The value should not be greater than one-fourth the default sizeA of the average working set to prevent a single page fault fromA displacing a major portion of a working set. Too large a value@ for PFCDEFAULT can hurt system performance. PFCDEFAULT can beC overridden on an image-by-image basis with the CLUSTER option of the OpenVMS linker.5 P 'FCDEFAULT has the AUTOGEN and DYNAMIC attributes. 2 PFN_COLOR_COUNT> (Alpha and Integrity servers) PFN_COLOR_COUNT specifies theB number of buckets (colors) into which all members of the zeroedC page list and all unencumbered members of the free page list areD sorted. OpenVMS Alpha systems might derive a preferred page color@ from a request to map a given virtual page and attempt to mapB that virtual page to a PFN of matching "color." This results inC less variance in wh (ich cache blocks are used when accessing thatB page. This might or might not improve performance, depending on the application.A This special parameter is use by VSI and is subject to change.E Do not change this parameter unless VSI recommends that you do so.C If you increase this parameter, you must also increase the ZERO_ LIST_HI system parameter. 2 PFRATH@ PFRATH specifies the page fault rate above which the limit of@ a working set is automatically increase )d. The unit of measureA is the number of faults per 10 seconds of processor time. At aB setting of 120, for example, the system automatically increasesC the limit of a working set if it is faulting more than 120 pagesB per 10 seconds. Decreasing the value of this parameter tends to@ increase the limits of the working sets, while increasing its( value tends to decrease their limits.> On Alpha and Integrity servers, the default value is 8 page faults every 10 seconds.< * PFRATH has the DYNAMIC and MAJOR attributes. On Alpha andB Integrity servers, PFRATH also is an AUTOGEN-altered parameter. 2 PFRATL@ PFRATL specifies the page fault rate below which the limit of@ a working set is automatically decreased. The unit of measureA is the number of faults per 10 seconds of processor time. At aD setting of 1, for example, the system automatically decreases theB limit of a working set if it is faulting less than 1 page every 10 seconds.? I +ncreasing the value of this parameter tends to decrease theB limits of the working sets, while decreasing its value tends to increase their limits.9 PFRATL has the AUTOGEN, DYNAMIC, and MAJOR attributes. 2 PHYSICAL_MEMORY> (Alpha and Integrity servers) PHYSICAL_MEMORY specifies theC amount of physical memory available for use. The default settingD is -1, which equates to all memory in the system. Decreasing this@ parameter allows you to test smaller configurations o ,f memory* without having to remove memory boards.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so.D Because of hardware configuration requirements on the AlphaServer@ ES47/ES80/GS1280 systems, VSI does not recommend altering theC setting of the system parameter PHYSICAL_MEMORY from its default@ setting of -1. Artificially reducing the amount of memory can2 produce unpredictable results on th-ese systems.+ PHYSICAL_MEMORY is an AUTOGEN parameter.) PHYSICALPAGES is an AUTOGEN parameter. 2 PIOPAGES@ PIOPAGES specifies the size of the process I/O segment, which= holds data structures and buffer pool space for RMS to useB when it handles I/O that involves process-permanent files. OnceD PIOPAGES is reset in SYSGEN, any new process receives the changed value.A Beginning with OpenVMS Version 7.2, the default value has been@ raised to 575. The settin .g has been raised to accommodate theB increased demands for process-permanent memory that result from: changes made to RMS file-naming parsing in Version 7.2.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so.0 PIOPAGES is an AUTOGEN and DYNAMIC parameter. 2 PIXSCANC PIXSCAN specifies the number of process index slots scanned eachB second for computable or computable-outswapped processes./ These? processes receive an automatic priority boost for 1 quantum,D unless the priority of the currently executing process is greaterC than 15. The priority boost is done to avoid potential deadlocks on the system.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so./ PIXSCAN is an AUTOGEN and DYNAMIC parameter. 2 POOLCHECKD This special parameter is use by VSI and is subject to ch 0ange. DoB not change this parameter unless VSI recommends that you do so.= POOLCHECK is used to investigate frequent and inexplicableA failures in a system. When POOLCHECK is enabled, pool-checking> routines execute whenever pool is deallocated or allocated.? Two loadable forms of SYSTEM_PRIMITIVES.EXE are available at@ boot time. The default image, which contains no pool-checking? code and no statistics maintenance, is loaded when POOLCHECK@ is set to zero. When POOLCH 1ECK is set to a nonzero value, theC monitoring version of SYSTEM_PRIMITIVES.EXE, which contains both< pool-checking code and statistics maintenance, is loaded.D Setting the SYSTEM_CHECK parameter to 1 has the effect of setting> POOLCHECK to %X616400FF. For further information about poolA checking, see the OpenVMS VAX Device Support Manual, (which is archived).A POOLCHECK is a DYNAMIC parameter. However, for a change in itsA value to have any effect, POOLCHECK must be n2on-0 at boot time= (to load the monitoring version of SYSTEM_PRIMITIVES.EXE). 2 POOLPAGING; POOLPAGING enables (1) paging of pageable dynamic pool.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 POWEROFF@ POWEROFF enables or disables software requests to the consoleB firmware to remove power from the system. This parameter shouldA normally be turned ON (1) to allow softw3are to make power-off@ requests. However, POWEROFF can be set to OFF (0) to disable software power-off requests.C If firmware or hardware support for the power-off request is notD implemented, the shut-down procedure will leave the system halted but fully powered.# POWEROFF is a DYNAMIC parameter. 2 PQL_DASTLMB PQL_DASTLM sets the default limit on the number of pending ASTs? for a process created by the Create Process ($CREPRC) system, service or the DC4L command RUN (Process).1 PQL_DASTLM has the DYNAMIC and GEN attributes. 2 PQL_DBIOLM? PQL_DBIOLM sets the default buffered I/O count limit for the? number of outstanding buffered I/O operations permitted to aD process created by the Create Process ($CREPRC) system service or! the DCL command RUN (Process).1 PQL_DBIOLM has the DYNAMIC and GEN attributes. 2 PQL_DBYTLMD PQL_DBYTLM sets the default buffered I/O byte count limit for theA amount of buffere5d space available to a process created by theA Create Process ($CREPRC) system service or the DCL command RUN (Process).1 PQL_DBYTLM has the DYNAMIC and GEN attributes. 2 PQL_DCPULMC PQL_DCPULM sets the default CPU time limit for a process createdD by the Create Process ($CREPRC) system service or the DCL commandC RUN (Process). PQL_DCPULM specifies the time limit in increments of 10 milliseconds.C The default value of 0 imposes no limit on CPU time usage a6nd is2 typically the correct value for this parameter.1 PQL_DCPULM has the DYNAMIC and GEN attributes. 2 PQL_DDIOLM= PQL_DDIOLM sets the default direct I/O limit for a process@ created by the Create Process ($CREPRC) system service or the DCL command RUN (Process).1 PQL_DDIOLM has the DYNAMIC and GEN attributes. 2 PQL_DENQLMB PQL_DENQLM sets the default enqueue limit for a process createdD by the Create Process ($CREPRC) system service or the DCL com7mand RUN (Process).1 PQL_DENQLM has the DYNAMIC and GEN attributes. 2 PQL_DFILLMD PQL_DFILLM sets the default open file limit for a process createdD by the Create Process ($CREPRC) system service or the DCL command RUN (Process).1 PQL_DFILLM has the DYNAMIC and GEN attributes. 2 PQL_DJTQUOTAA PQL_DJTQUOTA sets the default job table byte count quota for aD process created by the Create Process ($CREPRC) system service orC the DCL command RUN (Proc 8ess). PQL_DJTQUOTA specifies the numberA of bytes of paged pool allocated to the job table. The defaultB value is usually adequate, unless a large number of job logical) names or temporary mailboxes are used.' PQL_DJTQUOTA is a DYNAMIC parameter. 2 PQL_DPGFLQUOTA@ PQL_DPGFLQUOTA sets the default page file quota for a processD created by the Create Process ($CREPRC) system service or the DCLC command RUN (Process). VSI recommends that this parameter not be, small9er than the PQL_DWSEXTENT parameter.< PQL_DPGFLQUOTA has the DYNAMIC and GEN attributes. On VAX8 systems, PQL_DPGFLQUOTA is also an AUTOGEN parameter. 2 PQL_DPRCLM= PQL_DPRCLM sets the default subprocess limit for a process@ created by the Create Process ($CREPRC) system service or the DCL command RUN (Process).1 PQL_DPRCLM has the DYNAMIC and GEN attributes. 2 PQL_DTQELMB PQL_DTQELM sets the default number of timer queue entries for aD process created: by the Create Process ($CREPRC) system service or! the DCL command RUN (Process).1 PQL_DTQELM has the DYNAMIC and GEN attributes. 2 PQL_DWSDEFAULTA PQL_DWSDEFAULT sets the default working set size for a processD created by the Create Process ($CREPRC) system service or the DCL command RUN (Process).5 PQL_DWSDEFAULT has the AUTOGEN and GEN attributes. 2 PQL_DWSEXTENTB PQL_DWSEXTENT sets the default working set extent for a processD created by the Crea;te Process ($CREPRC) system service or the DCL command RUN (Process).> PQL_DWSEXTENT has the AUTOGEN, DYNAMIC, and GEN attributes. 2 PQL_DWSQUOTA@ PQL_DWSQUOTA sets the default working set quota for a processD created by the Create Process ($CREPRC) system service or the DCL command RUN (Process).= PQL_DWSQUOTA has the AUTOGEN, DYNAMIC, and GEN attributes. 2 PQL_MASTLMD PQL_MASTLM sets a minimum limit on the number of pending ASTs forC a process creat<ed by the Create Process ($CREPRC) system service$ or the DCL command RUN (Process).1 PQL_MASTLM has the DYNAMIC and GEN attributes. 2 PQL_MBIOLM? PQL_MBIOLM sets the minimum buffered I/O limit for a processD created by the Create Process ($CREPRC) system service or the DCL command RUN (Process).1 PQL_MBIOLM has the DYNAMIC and GEN attributes. 2 PQL_MBYTLMD PQL_MBYTLM sets the minimum buffered I/O byte limit for a processD created by the Create Proce=ss ($CREPRC) system service or the DCL command RUN (Process).1 PQL_MBYTLM has the DYNAMIC and GEN attributes. 2 PQL_MCPULM> PQL_MCPULM sets the minimum CPU time limit in increments of> 10 milliseconds for a process created by the Create Process= ($CREPRC) system service or the DCL command RUN (Process).1 PQL_MCPULM has the DYNAMIC and GEN attributes. 2 PQL_MDIOLM= PQL_MDIOLM sets the minimum direct I/O limit for a process@ created by the Create Proce>ss ($CREPRC) system service or the DCL command RUN (Process).1 PQL_MDIOLM has the DYNAMIC and GEN attributes. 2 PQL_MENQLMD PQL_MENQLM sets the minimum limit on the number of locks that canC be queued at one time by a process created by the Create Process= ($CREPRC) system service or the DCL command RUN (Process).1 PQL_MENQLM has the DYNAMIC and GEN attributes. 2 PQL_MFILLMD PQL_MFILLM sets the minimum open file limit for a process createdD by the Cr?eate Process ($CREPRC) system service or the DCL command RUN (Process).1 PQL_MFILLM has the DYNAMIC and GEN attributes. 2 PQL_MJTQUOTAA PQL_MJTQUOTA sets the minimum job table byte count quota for aD process created by the Create Process ($CREPRC) system service or! the DCL command RUN (Process).' PQL_MJTQUOTA is a DYNAMIC parameter. 2 PQL_MPGFLQUOTAB On VAX systems, PQL_MPGFLQUOTA sets the minimum page file quota? for a process created by the Create@ Process ($CREPRC) systemE service or the DCL command RUN (Process). VSI recommends that this. parameter be no smaller than PQL_MWSEXTENT.B On Alpha and Integrity servers, PQL_MPGFLQUOTA sets the minimumA pagelet file quota for a process created by the Create Process= ($CREPRC) system service or the DCL command RUN (Process).< PQL_MPQFLQUOTA has the DYNAMIC and GEN attributes. On VAX8 systems, PQL_MPQFLQUOTA is also an AUTOGEN parameter. 2 PQL_MPRCLM= PQL_MPRCLAM sets the minimum subprocess limit for a process@ created by the Create Process ($CREPRC) system service or the DCL command RUN (Process).1 PQL_MPRCLM has the DYNAMIC and GEN attributes. 2 PQL_MTQELMB PQL_MTQELM sets the minimum number of timer queue entries for aD process created by the Create Process ($CREPRC) system service or! the DCL command RUN (Process).1 PQL_MTQELM has the DYNAMIC and GEN attributes. 2 PQL_MWSDEFAULTA PQL_MWSDEFAULT sets theB minimum default working set size for aD process created by the Create Process ($CREPRC) system service or! the DCL command RUN (Process).D This value overrides a smaller quantity that is set for a user in AUTHORIZE.5 PQL_MWSDEFAULT has the AUTOGEN and GEN attributes. 2 PQL_MWSEXTENTB PQL_MWSEXTENT sets the minimum working set extent for a processD created by the Create Process ($CREPRC) system service or the DCL command RUN (Process).< This value overriCdes a smaller quantity set for a user in AUTHORIZE.> PQL_MWSEXTENT has the AUTOGEN, DYNAMIC, and GEN attributes. 2 PQL_MWSQUOTA@ PQL_MWSQUOTA sets the minimum working set quota for a processD created by the Create Process ($CREPRC) system service or the DCL command RUN (Process).< This value overrides a smaller quantity set for a user in AUTHORIZE.= PQL_MWSQUOTA has the AUTOGEN, DYNAMIC, and GEN attributes. 2 PRCPOLINTERVALB PRCPOLINTERVAL spec Difies, in seconds, the polling interval usedB to look for Systems Communications Services (SCS) applications,C such as the connection manager and mass storage control protocol@ disks, on other nodes. All discovered nodes are polled during each interval.C This parameter trades polling overhead against quick recognition, of new systems or servers as they appear.@ PRCPOLINTERVAL is a DYNAMIC parameter. On Alpha and Integrity8 servers, PRCPOLINTERVAL is also an AUTOGEN para Emeter. 2 PRIORITY_OFFSET@ PRIORITY_OFFSET specifies the difference in priority requiredC by the scheduler for one process to preempt the current process.? A value of 2, for example, means that if the current processA is executing at priority 1, a computable process at priority 2A or 3 is not allowed to preempt the current process. However, a@ priority 4 or higher process can preempt the current process.D This mechanism affects only normal priority (0-15) processes. TheF default value is 0.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 PROCSECTCNTD PROCSECTCNT sets the number of section descriptors that a processC can contain. Each section descriptor increases the fixed portion% of the process header by 32 bytes.@ Set a value greater than the maximum number of image sections? in any section to be run, as indicated by the linkage memory aGllocation map for the image.2 PROCSECTCNT has the AUTOGEN and GEN attributes. 2 PU_OPTIONS+ PU_OPTIONS is reserved for VSI use only. 2 QDSKINTERVAL@ QDSKINTERVAL establishes, in seconds, the disk quorum polling$ interval. The default value is 3. 2 QDSKVOTESB QDSKVOTES specifies the number of votes contributed by a quorum disk in a cluster. 2 QUANTUM! QUANTUM defines the following:@ o Processor time: maximum amount of processor time a pHrocessC can receive before control passes to another process of equal' priority that is ready to computeA o Balance set residency: minimum amount of service a compute-< state process must receive before being swapped out to secondary storage= QUANTUM has the DYNAMIC and MAJOR attributes. On Alpha and= Integrity servers, QUANTUM also has the AUTOGEN attribute. 2 RAD_SUPPORT4 RAD_SUPPORT enables RAD-aware code to be executed< on systems that supIport Resource Affinity Domains (RADs);8 for example, AlphaServer GS160 systems and Integrity = cell-based servers or BL8x0c i2 servers. A RAD is a set of; hardware components (CPUs and memory) with common access characteristics.< Bits are defined in the RAD_SUPPORT parameter as follows:6 RAD_SUPPORT (default is 207 for Alpha and 10944667  for Integrity servers)6 ___________________________________________________ 3 2 2 2 2 1 13 1 8 7 4 3 J 6 5 8 7 04 +-----+-----+-----------+-----------+-----------+4 |00|00| skip|ss|gg|ww|pp|00|00|00|00|0p|df|cr|ae|4 +-----+-----+-----------+-----------+-----------+- Bit 0 (e): Enable - Enables RAD supportD Bit 1 (a): Affinity - Enables Soft RAD Affinity (SRA) schedulingE Also enables the interpretation of the skip& bits, 24-27.? Bit 2 (r): Replicate - Enables system-space code replication4 BitK 3 (c): Copy - Enables copy on soft fault? Bit 4 (f): Fault - Enables special page fault allocation@ Also enables the interpretation of the1 allocation bits, 16-23.) Bit 5 (d): Debug - Reserved to VSI8 Bit 6 (p): Pool - Enables per-RAD non-paged pool) Bits 7-15: - Reserved to VSIE Bits 16-23: - If bit 4 is set, bits 16-23 are interpreted% as follows:? B Lits 16,17 (pp): Process = Pagefault on process (non global)# pages? Bits 18,19 (ww): Swapper = Swapper's allocation of pages for' processes7 Bits 20,21 (gg): Global = Pagefault on global pages= Bits 22,23 (ss): System = Pagefault on system space pages Encodings for pp, ww, gg, ss:: Current (0) - allocate PFNs from the current CPU's RAD< Random (1) - allocate PFNs using the "random" algorithmB Base (2) - Mallocate PFNs from the operating system's "base" RADC Home (3) - allocate PFNs from the current process's home RADG If bits 16-23 are 0, the defaults for pp, ww, gg, ss are interpreted as follows: Process = home RAD= Swapper = current RAD (also sets home RAD for process) Global = random RAD System = base RAD> Bits 24-27: - If bit 1 is set, bits 24-27 are interpretedB as a skip count value (power of 2 N). Example: If? bits 24-27 contain a 3, the skip count is 8.C If bits 24-27 contain a 5, the skip count is 32.A If bits 24-27 are 0, the default of 16 is used% as the skip count." Bits 28-31: - Reserved to VSIA For more information about using OpenVMS RAD features, see the> OpenVMS Alpha Galaxy and Partitioning Guide or VSI OpenVMS 7 Version 8.4 New Features and Documentation Overview.% RAD_SUPPORTO has the GEN attribute.< REALTIME_SPTS has the DYNAMIC, GEN, and MAJOR attributes. 2 RECNXINTERVAL> RECNXINTERVAL establishes the polling interval, in seconds,; during which to attempt reconnection to a remote system.? RECNXINTERVAL is a DYNAMIC parameter. On Alpha and Integrity7 servers, RECNXINTERVAL is also an AUTOGEN parameter. 2 RESALLOC< RESALLOC controls whether resource allocation checking isA performed. The default value of 0 disables resource all Pocation checking.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 RESHASHTBLB RESHASHTBL defines the number of entries in the lock managementC resource name hash table. Each entry requires 4 bytes. A typicalC tuning goal is to have the RESHASHTBL parameter about four timesB larger than the total number of resources in use on the system.B Managers of systems with memory constrainQts or systems that areC not critically dependent on locking speed could set the table to a smaller size.> RESHASHTBL has the AUTOGEN, FEEDBACK, and MAJOR attributes. 2 RJOBLIMD RJOBLIM defines the maximum number of remote terminals allowed in the system at any one time." RJOBLIM is a DYNAMIC parameter. 2 RMS_CONPOLICYA RMS_CONPOLICY specifies the policy to be used for dealing withA high-contention write-shared files. This dynamic parameter canC be us Red to ensure fairness between lock conversions and new lock requests.% Possible values are the following: Value Explanation@ NEVER (Default) Never use the higher overhead option@ to improve fairness for any write-shared files; accessed on the system; minimal overhead.? SOMETIMES Use this option for fairer bucket access (butA higher overhead) to any write-shared files withA globalS buffers enabled that are accessed on the system.? ALWAYS Use this option for fairer bucket access (but< higher overhead) to all write-shared files) accessed on the system.B You can set this system parameter with the DCL command SET RMS_C DEFAULT/SYSTEM/CONTENTION_POLICY=value and display the parameter) with the DCL command SHOW RMS_DEFAULT.( RMS_CONPOLICY is a DYNAMIC parameter. 2 RMSD*B RMSD1, RMSD2, RTMSD3, RMSD4, RMSD5, RMSD6, and RMSD7 are special# parameters reserved for VSI use. RMSD* parameters are DYNAMIC. 2 RMS_DFLRLD This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so.$ RMS_DFLRL is a DYNAMIC parameter. 2 RMS_DFMBCA RMS_DFMBC specifies a default multiblock count only for record< I/O operations, where count is the number of blocks to be! allocated for each I/O buffer. UB You can set this system parameter with the DCL command SET RMS_> DEFAULT/SYSTEM and display the parameter with the SHOW RMS_ DEFAULT command.1 RMS_DFMBC is an AUTOGEN and DYNAMIC parameter. 2 RMS_DFMBFIDXA RMS_DFMBFIDX establishes the default RMS multibuffer count forD indexed sequential disk operations. This value defines the number? of I/O buffers that RMS allocates for each indexed file. ForC sequential access, a larger number that allows some of the indeVx7 buckets to remain in memory can improve performance.9 You can set this system parameter with the DCL commandB SET RMS_DEFAULT/SYSTEM and display the parameter with SHOW RMS_ DEFAULT.4 RMS_DFMBFIDX is an AUTOGEN and DYNAMIC parameter. 2 RMS_DFMBFRELA RMS_DFMBFREL establishes the default RMS multibuffer count forA relative disk operations. This value defines the number of I/O5 buffers that RMS allocates for each relative file.9 You can set this systemW parameter with the DCL commandB SET RMS_DEFAULT/SYSTEM and display the parameter with SHOW RMS_ DEFAULT.4 RMS_DFMBFREL is an AUTOGEN and DYNAMIC parameter. 2 RMS_DFMBFSDKA RMS_DFMBFSDK establishes the default RMS multibuffer count forC sequential disk operations. This value defines the number of I/O8 buffers that RMS allocates for sequential disk files.@ The default value is usually adequate. However, if read-ahead@ or write-behind operations are used, a largXer number improves performance.9 You can set this system parameter with the DCL commandB SET RMS_DEFAULT/SYSTEM and display the parameter with SHOW RMS_ DEFAULT.4 RMS_DFMBFSDK is an AUTOGEN and DYNAMIC parameter. 2 RMS_DFMBFSMTA RMS_DFMBFSMT establishes the default RMS multibuffer count forA magnetic tape operations. This value defines the number of I/O6 buffers that RMS allocates for magnetic tape files.9 You can set this system parameter with the DCL YcommandB SET RMS_DEFAULT/SYSTEM and display the parameter with SHOW RMS_ DEFAULT.4 RMS_DFMBFSMT is an AUTOGEN and DYNAMIC parameter. 2 RMS_DFMBFSURB RMS_DFMBFSUR establishes the default multibuffer count for unit record devices.9 You can set this system parameter with the DCL commandB SET RMS_DEFAULT/SYSTEM and display the parameter with SHOW RMS_ DEFAULT.4 RMS_DFMBFSUR is an AUTOGEN and DYNAMIC parameter. 2 RMS_DFNBCB RMS_DFNBC specifies a d Zefault block count for network access to> remote, sequential, indexed sequential, and relative files.@ The network block count value represents the number of blocks? that RMS is prepared to allocate for the I/O buffers used toB transmit and receive data. The buffer size used for remote fileB access, however, is the result of a negotiation between RMS andC the remote file access listener (FAL). The buffer size chosen is* the smaller of the two sizes presented.C Thus, RMS_D [FNBC places an upper limit on the network buffer sizeD that is used. It also places an upper limit on the largest recordD that can be transferred to or from a remote file. In other words,B the largest record that can be transferred must be less than or. equal to RMS_DFNBC multiplied by 512 bytes.9 You can set this system parameter with the DCL commandB SET RMS_DEFAULT/SYSTEM and display the parameter with SHOW RMS_ DEFAULT.1 RMS_DFNBC is an AUTOGEN and DYNAMIC parameter \. 2 RMS_EXTEND_SIZE@ RMS_EXTEND_SIZE specifies the number of blocks by which filesD are extended as they are written. This number should be chosen toD balance the amount of extra disk space wasted at the ends of eachD file against the performance improvement provided by making large extents infrequently.B When small disk quotas are used, specify a small number such asD the disk cluster size to prevent the user's disk quota from beingC consumed. If the value of 0 is ]used, RMS allocates large extentsB and truncates the file back to its actual usage when it closes.9 You can set this system parameter with the DCL commandB SET RMS_DEFAULT/SYSTEM and display the parameter with SHOW RMS_ DEFAULT.* RMS_EXTEND_SIZE is a DYNAMIC parameter. 2 RMS_FILEPROTA RMS_FILEPROT determines the default file protection for systemC processes such as those that create the error log, operator log,A and job controller. It also determines default ^file protectionC for processes created by the job controller (all interactive and batch processes).@ Because a process always inherits its default file protectionA from its creator process, RMS_FILEPROT determines default fileC protection only for users who do not execute the DCL command SETA PROTECTION/DEFAULT in their login command procedures or during interactive sessions.@ The protection is expressed as a mask. (See the discussion of@ the $CRMPSC system servic_e in the VSI OpenVMS System ServicesD Reference Manual for more information about specifying protection: masks.) By default, the mask is 64000 (decimal) or FA00< (hexadecimal), which represents the following protection: (S:RWED,O:RWED,G:RE,W:) 2 RMS_HEURISTICD This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so.( RMS_HEURISTIC is a DYNAMIC parameter. 2 RMS_PATH_TMOB The RMS path `cache in each process holds entries that translate? DVI+DID+name to new DVI+DID. These are used to greatly speed? up directory path walks. Cache entries representing ordinaryA directory lookups are invalidated through the volume directory= sequence number mechanism (UDB$L_DIRSEQ), which is clocked@ on every volume dismount and each time a directory is deleted< or renamed. However, there is no convenient mechanism for> invalidating a cache entry that represents a symlink, whoseaA interpretation is affected by logical names or modification of@ the symlink. The only way to eliminate stale cache entries isC with a timeout. This parameter is the system-wide cache timeout. Special values:% 1 = don't keep cache entries' -1 = keep cache entries forever$RMS_PATH_TMO is a DYNAMIC parameter. 2 RMS_PROLOGUEA RMS_PROLOGUE specifies the default prologue RMS uses to create? indexed files. The default value 0 specifies that RMS shouldA b determine the prologue based on characteristics of the file. AA value of 2 specifies Prologue 2 or Prologue 1, and 3 specifiesD Prologue 3. The RMS prologues are described in the OpenVMS Record( Management Services Reference Manual.' RMS_PROLOGUE is a DYNAMIC parameter. 2 RMS_SEQFILE_WBH? (Alpha and Integrity servers) RMS_SEQFILE_WBH can enable the? RMS writebehind feature as a system default for any unshared@ sequential disk file if the file is opened for image cI/O withC write access specified. The possible settings are the following: Setting DescriptionC 0 (default) Do not enable writebehind feature. Preserve prior@ behavior of using writebehind only if the user@ requests it by setting RAB$V_WBH in RAB$L_ROP.? 1 Enable writebehind feature as system default,@ including the allocation of at least two local buffers.* RMS_SEQFILE_WBH is a dDYNAMIC parameter. 2 S0_PAGING, S0_PAGING controls paging of system code:> o Setting bit 0 disables paging of all Exec code and data.= o Setting bit 1 disables paging of all RMS code and data.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 S2_SIZEC (Alpha and Integrity servers) S2_SIZE is the number of megabytes@ to reserve for S2 space. This value does not include the esize* required for extended file cache (XFC). 2 SAVEDUMPA If the dump file is saved in the page file, SAVEDUMP specifiesB whether the page file is saved until the dump file is analyzed.A The default value 0 specifies that the page file should not be@ retained. A value of 1 specifies that the dump written to the? page file should be retained until either copied or released using the SDA utility. 2 SCHED_FLAGS2 Special DYNAMIC parameter reserved for VSI use.f 2 SCH_HARD_OFFLDD The scheduler hard off-load parameter is a CPU bitmask parameter.? The bits correspond to CPU IDs. For any bit set, the OpenVMS? scheduler does not schedule processes on this CPU unless theD process has hard affinity set for the CPU. In addition, a process> with the PRIMARY capability requirement will ignore the bit$ corresponding to the primary CPU.) SCH_HARD_OFFLD is a DYNAMIC parameter. 2 SCH_SOFT_OFFLDD The scheduler soft off-load p garameter is a CPU bitmask parameter.? The bits correspond to CPU IDs. For any bit set, the OpenVMS= scheduler tries to avoid scheduling processes on this CPU.< However, if no other idle CPUs exist, processes are still scheduled on this CPU.) SCH_SOFT_OFFLD is a DYNAMIC parameter. 2 SCSBUFFCNTA On VAX systems, SCSBUFFCNT is the number of buffer descriptorsB configured for all systems communication architecture (SCA). IfD an SCA device is not configured on your s hystem, this parameter isA ignored. Generally speaking, each data transfer needs a buffer> descriptor and thus the number of buffer descriptors can be? a limit on the number of possible simultaneous I/Os. Various= performance monitors report when a system is out of buffer? descriptors for a given workload which is an indication that@ a larger value for SCSBUFFCNT is worth considering. Note thatD AUTOGEN provides feedback for this parameter on VAX systems only.D On Alpha an id Integrity servers, the system communication servicesD (SCS) buffers are allocated as needed, and SCSBUFFCNT is reserved for VSI use only.< SCSBUFFCNT has the AUTOGEN, FEEDBACK, and GEN attributes. 2 SCSFLOWCUSH? Specifies the lower limit for receive buffers at which pointB system communication services (SCS) starts to notify the remoteB SCS of new receive buffers. For each connection, SCS tracks theD number of receive buffers available. SCS communicates this numberD j to the SCS at the remote end of the connection. However, SCS doesB not need to do this for each new receive buffer added. Instead,C SCS notifies the remote SCS of new receive buffers if the number< of receive buffers falls as low as the SCSFLOWCUSH value.> The default value is adequate on most systems. If a systemsB communication architecture (SCA) port is not configured on your% system, this parameter is ignored.& SCSFLOWCUSH is a DYNAMIC parameter. 2 SCSI_ERROR_ kPOLL? If an error occurs while a particular initiator is accessing@ a SCSI device, that error is latched for all other initiatorsB and is not unlatched and reported to the other initiators until@ the next time they access the device. Therefore, if the other> initiators do not access the device in a timely manner, theA reporting of the error can be greatly delayed, which can cause confusion.? The purpose of SCSI_ERROR_POLL is to cause OpenVMS to send a@ SCSI Test Unit lReady command every hour to each SCSI disk, in@ an attempt to force latched errors to become unlatched and toB be reported immediately. SCSI_ERROR_POLL has a default value ofC 1. It can, however, be set to 0 by the user in order to stop the error polling activity.A The parameter affects SCSI disks connected by Fibre Channel asB well as parallel SCSI. If the disk has multiple paths, then theB error polling is performed on all non-served paths to the disk.A Tapes and other nmon-disk devices are not subject to this error0 polling, regardless of the parameter setting.* SCSI_ERROR_POLL is a DYNAMIC parameter.& SCSI_NOAUTO is a DYNAMIC parameter. 2 SCSICLUSTER_P[1-4]: (Alpha only) SCSICLUSTER_P[1-4] parameters allow non-HP1 peripherals (CPU-lookalikes) in SCSI clusters.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 SCSMAXDG/ This parameter nis reserved for VSI use only." SCSMAXDG has the GEN attribute. 2 SCSMAXMSG/ This parameter is reserved for VSI use only.# SCSMAXMSG has the GEN attribute. 2 SCSNODED SCSNODE specifies the name of the computer. This parameter is not dynamic.C Specify SCSNODE as a string of up to six characters. Enclose the string in quotation marks.& NOTE> The maximum size of six characters is strictly enforced.? SYSBOOoT truncates the value of SCSNODE if the size of the: system parameter is set to more than six characters.D If the computer is in an OpenVMS Cluster, specify a value that is= unique within the cluster. Do not specify the null string.C If the computer is running DECnet for OpenVMS, the value must be$ the same as the DECnet node name.. SCSNODE has the AUTOGEN and GEN attributes. 2 SCSRESPCNT> SCSRESPCNT is the total number of response descriptor tableA entriesp (RDTEs) configured for use by all system applications.D If SCA or DSA ports are not configured on your system, the system ignores SCSRESPCNT.< SCSRESPCNT has the AUTOGEN, FEEDBACK, and GEN attributes. 2 SCSSYSTEMIDB Specifies a number that identifies the computer. This parameterB is not dynamic. SCSSYSTEMID is the low-order 32 bits of the 48-$ bit system identification number.D If the computer is in an OpenVMS Cluster, specify a value that is; unique within theq cluster. Do not use zero as the value.? If the computer is running DECnet for OpenVMS, calculate the= value from the DECnet address using the following formula:E SCSSYSTEMID = ((DECnet area number) * 1024) + (DECnet node number)B Example: If the DECnet address is 2.211, calculate the value as follows:( SCSSYSTEMID = (2 * 1024) + 211 = 2259% SCSSYSTEMID has the GEN attribute. 2 SCSSYSTEMIDH8 Specifies the high-order 16 bits of the 48-bit system@ ide rntification number. This parameter must be set to 0. It is" reserved by VSI for future use.& SCSSYSTEMIDH has the GEN attribute. 2 SECURITY_POLICY7 SECURITY_POLICY allows a system to run in a C2 or B17 configuration and to subset out particular pieces of= functionality-to exclude functionality that is outside the< evaluated configuration or to preserve compatibility withA previous versions of the operating system. See the VSI OpenVMSD Guide to System Security for sfurther information about the C2 and B1 evaluated configurations." The following bits are defined: Bit Description 0 Obsolete.> 1 Allows multiple user names to connect to DECW$SERVER.C 2 Allows unevaluated DECwindows transports (such as TCP/IP).7 3 Allows $SIGPRC and $PRCTERM to span job trees.@ 4 Allows security profile changes to protected objects onA a local node when the object server is absent and cannot5 update tthe cluster database VMS$OBJECTS.DAT.B 5 Allows creation of protected objects on a local node whenB the object server is absent and cannot update the cluster" database VMS$OBJECTS.DAT.@ 6 Allows SPAWN or LIB$SPAWN commands in CAPTIVE accounts. 7 Reserved to VSI. 8 Reserved to VSI.@ 9 Disables password synchronizations among ACME agents on? a systemwide pasis. This is functionally equivalent to@ the SYS$SINGLE_SIGNON u logical name bit mask value 4 for LOGINOUT.D 10 Allows privileged applications to successfully authenticateD a user whose principal name maps to a SYSUAF record that isC either expired or whose modal restrictions would otherwise- prevent the account from being used.A A SYSUAF record that is disabled or password-expired (inB the case of traditional OpenVMS authentication) cannot be! bypassed in this manner.= An apvplication with SECURITY privilege specifies theA SYS$ACM ACME$M_NOAUTHORIZE function modifier to override authorization checks.@ 11 Allows any record in the SYSUAF file to be mapped using! external authentication.C 12 Allows intrusions on a clusterwide or local basis. (If the5 bit is cleared, intrusions are clusterwide.) 13 Reserved to VSI.; 14 Allows the internal name and backlink of files andA directories to be rea wd if the user has either execute orD read access to the file or directory. If this bit is clear,! read access is required.B Setting this bit allows the full POSIX pathname of a fileB or directory to be displayed when some of the directoriesB in the path are execute-only to the user. This feature is0 required in the following environments:' o POSIX pathnames are in use.> o The BASH shell or other GNV components are in usxe.= o Applications are using the realpath(), getcwd(),A getpwnam(), and related C runtime library functions.? The default value of 7 preserves compatibility with existingC DECwindows Motif behavior. A value of 0 disables all unevaluated configurations. 2 SETTIMEC SETTIME enables (1) or disables (0) solicitation of the time ofD day each time the system is booted. This parameter should usuallyC be off (0), so that the system sets the time of dyay at boot timeD to the value of the processor time-of-day register. You can reset@ the time after the system is up with the DCL command SET TIME( (see the VSI OpenVMS DCL Dictionary). 2 SHADOW_D1-D53 Special DYNAMIC parameters reserved for VSI use. 2 SHADOW_ENABLE* Special parameter reserved for VSI use. 2 SHADOWINGB SHADOWING loads the host-based volume shadowing driver. See VSIB Volume Shadowing for OpenVMS for more information about setting* systezm parameters for volume shadowing.' Specify one of the following values: Value DescriptionB 0 No shadowing is enabled; SHDRIVER is not loaded. This is the default value.B 2 Host-based volume shadowing enabled; SHDRIVER is loaded.? Host-based volume shadowing provides shadowing of allD disks located on a standalone system or an OpenVMS Cluster system. 2 SHADOW_HBMM_RTC> (Alpha and Integrity servers) SHADOW_HBMM_RTC { specifies, inA seconds, how frequently each shadow set on this system has itsA modified block count compared with the reset threshold. If theC modified block count exceeds the reset threshold, the bitmap forB that shadow set is zeroed. This comparison is performed for all< shadow sets mounted on the system that have HBMM bitmaps.B The reset threshold is specified by the RESET_THRESHOLD keyword6 in the /POLICY qualifier of the SET SHADOW command.> When the comparison is |made, the modified block count might? exceed the reset threshold by a small increment or by a muchA larger amount. The difference depends on the write activity to3 the volume and on the setting of this parameter.* SHADOW_HBMM_RTC is a DYNAMIC parameter. 2 SHADOW_MAX_COPY? The value of SHADOW_MAX_COPY controls how many parallel copy' threads are allowed on a given node.> Carefully consider the needs of each shadowed node when you? set this parameter. Too high a }value for SHADOW_MAX_COPY canB affect performance by allowing too many copy threads to operateB in parallel. Too low a value unnecessarily restricts the number1 of threads your system can effectively handle.B See VSI Volume Shadowing for OpenVMS for more information about2 setting system parameters for volume shadowing.: SHADOW_MAX_COPY has the AUTOGEN and DYNAMIC attributes. 2 SHADOW_MAX_UNITC SHADOW_MAX_UNIT specifies the maximum number of shadow sets thatA can ~ exist on a system. The setting must be equal to or greater? than the number of shadow sets you plan to have on a system.C Dismounted shadow sets, unused shadow sets, and shadow sets with@ no write bitmaps allocated to them are included in the total.& NOTEA Review this default carefully. The setting must be equal to@ or greater than the number of shadow sets you plan to have@ on a system. If you attempt to mount more shadow sets than @ the number specified by SHADOW_MAX_UNIT, the MOUNT command@ will fail. Dismounted shadow sets, unused shadow sets, and= shadow sets with no write bitmaps allocated to them are0 included in the count for SHADOW_MAX_UNIT.D On Alpha and Integrity servers, the default value for this system9 parameter is 500, which consumes 24 KB of main memory.B If you do not plan to use Volume Shadowing for OpenVMS, you canD change the setting to its minimum of 10 (which consum es 480 bytesD of main memory). Setting the default to its minimum frees up 23.5A KB of main memory on an OpenVMS Alpha or Integrity servers andD 4.5 KB of main memory on a VAX system. (The maximum value of this parameter is 10,000.)= This system parameter is not dynamic; that is, a reboot is( required when you change the setting. 2 SHADOW_MBR_TMOA SHADOW_MBR_TMO controls the amount of time the system tries toB fail over physical members of a shadow set before rem oving themD from the set. The SHADOW_MBR_TMO parameter replaces the temporary* VMSD3 parameter used in prior releases.C The SHADOW_MBR_TMO parameter is valid for use only with Phase IIA of Volume Shadowing for OpenVMS. You cannot set this parameter+ for use with Phase I, which is obsolete.B Use the SHADOW_MBR_TMO parameter (a word) to specify the numberA of seconds, in decimal from 1 to 65,535, during which recoveryA of a repairable shadow set is attempted. If you do not specifyC a value or if you specify 0, the default delay of 120 seconds is used.D Because SHADOW_MBR_TMO is a dynamic parameter, you should use the@ SYSGEN command WRITE CURRENT to permanently change its value.) SHADOW_MBR_TMO is a DYNAMIC parameter. 2 SHADOW_PSM_RDLYC When a copy or merge operation is needed on a shadow set that isA mounted on more than one system, the shadowing driver attemptsC to perform the operation on a system that has a local connectio nB to all the shadow set members. Shadowing implements the copy or@ merge operation by adding a time delay based on the number ofB shadow set members that are MSCP-served to the system. No delayC is added for local members; a system with all locally accessibleA shadow set members usually performs the copy or merge before aB system on which one or more members is served (and therefore is delayed) does.@ SHADOW_PSM_RDLY allows the system manager to adjust the delayD tha t shadowing adds. By default, the delay is 30 seconds for eachC MSCP-served shadow set member. The valid range for the specified% delay is 0 through 65,535 seconds.A When a shadow set is mounted on a system, the value of SHADOW_C PSM_RDLY is used as the default shadow set member recovery delayA for that shadow set. To modify SHADOW_PSM_RDLY for an existing? shadow set, see the SET SHADOW/ /RECOVERY_OPTIONS=DELAY_PER_? SERVED_MEMBER=n command in VSI Volume Shadowing for OpenVMS. 2 SHADOW_REC_DLY (Alpha and Integrity servers)A The value of the SHADOW_REC_DLY parameter specifies the length? of time a system waits before it attempts to manage recovery< operations on shadow sets that are mounted on the system.= A shadow set is said to need recovery when a merge or copy, operation is required on that shadow set.@ SHADOW_REC_DLY can be used to better predict which systems in@ an OpenVMS Cluster performs recovery operations. This is do ne@ by setting lower values of SHADOW_REC_DLY on systems that are? preferred to handle recovery operations and higher values of? SHADOW_REC_DLY on systems that are least preferred to handle recovery operations.B The range of SHADOW_REC_DLY is 20 to 65535 seconds. The default value is 20 seconds.C For more information about controlling which systems perform theB merge or copy operations, see VSI Volume Shadowing for OpenVMS.) SHADOW_REC_DLY is a DYNAMIC parameter . 2 SHADOW_SITE_ID? (Alpha and Integrity servers) This parameter allows a systemA manager to define a site value, which Volume Shadowing uses to@ determine the best device to perform reads, thereby improving performance.> The system manager can now define the site value to be used@ for all shadow sets mounted on a system. This parameter is an? arbitrary numeric value coordinated by the system manager of@ disaster tolerant clusters. Reads from devices that have siteA values matching the shadow set's site value are preferred over> reads from devices with different site values. For detailedB information, see the description of the $SET DEVICE/SITE in theC VSI OpenVMS DCL Dictionary and VSI Volume Shadowing for OpenVMS.) SHADOW_SITE_ID is a DYNAMIC parameter. 2 SHADOW_SYS_DISKB A SHADOW_SYS_DISK parameter value of 1 enables shadowing of theC system disk. A value of 0 disables shadowing of the system disk. The default value  is 0.A Also specify a system disk shadow set virtual unit number withB the SHADOW_SYS_UNIT system parameter, unless the desired system disk unit number is DSA0.B A value of 4096 enables CI-based minimerge. To enable minimergeA on a system disk, however, you must enable DOSD by setting theC DUMPSTYLE parameter to dump off system disk, as described in theB VSI OpenVMS System Manager's Manual. You can then add the valueC 4096 to your existing SHADOW_SYS_DISK value. For ex ample, if youA have SHADOW_SYS_DISK set to a value of 1, change it to 4097 to enable minimerge. 2 SHADOW_SYS_TMOD The SHADOW_SYS_TMO parameter has the following two distinct uses:= o At system boot time, when this is the first node in theD cluster to boot and to create this specific shadow set. If theB proposed shadow set is not currently mounted in the cluster,B use this parameter to extend the time a booting system waitsB for all former members of the shadowed system disk to become available.> o Once the system successfully mounts the virtual unit and> begins normal operations. In this usage, the SHADOW_SYS_@ TMO parameter controls the time the operating system waitsB for errant members of a system disk. (Use the SHADOW_MBR_TMOB parameter to control the time the operating system waits for1 the errant members of an application disk.)C This parameter applies only to members of the system disk shado wB set. All nodes using a particular system disk shadow set shouldA 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 aA higher value if you want the system to wait more than the 120-A second default for all members to join the shadow set. You can9 set the parameter value to 120 through 65,535 seconds. 2 SHADOW_SYS_UNITB Use this parameter for Phase II shadowing o nly. The SHADOW_SYS_D UNIT parameter is an integer value that contains the virtual unitA number of the system disk. The default value is 0. The maximumC value allowed is 9999. This parameter is effective only when theD SHADOW_SYS_DISK parameter has a value of 1. This parameter shouldA be set to the same value on all nodes booting off a particular? system disk shadow set. See VSI Volume Shadowing for OpenVMSB for more information about setting system parameters for volume s hadowing. 2 SHADOW_SYS_WAITB The SHADOW_SYS_WAIT parameter extends the time a booting systemB waits for all current members of a mounted shadowed system diskC to become available to this node. The shadow set must already beC mounted by at least one other cluster node for this parameter to take effect.? The default value is 480 seconds. Change this parameter to aA higher value if you want the system to wait more than the 480-A second default for all members to join the shadow set. You can7 set the parameter value to 1 through 65,535 seconds. 2 SMCI_FLAGSB (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:/ Bit Mask Description> 0 0 0 = Do not create local communications channelsA (SYSGEN default). Local SCS communications ar e@ primarily used in test situations and are notC needed for normal operations. Not creating local? communications saves resources and overhead.8 1 = Create local communications channels.B 1 2 0 = Load SYS$PBDRIVER if booting into both a Galaxy2 and a Cluster (SYSGEN Default).> 1 = Load SYS$PBDRIVER if booting into a Galaxy.; 2 4 0 = Minimal console output (SYSGEN default).= 1 = Full console output; SYS$PBDRIVER displaysB console messages when it creates and tears down+ communications channels.( SMCI_FLAGS has the DYNAMIC attribute. 2 SMCI_PORTS@ On systems running OpenVMS Galaxy software, the Shared MemoryC Cluster Interconnect (SMCI) system parameter SMCI_PORTS controlsA initial loading of SYS$PBDRIVER. This parameter is a bit mask;A bits 0 through 25 each represent a contro ller 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 isB loaded, and so on up to bit 25, which causes PBZx to be loaded.B For OpenVMS Alpha Version 7.2 and later, VSI recommends leaving, this parameter at the default value of 1.@ Loading additional ports allows multiple paths between GalaxyC instances. In the initial release of the Galaxy software, having? multiple communications cha nnels 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. 2 SMP_CPU_BITMAPB This parameter indicates that the corresponding CPU is a bitmap< representing up to 1024 CPUs. Each bit set in this bitmap> indicates that the corresponding CPU automatically attemptsA to join t he active set in an OpenVMS symmetric multiprocessingC environment when the instance is booted. A cleared bit indicatesD that the corresponding CPU is ignored only at boot time; if it is< otherwise viable, the CPU can be started at a later time.C SMP_CPU_BITMAP defaults to all bits set. (CPU 0 through CPU 1023D are enabled for multiprocessing.) Note that the primary processorB is always booted regardless of the setting of the corresponding bit in the CPU bitmap.> To change the value of SMP_CPU_BITMAP in SYSBOOT or SYSGEN,B specify a list of individual bits or contiguous groups of bits. For example:* SYSGEN> SET SMP_CPU_BITMAP 0,5,17-21B The command in this example sets bits 0, 5, 17, 18, 19, 20, and. 21 in the bitmap and clears all other bits.2 This parameter replaces the SMP_CPUS parameter. 2 SMP_LNGSPINWAIT@ SMP_LNGSPINWAIT establishes, in 10-microsecond intervals, theB amount of time a CPU in an SMP system normally waits for access< to a shared resource. This process is called spinwaiting.; Generally spinlocks at IPL <= 8 have long holding times,@ therefore have their timeout intervals set to SMP_LNGSPINWAIT? to prevent SPINWAIT timeouts in cases of nested acquisition.+ A timeout causes a CPUSPINWAIT bugcheck.D The default value is 3000000 (30,00, 000 10-microsecond intervals or 30 second). 2 SMP_SANITY_CNT? SMP_SANITY_CNT establishes, in 10-millisecond intervals, theC  timeout period for each CPU in a symmetric multiprocessing (SMP)A system. Each CPU in an SMP system monitors the sanity timer ofD one other CPU in the configuration to detect hardware or softwareD failures. If allowed to go undetected, these failures could cause> the cluster to hang. A timeout causes a CPUSANITY bugcheck.; The default value is 300 milliseconds (30 10-millisecond intervals). 2 SMP_SPINWAITD SMP_SPINWAIT establishes, in 10-microsecond intervals, the amount@ of time a CPU in an SMP system normally waits for access to a7 shared resource. This process is called spinwaiting.+ A timeout causes a CPUSPINWAIT bugcheck.C The default value is 100000 (100,000 10-microsecond intervals or 1 second). 2 SMP_TICK_CNTA SMP_TICK_CNT sets the frequency of sanity timer checks by each# CPU in a multiprocessing system.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 SSI_ENABLE@ (Integrity servers only) This parameter controls the usage ofC system service interception. SSI_ENABLE is turned on by default.> System Service Interception is a mechanism that allows userD specified code to run before, after or instead of the intercepted? system service. This mechanism is available on OpenVMS Alpha> Version 6.1 and later and OpenVMS Integrity servers Version? 8.3 and later, but the parameter SSI_ENABLE is relevant only on Integrity server systems. 2 SSINHIBIT? SSINHIBIT controls whether system services are inhibited (1)@ (on a per-process basis). By default, system services are not inhibited (0).D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 STARTUP_P1-8> The following table describes possible values of STARTUP_P1 through _P8: STARTUP Value Description? STARTUP_P1 Specifies the type of system boot the system-B independent startup procedure is to perform when= STARTUP_P1 has one of the following values:3 o " "- A full boot is performed.C o "MIN"- A minimum boot that starts only what isB absolutely necessary for the operating system to run.A STARTUP_P2 Controls the setting of verification during the=  execution of the system-independent startupA procedure, STARTUP.COM, when STARTUP_P2 has one= of the values described in the lists below.B STARTUP_P2 can be one of the values shown in the! following list:> o F[ALSE], N[O], 0, " "-Verification is notD enabled; in other words, NOVERIFY is performed.A o T[RUE], Y[ES], 1-Verification is enabled; in<  other words, a SET VERIFY is performed.; Alternatively, STARTUP_P2 can be a string@ containing one or more of the letters shown in% the following list:D o C-Display various checkpointing messages during startup.C o D-Log (or Dump) the output from the startup toD a file called SYS$SPECIFIC:[SYSEXE]STARTUP.LOG.; o P-DCL  verification is enabled for eachD component file, but not for the startup driver.< If both P and V are used, P is ignored.@ o V-Full DCL verification is enabled; same as TRUE.@ For more information about STARTUP_P2, see the5 SYSMAN command STARTUP SET OPTIONS.A STARTUP_P3 Beginning in OpenVMS Version 7.2, if STARTUP_P3D is set to AGEN, the system executes AUTOGEN at the. end of the startup sequence.* STARTUP_P4 Reserved for future use. through STARTUP_P8 2 SWP_PRIO? SWP_PRIO sets the priority of I/O transfers initiated by the swapper.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 SWPFAIL? SWPFAIL sets the number of consecutive swap failures allowedC before the swap schedule algorithm is changed to ignore the swap quantum protection.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 SWPOUTPGCNTD This parameter allows the swapper an alternative mechanism before actually performing swaps.B On Alpha and Integrity servers, SWPOUTPGCNT defines the minimumC 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.9 SWPOUTPGCNT has the DYNAMIC attribute. On VAX systems,. SWPOUTPGCNT also has the AUTOGEN attribute. 2 SWPRATE< SWPRATE sets the swapping rate (in 10-millisecond units).A This parameter limits the amount of disk bandwidth consumed by swapping.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 SYSMWCNTB SYSMW CNT sets the quota for the size of the system working set,@ which contains the pageable portions of the system, the pagedD dynamic pool, RMS, and the resident portion of the system message file.D While a high value takes space away from user working sets, a lowD value can seriously impair system performance. Appropriate valuesA vary, depending on the level of system use. When the system isA running at full load, check the rate of system faults with theA MONITOR PAGE comman d of the Monitor utility. An average system? page fault rate of between 0 and 3 page faults per second isC desirable. If the system page fault rate is high, and especiallyC if the system seems to be slow, you should increase the value ofC SYSMWCNT. However, do not set this parameter so high that system page faulting never occurs.7 SYSMWCNT has the AUTOGEN, GEN, and MAJOR attributes. 2 SYSPFC? SYSPFC sets the number of pages to be read from disk on each system paging operation.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 SYSSER_LOGGING@ (Alpha and Integrity servers) A value of 1 for SYSSER_LOGGING@ enables logging of system service requests for a process. The default is 1.0 SYSSER_LOGGING is a DYNAMIC system parameter. 2 SYSTEM_CHECK< SYSTEM_CHECK investigates intermittent system failures by= enabling a number of run-ti me consistency checks on system2 operation and recording some trace information.> Enabling SYSTEM_CHECK causes the system to behave as if theA following system parameter values are set (although the values9 of the following parameters are not actually changed):- Parameter Value Description> BUGCHECKFATAL 1 Crash the system on nonfatal, bugchecks.? POOLCHECK %X616400FF Enable all poolchecking, wit h; an allocated pool pattern< of %x61616161 ('aaaa') and= deallocated pool pattern of5 x64646464 ('dddd').= MULTIPROCESSING 2 Enable full synchronization+ checking.> While SYSTEM_CHECK is enabled, the previous settings of the< BUGCHECKFATAL and MULTIPROCESSING parameters are ignored.> However, settin g the parameter POOLCHECK to a nonzero value1 overrides the setting imposed by SYSTEM_CHECK.D 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 performanceA implications of enabling SYSTEM_CHECK, see OpenVMS Performance Management. 2 TAPE_ALLOCLASS> TAPE_ALLOCLASS determines the tape allocation class for theA 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. 2 TAPE_MVTIMEOUTB TAPE_MVTIMEOUT is the time in seconds that a mount verificationB attempt continues on a given magnetic tape volume. If the mountA verification does not recover the volume within that time, theA I/O operations outstanding to the volume terminate abnormally.) TAPE_MVTIMEOUT is a DYNAMIC parameter. 2 TBSKIPWSL= TBSKIPWSL 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.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 TIME_CONTROLD This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so.D TIME_CONTROL is an SMP bit mask parameter that controls debugging- functions. The following bits are defined:% Bit Description# 0 Obsolete.@ 1 (EXE$V_SANITY)  Disables the SMP sanity timer support.A 2 (EXE$V_NOSPINWAIT) Disables the functional behavior of the/ SMP spinwait support.' TIME_CONTROL is a DYNAMIC parameter. 2 TIMEPROMPTWAIT? TIMEPROMPTWAIT defines the number of seconds that you want a? processor to wait for the time and date to be entered when aA system boot occurs, if the processor's time-of-year clock does? not contain a valid time. (The time unit of micro-fortnights< i s approximated as seconds in the implementation.) If theA 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.& NOTE@ VSI recommends that you set the correct system time before= allowing the system to run, so that all functions using= time-stamping (such as the operator log, the error log,B accounting records, file cre ation dates, and file expiration) dates) contain correct time values.: Depending on the value specified for the TIMEPROMPTWAIT; parameter, the system acts in one of the following ways:B o If TIMEPROMPTWAIT is 0, no prompt or wait occurs; the system? boots immediately, using the time of the last boot as the system time.A o If TIMEPROMPTWAIT is a positive number less than 32768, oneB prompt is issued and the value dictates how many seconds youC can take to respond with a time. If you do not provide a time@ before TIMEPROMPTWAIT elapses, the system boots, using the/ time of the last boot as the system time.A o If TIMEPROMPTWAIT is a number in the range of 32768 throughD 65535, the prompt for the time is issued at intervals starting= with 2 and doubling until 256 seconds is reached. If noB response is received, the prompts restart, with the 2-secondB interval. This prompting process repeats indefinitely, until you specify a time. 2 TIMVCFAILB TIMVCFAIL specifies the time required for an adapter or virtualB circuit failure to be detected. VSI recommends that the defaultE value be used. VSI also recommends that this value be lowered only@ in OpenVMS Cluster of three CPUs or less, that the same valueB be used on each computer in the cluster, and that dedicated LAN$ segments be used for cluster I/O.$ TIMVCFAIL is a DYNAMIC parameter. 2 TMSCP_LOADA TMS CP_LOAD allows the loading of the tape mass storage control? protocol server software. The TMSCP_LOAD parameter also setsD locally connected tapes served. For information about setting the9 TMSCP_LOAD parameter, see VSI OpenVMS Cluster Systems.B 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 andB makes all directly connected tape drives available clusterwide.A The following table describes the two states of the TMSCP_LOAD parameter: State FunctionC 0 Do not load the TMSCP tape server. Do not serve any local> tape devices clusterwide. This is the default value.@ 1 Load the TMSCP tape server. Serve all local TMSCP tape devices clusterwide.& TMSCP_LOAD is an AUTOGEN parameter. 2 TMSCP_SERVE_ALLD TMSCP_SERVE_ALL is a bit mask that controls the serving of tapes.D T he 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 areA implemented as a bit mask. To specify the type of serving yourA system will perform, locate the type you want in the following> table and specify its value. For some systems, you may wantA to specify two serving types, such as serving all tapes exceptA those whose allocation class does not match. To specify suc h aA 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 tapesC is restricted to serving all tapes except those whose allocationB class does not match the system's allocation class (pre-VersionB 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: Value When Bit Set DescriptionA Bit 0 1 Serve all available tapes (locally attached and? those connected to HSx and DSSI controllers).D Tapes with allocation classes that differ from theA system's allocation class (set by the ALLOCLASSA parameter) are also served if bit 3 is not set.? Bit 1 2 Serve locally attached (non-HSx and no n-DSSI) tapes. Bit 2 N/A Reserved.D Bit 3 8 Restrict the serving specified by bit 0. All tapesB except those with allocation classes that differ@ from the system's allocation class (set by the2 ALLOCLASS parameter) are served.C This is pre-Version 7.2 behavior. If your cluster@ includes systems running OpenVMS Version 7.1-xA or earlier, and you want to serve all availableB tapes, you must specify 9, the result of setting% this bit and bit 0.D Although the serving types are now implemented as a bit mask, theD values of 0, 1, and 2, specified by bit 0 and bit 1, retain their original meanings:B o 0 - Do not serve any tapes (the default for earlier versions of OpenVMS).$ o 1 - Serve all available tapes.C o 2 - Serve only locally attached (non-HSx and non-DSSI) tapes.>  If the TMSCP_LOAD system parameter is 0, TMSCP_SERVE_ALL is ignored. 2 TTY_ALTALARM@ TTY_ALTALARM sets the size of the alternate type-ahead bufferC alarm. This value indicates at what point an XOFF should be sentB to terminals that use the alternate type-ahead buffers with the0 size specified by the TTY_ALTYPAHD parameter. 2 TTY_ALTYPAHDA TTY_ALTYPAHD sets the size of the alternate type-ahead buffer.; Use this parameter to allow the block mode terminals and4 communications lines to operate more efficiently.C The default value is usually adequate. Do not exceed the maximum. value of 32767 when setting this parameter. 2 TTY_AUTOCHARB TTY_AUTOCHAR sets the character the terminal driver echoes when( the job controller has been notified.' TTY_AUTOCHAR is a DYNAMIC parameter. 2 TTY_BUF5 TTY_BUF sets the default line width for terminals. 2 TTY_CLASSNAMEA TTY_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. 2 TTY_DEFCHARD TTY_DEFCHAR sets the default characteristics for terminals, using> a code derived by summing the following hexadecimal values:, Characteristic Value (Hex) Function, PASSALL 1 Passall.0 NOECHO 2 Noecho mode.9 NOTYPEAHEAD 4 No type-ahead buffer.?  ESCAPE 8 Escape sequence processing.? HOSTSYNC 10 Host can send XON and XOFF.C TTSYNC 20 Terminal can send XON and XOFF.6 SCRIPT 40 Internal use only.. LOWER 80 Lowercase.4 MECHTAB 100 Mechanical tabs.> WRAP 200 Wraparound at end of line.A CRFILL 400 Perform carriage return fill.; LFFILL  800 Perform line feed fill.8 SCOPE 1000 Terminal is a scope.6 REMOTE 2000 Internal use only.7 EIGHTBIT 8000 Eight-bit terminal.4 MBXDSABL 10000 Disable mailbox.7 NOBRDCST 20000 Prohibit broadcast.: READSYNC 40000 XON and XOFF on reads.: MECHFORM 80000 Mechanical form feeds.B HALFDUP 100000 Set for half-duplex operation.: MODEM 200000 Set for modem signals.= PAGE FF000000 Page size. Default is 24.C Do not set the CRFILL or LRFILL characteristic as the default in TTY_DEFCHAR.. Where a condition is false, the value is 0.A The upper byte is the page length. The default characteristics? are 24 lines per page, terminal synchronization, wraparound,% lowercase, scope, and full-duplex. 2 TTY_DEFCHAR2: TTY_DEFCHAR2 sets a secon d longword of default terminal? characteristics. The default characteristics are representedA as a code that is derived by summing the following hexadecimal values:( Characteristic Value (Hex) FunctionA LOCALECHO 1 Enable local echo terminal logic;? use with the TTY_DEFCHAR NOECHO/ characteristic.: AUTOBAUD 2 Enable autobaud detection.2 HANGUP 4 Hang u p on logout.D MODHANGUP 8 Allow modification of HANGUP without+ privileges.> BRDCSTMBX 10 Allow sending of broadcasts to* mailboxes.> XON 20 (No effect in this parameter.)> DMA 40 (No effect in this parameter.)< ALTYPEAHD 80 Use the alternate type-ahead+ parameters.? SETSPEED 100 Clear to allow setting of speed3 without privileges.C DCL_MAILBX 200 Function reserved for VSI use only.@ DECCRT4 400 Terminal is DIGITAL CRT Level 4.? COMMSYNC 800 Enable flow control using modem( signals.5 EDITING 1000 Line editing allowed.= INSERT 2000 Sets default mode for insert.@ FALLBACK 4000 Do not set this bit wi th SYSGEN.: DIALUP 8000 Terminal is a dialup line.= SECURE 10000 Guarantees that no process isA connected to terminal after Break/ key is pressed.A DISCONNECT 20000 Allows terminal disconnect when a. hangup occurs.< PASTHRU 40000 Terminal is in PASTHRU mode.A SYSPWD 80000 Log in with system password only./ SIX EL 100000 Sixel graphics.D DRCS 200000 Terminal supports loadable character& fonts.: PRINTER 400000 Terminal has printer port.@ APP_KEYPAD 800000 Notifies application programs of< state to set keypad on exit.= ANSICRT 1000000 Terminal conforms to ANSI CRT6 programming standards.D REGIS 2000000 Terminal has  REGIS CRT capabilities.4 BLOCK 4000000 Block mode terminal.< AVO 8000000 Terminal has advanced video.7 EDIT 10000000 Terminal has local edit- capabilities.: DECCRT 20000000 Terminal is a DIGITAL CRT.B DECCRT2 40000000 Terminal is a DIGITAL CRT Level 2.B DECCRT3 80000000 Terminal is a DIGITAL CRT Level 3.) The defaults are AUTOBAUD and EDITING. 2 TTY_DEF CHAR3D (Alpha and Integrity servers) TTY_DEFCHAR3 allows a user to set aC bit so that the OpenVMS terminal driver remaps CTRL/H to Delete.D VSI recommends that you not set this bit as a systemwide default.( Characteristic Value (Hex) FunctionA TT3$M_BS 10 When this bit is set, the OpenVMSA terminal console remaps CTRL/H to' Delete.C For more information, see the SET TERM and SHOW TERM comman ds in" the VSI OpenVMS DCL Dictionary. 2 TTY_DEFPORT= TTY_DEFPORT provides flag bits for port drivers. Bit 0 set? to 1 indicates that the terminal controller does not provideB automatic XON/XOFF flow control. This bit should not be set forB VSI 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 VSI. 2 TTY_DIALTYPE> TTY_DIALTYPE provides flag bits for dialups. Bit 0 is 1 forB United Kingdom dialups and 0 for all others. Bit 1 controls theA modem protocol used. Bit 2 controls whether a modem line hangsB up 30 seconds after seeing CARRIER if a channel is not assignedA to the device. The remaining bits are reserved for future use.C See the OpenVMS I/O User's Reference Manual for more information about flag bits. 2 TTY_DMASIZE= 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_DMASIZE is a DYNAMIC parameter. 2 TTY_PARITY+ TTY_PARITY sets terminal default parity. 2 TTY_RSPEED> TTY_RSPEED defines the receive speed for terminals. If TTY_D RSPEED is 0, TTY_SPEED controls both the transmit and the receiveD speed. Maximum value is 20. This parameter is only applicable forD controllers that support split-speed operations, such as the DZ32 and the DMF32. 2 TTY_SCANDELTAC TTY_SCANDELTA sets the interval for polling terminals for dialup@ and hangup events. Shorter intervals use more processor time;9 longer intervals may result in missing a hangup event. 2 TTY_SILOTIME@ TTY_SILOTIME defines the interval at which the DMF32 hardware: polls the input silo for received characters. The DMF32< asynchronou s terminal controller can delay the generation= of a single input interrupt until multiple characters haveC accumulated in the input silo. TTY_SILOTIME specifies the number@ of milliseconds that the characters are allowed to accumulateA prior to the generation of an input interrupt by the hardware.& NOTEB The remainder of this discussion is of interest to customers% who use Digi Edgeport hardware.? TTY_SILOTIME controls latency, tr ading throughput and systemA overhead for latency. The default value for TTY_SILOTIME is 8.@ This value is multiplied by 100 and is used as a count of theD number of times to send a query to the device for more data after0 a character transmit or receive is performed.D If no input (or no subsequent output) is seen after 800 responsesC 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 overallA throughput; it also adds more system and USB overhead. SettingB TTY_SILOTIME to zero causes the driver to send input queries toB the device continually. This setting causes the lowest latency,C the highest system overhead, and the lowest throughput possible. 2 TTY_SPEEDA TTY_SPEED sets th e systemwide default speed for terminals. LowB byte is transmit speed, and high byte is receive speed. If highB byte is set to 0, receive speed is identical to transmit speed.C Maximum value is 20. Baud rates are defined by the $TTDEF macro. 2 TTY_TIMEOUT: TTY_TIMEOUT sets the number of seconds before a processB associated with a disconnected terminal is deleted. The defaultB value (900 seconds) is usually adequate. Note that using values? for TTY_TIMEOUT greater than one year (value %X01E13380) canC cause overflow errors and result in a disconnected device timing out immediately.& TTY_TIMEOUT is a DYNAMIC parameter. 2 TTY_TYPAHDSZ@ TTY_TYPAHDSZ sets the size of the terminal type-ahead buffer.C The default value is usually adequate. Do not exceed the maximum. value of 32767 when setting this parameter. 2 UAFALTERNATE< 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 toB 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) onlyB when the system is being used by a restricted set of users. YouA must create a user authorization file named SYSUAFALT prior to setting UAFALTERNATE to 1.1 UAFALTERNATE has the GEN and MAJOR attributes.  2 USERD1< USERD1 is reserved for definition at the user's site. The? reserved longword is referenced by the symbol SGN$GL_USERD1.8 On Alpha and Integrity servers, this symbol is in the- SYS$LOADABLE_IMAGES:SYS$BASE_IMAGE module.! USERD1 is a DYNAMIC parameter. 2 USERD2< USERD2 is reserved for definition at the user's site. The? reserved longword is referenced by the symbol SGN$GL_USERD2.8 On Alpha and Integrity servers, this symbol is in the- SYS$LOADABLE_IMAGES:SYS$BASE_IMAGE module.! USERD2 is a DYNAMIC parameter. 2 USER3> USER3 is a parameter that is reserved for definition at theA user's site. The reserved longword is referenced by the symbol SGN$GL_USER3.8 On Alpha and Integrity servers, this symbol is in the- SYS$LOADABLE_IMAGES:SYS$BASE_IMAGE module. 2 USER4> USER4 is a parameter that is reserved for definition at theA user's site. The reserved longword is referenced by the symbol SGN$GL_USER4.8 On Alpha and Integrity servers, this symbol is in the- SYS$LOADABLE_IMAGES:SYS$BASE_IMAGE module. 2 VAXCLUSTERB VAXCLUSTER controls loading of the cluster code. Specify one of the following: Value Description' 0 Never form or join a cluster.D 1 Base decision of whether to form (or join) a cluster or toA operate standalone on the presence of cluster hardware.( 2 Always form or join a cluster. The default value is 1.& VAXCLUSTER is an AUTOGEN parameter. 2 VCC_FLAGSA (Alpha only) The static system parameter VCC_FLAGS enables andA disables file system data caching. If caching is enabled, VCC_? FLAGS controls which file system data cache is loaded during system startup. Value DescriptionA 0 Disables file system data caching on the local node and) throughout the OpenVMS Cluster.D In an OpenVMS Cluster, if caching is disabled on any node,A  none of the other nodes can use the extended file cacheB or the virtual I/O cache. They can't cache any file dataC until that node either leaves the cluster or reboots with+ VCC_FLAGS set to a nonzero value.B 1 Enables file system data caching and selects the Virtual9 I/O Cache. This is the default for VAX systems.C 2 Enables file system data caching and selects the extended< file cache. This is the default for Alpha systems.& NOTE6 On Integrity servers, the volume caching productA ([SYS$LDR]SYS$VCC.EXE) is not available. XFC caching is the@ default caching mechanism. Setting the VCC_FLAGS parameter< to 1 is equivalent to not loading caching at all or to setting VCC_FLAGS to 0.% VCC_FLAGS is an AUTOGEN parameter. 2 VCC_MAXSIZEA (Alpha and Integrity servers) The static system parameter VCC_C MAXSIZE controls the size of the virtual I/O cache. VCC_MAXSIZE,? which specifies the size in blocks, is 3,700,000 by default.D The virtual I/O cache cannot shrink or grow. Its size is fixed at system startup.B To adjust the XFC size, use the VCC_MAX_CACHE system parameter.' VCC_MAXSIZE is an AUTOGEN parameter. 2 VCC_MAX_CACHEB (Alpha and Integrity servers) The dynamic system parameter VCC_B MAX_CACHE controls the maximum size of the extended file cache.D It specifies the size in megabytes. By defa ult, VCC_MAX_CACHE hasA a special value of -1 for people who do not want to tune theirA systems manually; this value means that at system startup, theB maximum size of the extended file cache is set to 50 percent of% the physical memory on the system.= The extended file cache can automatically shrink and grow,; depending on your I/O workload and how much spare memory= your system has. As your I/O workload increases, the cache@ automatically grows, but never to more than  the maximum size.> When your application needs memory, the cache automatically shrinks.C The value of VCC_MAX_CACHE at system startup sets an upper limit> for the maximum size of the extended file cache. You cannot> increase the maximum size of VCC_MAX_CACHE beyond its valueA at boot time. For example, if VCC_MAX_CACHE is 60 MB at systemA startup, you can then set VCC_MAX_CACHE to 40, which decreasesB the maximum size to 40 MB. If you then set VCC_MAX_CACHE to 80,@ t he maximum size is only increased to 60 MB, the value set at system startup.> Note that VCC_MAX_CACHE is a semi-dynamic parameter. If youC change its value, you must enter the DCL command SET CACHE/RESETB for any changes to take effect immediately. Otherwise, it might6 take much more time for the changes to take effect.< If you are using the reserved memory registry to allocate@ memory permanently, you must set the VCC$MIN_CACHE_SIZE entryC in the reserved memory registry to a value less than or equal to( VCC_MAX_CACHE at system startup time.C For instructions on setting permanent memory allocations for the6 cache, see the VSI OpenVMS System Manager's Manual.( VCC_MAX_CACHE is a DYNAMIC parameter. 2 VCC_MAX_IO_SIZEB (Alpha and Integrity servers) The dynamic system parameter VCC_B MAX_IO_SIZE controls the maximum size of I/O that can be cachedB by the extended file cache. It specifies the size in blocks. By# default, the size is 12 7 blocks.D Changing the value of VCC_MAX_IO_SIZE affects reads and writes toD volumes currently mounted on the local node, as well as reads and+ writes to volumes mounted in the future.@ If VCC_MAX_IO_SIZE is 0, the extended file cache on the local@ node cannot cache any reads or writes. However, the system isB not prevented from reserving memory for the extended file cacheB during startup if a VCC$MIN_CACHE_SIZE entry is in the reserved memory registry.* VCC_MAX_IO_SIZE is a DYNAMIC parameter. 2 VCC_MAX_LOCKS; (Alpha and Integrity servers) VCC_MAX_LOCKS is a special@ parameter reserved for VSI use only. Extended file cache will) use this parameter in future versions. 2 VCC_PAGESIZED (Alpha and Integrity servers) VCC_PAGESIZE is a special parameter? reserved for VSI use only. Extended file cache will use this parameter in future versions. 2 VCC_READAHEADB (Alpha and Integrity servers) The dynamic system paramete r VCC_C READAHEAD controls whether the extended file cache can use read-A ahead caching. Read-ahead caching is a technique that improves? the performance of applications that read data sequentially.D By default VCC_READAHEAD is 1, which means that the extended fileD cache can use read-ahead caching. The extended file cache detectsB when a file is being read sequentially in equal-sized I/Os, and@ fetches data ahead of the current read, so that the next read+ instruction can be satisfied from cache.A To stop the extended file cache from using read-ahead caching, set VCC_READAHEAD to 0.@ Changing the value of VCC_READAHEAD affects volumes currently? mounted on the local node, as well as volumes mounted in the future.B Readahead I/Os are totally asynchronous from user I/Os and only; take place if sufficient system resources are available.( VCC_READAHEAD is a DYNAMIC parameter. 2 VCC_RSVD@ (Alpha and Integrity servers) VCC_RSVD is a special parameter? reserved for VSI use only. Extended file cache will use this parameter in future versions. 2 VCC_WRITEBEHINDD (Alpha and Integrity servers) VCC_WRITEBEHIND is reserved for VSIB use only. Extended file cache will use this parameter in future versions. 2 VCC_WRITE_DELAYD (Alpha and Integrity servers) VCC_WRITE_DELAY is reserved for VSI use only. 2 VHPT_SIZEC (Integrity servers only) VHPT_SIZE is the number of kilobytes toA allocate for the virtual hash page table (VHPT) on each CPU in the system:, o 0 indicates that no VHPT is allocated.B o 1 indicates that OpenVMS is to choose a default size that is0 appropriate for your system configuration.A If a VHPT is created, the smallest size is 32KB. The VHPT_SIZEB must be a power of 2 KB in size. If the number specified is notC a power of 2, OpenVMS chooses a VHPT size to use for your system) that is close to the number specified.=  If insufficient memory is available during system startup,@ OpenVMS might choose a smaller size for the VHPT of each CPU.A A summary of possible values for VHPT_SIZE is in the following table: Value Description* 0 Do not create a VHPT on each CPU.D 1 (default) OpenVMS chooses a VHPT of an appropriate size for each CPU.A n Create a VHPT of nKB for each CPU, where n is a power ofA 2 that is 32 or greater. (The maximum value, however, is  platform-dependent.) 2 VIRTUALPAGECNTD On VAX systems, VIRTUALPAGECNT sets the maximum number of virtual= pages that can be mapped for any one process. A program isC allowed to divide its virtual space between the P0 and P1 tables in any proportion.> If you use SYS$UPDATE:LIBDECOMP.COM to decompress libraries? and the VIRTUALPAGECNT setting is low, make sure you set theC PGFLQUOTA field in the user authorization file to at least twice the size of t he library.B At installation time, AUTOGEN automatically sets an appropriate@ value for VIRTUALPAGECNT. The value depends on the particular@ configuration-the type and number of graphics adapters on the@ system, if any exist. You cannot set VIRTUALPAGECNT below the: minimum value required for your graphics configuration.? Because the VIRTUALPAGECNT setting supports hardware address; space rather than system memory, do not use the value ofB VIRTUALPAGECNT that AUTOGEN sets to gauge the size of your page file.@ Starting with OpenVMS Version 7.0, VIRTUALPAGECNT has been an? obsolete parameter on Alpha systems. Note, however, that the@ parameter remains in existence on Alpha and Integrity serversD for compatibility purposes and has a default and maximum value of> %X7FFFFFFF. SYSBOOT and AUTOGEN enforce this default value.= VIRTUALPAGECNT has the AUTOGEN, GEN, and MAJOR attributes. 2 VMS1-8= VMSD1, VMSD2, VMSD3, VMSD4, VMS5, VMS6, VMS7, and VMS8 areC special parameters reserved for VSI use. VMSD1 through VMSD4 are DYNAMIC. 2 VOTESB VOTES establishes the number of votes an OpenVMS Cluster member" system contributes to a quorum.# VOTES has the AUTOGEN attribute. 2 WBM_MSG_INTC WBM_MSG_INT is one of three system parameters that are available@ for managing the update traffic between a master write bitmapB and its corresponding local write bitmaps in an OpenVMS Cluster@ system. The o thers are WBM_MSG_UPPER and WBM_MSG_LOWER. These@ parameters set the interval at which the frequency of sendingD messages is tested and also set an upper and lower threshold thatB determine whether the messages are grouped into one SCS message or are sent one by one.> In single-message mode, WBM_MSG_INT is the time interval in> milliseconds between assessments of the most suitable writeD bitmap message mode. In single-message mode, the writes issued byB each remote node are,  by default, sent one by one in individual< SCS messages to the node with the master write bitmap. If= the writes sent by a remote node reach an upper threshhold? of messages during a specified interval, single-message mode% switches to buffered-message mode.> In buffered-message mode, WBM_MSG_INT is the maximum time aA message waits before it is sent. In buffered-message mode, the@ messages are collected for a specified interval and then sentC in one SCS message. During periods of increased message traffic,? grouping multiple messages to send in one SCS message to theD master write bitmap is generally more efficient than sending each message separately.C The minimum value of WBM_MSG_INT is 10 milliseconds. The maximumD value is -1, which corresponds to the maximum positive value that< a longword can represent. The default is 10 milliseconds.& WBM_MSG_INT is a DYNAMIC parameter. 2 WBM_MSG_LOWER; WBM_MSG_LOWER is one of three sys tem parameters that are= available for managing the update traffic between a master? write bitmap and its corresponding local write bitmaps in anB OpenVMS Cluster system. The others are WBM_MSG_INT and WBM_MSG_B UPPER. These parameters set the interval at which the frequency@ of sending messages is tested and also set an upper and lowerA threshold that determine whether the messages are grouped into* one SCS message or are sent one by one.B WBM_MSG_LOWER is the lower thre shold for the number of messagesD sent during the test interval that initiates single-message mode.@ In single-message mode, the writes issued by each remote nodeA are, by default, sent one by one in individual SCS messages to? the node with the master write bitmap. If the writes sent by? a remote node reach an upper threshhold of messages during a@ specified interval, single-message mode switches to buffered- message mode.A The minimum value of WBM_MSG_LOWER is 0 messages per interval.< The maximum value is -1, which corresponds to the maximum? positive value that a longword can represent. The default is 10.( WBM_MSG_LOWER is a DYNAMIC parameter. 2 WBM_MSG_UPPER; WBM_MSG_UPPER is one of three system parameters that are= available for managing the update traffic between a master? write bitmap and its corresponding local write bitmaps in anB OpenVMS Cluster system. The others are WBM_MSG_INT and WBM_MSG_B LOWER. These paramete rs set the interval at which the frequency@ of sending messages is tested and also set an upper and lowerA threshold that determine whether the messages are grouped into* one SCS message or are sent one by one.B WBM_MSG_UPPER is the upper threshold for the number of messages@ sent during the test interval that initiates buffered-messageC mode. In buffered-message mode, the messages are collected for a7 specified interval and then sent in one SCS message.A The minimum value of WBM_MSG_UPPER is 0 messages per interval.< The maximum value is -1, which corresponds to the maximum? positive value that a longword can represent. The default is 100 seconds.( WBM_MSG_UPPER is a DYNAMIC parameter. 2 WBM_OPCOM_LVLB WBM_OPCOM_LVL controls whether write bitmap system messages areA sent to the operator console. Possible values are shown in the following table: Value Description! 0 Messages are turned off.B 1 The default; messages are provided when write bitmaps are@ started, deleted, and renamed, and when the SCS message+ mode (buffered or single) changes.? 2 All messages for a setting of 1 are provided plus many more.( WBM_OPCOM_LVL is a DYNAMIC parameter. 2 WINDOW_SYSTEM? WINDOW_SYSTEM specifies the windowing system to be used on a4 workstation. Specify one of the following values: Value Description; 1 Load the DECwindows Motif for OpenVMS workstation environment./ 2 Load the UIS workstation environment.( WINDOW_SYSTEM is a DYNAMIC parameter. 2 WLKSYSDSK= (Alpha and Integrity servers) WLKSYSDSK is used by variousA bootstrap components to determine if the system disk should be? treated as though it is write-locked. This parameter is used0 primarily to allow OpenVMS to boot from a CD. 2 WPRE_SIZE> WPRE_SIZE represents the number of pages to be allocated toC accommodate WatchPoint Recovery Entries (WPRE) on the Watchpoint Driver.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so.$ WPRE_SIZE is a DYNAMIC parameter. 2 WPTTE_SIZEC WPTTE_SIZE is the number of entries that the WPDRIVER creates in the WatchPoint Trace Table.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so.% WPTTE_SIZE is a DYNAMIC parameter. 2 WRITABLESYS= WRITABLESYS controls whether system code is writable. This= parameter is set (value of 1) for debugging purposes only.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 WRITESYSPARAMS@ On Alpha and Integrity servers, WRITESYSPARAMS indicates that@ parameters are modified during SYSBOOT and are written out to" ALPHAVMSSYS.PAR by STARTUP.COM.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so.) WRITESYSPARAMS is a DYNAMIC parameter. 2 WSDEC? Increasing the value of this parameter tends to increase theB speed with which working set limits are decreased when the need arises.@ On Alpha and Integrity servers, WSDEC specifies the number of@ pagelets by which the limit of a working set is automaticallyC  decreased at each adjustment interval (which is quantum end). AtD a setting of 35, for example, the system decreases the limit of a? working set by 35 pagelets each time a decrease is required.8 WSDEC has the AUTOGEN, DYNAMIC, and MAJOR attributes. 2 WSINCC Decreasing the value of this parameter tends to reduce the speedD with which working set limits are increased when the need arises.C Normally, you should keep this parameter at a high value because> a rapid inc rease in limit is often critical to performance.@ On Alpha and Integrity servers, WSINC specifies the number of@ pagelets by which the limit of a working set is automaticallyC increased at each adjustment interval (which is quantum end). AtC a setting of 150, for example, the system increases the limit ofC a working set by 150 pagelets each time an increase is required.A On Alpha and Integrity servers, the default value is 2400 512-B byte pagelets (150 8192-byte Alpha and Integrity server pages).> A value of 0 for WSINC disables the automatic adjustment ofB working set limits for all processes. Limits stay at their base> values. You can disable the automatic adjustment of workingA set limits on a per-process basis by using the DCL command SET WORKING_SET.; WSINC has the DYNAMIC and MAJOR attributes. On Alpha and; Integrity servers, WSINC also has the AUTOGEN attribute. 2 WSMAXC WSMAX sets the maximum number of pages on a systemwide basis forB any working set. WSMAX is calculated by AUTOGEN as a quarter ofB the first gigabyte plus a decreasing amount for each additional? gigabyte up to a maximum value of 3002368 pagelets, like so: Memory WSMAX 512 MB 262144 1 GB 524288 2 GB 768432 4 GB 1091584 8 GB 1421312 16 GB 1763328 32 GB 2105344 64 GB 2435072 128 GB 2740224 256+ GB 3002368? Note: Reserved memory is excluded. WSMAX units are pagelets.A This is intended to assist managers of systems that host largeC numbers of users whose working sets are not large. Systems whose? user bases consist of a small number of users (or processes)> that require large amounts of physical memory (for example,; simulations) might need to set MIN_WSMAX to a value that1 satisfies the requirements of those processes.4 WSMAX has the AUTOGEN, GEN, and MAJOR attributes. 2 XQPCTL2> X QPCTL2 controls improved concurrency. The default value of= XQPCTL2 is 1, which turns on improved concurrency. Setting> XQPCTL2 to 0 turns off improved concurrency. This parameter9 affects local access to the extent and file ID caches.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 XQPCTLD1; XQPCTLD1 controls multithreading, which can be used only< by PATHWORKS servers. The default  value of XQPCTLD1 is 8,? which enables multithreading. Setting XQPCTLD1 to 0 disables multithreading,D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 ZERO_LIST_HIC (Alpha and Integrity servers) ZERO_LIST_HI is the maximum number@ of pages zeroed and put on the zeroed page list. This list isD used as a cache of pages containing all zeros, which improves the( performance of alloca ting such pages.7 ZERO_LIST_HI has the AUTOGEN and DYNAMIC attributes.G! ********************************************************************* ! PARAM-ENDG! End of help on SYSGEN parameters. Please leave this marker in place.F! It is required to permit the parameters help text to be removed from,! this file and made part of the SYSMAN helpG! *********************************************************************ww