| Previous | Contents | Index |
This is a sample of the removal procedure for DIGITAL PATHWORKS for OpenVMS (NetWare).
$ @SYS$UPDATE:PWVN$DEINSTAL 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 Do you want to delete the NetWare SYS Volume [no]: YES 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.
| [] | 1. |
Prepare for the installation by completing all preinstallation tasks on
the checklist in Section 1.9, Pre-installation Tasks, including the following:
|
| [] | 2. |
Start the installation procedure and respond to installation prompts.
You may choose to install:
|
| [] | 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 PATHWORKS for OpenVMS (Advanced Server)
Server Migration Guide for information about how to:
|
| [] | 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). |
| [] | 7. | Install Windows NT server administration tools (optional). |
This appendix shows sample installation and configuration procedures
for the PATHWORKS Advanced Server on an OpenVMS cluster.
B.1 Sample PATHWORKS Advanced Server Installation Procedure
The following example shows a sample installation dialog for the PATHWORKS Advanced Server.
$ @SYS$UPDATE:VMSINSTAL PWRKV60B060 SYS$DEVICE:[KITS.PWRK] OpenVMS AXP Software Product Installation Procedure V7.1 It is 16-OCT-1998 at 15:29. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? The following products will be processed: PWRKV60B V6.0 Beginning installation of PWRKV60B V6.0 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 © Digital Equipment Corporation 1998. 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 Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from DIGITAL or an authorized sublicensor. |
Please select from the following install options:
PATHWORKS V6.0B for OpenVMS (Advanced Server)
PATHWORKS V6.0B for OpenVMS (Advanced Server) license server (only)
External Authentication images (only)
* Do you want to install the complete PATHWORKS V6.0B for OpenVMS [NO]? YES
The following components will be installed:
PATHWORKS V6.0B 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
%PWRKV60B-I-VERSION, Checking for OpenVMS version 7.1, 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 144500 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...
© Digital Equipment Corporation 1998. All rights reserved.
Starting Installation Verification Procedure
for PATHWORKS V6.0B for OpenVMS (Advanced Server)
%PWRK-I-NORMAL, IVP completed successfully
Installation of PWRKV60B V6.0 completed at 15:36
Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY
Creating installation data file: VMI$ROOT:[SYSUPD]PWRKV60B060.VMI_DATA
VMSINSTAL procedure done at 15:36
|
The following example shows a sample configuration dialog for the PATHWORKS Advanced Server.
$ @SYS$UPDATE:PWRK$CONFIG
PATHWORKS V6.0B 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
76500 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,
Digital 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:
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
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.0B 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 network account is used to
administer the server. The Administrator network account
is mapped by default to the OpenVMS SYSTEM account.
If this server is to join an Advanced Server domain, the Administrator
network account password should be the same as the password
to the domain's existing Administrator network account.
The network account password can be up to 14 characters long.
Enter Administrator network account password:
Re-enter to verify password:
Changing password for Administrator network 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.0B 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.0B 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.0B for OpenVMS on node COBRAZ now [yes]: NO
$
|
This appendix shows sample installation and configuration procedures
for a standalone license server on an OpenVMS cluster.
C.1 Sample Standalone License Server Installation Procedure
The following example shows a sample installation dialog for the standalone license server.
$ @SYS$UPDATE:VMSINSTAL PWRKV60B060 SYS$DEVICE:[KITS.PWRK] OpenVMS AXP Software Product Installation Procedure V7.1 It is 16-OCT-1998 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: PWRKV60B V6.0 Beginning installation of PWRKV60B V6.0 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 © Digital Equipment Corporation 1998. 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 Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from DIGITAL or an authorized sublicensor. |
Please select from the following install options:
PATHWORKS V6.0B for OpenVMS (Advanced Server)
PATHWORKS V6.0B for OpenVMS (Advanced Server) license server (only)
External Authentication images (only)
* Do you want to install the complete PATHWORKS V6.0B for OpenVMS [NO]? NO
* Do you want to install only the PATHWORKS license server [NO]? YES
* Do you want to install only the External Authentication images [NO]? NO
The following components will be installed:
PATHWORKS V6.0B 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]
%PWRKV60B-I-VERSION, Checking for OpenVMS version 7.1, 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]
%PWRKV60B-I-FREEBLKS, Checking for 144500 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 ...
%PWRKV60B-I-DEFOBJS, Defining DECnet objects PCX$SERVER and PCSA$MAIL
%PWRKV60B-I-DCLCMDS, Installing PATHWORKS DCL commands
%PWRKV60B-I-SPECIFY, Specifying target directories for the provided files
%PWRKV60B-I-OBSOLETE, Deleting obsolete files
%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...
© Digital Equipment Corporation 1998. All rights reserved.
Starting Installation Verification Procedure
for PATHWORKS V6.0B for OpenVMS (Advanced Server)
%PWRK-I-NORMAL, IVP completed successfully
Installation of PWRKV60B V6.0 completed at 19:33
Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY
Creating installation data file: VMI$ROOT:[SYSUPD]PWRKV60B060.VMI_DATA
VMSINSTAL procedure done at 19:34
|
The following example shows a sample PATHWORKS Advanced Server configuration procedure for the standalone license server.
$ @SYS$UPDATE:PWRK$CONFIG
PATHWORKS V6.0B 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
5500 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,
Digital recommends that you specify a disk other than the system disk.
Press RETURN to continue:
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:
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
Do you want to serve PATHWORKS licenses over TCP/IP [no]: YES
Do you want to start the PATHWORKS license server now [yes]: NO
|
To automatically start the PATHWORKS license server 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).
$
|
| Previous | Next | Contents | Index |