DECset________________________________________ Release Notes for PCA Version V4.5-4 August 1997 These are the release notes for DIGITAL Performance and Coverage Analyzer V4.5-4 on OpenVMS Alpha and OpenVMS VAX. These release notes contain important general information, new and changed features, current restrictions, and documentation notes. Operating System and Version: OpenVMS VAX, Versions 5.5 - 7.1 OpenVMS Alpha, Versions 6.1 - 7.1 DECwindows Motif, Versions 1.1 - 1.2 Software Version: DECset for OpenVMS, Version V12.2 Software Version: DIGITAL Performance and Coverage Analyzer for OpenVMS, Version V4.5-4 Digital Equipment Corporation Maynard, Massachusetts __________________________________________________________ August 1997 While DIGITAL and EDS believe the information included in this publication is correct as of the date of publication, it is subject to change without notice. Possession, use, or copying of the software described in this documentation is authorized only pursuant to a valid written license from DIGITAL, an authorized sublicensor, or the identified licensor. Digital Equipment Corporation or EDS makes no repre- sentation that the interconnection of its products in the manner described in this document will not infringe existing or future patent rights, nor do the descriptions contained in this document imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Copyright © Digital Equipment Corporation 1992, 1993 1996, 1997. All Rights Reserved. Copyright © Electronic Data Systems Limited 1994, 1996, 1997. The following are trademarks of Digital Equipment Corporation: DEC Ada, DEC BASIC, DEC C, DEC COBOL, DECdocument, DECnet, DEC Pascal, DECset, DECwindows, DIGITAL, DIGITAL FORTRAN, OpenVMS, VAX, VAX Ada, VAX BLISS-32, VAXcluster, VAX COBOL, VAX DOCUMENT, and the DIGITAL logo. All other trademarks and registered trademarks are the property of their respective holders. This document was prepared using VAX DOCUMENT, Version 2.1. ________________________________________________________________ Contents Preface.................................................. v 1 General Information 1.1 Introduction.................................... 1-1 1.2 Documentation................................... 1-1 1.3 Installation.................................... 1-1 1.3.1 Documentation ................................ 1-2 1.3.2 Performance Hints ............................ 1-2 1.3.3 Installation Requirements .................... 1-2 2 New Features 2.1 New Features in PCA V4.5-4...................... 2-1 2.2 Undocumented New Features in Previous PCA Releases........................................ 2-1 2.2.1 Support for language C++ ..................... 2-1 2.2.2 Improved user interface selection ............ 2-2 2.2.3 Improved Pathname Support .................... 2-3 2.2.4 Added vector data collection documentation ... 2-3 2.2.5 Improved DECwindows interface (Alpha) ........ 2-3 2.2.6 User Routine support ......................... 2-4 2.2.7 New LIST command qualifiers .................. 2-4 2.2.8 Small Screen Support ......................... 2-4 2.2.9 New Data Collection (Alpha) .................. 2-5 2.2.10 New Analyzer Node Specifications (Alpha) ..... 2-5 2.2.11 New PLOT qualifiers (Alpha) .................. 2-6 2.2.12 Ada Tasking support (Alpha) .................. 2-6 2.2.13 I/O Service Data (Alpha) ..................... 2-6 2.2.14 Page Fault Data (Alpha) ...................... 2-7 2.2.15 System Service Data (Alpha) .................. 2-7 iii 3 Problems Fixed 3.1 OpenVMS Alpha systems........................... 3-1 3.2 OpenVMS VAX systems............................. 3-2 4 Known Problems 4.1 OpenVMS Alpha systems........................... 4-2 4.2 OpenVMS VAX systems............................. 4-2 5 Documentation Corrections 6 Restrictions 6.1 Collector....................................... 6-1 6.1.1 DECwindows ................................... 6-3 6.1.2 OpenVMS Alpha systems ........................ 6-3 6.1.3 OpenVMS VAX systems .......................... 6-3 6.1.4 User Routines ................................ 6-4 6.2 Analyzer........................................ 6-4 6.2.1 DECwindows ................................... 6-4 6.2.2 OpenVMS VAX systems .......................... 6-5 6.3 DECwindows...................................... 6-5 7 Reporting Problems and Suggestions Tables 1 Conventions Used ............................. vi iv ________________________________________________________________ Preface These release notes characterize DIGITAL Performance and Coverage Analyzer (PCA) V4.5-4 on the OpenVMS Alpha and OpenVMS VAX operating systems. These notes contain information that either supplements or supersedes the information in the DECset documentation set. Intended Audience These release notes are intended for any user or system manager who needs information on PCA for the OpenVMS platform. 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 all problems resolved by the current release. o Chapter 4 describes all outstanding issues in the current release. o Chapter 5 describes all documentation problems. o Chapter 6 describes all restrictions o Chapter 7 describes how to report problems v Associated Documents For more information on the DIGITAL Performance and Coverage Analyzer refer to the following documents: o DECset OpenVMS VAX V12.2 Software Product Description o DECset OpenVMS Alpha V12.2 Software Product Description o DECset Guide to Detailed Program Design for OpenVMS Systems o Using DECset for VMS Systems o Guide to DEC Performance and Coverage Analyzer for OpenVMS Systems o DEC Performance and Coverage Analyzer for OpenVMS Reference Manual o DEC Performance and Coverage Analyzer for OpenVMS Command-Line Interface Guide Sending DIGITAL Your Comments We welcome your comments on these release notes or on any other pieces of documentation. See Chapter 7 for details on how to contact DIGITAL with your comments. Conventions Table 1 lists the conventions used in these notes Table_1_Conventions_Used__________________________________ Convention__________Description___________________________ $ A dollar sign ($) represents the OpenVMS DCL system prompt. In interactive examples, a key name enclosed in a box indicates that you press a key on the keyboard. (continued on next page) vi Table_1_(Cont.)_Conventions_Used__________________________ Convention__________Description___________________________ 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 text user 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). 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 1.1 Introduction The information in these release notes pertain to DIGITAL Performance and Coverage Analyzer (PCA) V4.5- 4. DIGITAL 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. DIGITAL Performance and Coverage Analyzer (PCA) V4.5-4 is a maintenance release. 1.2 Documentation o The documentation, written for OpenVMS VAX systems, is unchanged for OpenVMS Alpha systems. As a consequence, several references for VAX should be considered references for Alpha as well. o Several kinds of data gathering are not supported on both OpenVMS Alpha and OpenVMS VAX systems. As a consequences the documentation describes the gathering and reporting of that data. See Chapter 6 for a list of these data types. 1.3 Installation General Information 1-1 1.3.1 Documentation The installation guide for PCA is contained within the DECset Installation Guide for OpenVMS Systems. 1.3.2 Performance Hints DIGITAL recommends the following if the DECwindows interface is used, the following figures are approximate and are the minimum recommendations. o Modify the user's WSQUOTA to 512. o Modify the user's WSEXTENT to 3100. 1.3.3 Installation Requirements o To use the PCA Motif interfaces you must have previously installed OpenVMS DECwindows Motif Version 1.1 or higher. o PCA must be re-installed after an OpenVMS upgrade as the PCA collector links against the system. OpenVMS Alpha systems o Prerequisite version of OpenVMS Alpha is Version 6.1 or higher. o For a new installation of PCA the following is required: Global Pagelets 3500 Global Sections 10 Disk Blocks 40000 OpenVMS VAX systems o Prerequisite version of OpenVMS VAX is Version 5.5 or higher. o For a new installation of PCA the following is required: Global Pages 1400 Global Sections 10 Disk Blocks 23000 1-2 General Information 2 ________________________________________________________________ New Features The following is a brief summary of enhancements added to the DIGITAL Performance and Coverage Analyzer (PCA). 2.1 New Features in PCA V4.5-4 o The following new LIST command qualifiers are supported: /DMT /GST o File specifications containing DECnet/OSI Phase V nodenames are supported. 2.2 Undocumented New Features in Previous PCA Releases 2.2.1 Support for language C++ The following commands control selection of language C++: o CANCEL LANGUAGE o SET LANGUAGE C_PLUS_PLUS o SHOW LANGUAGE o PCA Analyzer DECwindows Menu Options\Set Language... The following commands provide support for C++ pathnames and node specifications (including case-sensitive support): o CANCEL COUNTERS o CANCEL COVERAGE o CANCEL EVENTS o CANCEL FILTERS New Features 2-1 o PLOT o SET COUNTERS o SET COVERAGE o SET EVENTS o SET FILTERS o SEARCH o SHOW SYMBOL o TABULATE For additional information see PCA help topics Program_ Address_Domain Pathname and SET LANGUAGE Parameters. 2.2.2 Improved user interface selection The PCA Analyzer supports user interface selection via command qualifiers or logical names (using the existing syntax). The following new PCA command qualifiers are supported: /INTERFACE /INTERFACE=CHARACTER_CELL /INTERFACE=DECWINDOWS /INTERFACE=MOTIF The following new logical name is supported: PCAA$DECW$DISPLAY The PCA Collector supports user interface selection only via logical names (using the existing syntax). The following new logical name is supported: PCAC$DECW$DISPLAY For additional information see DCL help topic PCA /INTERFACE and PCA help topic Logical_Names. 2-2 New Features 2.2.3 Improved Pathname Support The following changes were made to pathname syntax support: o Extended quoted token syntax to include support for new characters and allow both single and double quoted strings. o Extended unquoted token syntax to include new characters. o Extended separator syntax for Ada. o Extended case-sensitive support. o Added %LABEL syntax. o Added %NAME syntax. o Improved accuracy of error reporting. For additional information see PCA help topics Program_ Address_Domain Pathname and SEARCH Parameters. 2.2.4 Added vector data collection documentation Documentation on instrumenting vector programs with PCA has been added in the PCA help topic Vectors System_ Configurations. 2.2.5 Improved DECwindows interface (Alpha) PCA Collector o collection naming (i.e. SET RUN_NAME, SET NOTE) o setting coverage node specifications o setting counters node specifications o setting sampling AST intervals o selecting shareable images as the focus of collection (i.e. SET DATAFILE/SHAREABLE) o collecting call tree information PCA Analyzer o analyzing call tree information New Features 2-3 2.2.6 User Routine support The following PCA Collector commands support the new /USER_ROUTINE qualifier: SET IO_SERVICES SET SERVICES 2.2.7 New LIST command qualifiers The following new LIST command qualifiers are supported: /[NO]START_TIME /[NO]SEQUENCE_NUMBERS /[NO]LOST_DATA /LOST_DATA=PCA /LOST_DATA=NONE /LOST_DATA=ALL /LOST_DATA=USER 2.2.8 Small Screen Support Support for various size video displays has been added to V4.3-4. The DECwindows interface to PCA has been modified to use a X/Motif resource files to specify default values for DECwindows resources. These resources include text fonts, main window sizes and other X/Motif window resources. Using a resource file allows the DECwindows interface to be customized for various video displays. An example of this is when using eXcursion to display the DECwindows interface to PCA on a PC display. Sometimes the PC display is not large enough to totally display all the windows for PCA DECwindows interface. In this case, the sizes of the windows and the fonts used by PCA can be modified by specifying new values for the resources in the X/Motif resource file. The modified resource files for PCA are: o PCA Collector - PCAC.DAT o PCA Analyzer - PCAA.DAT These files are installed in the directory DECW$SYSTEM_ DEFAULTS. A user may override the resource file in the DECW$SYSTEM_DEFAULTS directory by creating a local copy of the resource file in the directory DECW$USER_DEFAULTS. This local copy can then be modified to tailor the 2-4 New Features DECwindows interface to the user's requirements. Refer to each resource file for a list of the various resources that can be modified for PCA. 2.2.9 New Data Collection (Alpha) The following data may now be gathered on OpenVMS Alpha systems: Ada tasking I/O System Services Page Faults System Services PC and CPU sampling of User Mode ASTs 2.2.10 New Analyzer Node Specifications (Alpha) The following PCA Analyzer node specifications are now valid on OpenVMS Alpha systems: TASK BY TASK_IDENTIFIER TASK_IDENTIFIER BY task-id TASK_TYPE BY TASK_TYPE_NAME TASK_TYPE_NAME task-type TASK_PRIORITY BY [n] PRIORITY_UNITS IO_SYSTEM_SERVICE BY IO_SERVICE IO_SERVICE io-service-name FILE_NAME BY FILE FILE_VBN BY [n] BLOCKS PHYSICAL_IO_COUNT BY [n] COUNTS READ_COUNT BY [n] COUNTS RECORD_SIZE BY [n] BYTES WRITE_COUNT BY [n] COUNTS SYSTEM_SERVICE BY SERVICE SERVICE service-name New Features 2-5 2.2.11 New PLOT qualifiers (Alpha) The following PLOT command qualifiers are now valid on OpenVMS Alpha systems: /[NO]CREATOR_PC /[NO]PARENT_TASK /TASK_SWITCH /IO_SERVICES /PHYSICAL_IO_COUNT /READ_COUNT /WRITE_COUNT /FAULT_ADDRESS /PAGE_FAULTS /SERVICES 2.2.12 Ada Tasking support (Alpha) Complete Ada Tasking data support on OpenVMS Alpha systems: PCA Collector o CANCEL TASKING command. o SHOW TASKING command. o SET TASKING command. PCA Analyzer o Support for Ada Tasking data in the collection run description. o Support for LISTing Ada Tasking data. o Support for FILTERing Ada Tasking data. 2.2.13 I/O Service Data (Alpha) Complete I/O System Services data support on OpenVMS Alpha systems: 2-6 New Features PCA Collector o CANCEL IO_SERVICES command. o SHOW IO_SERVICES command. o SET IO_SERVICES command. PCA Analyzer o Support for I/O System Services data in the collection run description. o Support for LISTing I/O System Services data. o Support for FILTERing I/O System Services data. 2.2.14 Page Fault Data (Alpha) Complete Page Fault data support on OpenVMS Alpha systems: PCA Collector o CANCEL PAGE_FAULTS command. o SHOW PAGE_FAULTS command. o SET PAGE_FAULTS command. PCA Analyzer o Support for Page Fault data in the collection run description. o Support for LISTing Page Fault data. o Support for FILTERing Page Fault data. 2.2.15 System Service Data (Alpha) Complete System Services data support on OpenVMS Alpha systems: PCA Collector o CANCEL SERVICES command. o SHOW SERVICES command. o SET SERVICES command. New Features 2-7 PCA Analyzer o Support for System Services data in the collection run description. o Support for LISTing System Services data. o Support for FILTERing System Services data. 2-8 New Features 3 ________________________________________________________________ Problems Fixed o Bug 87: %PCA-F-PCAERR error occurs when Ada Package Name and C Filename Match. o Bug 101: %PCA-F-PCAERR, internal PCA coding error, PCA$COLLECTOR_MAIN. o Bug 167: ACCVIO occurs in the PCA Analyzer when MERGE /ANC is specified for datafiles which report the PCA- E-IMGFILMIS message when using either the MERGE or SET DATAFILE/APPEND commands. o Bug 170: LIST/DST output for PSECT sizes is incorrect. o Bug 174: %PCA-F-INTERR, internal PCA error in PCADFILE\PCA$FILE_INIT. o Bug 178: SET [IO_]SERVICE/USER_ROUTINE=(FOO\SHR,X,Y) attempts to use FOO as a shareable image name rather than reporting a syntax error on the filespec. o Bug 179: %PCA-F-INTERR, internal PCA error in PCAAMERGE\MERGE_PD_INPUT_FILE_NLS 1. 3.1 OpenVMS Alpha systems o Bug 171: On systems running versions of the OpenVMS Alpha operating system prior to V7 PCA does not always collect data on/near lines which have a breakpoint set (for COUNTERS/COVERAGE/EVENT) on an instruction which is emulated. o Bug 173: %PCA-F-PCAERR, internal PCA error in PCACDFILE\PCA$FILE_CREATE 10. o Bug 189: Collector reports Unaligned data is gathered before collection has started. Problems Fixed 3-1 3.2 OpenVMS VAX systems o Bug 169: LIST/DST output for MACRO is incorrectly leveled. 3-2 Problems Fixed 4 ________________________________________________________________ Known Problems o Source line with multiple PC ranges can cause miss reporting. The Analyzer does not properly assign the PC ranges to Source line with multiple PC ranges. In fact, it simply ignores all ranges after the first. This occurs much more frequently on Alpha system than on VAX systems due to the more extensive optimizations performed by the RISC system compilers. The net result is that data points will be assigned to the summary line: Data count not in defined buckets: for "BY LINE" plots which are not assigned to that summary line for "BY MODULE" plots. For COUNTER and COVERAGE data the problem can be safely ignored. It simply means that the Collector put a breakpoint down multiple times for the same line. For other data it means that the attribution of those data points cannot be determined at a granularity smaller than a routine. And if the percentage is very large, the analysis of the data becomes suspect. Compiling the program /NOOPTIMIZE will greatly reduce the occurances of this behavior in most cases. o Bug 106: The PCA Analyzer command TABULATE/CHAIN_NAME /ALPHABETICAL does not properly sort long call chain names. Known Problems 4-1 4.1 OpenVMS Alpha systems o Bug 160: I/O system services (and probably system services) are charged against the wrong line on Ada tasking programs on OpenVMS Alpha. o Bug 172: Prior to OpenVMS Alpha V7.0 PCA incorrectly marks lines as covered when collecting COUNTERS BY LINE. 4.2 OpenVMS VAX systems o Bug 83: PCA data corruption occurs with FORTRAN statement functions. o Bug 112: The PCA Collector locks up when calling user routines which call system services not written in C after intercepting a system service. 4-2 Known Problems 5 ________________________________________________________________ Documentation Corrections o Bug 147: The command SET COMMAND, which is documented in the DEC Performance and Coverage Analyzer for OpenVMS Reference Manual, is now obsolete. Documentation Corrections 5-1 6 ________________________________________________________________ Restrictions 6.1 Collector o PCA cannot gather data from any user program which calls SYS$EXIT directly or indirectly from its own exit handler, because it will not allow the Collector to close its data file correctly. Issuing SYS$EXIT from an exit handler will suppress the execution of the remaining exit handlers of that mode. Since PCA's exit handler runs after the user's exit handler, PCA's exit handler does not run at all in this situation, and the data file is not closed properly. As a result, the data gathered is lost. Two RTL routines that we know call SYS$EXIT are LIB$RUN_PROGRAM and LIB$DO_COMMAND. o The Collector is not AST re-entrant during program exit. PCA's exit handler cleans up and closes the data file. If an AST should fire during that time, the program's behavior is unpredictable. To avoid this situation, the user program should make sure there are no pending ASTs. 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 PCA's system service interception because the "real" system service vector has been relocated. Restrictions 6-1 o User programs must not use event flags which have not been allocated by LIB$GET_EF. If a user program uses event flags which are being used concurrently by PCA the results of both the user program and PCA will be unpredictable. o Users whose programs utilize the OpenVMS run-time library (RTL) heap storage management routines should be aware that PCA also utilizes these routines for dynamic memory allocation. PCA allocates memory from its own zones, so there will be no interaction between PCA and user programs which use either their own zones or the default zone. User programs should perform operations only on those VM zones which they create or the default zone. If a user program deletes or resets the zones used by PCA the results will be unpredictable. The data collected by PCA will be incomplete and possibly corrupted, indeterminate error messages may be issued, and the process may appear to hang. It is important to be aware that LIB$FIND_VM_ZONE and LIB$FIND_VM_ZONE_64 may return identifiers for zones which were not created by the user program, including those created by PCA. Any user program which calls these routines must take care not to modify, reset, or delete zones it did not create. 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 PCA does not correctly correlate stack pcs collected for services or IO services when PROGRAM_ADDRESS BY LINE is selected and the program in not compiled /NOOPTIMIZE as multiple adjacent but non overlapping DSTs describe the system service call line. The workaround is to compile the program /NOOPTIMIZE. o Programs which use the LBR$ routines must use only the library index returned by LBR$OPEN in subsequent calls to other LBR$ routines. Because PCA uses these routines to access help libraries, a program which makes assumptions about the value of the library index 6-2 Restrictions may fail unexpectedly and/or corrupt the PCA help library when run with PCA. An example of incorrect programming technique is assuming that the first library opened by the user program will be assigned an index = 1. 6.1.1 DECwindows o Switching a context from the DECset Environment Manager 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 anoymonous usage and using LBR$INI_CONTROL to allocate a library index for subsequent library operations. 6.1.2 OpenVMS Alpha systems o Codepath data cannot be collected. o Vector data cannot be collected. o No support is provided for intercepting system services from resident images prior to OpenVMS Alpha, Version 6.2 and PCA Version V4.4-3. Users prior to this can intercept system services from resident images by using the following workaround: $ DEFINE/USER SYS$SHARE:.EXE; 6.1.3 OpenVMS VAX systems o PCA does not gather system service or I/O system service data for nested system service calls (e.g. system services calls in an action routine called from CLI$DCL_PARSE). o Unaligned access fault data cannot be collected. Restrictions 6-3 o PCA may generate errors analyzing PLI programs compiled with the /CHECK qualifier. The workaround is to compile the program without /CHECK before running it with PCA. 6.1.4 User Routines 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 A system service routine which is invoked from a user- supplied routine should be written in the C language (as referenced by the /USER_ROUTINE qualifier in the glossary of the DEC Performance and Coverage Analyzer for OpenVMS Reference Manual). If written in some other languages, it may have the effect of locking up PCA. Examples are provided in PCA$EXAMPLES. 6.2 Analyzer 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. 6.2.1 DECwindows o No graphical print support is available, however, text versions of histograms can be printed using the "Save Chart" button. 6-4 Restrictions 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, because an error occurred when 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. 6.2.2 OpenVMS VAX systems o PCA cannot merge an SPM performance data file with a PCA data file that has previously collected data for a Shareable image. 6.3 DECwindows o There is currently no customization of the user preferences. Restrictions 6-5 7 ________________________________________________________________ Reporting Problems and Suggestions Depending on the nature of the request or problem and the type of support you have, you can call DIGITAL if your software contract or warranty agreement entitles you to telephone support. Review the SPD and Warranty Addendum for an explanation of warranty. If you encounter a problem during the warranty period, report the problem preferably using electronic means such as DSNlink. In the United States, customers can call the DIGITAL Customer Support Center at 1-800-354- 9000. In addition, DIGITAL now provides access to Web Information and Support (WIS), a new electronic delivery application that allows you to submit electronic service requests, access databases, download patch kits, transfer files from DIGITAL, and connect to global notes conferences via the World Wide Web. If you are an entitled service customer with access to the Web, you can now use your favorite browser to connect to electronic services through an easy-to-use, graphical interface. If you are already a DIA user, you can gain access to WIS by: 1. Opening http://www.service.digital.com/wis. 2. In the United States, clicking on the words "United States". 3. Entering your DIA Access ID and password. WIS and DIA use the same underlying account and directory on the DIGITAL Customer Support Center host system. Reporting Problems and Suggestions 7-1 If you are not already registered for DIA, you can register for a WIS account by contacting your Customer Support Center or local DIGITAL representative. This method should also be used to make requests for additional features or modifications to existing features. When submitting a report, please include the following information: o The versions of PCA and the OpenVMS operating system being used. o The problem reduced to as small a size as possible trying not to overlook any details. If the problem is with the PCA Collector: o Does the program run GO/NOCOLLECT? o Does the program run with the VMS debugger? o If Counters, Coverage, or Events are involved, does the program behave properly when breakpoints are put in the same locations with the VMS debugger? o Please supply the version of the compiler(s) used. o Files needed to build the program, including build procedures. If the problem is with the PCA Analyzer: o The .PCA file involved o The sources referenced by the .PCA file o A PCA initialization file to reproduce the problem. o Any stack dumps that occurred, if applicable. o All files should be submitted on machine-readable media (magnetic tape, floppy diskette, or tape cassette). If an error occurs while you are running PCA and you have reason to believe that the error is due to a problem in PCA, and you have a support contract, contact your DIGITAL support representative. Otherwise, contact your DIGITAL account representative or your authorized reseller. This 7-2 Reporting Problems and Suggestions method should also be used to make requests for additional features or modifications to existing features in PCA. When reporting a problem, please include the following information: o The version of PCA and the VMS operating system being used. o As complete a description of the problem as possible, trying not to overlook any details. o The problem reduced to as small a size as possible. o All file should be submitted on machine-readable media (magnetic tape `*preferred`*, floppy diskette, or tape cassette). o Any stack dumps that occurred, if applicable. Reporting Problems and Suggestions 7-3