HP OpenVMS Systems

HP Advanced Server V7.3B for OpenVMS
Release Notes

Always read the product documentation prior to using the software. This chapter describes additional guidelines for using the Advanced Server for OpenVMS software.

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.

• In Version 7.3-ECO2 of the Advanced Server for OpenVMS, the startup software checks that each member of an OpenVMS Cluster:
  • Uses the same Rightslist file (RIGHTSLIST.DAT)
  • Uses the same system user authorization file (SYS$COMMON:[SYSEXE]SYSUAF.DAT)
  • Uses the same Advanced Server data directory location for PWRK$ROOT (PWRK$COMMONROOT:)
  
  If the V7.3-ECO2 software detects any inconsistencies, the startup procedure's response depends on the definition of the PWRK$IGNORE_INCONSISTENCY logical (using the command DEFINE/SYSTEM/EXECUTIVE). If the logical is undefined, the startup procedure aborts, a message indicates what is wrong, and a second message acknowledges that you might intentionally want the server to run with the inconsistencies detected and that you can define the PWRK$IGNORE_INCONSISTENCY logical accordingly to ignore the inconsistencies.
  With Advanced Server V7.3A for OpenVMS, this software check has been eliminated. You will not see messages indicating such inconsistencies. Before you start the server, make sure no such inconsistencies exist among cluster members.
• The EIA0: network interface device (for Ethernet adapters DE600 and DE602, for example) is now included in the server's list of known devices, for all transport layers (TCP/IP, DECnet and NetBEUI).
• The default cluster name in PWRK$CONFIG for new installations has been changed from NODE_ALIAS to NODE-ALIAS. This has been done to avoid conflicts with DNS servers that do not accept the underscore (_) as a valid character.
• The following key is now defined in the OpenVMS Registry. (See the note in Section 6.4.3, Unable to View or Change Properties of a Windows-Managed Printer.)

  HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\CONTROL\PRINT\PROVIDERS

• If the configuration procedure (PWRK$CONFIG.COM) detects that your server is not configured to participate as a browser, it will prompt you, giving you the opportunity to allow the server to participate as a browser. For more information, see Section 3.4.2, Configuring Your Server to Participate as a Browser.
• The maximum file size that the Advanced Server for OpenVMS can handle for creating, copying, reading, or writing files is now 4 GBs. Previously, the maximum size was 2 GBs. For related information, see Section 7.3.1.
• The default for the data cache size has been increased from 2048 Kbytes (2 Mbytes) to 8192 Kbytes (8 Mbytes). The latter value is sufficient for most server configurations.
• Support of the Power Users group on members servers (as supported on Windows NT workstations). The Power User's group includes more privileges than the member server's domain User's group, namely the privilege to share and stop sharing directories and printers. For information about adding support for the Power User's group when upgrading an Advanced Server V7.3 for OpenVMS member server to Advanced Server V7.3B for OpenVMS, see Section 3.3.2.3, Upgrading an Advanced Server V7.3 for OpenVMS Member Server.

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.

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 product again.

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 complete Advanced Server for OpenVMS software (includes the License Server and external authentication images)
• Standalone License Server only
• Standalone external authentication images only
• Both the standalone License Server and the external authentication images

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:

• You cannot install the Advanced Server for OpenVMS software on a VAX system.
• You cannot run the PATHWORKS for OpenVMS (Advanced Server) on cluster members of the same cluster that is running the Advanced Server for OpenVMS. All cluster members must run the same version of the file server.
• The Advanced Server for OpenVMS can run on members of an OpenVMS Cluster that are running OpenVMS Alpha Version 7.2-2, 7.3, or 7.3-1. If you are running a mixed-version cluster that has some nodes running OpenVMS Version 7.2-1H1 and earlier and other nodes running OpenVMS Version 7.2-2 and later, be aware that the Registry server on the earlier systems is incompatible with the Registry server on the later systems. Therefore, you cannot run Registry servers or clients (such as the Advanced Server for OpenVMS) on both the earlier and later OpenVMS systems at the same time. For more information, refer to the OpenVMS Alpha release notes for the latest system you are running.
• You cannot run the PATHWORKS for OpenVMS (NetWare) server on the same system or cluster as the Advanced Server for OpenVMS. You must deinstall the NetWare server before installing the Advanced Server for OpenVMS.

  Note 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.

• In an OpenVMS Cluster, when installing the Advanced Server V7.3A for OpenVMS over a previous installation of V7.3, V7.3-ECO1, or V7.3-ECO2 of the Advanced Server for OpenVMS, you must reboot your system before you run the configuration procedure (PWRK$CONFIG.COM). The installation procedure will notify you while presenting the reboot options that you must reboot your system before running PWRK$CONFIG.COM.
  If you do reboot as recommended, you will not have to reboot your system again after configuring your server, unless you modify configuration parameters affecting system resources (such as changes to the physical memory to be used by the configuration, client capacity, or the data cache size).

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.

3.3.2.1 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 current version.

3.3.2.2 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.

3.3.2.3 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:

1. Back up the old (Advanced Server V7.3 for OpenVMS) databases.
2. After upgrading the member server to Advanced Server V7.3B for OpenVMS, invoke the following command at the DCL prompt, as shown:

   $ SAMCHECK -R

   
   This command updates the database to include the Power Users group.

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 for determining the initial setup and configuration parameters. The procedure also allows you to start the Advanced Server. You can use the procedure to reconfigure the server at a later time.
• The Configuration Manager for managing server-specific configuration parameters that affect the system environment in which the Advanced Server operates. The PWRK$CONFIG.COM configuration procedure gives you the option of invoking the Configuration Manager, or you can invoke it manually with the ADMINISTER/CONFIGURATION command at the OpenVMS DCL prompt.
• The PWRK$REGUTL utility for managing parameters stored in the OpenVMS Registry that affect the behavior of the Advanced Server but not, for the most part, file server resource consumption.

The PWRK$CONFIG.COM configuration procedure allows you to:

• Perform basic on-disk structure setup
• Modify server system environment parameters (using the Configuration Manager)
• Modify initial server configuration parameters that determine, for example:
  • Domain administrator account information
  • Domain name
  • Whether to run the License Server
  • Whether to enable certain services (Timesource, Alerter, and Netlogon)
  • Server role (primary domain controller, backup domain controller, or member server)
  • Computer name
  • Server cluster alias
  • Server announcement string
  • Server language
  • Printer management mode (locally, using the ADMINISTER interface, or remotely, using Windows NT print services)
• Start the Advanced Server

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:

$ ADMINISTER/CONFIGURATION

Refer to the HP Advanced Server for OpenVMS Server Administrator's Guide for more information about using the Configuration Manager.

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:

SYS$SYSTEM:PWRK$REGUTL.EXE

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:

• OpenVMS SYSPRV system privileges
• REG$UPDATE right identifier associated with the user account

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 Documentation CD-ROM).

3.4.4.1 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:

PWRK$PARAMS:PWRK$REGISTRY_PARAMS_nodename.LIS

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:

• DomainName
• ComputerName_nodename
• AliasName (applies to OpenVMS Clusters only)

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:

• If the ComputerName_nodename or AliasName parameter do not match the corresponding information in the SAM database, the server might start but will encounter problems communicating with other computers (clients and servers) in the network.
• If the DomainName value in the OpenVMS Registry has data that does not match the domain name in the SAM database, neither the configuration procedure nor the startup procedure will complete:
  • If the configuration procedure (PWRK$CONFIG.COM) determines that the DomainName parameter does not match the domain name in the SAM database, it displays the following messages and terminates:

    $ @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

  • If the startup procedure (PWRK$STARTUP.COM) determines that the DomainName parameter does not match the domain name in the SAM database, it displays the following messages and terminates:

    $ @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

To solve these problems, you must modify the data settings for the mismatched parameters in the OpenVMS Registry to match the corresponding information in the SAM database.