This chapter takes you through the TCPware product installation procedure and certain post-installation tasks. It is for the OpenVMS system manager, administrator, or technician responsible for product installation.
To prepare for installation, see Chapter 1, Before You Begin.
|
Note: Once you have installed TCPware, you need to reinstall it after you have done a major VMS upgrade.
|
To install TCPware:
1. Load the software.
2. Run the VMSINSTAL procedure.
3. Install other products, if needed, and perform post-installation tasks.
There are three steps to loading the TCPware software:
1. Log in to the system manager's account.
2. If TCPware is currently running, shut it down:
$ @TCPWARE:SHUTNET
If you are installing on a VMScluster, shut down TCPware on each node in the cluster:
$ RUN SYS$SYSTEM:SYSMAN
SYSMAN>SET ENVIRONMENT/CLUSTER
SYSMAN>DO @TCPWARE:SHUTNET
SYSMAN>EXIT
3. Physically insert the TCPware CD-ROM into the appropriate device.
· In a VMS cluster environment, if you want to access the media from more than one node, enter the following:
$ MOUNT/CLUSTER/SYSTEM device volume-label
· On a standalone system, or if you want to prevent multiple users from accessing the software, enter the following:
$ MOUNT device volume-label
|
Note: If you install TCPware on a VMScluster that has a common system disk, install the software on only one node in the cluster. If reinstalling or upgrading TCPware, first shut down TCPware on all nodes in the cluster.
If you install TCPware on a mixed architecture cluster, make sure you have TCPware licenses for all of the architectures in the cluster and install TCPware once on each architecture.
|
VMSINSTAL is OpenVMS's installation program for layered products. VMSINSTAL prompts you for any information it needs. Here are the first steps to follow:
|
Step |
For this task... |
Enter this response... |
|
1 |
Make sure that you are logged in to the system manager’s account, and invoke VMSINSTAL |
@SYS$UPDATE:VMSINSTAL |
|
2 |
Determine if you are satisfied with your system disk backup |
Return or Y (Yes) or N (No) |
|
3 |
Determine where the distribution volumes will be mounted |
The disk (and directory) or tape device where you want the software to be mounted. |
|
4 |
Enter the products you want processed from the first distribution volume set |
TCPWARE060 |
|
5 |
Enter the installation options you wish to use (such as obtaining the Release Notes) |
Return for no options or N for Release Notes. |
|
6 |
Specify the directory where you want the common files installed |
Return
if accepting default of SYS$COMMON or The device and directory of your choice. |
|
7 |
Specify the directory where you want the node specific files installed |
Return if
accepting default of SYS$SPECIFIC or The device and directory of your choice. |
Starting VMSINSTAL:
$ @SYS$UPDATE:VMSINSTAL
VAX/VMS Software Product Installation Procedure V7.3
It is 1-SEP-2014 at 17:13.
Enter a question mark (?) at any time for help.
* Are you satisfied with the backup of your system disk [YES]? Return
* Where will the distribution volumes be mounted: DKA300:
Enter the products to be processed from the first distribution
volume set.
* Products: TCPWARE060
* Enter installation options you wish to use (none): Return
The following products will be processed:
TCPWARE V6.0
Beginning installation of TCPWARE V6.0 at 17:14
%VMSINSTAL-I-RESTORE, Restoring product save set A ...
%VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.
TCPware(R) for OpenVMS Version 6.0
Copyright (c) 2018, by Process Software.
Refer to the "Installation" chapter of the TCPware Installation
& Configuration Guide.
You can specify the directory where you want the TCPware common files
installed. The default location for the TCPware common files is
SYS$COMMON. A [.TCPWARE] subdirectory will be created in the directory
you specify.
* Where do you want to install the TCPware common files SYS$COMMON]:Return
You can specify the directory where you want node specific files
installed. This directory must not be used by any other nodes in a
cluster. The default location is SYS$SPECIFIC:[TCPWARE]. A [.TCPWARE]
subdirectory will be created in the directory you specify.
* Where do you want to install the TCPware node specific files [SYS$SPECIFIC]: Return
TCPware will be installed.
VMSINSTAL continues by prompting you about rebooting the system, reinstalling TCPware in case of an upgrade, selecting the components, and confirming the installation.
VMSINSTAL continues as follows:
|
Step |
For this task... |
Enter this response... |
|
1 |
If you started an earlier version of TCPware since the system booted, reboot the system. You can reboot now or later. If you reboot later, do so before starting TCPware. |
Y (Yes) or N (No) |
|
2 |
If you answered N at the previous prompt, decide if you want to proceed with the installation.
If you already installed one or more TCPware component, select the ones you want to reinstall. |
Y or N
* Do you want
to reinstall component? Y if upgrading TCPware, N in most other cases |
|
3 |
Decide if you want to have online HELP available.
The DCL HELP library is in the SYS$HELP:HELPLIB.HLB file |
Return or Y or N |
|
4 |
If you are installing one or more TCPware components for the first time, select the ones you want to install.
VMSINSTAL displays the selections you made. |
Return or Y or N |
|
5 |
Confirm your selections. |
Return or Y or N
If you answer YES, OpenVMS takes a short time to complete the installation. If you enter NO, go back to step 3 to make corrections. |
VMSINSTAL restores the product save sets, installs each component, and confirms completion of the procedure. If you have an existing TCPWARE:SERVICES. file, the installation includes any services listed in it in the new file the installation creates.
For a complete sample installation, see Appendix A, Sample Installation.
Installing the TCPware components:
* Is it OK for the system to be REBOOTed after this installation? N
You may choose to proceed with this installation. However, if you do so, you will NOT be able to start TCPware until AFTER you have rebooted the system.
* Do you want to proceed with this installation? Y
TCPware for OpenVMS includes online HELP. You may add this HELP to the DCL HELP library (SYS$HELP:HELPLIB.HLB). The HELP text will display under the heading "TCPware".
* Do you want to add online HELP to the DCL HELP library [YES]?Return
Select the products to install by answering YES or NO to the following prompts. Install only those products for which you have a Product authorization Key. Installing products for which you do not have a Product Authorization Key does you no good (a Product Authorization Key is required which only allows you to use licensed products).
*
Do you want to install FTP-OpenVMS [YES]? Return
* Do you want to install Service
Accounting[YES]? Return
* Do you want to install NFS-OpenVMS
Client [YES]? Return
* Do you want to install NFS-OpenVMS
Server [YES]? Return
* Do you want to install SMTP-OpenVMS
[YES]? Return
* Do you want to install TELNET-OpenVMS
[YES]? Return
* Do you want to install SSH-OpenVMS
[YES]? Return
* Do you want to install Kerberos Services
[YES]? Return
* Do you want to install ONC RPC Services
[NO]? Return
The following products will be installed:
TCP-OpenVMS
FTP-OpenVMS (TCP/IP Services)
Service Accounting (TCP/IP Services)
NFS-OpenVMS Client (TCP/IP Services)
NFS-OpenVMS Server (TCP/IP Services)
SMTP-OpenVMS (TCP/IP Services)
TELNET-OpenVMS (TCP/IP Services)
SSH-OpenVMS (TCP/IP Services)
Kerberos Services (TCP/IP Services)
*
Is this correct [YES]? Return
This concludes the question and answer portion of the installation.
Your system will now be updated to include TCPware for OpenVMS. This will take a short while.
%VMSINSTAL-I-RESTORE, Restoring product save set B .....
Because TCPware creates files in some of the system directories like SYS$LIBRARY and SYS$SYSTEM, you need to install TCPware on each system disk. Because nodes of the same architecture can share the TCPware common files, be sure to specify a common directory when the installation instructions ask where to install the TCPware common files.
In a mixed platform cluster of VAX, Alpha and Itanium systems, the cluster needs to be set up to share the data files. You can do this by having separate TCPWARE_LOGICALS.COM files for the VAX, Alpha and Itanium nodes.
On the VAX nodes, the TCPWARE_LOGICALS.COM file looks something like this:
$
DEFINE/SYSTEM/NOLOG/EXEC TCPWARE_COMMON SYS$COMMON:, -
ALPHA$DKA300:[VMS$COMMON.]
$ DEFINE/SYSTEM/NOLOG/EXEC TCPWARE_SPECIFIC SYS$SPECIFIC:
$ DEFINE/SYSTEM/NOLOG/EXEC TCPWARE_ROOT SYS$SYSROOT:, -
ALPHA$DKA300:[VMS$COMMON.]
$ DEFINE/SYSTEM/NOLOG/EXEC TCPWARE "TCPWARE_ROOT:[TCPWARE]"
$ DEFINE/SYSTEM/NOLOG TCPWARE_INCLUDE -
"TCPWARE_ROOT:[TCPWARE.INCLUDE]"
On the Alpha nodes, the TCPWARE_LOGICALS.COM file looks something like this (being the “primary”):
$
DEFINE/SYSTEM/NOLOG/EXEC TCPWARE_COMMON SYS$COMMON:
$ DEFINE/SYSTEM/NOLOG/EXEC TCPWARE_SPECIFIC SYS$SPECIFIC:
$ DEFINE/SYSTEM/NOLOG/EXEC TCPWARE_ROOT SYS$SYSROOT:
$ DEFINE/SYSTEM/NOLOG/EXEC TCPWARE "TCPWARE_ROOT:[TCPWARE]"
$ DEFINE/SYSTEM/NOLOG TCPWARE_INCLUDE -
“TCPWARE_ROOT:[TCPWARE.INCLUDE]"
On the Itanium nodes, the TCPWARE_LOGICALS.COM file looks something like:
$
DEFINE/SYSTEM/NOLOG/EXEC TCPWARE_COMMON SYS$COMMON:, -
ALPHA$DKA300:[VMS$COMMON.]
$ DEFINE/SYSTEM/NOLOG/EXEC TCPWARE_SPECIFIC SYS$SPECIFIC:
$ DEFINE/SYSTEM/NOLOG/EXEC TCPWARE_ROOT SYS$SYSROOT:, -
ALPHA$DKA300:[VMS$COMMON.]
$ DEFINE/SYSTEM/NOLOG/EXEC TCPWARE "TCPWARE_ROOT:[TCPWARE]"
$ DEFINE/SYSTEM/NOLOG TCPWARE_INCLUDE -
"TCPWARE_ROOT:[TCPWARE.INCLUDE]"
The common files reside on ALPHA$DKA300:[VMS$COMMON.TCPWARE...], the Alpha system disk.
Keep in mind:
· Before you install a new version of TCPware, "restore" the logicals to their original values. Upon startup, TCPware checks for the logicals TCP, UDP, IP, INET, RMT, RCD, BG, and QX. If any of these logicals have been previously defined on your system, the following warning is generated:
%TCPWARE-W-BADLOGICAL
· After installing TCPware on VAX and Itanium systems, make sure to delete (or rename) the SYS$SYSROOT:[TCPWARE...]*_CONTROL.COM files. Otherwise, TCPware fails to start because it finds two sets of the control files and tries to execute each set, which can cause problems.
· After installing on VAX and Itanium systems, delete any of the data files TCPware creates during installation and which it can no longer locate because of the new logical definitions.
· For the VAX and Itanium systems, restore the TCPWARE_LOGICALS.COM file to that shown above.
You can install other products at the same time you install TCPware.
Install and start TCPware before you install INGRES/Net.
After TCPware installation, configuration, and startup, see Chapter 6, Starting and Testing TCPware, the Installing and Configuring INGRES/Net section.
Install and operate TCPware before installing SQL*Net.
After TCPware installation, configuration, and startup, see Chapter 6, Starting and Testing TCPware, the Installing and Configuring Oracle's SQL*Net section.
If you are reinstalling or upgrading TCPware or the OpenVMS operating system, there are some additional tasks to perform. Perform these tasks after you get confirmation of a successful installation:
1. Unload the distribution media from the device.
2. Reboot the system.
|
Caution! Do not use the STOP PROCESS/ID command to stop TCPware or any of its components. Use the SHUTNET command as described in Chapter 6.
|
|
Note: Be aware that TCPware provides new versions of the existing TCPWARE:NETWORKS., TCPWARE:SERVICES., and TCPWARE:PROTOCOLS. files. Any customizations that you made to these files should be merged with the new versions.
|