Installation and Upgrade Guide

7.8.10.3 Compatibility with Prior Releases
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.3-1H1 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.3-1H1. 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_V830-0060.EXE, where $I denotes I64),
V830 denotes the version of OpenVMS (8.3), 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.
7.8.10.4 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$DCL
Each 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:
$ TDC
134 After Installing or Upgrading the OpenVMS Operating System