ECP Collector and Analyzer for OpenVMS Version 5.4D - Release Notes September 2003 These are the Release Notes for ECP Collector and Analyzer for Open VMS. Revision/Update Information: This document supersedes the Release Notes for ECP Collector and Analyzer for OpenVMS V5.4C. Hewlett Packard Company ECP Collector & Analyzer for OpenVMS Release Note - V5.4D ========================================================= Included With This Release The complete Enterprise Capacity and Performance (ECP) product set consists of four components: * ECP Data Collector * ECP Analyzer and Reducer * ECP Capacity Planner * ECP Data Base This product, ECP for OpenVMS, consists of two of the above components: * ECP Data Collector * ECP Analyzer Version 5.4D is comprised of the following items: * ECP Version 5.4D software * ECP Collector and Analyzer Installation Guide for OpenVMS * ECP Collector and Analyzer User Guide for OpenVMS For more information on all the components, see Enterprise Capacity and Performance User Guide and the Enterprise Capacity and Performance Installation guides and Software Product Descriptions. ECP Collector and Analyzer Features and Options ----------------------------------------------- The following is a summary of new features and changes specific to this OpenVMS release: * Bug fixes for Version 5.4C Problems Fixed in this V5.4D Release: ===================================== Control Returns to the DCL prompt instead of the Analyzer Window ---------------------------------------------------------------- If the time interval chosen at the Analyzer window is outside the valid range, clicking the graph button results in an error issuing a message. The application exits returning to the DCL prompt when OK is clicked. This version gracefully returns to the Analyzer Window and allows the user to correct the time interval chosen. De-installation procedure doesn't handle selective un-installation ------------------------------------------------------------------ The De-installation procedure doesn't handle the un-installation of individual components correctly. The new procedure un-installs the chosen components of ECP. If the complete product is un-installed then the ECP related files are deleted on request. Queue Manager needs to be checked --------------------------------- No error detection in ECP$MANAGER if queue manager isn't running. The procedure fails to start the ECP Collector due to this. The new manager issues appropriate messages if the queue manager isn't running so that the user can take appropriate action. ECP$DRIVER corrupts the IPL-6 Fork queue ---------------------------------------- The ECP$DRIVER was inserting the same fork block multiple times into the IPL 6 fork queue, causing queue corruption and system crash. The area of code around queuing fork blocks has been changed to avoid this repeated queuing. New OpenVMS feature Dynamic Volume Expansion (DVE) -------------------------------------------------- From OpenVMS V7.3-2 onwards the "Logical Volume Size" is considered for calculating disk space utilization instead of "Total Blocks". The respective changes have been incorporated in this release of ECP. Refer OpenVMS V7.3-2 documentation for much information on DVE. Restrictions and Known Problems-OpenVMS ======================================= The following is a summary of currently known restrictions and potential problems. Upgrading to ECP 5.4D from previous versions -------------------------------------------- Installing ECP Collector and Analyzer V5.4D will not remove the CP/Reduce and CP/Planner functions from V5.3. Installing Version 5.3 after Version 5.4D ----------------------------------------- If installing ECP Version 5.3, after ECP Version 5.4D for OpenVMS has been installed, to add the CP/Reduce and CP/Planner functions, ECP Version 5.4D will have to be re-installed to enable the /DUMP function. ECP Installation on OpenVMS V7.3-1 and later -------------------------------------------- ECP installation fails on OpenVMS V7.3-1 and later, if the process execution characteristics /PARSE_STYLE and /CASE_LOOKUP has keywords other than "Traditional" and "Blind" respectively. Local Graphics terminal using PLAN ANALYZE/MOTIF ------------------------------------------------ The PLAN ANALYZE/MOTIF command invokes the Motif interface for the ECP Analyzer. If this command is not executed on the local graphics terminal, the remote display needs to be specified: $ SET DISPLAY/CREATE/NODE=remote-node /TRANSPORT=DECNET or TCPIP. VAXC2DECC.EXE shareable library is required ------------------------------------------- The Enterprise Capacity and Performance suite requires DEC C Libraries installed. These libraries may not be present on some older VMS systems. If the following message is received during installation: ECP-E-NEEDS Sharable Library VAXC2DECC.EXE required Install the C/C++ Runtime Components kit. Note: VAXC2DECC.EXE and VAXC$EMPTY.EXE are available with AACRTVAXE03060(C/C++ Runtime Components Kit.) VAXC$EMPTY.EXE shareable library is required -------------------------------------------- The Enterprise Capacity and Performance suite requires DEC C Libraries installed. These libraries may not be present on some older VMS systems. If the following message is received during installation: ECP-E-NEEDS Sharable Library VAXC$EMPTY.EXE required Install the C/C++ Runtime Components kit. Note: VAXC2DECC.EXE and VAXC$EMPTY.EXE are available with AACRTVAXE03060(C/C++ Runtime Components Kit.) Restrictions, Problems and Cautions =================================== Link warnings ------------- All link warnings on OpenVMS should be ignored. Ignore ECP$DRIVER error messages -------------------------------- The execution of ECP$STARTUP.COM will result in the installation of the ECP Collector driver for the pseudo device cpa0:. The IO CONNECT of the driver may result in an informational error message. This message is innocuous and may be ignored. ECP$LIBRARY: ----------- - Need to be specific to the Architecture and OS Version; i.e. not shared between Alpha and VAX or among different OS versions. - Perform separate installations for each system disk. ECP$PERF_DATA: ------------- The Data Collection output files MAY be shared on a cluster common non-system disk. This is recommended configuration. Caution when using /INTERVAL ---------------------------- The /INTERVAL qualifier does not enforce a minimum value. The Minimum value should be 60. Values lower than this are not recommended. SYS$BATCH needs to be specific to each node ------------------------------------------- Use a node specific-queue in SYS$STARTUP:ECP$STARTUP.COM. For example: $DEFINE ECP$DC_QUEUE F$GETSYI("nodename")'$BATCH in SYS$STARTUP:ECP$STARTUP.COM. Otherwise, a shared generic batch queue will cause the Data Collector to always execute on the first node in the server queue list. VMS Clusters should run Time Services ------------------------------------- Time services should be run when in a clustered environment, so that the times on each system are synchronized. This is necessary because the Batch Queue Manager uses times from only one node in the cluster and if this node has a time ahead of the other nodes, the execution of the ECP$MANAGER.COM file to collect data can be problematic. ECP$MANAGER may be activated before midnight causing 1 days data to be missed. This is not specifically an ECP$MANAGER.COM issue, but rather a problem generic to the Queue Manager. The batch jobs are released from HOLD according to the time on the node running Queue Manager, but executed according to local system time. This can have undesirable results when the Queue Manager thinks it's midnight, but the target system thinks it's only 23:59, or vice-versa. Even with frequent synchronization of the time, the problem may still exist if the clocks are off by just 1 second.