Compaq Advanced Server for OpenVMS
Installation and Configuration Guide
The procedure verifies the installation, and then finishes.
2.1.3 What To Do After the Installation Completes
If you have installed the external authentication images only, you can
proceed to enable external authentication, as explained in
Section 5.7, Setting Up External Authentication. For other installations, do the following after the
- If you had a previous version of Advanced Server for OpenVMS running on your
system, reboot your system before starting the Advanced Server, if
necessary. See the discussion of circumstances when reboots are
necessary, in the explanatory text following Example 2-3, Sample Installation Procedure---Part 3.
- Proceed to Chapter 3 to configure the Advanced Server for OpenVMS.
After the installation completes, you can display a list of the
Advanced Server for OpenVMS files that were installed by entering the following
$ PRODUCT LIST ADVANCEDSERVER /SOURCE=directory-path
where directory-path specifies the disk and directory name for
the source drive that holds the Advanced Server for OpenVMS kit. For example,
/SOURCE=DAD$100:[ASOVMS073]. If you do not specify the source
qualifier, the POLYCENTER Software Installation utility searches the
location defined by the logical name PCSI$SOURCE. If not defined, the
utility searches the current default directory.
2.2 Troubleshooting Installation Problems
The following sections describe some problems you can encounter if you
install Advanced Server for OpenVMS software in an environment that is not
2.2.1 Installing Advanced Server for OpenVMS Software on a VAX System
The Advanced Server does not run on OpenVMS VAX systems. If you attempt
to install the Advanced Server on a VAX system, the POLYCENTER Software
Installation utility procedure displays the following error message and
terminates the installation:
Advanced Server V7.3 for OpenVMS does not run on OpenVMS VAX
You can install this product on OpenVMS Alpha systems only.
2.2.2 Installing Advanced Server for OpenVMS on a System Running Another Advanced Server Image
If you attempt to install the Advanced Server for OpenVMS on a system (or anywhere in
a cluster) on which a PATHWORKS for OpenVMS or Advanced Server for OpenVMS image is running,
the installation procedure displays a message such as the following:
Advanced Server V7.3 for OpenVMS cannot be installed while
any Pathworks or Advanced Server processes are running.
If this node is part of a cluster, no node of the cluster
can be running any of those images.
At least one of the preconditions for installation have not been met.
See the Installation Guide for more information
%PCSI-E-S_OPFAIL, operation failed
%PCSIUI-E-ABORT, operation terminated due to an unrecoverable error condition
Stop these server images from running, and then restart the
2.2.3 System Disk Restrictions
If the installation procedure detects PATHWORKS (NetWare) files, the
procedure will notify you and request that you remove those files and
restart the installation procedure. The same is true if the
installation procedure detects
PATHWORKS for OpenVMS files or any Advanced Server files in a
SYS$SPECIFIC: directory. If certain images are detected in system
memory (such as the PWRK$STREAMSOS_V*.EXE file, as in Example 2-3, Sample Installation Procedure---Part 3),
the procedure will continue, notifying you that a reboot is necessary
before starting the Advanced Server for OpenVMS.
2.2.4 Installing Advanced Server for OpenVMS on a System with PATHWORKS for OpenVMS (Advanced Server), Version 6.0A or Earlier
If the system has Version 6.0A or earlier of PATHWORKS for OpenVMS (Advanced Server) installed,
the installation procedure displays the following message:
The migration path from PATHWORKS V6.0 to the Advanced
Server is valid, but not recommended. Do you want to
continue with the installation? [YES]:
Compaq recommends that you upgrade to Advanced Server V7.3 for OpenVMS from
PATHWORKS for OpenVMS (Advanced Server), Version 6.0C or later. To
upgrade from previous versions of the server, follow the migration path
described in Section 1.1.2, Upgrading to Advanced Server for OpenVMS, before you install Advanced Server V7.3 for OpenVMS.
2.3 Next Steps
To continue, depending on which server you are installing, do one of
Configuring the Advanced Server
This chapter describes how to configure the Advanced Server, and consists
of the following sections:
- Section 3.1, About the Advanced Server Configuration Procedure
- Section 3.2, Migrating LANMAN.INI Parameters to the OpenVMS Registry
- Section 3.3, Before You Start the Advanced Server Configuration Procedure
- Section 3.4, How to Start the Advanced Server Configuration Procedure
- Section 3.5, How to Respond to Advanced Server Configuration Prompts
- Section 3.6, How to Change Server Configuration Settings
- Section 3.7, Configuring the Advanced Server Domain Role
- Section 3.8, Configuring the Server Language
- Section 3.9, Configuring Windows NT Printer Management
- Section 3.10, Troubleshooting Configuration Procedure Problems
- Section 3.11, The Advanced Server Network Adapter
- Section 3.12, Next Steps
3.1 About the Advanced Server Configuration Procedure
The Advanced Server initial configuration procedure, PWRK$CONFIG.COM, is
installed by the Advanced Server for OpenVMS installation procedure.
Like the installation procedure, the configuration procedure asks you a
series of questions (by displaying prompts). The procedure uses your
answers to configure the Advanced Server.
You can use the PWRK$CONFIG procedure to reconfigure the server at any
time later. Note that the script contents change after the first
3.1.1 What the Configuration Procedure Does
PWRK$CONFIG is a command procedure that:
- Creates the Advanced Server on-disk structure (shown in
Section E.2,Advanced Server On-Disk Structure).
- Upgrades any existing file server user account and share databases,
such as when upgrading the server from a previous version, or when the
currently configured language is not compatible with the language used
by the existing file server.
- If configuring a previously configured server, stores the original
accounts database in specially-created directories. (For more
information, see Section 3.10.3, If Problems Occur When Reconfiguring the Advanced Server.)
- Starts the Registry server if it is not already running.
- If you are upgrading from a PATHWORKS for OpenVMS server to
Advanced Server for OpenVMS, migrates server configuration parameters from the
PATHWORKS for OpenVMS LANMAN.INI file to the OpenVMS Registry. (For
more information, see Section 3.2, Migrating LANMAN.INI Parameters to the OpenVMS Registry.)
- Allows you to enter the Configuration Manager to modify
configuration parameters that affect the system environment
and to verify the configuration setting against the available system
resources. For example, you can specify the transports the server will
run and the maximum number of clients that can connect to the server
For more information about the Configuration
Manager, refer to the Compaq Advanced Server for OpenVMS Server Administrator's Guide.
- Allows you to modify server configuration default settings such as
server role, domain name, and the services that are enabled.
- On a server that will run as a primary domain controller or member
server, allows you to specify the Administrator account password.
- Gives you the option of starting the server.
After you install the server, you must run the PWRK$CONFIG
configuration procedure before you can start the server. In an OpenVMS
Cluster, before you start the server,
you must run PWRK$CONFIG on each node where you plan to run the server.
Although the nodes in an OpenVMS Cluster function as a single unit in a
domain, treat them as individual units for purposes of configuration.
3.2 Migrating LANMAN.INI Parameters to the OpenVMS Registry
The PATHWORKS for OpenVMS and Advanced Server for OpenVMS servers store server
parameters in different locations. PATHWORKS for OpenVMS servers use
the LANMAN.INI file to store server configuration parameters. The
Advanced Server for OpenVMS uses the OpenVMS Registry, which is similar to the
Windows NT registry. For information about managing the server
configuration parameters in the OpenVMS Registry, refer to the
Compaq Advanced Server for OpenVMS Server Administrator's Guide.
If you are upgrading a system from PATHWORKS for OpenVMS 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 for the first time after
installation. (The Advanced Server for OpenVMS does not read parameter settings from
the LANMAN.INI file.) After they have been migrated to the OpenVMS
Registry, you manage the parameters in the registry. The LANMAN.INI
file is retained in case the system will run PATHWORKS for OpenVMS again later.
The PWRK$CONFIG.COM configuration procedure performs a one-time
migration of the parameters. At the time the parameters are migrated
into the registry, the PWRK$CONFIG procedure sets the data associated
with the LanmanIniMigrated value in the OpenVMS
Registry. If this value exists and has data associated with it, the
PWRK$CONFIG procedure will omit the parameter migration process.
You can display the value and its associated data in the OpenVMS
Registry using the following commands:
$ REGUTL :== $SYS$SYSTEM:PWRK$REGUTL.EXE
$ REGUTL SHOW VALUE * LANMANINIMIGRATED
In the following example, the data displayed for the
LanmanIniMigrated value indicates that the parameters
were migrated on October 29, 2000:
Current Data: LANMAN.INI migrated on 29-OCT-2000 15:31:48.90
The following example shows what data might be displayed for the
LanmanIniMigrated value if you are configuring your
Advanced Server for OpenVMS on a system that has not had PATHWORKS for OpenVMS
configured on it (that is, you are not upgrading from PATHWORKS for
REGUTL> SHOW VALUE * LANMANINIMIGRATED
Current Data: No LANMAN.INI to migrate on 29-OCT-2000 15:31:48.90
Refer to the Compaq Advanced Server for OpenVMS Server Administrator's Guide for more information about using the
PWRK$REGUTL utility to manage server configuration parameters in the
3.3 Before You Start the Advanced Server Configuration Procedure
Before you start the PWRK$CONFIG command procedure, answer the
questions discussed in the following sections.
3.3.1 On What OpenVMS Disk Device Do You Want to Store the Advanced Server Data Files?
The data files include:
- Configuration parameter files
- License Server data files
- Log files
- Printer spool files
- Server data files
- Security Account Manager (SAM) database files
- Client-based server administration tools and license kits
- Virtual memory section files
By default, the configuration procedure copies the data files to the
system device (SYS$SYSDEVICE). However, you can specify any existing
OpenVMS disk device that has at least 85,000 free blocks of disk space.
The amount needed depends on the components installed.
When you select a disk for the Advanced Server data files, keep the
following in mind:
- The Advanced Server frequently accesses the data files copied to the
specified disk device, which generates input to and output from the
disk. Having these operations occur on the system disk can degrade the
performance of both the OpenVMS system and the Advanced Server.
Therefore, Compaq recommends that you specify a disk device
other than the system disk.
- On an OpenVMS Cluster with multiple system disks, all nodes on
which you plan to run the Advanced Server must use the same disk device
to store and access Advanced Server data files. Using separate disks on
separate cluster members is strictly prohibited.
- You can run the PWRK$CONFIG command procedure at any time, to
change the disk device where Advanced Server data files are stored.
PWRK$CONFIG automatically copies the data files to the new location and
deletes the data files from the current location.
3.3.2 Do You Want to Change the System Configuration Parameters Now?
If you respond "YES" to the prompt to change the system
configuration parameters, you start the Configuration Manager. The
Configuration Manager is a utility that allows you to modify and verify
the system environment configuration parameter settings, such as the
maximum number of clients that can connect to the server, the
percentage of physical memory the server can use, and which network
transports the server uses.
You can change the system configuration parameter settings after
starting the Advanced Server by using the Configuration Manager. For more
information, refer to the Compaq Advanced Server for OpenVMS Server Administrator's Guide. Section B.2, Sample Advanced Server Configuration Procedure, shows the basic
Configuration Manager screen displayed when you opt to change the
system configuration parameter settings during PWRK$CONFIG.
22.214.171.124 Configuring Transports for a Backup Domain Controller or Member Server
If you are configuring a server as a backup domain controller (BDC) or
a member server, you must select at least one transport that will also
be run by the primary domain controller (PDC). Otherwise, the
configuration will fail.
When you select the transports to run on a server that will participate
in wide area networking, keep the following in mind:
- In a wide area network, the TCP/IP transport is required. (DECnet
also supports wide area networks but the functionality it provides is
not as extensive as that provided by TCP/IP.)
In a cluster, all Advanced Server members must be in the same subnet.
- If you are configuring a BDC or member server to join an existing
domain where the PDC is on a different TCP/IP subnet, both the server
you are configuring and the PDC must be configured to use the TCP/IP
transport, and you must set up wide area networking using either a WINS
(Windows Internet Name Service) Server, a Domain Name System (DNS)
server, or an LMHOSTS file for NetBIOS name resolution, as described in
Chapter 6, Implementing a Wide Area Network. (You can select one, two, or all three of these methods
for name resolution.)
- If you are using WINS for network name resolution, both the PDC and
any BDCs and member servers should use a WINS Server to provide NetBIOS
If your Advanced Server will run in an OpenVMS Cluster, to gain the
benefits of load balancing and failover, clients should connect to the
Advanced Server using the Advanced Server cluster alias. However, the
Advanced Server does not dynamically register the Advanced Server cluster
alias with the WINS server. Therefore, you should define a static
multihomed entry for the Advanced Server alias in the WINS database. For
more information, see Section 6.3.1, Setting up WINS for OpenVMS Clusters. If you plan to use DNS for NetBIOS
name resolution, you might need to remove this static multihomed entry
from the WINS database (if clients are configured to use both WINS and
DNS for NetBIOS name resolution, they first query the WINS server to
resolve the name).
- If you are using the LMHOSTS file, it must be set up on the PDC as
well as the BDCs and member servers. Before you configure any BDC or
member server that is not on the same subnet as the PDC, make sure that
a special NetBIOS name entry for the PDC is in the LMHOSTS file on that
BDC or member server; otherwise, the BDC or member server will not find
the PDC and will fail to join the existing domain. This NetBIOS name
entry should be the same as the domain name, space padded to 15
characters, with the hexadecimal control character 1B appended to it.
You map the IP address of the PDC to this special name. For example, if
the domain name is LANGROUP and the PDC of LANGROUP is DOMPDC with an
IP address of 10.20.30.40, the BDCs and member servers would need to
add the following lines to their LMHOSTS file:
10.20.30.40 DOMPDC #PRE #DOM:LANGROUP
10.20.30.40 "LANGROUP \0x1B" #PRE
Note that the total number of characters within the quotes should
always be 20 characters (the domain name padded to 15 characters, plus
the five characters required for the hexadecimal control character
For more information, see Chapter 6, Implementing a Wide Area Network.
If your Advanced Server will run in an OpenVMS Cluster, other domain
controllers (including the PDC) that are not in the same subnet as the
Advanced Server cluster must add an entry for the Advanced Server cluster
alias to their LMHOSTS file. This assumes they are not using other
methods (WINS or DNS) for resolving NetBIOS names. For domain
operations, all the domain controllers in the cluster operate as a
single domain controller identified by the Advanced Server cluster alias
name, rather than by the specific computer names of the individual
cluster members. However, because the LMHOSTS file does not offer any
means for mapping multiple IP addresses to a single NetBIOS name, the
entry for the Advanced Server cluster alias must be mapped to the IP
address of one specific server cluster member. If the Advanced Server is
stopped on that cluster member, you must modify the LMHOSTS file to map
the cluster alias name to the IP address of a cluster member on which
the Advanced Server is still running. On systems running a Microsoft
Windows operating system, the NetBIOS name cache must also be reloaded
using the command NBTSTAT -R (capital R required).
Due to the
LMHOSTS limitations noted above, it is difficult (and perhaps
unmanageable) to gain the benefits of load balancing and failover using
an LMHOSTS file.
- If your Advanced Server runs in an OpenVMS Cluster and you have it
set up for cluster load balancing using DNS,
then enable the use of DNS for NetBIOS name resolution on all servers
and clients. Remove any entries for the Advanced Server cluster alias
from the LMHOSTS file and WINS database. Compaq strongly
recommends that the Advanced Server cluster alias not be the same as the
TCP/IP cluster alias (referred to as the TCP/IP cluster impersonator
For information on setting up load balancing, refer to the
Compaq Advanced Server for OpenVMS Server Administrator's Guide.
To enable any of the wide area networking implementations, select them
using the Configuration Manager, as described in the Compaq Advanced Server for OpenVMS Server Administrator's Guide.
3.3.3 Do You Want to Change Any of the Server Configuration Settings?
The server configuration settings determine:
- Whether the License Server runs
The License Server is a software program that you can run on your
OpenVMS system to grant client-based licenses. Any client that wants to
use server resources must have a valid license. Each local area network
(LAN) needs only one License Server. The client license product
authorization keys (PAKs) must be loaded on the system that runs the
In an OpenVMS Cluster, the PAKs must be loaded in
a shared license database available to all cluster members.
License Server runs only if you enable it with the configuration
- If you are using client-based licensing, you must run the License
Server. Compaq recommends that you run the License Server on a
different system than the Advanced Server. See Section 1.3, About Licensing, for more
- If you are using server-based licenses, you do not need to run the
By default, the License Server does not run.
- Whether the Timesource service runs
The Timesource service allows your server to act as a time server.
Other servers on the network can synchronize with the time server to
coordinate network events (for example, running batch programs on all
computers the same time each day). Each LAN needs only one time server.
By default, the Timesource service does not run.
- Whether the Alerter service runs
The Alerter service sends messages called alerts to servers and clients
that run the Messenger service.
By default, the Alerter service
- Names of the users who receive alert messages
alert messages are sent to the Administrator account.
- Whether the Netlogon service is enabled.
In a domain, the Netlogon service distributes a domain-wide user
accounts database to all domain controllers running Netlogon. The
service allows for single domain-wide logon that enables users to
access resources on any server in the domain. The Netlogon service is
required for smooth operation of the domain; Compaq recommends that the
NetLogon service always be enabled, even on a member server.
default, the Netlogon service runs.
- Domain name
This is the domain in which your server is located. A domain is a
subdivision of clients and servers on the network. For more information
on domains, refer to the Compaq Advanced Server for OpenVMS Concepts and Planning Guide and the Compaq Advanced Server for OpenVMS Server Administrator's Guide.
default domain name is LANGROUP. You can specify a name that reflects
your company or group.
- Role of the server
This is the role of the server in the domain. You can designate an
Advanced Server as either the primary domain controller (PDC), backup
domain controller (BDC), or a member server. When you install the
Advanced Server in a new domain, the new server becomes the PDC by
default. In an OpenVMS Cluster, all nodes on the cluster have the same
role: when you change the role of one, the change applies to all the
servers on the cluster.
For more details on configuring the server
domain role, see Section 3.7, Configuring the Advanced Server Domain Role.
- Computer name
This unique name identifies your server in the domain. You define this
name or accept the default value when you run the configuration
The PWRK$CONFIG procedure will not prevent you from
specifying the same named PDC if another node or cluster has previously
been defined and is running in that role. However, on the new
(duplicate) PDC, the Netlogon service will not be started. The PDC must
be unique in the domain.
The default computer name is the same as
the server's SCSNODE name.
- Advanced Server cluster alias
If your server is a member of an OpenVMS Cluster, this is the name that
all servers in the cluster share. The alias lets remote nodes
(including clients) treat all server members in the cluster as a single
server. For example, a client user can specify the Advanced Server
cluster alias to connect to any server in the cluster; the user need
not know the specific node in the cluster to which it is connected.
If DECnet has been configured to run in the cluster, the default
Advanced Server cluster alias is the same as the DECnet cluster alias.
If a DECnet alias is not defined, the default Advanced Server cluster
alias is nodename_ALIAS, where nodename is the
SCSNODE name of the cluster member from which you initially run
Compaq strongly recommends that the Advanced Server cluster alias
and the TCP/IP cluster alias (referred to as the TCP/IP impersonator
cluster name) be different.
Do not use the name of the domain as the Advanced Server cluster
alias; if they are the same, the NetLogon service will fail to start.
- Server announce comment
This is the text that the Advanced Server displays when it announces its
presence on the network and when you display a list of available
The default server announce comment is "Advanced
Server V7.3 for OpenVMS."
- Advanced Server language
This determines the language and associated character set (one of
several ISO-8859 character sets) that the Advanced Server uses for
encoding text, such as file and share names, user names, description
strings, and any content of ADMINISTER command displays.
default is English (USA). You can configure any one of over 40
languages, many which include support of extended character set
characters. For an up-to-date list of languages that are officially
supported, refer to the Software Product Description (SPD).
The same language must be used by all servers in the domain. Compaq
recommends that all clients that will access the server also be
configured to use the same language; otherwise, names containing
characters that are not supported by the server language might not
appear to clients as expected.
If your disk device includes ODS-2 file names (in specific, file
names that include escape-encoded characters in the format
__XX), you must first convert the file names to ODS-5 file
names, as explained in Section 5.8, Converting Encoded File Names from ODS-2 to ODS-5. Section 3.8, Configuring the Server Language explains how to
configure the Advanced Server language. For more information on
languages, character sets, and Unicode, refer to the Compaq Advanced Server for OpenVMS Server Administrator's Guide.
- Enable NT style printing
This gives you a choice of managing shared printers either from a
remote Windows NT computer or locally using the ADMINISTER command
interface at the server. When enabled, administrators can store the
latest drivers for the printers on the Advanced Server. When new drivers
are distributed, administrators have to update a single location only.
When client users set up printers to use from their workstations, they
are able to download the appropriate printer driver automatically.
The default is local management of shared printers, using
ADMINISTER commands. When you enable Windows NT printer management,
only limited functionality is available for managing printers with the
ADMINISTER interface. Before configuring Windows NT style printer
management, see the considerations and restrictions in Section 3.9.1, Considerations Regarding Windows NT Printer Management.
Section 3.9.2, Example of Configuring Windows NT Printer Management, includes a sample configuration script showing how to
configure Windows NT style printer management.
For more information
about management of Advanced Server print shares, refer to the
Compaq Advanced Server for OpenVMS Server Administrator's Guide.