HP DECset for OpenVMS Source Code 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 HP Source Code Analyzer Version 5.1-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 HP Source Code Analyzer Version 5.1-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 HP SCA with DECwindows Motif............ 1-2 1.4 Installation Requirements..................... 1-2 2 New Features 2.1 New Features in HP SCA Version 5.1-1.......... 2-1 2.2 New Features in HP SCA Version 5.1............ 2-1 2.2.1 Extended File Specifications.............. 2-1 3 Problems Fixed 3.1 Problems Fixed in HP SCA Version 5.1-1........ 3-1 3.2 Problems Fixed in HP SCA Version 5.1.......... 3-1 4 Known Problems 4.1 General....................................... 4-1 4.2 DECwindows Interface.......................... 4-2 5 Restrictions 5.1 General Restrictions.......................... 5-1 5.2 C++ Language Support.......................... 5-3 5.3 ADA Language Support.......................... 5-5 iii Tables 1-1 HP SCA Installation Requirements (Minimum)................................. 1-2 1-2 HP SCA Account Quotas..................... 1-3 iv _________________________________________________________________ Preface These release notes describe the HP Source Code Analyzer for OpenVMS (HP SCA), Versions 5.1-1 and 5.1 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 HP SCA. 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 outstanding issues. 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 pertain to HP Source Code Analyzer for OpenVMS, Versions 5.1-1 and 5.1 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 HP Source Code Analyzer Version 5.1-1 for OpenVMS is a patch release. 1.2 Associated Documents The following documents contain information related to HP SCA. The documents associated with HP SCA are: o HP DECset for OpenVMS Guide to Source Code Analyzer o HP DECset for OpenVMS Language-Sensitive Editor/Source Code Analyzer Reference Manual 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 o HP DECset for OpenVMS Guide to Language-Sensitive Editor General Information 1-1 In addition to the base HP SCA 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 HP SCA with DECwindows Motif To use HP SCA 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 HP SCA. Table_1-1_HP_SCA_Installation_Requirements_(Minimum)_______ Global Disk Space Disk Space Page/PageletGlobal Operating During After Sections System______Installation_Installation_Required____Required_ OpenVMS 41,000 39,000 35,000 30 Integrity pagelets[1] servers OpenVMS 18,500 16,500 10,000 15 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 HP SCA. 1-2 General Information Table_1-2_HP_SCA_Account_Quotas____________________________ OpenVMS Integrity Resource_Name__servers____________OpenVMS_Alpha____________ ASTLM 24 24 BYTLM 18,000 18,000 ENQLM 30 30 FILLM 20 20 TQELM 5 5 BIOLM 18 18 DIOLM 18 18 PRCLM 2 2 WSDEF 600[1] 600[1] PGFLQUOTA 30,000 30,000 [1]3,000_optimum___________________________________________ ___________________________________________________________ General Information 1-3 2 _________________________________________________________________ New Features 2.1 New Features in HP SCA Version 5.1-1 No new features have been added to HP SCA for Version 5.1- 1. 2.2 New Features in HP SCA Version 5.1 2.2.1 Extended File Specifications SCA supports creation and use of SCA library on ODS-5 disks. It provides support for long file names that have a greater range of legal characters than is available in previous versions of OpenVMS. SCA now preserves the case of file names and also provides support for deep directories. For more information on the supported characters and the limitations for file names lengths, refer to OpenVMS Guide to Extended File Specifications. New Features 2-1 3 _________________________________________________________________ Problems Fixed 3.1 Problems Fixed in HP SCA Version 5.1-1 The following problem is fixed in this release of HP SCA: WFM 1212247241-121 - An ACCVIO error occurs while importing a corrupted XREF file. 3.2 Problems Fixed in HP SCA Version 5.1 The following problem was fixed in HP SCA Version 5.1: WFM 3209806045-321 - When using the DECwindows interface on SCA to obtain a call graph that returns a fairly large diagram, the query aborts and generates a stack dump with a STKOVF (stack overflow) error. Problems Fixed 3-1 4 _________________________________________________________________ Known Problems 4.1 General The following problem exists in HP SCA Version 5.1-1: WFM 1217780073-122 - IVP fails while installing HP SCA Version 5.1-1 The Installation Verification Procedure (IVP) fails while installing HP SCA Version 5.1-1. This problem occurs because the following informational line is suppressed from the output: %SCA-I-CONNECTING, Requesting connection to 0:: The following known problems exist from HP SCA Version 5.1: o ID:582 - SCA only recognizes first call statement in HP COBOL for OpenVMS [Integrity servers and Alpha] copylib. SCA is inconsistent in finding calls to subprograms using COBOL and Copy Library files. If the call to a subprogram exists in the main program, SCA finds all occurrences of the call. However, if the call to a subprogram appears in code included with a Copy statement in a copy library, SCA will only find the first occurrence of the call. Performing a find on each of the other programs does show that the call exists. SCA ignores the 'redundant' information from the several inclusions, and presents just one occurrence of the CALL found in "copylib.txt". A workaround is to issue the "set duplicate inclusions visible" command (available only in SCA's portable-style command interface). o ID:586 - Virtual memory leaks issuing queries from callable interface. Known Problems 4-1 When queries are performed on the library using the callable interface, SCA appears to leak virtual memory. If queries are performed repeatedly this will eventually lead to the process stopping with "%LIB-F-INSVIRMEM, insufficient virtual memory". This problem covers several individual leaks many of which were fixed in SCA Version 4.6. o ID:588 - SCA INSPECT SYMBOL=ROUTINE/CHAR=TYPE may result in an error. One of the following errors may occur: o %SCA-F-BADLOGIC, internal logic error: Extra super- symbol field o %SCA-F-BADREQ, invalid argument detected: attempt to create a relationship between same node There is currently no known workaround. o ID:595 - SCA-F-BADMEM after CTRL/C. Entering CTRL/C during an EXTRACT MODULE command may result in SCA failing with an internal memory management error. o ID:606 - Different command syntax defaults. The command syntax defaults are not consistent, in DECwindows mode the default is portable and in character-cell mode the default is VMS. 4.2 DECwindows Interface The following DECwindows interface problems exist from HP SCA Version 5.1 o ID:581 - Motif interface gives BADLOGIC error on a monochrome VXT 2000. Using the SCA DECwindows interface from a Monochrome VXT 2000 to determine the type of all data structures using a wildcard causes the reporting of the BADLOGIC error and SCA to hang. The workaround is to use different display hardware or the character-cell interface. 4-2 Known Problems o ID:583 - Call Graph output file not displaying correctly in CDA viewer. If you change the default colors for the SCA DECwindows interface to have a light foreground and dark background and invoke SCA and save the output of a Call Graph, when you later attempt to display the DDIF file with the CDA viewer you will lose most of the detail. With the light foreground SCA will display the Call Graph correctly, but when you view the Call Graph file with the CDA viewer none of the connecting lines are visible and the names for the objects are truncated if they extend beyond the object circle. Workarounds include either of the following: 1. Use two colors which would show through the default window background (for example black and red, or anything other than white if you have a white background). 2. Use a dark foreground with a light background. o ID:584 - DECwindows Call Graph gives errors and consumes resources. The SCA DECwindows interface, during production of a Call Graph for a small Fortran program, reports many Motif toolkit warnings and consumes excessive memory and CPU resources. The performance of subsequent queries are also affected - eventually resulting in the hanging of SCA. The workaround is to use the character-cell interface. o ID:628 - Data Structures Compact Tree / Graph Display connections The connections to and from the fields of a record may start or finish at the wrong fields (of the correct records) for a Compact Tree or Graph display. o ID:637 - SCA call graph results are not displayed properly for more than 1500 nodes. But by defining the logicals, SCA_NODE_DISTANCE and SCA_ZOOM, call graphs having of 2500 nodes are displayed properly. Known Problems 4-3 Please refer the HP DECset for OpenVMS Guide to Source Code Analyzer for more information on using these logicals. 4-4 Known Problems 5 _________________________________________________________________ Restrictions 5.1 General Restrictions The following general restrictions exist from HP SCA Version 5.1: o Force Connection to Server The protocol version of the client/server communication code has been changed from 3.0 to 4.0. This means that SCA Version 4.7 and above will fail to connect to a server for an earlier version of SCA. For example, for SCA Client Version 4.7 and SCA Server Version 4.6: $ sca set lib abcd::sca$example: %SCA-I-CONNECTING, Requesting connection to abcd:: %SCA-E-INCOMPSERV, Incompatible server running protocol 3.0 In general, an earlier version of SCA connecting to the server is likely to have less facilities and more outstanding problems. Hence the SCA Version 4.7 and above should not be connected to the server. Connection to an earlier server (running protocol 3.0) can be forced by defining the new logical SCA$FORCE_ CONNECTION to have the value 1, for example: $ define sca$force_connection 1 $ sca set lib abcd::sca$example: %SCA-I-CONNECTING, Requesting connection to abcd:: %SCA-I-COMPSERV, Compatible server running protocol 3.0 %SCA-S-LIB, your SCA Library is abcd::SCA$EXAMPLE: o Remote Libraries Remote libraries are not supported on the Itanium platform. o 'Old' ANA and 'Bad' ANA Restrictions 5-1 If an ANA file that is seen as 'Old' or 'Bad' by SCA is successfully loaded into an SCA library then certain operations may result in the following warnings: %SCA-W-BADRELEVAL, CONTAIN, TYPE, IN, or pathname may produce incomplete result -SCA-W-BADANAFOR, library contains module(s) with old/bad ANA file format 'Old' ANA should be unlikely as this refers to ANA that was designed to work with versions of SCA prior to Version 4. 'Bad' ANA refers to ANA that is seen as incorrect but still loadable by SCA. The commonest reason for 'Bad' ANA is that the ANA contains descriptions of scopes that overlap. Some relatively recent compilers have this problem. The following example uses a maintenance facility to show the problem. It should be noted that this facility may generate similar errors for lexical- ranges that overlap suspiciously, these can be ignored. $ sca load/check SCA_QAR107.ana %SCA-W-BADFEATURE, Invalid use of non-existent feature %SCA-W-BADLOAD, error loading DISK:[DIR]SCA_QAR107.ANA;2 -SCA-W-BADANA, error loading module SCA_QAR107 -SCA-F-BADEVENT, event number 1 and -SCA-F-BADEVENT, event number 9571 have lexical-ranges that overlap illegally -SCA-I-CREATEDANA, module was created by DEC Pascal V5.6-59 %SCA-S-REPLACED, module SCA_QAR107 replaced %SCA-S-COUNT, 1 module loaded (0 new, 1 replaced) Another possible reason for 'Bad' ANA is described in the following restriction. o ANA generated from compilation of concatenated source files. ANA files generated from compilations where source files are concatenated on the compile line are not supported. Such files can be loaded into an SCA library, however, certain operations may result in an error. 5-2 Restrictions SCA can usually recognize that the ANA is 'bad' and issue a warning at load time. For example: $ sca load bad %SCA-W-BADLOAD, error loading DECSET5:[SCA]BAD.ANA;1 -SCA-W-BADANA, error loading module FOO -SCA-W-WARNING, warning: may be due to compilation of concatenated source -SCA-I-CREATEDANA, module was created by HP Fortran V6.4-165 %SCA-S-REPLACED, module FOO replaced %SCA-S-COUNT, 1 module loaded (0 new, 1 replaced) For some compilers the SHOW MODULE/FULL command 'command line' field will indicate that source concatenation was used. If SCA recognized the ANA as 'bad' this will be indicated in the 'loaded' field. For example: $ sca show module/full FOO module name : FOO type : FORTRAN module identification : 01 compiler : HP Fortran V6.4-165 command line : FORTRAN/LIST/ANALYSIS F1+F2 compiled : 24-Nov-2006 17:29 library : DECSET5:[SCA] (#1) loaded : 4-Dec-2006 14:25 (bad format) o Portable syntax command options. Many of the portable syntax commands do not implement all the options of the corresponding OpenVMS syntax commands. For example the OpenVMS syntax FIND command has nine possible qualifiers and the portable syntax FIND command only has two options. 5.2 C++ Language Support The following problems and restrictions apply to the C++ language support. o The IMPORT command will only work with XREF files generated on OpenVMS Alpha systems running HP C++ Version 6.5 or higher. OpenVMS Integrity servers Versions of HP C++ does not support HP SCA. Restrictions 5-3 o Queries using the Symbol Class terms Exception, Generic, or Label will not identify any occurrences within a program. o Templates are not described correctly. o For Compaq C++ Version 5.6 template constructs or multiple includes of a file (but not normally those excluded by conditional compilation statements) may cause the following problems: o The result of a query to be incorrect. o The analysis data file is recognized as containing invalid data. This causes all relationship queries on this module to fail with the error: -SCA-W-BADANAFOR, library contains module(s) with Bad ANA format The command SHOW MODULE can be used to identify all invalid "Bad ANA format" modules. o References to an object may not be correctly linked to the primary declaration. o Use of Typedef statements are not recognized by queries. o The Go-To-Source feature will not always select the correct character position. For Compaq C++ V5.6 include file references, the line and file may also be incorrect. o Listing line numbers are not always correct. o Visible program constructs may be incorrectly marked with the hidden attribute and hidden constructs may be visible. o The scoping information of certain statements may not be correct causing incorrect results to queries. This affects the Typing and Containing relationships. For example: o Classes or Functions declared on a single line: CLASS X { int a( char *b ); }; o Comma delimited list: int a,b[4]; 5-4 Restrictions o Queries involving destructors should have the name in quotes. For example: FIND "~abc" 5.3 ADA Language Support OpenVMS Integrity servers Versions of GNAT ADA does not support SCA. Restrictions 5-5