Initialize or configure any of the following products as necessary, following the instructions in the sections indicated:
The Common Data Security Architecture (CDSA) software is installed, configured, and initialized automatically with the operating system installation or upgrade. CDSA is required for Secure Delivery purposes and other security features; otherwise, use of CDSA is not required.
Note that if you installed a new CDSA kit without upgrading the base operating system, you must enter the following command to initialize CDSA prior to its first use. Enter the command from an account that has both SYSPRV and CMKRNL privileges (for example, the SYSTEM account).
$@SYS$STARTUP:CDSA$UPGRADE
The following is an example of the output you might see:
Module uninstalled successfully. . . . CDSA-I-Init, CDSA has previously been initialized on this system. CDSA-I-Init, Re-initializing CDSA. CDSA-I-Init, Initializing CDSA MDS installed successfully. . . . CDSA-I-Init, CDSA Initialization complete CDSA-I-Init, Initializing Secure Delivery Install completed successfully. Install completed successfully. Module installed successfully. Module installed successfully. CDSA-I-Init, Secure Delivery Initialization complete
For more information about CDSA, see HP Open Source Security for OpenVMS, Volume 1: Common Data Security Architecture.
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 an Availability Manager Data Analyzer kit on an OpenVMS or Windows-based node in the local LAN. The kit is included in the OpenVMS upgrade media, or you can obtain it from the following website:
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, see the section "Performing Postinstallation Tasks" in the Availability Manager installation instructions for OpenVMS (HP Availability Manager Installation Instructions). This and other Availability Manager documents are available at the website mentioned previously.
The Kerberos for OpenVMS software, which is based on MIT Kerberos, is installed automatically 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).
Run the following command procedure to configure the Kerberos clients and servers:
$@SYS$STARTUP:KRB$CONFIGURE.COM
Add the following line to your SYLOGIN command procedure or to the LOGIN.COM of each user who will use Kerberos:
$@SYS$MANAGER:KRB$SYMBOLS
Edit SYS$MANAGER:SYSTARTUP_VMS.COM to remove the exclamation point from the KRB$STARTUP.COM line so that it appears as shown in the following example. (Note that SYSTARTUP_VMS.COM has HP TCP/IP Services for OpenVMS starting before Kerberos. This is required.)
$@SYS$STARTUP:KRB$STARTUP.COM
For additional setup and configuration information, see 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.4 kit.
The HP SSL for OpenVMS software is installed automatically with the operating system; however, use of SSL is not required. If you do not plan to use SSL or any products that depend on it, skip to the next section.
The SSL$STARTUP.COM command procedure has been added to VMS$LPBEGIN-050 to enable SSL to start automatically.
Add the following line to SYS$MANAGER:SYSHUTDOWN.COM:
$ @SYS$STARTUP:SSL$SHUTDOWN.COMIf you are upgrading and have an earlier version of SSL installed, copy your SSL$STARTUP.TEMPLATE file (located in SYS$STARTUP) to SSL$STARTUP.COM in the SYS$STARTUP directory.
Several other post-installation and post-upgrade
tasks are required, as described in the SSL release notes, available
in SYS$HELP:SSLnnn.RELEASE_NOTES, where nnn is
the version of the SSL software, such as 013.
For more information about SSL, see HP Open Source Security for OpenVMS, Volume 2: HP SSL for OpenVMS.
NOTE: Do not attempt to explicitly remove SSL from your system. The PRODUCT REMOVE command is not supported for SSL although there appears to be an option to remove SSL. SSL is installed with the operating system and is tightly bound with it. Attempts to remove it might not work as expected and can create undesirable side effects. An attempt to remove it results in a message similar to the following: %PCSI-E-HRDREF, product HP I64VMS SSL V1.4 is referenced by HP I64VMS OPENVMS V8.4 The two products listed above are tightly bound by a software dependency. If you override the recommendation to terminate the operation, the referenced product will be removed, but the referencing product will have an unsatisfied software dependency and may no longer function correctly. Please review the referencing product’s documentation on requirements. Answer YES to the following question to terminate the PRODUCT command. However, if you are sure you want to remove the referenced product then answer NO to continue the operation. Terminating is strongly recommended. Do you want to terminate? [YES] | |
WBEM Services for OpenVMS is installed automatically with OpenVMS installation. As with other similar products, an OpenVMS upgrade does not automatically include WBEM Services for OpenVMS if it is not already installed on the target system disk. In this case, you must install the product separately using the PCSI PRODUCT INSTALL command. If you do not plan to use WBEM Services for OpenVMS or any products that depend on it, simply do not configure the software; if you have already configured the software, you can choose not to start it.
You must configure WBEM Services for OpenVMS to obtain the services provided by HP SIM (Version 5.2 or later) and products such as Instant Capacity and gWLM. To provide services over the network, both TCP/IP Services for OpenVMS and SSL (for security purposes) are required and must be configured and running. (For information about configuring TCP/IP Services for OpenVMS, see Section .
To configure WBEM Services for OpenVMS on a system on which WBEM Services for OpenVMS has never been installed and configured, follow the steps described in “Section .” If you are configuring the product on a system on which it has been configured previously, see Section .
For more information about HP WBEM products, see the following website:
To configure WBEM Services for OpenVMS on a system for the first time, follow these steps:
$ RUN SYS$SYSROOT:[WBEM_SERVICES]WBEM_SERVICES$CONFIGThis command invokes the utility that configures and initializes the environment for WBEM Services for OpenVMS.
After displaying the initial configuration utility banner, the utility informs you where it will store the configuration files and repository and asks if you want to change the location.
The configuration files and repository will be placed in the following location:
SYS$SPECIFIC:[WBEM_Services].
Do you want to change this location (Yes/No) [No]?:NOTE: The repository, a compiled version of the Common Information Model (CIM) class schema, requires an ODS-5 formatted disk (the repository uses UNIX-style file names, which are not supported on ODS-2 formatted disks). If the default location is on an ODS-2 formatted disk, you must change the location to an ODS-5 disk. | |
When you accept the default location, the utility informs you that all configuration questions have been answered and asks whether you want to continue, as shown in the following example. If you choose to continue, the utility creates the CIMServer repository tree in the location indicated earlier. The CIMServer is the WBEM Services for OpenVMS process that runs on the system to support certain applications. It also creates the following command files:
| SYS$STARTUP:WBEM_Services$Startup.com |
| SYS$STARTUP:WBEM_Services$Shutdown.com |
| SYS$SYSROOT:[WBEM_SERVICES]WBEM_Services$Define_Commands.com |
The SYS$STARTUP:WBEM_Services$Startup.com file defines system logicals for the WBEM Services for OpenVMS environment.
All configuration questions have been answered.
Do you want to continue (Yes/No) [YES]?:
%WBEMCONFIG-I-CREREPBEGIN, Create Repository Begins...
%WBEMCONFIG-I-CREREPCOMPLETE, Create Repository Complete.
This utility creates:
SYS$STARTUP:WBEM_Services$Startup.com
which should be added to SYS$STARTUP:SYSTARTUP_VMS.COM.
This utility creates:
SYS$STARTUP:WBEM_Services$Shutdown.com
which should be added to SYS$STARTUP:SYSHUTDWN.COM.
This utility creates:
SYS$SYSROOT:[wbem_services]WBEM_Services$Define_Commands.com
which users who use this product can add to their login.com.The utility asks whether to start the CIMServer:
Do you want to start the CIMServer now (Yes/No) [Yes]?:CIMServer must be running so that your system can use such applications as Instant Capacity and gWLM. You can start CIMServer now, or you can perform other postinstallation or postupgrade tasks first and then start CIMServer. If you choose to start CIMServer now, the utility displays the progress and operating system information, as in the following example:
%RUN-S-PROC_ID, identification of created process is 21A00599
%WBEMCIM-I-STARTUPWAIT, Waiting for CIMServer to start... 120 seconds remaining.
%WBEMCIM-S-CSSTARTED, CIMServer successfully started.
OperatingSystem Information
Host: boston.hp.com
Name: OpenVMS
Version: V8.4
UserLicense: Unlimited user license
Number of Users: 1 users
Number of Processes: 29 processes
OSCapability: 64 bit
LastBootTime: Jul 31, 2009 10:52:55 (-0400)
LocalDateTime: Aug 3, 2009 10:14:58 (-0400)
SystemUpTime: 256923 seconds = 2 days, 23 hrs, 22 mins, 3 secs
%RUN-S-PROC_ID, identification of created process is 21A00599To ensure that CIMServer starts automatically at each reboot, add the following line to SYS$MANAGER:SYSTARTUP_VMS.COM after the line that starts TCP/IP:
$
@SYS$STARTUP:WBEM_Services$Startup.com
To have CIMServer shut down automatically with the operating system, add the following line to the SYS$MANAGER:SYSSTARTUP:SYSHUTDWN.COM file:
$ @SYS$STARTUP:WBEM_Services$Shutdown.com
All users who use this product should also add the following line to their LOGIN.COM file:
In an OpenVMS Cluster, each member that runs WBEM Services for OpenVMS needs its own repository. Therefore, you must perform the WBEM Services for OpenVMS configuration procedure on each of those cluster members.
To configure WBEM Services for OpenVMS on a system where it has been configured previously, follow these steps:
$ RUN SYS$SYSROOT:[WBEM_SERVICES]WBEM_SERVICES$CONFIGThis command starts the utility that configures and initializes the environment for WBEM Services for OpenVMS.
If the WBEM Services for OpenVMS product (Version 2.0) available with OpenVMS Integrity servers Version 8.3 is already configured on your system, the following error message and the recommended remedial actions appear:
%WBEMCONFIG-E-SYSCOMMONLOGICAL, WBEM_VAR can no longer be defined to point to
a location in SYS$COMMON. The repository files in WBEM_VAR should not be shared
with other cluster members.
Follow these manual steps to move the repository out of the SYS$COMMON
area and complete the post installation configuration tasks:
o Delete the sys$common:[WBEM_Services.var...] directory tree.
o Deassign the WBEM_VAR system logical.
o Run this procedure again.Perform the recommended steps, as in the following example:
$DELETE SYS$COMMON:[WBEM_SERVICES.VAR...]*.*;*$DELETE SYS$COMMON:[WBEM_SERVICES]VAR.DIR;*$DEASSIGN/SYS WBEM_VAR$RUN SYS$SYSROOT:[WBEM_SERVICES]WBEM_SERVICES$CONFIG
After you start the configuration procedure, go to Section and follow the steps described there, starting with step 2.
After displaying the initial configuration utility banner, the utility informs you where it will store the configuration files and repository and asks if you want to change the location.
The configuration files and repository will be placed in the following location:
SYS$SPECIFIC:[WBEM_Services].
Do you want to change this location (Yes/No) [No]?:The repository is a compiled version of the CIM class schema. This example assumes you accept the current location.
As shown in the following example, the utility informs you that all configuration questions have been answered and asks whether you want to continue.
If the utility determines that the repository schema has not changed, the utility informs you and continues. The utility does not need to upgrade the repository.
If the utility determines that the current repository needs upgrading, or if the utility does not find a repository (perhaps WBEM Services for OpenVMS had been installed but not configured), the utility displays a message informing you that the repository will be upgraded or created and that this will take 10 to 15 minutes depending on your processor and disk I/O speed. In the following example, the utility needs to create the repository tree.
The utility also creates the SYS$STARTUP:WBEM_Services$Startup.com, SYS$STARTUP:WBEM_Services$Shutdown.com, and SYS$SYSROOT:[WBEM_SERVICES]WBEM_Services$Define_Commands.com command files. The SYS$STARTUP:WBEM_Services$Startup.com file defines system logicals for the WBEM Services for OpenVMS environment.
All configuration questions have been answered.
Do you want to continue (Yes/No) [Yes]?:
%WBEMCONFIG-I-CREREPBEGIN, Create Repository Begins...
%WBEMCONFIG-I-CREREPCOMPLETE, Create Repository Complete.
This utility creates:
SYS$STARTUP:WBEM_Services$Startup.com
which should be added to SYS$STARTUP:SYSTARTUP_VMS.COM.
This utility creates:
SYS$STARTUP:WBEM_Services$Shutdown.com
which should be added to SYS$STARTUP:SYSHUTDWN.COM.
This utility creates:
SYS$SYSROOT:[wbem_services]WBEM_Services$Define_Commands.com
which users who use this product can add to their login.com.The utility now asks you whether to start the CIMServer:
Do you want to start the CIMServer now (Y/N) {Y}?:CIMServer must be running so that your system can use such applications as Instant Capacity and gWLM. You can start CIMServer now, or you can perform other postinstallation or postupgrade tasks first and then start CIMServer. If you choose to start CIMServer now, the utility displays the progress and operating system information, as in the following example:
%RUN-S-PROC_ID, identification of created process is 21A00599
%WBEMCIM-I-STARTUPWAIT, Waiting for CIMServer to start... 120 seconds remaining.
%WBEMCIM-S-CSSTARTED, CIMServer successfully started.
OperatingSystem Information
Host: boston.hp.com
Name: OpenVMS
Version: V8.4
UserLicense: Unlimited user license
Number of Users: 1 users
Number of Processes: 29 processes
OSCapability: 64 bit
LastBootTime: Jul 31, 2009 10:52:55 (-0400)
LocalDateTime: Aug 3, 2009 10:14:58 (-0400)
SystemUpTime: 256923 seconds = 2 days, 23 hrs, 22 mins, 3 secs
%RUN-S-PROC_ID, identification of created process is 21A00599To ensure that CIMServer starts automatically at each reboot, add the following line to the SYS$MANAGER:SYSTARTUP_VMS.COM file:
$ @SYS$STARTUP:WBEM_Services$Startup.com
To have CIMServer shut down automatically with the operating system, add the following line to the SYS$MANAGER:SYSSTARTUP:SYSHUTDWN.COM file:
$ @SYS$STARTUP:WBEM_Services$Shutdown.com
All users who use this product should also add the following line to their LOGIN.COM file:
In an OpenVMS Cluster, each member that will run WBEM Services for OpenVMS needs its own repository. Therefore, you must perform the WBEM Services for OpenVMS configuration procedure on each of those cluster members.
WBEM Providers for OpenVMS is installed automatically with OpenVMS installation. As with other similar products, an OpenVMS upgrade does not include WBEM Providers for OpenVMS if it is not currently installed on the target system disk. In this case, you must install the product separately using the PCSI PRODUCT INSTALL command.
You must configure WBEM Providers for OpenVMS to obtain the services provided by HP SIM . WBEM Providers for OpenVMS requires WBEM Services for OpenVMS.
NOTE: If you are using WBEM Providers for OpenVMS, and have performed an OpenVMS upgrade, you must re-configure WBEM Providers by following the steps below. | |
To configure WBEM Providers for OpenVMS, follow these steps:
If not done so already, define the WBEM Services logicals by entering the following command:
$@SYS$COMMON:[WBEM_SERVICES]WBEM_Services$Define_Commands.com
Ensure that the CIM Server is running and verify the list of providers installed by entering the following command:
$CIMPROVIDER -L -S
This displays output similar to the following:
MODULE STATUS
OperatingSystemModule OK
ComputerSystemModule OK
ProcessModule OK
IPProviderModule OKTo configure the WBEM Providers for OpenVMS software, enter the following command:
$@SYS$COMMON:[WBEMPROVIDERS]WBEMPROVIDERS$CONFIGURE.COM
You are prompted to enter the primary owner name and contact information.
%WBEMPROVIDERS-I-STARTING, Info:Starting WBEMPROVIDERS Configuration.
Enter Primary Owner name of the system: system
Enter Primary owner contact information: 25166235
%WBEMPROVIDERS-I-CONTINUECONFIG, Info:configuration of EventIndicationConsumerModule...
%WBEMPROVIDERS-I-CONTINUECONFIG, Info:configuration of EMSWrapperProviderModule...
%WBEMPROVIDERS-I-CONTINUECONFIG, Info:configuration of HPVMSLANIndicationProviderModule...
%WBEMPROVIDERS-I-CONTINUECONFIG, Info:configuration of StateChangeIndicationProviderModule...
%WBEMPROVIDERS-I-CONTINUECONFIG, Info:configuration of ChassisProviderModule...
%WBEMPROVIDERS-I-CONTINUECONFIG, Info:configuration of cpuprovidermodule...
%WBEMPROVIDERS-I-CONTINUECONFIG, Info:configuration of MemoryModule...
%WBEMPROVIDERS-I-CONTINUECONFIG, Info:configuration of FirmwareRevisionProviderModule...
%WBEMPROVIDERS-I-CONTINUECONFIG, Info:configuration of MPProviderModule...
%WBEMPROVIDERS-I-CONTINUECONFIG, Info:configuration of EnclosureProviderModule...
%WBEMPROVIDERS-I-CONTINUECONFIG, Info:configuration of HPHealthStateProviderModule...
%WBEMPROVIDERS-I-CONTINUECONFIG, Info:configuration of HPVMSLANProviderModule...
%WBEMPROVIDERS-I-CONTINUECONFIG, Info:configuration of HPVMSLANCSProviderModule...
%WBEMPROVIDERS-I-CONTINUECONFIG, Info:configuration of CSChassisProviderModule...
%WBEMPROVIDERS-I-CONTINUECONFIG, Info:configuration of HPVMProviderModule...
%WBEMPROVIDERS-I-CONTINUECONFIG, Info:configuration of HP_UtilizationProviderModule...
%RUN-S-PROC_ID, identification of created process is 00006939
%WBEMPROVIDERS-I-WAIT, Info:Waiting for 1 Minute for the Inventory to Initialize
%RUN-S-PROC_ID, identification of created process is 0000693F
%RUN-S-PROC_ID, identification of created process is 00006940
%WBEMPROVIDERS-I-PROVCONFIG, Info:Completed configuration of WBEMPROVIDERS.The configuration process takes a few minutes to complete and displays output similar to the following:
Starting WBEMPROVIDERS Configuration. This would take around
5 minutes
Starting WBEMPROVIDERS. This would take around 2 minutes
Inventory is not ready! Waiting for 2 Minutes
%RUN-S-PROC_ID, identification of created process is
23800EC2
WBEMPROVIDERS configuration is completed.This command procedure registers the WBEM Providers software with the CIM Server and copies the node specific files to SYS$SPECIFIC:[WBEMPROVIDERS].
Verify the list of providers installed and their status by entering the following command:
$CIMPROVIDER -L -S
This displays output similar to the following:
MODULE STATUS
OperatingSystemModule OK
ComputerSystemModule OK
ProcessModule OK
IPProviderModule OK
EventIndicationConsumerModule OK
EMSWrapperProviderModule OK
HPVMSLANIndicationProviderModule OK
StateChangeIndicationProviderModule OK
ChassisProviderModule OK
cpuprovidermodule OK
MemoryModule OK
FirmwareRevisionProviderModule OK
MPProviderModule OK
EnclosureProviderModule OK
HPHealthStateProviderModule OK
HPVMSLANProviderModule OK
HPVMSLANCSProviderModule OK
CSChassisProviderModule OK
HPVMProviderModule OK
HP_UtilizationProviderModule OK
To configure WBEM Providers for OpenVMS, follow the directions provided in the HP WBEM Providers Installation and Administrator's Guide, available in the SYS$COMMON:[WBEMPROVIDERS.DOCUMENTATION] directory on your OpenVMS system disk. For the latest information, see the following website and select the appropriate link:
http://h71000.www7.hp.com/openvms/system_management.html
Instant Capacity (iCAP) software is supported on cell-based Integrity servers. For support of this software, as well as Temporary Instant Capacity (TiCAP) , you must configure WBEM Services for OpenVMS.
If you choose to use Instant Capacity, Temporary Instant Capacity, or Global Instant Capacity, configure the software by entering the following command:
$ @SYS$MANAGER:ICAP$CONFIG.COMFor more information about configuring and using Instant Capacity, see the HP Instant Capacity User’s Guide on the following website:
http://docs.hp.com/en/netsys.html#Utility%20Pricing%20Solutions
To enable HP SIM support of OpenVMS on your system, follow the directions provided in the HP WBEM Providers Installation and Adminstrator's Guide, available in the SYS$COMMON:[WBEMPROVIDERS.DOCUMENTATION] directory on your OpenVMS system disk. For the latest information, see the documentation provided at the following website:
http://h18002.www1.hp.com/products/servers/management/hpsim/download.html
The Performance Data Collector for HP OpenVMS (TDC) collects and manages configuration and performance data for analysis by other applications. TDC_RT Version 2.3-20 is a run-time only (base) variant of the TDC software that is installed automatically 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.
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 enables 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 the following:
| 6000 pagelets on Alpha systems |
| 7000 pagelets on Integrity server systems |
TDC_RT provides a startup file that should be launched 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.
Note the following about prior releases of TDC software.
TDC Version 1.n
For
users of some third-party system-management applications, TDC Version
1.n was distributed by web download. Applications
developed using TDC Version 1.n will not
work with TDC Version 2.2 software until they are rebuilt using the
TDC Version 2.2 Software Developer’s Kit (SDK). You can obtain this
SDK kit from the following website:
http://www.hp.com/products/openvms/tdc/
Data files created using TDC Version 1.n cannot
be read by TDC_RT Version 2.2. Data files created using TDC_RT Version
2.2 cannot be read using TDC Version 1.n.
When TDC_RT Version 2.1 or any newer version of TDC is installed,
files associated with TDC Version 1.n are
not removed. In any case, TDC_RT Version 2.1 (or later) and TDC Version
1.n can safely coexist on a system. You
can remove the older TDC files by uninstalling TDC (use the DCL command
PRODUCT REMOVE).
TDC Version 2.2 on an earlier version of OpenVMS
If you upgrade to OpenVMS Version 8.4 from an earlier version of OpenVMS on which TDC Version 2.2 was installed, files shared by TDC_RT Version 2.2 and TDC Version 2.2 are updated; these files are the documentation and support files listed in SYS$COMMON:[TDC]README.TXT as common to all kit variants. Unless the TDC and TDC_RT kits share the same baselevel number (for example, 102), image files installed with TDC Version 2.2 are retained in their installed locations. Most likely, the downloaded TDC Version 2.2 software will be more recent (higher baselevel number) than the TDC_RT Version 2.2 software installed with OpenVMS Version 8.4. The TDC Version 2.2 SDK (if installed) and any additional documentation files installed with TDC Version 2.2 are retained.
Running SYS$STARTUP:TDC$STARTUP.COM causes the most recent TDC/TDC_RT Version 2.2 images to be used at runtime, regardless of whether they were installed with TDC Version 2.2 or with TDC_RT Version 2.2.
You can remove TDC Version 2.2 without affecting the integrity of the TDC_RT Version 2.2 installation if their baselevel numbers differ.
As of OpenVMS Version 8.2, TDC and TDC_RT use the same naming scheme for image files. A build number is tagged to the image file names. For example, if the version of TDC_RT that ships with your operating system is Version 2.2-60 (where 60 is the build number), then the files that are installed will have names such as TDC$APISHR$I_V840-0060.EXE, where $I denotes Integrity servers (or TDC$APISHR$A_V840-0060.EXE, where $A denotes Alpha), V840 denotes the version of OpenVMS (8.4), and 0060 is the build number. The SYS$STARTUP:TDC$STARTUP.COM startup file, which is also identical for both TDC and TDC_RT, uses this build number to determine which image files to use. When a subsequent installation is performed with software that has higher build numbers, the TDC$STARTUP.COM startup file uses the image files with the highest build number appropriate for the current platform.
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, enter the TDC command:
$ TDCFor more information about running the application, see the file SYS$COMMON:[TDC]TDC_README.TXT. Release notes are located in the file SYS$COMMON:[TDC]TDC_RELEASE_NOTES.TXT. See both of these files before running the collector application.
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.2) from the following website:
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.
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, see Appendix 8.
The latest version of the OpenVMS Debugger runs on OpenVMS Alpha and Integrity server systems. The debug server runs on OpenVMS, while a debug client, which is the user interface to the server, runs on OpenVMS and on Microsoft Windows 95, Windows 98, Windows NT, Windows 2000, Windows XP, and Windows Vista. There is no special installation procedure for the components that run on OpenVMS. The installation guide and kit for the OpenVMS debugger client is located on the Layered Products CD that comes with the OpenVMS binary CD set. The directory on the CD is DEBUG_CLIENTS011. The KIT.DIR subdirectory contains the following files:
For installation instructions, see the INSTALLATION_INFO.PS or INSTALLATION_INFO.TXT file in the DOCUMENTATION subdirectory.