HP_DECset_for_OpenVMS_______________________________ Module Management System for OpenVMS Release Notes August 2003 These release notes describe important general information, new and changed features, current restrictions, and documentation notes that pertains to the Module Management System Version 3.5 for OpenVMS software. Operating System Version: HP OpenVMS VAX Version 6.2, 7.2, or 7.3 HP OpenVMS Alpha Version 6.2, 7.2-2, or 7.3-1 Software Version: HP DECset Version 12.5 for OpenVMS Module Management System Version 3.5 for OpenVMS Hewlett-Packard Company Palo Alto, California ________________________________________________________________ © 2003 Hewlett-Packard Development Company, L.P. Microsoft, Windows, Windows NT, and Visual C++ are U.S. registered trademarks of Microsoft Corporation. Motif is a trademark of The Open Group in the United States and other countries. Confidential computer software. Valid license from HP and/or its subsidiaries 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 vendors standard commercial license. Neither HP nor any of its subsidiaries shall be liable for technical or editorial errors or omissions contained herein. The information in this document is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for HP products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty. _________________________________________________________________ Contents Preface................................................... v 1 General Information 1.1 Introduction..................................... 1-1 1.2 Associated Documents............................. 1-1 1.3 Associated Products.............................. 1-2 1.4 Using MMS with DECwindows Motif.................. 1-3 1.5 Installation Requirements........................ 1-3 2 New Features 2.1 Improved Conditional Processing.................. 2-1 2.2 MMS$SEVEREST_STATUS Symbol....................... 2-4 2.3 Suffixes Precedence List Directives.............. 2-4 3 New Features in Version 3.4 3.1 MMS Generator Qualifier - /SWITCHES.............. 3-2 3.2 MMS Generator Qualifier - /BUILTIN_RULES_APPLY... 3-2 3.3 Additional Predefined Functions.................. 3-2 3.3.1 Function Parameters ........................... 3-3 3.3.2 The Functions ................................. 3-3 3.3.2.1 Text operations............................. 3-3 3.3.2.1.1 ADDPREFIX ................................ 3-3 3.3.2.1.2 ADDSUFFIX ................................ 3-3 3.3.2.1.3 FILTER ................................... 3-3 3.3.2.1.4 FILTER-OUT ............................... 3-4 3.3.2.1.5 FINDSTRING ............................... 3-4 3.3.2.1.6 FIRSTWORD ................................ 3-4 3.3.2.1.7 FOREACH .................................. 3-4 3.3.2.1.8 JOIN ..................................... 3-4 3.3.2.1.9 PATSUBST ................................. 3-4 iii 3.3.2.1.10 SORT ..................................... 3-5 3.3.2.1.11 STRIP .................................... 3-5 3.3.2.1.12 SUBST .................................... 3-5 3.3.2.1.13 WORD ..................................... 3-5 3.3.2.1.14 WORDS .................................... 3-5 3.3.2.2 File operations............................. 3-5 3.3.2.2.1 BASENAME ................................. 3-5 3.3.2.2.2 DIR ...................................... 3-6 3.3.2.2.3 FILETYPE ................................. 3-6 3.3.2.2.4 FILEVERSION .............................. 3-6 3.3.2.2.5 NOTDIR ................................... 3-6 3.3.2.2.6 WILDCARD ................................. 3-6 3.3.2.3 Miscellaneous operations.................... 3-6 3.3.2.3.1 ORIGIN ................................... 3-6 3.4 64K Line Length Limit............................ 3-7 3.5 User Defined Severity............................ 3-7 3.6 Reserved Macros.................................. 3-8 4 Problems Fixed 5 Known Problems 6 Restrictions iv _________________________________________________________________ Preface These release notes characterize the Module Management System Version 3.5 for OpenVMS (MMS) software. These notes contain information that either supplements or supersedes the information in the HP DECset Version 12.5 for OpenVMS (DECset) documentation set. Intended Audience These release notes are intended for users and system managers who need information about MMS on either of the OpenVMS operating system platforms (VAX or Alpha). 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 contains a description of the new features included in Version 3.4. o Chapter 4 describes all problems resolved by the current release. o Chapter 5 describes all known problems in the current release. o Chapter 6 describes all restrictions. v Related Documents For additional information about OpenVMS or DECset products and services, visit the following web site: http://www.hp.com/go/openvms 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 OSSG Documentation Group, ZKO3-4/U08 110 Spit Brook Rd. Nashua, NH 03062-2698 How To Order Additional Documentation For information about how to order additional documentation, visit the following World Wide Web address: http://www.hp.com/go/openvms/doc/ 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. vi ___________________________________________________________ Convention__________Description____________________________ 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 The information in these release notes pertains to the Module Management System Version 3.5 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 MMS Version 3.5 is a minor release. 1.2 Associated Documents The following documents contain information related to MMS. Note however, that for the HP DECset Version 12.5 for OpenVMS release, only the software product descriptions and component product release notes have been updated. The document associated with MMS is: o Guide to DIGITAL Module Management System for OpenVMS Systems Also applicable are the general DECset documents: o Compaq DECset for OpenVMS Installation Guide o HP DECset for OpenVMS VAX Software Product Description o HP DECset for OpenVMS Alpha Software Product Description o Guide to Detailed Program Design for OpenVMS Systems o Using DECset for OpenVMS Systems General Information 1-1 In addition to the base MMS 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: SYS$SYSROOT:[SYSHLP.EXAMPLES.DECSET]DECSET_COOKBOOK.* 1.3 Associated Products The DECset Clients for CMS and MMS software provides access from a desktop personal computer (PC) to the Code Management System Version 4.2 for OpenVMS (CMS) libraries and MMS features residing on OpenVMS Alpha and OpenVMS VAX Systems. Note that the DECset Clients for CMS and MMS software is packaged and distributed separately from the HP DECset for OpenVMS, CMS and MMS products. DECset Clients for CMS and MMS can be used from a personal computer running Microsoft Windows; see the associated Software Product Description for information on supported versions. Connection to a CMS library from the PC is possible once the server software (provided with the client) and the CMS for OpenVMS software are installed at the server site. The main DECset Client windows offer menu access to most of the CMS and MMS functions. DECset Client commands can also be performed by clicking the command buttons on the toolbar. In addition, DECset Client supports drag-and- drop functionality for manipulating data within the DECset Client window. For configuration management, a set of files is stored in a CMS library on the OpenVMS system. These files can be fetched, reserved, and replaced in either the PC environment using the CMS Client or the local OpenVMS environment using CMS. As a result, a common configuration can be maintained regardless of the operating environment. Additional information on DECset Clients for CMS and MMS can be found 0n the DECset web page: http://h71000.www7.hp.com/commercial/decset/clients_index.html 1-2 General Information 1.4 Using MMS with DECwindows Motif To use MMS with the DECwindows Motif interface, one of the following must be installed: o HP DECwindows Motif for OpenVMS Alpha Version 1.2-5, 1.2-6, or 1.3 o HP DECwindows Motif for OpenVMS VAX Version 1.2-5 or 1.2-6 1.5 Installation Requirements For HP OpenVMS Alpha Systems For a new installation of MMS the following is required: Global Pages 1900 Global Sections 8 Disk Blocks 7500 For HP OpenVMS VAX Systems For a new installation of MMS the following is required: Global Pages 700 Global Sections 10 Disk Blocks 4500 General Information 1-3 2 _________________________________________________________________ New Features The following enhancements were added to MMS for Version 3.5: o Improved conditional processing using .IF, .ELSIF, .ELSE and .ENDIF directives. o Additional symbol, MMS$SEVEREST_STATUS, defined when MMS exits. o Improved handling of the suffixes precedence list using .SUFFIXES, .SUFFIXES_DELETE, .SUFFIXES_AFTER and .SUFFIXES_BEFORE directives. Descriptions of these enhancements can be found in the following sections. 2.1 Improved Conditional Processing New directives, .IF and .ELSIF, have been introduced to improve the conditional processing features of MMS. These directives, together with the existing directives .ELSE and .ENDIF, are used to instruct MMS to process selected lines in your description file and replace the conditional processing features described in Guide to DIGITAL Module Management System for OpenVMS Systems, Section 2.7.13. Note that, although the existing directive .IFDEF has been superseded by the features described here, description files using the .IFDEF directive will continue to execute precisely as in earlier versions of MMS. The .IF directive has the following format: New Features 2-1 .IF boolean-expression [description-file-line] ... {.ELSIF boolean-expression [description-file-line] ... } [.ELSE [description-file-line] ... ] .ENDIF In this syntax, the description-file-line is zero or more description file lines that may include further .IF directives. The .IF directive may be followed by zero or any number of .ELSIF directives, and zero or one .ELSE directive. The .IF directive must always be accompanied by a matching .ENDIF directive. MMS evaluates the boolean expression specified with the .IF directive. If true, the lines of the description file between the .IF directive and a corresponding .ELSIF, .ELSE or .ENDIF are processed; then, if either .ELSIF or .ELSE were detected, all description file lines from this line to the corresponding .ENDIF directive are ignored. When the boolean-expression specified with the .IF directive is false, all description file lines from this point to a corresponding .ELSE, .ENDIF, or .ELSIF whose associated boolean-expression is true, are ignored. Consider the following example: .IF boolexp-1 line-1 .ELSIF boolexp-2 line-2 .ELSE line-3 .ENDIF When boolexp-1 is true, then line-1 is processed and line- 2 and line-3 are ignored. When boolexp-1 is false and boolexp-2 is true, then line-2 is processed and line-1 and line-3 are ignored. When boolexp-1 and boolexp-2 are both false, then line-3 is processed and line-1 and line-2 are ignored. 2-2 New Features The boolean expression specified in .IF and .ELSIF directives is defined as follows: boolean-expression :== [ .NOT ] boolean-operation | [ .NOT ] boolean-operation boolean-operator boolean-expression boolean-operation :== ( boolean-expression ) | word | word comparison-operator word word :== null | any sequence of characters, terminated by space, and not starting with '.', '(' or ')'. boolean-operator :== .AND | .OR comparison-operator :== .EQ | .NE | .GE | .LE | .GT | .LT As shown above, the operands in boolean expression take one of two forms: .IF word-0 or .IF word-1 .EQ word-2 In the first case, MMS checks to see if word-0 is a macro that has been defined to a non-null value; the expression is true if it is, false otherwise. Note that this is precisely the same functionality as that of the .IFDEF directive in previous versions of MMS. In the second case, MMS performs the requested comparison between word-1 and word-2 to determine the expression value. Note that the comparison operation is case- sensitive. When using macros and functions in expressions of this form, you must reference the macro or function in the standard way, in $(). For example, to check that the macro FRUIT is defined to be BANANAS, you must write: .IF $(FRUIT) .EQ BANANAS not .IF FRUIT .EQ BANANAS which is always false. New Features 2-3 If you need to compare words that start with the characters '.', '(' or ')' or text containing layout characters then, enclose the words or text (on both sides of the comparison operator) in quotation-marks. For example, to check that the macro FILETYPE is defined as .MMS, and that the macro VERSION is not defined as 'Version 3.2', you must write: .IF "$(FILETYPE)" .EQ ".MMS" .AND "$(VERSION)" .NE "Version 3.2" 2.2 MMS$SEVEREST_STATUS Symbol An additional symbol, MMS$SEVEREST_STATUS, is defined to indicate the status of executed action lines; refer to Guide to DIGITAL Module Management System for OpenVMS Systems, Section 2.6.3. MMS uses two symbols, MMS$STATUS and MMS$SEVEREST_STATUS, to record return status values of action lines executed; these symbols reflect the value of $STATUS returned when an action line is executed. When MMS exits, MMS$STATUS reflects the status of the last action line executed and MMS$SEVEREST_STATUS reflects the severest status of all action lines executed. If the status values of more than one action line have the same severity, then the resulting value of MMS$SEVEREST_STATUS is that of the last of these action lines. 2.3 Suffixes Precedence List Directives Three new directives, .SUFFIXES_DELETE, .SUFFIXES_AFTER, and .SUFFIXES_BEFORE, can be used to manipulate the suffixes precedence list and augment the existing features described in Guide to DIGITAL Module Management System for OpenVMS Systems, Section 2.7.7. The operation of the existing directive, .SUFFIXES, is unchanged, except that a warning is now given if an attempt is made to append a type that already exists in the list. .SUFFIXES [file types list] .SUFFIXES_DELETE [file types list] .SUFFIXES_AFTER first file type [file types list] .SUFFIXES_BEFORE first file type [file types list] The .SUFFIXES directive appends the list of file types to the suffixes precedence list. If no list is specified, the entire suffixes precedence list is deleted. 2-4 New Features The .SUFFIXES_DELETE directive deletes the specified file types from the suffixes precedence list. If no list is specified, the entire suffixes precedence list is deleted. The .SUFFIXES_AFTER and .SUFFIXES_BEFORE directives insert the list of file types into the suffixes precedence list, after or before the first file type. If the first file type is not in the suffixes precedence list, a warning is given and the new list is appended to the suffixes precedence list. If a file type to be appended or inserted already exists in the suffixes precedence list, a warning is given and the file type is deleted from the suffixes precedence list before being included at its new position. New Features 2-5 3 _________________________________________________________________ New Features in Version 3.4 The following enhancements were added to MMS for Version 3.4: o The following qualifiers have been added to the MMS Generator: o /SWITCHES - specifies compiler and linker command line qualifiers to be included in the generated files. o /BUILTIN_RULES_APPLY - specifies that MMS built-in compilation actions should be used. o The addition of further predefined functions that enable text processing, word list operations, and file specification manipulation to be performed in MMS description files. o The 64K limit on the length of a macro expanded line has been removed. o A new directive has been added in MMS description files, .ACTION_STATUS, that enables MMS to deal correctly with action lines that do not return standard VMS status values. o The addition of new reserved macros MMSDESCRIPTION_FILE, MMSARCH_NAME, MMSALPHA and MMSVAX. Descriptions of these enhancements can be found in the following sections. New Features in Version 3.4 3-1 3.1 MMS Generator Qualifier - /SWITCHES The following command line qualifier, for use with the MMS Description file generator, has been added: /SWITCHES=([COMPILE="/sw1[/sw2...]"][,LINK="/sw3[ /sw4...]"] The specified compilation and link qualifiers are included in all the compilation and link commands in the generated description file. These qualifiers provide the same functionality as provided by the Additional Compiler Switches and the Additional Linker Switches buttons and text fields in the DECwindows interface. Note that the SCA library options in the DECwindows interface to the MMS generator have been removed; these have never been supported. 3.2 MMS Generator Qualifier - /BUILTIN_RULES_APPLY The following command line qualifier, for use with the MMS Description file generator, has been added: /[NO]BUILTIN_RULES_APPLY When selected, the description file generated only contains the dependency lines for compilations. No action lines are included, so MMS uses the built-in rules when processing this description file. The action lines for the link command are not affected by this qualifier (that is, they are always generated). The compile switches option (see Section 3.1) is not allowed when this option is specified. The default value of the qualifier is /NOBUILTIN_RULES_ APPLY. A new toggle button has been added to the main screen of the DECwindows file generator dialog. 3.3 Additional Predefined Functions The predefined functions described in the following sections can be used in description files to: o perform text processing operations o operate on file specifications o determine the origin of macros. 3-2 New Features in Version 3.4 Note that predefined functions can only be used if extended syntax has been enabled (use /EXTENDED_SYNTAX qualifier when invoking MMS or, in DECwindows MMS, check the Extended Syntax check box in the Build Definitions/Directives Options dialog box). 3.3.1 Function Parameters Where a parameter to a function is considered to be a list of words, a word is defined as any sequence of characters, not containing white-space characters, that is terminated by a white-space character or a right parenthesis. White- space characters are space and tab. Functions that generate word lists produce lists that are white-space compressed (that is, no leading or trailing spaces and a single space character between each word in the list). 3.3.2 The Functions The following sections describe the operation of all the predefined functions supported by MMS; for completeness, descriptions of the existing functions FINDSTRING, SUBST and WILDCARD are also included. 3.3.2.1 Text operations The following functions perform text processing operations. 3.3.2.1.1 ADDPREFIX $(ADDPREFIX prefix,text) This function prepends prefix to the start of each word in text. 3.3.2.1.2 ADDSUFFIX $(ADDSUFFIX suffix,text) This function appends suffix to the end of each word in text. 3.3.2.1.3 FILTER $(FILTER pattern...,text) This function filters text. Any word in text that does not match any pattern word is removed; pattern words may contain the wildcard characters * and %. New Features in Version 3.4 3-3 3.3.2.1.4 FILTER-OUT $(FILTER-OUT pattern...,text) This function filters text. Any word in text that matches any pattern word is removed; pattern words may contain the wildcard characters * and %. 3.3.2.1.5 FINDSTRING $(FINDSTRING find,text) This function performs a string search. If find occurs in text, the value is find; otherwise, the value is empty. 3.3.2.1.6 FIRSTWORD $(FIRSTWORD text) This function returns the first word in text. 3.3.2.1.7 FOREACH $(FOREACH macro,list,text) This function repeatedly expands text. For each word in list, text is repeated with the value of macro defined as the word from list. 3.3.2.1.8 JOIN $(JOIN list,text) This function concatenates word by word. Each word in text is appended to the corresponding word in list to form a word in the result. When the number of words in list and text are not the same, the remaining words from the longer are simply appended to the result. 3.3.2.1.9 PATSUBST $(PATSUBST pattern...,to,text) This function performs pattern substitution. Each word in text that matches any pattern word is replaced by to. pattern words may contain the wildcard characters * and %. If to also contains wildcard characters, they are replaced by the text that matched the wildcard characters in pattern. 3-4 New Features in Version 3.4 3.3.2.1.10 SORT $(SORT text) This function sorts text. Words in text are sorted into lexical order; duplicated words are removed. 3.3.2.1.11 STRIP $(STRIP text) This function performs white-space compression. Leading and trailing white-space is removed from text and each internal sequence of white-space characters is replaced by a single space. 3.3.2.1.12 SUBST $(SUBST from,to,text) This function performs string substitution. Each occurrence of from in text is replaced by to. 3.3.2.1.13 WORD $(WORD n,text) This function returns the n'th word from text. n should be in the range 1 to the number of words in the list; when n is not in this range, the result is empty. 3.3.2.1.14 WORDS $(WORDS text) This function returns the number of words in text. 3.3.2.2 File operations The following functions operate on file specifications; each has a single parameter which is a list of words where each word is considered to be a file specification. 3.3.2.2.1 BASENAME $(BASENAME text) For each file specification in text, this function returns that part of the file specification that is not the type or version. New Features in Version 3.4 3-5 3.3.2.2.2 DIR $(DIR text) For each file specification in text, this function returns that part of the file specification that is not the name, type or version. 3.3.2.2.3 FILETYPE $(FILETYPE text) For each file specification in text, this function returns the type part of the file specification. 3.3.2.2.4 FILEVERSION $(FILEVERSION text) For each file specification in text, this function returns the version part of the file specification. 3.3.2.2.5 NOTDIR $(NOTDIR text) For each file specification in text, this function returns the name and type part of the file specification. 3.3.2.2.6 WILDCARD $(WILDCARD text) This function searches for files. The result is the name and type part of all existing files that match any of the file specifications in text. The file specifications may contain the wildcard characters * and %. 3.3.2.3 Miscellaneous operations 3.3.2.3.1 ORIGIN $(ORIGIN macro) This function returns the origin of macro as follows: FILE defined in a description file COMMAND LINE defined on the command line SPECIAL a special macro DEFAULT a default macro 3-6 New Features in Version 3.4 CLI SYMBOL a CLI symbol TEMPORARY defined by function FOREACH UNDEFINED macro is not defined 3.4 64K Line Length Limit The limitation that the macro expanded length of a line is no more then 64K has been removed. 3.5 User Defined Severity A mechanism has been provided that enables MMS to deal with action lines that do not return standard OpenVMS status values. The new action line prefix, ?name, indicates those action lines for which the severity must be determined according to the rules defined by the new ACTION_STATUS directive. The ACTION_STATUS directive defines how the equivalent VMS severity can be determined from a foreign status value. The ACTION_STATUS directive has the following form (use the line continuation character (-) if the directive uses more than one line): .ACTION_STATUS name [ .MASK m ] [ .SUCCESS { s1,s2,... | OTHERS } ] [ .INFORMATION { i1,i2,... | OTHERS } ] [ .WARNING { w1,w2,... | OTHERS } ] [ .ERROR { e1,e2,... | OTHERS } ] [ .FATAL { f1,f2,... | OTHERS } ] where, o Name is any sequence of characters not starting with a punctuation character and terminated by comma, space or tab (punctuation characters are ! : ; , # ). o m, s, i, w, e and f are decimal, octal or hex numbers (octal numbers are 0... and hex numbers are %x... or 0x...) representing status values to be associated with the corresponding severity. o Space, tab or comma can be used as the separators in a list of numbers. New Features in Version 3.4 3-7 o OTHERS associates all otherwise unspecified status values with the corresponding severity; OTHERS can only be specified for one severity. o If OTHERS is not specified, all unspecified status values default to the least severe of any undefined severity (or ERROR if all severity values are defined). o The directive is effective over the entire file. o It is an error to specify two ACTION_STATUS directives with the same name. MMS then interprets the status returned from an action line prefixed by ?name as follows: o If mask is specified, extract value from the action line status using the mask value; the extracted value is shifted right to match the first bit in the mask. o If mask is not specified, extracted value is the action line status. o Determine the severity associated with the extracted value. MMS then continues, treating this severity as if it were a standard OpenVMS $SEVERITY. 3.6 Reserved Macros The following reserved macros have been added for this release: o MMSDESCRIPTION_FILE - expands to the full file specification of the original description file being processed (Note: it does not expand to any description file included using the .INCLUDE directive). o MMSARCH_NAME - expands to the architecture name of the processor on which MMS is running, that is, Alpha or VAX (Note: in earlier releases, the special macro MMS$ARCH_NAME performed this function; for compatibility with these versions, MMS$ARCH_NAME can be used as an alternative reserved macro). 3-8 New Features in Version 3.4 o MMSALPHA - expands to Alpha if MMS is running on an Alpha; otherwise the value is empty. Use this macro with .IFDEF to define description file lines that are for Alpha only. o MMSVAX - expands to VAX if MMS is running on a VAX; otherwise the value is empty. Use this macro with .IFDEF to define description file lines that are for VAX only. New Features in Version 3.4 3-9 4 _________________________________________________________________ Problems Fixed The following bugs were fixed and restrictions removed in MMS Version 3.5: o ID:124 - The MMS description file generator did not recognize the module name pragma in C source files. This problem has been corrected. o ID:125 - References to functions containing parameters that are macros or functions whose result contained the character ',' were not evaluated correctly. This problem has been corrected. o ID:127 - The MMS description file generator did not create the correct dependencies for nested BLISS require files. This problem has been corrected. o ID:128 - The MMS description file generator terminated a block of comment lines in the description file with the line '!--'. As '-' occurring at the end of a line indicates a continuation line, the line following the block comment was also treated as a comment line. To avoid this confusion, a block of comment lines is now terminated with the line '!=='. o ID:130 - The MMS description file generator did not create the correct dependencies for C header files; this was only a problem when using the /BUILTIN_RULES_APPLY qualifier. This problem has been corrected . o ID:131 - The MMS description file generator did not create the correct dependencies for FORTRAN source files containing multiple routines. This problem has been corrected. o ID:132 - The MMS description file generator could create a LINKER command line that is too long when processing a large number of Pascal Environment files. This problem has been corrected. Problems Fixed 4-1 o ID:133 - MMS could 'hang' indefinitely when used in conjunction with CDD on OpenVMS Version 7.2 and above. This problem has been corrected. o ID:134 - Warnings were not always generated when a mismatch of .IFDEF, .ELSE and .ENDIF directives existed in a description file. This problem has been corrected. o ID:135 - The MMS description file generator could create references to non-existent modules when COBOL source files containing identifiers of the form ...PROGRAM-ID were processed. This problem has been corrected. o ID:136 - The MMS description file generator did not use the logical name DECC$USER_INCLUDE when searching for C header files. This problem has been corrected. o ID:137 - Spurious blank lines could be written to the terminal and the listing file when MMS terminated; this has only been observed on OpenVMS Version 7.3-1. This problem has been corrected. o ID:139 - The MMS description file generator ignored the /LINK_LIBRARY qualifier and appended a spurious character to qualifier values appearing in the generated description file; this only occurred when the command line was too long (above 245 characters approximately) or the values originated from a context defined by the DECset Environment Manager. This problem has been corrected. o ID:142 - The MMS description file generator produced incorrect description files when processing a Pascal source that contained both global symbols and a reference to an environment module that used these symbols. When this occurred, the description file contained erroneous dependencies that caused MMS to fail with the message: %MMS-W-GWKLOOP, Circular dependency detected at target ... This problem has been corrected. 4-2 Problems Fixed 5 _________________________________________________________________ Known Problems The following problems are known to exist in MMS Version 3.5: o ID:42 - Installation: HP Forms Management System for OpenVMS (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 ID:143 - The MMS description file generator does not create the correct actions in the description file for a Pascal source file that is referenced as an environment module if the source file does not contain the ENVIRONMENT attribute. Ensure that all source files referenced as environment modules contain this attribute. Known Problems 5-1 6 _________________________________________________________________ Restrictions The following restrictions apply to MMS Version 3.5: o Specifying more than one description file, separated by commas or plus signs, is not supported with the DECwindows interface. Only the first description file listed is displayed in the description file area. Only the first description file is used in the MMS command. o Restriction on size of search list MMS propagates 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. Use of the 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 Changing fonts may cause buttons to disappear in the Sources, Additional Link Libraries, and Options Files dialog boxes. o The following restrictions apply to MMS for support of the HP Forms Management System for OpenVMS (FMS) libraries. - Support in MMS for FMS libraries is 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. Restrictions 6-1 - 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 Both of the shareable images must be installed in order for FMS to function properly. 6-2 Restrictions