|
HP OpenVMS Version 8.2-1 for Integrity Servers... |
After Installing or Upgrading the OpenVMS Operating... |
|
|
| |
Initializing or Configuring Installed Optional Components
Initializing CDSA
(Optional)
The Common Data Security Architecture (CDSA) software is installed
automatically with the operating system. However, use of CDSA is
not required. If you do not plan to use CDSA or any products that
depend on it, skip to the next section.
If you do plan to use CDSA, you must invoke the following command to perform a one-time configuration procedure. Invoke the command from an account that has both SYSPRV and CMKRNL privileges (for example, the SYSTEM account).
$@SYS$STARTUP:CDSA$INITIALIZE
The following is an example of the output you might:
Initializing CDSA *** Installing MDS MDS installed successfully. *** Installing CSSM Module installed successfully. *** Installing FFDL Module installed successfully. *** Installing 509CL Module installed successfully. *** Installing 509TP Module installed successfully. *** Installing EAYCSP Module installed successfully. *** Installing MAF_BSAFE Module installed successfully. *** Installing INSPKICLTP300 Module installed successfully. *** Installing INTELAC Module installed successfully. CDSA Initialization complete Initializing Secure Delivery *** Installing CDSA$VALIDATE_LIBSHR Install completed successfully. Installing CDSA$REVOKE_LIBSHR Install completed successfully. *** Installing VALIDATE_SHR Module installed successfully. *** Installing VALIDATE_EMM_SHR Module installed successfully. Secure Delivery Initialization complete
 | Do not attempt to remove CDSA from your system. The
PRODUCT REMOVE command is not supported for CDSA even though there
appears to be an option to remove CDSA. CDSA is installed with
the operating system and is tightly bound with it. Attempts to
remove it do not work cleanly and could create undesirable side
effects. An attempt to remove it results in a message similar to
the following: %PCSI-E-HRDREF, product HP I64VMS CDSA V2.1 is referenced by HP I64VMS OPENVMS V8.2-1 -PCSI-E-HRDRF1, the two products are tightly bound by this software dependency -PCSI-E-HRDF2, if you override the recommendation to terminate the operation, -PCSI-E-HRDF3, the referenced product will be removed, but the referencing -PCSI-E-HRDF4, product may no longer function correctly; please review -PCSI-E-HRDF5, dependency requirements for the referencing product Terminating is strongly recommended. Do you want to terminate? [YES] |
Configuring
the Availability Manager Base Software (Optional)
The Availability Manager base kit is installed automatically
with the operating system. However, use of Availability Manager
is not required. If you do not plan to use Availability Manager
or any products that depend on it, skip to the next section.
The files in the Availability Manager base kit make up what is called the Data Collector. The Data Collector is used to collect data for the Availability Manager and DECamds products. To display the data, you need to install either an Availability Manager or a DECamds kit on a node in the local LAN. These kits are included in the OpenVMS upgrade media, or you can obtain them from the following Web site:
http://www.hp.com/products/openvms/availabilitymanager
The base kit files are the same files that have been provided with the OpenVMS installation kit since Version 7.2. The only change for OpenVMS Version 8.2 and higher is that these files are now installed as a required product rather than being an optional software product in the operating system kit. Procedures for configuring and using these files remain unchanged.
For more information about how to configure and use the files in the Availability Manager base kit, refer to the section "Performing Postinstallation Tasks" in the Availability Manager installation instructions for OpenVMS (Installing Availability Manager on OpenVMS Alpha Systems and Running DECamds and the Availability Manager Concurrently ). This and other Availability Manager documents, as well as DECamds documents, are available at the following Web site:
http://www.hp.com/products/openvms/availabilitymanager
| Although the Availability Manager base software can
be removed from the system with the PRODUCT REMOVE command, HP recommends
that you do not attempt to remove the software. The Availability
Manager base software is installed with the operating system and
is tightly bound with it. Attempts to remove it do not work cleanly
and could create undesirable side effects. An attempt to remove
it results in a message similar to the following:%PCSI-E-HRDREF, product HP I64VMS Availability Manager V8.2-1 is referenced by HP I64VMS OPENVMS V8.2-1 -PCSI-E-HRDRF1, the two products are tightly bound by this software dependency -PCSI-E-HRDF2, if you override the recommendation to terminate the operation, -PCSI-E-HRDF3, the referenced product will be removed, but the referencing -PCSI-E-HRDF4, product may no longer function correctly; please review -PCSI-E-HRDF5, dependency requirements for the referencing product Terminating is strongly recommended. Do you want to terminate? [YES] |
Configuring Kerberos
(Optional)
The Kerberos for OpenVMS software, which is based on MIT Kerberos,
is automatically installed with the operating system. However,
use of Kerberos is not required. If you do not plan to use Kerberos
or any products that depend on Kerberos, skip to the next section.
To configure Kerberos, perform the following steps from a privileged OpenVMS user account (for example, SYSTEM).
$@SYS$STARTUP:KRB$CONFIGURE.COM
$@SYS$MANAGER:KRB$SYMBOLS
$@SYS$STARTUP:KRB$STARTUP.COM
For additional setup and configuration information, refer to the HP Open Source Security for OpenVMS, Volume 3: Kerberos manual. This document contains links to the MIT Kerberos documentation and is available from the OpenVMS Version 8.2-1 kit.
| Do not attempt to remove Kerberos from your system.
The PRODUCT REMOVE command is not supported for Kerberos even though
there appears to be an option to remove Kerberos. Kerberos is installed
with the operating system and is tightly bound with it. Attempts
to remove it do not work cleanly and could create undesirable side
effects. An attempt to remove it results in a message similar to
the following:%PCSI-E-HRDREF, product HP I64VMS Kerberos V2.1 is referenced by HP I64VMS OPENVMS V8.2-1 -PCSI-E-HRDRF1, the two products are tightly bound by this software dependency -PCSI-E-HRDF2, if you override the recommendation to terminate the operation, -PCSI-E-HRDF3, the referenced product will be removed, but the referencing -PCSI-E-HRDF4, product may no longer function correctly; please review -PCSI-E-HRDF5, dependency requirements for the referencing product Terminating is strongly recommended. Do you want to terminate? [YES] |
Initializing
and Running the Performance Data Collector Base Software (Optional)
The Performance Data Collector for HP OpenVMS (TDC) collects
and manages configuration and performance data for analysis by other
applications. TDC_RT Version 2.1 is a run-time only (base) variant
of the TDC software that is automatically installed with the OpenVMS
operating system for use on specific operating system platforms.
Use of the TDC_RT software is not required. If you do not plan to use TDC_RT or any products that depend on it, you can skip to the next section.
TDC_RT does not run automatically when the system starts, but any suitably privileged user can start the software manually. This section includes information about system parameters, privileges and quotas, startup, and installation in OpenVMS Clusters.
| Do not attempt to remove TDC_RT from your system. The
PRODUCT REMOVE command is not supported for TDC_RT even though there
appears to be an option to remove it. TDC_RT is installed with
the operating system and is tightly bound with it. HP or third-party
applications might require TDC_RT. Attempts to remove it do not
work cleanly and could create undesirable side effects. An attempt
to remove it results in a message similar to the following: %PCSI-E-HRDREF, product HP TDC_RT V2.1-nn is referenced by HP I64VMS OPENVMS V8.2-1 -PCSI-E-HRDRF1, the two products are tightly bound by this software dependency -PCSI-E-HRDF2, if you override the recommendation to terminate the operation, -PCSI-E-HRDF3, the referenced product will be removed, but the referencing -PCSI-E-HRDF4, product may no longer function correctly; please review -PCSI-E-HRDF5, dependency requirements for the referencing product Terminating is strongly recommended. Do you want to terminate? [YES] |
User Privileges
and Quotas
Users of TDC_RT require various privileges, depending on the
types of data to be collected. Online help is available when running
the collector application and specifies the privileges required
to collect each type of data. Enabling the following set of privileges
allows collection of all data items: CMKRNL, LOG_IO, NETMBX, PHY_IO,
SYSLCK, SYSPRV, WORLD.
Users of the product also require working set quotas (WSQUO) greater than 5000 pagelets.
Startup
File
TDC_RT provides a startup file that should be invoked during
system startup. The startup file defines several logical names
required for use of the product, but the startup file does not actually
start the data collector.
Add the following line to SYS$MANAGER:SYSTARTUP_VMS.COM:
$ @SYS$STARTUP:TDC$STARTUPTo directly run TDC$STARTUP.COM, SYSNAM privilege is required.
Running
TDC_RT
To run the collector application, users can enter the TDC
command at the DCL prompt. But first, because the TDC command is
not included in the system command table SYS$LIBRARY:DCLTABLES.EXE,
each user must add the command to their table by entering the following
command at the DCL prompt:
$ SET COMMAND SYS$COMMON:[TDC]TDC$DCLEach user can add this SET command to their LOGIN.COM file. However, because elevated privileges are required for most data collection operations, it might not be appropriate to add this command to SYS$MANAGER:SYLOGIN.COM.
To start the collector application, invoke the TDC command:
$ TDCFor more information about running the application, refer to the file SYS$COMMON:[TDC]TDC_RT_README.TXT. Release notes are located in the file SYS$COMMON:[TDC]TDC_RELEASE_NOTES.TXT. Refer to both of these files before running the collector application.
Installation
in OpenVMS Clusters
TDC_RT is installed in SYS$COMMON:[TDC] by default. Included
are only those files required to run the data collector with the
particular operating system version it was distributed with. Once
TDC_RT is installed and SYS$STARTUP:TDC$STARTUP.COM has been run
on each cluster member, then all cluster members in a single-version,
single-architecture OpenVMS Cluster should be able to run the software.
For mixed-version and mixed-architecture clusters, you should obtain and install a complete Performance Data Collector kit (TDC Version 2.1) from the following Web site:
http://www.hp.com/products/openvms/tdc
The complete kit provides an SDK and run-time environments for all supported OpenVMS configurations. It supports installation on a clusterwide basis in mixed-version and mixed-architecture OpenVMS Clusters.
Preparing to Use
OpenVMS Management Station (Optional)
If you installed the OpenVMS Management Station software on
your system (either by accepting all default values or by selecting
the component manually during the installation or upgrade procedure),
you must perform several tasks on your OpenVMS system and your PC
before you can use OpenVMS Management Station. These tasks include
the following:
For complete information about preparing your OpenVMS system and your PC to run the OpenVMS Management Station server and client software, refer to Preparing to Use OpenVMS Management Station.
|
|