The PATHWORKS for OpenVMS (NetWare) software is no longer included with the PATHWORKS for OpenVMS software kit. You must run the PATHWORKS for OpenVMS (NetWare) deinstallation procedure before you install PATHWORKS for OpenVMS (Advanced Server).

To start the deinstallation procedure and remove the PATHWORKS NetWare server:

1. Be sure you are logged in to the SYSTEM account.
2. Start the NetWare deinstallation procedure, as follows:

   $ @SYS$UPDATE:PWVN$DEINSTAL

Table 7-2, PWVN$DEINSTAL Prompts, tells you how to respond to the prompts the NetWare server deinstallation procedure displays.

Table 7-2 PWVN$DEINSTAL Prompts

Prompt	Desired Outcome	Response
Are you sure you want to deinstall Compaq 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

This is a sample of the deinstallation procedure for PATHWORKS for OpenVMS (NetWare).

$ @SYS$UPDATE:PWVN$DEINSTAL [Return] This procedure shuts down all PATHWORKS V1.0H for OpenVMS servers, and deletes all PATHWORKS V1.0H for OpenVMS (NetWare) images. Are you sure you want to deinstall PATHWORKS V1.0H for OpenVMS (NetWare) [no]: YES [Return] Do you want to delete the NetWare SYS Volume [no]: YES [Return] Stopping PATHWORKS for OpenVMS (NetWare) Server... Process NETBIOS stopped Process PWRK$LICENSE_R stopped Stopping IPX Daemon (NPSD)... Deleting PATHWORKS for OpenVMS common images... Deleting PATHWORKS for OpenVMS NETBIOS component... Deleting PATHWORKS V1.0H for OpenVMS (NetWare) images... Deleting NetWare data files... Deleting NetWare SYS Volume... Removing PWRK$DEFAULT and PWRK$GUEST VMS accounts... Removing PATHWORKS V1.0H for OpenVMS identifiers... Removing PATHWORKS V1.0H for OpenVMS DECnet objects... Deassigning PATHWORKS V1.0H for OpenVMS logical names... PATHWORKS V1.0H for OpenVMS (NetWare) is now deinstalled.

Table A-1 summarizes the tasks that you need to perform to install and configure the PATHWORKS Advanced Server. You can photocopy this table and use it as a checklist as you read about and complete the tasks in this book.

Table A-1 Installation and Upgrade Checklist

[]	1.	Prepare for the installation by completing all preinstallation tasks on the checklist in Section 1.9, Preinstallation Tasks, including the following: Check the part listing. Make sure that you have the required hardware. Log in to the SYSTEM account (or an equivalent account). Make sure your system has the required software. Read the release notes. Make sure that the system parameters GBLPAGES, GBLSECTIONS, PROCSECTCNT, and SCSNODE are set properly. Make sure the ENQLM quota system process parameter is set properly. Back up the system disks. Make sure that you have enough disk space to install the software. Make sure that the queue manager is running. Check the time zone configuration. Verify that DECnet (or DECnet-Plus) and TCP/IP, if needed, are running. Check for existing Compaq OpenVMS server images and files on the system. The system should be free of PATHWORKS for OpenVMS (NetWare) and PATHWORKS (LAN Manager) files, and no Compaq OpenVMS file and printer server images should be running. Check OpenVMS Cluster configuration, if installing on an OpenVMS Cluster.
[]	2.	Start the installation procedure and respond to installation prompts. You may choose to install: The complete PATHWORKS Advanced Server The Upgrade utility only The License Server only The PATHWORKS external authentication software only When installing the PATHWORKS Advanced Server in an OpenVMS Cluster, perform these functions in the order indicated: Install the server everywhere appropriate in the OpenVMS Cluster Configure the server everywhere in the cluster Then, start the server everywhere in the cluster
[]	3.	Start the configuration procedure and respond to configuration prompts.
[]	4.	If you are upgrading from PATHWORKS V5 for OpenVMS (LAN Manager), complete the upgrade procedure. Refer to the Compaq PATHWORKS for OpenVMS (Advanced Server) Server Migration Guide for information about how to: Determine the role of the server Upgrade the server Upgrade OpenVMS Clusters Create upgrade reports Upgrade users and groups Upgrade shares Upgrade security Upgrade server configuration parameters
[]	5.	Run the Installation Verification Procedure (if you did not do so when you installed the server).
[]	6.	Start the server (if you did not do so when you configured the server).

This appendix shows sample installation and configuration procedures for the PATHWORKS Advanced Server on an OpenVMS Cluster.

B.1 Sample Server Installation

The following example shows a sample installation dialog for the PATHWORKS Advanced Server.

$ @SYS$UPDATE:VMSINSTAL PWRK061 SYS$DEVICE:[KITS.PWRK] [Return] OpenVMS AXP Software Product Installation Procedure V7.2-1H1 It is 16-SEP-2001 at 15:29. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? [Return] The following products will be processed: PWRK V6.1 Beginning installation of PWRK V6.1 at 15:29 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. PATHWORKS for OpenVMS Installation © Compaq Computer Corporation 2000. All rights reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. This software is proprietary to and embodies the confidential technology of Compaq Computer Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Compaq or an authorized sublicensor.

Please select from the following install options: PATHWORKS V6.1 for OpenVMS (Advanced Server) PATHWORKS V6.1 for OpenVMS (Advanced Server) License Server (only) External Authentication images (only) * Do you want to install the complete PATHWORKS V6.1 for OpenVMS [NO]? YES [return] The following components will be installed: PATHWORKS V6.1 for OpenVMS (Advanced Server) If the selection is correct, the installation will continue. If the selection is not correct, you can change your selection. Press CTRL/Y if you want to terminate the installation. * Is the selection correct [YES]? [Return] NOTE ---- Because this kit provides a new streams execlet for NetBEUI and TCP/IP, you MUST reboot all nodes in the cluster that are now running or have run PATHWORKS to complete installation of PATHWORKS. If you do not reboot the nodes at this time, you must remember to reboot them later before starting PATHWORKS. To complete the installation of this product, you should reboot the system. If it is not convenient to reboot at this time, then enter NO to the following question. If you enter NO, the installation procedure will continue. * Will you allow a system shutdown after this product is installed [YES]? NO [Return] %PWRK-I-VERSION, Checking for OpenVMS version 6.2, or later... * Do you want to run the IVP after the installation is finished [YES]? [Return] * Do you want to purge files replaced by this installation [YES]? [Return] %PWRK-I-FREEBLKS, Checking for 160000 free blocks User Accounts and User Identification Codes (UICs) -------------------------------------------------- PATHWORKS for OpenVMS creates two OpenVMS accounts: a default account, PWRK$DEFAULT, and a guest account, PWRK$GUEST. The default UIC group number for both these new accounts depends on the following: o If you are installing the server for the first time, the default is the first unused UIC group number, starting with 360. o If there is an existing account PCFS$ACCOUNT, the default is the UIC group number associated with PCFS$ACCOUNT. o If there is an existing account PWRK$DEFAULT or PWRK$GUEST, the default is the UIC group number associated with PWRK$DEFAULT or PWRK$GUEST, in preference to PCFS$ACCOUNT. However, the default UIC group number will not be used to change the UIC of any existing accounts. For more information about UIC group numbers, see the OpenVMS System Manager's Manual. * Enter default UIC group number for PWRK$DEFAULT and PWRK$GUEST [360]: [Return] All questions have been answered. The installation of PATHWORKS for OpenVMS will continue. %PWRK-I-ACCOUNTS, Creating OpenVMS accounts for PWRK$DEFAULT and PWRK$GUEST %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named PWRK$DEFAULT. %UAF-I-ADDMSG, user record successfully added %UAF-I-RDBADDMSGU, identifier PWRK$DEFAULT value [000360,000001] added to rights database %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named PWRK$GUEST. %UAF-I-ADDMSG, user record successfully added %UAF-I-RDBADDMSGU, identifier PWRK$GUEST value [000360,000002] added to rights database %VMSINSTAL-I-RESTORE, Restoring product save set C ... %VMSINSTAL-I-RESTORE, Restoring product save set E ... %PWRK-I-DEFOBJS, Defining DECnet objects PCX$SERVER and PCSA$MAIL %PWRK-I-DCLCMDS, Installing PATHWORKS DCL commands %PWRK-I-SPECIFY, Specifying target directories for the provided files %PWRK-I-OBSOLETE, Deleting obsolete files Next Steps ---------- To continue the installation procedure, enter the following command to execute the server configuration command procedure: $ @SYS$UPDATE:PWRK$CONFIG For information about the configuration command procedure, see the PATHWORKS (Advanced Server) Installation and Configuration Guide. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Copyright Compaq Computer Corporation 2001. All rights reserved. Starting Installation Verification Procedure for PATHWORKS V6.1 for OpenVMS (Advanced Server) %PWRK-I-NORMAL, IVP completed successfully Installation of PWRK V6.1 completed at 15:36 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]PWRK061.VMI_DATA VMSINSTAL procedure done at 15:36

B.2 Sample Server Configuration

The following example shows a sample configuration dialog for the PATHWORKS Advanced Server.

$ @SYS$UPDATE:PWRK$CONFIG [Return] PATHWORKS V6.1 for OpenVMS (Advanced Server) Configuration Procedure PATHWORKS stores and accesses the following types of data files: o Configuration parameter files o License Server data files o Log files o Printer spool files o Virtual memory section files You can specify any existing OpenVMS disk device that has at least 5000 free blocks of disk space to store these data files. Note: the server frequently accesses the data files stored on the disk. If these files are stored on the system disk, it can degrade the performance of both the OpenVMS system and the server. Therefore, Compaq recommends that you specify a disk other than the system disk. Press RETURN to continue: [Return] If this OpenVMS Cluster has multiple system disks, make sure that all nodes on which you plan to run PATHWORKS: o Use the same disk device to store and access PATHWORKS data files. o Share the same SYSUAF.DAT file. In each system disk's startup file, define a system logical name that points all nodes to the shared SYSUAF.DAT file. For example: $ define/system/exec sysuaf pencil$dka300:[sys0.sysexe]sysuaf.dat The startup file is called SYS$MANAGER:SYSTARTUP_VMS.COM Enter disk device name where PATHWORKS data files will be stored [SYS$SYSDEVICE:]: DISK$PWRK: [Return] Creating PATHWORKS directory tree on DISK$PWRK:... Creating Advanced Server directory tree... Copying client files to Advanced Server directory tree... Creating PATHWORKS Monitor user authorization file PWRK$COMMON:PWMONUAF.DAT ...

Changing the server configuration parameters will allow you to modify this server's client capacity and select the transports to be used. COBRAZ is currently configured to + support 20 PC clients + use the following transport(s): DECnet If you want this server to be the primary domain controller, you should configure it to use all the transports used by any of the backup servers in the domain. If you want this server to be a backup domain controller, you should configure it to have at least one transport in common with the domain's primary domain controller, otherwise this configuration will fail. If you do not change the configuration parameters now, you may do so later by typing ADMIN/CONFIG. Do you want to change the server configuration parameters now? [YES]: NO [Return] Reading current configuration parameters ... PATHWORKS V6.0 for OpenVMS is presently configured to run as follows: 1. Run the License Server: NO 2. Enable Timesource service: NO 3. Enable Alerter service: YES 3a. Alert user names: Administrator 4. Enable Netlogon service: YES 5. Advanced Server domain: LANGROUP 6. Advanced Server role: PRIMARY 7. Advanced Server computer name: COBRAZ 7a. PATHWORKS OpenVMS Cluster alias: COBRAZ_ALIAS 8. Server announce comment: PATHWORKS V6.1 for OpenVMS (Advanced Server) Enter item number, or RETURN to use these values [DONE]: [Return] Saving parameters ... Checking the access control list file ... Successfully created new ACL store Creating sharefile PWRK$LMROOT:[LANMAN.DATAFILES]SHAREDB. ... New sharefile has been created. ADMIN$ added IPC$ added PWUTIL added

The Advanced Server Administrator account is used to administer the server. The Administrator account is mapped by default to the OpenVMS SYSTEM account. The Administrator account password can be up to 14 characters long and the case of the characters used will be preserved. Enter Administrator account password: [Return] Re-enter to verify password: [Return] Changing password for Administrator account... Checking system resources... The current system configuration for COBRAZ will support 20 PC clients. PATHWORKS is configured to use DECnet. To automatically start PATHWORKS V6.1 for OpenVMS at system startup, you should add the following line to the SYS$MANAGER:SYSTARTUP_VMS.COM file. @SYS$STARTUP:PWRK$STARTUP Note: Add this line below the lines that start all network transports (such as DECnet). Before starting PATHWORKS V6.1 for OpenVMS on this system, be sure to execute @SYS$UPDATE:PWRK$CONFIG on each node that will run PATHWORKS. Do you want to start PATHWORKS V6.1 for OpenVMS on node COBRAZ now [yes]: NO [Return] $

This appendix shows sample installation and configuration procedures for a standalone License Server on an OpenVMS Cluster.

C.1 Sample Standalone License Server Installation

The following example shows a sample installation dialog for the standalone License Server.

$ @SYS$UPDATE:VMSINSTAL PWRK061 SYS$DEVICE:[KITS.PWRK] [Return] OpenVMS AXP Software Product Installation Procedure V7.2-1H1 It is 16-SEP-2001 at 16:08. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? [Return] The following products will be processed: PWRK V6.1 Beginning installation of PWRK V6.1 at 16:08 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. PATHWORKS for OpenVMS Installation © Compaq Computer Corporation 2000. All rights reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. This software is proprietary to and embodies the confidential technology of Compaq Computer Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Compaq or an authorized sublicensor.

Please select from the following install options: PATHWORKS V6.1 for OpenVMS (Advanced Server) PATHWORKS V6.1 for OpenVMS (Advanced Server) License Server (only) External Authentication images (only) * Do you want to install the complete PATHWORKS V6.1 for OpenVMS [NO]? NO [Return] * Do you want to install only the PATHWORKS License Server [NO]? YES [Return] * Do you want to install only the External Authentication images [NO]? NO [Return] The following components will be installed: PATHWORKS V6.1 License Server If the selection is correct, the installation will continue. If the selection is not correct, you can change your selection. Press CTRL/Y if you want to terminate the installation. * Is the selection correct [YES]? [Return] %PWRK-I-VERSION, Checking for OpenVMS version 6.2, or later... NOTE ---- Because this kit provides a new streams execlet for NetBEUI and TCP/IP, you MUST reboot the system to complete installation of PATHWORKS. If you do not reboot the system at this time, you must remember to reboot later before starting PATHWORKS. To complete the installation of this product, you should reboot the system. If it is not convenient to reboot at this time, then enter NO to the following question. If you enter NO, the installation procedure will continue. * Will you allow a system shutdown after this product is installed [YES]? [Return] * How many minutes for system shutdown [0]: [Return] * Do you want to do an automatic system reboot [YES]? [Return] * Do you want to run the IVP after the installation is finished [YES]? [Return] * Do you want to purge files replaced by this installation [YES]? [Return] %PWRK-I-FREEBLKS, Checking for 160000 free blocks All questions have been answered. The installation of PATHWORKS for OpenVMS will continue. %VMSINSTAL-I-RESTORE, Restoring product save set C ... %VMSINSTAL-I-RESTORE, Restoring product save set E ... %PWRK-I-DEFOBJS, Defining DECnet objects PCX$SERVER and PCSA$MAIL %PWRK-I-DCLCMDS, Installing PATHWORKS DCL commands %PWRK-I-SPECIFY, Specifying target directories for the provided files %PWRK-I-OBSOLETE, Deleting obsolete files %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Copyright Compaq Computer Corporation 1993, 2001. Starting Installation Verification Procedure for PATHWORKS V6.1 for OpenVMS (Advanced Server) %PWRK-I-NORMAL, IVP completed successfully Installation of PWRK V6.1 completed at 19:33 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]PWRK061.VMI_DATA VMSINSTAL procedure done at 19:34

C.2 Sample Standalone License Server Configuration

The following example shows a sample PATHWORKS Advanced Server configuration procedure for the standalone License Server.

$ @SYS$UPDATE:PWRK$CONFIG [Return] PATHWORKS V6.1 for OpenVMS (Advanced Server) Configuration Procedure PATHWORKS stores and accesses the following types of data files: o Configuration parameter files o License Server data files o Log files o Printer spool files o Virtual memory section files You can specify any existing OpenVMS disk device that has at least 5000 free blocks of disk space to store these data files. Note: the server frequently accesses the data files stored on the disk. If these files are stored on the system disk, it can degrade the performance of both the OpenVMS system and the server. Therefore, Compaq recommends that you specify a disk other than the system disk. If this OpenVMS Cluster has multiple system disks, make sure that all nodes on which you plan to run PATHWORKS: o Use the same disk device to store and access PATHWORKS data files. o Share the same SYSUAF.DAT file. In each system disk's startup file, define a system logical name that points all nodes to the shared SYSUAF.DAT file. For example: $ define/system/exec sysuaf pencil$dka300:[sys0.sysexe]sysuaf.dat The startup file is called SYS$MANAGER:SYSTARTUP_VMS.COM Enter disk device name where PATHWORKS data files will be stored [SYS$SYSDEVICE:]: DISK$PWRK: [Return] Creating PATHWORKS directory tree on DISK$PWRK:... The PATHWORKS License Server can serve PATHWORKS licenses for Advanced Server clients over DECnet, NetBEUI, and TCP/IP. The Advanced Server file server does not need to be running for the License Server to operate. Do you want to serve PATHWORKS licenses over DECnet [yes]: [Return] Do you want to serve PATHWORKS licenses over NetBEUI [no]: YES [Return] Do you want to serve PATHWORKS licenses over TCP/IP [no]: YES [Return] Do you want to start the PATHWORKS License Server now [yes]: NO [Return] $