HP OpenVMS Systems
HP Advanced Server for OpenVMS
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:
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:
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:
HP 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
HP 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:
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 for Advanced Server mail notification|
|License Server||License Server component|
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:
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 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.
|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
(If you ran PWRK$CONFIG previously, the default disk device is the one you specified the last time you configured the server.)
|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:
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 $
To make sure that the License Server starts automatically each time you boot your OpenVMS system:
$ 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, HP suggests that you use the SYSMAN utility to start the server manually and simultaneously on all cluster members. To do so:
$ RUN SYS$SYSTEM:SYSMAN
SYSMAN> SET ENVIRONMENT/NODE=(SPEEDY,SPIN,SPAN)
SYSMAN> DO @SYS$STARTUP:PWRK$STARTUP
This chapter describes tasks you can perform after you install the Advanced Server and consists of the following sections:
Before you start the Advanced Server, make sure you have:
If the installation verification procedure (IVP) did not run when you installed the Advanced Server, you can run it now (or anytime later) to make sure that the server installed successfully. (When you specify the /NOTEST qualifier with the PRODUCT INSTALL command, the IVP procedure does not run.)
To run the IVP, enter the following command:
Table 5-1, IVP Indications and Steps You Should Take, indicates the steps to take according to the status of the installation indicated by IVP.
|Installation Status||IVP Indication||Steps to Take|
|Succeeded||The message: %PWRK-I-NORMAL, IVP completed successfully|
|Start the server, as described in Section 5.3, Starting the Advanced Server.|
An error message, followed by:
-PWRK-E-IVPFAIL, IVP has failed
|Reinstall the software, as described in Chapter 2, Installing Advanced Server for OpenVMS Software.|
The following sections describe when and how to start the Advanced Server
(manually or automatically), and what the startup procedure does.
5.3.1 When to Start the Advanced Server
You must configure the Advanced Server before you can start it for the
first time. After running the configuration procedure, you can start
and stop the Advanced Server at any time.
5.3.2 What the Startup Procedure Does
You can start the Advanced Server:
If you did not start the Advanced Server during the configuration procedure, you can start it now by entering:
The Advanced Server starts, and messages similar to the following are displayed:
The file server will use DECnet, NetBEUI, TCP/IP. Advanced Server mail notification will use DECnet. Process NETBIOS created with identification 00000248 Process PWRK$NBDAEMON created with identification 0000024A Process PWRK$KNBDAEMON created with identification 0000024C Process PWRK$LICENSE_R created with identification 0000024E Checking to see if the OpenVMS Registry Services are available... The Advanced Server is configured to support 20 PC clients. Process PWRK$MASTER created with identification 00000251 The master process will now start all other Advanced Server processes.
To make sure that the Advanced Server starts automatically each time you boot your OpenVMS system, edit the site-specific startup file, SYS$STARTUP:SYSTARTUP_VMS.COM. Add the Advanced Server startup command to the file below all lines that start network transports. For example:
$ @SYS$STARTUP:TCPIP$STARTUP.COM . . . $ @SYS$STARTUP:PWRK$STARTUP
If you installed and configured the Advanced Server on multiple members of the same OpenVMS Cluster, HP recommends that you use the SYSMAN utility to start the Advanced Server manually and simultaneously on all cluster members.
To start the Advanced Server on all cluster members at the same time, make sure you are logged in to the SYSTEM account on one of the member nodes, then run SYSMAN as follows:
|Enter this command...||To...|
|$ RUN SYS$SYSTEM:SYSMAN||Start the SYSMAN utility.|
|SYSMAN> SET ENVIRONMENT/NODE=(SPEEDY,SPIN,SPAN)|
|Define the OpenVMS Cluster members on which to start the server. For example, SPEEDY, SPIN, and SPAN.|
|SYSMAN> DO @SYS$STARTUP:PWRK$STARTUP|
|Start the Advanced Server on all the nodes you defined in the previous command.|
|SYSMAN> EXIT||Exit the SYSMAN utility.|
If you are using the STARTUP feature of the SYSMAN utility to start Advanced Server, you must pass a P1 parameter of " " (null or space). For example:
For more information on using the SYSMAN utility's STARTUP feature, refer to the OpenVMS System Management Utilities Reference Manual.
If Advanced Server startup does not complete successfully, check the SYLOGIN.COM procedure. Make sure that only commands that should be executed by detached processes are executed during Advanced Server startup.
In SYLOGIN.COM, you can use the DCL lexical function F$MODE or F$GETJPI
to conditionalize DCL commands, such as $SET TERM/INQUIRE, that should
be executed only by nondetached processes, so that they are not
executed during Advanced Server startup. Refer to the OpenVMS DCL Dictionary for
126.96.36.199 OpenVMS Registry Services Not Available
The Advanced Server will start only if the OpenVMS registry services are available. For information about starting the Registry Server, refer to the OpenVMS System Manager's Manual or the COM, Registry, and Events for OpenVMS Developer's Guide (included in the OpenVMS Documentation CD-ROM).
If the Registry Server is started as part of Advanced Server startup, a message similar to the following is displayed by the startup procedure:
Checking to see if the OpenVMS Registry Services are available... %RUN-S-PROC-ID, identification of created process is 0000023B
If the Registry Server cannot be started, the following message is displayed and the startup procedure is terminated:
SYS$REGISTRY must be defined to start the VMS Registry. %PWRK-F-NOREGISTRY, OpenVMS Registry services not configured for this system %PWRK-F-STARTERR, severe error encountered during start-up 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. Without them the file server cannot start. $
The Advanced Server startup procedure records a list of all Advanced Server parameters that are set in the OpenVMS Registry. You can use this list as a reference if you should ever need the latest parameter values. The list is stored in the following location, where nodename is the name of your server node:
You can stop the Advanced Server at any time for any reason, which can include the following:
To stop the Advanced Server, enter the following command:
$ @SYS$STARTUP:PWRK$SHUTDOWN Shutting down the currently running server(s)...
For a cluster server, enter:
$ @SYS$STARTUP:PWRK$SHUTDOWN CLUSTER
To stop the Advanced Server as part of an orderly system shutdown, add the shutdown command to the site-specific system shutdown procedure. In addition, prior to shutting down the server, announce the planned shutdown to connected users by using the ADMINISTER SEND/USERS command, as in the following example, which alerts all users connected to server WOODMAN:
LANDOFOZ\\TINMAN> SEND/USERS/SERVER=WOODMAN "Shutdown @ 1pm today!!!"