HP DECset for OpenVMS Performance and Coverage Analyzer for OpenVMS Release Notes December 2007 These release notes describe important general information, new and changed features, current restrictions, and documentation notes that pertain to the Performance and Coverage Analyzer Version 5.0-1 for OpenVMS software. Operating System Version: OpenVMS Integrity servers Versions 8.2-1 and 8.3 OpenVMS Alpha Versions 7.3-2, 8.2, and 8.3 Software Version: HP DECset Version 12.8 ECO1 for OpenVMS Performance and Coverage Analyzer Version 5.0-1 for OpenVMS Hewlett-Packard Company Palo Alto, California ________________________________________________________________ © Copyright 2007 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Java is a US trademark of Sun Microsystems, Inc. Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. Printed in the US _________________________________________________________________ Contents Preface................................................... v 1 General Information 1.1 Introduction.................................. 1-1 1.2 Associated Documents.......................... 1-1 1.3 Using PCA with DECwindows Motif............... 1-2 1.4 Installation Requirements..................... 1-2 2 New Features 2.1 New Features in PCA Version 5.0-1............. 2-1 2.2 New Features in PCA Version 5.0............... 2-1 2.2.1 Extended File Specifications.............. 2-1 3 Problems Fixed 3.1 Problems Fixed in PCA Version 5.0-1........... 3-1 3.2 Problems Fixed in PCA Version 5.0............. 3-1 4 Known Problems 5 Restrictions 5.1 Restrictions in PCA Version 5.0-1............. 5-1 5.2 Restrictions in PCA Version 5.0............... 5-2 5.2.1 Collector................................. 5-2 5.2.1.1 DECwindows.............................. 5-5 5.2.1.2 User Routines........................... 5-5 5.2.2 Analyzer.................................. 5-6 5.2.2.1 DECwindows.............................. 5-6 5.2.3 DECwindows................................ 5-6 iii Tables 1-1 PCA Installation Requirements (Minimum)... 1-2 1-2 PCA Account Quotas........................ 1-3 iv _________________________________________________________________ Preface These release notes describe the HP Performance and Coverage Analyzer for OpenVMS (PCA), Versions 5.0-1 and 5.0 software. These notes contain information that either supplements or supersedes the information in the HP DECset Version 12.8 ECO1 for OpenVMS (DECset) documentation set. Intended Audience These release notes are intended for users and system managers who need information about PCA. Document Structure These release notes are organized as follows: o Chapter 1 contains general information about this release. o Chapter 2 contains a description of the new features. o Chapter 3 describes the problems resolved. o Chapter 4 describes the known problems. o Chapter 5 describes the restrictions. Related Documents For additional information about OpenVMS or DECset products and services, visit the following web address: http://www.hp.com/go/openvms v Reader's Comments HP welcomes your comments on these release notes. Please send comments to either of the following addresses: Internet openvmsdoc@hp.com Mail Hewlett-Packard Company OpenVMS Documentation, ZKO3-4/Y02 110 Spit Brook Rd. Nashua, NH 03062-2698 How To Order Additional Documentation For information about how to order additional documentation, visit the following web address: http://www.hp.com/go/openvms/doc/order Conventions The following conventions are used in these notes. ___________________________________________________________ Convention__________Description____________________________ $ A dollar sign ($) represents the OpenVMS DCL system prompt. Ctrl/x The key combination Ctrl/x indicates that you must hold down the key labeled Ctrl while you press another key, for example, Ctrl/Y or Ctrl/Z or a pointing device button. boldface text Boldface text represents the introduction of a new term. monospace boldface Boldface monospace text represents user text input in interactive examples. italic text Italic text represents book titles, parameters, arguments, and information that can vary in system messages (for example, Internal error number). vi ___________________________________________________________ Convention__________Description____________________________ UPPERCASE Uppercase indicates the name of a command, routine, the name of a file, the name of a file protection code, or the abbreviation of a system privilege. lowercase Lowercase in examples indicates that you are to substitute a word or value ____________________of_your_choice.________________________ vii 1 _________________________________________________________________ General Information The information in these release notes pertains to the Performance and Coverage Analyzer for OpenVMS software. HP suggests that you upgrade your environment incrementally with each new release, but there is no technical requirement to do so. It is recommended that you review the release notes for each version because they capture important release-oriented information and advise you of changes between versions. 1.1 Introduction Performance and Coverage Analyzer Version 5.0-1 for OpenVMS is a patch release. 1.2 Associated Documents The following documents contain information related to PCA. The documents associated with PCA are: o HP DECset for OpenVMS Guide to Performance and Coverage Analyzer o HP DECset for OpenVMS Performance and Coverage Analyzer Reference Manual o HP DECset for OpenVMS Performance and Coverage Analyzer Command-Line Interface Guide Also applicable are the general DECset documents: o HP DECset for OpenVMS Installation Guide o HP DECset for OpenVMS Software Product Description o HP DECset for OpenVMS Guide to Detailed Program Design o Using HP DECset for OpenVMS Systems General Information 1-1 In addition to the base PCA documentation, the DECset engineering team has also provided the HP DECset for OpenVMS Cookbook for an Integrated Product Development Environment. This document comprises a series of technical articles that describe how each of the component applications can be used in different programming environments. This document is available in PostScript (.PS), HTML (.HTML), and ASCII text (.TXT) formats from the following location after installing the product: SYS$SYSROOT:[SYSHLP.EXAMPLES.DECSET]DECSET_COOKBOOK.* 1.3 Using PCA with DECwindows Motif To use PCA with the DECwindows Motif interface, one of the following product must be installed: o HP DECwindows Motif for OpenVMS Integrity servers Version 1.6 o HP DECwindows Motif for OpenVMS Alpha Version 1.3-1 or 1.5 1.4 Installation Requirements Table 1-1 lists the installation requirements for PCA. Table_1-1_PCA_Installation_Requirements_(Minimum)__________ Global Disk Space Disk Space Page/PageletGlobal Operating During After Sections System______Installation_Installation_Required____Required_ OpenVMS 61,000 25,000 2,500 11 Integrity pagelets[1] servers OpenVMS 40,000 8,000 2,500 7 Alpha pagelets[1] [1]Plus_the_size_(in_number_of_disk_blocks)_of_the_file____ SYS$LIBRARY:DCLTABLES.EXE at installation ___________________________________________________________ Table 1-2 lists the account quotas for PCA. 1-2 General Information Table_1-2_PCA_Account_Quotas_______________________________ OpenVMS Integrtiy Resource_Name__servers________OpenVMS_Alpha________________ ASTLM 30 30 BYTLM 13,000 13,000 ENQLM 30 30 FILLM 20 20 PGFLQUOTA______30,000_________30,000_______________________ General Information 1-3 2 _________________________________________________________________ New Features 2.1 New Features in PCA Version 5.0-1 No new features have been added to PCA for Version 5.0-1. 2.2 New Features in PCA Version 5.0 2.2.1 Extended File Specifications PCA Version 5.0 supports Extended File Specifications functionality, which includes the following: o Support for longer file names and have a greater range of legal characters than in previous versions of PCA on ODS-5 Volume structure. o Support for deep directories. In order to use extended file names, you need to install PCA Version 5.0 with extended filename support. Additionally, the structure of the disk used to create files must be ODS-5. For more informatiopn, see the OpenVMS Guide to Extended File Specifications guide. New Features 2-1 3 _________________________________________________________________ Problems Fixed 3.1 Problems Fixed in PCA Version 5.0-1 The following problem is fixed in this release of PCA: o WFM 2214698917-221 - While setting the datafile PCA fails with the BADFILNAM error on OpenVMS Alpha V7.3-2 as shown: PCAC> set datafile primes %PCA-W-BADFILNAM, illegal file specification ''. This problem is fixed to set the datafile in PCA. For more information, refer to the related section in the Restrictions chapter. 3.2 Problems Fixed in PCA Version 5.0 The following problems were fixed in PCA Version 5.0: o WFM 1211432756-122 - PCA crashes with NOFREE error The Analyser would crash with "no free memory" error message when executing PCA Version 4.9 on Alpha OpenVMS V7.3-2. This problem has been corrected. o ID:32 - Source line with multiple PC ranges could cause misreporting. The Analyzer did not properly assign the PC values to a source line with multiple PC ranges. This problem has been corrected (Note: This problem has already been corrected in PCA Version 4.8 on OpenVMS Integrtiy servers). o ID:226 - Problem with Data File Record Format The Collector did not create the PCA data file with an appropriate record format; this could cause problems Problems Fixed 3-1 when attempting to copy PCA data files. This problem has been corrected. o ID:227 - PCA failed to operate on OpenVMS Alpha Version 8.2. This problem has been corrected. 3-2 Problems Fixed 4 _________________________________________________________________ Known Problems The following known problems exist from PCA Version 5.0: On all OpenVMS platforms, o ID:106: The PCA Analyzer command TABULATE/CHAIN_ NAME/ALPHABETICAL does not properly sort long call chain names. On OpenVMS Alpha Systems, o ID:160: I/O system services (and probably system services) are charged against the wrong line on Ada tasking programs. Known Problems 4-1 5 _________________________________________________________________ Restrictions 5.1 Restrictions in PCA Version 5.0-1 The following restriction exists for this version of PCA: o On OpenVMS Alpha Version 7.3-2, when the "set datafile" is not specified, the case-sensitivity of the default data file name will not be retained. This is due to the limitation imposed by Image Activator. PCA receives the default data file name with uppercase and hence, creates a collection of data files with only uppercase characters. For example: On ODS-5 disk, run the following commands: $run pca$8queens_c.exe PCAC>go : : The file name on OpenVMS Alpha Version 8.3 is displayed as follows: $dir *.pca pca$8queens_c.PCA;1 (Case-sensitivity of the file name is retained) The file name on OpenVMS Alpha Version 7.3-2 is displayed as follows: $dir *.pca PCA$8QUEENS_C.PCA;1 (Case-sensitivity of the file name is not retained and the file name is displayed with only uppercase characters) Restrictions 5-1 5.2 Restrictions in PCA Version 5.0 The following restrictions exist from PCA Version 5.0: o When using PCA with extended file specifications from the DCL command line, the DCL parse style must be set to extended filenames. Use the DCL command: $ SET PROCESS /PARSE_STYLE=EXTENDED 5.2.1 Collector On all OpenVMS platforms, o PCA cannot gather data from user programs which call SYS$EXIT directly or indirectly from their exit handler. The PCA exit handler makes sure that all data is written to the data file and that the data file is properly closed. This exit handler executes after the completion of all user mode exit handlers declared by the application program. If the PCA exit handler does not execute there may be loss of data or unrecoverable corruption of the data file. When SYS$EXIT is called from within an exit handler no remaining exit handlers in the same access mode will be executed. When an application exit handler calls SYS$EXIT the PCA exit handler does not execute. Users should be aware that the RTL routines LIB$DO_ COMMAND and LIB$RUN_PROGRAM contain calls to SYS$EXIT. PCA can not be used to collect data for programs which call either of these routines in their exit handlers. o The Collector is not AST re-entrant during program exit. The PCA exit handler cleans up and closes the data file. If an AST should occur while PCA is exiting the results are unpredictable. To avoid this situation, the user program should make sure there are no pending ASTs prior to terminating. o Unpredictable results can occur if PCA is used to collect data on programs which use unallocated local event flags. During data collection the PCA Collector dynamically allocates local event flags using LIB$GET_EF. Applications which use local event flags without first 5-2 Restrictions allocating them in the same manner may use an event flag being used by PCA. If this occurs the results of both the application and PCA are unpredictable. Proper programming practice requires that all local event flags be allocated using LIB$GET_EF or LIB$RESERVE_EF prior to use. o The PCA Collector will fail if the program being analyzed deletes or resets virtual memory (VM) zones belonging to PCA. PCA uses the OpenVMS RTL virtual memory (VM) zone management routines to create two VM zones from which it performs all dynamic memory allocations. PCA makes heavy use of dynamically allocated memory. If an application running with the PCA Collector modifies, resets, or deletes these zones the Collector will not be able to continue executing. This situation can occur when a program obtains the zone identifier for one of the PCA zones by calling LIB$FIND_ VM_ZONE or LIB$FIND_VM_ZONE_64. Programmers using these routines must be aware that they may return information on zones not created directly by the program and take precautions to ensure such zones are not modified. It should also be noted that PCA is still executing at the time user program exit handlers are invoked; therefore, the above warnings also pertain to exit handlers. o Programs which use the LBR$ routines to access libraries must use the library index returned by LBR$OPEN in subsequent calls to other LBR$ routines. Problems have been reported where programs assume the index is a certain value rather than saving the index returned by LBR$OPEN. When the program is run with the PCA Collector the index values may be different if PCA opens help libraries before the program begins execution. On OpenVMS Alpha Systems, o When a collector data file is not specified, the collector may assign a truncated image filename as the default filename for collector data file. Note that this Restrictions 5-3 is due to the limitation with linker which support only 39 characters for image names. o Codepath data cannot be collected. o Vector data cannot be collected. o PCA does not gather system service or I/O system service data for user code which is called between a call to a system service and its return. o When both system service interception and random sampling data with stack PCs is being gathered, unnamed PCs in P0 space may appear in call chains. These will appear as hex addresses. These addresses may be caused by the PCA system service interception because the "real" system service vector has been relocated. o PCA may not correctly correlate stack PCs collected for system services or IO services when PROGRAM_ADDRESS BY LINE is selected and the program is not compiled /NOOPTIMIZE. The errors occur when multiple adjacent but non-overlapping DSTs describe the program line containing the system service or IO service call. The workaround is to compile the program /NOOPTIMIZE. On OpenVMS Integrity server Systems, o When a collector data file is not specified, the collector may assign a truncated image filename as the default filename for collector data file. Note that this is due to the limitation with linker which support only 39 characters for image names. o Ada tasking data cannot be collected. o I/O services data cannot be collected. o System services data cannot be collected. o Codepath data cannot be collected. o Vector data cannot be collected. o If any event markers have been set, or collection of execution counts has been selected, or collection of coverage data has been selected in the same run in which program counter sampling data with stack PCs is also selected, PCA may lose some stack PC data at collection 5-4 Restrictions time. When collecting data, the following message may be produced: %PCA-I-BADSTACK, stack corrupted - no further data available '........' When analyzing data collected in such a run, the following message may appear in any report produced: %PCA-S-STACKPCLOST, some stack PC data were lost at collection time and the summary section of each report may contain the line: Number of occurrences of stack corruption: n 5.2.1.1 DECwindows On all OpenVMS platforms, o Switching a context from the HP DECset Environment Manager for OpenVMS does not have any effect on the execution environment of currently invoked PCA Collector sessions. o PCA uses DECwindows help to allocate, access and control the PCA help in DECwindows, as a result the library index is never deallocated. The user program must therefore ensure that a conflict does not occur with PCA by not assuming anonymous usage and using LBR$INI_ CONTROL to allocate a library index for subsequent library operations. 5.2.1.2 User Routines On all OpenVMS platforms, o PCA will not call, or invoke, your user routine image if it is linked with warnings or errors. o You must define a logical name to access the user routine image if it is not found in SYS$SHARE. o System service routines which are invoked from user- supplied routines should be written in the C language (as referenced by the /USER_ROUTINE qualifier in the glossary of the HP DECset for OpenVMS Performance and Coverage Analyzer Reference Manual). Programs written in other languages may cause PCA to hang. Examples user routines are provided in PCA$EXAMPLES. Restrictions 5-5 5.2.2 Analyzer On all OpenVMS platforms, o The Analyzer sometimes runs out of virtual memory for very large plots (on the order of 100,000 buckets). o PCA cannot merge PCA data files with different image names. o PCA cannot merge PCA data files with identical image names and different image identifiers, link times or link identifiers except using MERGE/ANC. Only coverage- set information from the input PCA data file that can be validated by codepath information from both the input and output PCA data files will be added to the coverage-set table of the output PCA data file. 5.2.2.1 DECwindows On all OpenVMS platforms, o No graphical print support is available; however, text versions of histograms can be printed using the Save Chart button. o After choosing either the Histogram or Table from the Annotation sub-menu of the View menu, you hit the Apply button to get your selection reflected in the current chart. o If it is necessary to use Set Language for source viewing following an error while trying to view source with the right arrow VIEW button, it will be necessary to use the Apply button before being able to VIEW source again. 5.2.3 DECwindows On all OpenVMS platforms, o There is currently no customization of the user preferences. 5-6 Restrictions