You can upgrade PATHWORKS V5 for OpenVMS (Advanced Server) to PATHWORKS V6 for OpenVMS (Advanced Server). If the system has PATHWORKS V5 for OpenVMS (LAN Manager) installed, you can use the Upgrade utility, as described in the PATHWORKS for OpenVMS (Advanced Server) Server Migration Guide, to upgrade server information before you configure and start the PATHWORKS Advanced Server.

2.3.3 Installing the Standalone License Server on a System Where the PATHWORKS Advanced Server Has Been Installed

If you install the standalone license server on a system where the PATHWORKS Advanced Server has been installed, the installation procedure displays the following message:

The PATHWORKS Advanced Server was previously installed and you have selected to install the license server only. Because the PATHWORKS Advanced Server includes the license server, the complete PATHWORKS Advanced Server must be installed.

The installation procedure will choose to install the PATHWORKS Advanced Server. You have the option of continuing with this installation, or you can terminate the installation procedure by pressing [Ctrl/Y]. To install the standalone license server on this system, you must first remove the PATHWORKS Advanced Server software using the PWRK$DEINSTAL.COM command procedure, as described in Chapter 7, Removing PATHWORKS Advanced Server Software. Then start the VMSINSTAL procedure again.

For a sample installation and configuration script for the standalone license server, see Appendix C, Sample Standalone License Server Installation and Configuration Procedure.

2.3.4 Installing the External Authentication Software

You cannot install the External Authentication software only, if you have previously installed the PATHWORKS Advanced Server. The installation procedure displays the following message if you try to install the External Authentication images under these circumstances:

The PATHWORKS Advanced Server was previously installed, and you have selected to install the External Authentication images only. Because the PATHWORKS Advanced Server includes the External Authentication images, the complete PATHWORKS Advanced Server must also be installed.

You must remove the PATHWORKS Advanced Server software to be able to select this option. To remove PATHWORKS Advanced Server software, run the PWRK$DEINSTAL procedure, as described in Chapter 7, Removing PATHWORKS Advanced Server Software.

For a sample installation script for the External Authentication images, see Appendix E, Sample External Authentication Installation Procedure.

2.4 Next Steps

To continue, depending on the software you are installing, do one of the following:

If you are...	Proceed to...	Which tells you how to...
Installing the PATHWORKS Advanced Server	Chapter 3, Configuring the PATHWORKS Advanced Server	Configure the PATHWORKS Advanced Server.
Installing the standalone license server	Chapter 4, Configuring and Starting the Standalone License Server	Configure the standalone license server.
Upgrading from PATHWORKS V5 for OpenVMS (LAN Manager)	PATHWORKS for OpenVMS (Advanced Server) Server Migration Guide	Use the Upgrade utility to create and edit upgrade reports.
Installing the PATHWORKS External Authentication software only	Section 5.5, Setting Up External Authentication	Set up PATHWORKS external authentication on the system.

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

• Section 3.1, About the PATHWORKS Advanced Server Configuration Procedure
• Section 3.2, Before You Start the PATHWORKS Advanced Server Configuration Procedure
• Section 3.3, How to Start the PATHWORKS Advanced Server Configuration Procedure
• Section 3.4, How to Respond to PATHWORKS Advanced Server Configuration Prompts
• Section 3.5, How to Change Default Configuration Settings
• Section 3.6, Troubleshooting Configuration Procedure Problems
• Section 3.7, Selecting the PATHWORKS Advanced Server Network Device
• Section 3.8, Defining Communications Devices
• Section 3.9, Next Steps

The following sections describe the PATHWORKS Advanced Server configuration procedure and what it does.

3.1.1 What Is the Configuration Procedure?

PWRK$CONFIG.COM, the PATHWORKS Advanced Server configuration procedure, is installed by the PATHWORKS Advanced Server 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 PATHWORKS Advanced Server.

3.1.2 What the Configuration Procedure Does

PWRK$CONFIG is a command procedure that:

• Creates the PATHWORKS Advanced Server on-disk structure. (Refer to Appendix F,PATHWORKS Advanced Server Files and On-Disk Structure, for a list of files and a description of the on-disk structure).
• Allows you to enter the Configuration Manager to modify system configuration parameters, such as the transports the server will run and the maximum number of clients that can connect to the server simultaneously.
• Creates the PATHWORKS Advanced Server user account and share databases.
• Allows you to modify server configuration default settings such as server role, domain name, and which services are enabled.
• Allows you to set or change the Administrator account password.
• Gives you the option of starting the server.

After you install the server, you must run PWRK$CONFIG before you can start the server. In an OpenVMS cluster, you must run PWRK$CONFIG on each individual node where the PATHWORKS Advanced Server will run, before you can start the server. (Although the nodes in an OpenVMS cluster function as a single unit in a domain, you need to treat them as individual units for purposes of configuration.) For more information, read the information on the Configuration Manager in the PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide.

3.2 Before You Start the PATHWORKS Advanced Server Configuration Procedure

Before you start the PWRK$CONFIG command procedure, answer the following questions:

1. On what OpenVMS disk device do you want to store the following PATHWORKS data files?
   • Configuration parameter files
   • License server data files
   • Log files
   • Printer spool files
   • Server data files
   • Virtual memory section files
   
   By default, the configuration procedure copies the data files to the disk device SYS$SYSDEVICE:. However, you can specify any existing OpenVMS disk device that has at least 79,500 free blocks of disk space. When you choose a disk device for the PATHWORKS data files, keep the following in mind:
   • The PATHWORKS 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 server. Therefore, Compaq Computer Corporation 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 PATHWORKS Advanced Server must use the same disk device to store and access PATHWORKS Advanced Server files.
   • The configuration procedure may be run again after you complete the installation and initial configuration of the PATHWORKS Advanced Server. You may specify a different disk at that time to move the existing PATHWORKS Advanced Server data files to a different disk volume.
2. Do you want to change the system configuration parameters now?
   If you enter YES to the prompt to change the system configuration parameters, the Configuration Manager is started. The Configuration Manager is a utility that allows you to modify server configuration parameters, such as the maximum number of clients that can connect to the server and which network transports the server uses.
   Whether or not you choose to change the system configuration at this time, you can change it later by entering the ADMINISTER/CONFIG command at the OpenVMS system prompt:

   $ ADMINISTER/CONFIG

   
   For more information about transports and about using the Configuration Manager, refer to the Advanced Server for OpenVMS Server Administrator's Guide.

   Configuring Transports for a Backup Domain Controller
   
   If you are configuring a server as a backup domain controller (BDC), during the initial configuration you must select at least one transport for the BDC that will also be run by its primary domain controller (PDC). Otherwise, the configuration will fail.
   When you choose the transports to run, keep the following in mind if the system will support wide area networking:

   • If you are configuring a backup domain controller to join an existing domain where the primary domain controller is on a different TCP/IP subnet, both the backup domain controller and the primary domain controller must be configured to use the TCP/IP transport, and you must set up wide area networking using either a WINS (Windows Internet Naming Service) Server or an LMHOSTS file for network name resolution, as described in Chapter 6, Implementing a Wide Area Network.
   • If you are using a WINS server for network name resolution, both the backup domain controller and the primary domain controller must use a WINS Server to provide NetBIOS name resolution.
   • If you are using the LMHOSTS file, it must be set up on both the backup domain controller and the primary domain controller. Make sure that the entry for the primary domain controller is in the LMHOSTS file on the backup domain controller before you configure the backup domain controller. If there is no entry for the primary domain controller in the LMHOSTS file on the backup domain controller when you configure it, the backup domain controller will not find the primary domain controller and will fail to join the existing domain.
     To enable one or both of the wide area networking implementations, select them using the Configuration Manager. Refer to the PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide for more information.
3. Do you want to change any of the server configuration default settings? These 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 LAN needs only one PATHWORKS license server to serve client-based licenses. The product authorization keys (PAKs) must be loaded on the system that runs the PATHWORKS license server. If you are using server-based licensing, the license server is not required.
     In an OpenVMS cluster, the PAKs must be loaded on all nodes that run the PATHWORKS license server. This is best accomplished by adding the PAKs to a shared license database.
     By default, the license server does not run.
     For detailed information on managing PATHWORKS licenses, see the Advanced Server for OpenVMS Guide to Managing Advanced Server Licenses.
   • 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 runs.
   • Names of the users who receive alert messages
     By default, 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 servers 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 on all primary domain controllers and backup domain controllers. By default, the Netlogon service runs.
   • Domain name
     This is the name of the domain in which your server participates. A domain is a subdivision of clients and servers on the network.
     The default PATHWORKS Advanced Server domain name is LANGROUP. Compaq recommends that you choose another name for the domain.
   • Role of the server
     This is the server's role in the domain. You can designate a PATHWORKS Advanced Server as either the primary domain controller or as a backup domain controller. In an OpenVMS cluster, all nodes on the cluster must have the same role.
   • Computer name
     This is the unique name that identifies your server in the domain. You define this name or accept the default value when you run the configuration procedure.
     By default, the PATHWORKS Advanced Server computer name is the same as the system's SCSNODE name.
   • PATHWORKS cluster alias
     If your server is a member of an OpenVMS cluster, this is the network name that all servers in the cluster use. The alias lets remote nodes (such as clients) treat the entire cluster as though it were a single server. For example, a client user can specify the PATHWORKS alias to connect to any server in the cluster; the user does not know (and does not need to know) to which server the client is connected.
     If DECnet is configured on the system, the default is the same as the DECnet alias name. If not, the default PATHWORKS Advanced Server cluster alias is same as the OpenVMS cluster alias.
   • Server announce comment
     This is the description of the server that the PATHWORKS Advanced Server broadcasts out when it announces its presence on the network. This description may also be displayed when you view a list of available servers.
     The default server announce comment is "PATHWORKS V6.0B for OpenVMS (Advanced Server)."
   
   For detailed information on changing default server configuration settings, see Section 3.5, How to Change Default Configuration Settings.
4. What is the Administrator account password?
   If you are configuring a primary domain controller, the configuration procedure prompts you to define a password for the PATHWORKS Advanced Server Administrator account, from which you administer the server. Passwords are case sensitive and can contain up to 14 alphanumeric characters as well as any of the following special characters: ! # $ % & () - . ^ _ ` { } ~
5. Do you want to start the server?
   The configuration procedure asks you if you want to start the server. If you do not want to start the server at this time, you can do so later from the command line after the configuration procedure completes.
   For detailed information on alternate ways to start the server, see Section 5.3.4, Starting the File Server.

After the installation procedure completes, the OpenVMS system prompt ($) is displayed. If the system was rebooted following installation:

1. Ensure that you are logged in to the SYSTEM account.
2. Start the configuration procedure by entering:

   $ @SYS$UPDATE:PWRK$CONFIG

Table 3-1, PATHWORKS Advanced Server Configuration Prompts, tells you how to respond to the prompts that PWRK$CONFIG displays.

Table 3-1 PATHWORKS Advanced Server Configuration Prompts

At this prompt...	If you want the configuration procedure to...	Enter...
Do you want to continue with configuration [YES]: 1	Shut down the server or, if your server is part of an OpenVMS cluster, all servers in the cluster	[Return]
	Abort the configuration procedure	NO
Enter disk device name where PATHWORKS data files will be stored [ default_device]:	Copy the PATHWORKS on-disk structure to the default OpenVMS disk device displayed If you ran PWRK$CONFIG previously, the default disk device is the one you specified the last time you configured the server.	[Return]
	Copy the PATHWORKS on-disk structure to an OpenVMS disk device different from the default displayed	device_name
Do you want to change the server configuration parameters now? [YES]:	Enter the Configuration Manager tool	[Return] For detailed information about using the Configuration Manager, refer to the PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide.
	Continue the configuration procedure without entering the Configuration Manager	NO
Enter item number, or RETURN to use these values [DONE]:	Accept the configuration parameters displayed	[Return]
	Change the configuration settings displayed	The number associated with a setting you want to change. For detailed information on changing these default configuration settings, see Section 3.5, How to Change Default Configuration Settings.
Do you want to enter a new Administrator account password [NO]: 2,3	Keep the existing Administrator account password	[Return]
	Prompt you to enter a new Administrator account password	YES
Enter Administrator network account password: 3	Associate a password with the Administrator account	password If your server will be part of an existing domain, enter the password to the existing domain's Administrator account.
Re-enter to verify password: 3		password
Do you want to start PATHWORKS V6.0B for OpenVMS on node node_name now [YES]: 3	Start the server automatically after the installation procedure completes	[Return]
	Not start the server	NO

After you exit the Configuration Manager, the configuration procedure displays a list of server configuration settings and a prompt that lets you change them. For example:

PATHWORKS V6.0B for OpenVMS is presently configured to run as follows: 1. Run the license server: NO 2. Enable Timesource service: NO 3. Enable Alerter service: YES 3a. Alert user names: Administrator 4. Enable Netlogon service: YES 5. Advanced Server domain: LANGROUP 6. Advanced Server role: PRIMARY 7. Advanced Server computer name: COBRAZ 7a. PATHWORKS OpenVMS cluster alias: COBRAZ_ALIAS 8. Server announce comment: PATHWORKS V6.0B for OpenVMS (Advanced Server) Enter item number, or RETURN to use these values [DONE]:

• To change a server configuration setting, enter the number of the setting you want to change. A prompt is then displayed that lets you change that setting. Table 3-2, Configuration Settings, describes possible values for each setting.
• To save the settings after you complete your changes or to accept the settings displayed, press [Return] to use the default answer DONE. For information on completing the rest of the configuration procedure, see Section 3.4, How to Respond to PATHWORKS Advanced Server Configuration Prompts.

For a description of each server configuration setting, see Section 3.2, Before You Start the PATHWORKS Advanced Server Configuration Procedure.

Table 3-2 Configuration Settings

Setting	Possible Values
1. Run the license server:	YES, to run the license server. NO, to use the default and not run the license server.
2. Enable Timesource service:	YES, to enable the Timesource service. NO, to use the default and not enable the Timesource service.
3. Enable Alerter service:	YES, to accept the default and enable the Alerter service. NO, to disable the Alerter service.
3a. Alert user names: 1	A comma-delimited list of user names (each containing up to 20 characters), who can receive alert messages.
4. Enable Netlogon service:	YES, to accept the default and enable the Netlogon service. NO, to disable the Netlogon service.
5. Advanced Server domain:	A domain name of up to 15 characters. Press [Return] to use the default. The default domain name is LANGROUP. Compaq recommends that you specify another name for the domain.
6. Advanced Server role:	PRIMARY, to designate the server as the primary domain controller BACKUP, to designate the server as a backup domain controller.
7. Advanced Server computer name:	A computer name of up to 15 characters. Press [Return] to use the default. If this is the first time running the configuration procedure, the default is your system's SCSNODE name.
7a. PATHWORKS OpenVMS cluster alias: 2	The PATHWORKS cluster alias for the OpenVMS cluster to which your server belongs. Press [Return] to use the default. If DECnet is configured to run, the default is the DECnet cluster alias. If DECnet is not configured to run, the default is nodename_alias.
8. Server announce comment:	A text string of up to 48 characters that the server uses to announce its presence on the network. Press [Return] to use the default.