Compaq Advanced Server for OpenVMS
Server Installation and Configuration Guide


Previous Contents Index

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 installation completes:

  1. 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.
  2. 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 command:


$ 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 appropriate.

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 
systems. 
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 installation procedure.

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 the following:
If you are... Proceed to...
Installing the complete Advanced Server Chapter 3, Configuring the Advanced Server
Installing the standalone License Server Chapter 4, Configuring and Starting the Standalone License Server
Installing the standalone external authentication software Section 5.7, Setting Up External Authentication, and refer to the OpenVMS Guide to System Security.


Chapter 3
Configuring the Advanced Server

This chapter describes how to configure the Advanced Server, and consists of the following sections:

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

3.1.1 What the Configuration Procedure Does

PWRK$CONFIG is a command procedure that:

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:


Key: SYSTEM\CurrentControlSet\Services\AdvancedServer\Parameters 
Value: LanmanIniMigrated 
Type: String 
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 OpenVMS):


REGUTL> SHOW VALUE * LANMANINIMIGRATED 
 
Key: SYSTEM\CurrentControlSet\Services\AdvancedServer\Parameters 
Value: LanmanIniMigrated 
Type: String 
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 OpenVMS Registry.

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:

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:

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.

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

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:


Previous Next Contents Index