This section describes how to:

• Troubleshoot Registry Server startup problems
• Ensure sufficient resources will be available to support clients

For proper operation of the PWRK$CONFIG.COM configuration procedure and the file server, registry services must be available on the system running the Advanced Server.

In an OpenVMS cluster environment, the OpenVMS Registry can be configured so that the Registry server does not run on the server node but rather on another node in the cluster. However, Compaq recommends that the OpenVMS Registry be configured to run the Registry server on every Advanced Server node. This ensures that registry services are available to the file server. For instructions on starting the Registry server and enabling registry services, refer to Section 1.8.4, Step 4: Start the OpenVMS Registry Server.

• If registry services are not available, the PWRK$CONFIG.COM procedure attempts to start the OpenVMS Registry server. If the attempt is successful the procedure displays the following message:

  Checking to see if the OpenVMS Registry Services are available... %RUN-S-PROC_ID, identification of created process is 0000023B

• If the SYS$REGISTRY logical is not defined, the OpenVMS Registry will not start. In this case, the PWRK$CONFIG.COM displays the following messages and terminates.

  Checking to see if OpenVMS Registry Services are available... SYS$REGISTRY must be defined to start the VMS Registry %PWRK-F-NOREGISTRY, OpenVMS Registry services not configured for this system %PWRK-F-CONFIGERR, severe error encountered during configuration OpenVMS Registry Services are not available on this system. Some file server parameters are stored in the OpenVMS Registry. For the file server or file server utilities to be able to access these parameters, OpenVMS Registry Services must be available on this system. Since the file server requires access to the OpenVMS Registry, it is recommended that OpenVMS Registry Services be started as part of system start-up, before the file server is started. For instructions on how to start OpenVMS Registry Services please refer to the file server release notes. This configuration is incomplete and cannot continue. You must execute @SYS$UPDATE:PWRK$CONFIG again. Please configure and start the OpenVMS Registry Services before doing so.

  
  You must enable registry services and start the Registry Server, then run the PWRK$CONFIG.COM procedure again. For more information about enabling and starting the Registry Server, refer to the OpenVMS System Manager's Manual.

The Advanced Server requests the resources that it needs using the OpenVMS AUTOGEN utility. If AUTOGEN underestimates the resources required for use by processes other than the Advanced Server, and these resources have already been consumed when the Advanced Server is started, there may be insufficient resources left for the Advanced Server to support the desired number of clients.

To ensure sufficient resource allocation to support clients, make sure that all software that will run concurrently with the Advanced Server is installed and started before you run the the Advanced Server configuration procedure (PWRK$CONFIG.COM). If TCP/IP is selected as a transport, make sure that the TCP/IP product is loaded before you run the PWRK$CONFIG procedure.

After you successfully configure the Advanced Server, it may not start, reporting that there are insufficient resources to support any clients. In this case, examine the following file to determine the system resource that needs to be increased:

PWRK$LOGS:PWRK$CONFIG_ERROR_nodename.LOG

To increase the resource, make the appropriate modifications to the MODPARAMS.DAT file and then run AUTOGEN.

3.8 Selecting the Advanced Server Network Device

The configuration procedure selects the network device depending on the transport you specify when you run the procedure. If the server has more than one network device, and you do not want to use the device selected, or if the server has a network device that is not recognized by the Advanced Server, you can manually select the network device to use with the transport you specified.

Table 3-3, OpenVMS Network Device Logicals, lists OpenVMS logical names that you can use to control the network device over which the Advanced Server operates. You must add these logicals to SYS$MANAGER:SYLOGICALS.COM to have them available after rebooting.

Table 3-3 OpenVMS Network Device Logicals

Logical Name	Transport
NETBIOS$DEVICE	DECnet
PWRK$KNBDAEMON_DEVICE	TCP/IP
PWRK$NETBEUI_DEVICE	NetBEUI

For example:

• To select device EWA0: for DECnet transport, enter the following command before you start the server:

  $ DEFINE/SYSTEM NETBIOS$DEVICE EWA0:

• To select device ESA0: for the TCP/IP transport, enter the following command before you start the server:

  $ DEFINE/SYSTEM PWRK$KNBDAEMON_DEVICE ESA0:

• To select device ESA1: for the NetBEUI transport, enter the following command before you start the server:

  $ DEFINE/SYSTEM PWRK$NBDAEMON_DEVICE ESA1:

This section describes how to add new communications devices that are not automatically recognized by the Advanced Server, as well as restrictions and limitations on communications devices.

The PWRK$KNBDAEMON, NETBIOS, and PWRK$NBDAEMON processes require the communications device to be defined in an internal device table. New communications devices can be released before updated Advanced Server software is available to customers. Therefore, this section describes how to define the communications device you want the Advanced Server to use.

If the communications device is not recognized by the Advanced Server, each failing process writes an error message to its log file. Table 3-4, Undefined Device 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-4, the server node name is MYNODE.

Table 3-4 Undefined Device Messages

Process	Log File Name
PWRK$KNBDAEMON	PWRK$LOGS:PWRK$KNBDAEMON_MYNODE.LOG
Message: Tue Mar 24 13:13:50 1998 get_phys_addr: Failed to get Ethernet device characteristics
PWRK$NBDAEMON	PWRK$LOGS:PWRK$NBDAEMON_MYNODE.LOG
Message: Tue Mar 24 13:13:50 1998 Failed to open datalink
NETBIOS	PWRK$LOGS:NETBIOS_MYNODE.LOG
Message: %NB-W-ERRSIGNAL, exceptional conditional detected at 24-Mar-1998 13:13:50.00 -SYSTEM-W-NOSUCHDEV, no such device available

The device tables include all known communications devices. However, if you are running the latest release and you find any of the messages listed in Table 3-4, you can explicitly specify the communications device for all three processes, using the following procedure:

1. Define the physical communications device type for the PWRK$KNBDAEMON, NETBIOS, and PWRK$NBDAEMON processes. For example, if EWA0 was an unknown physical communications device type, you would enter the following commands:

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

2. Restart the server:

   $ @SYS$STARTUP:PWRK$STARTUP

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

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.

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

In an OpenVMS cluster, the PAKs must be loaded into a shared license database. For detailed information on managing licenses, see the 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

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 . . . $ @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 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 SPEEDY, SPIN, and SPAN:

   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