| Previous | Contents | Index |
The following section describes how to ensure sufficient resources will
be available to support clients.
3.6.1 Ensuring Sufficient Resources to Support Clients
PATHWORKS 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 PATHWORKS Advanced Server, and these resources have already been consumed when PATHWORKS Advanced Server is started, there may be insufficient resources left for PATHWORKS 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 PATHWORKS Advanced Server is installed and started before you run the PATHWORKS Advanced Server configuration procedure, especially if you run TCP/IP.
After you successfully configure the PATHWORKS 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_node.LOG |
To increase the resource allocation, make the appropriate modifications
to the MODPARAMS.DAT file and then run AUTOGEN. Refer to Chapter 1, Before You Install PATHWORKS Advanced Server,
for more information about the requirements for system parameter
settings.
3.7 Selecting the PATHWORKS 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 PATHWORKS 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 PATHWORKS Advanced Server operates. You must add these logicals to SYS$MANAGER:SYLOGICALS.COM to have them available after rebooting.
| Logical Name | Transport |
|---|---|
| NETBIOS$DEVICE | DECnet |
| PWRK$KNBDAEMON_DEVICE | TCP/IP |
| PWRK$NETBEUI_DEVICE | NetBEUI |
For example:
$ DEFINE/SYSTEM NETBIOS$DEVICE EWA0: |
$ DEFINE/SYSTEM PWRK$KNBDAEMON_DEVICE ESA0: |
$ DEFINE/SYSTEM PWRK$NBDAEMON_DEVICE ESA1: |
If TCP/IP is running on multiple network devices, and you select one of those devices for use by the PATHWORKS Advanced Server, make sure the device you select corresponds to the first device listed in the TCP/IP local hosts database. |
This section describes how to add new communications devices that are not automatically recognized by the PATHWORKS 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 PATHWORKS Advanced Server images are available to customers. Therefore, this section describes how to define the communications device you want the PATHWORKS Advanced Server to use.
If the communications device is not recognized by PATHWORKS 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 following examples, the server node name is MYNODE.
| 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 |
|
| 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 |
|
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:
$ DEFINE/SYSTEM PWRK$KNBDAEMON_DEVICE EWA0: $ DEFINE/SYSTEM NETBIOS$DEVICE EWA0: $ DEFINE/SYSTEM PWRK$NETBEUI_DEVICE EWA0: |
$ @SYS$STARTUP:PWRK$STARTUP |
You can start the PATHWORKS Advanced Server automatically as part of the configuration procedure.
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:
You can install the license server:
Compaq recommends that you install the license server on a designated OpenVMS system without the PATHWORKS Advanced Server, to ensure smooth and continuous operation of the license server. Therefore, the PATHWORKS Advanced Server 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 PATHWORKS Advanced Server, where cluster failover provides reliability.
The license server is required for client-based licensing. For 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 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. |
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 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:
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:
$ @SYS$UPDATE:PWRK$CONFIG |
Table 4-1, Standalone 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 Procedure. |
| 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 PATHWORKS Advanced Server on-disk structure to an OpenVMS disk device different from the default displayed | device_name | |
| Do you want to serve PATHWORKS 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 PATHWORKS 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 PATHWORKS 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 |
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 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
.
.
.
$ @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:
$ RUN SYS$SYSTEM:SYSMAN |
SYSMAN> SET ENVIRONMENT/NODE=(HYDRAA,HYDRAB,HYDRAC) |
SYSMAN>DO @SYS$STARTUP:PWRK$STARTUP |
This chapter describes tasks you can perform after you install the PATHWORKS Advanced Server software.
This chapter consists of the following sections:
Make sure you have completed all the required steps in Table 5-1, Have You Done..., before proceeding.
| If you are... | Make sure that you have... |
|---|---|
| Installing the PATHWORKS Advanced Server |
|
| Upgrading a PATHWORKS V5 for OpenVMS (LAN Manager) server to PATHWORKS V6 for OpenVMS (Advanced Server) server |
|
| Installing the Standalone License Server |
|
| Installing external authentication software only |
Completed the installation procedure described in Chapter 2, Installing the PATHWORKS Advanced Server. |
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 to make sure that the server installed successfully.
To run the IVP for PATHWORKS Advanced Server, enter:
$ @SYS$TEST:PWRK$IVP |
| If the installation... | Then the IVP displays... | And you should... |
|---|---|---|
| Succeeded | The message %PWRK-I-NORMAL, IVP completed successfully | |
| Start the server, as described in Section 5.3.4, Starting the File 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. | ||
The following sections describe when and how to start the PATHWORKS Advanced Server.
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
PATHWORKS Advanced Server processes are detached processes. During startup, all detached processes must execute the site-specific system login procedure (by default, SYS$MANAGER:SYLOGIN.COM).
If the PATHWORKS 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 the PATHWORKS Advanced Server startup.
In SYSLOGIN.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 the PATHWORKS Advanced Server startup. See the OpenVMS DCL Dictionary
for more information.
5.3.4 Starting the File Server
You can start the file server:
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.0B 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 |