PATHWORKS Advanced Server supports connections from the following types of clients:

• Windows NT
• Windows 95
• Windows 98
• Windows for Workgroups
• PATHWORKS for DOS and Windows
• PATHWORKS for Windows 95
• PATHWORKS 32

The system must have at least 64 MB of physical memory to run the PATHWORKS Advanced Server.

1.9 Pre-installation Tasks

Use the following checklist to make sure you have completed all the tasks you should perform before you install the software. Each task is described later in this section.

Table 1-1 Pre-installation Checklist

[]	1.	Check the part listing.
[]	2.	Make sure that the network hardware is installed and connected.
[]	3.	Make sure that the required software is installed.
[]	4.	Log in to the SYSTEM account.
[]	5.	Back up the system disks.
[]	6.	Read the release notes.
[]	7.	Make sure that you have adequate disk space for installation.
[]	8.	Check system parameters.
[]	9.	Check the queue manager.
[]	10.	Check the time zone configuration.
[]	11.	Make sure that DECnet is running, if you are planning to use the DECnet transport.
[]	12.	Make sure that TCP/IP is running, if you are planning to use the TCP/IP transport.
[]	13.	Check the OpenVMS cluster configuration, if you are installing PATHWORKS Advanced Server on a cluster.

Before you install PATHWORKS Advanced Server, perform these tasks:

1.9.1 Step 1: Check the Part Listing

The software part listing specifies the contents of the kit you receive. Check the contents of your kit against that information. If parts are missing or your kit is damaged, contact your Compaq Computer Corporation representative.

1.9.2 Step 2: Check the Network Hardware

PATHWORKS Advanced Server runs on OpenVMS systems that meet the software requirements. The PC local area network (LAN) requires:

• A supported network controller board in the server and in each client
• The cables to connect each client to the network

PATHWORKS Advanced Server requires the following:

• OpenVMS operating system, Version 7.1 or Version 7.2.
• DECnet or DECnet-Plus, if you are going to use the DECnet transport, the mail server, or the license server over DECnet.
• A TCP/IP product, if you are going to use the TCP/IP transport. Supported TCP/IP products are described in the PATHWORKS for OpenVMS (Advanced Server) Release Notes.

Before you install PATHWORKS Advanced Server, log in to the SYSTEM account, which has sufficient privileges to run the installation procedure.

To log in to the SYSTEM account:

1. At the Username: prompt, enter SYSTEM:

   Username: SYSTEM

2. At the Password: prompt, enter the password to the SYSTEM account. The password you enter is not displayed.

To safeguard against the loss of valuable data, Compaq Computer Corporation recommends that you back up all disks on your system before you install any layered product.

To do a system backup, use the OpenVMS BACKUP command. For information about the BACKUP command, see the OpenVMS System Management Utilities Reference Manual.

1.9.6 Step 6: Print and Read the Release Notes

If you have not already read the release notes, you should do so before installing the software. See Section 1.6, Reading the Release Notes, for more information.

1.9.7 Step 7: Check Disk Space Requirements

On your OpenVMS system, the following amount of free disk space on the system disk is required during the installation procedure.

To install these components...	You need this number of blocks on an Alpha system...	You need this number of blocks on a VAX system...
PATHWORKS Advanced Server	144,500 1	125,000 1
Standalone license server	144,500	125,000
Upgrade utility only	30,000	25,500
External authentication images only	144,500	125,000

To check the number of free blocks on the system disk, enter:

$ SHOW DEVICE SYS$SYSDEVICE

Result

The OpenVMS system displays information about the system disk, including the number of free blocks. For example:

Device Device Error Volume Free Trans Mnt Name Status Count Label Blocks Count Cnt DUA0: Mounted 0 AXPVMSSYS 1724856 280 1

1.9.8 Step 8: Check System Parameters

Make sure that the following OpenVMS system parameters are set properly.

GBLPAGES parameter

The minimum value of this parameter is listed in Table 1-2, GBLPAGES Parameter Minimum Value.

Table 1-2 GBLPAGES Parameter Minimum Value

For a VAX system, the value must be at least...	For an Alpha system, the value must be at least...
3500 pages	7500 pages

To ensure that your system has enough free global pages:

1. Enter the following:

   $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES")

   
   The value of the GBLPAGES parameter is displayed. For example:

   7500

2. If the value is less than required, edit the file SYS$SYSTEM:MODPARAMS.DAT and add a line similar to the following:

   ADD_GBLPAGES = 7500

GBLSECTIONS parameter

The minimum value of this parameter differs depending on which server is to be installed, as described in Table 1-3, GBLSECTIONS Parameter Minimum Value.

Table 1-3 GBLSECTIONS Parameter Minimum Value

For the standalone license server only, the value must be at least...	If the PATHWORKS Advanced Server is to be installed, the value must be at least...
50	75

To ensure that your system has enough free global sections:

1. Enter the following:

   $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS")

   
   The value of the GBLSECTIONS parameter is displayed. For example:

   75

2. If the value is less than required, edit the file SYS$SYSTEM:MODPARAMS.DAT and add a line similar to the following:

   ADD_GBLSECTIONS = 75

PROCSECTCNT parameter

The minimum value of this parameter differs depending on which server is to be installed, as described in Table 1-4, PROCSECTCNT Parameter Minimum Value.

Table 1-4 PROCSECTCNT Parameter Minimum Value

For the standalone license server only the value must be at least...	If the PATHWORKS Advanced Server is to be installed, the value must be at least...
32	40

To ensure that the value of the system parameter PROCSECTCNT is adequate:

1. Enter the following:

   $ WRITE SYS$OUTPUT F$GETSYI("PROCSECTCNT")

   
   The value of the PROCSECTCNT parameter is displayed. For example:

   40

2. If the value is less than required, edit the file SYS$SYSTEM:MODPARAMS.DAT and add a line similar to the following:

   MIN_PROCSECTCNT = 40

SCSNODE parameter

This parameter must be defined as your system's computer name. If you are running DECnet, the SCSNODE name should be the same as the DECnet node name.

To check whether the system parameter SCSNODE is defined as your system's computer name:

1. Enter the following command at the system prompt:

   $ WRITE SYS$OUTPUT F$GETSYI("SCSNODE")

   
   One of the following occurs:

   • If SCSNODE is defined, the computer name is displayed. For example, if your system's computer name is SPEEDY:

     $ WRITE SYS$OUTPUT F$GETSYI("SCSNODE") SPEEDY

   • If SCSNODE is not defined, the computer name is not displayed.
2. If SCSNODE is not defined, edit the file SYS$SYSTEM:MODPARAMS.DAT and define the parameter. For example, if your system's computer name is SPEEDY, edit the file so that it contains the following line:

   SCSNODE = "SPEEDY"

   
   If you edit the file SYS$SYSTEM:MODPARAMS.DAT, you must run the OpenVMS command procedure AUTOGEN and reboot the system either now or at some time before configuring the server. For example:

   $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT NOFEEDBACK

   
   For information about running AUTOGEN, see the OpenVMS System Manager's Manual.

The SCSNODE parameter's pre-installation status affects what happens after you install and configure the server and reboot the system, as follows:

If SCSNODE is...	And you...	Then the server...
Not defined	Do not define it	Does not start.
Already defined	Do not define it	Starts.
Not defined	Define it	Starts, but the OpenVMS system renames print and batch queues to include the new computer name. Therefore, you must requeue any existing print or batch jobs to the new queues. You may also have to rebuild the queue database. For information on these system management tasks, see the OpenVMS System Manager's Manual.

1.9.9 Step 9: Check the Queue Manager

It is not necessary to have the queue manager running during installation, but it must be running when you configure the server. You can enter the SHOW QUEUE/MANAGER command to check whether the queue manager is running:

$ SHOW QUEUE/MANAGER

If the queue manager is running, your OpenVMS system displays a message similar to the following:

Queue manager SYS$QUEUE_MANAGER, running, on CPEEDY::

If the queue manager is not running, you can use the following command to start it:

$ START/QUEUE/MANAGER

1.9.10 Step 10: Check Time Zone and TDF

To check the time zone and time differential factor (TDF) settings on the system, run the OpenVMS command procedure
SYS$MANAGER:UTC$TIME_SETUP.COM. From the SYSTEM account, enter the following command to begin the procedure:

$ @SYS$MANAGER:UTC$TIME_SETUP.COM

PATHWORKS Advanced Server's internal time management uses Greenwich Mean Time (GMT). To properly represent the time in the local environment, the time zone information must be set up before the server is started.

To set the time zone on your OpenVMS system, execute the following command procedure:

@ SYS$MANAGER:UTC$TIMEZONE_SETUP.COM

To set the time zone differential factor for the OpenVMS system, execute the following command procedure:

@ SYS$MANAGER:UTC$CONFIGURE_TDF.COM

If you change any time zone information, such as the daylight savings time setting, you must restart the server for the time to be properly represented.

For more information on running the command procedure and resetting time zone and TDF, see the section on setting time zone information in the OpenVMS System Manager's Manual.

1.9.11 Step 11: Check DECnet Status

It is not necessary to have DECnet running during the installation, but DECnet must be running on the system before you can configure the server, if you are planning to enable the DECnet transport.

1.9.11.1 Checking DECnet (Phase IV) Status

If you use DECnet (Phase IV), enter the following command to see whether it is running on the system where you are planning to install the server software:

$ MCR NCP SHOW EXECUTOR

If DECnet (Phase IV) is . . .	Then . . .
Running	The system displays State = on as shown below: Node Volatile Summary as of 16-SEP-1998 12:16:36 Executor node = 12.691 (COBRAZ) State = on Identification = DECnet for OpenVMS AXP V7.1
Not running	You can enter the following command to start it: $ @SYS$MANAGER:STARTNET

1.9.11.2 Checking DECnet-Plus Status

If you use DECnet-Plus (formerly DECnet/OSI for OpenVMS), enter the following command to see whether it is running on the system where you are planning to install the server software:

$ SHOW LOGICAL NET$STARTUP_STATUS

If DECnet is . . .	Then . . .
Running	The system displays: "NET$STARTUP_STATUS" = "RUNNING-ALL" (LNM$SYSTEM_TABLE)
Not running	You can enter the following command to start it: $ @SYS$STARTUP:NET$STARTUP

1.9.12 Step 12: Check TCP/IP Status

If you are planning to use the TCP/IP transport, make sure that TCP/IP is running and that the PATHWORKS IP (PWIP) driver has been loaded. The procedure for starting the TCP/IP product and the PWIP driver differs depending on the TCP/IP product running on the system. Refer to the documentation for your TCP/IP product for information on how to start TCP/IP and the PWIP driver.

For example, for TCP/IP Services for OpenVMS V4.x, use the configuration procedure UCX$CONFIG.COM to enable the PWIP driver on TCP/IP startup, or enter the following OpenVMS commands:

$ @SYS$STARTUP:UCX$STARTUP $ @SYS$STARTUP:UCX$PWIP_STARTUP

You can add these commands to the system startup procedure.

For TCP/IP Services for OpenVMS V5, enable the PWIP driver using the configuration procedure TCPIP:CONFIG.COM, or enter the following OpenVMS commands:

$ @SYS$STARTUP:TCPIP$STARTUP $ @SYS$STARTUP:TCPIP$PWIP_STARTUP

1.9.13 Step 13: Check OpenVMS Cluster Configuration

You can run PATHWORKS Advanced Server on multiple OpenVMS cluster members (server nodes). To do so, follow these steps:

1. On each system disk on which you want to run PATHWORKS Advanced Server, complete:
   • The tasks described in this chapter
   • The VMSINSTAL command procedure described in Chapter 2, Installing the PATHWORKS Advanced Server
2. On each cluster member that you want to use as a PATHWORKS Advanced Server, run the configuration command procedure (PWRK$CONFIG). This ensures that each node has enough resources to run the server.

To install PATHWORKS Advanced Server, proceed to Chapter 2, Installing the PATHWORKS Advanced Server.