DECset________________________________________ Release Notes for DIGITAL CMS Version V4.0 November 1998 These release notes for DIGITAL Code Management System Version V4.0 for OpenVMS VAX and OpenVMS Alpha contain important general information, new and changed features, current restrictions and documentation notes. Operating System and Version: OpenVMS VAX, Versions 6.2, 7.1, 7.2 OpenVMS Alpha, Versions 6.2, 7.1, 7.2 DECwindows Motif, Versions 1.2-3 - 1.2-5 Software Version: DECset for OpenVMS, Version V12.3 Software Version: DIGITAL Code Management System for OpenVMS Systems, Version V4.0 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, 1998. All rights reserved. © Electronic Data Systems Limited 1995, 1998. The following are trademarks of Digital Equipment Corporation: DEC Ada, DEC BASIC, DIGITAL C, DIGITAL COBOL, DECdocument, DECnet, DEC Pascal, DECset, DECwindows, DIGITAL, DIGITAL Fortran, eXcursion OpenVMS, VAX, VAX BLISS-32, OpenVMS Cluster, VAX DOCUMENT, VAX SDL, 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 Associated Documents............................ 1-1 1.3 DECset Clients for CMS and MMS.................. 1-2 1.4 Installation Requirements....................... 1-3 2 New Features 2.1 Enhancements in Version V4.0.................... 2-1 2.1.1 Extended filenames ........................... 2-1 2.1.2 Allocation of virtual memory ................. 2-1 2.1.3 SDL Description of Callable Routines ......... 2-2 3 Problems Fixed 4 Known Problems 4.1 General......................................... 4-1 4.2 DECwindows Problems............................. 4-7 4.3 Documentation Problems.......................... 4-9 iii 5 Restrictions 6 Reporting Problems and Suggestions Tables 1 Conventions .................................. vi iv ________________________________________________________________ Preface These release notes characterize the Version V4.0 release of DIGITAL Code 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 CMS 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 known problems 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 Code Management System Version V4.0. 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 Code Management System Version V4.0 is a minor release. 1.2 Associated Documents The documentation of CMS and of DECset has been revised for this release. This revision corrects errors, enhances descriptions, and describes all new functionality. The documents associated with CMS are: o Guide to DIGITAL Code Management System for OpenVMS Systems o DIGITAL Code Management System Reference Manual o DIGITAL Code Management System Callable Routines Reference Manual 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 VMS 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.3 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. 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 Clients windows offer menu access to most of the CMS and MMS functions. DECset Clients commands can also be performed by clicking the command buttons on the toolbar. In addition, DECset Clients supports drag-and-drop functionality for manipulating data within the DECset Clients window. The files under configuration management reside in a CMS library on the OpenVMS server site. Using the Client they can be fetched to, reserved to and replaced from directories on the PC. A CMS library can be accessed from many Clients and locally from the OpenVMS system. Thus, files can be held under configuration management and shared between the PC and the OpenVMS environments. Additional information on DECset Clients for CMS and MMS can be found in the DIGITAL OpenVMS web pages: 1-2 General Information http://www.openvms.digital.com/commercial/ 1.4 Installation Requirements For a new installation of CMS the following is required: OpenVMS Alpha Systems Global Pages 3500 Global Sections 10 Disk Blocks 32000 OpenVMS VAX Systems Global Pages 1500 Global Sections 15 Disk Blocks 25000 General Information 1-3 2 ________________________________________________________________ New Features The following enhancements were added to DIGITAL Code Management System. 2.1 Enhancements in Version V4.0 2.1.1 Extended filenames OpenVMS V7.2 for Alpha systems only. Extended filenames are supported in CMS V4.0 libraries and through the Callable Interface. Libraries must be created or modified using the /EXTENDED_FILENAMES qualifier. CMS with extended filenames supports both the ISO-LATIN1 and Unicode-2 characters set in its element names. To use extended filenames, your system must have installed CMS V4.0 with extended filename support. In addition, the structure of the disk containing the CMS libraries must be ODS-5. See your system manager for information. The CMS documentation describes the /EXTENDED_FILENAMES qualifier used with the CREATE and MODIFY LIBRARY commands, and the extended_filenames parameter for calling CMS$CREATE_LIBRARY and CMS$MODIFY_LIBRARY. 2.1.2 Allocation of virtual memory The size of the virtual memory block allocated for a library has been increased in proportion to the size of the existing library to allow the library to grow without requesting additional virtual memory as often. This has reduced the number of fragmented areas of memory allowing a library to handle a larger number of elements. New Features 2-1 2.1.3 SDL Description of Callable Routines A VAX SDL (Structure Definition Language) description of the CMS callable routines is now provided. This provides a programming language independent description of all the callable routines. From it interface descriptions in a range of supported languages can be generated. The languages supported are: Ada BASIC Bliss C Fortran Macro Pascal PL/I The SDL description is in the file CMS$ROUTINES.SDL located in the SYS$SYSROOT:[SYSHLP.EXAMPLES.CMS] directory. To generate the interface file for a particular language use the SDL command. For example, SDL/LANG=ADA SYS$SYSROOT:[SYSHLP.EXAMPLES.CMS]CMS$ROUTINES.SDL This will generate a CMS$ROUTINES.ADA file which defines the complete CMS callable interface as an Ada package. Note that for the C language, SDL generates an interface description intended for use with VAX C or with DIGITAL C using the /STANDARD=VAXC qualifier. The generated interface will need modification to work with ANSI C. 2-2 New Features 3 ________________________________________________________________ Problems Fixed The following bugs were fixed and restrictions were removed in CMS Version V4.0: o Bug 54 - Merge conflict record delimiters were too long. Merge conflict record delimiters are now a maximum of 80 characters long. o Bug 61 - FETCH/MERGE/NONOTES did not remove notes. Notes are now removed when the /NONOTES qualifier is specified. o Bug 63 - DIFFERENCES/OUTPUT=filespec failed to parse filename. Directories and filenames are now parsed using user supplied information in place of the default file specification. o Bug 84 - Attempts to delete a reserved element caused the reference copy of an element to be removed. The reference copy of an element will only be deleted if the element has been successfully deleted. o Bug 86 - CMS Installation Verification Procedure (IVP) left library set to IVP test library when finished. The library is now cleared before the IVP exits. o Bug 89 - ANNOTATE/MERGE lost generation information. Problems Fixed 3-1 ANNOTATE/MERGE now correctly displays generation and variant information. o Bug 93 - DECwindows New.Element deleted file regardless of Delete Input Files button. Input files are now only deleted if the Delete Input Files button is selected. o Bug 101 - Alpha, CMS-F-BADIOBLENGTH, The passed IOB has an invalid length. This occurred when using groups of 5 elements. The problem has been corrected. 3-2 Problems Fixed 4 ________________________________________________________________ Known Problems The following known problems exist for CMS Version V4.0: 4.1 General o Bug 11 - CMS-E-BADREF, reference copy for element. Using a reference copy directory with the /HISTORY and /REFERENCE attributes set on a particular type of file will cause CMS to think the reference copy file is bad and ask if the file should be recreated. After recreating the file, CMS confirms that the reference copy file has been repaired, but a subsequent verify shows the reference copy file to still be bad. The only workaround is either to set the /NOHISTORY attribute or set the /NOREFERENCE attribute. o Bug 14 - CMS differences on VFC files shows incorrect line numbers. An attempt to perform a comparison of two VFC files using the DIFFERENCES command can generate incorrect line numbering in the differences output. As the files are different, a difference file is created, but the line numbers in the difference file are not correct. Instead of the correct line number, the line number is 36097/1. The problem only occurs with VFC files. o Bug 15 - CMS reports a bogus conflict during variant merge. In certain circumstances, where there are a large number of generations and deleted lines in a relatively small region of a large CMS element file, the comparison algorithm fails to correctly track the deletion information in the element during merges. Known Problems 4-1 This can cause attempts to merge a variant (gen 28p1) and the main line of descent (gen 31) with a common ancestor (gen 28) via FETCH/MERGE or RESERVE/MERGE to result in a bogus first conflict. The lines in the conflict do not match the lines that are different. o Bug 23 - DIFFERENCES/SENTINEL on identical files can find differences. CMS DIFFERENCES can find two files identical. However, with the /SENTINEL switch, CMS may start to report differences. o Bug 25 - CMS merges incorrectly. Deleted lines may not stay deleted in a merge operation. o Bug 26 - MERGE is inconsistent in finding conflicts. MERGE may produce different results depending on the order new generations or variants are inserted into the CMS library. For example, the same second generation and variant are placed into a CMS library but in different orders. In one case, the files merge; in another case they only merge with conflicts. o Bug 34 - Problem with FETCH/GENERATION=no *.* and ACLs. Errors may be reported while fetching a class containing some elements that are protected by CMS ACLs. For example, where one of the elements has a CMS ACL that states that the user has no access to the element and another element has no ACL, the class is fetched with no privileges turned on. The one element is fetched as expected, but CMS attempts to fetch the other element and the following errors occur: %CMS-E-NOFETCH, error fetching element DISK:[DIR]BOGUS.DAT -CMS-E-NOACCESS, no FETCH access to element BOGUS.DAT When BYPASS privilege is turned on, the errors do not occur. o Bug 40 - RMS-E-ISI errors performing wildcard CREATE ELEMENT with mixed files. 4-2 Known Problems Wildcarded CREATE ELEMENT commands can fail if non- DDIF files follow DDIF files. The following errors are produced: %RMS-E-ISI, invalid internal stream identifier (ISI) value -RMS-E-EXTNOTFOU, RMS Extension not found %CMS-F-BUG, there is something wrong with CMS ... -CMS-F-SYSFAIL, LIB$FREE_VM system service request failed -LIB-F-BADBLOSIZ, bad block size DDIF files later in the list will be created without errors. The only known workaround is to avoid a wildcard CREATE of non-DDIF files after DDIF files. o Bug 53 - REMOVE GENERATION/IF_CHANGED returns the wrong status. If REMOVE GENERATION/IF_CHANGED is used to remove a generation that does not exist from a class, the status %X10000000 is returned rather than CMS$_NORMAL. o Bug 60 - Review state altered after REPLACE/IF_CHANGED on unchanged elements. The review state of element generations is incorrectly altered after a REPLACE/IF_CHANGED of an unmodified element. o Bug 66 - CMS$DIFFERENCES may fail if element is not in first search listed library. If an attempt is made to use CMS differences to compare a file with an element contained in a CMS library that is not the first in a library search list, CMS will report an error for any earlier libraries in the list before performing the comparison. o Bug 70 - Merging main-line generation into variant produces different result: CMS> FETCH element-name/GENERATION=2x1/MERGE=3 "" In relatively rare cases merging a main-line generation into a variant will produce an invalid and different result from merging the same variant into the same main-line generation: CMS> FETCH element-name/GENERATION=3/MERGE=2x1 "" Known Problems 4-3 When particular lines have been removed in the main-line generation, in a variant of an earlier generation, and then in an unrelated variant of the common ancestor's (generation 2 for the previous example), but not in the common ancestor, the lines are incorrectly included in the merged result when the main-line generation is merged into the variant. *3D <--- deleted in main-line generation *1V1D <--- deleted in an earlier variant *2V1D <--- deleted in unrelated variant of ancestor <--- the deleted line *2V1E <--- delete is the ONLY change (i.e. no inserts) *1V1E *3E When the variant is merged into the main-line generation, or the generations are created in different order then the lines remain deleted. *3D <--- deleted in main-line generation *2V1D <--- deleted in unrelated variant of ancestor *1V1D <--- deleted in an earlier variant <--- the deleted line *1V1E *2V1E <--- delete is the ONLY change (i.e. no inserts) *3E The problem can be avoided by always merging the variant in the main-line generation. For example: CMS> FETCH element-name/GENERATION=3/MERGE=2x1 "" Or: CMS> FETCH element-name/MERGE=2x1 "" o Bug 71 - A plus in the /FORMAT string confuses CMS. CMS gets confused if the /FORMAT string contains a plus sign "+". $ CMS SHOW ELEMENT *.* /FORMAT="$ cms diff #e/gen=1 #e" - _$ /OUTPUT=differ.com ! Works $ CMS SHOW ELEMENT *.* /FORMAT="$ cms diff #e/gen=1+ #e" - _$ /OUTPUT=differ.com ! Fails %CMS-E-ERRPAREXP, error parsing element expression -CMS-E-ILLCHAR, illegal character in group name 4-4 Known Problems o Bug 72 - /FORMAT splits long lines. CMS splits long output lines. For example: $ CMS SHOW ELEMENT *.* /OUTPUT=sys$scratch:x.tmp - _$ /FORMAT="$ IF F$SEARCH(""#e"") .NES. """" THEN - _$ CMS DIFFERENCE #e/GEN='p1 #e" If the library contains elements with long names, the output lines for these files can also be split by CMS. o Bug 73 - CMS subsystem quietly ignores lines starting with an at sign "@". The CMS subsystem quietly ignores lines starting with "@". For example: $ CMS CMS> @x.x CMS> o Bug 79 - A plus sign "+" in a /SINCE date-time string may confuse CMS. CMS may report an unrecognized keyword error in the /TRANSACTIONS qualifier of the SHOW HISTORY command if a "+" is used after the date-time string of the /SINCE or /BEFORE qualifier. For example: CMS> SHOW HISTORY - _CMS> /TRANSACTIONS=(CREATE)/BEFORE="15-AUG-1996 + 00:00:00" %CLI-W-IVKEYW, unrecognized keyword - check validity ... \(CREATE)\ Although the problem only occurs when the /TRANSACTIONS keywords are specified within parentheses, it is triggered by the "+" in the date-time string. The problem can be avoided by removing the plus from the date-time string: CMS> SHOW HISTORY - _CMS> /TRANSACTIONS=(CREATE)/BEFORE="15-AUG-1996 00:00:00" o Bug 81 - Quoted generation strings processed incor- rectly. When using /GENERATION=generation-expression do not enclose generation-expression in quotes. o Bug 85 - History and Notes problems on files with MRS attribute. Known Problems 4-5 CMS fails to recognize the maximum record size (MRS) attribute for Notes and History. As a result, CMS may add Notes or History to a record beyond its maximum size. On FETCH or RESERVE, CMS fails with the following error. CMS-F-BUG, there is something wrong with CMS ... CMS-F-NOQIO, $QIO failed RMS-F-RSZ, invalid record size o Bug 94 - When a group and an element have almost the same name, for example group FOO and element FOO.BAR, the command CMS SHOW HISTORY F*.BAR will not resolve the wildcard correctly. The command will show the history for both the group and element. o Bug 95 - If the remark field of the CMS MODIFY GENERATION command contains the exclamation point character "! ", CMS generates the following message: %CMS-F-BUG, there is something wrong with CMS ... -CMS-F-SYSFAIL, $FAOL system service request failed -SYSTEM-F-BADPARAM, bad parameter value o Bug 96 - If CMS is unable to delete the input file after a CREATE ELEMENT or REPLACE operation, no message will be issued to inform the user of the problem. The element is created or replaced without the file being deleted. o Bug 97 - When using the SET ACL/DELETE command to delete a list of ACEs from an ACL, the operation will terminate if it encounters an identifier that does not exist on the system. The correct behavior is to continue the operation with the remaining ACEs specified. o Bug 98 - Certain qualifiers that should only accept parameters in their non-negated form are also accepting them in their negated form, and the qualifier is then treated as if it were not negated. For example, the qualifier /NOHISTORY="#H" should be disallowed, but is being treated as /HISTORY="#H". 4-6 Known Problems o Bug 104 - Using the /BEFORE qualifier on a library that was previously set returns both an error and success status without changing the library's position in the search list. $ CMS SET LIBRARY [A], [B], [C] %CMS-I-LIBIS, library is DISK$USER:[A] %CMS-I-LIBINSLIS, library DISK$USER:[B] inserted at end of library list %CMS-I-LIBINSLIS, library DISK$USER:[C] inserted at end of library list %CMS-S-LIBSET, library is set $CMS SHOW LIBRARY Your CMS library list consists of: DISK$USER:[A] DISK$USER:[B] DISK$USER:[C] $ CMS SET LIBRARY [C]/BEFORE %CMS-E-LIBALRINLIS, library DISK$USER:[C] is already in the library list %CMS-S-LIBSET, library set Your CMS library list consists of: DISK$USER:[A] DISK$USER:[B] DISK$USER:[C] 4.2 DECwindows Problems o Bug 19 - The DECwindows interface ignores accelerator keys. The DECwindows accelerator keys Ctrl/O (open), Ctrl/C (close view) and Ctrl/E (exit) have no affect in the DECwindows interface. o Bug 35 - DECwindows CREATE ELEMENT claims work in progress when it is not. Under certain circumstances, the CMS DECwindows CREATE ELEMENT function will pop up an erroneous work-in- progress box. It can be ignored. o Bug 50 - DECwindows element view with search-listed libraries incorrectly causes all the elements in subsequent libraries to be displayed. o Bug 51 - DECwindows element view can cause a problem with the vertical scroll bar. Known Problems 4-7 When an element view expands beyond the confines of the window, for example after expanding all the details of on a library (View - Expand - All), the vertical scroll fails to function. o Bug 55 - Error fetching element in DECwindows class view. When attempting to fetch an element from the class view in the DECwindows interface, the element is not fetched, and the error "Error fetching element " occurs. o Bug 58 - LSE error is reported when groups are fetched with CMS DECwindows. If a DECwindows LSE is accessible, any attempts to fetch or reserve groups (or classes) using the CMS DECwindows interface will cause LSE to report a file not found error. As an example, trying to Fetch the elements denoted by: "a.a,,b.b" will result in elements A.A and B.B being fetched, followed by a caution box stating: "Error fetching element a.a,,b.b Group not found." o Bug 76 - DECwindows and filespecs greater than 255 characters. The DECwindows interface may produce strange results if the user inputs a filespec that is greater than 255 characters. DECwindows does not check the size and blindly passes this on to the low-level routines, which blindly moves the size into a byte field before processing. Thus, a 256-character filespec, is exactly like providing none. o Bug 92 - Can not deselect REPAIR button in VERIFY dialog. Once the REPAIR button has been selected in the VERIFY dialog box from the MAINTENANCE menu, it can not be deselected. o Bug 99 - Modify Library has a text widget to hold a library name. The library name is not written into this field. 4-8 Known Problems o Bug 100 - When VIEW RESERVATIONS is selected and the user double-clicks on a particular reservation, then selects CONCURRENT REPLACEMENTS, VIEW, EXPAND, ALL - an incorrect error message is reported. o Bug 105 - RESTRICT ELEMENT dialog box is laid out incorrectly. RESTRICT ELEMENT displays a button on top of a text field. o Bug 107 - In the case of virtual memory being exhausted when updating the contents of a CMS View, if the view is iconified, an access violation will occur when CMS attempts to bring up a caution box. If the view is not iconified, after acknowledging the box, the cursor will remain in a "watch" shape and attempting to bring up a dialog box can result in an access violation. The problem can be avoided through the use of the Customize Restrict functionality. For example, by default RESTRICT HISTORY will display only the previous 30 days' history. o Bug 108 - If message logging has been customized to None, the Cancel Operation button may not be recognized until after the operation has been completed. o Bug 109 - Some informational messages resulting from opening or closing libraries will appear on the terminal where the CMS DECwindows interface was invoked rather than in the output window. This also occurs when manipulating a reserved element or an element under review. o Bug 110 - When the CANCEL button is selected to cancel the CLOSE LIBRARY action, the action is not aborted and the library is closed. 4.3 Documentation Problems There are no known problems in the CMS documentation. Known Problems 4-9 5 ________________________________________________________________ Restrictions The following restrictions apply to CMS Version V4.0: o Rarely, when using CMS, the following error is encountered: %CMS-F-BUG, there is something wrong with CMS ... -CMS-F-NOMAP, Cannot map the appropriate control structure -CMS-F-TEXT, dynamic buffer space exhausted. Reenter CMS. This error is caused by a design limitation in CMS. Under extreme conditions, CMS does not have enough buffer space allocated to complete an operation and it cannot deallocate the exhausted buffer and reallocate it again. This error should only occur when using the COPY ELEMENT command, and only for attempts to copy elements with hundreds of generations (typically more than 500-600). This problem has nothing to do with the number of elements being copied, it only depends on the number of generations within any particular element. If the problem is encountered, the primary workaround is to reduce the number of generations in the element that caused the error. Typically, elements with this many generations have been automatically created or altered, and in many cases, the generation history isn't uniformly interesting. Judicious use of DELETE GENERATION could get the number of generations down to a manageable number. o When using CMS library reference copies, certain file system related messages, such as RMS-F-DEV or RMS-E- PRV, may refer to the reference copy directory. The CMS messages do not make this explicit in some cases. When such problems are encountered, check the protections on reference copy. Restrictions 5-1 o Using VERIFY/RECOVER on a library that does not need recovery, fails with an error diagnostic, RECNOTNEC, stating that the library does not need recovery: $ CMS VERIFY/RECOVER %CMS-E-NORECOVER, error recovering library -CMS-E-RECNOTNEC, recovery is not necessary; the library is in a safe state o Use of CMS/LSE integration features. To use the CMS/LSE integration features, introduced in CMS V3.8, LSE V4.3 is required. If a lower version of LSE is used, the CMS/LSE integration features will not be available. No other features are effected by using a version of LSE prior to V4.3. o The following restrictions apply to the CMS DIFFERENCES command when used with a CMS library search list. If both file_1 and file_2 are element generation specifications, then both of the elements must reside in the same library of the library search list. CMS DIFFERENCES will emit CMS-E-NOFETCH (or other messages returned by CMS$FETCH_OPEN) if it cannot locate a specified element generation. In a library search list, this may occur if one or both of the specified elements do not exist in the first library. These messages will be issued for each library of the library search list in which the element is not found. The exact sequence of such messages depends on the values of the /OCCLUDE qualifier. In such cases, a CMS- E-NOFETCH message may be followed by a CMS-S-IDENTICAL or CMS-W-DIFFERENT message. These messages indicate the actual status of the operation, whereas the intervening CMS-E-NOFETCH messages are a side-effect of the library search list traversal. The same considerations apply to the callable routine CMS$DIFFERENCES. CMS$DIFFERENCES uses the callable fetch routines CMS$FETCH_OPEN, CMS$FETCH_GET, and CMS$FETCH_CLOSE. Conditions may be signaled from these routines during the operation of CMS$DIFFERENCES. 5-2 Restrictions o The DECwindows Options.Save_Options feature overwrites the current CMS resource data file in the DECW$USER_ DEFAULTS directory. If a version of the CMS resource data has been placed in this directory for customizing the interface for eXcursion small screen support, it will be overwritten if this option is used. The customized values will not be copied into the new version of the resource data file and will no longer have any effect on the CMS DECwindows interface. o There have been several reports that CMS is corrupting source files via the use of the /NOTES qualifier. This occurs because CMS is strictly syntax driven when /NOTES is involved. During a CMS Replace, it will look at any information contained at the end of each line and remove this information if it looks like a valid notes field. (A notes field is parsed as a "left part" followed by a generation number followed by a "right part".) A notes field NOT containing any "left part" or "right part" contextual information and containing only a generation number field (most examples supplied with the reports specified that they used the /NOTES="#G" form) is especially vulnerable since the format of the generation number is, for many of its valid forms, exactly the same format as a numeric constant which commonly may show up at the end of a line in most programming languages. CMS does not (and probably cannot, in general) keep track of which specific lines it placed notes on. Thus when CMS replaces a file back into an element, it scans all input lines for notes information to be removed. The problem of remembering which lines had notes placed on them seems simple until you remember that the files have probably been edited so that the original context is relatively hard to recover except for the simplest cases. Even trying to depend on the /POSITION qualifier value to determine the "validity" of a particular string as a note is not trustworthy. Restrictions 5-3 To avoid this problem, take full advantage of the complexity allowed in the notes string syntax and define the notes string to have a form that would be very unlikely to be encountered using your normal coding styles. For example: /NOTES="/*--#G--*/" This syntax would probably be acceptable to a C programmer whose coding style did not typically include the "-" prefix and "-" suffix in comments. A side note: One of the COBOL examples received demonstrates this problem in a more subtle fashion. Specifically, when an element is reserved using /NONOTES, a subsequent REPLACE does not remember that it was reserved using /NONOTES and thus tries to remove the notes it finds (thus corrupting the file for the example received). The unfortunate part of this problem is that if we modify REPLACE to honor the state of the notes qualifier as reserved and NOT try to remove the notes from the file for this case, we now have a time bomb. The next time a RESERVE and REPLACE of the element is done WITH notes, the information will then likely be stripped off. In summary, when using /NOTES be careful when picking the notes prototype string to avoid colliding with otherwise legal syntax in the language being used. o CMS does not perform correctly when run from a detached process where no CLI present. Errors like LIB-F-NOCLI will occur. o Callable CMS allows a command string to contain a maximum of 256 characters, where interactive CMS allows a maximum of 1024 characters. The workaround is to provide an input routine and use the continuation line when the library is set up. o The history line sent to the CMS event handler and seen in notification messages will contain the letter 'W' after the transaction time field if the transaction resulted from a wildcard operation. This information should be suppressed, as it is by the SHOW HISTORY command. 5-4 Restrictions o CMS V2.n attempts to operate on a CMS V3.n library, despite having incompatible formats. This may result in a corrupted CMS V3.n library. Note that this problem does not exist for libraries created by or converted to CMS V3.5-5 or later. o A maximum of 65,536 characters can be copied from a CMS view to the DECwindows Clipboard. o When using CMS with extended filenames from the DCL command line, the DCL parse style must be set to extended filenames. Use the DCL command SET PROCESS /PARSE_STYLE=EXTENDED. For example: $ SET PROCESS/PARSE_STYLE=EXTENDED $ CMS SET LIBRARY DISK1:[PROGRAMS.CMSLIB_EXT] $ CMS DIFFERENCES Parser^[Old_Version^].CPP Parser^[New_Version^].CPP Restrictions 5-5 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. Reporting Problems and Suggestions 6-1 When submitting a request, please include the following information: 1. CMS version number and type of OpenVMS operating system. 2. Problem summary. 3. Stack dumps or error logs (if applicable). 4. Files in machine-readable media: magnetic tape (preferred), floppy diskette, or tape cassette. 6-2 Reporting Problems and Suggestions