| Previous | Contents | Index |
You can define server commands automatically when you log in to the privileged account that you use to manage the PATHWORKS Advanced Server.
To define server commands at login, edit the LOGIN.COM file of the privileged account to add the following line:
$ @SYS$STARTUP:PWRK$DEFINE_COMMANDS |
To make sure that the 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 PATHWORKS Advanced Server on multiple members of the same OpenVMS cluster, Compaq Computer Corporation recommends that you use the SYSMAN utility to start the server manually and simultaneously on all cluster members.
To start the servers at the same time, make sure you are logged in to the SYSTEM account on one of the server 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. (In this example, SPEEDY, SPIN, and SPAN.) | |
| SYSMAN> DO @SYS$STARTUP:PWRK$STARTUP | Start the PATHWORKS Advanced Server on all the nodes you defined in the previous command. |
| SYSMAN> EXIT | Exit the SYSMAN utility. |
The following sections describe when and how you stop the PATHWORKS Advanced Server.
5.4.1 When to Stop the PATHWORKS Advanced Server
You can stop the server at any time for any reason, which can include the following:
To stop the server, enter the following command:
$ @SYS$STARTUP:PWRK$SHUTDOWN |
To stop the server as part of an orderly system shutdown, add the
shutdown command to the site-specific system shutdown procedure.
5.5 Setting Up External Authentication
The OpenVMS operating system Versions 7.1 and higher provide support for external authentication. PATHWORKS Advanced Server participates with the operating system to provide external authentication, which allows PATHWORKS Advanced Server users to log in to the OpenVMS operating system using the PATHWORKS Advanced Server user name and password.
External authentication provides automatic password synchronization between an OpenVMS account and a corresponding Windows NT account. With external authentication enabled, users who have both OpenVMS and PATHWORKS Advanced Server user accounts can avoid having to maintain two different passwords.
To provide external authentication on the system, perform the following procedures.
| Step | Procedure | Refer to... |
|---|---|---|
| 1. |
Install one of the following:
|
Chapter 2, Installing the PATHWORKS Advanced Server |
| 2. | Copy the external authentication files to the system. | Section 5.5.1, Setting Up External Authentication in OpenVMS Clusters |
| 3. | Enable external authentication for the system. |
The appropriate OpenVMS document, one of the following:
|
| 4. | Set the OpenVMS user account to allow external authentication. |
The appropriate OpenVMS document, one of the following:
|
| 5. | Establish host mapping between the PATHWORKS Advanced Server user account and the OpenVMS user account, if necessary. | PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide |
If you are running PATHWORKS Advanced Server in an OpenVMS cluster, and you have enabled external authentication for PATHWORKS Advanced Server users, you should set up external authentication on all the member nodes in an OpenVMS cluster. If any nodes in the cluster are not running the PATHWORKS Advanced Server, you follow the procedure described in this section to set up external authentication on nodes that are not running the PATHWORKS Advanced Server.
For information about enabling external authentication, refer to the appropriate OpenVMS manual:
External authentication cannot occur if a network connection is required and the network is down. However, privileged users can enter the /LOCAL_PASSWORD qualifier after the OpenVMS user name at the login prompt, to specify local authentication. Be sure to specify the OpenVMS user name and password when using the /LOCAL_PASSWORD qualifier.
Because using the /LOCAL_PASSWORD qualifier effectively overrides the security policy established by the system manager, it is allowed only under the following conditions:
Refer to the OpenVMS System Management Utilities Reference Manual for more information about the
/LOCAL_PASSWORD qualifier to the LOGIN command.
5.5.3 Configuring Externally Authenticated Client Connections
By default, the PATHWORKS Advanced Server supports the processing of up to 10 simultaneous external authentication requests. You can modify this maximum to suit the server requirements using the Configuration Manager. To start the Configuration Manager, enter the following command:
$ ADMINISTER/CONFIGURATION |
The basic server parameters include the number of simultaneous activations for users with external authentication (also called "Single Sign-on").
For more information about using the Configuration Manager, refer to
the PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide.
5.6 Installing Optional Server Administration Tools
The PATHWORKS Advanced Server provides optional client-based server administration tools that allow you to manage the server from Windows 95, Windows 98, Windows for Workgroups, or Windows NT clients. These tools are available in the PWUTIL share after installing, configuring and starting the server.
The SRVTOOLS directory in the PWUTIL share contains a subdirectory for each type of client computer. Refer to the README.TXT file in the appropriate subdirectory for instructions on installing the software on the client computer.
Refer to the Windows NT Server documentation or use online Help for more information about how to use Windows NT Server administration tools.
This chapter describes how to set up a wide area network (WAN) using one of the TCP/IP transport software products supported by PATHWORKS Advanced Server.
This chapter consists of the following sections:
The PATHWORKS Advanced Server allows you to use one or both of the following methods for wide area networking name resolution:
In order to use them, they must be enabled using the Configuration
Manager. You can enable them through the PWRK$CONFIG.COM command
procedure, which provides access to the Configuration Manager when you
answer YES to the question "Do you want to change server
configuration parameters." To enable one or both of the wide area
networking methods, select the Transports screen and select the
appropriate checkbox. (Refer to the PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide for
information about using the Configuration Manager.)
6.2 Using the LMHOSTS File for Wide Area Networking
The PATHWORKS Advanced Server software provides the ability to set up a wide area network with the TCP/IP transport through the use of the LMHOSTS file. This file contains a list of domain controllers and member servers that are not in the same TCP/IP subnet as the primary domain controller. The LMHOSTS file allows the PATHWORKS Advanced Server to participate in a Windows NT wide area network as well.
Unlike a Windows NT Server, PATHWORKS Advanced Server does not support remote
LMHOSTS files (called into the Windows NT LMHOSTS file using #INCLUDE).
To include the same host names as an existing LMHOSTS file on a Windows
NT Server, copy the LMHOSTS file to the PATHWORKS Advanced Server, then manually
insert the entries into the PATHWORKS Advanced Server LMHOSTS file.
6.2.1 Setting up a TCP/IP Wide Area Network
To set up a TCP/IP wide area network, modify the LMHOSTS file, which consists of a list of the host names and TCP/IP addresses of the domain controllers and member servers in the wide area network that are in the same domain.
When you include a node in the LMHOSTS file, the primary domain controller copies the user account database onto that node and keeps it up to date. If you omit a node, its user account database may become out of date.
You can modify the LMHOSTS file at any time. As long as the LMHOSTS
file exists, users can establish TCP/IP connections to any server
listed in the file.
6.2.2 Enabling LMHOSTS Name Resolution
To use LMHOSTS for name resolution, it must be enabled in the server
configuration. Use the Configuration Manager when you run the
PWRK$CONFIG initial configuration procedure, or run the Configuration
Manager later, as described in PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide.
6.2.3 The LMHOSTS Directory
You set up a wide area network by supplying the following file on all PATHWORKS Advanced Servers that are in different subnets:
PWRK$LMROOT:[LANMAN]LMHOSTS.
The LMHOSTS file has no file extension.
6.2.4 LMHOSTS File Syntax
In the LMHOSTS file, create a list of nodes by specifying the following line for each node:
address nodename #PRE #DOM:domain_name
Where:
For example, the following entry might be included in the LMHOSTS file:
12.13.14.15 SERVER #PRE #DOM:VMSDOMAIN
This entry results in NetBIOS name SERVER with Internet address
12.13.14.15 being preloaded into the cache. Both the NetBIOS name
SERVER and the NetBIOS name VMSDOMAIN (the name of the domain) will be
available for matching.
6.2.5 Managing the LMHOSTS File
To change the list of available nodes, you can edit the file at any time. Domain names are resolved by checking the LMHOSTS file dynamically.
To disable LMHOSTS name resolution, rename the LMHOSTS file to any name other than LMHOSTS.
When you modify or disable the LMHOSTS file, it is not necessary to
restart the PATHWORKS Advanced Server. The change is effective immediately and is
referenced at the next lookup.
6.2.6 Using the LMHOSTS Log File
If errors occur when the LMHOSTS file is accessed, the errors are recorded in the following file:
PWRK$LMROOT:[LOGS]PWRK$KNBDAEMON_nodename.LOG
This file is open and being written to while the PATHWORKS Advanced Server is running. To close the log file, you must stop the PATHWORKS Advanced Server.
To prevent the log file from becoming too large, each error is logged
only once: the first time it occurs. If an error is found in the log
file, it is not logged again.
6.3 Using WINS in a Wide Area Network
You can configure the PATHWORKS Advanced Server as a WINS client. This allows the PATHWORKS Advanced Server to use WINS for NETBIOS name registration, resolution, renewal, and release in a wide area network configuration.
For more information on how to use the Configuration Manager to
configure the PATHWORKS Advanced Server to use WINS, refer to the PATHWORKS for OpenVMS (Advanced Server)
Server Administrator's Guide.
6.3.1 Setting up WINS Support for OpenVMS Clusters
To allow clients that are configured for WINS support to use a PATHWORKS alias name to connect to a clustered PATHWORKS Advanced Server across a WAN, you must add to the WINS database a static multihomed entry for the PATHWORKS alias name. The following is an example of an entry for the PATHWORKS alias name alpha1_alias:
alpha1_alias 16.20.240.24 |
When adding the static multihomed entry for the PATHWORKS alias name, you should enter the TCP/IP address of each node in the OpenVMS cluster that is running PATHWORKS Advanced Server.
The TCP/IP address that you place at the top of the list in the WINS database should be that of the first node that will start PATHWORKS Advanced Server in the cluster. |
For more information about adding static entries to the WINS database, refer to your WINS product documentation.
This chapter describes how to remove the PATHWORKS Advanced Server software from your system.
This chapter consists of the following sections:
You may need to remove server software for one of the following reasons:
You remove the PATHWORKS Advanced Server using a command procedure that is included when you install PATHWORKS Advanced Server. The deinstallation command procedure performs the following operations:
To start the deinstallation procedure and remove PATHWORKS Advanced Server software:
$ @SYS$UPDATE:PWRK$DEINSTAL |
Table 7-1, PWRK$DEINSTAL Prompts, tells you how to respond to the prompts the deinstallation procedure displays.
| At this prompt... | If you want the removal procedure to... | Enter... |
|---|---|---|
| Are you sure you want to deinstall PATHWORKS Advanced Server[no]: | Continue | YES |
| Exit | [Return] | |
| Do you want to delete the PATHWORKS Advanced Server data files [no]: | Save the PATHWORKS Advanced Server on-disk structure, including the user accounts and share databases | [Return] |
| Remove the PATHWORKS Advanced Server on-disk structure, including the user accounts and share databases | YES |
This is a sample of the removal procedure for PATHWORKS Advanced Server software.
This procedure shuts down all PATHWORKS V6.0B for OpenVMS servers and deletes all PATHWORKS V6.0B for OpenVMS (Advanced Server) images. Are you sure you want to deinstall PATHWORKS V6.0B for OpenVMS (Advanced Server)? [no]: YES Do you want to delete the Advanced Server data files [no]: YES Shutting down the currently running server(s)... Deleting PATHWORKS V6.0B for OpenVMS (Advanced Server) images... Deleting Advanced Server data files... Deassigning PATHWORKS V6.0B OpenVMS logical names... PATHWORKS V6.0B for OpenVMS (Advanced Server) is now deinstalled. |
The PATHWORKS for OpenVMS (NetWare) software is no longer included with the PATHWORKS for OpenVMS software kit. Therefore, you must run the PATHWORKS for OpenVMS (NetWare) removal procedure before you install PATHWORKS for OpenVMS (Advanced Server).
To start the deinstallation procedure and remove the PATHWORKS NetWare server:
$ @SYS$UPDATE:PWVN$DEINSTAL |
Table 7-2, PWVN$DEINSTAL Prompts, tells you how to respond to the prompts the NetWare server deinstallation procedure displays.
| At this prompt... | If you want the removal procedure to... | Enter... |
|---|---|---|
| Are you sure you want to deinstall DIGITAL PATHWORKS V1.0H for OpenVMS (NetWare) [no] 1: | Continue | YES |
| Exit | [Return] | |
| Do you want to delete the NetWare data files [no]: | Save the NetWare on-disk structure, including the configuration Files | [Return] |
| Remove the NetWare on-disk structure, including the configuration files | YES | |
| Do you want to delete the NetWare SYS Volume [no]: | Save the NetWare SYS volume | [Return] |
| Remove the NetWare SYS volume | YES |
| Previous | Next | Contents | Index |