% Librarian T09-20]T7?Jg/ 8?J5 AUTOCONFIGURE  CONFIGUREdCONNECTCREATE  DEINSTALL$$DISABLE$$ENABLE%`INSTALL&LOAD)$RELOAD*`SET1JSHARE: SHOWjRSYSGENkSys_Parameters2TERMINALZUSE <WRITEoP)j1 AUTOCONFIGURE: On VAX systems, automatically connects devices that are@ physically attached to the system and loads their drivers. On: Alpha systems, use the SYSMAN command IO AUTOCONFIGURE.B Use of the AUTOCONFIGURE command requires the CMKRNL privilege. Format AUTOCONFIGURE adapter-spec AUTOCONFIGURE ALL 2 Parameter adapter-spec> Specifies the adapter specification (backplane interconnectC arbitration line) or slot n umber of the single UNIBUS or MASSBUSB adapter that is to be configured. The adapter specification canD be expressed as an integer or with one of the names listed by the SYSGEN command SHOW/ADAPTER.> You can specify AUTOCONFIGURE ALL to configure all standard" devices attached to the system.' CAUTIONB If you use the AUTOCONFIGURE ALL command on a running system= with active UNIBUS or Q-bus devices, it could result in unpredictable behavior. 2 Qualifiers /EXCLUDE" /EXCLUDE=(device-name[,...])@ Specifies the device types that you do not want automatically configured.B You can specify a device-type code as shown in the table listed< under the /SELECT qualifier. You can include a controllerC designation but not a unit number. If the controller designationB is omitted, all devices of the specified type are excluded. TheD device-name specification defaults to all devices on the adapter.8 Do not use this qualifier with the /SELECT qualifier. /LOG< Produces a display of the controller and its units on the> current SYS$OUTPUT device after they have been successfully? autoconfigured. Each controller and its associated units areD displayed only after AUTOCONFIGURE has found the next controller.C Therefore, the error message displays precede the display of the. controller and units that caused the error. /SELECT! /SELECT=(device-name[,...])9 Specifies the device types that you want automatically configured.? You can specify a device-type code as shown in the followingA table. You can include a controller designation but not a unitC number. If the controller designation is omitted, all devices ofA the specified type are selected. The device-name specification* defaults to all devices on the adapter.2 Do not use /SELECT with the /EXCLUDE qualifier. Device Type Codes Code Device Type CR Card Reader" CS Console Storage Device DB RP05, RP06 Disk DD TU58 Cartridge Tape DJ RA60 Disk DL RL02 Cartridge Disk% DM RK06, RK07 Cartridge Disk) DQ RL02 Cartridge Disk, R80 Disk' DR RM03, RM05, RM80, RP07 Disk DU UDA Disk DX RX01 Diskette DY RX02 Diskette5 LA LPA11-K Laboratory Peripheral Accelerator! LC Line Printer on DMF32 LP Line Printer on LP11 MB Mailbox MF TU78 Magnetic Tape MS TS11 Magnetic Tape* MT TE16, TU45, TU77 Magnetic Tape MU Tape Class Driver1 NET Network Communications Logical Device NL System "Null" Device OP Operator's Console! PA Computer Interconnect PT TU81 Magnetic Tape PU UDA-50 RT Remote Terminal( TT Interactive Terminal on DZ11A TX Interactive Terminal on DMF32, DMZ32 , DHU11, or DMB320 XA DR11-W General-Purpose DMA Interface2 XD DMP-11 Synchronous Communications Line" XF DR32 Interface Adapter1 XG DMF32 Synchronous Communications Line! XI DR Interface on DMF321 XJ DUP11 Synchronous Communications Line1 XM DMC11 Synchronous Communications Line 2 Examples 1.SYSGEN> AUTOCONFIGURE ALL@ This command automatically configures all standard devices.1 2.SYSGEN> AUTOCONFIGURE ALL/S ELECT=(TT,MTA,LP)= This command automatically configures all terminals, all@ magnetic tape units on controller A, and all line printers.) 3.SYSGEN> AUTOCONFIGURE ALL/EXCLUDE=XM< This command shows the use of the /EXCLUDE qualifier toB autoconfigure all but the DMC11 devices, assuming DECnet will% not be operating on this system. ww0j 1 CONFIGUREB On VAX systems, requests UNIBUS device names and issues the setA of control and status register (CSR) and vector addresses that AUTOCONFIGURE will use. Format CONFIGURE 2 Parameters None. 2 Qualifiers /INPUT /INPUT=file-spec< Specifies the name of an input file from which previously= prepared data is read. By default, input data is read from SYS$INPUT. /OUTPUT /OUTPUT=file-spec< Specifies the name of an output file to which output from: CONFIGURE is written. By default, output is directed to- SYS$OUTPUT. The default file type is .LIS. /RESET /RESET /NORESET< Controls whether controller names are reset. The /NORESET= qualifier is useful with multiple UNIBUS systems. When youD specify /NORESET, you do not need to specify the second parameter? (p) on subsequent CONFIGURE commands, because the controller= names are not reset. By default, if you omit /NORESET, the controller names are reset. 2 Description5 The CONFIGURE command issues the following prompt: DEVICE>C Input should be in the following form, where input to the prompt is controller: controller[[,n],p]D You can optionally specify n, the number of devices on the UNIBUSA being configured, and p, the optional number of devices on allA previous UNIBUS devices in a multiple UNIBUS system. Note thatC p affects only the device names, not the addresses generated. By default, n is 1 and p is 0.A SYSGEN continues to prompt for devices until you enter Ctrl/Z.D SYSGEN then displays the CSR and vector addresses for the devices specified.; Note that CONFIGURE does not look at the actual hardwareB configuration of the system. Rather, CONFIGURE determines whichD CSR and vector addresses AUTOCONFIGURE would use if the specified hardware was installed. 2 Example SYSGEN> CONFIGURE DEVICE> DZ11,3,2 DEVICE> LP11 DEVICE> DMC11,2 DEVICE> , The system displays the followi ng data:K Device: RK611 Name: DMA CSR: 777440 Vector: 210 Support: yesK Device: LP11 Name: LPA CSR: 777514 Vector: 200 Support: yesK Device: DMC11 Name: XMA CSR: 760070* Vector: 300* Support: yesK Device: DMC11 Name: XMB CSR: 760100* Vector: 310* Support: yesK Device: DZ11 Name: TTC CSR: 760120* Vector: 320* Support: yesK Device: DZ11 Name: TTD CSR: 760130* Vector: 330* Support: yesK Device: DZ11 Name: TTE CSR: 760140* Vector: 340* Support: yes& * Indicates a floating address.A In this example, the CONFIGURE command calculates the UNIBUS? CSR and vector addresses. The support field in the displayD indicates whether Compaq includes the supported driver for this& device with the operating system. ww/x2j 1 CONNECT; On VAX systems, creates I/O data base control blocks forA additional devices. Also loads the appropriate driver if it is@ not currently loaded. This is usually used to add nonstandard; devices and I/O drivers to a system. Requires the CMKRNL privilege.7 On Alpha systems, use the SYSMAN command IO CONNECT. FormatE CONNECT device-name/[NO]ADAPTER=adapter-spec/CSR=aaaa/VECTOR=nn CONNECT CONSOLE [/REMOTE] 2 Parameters device-nameC Specifies the name of the device for which control blocks are to> be added to the I/O database, and has the following format: devcu where: dev is the device-type c is the controller u is the unitD For example, LPA0 specifies the line printer (LP) on controller AC at unit number 0. When specifying the device name, do not follow it with a colon (:). CONSOLEB Loads and connects the console block storage device driver. TheB console device name is typically CSA1 but can vary depending on the system type. 2 Qualifiers /ADAPTER  /ADAPTER=adapter-spec /NOADAPTERC Specifies the nexus number (SBI arbitration line) or slot number= of the adapter to which the device is connected. The nexus? number can be found by using the SYSGEN command SHOW/ADAPTER or SHOW/BUS.= /NOADAPTER specifies that the I/O driver does not handle a@ physical device, rather it is a pseudo or test device driver.' CAUTION@ The system does not perform complete error checking on the? CONNECT/ADAPTER=adapter-spec command. An incorrect vector@ address or misspelled device name, for example, can damage= the I/O database and usually causes the system to fail.@ The OpenVMS VAX Device Support Manual has more information@ about loading device drivers and connecting devices. (This> manual has been archived but is available on the OpenVMS Documentation CD-ROM.) /ADPUNIT /ADPUNIT=unit-number@ Specifies the unit number of a device on the MASSBUS adapter.D The unit number for a disk drive is the number of the plug on theB drive. For magnetic tape drives, the unit number corresponds to the tape controller's number. /CSR /CSR=csr-addrD Specifies the UNIBUS address of the first addressable location onD the controller (usually the status register) for the device. ThisA qualifier must be specified for UNIBUS devices. For devices onD multiple device boards (for example, the DMF32), the address mustD be the control and status register (CSR) address specified in theC output of the CONFIGURE command. To specify the address in octalC or hexadecimal, precede the address with %O or %X, respectively. /CSR_OFFSET /CSR_OFFSET=value> For devices on multiple device boards, specifies the offset? from the CSR address of the multiple device board to the CSRB address for the specific device being connected. To specify theB address in octal or hexadecimal, precede the address with %O or %X, respectively. /DRIVERNAME /DRIVERNAME=driverD Specifies the name of the driver as recorded in the prolog table.? If the driver has not been loaded, the system acts as if theA driver name is also the name of an executable image (file typeC .EXE) in the SYS$LOADABLE_IMAGES directory and loads the driver.> The driver name defaults to the first two characters of theB device name concatenated with "DRIVER" (for example, LPDRIVER). /MAXUNITS /MAXUNITS=max-unit-cntC Specifies the maximum number of units the controller can supportD (that is, the number of UCB slots in the IDB). The default is theB number specified in the prolog table of the driver, or 8 if the/ number is not specified in the prolog table. /NUMVEC /NUMVEC=vector-cnt? Specifies the number of interrupt vectors for the device. By" default, the vector count is 1. /REMOTED Enables a remote diagnostic port for a second console or terminal connected to a VAX 8600. /SYSIDHIGH /SYSIDHIGH=value8 Specifies the high-order 16 bits of the 48-bit system< identification number and must be 0. To specify the value< in octal or hexadecimal, precede the value with %O or %X, respectively. /SYSIDLOW /SYSIDLOW=value7 Specifies the low-order 32 bits of the 48-bit systemC identification number. The value must be identical to the DECnet= node number. To specify the value in octal or hexadecimal,1 precede the value with %O or %X, respectively. /VECTOR /VECTOR=vector-addr? Specifies the UNIBUS address of the interrupt vector for the= device or the lowest vector, if more than one exists. ThisA qualifier must be specified for UNIBUS devices. For devices onD multiple device boards (for example, the DMF32), the address must@ be the interrupt vector address for the multiple device boardC specified in the output of the CONFIGURE command. To specify theB address in octal or hexadecimal, precede the address with %O or %X, respectively. /VECTOR_OFFSET /VECTOR_OFFSET=valueC For devices on multiple device boards, specifies the offset fromC the interrupt vector address of the multiple device board to theD interrupt vector address for the specific device being connected.> To specify the address in octal or hexadecimal, precede the' address with %O or %X, respectively. 2 Examples2 1.SYSGEN> CONNECT LPA0/ADAPTER=3/CSR=%O777514 -/ SYSGEN> /DRIVERNAME=LP2DRIVER/VECTOR=%O200D This command connects the device named LPA0 to the driver named@ LP2DRIVER and loads the driver if it is not already loaded.3 2.SYSGEN> CONNECT NET/NOADAPTER/DRIVER=NETDRIVER= This command connects the device named NET to the driver@ NETDRIVER and loads the driver if it is not already loaded. wwO:j 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 contiguousA (/CONTIGUOUS) or contiguous-best-try (/NOCONTIGUOUS). You mus tC specify /NOCONTIGUOUS, which is the default, if you are creatingD a secondary page or swap file that spans volumes in a 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 th!e 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;j 1 DEINSTALL= Deinstalls a page or swap file. Requires CMKRNL privi "lege.< Any file installed with the SYSGEN command INSTALL can be deinstalled.B If the specified file is being actively 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 d%#isplay. 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]PAGEF %ILE.SYS /PAGEFILE ww/>j 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/>j 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/>j 1 INSTALL< Installs 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 ww3@j1 LOADA On VAX systems, loads( an I/O driver. On Alpha systems, use the SYSMAN command IO LOAD.9 Use of the LOAD command requires the CMKRNL privilege. Format LOAD file-spec 2 Parameter file-spec= Specifies the file specification of the driver image to be& loaded. This parameter is required.C If the entire file specification is the same as that of a driver= already loaded, no load takes place. If only the file name? is the same as that of a driver already loaded (but) the fileA specification is different), the driver specified replaces the= driver previously specified; that is, the existing driver.! The default file type is .EXE. 2 Description@ Refer to the OpenVMS VAX Device Support Manual for a completeB description of the LOAD command. (This manual has been archived9 but is available on the OpenVMS Documentation CD-ROM.) 2 Example# SYSGEN> LOAD SYS$SYSTEM:RTTDRIVERB This command loads the standard driver for *a remote terminal. wwoAj 1 RELOAD= On VAX systems, replaces a loaded device driver with a new version.; Use of the RELOAD command requires the CMKRNL privilege. Format RELOAD file-spec 2 Parameter file-specC The file specification of the new driver image. The default file? type is .EXE. The specified image is loaded and replaces any4 existing driver with the same file specification. 2 Qualifiers None.+ 2 Description@ Refer to the OpenVMS VAX Device Support Manual for a completeD description of the RELOAD command. (This manual has been archived9 but is available on the OpenVMS Documentation CD-ROM.) 2 Example% SYSGEN> RELOAD SYS$SYSTEM:RTTDRIVER5 This command reloads the remote terminal driver. wwoAj1 SETA Assigns a value to a system parameter in the SYSGEN work area.C This command does not modify parameter files, the current s,ystem@ 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 parameterA specified in the last SET or SHOW command. See the descriptionC of the SHOW [parameter] 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 default8 values for any parameter with the SYSGEN command SHOW [parameter].: 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 as/signs 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 0file 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 (including> the SPECIAL parameters reserved for Compaq use) and their values. 2 /STARTUP= Names the site-independent startup command procedure to be< associated with a parameter f1ile 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 c2urrent0 site-independent startup command procedure. wwDj1 SHAREB On VAX systems, connects a processor to a multiport memory unitC already initialized by this or another processor. The number andB name of the specified multiport memory unit must be those of an3 initialized unit, or an error condition results.: Use of the SHARE command requires the CMKRNL privilege. Format SHARE MPMn MPM-name 2 Parameters MPMnB Spe3cifies the number on the front panel of the multiport memory unit being connected. MPM-nameD Specifies the name of the multiport memory unit as indicated in a% previous SHARE/INITIALIZE command. 2 Qualifiers /MAXCEFCLUSTERS /MAXCEFCLUSTERS=max-cef= Specifies the maximum number of common event flag clustersB that the processor can create in the multiport memory unit. The default is no limit. /MAXGBLSECTIONS /MAXGBLSECTIONS=ma4x-gbl; Specifies the maximum number of global sections that theA processor can create in the multiport memory unit. The default is no limit. /MAXMAILBOXES /MAXMAILBOXES=max-mail> Specifies the maximum number of mailboxes the processor can@ create in the multiport memory unit. The default is no limit. 2 Example SYSGEN> SHARE MPM1 SHR_MEM_1> This command connects a multiport memory unit. Because noD qualifiers are specified, defaults appl5y to all the parameters.B The unit with a 1 on the front panel must be initialized with0 the name SHR_MEM_1 for the command to work. 2 /INITIALIZEC On VAX systems, initializes a multiport memory unit and connects2 it to the processor on which SYSGEN is running.: Use of the SHARE/INITIALIZE command requires the CMKRNL privilege. Format$ SHARE/INITIALIZE MPMn MPM-name 3 Parameters MPMnB Specifies the number on the front panel of th6e multiport memory unit being connected. MPM-name; Specifies the name by which the multiport memory unit is= to be known to systems using it. The MPM-name is a 1 to 15B alphanumeric character string that may contain dollar signs ($) and underscores (_). 3 Qualifiers /CEFCLUSTERS /CEFCLUSTERS=cef; Specifies the total number of common event flag clusters> permitted in the multiport memory unit. The cef value is an integer with a default 7of 32. /GBLSECTIONS /GBLSECTIONS=gblA Specifies the total number of global sections permitted in theD multiport memory unit. The gbl value is an integer with a default of 32. /MAILBOXES /MAILBOXES=mail; Specifies the total number of mailboxes permitted in the= multiport memory unit. The mail value is an integer with a default of 32. /MAXCEFCLUSTERS /MAXCEFCLUSTERS=max-cef= Specifies the maximum number of common event 8flag clustersB that the processor can create in the multiport memory unit. The default is no limit. /MAXGBLSECTIONS /MAXGBLSECTIONS=max-gbl; Specifies the maximum number of global sections that theA processor can create in the multiport memory unit. The default is no limit. /MAXMAILBOXES /MAXMAILBOXES=max-mail> Specifies the maximum number of mailboxes the processor can@ create in the multiport memory unit. The default is no limit. 9 /POOLBCOUNT /POOLBCOUNT=block-cntC Specifies the number of blocks allocated to the multiport memory@ unit's dynamic pool. The block-cnt value is an integer with a default of 128. /POOLBSIZE /POOLBSIZE=block-sizeC Specifies the size of each block in the dynamic pool. The block-8 size value is an integer with a default of 128 bytes. /PRQCOUNT /PRQCOUNT=prq-cnt? Specifies the number of interprocessor request blocks (PRQs)C a:llocated. The prq-cnt value is an integer with a default of 64. 3 DescriptionD If the specified multiport memory unit is already initialized andC connected to other active processors, the gbl, mail, cef, block-A cnt, block-size, and prq-cnt parameter values are ignored, and1 the unit is simply connected to the processor. 3 Example+ SYSGEN> SHARE MPM1 SHR_MEM_1/INITIALIZE -5 SYSGEN> /GBLSECTIONS=128/MAILBOXES=64/CEFCLUSTERS=0C This command initializes a mu;ltiport memory unit with defaultsC on all but the gbl, mail, and cef parameters. In this example,> assume that the number of the multiport memory unit as it? appears on the front panel is 1, and the unit name is SHR_ MEM_1. ww/Jj1 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 parameter? specified in the last SET parameter-name or SHOW [parameter] command. 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 add=resses 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. /JOB9 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. /PQL9 Specifies that al!?l PQL parameter values are displayed. /RMS9 Specifies that all RMS parameter values are displayed. /SCS9 Specifies that all SCS parameter values are displayed. /SPECIALB Specifies that all parameter values reserved for Compaq 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> Spe@cifies 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 Description< A 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 firstB parameter matching the abbreviation is selected for display. NoB ambiguity checks are made. On an Alpha platform, all parameters6 whose names match the abbreviation will be printed.B For example, a specification of SHOW GBL on a VAX displays onlyA the GBLSECTIONSB parameter. To display the GBLPAGFIL parameter,A you must specify SHOW GBLPAGF (to avoid further ambiguity withB the GBLPAGES parameter). On an Alpha, the same SHOW GBL command5 will display 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 SET. parameter-name or SHOW [parameter] command. 2 Examples 1.SYSGEN> SHOW GBLSECTIONSH GBLSECTIONS C 100 40 20 -1 Sections SYSGEN> SET . 110 SYSGEN> SHOW .H GBLSECTIONS 110 40 20 -1 Sections? In this example, the user first displays the values of theB GBLSECTIONS parameter and then refers to the parameter with aB period to set its current value to 110. The next SHOW commandB also uses the period notation to obtain confirmation that the change occurred. 2.SYSGEN> SHOW/ACP> On Da VAX system, the command in this example produces the following output:Parameters in use: ActiveNParameter Name Current Default Minimum Maximum Unit DynamicNACP_MULTIPLE 0 1 0 1 Boolean DHACP_SHARE 1 1 0 1 BooleanNACP_MAPCACHE 52 8 1 -1 Pages DNACP_HDRCACHE 138 128 2 -1 Pages DNACEP_DIRCACHE 138 80 2 -1 Pages DNACP_DINDXCACHE 37 25 2 -1 Pages DNACP_WORKSET 0 0 0 -1 Pages DNACP_FIDCACHE 64 64 0 -1 File-Ids DNACP_EXTCACHE 64 64 0 -1 Extents DNACP_EXTLIMIT 300 300 0 1000 Percent/10 DNACP_QUOCACHE F 130 64 0 -1 Users DNACP_SYSACC 4 8 0 -1 Directories DNACP_MAXREAD 32 32 1 64 Blocks DNACP_WINDOW 7 7 1 -1 Pointers DNACP_WRITEBACK 1 1 0 1 Boolean DNACP_DATACHECK 2 2 0 3 Bit-mask DNACP_BASEPRIO 8 8 4 G 31 Priority DNACP_SWAPFLGS 14 15 0 15 Bit-mask DHACP_XQP_RES 1 1 0 1 BooleanHACP_REBLDSYSD 0 1 0 1 Boolean 3.SYSGEN> SHOW/ACP/HEXB The command in this example produces a hexadecimal display of9 the values of the ACP system parameters, as follows:Parameters in use: ActiveNParameter Name Current Default Minimum MaximHum Unit DynamicNACP_MULTIPLE 00000000 00000001 00000000 00000001 Boolean DHACP_SHARE 00000001 00000001 00000000 00000001 BooleanNACP_MAPCACHE 00000034 00000008 00000001 FFFFFFFF Pages DNACP_HDRCACHE 0000008A 00000080 00000002 FFFFFFFF Pages DNACP_DIRCACHE 0000008A 00000050 00000002 FFFFFFFF Pages DNACP_DNDXCACHE 00000025 00000019 00000002 FFFFFFFF Pages DNACP_WORKSET I 00000000 00000000 00000000 FFFFFFFF Pages DNACP_FIDCACHE 00000040 00000040 00000000 FFFFFFFF File-Ids DNACP_EXTCACHE 00000040 00000040 00000000 FFFFFFFF Extents DNACP_EXTLIMIT 0000012C 0000012C 00000000 000003E8 Percent/10 DNACP_QUOCACHE 00000082 00000040 00000000 FFFFFFFF Users DNACP_SYSACC 00000004 00000008 00000000 FFFFFFFF Directories DNACP_MAXREAD 00000020 0000J0020 00000001 00000040 Blocks DNACP_WINDOW 00000007 00000007 00000001 FFFFFFFF Pointers DNACP_WRITEBACK 00000001 00000001 00000000 00000001 Boolean DNACP_DATACHECK 00000002 00000002 00000000 00000003 Bit-mask DNACP_BASEPRIO 00000008 00000008 00000004 0000001F Priority DNACP_SWAPFLGS 0000000E 0000000F 00000000 0000000F Bit-mask DHACP_XQP_RES 00000001 00000001 00000000 00000001 B KooleanHACP_REBLDSYSD 00000000 00000001 00000000 00000001 Boolean 4.SYSGEN> SHOW/PQLA On an Alpha system, the command in this example produces the following output:Parameters in use: ActivePParameter Name Current Default Min. Max. Unit DynamicP-------------- ------- ------- ------- ------- ---- -------MPQL_DASTLM 24 24 -1 -1 Ast DMPQL_MASTLM L 4 4 -1 -1 Ast DMPQL_DBIOLM 32 32 -1 -1 I/O DMPQL_MBIOLM 4 4 -1 -1 I/O DMPQL_DBYTLM 65536 65536 -1 -1 Bytes DMPQL_MBYTLM 1024 1024 -1 -1 Bytes DMPQL_DCPULM 0 0 -1 -1 10Ms DMPQL_MCPULM 0 0 -1 M -1 10Ms DMPQL_DDIOLM 32 32 -1 -1 I/O DMPQL_MDIOLM 4 4 -1 -1 I/O DMPQL_DFILLM 128 128 -1 -1 Files DMPQL_MFILLM 2 2 -1 -1 Files DMPQL_DPGFLQUOTA 65536 65536 -1 -1 Pagelets DM internal value 4096 4096 0 -1 Pages DMPQNL_MPGFLQUOTA 2048 2048 -1 -1 Pagelets DM internal value 128 128 128 -1 Pages DMPQL_DPRCLM 32 32 -1 -1 Processes DMPQL_MPRCLM 0 0 -1 -1 Processes DMPQL_DTQELM 16 16 -1 -1 Timers DMPQL_MTQELM 0 0 -1 -1 Timers DIPQL_DWSDEFAULT O 2000 2000 -1 -1 PageletsF internal value 125 125 0 -1 PagesIPQL_MWSDEFAULT 2000 2000 -1 -1 PageletsF internal value 125 125 125 -1 PagesMPQL_DWSQUOTA 4000 4000 -1 -1 Pagelets DM internal value 250 250 0 -1 Pages DMPQL_MWSQUOTA 4000 4000 -1 -1 Pagelets DPM internal value 250 250 250 -1 Pages DMPQL_DWSEXTENT 12000 12000 -1 -1 Pagelets DM internal value 750 750 0 -1 Pages DMPQL_MWSEXTENT 4000 4000 -1 -1 Pagelets DM internal value 250 250 250 -1 Pages DMPQL_DENQLM 64 64 -1 -1 Locks DMPQL_MENQLM Q 4 4 -1 -1 Locks DMPQL_DJTQUOTA 1024 1024 -1 -1 Bytes DMPQL_MJTQUOTA 0 0 -1 -1 Bytes D 2 /ADAPTERC On VAX systems, displays all the nexus numbers and generic names on the adapter.A Use of the SHOW/ADAPTER command requires the CMEXEC privilege. Format SHOW/ADAPTER 3 Parameters None. 3 Qualifiers None. 3 ERxample SYSGEN> SHOW/ADAPTER> The following example is a sample display produced by the! SYSGEN SHOW/ADAPTER command: CPU Type: 11/780) Nexus Generic Name or Description) 1 16K memory, non-interleaved 3 UB0 8 MB0 9 MB1 2 /BUSC On VAX systems, displays all the nexus numbers and generic namesC on the adapter. On Alpha systems, use the SYSMAN command IO SHOW BUS.= Use of the SHOW/BUS c'Sommand requires the CMEXEC privilege. Format SHOW/BUS 3 Parameters None. 3 Qualifiers None. 2 /CONFIGURATION8 On VAX systems, displays information about the device configuration.< Use of the SHOW/CONFIGURATION command requires the CMEXEC privilege. Format SHOW/CONFIGURATION 3 Parameters None. 3 Qualifiers /ADAPTER /ADAPTER=nexus; Specifies the number of MASSBUS or UNIBUS adaTpters to be? displayed. The nexus value can be expressed as an integer or= with one of the generic names listed by the SYSGEN command SHOW/ADAPTER. /COMMAND_FILE9 Specifies that SYSGEN formats all the device data into@ CONNECT/ADAPTER=adapter-spec commands and writes the commandsA in an output file you specify. In this way, you can completelyA reconfigure a system for UNIBUS devices without the use of the SYSGEN command AUTOCONFIGURE. /OUTPUT U/OUTPUT=file-specB Specifies the file specification of an optional output file. If@ you specify the /OUTPUT qualifier but omit the file type, theA default is .LIS. However, if you specify the /COMMAND_FILE andD /OUTPUT qualifiers together, the default file type for the output file is .COM. 3 DescriptionB The SHOW/CONFIGURATION command shows devices by name, number ofC units, nexus number, and adapter type, as well as by control andA status register (CSR) and vecto Vr addresses. You can specify an* output file with the /OUTPUT qualifier.D Note that you can remove a device from the middle of the floating> addresses without completely redoing jumpers to the CSR and? vector addresses of the remaining devices by following these steps:A 1. Modify your site-independent STARTUP.COM file to invoke theB command file specified with the /OUTPUT qualifier instead of, entering an AUTOCONFIGURE ALL command.A 2. Enter the SHOW/CONFIGU WRATION/COMMAND_FILE/OUTPUT command toC format and save the device data. If you must bring the systemA down for service and remove a board, SYS$SYSTEM:STARTUP.COM> invokes your output file as a command procedure when theD system reboots, and the system automatically configures UNIBUS* devices and MASSBUS devices for you.; Remember that a new version of SYS$SYSTEM:STARTUP.COM is@ provided with each major release, so you would need to repeatB any modificationsX you have made to SYS$SYSTEM:STARTUP.COM after you install the new version.& NOTE? Although this technique can offer a convenient short-term4 solution, use AUTOCONFIGURE ALL when possible. 3 Examples 1.SYSGEN> SHOW/CONFIGURATION? This command displays the current system I/O database. The@ following example illustrates a typical display produced by1 this command on VS3100 and 6000-400 systems:9 System C YSR and Vectors on 23-OCT-2000 16:39:28.74- Name: OPA Units: 1 Nexus:0 (410)- Name: PKB Units: 1 Nexus:0 (410)- Name: TTA Units: 4 Nexus:0 (410)- Name: PKA Units: 1 Nexus:0 (410)- Name: ESA Units: 3 Nexus:0 (410)- Name: GCA Units: 1 Nexus:0 (410)9 System CSR and Vectors on 23-OCT-2000 16:31:47.12- Name: PAA Units: 1 Nexus:48 (CI )- Name: PAB Units: 1 Nexus:64 (CI )- Name: PA ZC Units: 1 Nexus:64 (CI )- Name: PAD Units: 1 Nexus:176 (CI )- Name: FXA Units: 2 Nexus:192 (GXM)- Name: ETA Units: 3 Nexus:213 (BVP)- Name: PAE Units: 1 Nexus:228 (CI )- Name: PBA Units: 1 Nexus:237 (BVP)- Name: TXA Units: 16 Nexus:211 (DMB)> 2.SYSGEN> SHOW/CONFIGURATION/COMMAND_FILE/OUTPUT=CONFIG.COM. This command formats all device data intoB CONNECT/ADAPTER=adapter-spec commands and writes the commands? [ to the command file CONFIG.COM. The following example is a3 typical command file produced by this command: $ RUN SYS$SYSTEM:SYSGEN AUTOCONFIGURE 4 AUTOCONFIGURE 5O CONNECT DMA0 /ADAP=8 /CSR=%O777440 /VECT=%O210 /NUMV=01 /DRIVER=DMDRIVERO CONNECT DMA1 /ADAP=8 /CSR=%O777440 /VECT=%O210 /NUMV=01 /DRIVER=DMDRIVERO CONNECT LPA0 /ADAP=8 /CSR=%O777514 /VECT=%O200 /NUMV=01 /DRIVER=LPDRIVERO CONNECT DYA0 /ADAP=8 /CSR=%O777170 /VECT=%O264 /NUMV=\01 /DRIVER=DYDRIVERO CONNECT DYA1 /ADAP=8 /CSR=%O777170 /VECT=%O264 /NUMV=01 /DRIVER=DYDRIVERO CONNECT XMA0 /ADAP=8 /CSR=%O760070 /VECT=%O300 /NUMV=02 /DRIVER=XMDRIVERO CONNECT XMB0 /ADAP=8 /CSR=%O760100 /VECT=%O310 /NUMV=02 /DRIVER=XMDRIVERO CONNECT XMC0 /ADAP=8 /CSR=%O760110 /VECT=%O320 /NUMV=02 /DRIVER=XMDRIVERO CONNECT TTA0 /ADAP=8 /CSR=%O760130 /VECT=%O330 /NUMV=02 /DRIVER=DZDRIVERO CONNECT TTA1 /ADAP=8 /CSR=%O760130 /VECT=%O330 /NUMV=02 /DRIVER=DZD]RIVERO CONNECT TTA2 /ADAP=8 /CSR=%O760130 /VECT=%O330 /NUMV=02 /DRIVER=DZDRIVER . . .O CONNECT TTF7 /ADAP=8 /CSR=%O760200 /VECT=%O400 /NUMV=02 /DRIVER=DZDRIVER 2 /DEVICEA On VAX systems, displays full information about device driversC loaded into the system, the devices connected to them, and theirC I/O databases. All addresses are in hexadecimal and are virtual.; On Alpha systems, use the SYSMAN command IO SHOW DEVICE.@ Use of the ^SHOW/DEVICE command requires the CMEXEC privilege. Format SHOW/DEVICE=device-driver 3 Parameters None. 3 Qualifiers None. 3 DescriptionC The SHOW/DEVICE command specifies that the following information2 be displayed about the specified device driver: Driver Name of the driver* Start Starting address of the driver( End Ending address of the driver7 Dev Name of each device connected to the driver5 DDB Address _of the device's device data block9 CRB Address of the device's channel request block< IDB Address of the device's interrupt dispatch block- Unit Number of each unit on the device5 UCB Address of each unit's unit control blockD By default, if you omit the driver name, information is displayed1 for all device drivers loaded into the system. 3 Example SYSGEN> SHOW/DEVICE=DBDRIVER> This command displays the following information about the ` DBDRIVER:P __Driver_____Start____End____Dev___DDB______CRB______IDB_____Unit__UCB___# DBDRIVER 80082390 80082A7EB DBA 80000848 800988C0 80098920O 0 8000087CO 1 8008A4F0O 2 8008A590O a 5 8008A630P 7 8008A6D00 2 /DRIVERB On VAX systems, displays the starting and ending address of the2 specified device driver loaded into the system. Format SHOW/DRIVER=device-driver 3 Parameters None. 3 Qualifiers None. 3 DescriptionA If you omit the driver name, SHOW/DRIVER displays the startingC and ending address of all device drivers loaded into thbe system.4 All addresses are in hexadecimal and are virtual.@ Use of the SHOW/DRIVER command requires the CMEXEC privilege.C The SHOW/DRIVER command displays the following information about the specified device driver:% Driver Name of the device driver1 Start Starting address of the device driver/ End Ending address of the device driver 3 Example SYSGEN> SHOW/DRIVERC This command displays the starting and ending addresses of all dcrivers, as follows:# __Driver_____Start____End___# RTTDRIVER 800C1060 800C1960# NETDRIVER 800BAFD0 800BD4B0# TMDRIVER 800B3950 800B4BF0# DRDRIVER 800B2950 800B3290# DDDRIVER 800B1740 800B2060# DLDRIVER 800B0D10 800B15A0# DMDRIVER 800B0070 800B0990# LCDRIVER 800AFC50 800AFFB0# YCDRIVER 800AED20 800AF3E0# XGDRIVER 800AC3F0 800AE9E0# XDDRIVER 800AA5A0 800AC380# DZDRIVER 800A4F30d 800A59B0# XMDRIVER 800A3E10 800A4A50# DYDRIVER 800A3300 800A3C30# LPDRIVER 800A2E90 800A3300# DBDRIVER 800DE7A0 800DEFB7# TTDRIVER 800DC770 800DE79B# OPERATOR 80001650 80001F8B# NLDRIVER 80001626 80001D20# MBDRIVER 800015FC 80001CBE 2 /STARTUPD Displays the name of the current site-independent startup command procedure. Format SHOW/STARTUP 3 Parameters None. 3 Qualifi#eers 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. 2 /TURBOCHANNEL? On VAX systems, displays the nexus number of a device on the TURBOchannel. Format SHOW/TURBOCHANNEL 3 Parameters None. 3 Qualifiers None. 3 Example SYSGEN> SHOW/TURBOCHANNEL> The following example is a sampfle display produced by the SHOW/TURBOCHANNEL command:B TURBOCHANNEL: Device Name Nexus Number TC SlotC PMAQT-AA 00000000 00000001 2 /UNIBUSB On VAX systems, displays the addresses in UNIBUS I/O space that can be addressed.@ Use of the SHOW/UNIBUS command requires the CMKRNL privilege. Format SHOW/UNIBUS 3 Parameters None. 3 Qualifier /ADAPTER /ADAPTER=nexusC g Specifies that the address of the specified UNIBUS adapter is toC be displayed. The nexus value specifies the number of the UNIBUSD adapter. It can be expressed as an integer or as one of the names- listed by the SYSGEN command SHOW/ADAPTER. 3 Description? The SHOW/UNIBUS command reads all device registers. For some> controllers, the result might be reading a character out of> a buffer or some other undesired action. Therefore, use theB SHOW/UNIBUS command only whenh you debug a UNIBUS configuration.C On a system with more than one UNIBUS adapter, the command shows0 only the address of the first UNIBUS adapter.& NOTE< Never use the SHOW/UNIBUS command on a running system.? Use of this command is valid only during a conversational bootstrap. 3 Example SYSGEN> SHOW/UNIBUS/ADAPTER=4B This command displays the available addresses for nexus 4, as follows:? **UNIBUS ma ip for nexus #4 on 30-JUN-2000 14:19:38.00 **? Address 760070 (8001F838) responds with value 9B6E (hex)? Address 760072 (8001F83A) responds with value 0340 (hex)? Address 760074 (8001F83C) responds with value 403C (hex)? Address 760076 (8001F83E) responds with value 0240 (hex)? Address 760100 (8001F840) responds with value 8000 (hex)? Address 760102 (8001F842) responds with value 0340 (hex)? Address 760104 (8001F844) responds with value 7DAC (h jex)? Address 760106 (8001F846) responds with value 000A (hex)? Address 760110 (8001F848) responds with value 8000 (hex)? Address 760112 (8001F84A) responds with value 0340 (hex)? Address 760114 (8001F84C) responds with value AD5C (hex)? Address 760116 (8001F84E) responds with value 000A (hex)? Address 760130 (8001F858) responds with value 9B6E (hex)? Address 760132 (8001F85A) responds with value 030D (hex)? Address 760134 (8001F85C) respoknds with value FF00 (hex)? Address 760136 (8001F85E) responds with value CECE (hex)? Address 760140 (8001F860) responds with value 4060 (hex)? Address 760142 (8001F862) responds with value 0761 (hex)? Address 760144 (8001F864) responds with value FF00 (hex) . . . ww5#j 1 SYSGEN @ The System Generation utility (SYSGEN) is a system managementD tool used to tailor a system for a specific hardware and softwarel 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 memory7 - On OpenVMS VAX systems, create and debug UNIBUS configurations# To obtain help on a topic, type:- HELP command [/qualifers or parameters] wwmj1 Sys_Parameters; Help is providemd 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 for 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 nfollowing 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 consistenc oy 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 fil pe 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.9 3 Reserved for Compaq use only; must be zero.9 4 Reserved for Compaq use only; must be zero.E 5 and 6 These two bits control the checks that are performed onB reads and writes of direct qory 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 1r 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 Wh sen 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.9 7 Reserved for Compaq 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 tempotrary 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 directoryA 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 FEuEDBACK 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 operations, 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 frvee 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.@ 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_FIDCA wCHE 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 is 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 excexssive 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 excessive 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_MAXRE yAD 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 a 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 proce zsses 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 and 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 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. If 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 u}sed, 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 enabled 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 usuall y 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 contains 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 provide sC 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 qualifierD 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 memory 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_WRITEBACK@ ACP_WRITEBACK enables writeback caching. The default value ofB ACP_WRITEBACK is 1, which enables writeback caching. To disable- writeback caching, set ACP_WRITEBACK to 0.D On ODS-2 disks, only PATHWORKS servers can use writeback caching.3 All other applications use writethrough caching.( 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 systems C with a small number of users and little or no file activity that@ requires XQP intervention. Such activity 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.= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq recommends that you do so. 2 AFFINITY_TIME@ AFFINITY_TIME controls the breaking of implicit affinity. TheC value indicates how long a process remains on the compute queue.= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq 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_SUPPORTC (Alpha only) The Access Rights Block (ARB) compatibility option,@ the ARB_SUPPORT system parameter, is provided specifically to? support products that have not yet been updated with the newC per-thread security Persona Security Block (PSB) data structure.A Changing the value of ARB_SUPPORT from 2 or 3 (the default) to> any other value can affect the operation of these products.& NOTE= Compaq recommends that all Version 7.3 systems have theA ARB_SUPPORT parameter set to 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 BehaviorA ISS$C_ARB_ 0 The obsolete kernel data cells are not? NONE maintained by the system. Fields areA initialized to zero (or set to invalid9 pointers) at process creation.= ISS$C_ARB_ 1 The obsolete kernel data cells are? CLEAR cleared (or set to invalid pointers)A when the code would have set up values6 for backward compatibility.> ISS$C_ARB_ 2 The obsolete cells are updated withD  READ_ONLY corresponding security information storedD in the current PSB when a $PERSONA_ASSUME% is issued.C ISS$C_ARB_ 3 (de- Data is moved from the obsolete cells toD FULL fault) the currently active PSB on any 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 makes the+ change to and from daylight saving time. 2 AWSMINC On VAX systems, AWSMIN establishes the lowest number of pages toB which a working set limit can be decreased by automatic working set adjustment.< On Alpha systems, AWSMIN establishes the lowest number of< pagelets to which a working set limit can be decreased by$ automatic working set adjustment.! 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 unitsC of 10 milliseconds. The default value of 20, for example, is 200 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 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 numb er of working sets in memory. IfB this number is significantly lower than the value of BALSETCNT,D this parameter value may be lowered. If all balance set slots are, being used, raise the 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 toB MAXPROCESSCNT, lowering BALSETCNT will force swapping to occur,A which can affect system performance. Note that virtual balanceD slots (VBS) can affect the values of BALSETCNT and MAXPROCESSCNT.5 BALSETCNT is an AUTOGEN, GEN, and MAJOR parameter. 2 BORROWLIM@ BORROWLIM defines the minimum number of pages required on theA free-page list before the system permits process growth 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 heavy 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.= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq recommends that you do so. 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 being 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 CHANNELCNT< CHANNELCNT specifies the number of permanent I/O channels available to the system.= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq recommends that you do so. 2 CHECK_CLUSTER> (VAX only) CHECK_CLUSTER is the VAXCLUSTER parameter sanityC check. When CHECK_CLUSTER is set to 1, SYSBOOT outputs a warningB message and forces a conversational boot if it detects that the$ VAXCLUSTER parameter is set to 0. 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 created 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 or MCR symbols that can be created.$ CLISYMTBL is a DYNAMIC parameter. 2 CLOCK_INTERVALD (VAX only) CLOCK_INTERVAL sets the number of microseconds betweenD the hardware interval timer clock interrupts. It has no effect onB processors that have implemented only the subset interval clock registers.= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq recommends that you do so. 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$VAXcluster 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.> It is not required for all nodes in the cluster to have theB same value for CLUSTER_CREDITS. For small or memory-constrainedD systems, the default value of CLUSTER_CREDITS should be adequate. 2 CONCEAL_DEVICESD CONCEAL_DEVICES enables or disables the use of concealed devices.@ By default, this parameter is set to enable concealed devices (1).= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq recommends that you do so. 2 CRD_CONTROL= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq recommends that you do so.B On VAX systems, CRD_CONTROL serves the function of CRDENABLE inA earlier releases. On Alpha systems, 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.2 On VAX systems, the following bits are defined: Bit Description0 0 Enables CRD processing for all systems.B 1 Enables scrubbing (rewriting) of the memory location that induced the CRD.D 2 Enables page replacement of the pages that exhibit repeated CRD errors.D 3 Forces all memory pages to be included in the PFN database.C On systems that contain more than 512 megabytes of memory,B all memory is mapped by the PFN database by default. ThisB bit allows the mapping to occur on systems with less than! 512 megabytes of memory.= Default values are different for VAX and Alpha systems. On? VAX systems, the default is 7, which enables CRD processing,# scrubbing, and page replacement.4 On Alpha systems, 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 memory 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.@ 24-31 Reserved for platform-specific error-handling control.= On Alpha systems, the default setting is 22, which enables@ CRD processing, scrubbing, page replacement, and extended CRD handling. 2 CRDENABLEC (Alpha only) CRDENABLE enables or disables detection and loggingD of memory-corrected read data (ECC) errors. This parameter should normally be set to (1).A Beginning with OpenVMS Version 7.2, CRD_CONTROL can expand the1 function of CRDENABLE. (Refer to 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.= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq 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.= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq 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_SCRATCH@ (Alpha only) DBGTK_SCRATCH specifies how many pages of memoryB are allocated for the remote debugger. This memory is allocated? only if remote debugging is enabled with the 8000 boot flag.= Normally, the default value is adequate, but if the remote= debugger issues an error message, you sho uld increase this@ value. See Writing OpenVMS Alpha Device Drivers in C for moreB information. (This manual has been archived but is available on% the OpenVMS Documentation CD-ROM.) 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 0 disables deadlock@ checking. Setting DEADLOCK_WAIT to a value greater than 0 butC still less than the default setting provides faster detection of) deadlocks but requires more CPU usage.( DEADLOCK_WAIT is a DYNAMIC parameter. 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 the 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 submitter.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 DEVICE_NAMINGC (Alpha only) DEVICE_NAMING is a bit mask 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.; 1 Must be 0. This bit is reserved for use by Compaq.B For more information about port allocation classes, see OpenVMS Cluster Systems. 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.= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq 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.& DISK_QUORUM is a DYNAMIC parameter. 2 DLCKEXTRASTKB (VAX only) DLCKEXTRASTK specifies the amount of extra interrupt: stack (in bytes) to leave when doing a deadlock search./ This parameter is not used on Alpha systems.= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq recommends that you do so. 2 DNVOSI1? DNVOSI1 is reserved to DECnet-Plus for OpenVMS. This special? parameter is used by Compaq and is subject to change. Do notA change this parameter unless Compaq recommends that you do so. 2 DORMANTWA ITA 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 purposes. (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 the* 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= 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. This 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 s ystem@ parameter is the sum of the values of the bits that have beenA set. Remaining or undefined values are reserved for Compaq use only.* Bit Mask Description? 0 00000001 0 = Full dump (SYSGEN default).C The entire contents of physicalB memory are written to the dump) file.C 1 = Selective dump. The co ntents ofB memory are written to the dump@ file selectively to maximizeC the usefulness of the dump file@ 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) toD an alternate disk. (Refer to theC OpenVMS System Manager's Manual1 for details.)4 3 (Alpha only) 00000008 0 = Do not compress.? 1 = Compress. (See note below.)A 4 - 14 Reserved for Compaq use only.@ 15 (VAX only) 00008000 0 = Disable use of bits 16 - 27.? 1 = Enable use of bits 16 - 27.? 16 - 27 (VAX 0FFF0000 Range of DOSD unit numbers. only)A 28 - 31 Reserved for Compaq use only.? Note that VAX systems do not support dump compression. Also,+ VAX-only bits are specific to VAX 7000s.B If you plan to enable the Volume Shadowing minimerge feature on@ an Al pha system disk, be sure to specify DOSD to an alternate disk.& NOTE= On Alpha systems, you can save space on the system diskB and, in the event of a crash, save time recording the systemB memory, by using the OpenVMS Alpha 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 12 8 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 selective 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.? On Alpha systems, the mask of 00000009 directs the system to9 compress a selective dump with minimal console output.0 DUMPSTYLE has AUTOGEN and DYNAMIC attributes. 2 ERLBUFFERPAGES@ ERLBUFFERPAGES specifies the amount of memory to allocate for: each buffer requested by the ERRORLOGBUFFERS parameter.D On VAX systems, ERLBUFFERPAGES has a default value of 2 pages and a maximum value of 32 pages.< On Alpha systems, ERLBUFFERPAGES has a default value of 4/ pagelets and a maximum value of 32 pagelets.D On Alpha systems, ERLBUFFERPAGES is an AUTOGEN-altered parameter. 2 ERRORLOGBUFFERS? ERRORLOGBUFFERS specifies the number of buffers reserved for= system error log entries. Each buffer is ERLBUFFERPAGES in? length. If ERRORLOGBUFFERS is too low, messages might not be= written to the error log file. If it is too high, unneeded; physical pages can be consumed by the error log buffers.C If you increase ERRORLOGBUFFERS, you must also increase the size of the system dump file. 2 EXPECTED_VOTESC EXPECTED_VOTES specifies the maximum number of votes that may 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 milliseconds, allotted toA each of a process's exit handlers (for each access mode) after? the process times out (that is, reaches its CPU time limit).- EXTRACPU is a DYNAMIC attribute parameter. 2 EXUSRSTK? EXUSRSTK specifies the amount of space provided by the image4 activator to recover from a stack overflow error.= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq recommends that you do so. 2 FAST_PATHC (Alpha only) FAST_PATH is a static system parameter that enablesA (1) or disables (0) the Fast Path 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.A For additional information, see FAST_PATH_PORTS and IO_PREFER_ CPUS. 2 FAST_PATH_PORTS: (Alpha only) FAST_PATH_PORTS is a static parameter that. deactivates Fast Path for specific drivers.A FAST_PATH_PORTS is a 32-bit mask. If the value of a bit in theC mask is 1, Fast Path is disabled for the driver corresponding toC that bit. A value of -1 specifies that Fast Path is disab led for; all drivers that the FAST_PATH_PORTS parameter controls.C Bit position zero controls Fast Path for PKQDRIVER (for parallel? SCSI), and bit position one controls Fast Path for FGEDRIVER@ (for Fibre Channel). Currently, the default setting for FAST_B PATH_PORTS is 0, which means that Fast Path is enabled for both PKQDRIVER and FGEDRIVER.# 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 zero; has the same effect as setting FAST_PATH_PORTS to -1.@ For additional information, see FAST_PATH and IO_PREFER_CPUS. 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 GALAXY> (Alpha Galaxy platforms only) The GALAXY parameter controlsB whether the specified instance participates in a Galaxy sharing% set. Specify one of the following: Value DescriptionC 0 Never load. Do not participate in a Galaxy sharing set.= 1 Always load. Participate in a Galaxy sharing set.> The default value is 0. GALAXY is not an AUTOGEN parameter. 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, plu s 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 maximum 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 requir ements 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 attri butes. 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 temporary, 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 a ccordingly. 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 global 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 se quential 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 buffering 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 SET= FILE/GLOBAL_BUFFERS, which is described in the OpenVMS DCL Dictionary.; GBLPAGFIL is an AUTOGEN-altered and a DYNAMIC 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 permanentl y 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 requirements 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 GH_EXEC_CODE? (Alpha only) GH_EXEC_CODE specifies the size in pages of the(  execlet code granularity hint region.8 GH_EXEC_CODE has the AUTOGEN and FEEDBACK attributes. 2 GH_EXEC_DATA? (Alpha only) GH_EXEC_DATA specifies the size in pages of the( execlet data granularity hint region.8 GH_EXEC_DATA has the AUTOGEN and FEEDBACK parameters. 2 GH_RES_CODE> (Alpha only) 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_DATA> (Alpha only) GH_RES_DATA specifies the size in pages of the/ resident image data granularity hint region.7 GH_RES_DATA has the AUTOGEN and FEEDBACK attributes. 2 GH_RSRVPGCNTC GH_RSRVPGCNT specifies the number of pages in the resident imageA 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 the granularity hin tC 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$WRAPUPC attempts to leave in the resident image granularity hint region.@ If the GH_RSRVPGCNT number of pages is larger than the unusedC pages in the granularity hint region, the region is not expanded0 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.3 The default is 20,000 milliseconds (20 seconds). 2 GLX_SHM_REGA For Galaxy systems, GLX_SHM_REG is the number of shar ed memoryC region structures configured into the Galaxy Management DatabaseC (GMDB). If set to 0, the default number of shared memory regions are configured. 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_ADDRESS0 IEEE_ADDRESS is reserved for Compaq use only. 2 IEEE_ADDRESSH1 IEEE_ADDRESSH is reserved for Compaq 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 for the image activator if not" specified at program link time.= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq recommends that you do so. 2 IMGREG_PAGESA (Alpha only) IMGREG_PAGES is the number of pages to reserve inC P1 space for images to be installed with shareable address data.C If IMGREG_PAGES is set to 0, no images are installed with shared- address data. The default is 10,000 pages.? For more information, see the INSTALL section in the OpenVMS0 System Management Utilities Reference Manual. 2 INTSTKPAGES> (VAX only) INTSTKPAGES sets the size of the interrupt stack@ in pages. Each page on the interrupt stack requires a page of permanently resident memory.> Use the default value of 6 unless interrupt-stack-not-valid? exceptions occur. These may be caused by either an unusuallyC large number of devices or a driver that requires a large amount of stack space.? INTSTKPAGES has AUTOGEN, DYNAMIC, GEN, and MAJOR attributes. 2 IO_PREFER_CPUSA (Alpha only) IO_PREFER_CPUS is a dynamic system parameter thatC controls the set of CPUs that are available for use as Fast Path preferred CPUs.@ IO_PREFER_CPUS is a CPU bit mask specifying the CPUs that areC allowed to serve as preferred CPUs and that can thus be assignedD a Fast Path port. CPUs whose bit is set in the IO_PREFER_CPUS bitA mask are enabled for Fast Path port assignment. IO_PREFER_CPUSB defaults to -1, which specifies that all CPUs are allowed to be assigned Fast Path ports.> You might want to disable the primary CPU from serving as a< preferred CPU by clearing its bit in IO_PREFER_CPUS. ThisC reserves the primary CPU for non-Fast-Path IO operations to use.B Changing the value of IO_PREFER_CPUS causes the FASTPATH_SERVER= process to execute the automatic assignment algorithm thatC spreads Fast Path ports evenly among the new set of usable CPUs.A For additional information, see FAST_PATH and FAST_PATH_PORTS. 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.= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq recommends that you do so. 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.= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq recommends that you do so. 2 KFILSTCNT@ KFILSTCNT is no longer used on VAX systems and is not used on Alpha systems. 2 KSTACKPAGESB (Alpha only) KSTACKPAGES controls the number of pages allocated for process kernel stacks. 2 LAMAPREGS? (VAX only) LAMAPREGS sets the number of UNIBUS map registers> allocated to an LPA11 driver when the driver is loaded, andA limits the registers for the driver to that number. A value ofD 0 permits dynamic allocation of an unlimited number of registers.# LAMAPREGS has the GEN attribute. 2 LAN_FLAGS? (Alpha only) LAN_FLAGS is a bit mask used to enable features@ in the local area networks port drivers and support code. The$ default value for LAN_FLAGS is 0.& The bit definitions are as follows: Bit DescriptionC Bit 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.@ Bit 1 If set, this bit enables a subset of the ATM traceD and debug messages in the LAN port drivers and support code.> Bit 2 If set, this bit enables all ATM trace and debug@ messages in the LAN port drivers and support code.B Bit 3 If set, this bit runs UNI 3.0 over all ATM adapters.B Bit 4 If set, this bit runs UNI 3.1 over all ATM adapters.A Bit 5 If set, disables autoconfiguration over all Gigabit Ethernet Adapters.> Bit 6 If set, enables the use of jumbo frames over all( Gigabit Ethernet Adapters.$ LAN_FLAGS is a DYNAMIC parameter. 2 LCKMGR_CPUIDD (Alpha only) The LCKMGR_CPUID parameter controls the CPU that the? Dedicated CPU Lock Manager runs on. This is the CPU that theA LCKMGR_SERVER process will utilize if you turn this feature on) with the LCKMGR_MODE system parameter.> If the specified CPU ID is either the primary CPU or a non-B existent CPU, the LCKMGR_SERVER process will utilize the lowest non-primary CPU.> For more information, see the LCKMGR_MODE system parameter.' LCKMGR_CPUID is a DYNAMIC parameter.2 LCKMGR_MODE? (Alpha only) The LCKMGR_MODE parameter controls usage of the> Dedicated CPU Lock Manager. Setting LCKMGR_MODE to a number? greater than zero (0) indicates the number of CPUs that 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.= For more information about usage of the Dedicated CPU Lock3 Manager, see the OpenVMS Performance Management. Specify one of the following: Value DescriptionA 0 Indicates the Dedicated CPU Lock Manager is off. (The default.) C >0 Indicates the number of CPUs that must be active before8 the Dedicated CPU Lock Manager is turned on.& 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 that 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 fail ed 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_TIMB 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 users 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 carr ier. 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 time A and number of opportunities to attempt logins before they lose the carrier.( LGI_RETRY_TMO is a DYNAMIC parameter. 2 LNMPHASHTBLD 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, unlessC 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_IMAGES= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq 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.0 On VAX systems, the following bit is defined:* Bit DescriptionA 0 (SGN$V_LOAD_SYS_IMAGES) Enables loading alternate execletsC specified in VMS$SYSTEM_IMAGES.DATA.4 On Alpha systems, 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 of4 the Alpha huge pages.D These bits are on by default. Using conversational bootstrap exec slicing can be disabled.= On Alpha systems, 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 d efault 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.C The OpenVMS Lock Management facility is described in the OpenVMS> Programming Concepts Manual. You can monitor locks with 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.= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq recommends that you do so. 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: systems, LONGWAIT is also an AUTOGEN-altered parameter. 2 LRPCOUNT> This parameter has been obsolete since OpenVMS Version 6.0. 2 LRPSIZE> This parameter has been obsolete since OpenVMS Version 6.0. 2  MAXBOBMEM@ (Alpha only) MAXBOBMEM defines the maximum amount of physical> memory, measured in pagelets, that can be associated with a> single buffer object created by a process in user mode. The? default value of 0 means there is no system-imposed limit on the size of a buffer object.$ MAXBOBMEM is a DYNAMIC parameter.@ Other MAXBOB* parameters are obsolete in 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.A On OpenVMS VAX systems beginning with Version 7.1, the default< value is 4112. The default value on OpenVMS Alpha systems 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.= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq 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 process: 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_P1B (Alpha only) This special parameter is reserved for Compaq use.> Its 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 clus ter port driver.= PMDRIVER is a new driver that serves as the MEMORY CHANNEL< cluster port driver. It works together with MCDRIVER (the@ MEMORY CHANNEL device driver and driver interface) to provide@ MEMORY CHANNEL clustering. If PMDRIVER is not loaded, clusterA connections are not made over the MEMORY CHANNEL interconnect.B The default value 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.C Compaq 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.B The default value is 800. Compaq 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.B The default value is 200. Compaq recommends that this value notA be changed. This parameter value must be the same on all nodes connected by MEMORY CHANNEL. 2 MC_SERVICES_P5B (Alpha only) MC_SERVICES_P5 is reserved for Compaq use only andB must remain at the default value of 8000000. This value must be5 the 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 maximum 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. Compaq 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_P8B (Alpha only) MC_SERVICES_P8 is reserved for Compaq use only andD must 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. Compaq 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.= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq recommends that you do so.& MINCLASSPRI is a DYNAMIC parameter. 2 MINPRPRI> This parameter is not used on OpenVMS VAX or Alpha systems. 2 MINWSCNT> The value specified by MINWSCNT is added to the size of the< process header to establish the minimum working set size.B On VAX systems, MINWSCNT sets the minimum number of fluid pagesC (pages not locked in the working set) required for the execution> of a process. The value of MINWSCNT must provide sufficientC space to execute any VAX instruction. Theoretically, the longestC instruction requires 52 pages; however, all code can run with 20D fluid pages. An insufficient value may inhibit system performanceD or even put a process into an infinite loop on some instructions.> On Alpha systems, 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_CTLFLAGSB MMG_CTLFLAGS is a bit mask used to enable and disable proactive@ memory reclamation mechanisms. Beginning with OpenVMS Version@ 7.2, you can control when memory is tested. This helps reduceC the time between when you turn on the system and when you log inC to an AlphaServer 4100 computer. Bit 2 in the parameter controls deferred memory testing.- The following bit mask values are defined: Bit Description; 0 Reclamation enabled by trimming from periodicallyC executing, but otherwise idle processes. This occurs whenC the size of the free list drops below two times FREEGOAL.@ 1 Re clamation enabled by outswapping processes that haveA been idle for longer than LONGWAIT seconds. This occurs= when the size of the free list drops below FREELIM.+ 2 Controls deferred memory testing:= o If the bit is clear (the default), OpenVMS tests@ memory in the background and not necessarily before1 the bootstrap process has completed.B o If the bit is set, all memory is tested by the end of@ EXEC_INIT in the system bootstrap process (that is,, before IPL is lowered from 31)." 3-7 Reserved for future use.4 MMG_CTLFLAGS is an AUTOGEN and DYNAMIC parameter. 2 MPDEV_D1= (Alpha only) MPDEV_D1 is reserved for use by the operating system. 2 MPDEV_ENABLE? (Alpha only) MPDEV_ENABLE enables the formation of multipath= sets when set to ON (1). If set to OFF (0), the formation> of additional multipath sets is disabled. However, existing6 multipath sets remain in effect. The default is ON. 2 MPDEV_LCRETRIES@ (Alpha only) MPDEV_LCRETRIES controls the number of times theC system retries locally connected paths before moving on to localA unconnected paths or to an MSCP served path to the device. The> valid range for retries is 1 through 256. The default is 1. 2 MPDEV_POLLER< (Alpha only) MPDEV_POLLER enables polling of the paths to< multipath set members when set to ON (1). Polling allowsA early det ection of errors on inactive paths. If a path becomesD unavailable or returns to service, the system manager is notifiedB with an OPCOM message. If set to OFF (0), multipath polling is disabled. The default is ON. 2 MPDEV_REMOTE@ (Alpha only) MPDEV_REMOTE enables MSCP served disks to become@ members of a multipath set when set to ON (1). If set to OFFC (0), only local paths to a SCSI or Fibre Channel device will be6 used in the formation of additional multipath sets.B However, setting this parameter to OFF will not have any effectD on existing multipath sets that have remote paths. The default is OFF.C For OpenVMS Alpha Version 7.3, this parameter must remain set toD the default value of OFF (0). This restriction will be removed in a future release of OpenVMS. 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.A On Alpha systems, 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 availabl e> on the modified-page list for page faults. If the number isA too small, the caching effectiveness of the modified-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.= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq recommends that you do so. 2 MPW_THRESH@ MPW_THRESH sets a lower bound of pages that must exist on theD modified-page list 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 systems, 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 page 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 file. 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.? On VAX systems, the MPW_WRTCLUSTER default value and maximum@ value is 120 512-byte pages; its minimum value is 16 512-byte pages.A On Alpha systems, the MPW_WRTCLUSTER default value 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 GE N attributes. 2 MSCP_BUFFERD This buffer area is the space used by the server to transfer data* between client systems and local disks.B On VAX systems, MSCP_BUFFER specifies the number of pages to be4 allocated to the MSCP server's local buffer area.D On Alpha systems, MSCP_BUFFER specifies the number of pagelets to7 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 t he 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 MS CP command times out.> If command timeout errors are being logged on client nodes,> setting the parameter to a nonzero value on OpenVMS servers? reduces the number of errors logged. Increasing the value ofC this parameter reduces the numb client MSCP command timeouts and8 increases the time it takes to detect faulty devices.@ If you need to decrease the number of command timeout errors,D Compaq recommends that you set an initial value of 60. If timeout? errors 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. 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 t he type you want in the followingA table and specify its value. For some systems, you may want toA specify two serving types, such as serving 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 allocation@ class does not match the system's node allocation class (pre-A 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 DescriptionC Bit 0 Serve all available disks (locally attached and those@ (1) connected to HSx and DSSI controllers). Disks with> allocation classes that differ from th e system'sC allocation class (set by the ALLOCLASS parameter) are. also served if bit 3 is not set.> Bit 1 Serve locally attached (non-HSx and DSSI) disks. (2)A Bit 2 Serve the system disk. This is the default setting.? (4) This setting is important when other nodes in theA cluster rely on this system being able to serve itsC system disk. This setting prevents obscure contention? problems that can occur when a system attempts toC complete I/O to a remote system disk whose system has failed.@ Bit 3 Restrict the serving specified by bit 0. All disksC (8) except those with allocation classes that differ fromA the system's allocation class (set by the ALLOCLASS$ parameter) are served.? This is pre-Version 7.2 behavior. If your cluster@ includes systems running OpenVMS 7.1-x or earlier,A 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 o 0 - Do not serve any disks (the default for earlier versions of OpenVMS).$ o 1 - Serve all available disks.C o 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-c hecking multiprocessing synchronization8 image SYSTEM_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 VAX systems, this image is. SYSTEM_SYNCHRONIZATION_SPC.EXE.. o On Alpha systems, 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 Description> 0 Both Thread Manager upcalls and the creation of4 multiple kernel threads are disabled.B 1 Thread Manager upcalls are enabled; the creation of3  multiple kernel threads is disabled.> 2-256 Both Thread Manager upcalls and the creation of> (Alpha multiple kernel threads are enabled. The number@ only) specified represents the maximum number of kernel@ threads that can be created for a single process., The maximum value for MULTITHREAD is 256.' MULTITHREAD is an AUTOGEN parameter. 2 MVTIMEOUT= MVTIMEOUT is the time in seconds that a mount verification9 attempt continu es 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.C MVTIMEOUT is a DYNAMIC parameter. On Alpha systems, 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_LAN_OVRHD@ Beginning in OpenVMS Version 7.3, this parameter is obsolete. 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 circuitA connected to the system up to the limit set by this parameter.A Its default values are different for OpenVMS Alpha and OpenVMS VAX:A o On Alpha, to optimize performance, the default value is the9 largest packet size currently supported by OpenVMS.C o On VAX, to conserve memory, the default value is the Ethernet packet size.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_PKTSZI + NISCS checksum (only if data checking 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 PEdriv er 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-to-end path that involves an Ethernet segment restrict= packet size to that of an Ethernet packet (149 8 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 of0 LAN Minimum Value for NISCS_MAX_PKTSZ Ethernet 1498 FDDI 4468 Gigabit 7532 Ethernet ATM 7606= On Alpha systems, NISCS_MAX_PKTSZ is an AUTOGEN parameter. 2 NISCS_PORT_SERVA NISCS_PORT_SERV provides flag bits for PEDRIVER port services.D Setting bits 0 and 1 (decimal value 3) enables data checking. The. remaining bits are reserved for future use.- NISCS_PORT_SERV has the AUTOGEN attri"bute. 2 NJOBLIM> NJOBLIM establishes the limit for network jobs. The maximum? number of jobs is 1024. The minimum is 0, and the default is 16." NJOBLIM is a DYNAMIC parameter. 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.= This #special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq 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.= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq re$commends that you do so. 2 NOPGFLSWP; If enabled, NOPGFLSWP disables swapping into page files.= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq recommends that you do so. 2 NPAGECALCA NPAGECALC controls whether the system automatically calculates0 the initial size for nonpaged dynamic memory.B Compaq sets the default value of NPAGECALC to 1 only during theC initial boot after an install %ation or upgrade. When the value ofA 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 0 &D 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 t 'he 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 a (nd 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 NPAGERAD? (Alpha only) NPAGERAD specifies the total number of bytes of= nonpaged pool that will be allocated for Resource AffinityB Domains (RADs) other than the base RAD. For platforms that haveC 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 the RADs that areD not the base RAD. The system then assigns the remaining 4,194,304 bytes to the base RAD." NPAGERAD has the GEN attribute. 2 NPAGEVIR= NPAGEVIR defines the maximum size to which NPAGEDYN can beA increased. If this value is too small, the system can hang. If@ NPAGEVIR is too large, the result is a penalty of 4 bytes per9 extra page on VAX and 8 bytes p +er extra page on Alpha.? 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.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_AGGRESSIVE? (Alpha only) NPAG_AGGRESSIVE is the percentage of packets on? a nonpaged pool lookaside list that remain after the list is) trimmed during aggressive reclamation.* NPAG_AGGRESSIVE is a DYNAMIC parameter. 2 NPAG_BAP_MAXC - (Alpha only) NPAG_BAP_MAX is the maximum of bus addressable pool sizes requested. 2 NPAG_BAP_MAX_PAB (Alpha only) NPAG_BAP_MAX_PA is the smallest of the maximum bus1 addressable pool physical addresses requested. 2 NPAG_BAP_MINC (Alpha only) NPAG_BAP_MIN is the minimum of bus addressable pool sizes requested. 2 NPAG_BAP_MIN_PA= (Alpha only) NPAG_BAP_MIN_PA specifies the lowest physical1 address allowed within a bus addressable pool. 2 NPA.G_GENTLE= (Alpha only) NPAG_GENTLE is the percentage of packets on aC nonpaged pool lookaside list remaining after the list is trimmed during gentle reclamation.& NPAG_GENTLE is a DYNAMIC parameter. 2 NPAG_INTERVAL> (Alpha only) NPAG_INTERVAL is the number of seconds between. passes of nonpaged pool gentle reclamation.( NPAG_INTERVAL is a DYNAMIC parameter. 2 NPAG_RING_SIZEB (Alpha only) NPAG_RING_SIZE represents the number of entries in the ring bu /ffer. 2 PAGEDYN@ PAGEDYN sets the size of the paged dynamic pool in bytes. TheB specified value is rounded down to an integral number of pages.> Each page of paged dynamic pool adds 8 bytes of permanentlyC resident memory to the system page table; the paged dynamic pool+ has no other direct memory requirements.@ The paged dynamic pool is used to allocate storage for sharedB logical names, resident image headers, known file list entries,@ and RMS file-sharing struct0ures. Substantial amounts of spaceA for the pool can be overallocated with little effect on system performance.D The size of the paged pool can grow dynamically up to the maximum& size that this parameter specifies.< PAGEDYN has AUTOGEN, FEEDBACK, GEN, and MAJOR attributes. 2 PAGFILCNT? On VAX systems, PAGFILCNT defines the maximum number of page> files that can be installed. On Alpha systems, beginning in3 OpenVMS Version 7.3, this parameter is obsolete. 1 2 PAGTBLPFCC PAGTBLPFC specifies (in pages) the maximum number of page tables; to read to satisfy a fault for a nonresident page table.= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq 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 2 previously responding remote ports.= A system does not detect the existence of ports whose portA 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 3has 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 portsB 0 through 15). Compaq 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 defa 4ultA is 0.) When PANOPOLL is set, a computer does not discover thatC another computer has shut down 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.?5 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 param6eter 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 po7lling 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.@ This parameter trades polling overhead against quick responseB to virtual circuit failures. Compaq recommends that you use the$ default value for this parameter.B Compaq recommends that you set this parameter to the same value on each cluster computer.) PAPOLLINTERVAL is a DYNAMIC parameter. 2 PAPOOLINTERVAL? Spe8cifies, in seconds, the interval at which the port driverB checks available nonpaged pool after a pool allocation failure.D This parameter trades faster response to pool allocation failuresA against increased polling overhead. Compaq 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 9 CI and DSSI port sanity timers areD enabled to permit remote systems to detect a system that has beenC hung 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 semidyna:mic. A new value of PASANITY takes7 effect on the next CI or DSSI port reinitialization.@ If CI or DSSI devices are not configured on your system, this parameter is ignored.# PASANITY is a DYNAMIC parameter. 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 i;s 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 PEA PE1, PE2, PE3, PE <4, PE5, PE6 are reserved for Compaq use only.? These parameters are for cluster algorithms and their usagesB can change from release to release. Compaq recommends using the/ default values for these special parameters. 2 PFCDEFAULTC On VAX systems during execution of programs, PFCDEFAULT controlsB the number of image pages read from disk per I/O operation whenC a page fault occurs. The PFCDEFAULT maximum default value is 127 512-byte pages.< On Alpha systems du =ring execution of programs, PFCDEFAULT? controls the number of image pagelets read from disk per I/O= operation when a page fault occurs. The PFCDEFAULT maximum? default value is 2032 512-byte pagelets (127 8192-byte Alpha 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 shoul >d 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 PFCDEFAULT has the AUTOGEN and DYNAMIC attributes. 2 PFN_COLOR_COUNT<(Alpha only) PFN_COLOR_COUNT specifies the number of buckets?(colors) int?o which all members of the zeroed page list and allDunencumbered members of the free page list are sorted. OpenVMS AlphaAsystems might derive a preferred page color from a request to mapBa given virtual page and attempt to map that virtual page to a PFNAof matching "color." This results in less variance in which cacheAblocks are used when accessing that page. This might or might not2improve performance, depending on the application.= This special parameter is used by Compaq and is subject @ to@ change. Do not change this parameter unless Compaq recommends@ that you do so. 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 increased. 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 iAt 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 VAX systems, the default value is 120 page faults every 10 seconds.@ On Alpha systems, the default value is 8 page faults every 10 seconds.A PFRATH has the DYNAMIC and MAJOR attributes. On Alpha systems,/ PFRATH also is an AUTOGEN-altered parameter. 2 P BFRATL@ 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.? Increasing the value of this parameter tends to decrease theB limits of the working sets, while decreasing its value tends to increCase their limits.9 PFRATL has the AUTOGEN, DYNAMIC, and MAJOR attributes. 2 PHYSICAL_MEMORY@ (Alpha only) PHYSICAL_MEMORY specifies the amount of physical= memory available for use. The default setting is -1, whichA equates to all memory in the system. Decreasing this parameter> allows you to test smaller configurations of memory without" having to remove memory boards.= This special parameter is used by Compaq and is subject to@ change. Do not change this paraDmeter unless Compaq recommends that you do so.+ PHYSICAL_MEMORY is an AUTOGEN parameter. 2 PHYSICALPAGES? (VAX only) PHYSICALPAGES sets the maximum number of physical< pages of memory to be used on the system. Decreasing this@ parameter allows you to test smaller configurations of memory, without the need to remove memory boards.= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq recommends that yoEu do so.) 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 setting has been raised to accommodate theB increased dFemands for process-permanent memory that result from: changes made to RMS file-naming parsing in Version 7.2.= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq 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 automatiGc 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.= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq recommends that you do so./ PIXSCAN is an AUTOGEN and DYNAMIC parameter. 2 POOLCHECK= This special parameter is used by Compaq and is subject to@ change. Do not change H this parameter unless Compaq 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 POOLCHECK is set to a Inonzero 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 ON (1).D For further information about pool checking, refer to the OpenVMS VAX Device Support Manual.$ POOLCHECK is a DYNAMIC parameter. 2 POOLPAGING; POOLPAGING enables (1) paging of pageable dynamic pool.= This special parameter Jis used by Compaq and is subject to@ change. Do not change this parameter unless Compaq 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 software 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 requeKst 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 DCL 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 outLstanding 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 buffered 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.M 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 and 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 Nfor 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 command 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 Cr Oeate 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 (Process). 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) namPes 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). Compaq recommends that this parameter not/ be smaller 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_DPRCLMQ= 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_DWSDERFAULT 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 Create Process ($CREPRC) system service or the DCL command RUN (Process).> PQL_DWSEXTENT has the AUTOGEN, DYNAMIC, and GEN attributes. 2 PQL_DWSQUOTA@ PQL_DWSQUOTSA 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_MASTLMC PQL_MASTLM sets a default limit on the minimum number of pendingD ASTs for a process created 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? PQLT_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 Process ($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 minimUum 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 Process ($CREPRC) system service or the DCL command RUN (Process).1 PQL_MDIOLM has the DYNAMIC and GEN attributes. 2 PQL_MENQLMC PQL_MENQLM sets the defauVlt limit on the minimum number of locks= that can be queued at one time by a process created by theA 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 Create Process ($CREPRC) system service or the DCL command RUN (Process).1 PQL_MFILLM has the DYNAMIC and GEN attributes. 2 PQL_MJTQUOTAA W 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) systemC service or the DCL command RUN (Process). Compaq recommends that3 this parameter be no smaller than PQL_MWSEXTENT.A OXn Alpha systems, PQL_MPGFLQUOTA sets the minimum pagelet file> quota for a process created by the Create Process ($CREPRC)3 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_MPRCLM 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 haYs 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 the 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 overZrides 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 overrides 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 specifies, in seconds, the polling interval usedB to look for Systems Communications Services (SCS) applications,C such as the connection manager and mass storage con\trol 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 systems,/ PRCPOLINTERVAL is also an AUTOGEN parameter. 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. The default value is 0.= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq 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 allocation map for the image.2 PROCSECTCNT has the AUTOGEN and GEN attributes. 2 PSEUDOLOAA (VAX only) PSEUDOLOA specifies (in pages) the size of the PDA_0A system image. PSEUDOLOA is used to boot standalone BACKUP from magnetic tape.= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq recommends that you do so. 2 PU_OPTIONS. PU_OPTIONS is reserved for Compaq use only. 2 QBUS_MULT_INTR> (VAX only) QBUS_MULT_INTR enables (1) multilevel interruptD dispatching on systems that use the Q22-bus adapter. Refer to theC OpenVMS VAX Device Support Ma`nual for more information about theB QBUS_MULT_INTR system parameter. (This manual has been archived9 but is available on the OpenVMS Documentation CD-ROM.)= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq recommends that you do so. 2 QDSKINTERVAL@ QDSKINTERVAL establishes, in seconds, the disk quorum polling$ interval. The default value is 3. 2 QDSKVOTESB QDSKVOTES specifies the number of votaes contributed by a quorum disk in a cluster. 2 QUANTUM! QUANTUM defines the following:@ o Processor time: maximum amount of processor time a processC 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 storageB QUANTUM has the DYNAMIC and MAJOR attributes. On Alpha sybstems,* QUANTUM also has the AUTOGEN attribute. 2 RAD_SUPPORTA (Alpha only) RAD_SUPPORT enables RAD-aware code to be executed@ on systems that support Resource Affinity Domains (RADs); for& example, AlphaServer GS160 systems.@ A RAD is a set of hardware components (CPUs, memory, and I/O)A with common access characteristics. For more information about? using OpenVMS RAD features, see the OpenVMS Alpha Galaxy and Partitioning Guide.% RAD_SUPPORT has the GEN att cribute. 2 REALTIME_SPTSB (VAX only) REALTIME_SPTS reserves a number of system page tableA entries for mapping connect-to-interrupt processes into systemB space. This value should normally remain at the default (0) inC an environment that is not real-time. Where connect-to-interrupt? processes do use the system, this value should represent theC maximum number of pages that all concurrent connect-to-interruptC processes must map into system space. See the OpenVMS VAX Ddevice Support Manual< 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 systems,. RECNXINTERVAL is also an AUTOGEN parameter. 2 RESALLOC< RESALLOC controls whether resource allocation checking isA performed. The default value of 0 disables resource allocation c ehecking.= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq 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 constraintsf 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_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 eacgh I/O buffer.B 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 sohme of the index7 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 siet this system 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 arje used, a larger 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 parameterk with the DCL commandB 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 l specifies a default 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 m Thus, RMS_DFNBC 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 DYN nAMIC 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 ovalue 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 deter pmines 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.D The protection is expressed as a mask. (See the discussion of theB $CRMPSCq system service in the OpenVMS System Services ReferenceB Manual for more information about specifying protection masks.)A By default, the mask is 64000 (decimal) or FA00 (hexadecimal),- which represents the following protection: (S:RWED,O:RWED,G:RE,W:)9 You can set this system parameter with the DCL commandB SET RMS_DEFAULT/SYSTEM and display the parameter with SHOW RMS_ DEFAULT. 2 RMS_PROLOGUEA RMS_PROLOGUE specifies the default prologue RMS uses to creater? indexed files. The default value 0 specifies that RMS shouldA 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 RSRVPAGCNT< RSRVPAGCNT sets the number of pages that are reserved and. escrowed for the current process page file.= This specsial parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq recommends that you do so. 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.= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq recommends that you do so. 2 S2_SIZEDt (Alpha only) S2_SIZE is the number of megabytes to reserve for S2D space. This value does not include the size required for Extended File Cache (XFC). 2 SA_APP> SA_APP is a special parameter reserved for Compaq use only. 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 thuat the dump written to the? page file should be retained until either copied or released using the SDA utility. 2 SBIERRENABLEA (VAX only) This parameter enables (1) SBI error detection and logging.= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq recommends that you do so. 2 SCH_CTLFLAGS= (VAX only) This special parameter is used by Compaq and is@ subject to change. Do not change th vis parameter unless Compaq recommends that you do so.A The vector scheduling subsystem presently provides an enlargedC quantum to processes requiring vector capability. Customer sites? can disable vector quantum adjustment by setting bit NO_VEC_A QUANTADJ (bit 9) in the system parameter SCH_CTLFLAGS. Setting> this bit causes the scheduler to treat the vector processes? and scalar processes uniformly. However, doing so results inB more frequent vector context switches w when the number of vectorC processes exceeds the number of vector processors in the system.' SCH_CTLFLAGS is a DYNAMIC parameter. 2 SCSBUFFCNTA On VAX systems, SCSBUFFCNT is the number of buffer descriptors@ configured for all SCA. If an SCA device is not configured onC your system, this parameter is ignored. Generally speaking, eachA data transfer needs a buffer descriptor and thus the number of> buffer descriptors can be a limit on the number of possible> simulxtaneous 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 isB worth considering. Note that AUTOGEN provides feedback for this! parameter on VAX systems only.A On Alpha systems, the SCS buffers are allocated as needed, and. SCSBUFFCNT is reserved for Compaq use only.< SCSBUFFCNT has the AUTOGEN, FEEDBACK, and GEN attributes. 2 SCSCONNCNTB Beginning y with OpenVMS Version 7.2, this parameter is obsolete.D SCS connections are now allocated and expanded only as needed, up to a limit of 65,000. 2 SCSFLOWCUSHC Specifies the lower limit for receive buffers at which point SCSC starts to notify the remote SCS of new receive buffers. For eachB connection, SCS tracks the number of receive buffers available.C SCS communicates this number to the SCS at the remote end of theA connection. However, SCS does not need to do this fzor each newD receive buffer added. Instead, SCS notifies the remote SCS of newC receive buffers if the number of receive buffers falls as low as the SCSFLOWCUSH value.C The default value is adequate on most systems. If an SCA port is< not configured on your system, this parameter is ignored.& SCSFLOWCUSH is a DYNAMIC parameter. 2 SCSI_NOAUTO= (VAX only) This special parameter is used by Compaq and is@ subject to change. Do not change this parameter unless Comp {aq recommends that you do so.@ SCSI_NOAUTO prevents the loading of a disk or tape SCSI classD driver for any given device ID in a configuration that includes aC SCSI third-party device. The SCSI_NOAUTO system parameter storesA a bit mask of 32 bits, where the low-order byte corresponds to@ the first SCSI bus (PKA0), the second byte corresponds to the1 second SCSI bus (PKB0), and so on, as follows:# #31 24 23 16 15 8 7 0$ +-------+-------+-------+-------+ |$ | D | C | B | A |$ +-------+-------+-------+-------+B For each SCSI bus, setting the low-order bit inhibits automaticA configuration of the device with SCSI device ID 0; setting the? second low-order bit inhibits automatic configuration of the@ device with SCSI device ID 1, and so forth. For instance, theA value 00002000 subscript 16 prevents the device with SCSI ID 5A on the bus identified by SCSI port ID B from being configured.A By default, all the} bits in the mask are cleared, allowing all devices to be configured.& SCSI_NOAUTO is a DYNAMIC parameter. 2 SCSICLUSTER_P[1-4]> (Alpha only) SCSICLUSTER_P[1-4] parameters allow non-Compaq1 peripherals (CPU-lookalikes) in SCSI clusters.= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq recommends that you do so. 2 SCSMAXDG2 This parameter is reserved for Compaq use only." SCSMAXDG has ~the GEN attribute. 2 SCSMAXMSG2 This parameter is reserved for Compaq 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.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 entries (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 the 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@ identification number. This parameter must be set to 0. It is% reserved by Compaq 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 withC previous versions of the operating system. See the OpenVMS GuideA to System Security for further information about the C2 and B1 evaluated configurations." The following bits are defined: Bit Description; 0 Allows DECwindows to display PostScript extensions= 1 Allows multiple user names to connect to DECW$SERVERB 2 Allows unevaluated DECwindows transports (such as TCP/IP)6 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 cannot4 update the cluster database VMS$OBJECTS.DATB 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 accountsB 7 Allows intrusions on a clusterwide or local basis (If the5 bit is cleared, intrusions are clusterwide.)? 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 s ystem sets the time of day 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 OpenVMS DCL Dictionary). 2 SHADOWINGA SHADOWING enables or disables shadowing and specifies the mode@ of shadowing operations that you want to enable. SHADOWING is? a value that specifies the type of disk class driver that isD loaded on the system: DUDRIVER, DSDRIVER, or SHDRIVER. See VolumeB Shadowing for OpenVMS for more information about setting system# 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 Phase II shadowing enabled. SHDRIVER is loaded. Phase II@ shadowing provides shadowing of all disks located on a9 standalone system or an OpenVMS Cluster system.C Note that a parameter value o f 1 represents Phase I, which is no5 longer supported. Instead, use Phase II shadowing. 2 SHADOW_MAX_COPY? Use this parameter for Phase II shadowing only. The value of> SHADOW_MAX_COPY controls how many parallel copy threads are allowed on a given node.B Carefully consider the needs of each shadowed VAX 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.> See 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 that? can exist on a node. 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.= This system parameter is not dynamic; that is, a reboot is( required when you change the setting.B The default setting on OpenVMS Alpha systems is 500; on OpenVMSD VAX systems, the default is 100. The minimum value is 10, and the maximum value is 10,000. 2 SHADOW_MBR_TMOA SHADOW_MBR_TMO controls the amount of time the system tries toB fail over p hysical members of a shadow set before removing 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_TWO is a DYNAMIC parameter. 2 SHADOW_REMOVE_1@ (Alpha only) SHADOW_REMOVE_1 is reserved for Compaq use only. 2 SHADOW_REMOVE_2@ (Alpha only) SHADOW_REMOVE_2 is reserved for Compaq use only. 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.> To enable minimerge on a system disk, add the value 4096 to@ your existing SHADOW_SYS_DISK value. For example, if you haveC SHADOW_SYS_DISK  set to a value of 1, change it to 4097 to enableB minimerge. Also, be sure to set the DUMPSTYLE parameter to dump@ off system disk, as described in the OpenVMS System Manager's Manual. 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 us e 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 shadowB 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 throug h 65,535 seconds. 2 SHADOW_SYS_UNITB Use this parameter for Phase II shadowing only. 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 particularD system disk shadow set. See Volume Shadowin g for OpenVMS for moreD information about setting system parameters for volume shadowing. 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 communi cations channelsA (SYSGEN default). Local SCS communications are@ 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: (Alpha Galaxy platforms only) The Shared Memory ClusterC Interconnect (SMCI) system parameter SMCI_PORTS controls initial@ loading of SYS$PBDRIVER. This par ameter is a bit mask; bits 0B through 25 each represent a controller letter. If bit 0 is set,C which is the default setting, PBAx is loaded (where x representsA the Galaxy Partition ID). If bit 1 is set, PBBx is loaded, andB so on up to bit 25, which causes PBZx to be loaded. For OpenVMSA Alpha Version 7.2, Compaq recommends leaving this parameter at the default value of 1.@ Loading additional ports allows multiple paths between GalaxyC instances. In the initial release o f the Galaxy software, having? multiple communications channels is not an advantage because< SYS$PBDRIVER does not support fast path. A future release> of OpenVMS will provide Fast Path support for SYS$PBDRIVER,> when multiple CPUs improve throughput by providing multiple- communications channels between instances. 2 SMP_CPUS@ SMP_CPUS identifies which secondary processors, if available,A are to be booted into the multiprocessing system at boot time.B SMP_CPUS is a  32-bit mask; if the value of a bit in the mask is@ 1, the processor with the corresponding CPU ID is booted intoC the multiprocessing system (if it is available). For example, ifC you want to boot only the CPUs with CPU IDs 0 and 1, specify the value 3 (both bits are on).C The default value of SMP_CPUS, -1, boots all available CPUs into the multiprocessing system.B Note that although a bit in the mask corresponds to the primary> processor's CPU ID, the primary processor is always booted.A That is, if the mask is set to 0, the primary CPU still boots.= Any available secondary processors are not booted into the multiprocessing system.D This parameter is ignored if the MULTIPROCESSING parameter is set to 0. 2 SMP_CPUSHA SMP_CPUSH is a special parameter reserved for Compaq use only.4 Compaq recommends that you use the default value. 2 SMP_LNGSPINWAITC Certain shared resources in a multiprocessing system take longerB t o become available than allowed by the SMP_SPINWAIT parameter.@ SMP_LNGSPINWAIT establishes, in 10-microsecond intervals, theC length of time a processor in a multiprocessing system waits for< these resources. A timeout causes a CPUSPINWAIT bugcheck.C The default value is 3000000 (3 million 10-microsecond intervals or 30 seconds). 2 SMP_SANITY_CNT? SMP_SANITY_CNT establishes, in 10-millisecond intervals, theC timeout period for each CPU in a symmetric multiprocessin g (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.= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq recommends that you do so. 2 SPTREQ? (VAX only) SPTREQ sets the number of system page table (SPT)9 entries required for mapping the following components: Executive image RMS image SYSMSG.EXE file! Multiport memory structures Each MASSBUS adapter Each UNIBUS adapter Each DR32 adapterA The number of system page table entries required for all other? purposes is automatically computed and added to the value of< SPTREQ to yield the actual size of the system page table." SPTREQ is an AUTOGEN parameter. 2 SSINHIBIT? SSINHIBIT controls whether system services are inhibited (1)@ (on a per-process basis). By default, system services are not inhibited (0).= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq recommends that you do so. 2 STARTUP_P1-8; STARTUP_P1 specifies the type of system boot the system-@ independent startup procedure is to perform. If  STARTUP_P1 is@ " ", a full boot is performed; "MIN" indicates a minimum bootB that starts only what is absolutely necessary for the operating system to run.= STARTUP_P2 controls whether verification is set during the< execution of the system-independent startup procedure. IfC STARTUP_P2 is " ", verification is not enabled; "TRUE" indicates that verification is enabled.B Beginning in OpenVMS Version 7.2, if STARTUP_P3 is set to AGEN,B the system executes AUTOGEN at the end of the startup sequence.= STARTUP_P4 through STARTUP_P8 are reserved for future use. 2 SWP_PRIO? SWP_PRIO sets the priority of I/O transfers initiated by the swapper.= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq recommends that you do so. 2 SWPALLOCINCB (VAX only) SWPALLOCINC sets the size (in blocks) to use to backC up swap file space allocation in the swap or page file. Space inB the file is allocated in multiples of this unit (up to WSQUOTA) to guarantee swap space.= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq 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.= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq recommends that you do so. 2 SWPFILCNT? On VAX systems, SWPFILCNT defines the maximum number of swap> files that can be installed. On Alpha systems, beginning in3 OpenVMS Version 7.3, this parameter is obsolete. 2 SWPOUTPGCNTD This parameter allows the swapper an alternative mechanism before actually performing swaps.B On VAX systems, SWPOUTPGCNT defines the minimum number of pagesA to which the swapper should attempt to reduce a process beforeD swapping it out. The pages taken from the process are placed into the free-page list.> On Alpha systems, SWPOUTPGCNT defines the minimum number ofC pagelets to which the swapper should attempt to reduce a processB 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< S WPRATE sets the swapping rate (in 10-millisecond units).A This parameter limits the amount of disk bandwidth consumed by swapping.= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq recommends that you do so. 2 SYSMWCNTB SYSMWCNT 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 command 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.= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq recommends that you do so. 2 SYS TEM_CHECK< SYSTEM_CHECK investigates intermittent system failures by= enabling a number of run-time 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, with anD allocated pool pattern of %x61616161= ('aaaa') and deallocated pool> pattern of x64646464 ('dddd').; MULTIPROCESSING 2 Enable full synchronization) checking.> While SYSTEM_CHECK is enabled, the previous settings of the< BUGCHECKFATAL and MULTIPROCES SING parameters are ignored.> However, setting 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 byD SYSTEM_CHECK, see the description of the ACP_DATACHECK parameter.A For information about the performance implications of enabling4 SYSTEM_CHECK, see OpenVMS Performance Management.@ On VAX systems, SYSTEM_CHECK is a special parameter, which is? subject to change at any time and should be modified only if recommended by Compaq. 2 TAILOREDB TAILORED specifies whether or not the system is tailored duringB installation. Compaq recommends that you use the default value. 2 TAPE_ALLOCLASS> TAPE_ALLOCLASS determines the tape alloca tion 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.= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq recommends that you do so. 2  TIME_CONTROL= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq 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< is approximated as seconds in the implementation.) If theA time specified by TIMEPROMPTWAIT elapses, the system contin ues@ the boot operation, and the date and time are set to the last( recorded time that the system booted.& NOTE< Compaq 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, accounting records, file creation dates, and file4 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 vir tual= circuit failure to be detected. Compaq recommends that the@ default value be used. Compaq also recommends that this valueA be lowered only in OpenVMS Cluster of three CPUs or less, thatC the same value be used on each computer in the cluster, and that2 dedicated LAN segments be used for cluster I/O.$ TIMVCFAIL is a DYNAMIC parameter. 2 TMSCP_LOADA TMSCP_LOAD allows the loading of the tape mass storage control? protocol server software. The TMSCP_LOAD parame ter also setsC locally connected tapes served. Refer to OpenVMS Cluster Systems: for information about setting the TMSCP_LOAD parameter.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 The settings take effect when the system boots. You cannot change+ the settings when the system is running.;  Starting with OpenVMS Version 7.2, the serving types 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 such aA combination, add the values of each type, and specify the sum.? In a mixed-version cluster that inc ludes 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 non-DSSI) tapes. Bit 2 N/A Reserved.D Bit 3 8 Restrict the serving specified b y 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 second longword of default terminal? characteristics. The default characteristics are representedA as a code that is d erived 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 up on logout.D MODHANGUP 8 Allow modification of HANGUP without+ priv ileges.> 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.@ DCL_MAILBX 200 Function reserved for Compaq 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 with SYSGEN.= Refer to the OpenVMS Terminal;  Fallback Utility Manual for= information about setting the@ FALLBACK terminal characteristicD using the Terminal Fallback utility.> (This manual has been archived? but is available on the OpenVMS6 Documentation CD-ROM.): DIALUP 8000 Terminal is a dialup line.= SEC URE 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./ SIXEL 100000 Sixel graphics.D DRCS 200000 Te rminal 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_DEFPORTB TTY_DEFPORT provides flag bits for port drivers. Bit 0 set to 1D i ndicates that the terminal controller does not provide automatic? XON/XOFF flow control. This bit should not be set for Compaq> 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 Compaq. 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 17. 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< asynchronous 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. 2 TTY_SPEEDA TTY_SPEED sets the 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 17. Baud rates are defined by the $TTDEF macro. 2 TTY_TIMEOUT: TTY_T IMEOUT 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 usua lly 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 UDABURSTRATE0 UDABURSTRATE is reserved for Compaq use only.& UDABURSTRATE has the GEN attribute. 2 USERD1< USERD1 is reserved for definition at the user's site. The? reserved longword is referenced by the symbol SGN$GL_USERD1.* On Alpha systems, this symbol is in the- SYS$LOADABLE_IMAGES:SYS$BASE_IMAGE module.B On VAX systems, the symbol is in the SYS$SYSTEM:SYS.STB 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.* On Alpha systems, this symbol is in the- SYS$LOADABLE_IMAGES:SYS$BASE_IMAGE module.B On VAX systems, the symbol is in the SYS$SYSTEM:SYS.STB 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.* On Alpha systems, this symbol is in the- SYS$LOADABLE_IMAGES:SYS$BASE_IMAGE module.B On VAX systems, the symbol is in the SYS$SYSTEM:SYS.STB 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.* On Alpha systems, this symbol is in the- SYS$LOADABLE_IMAGES:SYS$BASE_IMAGE module.B On VAX systems, the symbol is in the SYS$SYSTEM:SYS.STB 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 VBN_CACHE_S= (VAX only) This special parameter is used by Compaq and is@ subject to change. Do not change this parameter unless Compaq recommends that you do so.C The static system parameter VBN_CACHE_S enables or disables fileC system data caching. By default its value is 1, which means that@ caching is enabled and the Virtual I/O Cache is loaded during system startup.B Setting the value to 0 disables file system data caching on the? local node and throughout the OpenVMS Cluster. In an OpenVMS@ Cluster, none of the other nodes in the cluster can cache anyA file data until this node either leaves the cluster or reboots with VBN_CACHE_S set to 1. 2 VBSS_ENABLE= (VAX only) This special parameter is used by Compaq and is@ subject to change. Do not change this parameter unless Compaq recommends that you do so.; This parameter enables virtual balance slots (VBS) to beB created. A virtual balance slot holds the mapping for a memory-C resident process that does not currently own a real balance slot? (RBS). The set of real balance slots is timeshared among all? memory-resident processes. With VBS enabled, the quantity of? memory-resident processes is limited by the system parameterD MAXPROCESSCNT. With VBS disabled, the quantity of memory-resident: processes is limited by the system parameter BALS ETCNT.@ When creating a new process, if the set of real balance slots? is allocated, then a virtual balance slot is created and the? owner of a real balance slot is selected and transitioned toC the virtual balance slot. The new process is created in the realD balance slot. Processes are transitioned (faulted) back to a real: balance slot as they are scheduled to execute on a CPU. Bit ResultD 0 Enables VBS. All other VBS enables are subordinate to this*  enable. The default is disabled.9 1 Enables the creation of a map for process-based@ direct I/O, allowing the process with direct I/O (DIO)C outstanding to be transitioned to a virtual balance slot.B Without DIO maps, a process with DIO outstanding retainsA its real balance slot for the duration of the DIO. This> reduces the pool of available real balance slots forD timesharing, which may result in a higher rate of faultingD into the limited set of real balance slots. The default is enabled., 2-7 Reserved to Compaq for future use.' VBSS_ENABLE is an AUTOGEN parameter. 2 VBSS_ENABLE2= (VAX only) This special parameter is used by Compaq and is@ subject to change. Do not change this parameter unless Compaq recommends that you do so.; This cell is used for enabling and disabling VBS dynamic< capabilities that are valid only when VBS is enabled. The7 following  table indicates the result for each value: Bit Result@ 0 Enables VBS to perform first-level data reduction when6 switching processes. The default is enabled.A 1 Enables VBS to perform second-level data reduction when6 switching processes. The default is enabled.D 2 Requests VBS to perform an optimization that detects emptyA private page table pages on the modified list and freesC them directly to the free list versus writing them to the4 page file. The default setting is enabled., 3-7 Reserved to Compaq for future use. 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.% VCC_FLAGS is an AUTOGEN parameter. 2 VCC_MAXSIZED (Alpha only) The static system parameter VCC_MAXSIZE controls theB size of the virtual I/O cache. VCC_MAXSIZE, which specifies the' size in blocks, is 6,400 by default.D The virtual I/O cache cannot shrink or grow. Its size is fixed at system startup.= This special parameter is used by Compaq and is subject to@ change. Do not change  this parameter unless Compaq recommends that you do so.' VCC_MAXSIZE is an AUTOGEN parameter. 2 VCC_MAX_CACHEC (Alpha only) The dynamic system parameter VCC_MAX_CACHE controls@ the maximum size of the Extended File Cache. It specifies theC size in megabytes. By default, VCC_MAX_CACHE has a special valueC of -1 for people who do not want to tune their systems manually;C this value means that at system startup, the maximum size of theB 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,@ the 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 Refer to the OpenVMS System Manager's Manual for instructions on6 setting permanent memory allocations for the cache.(  VCC_MAX_CACHE is a DYNAMIC parameter. 2 VCC_MAX_IO_SIZE< (Alpha only) The dynamic system parameter VCC_MAX_IO_SIZE= controls the maximum size of I/O that can be cached by theD Extended File Cache. It specifies the size in blocks. By default, the size is 127 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 only) VCC_MAX_LOCKS is a special parameter reserved? for Compaq use only. Extended File Cache intends to use this parameter in future versions. 2  VCC_MINSIZEA (VAX only) VCC_MINSIZE sets the lower limit in pages of memory used by virtual I/O cache.= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq recommends that you do so. 2 VCC_PTES? (VAX only) The static system parameter VCC_PTES controls theD maximum size of the virtual I/O cache. It specifies the potential size in pages.C The virtual I/O cache automatically shrinks and grows, depe ndingB on your I/O workload and how much spare memory your system has.A As your I/O workload increases, the cache automatically grows,B but never to more than the maximum size. When your applications0 need memory, the cache automatically shrinks.= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq recommends that you do so. 2 VCC_READAHEADC (Alpha only) The dynamic system parameter VCC_READAHEAD controls D whether the Extended File Cache can use read-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_WRITEBEHIND@ (Alpha only) VCC_WRITEBEHIND is reserved for Compaq use only.> Extended File Cache intends to use this parameter in future versions. 2 VCC_WRITE_DELAY@ (Alpha only) VCC_WRITE_DELAY is reserved for Compaq use only. 2 VECTOR_MARGIN> (VAX only) VECTOR_MARGIN establishes the time interval when< the system checks the status of all vector consumers. TheA VECTOR_MARGIN parameter accepts an integer value between 1 and> FFFFFFFF(16). This value represents a number of consecutiveB process quanta (as determined by the system parameter QUANTUM).? If the process has not issued any vector instructions in the@ specified number of quanta, the system declares it a marginal vector consumer.D The default value of the VECTOR_MARGIN parameter is 200 subscript 10.( VECTOR_MARGIN is a DYNAMIC parameter. 2 VECTOR_PROC? (VAX only) VECTOR_PROC controls loading of vector processingC support code. By default, in a VAX vector processing system, the@ system automatically loads the vector processing support codeA at boot time. You can override the default behavior by settingB the static system parameter VECTOR_PROC to one of the following values: Value ResultD 0 Do not load the vector processing support code, regardless& of the system configuration.A 1 Load the vector processing support code if at least one> vector-present processor exists. This is the default value.B 2 Load the vector processing support code if the system isB vector-capable. This setting is most useful for a system@ in which processors have separate power supplies. WithC this setting, you can reconfigure a vector processor into< the system without rebooting the operating system.9 3 Always load the vector processing support code./ This parameter is not used on Alpha systems. 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 the 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 theD parameter remains in existence on Alpha systems for compatibility> purposes and has a default and maximum value of %X7FFFFFFF.2 SYSBOOT and AUTOGEN enforce this default value.= VIRTUALPAGECNT has the AUTOGEN, GEN, and MAJOR attributes. 2 VMS= VMSD1, VMSD2, VMSD3, VMSD4, VMS5, VMS6, VMS7, and VMS8 areB special parameters reserved for Compaq 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 others 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 threshh old? 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 system parameters that are= available for managing the update traffic between a master? write bitmap and its corresponding local write bitmaps in anB OpenV MS 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 threshold 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_M SG_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 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 g rouped 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.( 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 WLKSYSDSKA (Alpha only) WLKSYSDSK is used by various bootstrap componentsD to determine if the system disk should be treated as though it isB write-locked. This parameter is used 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.= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq 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.= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq 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.= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq recommends that you do so. 2 WRITESYSPARAMS? On VAX systems, WRITESYSPARAMS indicates that parameters areB modified during SYSBOOT and are written out to VAXVMSSYS.PAR by STARTUP.COM.A On Alpha systems, WRITESYSPARAMS indicates that parameters areD modified during SYSBOOT and are written out to ALPHAVMSSYS.PAR by STARTUP.COM.= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq 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 VAX systems, WSDEC specifies the number of pages by which@ the limit of a working set is automatically decreased at eachB adjus tment interval (which is quantum end). At a setting of 35,B for example, the system decreases the limit of a working set by- 35 pages each time a decrease is required.D On Alpha systems, WSDEC specifies the number of pagelets by which@ the limit of a working set is automatically decreased at eachB adjustment interval (which is quantum end). At a setting of 35,B for example, the system decreases the limit of a working set by0 35 pagelets each time a decrease is required.8 W SDEC 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 increase in limit is often critical to performance.? On VAX systems, WSINC specifies the number of pages by which@ the limit of a working set is automatically increased at eachC adjustment interval (whic h is quantum end). At a setting of 150,B for example, the system increases the limit of a working set byC 150 pages each time an increase is required. On VAX systems, the' default value is 150 512-byte pages.D On Alpha systems, WSINC specifies the number of pagelets by which@ the limit of a working set is automatically increased at each> adjustment interval (which is quantum end). At a setting of@ 150, for example, the system increases the limit of a working< set by 150 pa gelets each time an increase is required. On= Alpha systems, the default value is 2400 512-byte pagelets (150 8192-byte Alpha 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 systems,( WSINC a lso has the AUTOGEN attribute. 2 WSMAXC WSMAX sets the maximum number of pages on a systemwide basis forA any working set. WSMAX is calculated as a quarter of the firstA 32 MB plus a sixteenth of the memory from 32 to 256 MB, plus a4 sixty-fourth of the memory (if any) above 256 MB.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 WS_OPA0@ (VAX only) WS_OPA0 enables OPA0 output to the QVSS screen forB a workstation. A value of 1 enables output for OPA0 to the QVSS= screen; a value of 0 causes output for OPA0 to be ignored. 2 XFMAXRATE> XFMAXRATE limits the data  transfer rate that can be set forB DR32 devices. On some hardware configurations (especially those? without interleaved memory), a high DR32 transfer rate could> cause a machine check (CPU timeout). The OpenVMS I/O User's; Reference Manual describes how to encode this parameter.$ WSMAXRATE is a DYNAMIC parameter. 2 XQPCTL2> XQPCTL2 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.= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq 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,= This special parameter is used by Compaq and is subject to@ change. Do not change this parameter unless Compaq recommends that you do so. 2 ZERO_LIST_HIB (Alpha only) ZERO_LIST_HI is the maximum number of pages zeroed@ and put on the zeroed page list. This list is used as a cacheC of pages containing all zeros, which improves the performance of allocating 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! *********************************************************************wwgj 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. wwgj1 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 Parameter 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./ On VAX systems, the system parameter file is SYS$SYSTEM:VAXVMSSYS.PAR.1 On Alpha systems, the system parameter file is SYS$SYSTEM:ALPHAVMSSYS.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 f or 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 work area with defaultD parameter values. The second command sets the START UP_P1 system parameter to "minimum." wwOjj1 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 Parameter file-specD The file specification 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./ On VAX systems, the system parameter file is SYS$SYSTEM:VAXVMSSYS.PAR.1 On Alpha systems, the system parameter file is SYS$SYSTEM:ALPHAVMSSYS.PAR.B Use of the WRITE CURRENT command requires the SYSPRV privilege. ACTIVEC Specifies that source information i s 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 u p 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 OpenVMS Guide to System Security.< On Alpha systems, both the WRITE ACTIVE and WRITE CURRENT6 commands send a message to OPCOM and log the event. 2 Examples% 1.SYSGEN> WRITE SYS$SYSTEM:SPECIAL= This command creates a new parameter specification file, SYS$SYSTEM:SPECIAL.PAR. 2.SYSGEN> WRITE CURRENT= On VAX systems, this command modifies the current system+ parameter file on disk, VAXVMSSYS.PAR.? On Alpha systems, this command modifies the current system- parameter file on disk, ALPHAVMSSYS.PAR.I! *********************************************************************** ! PARAM-STARTI! Start 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 helpI! ***********************************************************************ww