% Librarian T09-20*s=?JT>?J65@@ALFfATTACHXCLASS_SCHEDULE0 CONFIGURATION?DEFINEG DISKQUOTAvDOlEXITIOPLICENSE*Overview PARAMETERSRESERVED_MEMORYSET)\SHOW2&SHUTDOWN?RSPAWNGSTARTUPk SYS_LOADABLEt Sys_Parameters f Usage_SummaryWBl1 @> Requests that SYSMAN read subsequent command input from the specific file or device. Format @ filespec 2 Parameter filespecA Specifies either the input device or the command procedure youA want to execute. The default file type is .COM. You cannot use1 wildcard characters in the file specification. 2 DescriptionC Use the execute procedure command to execute a command procedure@ containing SYSMAN commands. To execute the command procedure,@ invoke SYSMAN, place the at sign (@) command at the beginning? of a command line, then specify the file name of the command procedure.> The command procedure can contain any valid SYSMAN command. 2 Examples 1.$ CREATE ENV.COM SET ENVIRONMENT SHOW PROFILE $ MCR SYSMAN SYSMAN> @ENV.COMH %SYSMAN-I-DEFDIR, default directory on node -- SYS$SYSROOT:[SYSMGR]= %SYSMAN-I-DEFPRIV, default process privileges on node -- CMKRNL CMEXEC SYSNAM . . . GRPPRV READALL SECURITY SYSMAN>C This example shows how to create a command procedure that sets? the SYSMAN environment to the local node, and displays the? current profile. These commands execute when you enter the @ENV.COM command. 2.$ CREATE TIME.COM SET ENVIRONMENT/CLUSTER$ CONFIGURATION SHOW TIME $ MCR SYSMAN SYSMAN> @TIME8 System time on node NODE23: 19-JUN-2000 13:32:19.458 System time on node NODE24: 19-JUN-2000 13:32:27.798 System time on node NODE25: 19-JUN-2000 13:32:58.66; This example shows how to create and execute a command? procedure that shows the current date and time for all the nodes in the cluster. wwȯl1 ALFB There are several ALF subcommands. Select the one you want from the choices below. 2 ADDD Adds a new record to the automatic login facility (ALF) database.2 You can also create records for proxy accounts.A Requires read (R) and write (W) access to the SYSALF database& (SYS$SYSTEM:SYSALF.DAT by default). Format ALF ADD device user 3 Parameters deviceC Specifies the terminal name or port name that you want to assign? to a user name. The parameter device must be a terminal name@ if you do not specify qualifiers on the command line, and can? be either a logical name or an abbreviated device name. ThisB parameter accepts a maximum of 63 characters, including devices for proxy accounts. userD Specifies the user name of the account that you want to assign to! a particular terminal or port. 3 Qualifiers /TERMINAL /TERMINAL (default)D Checks whether the device name you specified is a terminal on theB target system. The parameter  device can be a logical name or anD abbreviated device name, which SYSMAN translates to a full device name. /PORTC Checks whether the device name you specified is a valid port. IfB the port name contains special characters, such as a slash (/),A or if it contains lowercase letters that you want to preserve,? you must enclose the port name within quotation marks (" ").; Be aware that anything within quotation marks is written: literally to the ALF database file. For example, if theA actual port name contains uppercase letters as well as special> characters, be sure to specify uppercase letters within the@ quotation marks. Otherwise, a mismatch will occur between theA actual port name and what is specified in the SYSALF.DAT file. /PROXY? Checks that the device name is in the NODE::USERNAME format. /LOGD Displays the device names and user names as they are added to the ALF database. 3 DescriptionB You can u se the ALF ADD command to associate a terminal or portA with a particular user name. This will enable certain users toA log in to certain terminals or ports without specifying a user name.= The ALF ADD command adds a new record to the ALF database. 3 Examples# 1.SYSMAN> ALF ADD TTA3 JBERGERON2 SYSMAN> ALF ADD "MN34C3/LC-1-2" FMARTIN /PORT@ In this example, the first command assigns terminal TTA3 toB user JBERGERON. The second command assigns port MN34C 3/LC-1-2 to user FMARTIN.B 2.SYSMAN> ALF ADD VMS:.ZKO.VMSORG.SYSMAN.CLIENT1::SYSTEM FOOBARC In this example, VMS:.ZKO.VMSORG.SYSMAN.CLIENT1::SYSTEM is theA value for the device parameter, which is assigned to FOOBAR. 2 REMOVE5 Removes one or more records from the ALF database.A Requires read (R) and write (W) access to the SYSALF database (SYS$SYSTEM:SYSALF.DAT). Format ALF REMOVE device 3 Parameter deviceA Specifi es the terminal name or port name whose record you wantC to remove from ALF. The device name is required, even if you use* qualifiers with the ALF REMOVE command.? You can use wildcard characters in the terminal name or port@ name. For example, if you specify the device TTA*, the systemA removes all records that start with the string TTA. The systemC does not, however, remove any records that start with the stringB $TTA (where is the system's SCSNODE name).? To remove records starting with $, you would have to specify% $TTA* or use two wildcards: *TTA*.> If you omit wildcard characters and enter a REMOVE command,< SYSMAN attempts to match the device name exactly. If moreA than one record matches the criteria, SYSMAN displays an error message. 3 Qualifiers /USERNAME /USERNAME=user< Enables you to remove a record in ALF for a specific user@ associated with a device. You must also enter the device whenC you use the /USERNAME qualifier. You can use wildcard characters with the /USERNAME qualifier. /CONFIRMB Displays a message asking you to verify that you want to remove the record. /LOGD Displays each device name and user name after it has been removed from the ALF database. 3 DescriptionB The ALF REMOVE command removes one or more records from the ALF database. 3 Examples( 1.SYSMAN> ALF REMOVE WORK1/USERNAME=*A The command in this example removes the records of the WORK1A device from the ALF datebase for all users. The asterisk (*) replaces user names.$ 2.SYSMAN> ALF REMOVE */USERNAME=*A The command in this example removes all records from the ALF@ database. The first asterisk (*) replaces device names; the) second asterisk replaces user names. 3.SYSMAN> ALF REMOVE _TTA3:+ SYSMAN> ALF REMOVE */USERNAME=SMITHSON> In this example, the first command removes the record for? terminal TTA3. The second command removes all records (for1 all devices) assigned to user name SMITHSON. 4.SYSMAN> ALF REMOVE *TTA*@ The command in this example removes all records for devices containing the string TTA. 5.SYSMAN> REMOVE TTA7 This command produces the following error message:M %SYSMAN-E-ALFWILCRDREQ, more than one record might match - Wildcard or& unit number of device required.&  NOTE@ Compaq recommends that you use caution when issuing REMOVEB commands from Version 6.1 or lower SYSMAN clients to Version 6.2 or higher systems.B For example, the following command issued from a system runningC OpenVMS Version 6.1 or lower to a system running OpenVMS VersionD 6.2 produces no error messages and deletes all records that match FOOBAR$TTA:L SYSMAN> SET ENVIRONMENT/NODE=FOOBAR ! FOOBAR runs OpenVMS Version 6.2. %SYSMAN-I-ENV, current command environment:# Individual nodes: FOOBAR9 Username SYSTEM will be used on nonlocal nodesN SYSMAN> ALF REMOVE TTA ! Does not produce an error message SYSMAN>> If you issue the same command from a system running OpenVMSA Version 6.1 or lower to another system running OpenVMS Version9 6.1 or lower, it produces the following error message:2 %SYSMAN-I-NODERR, error returned from node FOO8 -SMI-E-ALFNOMATCH, no records matched search criteriaD This is due to incorrect processing of wildcards prior to OpenVMS Version 6.2. 2 SHOW6 Displays one or more records from the ALF database.A Requires read (R) and write (W) access to the SYSALF database (SYS$SYSTEM:SYSALF.DAT). Format ALF SHOW [device] 3 Parameter [device]A Specifies the terminal name or port name whose record you wantC to display. You can use wildcard characters in the terminal nameA  or port name. Certain restrictions in wildcard matching of ALF3 records exist, as shown in the examples section. 3 Qualifiers /USERNAME /USERNAME=user? Displays the records held by the specified user. You can use+ wildcard characters with this qualifier. /OUTPUT /OUTPUT[=filespec]= Directs the output of the command to a file. If you do notB include a file specification with this qualifier, SYSMAN writes? the output to the file SYSMAN.LIS in your default directory. 3 Description? The ALF SHOW command displays one or more records in the ALF database. 3 Examples; 1.SYSMAN> ALF SHOW TTA* /USERNAME=MANESS /OUTPUT=ALF.TXTC In this example, the records for all terminals named TTAx thatA are assigned to user MANESS are selected and directed to the file ALF.TXT. 2.SYSMAN> ALF SHOW TTA*A This command displays only those records that start with the string TTA. 3.SYSMAN> ALF SHOW TTAA This command displays only those records that start with the string $TTA. 4.SYSMAN> ALF SHOW *TTA@ This command displays records that have device names ending with TTA. 5.SYSMAN> ALF SHOW *TTA*C This command displays all records that contain the string TTA. wwjl 1 ATTACH: Transfers control from your current process (which then4 hibernates) to the specified process in your job.D The ATTACH and SPAWN commands cannot be used if your terminal has an associated mailbox. Format ATTACH [process-name] 2 Parameter process-nameA Specifies the name of a parent process or a spawned subprocessC to which control passes. The process must already exist, be part? of your current job tree, and share the same input stream asD your current process. However, the process cannot be your current> process or a subprocess created with the /NOWAIT qualifier.B Process names can contain from 1 to 15 alphanumeric characters.D If a connection to the specified process cannot be made, an error message is displayed. 2 Qualifier /PARENTD Enables you to attach to the parent process. If no parent process( exists, you receive an error message. 2 DescriptionD The ATTACH command connects your input stream to another process.< You can use the ATTACH command to change control from one= subprocess to another  subprocess or to the parent process.B When you enter the ATTACH command, the parent process goes into> hibernation and your input stream connects to the specifiedA destination process. You can use the ATTACH command to connectB to a subprocess that is part of a current job (left hibernatingC as a result of the SPAWN/WAIT command or another ATTACH command)C as long as the connection is valid. No connection can be made toD the current process, to a process that is not part of the currentB job, or to a process that does not exist. If you attempt any of3 these connections, you receive an error message.> You can also use the ATTACH command in conjunction with the; SPAWN/WAIT command to return to a parent process withoutA terminating the created subprocess. See the description of the" SPAWN command for more details. 2 Example $ SPAWN) %DCL-S-SPAWNED, process SYSTEM_1 spawned; %DCL-S-ATTACHED, terminal now attached to process SYSTEM_1 $ RUN SYS$SYSTEM:SYSMAN SYSMAN> ATTACH SYSTEM4 %DCL-S-RETURNED, control returned to process SYSTEM $< In this example, the SPAWN command creates a subprocess= (SYSTEM_1). After you invoke SYSMAN and enter the ATTACHD command, you transfer the terminal's control back to the parent process (SYSTEM). wwl1 CLASS_SCHEDULEC There are several CLASS_SCHEDULE subcommands. Select the one you want from the choices below. 2 ADD2 The ADD  command creates a new scheduling class.? The class scheduler provides the ability to limit the amount@ of CPU time that a system's users receive by placing users inA scheduling classes. Each class is assigned a percentage of theC overall system CPU time. As the system runs, the combined set ofA users in a class is limited to the percentage of CPU execution! time allocated to their class.< Users might get some additional CPU time if the qualifier@ /WINDFALL is enabled for their scheduling class. Enabling the? qualifier /WINDFALL allows the system to give a small amount@ of CPU time to a scheduling class when the scheduling class's@ allotted time has been depleted, but a free CPU is available. Format# CLASS_SCHEDULE ADD class_name 3 Parameter class_nameA Specifies the name of the scheduling class. You must specify aD class name with the ADD command. The maximum length for this name is 16 characters. 3 Qua lifiers /ACCOUNTA Specifies which user is part of this scheduling class. This is" part of a user's SYSUAF record./ The syntax for this qualifier is as follows:, [/ACCOUNT = (name1, name2,...name"n")] /CPULIMITD Defines the maximum amount of CPU time that this scheduling classA can receive for the specified days and hours. You must specify& this qualifier when adding a class./ The syntax for this qualifier is as follows:7 /CPULIMIT = ([pr !imary], [h1-h2=time%],[h1=time%],E [,...],[secondary],[h1-h2=time%],[h1=time%],[,...])@ The h1-h2=time% syntax allows you to specify a range of hours= followed by the maximum amount of CPU time (expressed as aA percentage) to be associated with this set of hours. The firstD set of hours after the keyword PRIMARY specifies hours on primary? days; the set of hours after the keyword SECONDARY specifiesA hours on secondary days. The hours are inclusive; if you cl"assA schedule a given hour, access extends to the end of that hour. /PRIMEDAYSB Allows you to define which days are primary days and which days are secondary days./ The syntax for this qualifier is as follows:% [/PRIMEDAYS = ([no]day[,...])]@ You specify primary days as MON, TUE, WED, THU, FRI, SAT, andA SUN. You specify secondary days as NOMON, NOTUE, NOWED, NOTHU, NOFRI, NOSAT, and NOSUN.? The default is MON through FRI and NOSAT and NOSUN. Any# daysB omitted from the list take their default value. You can use theD DCL command, SET DAY, to override the class definition of primary and secondary days. /UICC Specifies which users are part of this scheduling class. This is" part of a user's SYSUAF record./ The syntax for this qualifier is as follows:$ [/UIC = (uic1,uic2,...uic"n")] /USERNAMEA Specifies which user is part of this scheduling class. This is" part of a user's SYSUAF record.$/ The syntax for this qualifier is as follows:- [/USERNAME = (name1, name2,...name"n")] /WINDFALLD Specifies that all processes in the scheduling class are eligible for windfall./ The syntax for this qualifier is as follows: [/WINDFALL])D By enabling windfall, you allow processes in the scheduling classD to receive a "windfall", that is, a small percentage of CPU time,B when the class's allotted CPU time has been depleted, and a CPUA is idle. %Rather than let the CPU remain idle, you might decide? that it is better to let these processes execute, even if it2 means giving them more than their alloted time.4 The default value is for windfall to be disabled. 3 Description? The format for the CLASS_SCHEDULE ADD command is as follows:( SYSMAN> CLASS_SCHEDULE ADD class_nameD You can use the /ACCOUNT, /UIC, or /USERNAME qualifier to specify4 which users are to be part of a scheduling class. 2 DELETEB& The DELETE subcommand deletes a scheduling class from the class scheduler database file. Format& CLASS_SCHEDULE DELETE class_name 3 Parameter class_nameA Specifies the name of the scheduling class. You must specify aB class name with the DELETE command. The maximum length for this name is 16 characters. 3 Qualifiers None. 2 MODIFYD The MODIFY subcommand changes the characteristics of a scheduling class. Format&' CLASS_SCHEDULE MODIFY class_name 3 Parameter class_nameA Specifies the name of the scheduling class. You must specify aB class name with the MODIFY command. The maximum length for this name is 16 characters. 3 Qualifiers /ACCOUNTA Specifies which user is part of this scheduling class. This is" part of a user's SYSUAF record./ The syntax for this qualifier is as follows:, [/ACCOUNT = (name1, name2,...name"n")] /CPULIMIT (D Defines the maximum amount of CPU time that this scheduling classA can receive for the specified days and hours. You must specify& this qualifier when adding a class./ The syntax for this qualifier is as follows:7 /CPULIMIT = ([primary], [h1-h2=time%],[h1=time%],E [,...],[secondary],[h1-h2=time%],[h1=time%],[,...])@ The h1-h2=time% syntax allows you to specify a range of hours= followed by the maximum amount of CPU time (expressed as aA percent)age) to be associated with this set of hours. The firstD set of hours after the keyword PRIMARY specifies hours on primary? days; the set of hours after the keyword SECONDARY specifiesA hours on secondary days. The hours are inclusive; if you classA schedule a given hour, access extends to the end of that hour. /PRIMEDAYSB Allows you to define which days are primary days and which days are secondary days./ The syntax for this qualifier is as follows:% [/P*RIMEDAYS = ([no]day[,...])]@ You specify primary days as MON, TUE, WED, THU, FRI, SAT, andA SUN. You specify secondary days as NOMON, NOTUE, NOWED, NOTHU, NOFRI, NOSAT, and NOSUN.? The default is MON through FRI and NOSAT and NOSUN. Any daysB omitted from the list take their default value. You can use theD DCL command, SET DAY, to override the class definition of primary and secondary days. /UICC Specifies which users are part of this scheduling class. This i+s" part of a user's SYSUAF record./ The syntax for this qualifier is as follows:$ [/UIC = (uic1,uic2,...uic"n")] /USERNAMEA Specifies which user is part of this scheduling class. This is" part of a user's SYSUAF record./ The syntax for this qualifier is as follows:- [/USERNAME = (name1, name2,...name"n")] /WINDFALLD Specifies that all processes in the scheduling class are eligible for windfall./ The syntax for this qualifier is as, follows: [/WINDFALL])D By enabling windfall, you allow processes in the scheduling classD to receive a "windfall," that is, a small percentage of CPU time,D when the class's allotted CPU time has been depleted and a CPU isC idle. Rather than let the CPU remain idle, you might decide that@ it is better to let these processes execute, even if it means, giving them more than their alloted time.4 The default value is for windfall to be disabled. 3 Description@- To remove a time restriction, specify a zero (0) for the time: percentage associated with a particular range of hours.B To remove a name or uic value, you must specify a minus sign in front of each name or value. 2 RESUMEA The RESUME subcommand complements the suspend command. You use> this command to resume a scheduling class that is currently suspended. Format& CLASS_SCHEDULE RESUME class_name 3 Parameter class_nameA Specifies t.he name of the scheduling class. You must specify aB class name with the RESUME command. The maximum length for this name is 16 characters. 3 Qualifiers None. 2 SHOWC The SHOW subcommand displays the characteristics of a scheduling class. Format3 CLASS_SCHEDULE SHOW [class_name] [/qualifier] 3 Parameter class_name? Specifies the name of the scheduling class. You must specify@ a class name or the /ALL qualifier with the SHO/W command. The6 maximum length for the class name is 16 characters. 3 Qualifiers /ALLC Displays all scheduling classes. The qualifier must be specified if no class name is given. /FULL8 Displays all information about this scheduling class. 3 Description= By default, a limited display of data is shown by the SHOW2 subcommand. The default displays the following: o Name7 o Maximum CPU time or times for each range of hours% o Pr0imary days and secondary days o Windfall settings 2 SUSPENDB The SUSPEND subcommand suspends the specified scheduling class. Format' CLASS_SCHEDULE SUSPEND class_name 3 Parameter class_nameA Specifies the name of the scheduling class. You must specify aC class name with the SUSPEND command. The maximum length for this name is 16 characters. 3 Qualifiers None. 3 Description> When you suspend a scheduling class, al1l processes that are? part of the scheduling class remain as part of the class but" are granted unlimited CPU time. wwבl1 CONFIGURATIONB There are several CONFIGURATION subcommands. Select the one you want from the choices below. 2 SET 3 CLUSTER_AUTHORIZATION2 Modifies security data in a local area cluster. Requires SYSPRV privilege. Format, CONFIGURATION SET CLUSTER_AUTHORIZATION 4 Qualifiers /GROUP_NUM2BER /GROUP_NUMBER=[n]9 Specifies the cluster group number that is recorded in< SYS$SYSTEM:CLUSTER_AUTHORIZE.DAT. A group number uniquely@ identifies each local area cluster on a single Ethernet. This@ number must be in the range from 1 to 4095 or 61440 to 65535. /PASSWORD /PASSWORD=passwordB Specifies a password for cluster access. A password consists of@ 1 to 31 characters, including alphanumeric characters, dollar@ signs, and underscores. A passw 3ord provides a second level ofC validation to ensure the integrity of individual clusters on theA same Ethernet that accidentally use identical group numbers. AD password also prevents an intruder who discovers the group number from joining the cluster. 4 DescriptionC The CONFIGURATION SET CLUSTER_AUTHORIZATION command modifies theA group number and password of a local area cluster, as recordedA in SYS$SYSTEM:CLUSTER_AUTHORIZE.DAT. If your configuration has@ multi 4ple system disks, SYSMAN automatically updates each copyC of CLUSTER_AUTHORIZE.DAT, provided the environment is defined asB a cluster (SET ENVIRONMENT/CLUSTER). For more information about; CLUSTER_AUTHORIZE.DAT, refer to OpenVMS Cluster Systems.' CAUTION@ If you change either the group number or the password, you% must reboot the entire cluster.A The file CLUSTER_AUTHORIZE.DAT is initialized during execution= of CLUSTER_CONFIG.COM a5nd maintained through SYSMAN. UnderC normal conditions, altering records in the CLUSTER_AUTHORIZE.DAT@ file interactively is not necessary. To protect the integrity? of the cluster membership use the CONFIGURATION SET CLUSTER_ AUTHORIZATION command. 4 Example, SYSMAN> SET ENVIRONMENT/CLUSTER/NODE=NODE21' SYSMAN> SET PROFILE /PRIVILEGES=SYSPRVA SYSMAN> CONFIGURATION SET CLUSTER_AUTHORIZATION/PASSWORD=GILLIAN: %SYSMAN-I-CAFOLDGROUP, existing group will not be changed- %6SYSMAN-I-GRPNOCHG, Group number not changed8 SYSMAN-I-CAFREBOOT, cluster authorization file updated.' The entire cluster should be rebooted.@ The CONFIGURATION SET CLUSTER_AUTHORIZATION command in this> example sequence modifies the cluster password. Note that? the environment is defined to be a cluster, and the SYSPRVC privilege is established before entering the CONFIGURATION SET# CLUSTER_AUTHORIZATION command. 3 TIME$ Modifies the current system time.7B Requires OPER, LOG_IO, and SYSPRV privileges, and, in a cluster! environment, SYSLCK privilege. Format" CONFIGURATION SET TIME [time] 4 Description> The CONFIGURATION SET TIME command enables you to reset the@ system time. Specify a time value using the following format:! [dd-mmm-yyyy[:]] [hh:mm:ss.cc]> You can also enter a delta time value. Refer to the OpenVMS9 User's Manual for more information about time formats.A In an environment of indivi 8dual nodes, SYSMAN sets the time toB the specified value on each node. Without a time specification,C SYSMAN sets the time according to the time-of-year clock on each node.A In an OpenVMS Cluster environment, SYSMAN sets the time to the? specified value on each node. If you do not specify a value,A SYSMAN uses the time-of-year clock. In a local cluster, SYSMANB reads the clock on the node from which you are executing SYSMANB and assigns this value to all nodes in the cl 9uster. In a remote@ OpenVMS Cluster, SYSMAN reads the clock on the target node inA the cluster and assigns that value to all nodes. Note that theD time-of-year clock is optional for some processors; refer to your. processor handbook for further information.C SYSMAN uses special processing in an OpenVMS Cluster environmentC to ensure that all processors in the cluster are set to the sameB time. Because of communication and processing delays, it is notA possible to synchroni :ze clocks exactly. However, the variationA is typically less than a few hundredths of a second. If SYSMANA cannot set the time to within one half second of the specified? time, you receive a warning message that names the node that$ failed to respond quickly enough.> As a result of slight inaccuracies in each processor clock,= times on various members of a cluster tend to drift apart.A The following procedure synchronizes system times in a cluster environment: $; SYNCH_CLOCKS: $ RUN SYS$SYSTEM:SYSMAN! SET ENVIRONMENT/CLUSTER CONFIGURATION SET TIME EXIT $ WAIT 6:00:00 $ GOTO SYNCH_CLOCKS@ The procedure sets the time on all cluster nodes to the valueB obtained from the local time-of-year clock, waits 6 hours, then# resets the time for the cluster. 4 Example4 SYSMAN> SET ENVIRONMENT/NODE=(NODE21,NODE22,NODE23)& SYSMAN> SET PROFILE /PRIVILEGE=LOG_IO( SYSMAN> CONFIGURATION SET TIME 12:38:<00@ The CONFIGURATION SET TIME command in this example sequence< modifies the system time on NODE21, NODE22, and NODE23. 2 SHOW 3 CLUSTER_AUTHORIZATIONB Displays the group number and multicast address of a local area cluster. Requires SYSPRV privilege. Format- CONFIGURATION SHOW CLUSTER_AUTHORIZATION 4 Qualifier /OUTPUT /OUTPUT[=filespec]@ Redirects output from SYS$OUTPUT to the specified file. If no> file spec =ification is provided, SYSMAN writes the output to' SYSMAN.LIS in the current directory. 4 Description@ The CONFIGURATION SHOW CLUSTER_AUTHORIZATION command displays? the group number and multicast address, and Ethernet address@ used to send a message to all nodes in the cluster. The groupC number and multicast address are recorded in SYS$SYSTEM:CLUSTER_2 AUTHORIZE.DAT during the CLUSTER_CONFIG dialog.C In a cluster or multinode environment, SYSMAN displays the group>> number of the first node and then displays the names of any@ nodes in the cluster whose group numbers, passwords, or both, are different. 4 Example, SYSMAN> SET ENVIRONMENT/CLUSTER/NODE=NODE21 . . .& SYSMAN> SET PROFILE /PRIVILEGE=SYSPRV1 SYSMAN> CONFIGURATION SHOW CLUSTER_AUTHORIZATION( Node NODE23: Cluster group number 65240% Multicast address: AB-00-04-01-F2-FFA The CONFIGURATION SHOW CLUSTER_AUTHORIZATION command in this? example displays the group ?number and multicast address ofD NODE21. Because the group number and password on other nodes inD the cluster are identical, no further information is displayed. 3 TIME; Displays the current date and system time to the nearest hundredth of a second. Format CONFIGURATION SHOW TIME 4 Qualifier /OUTPUT /OUTPUT[=filespec]@ Redirects output from SYS$OUTPUT to the specified file. If no> file specification is provided, SYSMAN writes@ the output to' SYSMAN.LIS in the current directory. 4 Example, SYSMAN> SET ENVIRONMENT/CLUSTER/NODE=NODE21 . . . SYSMAN> CONFIGURATION SHOW TIME5 System time on node NODE21: 19-JUN-2000 13:32:19.455 System time on node NODE22: 19-JUN-2000 13:32:27.795 System time on node NODE23: 19-JUN-2000 13:32:58.66A The CONFIGURATION SHOW TIME command in this example displays3 the system times for all nodes in the cluster. wwwMΛl 1 DEFINE A2 /KEYA Defines a key to execute a SYSMAN command. This enables you toB press the key to enter a command, instead of typing the command name. Format DEFINE/KEY key-name string 3 Parameters key-nameD Specifies the name of the key you are defining. Use the key names- in the following table when defining keys.- Key Name VT100 LK201/LK401% PF1 PF1 PF1% PF2 PF2 PF2% PF3 B PF3 PF3% PF4 PF4 PF4, KP0, KP1-KP9 keypad 0-9 keypad 0-9, PERIOD period key period key+ COMMA comma key comma key+ MINUS minus key minus key+ ENTER ENTER key ENTER key, UP, DOWN, LEFT, arrow keys arrow keys RIGHT8 FIND, INSERT_HERE - Find, Insert Here keys5 REMOVE, SELECT - Remove, Select keys5 PREV_SCREEN - C Previous Screen key1 NEXT_SCREEN - Next Screen key/ HELP, DO - Help, Do keys/ F6-F10, F11-F14 - function keys/ F17-F20 - function keys stringC Specifies the string you want entered when you press the defined@ key. For example, you can define string as the SYSMAN command$ SHOW ENVIRONMENT or SHOW PROFILE. 3 Qualifiers /ECHO /ECHO (default) /NOECHO@ SpecifiDes whether the command line echoes after you press the@ defined key. Note that you cannot define a key using both the' /NOECHO and /NOTERMINATE qualifiers. /IF_STATE /IF_STATE=state_list /NOIF_STATED Specifies a list of states, any one of which must be set in order@ to enable the specified key definition. If you omit or negate. this qualifier, the current state prevails. /LOCK_STATE /LOCK_STATE /NOLOCK_STATE (default)D Retains tEhe state specified by the /SET_STATE qualifier until you3 use the /SET_STATE qualifier again to change it. /SET_STATE /SET_STATE /NOSET_STATEA Associates a state with the key you are defining. A state name= can be any alphanumeric string. If you omit or negate thisD qualifier, the current state remains unchanged. You cannot define= a key using both the /SET_STATE and /TERMINATE qualifiers. /TERMINATE /TERMINATE /NOTERMINATE@ Deter Fmines whether the specified command string executes whenC you press the key. When you use /NOTERMINATE, you must press theD Return key to execute the command string. You cannot define a key7 using both the /SET_STATE and /TERMINATE qualifiers. 3 DescriptionA The DEFINE/KEY command assigns a key to a SYSMAN command. This> enables you to execute the command by pressing the key. You@ can confirm which keys you have defined by using the SHOW KEY command.< When you exGit from SYSMAN, any SYSMAN key definitions you> established will be lost unless you define them in a SYSMAN initialization file. 3 Examples+ 1.SYSMAN> DEFINE /KEY PF1 "SHOW PROFILE"? This example shows how to define the keypad key PF1 as the= SYSMAN command SHOW PROFILE. To execute the SHOW PROFILE0 command, press PF1 and then the Return key.A 2.SYSMAN> DEFINE /KEY KP0 /TERMINATE "CONFIGURATION SHOW TIME"= This example shows how to define the keypHad key 0 as the> CONFIGURATION SHOW TIME command. The /TERMINATE qualifier? causes the SYSMAN command to execute when you press keypad* key 0 without having to press Return. wwZћl 1 DISKQUOTAC There are several DISKQUOTA subcommands. Select the one you want from the choices below. 2 ADD? Adds an entry to a disk quota file and initializes the usage count to zero.0 Requires write (W) access to the quota file. Format I DISKQUOTA ADD owner 3 Parameter ownerD Specifies the user identification code (UIC) or rights identifierA for which the quota entry is added. You can specify the UIC inA numeric or alphanumeric format. For complete information aboutD UIC specification, refer to the OpenVMS Guide to System Security.@ Rights identifiers are granted with the Authorize utility andB use an ID format rather than a UIC format. Refer to the OpenVMSC Programming Concepts Manual forJ a complete description of rights identifiers.= When working in nonlocal environments, be careful that the@ alphanumeric UIC or rights identifiers that you use are valid for the environment. 3 Qualifiers /DEVICE /DEVICE=device-specA Specifies the location of the quota file. SYSMAN validates theC device specification. You can specify a logical name for device-@ spec. If you do, the logical name is translated in the target environment.?K Without a device specification, SYSMAN uses the default disk@ on the target node. Unless you have set a default device withB the SET PROFILE command, the default disk is the current deviceA on the local node or the login default device on another node,, depending on the established environment. /OVERDRAFT /OVERDRAFT=valueD Specifies a positive integer that provides an overdraft value forA the specified UIC. If omitted, the overdraft value defaults to. the oLverdraft value in the entry for [0,0]. /PERMQUOTA /PERMQUOTA=value? Specifies a positive integer that provides the quota for theA specified UIC. If omitted, the permanent quota defaults to the- value of the quota in the entry for [0,0]. 3 DescriptionB The DISKQUOTA ADD command appends individual entries to a quotaD file on the specified disk. Note that the quota file must already exist and be enabled.? Unless you specify the permanent quota and overMdraft values,B SYSMAN applies the default values from the UIC entry [0,0]. You6 adjust UIC [0,0] with the DISKQUOTA MODIFY command. 3 Example- SYSMAN> SET ENVIRONMENT/NODE=(NODE21,NODE22), %SYSMAN-I-ENV, Current command environment:( Individual nodes: NODE21,NODE22; Username ALEXIS will be used on nonlocal nodes.& SYSMAN> SET PROFILE /PRIVILEGE=SYSPRV2 SYSMAN> DISKQUOTA ADD [MKT,MORSE] /DEVICE=WORK1 -& _SYSMAN> /PERMQUOTA=200 /OVERDRAFT=50< SYSMAN> DISKQUO NTA ADD PAYROLL /DEVICE=WORK1 /PERMQUOTA=10008 This command sequence performs the following tasks:C o Defines the management environment to be NODE21 and NODE22.A o Adds SYSPRV privilege to the user's current privileges in) order to write to the quota file.B o Adds UIC [MKT,MORSE] to the quota file on the device named> WORK1 on both NODE21 and NODE22, setting the permanentC quota to 200 disk blocks and the overdraft limit to 50 disk@ blOocks, for an absolute limit of 250 blocks. If the userD name MORSE has a unique UIC on the system, you can enter the following command:% SYSMAN> DISKQUOTA ADD MORSEA o Adds an entry for the rights identifier PAYROLL. Any user? holding the PAYROLL identifier can use this disk space. 2 CREATEC Creates and enables a quota file for a disk volume that does not currently contain one.C Requires write (W) access to the volume's master filPe directory> (MFD), plus one of the following items: SYSPRV privilege, a* system UIC, or ownership of the volume. Format DISKQUOTA CREATE 3 Qualifier /DEVICE /DEVICE=device-spec= Specifies the disk volume on which to create a quota file.C SYSMAN validates the device specification. A logical name may beC specified for device-spec. If so, it is translated in the target environment.? Without a device specification, SYSMAN uses the d Qefault disk@ on the target node. Unless you have set a default device withB the SET PROFILE command, the default disk is the current deviceA on the local node or the login default device on another node,, depending on the established environment. 3 DescriptionA The DISKQUOTA CREATE command creates a quota file for a volume$ that does not currently have one.< Only one quota file, [000000]QUOTA.SYS, can be present on@ any volume or volume set. As soon as you create aR quota file,B establish default values for quotas and overdrafts by adjusting? UIC [0,0] with the DISKQUOTA MODIFY command. When a disk hasC existing files, use the DISKQUOTA REBUILD command to have SYSMAN9 update the quota file to contain current usage values.& NOTEA Compaq recommends that you do not create and enable a quota@ file on the system disk unless users are allowed to create files on that disk. 3 Example SSYSMAN> SHOW ENVIRONMENT, %SYSMAN-I-ENV, Current command environment:% Node NODE24 of local cluster: Username ALEXIS will be used on nonlocal nodes SYSMAN> DO SHOW DEVICES . . .( SYSMAN> DISKQUOTA CREATE /DEVICE=DJA31:0 SYSMAN> DISKQUOTA MODIFY /DEVICE=DJA31: [0,0] -) _SYSMAN> /PERMQUOTA=10000 /OVERDRAFT=1006 The commands in this example sequence display the> characteristics of the current management environment andA verify the device name. Then thTey create a quota file on the0 disk DJA31 and set up default quota values. 2 DELETE& Removes an entry from a quota file.= See the command DISKQUOTA REMOVE for more information. TheB DISKQUOTA REMOVE and DISKQUOTA DELETE commands perform the same function. 2 DISABLE? Suspends the maintenance and enforcement of disk quotas on a@ volume in the current management environment; this applies to' each node that has the disk mounted.' U CAUTION= To use the DISKQUOTA DISABLE command on a disk that hasA been mounted on multiple nodes in a cluster, you must first7 specify the nodes in the SET ENVIRONMENT command.? Requires SYSPRV privilege, a system UIC, or ownership of the volume. Format DISKQUOTA DISABLE 3 Qualifier /DEVICE /DEVICE=device-spec< Specifies a disk volume on which to disable a quota file.C SYSMAN validates the device specification. VA logical name may beC specified for device-spec. If so, it is translated in the target environment.? Without a device specification, SYSMAN uses the default disk@ on the target node. Unless you have set a default device withB the SET PROFILE command, the default disk is the current deviceA on the local node or the login default device on another node,, depending on the established environment. 3 Description? The DISKQUOTA DISABLE command suspends quota operatioWns on a= volume. To permanently disable quotas on a device, disable; the quotas with the DISKQUOTA DISABLE command and delete? the file [000000]QUOTA.SYS. Otherwise, the system implicitlyA enables quotas when the disk is mounted, leaving invalid quota information.B If you enable the quota file later, enter the DISKQUOTA REBUILD2 command to update UIC entries and usage counts. 3 Examples0 1.SYSMAN> SET ENVIRONMENT/NODE=(AMANDA,BARRY), SYSMAN> DISKQUOTA X DISABLE /DEVICE=DJA1:D These commands suspend quota enforcement on disk DJA1, which is' mounted on nodes AMANDA and BARRY.& 2.SYSMAN> SET ENVIRONMENT/CLUSTER 10 %SYSMAN-I-ENV, current command environment:) Clusterwide on local cluster= Username STEIN will be used on nonlocal nodes5 SYSMAN> DO SHOW QUOTA/DISK=$6$dkd0:/USER=[0,0] 27 %SYSMAN-I-OUTPUT, command execution on node WALTER4 User [0,0] has 0 blocks used, 1000 available,YJ of 1000 authorized and permitted overdraft of 100 blocks on $6$DKD07 %SYSMAN-I-OUTPUT, command execution on node ARTOS24 User [0,0] has 0 blocks used, 1000 available,J of 1000 authorized and permitted overdraft of 100 blocks on $6$DKD07 %SYSMAN-I-OUTPUT, command execution on node ARTOS14 User [0,0] has 0 blocks used, 1000 available,J of 1000 authorized and permitted overdraft of 100 blocks on $6$DKD07 %SYSMAN-I-OUTPUT, command execution on node EXP ZERT4 User [0,0] has 0 blocks used, 1000 available,J of 1000 authorized and permitted overdraft of 100 blocks on $6$DKD00 SYSMAN> DISKQUOTA DISABLE/DEVICE=$6$dkd0: 35 SYSMAN> DO SHOW QUOTA/DISK=$6$dkd0:/USER=[0,0] 47 %SYSMAN-I-OUTPUT, command execution on node WALTER? %SYSTEM-F-QFNOTACT, disk quotas not enabled on this volume7 %SYSMAN-I-OUTPUT, command execution on node ARTOS2? %SYSTEM-F-QFNOTACT, disk quotas not enabled on this volume7 %SYSMAN-I[-OUTPUT, command execution on node ARTOS1? %SYSTEM-F-QFNOTACT, disk quotas not enabled on this volume7 %SYSMAN-I-OUTPUT, command execution on node EXPERT? %SYSTEM-F-QFNOTACT, disk quotas not enabled on this volume SYSMAN>8 In this example, the disk $6$dkd0: has been mounted clusterwide.@ 1 The SET ENVIRONMENT command sets the environment for all nodes in the cluster.@ 2 The output of this DO SHOW QUOTA command shows that disk, qu\otas are enabled over the cluster.C 3 The DISKQUOTA DISABLE command disables disk quotas over the entire cluster.@ 4 The output of this DO SHOW QUOTA command shows that disk" quotas have been disabled. 2 ENABLE< Resumes quota enforcement on a disk volume in the currentA management environment; this applies to each node that has the disk mounted.' CAUTION< To use the DISKQUOTA ENABLE command on a disk that] hasA been mounted on multiple nodes in a cluster, you must first7 specify the nodes in the SET ENVIRONMENT command.? Requires SYSPRV privilege, a system UIC, or ownership of the volume. Format DISKQUOTA ENABLE 3 Qualifier /DEVICE /DEVICE=device-spec= Specifies a disk volume on which to enable the quota file.C SYSMAN validates the device specification. A logical name may beC specified for device-spec. If so, it is translate^d in the target environment.? Without a device specification, SYSMAN uses the default disk@ on the target node. Unless you have set a default device withB the SET PROFILE command, the default disk is the current deviceA on the local node or the login default device on another node,, depending on the established environment. 3 Description= The DISKQUOTA ENABLE command reinstates the enforcement of@ quotas on a volume that had been suspended with the DISKQUOTAC _ DISABLE command. Whenever you enable quotas on a volume, use theD DISKQUOTA REBUILD command to update UIC entries and usage counts. 3 Examples1 1.SYSMAN> SET ENVIRONMENT/NODE=(NODE21,NODE22) SYSMAN> DISKQUOTA ENABLE SYSMAN> DISKQUOTA REBUILD? The DISKQUOTA ENABLE command in this example resumes quota? enforcement on the default disk DJA12, which is mounted onA NODE21 and NODE22. The DISKQUOTA REBUILD command updates the> quota file, correcting `quotas and adding any new entries.& 2.SYSMAN> SET ENVIRONMENT/CLUSTER 10 %SYSMAN-I-ENV, current command environment:) Clusterwide on local cluster= Username STEIN will be used on nonlocal nodes5 SYSMAN> DO SHOW QUOTA/DISK=$6$dkd0:/USER=[0,0] 27 %SYSMAN-I-OUTPUT, command execution on node WALTER? %SYSTEM-F-QFNOTACT, disk quotas not enabled on this volume7 %SYSMAN-I-OUTPUT, command execution on node ARTOS2? %SYSTEM-F-QFNOTACT, disk aquotas not enabled on this volume7 %SYSMAN-I-OUTPUT, command execution on node ARTOS1? %SYSTEM-F-QFNOTACT, disk quotas not enabled on this volume7 %SYSMAN-I-OUTPUT, command execution on node EXPERT? %SYSTEM-F-QFNOTACT, disk quotas not enabled on this volume/ SYSMAN> DISKQUOTA ENABLE/DEVICE=$6$dkd0: 35 SYSMAN> DO SHOW QUOTA/DISK=$6$dkd0:/USER=[0,0] 47 %SYSMAN-I-OUTPUT, command execution on node WALTER4 User [0,0] has 0 blocks used, 1000 available,J b of 1000 authorized and permitted overdraft of 100 blocks on $6$DKD07 %SYSMAN-I-OUTPUT, command execution on node ARTOS24 User [0,0] has 0 blocks used, 1000 available,J of 1000 authorized and permitted overdraft of 100 blocks on $6$DKD07 %SYSMAN-I-OUTPUT, command execution on node ARTOS14 User [0,0] has 0 blocks used, 1000 available,J of 1000 authorized and permitted overdraft of 100 blocks on $6$DKD07 %SYSMAN-I-OUTPUT, command execution on node EXPERTc4 User [0,0] has 0 blocks used, 1000 available,J of 1000 authorized and permitted overdraft of 100 blocks on $6$DKD08 In this example, the disk $6$dkd0: has been mounted clusterwide.@ 1 The SET ENVIRONMENT command sets the environment for all nodes in the cluster.@ 2 The output of this DO SHOW QUOTA command shows that disk% quotas have not been enabled.A 3 The DISKQUOTA ENABLE command enables disk quotas over the entire cdluster.@ 4 The output of this DO SHOW QUOTA command shows that disk2 quotas have been enabled over the cluster. 2 MODIFYA Changes an entry in a quota file or adjusts default values for? quotas and overdrafts. If a new quota limit is less than theA current usage count, SYSMAN issues a warning message before it implements the new quota.0 Requires write (W) access to the quota file. Format DISKQUOTA MODIFY owner 3 Parameter ow ener9 Specifies the user identification code (UIC) or rightsA identifier. You can specify the UIC in numeric or alphanumericB format. For complete information about UIC specification, refer+ to the OpenVMS Guide to System Security.@ Rights identifiers are granted with the Authorize utility andB use an ID format rather than a UIC format. Refer to the OpenVMSC Programming Concepts Manual for a complete description of rights identifiers.< When working in nonlocal enfvironments, make sure that the@ alphanumeric UIC or rights identifiers that you use are valid for the environment. 3 Qualifiers /DEVICE /DEVICE=device-specA Specifies the disk volume that contains the quota file. SYSMAN< validates the device specification. A logical name may beC specified for device-spec. If so, it is translated in the target environment.? Without a device specification, SYSMAN uses the default disk@ on the target node. Unlgess you have set a default device withB the SET PROFILE command, the default disk is the current deviceA on the local node or the login default device on another node,, depending on the established environment. /OVERDRAFT /OVERDRAFT=value@ Specifies a positive integer that provides an overdraft valueB for the specified UIC. If you omit a value, the overdraft value: defaults to the overdraft value in the entry for [0,0]. /PERMQUOTA /PERMQUOTA=value h? Specifies a positive integer that provides the quota for theC specified UIC. If you omit a value, the permanent quota defaults4 to the value of the quota in the entry for [0,0]. 3 DescriptionB The DISKQUOTA MODIFY command changes values in a quota file forA the disk named in the device specification. If you establish aD quota limit that is less than the current usage count, a user can1 still log in and out, but cannot create files.C After creating a quota file, iuse the DISKQUOTA MODIFY command toC set default values for quotas and overdrafts. UIC [0,0] sets theA default permanent quota and overdraft values for a quota file,? so you must change the entry [0,0] to values appropriate forC your installation. Unless you specify quota and overdraft valuesA when adding a file entry, SYSMAN applies these defaults to UIC entries. 3 Examples( 1.SYSMAN> SET ENVIRONMENT/NODE=NODE214 SYSMAN> DISKQUOTA MODIFY /DEVICE=DUA12: [0, j0] -, _SYSMAN> /PERMQUOTA=3000 /OVERDRAFT=300A The commands in this example edit the entry for UIC [0,0] in9 the quota file on DUA12, which is located on NODE21.= 2.SYSMAN> DISKQUOTA MODIFY /DEVICE=SYS$DISK1 [TTD,DAVIS] - _SYSMAN> /PERMQUOTA=900A This command sets the permanent quota for UIC [TTD,DAVIS] to? 900 blocks, while making no change to the overdraft limit.; SYSMAN modifies the quota file that is located on disk* SYS$DISK1 in the current kenvironment.C If the user name DAVIS has a unique UIC on the system, you can! enter the following command:3 SYSMAN> DISKQUOTA MODIFY DAVIS/PERMQUOTA=900 2 REBUILDD Updates a quota file, adding new UICs and correcting usage counts for each user on the volume.@ Requires write (W) access to the quota file, plus one of theC following items: SYSPRV privilege, a system UIC, or ownership of the volume. Format DISKQUOTA REBUILD 3 Quallifier /DEVICE /DEVICE=device-specA Specifies the disk volume that contains the quota file. SYSMAN@ validates the device specification and translates any logical= name in the target environment before rebuilding the file.? Without a device specification, SYSMAN uses the default disk@ on the target node. Unless you have set a default device withB the SET PROFILE command, the default disk is the current deviceA on the local node or the login default device o mn another node,, depending on the established environment. 3 Description= The DISKQUOTA REBUILD command reads the disk, recalculates? usage counts for all existing entries in QUOTA.SYS, and addsB new entries. It sets quota and overdraft values to the defaults@ set in UIC [0,0] if the entry did not previously exist. WhileC the DISKQUOTA REBUILD command is executing, file activity on theC volume is frozen. No files can be created, deleted, extended, or truncated.nD Use the DISKQUOTA REBUILD command in the following circumstances:B o After creating a quota file on a volume with existing files.B o When the quota file has been enabled after a period of beingB disabled. The command corrects the usage counts and adds any new UICs. 3 Example% SYSMAN> SET ENVIRONMENT /NODE=NODE21& SYSMAN> SET PROFILE /PRIVILEGE=SYSPRV) SYSMAN> DISKQUOTA ENABLE /DEVICE=DUA226:* SYSMAN> DISKQUOTA REBUILD /DEVICE=DUA226:C These commandos enable the quota file and reconstruct the usageD counts for all entries on disk DUA226, which is located on node NODE21. 2 REMOVE& Removes an entry from a quota file.0 Requires write (W) access to the quota file. Format DISKQUOTA REMOVE owner 3 Parameter owner9 Specifies the user identification code (UIC) or rightsA identifier. You can specify the UIC in numeric or alphanumericB format. For complete information about UIC specpification, refer+ to the OpenVMS Guide to System Security.D Rights identifiers are granted with the Authorize utility and useD an ID format rather than a UIC format. For more information about@ rights identifiers, refer to the OpenVMS Programming Concepts Manual.= When working in nonlocal environments, be careful that the@ alphanumeric UIC or rights identifiers that you use are valid for the environment. 3 Qualifier /DEVICE /DEVICE=device-spec q> Specifies the disk volume containing the quota file. SYSMAN@ validates the device specification and translates any logical@ name in the target environment before deleting the UIC entry.? Without a device specification, SYSMAN uses the default disk@ on the target node. Unless you have set a default device withB the SET PROFILE command, the default disk is the current deviceA on the local node or the login default device on another node,, depending on the established envirronment. 3 DescriptionA The DISKQUOTA REMOVE command eliminates the specified UIC from& the quota file on the named device.> If the usage count for the UIC is not zero, files remain on@ disk and the user can still log in, but any attempt to create or extend files will fail.) The UIC [0,0] entry cannot be removed. 3 Example" SYSMAN> SET ENVIRONMENT/NODE=MARS SYSMAN> SHOW PROFILEC %SYSMAN-I-DEFDIR, Default directory on node MARS -- WORK2:[CASEY]6 %SYSMsAN-I-DEFPRIV, Process privileges on node MARS -- TMPMGX OPER NETMBX SYSPRV4 SYSMAN> DISKQUOTA REMOVE /DEVICE=DUA45: [TTD,DAVIS]B These commands remove UIC [TTD,DAVIS] from the quota file for/ disk DUA45, which is located on node MARS. 2 SHOW1 Displays quotas, overdrafts, and usage counts.? Requires no additional privileges to display your own quota,> overdraft, and usage count, but otherwise requires read (R) access tto the quota file. Format DISKQUOTA SHOW owner 3 Parameter owner9 Specifies the user identification code (UIC) or rightsA identifier. You can specify the UIC in numeric or alphanumericB format. For complete information about UIC specification, refer+ to the OpenVMS Guide to System Security.@ Rights identifiers are granted with the Authorize utility andB use an ID format rather than a UIC format. Refer to the OpenVMSC Programming Concepts Manuual for a complete description of rights identifiers.A You can use an asterisk wildcard character (*) to specify the quota entry as follows:% Command DescriptionA DISQUOTA SHOW CJ Show user CJ (if CJ has a unique UIC on% the system)3 DISKQUOTA SHOW Show user CJ in group TTD [TTD,CJ]5 DISKQUOTA SHOW Show all users in group TTD [TTD,*]* DISKQUOTA SHOW * Show all entries 3 Qualifivers /DEVICE /DEVICE=device-specA Specifies the disk volume containing the quota file. DISKQUOTAD validates device specification and translates any logical name in8 the target environment before displaying UIC entries.? Without a device specification, SYSMAN uses the default disk@ on the target node. Unless you have set a default device withB the SET PROFILE command, the default disk is the current deviceA on the local node or the login default device on anwother node,, depending on the established environment. /OUTPUT /OUTPUT[=filespec]7 Directs output to the specified file. Without a file? specification, /OUTPUT defaults to SYSMAN.LIS in the current< directory on the local node where you are running SYSMAN. 3 Example SYSMAN> DISKQUOTA SHOW [ACCT,*]C This command displays quotas, overdrafts, and usage counts for1 all users in group ACCT on the default disk. ww0l1 DOxB Executes a DCL command or DCL command procedure on all nodes in& the current management environment.= Requires the privileges of the DCL command being executed. Format DO [command-line] 2 Parameter command-lineD Specifies a command string that SYSMAN passes to the command line! interface (CLI) for execution.? The command DO MCR SYSMAN [SYSMAN-command] is not supported. Instead, follow these steps:0 1. Enter MCR SYSMAN at the dollary ($) prompt.@ 2. At the SYSMAN> prompt, set the environment to the selected5 node or nodes with the SET ENVIRONMENT command.3 3. Enter a SYSMAN command at the SYSMAN> prompt.B For complete information about DCL command syntax, refer to the OpenVMS DCL Dictionary. 2 Qualifier /CONFIRMB Verifies that you want to perform a DO command on each node you: have specified with the SYSMAN command SET ENVIRONMENT.A When you use the /CONFIRM qualifier, the syzstem prompts you as follows:, Execute command for node ? [N]:% The following responses are valid:( YES NO QUIT ALL" TRUE FALSE " 1 0   Usage Notes/ o Affirmative answers are YES, TRUE, and 1.@ o Negative answers are NO, FALSE, 0, and pressing the Return key.D o You can use any combination of uppercase and lowercase letters for word{ responses.C o You can abbreviate word responses to one or more letters (forD example, T, TR, or TRU for TRUE), but these abbreviations must be unique.C o Entering QUIT or pressing Ctrl/C or Ctrl/Z indicates that you8 want to stop processing the command at that point.C o When you enter ALL, the command continues to process, but the) system displays no further prompts.@ o If you type a response that is not valid, SYSMAN issues an. error messag|e and redisplays the prompt. /OUTPUT /OUTPUT[=filespec]? Records output from the command in the specified file, which> is located on the node from which you are executing SYSMAN.? Position the qualifier immediately after the DO command. TheA default file specification is SYSMAN.LIS in the current deviceC and directory. SYSMAN prefaces output with the message "%SYSMAN-/ I-OUTPUT, command execution on node xxxxxx." /PAUSED Controls the rate at which }the system displays information. Using@ the /PAUSE qualifier causes the system to display informationC about one node at a time; the system prompts you to press ReturnA when you are ready to display information about the next node. 2 Description> The DO command executes the accompanying DCL command or DCLB command procedure on all nodes in the current environment. Each? DO command executes as an independent process, so no process@ context is retained between DO commands ~. For this reason, youD must express all DCL commands in a single command string, and you+ cannot run a program that expects input.B In an OpenVMS Cluster environment, SYSMAN executes the commandsB sequentially on all nodes in the cluster. Each command executes< completely before SYSMAN sends it to the next node in the> environment. Any node that is unable to execute the command@ returns an error message. SYSMAN displays an error message if7 the timeout period expires before the node responds.A Use the RSX command MCR to run programs located in SYS$SYSTEM.D The MCR command enables you to run a program and supply a command in a single command string.C The system cannot display output returned from a command of more. than 2048 characters without concatenation.? Three exceptions to be aware of when using the DO command in# clusters are the following ones:? o In a dual-architecture heterogeneous cluster running bothD OpenVMS VAX and OpenVMS Alpha, some uses of the DO command mayB require special handling. For example, if you are installingA images that are named differently in each architecture, youD can still use the DO command if you create logical name tables@ for VAX and for Alpha nodes. See the example sequence that. follows this description for an example.5 o Some DCL commands, such as MOUNT/CLUSTER or SET? QUORUM/CLUSTER, operate clusterwide by design. It is best@ to a void using these kinds of commands with the DO command: in SYSMAN when the environment is set to cluster. As? alternatives, you could leave SYSMAN temporarily with theC SPAWN command and execute these commands in DCL, or you couldD define the environment to be a single node within the cluster.C Similarly, operations on clusterwide logical names and tables$ operate clusterwide by design.B o Make sure that if you redefine the logical DCLTABLES, you doB so in SYLOGICALS.COM, not in SYSTARTUP_VMS.COM or elsewhere.D Otherwise, you will receive a command interpreter failure when. executing a DO command on a remote node. 2 Examples0 1.SYSMAN> SET ENVIRONMENT/CLUSTER/NODE=NODE21" SYSMAN> DO/OUTPUT SHOW DEVICE= The first command in this example defines the management@ environment to be the cluster where NODE21 is a member. The> second command executes a DCL command on each node in the? cluster. Output g oes to the file SYSMAN.LIS rather than to the terminal.6 2.SYSMAN> SET PROFILE /PRIVILEGES=(CMKRNL,SYSPRV) -! _SYSMAN> /DEFAULT=SYS$SYSTEM< SYSMAN> DO INSTALL ADD /OPEN/SHARED WRKD$:[MAIN]STATSHR< SYSMAN> DO MCR AUTHORIZE ADD JONES/PASSWORD=COLUMBINE -. _SYSMAN> /DEVICE=WORK1 /DIRECTORY=[JONES]= The first command in this example adds CMKRNL and SYSPRV@ privileges to the current profile because they are required? by the INSTALL command and the AUTHORIZ E command. The next@ command installs the file STATSHR. The last command sets upB an account for user JONES, specifying a password as well as a" default device and directory.C The MCR command in the last line of the example enables you toB invoke the AUTHORIZE command from SYS$SYSTEM and add a record& to the UAF in one command string.( 3.SYSMAN> SET ENVIRONMENT/NODE=NODE211 SYSMAN> SET PROFILE /DEFAULT=[CJ.PROGRAMS] -" _SYSMAN> /PRIVILEGES=NOSYSPRV$ SYSMAN> DO/OUTPUT @PROCESS_INFOD The commands in this example define the environment as a single> node and adjust the current privileges and directory. The@ DO command executes the command procedure PROCESS_INFO.COM,@ located in directory [CJ.PROGRAMS] and writes any output to> SYSMAN.LIS in the directory from which SYSMAN is running.F 4.$ CREATE/NAME_TABLE/PARENT=LNM$SYSTEM_DIRECTORY SYSMAN$NODE_TABLEF $ DEFINE/TABLE=SYSMAN$NODE_TABLE ALPHA_NODES NODE21,NODE22, NODE23D $ DEFINE/TABLE=SYSMAN$NODE_TABLE VAX_NODES NODE24,NODE25,NODE26 $ RUN SYS$SYSTEM:SYSMAN- SYSMAN> SET ENVIRONMENT/NODE=ALPHA_NODES0 %SYSMAN-I-ENV, current command environment:4 Individual nodes: NODE21,NODE22,NODE23> Username BOUCHARD will be used on nonlocal nodes9 SYSMAN> DO INSTALL REPLACE SYS$LIBRARY:DCLTABLES.EXE7 %SYSMAN-I-OUTPUT, command execution on node NODE217 %SYSMAN-I-OUTPUT, command execution on node NODE227 %SYSMAN-I-OUTPUT, command execution on node NODE23; SYSMAN> DO INSTALL REPLACE SYS$SYSTEM: COM_FORTRAN.EXE7 %SYSMAN-I-OUTPUT, command execution on node NODE217 %SYSMAN-I-OUTPUT, command execution on node NODE227 %SYSMAN-I-OUTPUT, command execution on node NODE23+ SYSMAN> SET ENVIRONMENT/NODE=VAX_NODES0 %SYSMAN-I-ENV, current command environment:4 Individual nodes: NODE24,NODE25,NODE26> Username BOUCHARD will be used on nonlocal nodes 9 SYSMAN> DO INSTALL REPLACE SYS$LIBRARY:DCLTABLES.EXE7 %SYSMAN-I-OUTPUT, command execution on node NODE247 %SYSMAN-I-OUTPUT, command execution on node NODE257 %SYSMAN-I-OUTPUT, command execution on node NODE26; SYSMAN> DO INSTALL REPLACE SYS$SYSTEM:FORTRAN$MAIN.EXE7 %SYSMAN-I-OUTPUT, command execution on node NODE247 %SYSMAN-I-OUTPUT, command execution on node NODE257 %SYSMAN-I-OUTPUT, command execution on node NODE26@ This example shows how you can define logical names for VAXB and Alpha nodes in a dual-architecture heterogeneous cluster,@ so that you can use the DO command to install architecture- specific images. 5.$ MCR SYSMAN$ SYSMAN> SET ENVIRONMENT/CLUSTER0 %SYSMAN-I-ENV, current command environment:) Clusterwide on local cluster< Username STEIN will be used on nonlocal nodes! SYSMAN> DO/CONFIRM SHOW TIME5 Execute command for node EXPERT? [N]: Y 7  %SYSMAN-I-OUTPUT, command execution on node EXPERT 22-MAR-2000 09:40:285 Execute command for node MODERN? [N]: Y 7 %SYSMAN-I-OUTPUT, command execution on node MODERN 22-MAR-2000 09:40:565 Execute command for node IMPOSE? [N]: N 5 Execute command for node ADU26A? [N]: Y . . .A The commands in this example show how to control whether the5 system displays time for each node in a cluster. 6.SYSMAN> DO/PAUSE SHOW TIME7 %SYSMAN-I-OUTPUT, command execution on node EXPERT 22-MAR-2000 09:40:13& Press return to continue 6 %SYSMAN-I-OUTPUT, command execution on node MODER 22-MAR-2000 09:40:41& Press return to continue 7 %SYSMAN-I-OUTPUT, command execution on node IMPOSE 22-MAR-2000 09:39:46& Press return to continue . . .C The commands in this example show how you can control the rate6 at which information is displayed on your system. wwwl1 EXIT? Terminates the SYSMAN session and returns control to the DCLD command level. Any profile changes, established on the local nodeD with the command SET PROFILE, are restored to their values at theD time SYSMAN was invoked. You can also press Ctrl/Z to exit at any time. Format EXIT wwwl1 IOA There are several IO subcommands. Select the one you want from the choices below. 2 AUTOCONFIGUREB This command is for use on Alpha systems only. It automatically? identifies and configures all hardware devices attached to aA system by connecting devices and loading their drivers. On VAX1 systems, use the SYSGEN command AUTOCONFIGURE.; You must have CMKRNL and SYSLCK privileges to use the IO AUTOCONFIGURE command. Format IO AUTOCONFIGURE 3 Qualifiers /SELECT /SELECT=(device_name)@ Specifies the device type to be automatically configured. UseB valid device names or mnemonics that indicate the devices to beA included in the configuration. You can use wildcard characters with this qualifier.B The /SELECT and /EXCLUDE qualifiers are not mutually exclusive,A as they are on VAX systems. You can specify both qualifiers on the command line.D This table shows examples of how the /SELECT qualifier works with ports PKA, PKB, and PIA:D COMMAND DEVICES CONFIGURED DEVICES NOT CONFIGURED2 /SELECT=P* PKA,PKB,PIA None1 /SELECT=PK* PKA,PKB PIA5 /SELECT=PKA* PKA PKB,PIA /EXCLUDE /EXCLUDE=(device_name)= Specifies the device type that should not be automatically@ configured. Use valid device names or mnemonics that indicateA the devices to be excluded from the configuration. You can use+ wildcard characters with this qualifier.B The /SELECT and /EXCLUDE qualifiers are not mutually exclusive,A as they are on VAX systems. You can specify both qualifiers on the command line. /LOG9 Controls whether the IO AUTOCONFIGURE command displays$ information about loaded devices. 3 Description= The IO AUTOCONFIGURE command identifies and configures allA hardware devices attached to a system. VAX system managers useB the SYSGEN command AUTOCONFIGURE. It connects devices and loadsC their drivers. You must have CMKRNL and SYSLCK privileges to use the IO AUTOCONFIGURE command. 3 Examples* 1.SYSMAN> IO AUTOCONFIGURE/EXCLUDE=DKA0A This command autoconfigures all devices on the system except DKA0.C IO AUTOCONFIGURE automatically configures all standard devices? that are physically attached to the system, except for the# network communications device.! 2.SYSMAN> IO AUTOCONFIGURE/LOGB The /LOG qualifier displays information about all the devices that AUTOCONFIGURE loads. 2 CONNECT= This command is for use on Alpha systems only. It connects? a hardware device and loads its driver, if the driver is notB already loaded. On VAX systems, use the SYSGEN command CONNECT.C You must have CMKRNL and SYSLCK privileges to use the IO CONNECT command. Format IO CONNECT device-name[:] 3 Parameters device-name[:]A Specifies the name of the hardware device to be connected. The- device name requires the following format:( device-type controller unit-number= For example, in the designation LPA0, LP is a line printer> on controller A at unit number 0. If you use the /NOADAPTER6 qualifier, the device is the software to be loaded. 3 Qualifiers /ADAPTER /ADAPTER=tr_number /NOADAPTER (default)C Specifies the nexus number of the adapter to which the specified?  device is connected. It is a nonnegative 32-bit integer. TheC /NOADAPTER qualifier indicates that the device is not associated< with any particular hardware. The /NOADAPTER qualifier is3 compatible with the /DRIVER_NAME qualifier only. /CSR /CSR=csr_addressB Specifies the CSR address for the device being configured. ThisA address must be specified in hexadecimal. You must precede theC CSR address with %X. The CSR address is a quadword value that isC loaded into IDB$Q_CSR without any interpretation by SYSMAN. This@ address can be physical or virtual, depending on the specific device being connected:- o /CSR=%X3A0140120 for a physical address= o /CSR=%XFFFFFFFF807F8000 for a virtual address (the sign8 extension is required for Alpha virtual addresses)A This qualifier is required if /ADAPTER=tr_number is specified. /DRIVER_NAME /DRIVER_NAME=filespec@ Specifies the name of the device driver that you ar e loading.; If you do not specify this qualifier, SYSMAN obtains the: default in the same way that the SYSGEN default name isC determined. For example, if you want to load the Compaq-suppliedA SYS$ELDRIVER.EXE, the prefix SYS$ must be present. Without theC SYS$, SYSMAN looks for ELDRIVER.EXE in SYS$LOADABLE_IMAGES. ThisA implementation separates the user device driver namespace from/ the Compaq-supplied device driver namespace. /LOG' /LOG=(ALL,CRB,DDB,DPT,IDB,SB,UCB) /NOLOG (default)B Controls whether SYSMAN displays the addresses of the specified> control blocks. The default value for the /LOG qualifier is? /LOG=ALL. If /LOG=UCB is specified, a message similar to the following one is displayed:> %SYSMAN-I-IOADDRESS, the UCB is located at address 805AB000 /MAX_UNITS( /MAX_UNITS=maximum-number-of-unitsD Specifies the maximum number of units the driver can support. TheA default is specified in the driver prologue table (DPT) of theA driver. If the number is not specified in the DPT, the defaultC is 8. This number must be greater than or equal to the number of= units specified by /NUM_UNITS. This qualifier is optional. /NUM_UNITS /NUM_UNITS=number-of-unitsC Specifies the number of units to be created. The starting device? number is the number specified in the device name parameter.A For example, the first device in DKA0 is 0. Subsequent devicesA are numbered sequentially. The default is 1. This qualifier is optional. /NUM_VEC /NUM_VEC=vector-count? Specifies the number of vectors for this device. The default> vector count is 1. The /NUM_VEC qualifier is optional. This? qualifier should be used only when using the /VECTOR_SPACINGB qualifier. When using the /NUM_VEC qualifier, you must also use3 the /VECTOR qualifier to supply the base vector. /SYS_ID% /SYS_ID=number-of-remote-system@ Indicates the SCS system ID of the remote system to which the> device is to be connected. It is a 64-bit integer; you must? specify the remote system number in hexadecimal. The default3 is the local system. This qualifier is optional. /VECTOR" /VECTOR=(vector-address,...)C Specifies the interrupt vectors for the device or lowest vector.D This is either a byte offset into the SCB of the interrupt vectorA for directly vectored interrupts or a byte offset into the ADPC vec tor table for indirectly vectored interrupts. The values mustA be longword aligned. To specify the vector address in octal orD hexadecimal, precede the address with %O or %X, respectively. TheD /VECTOR qualifier is required when you use the /ADAPTER=tr_numberD qualifier or the /NUM_VEC=vector-count qualifier. You can list up to 64 vectors. /VECTOR_SPACING5 /VECTOR_SPACING=number-of-bytes-between-vectorsA Specifies the spacing between vectors. Specify the amount as aA multiple of 16 bytes. The default is 16. You must specify bothD the base vector with /VECTOR and the number of vectors with /NUM_# VEC. This qualifier is optional. 3 DescriptionB The IO CONNECT command connects a hardware device and loads itsC driver, if the driver is not already loaded. VAX system managersB use the SYSGEN command CONNECT. You must have CMKRNL and SYSLCK, privileges to use the IO CONNECT command.B The chapter "Managing Peripheral Devices" in the OpenVMS System@ Manager's Manual contains information about file-based device configuration support. 3 ExamplesD 1.SYSMAN> IO CONNECT DKA0:/DRIVER_NAME=SYS$DKDRIVER/CSR=%X80AD00-> /ADAPTER=4/NUM_VEC=3/VECTOR_SPACING=%X10/VECTOR=%XA20/LOG@ %SYSMAN-I-IOADDRESS, the CRB is located at address 805AEC40@ %SYSMAN-I-IOADDRESS, the DDB is located at address 805AA740@ %SYSMAN-I-IOADDRESS, the DPT is located at address 80D2A000@ %SYSMAN-I-IOADDRESS, the IDB is located at address 805AEE80? %SYSMAN-I-IOADDRESS, the SB is located at address 80417F80@ %SYSMAN-I-IOADDRESS, the UCB is located at address 805B68C0C The command in this example connects device DKA0, loads driver4 SYS$DKDRIVER, and specifies the following data: Physical CSR address Adapter number Number of vectors Spacing between vectors Interrupt vector address= The /LOG qualifier displays the addresses of all control  blocks, as shown.D 2.SYSMAN> IO CONNECT DKA0:/DRIVER_NAME=SYS$DKDRIVER/CSR=%X80AD00-< /ADAPTER=4/VECTOR=(%XA20,%XA30,%XA40)/LOG=(CRB,DPT,UCB)@ %SYSMAN-I-IOADDRESS, the CRB is located at address 805AEC40@ %SYSMAN-I-IOADDRESS, the DPT is located at address 80D2A000@ %SYSMAN-I-IOADDRESS, the UCB is located at address 805B68C0C The command in this example connects device DKA0, loads driver4 SYS$DKDRIVER, and specifies the following data: Physical C SR address Adapter number' Addresses for interrupt vectors= The /LOG qualifier displays the addresses of the channelB request block (CRB), the driver prologue table (DPT), and the unit control block (UCB).E 3.SYSMAN> IO CONNECT FTA0:/DRIVER=SYS$FTDRIVER/NOADAPTER/LOG=(ALL)@ %SYSMAN-I-IOADDRESS, the CRB is located at address 805AEC40@ %SYSMAN-I-IOADDRESS, the DDB is located at address 805AA740@ %SYSMAN-I-IOADDRESS, the DPT is located at addres s 80D2A000@ %SYSMAN-I-IOADDRESS, the IDB is located at address 805AEE80? %SYSMAN-I-IOADDRESS, the SB is located at address 80417F80@ %SYSMAN-I-IOADDRESS, the UCB is located at address 805B68C0> The command in this example connects pseudoterminal FTA0,A loads driver SYS$FTDRIVER, and uses the /NOADAPTER qualifier@ to indicate that FTA0 is not an actual hardware device. The? /LOG=(ALL) qualifier displays the addresses of all control blocks, as shown.D F or more information about loading and configuing device drivers,6 refer to Writing OpenVMS Alpha Device Drivers in C. 2 FIND_WWIDC The IO FIND_WWID command probes all Fibre Channel ports, detectsA all previously undiscovered tapes and medium changers behind a@ Modular Data Router (MDR), and assigns a worldwide identifier> (WWID) to each one. The command also displays a list of theE devices and their assigned device names, and automatically recordsD this information in the SYS$SYSTEM:SYS$DEVICES.DAT file. Finally,< the command updates relevant local and clusterwide memory structures.D To configure newly attached Fibre Channel tapes, use this command8 prior to running the SYSMAN command IO AUTOCONFIGURE.B You must have CMKRNL privilege to use the IO FIND_WWID command.C For more information about Fibre Channel, see the Guidelines for" OpenVMS Cluster Configurations. Format IO FIND_WWID 3 Parameters None. 3 Qualifiers None. 3 DescriptionA Prior to configuring a tape device on Fibre Channel ports, the= worldwide identifier (WWID) of the device must be detected9 and stored, along with a device name, in the text fileB SYS$SYSTEM:SYS$DEVICES.DAT. You use the SYSMAN command IO FIND_ WWID to accomplish this.> The IO FIND_WWID command probes all Fibre Channel ports andD locates all tape and medium changer devices. For tapes and medium@ changers that have not been d etected by any previous IO FIND_B WWID command, IO FIND_WWID assigns a device name, retrieves theB WWID of the device, stores the device name and WWID data in theB SYS$SYSTEM:SYS$DEVICES.DAT file, and updates memory structures.; Because the main goal of IO FIND_WWID is to populate theD SYS$DEVICES.DAT file, you need to invoke the IO FIND_WWID commandB only one time for each new device. Note that using the IO FIND_@ WWID command for the first time detects all existing tape and5 medium changer devices on the system at that time.D Once the information is stored in the file, subsequent use of theB IO AUTOCONFIGURE command reads the file and configures the tapeB and medium changer devices automatically, loading or connectingA the device drivers as needed. The SYS$DEVICES.DAT file is readD during each system reboot, initiating the automatic configurationC of tapes and medium changers on the Fibre Channel. (IO FIND_WWID7 does not load or connect the ac tual device drivers.)& NOTEB A restriction exists in OpenVMS Version 7.3: if you add more@ devices to the system at a later time, you must powercycle> the MDR to update internal mapping information. You must@ also run the IO FIND_WWID command again, to append the new5 device information to the SYS$DEVICES.DAT file.? In an OpenVMS cluster environment, you must run the IO FIND_B WWID command on each node in the cluster to upd ate various dataC structures in memory. Alternatively, you can run IO FIND_WWID onA one node, and then reboot the other nodes that share that same@ system disk, because the SYS$DEVICES.DAT file is read at bootA time and causes memory structures to be correctly initialized.C In the case of multiple system disks in the cluster, ensure that> all copies of the SYS$DEVICES.DAT file are kept consistent,? preferably by running the IO FIND_WWID command on all nodes.= Alternative ly, you can run IO FIND_WWID to update just one= SYS$DEVICES.DAT file, and then manually edit the remaining? SYS$DEVICES.DAT files by cutting and pasting the appropriateB devnam/WWID records from the original file to the target files.= Compaq recommends that you refrain from copying the entireD original file to another system disk, because the SYS$DEVICES.DAT? file is also used to define Port Allocation Classes, and PACC entries could be inadvertently transferred to the target system. 3 Example SYSMAN> IO FIND_WWID3 %SYSMAN-I-OUTPUT, command execution on node SAMPLEI On port _SAMPLE$PGA0:, the following tape WWIDs and their proposed; device names have been found but not yet configured: [Device $2$GGA0]A WWID=04100024:"DEC TL800 (C) DEC3G9CCR82A017" [Device $2$MGA0]? WWID=04100022:"DEC TZ89 (C) DECCX939S2777" [Device $2$MGA1]? WWID= 04100022:"DEC TZ89 (C) DECCX942S6295"D This is a configuration example using a TL891 tape library. TheB SYSMAN command IO FIND_WWID displays a list of all previously6 undiscovered tape devices and their device names.C Note that the overall WWID consists of everything to the right> of the equal sign. Each such WWID is unique; however, theD header portion might not be unique, because the header reflects9 only the basic type and length of the the WWID data.C The IO FIND_WWID command automatically records the information> about the new tape devices in SYS$SYSTEM:SYS$DEVICES.DAT:( $ TYPE SYS$SYSTEM:SYS$DEVICES.DAT !4 ! Updated 23-OCT-2000 14:17:41.85: DEC TL800 ! [Device $2$GGA0]; WWID=04100024:"DEC TL800 (C) DEC3G9CCR82A017" ! !3 ! Updated 23-OCT-2000 14:17:41.93: DEC TZ89 ! [Device $2$MGA0]9 WWID=04100022:"DEC TZ89 (C) DECCX939S2777" ! !3 ! Updated 23-OCT-2000 14:17:42.01: DEC TZ89 ! [Device $2$MGA1]9 WWID=04100022:"DEC TZ89 (C) DECCX942S6295" !D You would then use the SYSMAN command IO CONFIGURE to configure; these devices. After you completed this step, the SHOW? DEVICE/FULL command would display the worldwide identifier of the tape. 2 LOADA This command is for use on Alpha systems only. It loads an I/O7 driver. On VAX systems, use the SYSGEN command LOAD.@ You must have CMKRNL and SYSLCK privileges to use the IO LOAD command.& NOTEA Be very careful when issuing an IO LOAD command because the( system does little error-checking. Format IO LOAD filespec 3 Parameters filespec; Specifies the file name of the driver to be loaded. This parameter is required. 3 Qualifiers /LOG /LOG=(ALL,DPT)B Controls whether SYSMAN displays information about drivers that@ have been loaded. The default value for the /LOG qualifier isA /LOG=ALL. The driver prologue table (DPT) address is displayed1 when either /LOG=DPT or /LOG=ALL is specified. 3 Description? The IO LOAD command loads an I/O driver. VAX system managers? use the SYSGEN command LOAD. You must have CMKRNL and SYSLCK) privileges to use the IO LOAD command. 3 Example! SYSMAN> IO LOAD/LOG SYS$DKDRIVER< %SYSMAN-I-IOADDRESS, the DPT is located at address 80D5A000D This example loads device SYS$DKDRIVER and displays the address( of the driver prologue table (DPT). 2 REBUILD= This command is for use on Alpha systems only. It rebuilds> device configuration tables in preparation for using the IO3 AUTOCONFIGURE command to reconfigure the system. Format IO REBUILD 3 Qualifiers /VERIFYC Causes SYSMAN to read and process the files S YS$SYSTEM:SYS$USER_C CONFIG.DAT and SYS$SYSTEM:CONFIG.DAT, but not to apply the filesA to the I/O database. Messages will be displayed for any errors? that are encountered. This command can be used by developers@ to test new changes to SYS$SYSTEM:SYS$USER_CONFIG.DAT without modifying the current system. 3 DescriptionD The IO REBUILD command rebuilds the system's device configurationC tables by reading and parsing the SYS$SYSTEM:SYS$USER_CONFIG.DAT' and SYS$SYSTEM:SYS$CONFIG.DAT files.? To debug modifications to the SYS$SYSTEM:SYS$USER_CONFIG.DATD file, you can use the IO REBUILD and IO AUTOCONFIGURE commands toD load drivers without having to reboot. Once you load a driver forB an adapter, however, you cannot reload it without rebooting the system. 3 Example SYSMAN> IO REBUILD SYSMAN> IO AUTOCONFIGURED The first command in this example rebuilds device configuration> tables. The second command reads the device con figuration8 tables and loads drivers for newly defined drivers. 2 REPLACE_WWID> This command allows a user to replace one tape drive behind? a Modular Data Router (MDR) wither another tape drive at theC same Fibre Channel (FC) Logical Unit Number (LUN) location. ThisD command updates all the necessary file and memory data structuresC with the WWID of the new tape drive. The name of the replacement< drive will be the same as the name of the original drive.@ This command requires CMKRNL privilege. It applies only to FC tapes behind an MDR.C For more information about Fibre Channel, see the Guidelines for" OpenVMS Cluster Configurations. Format IO REPLACE_WWID devnam 3 Parameters devnam) The device name of the new tape drive. 3 Qualifiers None. 3 DescriptionA You might, for example, need to replace a defective tape driveD with a new drive without rebooting the cluster, and the new driveD might need to retain the device name of the previous tape at that location. . When you use this command, keep in mind that:C o The replacement device must be set to the same SCSI target ID as the original device.D o You must stop all activity on the device before issuing the IO REPLACE_WWID command.B o The command requires CMKRNL privilege and applies only to FC tapes behind an MDR. 3 Example SYSMAN> IO REPLACE_WWID $2$MGA1@ T his command updates all the necessary file and memory data= structures with the WWID of the new tape drive, $2$MGA1. 2 SCSI_PATH_VERIFY> This command is for use on Alpha systems only. This commandB checks each SCSI and FC path in the system to determine whether> the attached device has been changed. If a device change is? detected, then the SCSI or FC path is disconnected in the IO? database. This allows the path to be reconfigured on the new1 device, by using the IO AUTOCONFIGURE command. Format IO SCSI_PATH_VERIFY 3 Description: You usually enter the IO SCSI_PATH_VERIFY command after: performing an online reconfiguration of a SCSI or an FC= interconnect. The command reads the device type and deviceC identifier on each SCSI and FC path in the system. If the device> does not match the data stored in the IO database, then theA path is disconnected in the IO database. Following an IO SCSI_= PATH_VERIFY command, you usually enter an IO AUTOCONFIGURE? command, which updates the IO database to match the new SCSI or FC configuration. 3 Example SYSMAN> IO SCSI_PATH_VERIFY SYSMAN> IO AUTOCONFIGURE@ The first command in this example checks all SCSI paths and> disconnects the ones that are no longer valid. The secondD command autoconfigures all devices that are physically attached to the system. 2 SET 3 EXCLUDE= This command is for use on Alpha systems only. It sets the? permanent exclusion list to be used when configuring devices automatically. Format$ IO SET EXCLUDE = (device_name) 4 Parameters (device_name): Specifies the device type to be excluded from automaticC configuration. Use valid device names or mnemonics that indicateB the devices to be included in the permanent exclusion list. You can specify wildcards. 4 Description@ Sets the permanent exclusion list to be used when configuring devices. 4 Example% SYSMAN> IO SET EXCLUDE=(DKC500,DKD*)C This example specifies that DKC500 and all DKD devices are not to be autoconfigured.@ Refer to the /SELECT qualifier for additional examples that& show how to specify device names. 3 PREFIXD This command is for use on Alpha systems only. It sets the prefixD list that is used to manufacture the IOGEN Configuration Building Module (ICBM) names. Format IO SET PREFIX =icbm_prefix 4 Parameters icbm_prefix= Specifies ICBM prefixes. These prefixes are used by the IO3 AUTOCONFIGURE command to build ICBM image names. 4 DescriptionB The IO SET PREFIX command sets the prefix list which is used to manufacture ICBM names. 4 Example' SYSMAN> IO SET PREFIX=(SYS$,PSI$,VME_)7 This example specifies the prefix names used by IOB AUTOCONFIGURE to build the ICBM names. The prefixes are SYS$, PSI$, and VME_. 2 SHOW 3 BUS> This command is for use on Alpha systems only. It lists all? the buses, node numbers, bus names, TR numbers, and base CSR= addresses on the system. This display exists primarily for internal engineering support.3 On VAX systems, use the SYSGEN command SHOW/BUS. 4 DescriptionA The IO SHOW BUS command lists all the buses, node numbers, busA names, TR numbers, and base CSR addresses. This display existsC primarily for internal engineering support. You must have CMKRNL privilege to use IO SHOW BUS. 4 Example SYSMAN> IO SHOW BUS; _Bus__________Node_TR#__Name____________Base CSR__________8 LSB 0 1 EV3 4MB FFFFFFFF86FA00008 LSB 6 1 MEM FFFFFFFF86FC40008 LSB 7 1 MEM FFFFFFFF86FCA0008 LSB 8 1 IOP FFFFFFFF86FD0000< XZA XMI-SCSI 0 3 XZA-SCSI 0000008001880000< XZA XMI-SCSI 1 3 XZA-SCSI 0000008001880000< XZA XMI-SCSI 0 4 XZA-SCSI 0000008001900000< XZA XMI-SCSI 1 4 XZA-SCSI 0000008001900000: XMI 4 2 LAMB 0000008001A00000< DEMNA 0 5 Generic XMI 0000008001E80000< DEMNA 0 6 Generic XMI 0000008001F00000C This example is from a DEC 7000 Model 600. Displays vary among different Alpha systems.@ The indentation levels are deliberate in this display. They@ indicate the hierarchy of the adapter control blocks in the@ system. The column titles in the display have the following meanings:  Column Titles Meaning( Bus Identity of the busA Node Index into the associated bus array; the bus slot= TR# Nexus number of the adapter to which the2 specified device is connected' Name Name of the device3 Base CSR  Base CSR address of the device? On Alpha systems, you can use the SDA command CLUE CONFIG toA display additional information including hardware adapters andB devices. This command is documented in the OpenVMS Alpha System Dump Analyzer Utility Manual.D For more information about loading and configuing device drivers,6 refer to Writing OpenVMS Alpha Device Drivers in C. 3 DEVICE= This command is for use on Alpha systems only. It displays? information about device drivers loaded into the system, theD devices connected to them, and their I/O databases. All addresses> are in hexadecimal and are virtual. On VAX systems, use the SYSGEN command SHOW/DEVICE. Format IO SHOW DEVICE 4 DescriptionC The IO SHOW DEVICE command displays information about the deviceA drivers loaded into the system, the devices connected to them, and their I/O databases.: The IO SHOW DEVICE command specifies that the following> i nformation be displayed about the specified device driver: Driver Name 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 block4 All addresses are in hexadecimal and are virtual.< Refer to A Comparison of System Management on OpenVMS AXP> and OpenVMS VAX and the OpenVMS System Manager's Manual for' additional information about SYSMAN. 4 Example SYSMAN> IO SHOW DEVICEA The following example is a sample display produced by the IO SHOW DEVICE command:C __Driver________Dev_DDB______CRB______IDB______Unit_UCB_____ SYS$FTDRIVER5 FTA 802CE930 802D1250 802D04C0B 0 801C3710 SYS$EUDRIVER5 EUA 802D0D80 802D1330 802D0D10B 0 801E35A0 SYS$DKDRIVER5 DKI 802D0FB0 802D0F40 802D0E60B 0 801E2520 SYS$PKADRIVER5 PKI 802D1100 802D13A0 802D1090B 0 801E1210 SYS$TTDRIVER OPERATOR NLDRIVER= SYS$TTDRIVER, OPERATOR, and NLDRIVER do not have devices associated with them. 3 EXCLUDE= This command is for use on Alpha systems only. It displays@ the permanent exclusion list used in the autoconfiguration of devices. Format IO SHOW EXCLUDE 4 DescriptionD The IO SHOW EXCLUDE command displays the permanent exclusion list@ on the console. This list is used in the autoconfiguration of devices. 4 Example SYSMAN> IO SHOW EXCLUDE %SYSMAN-I-?IOEXCLUDE, the current permanent exclusion list is: DKC500,DKD*@ This example shows the permanent exclusion list used in theC autoconfiguration of devices; the current list contains DKC500 and all DKD devices. 3 PREFIXA This command is for use on Alpha systems only. It displays the= current prefix list used in the manufacture of ICBM names. Format IO SHOW PREFIX 4 DescriptionA The IO SHOW PREFIX command displays the current prefix list onD the console. This list is used by the IO AUTOCONFIGURE command to build ICBM names. 4 Example SYSMAN> IO SHOW PREFIX? %SYSMAN-I-IOPREFIX, the current prefix list is: SYS$,PSI$,VME_@ This example shows the prefixes used by IO AUTOCONFIGURE to build ICBM names. wwl 1 LICENSEA There are several LICENSE subcommands. Select the one you want from the choices below. 2 LOAD9 Activates licenses registered in the LICENSE database.2 Requires CMKRNL, SYSNAM, and SYSPRV privileges.& NOTE< Except for the number of status messages returned, the5 following commands are functionally equivalent: SYSMAN> LICENSE LOAD $ LICENSE LOAD@ To see all the status messages on remote nodes for the DCL8 command, you can use the following SYSMAN command: SYSMAN> DO LICENSE LOAD Format LICENSE LOAD product 3 Parameter product> Specifies the name of the product whose license you want to activate. 3 Qualifiers /DATABASE /DATABASE=filespecC Specifies the location of the LICENSE database. The default fileA specification is SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB. Using the> /DATABASE qualifier is not necessary if you use the default& LICENSE database name and location. /PRODUCER /PRODUCER=stringD Specifies the name of the company t hat owns the product for which@ you have a license. Use this qualifier only if the product is$ from a company other than Compaq. 3 Description? You can use the LICENSE LOAD command to activate licenses onD multiple systems and on nonlocal systems in the system management? environment. The SYSMAN LICENSE commands are a subset of theC License Management Facility (LMF) commands. For more informationA about the LMF, refer to the OpenVMS License Management Utility Manual. 3 Example SYSMAN> LICENSE LOAD FORTRAN> This example activates the license for Compaq Fortran for> OpenVMS. Because the license is for a Compaq product, the6 command does not include the /PRODUCER qualifier. 2 UNLOAD; Deactivates licenses registered in the LICENSE database.2 Requires CMKRNL, SYSNAM, and SYSPRV privileges. Format LICENSE UNLOAD [product] 3 Parameter product> Specifies the name of the product whose license you want to> deactivate. If you enter the LICENSE UNLOAD command withoutB specifying a product name, the system deactivates all available registered licenses. 3 Qualifier /PRODUCER /PRODUCER=stringD Specifies the name of the company that owns the product for which@ you have a license. Use this qualifier only if the product is$ from a company other than Compaq. 3 DescriptionC You can use the LICENSE UNLOAD command to deactivate licenses onD multiple systems and on nonlocal systems in the system management? environment. The SYSMAN LICENSE commands are a subset of theC License Management Facility (LMF) commands. For more informationA about the LMF, refer to the OpenVMS License Management Utility Manual. 3 Example SYSMAN> LICENSE UNLOAD FORTRAN@ This command deactivates the license for Compaq Fortran for> OpenVMS. Because the license is for a Compaq product, the6 command does not include the /PRODUCER qualifier. wwwl 1 Overview< The System Management utility (SYSMAN) centralizes system@ management, enabling you to manage nodes or clusters from one location. Format RUN SYS$SYSTEM:SYSMAN wwl 1 PARAMETERSD There are several PARAMETERS subcommands. Select the one you want from the choices below. 2 DISABLE 3 CHECKS< Bypasses validation of parameter values. SYSMAN parameterA validation ensures that the parameters fall within the defined= minimum and maximum values specified in the PARAMETERS SET command. Format PARAMETERS DISABLE CHECKS 4 Description@ The PARAMETERS DISABLE CHECKS command enables you to override@ minimum and maximum values established for system parameters.= SYSMAN does parameter checks by default. If you attempt to@ set parameter values outside the allowable limits when checks@ are enabled, the operating system issues an error message. ByB disabling checks you can set parameter values regardless of the minimum and maximum limits.& NOTEA Range checks are enabled by default because Compaq suggests; that systems operate within these minimum and maximum@ values. Setting parameters outside these limits can result" in system failures or hangs. 4 Example SYSMAN> SET ENVIRONMENT/CLUSTER9 SYSMAN> SET PROFILE/DEFAULT=SYS$SYSTEM/PRIVILEGES=CMEXEC( SYSMAN> PARAMETERS SET MAXPROCESSCNT 10+ %SMI-E-OUTRANGE, parameter is out of range" SYSMAN> PARAMETERS DISABLE CHECKS( SYSMAN> PARAMETERS SET MAXPROCESSCNT 10> In this example, the initial attempt to set MAXPROCESSCNT> below the minimum fails because range checks are enabled.@ However, once range checks are disabled, the PARAMETERS SET$ MAXPROCESSCNT command succeeds. 2 ENABLE 3 CHECKSA Validates all parameter values to ensure that they fall within* the defined minimum and maximum values.> Because range checks are enabled by default, use PARAMETERSD ENABLE CHECKS after entering a PARAMETERS DISABLE CHECKS command. Format PARAMETERS ENABLE CHECKS 4 Example" SYSMAN> PARAMETERS DISABLE CHECKS SYSMAN> PARAMETERS SET WSMAX 20! SYSMAN> PARAMETERS ENABLE CHECKS SYSMAN> PARAMETERS SET WSMAX 30+ %SMI-E-OUTRANGE, parameter is out of range SYSMAN> PARAMETERS SHOW WSMAXC Parameter Name Current Default Minimum Maximum Unit Dynamic9 WSMAX 2000 1024 60 6400 pages? The PARAMETERS ENABLE CHECKS command in this example shows? that when range checking is disabled, the system accepts aB working set value (WSMAX) of 20. However, once range checking> is enabled with the PARAMETERS ENABLE CHECKS command, the? system does not accept a WSMAX below the minimum, which is 60. 2 SET> Changes the value of a specific parameter in the work area.B The PARAMETERS SET command does not modify parameter files, the? current system parameter file on disk, or the active system.@ For information about performing these modifications, see the PARAMETERS WRITE command. Format+ PARAMETERS SET parameter-name [value]& /STARTUP filespec 3 Parameters parameter-name> Specifies the name of the parameter to modify. Instead of aD name, you can enter a period (.) to change the value of the mostB recently displayed or the most recently modified parameter. SeeD the PARAMETERS SHOW command for an example of using the period in place of a parameter name.@ For a list of system parameters and further information about) them, use the command HELP PARAMETERS. value@ Specifies the new value for the parameter. Enclose values for? ASCII parameters in quotation marks if they contain embedded& spaces or other special characters.@ Typically the value is an integer or the keyword DEFAULT. The? keyword DEFAULT sets the parameter to its default value. TheA PARAMETERS SHOW command displays the defined minimum, maximum,B and default values for the parameter, which are required unlessA range checking is disabled with the command PARAMETERS DISABLE CHECKS. 3 Qualifiers /STARTUP /STARTUP filespecA Sets the name of the site-independent startup procedure to the? given file specification. A file specification has a maximumD length of 31 characters. The initial startup command procedure is SYS$SYSTEM:STARTUP.COM. 3 Examples) 1.SYSMAN> PARAMETERS SET PFCDEFAULT 20D This command assigns a value of 20 to the PFCDEFAULT parameter./ 2.SYSMAN> PARAMETERS SET GBLSECTIONS DEFAULTC This command assigns the default value (40) to the GBLSECTIONS parameter.; 3.SYSMAN> PARAMETERS SET/STARTUP SYS$SYSTEM:XSTARTUP.COM@ This command assigns SYS$SYSTEM:XSTARTUP.COM as the current0 site-independent startup command procedure. 2 SHOWD Displays the value of a parameter or a group of parameters in theB work area. In addition, the command shows the minimum, maximum,= and default values of a parameter and its unit of measure. Format& PARAMETERS SHOW [parameter-name] 3 Parameter parameter-nameB Specifies the name of a parameter or a period (.). A period isC interpreted as a request for the parameter specified in the last@ PARAMETERS SET or PARAMETERS SHOW command. The parameter nameB can be abbreviated, but the abbreviation must be unique because3 SYSMAN selects the first parameter that matches. 3 Qualifiers /ACP( Displays all Files-11 ACP parameters. /ALL0 Displays the values of all active parameters. /CLUSTER0 Displays all parameters specific to clusters. /DYNAMICD Displays all parameters that would be in effect immediately after/ you enter a PARAMETERS WRITE ACTIVE command. /GEN# Displays all general parameters. /HEXA Displays numeric parameters in hexadecimal rather than decimalA radix. Specify the /HEX system parameter name or the parameter: type. If you specify the /HEX qualifier with the /NAMES qualifier, /HEX is ignored. /JOB* Displays all job controller parameters. /LGI2 Displays all LOGIN security control parameters. /MAJOR*  Displays the most important parameters. /MULTIPROCESSING3 Displays parameters specific to multiprocessing. /NAMESB Displays only parameter names. You can combine other qualifiers with this one. /OUTPUT? Directs output to the specified file rather than SYS$OUTPUT.A Without a file specification, the output goes to SYSMAN.LIS in the current directory. /PAUSEC Controls the rate at which the system displays information about parameters.% /PQL: Displays the parameters for all default process quotas. /RMS@ Displays all parameters specific to OpenVMS Record Management Services (RMS). /SCS= Displays all parameters specific to OpenVMS Cluster System Communications Services. /SPECIAL+ Displays all special control parameters. /STARTUP? Displays the name of the site-independent startup procedure. /SYS) Displays all active system parameters. /TTY0 Displays all parameters for terminal drivers. 3 DescriptionD SYSMAN displays parameters in decimal unless you specify the /HEX9 qualifier. ASCII values are always displayed in ASCII.B Abbreviations for parameter names must be unique because SYSMAND displays the first parameter matching the abbreviation. AmbiguityB checks do not occur. For example, a specification of PARAMETERS> SHOW GBL displays the GBLSECTIONS parameter. To display the@ GBLPAGFIL parameter, you must specify PARAMETERS SHOW GBLPAGF. to avoid displaying the GBLPAGES parameter.C You can use a period (.) to indicate that you want to work withA the system parameter that you specified in the last PARAMETERS" SET or PARAMETERS SHOW command. 3 Examples( 1.SYSMAN> PARAMETERS SHOW GBLSECTIONSL Parameter Name Current Default Minimum Maximum Unit DynamicC GBLSECTIONS 100 40 20 -1 Sections! SYSMAN> PARAMETERS SET . 110 SYSMAN> PARAMETERS SHOW .L Parameter Name Current Default Minimum Maximum Unit DynamicC GBLSECTIONS 110 40 20 -1 Sections? In this example, the user first displays the values of the; GBLSECTIONS parameter and then refers to the parameter< with a period to set its current value to 110. The nextD PARAMETERS SHOW command also uses the period notation to obtain+ confirmation that the change occurred. 2.SYSMAN> PAR AMETERS SHOW/ACPC This command produces output similar to the following example:Parameters in use: ActiveIParameter Name Current Default Minimum Maximum Unit DynamicIACP_MULTIPLE 0 1 0 1 Boolean DCACP_SHARE 1 1 0 1 BooleanIACP_MAPCACHE 52 8 1 -1 Pages DIACP_HDRCACHE 138 128 2 -1 Pages DIACP_DIRCACHE 138 80 2 -1 Pages DIACP_DINDXCACHE 37 25 2 -1 Pages DIACP_WORKSET 0 0 0 -1 Pages DIACP_FIDCACHE 64 64 0 -1 File-Ids DIACP_EXTCACHE 64 64 0 -1 Extents DIACP_EXTLIMIT 300 300 0 1000 Percent/10 DIACP_QUOCACHE 130 64 0 -1 Users DIACP_SYSACC 4 8 0 -1 Directories DIACP_MAXREAD 32 32 1 64 Blocks DIACP_WINDOW 7 7 1 -1 Pointers DIACP_WRITEBACK 1 1 0 1 Boolean DIACP_DATACHECK 2 2 0 3 Bit-mask DIACP_BASEPRIO 8 8 4 31 Priority DIACP_SWAPFLGS 14 15 0 15 Bit-mask DCACP_XQP_RES 1 1 0 1 BooleanCACP_REBLDSYS 0 1 0 1 Boolean$ 3.SYSMAN> PARAMETERS SHOW/ACP/HEXA This command produces a hexadecimal display of the values of the ACP system parameters.Parameters in use: ActiveIParameter Name Current Default Minimum Maximum Unit DynamicIACP_MULTIPLE 00000000 00000001 00000000 00000001 Boolean DCACP_SHARE 00000001 00000001 00000000 00000001 BooleanIACP_MAPCACHE 00000034 00000008 00000001 FFFFFFFF Pages DIACP_HDRCACHE 0000008A 00000080 00000002 FFFFFFFF Pages DIACP_DIRCACHE 0000008A 00000050 00000002 FFFFFFFF Pages DIACP_DNDXCACHE 00000025 00000019 00000002 FFFFFFFF Pages DIACP_WORKSET 00000000 00000000 00000000 FFFFFFFF Pages DIACP_FIDCACHE 00000040 00000040 00000000 FFFFFFFF File-Ids DIACP_EXTCACHE 00000040 00000040 00000000 FFFFFFFF Extents DIACP_EXTLIMIT 0000012C 0000012C 00000000 000003E8 Percent/10 DIACP_QUOCACHE 00000082 00000040 00000000 FFFFFFFF Users DIACP_SYSACC 00000004 00000008 00000000 FFFFFFFF Directories DIACP_MAXREAD 00000020 00000020 00000001 00000040 Blocks DIACP_WINDOW 00000007 00000007 00000001 FFFFFFFF Pointers DIACP_WRITEBACK 00000001 00000001 00000000 00000001 Boolean DIACP_DATACHECK 00000002 00000002 00000000 00000003 Bit-mask DIACP_BASEPRIO 00000008 00000008 00000004 0000001F Priority DIACP_SWAPFLGS 0000000E 0000000F 00000000 0000000F Bit-mask DCACP_XQP_RES 00000001 00000001 00000000 00000001 BooleanCACP_REBLDSYS 00000000 00000001 00000000 00000001 Boolean$ 4.SYSMAN> PARAMETERS SHOW/STARTUP2 Startup command file = SYS$SYSTEM:STARTUP.COMC This command displays the name of the site-independent startup command procedure.. SYSMAN> PARAMETERS SHOW/PAUSE MAXPROCESSCNT+ Node EXPERT: Parameters in use: ACTIVEP Parameter Name Current Default Minimum Maximum Unit DynamicP -------------- ------- ------- ------- ------- ---- -------L MAXPROCESSCNT 160 32 12 8192 Processes$ Press return to continue + Node MODERN: Parame ters in use: ACTIVEP Parameter Name Current Default Minimum Maximum Unit DynamicP -------------- ------- ------- ------- ------- ---- -------L MAXPROCESSCNT 157 32 12 8192 Processes$ Press return to continue + Node IMPOSE: Parameters in use: ACTIVEP Parameter Name Current Default Minimum Maximum Unit DynamicP -------------- ------- ------- ------- ------- ---- -------L MAXPROCESSCNT 50 32 12 8192 Processes$ Press return to continue  . .@ The command in this example allows you to control the rate at& which the information is displayed. 2 USEB Reads a set of system parameters into the work area for display or modification. Format PARAMETERS USE source 3 Parameter sourceA The source of a system parameter file for data to be re ad into? the work area. The source can be any of the following items:@ ACTIVE Read parameters from memory. When you invoke SYSMAN,( active values are in effect.C CURRENT Read parameters from the default system parameter file,@ which is the source for parameters when you boot theB system. Using the current parameters requires read (R)1 access to the system parameters file.? o On Alpha systems, the file that contains curren t8 parameters is SYS$SYSTEM:ALPHAVMSSYS.PAR.= o On VAX systems, the file that contains current6 parameters is SYS$SYSTEM:VAXVMSSYS.PAR.< filespec Read parameters from a previously created systemC parameter file. The default file type is .PAR. You need$ read access to the file.> DEFAULT Read a parameter set containing the default valuesB for all parameters. These values are supplied with the operating system. 3 DescriptionA Depending on the source you enter with the command, PARAMETERS& USE activates the parameter values: o Stored in memory (ACTIVE)9 o Stored in the default boot parameter file (CURRENT)" o From another file (filespec). o From the system default values (DEFAULT) 3 Example SYSMAN> PARAMETERS USE DEFAULT SYSMAN> SET STARTUP_P1 "MIN"B The first command activates the default parameter values that? are supplied with the operating system. The second commandC sets the STARTUP_P1 system parameter to "minimum." This avoidsD starting all layered products on a system that is not tuned for0 them, which might cause the system to hang. 2 WRITEC Writes the contents of the work area to memory, to disk, or to a7 file, depending on the destination that you specify. Format" PARAMETERS WRITE destination 3 Parameter destination< The destination of a new para meter file can be any of the following ones:B ACTIVE Write parameters to memory. Using the ACTIVE parameter& requires CMKRNL privilege.A CURRENT Write parameters to the system parameters file, which> contains the current parameters on disk. Using the? current parameter requires write (W) access to the# system parameters file.? o On Alpha systems, the file that contains current8 parameters is SYS$SYSTEM:ALPHAVMSSYS.PAR.= o On VAX systems, the file that contains current6 parameters is SYS$SYSTEM:VAXVMSSYS.PAR.@ filespec Write parameters to a file. The default file type is7 .PAR and you need write access to the file. 3 DescriptionB The PARAMETERS WRITE command writes the system parameter valuesA and the name of the site-independent startup command procedureA from the work area to the active system in memory, the current? system parameter file on disk, or your choice of a parameterB file. You can write only dynamic parameter values to the active system.@ Both the PARAMETERS WRITE ACTIVE and PARAMETERS WRITE CURRENT8 commands send a message to OPCOM to record the event. 3 Examples0 1.SYSMAN> PARAMETERS WRITE SYS$SYSTEM:SPECIAL= This command creates a new parameter specification file.% 2.SYSMAN> PARAMETERS WRITE CURRENTD This command modifies the current system parameter file on disk" (SYS$SYSTEM:ALPHAVMSSYS.PAR). L!***************************************************************************wwl1 RESERVED_MEMORYD There are several RESERVED_MEMORY subcommands. Select the one you want from the choices below. 2 ADDB On Alpha systems, adds an entry to the Reserved Memory Registry= data file. (However, changes and additions to this file do@ not take effect until the next reboot of the system.) You can@ also use RESERVED_MEMORY ADD qualifiers to reserve a block of( contiguous page frame numbers (PFNs).C For information about the Reserved Memory Registry, refer to the= OpenVMS Alpha Guide to 64-Bit Addressing and VLM Features. Format! RESERVED_MEMORY ADD gs_name 3 Parameter gs_nameB Name of the memory-resident global section associated with this, reserved memory. You must specify a name. 3 Qualifiers /ALLOCATE /ALLOCATE /NOALLOCATE (defau lt)@ Allocates contiguous, aligned pages during the next reboot ofA the system. The allocated memory is deducted from the system'sC fluid page count, and the creation of the memory-resident globalB section results in the use of the allocate option. The physicalB alignment of the pages is based on the maximum granularity hintD factor that can be used to map the pages depending on the size of the reserved memory.C Possible granularity hint factors are 512 pages (or 4 MB) and 64C pages (or 512 KB). Therefore, assuming an 8 KB system page size,4 reserved memory is physically aligned as follows:9 o size >= 4 MB: physically aligned on a 4 MB boundary: o size < 4 MB: physically aligned on a 512 KB boundaryA /NOALLOCATE implies /NOZERO because /ZERO is incompatible with= /NOALLOCATE. If you specify /NOALLOCATE, or do not specify> /ALLOCATE, reserved memory is not allocated during the next> reboot of the system. Reserved memory is deducted only fromA the system's fluid page count, and the creation of the memory-B resident global section results in the use of the fault option. /GLOBAL_SECTION /GLOBAL_SECTION (default) /NOGLOBAL_SECTION? /NOGLOBAL_SECTION indicates that the memory qualifier is for? a privileged application instead of a group or system globalC section. (/GLOBAL_SECTION indicates that the memory qualifier isC for a group or system global section.) You cannot use /NOGLOBAL_@ SECTION with the qualifiers /GROUP, /SYSGBL, or /PAGE_TABLES.B AUTOGEN processes the Reserved Memory Registry data file in itsD GETDATA phase. The size of all entries is taken into account whenD calculating system parameters that depend on the available amount of physical memory.= The reservation size is also used to calculate the initial? size of the global page table unless the entry was specified as /NOGLOBAL_SECTION. /GROUP /GROUP=n= Establi shes that the reserved memory is for a group globalD section. The value n specifies the UIC group number (in octal) ofD the process that creates the group global section. Only processesB within the creator's UIC group number are allowed access to theD global section. For example, if a process with the UIC of [6,100]C is the creator of the group global section, the group number for the /GROUP qualifier is 6.= You cannot use the /GROUP qualifier with either /SYSGBL or /NOGLOBAL_SECTION qualifiers. /PAGE_TABLES /PAGE_TABLES (default) /NOPAGE_TABLES> Reserves additional memory for shared page tables. When theD memory-resident global section is created, shared page tables areB created for the global section. If you do not specify /ALLOCATEB (or if you specify /NOALLOCATE), the additional reserved memory> is deducted only from the system's fluid page count. If youC specify /ALLOCATE, additional contiguous, during the next rebootA of the system, aligned pages are allocated for the shared pageA table, and the additional reserved memory is deducted from the system's fluid page count.A If you do not specify /PAGE_TABLES, or if you specify /NOPAGE_D TABLES, additional memory is not reserved for shared page tables.B When the memory-resident global section is created, shared page1 tables are not created for the global section. /SIZE/ /SIZE=[size of reserved memory, unit: MB]< Specifies the number of megabytes to be deducted from theD system's fluid page count for this memory-resident global sectionD when the VMS$RESERVED_MEMORY.DATA data file is read during system initialization. /SYSGBL> Indicates that a reservation is for a system global memory- resident section.B You cannot combine this qualifier with the /GROUP or /NOGLOBAL_> SECTION qualifier. This qualifier is the default unless you' specify /GROUP or /NOGLOBAL_SECTION. /ZERO /ZERO /NOZERO (default)? /ZERO implies /ALLOCATE. If you specify /ZERO, pre-allocatedB pages are zeroed during system initialization. Zeroed pages areC required for memory-resident global sections; however, the pages9 do not need to be zeroed during system initialization.A /NOALLOCATE implies /NOZERO because /ZERO is incompatible with> /NOALLOCATE. If you do not specify /ZERO, or if you specify< /NOZERO, pre-allocated pages are not zeroed during systemB initialization. Instead, these pages are zeroed when the global section is created. 3 Example@ SYSMAN> RESERVED_MEMORY ADD DFW$GS_1 /NOPAGE /GROUP=100 /SIZE=1@ SYSMAN> RESERVED_MEMORY ADD DFW$GS_2 /PAGE /SIZE=2 /ALLOC /ZERO3 SYSMAN> RESERVED_MEMORY ADD DFW$GS_3 /PAGE /SIZE=3D The commands in this example add entries to the Reserved MemoryB Registry data file. (The example for the RESERVED_MEMORY SHOW4 command displays the values for these entries.) 2 FREE A On a running Alpha system, frees reserved memory. This commandD does not affect the contents of the Reserved Memory Registry data@ file; it affects only the memory with the running system. YouB can also use RESERVED_MEMORY FREE qualifiers to free a block of( contiguous page frame numbers (PFNs).C For information about the Reserved Memory Registry, refer to the= OpenVMS Alpha Guide to 64-Bit Addressing and VLM Features. Format" RESERVED_MEMORY FREE gs_name  3 Parameter gs_nameB Name of the memory-resident global section associated with this, reserved memory. You must specify a name. 3 Qualifiers /GLOBAL_SECTION /GLOBAL_SECTION (default) /NOGLOBAL_SECTION? /NOGLOBAL_SECTION indicates that the memory qualifier is for? a privileged application instead of a group or system globalC section. (/GLOBAL_SECTION indicates that the memory qualifier isC for a group or system global section.) You cannot use /NOGLOBAL_@ SECTION with the qualifiers /GROUP, /SYSGBL, or /PAGE_TABLES.= AUTOGEN processes the Reserved Memory Registry File in its? GETDATA phase. The size of all entries is taken into accountB when calculating system parameters that depend on the available amount of physical memory.= The reservation size is also used to calculate the initial? size of the global page table unless the entry was specified as /NOGLOBAL_SECTION. /GROUP /GROUP=n@ You must specify /GROUP if the memory-resident global sectionB is a group global section. Do not specify /GROUP if the memory-B resident global section is a system global section. The value nA is the UIC group number (in octal) associated with the memory- resident being freed.= You cannot use the /GROUP qualifier with either /SYSGBL or /NOGLOBAL_SECTION qualifiers. /SYSGBL? Indicates that a reservation is for a system global, memory- resident section.B You cannot combine this qualifier with the /GROUP or /NOGLOBAL_> SECTION qualifier. This qualifier is the default unless you' specify /GROUP or /NOGLOBAL_SECTION. 3 Example& SYSMAN> RESERVED_MEMORY FREE DFW$GS_2< %SMI-S-RMRFREPAG, pages successfully freed from reservation SYSMAN> RESERVED_MEMORY SHOW3 %SYSMAN-I-OUTPUT, command execution on node PIPERIJ Name Pages In Use Group PTs Alloced ZeroedF DFW$GS_3 384  0 SYSGBL No No NoF DFW$GS_1 128 0 00000100 No No NoF DFW$GS_3 1 0 SYSGBL Yes No No@ In this example, the first command frees reserved memory inA DFW$GS_2. The second command displays reserved memory in theD running system for DFW$GS_3 and DFW$GS_1, but not for DFW$GS_2," which has no reserved memory. 2 MODIFYB On Alpha systems, allows you to modify an existing entry in the& Reserved Memory Registry data file. Format$ RESERVED_MEMORY MODIFY gs_name 3 Parameter gs_nameA Name of the memory-resident global section associated with the0 entry being removed. You must specify a name. 3 Qualifiers /ALLOCATE /ALLOCATE /NOALLOCATE (default)D Allocates contiguous, aligned pages during the next reboot of theA system as specified on the command line. (The default is takenC from the existing Res erved Memory Registry entry.) The allocated@ memory is deducted from the system's fluid pagecount, and theD creation of the memory-resident global section results in the useA of the allocate option. The physical alignment of the pages isC based on the maximum granularity hint factor that can be used to> map the pages depending on the size of the reserved memory.C Possible granularity hint factors are 512 pages (or 4 MB) and 64C pages (or 512 KB). Therefore, assuming an 8-KB system page size,4 reserved memory is physically aligned as follows:9 o size >= 4 MB: physically aligned on a 4-MB boundary: o size < 4 MB: physically aligned on a 512-KB boundary; /NOALLOCATE implies /NOZERO. (/ZERO is incompatible with> /NOALLOCATE.) If you specify /NOALLOCATE, or do not specifyB /ALLOCATE, the reserved memory is not allocated during the nextB reboot of the system. The reserved memory is deducted only fromA the system's fluid page count, and the creation of the memory-B resident global section results in the use of the fault option. /GLOBAL_SECTION /GLOBAL_SECTION (default) /NOGLOBAL_SECTION? /NOGLOBAL_SECTION indicates that the memory qualifier is for? a privileged application instead of a group or system globalC section. (/GLOBAL_SECTION indicates that the memory qualifier isC for a group or system global section.) You cannot use /NOGLOBAL_@ SECTION with the qualifiers /GROUP, /SYSGBL, or /PAGE_TABLES.= AUTOGEN processes the Reserved Memory Registry File in its? GETDATA phase. The size of all entries is taken into accountB when calculating system parameters that depend on the available amount of physical memory.= The reservation size is also used to calculate the initial? size of the global page table unless the entry was specified as /NOGLOBAL_SECTION. /GROUP /GROUP=n= Establishes that the reserved memory is for a group globalD section. The value n specifies the UIC group number (in octal) ofD the process that creates the group global section. Only processesB within the creator's UIC group number are allowed access to theD global section. For example, if a process with the UIC of [6,100]C is the creator of the group global section, the group number for the /GROUP qualifier is 6.= You cannot use the /GROUP qualifier with either /SYSGBL or /NOGLOBAL_SECTION qualifiers. /PAGE_TABLES /PAG E_TABLES (default) /NOPAGE_TABLES> Reserves additional memory for shared page tables system as@ specified on the command line. (The default is taken from the= existing Memory Registry.) When the memory-resident globalD section is created, shared page tables are created for the global> section. If you do not specify /ALLOCATE (or if you specify@ /NOALLOCATE), the additional reserved memory is deducted only@ from the system's fluid page count. If you specify /ALLOCATE,?  additional contiguous, during the next reboot of the system,A aligned pages are allocated for the shared page table, and theA additional reserved memory is deducted from the system's fluid page count.A If you do not specify /PAGE_TABLES, or if you specify /NOPAGE_D TABLES, additional memory is not reserved for shared page tables.B When the memory-resident global section is created, shared page1 tables are not created for the global section.= You cannot specify /PAGE_ TABLES if the reservation has the attribute /NOGLOBAL_SECTION. /SIZE/ /SIZE=[size of reserved memory, unit: MB]< Specifies the number of megabytes to be deducted from theD system's fluid page count for this memory-resident global sectionD when the VMS$RESERVED_MEMORY.DATA data file is read during system@ initialization. The default value for /SIZE is taken from the% existing Reserved Memory Registry. /SYSGBL= Indicates that a reservation is for a s ystem global memory resident section.B You cannot combine this qualifier with the /GROUP or /NOGLOBAL_> SECTION qualifier. This qualifier is the default unless you' specify /GROUP or /NOGLOBAL_SECTION. /ZERO /ZERO /NOZERO (default)? /ZERO implies /ALLOCATE. If you specify /ZERO, pre-allocated> pages are zeroed during system initialization. Zeroed pagesA are required for memory-resident global sections; however, theC pages do not need to be zer oed during system initialization. The@ default value is taken from existing Reserved Memory Registry entry.A /NOALLOCATE implies /NOZERO because /ZERO is incompatible with> /NOALLOCATE. If you do not specify /ZERO, or if you specify< /NOZERO, pre-allocated pages are not zeroed during systemB initialization. Instead, these pages are zeroed when the global section is created. 3 DescriptionB The Reserved Memory Registry entry to be modified is identified- by the combination of the following items: gs_name /[NO]GLOBAL_SECTION /GROUP=n /SYSGBLC The values of these qualifiers are the same as for the RESERVED_ MEMORY ADD command. 3 Example SYSMAN> RESERVED_MEMORY MODIFY+ X234567890123456789012345678901/SIZ=2/ZERO+ $ TYPE SYS$SYSTEM:VMS$RESERVED_MEMORY.DATA! ! VMS$RESERVED_MEMORY.DATA ! Do NOT edit this file4 ! Modify with SYSMAN RESERVED_MEMORY commands@ ! A = /ALLOCA TE, Z = /ZERO, P = /PAGE_TABLES, VERSION = 1K ! SIZE (MB) RESERVATION NAME GROUP A Z PK 1 X23456789012345678901234567890 1 0 0 1K 2 X234567890123456789012345678901 SYSGBL 1 1 1K 1 X2345678901234567890123456789012 NOGBL 0 0 0 SYSMAN> EXIT $B The command in this example modifies an entry to reserve 2 MBA of memory and to allocate and zero this memory at b oot time. 2 REMOVE= On Alpha systems, removes a reserved memory entry from theB Reserved Memory Registry data file. The command does not affectC memory within the memory allocation for running systems. You canB also use RESERVED_MEMORY REMOVE qualifiers to remove a block of@ contiguous page frame numbers (PFNs) from the Reserved Memory Registry data file.C For information about the Reserved Memory Registry, refer to the= OpenVMS Alpha Guide to 64-Bit Addressing and VLM Features. Format$ RESERVED_MEMORY REMOVE gs_name 3 Parameter gs_nameA Name of the memory-resident global section associated with the0 entry being removed. You must specify a name.C If page tables are reserved for the named memory-resident global; section, the additional reserved memory is also removed. 3 Qualifiers /GLOBAL_SECTION /GLOBAL_SECTION (default) /NOGLOBAL_SECTION? /NOGLOBAL_SECTION indicates t hat the memory qualifier is for? a privileged application instead of a group or system globalC section. (/GLOBAL_SECTION indicates that the memory qualifier isC for a group or system global section.) You cannot use /NOGLOBAL_@ SECTION with the qualifiers /GROUP, /SYSGBL, or /PAGE_TABLES.B AUTOGEN processes the Reserved Memory Registry data file in itsD GETDATA phase. The size of all entries is taken into account whenD calculating system parameters that depend on the available amount of physical memory.= The reservation size is also used to calculate the initial? size of the global page table unless the entry was specified as /NOGLOBAL_SECTION. /GROUP /GROUP=n@ You must specify /GROUP if the memory-resident global sectionB is a group global section. Do not specify /GROUP if the memory-B resident global section is a system global section. The value nA is the UIC group number (in octal) associated with the memory-< resident section being removed. You cannot use the /GROUPA qualifier with either /SYSGBL or /NOGLOBAL_SECTION parameters. /SYSGBL= Indicates that a reservation is for a system global memory resident section.B You cannot combine this qualifier with the /GROUP or /NOGLOBAL_> SECTION qualifier. This qualifier is the default unless you' specify /GROUP or /NOGLOBAL_SECTION. 3 Example+ SYSMAN> RESERVED_MEMORY ADD DFW$GS1/SIZE=1' SYSMAN> RESERVED_MEMORY REMOVE DFW$GS1? The first command in this example adds DFW$GS1; the second command removes it. 2 SHOWD On Alpha systems, displays the memory reservations on the runningB system. The display includes how much of the reserved memory isA currently in use by the named global section. It also includesD how much memory is reserved and currently in use for page tables,A if any, and the blocks of contiguous page frame numbers (PFNs) reserved.C For information about Reserved Memory Registry, refer to OpenVMS5 Alpha Guide to 64-Bit Addressing and VLM Features. Format" RESERVED_MEMORY SHOW gs_name 3 Parameter gs_nameA Name of the memory-resident global section associated with theA entry being displayed within the running system. If you do notA specify gs_system, the system displays the reserved memory for" all registered global sections. 3 Qualifiers /GLOBAL_SECTION /GLOBAL_SECTION (default)  /NOGLOBAL_SECTION? /NOGLOBAL_SECTION indicates that the memory qualifier is for? a privileged application instead of a group or system globalC section. (/GLOBAL_SECTION indicates that the memory qualifier isC for a group or system global section.) You cannot use /NOGLOBAL_@ SECTION with the qualifiers /GROUP, /SYSGBL, or /PAGE_TABLES.B AUTOGEN processes the Reserved Memory Registry data file in itsD GETDATA phase. The size of all entries is taken into account whenD  calculating system parameters that depend on the available amount of physical memory.= The reservation size is also used to calculate the initial? size of the global page table unless the entry was specified as /NOGLOBAL_SECTION. /GROUP /GROUP=n@ You must specify /GROUP if the memory-resident global sectionB is a group global section. Do not specify /GROUP if the memory-@ resident global section is a system global section. The value; n is the UIC group number (in octal) associated with theB memory-resident section being displayed. You can use the /GROUPC qualifier only if you specify gs_name. You cannot use the /GROUPA qualifier with either /SYSGBL or /NOGLOBAL_SECTION parameters. /SYSGBL= Indicates that a reservation is for a system global memory resident section.B You cannot combine this qualifier with the /GROUP or /NOGLOBAL_> SECTION qualifier. This qualifier is the default unless you' specify /GROUP or /NOGLOBAL_SECTION. 3 Example SYSMAN> RESERVED_MEMORY SHOW2 %SYSMAN-I-OUTPUT, command execution on node PIPERD Name Pages In Use Group PTs Alloced Zeroed@ DFW$GS_3 384 0 SYSGBL No No No@ DFW$GS_2 256 0 SYSGBL No Yes Yes@ DFW$GS_1 128 0 00000100 No No No@ DFW$GS_3 1 0 SYSGBL Yes No No@ DFW$GS_2 1 0 SYSGBL Yes Yes NoD The command in this example displays the memory reservations on a running system. wwl1 SETB There are several SET subcommands. Select the one you want from the choices below. 2 ENVIRONMENTC Defines the nodes or cluster to which subsequent commands apply.? Requires OPER or SETPRV privilege on all nodes in the target environment. Format SET ENVIRONMENT 3 Qualifiers /CLUSTER? Specifies that all subsequent commands apply to all nodes inC the cluster. By default, the management environment is the localC cluster. Specify a nonlocal cluster by naming one cluster member with the /NODE qualifier. /NODE /NODE=(node1,node2,...)A Specifies that SYSMAN execute subsequent commands on the given> DECnet nodes. If accompanied by the /CLUSTER qualifier, theA environment becomes the cluster where the given DECnet node is@ a member. A node name can be a system name, cluster alias, orD logical name. However, before you can use logical names to defineB the command environment, you must set up the logical name tableD SYSMAN$NODE_TABLE. For more information about defining the SYSMAND logical name table, refer to the OpenVMS System Manager's Manual. /USERNAME /USERNAME=usernameB Specifies that this user name should be used for access control? purposes on another node. You can use this qualifier only inA c onjunction with the /CLUSTER or /NODE qualifiers. SYSMAN usesB the current user name if none is supplied. SYSMAN prompts for a1 password whenever you specify a new user name.& NOTE> The account specified must have only a primary password.: Accounts with secondary passwords are not supported. 3 DescriptionB The SET ENVIRONMENT command defines the target nodes or cluster? for subsequent commands. When invoked, the system management B environment is the local node where you are running SYSMAN. YouD can change the environment to any other nodes in the cluster, theD entire cluster, or any nodes or cluster available through DECnet.= Designate an OpenVMS Cluster environment with the /CLUSTERB qualifier. When specifying a nonlocal cluster, also include the+ /NODE qualifier to identify the cluster.B If your environment consists of VAX and Alpha nodes, see the DOA command for information about creating logi cals to manage each platform as an environment.@ You can display the current environment with the command SHOWA ENVIRONMENT. To adjust privileges and defaults for the current, environment, use the SET PROFILE command.@ An environment exists until you exit from SYSMAN or establish< another command context with the SET ENVIRONMENT command. 3 Examples$ 1.SYSMAN> SET ENVIRONMENT/CLUSTER0 %SYSMAN-I-ENV, Current command environment:) Clusterwide on lo!cal cluster> Username ALEXIS will be used on nonlocal nodes> This command defines the command environment as the local2 cluster. SYSMAN confirms the new environment.0 2.SYSMAN> SET ENVIRONMENT/NODE=NODE21/CLUSTER Remote Password:0 %SYSMAN-I-ENV, Current command environment:. Clusterwide on remote node NODE21> Username ALEXIS will be used on nonlocal nodes= This command establishes a management environment on theD " cluster where NODE21 is a member. SYSMAN prompts for a password* because it is a nonlocal environment.8 3.SYSMAN> SET ENVIRONMENT/NODE=(NODE21,NODE22,NODE23)0 %SYSMAN-I-ENV, Current command environment:3 Individual nodes: NODE21,NODE22,NODE23= Username ALEXIS will be used on nonlocal nodes@ This command defines the management environment to be three individual nodes.6 4.$ CREATE/NAME_TABLE/PARENT=LNM$SYSTEM_DIRECTORY - _$ SYSMAN$NOD #E_TABLE? $ DEFINE LAVCS SYS1,SYS2,SYS3,SYS4/TABLE=SYSMAN$NODE_TABLE $ RUN SYS$SYSTEM:SYSMAN) SYSMAN> SET ENVIRONMENT/NODE=(LAVCS)0 %SYSMAN-I-ENV, Current command environment:2 Individual nodes: SYS1,SYS2,SYS3,SYS4= Username ALEXIS will be used on nonlocal nodes? The commands in this example set up the logical name tableB SYSMAN$NODE_TABLE, define a logical name (LAVCS), and use the4 logical name to define the command environment.$ 2 PROFILE? Temporarily modifies a user's current privileges and default device and directory. Format SET PROFILE 3 Qualifiers /DEFAULT! /DEFAULT=device:[directory]@ Specifies the default disk device and directory name that the> system should use in this environment to locate and catalog files. /PRIVILEGES" /PRIVILEGES=(priv1,priv2...)A Specifies the privileges to add to the current privileges. Any* enhanced pr%ivileges must be authorized. /VERIFY /VERIFY /NOVERIFY (default)B Specifies whether you want DCL verification (both procedure and! image) for future DO commands. 3 Description: The SET PROFILE command modifies process attributes for< the current management environment. After considering the? privilege requirements of commands that you intend to use in? an environment, you can add or delete current privileges, ifA they are authorized. You can &also set a new default device and? directory, as well as use the SET PROFILE/[NO]VERIFY commandB to control DCL command verification in SYSMAN. Other attributesB of your process remain constant. The profile is in effect untilA you change it, reset the environment, or exit from SYSMAN. TheD OpenVMS System Manager's Manual discusses profile changes in more detail. 3 Examples/ 1.SYSMAN> SET PROFILE/DEFAULT=WORK1:[ALEXIS]A This command changes the default device' and directory in the6 user account to directory ALEXIS on device WORK1.: 2.SYSMAN> SET PROFILE/PRIVILEGES=(SYSPRV,CMKRNL)/VERIFY= This command makes the authorized privileges, SYSPRV and= CMKRNL, part of the current privileges, and turns on DCL< verification. The privileges remain in effect until the@ environment changes, you enter another SET PROFILE command, or you exit. 2 TIMEOUT< Establishes the amount of time SYSMAN waits for a node toC res(pond. Once the time limit expires, SYSMAN proceeds to execute3 the command on the next node in the environment. Format SET TIMEOUT time 3 Parameter time@ Specifies a delta time value, which has the following format: hh:mm:ss[.cc.]= This is the amount of time that SYSMAN waits for a node toB respond. SYSMAN waits indefinitely-by default it has no timeoutB period. Refer to the OpenVMS User's Manual for a description of delta time values.) 3 Example SYSMAN> SET TIMEOUT 00:00:30- %SYSMAN-I-TIMEVAL, timeout value is 00:00:30 SYSMAN> CONFIGURATION SHOW TIME2 System time on node NODE21: 19-JUN-2000 14:22:332 %SYSMAN-I-NODERR, error returned from node NODE22/ %SMI-E-TIMEOUT, remote operation has timed out2 System time on node NODE23: 19-JUN-2000 14:23:15= This command establishes a timeout period of 30 seconds.= Because NODE22 did not respond within 30 seconds, SYSMANB displays an error message and p*roceeds to execute the command) on the next node in the environment. www l1 SHOWC There are several SHOW subcommands. Select the one you want from the choices below. 2 ENVIRONMENTA Displays the target nodes or cluster where SYSMAN is executing commands. Format SHOW ENVIRONMENT 3 Description? The SHOW ENVIRONMENT command displays the current managementC environment. It can be the local cluster, local or remote nod+es,@ or a nonlocal cluster. SYSMAN indicates if the environment is? limited to individual nodes or if it is clusterwide. It also shows the current user name.= The environment exists until you exit from SYSMAN or enter# another SET ENVIRONMENT command. 3 Examples 1.SYSMAN> SHOW ENVIRONMENT0 %SYSMAN-I-ENV, Current command environment:) Clusterwide on local cluster= Username ALEXIS will be used on nonlocal nodes< This comman,d shows the current environment is the localA cluster. User name ALEXIS will be used on other nodes in the cluster. 2.SYSMAN> SHOW ENVIRONMENT0 %SYSMAN-I-ENV, Current command environment:1 Clusterwide on remote cluster NODE21= Username ALEXIS will be used on nonlocal nodesB This command shows that the command environment is a nonlocal& cluster where NODE21 is a member. 3.SYSMAN> SHOW ENVIRONMENT0 %SYSMAN-I-ENV, Current comm-and environment:, Individual nodes: NODE22,NODE236 At least one node is not in local cluster= Username ALEXIS will be used on nonlocal nodesD This command shows that the command environment consists of two nodes. 2 KEY@ Displays key definitions created with the DEFINE/KEY command. Format SHOW KEY [key-name] 3 Parameter key-name: Specifies the name of the key whose definition you want@ displayed. .See the DEFINE/KEY command for a list of valid key names. 3 Qualifiers /ALL= Displays all the key definitions in the specified state or2 states. Specifying a key name is not necessary. /BRIEFD Displays only the key definition. By default, the system displaysC all the qualifiers associated with the key definition, including< any specified state, unless you use the /BRIEF qualifier. /DIRECTORYB Displays the names of all the states for which yo/u have defined= keys. If you have not defined keys, the SHOW KEY/DIRECTORY= command displays the DEFAULT and GOLD states (which is the default SYSMAN keypad). /STATE /STATE=(state, state...)< Specifies the name of a state for which the specified key? definitions are to be displayed. If you select more than one@ state name, separate them with commas and enclose the list in parentheses. 3 Description: Specifies the name of the key whose definition 0you want@ displayed. See the DEFINE/KEY command for a list of valid key names. 3 Example SYSMAN> SHOW KEY/ALL DEFAULT keypad definitions:" KP0 = "SHOW ENVIRONMENT" (echo) KP1 = "SHOW PROFILE" (echo) SYSMAN>? This command displays all the key definitions currently in effect. 2 PROFILE? Displays the privileges and the default device and directory) being used in the current environment. Format SHOW PROFILE 3 Qualifier1s /DEFAULT? Displays the default disk device and directory name that the? system uses in this environment to locate and catalog files. /PRIVILEGES9 Displays only the privileges in effect for the current environment. 3 Description; The SHOW PROFILE command displays the privileges and theA default device and directory that is being used in the currentD environment. You can modify these attributes with the SET PROFILE command.A These value2s remain in effect until you change environments or% enter another SET PROFILE command. 3 Example SYSMAN> SHOW PROFILE7 %SYSMAN-I-DEFDIR, Default directory on node NODE21 --WORK1:[BERGERON]8 %SYSMAN-I-DEFPRIV, Process privileges on node NODE21 -- TMPMGX OPER NETMBX SYSPRVC This command shows the default device and directory as well as current privileges. 2 TIMEOUTB Displays the amount of time SYSMAN waits for 3a node to respond.* By default, there is no timeout period. Format SHOW TIMEOUT 3 Example SYSMAN> SHOW TIMEOUT0 %SYSMAN-I-TIMEVAL, timeout value is 00:00:04.00@ This command displays the current timeout value, which is 4 seconds. ww]l 1 SHUTDOWN 2 NODE6 Shuts down one or more nodes in an OpenVMS Cluster.@ The SHUTDOWN NODE command invokes SYS$SYSTEM:SHUTDOWN to shutB down one node or multiple nodes, as you s4pecify, in the currentD management environment. You can enter the shutdown command in oneC command line, instead of executing the SHUTDOWN.COM procedure on each node individually.@ Requires SETPRV privilege or all of the following privileges:@ CMKRNL, EXQUOTA, LOG_IO, OPER, SYSNAM, SYSPRV, TMPMBX, WORLD. Format SHUTDOWN NODE 3 Qualifiers /AUTOMATIC_REBOOT /AUTOMATIC_REBOOT# /NOAUTOMATIC_REBOOT (default)B Reboots the system automa5tically when the shutdown is complete. /CLUSTER_SHUTDOWN /CLUSTER_SHUTDOWN# /NOCLUSTER_SHUTDOWN (default)! Shuts down the entire cluster.C When you use the /CLUSTER_SHUTDOWN qualifier, each node suspendsC activity just short of shutting down completely, until all otherC nodes in the cluster have reached the same point in the shutdown procedure.A You must specify this option on every cluster node. If any oneD node is not shut down completely, t6he clusterwide shutdown cannot occur.@ You should use the SET ENVIRONMENT/CLUSTER command before youD issue a SHUTDOWN NODE/CLUSTER_SHUTDOWN command to ensure that all* nodes in the cluster are shutting down. /DISABLE_AUTOSTARTA Specifies the number of minutes before shutdown when autostart= queues running on the node are marked stop pending and are' subject to failover to another node.A Using this qualifier gives you control over when the autostartD failo7ver process begins. By default, the value equals that of the" /MINUTES_TO_SHUTDOWN qualifier.7 Determine the appropriate number of minutes for your: configuration by weighing a smoother transition againstB completing a maximum number of jobs before shutdown. The largerB the value, the smoother the transition will be. The smaller the1 value, the more jobs will execute on the node. /INVOKE_SYSHUTDOWN" /INVOKE_SYSHUTDOWN (default) /NOINVOKE_SYSHUTDOWN. Inv 8okes a site-specific shutdown procedure. /MINUTES_TO_SHUTDOWN! /MINUTES_TO_SHUTDOWN=number= The number of minutes until shutdown occurs. If the system@ logical name SHUTDOWN$MINIMUM_MINUTES is defined, its integer? value is the minimum value that you can enter. Therefore, ifB the logical name is defined as 10, you must specify at least 10A minutes to final shutdown or an error message displays. If the? logical name is not defined, and you do not enter a value, 09 minutes is the default. /POWER_OFF> Specifies that the system is to power off after shutdown is complete. /REASON /REASON=text* The reason for the shutdown (one line). /REBOOT_CHECK /REBOOT_CHECK /NOREBOOT_CHECK (default)B Checks for basic operating system files and notifies you if anyB are missing. Be sure to replace missing files before rebooting. /REBOOT_TIME /REBOOT_TIME=time8 The time when you expec:t to reboot the system such as< IMMEDIATELY, IN 10 MINUTES, 2 P.M., or 14:00:00. Shutdown5 displays this time in a shutdown message to users. /REMOVE_NODE /REMOVE_NODE /NOREMOVE_NODE (default)D Removes a node from the active cluster quorum. Use this qualifierB when you do not expect the shut-down node to rejoin the cluster for an extended period.@ When you use the /REMOVE_NODE qualifier, active quorum in theD remainder of the cluster is adjusted downwa;rd to reflect the factC that the removed node's votes no longer contribute to the quorumD value. The shutdown procedure readjusts the quorum by issuing the& SET CLUSTER/EXPECTED_VOTES command.8 You can reset options by using the following command:7 SYSMAN> STARTUP SET OPTIONS/NOVERIFY/NOCHECKPOINTINGB For more information about cluster management, refer to OpenVMS Cluster Systems. /SAVE_FEEDBACK /SAVE_FEEDBACK /NOSAVE_FEEDBACK (default)D Recor<ds feedback data collected from the system since it was last@ booted and creates a new version of the AUTOGEN feedback data9 file, which you can use the next time you run AUTOGEN. /SPIN_DOWN_DISKS /SPIN_DOWN_DISKS" /NOSPIN_DOWN_DISKS (default): Spins down disks. You cannot spin down the system disk. 3 Examples$ 1.SYSMAN> SET ENVIRONMENT/CLUSTERF SYSMAN> SHUTDOWN NODE/MINUTES_TO_SHUTDOWN=15/REBOOT_TIME="later"-G _SYSMAN> /REASON="SOFTWARE UPGRA =DE"/REBOOT_CHECK/CLUSTER_SHUTDOWND The first command in this example ensures that all nodes in theC cluster will shut down. The second command requests a shutdown> for the entire cluster and a reboot check for any missingA operating system files. The following messages are displayed to users on the cluster:C SHUTDOWN message on NODE21, from user SYSTEM at NODE21$0PA0:@ 12:00:00:20. NODE21 will shut down in 15 minutes; back up5 later. Please log o >ff NODE21. SOFTWARE UPGRADEC SHUTDOWN message on NODE22, from user SYSTEM at NODE22$0PA0:@ 12:00:00:22. NODE22 will shut down in 15 minutes; back up5 later. Please log off NODE22. SOFTWARE UPGRADEC SHUTDOWN message on NODE23, from user SYSTEM at NODE23$0PA0:@ 12:00:00:24. NODE23 will shut down in 15 minutes; back up5 later. Please log off NODE23. SOFTWARE UPGRADE# 2.SYSMAN> SET ENVIRONMENT/NODE=0 Password:& SYSMAN> SHUTDOWN NODE/MINUT ?ES=1206 %SYSMAN-I-SHUTDOWN, SHUTDOWN request sent to node SYSMAN> EXIT $ LOGOUTB This example shuts down the local node in 2 hours. As long asC you set the environment to the local node, a subprocess of theC SMISERVER system detached process runs shutdown, and remainingD logged into the system during the shutdown is not necessary. IfC you do not set the environment to the local node, the shutdownA runs via a subprocess of the current process, requi@ring that4 you remain logged in during the shutdown cycle. wwWxl1 SPAWNB Creates a subprocess of the current process. The context of theA subprocess is copied from the current process. You can use theA SPAWN command to leave SYSMAN temporarily, perform other tasksC (such as displaying a directory listing or printing a file), and return to SYSMAN.B Note that SPAWN performs actions on the local node only. If you@ want to execute DCL commands orA command procedures throughout( your environment, use the DO command.C Requires TMPMBX or PRMMBX user privilege. The SPAWN command doesD not manage terminal characteristics. You cannot use the SPAWN and> ATTACH commands if your terminal has an associated mailbox. Format SPAWN [command-string] 2 Parameter command-string? Specifies a command string of fewer than 132 characters that> you want executed in the context of the created subprocess.B WheBn the command completes execution, the subprocess terminatesA and control returns to the parent process. If you specify both@ a command string and the /INPUT qualifier, the command stringC executes before additional commands are obtained from the /INPUT qualifier. 2 Qualifiers /INPUT /INPUT=filespec= Specifies an input file containing one or more DCL commandC strings that you want executed by the spawned subprocess. If youA specify a command strinCg along with an input file, the commandD string gets processed before the commands in the input file. When5 processing is complete, the subprocess terminates. /LOGICAL_NAMES /LOGICAL_NAMES (default) /NOLOGICAL_NAMESD Specifies that the logical names of the parent process are copiedD to the subprocess. When you do not want the subprocess to use theB logical names of the parent process, enter the /NOLOGICAL_NAMES qualifier. /OUTPUT /OUTPUT=DfilespecC Identifies the output file to which the results of the operation@ are written. Specify an output other than SYS$OUTPUT wheneverA you use the /NOWAIT qualifier. This prevents output from beingC displayed while you are specifying new commands. If you omit theC /OUTPUT qualifier, output gets written to the current SYS$OUTPUT device. /PROCESS /PROCESS=subprocess-nameD Specifies the name of the subprocess that you want to create. The7 default subprEocess name is in the format USERNAME_n. /SYMBOLS /SYMBOLS (default) /NOSYMBOLSD Determines whether the system passes DCL global and local symbols to the subprocess. /WAIT /WAIT (default) /NOWAITC Controls whether the system waits until the subprocess completes> before you can specify more commands. The /NOWAIT qualifier: enables you to specify new commands while the specified? subprocess is running. If you specify the /NOWAIT qFualifier,C use the /OUTPUT qualifier to direct the output to a file insteadD of displaying it on the screen. Doing this prevents your terminal; from being used by more than one process simultaneously. 2 Examples* 1.SYSMAN> SPAWN DIR SYS$MANAGER:SITE*.*" Directory CLU$COMMON:[SYSMGR] SITE$STARTUP.COM;5 Total of 1 file. SYSMAN>C This command enables you to enter the DIRECTORY command in DCL@ to see if a site-specific startup file isG in the directory.A After the DIRECTORY command executes, control returns to the parent process. 2.SYSMAN> SPAWN $ EDIT SITE$STARTUP.COM . . . $ LOGOUT; Process SYSTEM_1 logged out at 28-JUN-2000 10:05:17.24 SYSMAN>B This example shows how you can use the SPAWN command to leave> SYSMAN and edit a file. The LOGOUT command returns you to SYSMAN., 3.SYSMAN> SPAWN /NOLOGICAL_NAMES SET HOST _Node: NODE21 H . . . $ LOGOUT3 %REM-S-END, control returned to node _NODE22:: SPAWN> C This example shows how you can use the SPAWN command to createA a subprocess in which you can use the SET HOST command. When< you want to leave NODE21, enter the LOGOUT command. TheA /NOLOGICAL_NAMES qualifier prevents the logical names of the8 parent process from being copied to the subprocess. wwl 1 STARTUPA ThereI are several STARTUP subcommands. Select the one you want from the choices below. 2 ADD, Adds a component to the startup database.C Requires read (R) and write (W) access to the startup database. Format STARTUP ADD FILE filespec 3 Parameters FILE< Adds a component to the startup database. SYSMAN modifies& STARTUP$STARTUP_LAYERED by default. filespec< Specifies which file to add to the startup database. EachB component of thJe startup database must have a file type of .COM% or .EXE and reside in SYS$STARTUP. 3 Qualifiers /CONFIRM /CONFIRM /NOCONFIRM (default)B Controls whether SYSMAN displays the file specification of eachD file before adding it to the startup database and requests you toB confirm the addition. If you specify /CONFIRM, you must respond> to the prompt with a Y (Yes) or a T (True) and press Return@ before the file is added. If you enter anything else, sucKh as, N or No, the requested file is not added. /LOG /LOG /NOLOG (default)= Controls whether the STARTUP ADD command displays the file6 specification of each file after it has been added. /MODE /MODE=modeD Specifies the mode of execution for the file. Valid modes include DIRECT, SPAWN, BATCH, or ANY. /NODE# /NODE=(node1,node2,...,noden)> Names the nodes within the cluster that run the file during? startup. By defaultL, a startup file executes on all nodes in the cluster. /PARAMETER. /PARAMETER=(P1:arg1,P2:arg2,...,P8:arg8)= Specifies the parameters that are to be passed to the fileB during startup. Parameters that are omitted receive the default< parameters defined by the system parameter STARTUP_Pn. IfA STARTUP_Pn is blank, "FULL" is used as parameter 1 (P1) and isD passed by STARTUP.COM to each startup component file. If you wantC a blank P1 parameter given to a specifiMc component file, use the command:8 SYSMAN> STARTUP MODIFY FILE component.com/PARAM=P1:"" /PHASE /PHASE=phase-nameC Indicates the phase within system startup when the file is to beC executed. Valid phases include LPBEGIN, LPMAIN, LPBETA, and END. LPMAIN is the default. 3 DescriptionD The STARTUP ADD command adds a component to the startup database.D Startup components are the command procedures or executable filesD that perform actual startupN work. Files from the startup databaseB are used to start the operating system, site-specific programs,A and layered products. STARTUP$STARTUP_VMS and STARTUP$STARTUP_7 LAYERED list the components of the startup database.> Because an OpenVMS Cluster typically shares one copy of the= startup database, the SYSMAN environment can be defined as4 clustered or as a single node within the cluster. 3 Example6 SYSMAN> STARTUP ADD FILE /MODE=DIRECT /PHASE=LPMAIN -# _SYSMAN> DEOCSET$ENVMGR_STARTUP.COMC This command adds a record to the startup database that starts- the DECSET environment manager software. 2 DISABLE: Prevents a file in the startup database from executing.C Requires read (R) and write (W) access to the startup database. Format# STARTUP DISABLE FILE filespec 3 Parameters FILE@ Disables a component of the startup database. SYSMAN modifies& STARTUP$STARTUP_LAYERED by default. filespecPA Specifies the name of a component in the startup database. The? startup file must reside in SYS$STARTUP and have a file type= of .COM or .EXE. The asterisk (*) and percent (%) wildcard characters are permitted. 3 Qualifiers /CONFIRM /CONFIRM /NOCONFIRM (default)A Controls whether the STARTUP DISABLE command displays the file@ specification of each file before disabling it in the startupB database and requests you to confirm that the file Qbe disabled.C If you specify /CONFIRM, you must respond to the prompt with a YD (Yes) or a T (True) and press Return before the file is disabled.B If you enter anything else, such as N or No, the requested file is not disabled. /LOG /LOG /NOLOG (default)A Controls whether the STARTUP DISABLE command displays the file9 specification of each file after it has been disabled. /NODE# /NODE=(node1,node2,...,noden)? Identifies nodes withinR the cluster that do not run the fileB during startup. By default, the startup file is disabled on all nodes in the cluster. /PHASE /PHASE=phase-nameD Indicates the phase of system startup in which the specified fileC normally executes. Valid phases include LPBEGIN, LPMAIN, LPBETA," and END. LPMAIN is the default. 3 Description= The STARTUP DISABLE command prevents a file in the startup= database from executing. The command edits a record in the4 S startup database, temporarily disabling the file. 3 ExampleD SYSMAN> STARTUP DISABLE FILE /NODE=NODE21 DECSET$ENVMGR_STARTUP.COMB This command modifies the startup database so that the DECset9 environment manager will not be installed on NODE21. 2 ENABLE@ Enables a previously disabled file in the startup database to! execute during system startup.C Requires read (R) and write (W) access to the startup database. Format" STARTUP ENABLE FILE Tfilespec 3 Parameters FILE? Enables a component of the startup database. SYSMAN modifies& STARTUP$STARTUP_LAYERED by default. filespec@ Specifies the name of the startup file that you are enabling.$ Wildcard characters are accepted. 3 Qualifiers /CONFIRM /CONFIRM /NOCONFIRM (default)@ Controls whether the STARTUP ENABLE command displays the file? specification of each file before enabling it in the startupA database anUd requests you to confirm that the file be enabled.C If you specify /CONFIRM, you must respond to the prompt with a YC (Yes) or a T (True) and press Return before the file is enabled.B If you enter anything else, such as N or No, the requested file is not enabled. /LOG /LOG /NOLOG (default)@ Controls whether the STARTUP ENABLE command displays the file8 specification of each file after it has been enabled. /NODE# /NODE=(node1,node2,...,nodVen)D Names nodes within the cluster where the file will be enabled. By5 default, the startup file is enabled on all nodes. /PHASE /PHASE=phase-nameD Indicates the phase within system startup when the specified fileB is to be enabled. Valid phases include LPBEGIN, LPMAIN, LPBETA," and END. LPMAIN is the default. 3 Description@ The STARTUP ENABLE command permits a file that was previously- disabled to execute during system startup. 3 ExampleWC SYSMAN> STARTUP ENABLE FILE /NODE=NODE22 DECSET$ENVMGR_STARTUP.COMA This command modifies the startup database. NODE22 will have9 the DECSET environment manager installed at startup. 2 MODIFYD Changes information associated with a startup file in the startup database.C Requires read (R) and write (W) access to the startup database. Format" STARTUP MODIFY FILE filespec 3 Parameters FILE= Modifies a record in the startup databaXse. SYSMAN modifies& STARTUP$STARTUP_LAYERED by default. filespecC Selects a startup file for modification. Wildcard characters are accepted. 3 Qualifiers /CONFIRM /CONFIRM /NOCONFIRM (default); Controls whether the STARTUP MODIFY command displays the? file specification of each file before modifying its startup? characteristics in the startup data file and requests you toD confirm that the file characteristics be modified. If you sYpecify? /CONFIRM, you must respond to the prompt with a Y (Yes) or a@ T (True) and press Return before the file is modified. If youB enter anything else, such as N or No, the requested file is not modified. /LOG /LOG NOLOG (default)@ Controls whether the STARTUP MODIFY command displays the fileD specification of each file after its startup characteristics have been modified. /MODE /MODE=mode@ Changes the mode of execution for a sZtartup file. Valid modes( include DIRECT, SPAWN, BATCH, or ANY. /NAME /NAME=filespec@ Changes the name of the startup file. The file must reside in SYS$STARTUP. /PARAMETER. /PARAMETER=(P1:arg1,P2:arg2,...,P8:arg8)B Changes the parameters that are to be passed to the file during; startup. Parameters that are omitted receive the default< parameters defined by the system parameter STARTUP_Pn. IfA STARTUP_Pn is blank, "FULL" is used as parameter [1 (P1) and isD passed by STARTUP.COM to each startup component file. If you wantC a blank P1 parameter given to a specific component file, use the command:8 SYSMAN> STARTUP MODIFY FILE component.com/PARAM=P1:"" /PHASE /PHASE=phase-name? Selects startup files for modification based on the phase inD which they run. Valid phases include LPBEGIN, LPMAIN, LPBETA, and END. LPMAIN is the default. 3 DescriptionB The STARTUP MODIFY command edits startu\p information associatedD with components in the startup database. For example, the command= can rename a file or change the parameters that are passed@ to a file during startup. You can select a group of files for5 modification based on the phase in which they run. 3 Example8 SYSMAN> STARTUP MODIFY FILE DECSET$ENVMGR_STARTUP.COM -, _SYSMAN> /PARAM=(P3:TRUE,P4:FALSE) /CONFIRM@ This command changes two startup parameters for the command) procedure DECSET$ENVMGR_STA]RTUP.COM. 2 REMOVE= Removes a record in the startup database, so the specified9 startup file no longer executes during system startup.C Requires read (R) and write (W) access to the startup database. Format" STARTUP REMOVE FILE filespec 3 Parameters FILEA Removes a component from the startup database. SYSMAN modifies& STARTUP$STARTUP_LAYERED by default. filespec< Specifies the name of the file to remove from the startup. d^atabase. Wildcard characters are accepted. 3 Qualifiers /CONFIRM /CONFIRM /NOCONFIRM (default)@ Controls whether the STARTUP REMOVE command displays the file? specification of each file before deleting its record in the@ startup database and requests you to confirm that the file beC deleted. If you specify /CONFIRM, you must respond to the prompt@ with a Y (Yes) or a T (True) and press Return before the file? is removed. If you enter anything else,_ such as N or No, the! requested file is not removed. /LOG /LOG /NOLOG (default)B Controls whether SYSMAN displays the file specification of each" file after it has been removed. /PHASE /PHASE=phase-nameD Indicates the phase of system startup from which the file will beB removed. Valid phases include LPBEGIN, LPMAIN, LPBETA, and END. 3 Example; SYSMAN> STARTUP REMOVE FILE DECSET$ENVMGR_STARTUP.COM /LOGA This command takes `the file DECSET$ENVMGR_STARTUP.COM out of the startup database. 2 SET 3 DATABASE, Establishes the current startup database. Format# STARTUP SET DATABASE database 4 Parameters database6 Specifies the name of the target database, which is; STARTUP$STARTUP_LAYERED by default. The second database,A STARTUP$STARTUP_VMS, is available for viewing; however, Compaq( recommends that you do not modify it. 4 Qualifiers None.a 4 Example5 SYSMAN> STARTUP SET DATABASE STARTUP$STARTUP_LAYERED %SYSMAN-I-ANEWCOMPFIL, current component file is now STARTUP$STARTUP_LAYERED SYSMAN> STARTUP SHOW FILEA %SYSMAN-I-COMPFIL, contents of component database on node LUCERN Phase Mode File- ----- ---- ---------------------------- LPBEGIN DIRECT VMS$LPBEGIN_070_STARTUP.COM, LPMAIN DIRECT FOR$LPMAIN_070_STARTUP.COM@ The commands in this example establish the layered products5 database as tbhe default, so it can be displayed. 3 OPTIONSD Displays startup status for one or more nodes in a cluster during startup.? Requires READ (R) and WRITE (W) access to the current system< parameter file on disk: SYS$SYSTEM:VAXVMSSYS.PAR (for VAX> systems) or SYS$SYSTEM:ALPHAVMSSYS.PAR (for Alpha systems). Format STARTUP SET OPTIONS 4 Qualifiers /CHECKPOINTING /CHECKPOINTING /NOCHECKPOINTINGD Displays informational messages dcescribing the time and status of. each startup phase and component procedure. /OUTPUT# /OUTPUT=FILE,CONSOLE(default)B Sends output generated by using the /VERIFY qualifier to a file> or to the system console. If you choose the FILE option, it, creates SYS$SPECIFIC:[SYSEXE]STARTUP.LOG. /VERIFY$ /VERIFY=FULL (default),PARTIAL /NOVERIFY> Displays startup procedures as they execute. This qualifierB defines the system parameter STARTUP_P2 to hadve the appropriate) value based on the options you choose:C o FULL-Displays every line of DCL executed by startup component# procedures and by STARTUP.COM< o PARTIAL-Displays every line of DCL executed by startup@ component procedures, but does not display DCL executed by STARTUP.COM' CAUTION< All STARTUP_P* parameter values modified by the SYSMAN? STARTUP OPTIONS will be overridden by the AUTOGEN commandB pr eocedure. To preserve any parameter modifications made withB SYSMAN, edit the SYS$SYSTEM:MODPARAMS.DAT file, as explained- in the OpenVMS System Manager's Manual. 4 DescriptionA The STARTUP SET OPTIONS command enables you to perform loggingB and checkpointing during startup. You can control the amount ofA information logged (full or partial) and where it is displayed> (file or console). You can also choose checkpointing, which? displays informational messages aboutf the time and status of each phase during startup.C Because SYSMAN enables you to define the target environment, youD can perform startup logging on your local node, your own cluster,A and a subset of nodes on your cluster. See the SET ENVIRONMENT command for more information. 4 ExampleB SYSMAN> STARTUP SET OPTIONS/VERIFY=FULL/OUTPUT=FILE/CHECKPOINTINGB This example requests startup logging with full verification,C output to SYS$SPECIFIC:[SYSEXE]STARTUP.LOgG, and checkpointing. 2 SHOW; Displays the name of the current startup database or itsB components as well as the startup logging options selected with# the STARTUP SET OPTIONS command. Format STARTUP SHOW DATABASE FILE OPTIONS 3 Parameters DATABASE9 Displays the name of the current startup database. The8 two startup databases are STARTUP$STARTUP_LAYERED and@ STARTUP$STARTUP_VMS. Compaq recomhmends that you do not modify$ the STARTUP$STARTUP_VMS database. FILE= Displays the contents of the current startup database. The? display includes the file name, phase, and mode of execution& for each component in the database. OPTIONSC Displays the options selected when using the STARTUP SET OPTIONS command. 3 Qualifiers /FULLB Displays full information about each component in the database.A In addition to the phase, file name, and moide of execution for= each startup component, SYSMAN displays the nodes on which@ the file executes and the parameters passed to the file. This1 qualifier is relevant with the FILE parameter. /NODE: Displays the nodes within the cluster on which the fileC executes. By default, a startup file executes on all nodes in anC environment. This qualifier is relevant with the FILE parameter. /OUTPUT /OUTPUT=filespecB Redirects command output from SYS$OUTPU jT to the file named withA the qualifier. Without a filespec, SYSMAN writes the output to' SYSMAN.LIS in the current directory. /PARAMETERS= Lists the parameters with which the startup file executes.D Parameters that are not specified receive the defaults defined byB the system parameter STARTUP_Pn. If STARTUP_Pn is blank, "FULL"C is used as parameter 1 (P1) and is passed by STARTUP.COM to eachA startup component file. If you want a blank P1 parameter givenC to a kspecific component file, see the /PARAMETER qualifier under+ STARTUP MODIFY command for instructions. /PHASE /PHASE=phase-nameA Displays components that execute in a specific phase of systemB startup. Valid phases include LPBEGIN, LPMAIN, LPBETA, and END.B LPMAIN is the default. This qualifier is relevant with the FILE parameter. 3 Example1 SYSMAN> STARTUP SET DATABASE STARTUP$STARTUP_VMS SYSMAN> STARTUP SHOW FILEA %SYSMAN-I-COMPFIL, contents of colmponent database on node LUCERN Phase Mode File6 ----- ---- --------------------------------1 BASEENVIRON DIRECT VMS$BASEENVIRON_050_LIB.COM7 BASEENVIRON CALLED VMS$BASEENVIRON_050_SMISERVER.COM1 BASEENVIRON DIRECT VMS$BASEENVIRON_050_VMS.COM . . .= The commands in this example display the contents of the startup database. wwwN0l1 SYS_LOADABLEA There are several SYS_LOADABLE subcommands. Select the one you want mfrom the choices below. 2 ADDA Adds an entry in the system images file SYS$UPDATE:VMS$SYSTEM_ IMAGES.IDX.' CAUTION> The SYS_LOADABLE ADD command is not intended for general; use. Only advanced system programmers should use this command. Format$ SYS_LOADABLE ADD product image 3 Parameter productB A 1- to 8-character product mnemonic that uniquely identifies aA loadable image. For user-writtenn images, this should typically contain the string _LOCAL_. image@ The file name of the system loadable image you want to add. AB file name is the only value you can specify for this parameter.= Do not specify a device, directory, file type, or wildcard characters. 3 Qualifiers /LOAD_STEPB Indicates the step of the booting process at which you want theC image loaded. Valid load steps are INIT (which causes the systemD initialization code to loado the image), and SYSINIT (which causes* the SYSINIT process to load the image).A If you do not specify a value for the /LOAD_STEP qualifier, it defaults to SYSINIT. /LOG /LOG /NOLOG (default); Controls whether the SYS_LOADABLE ADD command displays a/ notification after the entry has been added. /MESSAGEA Enables you to specify the text of a message that is displayed; when the appropriate condition is met (see the /SEVERITYA qualifier).p The default message is "system image load failed". /SEVERITYB Determines how the image load status will affect console outputA and booting progress. You can specify the following values for this qualifier: Value Description@ FATAL If an error occurs loading the image, display the6 error message and BUGCHECK information.; INFORMATION Display the message and continue processing.D SUCCESS Continue even if loading the image produces aqn error., Does not display the message.@ WARNING If an error occurs loading the image, display the5 error message and continue processing.@ If you do not specify a value for the /SEVERITY qualifier, it defaults to WARNING. 3 DescriptionB The SYS_LOADABLE ADD command adds an entry to the system images> file SYS$UPDATE:VMS$SYSTEM_IMAGES.IDX. You can then process? this file using the command procedure SYS$UPDATE:VMS$SYSTEM_= IMAGES.COM.r Processing the file with VMS$SYSTEM_IMAGES.COM? generates a new system images data file that the system uses when it boots.C If the file SYS$UPDATE:VMS$SYSTEM_IMAGES.IDX does not exist, the. SYS_LOADABLE ADD command creates a new one. 2 REMOVED Removes an entry in the system images file SYS$UPDATE:VMS$SYSTEM_ IMAGES.IDX.' CAUTIONA The SYS_LOADABLE REMOVE command is not intended for general; use. Only advanced system sprogrammers should use this command. Format! SYS_LOADABLE REMOVE product image 3 Parameter product@ A 1- to 8-character product mnemonic that uniquely identifiesB a loadable image. For user-written images this should typically contain the string _LOCAL_. imageC The file name of the system loadable image you want to remove. AB file name is the only value you can specify for this parameter.= Do not spectify a device, directory, file type, or wildcard characters. 3 Qualifiers /LOG /LOG /NOLOG (default)> Controls whether the SYS_LOADABLE REMOVE command displays a1 notification after the entry has been removed. 3 Description< The SYS_LOADABLE REMOVE command removes an entry from the; system images file SYS$UPDATE:VMS$SYSTEM_IMAGES.IDX. You9 can then process this file using the command procedure= SYS$UPDATE:VMS$SYSTEM_IMAGES.COM. Processuing the file with@ VMS$SYSTEM_IMAGES.COM generates a new system images data file& that the system uses when it boots.C If the file SYS$UPDATE:VMS$SYSTEM_IMAGES.IDX does not exist, the8 SYS_LOADABLE REMOVE command creates a new, empty one.ww&l1 Sys_Parameters; Help is provided for the system parameters listed below. 2 ACP_BASEPRIOD ACP_BASEPRIO sets the base priority for all ACPs. The DCL commandC SET PROCESS/PRIORITY can be used to reset the bvase 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 following table shows the bits that are defined currently: Bit Description@ 0 Set this bit to perform consistency checks on read operations. w? When this bit is set, the IO$M_DATACHECK functionB modifier is automatically set on all subsequent IO$_E READLBLK operations that read file system metadata (see7 the OpenVMS I/O User's Reference Manual).A 1 Set this bit to perform consistency checks on write operations.? When this bit is set, the IO$M_DATACHECK functionB modifier is automatically set on all subsequent IO$_A x WRITELBLK operations that read file system metadata< (see the OpenVMS I/O User's Reference Manual).B 2 Set this bit to perform read-after-write consistency checks.C This is similar to setting bit 1, except that in thisA case the file system does the checks, not the lower* level device or disk driver.C Note that read-after-write consistency checks are notD allowed on defer yred 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 directory blocks. You can select+ one of four different levels:2 By7 Select SettingC z This Bit 6 And Bit 5? To Check That... Level... to... to...; The block is a valid 0 0 0 directory block (reads only); The block is a valid 1 0 1 directory block (reads and writes); The block is a valid 2 1 0 directory block and contai{ns valid entries (reads and writes); The block is a valid 3 1 1 directory block and contains valid entries in correct alphanumeric order (reads and writes)B When you set the SYSTEM_CHECK system parameter to 1,> you enable level 3 checking of directory blocks.D Write errors result in BUGCHECK and crash your system;B| read errors exit with error status SS$_BADDIRECTORY.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 temporary index into the directoryA file, thereby reducing search time and directory header lookup operations.A ACP_DINDXCACHE is an AUTOGEN, DYNAMIC, and FEEDBACK parameter. }2 ACP_DIRCACHE> ACP_DIRCACHE sets the number of pages for caching 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 FEEDBACK parameter. 2 ACP_EXTCACHE? ACP_EXTCACHE sets the number of entries in the extent cache.B Each entry points to one contiguous area of free space on disk.@ A speci ~fication 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 free space to@ which the extent cache can point, expressed in thousandths of@ the currently available free blocks on the disk. For example,: if available free space on the disk is 20,000 blocks, a= specification of 10 limits the extent cache to 200 blocks.@ The computed, installed value is usually adequate. Users withA four or more OpenVMS Cluster node systems might want to adjust this parameter.' ACP_EXTLIMIT is a DYNAMIC parameter. 2 ACP_FIDCACHED ACP_FIDCACHE sets the number of file identification slots cached.@ A specification of 1 means no cache. Too small a value causes? excessive XQP I/O operations, while too large a value causes> excessive physical memory to be consumed by the FID caches.4 ACP_FIDCACHE 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 excessive physical memory to be& consumed by the file header caches.? ACP_HDRCACHE is an AUTOGEN, DYNAMIC, and FEEDBACK parameter. 2 ACP_MAPCACHE? ACP_MAPCACHE sets the number of pages for caching index file< bitmap blocks. Too small a value causes 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_MAXREAD sets the maximum number of directory blocks read in one I/O operation.& ACP_MAXREAD is a DYNAMIC parameter. 2 ACP_MULTIPLED ACP_MULTIPLE enables (1) or disables ( 0) the default creation ofC a separate disk XQP cache for each volume mounted on 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 processes are no longer created. In general, havingD multiple caches is unnecessary. One large cache is more efficient@ than several small ones. ACP_MULTIPLE can be overridden on an6 individual-volume basis with the DCL command MOUNT.4 ACP_MULTIPLE is an AUTOGEN 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 spe cifies 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 used, enabling succeeding ACPs to shareC its code. This parameter should be set to 0 when ACP_MULTIPLE is on.$ ACP_SHARE is a DYNAMIC parameter. 2 ACP_SWAPFLGS? ACP_SWAPFLGS enables or disables swap through the value of a7 4-bit number for the following four classes of ACPs: Bit Class of ACP' 0 Disks mounted by MOUNT/SYSTEM& 1 Disks mounted by MOUNT/GROUP 2 Private disks 3 Magnetic tape ACP@ If the value of the bit is 1, the corresponding class of ACPsB can be swapped. The value of decimal 15 (hexadecimal F-all bits> on) enables swap for all classes of ACP. A value of decimalA 14 disables swap fo r 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 usually no file ACPs exist.4 ACP_SWAPFLGS is an AUTOGEN and DYNAMIC parameter. 2 ACP_SYSACC> ACP_SYSACC sets the number of directory file control blocks< (FCBs) that are cached for disks mounted with the /SYSTEMD qualifier. Each directory FCB 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 providesC quick access to a required directory block. This parameter valueA should be roughly equivalent to the number of directories that= are in use concurrently on each system volu me. 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 systemsC 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.= I SS$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 B ALSETCNT sets the number of balance set slots in the system pageC table. Each memory-resident working set requires one balance set slot.> You can monitor the active system with the DCL command SHOWD MEMORY or the MONITOR PROCESSES command of the Monitor utility toD determine the actual maximum number of working sets in memory. IfB this number is significantly lower than the value of BALSETCNT,D this parameter value may be lowered. If all balance set slots are, being used, r aise 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 BALSE TCNT 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 cal ls 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_CREDITS C 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 should 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 S ystems. 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 DORMANTWAITA DORMANTWAIT specifies, in seconds, the amount of time that can> elapse without a significant event before the system treats= a low-priority computable process as a DORMANT pr ocess 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 system@ 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 Des cription? 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 contents ofB memory are written to the dump@ file selectively to maximizeC the us efulness 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 Alpha system disk, be sure to specify DOSD to an alternate disk.& NOTE= On Alpha systems, you can save space on the system diskB and, i n 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 128 MB of memory, the systemA sets the DUMPSTYLE to 1 (a raw selective dump) and sizes% the dump file appropriately.A o On a system with 128 MB of memory or greater, the system? sets the DUMPSTYLE to 9 (a compressed 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_PA TH_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 disabled 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 F AST_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, plus 2 entries, with the total rounded up to an even number.= Users with CMKRNL privilege can change this parameter on a@ running system. Increasing the value of this parameter allows@ the global page table to expand, on demand, up to the 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 requirements with the /GLOBAL qualifier ofA the Install utility (INSTALL) and reduce the value of GBLPAGES? accordingly. However, do not set the value of this parameterA too low, beca use the page table entries use little permanently> resident memory. If you plan to install many user images as? shared, or if user programs are likely to create many global; sections, you must increase the value of this parameter.> GBLPAGES has the AUTOGEN, DYNAMIC, FEEDBACK, GEN, and MAJOR attributes. 2 GBLPAGFILC GBLPAGFIL defines the maximum number of systemwide pages allowedB for global page-file sections (scratch global sections that can> be used without bei ng 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 accordingly. Users with CMKRNL privilege can change, this parameter value on a running system.@ Global page-file sections are created with the Create and MapA Section system serv ices ($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 sequential files, use the multiblock count of the first@ stream to perform the $CONNECT service in place of the file's bucket size.< The default value for this parameter is ade quate 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 permanently resident memory.D The default value is sufficient for the images normally installed? as shared in the system startup command procedures. Once theA system is running and all g lobal 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 G H_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 hintC region at the the end of system startup. The unused pages of theA resident image granularity hint region are either reserved for5 future use, or given back to the free memory list.= GH_RSRVPGCNT specifies the number of pages that LDR$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 shared 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 AUT OGEN, 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 befo re 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 paramete r. 2 LGI_BRK_TERM: LGI_BRK_TERM causes the terminal name to be part of theB association string for the terminal mode of break-in detection.@ When LGI_BRK_TERM is set to off (0), the processing considers? the local or remote source of the attempt, allowing break-in@ detection to correlate failed access attempts across multipleB terminal devices. When set to on (1), LGI_BRK_TERM assumes that> only local hard-wired or dedicated terminals are in use andD causes breakin detection processing to include the specific localB terminal name when examining and correlating break-in attempts.B Ordinarily, LGI_BRK_TERM should be set to off (0) when physical? terminal names are created dynamically, such as when network, protocols like LAT and Telnet are in use.' LGI_BRK_TERM is a DYNAMIC parameter. 2 LGI_BRK_TMO= LGI_BRK_TMO specifies the length of the failure monitoringC period. This time increment is added to the suspect's expirationD time each time a login failure occurs. Once the expiration periodC passes, prior failures are discarded, and the suspect is given a clean slate.& LGI_BRK_TMO is a DYNAMIC parameter. 2 LGI_CALLOUTSD LGI_CALLOUTS specifies the number of installation security policyD callout modules to be invoked at each login. LGI_CALLOUTS must be/ set to 0 unless callout modules are present.' LGI_CALLOUTS is a DYNAMIC parameter. 2 LGI_HID_TIMB LGI_HID_TIM specifies the num ber 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 ac count passwords at login time. Also, when using theA SET PASSWORD command, LGI_PWD_TMO specifies the period of time@ the system waits for a user to type in a new password, an old+ password, and the password verification.& LGI_PWD_TMO is a DYNAMIC parameter. 2 LGI_RETRY_LIM? LGI_RETRY_LIM specifies the number of retry attempts allowedC users attempting to log in. If this parameter is greater than 0,D and a legitimate user fails to log in correctly because of typingD  errors, the user does not automatically lose the carrier. InsteadA (provided that LGI_RETRY_TMO has not elapsed), by pressing the> Return key, the user is prompted to enter the user name andA password again. Once the specified number of attempts has been? made without success, the user loses the carrier. As long as@ neither LGI_BRK_LIM nor LGI_BRK_TMO has elapsed, the user can% dial in again and reattempt login.( LGI_RETRY_LIM is a DYNAMIC parameter. 2 LGI_RETRY_TMO@ LGI_RETRY_TMO specifies the number of seconds allowed between< login retry attempts after each login failure. (Users can; initiate login retries by pressing the Return key.) This: parameter is intended to be used with the LGI_RETRY_LIM@ parameter; it allows dialup users a reasonable amount of timeA and number of opportunities to attempt logins before they lose the carrier.( LGI_RETRY_TMO is a DYNAMIC parameter. 2 LNMPHASHTBLD LNMPHASHTBL sets the size of th e 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 LNMSH ASHTBLC 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 l arge 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 LOCKI DTBLB LOCKIDTBL sets the initial number of entries in the system Lock@ ID table and defines the amount by which the Lock ID table isA extended whenever the system runs out of locks. One entry mustB exist for each lock in the system; each entry requires 4 bytes.A For simple timesharing systems, the default value is adequate.C If your application uses many locks, as in the case of heavy RMS@ file sharing or a database management application, you shouldC increase this parameter. When you change the value of LOCKIDTBL,> examine the value of RESHASHTBL and change it if necessary.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 numbe r 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% drive rs 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 set s 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 cluster 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 D YNAMIC 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 n umber 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@ r equired 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 Reclamation 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 be fore 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 detection 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 pollin g 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 i t 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, M PW_IOLIMIT is an AUTOGEN-altered parameter. 2 MPW_LOLIMITB MPW_LOLIMIT sets a lower limit for the modified-page list. When@ writing of the list causes the number of pages on the list to. drop to or below this limit, writing stops.C MPW_LOLIMIT ensures that a certain number of pages are available> on the modified-page list for page faults. If the number isA too small, the caching effectiveness of the 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 pa ges 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 GEN 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 the time in seconds that the OpenVMS MSCP server= uses to detect MSCP command timeouts. The MSCP Server must? complete the command within a built-in time of approximately; 40 se conds plus the value of the MSCP_CMD_TMO parameter.> The MSCP_CMD_TMO default value of 0 is normally adequate. A@ value of 0 provides the same behavior as in previous releasesD of OpenVMS (which did not have an MSCP_CMD_TMO system parameter).@ A nonzero setting increases the amount of time before an MSCP command times out.> If command timeout errors are being logged on client nodes,> setting the parameter to a nonzero value on OpenVMS servers? 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 the type you want in the followingA table and specify its value. For some systems, you may want toA specify two serving types, such as serving the system disk andA serving local ly 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 the 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-checking 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 con!trols 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 continues on a given disk volume. If the mountA verification does not recover the volume within that time, theA I/O operations outstanding to the volume terminate abnormally.C MVTIM#EOUT 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_P %KTSZA 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 PEdriver determines that the LAN@ path between two nodes, including the local and remote LAN? adapters and intervening LAN equipment, can only convey a lesser size.? (In other words, only nodes with large-packet LAN adapters@ connected end-to-end by large-packet LAN equipment can useD large packets. Nodes connected to large-packet LANs but havingC an end-to-end path that involves an Ethernet segment restrict= packet size to that of an Ethernet packet (1498 bytes).; o For performance reasons, PEDRIVER might further limit? the upper bound on packet size so that the packets can be; allocated from a lookaside list in the n)onpaged 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 attribute. 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 DYNAMI+C 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 recommends 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 installation 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 0D after AUTOGEN has determined more refined values for the NPAGEDYN" and NPAGEVIR system parameters. 2 NPAGEDYN@ NPAGEDYN sets the size of the nonpaged dynamic pool in by /tes.> This figure is rounded down to an integral number of pages.@ NPAGEDYN establishes the initial setting of the nonpaged pool8 size, but the pool size can be increased dynamically.@ To set a value for this parameter, use AUTOGEN initially, and> then monitor the amount of space actually used with the DCL! command SHOW MEMORY/POOL/FULL.? For the benefit of OpenVMS VAX systems with limited physicalC memory, AUTOGEN logs a warning message in its report if NPAGEDYNB exc 0eeds 10 percent of physical memory or if NPAGEVIR exceeds 33 percent of physical memory.? AUTOGEN also limits its own calculated value for NPAGEDYN toB 20 percent of physical memory and limits NPAGEVIR to 50 percent? of physical memory. These calculated values are adequate for> most workstations and systems with 16 or fewer megabytes ofC physical memory. If your system requires a larger value, you canB override the AUTOGEN calculated values by setting higher values in MO1DPARAMS.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 2 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,3043 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 per 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 4 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.+ 5 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 a6ddressable 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 NPAG_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_GE7NTLE 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 buffer. 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 dynami 8c 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 structures. 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 max9imum& 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. 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 C:ompaq 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 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 has a totalA of 5 ports assigned to port numbers 0 through 4, you could set PAMAXPORT to 4.@ If CI or DSSI devices are not configured on your system, this parameter is ig<nored.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 defaultA 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 boot =ed. This parameter is@ useful when you want to bring up a computer detached from the- rest of the cluster for checkout purposes.C PANOPOLL is functionally equivalent to uncabling the system fromC the DSSI or star coupler. This parameter does not affect OpenVMS! Cluster communications by LAN.? The default value of 0 is the normal setting and is requiredA if you are booting from an HSC controller or if your system isD joining an OpenVMS Cluster. This parameter is ignor>ed if no CI or. DSSI devices are configured on your system.# PANOPOLL is a DYNAMIC parameter. 2 PANUMPOLL> PANUMPOLL establishes the number of CI and DSSI ports to beA polled each polling interval. The normal setting for PANUMPOLL is 16.B On systems with less powerful CPUs, the parameter may be usefulB in applications sensitive to the amount of contiguous time thatD the system spends at IPL 8. Reducing PANUMPOLL reduces the amount= of time spent at IPL 8 duri?ng each polling interval, while@ increasing the number of polling intervals needed to discover new or failed ports.@ If CI or DSSI devices are not configured on your system, this parameter is ignored.$ PANUMPOLL is a DYNAMIC parameter. 2 PAPOLLINTERVALA Specifies, in seconds, the polling interval the CI port driverB uses to poll for a newly booted computer, a broken port-to-port0 virtual circuit, or a failed remote computer.@ 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? Specifies, 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 allocatioAn 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 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 B circuit checking gets enabled on the local system. The8 TIMVCFAIL parameter controls the time (1-99 seconds).A PASANITY is normally set to 1 and should be set to 0 only when@ you are debugging with XDELTA or planning to halt the CPU for" periods of 100 seconds or more.> PASANITY is only semidynamic. A new value of PASANITY takes7 effect on the next CI or DSSI port reinitialization.@ If CI or DSSI devices are not configured on your system, this parameter is ignored.C# 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 is an AUTOGEN parameter. 2 PASTIMOUT= The basic interval at which the CI port driver wakes up toC perform time-based bookkeeping operations. It is also the period> afterD 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, PE4, 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/ def Eault 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 during 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 i Fs 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 should not be greater than one-fourth the default sizeA of the average working set to prevent a single page fault fromA displacing a major portion of a working set. Too large a value@ G 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) into 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 ma HpBa 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. I 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 it is faulting more than 120 pagesB per 10 seconds. Decreasing the value of this parameter tends to@ increase the limits of the working sets, while increasing its( value tends to Jdecrease 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 PFRATL@ PFRATL specifies the page fault rate below which the limit of@ a working set is automatically decreased. The unit of measureA is the number of faults per 10 seconds of proKcessor 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 increase their limits.9 PFRATL has the AUTOGEN, DYNAMIC, and MAJOR attributes. 2 PHYSICAL_MEMORY@ (Alpha only) PHYSICAL_MEMORY specifies the amount of physical= memory avaiLlable 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 parameter unless Compaq recommends that you do so.+ PHYSICAL_MEMORY is an AUTOGEN parameter. 2 PHYSICALPAGES? (VAX only) PHYSICALPAGES sets the maximum number of physicalM< 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 you 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 N 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 demands 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@ chang Oe. 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 automatic priority boost for 1 quantum,D unless the priority of the currently executing process is greaterC than 15. The priority boost is done to avoid potential deadlocks on the systPem.= 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 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-che Qcking> 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 nonzero value, theC monitoring version of SYSTEM_PRIMITIVES.EXE, which contains both< pool-checking code and statistics maintenance, is loaded.D Setting the SYSTEM_CHECK parameRter 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 is 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 reqSuests 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 request is notD implemented, the shut-down procedure will leave the system halted but fully powered.# POWEROFF is a DYNAMIC parameter. 2 PQL_DASTLMB PQL_DASTLM sets tThe 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 outstanding buffered I/O operations permitted to aD process created by the Create Process ($CREPRC) system service or! the DCL command RUN (Process).1 PQL_DBIOLM has the DYNAMIC Uand 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. 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_DCVPULM 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 for a process@ created by the Create Process ($CREPRC) system service or the DCL command RUN (Process).1 PQL_DDIOLM has the DYNAMIC and GEN attributes. 2 PQL_DENQLMWB 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 Create Process ($CREPRC) system service or the DCL command RUN (Process).1 PQL_DFILLM has the DYNAMIC and GEN attributes. 2 PQL_DJTQUOTAA PQL_DJTQUOTA sets the default X 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) names or temporary mailboxes are used.' PQL_DJTQUOTA is a DYNAMIC parameter. 2 PQL_DPGFLQUOTA@ PQL_DPGFLQUOTA sets the default page file quota for a processD created by Ythe 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_DPRCLM= PQL_DPRCLM sets the default subprocess limit for a process@ created by the Create Process ($CREPRC) system service or the DCL command RUN (Process).1 PQL_DPRCLM has the ZDYNAMIC and GEN attributes. 2 PQL_DTQELMB PQL_DTQELM sets the default number of timer queue entries for aD process created by the Create Process ($CREPRC) system service or! the DCL command RUN (Process).1 PQL_DTQELM has the DYNAMIC and GEN attributes. 2 PQL_DWSDEFAULTA PQL_DWSDEFAULT sets the default working set size for a processD created by the Create Process ($CREPRC) system service or the DCL command RUN (Process).5 PQL_DWSDEFAULT has the AUTOGE[N 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_DWSQUOTA sets the default working set quota for a processD created by the Create Process ($CREPRC) system service or the DCL command RUN (Process).= PQL_DWSQUOTA has the AUTOGEN, DYN\AMIC, 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? PQL_MBIOLM sets the minimum buffered I/O limit for a processD created by the Create Process ($CREPRC) system service or the DCL command RUN (Process).1 PQL_MBIOLM has the DYNAMI]C 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 minimum CPU time limit in increments of> 10 milliseconds for a process created by the Create Process= ($CREPRC) system service or the DCL command RUN (Process).1 PQL_MCPULM has the ^DYNAMIC and GEN attributes. 2 PQL_MDIOLM= PQL_MDIOLM sets the minimum direct I/O limit for a process@ created by the Create 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 default 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 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_MJTQUOT`A 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 On 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).< PaQL_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 has the DYNAMIC and GEN attributes. 2 PQL_MTQELMB PQL_MTQELM sets the minimum number of timer queue entries for aD process created by the Create Process ($CREPRC) system servbice 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 overrides a smaller quantity that is set for a user in AUTHORIZE.5 PQL_MWSDEFAULT has the AUTOGEN and GEN attributes. 2 PQL_MWSEXTENTB PQL_MWSEXTENT sets the minimum workcing 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 quantityd 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 control protocol@ disks, on other nodes. All discovered nodes are polled during each interval.C This parameter trades polling overhead against quick recognition, of new syst eems 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, fa@ 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 g32 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 PDA0A 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 hparameter 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 Manual 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 paraimeter 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 votes 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 recejive 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 systems,* 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 Dkomains (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 attribute. 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 val lue 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 Device Support Manual< REALTIME_SPTS has the DYNAMIC, GEN, and MAJOR attributes. 2 RECNXINTERVAL> RECNXINTERVAL establishes the polling interval, in seconds,; durinmg 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 checking.= 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 R nESHASHTBL 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 constraints 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 RoJOBLIMD 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 each 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 i ps an AUTOGEN and DYNAMIC parameter. 2 RMS_DFMBFIDXA RMS_DFMBFIDX establishes the default RMS multibuffer count forD indexed sequential disk operations. This value defines the number? of I/O buffers that RMS allocates for each indexed file. ForC sequential access, a larger number that allows some of the 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 parameteqr with SHOW RMS_ DEFAULT.4 RMS_DFMBFIDX is an AUTOGEN and DYNAMIC parameter. 2 RMS_DFMBFRELA RMS_DFMBFREL establishes the default RMS multibuffer count forA relative disk operations. This value defines the number of I/O5 buffers that RMS allocates for each relative file.9 You can set this 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. r2 RMS_DFMBFSDKA RMS_DFMBFSDK establishes the default RMS multibuffer count forC sequential disk operations. This value defines the number of I/O8 buffers that RMS allocates for sequential disk files.@ The default value is usually adequate. However, if read-ahead@ or write-behind operations are used, a 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_ DEFsAULT.4 RMS_DFMBFSDK is an AUTOGEN and DYNAMIC parameter. 2 RMS_DFMBFSMTA RMS_DFMBFSMT establishes the default RMS multibuffer count forA magnetic tape operations. This value defines the number of I/O6 buffers that RMS allocates for magnetic tape files.9 You can set this system parameter with the DCL 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 t RMS_DFMBFSUR establishes the default multibuffer count for unit record devices.9 You can set this system parameter with the DCL commandB SET RMS_DEFAULT/SYSTEM and display the parameter with SHOW RMS_ DEFAULT.4 RMS_DFMBFSUR is an AUTOGEN and DYNAMIC parameter. 2 RMS_DFNBCB RMS_DFNBC specifies a default block count for network access to> remote, sequential, indexed sequential, and relative files.@ The network block count value represents the number of blocks? u that RMS is prepared to allocate for the I/O buffers used toB transmit and receive data. The buffer size used for remote fileB access, however, is the result of a negotiation between RMS andC the remote file access listener (FAL). The buffer size chosen is* the smaller of the two sizes presented.C Thus, RMS_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 fvile. In other words,B the largest record that can be transferred must be less than or. equal to RMS_DFNBC multiplied by 512 bytes.9 You can set this system parameter with the DCL commandB SET RMS_DEFAULT/SYSTEM and display the parameter with SHOW RMS_ DEFAULT.1 RMS_DFNBC is an AUTOGEN and DYNAMIC parameter. 2 RMS_EXTEND_SIZE@ RMS_EXTEND_SIZE specifies the number of blocks by which filesD are extended as they are written. This number should be chosen toD balan wce the amount of extra disk space wasted at the ends of eachD file against the performance improvement provided by making large extents infrequently.B When small disk quotas are used, specify a small number such asD the disk cluster size to prevent the user's disk quota from beingC consumed. If the value of 0 is used, RMS allocates large extentsB and truncates the file back to its actual usage when it closes.9 You can set this system parameter with the DCL commandB SET RxMS_DEFAULT/SYSTEM and display the parameter with SHOW RMS_ DEFAULT.* RMS_EXTEND_SIZE is a DYNAMIC parameter. 2 RMS_FILEPROTA RMS_FILEPROT determines the default file protection for systemC processes such as those that create the error log, operator log,A and job controller. It also determines default file protectionC for processes created by the job controller (all interactive and batch processes).@ Because a process always inherits its default file protecti yonA 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 $CRMPSC 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 (hexadecimazl),- 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 create? 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, an{d 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 special 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 o|f 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_SIZED (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_AP}P 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 that 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 this parameter unless Compaq recommends that you do so.A The vector scheduling subsystem presently provides an enlargedC quantum to processes requiring vector capability. Custo mer 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 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, SCSBUFF CNT 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> simultaneous I/Os. Various performance monitors report when= a system is out of buffer descriptors for a given workload? which is an indication that a larger value for SCSBUFFCNT 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 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 t he 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 for 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 Compaq 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 system 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 of 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 Re view 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 physical 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 use this parameter to extend the time a booting system waitsB for all former members of the shadowed system disk to become available.> o Once the system successfully mount s 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 through 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 n umber 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 Shadowing 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_FLAG SB (Alpha Galaxy platforms only) The SMCI_FLAGS parameter controls@ operational aspects of SYS$PBDRIVER, the Galaxy Shared Memory Cluster Interconnect (SMCI).* Bits in the bit mask are the following:/ Bit Mask Description> 0 0 0 = Do not create local communications channelsA (SYSGEN default). Local SCS communications 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 m essages 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 parameter 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 Partit ion 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 of the Galaxy software, having? multiple communications channels is not an advantage because< SYS$PBDRIVER does not support fast path. A future release> of OpenVMS will provide F ast 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 to 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 multiprocessing (SMP)A system. Each CPU in an SMP system monitors the sanity timer ofD one other CPU in the configuration to detect hardware or softwareD failures. If allowed to go undetected, these failures could cause> the cluster to hang. A timeout causes a CPUSANITY bugcheck.; The default value is 300 milliseconds (30 10-millisecond intervals). 2 SMP_SPINWAITD SMP_SPINWAIT establishes, in 10-microsecond intervals, the amount@ of time a CPU in an SMP system normally waits for access to a7 shared resource. This process is called spinwaiting.+ A timeout causes a CPUSPINWAIT bugcheck.C The default value is 100000 (100,000 10-microsecond intervals or 1 second). 2 SMP_TICK_CNTA SMP_TICK_CNT sets the frequency of sanity timer checks by each# CPU in a multiprocessing system.= 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< SWPRATE 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 SYSTEM_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 MULTIPROCESSING 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 allocation class for theA system. The tape allocation class creates a unique clusterwide: device name for multiple access paths to the same tape.> The TAPE_ALLOCLASS parameter can also be used to generate a? unique clusterwide name for tape devices with identical unit numbers. 2 TAPE_MVTIMEOUTB TAPE_MVTIMEOUT is the time in seconds that a mount verificationB attempt continues on a given magnetic tape volume. If the mountA verification does not recover the volume within that time, theA I/O operations outstanding to the volume terminate abnormally.) TAPE_MVTIMEOUT is a DYNAMIC parameter. 2 TBSKIPWSL= TBSKIPWSL specifies the maximum number of working set list@ entries that may be skipped while scanning for a "good" entry= to discard. Setting this parameter to 0 disables skipping.= 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? pro cessor 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 continues@ the boot operation, and the date and time are set to the last( recorded time that the system booted.& NOTE< Compaq recommends that y ou 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 t ime 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 st arting= 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 virtual= 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 parameter 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 fo llowing> 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 includes any systems running@ OpenVMS Version 7.1-x or earlier, serving all available tapesC is restricted to serving all tapes except those whose allocationB class does not match the system's allocation class (pre-VersionB 7.2 meaning). To specify this type of serving, use the value 9,@ which sets bit 0 and bit 3. The following table describes the= serving type controlled by each bit and its decimal value. Value When Bit Set DescriptionA Bit 0 1 Serve all available tapes (locally attached and? those connected to HSx and DSSI controllers).D Tapes with allocation classes that differ from theA system's allocation class (set by the ALLOCLASSA parameter) are also served if bit 3 is not set.? Bit 1 2 Serve locally attached (non-HSx and non-DSSI) tapes. Bit 2 N/A Reserved.D Bit 3 8 Restrict the serving specified by bit 0. All tapesB except those with allocation classes that differ@ from the system's allocation class (set by the2 ALLOCLASS parame ter) 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:, Cha racteristic 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 derived by summing the following hexadecimal values:( Characteristic Value (Hex) FunctionA LOCALECHO 1 Enable local echo terminal logic;?  use with the TTY_DEFCHAR NOECHO/ characteristic.: AUTOBAUD 2 Enable autobaud detection.2 HANGUP 4 Hang up on logout.D MODHANGUP 8 Allow modification of HANGUP without+ privileges.> BRDCSTMBX 10 Allow sending of broadcasts to* mailboxes.> XON 20 (No effect in this parameter.)> DMA  40 (No effect in this parameter.)< ALTYPEAHD 80 Use the alternate type-ahead+ parameters.? SETSPEED 100 Clear to allow setting of speed3 without privileges.@ DCL_MAILBX 200 Function reserved for Compaq use% only.@ DECCRT4 400 Terminal is DIGITAL CRT Level 4.? COMMSYNC 800 Enable flow cont rol 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.= SECURE 10000 Guarantees that no process isA connected to terminal after Break/ key is pressed.A DISCONNEC T 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 Terminal supports loadable character& fonts.: PRINTER 400000 Terminal has printer port.@ APP_KEYPAD 800000 Notifies application  programs of< state to set keypad on exit.= ANSICRT 1000000 Terminal conforms to ANSI CRT6 programming standards.D REGIS 2000000 Terminal has REGIS CRT capabilities.4 BLOCK 4000000 Block mode terminal.< AVO 8000000 Terminal has advanced video.7 EDIT 10000000 Terminal has local edit- capabilities.: DECCRT 20000000 Terminal is a DIGITAL CRT.B DECCRT2 40000000 Terminal is a DIGITAL CRT Level 2.B DECCRT3 80000000 Terminal is a DIGITAL CRT Level 3.) The defaults are AUTOBAUD and EDITING. 2 TTY_DEFPORTB TTY_DEFPORT provides flag bits for port drivers. Bit 0 set to 1D indicates 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 contro llers.< 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 T TY_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_TIMEOUT sets the number of seconds before a processB associated with a disconnected terminal is deleted. The defaultB value (900 seconds) is usually adequate. Note that using values? for TTY_TIMEOUT greater than one year (value %X01E13380) canC cause overflow errors and result in a disconnected device timing out immediately.& TTY_TIMEOUT is a DYNAMIC parameter. 2 TTY_TYPAHDSZ@ TTY_TYPAHDSZ sets the size of the terminal type-ahead buffer.C The default value is usually adequate. Do not exceed the maximum. value of 32767 when setting this parameter. 2 UAFALTERNATE< UAFALTERNATE enables or disables the assignment of SYSUAF< as the lo gical 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@ s ubject 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 BALSETCNT.@ When creating a new process, if the set of real balance slots? is allocated, then a virtual balance slot is created and the? owner of a real balance slot is selected an d 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 VC C_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 th eD 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@ chang e. 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, dependingB 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 controlsD 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 VEC TOR_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 deco mpress 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 configurat ion.? 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 availabl e@ 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> m illiseconds between assessments of the most suitable writeD bitmap message mode. In single-message mode, the writes issued byB each remote node are, by default, sent one by one in individual< SCS messages to the node with the master write bitmap. If= the writes sent by a remote node reach an upper threshhold? of messages during a specified interval, single-message mode% switches to buffered-message mode.> In buffered-message mode, WBM_MSG_INT is the maximum time aA message  waits before it is sent. In buffered-message mode, the@ messages are collected for a specified interval and then sentC in one SCS message. During periods of increased message traffic,? grouping multiple messages to send in one SCS message to theD master write bitmap is generally more efficient than sending each message separately.C The minimum value of WBM_MSG_INT is 10 milliseconds. The maximumD value is -1, which corresponds to the maximum positive value that< a longw ord 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 OpenVMS Cluster system. The others are WBM_MSG_INT and WBM_MSG_B UPPER. These parameters set the interval at which the frequency@ of sending messages is tested and also set an upper and l owerA 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_MSG_LOWER is a DYNAMIC parameter. 2 WBM_MSG_UPPER; WBM_MSG_UPPER is one of three system parameters that are= available for managing the update traffic between a master? w rite 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 grouped into* one SCS message or are sent one by one.B WBM_MSG_UPPER is the upper threshold for the number of messages@ sent during the test interval that initiates buffered-messageC mode. In buffered-message mode, the messages are collected for a7 specified interval and then sent in one SCS message.A The minimum value of WBM_MSG_UPPER is 0 messages per interval.< The maximum value is -1, which corresponds to the maximum? positive value that a longword can represent. The default is 100.( 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 adjustment 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 Alph a 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 WSDEC has the AUTOGEN, DYNAMIC, and MAJOR attributes. 2 WSINCC Decreasing the value of this parameter tends to reduce the speedD with which working set limits are increased w hen 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 (which 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' defau lt 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 pagelets 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 also 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 chan ge 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-END! PARAM-INSERT<! HELP on the individual parameters is taken from SYSGEN andB! is inserted here by the build procedures. Please do not edit the! first comment  line.M!****************************************************************************ww5l1 Usage_SummaryC To invoke SYSMAN, enter the following command at the DCL prompt: $ RUN SYS$SYSTEM:SYSMAN> SYSMAN displays the following prompt at which you can enter: SYSMAN commands using the standard rules of DCL syntax: SYSMAN>> As an alternative, you can enter the RSX command MCR, which expands to RUN SYS$SYSTEM: $ MCR SYSMANC With the MCR command, you can invoke SYSMAN and supply a commandA in one command string. With any SYSMAN command invoked in thisC way (except SET ENVIRONMENT), SYSMAN executes the command stringD and exits. After executing a SET ENVIRONMENT command, the utility returns the SYSMAN> prompt.A To exit from SYSMAN and return to the DCL command level, enter: the EXIT command at the SYSMAN> prompt or press Ctrl/Z.& NOTE, SYSMAN has the following res trictions:? o You must have the OPER privilege on the local node and> authorization for the OPER or SETPRV privilege on any4 remote nodes in the management environment.A You must also have the privileges required by individual@ commands, as each command in this chapter describes. ToA determine which privileges are required for DCL commandsA or for system management utilities, refer to the OpenVMSA DCL Dictionary or the appro priate utility reference part of this manual.B o You cannot run SYSMAN from a batch job in any environment" that requires a password.< o Some DCL commands, such as SHOW SYSTEM/CLUSTER, SET= CLUSTER/QUORUM, MOUNT/CLUSTER, and some forms of the< REPLY command, operate clusterwide by design. These< commands should not be run using SYSMAN, unless the> environment has been set to a single node. Similarly,; operations on clu sterwide logical names and tables' operate clusterwide by design.: o If a SYSMAN user running with more than 125 total> rights attempts to issue a SYSMAN command to a remote> node within a cluster, the following error message is displayed:0 SMI-E-RIGHTSLIM, Rights limit exceeded.? Note that this rights limitation includes a minimum ofA three identifiers that are granted during login when the( process rights list is created: - A UIC identifier - A system identifierB - Depending upon the environment in which the process is< operating, at least one environmental identifierA Users who want to run SYSMAN must have either one of the following items:; - A separate account with no more than 125 rightsA - Enough identifiers removed from their current account? so that the total number of rights falls within the appropriate range ww