HP OpenVMS Systems
HP Advanced Server V7.3B for OpenVMS
Always read the product documentation prior to using the software. This
chapter describes additional guidelines for using the Advanced Server for OpenVMS
3.1 Changes Introduced with Version 7.3A of the Advanced Server for OpenVMS
This section covers changes to the latest release of the Advanced Server for OpenVMS that you might notice and which are not listed in Section 2.5, New Features Provided by Advanced Server V7.3A for OpenVMS.
Beginning with OpenVMS Version 7.3-1, an option for case-sensitive lookups of file names is supported. Case-blind file name lookup is the default behavior for OpenVMS and the Advanced Server. As reported in the OpenVMS Alpha Version 7.3-1 Release Notes, case-sensitive file name lookup is a very significant change in behavior and cannot be expected to work seamlessly with existing applications. Likewise, command line processing of case-sensitive commands might result in unexpected behavior. HP recommends that you do not enable this feature on systems that run the Advanced Server. For more information, see Section 13.4.17, Case Sensitivity.
The installation software calculates the system disk space required for installation.
Table 3-1 lists the approximate amount of free disk space on the OpenVMS system disk that is required during the installation procedure.
|Components||Free Disk Space|
|Complete Advanced Server||150,000|
|Standalone License Server||30,000|
|Standalone external authentication images||5,000|
|Standalone License Server and external authentication images||35,000|
Note that if the available space is barely enough to install the kit, you might see messages similar to these during the installation:
%PCSI-E-WRITEERR, error writing DISK$AXP072:[VMS$COMMON.][SYSEXE]DEC-AXPVMS-VMS- V0702-1.PCSI$DATABASE;1 -RMS-F-FUL, device full (insufficient space for allocation) %PCSI-E-CLOSEOUT, error closing DISK$AXP072:[VMS$COMMON.][SYSEXE]DEC-AXPVMS-VMS- V0702-1.PCSI$DATABASE;1 as output -RMS-F-FUL, device full (insufficient space for allocation) %PCSI-E-S_OPFAIL, operation failed %PCSIUI-E-ABORT, operation terminated due to an unrecoverable error condition
The software installation procedure (PCSI) has completed its task of
installing the product, but does not have space to record its success.
HP recommends that you make additional space available and install the
3.3 Server Installation
Advanced Server for OpenVMS provides a single installation procedure, using the POLYCENTER Software Installation (PCSI) utility, that allows you to choose one of the following installations:
The Advanced Server for OpenVMS requires an OpenVMS Alpha operating system, Version 7.3-1 and Version 7.3-2.
Consider the following restrictions related to server installation:
Before attempting to install the Advanced Server, HP recommends that you check your system for the SYS$UPDATE:PWVN$IVP.DAT file and remove it. Previous versions of PWVN$DEINSTAL.COM failed to remove the file. If SYS$UPDATE:PWVN$IVP.DAT is present, the installation assumes that Netware is still present and fails.
Refer to the HP Advanced Server for OpenVMS Server Installation and Configuration Guide for more information.
3.3.2 Upgrading the Server
This section provides several guidelines for upgrading your server that
are not documented elsewhere.
18.104.22.168 Upgrading Your Server and OpenVMS
If you plan to upgrade an OpenVMS Version 7.2-1x system to Version 7.3x, and that system is running an Advanced Server for OpenVMS version prior to V7.3, first upgrade the Advanced Server for OpenVMS to the latest version before you upgrade the OpenVMS system.
If you are running V7.3 of the Advanced Server for OpenVMS on an
OpenVMS Version 7.2-1x, then first upgrade the OpenVMS system
to Version 7.3x before you upgrade the Advanced Server to its
22.214.171.124 Upgrading a Server with a Large Share Database
If your share database is extremely large, see Section 13.2.2, Upgrading Large Share Databases, prior to
running PWRK$CONFIG.COM to perform the upgrade.
126.96.36.199 Upgrading an Advanced Server V7.3 for OpenVMS Member Server
As with Windows NT workstations, the Advanced Server V7.3B for OpenVMS member server supports the Power Users group, which includes more privileges than the member server's local domain User's group, namely the privilege to share and stop sharing directories and printers. On a fresh installation of the Advanced Server V7.3B for OpenVMS, the Power Users group is included in the member's local domain database after changing the server's role to member server. However, when upgrading an Advanced Server V7.3 for OpenVMS member server to Advanced Server V7.3B for OpenVMS, the Power User's group will not be included in the member server's local domain database. To add this group to the database, do the following:
$ SAMCHECK -R
If you currently have Version 7.3-ECO1 or 7.3-ECO2 of the Advanced Server for OpenVMS installed on your system, then when you install Advanced Server V7.3A for OpenVMS or any ECOs to V7.3A, the PCSI installation procedure displays the warning messages such as the following, which you can ignore:
%PCSI-W-VERLOW, you have selected a lower version of an installed product -PCSI-W-VERINS, the installation of product CPQ AXPVMS ADVANCEDSERVER V7.3-A -PCSI-W-VERREM, will remove current product CPQ AXPVMS ADVANCEDSERVER V7.3-1 Do you want to continue? [YES]
As you can see from the warning messages, PCSI translates the Version 7.3-ECO1 kit version string (V0703-1) to V7.3-1, which is higher than V7.3-A, the translation for the Version 7.3A kit version string (V0703-A). Of course, in actuality, the Advanced Server V7.3A for OpenVMS is higher than Advanced Server V7.3-ECO1 for OpenVMS.
Ignore the warning messages and continue, as indicated by the following message that displays prior to PCSI's warning messages:
******************************************************* You will soon see a warning message claiming the version to be installed is lower than the version already installed. Disregard that message. It is safe to continue with the installation. You are installing a higher version. *******************************************************
The Advanced Server provides several configuration utilities:
The PWRK$CONFIG.COM configuration procedure allows you to:
You run the PWRK$CONFIG.COM configuration procedure after installing
the Advanced Server. You may run it again at a later time if you want to
reconfigure the Advanced Server. For more information about installing
and configuring the Advanced Server for OpenVMS software, refer to the HP Advanced Server for OpenVMS Server Installation and Configuration Guide.
For restrictions regarding member servers joining a domain, see
Section 13.10.4, Member Server Role Restrictions.
3.4.2 Configuring Your Server to Participate as a Browser
Beginning with Version 7.3A of the Advanced Server for OpenVMS, the server uses the OpenVMS Registry value MaintainServerList to determine whether your server participates as a browser (when set to yes, your server participates as a browser; when set to no, it does not participate as a browser).
By default, this parameter is normally set to YES. However, if you have upgraded your server from Version 7.3-ECO1 or earlier, the previous server might have automatically set the MaintainServerList registry value to NO. The earlier server still participated as a browser because it ignored the MaintainServerList value. Alternatively, you might manually set the registry value to NO on your current server.
In any case, if the PWRK$CONFIG.COM configuration procedure now detects that the MaintainServerList value is set to NO, it will prompt you as follows to give you a chance to change that if you intend to have your server participate as a browser:
Currently this server is not configured to participate as a browser. This server will not gather information about other computers in the domain because the registry value MaintainServerList is set to No. This setting of the registry value may have been made inadvertently in previous versions of the Advanced Server. Would you like your computer to participate as a browser? ([Y]/N)
To manage server-specific configuration parameters that determine the system environment in which the server operates, you can use the Configuration Manager, a character-cell user interface. These parameters are, for the most part, directly or indirectly related to the environment in which the Advanced Server operates, such as the server's usage of OpenVMS system resources and physical memory. Examples of these parameters include the server's client capacity, the size of its data cache, and which network transports it should use. The parameters modified by the Configuration Manager are not stored in the OpenVMS Registry.
The PWRK$CONFIG.COM configuration procedure gives you the option of invoking the Configuration Manager. After installing and configuring your server, you can also invoke the Configuration Manager at the OpenVMS DCL ($) prompt as follows:
Refer to the HP Advanced Server for OpenVMS Server Administrator's Guide for more information about using the
3.4.4 Modifying Server Parameters Stored in the OpenVMS Registry
The Advanced Server for OpenVMS software relies on the OpenVMS Registry to store and reference server parameters. The OpenVMS Registry is similar to the Windows NT Registry.
To manage server-specific configuration parameters that are stored in the OpenVMS Registry, you can use the PWRK$REGUTL utility. These parameters affect the behavior of the Advanced Server but not, for the most part, file server resource consumption. Examples of these parameters include the name for the Advanced Server on the network, its cluster alias, values that specify how the Advanced Server deals with Browser activity, values that affect network logon, and values that define the shares created automatically by the Advanced Server.
The PWRK$REGUTL utility is available to use after you install the Advanced Server software. The program is found at:
If your process has included the Advanced Server command definitions in the PWRK$DEFINE_COMMANDS.COM file, or if you have defined the REGUTL command, you can start the PWRK$REGUTL utility by entering the REGUTL command. To define the REGUTL command and start the utility, enter the following commands at the OpenVMS command prompt:
$ REGUTL :== $SYS$SYSTEM:PWRK$REGUTL.EXE $ REGUTL REGUTL>
As shown, the PWRK$REGUTL utility responds by displaying the REGUTL> prompt.
To use PWRK$REGUTL to access the OpenVMS Registry, your process must have one of the following:
You can use the OpenVMS REG$CP utility as well as PWRK$REGUTL to manage parameters in the OpenVMS Registry. However, HP recommends that you use PWRK$REGUTL to manage server configuration parameters, because it has built-in knowledge of keys and values used by the Advanced Server, including the attributes of the data, such as minimum, maximum, and default values.
For more information on the OpenVMS Registry and how to manage server
parameters, refer to the HP Advanced Server for OpenVMS Server Administrator's Guide. For information on starting the
OpenVMS Registry, refer to the HP Advanced Server for OpenVMS Server Installation and Configuration Guide. For more information on
setting up and managing the OpenVMS Registry, refer to the
OpenVMS System Manager's Manual or the COM, Registry, and Events for OpenVMS Developer's Guide (included in the OpenVMS
188.8.131.52 LANMAN.INI Parameters Are Migrated to the OpenVMS Registry When Upgrading from PATHWORKS for OpenVMS
If you are upgrading a system from a previous PATHWORKS for OpenVMS product to Advanced Server for OpenVMS, the parameters and settings in the existing LANMAN.INI file are migrated to the OpenVMS Registry when you run the PWRK$CONFIG.COM configuration procedure after installation. In specific, the PWRK$CONFIG.COM procedure invokes the SYS$UPDATE:PWRK$MIGRATE_INI.COM file to perform a "one time" setup of the registry and migration of the parameters. After the migration is complete, the LANMAN.INI file is retained but not used. A parameter is set in the OpenVMS Registry indicating that the server parameters have been migrated. As long as this parameter exists and has a non-NULL value, subsequent invocations of the PWRK$MIGRATE_INI.COM file will skip over the migration process.
You can view this parameter in the registry using the following commands:
$ REGUTL :== $SYS$SYSTEM:PWRK$REGUTL $ REGUTL SHOW VALUE * LanmanIniMigrated
The Advanced Server startup procedure records a list of all Advanced Server parameters that are set in the OpenVMS Registry. You can use this list as a reference if you should ever need the latest parameter values. The list is stored in the following location, where nodename is the name of your server node:
The Advanced Server requires that the following server configuration parameters, which are stored in the OpenVMS Registry, always match the corresponding information in the Advanced Server Security Account Manager (SAM) database:
These parameters are initially defined when you run the PWRK$CONFIG configuration procedure, as described in the HP Advanced Server for OpenVMS Server Installation and Configuration Guide. The configuration procedure stores the information that you provide, both in the OpenVMS Registry and in the SAM database.
If the information stored in these two locations becomes inconsistent, the Advanced Server will not operate properly, and the following problems can occur:
$ @SYS$UPDATE:PWRK$CONFIG.COM Advanced Server V7.3A for OpenVMS Configuration Procedure . . . Enter disk device name where the Advanced Server data files will be stored [PWROOT:]: Checking to see if OpenVMS Registry Services are available... Verifying SAM database files... The SAM database is too corrupt to check or repair. %PWRK-F-SAMCHECK Error initializing Sam database files
$ @SYS$STARTUP:PWRK$STARTUP.COM The file server will use DECnet, NetBEUI, TCP/IP. Advanced Server mail notification will use DECnet. Process NETBIOS created with identification 00000143 Process PWRK$NBDAEMON created with identification 00000145 Process PWRK$KNBDAEMON created with identification 00000147 Process PWRK$LICENSE_R created with identification 00000149 Checking to see if OpenVMS Registry Services are available... %PWRK-F-INCOMPLETE, Advanced Server for OpenVMS has not been completely configured -PWRK-I-CONFIG, please execute @SYS$UPDATE:PWRK$CONFIG.COM