Document revision date: 30 March 2001

If you reconfigure a previously configured server, the PWRK$CONFIG command procedure creates subdirectories in the PWRK$LMDOMAINS: and PWRK$LMDATAFILES: directories, and stores the original accounts database files there.

The names of the subdirectories are based on the date and time, such as 16JUN200014314818.DIR, indicating that the directory was created on 16-JUN-2000 at approximately 2:32 p.m.

If an error occurs during configuration, the server configuration will be returned to its original state. After you are confident you have a successful reconfiguration, you can manually delete these subdirectories and their contents.

3.11 The Advanced Server Network Adapter

The PWRK$CONFIG configuration might need to use the network to communicate with the PDC. If the system has more than one network adapter (also referred to as a network interface card), the default adapter chosen by PWRK$CONFIG might not be the correct interface. Or, on some newer systems, the Advanced Server might not recognize the only network adapter present. In cases such as these, you can define system logical names to direct the Advanced Server to use a specific interface. If no such logical is defined, PWRK$CONFIG selects the first adapter (alphabetically) defined on your system from a list of known adapters.

If the server has access to more than one network adapter, and you do not want to use the adapter selected, or if the system has a network adapter that is not found or recognized by the Advanced Server, you can manually specify the network adapter to use with the transport you specified.

3.11.1 Manually Defining the Network Adapter

To manually define the network adapter to be used for a specific protocol, follow these steps:

1. Use the DCL DEFINE/SYSTEM command 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:

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.11.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.12 Next Steps

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

If you are ready to start the server, see Chapter 5, After You Install the Advanced Server, for instructions.

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

The Advanced Server for OpenVMS 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 servers:

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

The License Server included with Advanced Server for OpenVMS 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 the Advanced Server.

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. Therefore, the Advanced Server for OpenVMS kit allows you to install the standalone License Server separately from the file server. Alternatively, you can run the License Server on an OpenVMS Cluster with the Advanced Server, where cluster failover provides reliability. (You can also run the License Server on an OpenVMS Cluster without the Advanced Server.)

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.

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 Advanced Server. The procedures are described in Chapter 2, Installing Advanced Server for OpenVMS Software.

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

The following table shows details about the PWRK$STARTUP.COM procedure:

If the following is configured	Then the following is started
DECnet	DECnet transport
NetBEUI	NetBEUI transport
TCP/IP	TCP/IP transport
DECnet	DECnet transport for Advanced Server mail notification
License Server	License Server component

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:

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

   $ @SYS$UPDATE:PWRK$CONFIG

3. Respond to the 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.

Table 4-1 License Server Configuration Prompts

At this prompt...	If you want the configuration procedure to...	Enter...
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 (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 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 Advanced Server License Server now [YES]:	Start the server automatically after the configuration procedure completes	[Return]
	Complete the configuration procedure without starting the server	NO

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.

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

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 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 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 SPEEDY, SPIN, and SPAN, enter the following at the SYSMAN> prompt:

   SYSMAN> SET ENVIRONMENT/NODE=(SPEEDY,SPIN,SPAN)

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

   SYSMAN> DO @SYS$STARTUP:PWRK$STARTUP

	privacy and legal statement
6540PRO_006.HTML