This chapter describes tasks you can perform after you install the Advanced Server and consists of the following sections:

• Section 5.1, Before You Begin Post-installation Tasks
• Section 5.2, Verifying the Advanced Server Installation
• Section 5.3, Starting the Advanced Server
• Section 5.4, Ways to Start the Advanced Server
• Section 5.5, Stopping the Advanced Server
• Section 5.6, Setting Up External Authentication
• Section 5.7, Converting Encoded File Names from ODS-2 to ODS-5
• Section 5.8, Installing Optional Server Administration Tools

Before you start the Advanced Server, make sure you have:

• Installed the Advanced Server, as described in Chapter 2, Installing Advanced Server for OpenVMS Software.
• Completed the configuration procedure, as described in Chapter 3, Configuring the Advanced Server.

If you did not run the IVP when you installed the Advanced Server, you can run it now to make sure that the server installed successfully.

To run the IVP, enter the following command:

$ @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, Starting the Advanced Server.
Failed	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.

5.3 Starting the Advanced Server

The following sections describe how to start the Advanced Server and how to automate server startup.

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

The startup procedure:

1. Checks for the required privileges.
2. Verifies that required configuration files are available.
3. Verifies that the server has been configured, and exits if it has not.
4. Loads transport drivers.
5. Installs images.
6. Starts transport support processes.
7. Starts the OpenVMS Registry Server, if necessary.
8. Starts each of the components:
   • License Registrar
   • License server (if configured)
   • File server

You can start the Advanced Server:

• During the configuration procedure, as described in Chapter 3, Configuring the Advanced Server.
• Manually from the command line.
• Automatically each time you reboot.

If you did not start the Advanced Server during the configuration procedure, you can start it now by entering:

$ @SYS$STARTUP:PWRK$STARTUP

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.

5.4.2 How to Define Advanced Server Commands at Login

You can define Advanced Server management commands automatically when you log in to the privileged account that you use to manage the Advanced Server.

To define Advanced Server commands at login, edit the LOGIN.COM file of the privileged account to add the following line:

$ @SYS$STARTUP:PWRK$DEFINE_COMMANDS

5.4.3 How to Start the Advanced Server Automatically

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:

$ START/NETWORK DECNET . . . $ @SYS$STARTUP:PWRK$STARTUP

5.4.4 How to Start the Advanced Server in an OpenVMS Cluster

If you installed and configured the Advanced Server on multiple members of the same OpenVMS cluster, Compaq 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.

Some of the problems that prevent the Advanced Server from starting are:

• SYLOGIN.COM contains commands that are not suitable for detached processes
  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 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. See the OpenVMS DCL Dictionary for more information.
• OpenVMS registry services are not available
  The Advanced Server will start only if the OpenVMS registry services are available. For information about starting the Registry Server, see the OpenVMS System Manager's Manual.
  • If the Registry Server is started as part of Advanced Server startup, a message similar to the following is displayed by the startup procedure:

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

You can stop the Advanced Server at any time for any reason, which can include the following:

• When you change server configuration parameters
• As part of an orderly system shutdown

To stop the Advanced Server, enter the following command:

$ @SYS$STARTUP:PWRK$SHUTDOWN Shutting down the currently running server(s)...

To stop the Advanced Server as part of an orderly system shutdown, add the shutdown command to the site-specific system shutdown procedure.

5.6 Setting Up External Authentication

The OpenVMS operating system Versions 7.1 and higher provide support for external authentication. Advanced Server participates with the operating system to provide external authentication to allow Advanced Server users to log in to the OpenVMS operating system using the 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 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: The Advanced Server The external authentication software only	Chapter 2, Installing Advanced Server for OpenVMS Software.
2.	Enable external authentication for the system.	OpenVMS V7.2 Guide to System Security
3.	Set the OpenVMS user account to allow external authentication.	OpenVMS V7.2 Guide to System Security
4.	Establish host mapping between the Advanced Server user account and the OpenVMS user account, if necessary.	Advanced Server for OpenVMS Server Administrator's Guide

5.6.1 Enabling External Authentication over a Network

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:

• When the user's account has SYSPRV as an authorized privilege. This allows the system manager to gain access to the system when the network is down.
• When Bit 1 is set in the SYS$SINGLE_SIGNON logical name, which allows nonprivileged users who are normally externally authenticated to log in locally.

Refer to the OpenVMS System Management Utilities Reference Manual for more information about the /LOCAL_PASSWORD qualifier to the LOGIN command.

5.6.2 Configuring Externally Authenticated Client Connections

By default, the Advanced Server supports the processing of up to 10 simultaneous external authentication requests. You can modify this maximum to suit the Advanced 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 Advanced Server for OpenVMS Server Administrator's Guide.

5.7 Converting Encoded File Names from ODS-2 to ODS-5

Existing Advanced Server shares may be converted from ODS-2 to ODS-5 to take advantage of the OpenVMS Version 7.2 support of extended file specifications. The Advanced Server for OpenVMS software provides a conversion utility for converting ODS-2 encoded file names on ODS-5 devices that have been converted from ODS-2. The conversion utility removes escape-encoded characters in file names, changing the file names to ISO Latin-1 characters. For example, if a file name is created on an ODS-2 disk containing the character-encoding sequence __E4, to represent the lowercase a-umlaut (ä), the conversion utility removes the encoding and replaces it with the ä character.

You can convert ODS-2 file names to ODS-5 file names after:

• The Advanced Server for OpenVMS has been installed and configured.
• The disk device containing escape-encoded file names has been converted from ODS-2 to ODS-5. Refer to the OpenVMS Guide to Extended File Specifications for information about converting disk devices to ODS-5.

The Advanced Server for OpenVMS software kit includes a file name conversion utility that allows you to convert file names from the encoding used on ODS-2 file systems to ISO Latin-1 file names. The file name conversion utility file is:

SYS$SYSTEM:PWRK$CNVTOHFS.EXE

When the Advanced Server commands have been defined, you can use the PWCONVERT command to invoke the Convert Utility. For information about defining Advanced Server commands, see Section 5.4.2, How to Define Advanced Server Commands at Login. For example, to define the PWCONVERT command, enter the following DCL command:

$ PWCONVERT :== $SYS$SYSTEM:PWRK$CNVTOHFS.EXE

The format of the PWCONVERT command is:

$ PWCONVERT /qualifiers file-spec

Where:

• Qualifiers are optional. They are described in Table 5-1, PWCONVERT Qualifiers. The default setting is used if you omit the qualifier.
• The file-spec argument is required, and may include the device name, directory name, and file name.
  • If you specify only a disk device, the conversion utility scans the entire device for file names that are encoded, and converts them if necessary.
  • If you specify a disk device and a directory, all the files in the specified directory are scanned and converted if necessary. You may include wildcard characters in directory names and file names.
  • If you specify a disk device, directory, and a single file name, only that file is converted.
  • If you enter the PWCONVERT command with no file specification, it prompts you for a file specification. For example:

    $ PWCONVERT FILENAME:

    
    In response to this prompt, you must supply a device name, and optionally a directory and file name to convert. You may include qualifiers.

Table 5-1 PWCONVERT Qualifiers

Qualifier	Description	Default
/CODE_PAGE= n	The code page used to translate encoded characters, where n is the code page. For more information about code pages, refer to the OpenVMS User's Guide.	None
/DISABLE= keyword	Disables the function of the conversion utility specified by the keyword. The keywords are: ACE, which specifies that the conversion utility will not check for PATHWORKS ACEs on the files. STRUCTURE_LEVEL, which specifies that the conversion utility will not check the file system type (ODS-2 or ODS-5).	/NODISABLE
/LOG= log-file-specification	Creates a log file containing the file names converted. You can specify the location and name of the log file using this qualifier.	/NOLOG. Information is displayed and no log file is created.
/VERBOSE	Displays all the file names scanned during the conversion operation.	/NOVERBOSE
/NOLIST	Suppresses the display of all the file names that are converted. Only error messages are displayed.	/LIST

5.7.2 Example of Converting an Encoded File Name

In this example, the file named A FILE.TXT has been created by a Windows 95 client on DISKA, and has been encoded as A__20FILE.TXT. The device DISKA has been converted from ODS-2 to ODS-5. As viewed from OpenVMS, the file appears as follows:

$ DIRECTORY DISKA:[FILES] Directory DISKA:[FILES] . . . A__20FILE.TXT $

Use the PWCONVERT command to convert this file name, as follows:

$ PWCONVERT/VERBOSE DISKA:[FILES]A__20FILE.TXT Scanning file - DISKA:[FILES]A__20FILE.TXT;1 Renamed A__20FILE.TXT to A FILE.TXT Convert Utility Complete $

5.7.3 Example of Converting All Encoded File Names

To convert all the encoded file names on a disk device and directory, enter the PWCONVERT command, specifying the disk device and directory without a file name. For example, to convert all the encoded file names stored on device DISK$USER1, enter the following:

$ PWCONVERT FILENAME: DISK$USER1: Renamed A__20FILE.TXT to A FILE.TXT . . . Convert Utility Complete

5.8 Installing Optional Server Administration Tools

The Advanced Server provides optional client-based server administration tools that allow you to manage the server from Windows 98, Windows 95, 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.