| Previous | Contents | Index |
The PWRK$REGUTL utility allows you to display and set server configuration parameters in the OpenVMS Registry. Server configuration parameters can be managed using either of two different modes: Registry mode and LANMAN.INI mode. The default environment sets Registry mode.
Set LANMAN.INI mode if you are familiar with LANMAN.INI sections and keywords. LANMAN.INI syntax mode conforms to the structure and naming of server parameters as used in PATHWORKS V6 for OpenVMS (Advanced Server). When you set LANMAN.INI syntax mode, the server parameters are actually retrieved and modified on the OpenVMS Registry.
To set LANMAN.INI syntax mode:
Use the PWRK$REGUTL command SET MODE INI. The following example shows commands to:
REGUTL> SHOW VALUE * SRVCOMMENT Key: SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters Value: SrvComment Type: String Current Data: Advanced Server V7.2 for OpenVMS REGUTL> SET MODE INI REGUTL> SHOW MODE Current mode is INI REGUTL> SHOW VALUE * SRVCOMMENT Section Name: server Parameter Name: srvcomment Type: String Current Data: Advanced Server V7.2 for OpenVMS REGUTL> |
When you start PWRK$REGUTL the first time, you can display server parameters and settings that are established by the configuration procedure and those that have been migrated from the LANMAN.INI file if the server was upgraded from PATHWORKS V6 for OpenVMS (Advanced Server). Parameters that have not been modified from the supplied default settings are not stored in the OpenVMS Registry and will not be displayed by PWRK$REGUTL.
To display current parameters and settings:
Use the PWRK$REGUTL command SHOW VALUE, specifying the following command options:
You can specify the wildcard character (*) for either or both command options, or to replace a portion of the command option. For example, to display the location where logon scripts are stored, enter the following command in registry mode:
REGUTL> SHOW VALUE * SCRIPTS Key: SYSTEM\CurrentControlSet\Services\Netlogon\Parameters Value: Scripts Type: Expanded String Current Data: PWRK$LMROOT:[LANMAN.REPL.IMPORT.SCRIPTS] REGUTL> |
You can include the /MODE qualifier on the SHOW VALUE command line to specify the mode in which PWRK$REGUTL will interpret the value name. For example, to get information about Scripts, a LANMAN.INI parameter, enter the following command:
REGUTL> SHOW VALUE * SCRIPTS/MODE=INI Section Name: netlogon Parameter Name: scripts Type: Expanded String Current Data: PWRK$LMROOT:[LANMAN.REPL.IMPORT.SCRIPTS] REGUTL> |
To display information about the registry values, include the appropriate qualifier to the SHOW VALUE command. The SHOW VALUE command qualifiers are listed in Table 7-4, PWRK$REGUTL SHOW VALUE Command Qualifiers.
| /DIFFERENCE | Displays only the parameters that have been modified since the configuration of the server. |
| /FULL | Displays complete information about the parameter, including data type and ranges. |
| /MAP_NAME | Displays both the LANMAN.INI keyword and the registry value name. |
To display both the registry parameter name and the LANMAN.INI parameter name, include the /MAP_NAME qualifier on the SHOW VALUE command line. For example:
REGUTL> SHOW VALUE * SCRIPTS/MAP_NAME Key: SYSTEM\CurrentControlSet\Services\Netlogon\Parameters Value: Scripts Section Name: netlogon Parameter Name: scripts Type: Expanded String Current Data: PWRK$LMROOT:[LANMAN.REPL.IMPORT.SCRIPTS] REGUTL> |
To display detailed information about one or more server parameters, include the /FULL qualifier on the SHOW VALUE command line. The display includes information such as the parameter default setting, and minimum and maximum values allowed. For example, to display detailed information about the MaxSize server parameter, enter the following command:
REGUTL> SHOW VALUE * MAXSIZE/FULL Key: SYSTEM\CurrentControlSet\Services\EventLog\Application Value: MaxSize Source: Registry Type: Integer Current Data: 524288 Default Data: 524288 Min: 1024 Max: -1 Key: SYSTEM\CurrentControlSet\Services\EventLog\Security Value: MaxSize Source: Registry Type: Integer Current Data: 524288 Default Data: 524288 Min: 1024 Max: -1 Key: SYSTEM\CurrentControlSet\Services\EventLog\System Value: MaxSize Source: Registry Type: Integer Current Data: 524288 Default Data: 524288 Min: 1024 Max: -1 REGUTL> |
This example shows that the MaxSize parameter is defined in three registry keys: one for each type of event log maintained by the Advanced Server:
For a detailed list of the server configuration parameters that can be
stored in the OpenVMS Registry, including descriptions of the
parameters, LANMAN.INI parameter mappings, default data settings and
minimum and maximum values for integer data, see Appendix A, Server Configuration Parameters.
7.2.6 Modifying Server Parameters
To modify the data settings for any server parameter, use the PWRK$REGUTL command SET VALUE. For example, to change the text string associated with the SrvComment parameter, enter the following command:
REGUTL> SET VALUE SYSTEM\CURRENTCONTROLSET\SERVICES\LANMANSERVER- _REGUTL>\PARAMETERS SRVCOMMENT "My OpenVMS Server" REGUTL> |
This example includes the command-line continuation character (-) to allow the command to be continued past the end of the first line. You can use the wildcard character to replace the key, simplifying the command input.
PWRK$REGUTL enforces the minimum and maximum values allowed for each server parameter. If you enter a value below the minimum, the value is set to the minimum. If you enter a value above the maximum, the value is set to the maximum. For example, the following command attempts to set the maximum client session capacity to 150, which is higher than the maximum setting:
REGUTL> SET VALUE * NUMCLIENT_SESSION 150 %REGUTL-I-VALTOMAX, value set to maximum of 128 REGUTL> |
As the PWRK$REGUTL message indicates, the maximum value is set as a result of this command.
Similarly, the PWRK$REGUTL utility prevents you from entering a server parameter that is not recognized by the Advanced Server. For example, if you misspell the parameter value in the registry, the following message is displayed:
REGUTL> SET VALUE * NUM_CLIENTSESSION 150 %REGUTL-W-VALUNKWN, unknown value NUM_CLIENTSESSION REGUTL> |
To reset the data setting for a parameter to the default setting, omit
the data and include the /DEFAULT qualifier on the SET VALUE command
line.
7.2.6.2 Creating a Value in the Registry
To create a parameter that is not in the OpenVMS Registry, include the /CREATE qualifier on the SET VALUE command line. To create a parameter that is not currently stored in the registry and to set the data value to the default setting, enter the SET VALUE command with both qualifiers. For example, to define the NumClient_Session parameter in the OpenVMS Registry, set its value to the default setting, and then display the setting, enter the following command:
REGUTL> SET VALUE SYSTEM\CURRENTCONTROLSET\SERVICES\ADVANCEDSERVER- _REGUTL>\PROCESSPARAMETERS NUMCLIENT_SESSION/CREATE/DEFAULT REGUTL> SHOW VALUE * NUMCLIENT_SESSION Key:SYSTEM\CurrentControlSet\Services\AdvancedServer\ProcessParameters Value: NumCLIENT_SESSION Type: Integer Current Data: 32 REGUTL> |
PWRK$REGUTL only allows you to create values known to the
Advanced Server. To create other keys and values, use another registry
editor listed in Section 7.2.2.1, How to Manage Server Parameters.
7.2.7 Deleting Server Parameters
The PWRK$REGUTL utility allows you to remove a server parameter and associated data from the OpenVMS Registry. To remove a parameter and its setting, use the DELETE VALUE command. For example, to remove the server parameter NumClient_Session from the registry, enter the following REGUTL command. The subsequent SHOW VALUE command results in a message indicating the server parameter does not exist in the registry.
REGUTL> DELETE VALUE \SYSTEM\CURRENTCONTROLSET\SERVICES- _REGUTL>\ADVANCEDSERVER\PROCESSPARAMETERS NUMCLIENT_SESSION REGUTL> SHOW VALUE * NUMCLIENT_SESSION %REGUTL-W-NOTINREG, known but not found in registry REGUTL> |
The server configuration parameters for the Advanced Server are stored and referenced from the OpenVMS Registry. The registry contains a collection of parameters that define the configuration of the Advanced Server software. When the Advanced Server is installed, default settings are assigned to these parameters. For information about managing server configuration parameters, see Section 7.2, Managing Server Configuration Parameters.
This appendix lists the configuration parameters, including:
For more information about managing the server configuration parameters
in the OpenVMS Registry, refer to Section 7.2, Managing Server Configuration Parameters.
A.1 Server Upgrade and Migration
On PATHWORKS for OpenVMS servers, the LANMAN.INI file is used to modify and store server parameters. Advanced Server stores these parameters in the OpenVMS Registry, which is similar to the Windows NT Registry.
The Advanced Server for OpenVMS software relies on the OpenVMS Registry to store and reference server parameters. Parameters stored in the LANMAN.INI file are not recognized by the Advanced Server.
If you are upgrading a system from PATHWORKS V6 for OpenVMS (Advanced Server) to Advanced Server for OpenVMS, the parameters and settings in the existing LANMAN.INI file are migrated to Registry parameters when you run the PWRK$CONFIG.COM initial configuration procedure.
When the configuration procedure migrates LANMAN.INI parameters to the
registry, it creates the LanmanIniMigrated value in
the Advanced Server Parameters key, and, as the associated data, stores
the date when the parameters were migrated from the LANMAN.INI file to
the OpenVMS Registry.
A.2 OpenVMS Registry Values
Table A-1, Registry Value Terminology, describes the terms used in this appendix to describe the server configuration parameters and how they are stored in the OpenVMS Registry.
| Term | Definition | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Key |
The path to follow from the root key
HKEY_LOCAL_MACHINE to find the value. |
||||||||||
| Value | The name under which the server configuration parameter is stored in the OpenVMS Registry | ||||||||||
| Valid Data | Describes the valid parameters of the data associated with the value, such as minimum and maximum values for integer data. | ||||||||||
| Default | The data associated with the value by default. | ||||||||||
| LANMAN.INI Section Name | For parameters migrated from the LANMAN.INI file, the LANMAN.INI section name | ||||||||||
| LANMAN.INI Keyword | For parameters migrated from the LANMAN.INI file, the LANMAN.INI parameter name. | ||||||||||
| Keyword Type | The type of parameter, either static or dynamic. If you modify a static parameter, you must restart the server for the change to be effective. If you modify a dynamic parameter, changes are effective the next time the parameter is referenced. | ||||||||||
| Data Type |
The type of data that may be associated with the value. The data type
information as displayed by the PWRK$REGUTL utility, and the
information displayed by the Windows NT registry editor, REGEDT32, are
listed below. For more information about using REGEDT32 to display
server configuration parameters in the OpenVMS Registry, see
Section 7.2.1.1, Registry Architecture.
|
For more information about managing the server configuration parameters stored in the OpenVMS Registry, refer to Section 7.2, Managing Server Configuration Parameters.
The following sections describe many of the server configuration parameters that can be stored in the OpenVMS Registry. Most of these are available for modification. You may see additional values in the OpenVMS Registry that are not documented here; you should not modify undocumented values.
A.2.1 Computer Name Parameters
The Computer Name key may include values that specify the way the
server is identified on the network.
The Computer Name key is:
SYSTEM\CurrentControlSet\Control\ComputerName\ComputerName |
Table A-2, Computer Name Values, lists the values that may be stored in the Computer Name key.
| Value | Description | |
|---|---|---|
| ComputerName_ nodename |
Specifies the name of the server on the network. This value allows
users to connect to the server using the specified node name.
Do not change the computer name by editing the OpenVMS Registry. To change the computer name, use the PWRK$CONFIG.COM configuration procedure. |
|
| Valid Data: | Up to 15 alphanumeric characters | |
| Default Data: | The server node name | |
| LANMAN.INI Section: | NODE_ servername | |
| LANMAN.INI Keyword: | listenname | |
| Parameter Type: | Static | |
| Data Type: | String | |
| AliasName |
Specifies the Advanced Server cluster alias. This value allows users to
connect to the server in an OpenVMS cluster configuration. (Refer to
Section 2.4.1, About the Advanced Server Cluster Alias for more information.)
Do not change the Advanced Server cluster alias by editing the OpenVMS Registry. To change the PATHWORKS cluster alias, use the PWRK$CONFIG.COM configuration procedure. |
|
| Valid Data: | Alphanumeric string | |
| Default Data: | OpenVMS cluster alias | |
| LANMAN.INI Section: | VMSSERVER | |
| LANMAN.INI Keyword: | pwrkalias | |
| Parameter Type: | Static | |
| Data Type: | String | |
The Browser Parameters key may include values that specify how the server deals with Browser activity. The Master Browser polls for domains, and builds and updates a master list of its domains. The backup Browser sends a request to the Master Browser to update its own list. The Browser service is always started at server startup.
The key containing the Browser values is:
SYSTEM\CurrentControlSet\Services\Browser\Parameters |
Table A-3, Browser Values, lists the values that may be stored in the Browser Parameters key.
| Value | Description | |
|---|---|---|
| MasterUpdate | Specifies the interval after which domain updates occur. | |
| Valid Data: |
Minimum: 60
Maximum: unlimited |
|
| Default Data: | 720 seconds (12 minutes) | |
| LANMAN.INI Section: | Browser | |
| LANMAN.INI Keyword: | masterupdate | |
| Parameter Type: | Static | |
| Data Type: | Integer | |
| BackupUpdate | Specifies the interval after which a backup Browser updates its list by querying the Master Browser. | |
| Valid Data: |
Minimum: 60
Maximum: unlimited |
|
| Default Data: | 720 seconds (12 minutes) | |
| LANMAN.INI Section: | Browser | |
| LANMAN.INI Keyword: | backupupdate | |
| Parameter Type: | Dynamic | |
| Data Type: | Integer | |
| BackupRecovery | Specifies the interval after which recovery is initiated if the backup Browser gets no response from the Master Browser. | |
| Valid Data: |
Minimum: 60
Maximum: unlimited |
|
| Default Data: | 1800 seconds (30 minutes) | |
| LANMAN.INI Section: | Browser | |
| LANMAN.INI Keyword: | backuprecovery | |
| Parameter Type: | Static | |
| Data Type: | Integer | |
| MoreLog | Specifies whether the Browser is to log more details. | |
| Valid Data: | YES or NO | |
| Default Data: | NO | |
| LANMAN.INI Section: | Browser | |
| LANMAN.INI Keyword: | morelog | |
| Parameter Type: | Static | |
| Data Type: | String | |
| Previous | Next | Contents | Index |