% Librarian I01-42;gKKgKno5d @ALFATTACH"CLASS_SCHEDULE5 CONFIGURATIONEDEFINE DescriptionL DISKQUOTArDO DUMP_PRIORITYEXIT(IOLICENSEOverview PARAMETERSdB RAD_ExampleRESERVED_MEMORY SETvSHOW$FSHUTDOWN-SPAWN6 STARTUP[ SYS_LOADABLE(Sys_Parameters SYSMAN displays the following prompt at which you can enter: SYSMAN commands using the standard rules of DCL syntax: SYSMAN> 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 restrictions:? 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 com mand in this chapter describes. ToA determine which privileges are required for DCL commands@ or for system management utilities, see the VSI OpenVMSA DCL Dictionary or the appropriate 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 clusterwide 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 followi ng 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 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 $ RUN SYS$SYSTEM:SYSMAN SYSMAN> @ENV.COM3 %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 $ RUN SYS$SYSTEM:SYSMAN SYSMAN> @TIME8 System time on node NODE23: 19-JUN-2002 13:32:19.458 System time on node NODE24: 19-JUN-2002 13:32:27.798 System time on node NODE25: 19-JUN-2002 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 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 use 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 MN34C3/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 Specifies 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 char acters 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.& NOTE= VSI recommends that you use caution when issuing REMOVEB commands from Version 6.1 or lower SYSMAN clients to Version 6.2 or higher systems. 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. ww =gK 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 S pecifies 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 destina !tion 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 conj"unction 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). ww4=gK1 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 sched $uling 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@ allotte%d 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 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")] /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 = ([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= follo 'wed 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 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:% [/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 el*igible 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 d+efault 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 clas,s_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 comman-d. 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")] /CPULIMITD Defines the maximum amount of CPU time that this scheduling class0 can receive for the specified days and hours./ The syntax for this qualifier is as follows:7 /C .PULIMIT = ([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 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 inclus/ive; 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:% [/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 0and 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 SY1SUAF 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 2isC 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 the time percentage as, "none" for the 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 R3ESUME 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 the 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 s4cheduling 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 SHOW 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 ab5out 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 Primary 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 Specifies6 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, all processes that are? part of the scheduling class remain as part of the class but" are granted unlimited CPU time. ww=gK1 CONFIGURATIONB There are several CONFIGURATION subcommands. Select the one you want from the7 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_NUMBER /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 f8rom 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 password 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 9the 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@ multiple 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, see VSI 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 and 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 c;ommand. 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- %SYSMAN-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 p<assword. 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.B 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]D You can also enter a delta time value. For more information about/ time formats, see the OpenVMS User's Manual.A In an environment of individual 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? spe>cified 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 cluster. 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 the? time-of-year clock is optional for some processors; for more, information, see your processor handboo ?k.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 synchronize 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 q@uickly 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 theA 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. B 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 specification 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 meCssage 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=SYSPRV D1 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 Ea 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-2002 13:32:19.455 System time on node NODE22: 19-JUN-2002 F13:32:27.795 System time on node NODE23: 19-JUN-2002 13:32:58.66A The CONFIGURATION SHOW TIME command in this example displays3 the system times for all nodes in the cluster. ww>gK 1 DEFINE 2 /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 nGame 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 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 H 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 - 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 yoIu 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@ Specifies 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, anyJ 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 the 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 sKtring. 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@ Determines 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 DesLcriptionA 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 exit 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 Mthe= 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 keypad 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. ww m>gK 1 DISKQUOTAC There are several DISKQUOTA sNubcommands. 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 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 aboutC O UIC specification, see the VSI 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 a complete descriptionB of rights identifiers, see the VSI 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 Qualifiers /DEVICE /DEVICE=devi Pce-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.? 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,, Q 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 overdraft 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]. R3 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 overdraft 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:( Individ Sual 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> DISKQUOTA 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 T 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@ blocks, 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? U 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 file 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 V 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 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 W 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 a 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 vaXlues.& NOTEC VSI recommends that you do not create and enable a quota fileA on the system disk unless users are allowed to create files on that disk. 3 Example SYSMAN> 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> DISKQUOTAY 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 they 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 sameZ 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.' 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. 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. 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 operations 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. 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 translated in the target environment.? Without a device specification, SYSMAN uses the default dis _k@ 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. 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 owner9 Specifies the user identification code (UIC) or rightsA identifier. You can s apecify the UIC in numeric or alphanumericD format. For complete information about UIC specification, see the( VSI 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 a complete descriptionB of rights identifiers, see the VSI OpenVMS Programming Concepts Manual.< When working in nonlocal environments, make sure that the@ alphanumeric UIC or rights identifiers that you use are validb 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. Unless you have set a default device withB the SET PROFILE command, the default disk is the currcent 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? Specifies a positive integer that provides the quota for theC specified UIC. If you omi dt 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, use the DISKQUOTA MODIFY command toC set default values for quotas and overdrafts. UIC [0,0]e 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,0] -, _SYSMAN> /PERMQUOTA=3000 /OVERDRAFT=300A The commands in this example edit the f 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 environment.C If the user name DAVIS has a unique UIC on the system, you can! enterg 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 Qualifier /DEVICE /DEVICE=device-specA Specifies the disk volume that contai hns 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 on another node,, depending on the established environment. 3 Description= The DIS iKQUOTA 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.D Use the DISKQUOTA REBUILD command in the following circumstances:B o After creating aj 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 commands enable the quota file and reconstruct the usageD counts for all entries on disk DUA226, kwhich 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 alphanumericD format. For complete information about UIC specification, see the( VSI OpenVMS Guide to System Security.@ Rights identifiers are granteld with the Authorize utility andB use an ID format rather than a UIC format. For more informationE about rights identifiers, see the VSI 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> Specifies the disk volume containing the quota file. SYSMAN@ validates the device specif mication 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 environment. 3 DescriptionA The DISKQUOTA REMOVE command eliminates the specified UIC fromn& 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 %SYSMAN-I-DEFPRIV, Process privileges on node MARS -- TMPMGX OPER NETMBoX 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 to the quota file. Format DISKQUOTA SHOW owner 3 Parameter owner p9 Specifies the user identification code (UIC) or rightsA identifier. You can specify the UIC in numeric or alphanumericD format. For complete information about UIC specification, see the( VSI 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 a complete descriptionB of rights identifiers, see the VSI OpenVMS Programming Concepts Manual.A You can use an asterisk wildcard charqacter (*) 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 Qualifiers /DEVICE /DEVICE=device-specA Specifies the disk volume containing the quotra 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 another node,, depending on the established environment. /OUTPUT /OUTPUT[=filespec]s7 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. wwp0?gK1 DOB Executes a DCL command or DCL command procedure on all nodes in& the current management envirotnment.= 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 RUN SYS$SYSTEM:SYSMAN [SYSMAN-command] is not* supported. Instead, follow these steps:; 1. Enter RUN SYS$SYSTEM:SYSMAN at the dollar ($) prompt.@ 2. At the SYSMAN> prompt, set the environment to the selectedu5 node or nodes with the SET ENVIRONMENT command.3 3. Enter a SYSMAN command at the SYSMAN> prompt.A For complete information about DCL command syntax, see the VSI OpenVMS DCL Dictionary. 2 Qualifiers /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 system prompts you as follows:, Execute command for node ? v[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 lettersw (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 message and redisplays the prompt. /OUTPUT /OUTPUT[=filespec]? x 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 sys ytem 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 s ztring, 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.C The system cannot display output returned from a co {mmand of more. than 2048 characters without concatenation.? Three exceptions to be aware of when using the DO command in# clusters are the following ones:C o In a multi-architecture heterogeneous cluster running OpenVMS< VAX, Alpha, and Integrity servers, some uses of the DO? command may require special handling. For example, if you> are installing images that are named differently in eachB architecture, you can still use the DO command if you create> | logical name tables for VAX, Alpha, and Integrity serverC 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 avoid 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 thes}e 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 goes to the file SYSMAN.LIS rather than to the terminal.( 2.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 3.$ CREATE/NAME_TABLE/PARENT=LNM$SYSTEM_DIRECTORY SYSMAN$NODE_TABLEF $ DEFINE/TABLE=SYSMAN$NODE_TABLE ALPHA_NODES NODE21,NODE22,NODE23D $ DEFIN E/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, c ommand 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 nodes9 SYSMAN> DO IN STALL 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 NODE26B This example shows how you can define logical n ames for VAX, ? Alpha, and Integrity server nodes in a multi-architecture ? heterogeneous cluster, so that you can use the DO command - to install architecture-specific images. 4.$ RUN SYS$SYSTEM: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 <Return>7 %SYSMAN-I-OUTPUT, command execution on node EXPERT 22-MAR-2002 09:40:285 Execute command for node MODERN? [N]: Y 7 %SYSMAN-I-OUTPUT, command execution on node MODERN 22-MAR-2002 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. 5.SYSMAN> DO/PAUSE SHOW TIME7 %SYSMAN-I-OUTPUT, command execution on node EXPERT 22-MAR-2002 09:40:13& Press return to continue 6 %SYSMAN-I-OUTPUT, command execution on node MODER 22-MAR-2002 09:40:41& Press return to continue 7 %SYSMAN-I-OUTPUT, command execution on node IMPOSE 22-MAR-2002 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.wwW?gK1 DUMP_PRIORITYA Several DUMP_PRIORITY subcommands exist on Alpha and Integrity? servers. Select the one you want from the choices below. TheA ADD command contains a description of the System Dump PriorityD registry data file, whose contents DUMP_PRIORITY commands affect. 2 ADD 3 and 4 IntegrityC On Alpha and Integr ity servers, adds an entry to the System Dump Priority registry file.A The registry data file is the permanent database that survivesD reboots. It is loaded into memory during a boot. (You can use theA DUMP_PRIORITY LOAD command at any time to load the contents of this file into memory.)? When you add an entry to the registry file, you must specify@ both the process name and UIC. If you attempt to add an entryB that already exists, the system displays the following me ssage:8 "SMI-I-SDPDUPIGN, duplicate record creation ignored." How Dump Priority Works@ BUGCHECK uses the loaded contents of the System Dump PriorityB registry to select priority processes to dump early on during aA selective dump. Adding a dump priority for a process increasesA the likelihood that the process will be included in a dump, ifB there is insufficient space for all processes. (The ADD commandD only adds an entry to the System Dump Priority registry permanent@ file. For BUGCHECK to be able to see the entry, you must also' enter a DUMP_PRIORITY LOAD command.)C BUGCHECK also keeps its own in-memory hardcoded list of priorityB processes, which are always treated as priority processes, evenA if the System Dump Priority registry is empty. These processes are the following: Process Name UIC MSCPmount [1,4] AUDIT_SERVER [1,4] NETACP [1,4] NET$ACP [1,3] REMACP [1,3] LES$ACP [1,4]< Note that you cannot see, change, or delete these default) processes with DUMP_PRIORITY commands.A If you enter a process into the System Dump Priority registry,B that process is dumped earlier, because user-specified priority@ processes are dumped before processes that are hardcoded into BUGCHECK.D Keep in mind that BUGCHECK keeps track of the processes that have3 been dumped, so that no process is dumped twice. Format: DUMP_PRIORITY ADD process-name /UIC=uic [/WILD_CARD] 5 Parameter process-nameC The exact name of the process. If the process name is mixed-caseB or includes spaces or any other nonstandard OpenVMS characters,C you must enclose it in double quotes; for example, "My Process".; You can use wildcard characters (* and %). Because these@ characters are valid characters in any process name, you mustD include the wildcard flag /WILD_CARD. Setting the /WILD_CARD flagD  for a specific process entry tells BUGCHECK to treat the asterisk* (*) and percent-sign (%) as wild cards. 5 Qualifiers /INFORMATIONAL /INFORMATIONAL (default) /NOINFORMATIONALC On Alpha and Integrity servers, allows you to control the outputA of informational messages, for example, in command procedures.B These qualifiers allow you to suppress or reinstate the display of informational messages.D Suppressing messages can also be useful when you are running in aB software installation environment and want to avoid the display< of informational messages. The default is /INFORMATIONAL. /UICB Specifies the UIC of the entry to add. You must enclose the UICC in brackets ([ ]). You can specify the /UIC with an octal numberC (for example, [377,377]) or in the identifier form (for example, [SYSTEM] or [VMS,USER]).$ Wildcards are allowed as follows: Wildcard Example DescriptionD /UIC = [*]  To select processes with the specified name in any UIC.D /UIC = To select processes with the specified name in the' [group,*] group called "group".@ /UIC = To select processes with the specified name in [100,*] group 100>.& NOTE@ You cannot use wildcards within identifier names or within@ UIC numbers. For example, /UIC=[USER*,*] or /UIC=[17*,100] are not allowed. /WILD_CARD  /WILD_CARD /NOWILD_CARDC Specifies whether or not wildcard characters in the process nameA are to be treated as wildcards. Note, however, that you cannot> add the same process name and UIC combination both with andC without the /WILD_CARD qualifier. If the combination has alreadyA been specified, use the DUMP_PRIORITY MODIFY command to change the wildcard setting.B The /WILD_CARD setting affects only the process name. Wildcards! are always allowed in the UIC. 5 Example6 SYSMAN> DUMP_PRIORITY ADD "MyPro*"/UIC=[*]/WILD_CARD SYSMAN> DUMP_PRIORITY LIST2 %SYSMAN-I-OUTPUT, command execution on node VMS73> Process name UIC Wild Card6 MyPro* [*] YB The first command in this example adds an entry to the SystemB Dump Priority registry. The process name is "MyPro*" with anyA UIC, and BUGCHECK will treat the asterisk (*) in MyPro* as a6 wildcard when the registry is loaded into memory.A BUGCHECK treats the UIC wildcard asterisk (*) as a wildcard,? even if you do not specify the /WILD_CARD qualifier on the command line.@ The Y under the Wild Card heading means that the /WILD_CARDD qualifier has been specified on the command line and a wildcard, has been specified in the process name. 2 LIST 3 and 4 IntegrityC On Alpha and Integrity servers, lists the contents of the System Dump Priority registry file. Format DUMP_PRIORITY LIST 5 Example SYSMAN> DUMP_PRIORITY LIST2 %SYSMAN-I-OUTPUT, command execution on node VMS73> Process name UIC Wild Card6 MSCPmount [SYSTEM] N6 NETACP [SYSTEM] N6 NET$ACP [1,3] N6 REMACP [1,3] N6 LES$ACP [SYSTEM]  N SYSMAN>C The command in this example produces a list of the contents ofB the System Dump Priority registry, including the process name@ and UIC of each entry. The list also shows N under the Wild@ Card heading, which indicates that BUGCHECK is to match the@ process name exactly during a crash. (However, N or Y underA Wild Card is important only if the the process name contains& one or more wildcard characters.) 2 LOAD 3 and  4 IntegrityC On Alpha and Integrity servers, loads the contents of the System? Dump Priority registry file into memory for BUGCHECK to use. Format DUMP_PRIORITY LOAD 5 Example SYSMAN> DUMP_PRIORITY SHOW3 %SMI-F-SDPNOTLOAD, System Dump Priority not loaded SYSMAN> DUMP_PRIORITY LOAD SYSMAN> DUMP_PRIORITY SHOW2 %SYSMAN-I-OUTPUT, command execution on node VMS73> Process name UIC Wild Card6 MSCPmount [SYSTEM] N6 NETACP [SYSTEM] N6 NET$ACP [00001,000003] N6 REMACP [00001,000003] N6 LES$ACP [SYSTEM] N SYSMAN>? The first command in the example displays the message that? the System Dump Priority registry file has not been loadedA into memory. The second command loads the registry file into? memory for BUGCHECK to use, and the third command displaysA the contents of the registry file that have been loaded into memory. 2 MODIFY 3 and 4 IntegrityB On Alpha and Integrity servers, modifies an entry in the System Dump Priority registry file. Format0 DUMP_PRIORITY MODIFY process-name /UIC=uic7 [/NEWUIC=newuic][/WILD_CARD] 5 Parameter process-nameC The exact name of the process. If the process name is mixed-caseB or includ es spaces or any other nonstandard OpenVMS characters,C you must enclose the process name in double quotes; for example,< "My Process". Also, when you enter a DUMP_PRIORITY MODIFY> command, be sure to enter the process name exactly as it isA displayed when you enter a DUMP_PRIORITY LIST command, becauseA the system searches for that process name to find the entry to modify.D If you attempt to modify an existing entry where the modification? can result in a duplicate, the system displays the followingA message: "SMI-I-SDPDUPIGN, duplicate record creation ignored."& The existing record is not removed. 5 Qualifiers /INFORMATIONAL /INFORMATIONAL (default) /NOINFORMATIONALC On Alpha and Integrity servers, allows you to control the outputA of informational messages, for example, in command procedures.B These qualifiers allow you to suppress or reinstate the display of informational messages.D Suppressing messages can also be useful when you are running in aB software installation environment and want to avoid the display< of informational messages. The default is /INFORMATIONAL. /UIC? Specifies the UIC of the entry in the registry that you want> to modify. The UIC and process name together make the entry@ unique. Specify the UIC as it is displayed when you enter the DUMP_PRIORITY LIST command. /NEWUICD Modifies the UIC of an entry that you specify by its process nameD and current UIC. You can specify the /NEWUIC with an octal numberC (for example, [377,377]) or in the identifier form (for example, [SYSTEM] or [VMS,USER]).$ Wildcards are allowed as follows: Wildcard Example DescriptionD /UIC = [*] To select processes with the specified name in any UIC.D /UIC = To select processes with the specified name in the' [group,*] group called "group".@ /UIC = To select processes with the specified name in [100,*] group 100>.& NOTE@ You cannot use wildcards within identifier names or within@ UIC numbers. For example, /UIC=[USER*,*] or /UIC=[17*,100] are not allowed. /WILD_CARD /WILD_CARD /NOWILD_CARD: The /WILD_CARD qualifier, used together with the MODIFYC command, modifies the wildcard setting on the entry that you areB modifying. If you omit /WILD_CARD, the current wildcard setting is retained. 5 Example SYSMAN> DUMP_PRIORITY LIST2 %SYSMAN-I-OUTPUT, command execution on node VMS73> Process name UIC Wild Card6 MSCP* [SYSTEM] Y6 NETACP [SYSTEM] N SYSMAN> DUMP_@PRIORITY MODIFY "MSCP*"/UIC=[SYSTEM]/NEWUIC=[TEST]/NOWILD_CARD 1 SYSMAN> DUMP_PRIORITY LIST2 %SYSMAN-I-OUTPUT, command execution on node VMS73> Process name UIC  Wild Card6 MSCP* [TEST] N6 NETACP [SYSTEM] N= SYSMAN> DUMP_PRIORITY MODIFY "MSCP*"/UIC=[TEST]/NEWUIC=[*] 2 SYSMAN> DUMP_PRIORITY LIST2 %SYSMAN-I-OUTPUT, command execution on node VMS73> Process name UIC Wild Card6 MSCP* [*] N6 NETACP [SYSTEM] N9 SYSMAN> DUMP_PRIORITY M ODIFY "MSCP*"/UIC=[*]/WILD_CARD 32 %SYSMAN-I-OUTPUT, command execution on node VMS73> Process name UIC Wild Card6 MSCP* [*] Y6 NETACP [SYSTEM] N@ Refer to the numbers at the end of the DUMP_PRIORITY MODIFYC command lines in the example, which correspond to the numbered? explanations that follow. (The DUMP_PRIORITY LIST command,; after each MODIFY command, di splays the results of the9 modifications in the System Dump Priority registry.)A 1 The first DUMP_PRIORITY MODIFY command modifies the MSCP*B entry with the current UIC [SYSTEM] the new UIC [TEST]. It@ also changes the /WILD_CARD flag to /NOWILD_CARD. If theA System Dump Priority registry is then loaded into memory,D BUGCHECK will not treat the asterisk (*) in the process nameC as a wildcard, but rather, will do an exact character match  of MSCP*.= 2 The second DUMP_PRIORITY MODIFY command modifies only@ the UIC of the entry to [*]. Omitting the /[NO]WILD_CARD; qualifier will leave the current setting unchanged.@ 3 The third DUMP_PRIORITY MODIFY command modifies only theD process name wildcarding flag with the /WILD_CARD qualifier. 2 REMOVE 3 IntegrityC On Alpha and Integrity servers, removes a record from the System Dump Priority registry file. Format0  DUMP_PRIORITY REMOVE process-name /UIC=uic 4 Parameter process-nameC The exact name of the process. If the process name is mixed-caseB or includes spaces or any other nonstandard OpenVMS characters,C you must enclose the process name in double quotes; for example, "My Process".B Also, when you enter a DUMP_PRIORITY REMOVE command, be sure toC enter the process name exactly as it is displayed when you enter@ a DUMP_PRIORITY LIST command, because the system searches for@ that process name to find the entry to remove. If you attempt> to remove a nonexistent entry from the System Dump Priority? registry, the system displays the following message: "SMI-I-> SDPRNOTREM, no record removed." When the system cannot find@ the entry to modify, it displays the following message: "SMI_: F_SDPRNOTFOUND, system dump priority record not found." 4 Qualifier /INFORMATIONAL /INFORMATIONAL (default) /NOINFORMATIONALC On Alpha and Integrity servers, allows you to control the outputA of informational messages, for example, in command procedures.B These qualifiers allow you to suppress or reinstate the display of informational messages.D Suppressing messages can also be useful when you are running in aB software installation environment and want to avoid the display< of informational messages. The default is /INFORMATIONAL. /UIC? Specifies the UIC of the entry in the registry that you want> to remove. The UIC and process name together make the entry@ unique. Specify the UIC as it is displayed when you enter the DUMP_PRIORITY LIST command. 4 Example SYSMAN> DUMP_PRIORITY LIST2 %SYSMAN-I-OUTPUT, command execution on node VMS73> Process name UIC Wild Card6 MSCPmount [SYSTEM] N6 NETACP [SYSTEM] N6 NET$ACP [1,3] N 6 REMACP [1,3] N6 LES$ACP [SYSTEM] N6 SYSMAN> DUMP_PRIORITY REMOVE "MSCPmount"/UIC=[SYSTEM] SYSMAN> DUMP_PRIORITY LIST2 %SYSMAN-I-OUTPUT, command execution on node VMS73> Process name UIC Wild Card6 NETACP [SYSTEM] N6 NET$ACP [1,3] N6 REMACP [1,3] N6 LES$ACP [SYSTEM] NA The DUMP_PRIORITY REMOVE command in this example removes theB entry MSCPmount with the UIC of [SYSTEM] from the System DumpD Priority registry file. (The process name MSCPmount is enclosed) in quotes because it is mixed-case.) 2 SHOW 3 and 4 Integrity@ On Alpha and Integrity servers, lists the contents of the in-9 memory copy of the System Dump Priority registry file. Format DUMP_PRIORITY SHOW 5 Example SYSMAN> DUMP_PRIORITY SHOW3 %SMI-F-SDPNOTLOAD, System Dump Priority not loaded SYSMAN> DUMP_PRIORITY LOAD SYSMAN> DUMP_PRIORITY SHOW2 %SYSMAN-I-OUTPUT, command execution on node VMS73> Process name UIC Wild Card6 MSCPmount [SYSTEM] N6 NETACP [SYSTEM] N6 NET$ACP [00001,000003] N6 REMACP [00001,000003] N6 LES$ACP [SYSTEM] N SYSMAN>C The first DUMP_PRIORITY SHOW command in the example results inB the display indicating that the System Dump Priority registryC file has not been loaded into memory. The second DUMP_PRIORITY@ SHOW command, which follows a LOAD command, displays an in- memory copy of the file. 2 UNLOAD 3 and 4 IntegrityC On Alpha and Integrity servers, clears the in-memory copy of the& System Dump Priority registry file. Format DUMP_PRIORITY UNLOAD 5 Example SYSMAN> DUMP_PRIORITY UNLOAD SYSMAN> DUMP_PRIORITY SHOW3 %SMI-F-SDPNOTLOAD, System Dump Priority not loaded@ Following a DUMP_PRIORITY UNLOAD command, the DUMP_PRIORITY? SHOW command in this example displays the message that theB System Dump Priority registry no longer has an in-memory copy of the file. ww@gK1 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 ww@gK1 IOC There are several SYSMAN IO subcommands. Select the one you want from the choices below. 2 AUTOCONFIGURE? This command is for use on Alpha and Integrity servers only.B It automatically identifies and configures all hardware devices? attached to a system by connecting devices and loading their drivers.8 On VAX systems, use the SYSGEN command AUTOCONFIGURE.B You must have CMKRNL and SYSLCK privileges to use the SYSMAN 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 See the Usage Notes under the /EXCLUDE qualifier for notes that apply to both qualifiers.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.6 Usage Notes for the /SELECT and /EXCLUDE QualifiersD o The /SELECT and /EXCLUDE qualifiers are not mutually exclusive> and yo u can specify both qualifiers on the command line.D o You can use the /SELECT and /EXCLUDE qualifiers to permanentlyC specify device autoconfiguration to include and exclude Fibre? Channel port driver devices (FG) and any SCSI port driverA devices (PK) for the duration of a manual autoconfiguration@ command. (To permanently specify devices to be excluded at? each system boot, use the SYSMAN command IO SET EXCLUDE.)C You cannot use the /SELECT and /EXCLUDE qualifiers to include4 and exclude any of the following device types:C - SCSI class-driver devices (DK, MK, GK) whose names include; a port allocation class or an HSZ allocation class8 - Fibre Channel class-driver devices (PG, DG, GG)D This restriction also applies to SCSI devices on OpenVMS AlphaB Version 7.1 systems, if the SCSI device names include a port allocation class. /LOG@ Controls whether the SYSMAN IO AUTOCONFIGURE command displays$ information about loaded devices. 3 DescriptionD The SYSMAN IO AUTOCONFIGURE command identifies and configures allA hardware devices attached to a system. It connects devices andB loads their drivers. You must have CMKRNL and SYSLCK privileges. to use the SYSMAN 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 CONNECTB This command is for use on Alpha and Integrity servers only. ItD connects a hardware device and loads its driver, if the driver is not already loaded.2 On VAX systems, use the SYSGEN command CONNECT.B You must have CMKRNL and SYSLCK privileges to use the SYSMAN IO CONNECT command. Format IO CONNECT device-name[:] 3 Parameter 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 Speci fies 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 signC extension is required for Alpha and Integrity servers 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 are loading.C If you do not specify this qualifier, SYSMAN obtains the defaultB in the same way that the SYSGEN default name is determined. ForB example, if you want to load the VSI-supplied SYS$ELDRIVER.EXE,B the prefix SYS$ must be present. Without the SYS$, SYSMAN looks? for ELDRIVER.EXE in SYS$LOADABLE_IMAGES. This implementationC separates the user device driver namespace from the VSI-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=(vecto r-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 vector 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 Description? The SYSMAN IO CONNECT command connects a hardware device andB  loads its driver, if the driver is not already loaded. You mustA have CMKRNL and SYSLCK privileges to use the SYSMAN IO CONNECT command.? The chapter "Managing Peripheral Devices" in the VSI 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 CR B 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 CSR 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 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 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.< For more information about loading and configuring deviceA drivers, see Writing OpenVMS Alpha Device Drivers in C (Margie; Sherlock and Leonard S. Szubowicz, Digital Press, 1996). 2 CREATE_WWIDC Assigns a specific, previously unused device name to a specific,C previously unused worldwide identifier (WWID) from the SYSMAN IO LIST_WWID display.D VSI recommends that you execute this command clusterwide and thatC you follow the command with a SYSMAN IO AUTOCONFIGURE command to! actually configure the device. Format3 IO CREATE_WWID devnam_string/WWID=wwid_string 3 Parameter devnam_stringA Specifies a device-name string. The string must be in the form& $2$MGAn, where n is less than 9999. 3 Qualifier /WWID  /WWID=wwid_string? Specifies a WWID string that comes directly from a SYSMAN IO LIST_WWID display. This qualifier is required. 3 Description< This command is an alternative to the SYSMAN IO FIND_WWID? command, which selects system-generated device names for theC discovered WWIDs. Do not, however, use the SYSMAN IO CREATE_WWIDA command after the SYSMAN IO FIND_WWID command to redefine WWIDD correlations. Also, do not specify device and WWID strings in theD SYSMAN IO CREATE_WWID command that are specified elsewhere in the cluster. 3 Example SYSMAN> SET ENVIRONMENT/CLUSTER SYSMAN> IO CREATE_7WWID $2$MGA5/WWID=04100022:"DEC TZ89 (C) DECCX939S2777"A SYSMAN> IO CREATE_WWID $2$MGA3/WWID=02000008:500E-09E0-0005-30D7 SYSMAN> IO AUTOCONFIGUREB The commands in this example create two device names, $2$MGA5, and $2$MGA3, and configure the devices. 2 FIND_WWIDB The SYSMAN IO FIND_WWID command probes all Fibre Ch annel ports,@ detects all previously undiscovered tapes and medium changersA behind a Network Storage Router (NSR) or a Modular Data Router@ (MDR), and assigns a worldwide identifier (WWID) to each one.< The command also displays a list of the devices and theirC assigned device names and automatically records 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.@ You must have CMKRNL privilege to use the SYSMAN IO FIND_WWID command.C For more information about Fibre Channel, see the Guidelines for" OpenVMS Cluster Configurations. Format IO FIND_WWID 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.A The SYSMAN IO FIND_WWID command probes all Fibre Channel portsA and locates all tape and medium changer devices. For tapes and> medium changers that have not been detected by any previousC SYSMAN IO FIND_WWID command, IO FIND_WWID assigns a device name,D retrieves the WWID of the device, stores the device name and WWIDB data in the SYS$SYSTEM:SYS$DE VICES.DAT file, and updates memory structures.B Because the main goal of SYSMAN IO FIND_WWID is to populate the? SYS$DEVICES.DAT file, you need to invoke the SYSMAN IO FIND_B WWID command only one time for each new device. Note that usingA the SYSMAN IO FIND_WWID command for the first time detects allA existing tape and medium changer devices on the system at that time.@ Once the information is stored in the file, subsequent use ofD the SYSMAN IO AUTOCONFIGURE comma nd reads the file and configures@ the tape and medium changer devices automatically, loading or? connecting the device drivers as needed. The SYS$DEVICES.DATC file is read during each system reboot, initiating the automaticC configuration of tapes and medium changers on the Fibre Channel.B (SYSMAN IO FIND_WWID does not load or connect the actual device drivers.)& NOTE< If you add more devices to the system at a later time,< you mu st powercycle the MDR to update internal mapping< information. You must also run the SYSMAN IO FIND_WWID? command again to append the new device information to the SYS$DEVICES.DAT file.B Similarly, for the Network Storage Router (NSR), the LUN map must be updated.@ In an OpenVMS cluster environment, you must run the SYSMAN IOB FIND_WWID command on each node in the cluster to update various? data structures in memory. Alternatively, you can run SYSMANA IO FIND_WWID on one node, and then reboot the other nodes thatC share that same system disk, because the SYS$DEVICES.DAT file isA read at boot 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 SYSMAN IO FIND_WWID command on all@ nodes. Alternatively, you can run IO FIND_WWID to update justA 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.C VSI recommends that you refrain from copying the entire original@ file to another system disk, because the SYS$DEVICES.DAT fileB is also used to define Port Allocation Classes, and PAC entries; could be inadvertently transferred to the target system. 3 Example SYSMAN> IO FIND_WWID3 %SYSMAN-I-OUTPUT, command execution on node SAMPLEC On port _SAMPLE$PGA0:, the following tape WWIDs and their proposed5 device names have been found but not yet configured: [Device $2$GGA0]; WWID=04100024:"DEC TL800 (C) DEC3G9CCR82A017" [Device $2$MGA0]9 WWID=04100022:"DEC TZ89 (C) DECCX939S2777" [Device $2$MGA1]9 WWID=04100022:"DEC TZ89 (C) DECCX942S6295"D This is a configuration example using a TL891 tape library. T heB 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.: The SYSMAN IO FIND_WWID command automatically records2 the information about the new tape devices in SYS$SYSTEM:SYS$DEVICES.DAT:( $ TYPE SYS$SYSTEM:SYS$DEVICES.DAT !4 ! Updated 23-OCT-2002 14:17:41.85: DEC TL800 ! [Device $2$GGA0]; WWID=04100024:"DEC TL800 (C) DEC3G9CCR82A017" ! !3 ! Updated 23-OCT-2002 14:17:41.93: DEC TZ89 ! [Device $2$MGA0]9 WWID=04100022:"DEC TZ89 (C) DECCX939S2777" ! !3 ! Updated 23-OCT-2002 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 LIST_WWID@ Applies only to tape devices on Fibre Channel. Lists all tape= device WWIDs that are not yet configured on Fibre Channel.C You can use the output of this command as input to the SYSMAN IO3 CREATE_WWID and SYSMAN IO REPLACE_WWID commands. Format IO LIST_WWID 3 Example SYSMAN> IO LIST_WWID2 %SYSMAN-I-OUTPUT, command execution on node ROCKY On port _=ROCKY$PGA0:, the following tape WWIDs are not yet configured:$ Target 3, LUN 1, COMPAQ SuperDLT1" WWID=02000008:500E-09E0-0005-30D7# Target 3, LUN 3, COMPAQ SDX-500C" WWID=0C000008:0800-4606-C00D-473F$ Target 4, LUN 1, COMPAQ SuperDLT1" WWID=02000008:500E-09E0-0005-30D7# Target 4, LUN 3, COMPAQ SDX-500C" WWID=0C000008:0800-4606-C00D-473FA In this example, each drive is listed twice because the tape@ bridge is dual-ported, with one FC port at target 3 and the other FC port at target 4. 2 LOADB This command is for use on Alpha and Integrity servers only. It loads an I/O driver.B You must have CMKRNL and SYSLCK privileges to use the SYSMAN IO LOAD command.& NOTE; Be very careful when issuing a SYSMAN IO LOAD command4 because the system does little error-checking. Format IO LOAD filespec 3 Parameter filespec; Specifies the file name of the driver to be loaded. This parameter is required. 3 Qualifier /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 SYSMAN IO LOAD command loads an I/O driver. You must haveB CMKRNL and SYSLCK privileges to use the SYSMAN 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 REBUILDB This command is for use on Alpha and Integrity servers only. ItD rebuilds device configuration tables in preparation for using the= SYSMAN IO AUTOCONFIGURE command to reconfigure the system. Format IO REBUILD 3 Qualifier /VERIFYC Causes SYSMAN to read and process the files SYS$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 Description6 The SYSMAN IO REBUILD command rebuilds the system's9 device configuration 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.DAT8 file, you can use the SYSMAN IO REBUILD and SYSMAN IOC AUTOCONFIGURE commands to load drivers without having to reboot.D Once you load a driver for 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 configuration8 tables and loads drivers for newly defined drivers. 2 REPLACE_WWID@ This command allows a user to replace one tape drive behind aC Network Stora ge Router (NSR) with another tape drive at the same9 Fibre Channel (FC) Logical Unit Number (LUN) location.> This command updates all the necessary file and memory dataB structures with the WWID of the new tape drive. The name of theA replacement drive will be the same as the name of the original drive.@ This command is primarily intended to be used when a hardware? problem occurs on a tape drive, and a replacement drive must installed in its place.? The command requires CMKRNL privilege. It applies only to FCA tapes behind a Fibre Channel tape bridge such as an NSR or MDR (Modular Data Router).C For more information about Fibre Channel, see the Guidelines for" OpenVMS Cluster Configurations. Format4 IO REPLACE_WWID devnam_string/WWID=wwid_string 3 Parameter devnam_string Specifies a tape device name. 3 Qualifier /WWID /WWID=wwid_stringD Specifies a string that comes direc tly from a SYSMAN IO LIST_WWIDC display. The use of this qualifier is appropriate only under the4 circumstances explained in the description below. 3 DescriptionA You can use the two parameters, devnam_string and wwid_string,@ with the REPLACE_WWID command to replace a broken tape device@ with a new device. The command automatically updates the dataB structures that record the new devnam-WWID correlation, and the5 device automatically begins to function correctly.1 This command is useful in two different cases:= o In one case, the drive might malfunction and need to be@ replaced immediately without rebooting the system. If thisA happens, the drive is physically replaced with a new drive,> and the command SYSMAN IO REPLACE_WWID $2$MGAn is issuedA clusterwide. The /WWID qualifier is not appropriate in this@ case, because the new WWID is automatically detected using9 information stored in the device's data structures. < o In the other case, the drive might malfunction and not> be replaced until after the system has been shut down orD rebooted. The device name no longer appears in the SHOW DEVICE? display because the device failed to configure during the reboot.; The configuration failure occurred either because the@ broken drive did not respond, or because the new drive hasD a different WWID from the one SYSMAN IO AUTOCONFIGURE expected> at boot time. Therefore, in this situation, in which theB device name is in SYS$DEVICES.DAT but not in the SHOW DEVICED display, use the /WWID qualifier to define the new devnam-WWID correlation.% Follow these steps clusterwide:C 1. Execute the SYSMAN IO LIST_WWID command to display the new WWID.A 2. Use the command SYSMAN IO REPLACE_WWID $2$MGAn/WWID=new_, wwid to define the new correlation.A 3. Use the SYSMAN IO AUTOCONFIGURE command to configure the device.C When you use the SYSMAN IO LIST_WWID command, keep in mind that:D o You must set the replacement device to the same SCSI target ID as the original device.A o You must stop all activity on the device before issuing the% SYSMAN IO REPLACE_WWID command.B o The command requires CMKRNL privilege and applies only to FC! tapes behind an NSR or MDR. 3 Example SYSMAN> SET ENVIRONMENT/CLUSTERB SYSMAN> IO REPLACE_WWID $2$MGA3/W WID=02000008:500E-09E0-0005-30D7 SYSMAN> IO AUTOCONFIGURE@ In this example, the device named $2$MGA3 malfunctioned andC was replaced while the system was down. Upon reboot, the driveC did not get configured, because its new WWID did not match theB WWID that OpenVMS expected. Therefore, the user redefines theB devnam-WWID correlation and is then able to configure $2$MGA3? correctly. The specified WWID comes from the output of the! SYSMAN IO LIST_WWID command. 2 SCSI_PATH_VERIFYD This command is for use on Alpha and Integrity servers only. ThisB command checks each SCSI and FC path in the system to determineC whether the attached device has been changed. If a device change? is detected, then the SCSI or FC path is disconnected in theB IO database. This allows the path to be reconfigured on the new8 device, by using the SYSMAN IO AUTOCONFIGURE command. Format IO SCSI_PATH_VERIFY 3 Description; You usually enter the SYSMAN 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 deviceC does not match the data stored in the IO database, then the pathB is disconnected in the IO database. Following a SYSMAN IO SCSI_C PATH_VERIFY command, you usually enter a SYSMAN IO AUTOCONFIGUREB 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 EXCLUDEB This command is for use on Alpha and Integrity servers only. It@ sets the permanent exclusion list to be used when configuring devices automatically.A The exclusion list can be cleared by entering an empty string. Format" IO SET EXCLUDE = device_name 4 Parameter 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 configuri ng devices.9 You can use this command to permanently specify deviceA autoconfiguration to exclude Fibre Channel port driver devicesB (FG) and any SCSI port driver devices (PK) at each system boot.D (To specify permanently the exclusion or inclusion of devices forC the duration of a manual configuration command, use the /EXCLUDEB or /SELECT qualifier with the SYSMAN IO AUTOCONFIGURE command.)B You cannot use the SYSMAN IO SET EXCLUDE command to exclude any! of the following device types:B o SCSI class-driver devices (DK, MK, GK) whose names include a6 port allocation class or an HSZ allocation class5 o Fibre Channel class-driver devices (PG, DG, GG)A This restriction also applies to SCSI devices on OpenVMS Alpha? Version 7.1 systems, if the SCSI device names include a port allocation class. 4 Examples) 1.SYSMAN> IO SET EXCLUDE=(DKC500,DKD*)C This example specifies that DKC500 and all DKD devices are not  to be autoconfigured.C For additional examples that show how to specify device names,< see the /SELECT qualifier available with the SYSMAN IO  AUTOCONFIGURE command. ! 2.SYSMAN> IO SET EXCLUDE=(" "), This example clears the exclusion list. 3 PREFIX? This command is for use on Alpha and Integrity servers only.@ It sets the prefix list that is used to manufacture the IOGEN. Configuration Building Module (ICBM) names. Format IO SET PREFIX =icbm_prefix 4 Parameter icbm_prefixD Specifies ICBM prefixes. These prefixes are used by the SYSMAN IO3 AUTOCONFIGURE command to build ICBM image names. 4 DescriptionA The SYSMAN IO SET PREFIX command sets the prefix list which is" used to manufacture ICBM names. 4 Example' SYSMAN> IO SET PREFIX=(SYS$,PSI$,VME_)> This example specifies the prefix names used by SYSMAN IOB AUTOCONFIGURE to build the ICBM names. The prefixes are SYS$, PSI$, and VME_. 2 SHOW 3 BUSB This command is for use on Alpha and Integrity servers only. It@ lists all the buses, node numbers, bus names, TR numbers, andB 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 DescriptionD The SYSMAN IO SHOW BUS command lists all the buses, node numbers,> bus names, TR numbers, and base CSR addresses. This displayC  exists primarily for internal engineering support. You must have. CMKRNL privilege to use SYSMAN 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 FFFFFFFF86FD00008 XZA XMI-SCSI 0 3 XZA-SCSI 000000800188 00008 XZA XMI-SCSI 1 3 XZA-SCSI 00000080018800008 XZA XMI-SCSI 0 4 XZA-SCSI 00000080019000008 XZA XMI-SCSI 1 4 XZA-SCSI 00000080019000008 XMI 4 2 LAMB 0000008001A000008 DEMNA 0 5 Generic XMI 0000008001E800008 DEMNA 0 6 Generic XMI 0000008001F00000C This example is from a DEC 7000 Model 600. Displays vary among+ different Alpha and Integrity servers.@ 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 and Integrity servers, you can use the SDA commandC CLUE CONFIG to display additional information including hardwareB adapters and devices. This command is documented in the OpenVMS- Alpha System Dump Analyzer Utility Manual.D For more information about loading and configuing device drivers,1 see Writing OpenVMS Alpha Device Drivers in C. 3 DEVICE? This command is for use on Alpha and Integrity servers only.? It displays information about device drivers loaded into theB system, the devices connected to them, and their I/O databases.4 All addresses are in hexadecimal and are virtual.6 On VAX systems, use the SYSGEN command SHOW/DEVICE. Format IO SHOW DEVICE 4 DescriptionC The SYSMAN IO SHOW DEVICE command displays information about theB device drivers loaded into the system, the devices connected to! them, and their I/O databases.A The SYSMAN IO SHOW DEVICE command specifies that the following> information 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.? For additional information about SYSMAN, see A Comparison ofB System Management on OpenVMS AXP and OpenVMS VAX (archived) butE available on the OpenVMS Documentation CD-ROM) and the VSI OpenVMS System Manager's Manual. 4 Example SYSMAN> IO SHOW DEVICE> The following example is a sample display produced by the# SYSMAN 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 EXCLUDE9 This command is for use on Alpha and Integrity servers= only. It displays the permanent exclusion list used in the autoconfiguration of devices. Format IO SHOW EXCLUDE 4 Description< The SYSMAN 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 PREFIXB This command is for use on Alpha and Integrity servers only. ItC displays the current prefix list used in the manufacture of ICBM names. Format IO SHOW PREFIX 4 Description@ The SYSMAN IO SHOW PREFIX command displays the current prefix: list on the console. This list is used by the SYSMAN IO- AUTOCONFIGURE command to build ICBM names. 4 Example SYSMAN> IO SHOW PREFIX? %SYSMAN-I-IOPREFIX, the current prefix list is: SYS$,PSI$,VME_D This example shows the prefixes used by SYSMAN IO AUTOCONFIGURE to build ICBM names. ww=BgK 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 that owns the product for which@ you have a license. Use this qualifier only if the product is! from a company other than VSI. 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 information@ about the LMF, see the VSI OpenVMS License Management Utility Manual. 3 Example SYSMAN> LICENSE LOAD FORTRAND This example activates the license for VSI Fortran for OpenVMS.C Because the license is for a VSI product, the 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 VSI. 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 information@ about the LMF, see the VSI OpenVMS License Management Utility Manual. 3 Example SYSMAN> LICENSE UNLOAD FORTRAN= This command deactivates the license for VSI Fortran forC OpenVMS. Because the license is for a VSI product, the command. does not include the /PRODUCER qualifier. wwdBgK 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.& NOTEC Range checks are enabled by default because VSI suggests that> systems operate within these minimum and maximum values.B 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 Qualifier /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.C Beginning in OpenVMS Version 8.2, if the parameter-name that youC enter is obsolete, SYSMAN displays OBSOLETE in the Units column. 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 paramet!ers. /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. /OBSOLETE8 Displays the names of all obsolete system parameters. /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 para meters. /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. Ambiguity B 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. 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 read 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. Us ing the current parameters requires read (R)1 access to the system parameters file.? o On Alpha systems, the file that contains current8 parameters is SYS$SYSTEM:ALPHAVMSSYS.PAR.C o On Integrity servers, the file that contains current7 parameters is SYS$SYSTEM:IA64VMSSYS.PAR.< filespec Read parameters from a previously created systemC parameter file. The default file type is .PAR. You need$ read a ccess 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 parameter 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.C o On Integrity servers, the file that contains current7 parameters is SYS$SYSTEM:IA64VMSSYS.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).B!*****************************************************************wwЋBgK1 Sys_Parameters; Help is provided for the system parameters listed below. 2 ACP_BASEPRIOD ACP_BASEPRIO sets the base priority for all ACPs. The DCL commandC SET PROCESS/PRIORITY can be used to reset the base priorities of< individual ACPs. ACP_BASEPRIO is not applicable 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 re ad operations.? When this bit is set, the IO$M_DATACHECK functionB modifier is automatically set on all subsequent IO$_E READLBLK operations that read file system metadata (see7 the OpenVMS I/O User's Reference Manual).A 1 Set this bit to perform consistency checks on write operations.? When this bit is set, the IO$M_DATACHECK functionB modifier is automatically se t on all subsequent IO$_A WRITELBLK operations that read file system metadata< (see the OpenVMS I/O User's Reference Manual).B 2 Set this bit to perform read-after-write consistency checks.C This is similar to setting bit 1, except that in thisA case the file system does the checks, not the lower* level device or disk driver.C Note that read-after-write consistency checks are notD  allowed on deferred writes. Deferred writes are turned% off if this bit is set.6 3 reserved for VSI use only; must be zero.6 4 reserved for VSI use only; must be zero.E 5 and 6 These two bits control the checks that are performed onB reads and writes of directory blocks. You can select+ one of four different levels:2 By7 Select SettingC This Bit 6 And Bit 5? To Check That... Level... to... to...; The block is a valid 0 0 0 directory block (reads only); The block is a valid 1 0 1 directory block (reads and writes); The block is a valid 2 1 0 directory block  and contains valid entries (reads and writes); The block is a valid 3 1 1 directory block and contains valid entries in correct alphanumeric order (reads and writes)B When you set the SYSTEM_CHECK system parameter to 1,> you enable level 3 checking of directory blocks.D Write errors result in BUGCHECK and crash your system;B read errors exit with error status SS$_BADDIRECTORY.6 7 reserved for VSI use only; must be zero. 2 ACP_DINDXCACHE@ ACP_DINDXCACHE controls the size of the directory index cache= and the number of buffers used on a cachewide basis. Also,= ACP_DINDXCACHE builds a temporary index into the directoryA file, thereby reducing search time and directory header lookup operations.A ACP_DINDXCACHE is an AUTOGEN, DYNAMIC, and FEEDBACK parameter. 2 ACP_DIRCACHE> ACP_DIRCACHE sets the number of pages for caching 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 specification of 0 means no cache. Too small a value causes? excessive XQP I/O operations, while too large a value causes@ excessive physical memory to be consumed by the extent cache.4 ACP_EXTCACHE is a DYNAMIC and FEEDBACK parameter. 2 ACP_EXTLIMIT= ACP_EXTLIMIT specifies the maximum amount of 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 over ridden on an6 individual-volume basis with the DCL command MOUNT.4 ACP_MULTIPLE is an AUTOGEN and DYNAMIC parameter. 2 ACP_QUOCACHE? ACP_QUOCACHE sets the number of quota file entries cached. A> specification of 0 means no cache. Too small a value causes? excessive XQP I/O operations, while too large a value causes@ excessive physical memory to be consumed by the quota caches.? ACP_QUOCACHE is an AUTOGEN, DYNAMIC, and FEEDBACK parameter. 2 ACP_REBLDSYSDD ! ACP_REBLDSYSD specifies whether the system disk should be rebuiltC if it was improperly dismounted with extent caching, file numberD caching, or disk quota caching enabled. The ACP_REBLDSYSD defaultB value (1) ensures that the system disk is rebuilt. Setting the, value to 0 means the disk is not rebuilt.; Depending on the amount of caching enabled on the volume@ before it was dismounted, the rebuild operation may consume aB considerable amount of time. Setting the value of A"CP_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 decimal $A 14 disables swap for ACPs for volumes mounted with the /SYSTEMB qualifier but leaves swap enabled for all other ACPs. Note thatD one has only disk ACPs present if they are specifically requestedC at mount time or if a Files-11 On-Disk Structure Level 1 disk isD mounted. In general, only bit 3 is significant because 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 bl %ocks< (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 concurre &ntly on each system volume. It might be@ overridden on a per-volume basis with the /ACCESSED qualifierD to the DCL command MOUNT. The value should be kept low in systems? with small physical memory and little file activity, becauseA the FCBs require a significant amount of space in the nonpaged dynamic pool.C Too small a value causes excessive XQP I/O operations, while tooC large a value causes excessive physical memory to be consumed by the FCB caches.2 ACP_SYSAC'C 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_WRITEBACKD ACP_WRITEBACK is a dynamic system parameter that controls whetherD deferred writes to file headers are enabled. The default value isC 1, which enables deferred writes to file headers. To disable the# feature, set ACP_)WRITEBACK to 0.A This system parameter affects only applications like PATHWORKS> that can request deferred writes to file headers. Note that@ the deferred write feature is not available on Files-11 ODS-1 volumes.( ACP_WRITEBACK is a DYNAMIC parameter. 2 ACP_XQP_RES? ACP_XQP_RES controls whether the XQP is currently in memory.A The default value (1) specifies that the XQP is permanently in? memory. Change the default only on restricted memory systemsC with *a small number of users and little or no file activity that@ requires XQP intervention. Such 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.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 AFF +INITY_TIME@ AFFINITY_TIME controls the breaking of implicit affinity. TheC value indicates how long a process remains on the compute queue.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 ALLOCLASSC ALLOCLASS determines the device allocation class for the system.> The device allocation class is used to derive a common lock> resource name for multiple access paths to the same device. , 2 ARB_SUPPORT> (Alpha and Integrity servers) The Access Rights Block (ARB)= compatibility option, the ARB_SUPPORT system parameter, isC provided specifically to support products that have not yet beenD updated to use the new per-thread security Persona Security BlockA (PSB) data structure instead of the ARB. Changing the value of? ARB_SUPPORT from 2 or 3 (the default) to any other value can* affect the operation of these products.& NO-TE< VSI recommends that all Version 7.3-1 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 BehaviorD ISS$C_ARB_NONE 0 The obsolete kernel data cells are notB . maintained by the system. Fields areD initialized to zero (or set to invalid< pointers) at process creation.@ ISS$C_ARB_CLEAR 1 The obsolete kernel data cells areB cleared (or set to invalid pointers)D when the code would have set up values9 for backward compatibility.A ISS$C_ARB_READ_ 2 The obsole/te cells are updated with@ ONLY corresponding security information> stored in the current PSB when a8 $PERSONA_ASSUME is issued.C ISS$C_ARB_FULL 3 (de- Data is moved from the obsolete cells@ fault) to the currently active PSB on any7 security-based operation.& ARB_SUPPORT is a DYNAMIC parameter. 2 AUTO_DLIGHT_SAV= AUTO_DLIGHT_SAV is set 0to 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 AWSMIN@ On Alpha and Integrity servers, AWSMIN establishes the lowestC number of pagelets to which a working set limit can be decreased. by automatic adjustment of the working set.! AWSMIN is a DYNAMIC parameter. 2 AWSTIME> AWSTIME specifies the minimum amount of processor time that@ must elapse for the system 1to collect a significant sample ofB a working set's page fault rate. The time is expressed in unitsA of 10 milliseconds. The default value of 5, for example, is 50 milliseconds.> Some application configurations that have a large number ofB memory-intensive processes may benefit if the value is reduced. The value can be as low as 4.B AWSTIME expiration is checked only at quantum end. Reducing its? value and not reducing QUANTUM effectively sets the value of) AWSTIME e2qual to the value of QUANTUM." AWSTIME is a DYNAMIC parameter. 2 BALSETCNTD BALSETCNT sets the number of balance set slots in the system pageC table. Each memory-resident working set requires one balance set slot.> You can monitor the active system with the DCL command SHOWD MEMORY or the MONITOR PROCESSES command of the Monitor utility toD determine the actual maximum number of working sets in memory. IfB this number is significantly lower than the value of BALS 3ETCNT,B this parameter value could be lowered. If all balance set slots0 are being used, raise the value of BALSETCNT.9 Never set BALSETCNT to a value higher than 2 less than< MAXPROCESSCNT. If physical memory is a significant systemB constraint, consider lowering this value even further. However,A if your system runs with a number of processes nearly equal toD MAXPROCESSCNT, lowering BALSETCNT forces swapping to occur, which! can affect system performance.; BALSETCNT 4 is no longer a strict setting of the number of@ processes that might be resident in memory. The swapper tries@ to reduce the number of resident processes down to BALSETCNT.A However, if the total number of active processes and processesB that have disabled swapping exceeds BALSETCNT, the swapper does? not force processes out of memory just to meet the BALSETCNT setting.> BALSETCNT is an AUTOGEN, GEN, DYNAMIC, and MAJOR parameter. 2 BORROWLIM@ BORROWLIM defines t 5he 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 6the values of parameters WSINC, PFRATH, and AWSTIME.C Working set growth attempts to alleviate heavy page faulting. ToA make use of this growth, you must also set the user's WSEXTENTA authorization quota to a larger number than the WSQUOTA value.8 BORROWLIM is an AUTOGEN, DYNAMIC and MAJOR parameter. 2 BREAKPOINTS? If XDELTA is loaded, BREAKPOINTS enables additional built-inB calls for XDELTA during the boot sequence. The breakpoints that= are enabled may change fr7om release to release of OpenVMS.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so.& BREAKPOINTS is a DYNAMIC parameter. 2 BUGCHECKFATAL? BUGCHECKFATAL enables or disables the conversion of nonfatalC bugchecks into fatal bugchecks. The system must be rebooted on aB fatal bugcheck. A nonfatal bugcheck places an entry only in the3 error log and deletes the corresponding process.C T8his 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 i9s a DYNAMIC parameter. 2 CHANNELCNTD CHANNELCNT specifies the maximum number of I/O channels available> to processes and to the system. The FILLM quota can be used@ to reduce the maximum number of I/O channels for a process. AD process with a FILLM quota larger than CHANNELCNT is nevertheless= limited to the maximum number of I/O channels specified by CHANNELCNT. 2 CLASS_PROT: CLASS_PROT performs the nondiscretionary classification> checks. CLASS_PROT is als:o 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 symbols that can be created.$ CLISYMTBL is a DYNAMIC parameter. 2 CLUSTER_CREDITSC CLUSTER_CREDITS specifies the number of per-connection buffers a= node allocates to receiving VMS$VAXcluster communic ;ations.? 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.C It is not required for <all nodes in the cluster to have the same value for CLUSTER_CREDITS.> The default value is currently 32. Unless a system has veryA constrained memory available, VSI recommends that these values not be increased. 2 CONCEAL_DEVICESD CONCEAL_DEVICES enables or disables the use of concealed devices.@ By default, this parameter is set to enable concealed devices (1).D This special parameter is use by VSI and is subject to change. DoB not change this parameter u =nless VSI recommends that you do so. 2 CPU_POWER_MGMT_(D)@ On Integrity servers, a CPU can be placed in "low-power mode"= when it is idle. This minimizes power consumption, therebyB reducing energy costs for the system. Beginning in Version 8.2-B 1, OpenVMS Integrity servers supports this feature based on theC settings of two system parameters: CPU_POWER_MGMT and CPU_POWER_ THRSH.B A value of 1 for CPU_POWER_MGMT means on (the default); a valueB of 0 means off. W >henever the CPU_POWER_THRSH parameter value isB exceeded, the operating system places an Integrity processor inD low-power mode if it is idle. OpenVMS Integrity servers does thisC only if CPU_POWER_MGMT is on. A CPU returns to normal power when it receives an interrupt.) CPU_POWER_MGMT is a DYNAMIC parameter. 2 CPU_POWER_THRSH_(D)A On Integrity servers, CPU_POWER_THRSH is a parameter expressedA as a percentage. OpenVMS Integrity servers monitors how active@ each ?CPU is over a fixed time period. If CPU_POWER_MGMT is onA and a CPU is idle for a period of time indicated by CPU_POWER_D THRSH, the CPU is placed in a low-power mode if it is idle. A CPU9 returns to normal power when it receives an interrupt.A For systems supporting real-time operations that require quickE response time, VSI recommends that this feature be turned off. UseA of this feature can result in a small performance degradation.B For more information, see the Intel@ IA-64 Architecture Software; Developer's Manual, Volume 2: IA-64 System Architecture.) See also the CPU_POWER_MGMT parameter.* CPU_POWER_THRSH is a DYNAMIC parameter. 2 CRD_CONTROLA This special parameter is use by VSI and is subject to change.E Do not change this parameter unless VSI recommends that you do so.D On Alpha and Integrity servers, CRD_CONTROL can be used to expand% the function defined by CRDENABLE.? CRD_CONTROL is a bit mask for corrected read Adata (CRD) soft? error control flags. These flags control the use of CRDERROR routines.B On Alpha and Integrity servers, the following bits are defined: Bit Description1 0 Enables CRD processing for all systems.C 1 Enables scrubbing (rewriting) of the memory location that induced the CRD.< 2 Enables page replacement of the pages that exhibit repeated CRD errors.; 3 Forces all memory pages to be included in the PFN BC 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 firmCware support are available." 6 Disables CRD throttling.2 7 Disables System Event Log (SEL) polling.@ 16-31 Reserved for platform-specific error-handling control.C On Alpha and Integrity servers, the default setting is 22, whichB enables scrubbing, page replacement, and extended CRD handling. 2 CRDENABLE> (Alpha and Integrity servers) CRDENABLE enables or disablesD detection and logging of memory-corrected read data (ECC) errors.0 This paraDmeter should normally be set to (1).A Beginning with OpenVMS Version 7.2, CRD_CONTROL can expand the, function of CRDENABLE. (See CRD_CONTROL.) 2 CTLIMGLIMA CTLIMGLIM specifies the size of the default image I/O segment;B that is channel table and initial buffer pool for image-related file and RMS I/O.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 CTLPAGESD CTLPAGES spEecifies the size of P1 pool. CTLPAGES is automaticallyD changed only when the process logical name table, DCL symbols, orB some layered products require an increase in the size of the P1 pool area.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so.$ CTLPAGES is an AUTOGEN parameter. 2 CWCREPRC_ENABLEC CWCREPRC_ENABLE controls whether an unprivileged user can createD a process on anot Fher OpenVMS Cluster node. The default value of 1D allows an unprivileged user to create a detached process with theC same UIC on another node. A value of 0 requires that a user haveB DETACH or CMKRNL privilege to create a process on another node. 2 DBGTK_SCRATCHA (Alpha and Integrity servers) DBGTK_SCRATCH specifies how many> pages of memory are allocated for the remote debugger. ThisC memory is allocated only if remote debugging is enabled with theB 8000 boot flag. Nor Gmally, the default value is adequate, but ifC the remote debugger issues an error message, you should increaseD this value. See Writing OpenVMS Alpha Device Drivers in C (MargieB Sherlock and Lenny S. Szubowicz, Digital Press, 1996). for more0 information. (This manual has been archived.) 2 DCL_CTLFLAGS> DCL_CTLFLAGS is a bit mask that alters default behavior for@ certain DCL-related functions on a systemwide basis. However,8 the default values satisfy the needs of most Hsystems.C Bits 0 and 2 control the formulation of system-generated processC names for processes created using the SPAWN command or LIB$SPAWN< library routine. They are provided for compatibility withB behavior of prior OpenVMS versions. Note that you can eliminateB the use of system-generated names by supplying your own process names.- Bit 1 controls the token size used by DCL.@ Bit 3 controls the maximum number input parameters to command procedure.D Bit 4I controls the the maximum length for an user name, for which* OpenVMS mail forwarding address is set.: DCL_CTLFLAGS bits are described in the following table. Bit DescriptionA Bit If clear (the default), the numeric portion of a system-A 0 generated spawned process name is generated randomly. IfD set, the numeric portion is generated sequentially starting with sequence number 1.< The option of sequential generation is provided for= J compatibility with OpenVMS versions prior to Version= 7.3-1. However, this choice can be very expensive in? performance terms because of the mechanism for findingD the next available process name. This mechanism attempts toB create all process names beginning with sequence number 1+ until it finds one that is unused.= Random generation is the preferred choice because it? results in a very high probability of finding a unique K name on the first try.; Bit Controls the token size used by DCL. If clear (the@ 1 default), this bit instructs DCL to use the traditionalB token size. A token cannot exceed 255 characters. If thisB bit is set, extended tokens are used. Extended tokens are 4000 characters.7 Note that if you turn on extended tokens, file> specifications can exceed 255 characters, which mightC require larger structures for parsing file specif Lications.A Bit If clear (the default), the numeric portion of a system-> 2 generated spawned process name has a maximum value of= 65535. If set, the numeric portion of the name has a maximum value of 255.7 The option of a maximum of 255 is provided forB compatibility with OpenVMS versions prior to Version 8.3,D when it was the only choice. The larger maximum allows many? more unique spawned process names for a given process. M> For this reason, it is the preferred choice. However,? the larger maximum uses two additional characters from@ the process name, which might make it more difficult toD identify users uniquely by looking at their spawned processA names. If this is an issue on your system, setting bit 2" might be a better choice.? Bit If clear (the default), command procedure supports theD 3 default eight optional parameters (that is, (P1,P2,...P N8)).B If set, command procedure supports up to sixteen optional; parameters (that is, (P1,P2,...P16)). This is alsoC applicable when using the CALL command to transfer control to a subroutine.C Bit This bit controls the the maximum length for an user name,C 4 for which OpenVMS mail forwarding address is set. If clearC (the default), user name string length is set to a maximumD length of 31 characters. If set, user name string O length is, set to a maximum of 255 characters.? Note: Once this bit is set, user name length is set to@ maximum of 255 characters. Even if this bit is cleared,D the behavior remains unchanged, that is, supports user nameB length of 255 characters, but there is no way to reset it to 31 characters. 2 DEADLOCK_WAITB DEADLOCK_WAIT defines the number of seconds that a lock requestD must wait before the system initiates a deadlock sear Pch on behalf@ of that lock. Setting DEADLOCK_WAIT to zero disables deadlock? checking. Setting DEADLOCK_WAIT to a value greater than zeroA and less than the default setting provides faster detection of) deadlocks but requires more CPU usage.B The DEADLOCK_WAIT value is expressed in seconds; therefore, theC smallest value you can set is 1 second. Beginning in VSI OpenVMS? Version 8.3, a subsecond deadlock wait time, which is set inB the system service $SET_PROCESS_PROPERTQIESW item code $PPROP$C_D DEADLOCK_WAIT, overrides DEADLOCK_WAIT. For more information, seeD the $SET_PROCESS_PROPERTIESW system service in VSI OpenVMS System Services Reference Manual.( DEADLOCK_WAIT is a DYNAMIC parameter. 2 DEFGID0 Default POSIX GID used internally by OpenVMS. 2 DEFMBXBUFQUOB DEFMBXBUFQUO sets the default for the mailbox buffer quota size@ in bytes when this value is not specified in a Create Mailbox! ($CREMBX) system service call.'R 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 (prSinter, 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 DEFUID0 Default POSIX UID useTd internally by OpenVMS. 2 DELPRC_EXITD DELPRC_EXIT can be used to control $DELPRC system service optionsC that call exit handlers prior to final cleanup and deletion of a8 process. The following table describes these options: Option Description= 0 Disable the exit handler functionality with $DELPRC.4 4 Execute kernel mode exit handlers.< 5 (default) Execute exec and more privileged mode exit U handlers.B 6 Execute supervisor and more privileged mode exit handlers.< 7 Execute user and more privileged mode exit handlers.& DELPRC_EXIT is a DYNAMIC parameter. 2 DEVICE_NAMING< (Alpha and Integrity servers) DEVICE_NAMING is a bit maskA indicating whether port allocation classes are used in forming SCSI device names.# Following is the bit definition: Bit Definition! 0 V If 1, enable new naming.8 1 Must be 0. This bit is Reserved for use by VSI.E 2 If 1, cloned device unit numbers wrap after 9999(not 65472). F 3 If 1, cloned device unit numbers wrap after 32767(not 65472).G Note that even if both bits are zero, device unit numbers willF wrap after 9999 if "nodename$" is prefixed to the name of theH device in question (e.g. VMS123$DKA100:); devices whose driversF support larger device numbers will wr Wap after 65472 (or 32767D if bit 3 is set) only if the nodename is not built into the device name. B For more information about port allocation classes, see the VSI" OpenVMS Cluster Systems manual. 2 DISABLE_UPCALLS> DISABLE_UPCALLS is primarily a debugging aid. It allows the> system manager to disable threads upcalls of specific types@ for the entire system. The value is a bit mask, with the bitsB corresponding to the upcall types. The upcall types aXre defined# in the definition macro $TMCDEF.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so.* DISABLE_UPCALLS is a DYNAMIC parameter. 2 DISK_QUORUMC The DISK_QUORUM parameter is the name of an optional quorum disk? in ASCII. ASCII spaces indicate that no quorum disk is being used. 2 DISMOUMSGD DISMOUMSG controls whether the messages that log volume dismountsC appear onY the operator's terminal and in the operator's log. The; default value of 0 disables reporting of these messages.$ DISMOUMSG is a DYNAMIC parameter. 2 DNVOSI1? DNVOSI1 is reserved to DECnet-Plus for OpenVMS. This specialB parameter is use by VSI and is subject to change. Do not change7 this parameter unless VSI recommends that you do so. 2 DORMANTWAITA DORMANTWAIT specifies, in seconds, the amount of time that can> elapse without a significant event before t Zhe system treats= a low-priority computable process as a DORMANT process forB scheduling purposes. (A low-priority process is a non real-timeD process whose current priority is equal to or less than the value? specified by the system parameter DEFPRI [default=4].) AfterD SUSP (suspended) processes, DORMANT processes are the most likely4 candidates for memory reclamation by the swapper.@ Increasing the value of DORMANTWAIT can increase the interval@ that a low priority proce[ss 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 number\ed 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 e ]rror 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 beenD set. Remaining or undefined values are re ^served for VSI use only.* Bit Mask Description? 0 00000001 0 = Full dump (SYSGEN default).C The entire contents of physicalB memory are written to the dump) file.C 1 = Selective dump. The contents ofB memory are written to the dump@ file selec _tively to maximizeC the usefulness of the dump file@ while conserving disk space.; 1 00000002 0 = Minimal console output.A 1 = Full console output (includesB stack dump, register contents,/ and so on).8 2 00000004 0 = Dump to system disk.B 1 = Dump ` off system disk (DOSD) toC an alternate disk. (see the VSIC OpenVMS System Manager's Manual1 for details.)4 3 (Alpha and 00000008 0 = Do not compress. Integrity servers)A 1 = Compress. (VAX systems do not> support dump compression.)7 4 (Alpha and 00000010 0 = Dump shared memory. Integri aty servers)C 1 = Do not dump shared memory. (VAXA systems do not support shared, memory.)> 5 - 14 reserved for VSI use only.@ 15 (VAX only) 00008000 0 = Disable use of bits 16 - 27.< (Specific to VAX 7000s.)? 1 = Enable use of bits 16 - 27.D 16 - 27 (VAX 0FFF0000 Rangbe of DOSD unit numbers. (VAXA only) systems do not support shared, memory.)> 28 - 31 reserved for VSI use only.B If you plan to enable the Volume Shadowing minimerge feature onD an Alpha or Integrity servers disk, be sure to specify DOSD to an alternate disk.& NOTE; On Alpha and Integrity servers, you can save space on= the system disk and, in cthe event of a crash, save time= recording the system memory, by using the OpenVMS Alpha< and Integrity servers dump compression feature. Unless? you override the default AUTOGEN calculations (by setting= DUMPSTYLE in MODPARAMS.DAT), AUTOGEN uses the following algorithm:@ o On a system with less than 128 MB of memory, the systemA sets the DUMPSTYLE to 1 (a raw selective dump) and sizes% the dump file appropriately.A o On a system d 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 neumber is 9.C On Alpha and Integrity servers, the mask of 00000009 directs theC system to compress a selective dump with minimal console output.0 DUMPSTYLE has AUTOGEN and DYNAMIC attributes. 2 ERLBUFFERPAG_S2= ERLBUFFERPAG_S2 specifies the amount of S2 space memory to? allocate for each S2 space error log buffer requested by the ERRORLOGBUFF_S2 parameter.B If you increase ERLBUFFERPAG_S2, you must either run AUTOGEN orB manually increase the size of botfh the system dump file and the error log dump file.A ERLBUFFERPAG_S2 is an AUTOGEN parameter on Alpha and Integrity servers. 2 ERLBUFFERPAGES< ERLBUFFERPAGES specifies the amount of S0 space memory to? allocate for each S0 space error log buffer requested by the ERRORLOGBUFFERS parameter.@ ERLBUFFERPAGES is an AUTOGEN parameter on Alpha and Integrity servers. 2 ERRORLOGBUFF_S2= ERRORLOGBUFF_S2 specifies the number of S2 space error log= buf gfers reserved for system error log entries. Each buffer? is ERLBUFFERPAG_S2 in length. If ERRORLOGBUFF_S2 is too low,D messages might not be written to the error log file. If it is too< high, the buffers can consume unnecessary physical pages.B If you increase ERRORLOGBUFF_S2, you must either run AUTOGEN orB manually increase the size of both the system dump file and the error log dump file.A ERRORLOGBUFF_S2 is an AUTOGEN parameter on Alpha and Integrity servers. h2 ERRORLOGBUFFERS= ERRORLOGBUFFERS specifies the number of S0 space error log@ buffers reserved for system error log entries. Each buffer isD ERLBUFFERPAGES in length. If ERRORLOGBUFFERS is too low, messagesA might not be written to the error log file. If it is too high,6 the buffers can consume unnecessary physical pages.A ERRORLOGBUFFERS is an AUTOGEN parameter on Alpha and Integrity servers. 2 EXECSTACKPAGESC (Alpha and Integrity servers) EXECSTACKPAGES icontrols the number. of pages allocated for each RMS exec stack.) EXECSTACKPAGES is a DYNAMIC parameter. 2 EXPECTED_VOTESC EXPECTED_VOTES specifies the maximum number of votes that can beD present in a cluster at any given time. Set it to a value that isB equal to the sum of the vote parameters of all cluster members,? plus any votes that are contributed by the quorum disk. ThisA value is used to automatically derive the number of votes that8 must be present forj the cluster to function (quorum).4 EXPECTED_VOTES is an AUTOGEN attribute parameter. 2 EXTRACPUC EXTRACPU sets the time, in units of 10 ms, allotted to each of aC process's exit handlers (for each access mode) after the process3 times out (that is, reaches its CPU time limit).- EXTRACPU is a DYNAMIC attribute parameter. 2 FAST_PATH= (Alpha and Integrity servers) FAST_PATH is a static system; parameter that enables (1) or disables (0) the Fast Path8 pkerformance features for all Fast Path-capable ports.D Starting in OpenVMS Version 7.2, FAST_PATH is enabled by default.> In Versions 7.0 and 7.1, FAST_PATH was disabled by default.3 For additional information, see FAST_PATH_PORTS. 2 FAST_PATH_PORTS< (Alpha and Integrity servers) FAST_PATH_PORTS is a static= parameter that deactivates Fast Path for specific drivers.A FAST_PATH_PORTS is a 32-bit mask, with a bit assigned for each? Fast Path port driver. The followinlg table describes the bit values: Bit Value DescriptionC 1 Indicates that Fast Path is disabled for ports serviced( by the corresponding driver.> 0 Indicates that Fast Path is not disabled for ports1 serviced by the corresponding driver.= Beginning in OpenVMS Version 7.3-1, values of specific bit8 positions are those described in the following table: Bit Position DescriptionA 0 Controls Fast Path for PmKQDRIVER (for parallel SCSI).@ 1 Controls Fast Path for FGEDRIVER (for Emulex LP7000,: LP8000, LP9002, LP9802, LP10000 FibreChannel).B 2 Controls Fast Path for PKADRIVER (for Adaptec AIC-78xx Ultra3 SCSI).6 3 Controls Fast Path for PEDRIVER (for LAN).D 4 Controls Fast Path for PKRDRIVER (for SMART Array 5300).; 5 Controls Fast Path for PKMDRIVER, the LSI Logic( LSI53C1030 SCSI port driver.@ 6 n Controls Fast Path for PGQDRIVER, the Qlogic ISP23xx% FibreChannel port driver.A Currently, the default setting for FAST_PATH_PORTS is 0, whichA means that Fast Path is enabled for all drivers that appear in the table.# In addition, note the following:A o CI drivers are not controlled by FAST_PATH_PORTS. Fast PathA for CI is enabled and disabled exclusively by the FAST_PATH system parameter.> o FAST_PATH_PORTS is relevant only if the FAST o_PATH systemB parameter is enabled (equal to 1). Setting FAST_PATH to zeroD has the same effect as setting all the bits in FAST_PATH_PORTS to 1.C For additional information, see FAST_PATH. For an explanation ofD how to set the bits, see the OpenVMS I/O User's Reference Manual. 2 FREEGOAL< FREEGOAL establishes the number of pages that you want to> reestablish on the free-page list following a system memoryC shortage. Memory shortages occur when the system pdrops 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 couqnt.D While the larger free-page list generally means less page I/O, itC also means less space for the balance set, which tends to resultD in more swap I/O. You can monitor the size of the free-page list,A the amount of page, and the amount of swap with the MONITOR IO" command of the Monitor utility.0 FREELIM has the AUTOGEN and MAJOR attributes. 2 GALAXYA (Alpha Galaxy platforms only) The GALAXY parameter sets memory sharing. Specify one of the followinrg: Value Description@ 0 The default. Do not participate in a memory sharing., 1 Participate in a memory sharing.B When you set GALAXY to 1 in a hard partition, OpenVMS instances= will share memory between soft partitions within that hardB partition. (You can run more than two soft partitions in a hardD partition, and you might might not want to share memory among allB of them.) Note that GALAXY specifies only if a node uses shared? memory. You do snot need to use the parameter to run multipleD cooperative instances of OpenVMS; you do this by console setup of( the configuration tree that you want. 2 GBLPAGESB GBLPAGES sets the number of global page table entries allocated@ at bootstrap time. Each global section requires 1 global page? table entry per section page, plus 2 entries, with the total rounded up to an even number.= Users with CMKRNL privilege can change this parameter on a@ running system. Increas ting 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 t uhis parameterA too low, because the page table entries use little permanently> resident memory. If you plan to install many user images as? shared, or if user programs are likely to create many global; sections, you must increase the value of this parameter.> GBLPAGES has the AUTOGEN, DYNAMIC, FEEDBACK, GEN, and MAJOR attributes. 2 GBLPAGFILC GBLPAGFIL defines the maximum number of systemwide pages allowedB for global page-file sections (scratch global sections vthat can> be used without being mapped to a file). These global page-? file sections can be temporary, permanent, system, or group,? and are allocated from the page file specified in the system= process header at bootstrap time. When you allow pages for? global page-file sections, you must increase the size of the@ page file accordingly. Users with CMKRNL privilege can change, this parameter value on a running system.@ Global page-file sections are created with the Create w and MapA Section system services ($CREATE_GPFILE, $CRMPSC, and $CRMPSC_D GPFILE_64) without an explicit disk file. These sections are usedA for the RMS global buffers required for shared files. Users of@ shared files should note that global page-file sections cause> both the global page table and the default system page file> (PAGEFILE.SYS) to be used. If the value of GBLPAGFIL is tooD small, $CRMPSC issues an error message when you attempt to create global page-file sectio xns.> 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 y value for this parameter is adequate for most@ systems. However, if your site uses RMS global buffering to aD significant extent, you may need to raise the value of GBLPAGFIL.> Use the /GLOBAL qualifier of the Install utility to examineA the number of pages consumed by RMS global buffers. The global? sections used by RMS for global buffers have the prefix RMS$$ followed by 8 hexadecimal digits.6 Global buffers are enabled with the DCL command SETA FILE/GLOBAL_BUFFERS, whiczh is described in the VSI 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 global sections are created, you canD examine the actual requirements with the /GLOBAL qualifier of theC Install utility and reduce the value of GBLSECTIONS accordingly.B However, the value of this parameter should not be set too low.@ If you plan to install many user images as shared, or if user? programs are likely to create many global sections, you must( increase the value of this parameter.B If the value of GBLSECTIONS is too small, you | receive a message> from the Install utility at system startup time or whenever? you install images manually. Note that too large a value for& GBLSECTIONS wastes physical memory.D GBLSECTIONS has the AUTOGEN, FEEDBACK, GEN, and MAJOR attributes. 2 GB_CACHEALLMAXC (Alpha and Integrity servers) If a file is connected to RMS withA the RMS global buffer DEFAULT option enabled, the number of ofD blocks cached is either a maximum of the GB_CACHEALLMAX parameterD or a pe}rcentage of the file, whichever results in a larger global count.; Note that although a maximum cache size of %x7FFFFFFF is> supported for an indexed file, sequential and relative fileA organizations are restricted to a maximum cache size of 32767.) GB_CACHEALLMAX is a DYNAMIC parameter. 2 GB_DEFPERCENTC (Alpha and Integrity servers) If a file is connected to RMS withD the RMS global buffer DEFAULT option enabled, either a percentage@ (GB_DEFPERCENT) of the fi ~le is cached or up to GB_CACHEALLMAX@ blocks of it are cached, whichever results in a larger global= buffer count. A percentage greater than 100 percent can beA specified for GB_DEFPERCENT to provide growing room for a file in the global cache.; Note that although a maximum cache size of %x7FFFFFFF is> supported for an indexed file, sequential and relative fileA organizations are restricted to a maximum cache size of 32767.( GB_DEFPERCENT is a DYNAMIC parameter. 2 GH_EXEC_CODEC (Alpha and Integrity servers) GH_EXEC_CODE specifies the size in5 pages of the execlet code granularity hint region.8 GH_EXEC_CODE has the AUTOGEN and FEEDBACK attributes. 2 GH_EXEC_DATAC (Alpha and Integrity servers) GH_EXEC_DATA specifies the size in5 pages of the execlet data granularity hint region.8 GH_EXEC_DATA has the AUTOGEN and FEEDBACK parameters. 2 GH_RES_CODEB (Alpha and Integrity servers) GH_RES_CODE specifies the size in< pages of the resident image code granularity hint region.7 GH_RES_CODE has the AUTOGEN and FEEDBACK attributes. 2 GH_RES_CODE_S2> Specifies the size in pages of the resident 64-bit S2 space/ resident image code granularity hint region. 2 GH_RES_DATAB (Alpha and Integrity servers) GH_RES_DATA specifies the size in< pages of the resident image data granularity hint region.> If bit 2 of the LOAD_SYS_IMAGES parameter is set, the image? LDR$WRAPUP releases all unused pages in the granularity hintC region at the the end of system startup. The unused pages of theA resident image granularity hint region are either reserved for5 future use, or given back to the free memory list.7 GH_RES_DATA has the AUTOGEN and FEEDBACK attributes. 2 GH_RSRVPGCNTC GH_RSRVPGCNT specifies the number of pages in the resident image@ code granularity hint region that the Install utility can use) after the system has finished booting.> If bit 2 of the LOAD_SYS_IMAGES parameter is set, the image? LDR$WRAPUP releases all unused pages in 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$WRAPUP@ attempts to leave in the resident image code granularity hintA region. If the GH_RSRVPGCNT number of pages is larger than theA unused pages in the granularity hint region, the region is not9 expanded to accommodate the number of pages requested.2 GH_RSRVPGCNT is a FEEDBACK attribute parameter. 2 GLX_INST_TMO= (Alpha Galaxy platforms only) GLX_INST_TMO is the time (inB milliseconds) that an instance in a Galaxy sharing set can failD to increment its timeout value before the other sharing instancesB presume that the instance failed and remove it from the sharing set.) The  default is 20,000 ms (20 seconds). 2 GLX_SHM_REG@ For Alpha Galaxy systems, GLX_SHM_REG is the number of sharedA memory region structures configured into the Galaxy ManagementD Database (GMDB). If set to 0, the default number of shared memory regions are configured.> If the condition value SS$_INSF_SHM_REG is returned for theD $CRNMPSC_GDZRO_64 system service with the flag SEC$M_SHM_REG, theA Galaxy shared memory code has run out of internal SHM_REG dataD structu res. You need to increase the system parameter GLX_SHM_REGD and reboot all Galaxy instances with this larger parameter value. 2 GROWLIMD GROWLIM sets the number of pages that the system must have on theA free-page list so that a process can add a page to its workingC set when it is above quota. GROWLIM has no effect if the processA is below its working set quota. GROWLIM acts as a fast shutoffA to the working set extent mechanism based on the system's free memory.6 GROWLIM has AUTOGEN, DYNAMIC, and MAJOR attributes. 2 IEEE_ADDRESS- IEEE_ADDRESS is reserved for VSI use only. 2 IEEE_ADDRESSH. IEEE_ADDRESSH is reserved for VSI use only. 2 IJOBLIMB IJOBLIM sets the maximum number of interactive jobs that can beD on the system concurrently. You can control the maximum number ofB concurrent interactive users on the system with the DCL command SET LOGINS/INTERACTIVE." IJOBLIM is a DYNAMIC parameter. 2 IMGIOCN T> 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.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 IMGREG_PAGES> (Alpha and Integrity servers) IMGREG_PAGES is the number of? pages to reserve in P1 space for images to be installed withA shareable address data. If IMGREG_PAGES is set to 0, no images@ are installed with shared address data. The default is 10,000 pages.C For more information, see the INSTALL section in the VSI OpenVMS0 System Management Utilities Reference Manual. 2 IO_PRCPU_BITMAP; (Alpha and Integrity servers) This parameter is a bitmap< representing up to 1024 CPUs. Each bit set in this bitmapA indicates that the corresponding CPU is available for use as a Fast Path preferred CPU.D IO_PRCPU_BITMAP defaults to all bits set. (CPU 0 through CPU 10232 are all enabled for Fast Path port assignment.)> You might want to disable the primary CPU from serving as aC preferred CPU by leaving its bit clear in IO_PRCPU_BITMAP, whichC reserves the primary CPU for non-Fast Path IO operations to use.? To change the value of IO_PRCPU_BITMAP in SYSBOOT or SYSGEN,B specify a list of individual bits or contiguous groups of bits. For example:+ SYSGEN> SET IO_PRCPU_BITMAP 0,5,17-21D This command sets bits 0, 5, 17, 18, 19, 20, and 21 in the bitmap and clears all other bits.C Changing the value of IO_PRCPU_BITMAP causes the FASTPATH_SERVERA process to run the automatic assignment algorithm that spreads; Fast Path ports evenly among the new set of usable CPUs.A For additional information, see FAST_PATH and FAST_PATH_PORTS.) This parameter replaces IO_PREFER_CPU. 2 IOTAA IOTA specifies the amount of time (in 10-millisecond units) toC cha rge to the current residence quantum for each voluntary wait.C The correct value approximates the cost of a disk I/O neglecting wait time.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 IRPCOUNT@ IRPCOUNT sets the number of preallocated intermediate requestB packets. Each packet requires 160 bytes of permanently resident? memory. If IRPCOUNT is too large, physical memory is wasted .; If IRPCOUNT is too small, the system increases its value: automatically, as needed, to permit proper performance.@ However, the system cannot increase IRPCOUNT beyond the value of IRPCOUNTV.< Allowing this growth causes a physical memory penalty. IfD IRPCOUNT is underconfigured, the penalty is 4 percent of physical> memory from the configured value to the actual value on the running system.A You can use the DCL command SHOW MEMORY/POOL/FULL to determine IRPCOUNT usage.- IRPCOUNT has the GEN and MAJOR attributes. 2 IRPCOUNTVA IRPCOUNTV establishes the upper limit to which IRPCOUNT can be) automatically increased by the system.> If this parameter is set too low, system performance can beC adversely affected because IRPCOUNTV cannot be used for nonpaged pool requests.@ A physical memory penalty of 1 percent results for any unusedC growth space (1 longword for every 3 unused intermediate request packets).#  IRPCOUNTV has the GEN attribute. 2 JBOBLIM& This parameter is no longer in use. 2 JOBCTLDC System managers do not usually alter JOBCTLD; this word of debugA flags is used in rolling upgrades of OpenVMS. If bit 0 is set,6 the queue manager does not start. The default is 0.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 KSTACKPAGESC (Alpha and Integrity servers) KSTACKPAGES controls the number of- pages allocated for process kernel stacks. 2 LAN_FLAGS@ (Alpha and Integrity servers) LAN_FLAGS is a bit mask used to> enable features in the local area networks port drivers and6 support code. The default value for LAN_FLAGS is 0.& The bit definitions are as follows: Bit DescriptionC 0 The default of zero indicates that ATM devices run inE SONET mode. If set to 1, this bit indicates ATM devices  run in SDH mode.@ 1 If set, this bit enables a subset of the ATM traceD and debug messages in the LAN port drivers and support code.> 2 If set, this bit enables all ATM trace and debug@ messages in the LAN port drivers and support code.B 3 If set, this bit runs UNI 3.0 over all ATM adapters.E (Auto-sensing of the ATM UNI version is enabled if both+ bit 3 and bit 4 are off (0).)B 4 If set, this bit runs UNI 3.1 over all ATM adapters.E (Auto-sensing of the ATM UNI version is enabled if both+ bit 3 and bit 4 are off (0).)@ 5 If set, disables auto-negotiation over all Gigabit Ethernet Adapters.> 6 If set, enables the use of jumbo frames over all( Gigabit Ethernet Adapters. 7 Reserved.C 8 If set, disables the use of flow control over all LAN1  adapters that support flow control. 9 Reserved. 10 Reserved.B 11 If set, disables the logging of error log entries by LAN drivers.B 12 If set, enables a fast timeout on transmit requests,A usually between 1 and 1.2 seconds instead of 3 to 4, seconds, for most LAN drivers.@ 13 If set, transmits that are given to the LAN deviceA and never completed by the device (transmit timeoutD condition) are completed with error status (SS$_ABORT)6 rather than success status (SS$_NORMAL).$ LAN_FLAGS is a DYNAMIC parameter. 2 LCKMGR_CPUIDC (Alpha and Integrity servers) LCKMGR_CPUID controls the CPU thatC the Dedicated CPU Lock Manager runs on. This is the CPU that theB LCKMGR_SERVER process utilizes if you turn this feature on with$ the LCKMGR_MODE system parameter.9 If the specified CPU ID is either the primary CPU or aA nonexistent CPU, the LCKMGR_SERVER process utilizes the lowestC nonprimary CPU. For more information, see the LCKMGR_MODE system parameter.' LCKMGR_CPUID is a DYNAMIC parameter. 2 LCKMGR_MODEC (Alpha and Integrity servers) The LCKMGR_MODE parameter controlsB use of the Dedicated CPU Lock Manager. Setting LCKMGR_MODE to aA number greater than zero (0) indicates the number of CPUs thatA must be active before the Dedicated CPU Lock Manager is turned on. A The Dedicated CPU Lock Manager performs all locking operationsA on a single dedicated CPU. This can improve system performanceC on large SMP systems with high MP_Synch associated with the lock manager.C If the number of active CPUs is greater than or equal to LCKMGR_> MODE, a LCKMGR_SERVER process is created to service lockingB operations. This process runs at a real-time priority of 63 and is always current.C In addition, if the number of active CPUs should ever be reducedB below the required threshold by either a STOP/CPU command or byB a CPU reassignment in a Galaxy configuration, the Dedicated CPUB Lock Manager automatically turns off within one second, and theA LCKMGR_SERVER is placed in a hibernate state. If the number of@ active CPUs is increased, the LCKMGR_SERVER resumes servicing locking operations. Specify one of the following:C o Zero (0) indicates that the Dedicated CPU Lock Manager is off (the default).A o A number greater than zero (0) indicates the number of CPUsD that must be active before the Dedicated CPU Lock Manager will turn on.> When the Dedicated CPU Lock Manager is turned on, fast path@ devices are not assigned to the CPU used by the Dedicated CPU Lock Manager.> When the Dedicated CPU Lock Manager is turned on, fast path@ devices are not assigned to the CPU used by the Dedicated CPU Lock Manager.D For more information about use of the Dedicated CPU Lock Manager,1 see the OpenVMS Performance Management manual.& LCKMGR_MODE is a DYNAMIC parameter. 2 LGI_BRK_DISUSERC LGI_BRK_DISUSER turns on the DISUSER flag in the UAF record when> an attempted break-in is detected, thus permanently locking> out that account. The parameter is off (0) by default. YouB should set the parameter (1) only under extreme security watch= conditions, because it results in severely restricted user service.* LGI_BRK_DIS USER is a DYNAMIC parameter. 2 LGI_BRK_LIMA LGI_BRK_LIM specifies the number of failures that can occur at? login time before the system takes action against a possibleA break-in. The count of failures applies independently to loginA attempts by each user name, terminal, and node. Whenever login> attempts from any of these sources reach the break-in limitB specified by LGI_BRK_LIM, the system assumes it is under attack? and initiates evasive action as specified by the LGI_HID_TIM parameter.A The minimum value is 1. The default value is usually adequate.& LGI_BRK_LIM is a DYNAMIC parameter. 2 LGI_BRK_TERM: LGI_BRK_TERM causes the terminal name to be part of theB association string for the terminal mode of break-in detection.@ When LGI_BRK_TERM is set to off (0), the processing considers? the local or remote source of the attempt, allowing break-in@ detection to correlate 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 number of seconds that evasive actionC persists following the detection of a possible break-in attempt.B The system refuses to allow any logins during this period, even3 if a valid user name and password are specified.& LGI_HID_TIM is a DYNAMIC parameter. 2 LGI_PWD_TMO? LGI_PWD_TMO specifies, in seconds, the period of time a userB has to enter the correct system password (if used). LGI_PWD_TMO? also establishes the timeout period for users to enter theirA personal account passwords at login time. Also, when using theA SET PASSWORD command, LGI_PWD_TMO specifies the period of time@ the system waits for a user to type in a new password, an old+ password, and the password verification.& LGI_PWD_TMO is a DYNAMIC parameter. 2 LGI_RETRY_LIM? LGI_RETRY_LIM specifies the number of retry attempts allowedC  users attempting to log in. If this parameter is greater than 0,D and a legitimate user fails to log in correctly because of typingD errors, the user does not automatically lose the carrier. InsteadA (provided that LGI_RETRY_TMO has not elapsed), by pressing the> Return key, the user is prompted to enter the user name andA password again. Once the specified number of attempts has been? made without success, the user loses the carrier. As long as@ neither LGI_BRK_LIM nor LGI_B RK_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 the process logical name hash table.? Logical names are hashed using a function of the name length@ and contents. The LNMPHASHTBL parameter determines the number@ of entries for process-private logical names. The recommendedB setting is the average number of process-private logical names.B Note that the hashed values are rounded up to the nearest power  of 2.D LNMPHASHTBL has the GEN attribute. On VAX systems, LNMPHASHTBL is% also an AUTOGEN-altered parameter. 2 LNMSHASHTBLC LNMSHASHTBL sets the size of the system logical name hash table.? Logical names are hashed using a function of the name length@ and contents. The LNMSHASHTBL parameter determines the numberB of entries for shareable logical names. These names include allA names from the system, group, and job logical name tables. The@ recommended setting  allows one to four logical names per hash? table entry. The default setting is usually adequate, unlessC your installation has a large number of groups, or many jobs areC active simultaneously. In that case, an increase in the value ofD the next higher power of 2 might improve logical name translationA performance. Note that the hashed values are rounded up to the nearest power of 2.= LNMSHASHTBL has the AUTOGEN, FEEDBACK, and GEN attributes. 2 LOAD_PWD_POLICY<  LOAD_PWD_POLICY controls whether the SET PASSWORD command@ attempts to use site-specific password policy routines, whichA are contained in the shareable image SYS$LIBRARY:VMS$PASSWORD_B POLICY.EXE. The default is 0, which indicates not to use policy routines. 2 LOAD_SYS_IMAGESD This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so.B LOAD_SYS_IMAGES controls the loading of system images describedC in the system image data file, VMS$SYSTEM_IMAGES. This parameter is a bit mask.B On Alpha and Integrity servers, the following bits are defined:* Bit DescriptionA 0 (SGN$V_LOAD_SYS_IMAGES) Enables loading alternate execletsC specified in VMS$SYSTEM_IMAGES.DATA.9 1 (SGN$V_EXEC_SLICING) Enables executive slicing.C 2 (SGN$V_RELEASE_PFNS) Enables releasing unused portions ofC  the Alpha and Integrity servers huge% pages.D These bits are on by default. Using conversational bootstrap exec slicing can be disabled.@ On Alpha and Integrity servers, LOAD_SYS_IMAGES is an AUTOGEN parameter. 2 LOCKDIRWTB LOCKDIRWT determines the portion of lock manager directory that> this system handles. The default value is usually adequate.% LOCKDIRWT is an AUTOGEN parameter. 2 LOCKIDTBLB LOCKIDTBL sets the initial number of entries in the system Lock@ ID table and defines the amount by which the Lock ID table isA extended whenever the system runs out of locks. One entry mustB exist for each lock in the system; each entry requires 4 bytes.A For simple timesharing systems, the default value is adequate.C If your application uses many locks, as in the case of heavy RMS@ file sharing or a database management application, you shouldC increase this parameter. When you change the value of LOCKIDTBL,> examine the value of RESHASHTBL and change it if necessary.? The OpenVMS Lock Management facility is described in the VSIB OpenVMS Programming Concepts Manual. You can monitor locks with3 the MONITOR LOCK command of the Monitor utility.= LOCKIDTBL has the AUTOGEN, FEEDBACK, and MAJOR attributes. 2 LOCKIDTBL_MAX@ LOCKIDTBL_MAX is obsolete beginning with OpenVMS Version 7.1. 2 LOCKRETRY> LOCKRETRY establishes the number of attempts made to lock a! multiprocessor data structure.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 LOCKRMWT& NOTE? On OpenVMS Version 8.3 systems, LOCKRMWT does not control& lock remastering. See LOCKDIRWT.? LOCKRMWT can have a value from zero to 10. The default is 5.B Remaster decisions are based on the difference in lock remasterA weights bet ween the master and a remote node. When weights areB equal, the remote node needs about 13% more activity before theB tree is remastered. If a remote node has a higher lock remasterC weight, the amount of activity is less. If the remote node has aB lower lock remaster weight, the additional activity required to! move the tree is much greater.A Lock remaster weights of zero and 10 have additional meanings.@ A value of zero indicates that a node does not want to masterA tre es and always remasters to an interested node with a higher= LOCKRMWT. Lock trees on an interested node with a LOCKRMWT? lower than 10 are remastered to the node with a weight of 10 for LOCKRMWT.# LOCKRMWT is a DYNAMIC parameter. 2 LONGWAIT? LONGWAIT defines how much real time (in seconds) must elapseA before the swapper considers a process to be temporarily idle.D This parameter is applied to local event flag (LEF) and hibernateC (HIB) waits to detect such conditions as an inactive terminal or ACP.@ LONGWAIT has the DYNAMIC, GEN, and MAJOR attributes. On Alpha= and Integrity servers, LONGWAIT is also an AUTOGEN-altered parameter. 2 MAXBOBMEM> (Alpha and Integrity servers) MAXBOBMEM defines the maximum? amount of physical memory, measured in pagelets, that can be> associated with a single buffer object created by a processA in user mode. The default value of 0 means there is no system-0 imposed limit on the size of a buffer object.$ MAXBOBMEM is a DYNAMIC parameter.? Other MAXBOB* parameters are obsolete beginning with OpenVMS Version 7.3. 2 MAXBUFA MAXBUF sets the maximum allowable size for any single buffered: I/O packet. Buffered I/O packets are allocated from the< permanently resident nonpaged dynamic pool. The terminal,= mailbox, and printer device drivers are examples of device% drivers that perform buffered I/O.D The number of bytes specified in the I/O request plus the size ofB a driver-dependent and function-dependent header area determine@ the required buffered I/O packet size. The size of the headerC area is a minimum of 16 bytes; there is no absolute upper limit.D However, this header area is usually a few hundred bytes in size.C The default value on Alpha and Integrity servers continues to be 8192.. The maximum value of MAXBUF is 64000 bytes.! MAXBUF is a DYNAMIC parameter. 2 MAXCLASSPRI? If class sc heduling is enabled, MAXCLASSPRI sets the maximum< range in the priority range of class-scheduled processes.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so.& MAXCLASSPRI is a DYNAMIC parameter. 2 MAXPROCESSCNTD MAXPROCESSCNT sets the number of process entry slots allocated atC bootstrap time. One slot is required for each concurrent processD on the system. Each slot requires 6 bytes of permanently resident memory.B The default value is normally configured to allow you to create< the desired number of processes. If the following message< appears, you need to increase the value of MAXPROCESSCNT:. %SYSTEM-F-NOSLOT, No PCB to create processA On Alpha and Integrity servers beginning with Version 8.1, the default value is 32,767.: MAXPROCESSCNT has the AUTOGEN, FEEDBACK, GEN, and MAJOR attributes. 2 MAXQUEPRIC MAXQUEPRI determines the highest scheduling priority that can beA assigned to jobs entered in batch and output (printer, server,D and terminal) queues without the submitter process having OPER orD ALTPRI privilege. The value of this parameter can range from 0 toD 255; the default is 100. The value of MAXQUEPRI should be greater than or equal to DEFQUEPRI.& NOTEA MAXQUEPRI refers to relative queue scheduling priority, not+ to the execution priority of the job.$ MAXQUEPRI is a DYNAMIC parameter. 2 MAXSYSGROUPB MAXSYSGROUP sets the highest value that a group number can haveB and still be classified as a system UIC group number. Note thatD the specification is not in octal unless preceded by the %O radix> indicator. This parameter is normally left at 8 (10 octal).& MAXSYSGROUP is a DYNAMIC parameter. 2 MC_SERVICES_P0D (Alpha only) MC_SERVICES_P0 controls whether other MEMORY CHANNELA nodes in the cluster continue to run if this node bugchecks or shuts down.C A value of 1 causes other nodes in the MEMORY CHANNEL cluster toB crash with bugcheck code MC_FORCED_CRASH if this node bugchecks or shuts down.> The default value is 0. A setting of 1 is intended only for@ debugging purposes; the parameter should otherwise be left at its default value.) MC_SERVICES_P0 is a DYNAMIC parameter. 2 MC_SERVICES_P1C (Alpha only) This special parameter is reserved for VSI use. ItsC value must be the same on all nodes connected by MEMORY CHANNEL.) MC_SERVICES_P1 is a DYNAMIC parameter. 2 MC_SERVICES_P2< (Alpha only) MC_SERVICES_P2 specifies whether to load the6 PMDRIVER (PMA0) MEMORY CHANNEL cluster port driver.A PMDRIVER is a driver that serves as the MEMORY CHANNEL clusterC port driver. It works together with MCDRIVER (the MEMORY CHANNEL@ device driver and driver interface) to provide MEMORY CHANNELA clustering. If PMDRIVER is not loaded, cluster connections are1 not made over the MEMORY CHANNEL interconnect.B The default 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.@ VSI recommends that this value not be changed. This parameterC value must be the same on all nodes connected by MEMORY CHANNEL. 2 MC_SERVICES_P3C (Alpha only) MC_SERVICES_P3 specifies the maximum number of tagsA supported. The maximum value is 2048, and the minimum value is 100.? The default value is 800. VSI recommends that this value notA be changed. This parameter value must be the same on all nodes connected by MEMORY CHANNEL.) MC_SERVICES_P3 is a DYNAMIC parameter. 2 MC_SERVICES_P4> (Alpha only) MC_SERVICES_P4 specifies the maximum number of@ regions supported. The maximum value is 4096, and the minimum value is 100.? The default value is 200. VSI recommends that this value notA be changed. This parameter value must be the same on all nodes connected by MEMORY CHANNEL. 2 MC_SERVICES_P5D (Alpha only) MC_SERVICES_P5 is reserved for VSI use only and mustA remain at the default value of 8000000. This value must be the1 same on all nodes connected by MEMORY CHANNEL.) MC_SERVICES_P5 is a DYNAMIC parameter. 2 MC_SERVICES_P6? (Alpha only) MC_SERVICES_P6 specifi es 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 information al9 messages appear on the console or in the error log.A o A value of 1 indicates verbose mode: informational messagesB from both MCDRIVER and PMDRIVER appear on the console and in the error log.A o A value of 2 provides the same output as a value of 1, with> the addition of PMDRIVER stalling and recovery messages.= The default value is 0. VSI recommends that this value not? be changed except while debugging MEMORY CHANNEL problems or* adjusting the MC_SERVICES_P9 parameter.) MC_SERVICES_P7 is a DYNAMIC parameter. 2 MC_SERVICES_P8D (Alpha only) MC_SERVICES_P8 is reserved for VSI use only and mustB remain at the default value of 0. The value must be the same on) all nodes connected by MEMORY CHANNEL. 2 MC_SERVICES_P9> (Alpha only) MC_SERVICES_P9 specifies the number of initialA entries in a single channel's free queue. The maximum value is% 2048, and the minimum value is 10.@ Note that MC_SERVICES_P9 is not a dynamic parameter; you must> reboot the system after each change for that change to take effect.B The default value is 150. VSI recommends that this value not be changed.< The value of MC_SERVICES_P9 must be the same on all nodes connected by MEMORY CHANNEL. 2 MINCLASSPRI? If class scheduling is enabled, MINCLASSPRI sets the minimum< range in the priority range of class-scheduled processes.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so.& MINCLASSPRI is a DYNAMIC parameter. 2 MINWSCNT> The value specified by MINWSCNT is added to the size of the< process header to establish the minimum working set size.C On Alpha and Integrity servers, MINWSCNT sets the minimum number@ of pages required for the execution of a process. The default( value is 20; the minimum value is 10.$ MINWSCNT is an AUTOGEN parameter. 2 MMG_CTLFLAGS= MMG_CTLFLAGS is a bitmask used to enable or disable memory! management-related activities.< The first two bits, 0 and 1, control the proactive memoryB reclamation mechanisms. Bit 2 controls deferred memory testing.- The following bit mask values are defined: Bit Description@ 0 If this bit is set, reclamation is enabled by trimming: from periodically executing, but otherwise idle,? processes. This occurs when the size of the free l istC plus the modified list drops below two times the value ofB FREEGOAL. This function is disabled if the bit is clear.C 1 If this bit is set, reclamation is enabled by outswapping@ processes that have been idle for longer than LONGWAITC seconds. This occurs when the size of the free list dropsA below FREEGOAL. This function is disabled if the bit is clear.? 2 Controls deferred memory testing (only on AlphaServerA  4100 systems). You can use this bit to speed up elapsed> bootstrap time by controlling when memory is tested:D o If the bit is clear (the default), OpenVMS tests memory? as a background activity, which might or might not> complete before the end of the bootstrap process.; o If the bit is set, all memory is tested in the@ bootstrap process by the end of the EXEC_INIT phase6 (that is, before IPL is lowered from 31).0 3 Reserved to OpenVMS use; must be zero.< 4 If this bit is clear (the default), all page sizesB supported by hardware can be used to map resident memoryA sections on Integrity servers. If this bit is set, page? sizes on Integrity servers are limited to the maximumB GH factor available on Alpha systems (512 * )." 5-7 Reserved for future use.4 MMG_CTLFLAGS is an AUTOGEN and DYNAMIC parameter. 2 MOUNTMSG_(D)@ MOUNTMSG controls whether or not the messages that log volumeA mounts appear on the operator's terminal and in the operator'sD log. The default value of 0 disables reporting of these messages.B This parameter does not control the messages generated by mount assistance requests.# MOUNTMSG is a DYNAMIC parameter. 2 MPDEV_AFB_INTVL> (Alpha and Integrity servers) MPDEV_AFB_INTVL specifies theA automatic failback interval in seconds. The  automatic failbackD interval is the minimum number of seconds that must elapse before> the system attempts another failback from an MSCP path to a" direct path on the same device.C MPDEV_POLLER must be set to ON to enable automatic failback. YouA can disable automatic failback without disabling the poller by< setting MPDEV_AFB_INTVL to 0. The default is 300 seconds. 2 MPDEV_D*> (Alpha and Integrity servers) MPDEV_D1 through MPDEV_D4 are, reserved for use by the operating system. 2 MPDEV_ENABLEC (Alpha and Integrity servers) MPDEV_ENABLE enables the formation@ of multipath sets when set to ON (1). If MPDEV_ENABLE is setB to OFF (0), the formation of additional multipath sets and theA addition of new paths to existing multipath sets are disabled.D However, existing multipath sets remain in effect. The default is ON.D MPDEV_REMOTE and MPDEV_AFB_INTVL have no effect when MPDEV_ENABLE is set to OFF. 2 MPDEV_LCRETRI ESD (Alpha and Integrity servers) MPDEV_LCRETRIES controls the numberA of times the system retries the direct paths to the controllerA that the logical unit is online to, before moving on to directB paths to the other controller, or to an MSCP served path to theD device. The valid range for retries is 1 through 256. The default is 1. 2 MPDEV_POLLER@ (Alpha and Integrity servers) MPDEV_POLLER enables polling ofB the paths to multipath set members when set to ON (1).  Polling@ allows early detection of errors on inactive paths. If a pathC becomes unavailable or returns to service, the system manager isB notified with an OPCOM message. When set to OFF (0), multipathC polling is disabled. The default is ON. Note that this parameter; must be set to ON to use the automatic failback feature. 2 MPDEV_REMOTEA (Alpha and Integrity servers) MPDEV_REMOTE enables MSCP servedA paths to become members of a multipath set when set to ON (1).D  When set to OFF (0), only local paths to a SCSI or Fibre Channel@ device is used in the formation of additional multipath sets.B However, setting this parameter to OFF does not have any effect5 on existing multipath sets that have remote paths.@ To use multipath failover to a served path, MPDEV_REMOTE must> be enabled on all systems that have direct access to shared@ SCSI/Fibre Channel devices. The first release to provide this? feature is OpenVMS Alpha Version 7.3-1. There fore, all nodesA on which MPDEV_REMOTE is enabled must be running OpenVMS Alpha Version 7.3-1 (or later).A If MPDEV_ENABLE is set to OFF (0), the setting of MPDEV_REMOTEC has no effect because the addition of all new paths to multipath' sets is disabled. The default is ON. 2 MPW_HILIMITC MPW_HILIMIT sets an upper limit for the modified-page list. WhenD the list accumulates the number of pages specified by this limit,B writing of the list begins. The pages that are written are then% transferred to the free-page list.D If MPW_HILIMIT is too low, excessive page faulting can occur fromC the page file. If it is too high, too many physical pages can be& consumed by the modified-page list.? If you increase MPW_HILIMIT, you might also need to increase9 MPW_WAITLIMIT. Note that if MPW_WAITLIMIT is less than@ MPW_HILIMIT, a system deadlock occurs. The values for the two parameters are usually equal.2 MPW_HILIMIT has the AUTOGEN and GEN attributes. 2 MPW_IOLIMIT> MPW_IOLIMIT specifies the number of outstanding I/Os to the modified-page writer.D On Alpha and Integrity servers, MPW_IOLIMIT is an AUTOGEN-altered parameter. 2 MPW_LOLIMITB MPW_LOLIMIT sets a lower limit for the modified-page list. When@ writing of the list causes the number of pages on the list to. drop to or below this limit, writing stops.C MPW_LOLIMIT ensures that a certain number of pages are available> on the modified-page list for page faults. If the number isA too small, the caching effectiveness of the 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.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so.  2 MPW_THRESH@ MPW_THRESH sets a lower bound of pages that must exist on theD modified-page 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 and Integrity4 servers, MPW_THRESH is also an AUTOGEN parameter. 2 MPW_WAITLIMITC MPW_WAITLIMIT sets the number of page s 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 w ritten during one@ I/O operation from the modified-page list to the page file or@ a section file. The actual size of the cluster may be limited? by the number of pages available for the I/O operation. ThisB parameter can range in value from 16 to 120, in multiples of 8.D Each page in the cluster requires 6 bytes of permanently resident memory.? If MPW_WRTCLUSTER is too small, it takes many I/O operationsB to empty the modified-page list. If MPW_WRTCLUSTER is too large@  for the speed of the disk that holds the page file, other I/O; operations are held up for the modified-page list write.C On Alpha and Integrity servers, the MPW_WRTCLUSTER default valueC is 64 8192-byte pages; its maximum value is 512 8192-byte pages;/ and its minimum value is 16 8192-byte pages.5 MPW_WRTCLUSTER has the AUTOGEN and GEN attributes. 2 MSCP_BUFFERD This buffer area is the space used by the server to transfer data* between client systems and local disks.C On Alpha and Integrity servers, MSCP_BUFFER specifies the number@ of pagelets to be allocated to the MSCP server's local buffer area.4 MSCP_BUFFER is an AUTOGEN and FEEDBACK parameter. 2 MSCP_CMD_TMOC MSCP_CMD_TMO is the time in seconds that the OpenVMS MSCP server= uses to detect MSCP command timeouts. The MSCP Server must? complete the command within a built-in time of approximately; 40 seconds plus the value of the MSCP_CMD_TMO parameter.> The M SCP_CMD_TMO default value of 0 is normally adequate. A@ value of 0 provides the same behavior as in previous releasesD of OpenVMS (which did not have an MSCP_CMD_TMO system parameter).@ A nonzero setting increases the amount of time before an MSCP command times out.> If command timeout errors are being logged on client nodes,> setting the parameter to a nonzero value on OpenVMS servers> may reduce the number of errors logged. As the value of theE MSCP_CMD_TMO increases, the number of client MSCP command timeoutsB will decrease, at the cost of increased time to detect a faulty) MSCP controller or MSCP-served device.D If you need to decrease the number of command timeout errors, VSID recommends that you set an initial value of 60. If timeout errorsC continue to be logged, you can increase this value in increments of 20 seconds.' MSCP_CMD_TMO is a DYNAMIC parameter. 2 MSCP_CREDITS@ MSCP_CREDITS specifies the number of outstanding I/O requests- that can be active from one client system.> The default value is currently 32. Unless a system has veryA constrained memory available, VSI recommends that these values not be increased. 2 MSCP_LOADD MSCP_LOAD controls the loading of the MSCP server during a system- boot. Specify one of the following values: Value DescriptionA 0 Do not load the MSCP server. This is the default value.B 1 Load the MSCP server and serve disks as specified by the# MSCP_SERVE_ALL parameter.' MSCP_LOAD has the AUTOGEN attribute. 2 MSCP_SERVE_ALL@ MSCP_SERVE_ALL is a bit mask that controls disk serving in anA OpenVMS Cluster. A disk is served regardless of its allocation' class unless bit 3 has a value of 1.; Starting with OpenVMS Version 7.2, the serving types areA implemented as a bit mask. To specify the type of serving yourA system will perform, locate the type you want in the followingA tab le and specify its value. For some systems, you may want toA specify two serving types, such as serving the system disk andA serving locally attached disks. To specify such a combination,4 add the values of each type, and specify the sum.? In a mixed-version cluster that includes any systems running@ OpenVMS Version 7.1-x or earlier, serving all available disksC is restricted to serving all disks except those whose allocationA class does not match the system's node allocation class (priorD to Version 7.2). To specify this type of serving, use the value 9 (which sets bit 0 and bit 3).D The following table describes the serving type controlled by each bit and its decimal value: Bit and Value When Set Description@ Bit 0 (1) Serve all available disks (locally attached and> those connected to HSx and DSSI controllers).? Disks with allocation classes that differ fromD the system' s allocation class (set by the ALLOCLASS@ parameter) are also served if bit 3 is not set.A Bit 1 (2) Serve locally attached (non-HSx and DSSI) disks.D Bit 2 (4) Serve the system disk. This is the default setting.B This setting is important when other nodes in the@ cluster rely on this system being able to serve? its system disk. This setting prevents obscureA contention problems that can occur when  a systemA attempts to complete I/O to a remote system disk) whose system has failed.C Bit 3 (8) Restrict the serving specified by bit 0. All disksA except those with allocation classes that differ? from the system's allocation class (set by the1 ALLOCLASS parameter) are served.B This is pre-Version 7.2 behavior. If your clusterC includes systems running OpenVMS 7.1-x or earlier,D and you want to serve all available disks, you mustB specify 9, the result of setting this bit and bit 0.D Although the serving types are now implemented as a bit mask, theD values of 0, 1, and 2, specified by bit 0 and bit 1, retain their original meanings:B 0 - Do not serve any disks (the default for earlier versions of OpenVMS).$ 1 - Serve all available disks.C 2 - Serve only locally attached (non-HSx and non-DSSI) disks.< If the MSCP_LOAD system parameter is 0, MSCP_SERVE_ALL is ignored. 2 MULTIPROCESSING5 MULTIPROCESSING controls the loading of the system synchronization image.' Specify one of the following values: Value Description8 0 Load the uniprocessing synchronization image+ SYSTEM_SYNCHRONIZATION_UNI.EXE.8 1 If the CPU type is capable of SMP and two or9 more CPUs are present on the  system, load the9 full-checking multiprocessing synchronization8 image 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 th e system, load the optimized. streamlined multiprocessing image:< o On Alpha and Integrity servers, this image is. SYSTEM_SYNCHRONIZATION_MIN.EXE.C Otherwise, load the uniprocessing synchronization imageC SYSTEM_SYNCHRONIZATION_UNI.EXE. The default value is 3.= 4 Always load the streamlined multiprocessing image@ SYSTEM_SYNCHRONIZATION_MIN.EXE, regardless of system. configuration or CPU availability.D Setting the SYSTEM_CHECK parameter to 1 has the effect of setting MULTIPROCESSING to 2. 2 MULTITHREAD: MULTITHREAD controls the availability of kernel threads2 functions. Specify one of the following values: Value DescriptionC 0 Both Thread Manager upcalls and the creation of9 multiple kernel threads are disabled.D 1 Thread Manager upcalls are enabled; the creation; of multiple kernel threads is disabled.@ 2-256 (Alpha Both Thread Manager upcalls and the creation? and Integrity of multiple kernel threads are enabled. TheB servers) number specified represents the maximum number? of kernel threads that can be created for a# single process., The maximum value for MULTITHREAD is 256.3 MULTITHREAD is an AUTOGEN and DYNAMIC parameter. 2 MVSUPMSG_INTVL< (Alpha and Integrity servers) The  system suppresses mount= verification start and end messages for fibre channel disk? devices if mount verification completes on the first attemptC and if mount verification does not occur too often. MVSUPMSG_NUM+ and this parameter establish this limit.B The system issues a mount verification message after a sequenceA of MVSUPMSG_NUM mount verifications have gone unannounced on a@ specific fibre channel disk device within a span of MVSUPMSG_ INTVL seconds.A If this parameter is zero, all mount verification messages are announced.) MVSUPMSG_INTVL is a DYNAMIC parameter. 2 MVSUPMSG_NUM< (Alpha and Integrity servers) The system suppresses mount= verification start and end messages for fibre channel diskC devices if mount verification completes on the first attempt andA if mount verification does not occur too often. MVSUPMSG_INTVL+ and this parameter establish this limit.B The system issues a mount verification message after a sequenceA of MVSUPMSG_NUM mount verifications have gone unannounced on a@ specific fibre channel disk device within a span of MVSUPMSG_ INTVL seconds.A If this parameter is zero, all mount verification messages are announced.' MVSUPMSG_NUM is a DYNAMIC parameter. 2 MVTIMEOUT= MVTIMEOUT is the time in seconds that a mount verification9 attempt continues on a given disk volume. If the mountA verification does not recover the volume within that ti me, theA I/O operations outstanding to the volume terminate abnormally.D MVTIMEOUT is a DYNAMIC parameter. On Alpha and Integrity servers,* MVTIMEOUT is also an AUTOGEN parameter. 2 NET_CALLOUTSC NET_CALLOUTS is normally set to 0. A value of 255 indicates thatB no attempt is to be made to assign a new proxy connection to anB active server, but that a new process must be started to invokeD the installation security policy callout modules in LOGINOUT.EXE.4 Values 1 through 254 are reserved for future use.' NET_CALLOUTS is a DYNAMIC parameter. 2 NISCS_CONV_BOOT< NISCS_CONV_BOOT controls whether a conversational boot is@ permitted during a remote system boot. The default value of 09 specifies that conversational boots are not permitted. 2 NISCS_LOAD_PEA0C NISCS_LOAD_PEA0 controls whether the NI-SCS port driver PEDRIVERD is loaded during system boot. The default of 0 specifies that the PEDRIVER is not loaded. 2 NIS CS_MAX_PKTSZA This parameter specifies an upper limit on the size, in bytes,C of the user data area in the largest packet sent by NISCA on any local area network (LAN).A NISCS_MAX_PKTSZ allows the system manager to change the packet@ size used for cluster communications on network communication< paths. PEDRIVER automatically allocates memory to support@ the largest packet size that is usable by any virtual circuitD connected to the system up to the limit set by this param eter. OnD Alpha and Integrity servers, to optimize performance, the defaultC value is the largest packet size currently supported by OpenVMS.A PEDRIVER uses NISCS_MAX_PKTSZ to compute the maximum amount of& data to transmit in any LAN packet:9 LAN packet size <= LAN header (padded Ethernet format)' + NISCS_MAX_PKTSZ= + NISCS checksum (only if data checking3 is enabled)& + LAN CRC or FCSA The actual packet size automatically used by PEDRIVER might beB smaller than the NISCS_MAX_PKTSZ limit for any of the following reasons:B o On a per-LAN path basis, if PEdriver determines that the LAN@ path between two nodes, including the local and remote LAN? adapters and intervening LAN equipment, can only convey a lesser size.? In other words, only nodes with large-packet LAN adapters@ connected end-to-end by large-packet LAN e quipment 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 nonpaged pool.D The actual memory allocation includes the required data structureD overhead used by PEDRIVER and the LAN drivers, in addition to the actual LAN packet size.> The following table shows the minimum NISCS_MAX_PKTSZ valueA required to use the maximum packet size supported by specified LAN types:: Type of LAN Minimum Value for NISCS_MAX_PKTSZ Ethernet 14982 FDDI 4382 (before Version 7.3)5 4396 (Version 7.3 and later) Gigabit Ethernet 8192 ATM 7606>  Note that the maximum packet size for some Gigabit Ethernet? adapters is larger than the maximum value of NISCS_MAX_PKTSZA (8192 bytes). See the LAN_FLAGS parameter for a description ofA how to enable jumbo frames on Gigabit Ethernet-that is, packet. sizes larger than those noted for Ethernet.@ On Alpha and Integrity servers, NISCS_MAX_PKTSZ is an AUTOGEN parameter. 2 NISCS_PORT_SERVA NISCS_PORT_SERV provides flag bits for PEDRIVER port services:= o Setting bits 0 and 1 (hex bitmask value 3) enables data checking.B o Setting bit 2 (hex bitmask value 4) enables data compression9 on all virtual channels (VCs) to nodes that support compression.2 The remaining bits are reserved for future use.= Starting with OpenVMS Version 7.3-1, you can use the SCACPB command SET VC/CHECKSUMMING to specify data checking on the VCsC to certain nodes. You can do this on a running system. (For moreE information, see the SCACP documentation in the VSI OpenVMS System) Management Utilities Reference Manual.@ Starting with OpenVMS Version 8.3, you can also use the SCACP@ command SET VC/COMPRESSION to specify data compression on theB on the VCs to certain nodes. You can use SCACP to enable eitherB data checking or data compression on a running system. (See the? SCACP documentation in the the VSI OpenVMS System ManagementA Utilities Reference Manual for more information. Also startingA with OpenVMS Version 8.3, the NISCS_PORT_SERV system parameterA is dynamic, that is, changing the setting of this parameter no@ longer requires a reboot. Furthermore, this parameter appliesB to all virtual circuits between the node on which it is set and other nodes in the cluster.: NISCS_PORT_SERV has the DYNAMIC and AUTOGEN attributes. 2 NOAUTOCONFIG> NOAUTOCONFIG controls whether all devices are automaticallyD configured when the system boots. The default value of 0 sets theB  system to automatically configure all devices. Set NOAUTOCONFIGA to 1 (no automatic configuration) only for debugging purposes.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so.' NOAUTOCONFIG is a DYNAMIC parameter. 2 NOCLUSTER? NOCLUSTER controls whether page read clustering is inhibited? when the system boots. Set NOCLUSTER to 1 (inhibit page read+ clustering) only for debugging purposes.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 NOPGFLSWP; If enabled, NOPGFLSWP disables swapping into page files.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 NPAGECALCA NPAGECALC controls whether the system automatically calculates0 the initial size for nonpaged dynamic mem ory.? VSI sets the default value of NPAGECALC to 1 only during the@ initial boot after an installation or upgrade. When the valueD of NPAGECALC is 1, the system calculates an initial value for theD NPAGEVIR and NPAGEDYN system parameters. This calculated value is8 based on the amount of physical memory in the system.D NPAGECALC's calculations do not reduce the values of NPAGEVIR andA NPAGEDYN from the values you see or set at the SYSBOOT prompt.@ However, NPAGECALC's calculation might increase these values.@ AUTOGEN sets NPAGECALC to 0. NPAGECALC should always remain 0D after AUTOGEN has determined more refined values for the NPAGEDYN" and NPAGEVIR system parameters. 2 NPAGEDYN@ NPAGEDYN sets the size of the nonpaged dynamic pool in bytes.> This figure is rounded down to an integral number of pages.@ NPAGEDYN establishes the initial setting of the nonpaged pool8 size, but the pool size can be increased dynamically.@ To set a value for this parameter, use AUTOGEN initially, and> then monitor the amount of space actually used with the DCL! command SHOW MEMORY/POOL/FULL.? For the benefit of OpenVMS VAX systems with limited physicalC memory, AUTOGEN logs a warning message in its report if NPAGEDYNB exceeds 10 percent of physical memory or if NPAGEVIR exceeds 33 percent of physical memory.? AUTOGEN also limits its own calculated value for NPAGEDYN toB 20 percent of physical memory and limits NPAGEVIR  to 50 percent? of physical memory. These calculated values are adequate for> most workstations and systems with 16 or fewer megabytes ofC physical memory. If your system requires a larger value, you canB override the AUTOGEN calculated values by setting higher values in MODPARAMS.DAT.= NPAGEDYN has AUTOGEN, FEEDBACK, GEN, and MAJOR attributes. 2 NPAGERADD (Alpha and Integrity servers) NPAGERAD specifies the total number@ of bytes of nonpaged pool that will be al located for ResourceA Affinity Domains (RADs) other than the base RAD. For platforms? that have no RADs, NPAGERAD is ignored. Notice that NPAGEDYN< specifies the total amount of nonpaged pool for all RADs.@ Also notice that the OpenVMS system might round the specified? values higher to an even number of pages for each RAD, whichB prevents the base RAD from having too little nonpaged pool. For@ example, if the hardware is an AlphaServer GS160 with 4 RADs: NPAGEDYN = 6291456 bytes NPAGERAD = 2097152 bytes8 In this case, the OpenVMS system allocates a total ofB approximately 6,291,456 bytes of nonpaged pool. Of this amount,A the system divides 2,097,152 bytes among the RADs that are not@ the base RAD. The system then assigns the remaining 4,194,304 bytes to the base RAD.& NOTE> The system actually rounds up to an even number of pages@ on each RAD. In addition, the base RAD is never assigned a@  value less than the smaller of the value of NPAGEDYN and 4 megabytes.B On AlphaServer GS series processors on OpenVMS systems prior toD Version 7.3-1, system managers frequently saw pool expansion thatA increasing NPAGEDYN did not reduce. This problem was caused by. leaving NPAGERAD at its default value of 0.? Starting with OpenVMS Version 7.3-1, when NPAGERAD is 0 (theC default), the system calculates a value to use for NPAGERAD with the following formula:$ Base RAD memory& NPAGEDYN * (1- --------------- )" Total memoryD This calculation gives more pool to the non-base RADs than before: and, therefore, reduces the expansion of non-base RADs." NPAGERAD has the GEN attribute. 2 NPAGEVIR= NPAGEVIR defines the maximum size to which NPAGEDYN can be> increased. If this value is too small, the system can hang.? If NPAGEVIR is too large, the result is a penalty of 4 bytes@ per  extra page on VAX and 8 bytes per extra page on Alpha and Integrity servers.? For the benefit of OpenVMS VAX systems with limited physicalC memory, AUTOGEN logs a warning message in its report if NPAGEDYNB exceeds 10 percent of physical memory or if NPAGEVIR exceeds 33 percent of physical memory.B AUTOGEN also limits its own calculated value for NPAGEDYN to 20@ percent of physical memory, and limits NPAGEVIR to 50 percent? of physical memory. These calculated values a re adequate for> most workstations and systems with 16 or fewer megabytes ofC physical memory. If your system requires a larger value, you canB override the AUTOGEN calculated values by setting higher values in MODPARAMS.DAT.+ NPAGEVIR has AUTOGEN and GEN attributes. 2 NPAG_AGGRESSIVEB Beginning with OpenVMS Version 8.2, the default values of NPAG_? AGGRESSIVE and NPAG_GENTLE are 100. A value of 100 turns offD both gentle and aggressive reclamation of nonpaged po ol lookasideB lists. In many cases, when pool reclamation moves small packetsA from the lookaside lists back to the variable list, the resultD is fragmentation of the variable list. This fragmentation appearsD as many small packets at the front of the variable list and a few( large packets at the end of the list.A When an allocation occurs for a packet that is larger than any> of the lookaside lists, the system must find a large enoughC packet on the variable list. When hea vily fragmented, the entire> variable list often must be searched to find a large enoughC packet. Because the variable list is kept in address order, whenB a large packet is deallocated, the entire list must be searched" again to deallocate the packet.= Under these conditions, system performance can be severelyC degraded. For this reason, VSI recommends that you turn off poolC reclamation but keep both NPAG_AGGRESSIVE and NPAG_GENTLE system parameters set to 100.*  NPAG_AGGRESSIVE is a DYNAMIC parameter. 2 NPAG_BAP_MAXB (Alpha and Integrity servers) NPAG_BAP_MAX is the size in bytesB of the bus addressable pool (BAP) that the system creates under normal circumstances. See also NPAG_BAP_MIN. 2 NPAG_BAP_MAX_PA? (Alpha and Integrity servers) NPAG_BAP_MAX_PA is the highestC physical address in megabytes that is allowed in bus addressable pool (BAP). 2 NPAG_BAP_MINB (Alpha and Integrity servers) NPAG_BAP_MIN is the size in bytesA of the bus addressable pool (BAP) that the system creates when. memory resources are unusually constrained. 2 NPAG_BAP_MIN_PA> (Alpha and Integrity servers) NPAG_BAP_MIN_PA specifies the> lowest physical address in megabytes that is allowed in bus addressable pool (BAP). 2 NPAG_GENTLED Beginning with Version 8.2, the default values of NPAG_AGGRESSIVE@ and NPAG_GENTLE are 100. A value of 100 turns off both gentle? and aggressive reclamatio n of nonpaged pool lookaside lists.@ In many cases, when pool reclamation moves small packets from? the lookaside lists back to the variable list, the result isA fragmentation of the variable list. This fragmentation appearsD as many small packets at the front of the variable list and a few( large packets at the end of the list.A When an allocation occurs for a packet that is larger than any> of the lookaside lists, the system must find a large enoughC packet on the varia ble list. When heavily fragmented, the entire> variable list often must be searched to find a large enoughC packet. Because the variable list is kept in address order, whenB a large packet is deallocated, the entire list must be searched" again to deallocate the packet.= Under these conditions, system performance can be severelyC degraded. For this reason, VSI recommends that you turn off poolC reclamation but keep both NPAG_AGGRESSIVE and NPAG_GENTLE system parameters set to 100.& NPAG_GENTLE is a DYNAMIC parameter. 2 NPAG_INTERVAL; NPAG_INTERVAL is the number of seconds between passes of$ nonpaged-pool gentle reclamation.( NPAG_INTERVAL is a DYNAMIC parameter. 2 NPAG_RING_SIZE> NPAG_RING_SIZE represents the number of entries in the ring buffer. 2 PAGED_LAL_SIZEA PAGED_LAL_SIZE sets the maximum size, in bytes, to use for theB page dynamic pool lookaside lists. Use of these lookaside listsD can reduce page d dynamic pool variable freelist fragmentation and> improve paged pool allocation and deallocation performance.D By default, PAGED_LAL_SIZE is set to 0, which disables the use of* the paged dynamic pool lookaside lists.= For environments experiencing paged pool variable freelist@ fragmentation a modest PAGED_LAL_SIZE, 512, has been adequateA to improve paged pool performance and reduce fragmentation. IfA this parameter is made large and later decreased in size, someD pag ed pool packets can be left unused until the parameter is madeC larger again, or the lookaside lists are reclaimed from due to aC paged pool shortage. The paged dynamic pool lookaside lists willC not occupy more than three-quarters of the available paged pool.9 PAGED_LAL_SIZE has DYNAMIC, GEN, and MAJOR attributes. 2 PAGFILCNTD On Alpha and Integrity servers, beginning in OpenVMS Version 7.3, this parameter is obsolete.2 PAGFILCNT has the GEN attribute on VAX systems. 2 PAGTBLPFCC PAGTBLPFC specifies (in pages) the maximum number of page tables; to read to satisfy a fault for a nonresident page table.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 PAMAXPORTC PAMAXPORT specifies the maximum port number to be polled on eachC CI and DSSI. The CI and DSSI port drivers poll to discover newlyD initialized ports or the absence/failure of p reviously 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 ignored.D The default for this parameter is 15 (poll for all possible portsC 0 through 15). VSI recommends that you set this parameter to the' same value on each cluster computer.$ PAMAXPORT is a DYNAMIC parameter. 2 PANOPOLLC Disables CI and DSSI polling for ports if set to 1. (The default A is 0.) When PANOPOLL is set, a computer does not discover thatC another computer has shut down or powered down promptly and doesA not discover a new computer that has booted. This parameter is@ useful when you want to bring up a computer detached from the- rest of the cluster for checkout purposes.C PANOPOLL is functionally equivalent to uncabling the system fromC the DSSI or star coupler. This parameter does not affect OpenVMS! Cluster communications by LAN.? The default value of 0 is the normal setting and is requiredA if you are booting from an HSC controller or if your system isD joining an OpenVMS Cluster. This parameter is ignored if no CI or. DSSI devices are configured on your system.# PANOPOLL is a DYNAMIC parameter. 2 PANUMPOLL> PANUMPOLL establishes the number of CI and DSSI ports to beA polled each polling interval. The normal setting for PANUMPOLL is 16.B On systems with less powerful CPUs, the parameter may be usefulB in applications sensitive to the amount of contiguous time thatD the system spends at IPL 8. Reducing PANUMPOLL reduces the amount= of time spent at IPL 8 during each polling interval, while@ increasing the number of polling intervals needed to discover new or failed ports.@ If CI or DSSI devices are not configured on your system, this parameter is ignored.$ PANUMPOLL is a DYNAMIC parameter. 2 PAPOLLINTERVALA Specifies, in seconds, the pollin g interval the CI port driverB uses to poll for a newly booted computer, a broken port-to-port0 virtual circuit, or a failed remote computer.C This parameter trades polling overhead against quick response toD virtual circuit failures. VSI recommends that you use the default value for this parameter.B VSI recommends that you set this parameter to the same value on each cluster computer.) PAPOLLINTERVAL is a DYNAMIC parameter. 2 PAPOOLINTERVAL? Specifies,  in seconds, the interval at which the port driverB checks available nonpaged pool after a pool allocation failure.D This parameter trades faster response to pool allocation failuresB against increased polling overhead. VSI recommends that you use( the default value for this parameter.@ If CI or DSSI devices are not configured on your system, this parameter is ignored.* PAPOOLLINTERVAL is a DYNAMIC parameter. 2 PASANITYC PASANITY controls whether the CI and DSSI  port sanity timers areD enabled to permit remote systems to detect a system that has beenC hung at IPL 8 or above for 100 seconds. It also controls whetherA virtual circuit checking gets enabled on the local system. The8 TIMVCFAIL parameter controls the time (1-99 seconds).A PASANITY is normally set to 1 and should be set to 0 only when@ you are debugging with XDELTA or planning to halt the CPU for" periods of 100 seconds or more.> PASANITY is only semidynamic. A new v alue 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. 2 PASTDGBUFD The number of datagram receive buffers to queue initially for theC cluster port driver's configuration poller. The initial value is/ expanded during system operation, if needed.0 Memory Channel devices ignore this parameter.% PASTDGBUF is an AUTOGEN parameter. 2 PASTIMOUT= The  basic interval at which the CI port driver wakes up toC perform time-based bookkeeping operations. It is also the period> after which a timeout is declared if no response to a start( handshake datagram has been received.@ If CI or DSSI devices are not configured on your system, this parameter is ignored./ The default value should always be adequate.$ PASTIMOUT is a DYNAMIC parameter. 2 PE1-6D PE1, PE2, PE3, PE4, PE5, PE6 are reserved for VSI use only. TheseD  parameters are for cluster algorithms and their usages can changeC from release to release. VSI recommends using the default values for these special parameters. 2 PFCDEFAULT? On Alpha and Integrity servers during execution of programs,= PFCDEFAULT controls the number of image pagelets read fromB disk per I/O operation when a page fault occurs. The PFCDEFAULTA maximum default value is 2032 512-byte pagelets (127 8192-byte% Alpha and Integrity server pages).?  The read I/O operations can take place from an image file orA from the page file. The actual size of the cluster can be lessC than PFCDEFAULT, depending on the size of image sections and the pattern of page references.C The value should not be greater than one-fourth the default sizeA of the average working set to prevent a single page fault fromA displacing a major portion of a working set. Too large a value@ for PFCDEFAULT can hurt system performance. PFCDEFAULT can be C 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 and Integrity servers) PFN_COLOR_COUNT specifies theB number of buckets (colors) into which all members of the zeroedC page list and all unencumbered members of the free page list areD sorted. OpenVMS Alpha systems might derive a preferred page color@ from a request to map a given virtual page and attempt to mapB that virtual page to a PFN of matching "color." This results inC less variance in which cache blocks are used when accessing thatB page. This might or might not improve performance, depending on the application.A This special parameter is use by VSI and is subject to change.E Do not change this parameter unless VSI recommends that you do so.C If you increase this parameter, you must also increase the ZERO_ LIST_HI system parameter. 2 PFRATH@ PFRATH specifies the page fault rate above which the limit of@ a working set is automatically 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 decrease their limits. > On Alpha and Integrity servers, the default value is 8 page faults every 10 seconds.< PFRATH has the DYNAMIC and MAJOR attributes. On Alpha andB Integrity servers, PFRATH also is an AUTOGEN-altered parameter. 2 PFRATL@ PFRATL specifies the page fault rate below which the limit of@ a working set is automatically decreased. The unit of measureA is the number of faults per 10 seconds of processor time. At aD setting of 1, for example, the system automatically decreases theB limit of a working set if it is faulting less than 1 page every 10 seconds.? 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 and Integrity servers) PHYSICAL_MEMORY specifies theC amount of physical memory available for use. The default settingD is -1, which equates to all memory in the system. Decreasing this@ parameter allows you to test smaller configurations of memory* without having to remove memory boards.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so.D Because of hardware configuration requirements on the AlphaServer@ ES47/ES80/GS1280 systems, VSI does not recommend altering theC setting of the system parameter PHYSICAL_MEMORY from its default@  setting of -1. Artificially reducing the amount of memory can2 produce unpredictable results on these systems.+ PHYSICAL_MEMORY is an AUTOGEN parameter.) PHYSICALPAGES is an AUTOGEN parameter. 2 PIOPAGES@ PIOPAGES specifies the size of the process I/O segment, which= holds data structures and buffer pool space for RMS to useB when it handles I/O that involves process-permanent files. OnceD PIOPAGES is reset in SYSGEN, any new process receives the changed value.A Beginning with OpenVMS Version 7.2, the default value has been@ raised to 575. The 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.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so.0 PIOPAGES is an AUTOGEN and DYNAMIC parameter. 2 PIXSCANC PIXSCAN specifies the num ber of process index slots scanned eachB second for computable or computable-outswapped processes. These? processes receive an automatic priority boost for 1 quantum,D unless the priority of the currently executing process is greaterC than 15. The priority boost is done to avoid potential deadlocks on the system.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so./ PIXSCAN is an AUTOGEN and  DYNAMIC parameter. 2 POOLCHECKD This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so.= POOLCHECK is used to investigate frequent and inexplicableA failures in a system. When POOLCHECK is enabled, pool-checking> routines execute whenever pool is deallocated or allocated.? Two loadable forms of SYSTEM_PRIMITIVES.EXE are available at@ boot time. The default image, which contains no pool-chec king? 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 parameter to 1 has the effect of setting> POOLCHECK to %X616400FF. For further information about poolA checking, see the OpenVMS VAX Device Support Manual, (which is archived).A POOLCHECK is a DYNAMIC parameter. However, for a change in itsA value to have any effect, POOLCHECK must be non-0 at boot time= (to load the monitoring version of SYSTEM_PRIMITIVES.EXE). 2 POOLPAGING; POOLPAGING enables (1) paging of pageable dynamic pool.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 POWEROFF@ POWEROFF enables or disables software requests to the consoleB firmware to remove power from the system. This parameter shouldA normally be turned ON (1) to allow 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 the default limit on the number of pending ASTs? for a process created by the Create Process ($CREPRC) system, service or the DCL command RUN (Process).1 PQL_DASTLM has the DYNAMIC and GEN attributes. 2 PQL_DBIOLM? PQL_DBIOLM sets the default buffered I/O count limit for the? number of outstanding buffered I/O operations permitted to aD process created by the Create Process ($CREPRC) system service or! the DCL command RUN (Process).1 PQL_DBIOLM has the DYNAMIC and GEN attributes. 2 P QL_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_DCPULM specifies the time limit in increments of 10 milliseconds.C The default value of 0 imposes no limit on CPU time usage and is2 typically the correct value for this parameter.1 PQL_DCPULM has the DYNAMIC and GEN attributes. 2 PQL_DDIOLM= PQL_DDIOLM sets the default direct I/O limit for a process@ created by the Create Process ($CREPRC) system service or the DCL command RUN (Process).1 PQL_DDIOLM has the DYNAMIC and GEN attributes. 2 PQL_DENQLMB PQL_DENQLM sets the default  enqueue limit for a process createdD by the Create Process ($CREPRC) system service or the DCL 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 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 the Create Process ($CREPRC) sys"tem service or the DCLC command RUN (Process). VSI 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 DYNAMIC and GEN attributes. #2 PQL_DTQELMB PQL_DTQELM sets the default number of timer queue entries for aD process created by the Create Process ($CREPRC) system service or! the DCL command RUN (Process).1 PQL_DTQELM has the DYNAMIC and GEN attributes. 2 PQL_DWSDEFAULTA PQL_DWSDEFAULT sets the default working set size for a processD created by the Create Process ($CREPRC) system service or the DCL command RUN (Process).5 PQL_DWSDEFAULT has the AUTOGEN and GEN attributes. 2 PQL$_DWSEXTENTB PQL_DWSEXTENT sets the default working set extent for a processD created by the 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, DYNAMIC, and GEN attributes. 2 % PQL_MASTLMD PQL_MASTLM sets a minimum limit on the number of pending ASTs forC 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 DYNAMIC and GEN attributes. 2 PQL_MBYTLM&D 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_M'DIOLM= 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_MENQLMD PQL_MENQLM sets the minimum limit on the number of locks that canC be queued at one time by a process created by the Create Process= ($CREPRC) system service or the DCL command RUN (Process).1 PQL_MENQLM has the DYNAMIC and GEN attributes. ( 2 PQL_MFILLMD PQL_MFILLM sets the minimum open file limit for a process createdD by the 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_MJTQUOTA is a DYNAMIC parameter. 2 PQL_MPGFLQUOTAB O )n VAX systems, PQL_MPGFLQUOTA sets the minimum page file quota? for a process created by the Create Process ($CREPRC) systemE service or the DCL command RUN (Process). VSI recommends that this. parameter be no smaller than PQL_MWSEXTENT.B On Alpha and Integrity servers, PQL_MPGFLQUOTA sets the minimumA pagelet file quota for a process created by the Create Process= ($CREPRC) system service or the DCL command RUN (Process).< PQL_MPQFLQUOTA has the DYNAMIC and GEN attributes*. On VAX8 systems, PQL_MPQFLQUOTA is also an AUTOGEN parameter. 2 PQL_MPRCLM= PQL_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 service or! the DCL command RUN (Process).1 + PQL_MTQELM has the DYNAMIC and GEN attributes. 2 PQL_MWSDEFAULTA PQL_MWSDEFAULT sets the minimum default working set size for aD process created by the Create Process ($CREPRC) system service or! the DCL command RUN (Process).D This value overrides a smaller quantity that is set for a user in AUTHORIZE.5 PQL_MWSDEFAULT has the AUTOGEN and GEN attributes. 2 PQL_MWSEXTENTB PQL_MWSEXTENT sets the minimum working set extent for a processD created by the ,Create Process ($CREPRC) system service or the DCL command RUN (Process).< This value overrides a smaller quantity set for a user in AUTHORIZE.> PQL_MWSEXTENT has the AUTOGEN, DYNAMIC, and GEN attributes. 2 PQL_MWSQUOTA@ PQL_MWSQUOTA sets the minimum working set quota for a processD created by the Create Process ($CREPRC) system service or the DCL command RUN (Process).< This value overrides a smaller quantity set for a user in AUTHORIZE.= PQL_MWS-QUOTA 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 systems or servers as they appear.@ PRCPOLINTER .VAL is a DYNAMIC parameter. On Alpha and Integrity8 servers, PRCPOLINTERVAL is also an AUTOGEN parameter. 2 PRIORITY_OFFSET@ PRIORITY_OFFSET specifies the difference in priority requiredC by the scheduler for one process to preempt the current process.? A value of 2, for example, means that if the current processA is executing at priority 1, a computable process at priority 2A or 3 is not allowed to preempt the current process. However, a@ priority 4 or higher process /can preempt the current process.D This mechanism affects only normal priority (0-15) processes. The default value is 0.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 PROCSECTCNTD PROCSECTCNT sets the number of section descriptors that a processC can contain. Each section descriptor increases the fixed portion% of the process header by 32 bytes.@ Set a value greater than the ma0ximum 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 PU_OPTIONS+ PU_OPTIONS is reserved for VSI use only. 2 QDSKINTERVAL@ QDSKINTERVAL establishes, in seconds, the disk quorum polling$ interval. The default value is 3. 2 QDSKVOTESB QDSKVOTES specifies the number of votes contributed by a quorum disk in a cluster. 2 QUA 1NTUM! QUANTUM defines the following:@ o Processor time: maximum amount of processor time a processC can receive before control passes to another process of equal' priority that is ready to computeA o Balance set residency: minimum amount of service a compute-< state process must receive before being swapped out to secondary storage= QUANTUM has the DYNAMIC and MAJOR attributes. On Alpha and= Integrity servers, QUANTUM also has the AUTOGEN attribute2. 2 RAD_SUPPORT4 RAD_SUPPORT enables RAD-aware code to be executed< on systems that support Resource Affinity Domains (RADs);8 for example, AlphaServer GS160 systems and Integrity = cell-based servers or BL8x0c i2 servers. A RAD is a set of; hardware components (CPUs and memory) with common access characteristics.< Bits are defined in the RAD_SUPPORT parameter as follows:6 RAD_SUPPORT (default is 207 for Alpha and 10944667  for Integrity servers)6 _____ 3______________________________________________ 3 2 2 2 2 1 13 1 8 7 4 3 6 5 8 7 04 +-----+-----+-----------+-----------+-----------+4 |00|00| skip|ss|gg|ww|pp|00|00|00|00|0p|df|cr|ae|4 +-----+-----+-----------+-----------+-----------+- Bit 0 (e): Enable - Enables RAD supportD Bit 1 (a): Affinity - Enables Soft RAD Affinity (SRA) schedulingE Also enables the interpretation of the skip& 4 bits, 24-27.? Bit 2 (r): Replicate - Enables system-space code replication4 Bit 3 (c): Copy - Enables copy on soft fault? Bit 4 (f): Fault - Enables special page fault allocation@ Also enables the interpretation of the1 allocation bits, 16-23.) Bit 5 (d): Debug - Reserved to VSI8 Bit 6 (p): Pool - Enables per-RAD non-paged pool) Bits 7-15: - Reserved to VSIE Bits 16-23: 5 - If bit 4 is set, bits 16-23 are interpreted% as follows:? Bits 16,17 (pp): Process = Pagefault on process (non global)# pages? Bits 18,19 (ww): Swapper = Swapper's allocation of pages for' processes7 Bits 20,21 (gg): Global = Pagefault on global pages= Bits 22,23 (ss): System = Pagefault on system space pages Encodings for pp, ww, gg, ss:: Current (0) - allocate PFNs from t6he current CPU's RAD< Random (1) - allocate PFNs using the "random" algorithmB Base (2) - allocate PFNs from the operating system's "base" RADC Home (3) - allocate PFNs from the current process's home RADG If bits 16-23 are 0, the defaults for pp, ww, gg, ss are interpreted as follows: Process = home RAD= Swapper = current RAD (also sets home RAD for process) Global = random RAD System = base RAD> Bits 24-27: 7 - If bit 1 is set, bits 24-27 are interpretedB as a skip count value (power of 2). Example: If? bits 24-27 contain a 3, the skip count is 8.C If bits 24-27 contain a 5, the skip count is 32.A If bits 24-27 are 0, the default of 16 is used% as the skip count." Bits 28-31: - Reserved to VSIA For more information about using OpenVMS RAD features, see the> OpenVMS Alpha Galaxy and Partitio8ning Guide or VSI OpenVMS 7 Version 8.4 New Features and Documentation Overview.% RAD_SUPPORT has the GEN attribute.< REALTIME_SPTS has the DYNAMIC, GEN, and MAJOR attributes. 2 RECNXINTERVAL> RECNXINTERVAL establishes the polling interval, in seconds,; during which to attempt reconnection to a remote system.? RECNXINTERVAL is a DYNAMIC parameter. On Alpha and Integrity7 servers, RECNXINTERVAL is also an AUTOGEN parameter. 2 RESALLOC< RESALLOC contro 9ls whether resource allocation checking isA performed. The default value of 0 disables resource allocation checking.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 RESHASHTBLB RESHASHTBL defines the number of entries in the lock managementC resource name hash table. Each entry requires 4 bytes. A typicalC tuning goal is to have the RESHASHTBL parameter about four timesB larger :than the total number of resources in use on the system.B Managers of systems with memory 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 RJOBLIMD RJOBLIM defines the maximum number of remote terminals allowed in the system at any one time." RJOBLIM is a DYNAMIC parameter. 2 RMS_CONPOLICYA RMS_CONPOLICY specifies the policy to b ;e used for dealing withA high-contention write-shared files. This dynamic parameter canC be used to ensure fairness between lock conversions and new lock requests.% Possible values are the following: Value Explanation@ NEVER (Default) Never use the higher overhead option@ to improve fairness for any write-shared files; accessed on the system; minimal overhead.? SOMETIMES Use this option for fairer bucket acce <ss (butA higher overhead) to any write-shared files withA global buffers enabled that are accessed on the system.? ALWAYS Use this option for fairer bucket access (but< higher overhead) to all write-shared files) accessed on the system.B You can set this system parameter with the DCL command SET RMS_C DEFAULT/SYSTEM/CONTENTION_POLICY=value and display the parameter) with the DCL comm=and SHOW RMS_DEFAULT.( RMS_CONPOLICY is a DYNAMIC parameter. 2 RMSD*B RMSD1, RMSD2, RMSD3, RMSD4, RMSD5, RMSD6, and RMSD7 are special# parameters reserved for VSI use. RMSD* parameters are DYNAMIC. 2 RMS_DFLRLD This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so.$ RMS_DFLRL is a DYNAMIC parameter. 2 RMS_DFMBCA RMS_DFMBC specifies a default multiblock count only for rec>ord< 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 is an AUTOGEN and DYNAMIC parameter. 2 RMS_DFMBFIDXA RMS_DFMBFIDX establishes the default RMS multibuffer count forD indexed sequential disk operations. This value defines the number? of I/O buffers that RMS all?ocates 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 parameter with SHOW RMS_ DEFAULT.4 RMS_DFMBFIDX is an AUTOGEN and DYNAMIC parameter. 2 RMS_DFMBFRELA RMS_DFMBFREL establishes the default RMS multibuffer count forA relative disk operations. This value defines th@e 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. 2 RMS_DFMBFSDKA RMS_DFMBFSDK establishes the default RMS multibuffer count forC sequential disk operations. This value defines the number of I/O8 buffers that RMS allocates for sequential disk files.@ The defAault 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_ DEFAULT.4 RMS_DFMBFSDK is an AUTOGEN and DYNAMIC parameter. 2 RMS_DFMBFSMTA RMS_DFMBFSMT establishes the default RMS multibuffer count forA magnetic tape operations. This value defines the number of I/O6 bufBfers 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 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. C4 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? 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 li Dstener (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 file. In other words,B the largest record that can be transferred must be less than or. equal to RMS_DFNBC multiplied by 512 bytes.9 You can set this system parameter with the DCL commandB SET RMS_DEFAULT/SYSTEM and Edisplay the parameter with SHOW RMS_ DEFAULT.1 RMS_DFNBC is an AUTOGEN and DYNAMIC parameter. 2 RMS_EXTEND_SIZE@ RMS_EXTEND_SIZE specifies the number of blocks by which filesD are extended as they are written. This number should be chosen toD balance the amount of extra disk space wasted at the ends of eachD file against the performance improvement provided by making large extents infrequently.B When small disk quotas are used, specify a small number such asD F the disk cluster size to prevent the user's disk quota from beingC consumed. If the value of 0 is used, RMS allocates large extentsB and truncates the file back to its actual usage when it closes.9 You can set this system parameter with the DCL commandB SET RMS_DEFAULT/SYSTEM and display the parameter with SHOW RMS_ DEFAULT.* RMS_EXTEND_SIZE is a DYNAMIC parameter. 2 RMS_FILEPROTA RMS_FILEPROT determines the default file protection for systemC processes such Gas those that create the error log, operator log,A and job controller. It also determines default file protectionC for processes created by the job controller (all interactive and batch processes).@ Because a process always inherits its default file protectionA from its creator process, RMS_FILEPROT determines default fileC protection only for users who do not execute the DCL command SETA PROTECTION/DEFAULT in their login command procedures or during interactive sessiHons.@ The protection is expressed as a mask. (See the discussion of@ the $CRMPSC system service in the VSI OpenVMS System ServicesD Reference Manual for more information about specifying protection: masks.) By default, the mask is 64000 (decimal) or FA00< (hexadecimal), which represents the following protection: (S:RWED,O:RWED,G:RE,W:) 2 RMS_HEURISTICD This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends I that you do so.( RMS_HEURISTIC is a DYNAMIC parameter. 2 RMS_PATH_TMOB The RMS path cache in each process holds entries that translate? DVI+DID+name to new DVI+DID. These are used to greatly speed? up directory path walks. Cache entries representing ordinaryA directory lookups are invalidated through the volume directory= sequence number mechanism (UDB$L_DIRSEQ), which is clocked@ on every volume dismount and each time a directory is deleted< or renamed. HoweverJ, there is no convenient mechanism for> invalidating a cache entry that represents a symlink, whoseA interpretation is affected by logical names or modification of@ the symlink. The only way to eliminate stale cache entries isC with a timeout. This parameter is the system-wide cache timeout. Special values:% 1 = don't keep cache entries' -1 = keep cache entries forever$RMS_PATH_TMO is a DYNAMIC parameter. 2 RMS_PROLOGUEA RMS_PROLOGUE specifies the de Kfault 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, and 3 specifiesD Prologue 3. The RMS prologues are described in the OpenVMS Record( Management Services Reference Manual.' RMS_PROLOGUE is a DYNAMIC parameter. 2 RMS_SEQFILE_WBH? (Alpha and Integrity servers) RMS_SEQFILE_WBH can enable the? RMS writebehind f Leature as a system default for any unshared@ sequential disk file if the file is opened for image I/O withC write access specified. The possible settings are the following: Setting DescriptionC 0 (default) Do not enable writebehind feature. Preserve prior@ behavior of using writebehind only if the user@ requests it by setting RAB$V_WBH in RAB$L_ROP.? 1 Enable writebehind feature as system default,@ Mincluding the allocation of at least two local buffers.* RMS_SEQFILE_WBH is a DYNAMIC parameter. 2 S0_PAGING, S0_PAGING controls paging of system code:> o Setting bit 0 disables paging of all Exec code and data.= o Setting bit 1 disables paging of all RMS code and data.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 S2_SIZEC (Alpha and Integrity serv Ners) S2_SIZE is the number of megabytes@ to reserve for S2 space. This value does not include the size* required for extended file cache (XFC). 2 SAVEDUMPA If the dump file is saved in the page file, SAVEDUMP specifiesB whether the page file is saved until the dump file is analyzed.A The default value 0 specifies that the page file should not be@ retained. A value of 1 specifies that the dump written to the? page file should be retained until either copied or releasedO using the SDA utility. 2 SCHED_FLAGS2 Special DYNAMIC parameter reserved for VSI use. 2 SCH_HARD_OFFLDD The scheduler hard off-load parameter is a CPU bitmask parameter.? The bits correspond to CPU IDs. For any bit set, the OpenVMS? scheduler does not schedule processes on this CPU unless theD process has hard affinity set for the CPU. In addition, a process> with the PRIMARY capability requirement will ignore the bit$ corresponding to the primary CPU.)P SCH_HARD_OFFLD is a DYNAMIC parameter. 2 SCH_SOFT_OFFLDD The scheduler soft off-load parameter is a CPU bitmask parameter.? The bits correspond to CPU IDs. For any bit set, the OpenVMS= scheduler tries to avoid scheduling processes on this CPU.< However, if no other idle CPUs exist, processes are still scheduled on this CPU.) SCH_SOFT_OFFLD is a DYNAMIC parameter. 2 SCSBUFFCNTA On VAX systems, SCSBUFFCNT is the number of buffer descriptorsB configuQred for all systems communication architecture (SCA). IfD an SCA device is not configured on your system, this parameter isA ignored. Generally speaking, each data transfer needs a buffer> descriptor and thus the number of buffer descriptors can be? a limit on the number of possible simultaneous I/Os. Various= performance monitors report when a system is out of buffer? descriptors for a given workload which is an indication that@ a larger value for SCSBUFFCNT is worth considerRing. Note thatD AUTOGEN provides feedback for this parameter on VAX systems only.D On Alpha and Integrity servers, the system communication servicesD (SCS) buffers are allocated as needed, and SCSBUFFCNT is reserved for VSI use only.< SCSBUFFCNT has the AUTOGEN, FEEDBACK, and GEN attributes. 2 SCSFLOWCUSH? Specifies the lower limit for receive buffers at which pointB system communication services (SCS) starts to notify the remoteB SCS of new receive buffers. For e Sach connection, SCS tracks theD number of receive buffers available. SCS communicates this numberD to the SCS at the remote end of the connection. However, SCS doesB not need to do this for each new receive buffer added. Instead,C SCS notifies the remote SCS of new receive buffers if the number< of receive buffers falls as low as the SCSFLOWCUSH value.> The default value is adequate on most systems. If a systemsB communication architecture (SCA) port is not configured on your% T system, this parameter is ignored.& SCSFLOWCUSH is a DYNAMIC parameter. 2 SCSI_ERROR_POLL? If an error occurs while a particular initiator is accessing@ a SCSI device, that error is latched for all other initiatorsB and is not unlatched and reported to the other initiators until@ the next time they access the device. Therefore, if the other> initiators do not access the device in a timely manner, theA reporting of the error can be greatly delayed, which can cause U confusion.? The purpose of SCSI_ERROR_POLL is to cause OpenVMS to send a@ SCSI Test Unit Ready command every hour to each SCSI disk, in@ an attempt to force latched errors to become unlatched and toB be reported immediately. SCSI_ERROR_POLL has a default value ofC 1. It can, however, be set to 0 by the user in order to stop the error polling activity.A The parameter affects SCSI disks connected by Fibre Channel asB well as parallel SCSI. If the disk has multiple patVhs, then theB error polling is performed on all non-served paths to the disk.A Tapes and other non-disk devices are not subject to this error0 polling, regardless of the parameter setting.* SCSI_ERROR_POLL is a DYNAMIC parameter.& SCSI_NOAUTO is a DYNAMIC parameter. 2 SCSICLUSTER_P[1-4]: (Alpha only) SCSICLUSTER_P[1-4] parameters allow non-HP1 peripherals (CPU-lookalikes) in SCSI clusters.D This special parameter is use by VSI and is subject to change. DoB nWot change this parameter unless VSI recommends that you do so. 2 SCSMAXDG/ This parameter is reserved for VSI use only." SCSMAXDG has the GEN attribute. 2 SCSMAXMSG/ This parameter is reserved for VSI use only.# SCSMAXMSG has the GEN attribute. 2 SCSNODED SCSNODE specifies the name of the computer. This parameter is not dynamic.C Specify SCSNODE as a string of up to six characters. Enclose the string in quotation marks.& X NOTE> The maximum size of six characters is strictly enforced.? SYSBOOT truncates the value of SCSNODE if the size of the: system parameter is set to more than six characters.D If the computer is in an OpenVMS Cluster, specify a value that is= unique within the cluster. Do not specify the null string.C If the computer is running DECnet for OpenVMS, the value must be$ the same as the DECnet node name.. SCSNODE has the AUTOGEN and GEN attribuYtes. 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 identificationZ 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 VSI for future use.& SCSSYSTEMIDH has the GEN attribute. 2 SECURITY_POLICY7 SECURITY_POLICY allows a system to run in a C2 or B17 configuration and to subset out particular pieces of= functionality-to exclude functionality that is outside the< evaluated configuration or to preserve compatibility with\A previous versions of the operating system. See the VSI OpenVMSD Guide to System Security for further information about the C2 and B1 evaluated configurations." The following bits are defined: Bit Description 0 Obsolete.> 1 Allows multiple user names to connect to DECW$SERVER.C 2 Allows unevaluated DECwindows transports (such as TCP/IP).7 3 Allows $SIGPRC and $PRCTERM to span job trees.@ 4 Allows security profile changes to prot]ected objects onA a local node when the object server is absent and cannot5 update the cluster database VMS$OBJECTS.DAT.B 5 Allows creation of protected objects on a local node whenB the object server is absent and cannot update the cluster" database VMS$OBJECTS.DAT.@ 6 Allows SPAWN or LIB$SPAWN commands in CAPTIVE accounts. 7 Reserved to VSI. 8 Reserved to VSI.@ 9 Disables password synchronizations among ACME agent ^s on? a systemwide pasis. This is functionally equivalent to@ the SYS$SINGLE_SIGNON logical name bit mask value 4 for LOGINOUT.D 10 Allows privileged applications to successfully authenticateD a user whose principal name maps to a SYSUAF record that isC either expired or whose modal restrictions would otherwise- prevent the account from being used.A A SYSUAF record that is disabled or password-expired (inB the case _of traditional OpenVMS authentication) cannot be! bypassed in this manner.= An application with SECURITY privilege specifies theA SYS$ACM ACME$M_NOAUTHORIZE function modifier to override authorization checks.@ 11 Allows any record in the SYSUAF file to be mapped using! external authentication.C 12 Allows intrusions on a clusterwide or local basis. (If the5 bit is cleared, intrusions are clusterwide.) 13 Reserved to ` VSI.; 14 Allows the internal name and backlink of files andA directories to be read if the user has either execute orD read access to the file or directory. If this bit is clear,! read access is required.B Setting this bit allows the full POSIX pathname of a fileB or directory to be displayed when some of the directoriesB in the path are execute-only to the user. This feature is0 required in the following environments:' a o POSIX pathnames are in use.> o The BASH shell or other GNV components are in use.= o Applications are using the realpath(), getcwd(),A getpwnam(), and related C runtime library functions.? The default value of 7 preserves compatibility with existingC DECwindows Motif behavior. A value of 0 disables all unevaluated configurations. 2 SETTIMEC SETTIME enables (1) or disables (0) solicitation of the time ofD day each time theb 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 VSI OpenVMS DCL Dictionary). 2 SHADOW_D1-D53 Special DYNAMIC parameters reserved for VSI use. 2 SHADOW_ENABLE* Special parameter reserved for VSI use. 2 SHADOWINGB SHADOWING loads the host-based volume schadowing driver. See VSIB Volume 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 Host-based volume shadowing enabled; SHDRIVER is loaded.? Host-based volume shadowing provides shadowing of allD disks located on a standalone system or an OpenVMS C dluster system. 2 SHADOW_HBMM_RTC> (Alpha and Integrity servers) SHADOW_HBMM_RTC specifies, inA seconds, how frequently each shadow set on this system has itsA modified block count compared with the reset threshold. If theC modified block count exceeds the reset threshold, the bitmap forB that shadow set is zeroed. This comparison is performed for all< shadow sets mounted on the system that have HBMM bitmaps.B The reset threshold is specified by the RESET_TeHRESHOLD keyword6 in the /POLICY qualifier of the SET SHADOW command.> When the comparison is made, the modified block count might? exceed the reset threshold by a small increment or by a muchA larger amount. The difference depends on the write activity to3 the volume and on the setting of this parameter.* SHADOW_HBMM_RTC is a DYNAMIC parameter. 2 SHADOW_MAX_COPY? The value of SHADOW_MAX_COPY controls how many parallel copy' threads are allowed on a given node. f> Carefully consider the needs of each shadowed node when you? set this parameter. Too high a value for SHADOW_MAX_COPY canB affect performance by allowing too many copy threads to operateB in parallel. Too low a value unnecessarily restricts the number1 of threads your system can effectively handle.B See VSI Volume Shadowing for OpenVMS for more information about2 setting system parameters for volume shadowing.: SHADOW_MAX_COPY has the AUTOGEN and DYNAMIC attributes. g 2 SHADOW_MAX_UNITC SHADOW_MAX_UNIT specifies the maximum number of shadow sets thatA can exist on a system. The setting must be equal to or greater? than the number of shadow sets you plan to have on a system.C Dismounted shadow sets, unused shadow sets, and shadow sets with@ no write bitmaps allocated to them are included in the total.& NOTEA Review this default carefully. The setting must be equal to@ or greater than the nu hmber of shadow sets you plan to have@ on a system. If you attempt to mount more shadow sets than@ the number specified by SHADOW_MAX_UNIT, the MOUNT command@ will fail. Dismounted shadow sets, unused shadow sets, and= shadow sets with no write bitmaps allocated to them are0 included in the count for SHADOW_MAX_UNIT.D On Alpha and Integrity servers, the default value for this system9 parameter is 500, which consumes 24 KB of main memory.B If you do not plan ito use Volume Shadowing for OpenVMS, you canD change the setting to its minimum of 10 (which consumes 480 bytesD of main memory). Setting the default to its minimum frees up 23.5A KB of main memory on an OpenVMS Alpha or Integrity servers andD 4.5 KB of main memory on a VAX system. (The maximum value of this parameter is 10,000.)= This system parameter is not dynamic; that is, a reboot is( required when you change the setting. 2 SHADOW_MBR_TMOA SHADOW_MBR_TMO cont jrols 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 decikmal from 1 to 65,535, during which recoveryA of a repairable shadow set is attempted. If you do not specifyC a value or if you specify 0, the default delay of 120 seconds is used.D Because SHADOW_MBR_TMO is a dynamic parameter, you should use the@ SYSGEN command WRITE CURRENT to permanently change its value.) SHADOW_MBR_TMO is a DYNAMIC parameter. 2 SHADOW_PSM_RDLYC When a copy or merge operation is needed on a shadow set that isA mounted on more than one systlem, the shadowing driver attemptsC to perform the operation on a system that has a local connectionB to all the shadow set members. Shadowing implements the copy or@ merge operation by adding a time delay based on the number ofB shadow set members that are MSCP-served to the system. No delayC is added for local members; a system with all locally accessibleA shadow set members usually performs the copy or merge before aB system on which one or more members is served (and theref more is delayed) does.@ SHADOW_PSM_RDLY allows the system manager to adjust the delayD that shadowing adds. By default, the delay is 30 seconds for eachC MSCP-served shadow set member. The valid range for the specified% delay is 0 through 65,535 seconds.A When a shadow set is mounted on a system, the value of SHADOW_C PSM_RDLY is used as the default shadow set member recovery delayA for that shadow set. To modify SHADOW_PSM_RDLY for an existing? shadow set, see then SET SHADOW/ /RECOVERY_OPTIONS=DELAY_PER_? SERVED_MEMBER=n command in VSI Volume Shadowing for OpenVMS. 2 SHADOW_REC_DLY (Alpha and Integrity servers)A The value of the SHADOW_REC_DLY parameter specifies the length? of time a system waits before it attempts to manage recovery< operations on shadow sets that are mounted on the system.= A shadow set is said to need recovery when a merge or copy, operation is required on that shadow set.@ SHADOW_REC_DLY can be u osed to better predict which systems in@ an OpenVMS Cluster performs recovery operations. This is done@ by setting lower values of SHADOW_REC_DLY on systems that are? preferred to handle recovery operations and higher values of? SHADOW_REC_DLY on systems that are least preferred to handle recovery operations.B The range of SHADOW_REC_DLY is 20 to 65535 seconds. The default value is 20 seconds.C For more information about controlling which systems perform theB mergep or copy operations, see VSI Volume Shadowing for OpenVMS.) SHADOW_REC_DLY is a DYNAMIC parameter. 2 SHADOW_SITE_ID? (Alpha and Integrity servers) This parameter allows a systemA manager to define a site value, which Volume Shadowing uses to@ determine the best device to perform reads, thereby improving performance.> The system manager can now define the site value to be used@ for all shadow sets mounted on a system. This parameter is an? arbitrary numeric val que coordinated by the system manager of@ disaster tolerant clusters. Reads from devices that have siteA values matching the shadow set's site value are preferred over> reads from devices with different site values. For detailedB information, see the description of the $SET DEVICE/SITE in theC VSI OpenVMS DCL Dictionary and VSI Volume Shadowing for OpenVMS.) SHADOW_SITE_ID is a DYNAMIC parameter. 2 SHADOW_SYS_DISKB A SHADOW_SYS_DISK parameter value of 1 enables shadow ring of theC system disk. A value of 0 disables shadowing of the system disk. The default value is 0.A Also specify a system disk shadow set virtual unit number withB the SHADOW_SYS_UNIT system parameter, unless the desired system disk unit number is DSA0.B A value of 4096 enables CI-based minimerge. To enable minimergeA on a system disk, however, you must enable DOSD by setting theC DUMPSTYLE parameter to dump off system disk, as described in theB VSI OpenVMS Syste sm Manager's Manual. You can then add the valueC 4096 to your existing SHADOW_SYS_DISK value. For example, if youA have SHADOW_SYS_DISK set to a value of 1, change it to 4097 to enable minimerge. 2 SHADOW_SYS_TMOD The SHADOW_SYS_TMO parameter has the following two distinct uses:= o At system boot time, when this is the first node in theD cluster to boot and to create this specific shadow set. If theB proposed shadow set is not currently mounted in the cluster, tB use this parameter to extend the time a booting system waitsB for all former members of the shadowed system disk to become available.> o Once the system successfully mounts the virtual unit and> begins normal operations. In this usage, the SHADOW_SYS_@ TMO parameter controls the time the operating system waitsB for errant members of a system disk. (Use the SHADOW_MBR_TMOB parameter to control the time the operating system waits for1 the errant m uembers 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 v120 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 number of the system disk. The default value is 0. The maximumC value allowed is 9999. This parameter is effective only when theD SHADOW_SYS_DISK parameter has a value of 1. This parameter shouldA be set to the same value on all nodes booting off a particular? system disk shadow set. See VSI Vwolume Shadowing for OpenVMSB for more 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 hxigher value if you want the system to wait more than the 480-A second default for all members to join the shadow set. You can7 set the parameter value to 1 through 65,535 seconds. 2 SMCI_FLAGSB (Alpha Galaxy platforms only) The SMCI_FLAGS parameter controls@ operational aspects of SYS$PBDRIVER, the Galaxy Shared Memory Cluster Interconnect (SMCI).* Bits in the bit mask are the following:/ Bit Mask Description> 0 0 0 = Do not ycreate 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).> z1 = Load SYS$PBDRIVER if booting into a Galaxy.; 2 4 0 = Minimal console output (SYSGEN default).= 1 = Full console output; SYS$PBDRIVER displaysB console messages when it creates and tears down+ communications channels.( SMCI_FLAGS has the DYNAMIC attribute. 2 SMCI_PORTS@ On systems running OpenVMS Galaxy software, the Shared MemoryC Cluster Interconnect (SMCI) system parameter SMCI_PORTS controlsA initial { loading of SYS$PBDRIVER. This parameter is a bit mask;A bits 0 through 25 each represent a controller letter. If bit 0@ is set, which is the default setting, PBAx is loaded (where x@ represents the Galaxy Partition ID). If bit 1 is set, PBBx isB loaded, and so on up to bit 25, which causes PBZx to be loaded.B For OpenVMS Alpha Version 7.2 and later, VSI recommends leaving, this parameter at the default value of 1.@ Loading additional ports allows multiple paths between Galaxy |C instances. In the initial release of the Galaxy software, having? multiple communications channels is not an advantage because< SYS$PBDRIVER does not support fast path. A future release> of OpenVMS will provide Fast Path support for SYS$PBDRIVER,> when multiple CPUs improve throughput by providing multiple- communications channels between instances. 2 SMP_CPU_BITMAPB This parameter indicates that the corresponding CPU is a bitmap< representing up to 1024 CPUs. Eac }h bit set in this bitmap> indicates that the corresponding CPU automatically attemptsA to join the active set in an OpenVMS symmetric multiprocessingC environment when the instance is booted. A cleared bit indicatesD that the corresponding CPU is ignored only at boot time; if it is< otherwise viable, the CPU can be started at a later time.C SMP_CPU_BITMAP defaults to all bits set. (CPU 0 through CPU 1023D are enabled for multiprocessing.) Note that the primary processorB i~s always booted regardless of the setting of the corresponding bit in the CPU bitmap.> To change the value of SMP_CPU_BITMAP in SYSBOOT or SYSGEN,B specify a list of individual bits or contiguous groups of bits. For example:* SYSGEN> SET SMP_CPU_BITMAP 0,5,17-21B The command in this example sets bits 0, 5, 17, 18, 19, 20, and. 21 in the bitmap and clears all other bits.2 This parameter replaces the SMP_CPUS parameter. 2 SMP_LNGSPINWAIT@ SMP_LNGSPINWAIT  establishes, in 10-microsecond intervals, theB amount of time a CPU in an SMP system normally waits for access< to a shared resource. This process is called spinwaiting.; Generally spinlocks at IPL <= 8 have long holding times,@ therefore have their timeout intervals set to SMP_LNGSPINWAIT? to prevent SPINWAIT timeouts in cases of nested acquisition.+ A timeout causes a CPUSPINWAIT bugcheck.D The default value is 3000000 (30,00, 000 10-microsecond intervals or 30 sec ond). 2 SMP_SANITY_CNT? SMP_SANITY_CNT establishes, in 10-millisecond intervals, theC timeout period for each CPU in a symmetric multiprocessing (SMP)A system. Each CPU in an SMP system monitors the sanity timer ofD one other CPU in the configuration to detect hardware or softwareD failures. If allowed to go undetected, these failures could cause> the cluster to hang. A timeout causes a CPUSANITY bugcheck.; The default value is 300 milliseconds (30 10-millisecond intervals). 2 SMP_SPINWAITD SMP_SPINWAIT establishes, in 10-microsecond intervals, the amount@ of time a CPU in an SMP system normally waits for access to a7 shared resource. This process is called spinwaiting.+ A timeout causes a CPUSPINWAIT bugcheck.C The default value is 100000 (100,000 10-microsecond intervals or 1 second). 2 SMP_TICK_CNTA SMP_TICK_CNT sets the frequency of sanity timer checks by each# CPU in a multiprocessing system.D T his special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 SSI_ENABLE@ (Integrity servers only) This parameter controls the usage ofC system service interception. SSI_ENABLE is turned on by default.> System Service Interception is a mechanism that allows userD specified code to run before, after or instead of the intercepted? system service. This mechanism is available on OpenVMS Alpha> Version 6.1 and later and OpenVMS Integrity servers Version? 8.3 and later, but the parameter SSI_ENABLE is relevant only on Integrity server systems. 2 SSINHIBIT? SSINHIBIT controls whether system services are inhibited (1)@ (on a per-process basis). By default, system services are not inhibited (0).D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 STARTUP_P1-8> The following table describes possible values of STARTUP_P1 through _P8: STARTUP Value Description? STARTUP_P1 Specifies the type of system boot the system-B independent startup procedure is to perform when= STARTUP_P1 has one of the following values:3 o " "- A full boot is performed.C o "MIN"- A minimum boot that starts only what isB absolutely necessary for the operating system  to run.A STARTUP_P2 Controls the setting of verification during the= execution of the system-independent startupA procedure, STARTUP.COM, when STARTUP_P2 has one= of the values described in the lists below.B STARTUP_P2 can be one of the values shown in the! following list:> o F[ALSE], N[O], 0, " "-Verification is notD enabled; in other  words, NOVERIFY is performed.A o T[RUE], Y[ES], 1-Verification is enabled; in< other words, a SET VERIFY is performed.; Alternatively, STARTUP_P2 can be a string@ containing one or more of the letters shown in% the following list:D o C-Display various checkpointing messages during startup.C o D-Log (or Dump) the output from the startup t oD a file called SYS$SPECIFIC:[SYSEXE]STARTUP.LOG.; o P-DCL verification is enabled for eachD component file, but not for the startup driver.< If both P and V are used, P is ignored.@ o V-Full DCL verification is enabled; same as TRUE.@ For more information about STARTUP_P2, see the5 SYSMAN command STARTUP SET OPTIONS.A STARTUP_P3  Beginning in OpenVMS Version 7.2, if STARTUP_P3D is set to AGEN, the system executes AUTOGEN at the. end of the startup sequence.* STARTUP_P4 Reserved for future use. through STARTUP_P8 2 SWP_PRIO? SWP_PRIO sets the priority of I/O transfers initiated by the swapper.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 SWPFAIL? SWPFAIL sets the number of consecutive swap failures allowedC before the swap schedule algorithm is changed to ignore the swap quantum protection.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 SWPOUTPGCNTD This parameter allows the swapper an alternative mechanism before actually performing swaps.B On Alpha and Integrity servers, SWPOUTPGCNT defines the minimumC number of pagelets to which the swapper should attempt to reduce@ a process before swapping it out. The pagelets taken from the. process are placed into the free-page list.9 SWPOUTPGCNT has the DYNAMIC attribute. On VAX systems,. SWPOUTPGCNT also has the AUTOGEN attribute. 2 SWPRATE< SWPRATE sets the swapping rate (in 10-millisecond units).A This parameter limits the amount of disk bandwidth consumed by swapping.D This special parameter is use by VSI and is subject to change . DoB not change this parameter unless VSI recommends that you do so. 2 SYSMWCNTB 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.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 SYSSER_LOGGING@ (Alpha and Integrity servers) A value of 1 for SYSSER_LOGGING@ enables logging of system service requests for a process. The default is 1.0 SYSSER_LOGGING is a DYNAMIC system parameter. 2 SYSTE M_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; an allocated pool pattern< of %x61616161 ('aaaa') and= deallocated pool pattern of5 x64646464 ('dddd').= MULTIPROCESSING 2 Enable full synchronization+ checking.> While SYSTEM_CHECK is enabled, the prev ious 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 by SYSTEM_CHECK, see the de scription of the ACP_= DATACHECK parameter. For information about the performanceA implications of enabling SYSTEM_CHECK, see OpenVMS Performance Management. 2 TAPE_ALLOCLASS> TAPE_ALLOCLASS determines the tape allocation class for theA system. The tape allocation class creates a unique clusterwide: device name for multiple access paths to the same tape.> The TAPE_ALLOCLASS parameter can also be used to generate a? unique clusterwide name for tape devices with identical unit numbers. 2 TAPE_MVTIMEOUTB TAPE_MVTIMEOUT is the time in seconds that a mount verificationB attempt continues on a given magnetic tape volume. If the mountA verification does not recover the volume within that time, theA I/O operations outstanding to the volume terminate abnormally.) TAPE_MVTIMEOUT is a DYNAMIC parameter. 2 TBSKIPWSL= TBSKIPWSL specifies the maximum number of working set list@ entries that may be skipped while scanning for a "good" entry= to discard. Setting this parameter to 0 disables skipping.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 TIME_CONTROLD This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so.D TIME_CONTROL is an SMP bit mask parameter that controls debugging- functions. The following bits are defined:% Bit Description# 0 Obsolete.@ 1 (EXE$V_SANITY) Disables the SMP sanity timer support.A 2 (EXE$V_NOSPINWAIT) Disables the functional behavior of the/ SMP spinwait support.' TIME_CONTROL is a DYNAMIC parameter. 2 TIMEPROMPTWAIT? TIMEPROMPTWAIT defines the number of seconds that you want a? processor to wait for the time and date to be entered when aA system boot occurs, if the proces sor'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@ VSI recommends that you set the correct system time before= allowing the system to run, so that all functions usin g= time-stamping (such as the operator log, the error log,B accounting records, file creation dates, and file expiration) dates) contain correct time values.: Depending on the value specified for the TIMEPROMPTWAIT; parameter, the system acts in one of the following ways:B o If TIMEPROMPTWAIT is 0, no prompt or wait occurs; the system? boots immediately, using the time of the last boot as the system time.A o If TIMEPROMPTWAIT is a positive number  less than 32768, oneB prompt is issued and the value dictates how many seconds youC can take to respond with a time. If you do not provide a time@ before TIMEPROMPTWAIT elapses, the system boots, using the/ time of the last boot as the system time.A o If TIMEPROMPTWAIT is a number in the range of 32768 throughD 65535, the prompt for the time is issued at intervals starting= with 2 and doubling until 256 seconds is reached. If noB response is receiv ed, the prompts restart, with the 2-secondB interval. This prompting process repeats indefinitely, until you specify a time. 2 TIMVCFAILB TIMVCFAIL specifies the time required for an adapter or virtualB circuit failure to be detected. VSI recommends that the defaultE value be used. VSI also recommends that this value be lowered only@ in OpenVMS Cluster of three CPUs or less, that the same valueB be used on each computer in the cluster, and that dedicated LAN$ segments be used for cluster I/O.$ TIMVCFAIL is a DYNAMIC parameter. 2 TMSCP_LOADA TMSCP_LOAD allows the loading of the tape mass storage control? protocol server software. The TMSCP_LOAD parameter also setsD locally connected tapes served. For information about setting the9 TMSCP_LOAD parameter, see VSI OpenVMS Cluster Systems.B Setting TMSCP_LOAD to 0 inhibits the loading of the tape server? and the serving of local tapes. Setting TMSCP to 1 loads the? tape server into memory at the time the system is booted andB makes all directly connected tape drives available clusterwide.A The following table describes the two states of the TMSCP_LOAD parameter: State FunctionC 0 Do not load the TMSCP tape server. Do not serve any local> tape devices clusterwide. This is the default value.@ 1 Load the TMSCP tape server. Serve all local TMSCP tape devices clusterwide.& TMSCP_LOAD is an AUTOGEN parameter.  2 TMSCP_SERVE_ALLD TMSCP_SERVE_ALL is a bit mask that controls the serving of tapes.D The settings take effect when the system boots. You cannot change+ the settings when the system is running.; Starting with OpenVMS Version 7.2, the serving types areA implemented as a bit mask. To specify the type of serving yourA system will perform, locate the type you want in the following> table and specify its value. For some systems, you may wantA to specify two serving ty pes, 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 parameter) are served.C This is pre-Version 7.2 behavior. If your cluster@  includes systems running OpenVMS Version 7.1-xA or earlier, and you want to serve all availableB tapes, you must specify 9, the result of setting% this bit and bit 0.D Although the serving types are now implemented as a bit mask, theD values of 0, 1, and 2, specified by bit 0 and bit 1, retain their original meanings:B o 0 - Do not serve any tapes (the default for earlier versions of OpenVMS).$ o 1 - Serve all available tapes.C o 2 - Serve only locally attached (non-HSx and non-DSSI) tapes.> If the TMSCP_LOAD system parameter is 0, TMSCP_SERVE_ALL is ignored. 2 TTY_ALTALARM@ TTY_ALTALARM sets the size of the alternate type-ahead bufferC alarm. This value indicates at what point an XOFF should be sentB to terminals that use the alternate type-ahead buffers with the0 size specified by the TTY_ALTYPAHD parameter. 2 TTY_ALTYPAHDA TTY_ALTYPAHD sets the size of the alternate type-ahead buffer.; Use this parameter to allow the block mode terminals and4 communications lines to operate more efficiently.C The default value is usually adequate. Do not exceed the maximum. value of 32767 when setting this parameter. 2 TTY_AUTOCHARB TTY_AUTOCHAR sets the character the terminal driver echoes when( the job controller has been notified.' TTY_AUTOCHAR is a DYNAMIC parameter. 2 TTY_BUF5 TTY_BUF sets the default line width for terminals. 2 TTY_CLASSNAMEA TTY_CLASSNAME provides the 2-character prefix for the terminal@ class driver name that is required when booting. Changing the= prefix can be useful when debugging a new terminal driver. 2 TTY_DEFCHARD TTY_DEFCHAR sets the default characteristics for terminals, using> a code derived by summing the following hexadecimal values:, Characteristic Value (Hex) Function, PASSALL 1 Passall.0 NOECH O 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 Wraparou nd 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 th e alternate type-ahead+ parameters.? SETSPEED 100 Clear to allow setting of speed3 without privileges.C DCL_MAILBX 200 Function reserved for VSI use only.@ DECCRT4 400 Terminal is DIGITAL CRT Level 4.? COMMSYNC 800 Enable flow control using modem( signals.5 EDITING 1000 Line editing allowed.= INSERT  2000 Sets default mode for insert.@ FALLBACK 4000 Do not set this bit with SYSGEN.: DIALUP 8000 Terminal is a dialup line.= SECURE 10000 Guarantees that no process isA connected to terminal after Break/ key is pressed.A DISCONNECT 20000 Allows terminal disconnect when a. hangup occurs.< PASTHRU 40000 Te rminal 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 CRT 6 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_DEFCHAR3D (Alpha and Integrity servers) TTY_DEFCHAR3 allows a user to set aC bit so that the OpenVMS terminal driver remaps CTRL/H to Delete.D VSI recommends that you not set this bit as a systemwide default.( Characteristic Value (Hex) FunctionA TT3$M_BS 10 When this bit is set, the OpenVMSA terminal console remaps CTRL/H to'  Delete.C For more information, see the SET TERM and SHOW TERM commands in" the VSI OpenVMS DCL Dictionary. 2 TTY_DEFPORT= TTY_DEFPORT provides flag bits for port drivers. Bit 0 set? to 1 indicates that the terminal controller does not provideB automatic XON/XOFF flow control. This bit should not be set forB VSI Controllers, but it is needed for some foreign controllers.< Currently only the YCDRIVER (DMF32, DMZ32) uses this bit.? The rem aining bits are reserved for future use. This special; parameter should be modified only if recommended by VSI. 2 TTY_DIALTYPE> TTY_DIALTYPE provides flag bits for dialups. Bit 0 is 1 forB United Kingdom dialups and 0 for all others. Bit 1 controls theA modem protocol used. Bit 2 controls whether a modem line hangsB up 30 seconds after seeing CARRIER if a channel is not assignedA to the device. The remaining bits are reserved for future use.C See the OpenVMS I/O User's Reference Manual for more information about flag bits. 2 TTY_DMASIZE= TTY_DMASIZE specifies a number of characters in the output@ buffer. Below this number, character transfers are performed;> above this number, DMA transfers occur if the controller is capable of DMA I/O.& TTY_DMASIZE is a DYNAMIC parameter. 2 TTY_PARITY+ TTY_PARITY sets terminal default parity. 2 TTY_RSPEED> TTY_RSPEED defines the receive speed for terminals. If TTY_D RSPEED is 0, TTY_SPEED controls both the transmit and the receiveD speed. Maximum value is 20. This parameter is only applicable forD controllers that support split-speed operations, such as the DZ32 and the DMF32. 2 TTY_SCANDELTAC TTY_SCANDELTA sets the interval for polling terminals for dialup@ and hangup events. Shorter intervals use more processor time;9 longer intervals may result in missing a hangup event. 2 TTY_SILOTIME@ TTY_SILOTIME defines the interval a t 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.& NOTEB The remainder of this discussion is of  interest to customers% who use Digi Edgeport hardware.? TTY_SILOTIME controls latency, trading throughput and systemA overhead for latency. The default value for TTY_SILOTIME is 8.@ This value is multiplied by 100 and is used as a count of theD number of times to send a query to the device for more data after0 a character transmit or receive is performed.D If no input (or no subsequent output) is seen after 800 responsesC to the query, the driver stops sending querie s to the device and@ waits for an input interrupt. Reducing the TTY_SILOTIME value> allows the device to buffer more data, with slightly higher latency.= Increasing the value of TTY_SILOTIME makes the device more; sensitive to latency but decreases buffering and overallA throughput; it also adds more system and USB overhead. SettingB TTY_SILOTIME to zero causes the driver to send input queries toB the device continually. This setting causes the lowest latency,C the highest system overhead, and the lowest throughput possible. 2 TTY_SPEEDA TTY_SPEED sets 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 20. Baud rates are defined by the $TTDEF macro. 2 TTY_TIMEOUT: TTY_TIMEOUT sets the number of seconds before a processB associated with a disconnected terminal is deleted. The defaultB value (900 seconds) is usually adequate. Note that using values? for TTY_TIMEOUT greater than one year (value %X01E13380) canC cause overflow errors and result in a disconnected device timing out immediately.& TTY_TIMEOUT is a DYNAMIC parameter. 2 TTY_TYPAHDSZ@ TTY_TYPAHDSZ sets the size of the terminal type-ahead buffer.C The default value is usually adequate. Do not exceed the maximum. value of 32767 when setting this parameter. 2 UAFALTERNATE< UAFALTERNATE enables or disables the assignment of SYSUAF< as the logical name for SYSUAFALT, causing all references> to the user authorization file (SYSUAF) to be translated toB SYS$SYSTEM:SYSUAFALT. Use of the normal user authorization file@ (SYS$SYSTEM:SYSUAF) can be restored by deassigning the system@ logical name SYSUAF. This parameter should be set on (1) onlyB when the system is being used by a restricted set of users. YouA must create a user authorization file named SYSUAFALT prior to setting UAFALTERNATE to 1.1 UAFALTERNATE has the GEN and MAJOR attributes. 2 USERD1< USERD1 is reserved for definition at the user's site. The? reserved longword is referenced by the symbol SGN$GL_USERD1.8 On Alpha and Integrity servers, this symbol is in the- SYS$LOADABLE_IMAGES:SYS$BASE_IMAGE module.! USERD1 is a DYNAMIC parameter. 2 USERD2< USERD2 is reserved for definition at the user's site. The? reserved longword is referenced by the symbol SGN$GL_USERD2.8 On Alpha and Integrity servers, this symbol is in the- SYS$LOADABLE_IMAGES:SYS$BASE_IMAGE module.! USERD2 is a DYNAMIC parameter. 2 USER3> USER3 is a parameter that is reserved for definition at theA user's site. The reserved longword is referenced by the symbol SGN$GL_USER3.8 On Alpha and Integrity servers, this symbol is in the- SYS$LOADABLE_IMAGES:SYS$BASE_IMAGE module. 2 USER4> USER4 is a parameter that is reserved for definition at theA user's site. The reserved longword is referenced by the symbol SGN$GL_USER4.8 On Alpha and Integrity servers, this symbol is in the- SYS$LOADABLE_IMAGES:SYS$BASE_IMAGE module. 2 VAXCLUSTERB VAXCLUSTER controls loading of the cluster code. Specify one of the following: Value Description' 0 Never form or join a cluster.D 1 Base decision of whether to form (or join) a cluster or toA operate standalone on the presence of cluster hardware.( 2 Always form or join a cluster. The default value is 1.& VAXCLUSTER is an AUTOGEN parameter. 2 VCC_FLAGSA (Alpha only) The static system parameter VCC_FLAGS enables andA disables file system data caching. If caching is enabled, VCC_? FLAGS controls which file system data cache is loaded during system startup. Value DescriptionA 0 Disables file system data caching on the local node and) throughout  the OpenVMS Cluster.D In an OpenVMS Cluster, if caching is disabled on any node,A none of the other nodes can use the extended file cacheB or the virtual I/O cache. They can't cache any file dataC until that node either leaves the cluster or reboots with+ VCC_FLAGS set to a nonzero value.B 1 Enables file system data caching and selects the Virtual9 I/O Cache. This is the default for VAX systems.C 2 Enables file system data caching and selects the extended< file cache. This is the default for Alpha systems.& NOTE6 On Integrity servers, the volume caching productA ([SYS$LDR]SYS$VCC.EXE) is not available. XFC caching is the@ default caching mechanism. Setting the VCC_FLAGS parameter< to 1 is equivalent to not loading caching at all or to setting VCC_FLAGS to 0.% VCC_FLAGS is an AUTOGEN parameter. 2 VCC_MAXSIZEA (Alpha and Integrity servers) The static system parameter VCC_C MAXSIZE controls the size of the virtual I/O cache. VCC_MAXSIZE,? which specifies the size in blocks, is 3,700,000 by default.D The virtual I/O cache cannot shrink or grow. Its size is fixed at system startup.B To adjust the XFC size, use the VCC_MAX_CACHE system parameter.' VCC_MAXSIZE is an AUTOGEN parameter. 2 VCC_MAX_CACHEB (Alpha and Integrity servers) The dynamic system parameter VCC_B MAX_CACHE  controls the maximum size of the extended file cache.D It specifies the size in megabytes. By default, VCC_MAX_CACHE hasA a special value of -1 for people who do not want to tune theirA systems manually; this value means that at system startup, theB maximum size of the extended file cache is set to 50 percent of% the physical memory on the system.= The extended file cache can automatically shrink and grow,; depending on your I/O workload and how much spare memory= your system has. As your I/O workload increases, the cache@ automatically grows, but never to more than the maximum size.> When your application needs memory, the cache automatically shrinks.C The value of VCC_MAX_CACHE at system startup sets an upper limit> for the maximum size of the extended file cache. You cannot> increase the maximum size of VCC_MAX_CACHE beyond its valueA at boot time. For example, if VCC_MAX_CACHE is 60 MB at systemA startup, you can then set VCC_MAX_C ACHE 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 For instructions on setting permanent memory allocations for the6 cache, see the VSI OpenVMS System Manager's Manual.( VCC_MAX_CACHE is a DYNAMIC parameter. 2 VCC_MAX_IO_SIZEB (Alpha and Integrity servers) The dynamic system parameter VCC_B MAX_IO_SIZE controls the maximum size of I/O that can be cachedB by the extended file cache. It specifies the size in blocks. By# default, the size is 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 and Integrity servers) VCC_MAX_LOCKS is a special@ parameter reserved for VSI use only. Extended file cache will) use this parameter in future versions. 2 VCC_PAGESIZED (Alpha and Integrity servers) VCC_PAGESIZE is a special parameter? reserved for VSI use only. Extended file cache will use this parameter in future versions. 2 VCC_READAHEADB (Alpha and Integrity servers) The dynamic system parameter VCC_C READAHEAD controls whether the extended file cache can use read-A ahead caching. Read-ahead caching is a technique that improves? the performance of applications that read data sequentially.D By default VCC_READAHEAD is 1, which means that the extended fileD cache can use read-ahead caching. The extended file cache detectsB when a file is being read sequentially in equal-sized I/Os, and@ fetches data ahead of the current read, so that the next read+ instruction can be satisfied from cache.A To stop the extended file cache from using read-ahead caching, set VCC_READAHEAD to 0.@ Changing the value of VCC_READAHEAD affects volumes currently? mounted on the local node, as well as volumes mounted in the future.B Readahead I/Os are totally asynchronous from user I/Os and only; take place if sufficient system resources are available.( VCC_READAHEAD is a DYNAMIC parameter. 2 VCC_RSVD@ (Alpha and Integrity servers) VCC_RSVD is a special parameter? reserved for VSI use only. Extended file cache will use this parameter in future versions. 2 VCC_WRITEBEHINDD (Alpha and Integrity servers) VCC_WRITEBEHIND is reserved for VSIB use only. Extended file cache will use this parameter in future versions. 2 VCC_WRITE_DELAYD (Alpha and Integrity servers) VCC_WRITE_DELAY is reserved for VSI  use only. 2 VHPT_SIZEC (Integrity servers only) VHPT_SIZE is the number of kilobytes toA allocate for the virtual hash page table (VHPT) on each CPU in the system:, o 0 indicates that no VHPT is allocated.B o 1 indicates that OpenVMS is to choose a default size that is0 appropriate for your system configuration.A If a VHPT is created, the smallest size is 32KB. The VHPT_SIZEB must be a power of 2 KB in size. If the number specified is notC a power of 2, OpenVMS chooses a VHPT size to use for your system) that is close to the number specified.= If insufficient memory is available during system startup,@ OpenVMS might choose a smaller size for the VHPT of each CPU.A A summary of possible values for VHPT_SIZE is in the following table: Value Description* 0 Do not create a VHPT on each CPU.D 1 (default) OpenVMS chooses a VHPT of an appropriate size for each CPU.A n Create a VHPT of nKB fo r each CPU, where n is a power ofA 2 that is 32 or greater. (The maximum value, however, is platform-dependent.) 2 VIRTUALPAGECNTD On VAX systems, VIRTUALPAGECNT sets the maximum number of virtual= pages that can be mapped for any one process. A program isC allowed to divide its virtual space between the P0 and P1 tables in any proportion.> If you use SYS$UPDATE:LIBDECOMP.COM to decompress libraries? and the VIRTUALPAGECNT setting is low, make sur e you set theC PGFLQUOTA field in the user authorization file to at least twice the size of the library.B At installation time, AUTOGEN automatically sets an appropriate@ value for VIRTUALPAGECNT. The value depends on the particular@ configuration-the type and number of graphics adapters on the@ system, if any exist. You cannot set VIRTUALPAGECNT below the: minimum value required for your graphics configuration.? Because the VIRTUALPAGECNT setting supports hardware addr ess; space rather than system memory, do not use the value ofB VIRTUALPAGECNT that AUTOGEN sets to gauge the size of your page file.@ Starting with OpenVMS Version 7.0, VIRTUALPAGECNT has been an? obsolete parameter on Alpha systems. Note, however, that the@ parameter remains in existence on Alpha and Integrity serversD for compatibility purposes and has a default and maximum value of> %X7FFFFFFF. SYSBOOT and AUTOGEN enforce this default value.= VIRTUALPAGECNT has the AUTOGEN, GEN, and MAJOR attributes. 2 VMS1-8= VMSD1, VMSD2, VMSD3, VMSD4, VMS5, VMS6, VMS7, and VMS8 areC special parameters reserved for VSI use. VMSD1 through VMSD4 are DYNAMIC. 2 VOTESB VOTES establishes the number of votes an OpenVMS Cluster member" system contributes to a quorum.# VOTES has the AUTOGEN attribute. 2 WBM_MSG_INTC WBM_MSG_INT is one of three system parameters that are available@ for managing the update traffic between a mas ter write bitmapB and its corresponding local write bitmaps in an OpenVMS Cluster@ system. The others are WBM_MSG_UPPER and WBM_MSG_LOWER. These@ parameters set the interval at which the frequency of sendingD messages is tested and also set an upper and lower threshold thatB determine whether the messages are grouped into one SCS message or are sent one by one.> In single-message mode, WBM_MSG_INT is the time interval in> milliseconds between assessments of the most suitable  writeD bitmap message mode. In single-message mode, the writes issued byB each remote node are, by default, sent one by one in individual< SCS messages to the node with the master write bitmap. If= the writes sent by a remote node reach an upper threshhold? of messages during a specified interval, single-message mode% switches to buffered-message mode.> In buffered-message mode, WBM_MSG_INT is the maximum time aA message waits before it is sent. In buffered-message mode, the@ messages are collected for a specified interval and then sentC in one SCS message. During periods of increased message traffic,? grouping multiple messages to send in one SCS message to theD master write bitmap is generally more efficient than sending each message separately.C The minimum value of WBM_MSG_INT is 10 milliseconds. The maximumD value is -1, which corresponds to the maximum positive value that< a longword can represent. The default is 10 milliseconds. & WBM_MSG_INT is a DYNAMIC parameter. 2 WBM_MSG_LOWER; WBM_MSG_LOWER is one of three 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 lowerA threshold that determine whether the messag es 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? write bitmap and its corresponding local write bitmap s 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 seconds.( WBM_MSG_UPPER is a DYNAMIC parameter. 2 WBM_OPCOM_LVLB WBM_OPCOM_LVL controls whether write bitmap system messages areA sent to the operator console. Possible values are shown in the following table: Value Description! 0 Messages are turned off.B 1 The default; messages are provided when write bitmaps are@ started, deleted, and renamed, and when the SCS message+ mode (buffered or single) changes.? 2 All messages for a setting of 1 are provided plus many more.( WBM_OPCOM_LVL is a DYNAMIC parameter. 2 WINDOW_SYSTEM? WINDOW_SYSTEM specifies the windowing system to be used on a4 workstation. Specify one of the following values: Value Description; 1 Load the DECwindows Motif for OpenVMS workstation environment./ 2 Load the UIS workstation environment.( WINDOW_SYSTEM is a DYNAMIC parameter. 2 WLKSYSDSK= (Alpha and Integrity servers) WLKSYSDSK is used by variousA bootstrap components to determine if the system disk should be? treated as though it is write-locked. This parameter is used0 primarily to allow OpenVMS to boot from a CD. 2 WPRE_SIZE> WPRE_SIZE represents the number of pages to be allocated toC accommodate WatchPoint Recovery Entries (WPRE) on the Watchpoint Driver.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so.$ WPRE_SIZE is a DYNAMIC parameter. 2 WPTTE_SIZEC WPTTE_SIZE is the number of entries that the WPDRIVER creates in the WatchPoint Trace Table.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so.% WPTTE_SIZE is a DYNAMIC parameter. 2 WRITABLESYS= WRITABLESYS controls whether system code is writable. This= parameter is set (value of 1) for debugging purposes only.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 WRITESYSPARAMS@ On Alpha and Integrity servers, WRITESYSPARAMS indicates that@ parameters are modified during SYSBOOT and are written out to" ALPHAVMSSYS.PAR by STARTUP.COM.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so.) WRITESYSPARAMS is a DYNAMIC parameter. 2 WSDEC? Increasing the value of this parameter tends to increase theB speed with which working set limits are decreased when the need arises.@ On Alpha and Integrity serv ers, WSDEC specifies the number of@ pagelets by which the limit of a working set is automaticallyC decreased at each adjustment interval (which is quantum end). AtD a setting of 35, for example, the system decreases the limit of a? working set by 35 pagelets each time a decrease is required.8 WSDEC has the AUTOGEN, DYNAMIC, and MAJOR attributes. 2 WSINCC Decreasing the value of this parameter tends to reduce the speedD with which working set limits are increased when the need arises.C Normally, you should keep this parameter at a high value because> a rapid increase in limit is often critical to performance.@ On Alpha and Integrity servers, WSINC specifies the number of@ pagelets by which the limit of a working set is automaticallyC increased at each adjustment interval (which is quantum end). AtC a setting of 150, for example, the system increases the limit ofC a working set by 150 pagelets each time an increase is required.A On Alph a and Integrity servers, the default value is 2400 512-B byte pagelets (150 8192-byte Alpha and Integrity server pages).> A value of 0 for WSINC disables the automatic adjustment ofB working set limits for all processes. Limits stay at their base> values. You can disable the automatic adjustment of workingA set limits on a per-process basis by using the DCL command SET WORKING_SET.; WSINC has the DYNAMIC and MAJOR attributes. On Alpha and; Integrity servers, WSINC also  has the AUTOGEN attribute. 2 WSMAXC WSMAX sets the maximum number of pages on a systemwide basis 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 process es)> that require large amounts of physical memory (for example,; simulations) might need to set MIN_WSMAX to a value that1 satisfies the requirements of those processes.4 WSMAX has the AUTOGEN, GEN, and MAJOR attributes. 2 XQPCTL2> 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.D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 XQPCTLD1; XQPCTLD1 controls multithreading, which can be used only< by PATHWORKS servers. The default value of XQPCTLD1 is 8,? which enables multithreading. Setting XQPCTLD1 to 0 disables multithreading,D This special parameter is use by VSI and is subject to change. DoB not change this parameter unless VSI recommends that you do so. 2 ZERO_LIST_HIC (Alpha and Integrity servers) ZERO_LIST_HI is the maximum number@ of pages zeroed and put on the zeroed page list. This list isD used as a cache of pages containing all zeros, which improves the( performance of 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 and C! is inserted here by the build procedures. Please do not edit the ! first comment line.B!***************************************************************** ww,JgK1 RESERVED_MEMORYD There are several RESERVED_MEMORY subcommands. Select the one you want from the choices below. 2 ADD@ On Alpha and Integrity servers, adds an entry to the ReservedC Memory Registry data file. Changes and additions to the Reserved> Memory Registry data file do not ta ke effect until the next reboot of the system.> Use the RESERVED_MEMORY ADD command to reserve an amount ofA physical memory that might be needed at a future time. Use theB /ALLOCATE qualifier to set aside one or more blocks of physical@ memory during the boot process. Using the /ALLOCATE qualifier@ allows memory to be sufficiently contiguous and aligned to be used with granularity hints.B AUTOGEN processes the Reserved Memory Registry data file in itsD GETDATA phase . AUTOGEN takes the size of all entries into accountB when calculating system parameters that depend on the available amount of physical memory.@ AUTOGEN uses the reservation size of all entries to calculateA the initial size of the global page table unless the entry was" specified as /NOGLOBAL_SECTION.A For more information about the Reserved Memory Registry, referA to the VSI OpenVMS System Manager's Manual and the VSI OpenVMS Programming Concepts Manual. Format RESERVED_MEMORY ADD name 3 Parameter name; Name of the memory reservation. You must specify a name.B If the reservation is for a memory resident global section, theA name of the reservation must be the same as the global section name. 3 Qualifiers /ALLOCATE /ALLOCATE /NOALLOCATE (default)< Allocates pages during the next reboot of the system. The: physical alignment of the pages is based on the maximum< granu larity hint factor that can be used to map the pagesA without exceeding the size of the memory reservation. (See the> introduction to this section for more information about the /ALLOCATE qualifier.)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 boundaryB If you specify /NOALLOCATE, or do not specify /ALLOCATE, memoryB is reserved only by reducing the system's fluid page count, but# no specific pages are set aside. /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. /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 /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 you< specify /ALLOCATE, additional pages are allocated for theB shared page table during the next reboot of the system, 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. /RAD /RAD=nA Specifies the preferred resource affinity domain (RAD) for the@ reservation you want to make. The value of n is the number ofB the RAD you specify. If you omit this qualifier, or if this RADA does not have sufficient memory, any other RAD can satisfy theC reservation request, and the first available memory section will be used.D The /ALLOCATE qualifier is enforced implicitly when you specify a RAD. /SIZE+ /SIZE=size of reserved memory, in MBs< 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, preallocatedB 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, preallocated 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 fo r the RESERVED_MEMORY SHOW4 command displays the values for these entries.) 2 EXTENDA On Alpha and Integrity servers, adds sections of memory if youC want to specify more than one resource affinity domain (RAD) for a single reservation.D EXTEND does not allow you to specify any of the /ALLOCATE, /ZERO,A or /PAGE_TABLES flags. The existing reservation determines theB state of these flags. The /ALLOCATE flag is set implicitly withA EXTEND, whether or not it was set for the initial reservation.C To add a memory section without specifying a RAD, use the /NORAD qualifier. Format! RESERVED_MEMORY EXTEND name 3 Parameter name; Name of the memory reservation. You must specify a name.B If the reservation is for a memory resident global section, theA name of the reservation must be the same as the global section name. 3 Qualifiers /RAD /RAD=n /NORAD@ Specifies an additional memory section if you want to specify. more than one RAD for a single reservation.? Use /NORAD to add a memory section without specifying a RAD. /SIZE+ /SIZE=size of reserved memory, in MBs< 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. 2 FREEB On a running Alpha or Integrity servers, frees reserved memory.C This command does not affect the contents of the Reserved Memory: Registry data file; it affects only the running system. Format RESERVED_MEMORY FREE name 3 Parameter name; Name of the memory reservation. 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. /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. 2 LIST= On Alpha and Integrity servers, provides a preview of this? reservation as it is currently stored in the Reserved MemoryB Registry data file. If no reservation is specified, all current reservations are displayed.B Use this qualifier to ensure that a reservation will be made as intended. Format RESERVED_MEMORY LIST name 3 Parameter nameD Name of the reservation you want to verify in the Reserved Memory Registry data file. 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. /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. 2 MODIFYC On Alpha and Integrity servers, allows you to modify an existing3 entry in the Reserved Memory Registry data file. Format! RESERVED_MEMORY MODIFY name 3 Parameter nameC Name associated with the entry being removed. You must specify a name. 3 Qualifiers /ALLOCATE /ALLOCATE /NOALLOCATE (default)D Allocates p ages during the next reboot of the system as specified? on the command line. (The default is taken from the existingA Reserved Memory Registry entry.) The physical alignment of theA pages is based on the maximum granularity hint factor that canA 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 boundaryB If you specify /NOALLOCATE, or if you do not specify /ALLOCATE,> memory is reserved only by reducing the system's fluid page. count, but no specific pages are set aside. /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. /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. /NEW_RAD /NEW_RAD=nn /NONEW_RADD Use NEW_RAD to change the RAD assignment for an entry. Do this byC first specifying /RAD=n to identify the entry you want to changeA and then specify /NEW_RAD=nn to identify the new RAD. Use onlyD /NEW_RAD=nn (without the /RAD qualifier) if the old entry did not have a RAD assigned. /PAGE_TABLES /PAGE_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 global section is created, shared@ page tables are c reated for the global section. If you do notC specify /ALLOCATE, or if you specify /NOALLOCATE, the additionalB reserved memory is deducted from the system's fluid page count.C If you specify /ALLOCATE, additional pages are allocated for theB shared page table during the next reboot of the system, 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. /RAD /RAD=n /NORADA MODIFY/RAD=n affects only the entry for the specified resource@ affinity domain (RAD). The value of n is the RAD you specify. Usage RulesA o Do not use MODIFY/RAD=n to change the size  of a reservation> for an entry without a specified number or to change theA state of the /ZERO or /PAGE_TABLES flags. (Flags are always9 consistent for all entries in a given reservation.)? o To change the RAD assignment for an entry, specify /RAD=nA to identify the entry you want to change and /NEW_RAD=nn toB identify the new RAD. Use only /NEW_RAD=nn (without the /RAD> qualifier) if the old entry did not have a RAD assigned.@ o Use MODIFY name /NORAD if you no longer want to tie memoryB for this reservation to any specific RADs. SYSMAN compressesA multiple entries into a single entry for an unspecified RADB with the total memory size as the sum of all RAD entries for this reservation. /SIZE+ /SIZE=size of reserved memory, in MBs< 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 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, preallocated> pages are zeroed during system initialization. Zeroed pagesA are required for memory-resident global sections; however, theC pages do not need to be zeroed 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, preallocated 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: 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 file. ! Modify with SYSMAN RESERVED_MEMORY commands: ! A = /ALLOCATE, Z = /ZERO, P = /PAGE_TABLES, VERSION = 1E ! SIZE (MB) RESERVATION NAME GROUP A Z PE 1 X23456789012345678901234567890 1 0 0 1E 2 X234567890123456789012345678901 SYSGBL 1 1 1E 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 boot time. 2 REMOVE< On Alpha and Integrity servers, removes a reserved memoryB entry from the Reserved Memory Registry data file. This commandB takes effect on the next reboot and does not affect the running systems. Format! RESERVED_MEMORY REMOVE name 3 Parameter nameC Name associated with the 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 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. /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 com mand removes it. 2 SHOWC On Alpha and Integrity servers, displays the memory reservations on the running system.D The display includes how much of the reserved memory is currently@ in use by the named global section. It also includes how muchC memory is reserved and currently in use for page tables, if any,- and the blocks of physical pages reserved. Format RESERVED_MEMORY SHOW name 3 Parameter nameD Name associated with the entry  being displayed within the running@ system. If you do not specify a name, the system displays the6 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 sect ion.) You cannot use /NOGLOBAL_@ SECTION with the qualifiers /GROUP, /SYSGBL, or /PAGE_TABLES. /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 displayed. You can use the /GROUP@ qualifier only if you specify name. Y ou 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. ww0JgK1 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 SYSMANC logical name table, see the VSI 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 conjunction 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 sp ecified 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 managementB 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 envi ronment with the /CLUSTERB qualifier. When specifying a nonlocal cluster, also include the+ /NODE qualifier to identify the cluster.C If your environment consists of Vax, Alpha, and Integrity serverD nodes, see the DO command for information about creating logicals- 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 local 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$NODE_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 privileges 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 andB directory, as well as use the SET PROFILE/[NO]VERIFY command toB control DCL command verification in SYSMAN. Other attributes ofC your process remain constant. The profile is in effect until youA change it, reset the environment, or exit from SYSMAN. The VSID 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 respond. 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-2002 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-2002 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 proceeds to execute the command) on the next node in the environment. ww@JgK1 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 nodes,@ 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 command 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 command 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 comma nd 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. /B RIEFD 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 you 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 you 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 Qualifiers /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 th#e 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 values 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 a 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 t%he current timeout value, which is 4 seconds. wwPKgK 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 specify, 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 o&r 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 automatically 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, eac 'h 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, the 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 failover 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 com)pleting 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. Invokes 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 define*d, 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, 0 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). /REBOO+T_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 expect 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 downward 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 o-ptions by using the following command:7 SYSMAN> STARTUP SET OPTIONS/NOVERIFY/NOCHECKPOINTINGA For more information about cluster management, see VSI OpenVMS Cluster Systems. /SAVE_FEEDBACK /SAVE_FEEDBACK /NOSAVE_FEEDBACK (default)D Records 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 /SPI.N_DOWN_DISKS" /NOSPIN_DOWN_DISKS (default): Spins down disks. You cannot spin down the system disk. ww`>KgK1 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 on/ly. If you@ want to execute DCL commands or 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 0the context of the created subprocess.B When 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 s1ubprocess. If youA specify a command string 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 2 qualifier. /OUTPUT /OUTPUT=filespecC 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 3that you want to create. The7 default subprocess 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? subpr4ocess is running. If you specify the /NOWAIT qualifier,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@5 to see if a site-specific startup file is 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-2002 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 /6NOLOGICAL_NAMES SET HOST _Node: NODE21 . . . $ 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. 7ww`>KgK 1 STARTUPA There 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 8the startup database. EachB component of the 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 9file is added. If you enter anything else, such 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 th:at run the file during? startup. By default, 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 wa;ntC 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-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 ex<ecutable filesD that perform actual startup 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 F=ILE /MODE=DIRECT /PHASE=LPMAIN -# _SYSMAN> DECSET$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& START>UP$STARTUP_LAYERED by default. filespecA 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 datab?ase and requests you to confirm that the file be 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,n@ode2,...,noden)? Identifies nodes within 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 exeAcuting. The command edits a record in the4 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 B. Format" STARTUP ENABLE FILE filespec 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 befoCre enabling it in the startupA database and 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. D/NODE# /NODE=(node1,node2,...,noden)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 execuEte during system startup. 3 ExampleC 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 FILEF= Modifies a record in the startup database. 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 Gthe file characteristics be modified. 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 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=moHde@ Changes the mode of execution for a startup 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 STAIRTUP_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 DescriptiJonB The STARTUP MODIFY command edits startup 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 forK the command) procedure DECSET$ENVMGR_STARTUP.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 namLe of the file to remove from the startup. database. 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 fiMle? 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$ENVMGRN_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 Parameter database6 Specifies the name of the target database, which is; STARTUP$STARTUP_LAYERED by default. The second database,> STARTUP$STARTUP_VMS, is available for viewing; however, VSI( recommends that you do not modiOfy it. 4 Qualifiers None. 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 Pthe layered products5 database as the default, so it can be displayed. 3 OPTIONSD Controls logging and display of information for one or more nodes in a cluster during startup.? Requires READ (R) and WRITE (W) access to the current systemB parameter file on disk: SYS$SYSTEM:ALPHAVMSSYS.PAR (for Alpha),9 and SYS$SYSTEM:IA64VMSSYS.PAR (for Integrity servers). Format STARTUP SET OPTIONS 4 Qualifiers /CHECKPOINTING /CHECKPOINTINGQ /NOCHECKPOINTINGD Displays informational messages describing the time and status of. each startup phase and component procedure.C The value of the system parameter STARTUP_P2 that corresponds to /OUTPUT=CHECKPOINTING is "C". /OUTPUT /OUTPUT=FILE,CONSOLEB 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.C The value of the system pRarameter STARTUP_P2 that corresponds to /OUTPUT=FILE is "D". /VERIFY /VERIFY=FULL,PARTIAL /NOVERIFY> Displays startup procedures as they execute. This qualifierB defines the system parameter STARTUP_P2 to have the appropriate@ value based on the options you choose. (/VERIFY with no value3 following it is the equivalent of /VERIFY=full.). /VERIFY options are in the following table: Value DescriptionC FULL Displays every line of DCL execSuted by startup component) procedures and by STARTUP.COM.< The value of the system parameter STARTUP_P2 that- corresponds to this option is "V".C PARTIAL Displays every line of DCL executed by startup component; procedures, but does not display DCL executed by STARTUP.COM.< The value of the system parameter STARTUP_P2 that- corresponds to this option is "P".' CAUTION< TAll STARTUP_P2 parameter values modified by the SYSMAN? STARTUP OPTIONS will be overridden by the AUTOGEN commandB procedure. To preserve any parameter modifications made withB SYSMAN, edit the SYS$SYSTEM:MODPARAMS.DAT file, as explained1 in the VSI OpenVMS System Manager's Manual. 4 DescriptionA The STARTUP SET OPTIONS command enables you to control loggingB and checkpointing during startup. You can control the amount ofA information logged (full or partial U) and where it is displayed> (file or console). You can also choose checkpointing, which? displays informational messages about the time and status of each phase during startup.A The default options are /NOCHECKPOINTING, /OUTPUT=CONSOLE, and /NOVERIFY.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 morVe 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.LOG, and checkpointing.? The corresponding value for system parameter STARTUP_P2 is "VDC". 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.W 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 andA STARTUP$STARTUP_VMS. VSI recommends 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 executioXn& 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 mode 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. Y/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$OUTPUT 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 filZe 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 specific 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 component 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. wwKgK1 SYS_LOADABLEA There are several SYS_LOADABLE subcommands. Select the one you want from 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 Parameters productB A 1- to 8-character product mnemonic that uniquely identifies aA loadable image. For user-written 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 pa^rameter.= 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 load 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). 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 fo`r 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 an 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 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. 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, theb. 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 programmers should use this command. Format! SYS_LOADABLE REMOVE product image 3 Parameters product@ A 1- to 8-character product mcnemonic 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 specify a device, directory, file type, or wildcard characters. 3 Qualifier /LOG /LOG /NOLOG (default)> Controls whether the SYS_LOADABLE REMOVE command displays a1 d 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. 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, the8 SYS_LeOADABLE REMOVE command creates a new, empty one. wwKgK1 RAD_ExampleC The following example procedure shows how to use SYSMAN resource0 affinity domain (RAD) qualifiers and options.3 1. Show that no reserved memory registry exists:" SYSMAN> reserved_memory list7 %SYSMAN-I-NODERR, error returned from node PIPERI -RMS-E-FNF, file not foundB 2. Add a reservation for a group global section and display the new reservation:FSYSMAN> freserved_memory add ak_sec/gr=4711 /size=16 /zero /page_tablesSYSMAN> reserved_memory list2%SYSMAN-I-OUTPUT, command execution on node PIPERI=Reservation Name Group RAD Size (MB) Pages AttributesCAK_SEC 4711 ANY 16 2048 Allocated ZeroedGAK_SEC 4711 2 PageTables AllocatedA 3. Modify the reservation to have memory assigned from each of$ four RADs; display the result:@SYSMAN> reserved_memory modify ak_sec/gr g=4711 /new_rad=0 /size=4<SYSMAN> reserved_memory extend ak_sec/gr=4711 /rad=1 /size=4<SYSMAN> reserved_memory extend ak_sec/gr=4711 /rad=2 /size=4<SYSMAN> reserved_memory extend ak_sec/gr=4711 /rad=3 /size=4SYSMAN> reserved_memory list2%SYSMAN-I-OUTPUT, command execution on node PIPERI@Reservation Name Group RAD Size (MB) Pages AttributesFAK_SEC 4711 0 4 512 Allocated ZeroedFAK_SEC 4711 1 4 512 Allocated ZeroedF hAK_SEC 4711 2 4 512 Allocated ZeroedFAK_SEC 4711 3 4 512 Allocated ZeroedJAK_SEC 4711 2 PageTables AllocatedA 4. Modify the reservation to no longer zero allocated pages atC boot time. Note that you can change properties such as /ZERO,B /ALLOCATE, /PAGE_TABLES only for the reservation as a whole, not for a specific RAD.5SYSMAN> reserved_memory modify ak_sec/gr=471 i1 /nozeroSYSMAN> reserved_memory list2%SYSMAN-I-OUTPUT, command execution on node PIPERI@Reservation Name Group RAD Size (MB) Pages Attributes?AK_SEC 4711 0 4 512 Allocated?AK_SEC 4711 1 4 512 Allocated?AK_SEC 4711 2 4 512 Allocated?AK_SEC 4711 3 4 512 AllocatedJAK_SEC 4711 2 PageTables Allocated= j 5. Modify the reservation to no longer request memory fromB specific RADs. Note that the overall size remains unchanged.4SYSMAN> reserved_memory modify ak_sec/gr=4711 /noradSYSMAN> reserved_memory list2%SYSMAN-I-OUTPUT, command execution on node PIPERI@Reservation Name Group RAD Size (MB) Pages Attributes?AK_SEC 4711 ANY 16 2048 AllocatedJAK_SEC 4711 2 PageTables AllocatedA 6. Starting with a rese krvation allocated across multiple RADs,C request that memory no longer be allocated at boot time. Note? that this implies that memory is no longer allocated from specific RADs." Reservation prior to change:SYSMAN> reserved_memory list2%SYSMAN-I-OUTPUT, command execution on node PIPERIAReservation Name Group RAD Size (MB) Pages Attributes?AK_SEC 4711 0 4 512 Allocated?AK_SEC 4711 1 4 l 512 Allocated?AK_SEC 4711 2 4 512 Allocated?AK_SEC 4711 3 4 512 AllocatedJAK_SEC 4711 2 PageTables Allocated1 Command to no longer allocate at boot time:6SYSMAN> reserved_memory modify ak_sec/gr=4711 /noalloc New state of reservation:SYSMAN> reserved_memory list2%SYSMAN-I-OUTPUT, command execution on node PIPERI@Reservation Name Group RAD Size (MB) m Pages Attributes4AK_SEC 4711 ANY 16 2048@AK_SEC 4711 2 PageTablesB 7. To change the size of a reservation with an assigned RAD, or@ to change the reservation to use a different RAD, you must specify the current RAD." Reservation prior to change:SYSMAN> reserved_memory list2%SYSMAN-I-OUTPUT, command execution on node PIPERI=Reservation Name Group RAD Size (MB) Pages Attributes<AK_SEC n 4711 2 16 2048 AllocatedGAK_SEC 4711 2 PageTables Allocated) Attempt to change reservation size:3SYSMAN> reserved_memory mod ak_sec/gr=4711 /size=201%SYSMAN-I-NODERR, error returned from node PIPERI5-SMI-E-RMRNOMATCH, no records matched search criteria Correct command:; SYSMAN> reserved_memory mod ak_sec/gr=4711 /rad=2 /size=20 New state of reservation:SYSMAN> reserved_memory list2%SYSMAN-I-OUTPUT, command execution on node PIPERI<Reservation Name Group RAD Size (MB) Pages Attributes;AK_SEC 4711 2 20 2560 AllocatedFAK_SEC 4711 3 PageTables Allocatedww