# Compaq PATHWORKS for OpenVMS
Server Installation and Configuration Guide

Previous | Contents | Index

## 3.8.1 Manually Defining the Network Adapter

To manually define the network adapter to be used for a specific protocol (after restarting the server), follow these steps:

1. Use the DCL command DEFINE/SYSTEM to define a system logical name that specifies the network adapter, as shown in the following examples. Table 3-5, OpenVMS Network Adapter Logicals, lists the OpenVMS logical name that you can use for each transport. You must add the appropriate logicals to SYS$MANAGER:SYLOGICALS.COM to have them available after rebooting.
2. Restart the server:

       $ @SYS$STARTUP:PWRK$STARTUP

Table 3-5 OpenVMS Network Adapter Logicals
Logical Name | Transport
--- | ---
NETBIOS$DEVICE | DECnet
PWRK$KNBDAEMON_DEVICE | TCP/IP
PWRK$NETBEUI_DEVICE | NetBEUI

The following examples show how to define the appropriate network adapter for the DECnet, TCP/IP, and NetBEUI transports, respectively:

- To specify adapter EWA0: for the DECnet transport, enter the following command:

      $ DEFINE/SYSTEM NETBIOS$DEVICE EWA0:

- To specify adapter ESA0: for the TCP/IP transport, enter the following command:

      $ DEFINE/SYSTEM PWRK$KNBDAEMON_DEVICE ESA0:

  Note If TCP/IP is running on multiple network adapters, and you select one of those adapters for use by the Advanced Server, make sure the adapter you select corresponds to the first adapter listed in the TCP/IP local hosts database.

- To specify adapter ESA1: for the NetBEUI transport, enter the following command:

      $ DEFINE/SYSTEM PWRK$NETBEUI_DEVICE ESA1:

Note that you can specify the same adapter for each protocol, as in the following example:

    $ DEFINE/SYSTEM NETBIOS$DEVICE EWA0:
    $ DEFINE/SYSTEM PWRK$KNBDAEMON_DEVICE EWA0:
    $ DEFINE/SYSTEM PWRK$NETBEUI_DEVICE EWA0:

Note The names of adapters defined by use of the logical names PWRK$NETBEUI_DEVICE, PWRK$KNBDAEMON_DEVICE, and NETBIOS$DEVICE must not start with an underscore (_); otherwise, the PWRK$KNBDAEMON will not start, and other processes will start, but they will not operate properly.

## 3.8.2 What to Do If the Network Adapter Is Not Found

The NETBIOS, PWRK$KNBDAEMON (for TCP/IP), and PWRK$NBDAEMON (for NetBEUI) processes require that their associated network adapter is known and available to the server software. It is possible that new network adapters are released that are not known to the current version of the Advanced Server software. If the Advanced Server does not find or recognize the selected network adapter, each of the failing processes (NETBIOS, which is always present, and PWRK$KNBDAEMON and PWRK$NBDAEMON, if present) writes an error message to its log file. Table 3-6, Undefined Adapter Messages, shows each process, the log file that records the error message from the process, and examples of the text of the error message. In the examples in Table 3-6, the server node name is MYNODE. All three error messages have the same meaning: that no such device was found by the server.

Table 3-6 Undefined Adapter Messages
Process | Log File Name
--- | ---
PWRK$KNBDAEMON | PWRK$LOGS:PWRK$KNBDAEMON_MYNODE.LOG
Message:
    Tue Mar 24 13:13:50 2000 get_phys_addr: Failed to get Ethernet

    device characteristics
PWRK$NBDAEMON | PWRK$LOGS:PWRK$NBDAEMON_MYNODE.LOG
Message:
    Tue Mar 24 13:13:50 2000 Failed to open datalink
NETBIOS | PWRK$LOGS:NETBIOS_MYNODE.LOG
Message:
    %NB-W-ERRSIGNAL, exceptional conditional detected at

    24-Mar-2000 13:13:50.00

    -SYSTEM-W-NOSUCHDEV, no such device available

If you find any of the messages listed in Table 3-6, define the network adapter for the appropriate processes, using the procedure outlined in Section 3.8.1, Manually Defining the Network Adapter. For example, if the server reported an unknown device, enter the DEFINE/SYSTEM commands to define the appropriate adapter for each protocol on the server.

# 3.9 Next Steps

You can start the PATHWORKS Advanced Server automatically as part of the configuration procedure.

- If you are upgrading from PATHWORKS (LAN Manager) perform the upgrade procedures described in the Compaq PATHWORKS for OpenVMS (Advanced Server) Server Migration Guide.
- If you are ready to start the server, see Chapter 5, After You Install the PATHWORKS Advanced Server, for instructions.

# Chapter 4
Configuring and Starting the Standalone License Server

The License Server is a software program that you can run on an OpenVMS system to grant licenses to clients.

This chapter describes how to configure and start the standalone License Server, and consists of the following sections:

- Section 4.1, About the License Server
- Section 4.2, Before You Begin to Configure the Standalone License Server
- Section 4.3, Configuring the Standalone License Server
- Section 4.4, Configuring the Transports
- Section 4.5, How to Respond to License Server Configuration Prompts
- Section 4.6, How to Start the Standalone License Server

# 4.1 About the License Server

The PATHWORKS Advanced Server License Server can provide license verification for clients requiring access to PATHWORKS (LAN Manager) servers, PATHWORKS for OpenVMS (Advanced Server) servers, and Advanced Server for OpenVMS servers.

The License Server is required for client-based licensing. If you are using server-based licensing, you do not have to run the License Server.

Each LAN needs only one License Server to support client-based licenses. The same License Server can manage licenses for client access to any of the following types of file and print servers:

- PATHWORKS V5 for OpenVMS (LAN Manager)
- PATHWORKS V6 for OpenVMS (Advanced Server)
- Advanced Server for OpenVMS

You can install the License Server:

- Separately from the Advanced Server
- In conjunction with the Advanced Server

Compaq recommends that you install the License Server on a designated OpenVMS system without the Advanced Server. The PATHWORKS Advanced Server kit allows you to install the standalone License Server separately from the file and print server. You can run the standalone License Server on an OpenVMS Cluster, where cluster failover provides reliability.

In an OpenVMS Cluster, the PAKs must be loaded into a shared license database. For detailed information on managing licenses, refer to the Compaq Advanced Server for OpenVMS Guide to Managing Advanced Server Licenses.

Note The License Server included with PATHWORKS Advanced Server will not issue or manage PATHWORKS for OpenVMS (NetWare) licenses. If you have clients using NetWare networking software, maintain the existing version of the License Server on a different system from the one that is running PATHWORKS Advanced Server.

# 4.2 Before You Begin to Configure the Standalone License Server

You install the standalone License Server from the same software kit that you use to install the PATHWORKS Advanced Server. The procedures are described in Chapter 2, Installing the PATHWORKS Advanced Server.

# 4.3 Configuring the Standalone License Server

You must configure the standalone License Server to provide licenses to clients in the LAN. Therefore, you select the appropriate transports used by the clients. You can configure the License Server to use the following transports:

- DECnet
- NetBEUI
- TCP/IP

Because the License Server supports all these types of transports, the startup and shutdown procedures have been carefully designed to prevent unexpected interruptions in service. You can start and shut down the License Server using the file and print server command procedures PWRK$STARTUP.COM and PWRK$SHUTDOWN.COM. For more information on starting a standalone License Server, see Section 4.6, How to Start the Standalone License Server.

# 4.4 Configuring the Transports

The following section describes how to use the configuration command procedure to configure the transports for the standalone License Server.

After the installation procedure completes, the OpenVMS system prompt ($) is displayed. If the system was rebooted following installation, ensure that you are logged in to the SYSTEM account, and do the following:

1. Start the configuration procedure by entering:

       $ @SYS$UPDATE:PWRK$CONFIG

2. Respond to the configuration prompts.

# 4.5 How to Respond to License Server Configuration Prompts

Table 4-1, License Server Configuration Prompts, tells you how to respond to the prompts displayed by PWRK$CONFIG when you configure the standalone License Server.

Note Table 4-1 shows only the prompts that PWRK$CONFIG displays; it does not show any informational messages. For a complete sample configuration script, see Appendix C, Sample Standalone License Server Installation and Configuration.

Table 4-1 License Server Configuration Prompts
Prompt | Desired Outcome | How to Respond
--- | --- | ---
Enter disk device name where the Advanced Server data files will be stored [ default_device]: | Copy the server on-disk structure to the default OpenVMS disk device displayed; you need 5,000 free blocks of disk space to store these data files. (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 Advanced Server on-disk structure to an OpenVMS disk device different from the default displayed | device_name
Do you want to serve client-based licenses over DECnet [YES]: 1 | Allow licenses to be served over DECnet | `[Return]`
| Not allow licenses to be served over DECnet | NO
Do you want to serve client-based licenses over NetBEUI [NO]: 1 | Allow licenses to be served over NetBEUI | YES
| Not allow licenses to be served over NetBEUI | `[Return]`
Do you want to serve client-based licenses over TCP/IP [NO]: 1 | Allow licenses to be served over TCP/IP | YES
| Not allow licenses to be served over TCP/IP | `[Return]`
Do you want to start the PATHWORKS License Server now [YES]: | Start the server automatically after the configuration procedure completes | `[Return]`
| Complete the configuration procedure without starting the server | NO

1Default answers may differ if you ran the PWRK$CONFIG procedure previously.

# 4.6 How to Start the Standalone License Server

You can start the License Server in any of the following ways:

- During the configuration procedure, as described in Section 4.3, Configuring the Standalone License Server.
- Manually from the command line.
- Automatically each time you reboot.

## 4.6.1 How to Start the License Server Manually

If you did not start the License Server during the configuration procedure, you can start it manually using the following command:

    $ @SYS$STARTUP:PWRK$STARTUP [Return]

    The License Server will use DECnet, NetBEUI, TCP/IP.
    Process NETBIOS created with identification 0000011E
    Process PWRK$NBDAEMON created with identification 00000120
    Process PWRK$KNBDAEMON created with identification 00000122
    Process PWRK$LICENSE_S created with identification 00000124
    $

## 4.6.2 How to Start the License Server Automatically

To make sure that the License Server starts automatically each time you boot your OpenVMS system:

1. Edit the system startup file (SYS$STARTUP:SYSTARTUP_VMS.COM).
2. Add the startup command, as shown in the following example. Add the command to the file below all lines that start network transports. The following example shows how to edit the file.

       $ IF F$SEARCH("SYS$SYSTEM:NETACP.EXE") .NES. ""
       $ THEN @SYS$MANAGER:STARTNET
       $ ENDIF
       .
       .
       .

       $ @SYS$STARTUP:PWRK$STARTUP

## 4.6.3 How to Start the License Server in an OpenVMS Cluster

If you installed and configured the License Server on multiple members of the same OpenVMS Cluster, Compaq suggests that you use the SYSMAN utility to start the License Server manually and simultaneously on all cluster members. To do so:

1. Make sure that you are logged in to the SYSTEM account on one of the server nodes in the OpenVMS Cluster.
2. Start the SYSMAN utility by entering:

       $ RUN SYS$SYSTEM:SYSMAN

3. Define all the cluster members on which you want to start the standalone License Server. For example, if you want to start the License Server on nodes HYDRAA, HYDRAB, and HYDRAC:

       SYSMAN> SET ENVIRONMENT/NODE=(HYDRAA,HYDRAB,HYDRAC)

4. Start the License Server on the nodes you defined. At the SYSMAN> prompt, enter the following command:

       SYSMAN> DO @SYS$STARTUP:PWRK$STARTUP

Only one License Server in the cluster will be active at a time. If that License Server becomes unavailable, cluster failover activates one of the other License Servers to take over.

# Chapter 5
After You Install the PATHWORKS Advanced Server

This chapter describes tasks you can perform after you install the PATHWORKS Advanced Server software and consists of the following sections:

- Section 5.1, Before You Begin Postinstallation Tasks
- Section 5.2, Verifying the PATHWORKS for OpenVMS (Advanced Server) Installation
- Section 5.3, Starting the PATHWORKS Advanced Server
- Section 5.4, Stopping the PATHWORKS Advanced Server
- Section 5.5, How to Define PATHWORKS Advanced Server Commands When You Log In
- Section 5.6, Setting Up External Authentication
- Section 5.7, Installing Optional Server Administration Tools

# 5.1 Before You Begin Postinstallation Tasks

Before proceeding, make sure you have completed the steps listed in the second column of Table 5-1, depending on the task you are performing, listed in the first column.

Table 5-1 Steps That Must Be Completed Before Postinstallation
Task You Are Performing | Steps Required
--- | ---
Installing the PATHWORKS Advanced Server | Completed the installation procedure described in Chapter 2, Installing the PATHWORKS Advanced Server. Completed the configuration procedure described in Chapter 3, Configuring the PATHWORKS Advanced Server.
Upgrading a PATHWORKS (LAN Manager) server to PATHWORKS V6 for OpenVMS (Advanced Server) server | Completed the installation procedures described in Chapter 2, Installing the PATHWORKS Advanced Server. Completed the upgrade procedure described in the Compaq PATHWORKS for OpenVMS (Advanced Server) Server Migration Guide. Completed the configuration procedure described in Chapter 3, Configuring the PATHWORKS Advanced Server.
Installing the Standalone License Server | Completed the installation procedures described in Chapter 2, Installing the PATHWORKS Advanced Server. Completed the configuration procedure described in Chapter 4, Configuring and Starting the Standalone License Server.
Installing external authentication software only | Completed the installation procedure described in Chapter 2, Installing the PATHWORKS Advanced Server.

# 5.2 Verifying the PATHWORKS for OpenVMS (Advanced Server) Installation

If you did not run the IVP as part of the installation procedure, as described in Chapter 2, Installing the PATHWORKS Advanced Server, you can run it now (or anytime later) to make sure that the server installed successfully.

To run the IVP for PATHWORKS Advanced Server, enter the following command:

    $ @SYS$TEST:PWRK$IVP

Table 5-2, IVP Indications and Steps You Should Take, indicates the steps to take according to the status of the installation indicated by IVP.

Table 5-2 IVP Indications and Steps You Should Take
Installation Status | IVP Indication | Steps to Take
--- | --- | ---
Succeeded | The message `%PWRK-I-NORMAL, IVP completed successfully`
|  | If it is not already running, start the server, as described in Section 5.3, Starting the PATHWORKS Advanced Server.
Failed | An error message, followed by `-PWRK-E-IVPFAIL, IVP has failed`
|  | Reinstall the software, as described in Chapter 2, Installing the PATHWORKS Advanced Server.

# 5.3 Starting the PATHWORKS Advanced Server

The following sections describe what the startup procedure does, when and how to start the PATHWORKS Advanced Server (manually or automatically), and and how to troubleshoot problems with startup.

You can start the Advanced Server:

- During the configuration procedure, as described in Chapter 3, Configuring the PATHWORKS Advanced Server
- Manually from the command line
- Automatically each time you reboot

## 5.3.1 When to Start the PATHWORKS Advanced Server

You must configure the server before you can start it for the first time. After running the configuration procedure, you can start and stop the server at any time.

## 5.3.2 What the Startup Procedure Does

The startup procedure:

1. Checks for the required privileges.
2. Verifies that required configuration files are available.
3. Verifies that the server has been configured, and exits if it was not.
4. If a reboot is required, verifies that it was performed, and exits if it was not.
5. Loads transport drivers.
6. Installs images.
7. Starts transport support processes.
8. Starts each of the components:
   - License Registrar
   - License Server (if configured)
   - File and print server

## 5.3.3 How to Start the PATHWORKS Advanced Server Manually

If you did not start the PATHWORKS Advanced Server during the configuration procedure, you can start it now by entering:

    $ @SYS$STARTUP:PWRK$STARTUP

The PATHWORKS Advanced Server starts, and messages similar to the following are displayed:

    PATHWORKS file server will use DECnet, TCP/IP.
    PATHWORKS mail notification will use DECnet.
    Process NETBIOS created with identification 0000009A
    Process PWRK$LICENSE_R created with identification 0000009D
    The PATHWORKS V6.1 server is configured to support 20 PC clients.
    Process PWRK$MASTER created with identification 000000A2
    The master process will now start all other PATHWORKS processes.

Previous | Next | Contents | Index