DECset________________________________________ Release Notes for DIGITAL Environment Manager Version V1.2-02 August 1997 These release notes for DIGITAL Environment Manager Version 1.2 for DIGITAL OpenVMS VAX and DIGITAL OpenVMS Alpha contain important general information, new and changed features, current restrictions and documentation notes. Operating System and Version: OpenVMS VAX, Versions 6.0 - 7.1 OpenVMS Alpha, Versions 6.1 - 7.1 DECwindows Motif, Versions 1.1 - 1.2 Software Version: DECset for OpenVMS Version 12.2 Software Version: DIGITAL Environment Manager for OpenVMS Systems Version 1.2 Digital Equipment Corporation Maynard, Massachusetts __________________________________________________________ August 1997 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 repre- sentations that the interconnection of its products in the manner described in this document will not infringe existing or future patent rights, nor do the descriptions contained in this document imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. © Digital Equipment Corporation 1995, 1997. All rights reserved. © Electronic Data Systems Limited 1995, 1997. The following are trademarks of Digital Equipment Corporation: DEC Ada, DEC BASIC, DEC C, DEC COBOL, DECdocument, DECnet, DEC Pascal, DECset, DECwindows, DIGITAL, DIGITAL Fortran, eXcursion OpenVMS, VAX, VAX BLISS-32, VAXcluster, VAX COBOL, VAX DOCUMENT, and the DIGITAL logo. All other trademarks and registered trademarks are the property of their respective holders. This document was prepared using VAX DOCUMENT, Version 2.1. ________________________________________________________________ Contents Preface.................................................. iv 1 General Information 1.1 Introduction.................................... 1-1 1.2 Installation.................................... 1-1 2 New Features 2.1 Phase V File Names.............................. 2-1 3 Problems Fixed 4 Known Problems 5 Restrictions 6 Reporting Problems and Suggestions Tables 1 Conventions .................................. v iii ________________________________________________________________ Preface These release notes characterize the Version 1.2 release of Environment Manager for DIGITAL 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 Environment Manager 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. iv Associated Documents For more information on Environment Manager, refer to the following documents o DECset OpenVMS VAX V12.2 Software Product Description o DECset OpenVMS Alpha V12.2 Software Product Description o DECset Guide to Detailed Program Design for OpenVMS Systems o Using DECset for VMS Systems 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. (continued on next page) v Table_1_(Cont.)_Conventions_______________________________ 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._______________________ vi 1 ________________________________________________________________ General Information The information in these release notes pertain to Environment Manager Version 1.2. 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 Environment Manager Version 1.2 is a maintenance release. 1.2 Installation Environment Manager is installed automatically by other components of DECset. OpenVMS Alpha systems For a new installation of Environment Manager the following is required: Global Pages 1500 Global Sections 8 Disk Blocks 6600 OpenVMS VAX systems For a new installation of Environment Manager the following is required: Global Pages 700 Global Sections 6 Disk Blocks 2500 General Information 1-1 2 ________________________________________________________________ New Features DECset Version 12.2 is a maintenance release with the following goals for each individual DECset component: o Support for OpenVMS V7.1. o To fix many known problems. o To add minor functionality. Details regarding particular functionality enhancements and bug fixes for each component are found in the individual component's release notes. The following enhancements were added in DECset Environment Manager Version 1.2. 2.1 Phase V File Names The Environment Manager now handles DECnet Phase V file names. New Features 2-1 3 ________________________________________________________________ Problems Fixed The following bugs were fixed and restrictions were removed in Environment Manager Version 1.2: o Bug 60 - Logical name equivalence strings are enclosed in double quotes when written to the context file. The Environment Manager now verifies that the logical name equivalence strings are valid file specifications and does not use quotes. For old context files, the extra quotes can be removed from within the Environment Manager or by editing the context file. For example, change: DEFINE/TABLE=LNM$PROCESS TEST_DIR - "DISK1:[DECSET.TEST]" to: DEFINE/TABLE=LNM$PROCESS TEST_DIR - DISK1:[DECSET.TEST] o Bug 62 - Symbol equivalence strings are enclosed in double quotes when written to the context file. The Environment Manager no longer uses double quotes around symbol strings. For old context files, the extra quotes can be removed from within the Environment Manager or by editing the context file. o Bug 63 - If the logical name SYS$LOGIN was re-defined, either directly or via a context, this caused problems with the filter in the Open Database window. This no longer occurs when SYS$LOGIN has a valid translation. o Bug 65 - Unable to define symbols with embedded spaces. Problems Fixed 3-1 The Environment Manager no longer adds quotes to or removes spaces from symbol definitions. If an old context file contains extra quotes or is missing spaces, the symbol definitions can be corrected from within the Environment Manager or by editing the context file. o Bug 77 - Setting the default directory for a context did not change the device name. For example: If sys$login is DISK:[MY_DIRECTORY] and the context's default directory is set to OTH_ DISK:[OTHER_DIRECTORY], the actual default directory set would be DISK:[OTHER_DIRECTORY]. This problem has been corrected. o Bug 78 - When a logical name, symbol name, context name, parent name, or macro name was entered via quick- copy, it was not converted to upper case. This problem has been corrected. o Bug 64 - When changes have been made to an environment context and saved and applied, then the Exit option from the File menu is selected, a dialog box pops up momentarily asking whether to "Save modifications first?". This problem has been corrected. o Bug 37 - Deleting the context file of the current context and then applying the context would cause the Environment Manager to terminate abnormally. An error message is now produced. 3-2 Problems Fixed 4 ________________________________________________________________ Known Problems The following known problems exist in Environment Manager Version 1.2: 1. Bug 61 - The DECSET SET CONTEXT command does not delete the temporary files that it creates in the SYS$LOGIN directory. These files are named DECSET$UTIL_CTXDB_xxxxxxxx.DAT, DECSET$BASE_CTX_xxxxxxxx.DAT, and DECSET$PREV_CTX_ xxxxxxxx.DAT. The "xxxxxxxx" portion of the file name is the hexadecimal representation of your process ID. Multiple versions of each file may exist. 2. When a tool terminates, the effects of any context `apply' operations that may have taken place are not reversed. 3. Node name is ignored in Context File specification. The Context File specification must exist in the format: disk:[directory.subdirectory]*.decset_context. If you specify a node name in the File menu New Context... Context File: field-even if the node name is part of a local cluster-the node specification is ignored at the time of context file retrieval from the context database. 4. The File menu option Delete Context File... deletes the context file from the selected context. However, if another context specifies the file that was deleted, this context will still appear to refer to that file. When you select this context, DECset displays the following error message: Error selecting context, cannot open context file. Click on the OK button to return to DECset. Known Problems 4-1 5. Under certain circumstances, the View Context [File] operation may list logical name tables even though the named context does not define or deassign any logical names in that table. 6. Parent context file does not exist. Attempting to apply a context with a parent whose con- text file has been deleted will cause the Environment Manager to exit with a fatal error. 7. Saving to directory without write access. Attempting to save a context to a directory to which the user does not have write access will cause the Environment Manager to exit with a fatal error. 8. Bug 3 - The Delete Context file or Context Database command only deletes the latest version of the file. 9. Bug 5 - The Environment Manager operations Delete Context Entry, Context File and Database do not delete all the versions of the contexts and database files. 10.Bug 7 - The Environment Manager GUI varies in its handling of error conditions. 11.Bug 12 - The View and Print Context with Inheritance operations will always use the state of the current context as it exists in the context file for generating the information to be viewed or printed. 12.Bug 14 - The Environment Manager sometimes marks contexts as having been modified when, in fact, they have not. A Save Context confirmation dialog box may be displayed when no changes have been made to the context, resaving the context if no changes have been made to it does not cause any problems. 13.Bug 20 - A logical name table cannot be added to the list of logical name tables if the new logical name table does not contain any logical name definitions. 14.Bug 24 - Clicking on a selected item in the item list of a ordered list manager window will cause that item to be de-selected, de-highlighted and the selection text field to be cleared. The other windows with scrolled lists do not behave in this manner, there 4-2 Known Problems is no affect on the selected item when it is repeatedly selected. 15.Bug 25 - After modifying a context and then selecting a new context by double clicking on a different context in the known contexts list, the first context is saved and the Save confirmation box is displayed, but the new context is not applied and the Apply confirmation box is not displayed. 16.Bugs 28,72 - There is no way to view the current context with inheritance if the context has been modified. The View Context with Inheritance command will always use the context as it exists in the context file, not how it currently exists after any modifications have been made to it and will not save to the context file. 17.Bug 31 - Creating a context causes the save modifi- cation box to display after creating the context and switching contexts, but modifying the context does NOT cause the save modification box to be displayed after modifying the context and then switching contexts. In both cases, the database is updated immediately with the new information. 18.Bug 45 - Modifying the name of a context is not updated throughout the entire context database. If the name of a context that is a parent context is modified, the context entry which specifies that context as its parent is not updated with the parent's context new name. 19.Bug 46 - When modifying a context's name immediately after creating the context, two entries are created in the known context list. One entry has the original name of the context and another entry has the modified name of the context. The modified entry is valid and can be selected, but the original entry cannot be selected, and if attempted, the error message "invalid context name" is displayed in an error message window. Known Problems 4-3 20.Bug 50 - Trying to apply a valid context after unsuccessfully applying an erroneous context will cause the current context application to fail. The Environment Manager must be terminated and then restarted in order to successfully apply a new context. 21.Bug 56 - If the Environment Manager terminates while a DECset client is currently in the middle of a context switch, then the client will timeout while waiting for a response from the Environment Manager and the client can be left in an inconsistent state. 22.Bug 57 - If an error occurs during a context `apply' operation, the (usually partial) effects of the `apply' operation or DECSET SET CONTEXT command are not reversed. 23.Bug 66 - Cannot apply default directory with unknown logical. Because the Environment Manager runs in a detached process, it does not inherit the process logical names defined in the process from which it was invoked. LOGIN.COM is never invoked and thus logical names defined in LOGIN.COM are also not seen. This causes a problem with the Default Directory option in the Settings menu. If a logical name is used in the default directory specification, the Environment Manager will not permit any logical names that it cannot see. When an attempt is made to use a logical name that it cannot see, the following error is displayed in a pop-up box: Filename Error Error in device name or inappropriate device type for operation If an attempt is made to apply a context containing a default directory specification containing an undefined logical name, the resulting error is: Error in directory name The problem can be avoided by defining the logical name in the group or system table. 4-4 Known Problems 24.Bug 70 - If the Environment Manager GUI is running at the time that the Session Manager is terminated, a "Waiting for application response" error box is displayed. It is OK to ignore this error message. 25.Bug 74 - A DECset product will not display an error message if it cannot connect to the DECset Environment Manager. The DECset product will continue to function properly but will not respond to any Environment Manager actions. 26.Bug 75 - If a DECset product times-out when registering with the DECset Environment Manager, it cannot distinguish if an initial context should be applied. Known Problems 4-5 5 ________________________________________________________________ Restrictions The following restrictions apply to the Environment Manager's graphical user interface: 1. Keyboard traversals are unpredictable. If a dialog box is selected, for example, the settings menu option Symbols..., the insertion character "^" is not always displayed on the initial Symbol input field, but rather on the subsequent Definition field. Use the mouse to position the cursor on the desired input field, and click on the OK or Cancel buttons when you've completed input to the dialog box. The use of the Tab key to move between input fields is unpredictable. Use the mouse to move between input fields, then click on the OK or Cancel buttons when dialog box input is complete. Restrictions 5-1 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 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