HP OpenVMS Systems Documentation
Compaq PATHWORKS V6.1 for OpenVMS (Advanced
Always read the product documentation prior to using the software. This
chapter describes additional guidelines for using the PATHWORKS Advanced Server
3.1 Disk Space Requirements
The installation software calculates the system disk space required for installation. The installation software needs room on the system disk to unpack the savesets containing the software options requested by the installer. The installation procedure calculates the needed space based on the sizes of the savesets to be unpacked, adding an additional 4500 blocks needed for the unpacking process. (The actual space occupied by the PATHWORKS Advanced Server software after installation and configuration might be less, but additional room is needed on the installation device to run the configuration procedure (PWRK$CONFIG).)
Table 3-1 lists the amount of free disk space on the OpenVMS system disk that is required during the installation procedure.
|To install these components...||You need this number of blocks on an Alpha system...||You need this number of blocks on a VAX system...|
|PATHWORKS Advanced Server||160,000 1||131,000 1|
|Standalone License Server||160,000||131,000|
|External authentication images only||160,000||131,000|
|Upgrade utility only||45,500||30,500|
3.2 Upgrading a Version 5 Member Server or Standalone Server
To upgrade a PATHWORKS V5 for OpenVMS (LAN Manager) member server or standalone server, run the
Upgrade utility. (If the upgrade fails, see the note in Section 7.2.1, Upgrade Fails with an RMS-W-RTB Error.)
By default, the Upgrade utility configures the PATHWORKS V6.1
server role as a backup domain controller (BDC). You can change the
role after the upgrade completes. To change the role to a primary
domain controller (PDC), use the PWRK$CONFIG.COM configuration
procedure (first configuration run only) or the ADMINISTER SET
COMPUTER/ROLE command. To change the role to a member server, you must
use the PWRK$CONFIG.COM configuration procedure. For more information
on using the Upgrade utility, refer to the Compaq PATHWORKS for OpenVMS (Advanced Server) Server Migration Guide. For more
information on using the PWRK$CONFIG.COM configuration procedure, refer
to the Compaq PATHWORKS for OpenVMS (Advanced Server) Server Installation and Configuration Guide. You can find information on the ADMINISTER SET
COMPUTER command in the Compaq Advanced Server for OpenVMS Commands Reference Manual or through the ADMINISTER command
3.2.1 Upgrading File Security
Files with security specified entirely according to PATHWORKS V5 for OpenVMS (LAN Manager) security can be upgraded by the Upgrade utility. As an alternative, you can enable the Advanced Server to perform dynamic security upgrades of the files when they are accessed by the server. Compaq recommends letting the Upgrade utility perform the file security upgrade, especially if you are upgrading a BDC or standalone server to a member server.
When a member server performs dynamic security upgrade of PATHWORKS V5 for OpenVMS (LAN Manager) files, it upgrades the security ACE for a user or group by first looking in the member server's local Security Account Manager (SAM) database for the security identifier (SID) of the user/group. If the member server does not find the user/group in the local SAM, it then looks for the SID in the SAM on the primary domain controller (PDC). When it finds the SID, it creates an upgraded (Version 6.0) security descriptor and applies it to the file. All built-in users and groups, such as Administrator and Administrators, are located in the member server's local SAM database. So the SIDS of built-in users and groups will be from the local SAM database.
As an example, all Version 5 security ACEs for the Version 5 user ADMIN
(where the Version 5 user ADMIN is upgraded to the Version 6 user
Administrator during the User upgrade) will be upgraded using the SID
from the member server's local SAM database.
3.3 Server Installation in OpenVMS Clusters with Multiple System Disks
When installing the Advanced Server on an OpenVMS Cluster member, you must shut down the server and, possibly, reboot the systems running the server, if both of the following conditions are true:
To avoid having to reboot the systems that are already running the Advanced Server, the system administrator can deassign the logical name (PWRK$REBOOT_REQUIRED) that forces the reboot to occur on each affected node, as follows:
$ DEASSIGN/SYSTEM PWRK$REBOOT_REQUIRED
The Advanced Server provides the following configuration utilities:
In addition, the LANMAN.INI file stores server parameters that affect
the behavior of the Advanced Server but not, for the most part, file
server resource consumption.
3.4.1 Initial Server Configuration Procedure
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 PATHWORKS for OpenVMS (Advanced Server) software, refer to the Compaq PATHWORKS for OpenVMS (Advanced Server) Server Installation and Configuration Guide.
3.4.2 Modifying Server System Environment Parameters
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 LANMAN.INI file.
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 Compaq PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide for more information about using the
3.4.3 LANMAN.INI Parameters
The LANMAN.INI configuration file stores parameters that 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.
When the PATHWORKS Advanced Server is installed, the LANMAN.INI file contains values for certain keywords. Other keywords, and the titles of the sections to which they belong, are added when you run the Configuration Manager or edit the LANMAN.INI file. If a keyword does not appear in the file (or is commented out with a semicolon), it is set to its default value.
Before you change any keywords in the LANMAN.INI file, you should understand the relationship between the LANMAN.INI file entries and server parameter default settings. All server parameters have default settings.
With certain exceptions, you can edit the LANMAN.INI file to set keywords to values other than the server defaults. Server parameter defaults do not appear in the LANMAN.INI file. A value assigned to any keyword in the LANMAN.INI file always supersedes the default value for that keyword.
The keywords whose value you cannot change by editing the LANMAN.INI file are:
To change these parameters, use the PWRK$CONFIG.COM configuration command procedure.
When you want to set the value of a keyword to something other than the
default, you must edit the LANMAN.INI file, locate or add the
appropriate section title in the file, and then add the desired
keyword=value entry. For more information, refer to the
Compaq PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide.
3.5 Startup of the Advanced Server
Beginning with PATHWORKS V6.0C-ECO1, when you invoke the PWRK$STARTUP procedure, or use the PWSTART command defined in the command definition file SYS$STARTUP:PWRK$DEFINE_COMMANDS.COM, the PWRK$STARTUP script no longer stops the file server if it is running. Instead, it reports PATHWORKS is running and continues. PWRK$STARTUP.COM issues the following message and exits with a status of 1 if the file server is already running:
PWRK-I-RUNNING, Advanced Server is already running on this node
If you would like the PWRK$STARTUP procedure (or PWSTART command) to stop the server automatically, use the PWRESTART command (contained in the PWRK$DEFINE_COMMANDS.COM file). PWRESTART invokes PWRK$STARTUP with RESTART as the P1 parameter, which shuts down the server before restarting.
To shut down and restart a file server, use one of the following:
If the server is already running, a message will indicate so. If it is
not running, it will start.
3.6 Shutting Down the OpenVMS System with the Advanced Server
Before shutting down the OpenVMS system, Compaq recommends that you
first stop the Advanced Server.
3.7 Guideline for File Share Description Strings
Compaq recommends that the description (comment) strings defined for
file or directory shares be limited to at most 32 characters in length.
Strings exceeding that limit are not cached by the file server, and
therefore, for each server transaction, must be accessed from disk, at
the expense of server performance.
3.8 Startup THREAD Resume Error Message
When the server starts up, a "THREAD\resume" error message might appear, as in the following example:
24-JAN-2000 15:16:03.40 20400137:AST_LVL THREAD\resume_0: threadinit has not been called!! 24-JAN-2000 15:16:03.41 20400137:AST_LVL results of the execution of this function are unpredictable!!
The condition being reported is benign and does not affect the
operation of the file server. You can safely ignore this error message.
3.9 "LANMAN.INI Has an Unknown Keyword" Messages in System Event Log
The system event log might include "LANMAN.INI Has an Unknown Keyword" error messages such as the following:
T Date Time Source Category Event User Computer - -------- ----------- --------- ----------- ------ ------- ---------- W 02/15/99 10:32:15 AM SERVER None 6123 N/A ALP010 ASU6123: LANMAN.INI has an unknown keyword [vmsserver] hostpasswordsync.
These messages might indicate that the LANMAN.INI file includes outdated parameters (for example, PATHWORKS V5 parameters that are no longer valid with PATHWORKS V6 and later versions), or that the parameters are misspelled.
To prevent these messages from appearing again, modify the LANMAN.INI
file to correct the spelling of misspelled parameters and to remove any
3.10 The Advanced Server in an OpenVMS Cluster
The following list summarizes some of the most important considerations
for servers in an OpenVMS Cluster. Refer to the appropriate
documentation for more information.
3.10.1 Installation and Configuration Considerations for Clusters
PATHWORKS for OpenVMS (Advanced Server) versions prior to V6.0C use the PWRK$LMDMN process to validate logons and replicate the domain security accounts database. Now the PWRK$LMSRV process provides this functionality instead. As noted in Section 2.2.3, Domain Database Replication and Network Logon Performance Improvement, this serves to streamline the operation of the Advanced Server, especially during replication.