------------------------------------------------------------------------------- TDC Version 2.3 Release Notes (Baselevel V2.3-15) ------------------------------------------------------------------------------- TDC Version 2.3 is primarily a maintenance release of the Performance Data Collector for OpenVMS software. The principal goals in providing this version are to correct defects discovered in TDC V2.2 and to provide the ability to create CSV-formatted (Comma-Separated Values) output files from TDC data records. *** IMPORTANT NOTE -- READ THIS! *** ************************************************************************** *** PLEASE NOTE THAT TDC SOFTWARE FOR OpenVMS Version 8.2 (I64) IS NO *** *** LONGER PROVIDED, EFFECTIVE WITH RELEASE OF TDC V2.3. IF YOU ARE *** *** STILL USING OpenVMS Version 8.2 (I64), YOU SHOULD NOT INSTALL THIS *** *** TDC V2.3 KIT. *** ************************************************************************** TDC Version 2.3 installs the most recent versions of all TDC runtime files, incorporating new functionality as well as all corrections and enhancements delivered in previous TDC Version 2.1 and Version 2.2 releases and ECOs. Prior installation of an earlier version of TDC or TDC_RT is not required. This document contains the following sections: * TDC Version 2.3 Runtime Requirements * TDC Version 2.3 Restrictions * Compatibility with Previous Releases * TDC Version 2.3 Installation Notes * TDC Version-Checking * TDC Version 2.3 New Features * TDC Version 2.3 Release Notes + V2.3-1 notes Software developers should also consult the following file: SYS$COMMON:[TDC.SDK]TDC_SDK_RELEASE_NOTES.TXT That file is provided when the SDK is installed from a "full" TDC kit. --------------- TDC Version 2.3 Runtime Requirements ------------------------- V2.3:RQ1 -- System requirements TDC Version 2.3 requires the following system resources: - Systemwide lock "node:TDC$EXECLET_LOCK" [node is the system node name] - Systemwide lock "TDC$node_XVC_DL2" [node is the system node name] _ Cluster-wide lock tree "TDC$CLUSTER" - The following spin locks: CPU, SCHED and PERFMON - Approximately 50 bytes of non-paged pool ------------------------------------------------------------------------------ V2.3:RQ2 -- User requirements A. Privileges TDC Version 2.3 requires the following privileges to collect all data items: - CMKRNL - LOG_IO - NETMBX - PHY_IO - SYSLCK - SYSPRV - WORLD The online help ( TDC> HELP PRIVILEGES ) lists the specific privileges required to collect each TDC data types. TDC Version 2.3 requires SYSLCK privilege to create a detached data collector process. Required privileges must be enabled by the user prior to using the TDC software. B. Working set Users of TDC Version 2.3 should have a working set quota (WSQUO) greater than 7000 pagelets to run the product on Integrity server platforms, or greater than 6000 pagelets to run the product on Alpha platforms. ------------------------------------------------------------------------------ --------------------- TDC Version 2.3 Restrictions -------------------------- V2.3:RS1 Do not start a TDC data collector as a part of the system boot procedure. There has been one report of a boot hang when a TDC collector was started before the system had fully booted. The problem is avoided by waiting until the system has fully booted before starting a TDC collector. This issue applies both to running the TDC collector directly and to running software that itself runs a TDC collector (for example, OpenView Performance Agent for OpenVMS). ------------------------------------------------------------------------------ V2.3:RS2 The TDC software should be installed only into a directory that is accessible through the SYS$SYSROOT: search list. In general, this includes SYS$SPECIFIC:[TDC] and SYS$COMMON:[TDC]. Also, see file [TDC]TDC_COMPLETE_INSTALL_GUIDE.TXT for additional possibilities. Avoid installing the TDC software into an arbitrary directory, such as DISK$PRODS:[TDC]. While the installation may complete successfully, the required runtime images will generally not be found when attempting to run the TDC software. If installation into an arbitrary directory is required for some reason, you'll have to edit a copy of TDC$STARTUP.COM to look for the runtime images in the correct locations; redefinition of various system logicals, such as SYS$SHARE, SYS$STARTUP, SYS$TEST, and SYS$LOADABLE_IMAGES may also be necessary. Installation into an arbitrary directory as described above is not supported by OpenVMS engineering. ------------------------------------------------------------------------------ V2.2:RS3 Internet statistics (TCP/IP) can be collected only when one of the following is configured as the networking software (IP stack): * HP TCP/IP Services for OpenVMS * Multinet (see below) * TCPware (see below) Process Software has made available plug-in modules for use with TDC Version 2.2-108 and later. These modules allow TDC to report internet metrics (INET record) in the following environments: Alpha systems running OpenVMS Version 7.3-2 and later: * MultiNet Versions 4.4, 5.0, and 5.1 * TCPware Versions 5.6-2 and 5.7-2 Integrity systems running OpenVMS Version 8.2 and later: * MultiNet Version 5.1 * TCPware Version 5.7-2 The required software can be downloaded from the Process Software support site: MultiNet: ftp://ftp.multinet.process.com/patches/multinet051/tdc_multinet010.zip TCPware: ftp://ftp.process.com/support/57_2/tdc_tcpware010.zip Once installed, no further action is required: TDC will detect the presence of the software and load it as necessary. ------------------------------------------------------------------------------ V2.3:RS4 There is an upper limit of 2 gigabytes (4194303 blocks) on the size of individual collection files created by TDC Version 2.3. Attempting to exceed that size will cause the collection operation to exit. The only workaround to this restriction is to create smaller files, perhaps by running the collector daily and storing each day's data in a separate file or by specifying a longer period between data snapshots (/INTERVAL=n [seconds]). ------------------------------------------------------------------------------ V2.3:RS5 TDC Version 2.3 does not adapt to abrupt changes to the system time when collecting data. Setting the system time back while a TDC collector is running (for example, from 10:00:00 to 09:00:00) may trigger a flurry of data snapshots with no intervening time between snapshots, and may cause the data collection to halt prematurely if the new system time is earlier than the specified end time for a data collection. Setting the system time ahead while a TDC collector is running (for example, from 09:00:00 to 10:00:00) will introduce a delay between consecutive snapshots. In either event, an application's processing of data collected around a system time change may produce unreliable results. Gradual changes to the system time, as performed by various time synchronization services, should not be a problem. ------------------------------------------------------------------------------ V2.3:RS6 While collecting data and storing it in a data collection file, the TDC software maintains exclusive access to the file. This restriction means that the contents of the file are not available for processing until the file has been closed. File metadata (the file header and various internal pointers) are updated at each snapshot. The contents of the file are, therefore, not stable until TDC has closed the file at the end of a collection. This restriction does not apply to reading TDC collection files, in which TDC opens the file in such a way as to allows shared access. One workaround to this restriction is to break a collection up into smaller files. This can be accomplished either through DCL scripts that control the start and stop times of a series of TDC COLLECT commands, or by using the TDC Software Developers Kit (SDK) to develop a customized collector application. The OpenVMS Technical Journal article at < http://h71000.www7.hp.com/openvms/journal/v5/ [continues on next line] intro-to-performance-data-collector.pdf > shows most of an application that splits a 24-hour data collection into a series of 1-hour collections, each storing its data into a unique file. Individual files are then available for processing on an hourly basis. The TDC SDK can also be used to develop software to be loaded as a part of a TDC collection operation. That software, probably in the form of a "consumer processor module," can utilize the TDC-provided data as it is collected and write all data, or a subset of it, to a file whenever needed, in whatever format or shared-access mode is appropriate. ------------------------------------------------------------------------------ V2.3:RS7 Disk I/O counts are not tracked for LDx or for DPA devices. Changes to the relevant drivers will be pursued for a future update. ------------------------------------------------------------------------------ ------------------- Compatibility with Previous Releases --------------------- Software Compatibility ---------------------- V2.3:C1 ECP (Enterprise Capacity and Performance) TDC Version 2.3 is not compatible with ECP Version 5.5A; an upgrade to ECP Version 5.6 or later is required (only if ECP is a part of your system management solution). V2.3:C2 Other than as noted in V2.3:C1, software developed using TDC Versions 2.1 or 2.2 should work without changes when run against the TDC Version 2.3 software, but will typically not have access to new features or data. V2.3:C3 Software developed using TDC Version 1.x or Version 2.0 is not compatible with TDC Version 2.3 until it has been rebuilt using the TDC Version 2.3 Software Developers Kit. Data Compatibility ------------------ V2.3:C4 Data files created using TDC Version 2.1 should be readable with TDC Version 2.3, but files created using TDC Version 2.3 are not readable with TDC Version 2.1 software. V2.2:C5 Data files created using TDC Version 2.2 should be readable with TDC Version 2.3, but files created using TDC Version 2.3 are not readable with TDC Version 2.2 software. V2.2:C6 Data files created using TDC Version 1.x or Version 2.0 cannot be read using TDC Version 2.3. Data files created using TDC Version 2.3 cannot be read using TDC Version 1.x or 2.0. ------------------- TDC Version 2.3 Installation Notes ----------------------- This section addresses various scenarios in which TDC or TDC_RT Version 2.3 is installed on a system on which TDC or TDC_RT Version 2.1, 2.2, or 2.3 was previously installed. "TDC_RT" software is installed with OpenVMS Versions 8.2 and later; it includes the TDC runtime software required for use with the OpenVMS version with which it is installed. "TDC" software is downloaded from the web site at the following URL: http://www.hp.com/products/openvms/tdc It includes runtime software for all supported OpenVMS configurations, as well as a Software Developers Kit (SDK). The runtime software provided by that kit will generally provide corrections to, and minor enhancements over, the TDC_RT software installed with OpenVMS Version 8.2 or later. 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. A system reboot is NOT required after installing or upgrading the TDC software. In general, installation of a "TDC" kit does NOT remove, and does NOT update, the "TDC_RT" software installed with OpenVMS, and installation of a "TDC_RT" kit does NOT remove or update "TDC" software installed from a downloaded kit. Some HP-supplied and third-party software may have dependencies on the TDC_RT software specifically installed with OpenVMS Version 8.2 or later. Therefore, HP does not recommend removing the TDC_RT software installed with the operating system, even when installing an update by means of a TDC kit downloaded from the above web site. The following sections may refer to "baselevel numbers." Each TDC and TDC_RT Version 2.3 installation kit is identified by a version string, similar to "V0203-1," as a part of the kit file name. In the example, "1" is the baselevel number. ------------------------------------------------------------------------------ V2.3:Inst01 -- Installing TDC_RT Version 2.3 Over TDC_RT Version 2.1 This scenario might be relevant if you are performing an OpenVMS upgrade. TDC_RT Version 2.3 completely supersedes TDC_RT Version 2.1; all files shared by the two releases will be appropriately updated, and any files used by TDC_RT Version 2.1 that are not also used by Version 2.3 will be removed from the system. The version of TDC_RT displayed by $ PRODUCT SHOW PRODUCT TDC_RT will be updated. ------------------------------------------------------------------------------ V2.3:Inst02 -- Installing TDC_RT Version 2.3 Over TDC Version 2.1 This scenario might be relevant if you are performing an OpenVMS upgrade. If you are upgrading from OpenVMS Version 8.2 or Version 8.2-1 to a later OpenVMS version, then the above section, V2.3:Inst01, may also be relevant. Files shared by TDC_RT Version 2.3 and TDC Version 2.1 will be updated; this includes the documentation and support files listed in SYS$COMMON:[TDC]README.TXT as common to all kit variants. Image files installed with TDC Version 2.1 will be retained in their installed locations. The TDC Version 2.1 SDK, if installed ([SYS$COMMON:[TDC.SDK...]), will not be touched, and any additional documentation files installed with TDC Version 2.1 will also be retained. You can continue to use the TDC Version 2.1 SDK to develop software to interact with TDC, but you will have to download and install the Version 2.3 kit, with its SDK, to access new data records and other features. The version of TDC displayed by $ PRODUCT SHOW PRODUCT TDC will not be changed by the installation of TDC_RT Version 2.3. Subsequent removal of TDC Version 2.1 will not impact integrity of the TDC_RT Version 2.3 installation. Running SYS$STARTUP:TDC$STARTUP.COM will cause the TDC_RT Version 2.3 images, rather than the TDC Version 2.1 images, to be used at runtime. ------------------------------------------------------------------------------ V2.3:Inst03 -- Installing TDC_RT Version 2.3 Over TDC Version 2.2 This section might be relevant if you are upgrading to OpenVMS Version 8.3-1H1 from an earlier version on which you installed TDC Version 2.2. Files shared by TDC_RT Version 2.3 and TDC Version 2.2 will be updated; this includes the documentation and support files listed in SYS$COMMON:[TDC]README.TXT as common to all kit variants. Image files installed with TDC Version 2.2 will be retained in their installed locations. The TDC Version 2.2 SDK, if installed (SYS$COMMON:[TDC.SDK...]), will not be touched, and any additional documentation files installed with TDC Version 2.2 will also be retained. The version of TDC_RT displayed by $ PRODUCT SHOW PRODUCT TDC_RT will be updated. Subsequent removal of TDC Version 2.2 will not affect the integrity of the TDC_RT Version 2.2 installation (assuming different baselevel numbers). Running SYS$STARTUP:TDC$STARTUP.COM will cause 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. ------------------------------------------------------------------------------ V2.3:Inst04 -- Installing TDC_RT Version 2.3 Over TDC Version 2.3 This section might be relevant if you are upgrading to OpenVMS Version 8.3-1H1 from an earlier version on which you installed TDC Version 2.3. Files shared by TDC_RT Version 2.3 and TDC Version 2.3 will be updated; this includes 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, 1), image files installed with TDC Version 2.3 will be retained in their installed locations. It is very likely that the downloaded TDC Version 2.3 software will be more recent (higher baselevel number) than the TDC_RT Version 2.3 software installed with OpenVMS Version 8.3-1H1. The TDC Version 2.3 SDK, if installed (SYS$COMMON:[TDC.SDK...]), will not be touched, and any additional documentation files installed with TDC Version 2.3 will also be retained. The version of TDC displayed by $ PRODUCT SHOW PRODUCT TDC will not be changed by the installation of TDC_RT Version 2.3. Subsequent removal of TDC Version 2.3 will not affect the integrity of the TDC_RT Version 2.3 installation (assuming different baselevel numbers). Running SYS$STARTUP:TDC$STARTUP.COM will cause the most recent TDC/TDC_RT Version 2.3 images to be used at runtime, regardless of whether they were installed with TDC Version 2.3 or with TDC_RT Version 2.3. ------------------------------------------------------------------------------ V2.3:Inst05 -- Installing TDC Version 2.2 Over TDC_RT Version 2.1 This scenario is likely if you are installing downloaded TDC software onto an OpenVMS Version 8.2 or 8.2-1 system. Files shared by TDC Version 2.3 and TDC_RT Version 2.1 will be updated; this includes the documentation and support files listed in SYS$COMMON:[TDC]README.TXT as common to all kit variants. Image files installed with TDC_RT Version 2.1 will be retained in their installed locations. The version of TDC_RT displayed by $ PRODUCT SHOW PRODUCT TDC_RT will not be changed by the installation of TDC Version 2.3. Subsequent removal of TDC_RT Version 2.1 will not affect the integrity of the TDC Version 2.3 installation. Running SYS$STARTUP:TDC$STARTUP.COM will cause the TDC Version 2.3 images, rather than the TDC_RT Version 2.1 images, to be used at runtime. ------------------------------------------------------------------------------ V2.3:Inst06 -- Installing TDC Version 2.3 Over TDC_RT Version 2.2 This scenario is likely if you are installing downloaded TDC software onto an OpenVMS Version 8.3 system. Files shared by TDC Version 2.3 and TDC_RT Version 2.3 will be updated; this includes the documentation and support files listed in SYS$COMMON:[TDC]README.TXT as common to all kit variants. Image files installed with TDC_RT Version 2.2 will be retained in their installed locations. The version of TDC_RT displayed by $ PRODUCT SHOW PRODUCT TDC_RT will not be changed by the installation of TDC Version 2.3. Subsequent removal of TDC_RT Version 2.2 will not affect the integrity of the TDC Version 2.3 installation. Running SYS$STARTUP:TDC$STARTUP.COM will cause the TDC Version 2.3 images, rather than the TDC_RT Version 2.2 images, to be used at runtime. ------------------------------------------------------------------------------ V2.3:Inst07 -- Installing TDC Version 2.3 Over TDC_RT Version 2.3 This scenario is likely if you are installing downloaded TDC software onto an OpenVMS Version 8.3-1H1 system. Files shared by TDC Version 2.3 and TDC_RT Version 2.3 will be updated; this includes 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, 1), image files installed with TDC_RT Version 2.3 will be retained in their installed locations. It is very likely that the downloaded TDC Version 2.3 software will be more recent (higher baselevel number) than the TDC_RT Version 2.3 software installed with OpenVMS Version 8.3. The version of TDC_RT displayed by $ PRODUCT SHOW PRODUCT TDC_RT will not be changed by the installation of TDC Version 2.3. Subsequent removal of TDC_RT Version 2.3 will not impact integrity of the TDC Version 2.3 installation. Running SYS$STARTUP:TDC$STARTUP.COM will cause the most recent TDC/TDC_RT Version 2.3 images to be used at runtime, regardless of whether they were installed with TDC Version 2.3 or with TDC_RT Version 2.3. ------------------------------------------------------------------------------ V2.3:Inst08 -- Installing TDC Version 2.3 Over TDC Version 2.1 This scenario is likely if you previously installed TDC Version 2.1 software from the web site and have now downloaded the TDC Version 2.3 software. TDC Version 2.3 completely supersedes TDC Version 2.1; all files shared by the two releases will be appropriately updated, and any files used by TDC Version 2.1 that are not also used by Version 2.3 will be removed from the system. The TDC Version 2.1 SDK, if installed (in SYS$COMMON:[TDC.SDK...]), will be removed during the installation of TDC Version 2.3 (and replaced by the TDC Version 2.3 SDK if that installation option is selected). The version of TDC displayed by $ PRODUCT SHOW PRODUCT TDC will be updated. ------------------------------------------------------------------------------ V2.3:Inst09 -- Installing TDC Version 2.3 Over TDC Version 2.2 This scenario is likely if you previously installed TDC Version 2.2 software from the web site and have now downloaded the TDC Version 2.3 software. TDC Version 2.3 completely supersedes TDC Version 2.2; all files shared by the two releases will be appropriately updated, and any files used by TDC Version 2.2 that are not also used by Version 2.3 will be removed from the system. The TDC Version 2.2 SDK, if installed (in SYS$COMMON:[TDC.SDK...]), will be removed during the installation of TDC Version 2.3 (and replaced by the TDC Version 2.3 SDK if that installation option is selected). The version of TDC displayed by $ PRODUCT SHOW PRODUCT TDC will be updated. ------------------------------------------------------------------------------ V2.3:Inst10 -- Installing TDC Version 2.3 Over TDC Version 2.3 This scenario is likely if you previously installed TDC Version 2.3 software from the web site and have now downloaded a newer baselevel of the TDC Version 2.3 software. TDC Version 2.3 completely supersedes any older TDC Version 2.3 kit; all files shared by the two releases will be appropriately updated, and any files used by the older TDC Version 2.3 release that are not also used by the new release will be removed from the system. The TDC Version 2.3 SDK, if installed (in SYS$COMMON:[TDC.SDK...]), will be removed during the installation of a newer TDC Version 2.3 release (and replaced by the newer TDC Version 2.3 SDK if that installation option is selected). The version of TDC displayed by $ PRODUCT SHOW PRODUCT TDC will be updated. ------------------------------------------------------------------------------ ------------------------- TDC Version-Checking ------------------------------- Sometimes it is necessary to determine which version of the TDC software is running on a system. The following notes (V2.3:VC01 - V2.3:VC04) describde various ways to determine that. First, note the following two points: * In an OpenVMS Cluster environment, it is possible that the version of TDC installed on a system is not the version actually in use on that system. This situation can arise when the system disk is shared among systems. The TDC startup file (SYS$STARTUP:TDC$STARTUP.COM) looks for the most recent version of the TDC software that it can find. If, for example, TDC Version 2.1-83 has been installed into the SYS$SPECIFIC: root, while TDC Version 2.3-1 has been installed into the SYS$COMMON: root, TDC$STARTUP will cause the TDC Version 2.3-1 software to be run -- despite the fact the TDC Version 2.1-83 is actually installed on the system. For that reason, DCL command "$ PRODUCT SHOW PRODUCT" may not reliably indicate the version of the TDC software actually in use on the system. * "TDC" and "TDC_RT" represent two different packagings of the same runtime software. Once installed, however, the software is "TDC," no matter the software kit from which it was installed, and the TDC startup file (SYS$STARTUP:TDC$STARTUP.COM) will identify the most recent version available to the system and cause that to be run (see above). The installation notes above discuss expected outcomes of installing both products. ------------------------------------------------------------------------------ V2.3:VC01 -- Identifying the TDC software in use (run TDC) The easiest way to identify the version of the TDC software actually available for use on a system is to run the TDC control application: $ @SYS$STARTUP:TDC$STARTUP $ SET COMMAND SYS$COMMON:[TDC]TDC$DCL $ TDC Performance Data Collector for hp OpenVMS TDC$CP, V2.3-20001 for HP OpenVMS (Alpha) V7.3-2, 06-Jun-2007:14:31:04 API: TDC$APISHR, V2.3-20001 for HP OpenVMS (Alpha) V7.3-2, 06-Jun-2007:14:31:04 LIB: TDC$LIBSHR, V2.3-20001 for HP OpenVMS (Alpha) V7.3-2, 06-Jun-2007:14:31:04 At startup, the TDC control application displays the versions of all components of the TDC software that it has loaded. In the above display, the version is V2.3-1 (the first character after the '-' is '2' for Alpha systems or '3' for Integrity systems). "0001" ("1") is the baselevel number. Note that the displayed times are software build times, and not the current time. ------------------------------------------------------------------------------ V2.3:VC02 -- Identifying the TDC software in use (logical names) The TDC software that would be run can also be identified on the basis of a set of logical names created by the TDC startup file (SYS$STARTUP:TDC$STARTUP.COM) for each of the TDC components: $ @SYS$STARTUP:TDC$STARTUP $ SHOW LOGICAL/SYSTEM TDC* (LNM$SYSTEM_TABLE) "TDC$APISHR" = "CLU$COMMON:[SYSLIB]TDC$APISHR$A_V732-0203-0001.EXE" "TDC$CP" = "CLU$COMMON:[TDC]TDC$CP$A_V732-0203-0001.EXE" "TDC$LIBSHR" = "CLU$COMMON:[SYSLIB]TDC$LIBSHR$A_V732-0203-0001.EXE" "TDC_EXEC_C" = "TDC_EXEC_C$A_V732-0203-0001.EXE" In this case, each file NAME ends with a string of the form, "$c_Vnnn-vvvv-mmmm" where: * 'c' is either 'A' for Alpha systems or 'I' for Integrity systems; * 'nnn' is the OpenVMS version for which the software was built (currently one of: '732', '820', '821', '830', or 831H1); * 'vvvv' identifies the TDC version (beginning with TDC Version 2.3), and is '0203' to identify this as a TDC Version 2.3 image; * 'mmmm' is the TDC Version 2.3 build number ('0001' for this baselevel). ------------------------------------------------------------------------------ V2.3:VC03 -- Identifying the TDC software that is potentially available $ DIRECTORY SYS$SHARE:TDC$*.EXE will list all TDC shareable images installed in SYS$SHARE: Note V2.3:VC02 discusses how the various software versions can be identified from the file names. ------------------------------------------------------------------------------ V2.3:VC04 -- Writing TDC version information to a file You can, if needed, run the TDC control application to write identifying version information into a file, perhaps for processing by a DCL script: $ @SYS$STARTUP:TDC$STARTUP $ SET COMMAND SYS$COMMON:[TDC]TDC$DCL $ TDC SHOW VERSION[/FULL]/OUTPUT=tdc.out Performance Data Collector for hp OpenVMS TDC$CP, V2.3-20001 for HP OpenVMS (Alpha) V7.3-2, 06-Jan-2006:14:31:04 API: TDC$APISHR, V2.3-20001 for HP OpenVMS (Alpha) V7.3-2, 06-Jan-2006:14:31:04 LIB: TDC$LIBSHR, V2.3-20001 for HP OpenVMS (Alpha) V7.3-2, 06-Jan-2006:14:31:04 $ type tdc.out TDC$CP: TDC$CP, V2.3-20001 for HP for hp OpenVMS (Alpha) V7.3-2, 06-Jan-2006:14:31:04 TDC$APISHR: TDC$APISHR, V2.3-20001 for HP OpenVMS (Alpha) V7.3-2, 06-Jan-2006:14:31:04 TDC$LIBSHR: TDC$LIBSHR, V2.3-20001 for HP for hp OpenVMS (Alpha) V7.3-2, 06-Jan-2006:14:31:04 TDC_EXEC_C: TDC_EXEC_C$A_V732-0203-0001.EXE ------------------------------------------------------------------------------ --------------------- TDC Version 2.3 New Features --------------------------- V2.3:F1 CSV (Comma-Separated Values) files can be generated from TDC data, either while runing a collection, or from a data collection file. $ TDC COLLECT/CONVERT=SYS/FORMAT=CSV/OUTPUT=TDC$SYS.CSV will write CSV-formatted SYS records to file TDC$SYS.CSV while the collection is running AND WHILE a TDC data file is also being created. For SYS records, one CSV record will be created at each TDC snapshot. Use the /NOCOLLECTION_FILE qualifier to inhibit creation of the TDC collection file. TDC EXTRACT/CONVERT=(SYS,MEM)/FORMAT=CSV/OUTPUT=TDC$SYSMEM.CSV/COLLECTION=file will create a file with CSV-formatted records; each record will contain both SYS and MEM data for one snapshot (that is, specifying a list of record types with /CONVERT will produce output records in which those records are concatenated). ------------------------------------------------------------------------------ V2.3:F2 In response to a customer concern about fragmentation of TDC data collection files as they are written to a fragemented disk [QXCM100413953], some degree of site-specific control over TDC's creation of collection files is now supported. By default, when the between-snapshot interval is at least 30 seconds (the default between snapshot time is 120 seconds), TDC will close the data file after updating it at each snapshot point and will then reopen it. Also by default, for shorter between-snapshot intervals, TDC will flush the collection file after updating it at each snapshot, but will keep the file open. Logical name TDC$REOPEN_FREQUENCY can be defined to modify TDC's file-handling as described above. TDC$REOPEN_FREQUENCY can be defined as a positive integer value; the value will control the frequency at which TDC closes and reopens its collection file. For example, if TDC$REOPEN_FREQUENCY is defined as "10" then TDC will close and reopen the file at every 10th snapshot, regardless of the between-snapshot interval. TDC$REOPEN_FREQUENCY can be defined in the collector process' process or job logical name table, or in the system logical name table. Tables will be scanned in the order LNM$PROCESS, LNM$JOB, LNM$SYSTEM; the first definition of TDC$REOPEN_FREQUENCY that is seen will be used. If TDC$REOPEN_FREQUENCY is undefined after scanning all three tables, or if the first occurrence of TDC$REOPEN_FREQUENCY defines its value as "", "0", or "1", then the current default behavior will be maintained. In using TDC$REOPEN_FREQUENCY to try to control file fragmentation, it will probably also be necessary to specify non-default RMS parameters for the TDC collection. That might best be achieved by a $ SET RMS_DEFAULT=nnnn [blocks] command in the context of the collector process. An appropriate location for such a command might be the "prolog" command file executed when running the collector in a detached process. SYS$COMMON:[TDC]TDC$DETACHED_PROLOG.COM is the default prolog file; it contains usage instructions. ------------------------------------------------------------------------------ V2.3:F3 AAdditional data items are available in the SYS and PRO records. ------------------------------------------------------------------------------ --------------------- TDC Version 2.3 Release Notes -------------------------- The following list describes known defects and issues related to using TDC Version 2.3, as well as issues that have been addressed. ------------------------------------------------------------------------------ ----------------- Start TDC Version 2.3-1 Release Notes -------------------- ------------------------------------------------------------------------------ V2.3:05 ADP, DEV, CLU, CPUCFG, GLX, CTL and PAR data records are collected only once per collection. Therefore, CSV/T4/TLC output of these data records cannot be generated. ------------------------------------------------------------------------------ V2.3:04 An issue with data items having been shifted in the INET record has been corrected. ------------------------------------------------------------------------------ V2.3:03 A lingering collection-startup issue sometimes seen with previous baselevels, as a result of which detached collectors would fail to start has been corrected. The error reported (in the collection log file) as a result of this issue was: %TDC-E-INITERR, IPC startup failed: 2544 [%SYSTEM-W-VALNOTVALID, value block not valid] %TDC-E-NOSTART, Startup failed, exiting ------------------------------------------------------------------------------ V2.3:02 An issue collecting DSK/DEV records on OpenVMS Version 7.3-2 systems that had not installed ECO VMS732_SYS V4 or later has been corrected. ------------------------------------------------------------------------------ V2.3:01 An ACCVIO that could occur while extracting data in LIST format has been corrected. ------------------------------------------------------------------------------ ----------------- End TDC Version 2.3-1 Release Notes ----------------------