DECset________________________________________ Release Notes for DIGITAL MMS Version 3.3 November 1998 These release notes for DIGITAL Module Management System Version 3.3 for OpenVMS VAX and OpenVMS Alpha contain important general information, new and changed features, current restrictions and documentation notes. Operating System and Version: OpenVMS Versions 6.2, 7.1, 7.2 DECwindows Motif, Versions 1.2-3, 1.2- 4, 1.2-5 Software Version: DECset for OpenVMS, Version 12.3 Software Version: DIGITAL Module Management System for OpenVMS Systems, Version 3.3 Digital Equipment Corporation Maynard, Massachusetts __________________________________________________________ November 1998 While DIGITAL or EDS believes 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 publication 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 represen- tations that the interconnection of its products in the manner described in this publication 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. © Digital Equipment Corporation 1994, 1995, 1996, 1997, 1998. All rights reserved. © Electronic Data Systems Limited 1995, 1996, 1997, 1998. The following are trademarks of Digital Equipment Corporation: DEC Ada, DEC BASIC, DEC C, DECdocument, DECnet, DEC Pascal, DECset, DECwindows, DIGITAL, DIGITAL COBOL, DIGITAL Fortran, eXcursion, OpenVMS, OpenVMS Cluster, VAX, VAX BLISS-32, 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.1.1 Documentation ................................ 1-1 1.2 DECset Clients for CMS and MMS.................. 1-2 1.3 Installation Requirements....................... 1-4 2 New Features 3 Problems Fixed 4 Known Problems 5 Restrictions 6 Reporting Problems and Suggestions Tables 1 Conventions .................................. vi iii ________________________________________________________________ Preface These release notes characterize Version 3.3 release of DIGITAL Module Management System for OpenVMS 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 MMS 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 restrictions. o Chapter 6 describes how to report problems. v Sending DIGITAL Your Comments We welcome your comments on these release notes or on any other pieces of documentation. See Chapter 6 for details on how to contact DIGITAL with your comments. Conventions Table 1 lists the conventions used in these notes Table_1_Conventions_______________________________________ 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 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._______________________ vi 1 ________________________________________________________________ General Information The information in these release notes pertain to DIGITAL Module Management System Version 3.3. 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. 1.1 Introduction DIGITAL Module Management System Version 3.3 is a minor release. 1.1.1 Documentation The documentation of DIGITAL Module Management System and of DECset has been revised for this release. This revision corrects errors, enhances descriptions, and describes all new functionality. The document associated with DIGITAL Module Management System is: o Guide to DIGITAL Module Management System for OpenVMS Systems The revised installation guide for all DECset components is: o DECset Installation Guide for OpenVMS Systems Also applicable are the general DECset documents: o DECset OpenVMS VAX V12.3 Software Product Description o DECset OpenVMS Alpha V12.3 Software Product Description General Information 1-1 o DECset Guide to Detailed Program Design for OpenVMS Systems o Using DECset for OpenVMS Systems New with this release is the "DECset Cookbook". This document contains technical articles giving instructions on the use of DECset components in particular situations. This document is provided online, in PostScript format, and can be found in: SYS$SYSROOT:[SYSHLP.EXAMPLES.DECSET]DECSET_COOKBOOK.PS 1.2 DECset Clients for CMS and MMS DECset Clients for CMS and MMS provides access from the desktop personal computer (PC) to the DIGITAL Code Management System libraries and DIGITAL Module Management System (MMS) features residing on OpenVMS Alpha and OpenVMS VAX systems. DECset Clients for CMS and MMS is a separate product from DECset for OpenVMS, DIGITAL CMS and DIGITAL MMS. DECset Clients for CMS and MMS can be used from a personal computer running Microsoft Windows 95, Microsoft Windows 98 or Windows NT. Use of MMS from the PC is possible once the Server software (provided with the Client) and the MMS for OpenVMS software are installed at the server site. The main DECset Clients window offers menu access to most of the CMS and MMS functions. DECset Clients commands can also be performed by clicking the command buttons on the toolbars. The MMS Client supports the use of the MMS generator to produce a description file for source files resident on the OpenVMS server. It also supports the viewing, editing and execution of description files. Description files are executed on the remote OpenVMS system. Thus, OpenVMS builds can be managed from the PC. Additional information on DECset Clients for CMS and MMS can be found in the documents: o DECset OpenVMS VAX V12.3 Software Product Description o DECset OpenVMS Alpha V12.3 Software Product Description and on the OpenVMS web pages: 1-2 General Information http://www.openvms.digital.com/commercial/ General Information 1-3 1.3 Installation Requirements OpenVMS Alpha systems For a new installation of MMS the following is required: Global Pages 1000 Global Sections 6 Disk Blocks 6500 OpenVMS VAX systems For a new installation of MMS the following is required: Global Pages 600 Global Sections 8 Disk Blocks 4000 1-4 General Information 2 ________________________________________________________________ New Features The following enhancements were added to DIGITAL Module Management System for Version 3.3: A new qualifier, /EXTENDED_SYNTAX, has been added that enables two extensions to the syntax of MMS description files. These are: o Use of predefined MMS functions o Macro redefinition Predefined functions can be used in MMS description files to perform various text processing operations and for computing the names of files on which to operate. These functions perform: o text substitution o text search o wildcard expansion for files MMS now supports the redefinition of macros. The macro interface for MMS will remain the same as it is now, except that macro values can be redefined. The description of these features can be found in sections 2.3.3 and 2.3.7 of the Guide to DIGITAL Module Management System for OpenVMS Systems. An "Extended_Syntax" check box has been added to the DECwindows MMS Build Definitions/Directives Options dialog box for enabling the /EXTENDED_SYNTAX qualifier. Where appropriate, any future extensions made to the syntax of MMS description files may also be enabled by this qualifier. By default, or by using the inverse qualifier (/NOEXTENDED_SYNTAX), MMS will continue to support the syntax of Version 3.2. New Features 2-1 3 ________________________________________________________________ Problems Fixed The following bugs were fixed and restrictions removed in MMS Version 3.3: o Bug 14 - MMS used to split long DCL commands incor- rectly. This problem has been corrected. o Bug 20 - MMS failed to issue RMS errors messages when trying to open a file that can't be opened. This problem has been corrected. o Bug 30 - The MMS Description File Generator generated a nonsensical COMPLETE_APPLICATION rule. This problem has been corrected. o Bug 40 - The Description File Generator used to generate erroneous "Files not found" errors. MMS no longer generates "Files not found" errors where no definition is found for a referenced routine. o Bug 45 - Description File Generator failed to recognize the C #include directive for including text modules. This problem has been corrected. o Bug 47 - Description File Generator failed to list dependency on function's source file. This problem has been corrected. o Bug 49 - Angle brackets in directory specification caused MMS to issue a %MMS-W-GENERR error. This problem has been corrected. o Bug 50 - Description File Generator issued a %SCN-F- SUBSTRERR error caused by C printf call. This problem has been corrected. o Bug 51 - When using CMS Libraries, the Description File Generator failed to identify C RTL files. This problem has been corrected. Problems Fixed 3-1 o Bug 53 - Description File Generator did not handle Pascal environment files correctly. This problem has been corrected. o Bug 54 - Description File Generator error, a Pascal module declared in an environment file was omitted from the link command. This problem has been corrected. o Bug 56 - The Description File Generator issued "%SCN- F-TRENODNOT, Tree node does not exist" error messages. This problem has been corrected. o Bug 57 - The Description File Generator issued %MMS-F- GENERR errors in initialization routines. This problem has been corrected. o Bug 88 - The following errors occurred when processing a description file that contains references to CDD elements: CDD-E-NOXFND, protocol not supported by translator: CDD$FORM MMS-F-CDDPLUSERR, Error returned from CDD/PLUS This problem has been corrected. o Bug 97 - Access violation occurred when file name is NULL macro. This problem has been corrected. o Bug 103 - MMS failed with errors CDD-E-NOXFND and MMS-F-CDDPLSERR. This problem has been corrected. o Bug 104 - The macro MMS$CHANGED_LIST ($?) was expanded correctly. This problem has been corrected. o The following documentation problems are addressed in the revised Guide to DIGITAL Module Management System for OpenVMS Systems issued with this release: o Bug 38 - Default description file name is MAKEFILE. not MAKEFILE.MMS. o Bug 43 - Missing parenthesis in example 3-4. 3-2 Problems Fixed 4 ________________________________________________________________ Known Problems The following problems are known to exist in MMS Version 3.3: o Bug 42 - Installation: FMS related linker warnings when DECwindows is not installed. Installing MMS on systems without DECwindows, but with FMS, may cause linker warnings to occur. The Link-time Warnings are generated at installation time due to undefined FMS symbols, the warnings include: fdv$$plidispatch sys$common:[syslib]starlet.olb fdv$$plitrm sys$common:[syslib]starlet.olb The warnings can safely be ignored. o Bug 48 - Linker information defined in a context is ignored. The Environment Manager (via the MMS Options menu in the Settings pull down menu) allows the specification of Linker Object Libraries and Linker Options. However, these settings are not picked up by MMS when generating description file or building programs. Therefore, even though the context has the following defined: Object library in generated MMS description files: Linker object library: $DISK$:[DECSET]TEST.OLB; Linker options files: $DISK$:[DECSET]DECC.OPT The object library and options file must still be set in the MMS Description File Generator window. There is no known workaround for this problem. Known Problems 4-1 o Bug 102 - The File Generator Sources, Additional Link Libraries and Options Files window is too large to fit on small display screens. o Bug 106 - Action line prefixes do not work with the `kind feature. The action line prefixes (@ and -) can not be used with action lines associated with the `kind_FIRST and `kind_ GETTIME rules for obtaining the timestamps of user- defined objects. The prefix characters will be treated as part of the action to be performed. Apart from the use of the .SILENT directive to suppress output of all action lines, there is no known workaround for this problem. 4-2 Known Problems 5 ________________________________________________________________ Restrictions The following restrictions apply to MMS Version 3.3: o More than one description file, separated by commas or plus signs, will not work with the Motif interface. Only the first description file listed will be displayed in the description file area. Only the first description file will be used in the MMS command. o Restriction on size of search list MMS will propagate to the subprocess. The problem is not really within MMS, but rather in DCL, which has an undocumented restriction on the size of a process logical name search list that can be successfully copied to a subprocess. DCL's SPAWN command would show the message: %DCL-W-SYMTOOLNG, symbol is too long to copy to subprocess The problem can be worked around by using several smaller logical name search lists, or by putting the logical names in a job-wide logical name table, which is shared with (not copied to) the subprocess. o CMS library search lists are not completely supported with the MMS Motif interface of the Description File Generator. A comma-separated list specified in the CMS Library text field does not get processed properly; only the first library listed will be used. However, if a CMS library search list is set before invoking MMS, even though the CMS Library text field does not reflect the multiple libraries, the complete CMS library search list will be used for the input source list. Restrictions 5-1 o Changing fonts may cause buttons to disappear in the Sources, Additional Link Libraries, and Options Files dialog boxes. o For OpenVMS Alpha Motif interface: - When an MMS build is completed, the informational dialog box informing the user of the build completion does not appear. This is different behavior than the OpenVMS VAX version. o The following restrictions apply to MMS for support of FMS libraries. - Support in MMS for FMS libraries will be determined during the installation of MMS. If FMS is installed on the system when MMS is being installed, MMS will contain support for FMS. If FMS is not installed on the system when MMS is being installed, MMS will not contain support for FMS. - If FMS is installed on a system after MMS has been installed without FMS support, then MMS will have to be reinstalled in order to contain FMS support. - If FMS is removed from a system, MMS will have to be reinstalled in order to remove FMS support. MMS will access violate if there is an attempt to use FMS libraries. - If a new version of STARLET.OLB is installed on a system, MMS will have to be reinstalled so it reflects any changes in the new version of STARLET.OLB. MMS may access violate if FMS has not been installed with the new version of STARLET.OLB. - MMS with FMS support may crash with an access violation if the FMS shareable images are not installed as known images. If MMS fails to run correctly when FMS is installed on the system, ensure that the FMS shareable images are installed as known images; this is achieved by executing the commands: $install add/open/share SYS$LIBRARY:FDVSHR $install add/open/share SYS$MESSAGE:FDVMSG 5-2 Restrictions Both of the shareable images must be installed in order for FMS to function properly. Restrictions 5-3 6 ________________________________________________________________ Reporting Problems and Suggestions Depending on the nature of the request or problem, customers can call DIGITAL provided their software contract and warranty entitles them to telephone support. Review the SPD and Warranty Addendum for an explanation of warranty. If a problem is encountered during the warranty period, customers can report the problem using DSNlink. In the United States, customers can call the DIGITAL Customer Support Center at 1-800-354-9000. In addition, DIGITAL provides access to Web Information and Support (WIS), an Internet-based electronic services application that allows customers 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. Dial-In Access (DIA) users can access WIS by: 1. Opening http://www.service.digital.com/wis. 2. Choosing a country code. 3. Entering DIA Access ID and password. WIS and DIA use the same underlying account and directory on the DIGITAL Customer Support Center host system. Customers can register for DIA and receive a WIS account by contacting their Customer Support Center or local DIGITAL representative. This method can also be used to make requests for additional features or modifications to existing features. When submitting a request, please include the following information: Reporting Problems and Suggestions 6-1 o The version of MMS and type of OpenVMS operating system. o Problem Summary. o Stack dumps or error logs (if applicable). o Files in machine-readable media: magnetic tape (preferred), floppy diskette, or tape cassette. 6-2 Reporting Problems and Suggestions