TDC Version 2.2 is primarily a maintenance release of the Performance Data Collector for OpenVMS software. The principal goal in providing this version is to provide additional configuration and performance metrics required by other applications. Installing the Performance Data Collector for HP OpenVMS (TDC Version 2.2-107) 1. Compatibility issues A. TDC Version 1.0 TDC Version 1.0 was made available to users of some third-party system management applications. TDC Version 2.2 is incompatible with TDC Version 1.0, and software that uses TDC Version 1.0 has to be updated by the provider in order to be compatible with TDC Version 2.2. TDC Versions 1.0 and 2.2 can co-exist safely on a system, as they are installed in different locations and use different files. B. TDC Version 2.0 TDC Version 2.0 was made available via software download for Alpha systems running OpenVMS Version 7.3-2. Software built to use TDC Version 2.0 should be rebuilt using the Software Devlopers Kit provided with TDC Version 2.2. TDC Version 2.0 should be removed from the system prior to installing TDC Version 2.2. C. TDC_RT Version 2.1 TDC_RT Version 2.1 is distributed with, and installed by, OpenVMS Version 8.2 on both Alpha and Integrity server systems, and with OpenVMS Version 8.2-1 on Integrity server systems. It provides the runtime environment required to use TDC with the operating system version with which it is distributed. TDC Version 2.2 contains enhancements not available with TDC (or TDC_RT) Version 2.1. DO NOT ATTEMPT TO USE THIS TDC V2.2 BASELEVEL with software built to use TDC Version 2.1 unless you first confirm interoperability with the provider of that software. Installation of a TDC Version 2.2 kit does NOT automatically remove software installed by TDC_RT Version 2.1. The TDC startup file, SYS$STARTUP:TDC$STARTUP.COM, will, however, cause the most recent TDC runtime software to be used. Some HP-supplied and third-party software may have dependencies on the TDC_RT Version 2.1 software installed with OpenVMS Version 8.2 or 8.2-1. Therefore, HP does not recommend removing the TDC_RT software installed with the operating system. D. TDC_RT Version 2.2 TDC_RT Version 2.2 is distributed with, and installed by, OpenVMS Version 8.3 on both Alpha and Integrity server systems. It provides the runtime environment required to use TDC with the operating system version with which it is distributed. The runtime software installed by a TDC Version 2.2 kit is identical to the runtime software installed by TDC_RT Version 2.2, provided that the baselevels are identical (for example, TDC_RT Version 2.2-107 and TDC Version 2.2-107). In most cases, however, the runtime software provided by a TDC kit will include corrections and enhancements not available in the TDC_RT kit, and will have a later baselevel number (for example, TDC Version 2.2-108 contains updates not present in TDC_RT Version 2.2-107). Installation of a "TDC" kit does NOT automatically remove software installed by TDC_RT Version 2.2. The TDC startup file, SYS$STARTUP:TDC$STARTUP.COM, will, however, cause the most recent TDC runtime software to be used. Some HP-supplied and third-party software may have dependencies on the TDC_RT Version 2.2 software installed with OpenVMS Version 8.3 While any TDC Version 2.2 kit will meet the runtime requirements of those products, there remains a possibility that installation scripts for those products may check for an appropriate "TDC_RT" version, rather than checking for either "TDC_RT" or "TDC." For that reason, HP does not recommend removing the TDC_RT software installed with the operating system. If removal of the TDC_RT software installed with the operating system is a requirement, however, you can remove the TDC_RT software after installing TDC: $ PRODUCT REMOVE TDC_RT You will receive several warnings indicating that TDC_RT is a required part of the operating system. Those warnings can be ignored, provided that you intend to retain the TDC software that you have installed. E. TDC Version 2.1 TDC Version 2.1 has been available for download from the TDC web site. TDC Version 2.2 contains enhancements not available with TDC or TDC_RT Version 2.1. DO NOT ATTEMPT TO USE THIS TDC V2.2 BASELEVEL with software built to use TDC Version 2.1 unless you first confirm interoperability with the provider of that software. TDC Version 2.2 completely supersedes TDC Version 2.1. All files shared by the two versions will be updated; files used by Version 2.1 that are not also used by Version 2.2 will be removed from the system. If you previously installed the Version 2.1 TDC SDK, those files will also be removed during a TDC Version 2.2 installation. You can choose installation of the updated SDK as a part of the TDC Version 2.2 installation. 2. Software updates Updates to files provided with TDC_RT Version 2.2 and TDC Version 2.2 will be provided through the complete TDC kit, which can be downloaded from the web site at: http://www.hp.com/products/openvms/tdc 3. System requirements There are no special system requirements. If your site runs TCPware or MultiNet software, a software download available from Process Software will enable additional TDC functionality as described in the release notes (SYS$COMMON:[TDC]TDC_RELEASE_NOTES.TXT). 4. User privileges and quotas The following privileges must be enabled in order to collect all metrics provided by TDC: CMKRNL, LOG_IO, NETMBX, PHY_IO, SYSLCK, SYSPRV, WORLD Various subsets of those privileges may allow collection of some metrics. The online help provided when the TDC collector application is running specify the privileges required to collect each group of metrics. Users running TDC require working set quotas (WSQUO) in excess of the following: 6000 pagelets to run TDC in an Alpha environment 7000 pagelets to run TDC in an Integrity server environment Higher quotas are recommended if the value of SYSGEN parameter MAXPROCESSCNT is greater than 500, or if there more than 200 disks are visible to the system. 5. Installation options Before installing TDC, you should stop any applications that utilize TDC(_RT) (for example, the OpenView(R) Performance Agent or any active TDC collectors). The new TDC software will be unable to fully load to perform a data collection until those applications have been stopped, resulting in a temporary inability to collect I/O metrics. During installation, you will be given the option of installing all TDC components, or a subset of TDC components. The current options include: - Selection of the runtime environment(s) to install: OpenVMS Version 7.3-2 (Alpha) OpenVMS Version 8.2 (Alpha) OpenVMS Version 8.3 (Alpha) OpenVMS Version 8.2 (I64) OpenVMS Version 8.2-1 (I64) OpenVMS Version 8.3 (I64) - Installing the Software Developers Kit, which provides the ability to create software that interacts with TDC. A system reboot is NOT required after installing TDC. 6. Installing TDC in an OpenVMS Cluster A. Single-version, single-architecture clusters By default, TDC is installed in SYS$COMMON:[TDC]. All cluster members that share that system disk can utilize the TDC software installed there. Note, however, that the TDC startup file, SYS$STARTUP:TDC$STARTUP.COM, must be run from each cluster member so that updated images will be recognized. B. Mixed-version, single-architecture clusters System disks are architecture-specific and can be shared only by systems running the same version of the operating system. It is possible, however, to define a common system root that can be shared among systems. For example, the following scheme uses the logical name CLU$COMMON as a system root on a disk served to all cluster members; SYS$SYSROOT is then defined as a search list consisting of the OpenVMS version- specific root and the cluster-common root: $ SHOW LOGICAL SYS$SYSROOT "SYS$SYSROOT" = "$6$DKA0:[SYS0.]" (LNM$SYSTEM_TABLE) = "SYS$COMMON:" "SYS$COMMON" = "$6$DKA0:[SYS0.SYSCOMMON.]" (LNM$SYSTEM_TABLE) = "CLU$COMMON:" "CLU$COMMON" = "$4$DUA11:[CLUSTER$COMMON.]" (LNM$SYSTEM_TABLE) If TDC is installed using the command: $ PRODUCT INSTALL TDC /DEST=CLU$COMMON: then it will be installed in the CLU$COMMON root, and the following directories will be created and populated as necessary: CLU$COMMON:[SYS$LDR] CLU$COMMON:[SYSLIB] CLU$COMMON:[SYS$STARTUP] CLU$COMMON:[SYSTEST] CLU$COMMON:[TDC] After the installation, TDC$STARTUP.COM must be run on all cluster members: $ MCR SYSMAN SYSMAN> SET ENVIRONMENT/CLUSTER SYSMAN> DO @SYS$STARTUP:TDC$STARTUP SYSMAN> EXIT Note that if TDC_RT was previously installed on any cluster member, it will have placed file TDC$STARTUP.COM in SYS$COMMON:[SYS$STARTUP], and that file will be executed instead of the file installed by TDC in CLU$COMMON:[SYS$STARTUP]. That should not be an issue: both startup files will locate the most recent versions of the TDC images and create the appropriate logical names. C. Mixed-version, mixed-architecture clusters System disks are architecture-specific and can be shared only by systems running the same version of the operating system. It is possible, however, to define a common system root that can be shared among systems. For example, the following scheme uses the logical name CLU$COMMON as a system root on a disk served to all cluster members; SYS$SYSROOT is then defined as a search list consisting of the OpenVMS version- specific root, a shared architecture-specific root, and the cluster-common root. For an Alpha system in the cluster, a scheme similar to the following might be in effect: $ SHOW LOGICAL SYS$SYSROOT "SYS$SYSROOT" = "$6$DKA0:[SYS0.]" (LNM$SYSTEM_TABLE) = "SYS$COMMON:" "SYS$COMMON" = "$6$DKA0:[SYS0.SYSCOMMON.]" (LNM$SYSTEM_TABLE) = "CLU$ALPHA_COMMON:" "CLU$ALPHA_COMMON" = "$4$DUA11:[CLUSTER$ALPHA_COMMON.]" (LNM$SYSTEM_TABLE) = "CLU$COMMON:" "CLU$COMMON" = "$4$DUA11:[CLUSTER$COMMON.]" (LNM$SYSTEM_TABLE) From an Integrity server system in the cluster, a parallel scheme similar to the following might be in effect: $ SHOW LOGICAL SYS$SYSROOT "SYS$SYSROOT" = "$6$DKA0:[SYS0.]" (LNM$SYSTEM_TABLE) = "SYS$COMMON:" "SYS$COMMON" = "$6$DKA0:[SYS0.SYSCOMMON.]" (LNM$SYSTEM_TABLE) = "CLU$IA64_COMMON:" "CLU$IA64_COMMON" = "$4$DUA11:[CLUSTER$IA64_COMMON.]" (LNM$SYSTEM_TABLE) = "CLU$COMMON:" "CLU$COMMON" = "$4$DUA11:[CLUSTER$COMMON.]" (LNM$SYSTEM_TABLE) If TDC is installed using the command: $ PRODUCT INSTALL TDC /DEST=CLU$COMMON: then it will be installed in the CLU$COMMON root, and the following directories will be created and populated as necessary: CLU$COMMON:[SYS$LDR] CLU$COMMON:[SYSLIB] CLU$COMMON:[SYS$STARTUP] CLU$COMMON:[SYSTEST] CLU$COMMON:[TDC] After the installation, TDC$STARTUP.COM must be run on all cluster members: $ MCR SYSMAN SYSMAN> SET ENVIRONMENT/CLUSTER SYSMAN> DO @SYS$STARTUP:TDC$STARTUP SYSMAN> EXIT Note that if TDC_RT was previously installed on any cluster member, it will have placed file TDC$STARTUP.COM in SYS$COMMON:[SYS$STARTUP], and that file will be executed instead of the file installed by TDC in CLU$COMMON:[SYS$STARTUP]. That should not be an issue: both startup files will locate the most recent versions of the TDC images and create the appropriate logical names. 7. Sample Installation Log The following installation was performed on an OpenVMS Version 7.3-2 system after downloading (and unpacking, for downloads to Alpha systems) the complete kit from the web site cited above. The installation was performed in a mixed-version, mixed-architecture, OpenVMS Cluster, in which location CLU$COMMON: is shared by all cluster members. Accompanying comments are delimited by '!' in the log below. $ product install tdc /dest=clu$common: The following product has been selected: HP VMS TDC V2.2-108 Layered Product Do you want to continue? [YES] Configuration phase starting ... You will be asked to choose options, if any, for each selected product and for any products that may be installed to satisfy software dependency requirements. HP VMS TDC V2.2-108: The Performance Data Collector for OpenVMS © 2003-2005 Hewlett-Packard Development Company, L.P. All rights reserved. Hewlett-Packard Development Company, L.P. A separate license is not required for use of this product. You are installing software from the complete Performance Data Collector kit. The kit includes runtime environments for all supported OpenVMS configurations as well as a Software Developers Kit (SDK) to use to develop software that can use the Performance Data Collector. This kit contains the following software: The TDC Software Developers Kit (SDK) TDC runtime software for OpenVMS Version 7.3-2 (Alpha) TDC runtime software for OpenVMS Version 8.2 (Alpha) TDC runtime software for OpenVMS Version 8.3 (Alpha) TDC runtime software for OpenVMS Version 8.2 (Integrity server) TDC runtime software for OpenVMS Version 8.2-1 (Integrity server) TDC runtime software for OpenVMS Version 8.3 (Integrity server) You can choose to install the entire contents of this kit or to install individual components. Do you want to install the entire kit? [YES]: The following options will be installed: The Software Developers Kit The OpenVMS V7.3-2 (Alpha) runtime environment The OpenVMS V8.2 (Alpha) runtime environment The OpenVMS V8.3 (Alpha) runtime environment The OpenVMS V8.2 (Integrity server) runtime environment The OpenVMS V8.2-1 (Integrity server) runtime environment The OpenVMS V8.3 (Integrity server) runtime environment Is this correct? [YES]: * This product does not have any configuration options. Execution phase starting ... The following product will be installed to destination: HP VMS TDC V2.2-108 DISK$FOLK$:[FOLK$COMMON.] Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% The following product has been installed: HP VMS TDC V2.2-108 Layered Product %PCSI-I-IVPEXECUTE, executing test procedure for HP VMS TDC V2.2-108 ... %PCSI-I-IVPSUCCESS, test procedure completed successfully HP VMS TDC V2.2-108: The Performance Data Collector for OpenVMS Users of this product require the following privileges: (CMKRNL,LOG_IO,WORLD,PHY_IO,SYSPRV,SYSLCK) Users of this product require the following process resource limits: WSQUO minimum 6000 Insert the following lines in SYS$MANAGER:SYSTARTUP_VMS.COM: @sys$startup:tdc$startup.com A read-me file is available in SYS$COMMON:[TDC]TDC_README.TXT Release notes are available in SYS$COMMON:[TDC]TDC_RELEASE_NOTES.TXT $ $ mcr sysman ! Make the update visible throughout the cluster SYSMAN> set environment/cluster %SYSMAN-I-ENV, current command environment: Clusterwide on local cluster Username SYSTEM will be used on nonlocal nodes SYSMAN> do @sys$startup:tdc$startup ... SYSMAN> Exit $ $ sho logical tdc* ! logical names created by TDC$STARTUP.COM on this system; ! the exact names created by TDC$STARTUP depend upon ! the platform on which TDC$STARTUP is run, and the ! most recent version of the TDC software which is ! visible to TDC$STARTUP through the SYS$COMMON: ! system root. (LNM$SYSTEM_TABLE) "TDC$APISHR" = "CLU$COMMON:[SYSLIB]TDC$APISHR$A_V732-0081.EXE" "TDC$CP" = "CLU$COMMON:[TDC]TDC$CP$A_V732-0081.EXE" "TDC$LIBSHR" = "CLU$COMMON:[SYSLIB]TDC$LIBSHR$A_V732-0081.EXE" "TDC_EXEC_C" = "TDC_EXEC_C$A_V732-0081.EXE" $