DECset________________________________________ Release Notes for DIGITAL LSE Version 4.6 November 1998 These release notes for DIGITAL Language-Sensitive Editor Version 4.6 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 Language- Sensitive Editor for OpenVMS Systems, Version 4.6 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 documentation is authorized only pursuant to a valid written license from DIGITAL, an authorized sublicensor, or the identified licenser. 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 1994, 1996, 1997, 1998. All rights reserved. © Electronic Data Systems Limited 1994, 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.2 Documentation................................... 1-1 1.3 Installation Requirements....................... 1-2 1.4 Compatibility Issues............................ 1-2 2 New Features 2.1 Ability to Globally Turn Off UNDO............... 2-1 2.2 Ability to Tab Using Space Characters........... 2-1 2.3 Provision of Missing Example TPU File........... 2-1 2.4 Example Language and Operation Extensions....... 2-1 3 Problems Fixed 4 Known Problems 4.1 General......................................... 4-1 5 Restrictions iii 6 Reporting Problems and Suggestions Tables 1 Conventions .................................. vi iv ________________________________________________________________ Preface These release notes characterize the Version 4.6 release of DIGITAL Language-Sensitive Editor for OpenVMS VAX and OpenVMS Alpha. 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 the DIGITAL Language- Sensitive Editor 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 Language-Sensitive Editor Version 4.6. 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 This version of DIGITAL Language-Sensitive Editor is a minor release. 1.2 Documentation The documentation of DIGITAL Language-Sensitive Editor and of DECset has been revised for this release. This revision corrects errors, enhances descriptions, and describes all new functionality. The documents associated with DIGITAL Language-Sensitive Editor are: o Guide to DIGITAL Language-Sensitive Editor for OpenVMS Systems o DIGITAL Language-Sensitive Editor/Source Code Analyzer for OpenVMS 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 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 o Guide to DIGITAL Source Code Analyzer 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.3 Installation Requirements For a new installation of LSE the following is required: OpenVMS Alpha Systems Global Pages 8600 Global Sections 15 Disk Blocks 42000 OpenVMS VAX Systems Global Pages 6000 Global Sections 15 Disk Blocks 40000 1.4 Compatibility Issues In versions of LSE prior to V4.3 the UNDO command is implemented to reverse the effect of the last ENTER COMMENT command. This effect can still be achieved if the user specifies the following format: UNDO ENTER [COMMENT] 1-2 General Information 2 ________________________________________________________________ New Features The following enhancements were added to DIGITAL Language- Sensitive Editor for Version 4.6. 2.1 Ability to Globally Turn Off UNDO A new global attribute has been added to control UNDO processing. For details see the description of the SET MODE (keyword UNDO) command in the DIGITAL Language-Sensitive Editor /Source Code Analyzer for OpenVMS Reference Manual. 2.2 Ability to Tab Using Space Characters A new global attribute has been added to control whether new tabs are represented by tab or space characters. For details see the description of the SET MODE (keyword TABS) command in the DIGITAL Language-Sensitive Editor /Source Code Analyzer for OpenVMS Reference Manual. 2.3 Provision of Missing Example TPU File File PACKAGE_SUPPORT.TPU has been added to the example TPU files directory (LSE$EXAMPLE). 2.4 Example Language and Operation Extensions Example files for a large number of languages and editing extensions have been added to the examples directory (LSE$EXAMPLE). Also included are command files to build a version of LSE with the extensions and a "read me" file XLSE_READ_ME.TXT which describes the extensions, how to build them, the commands and keys that access them plus some examples. New Features 2-1 The extensions include languages such as DCL, HTML and MMS, and operations such as rectangular cut and paste, an EMACS style incremental search and comparing a buffer with an external file. 2-2 New Features 3 ________________________________________________________________ Problems Fixed The following bugs were fixed and restrictions removed in DIGITAL Language-Sensitive Editor Version 4.6: o Bug 2163 - Blank comment lines are no longer incor- rectly created when wrapping is turned on and comments are added near the right margin. o Bug 2192 - CHECK LANGUAGE/HELP now correctly reports topics for which there is no help information. o Bug 2206 - Issuing a SET SCREEN HEIGHT command to adjust the screen height no longer causes LSE to hang. o Bug 2213 - Definition of an invalid key no longer causes subsequent definitions to fail. o Bug 2232 - The Buffer Attributes Window Apply & OK actions no longer fail if the Read Only/Write state has been changed. o Bug 2233 - An empty mark name can no longer be set. o Bug 2234 - The error that caused a stack dump following a license failure message has been fixed. o Bug 2238 - The error that caused a memory deallocation failure when the use of the View menu option Overview Source was followed by a FOCUS command has been fixed. o Bug 2239 - The error that resulted in an UNDO command removing a line of text from a buffer that was not inserted as the previous operation has been fixed. o Bug 2241 - The portable help no longer contains documentation index tags. o Bug 2242 - The SHOW BUFFER 'Cmp' field is no longer left unset following a compilation of the buffer using the OpenVMS syntax COMPILE command. Problems Fixed 3-1 o Bug 2244 - Online help is no longer missing for the EXECUTE BUFFER LSE portable command. o Bug 2249 - The fault that resulted in an unexpected internal error if command mode was entered by positioning the mouse on the command prompt has been fixed. o These documentation problems are addressed in the revised documentation set issued with this release: o Bug 2162 - The description of the ERASE PLACEHOLDER command did not describe the fact that a space may be inserted depending on the context. o Bug 2170 - LSE SHOW BUFFER documentation was incorrect. o Bug 2183 - Portable commands were not documented in LSE/SCA reference manual. o Bug 2185 - The syntax in the NEW FILE command example was incorrect. o Bug 2197 - The SET PLACEHOLDER BODY LINE examples were incorrect. o Bug 2219 - The SHOW BUFFER/BRIEF command description was incorrect. 3-2 Problems Fixed 4 ________________________________________________________________ Known Problems 4.1 General The following known problems exist in DIGITAL Language- Sensitive Editor Version 4.6: o Bug 2149 - QUOTE command followed by DO results in error. Using the QUOTE command to enter the control sequence for the DO key, in DECwindows mode, results in an error. o Bug 2150 - LSE stair stepping tabs after continuation characters. LSE is stair-stepping using tabs after continuation characters when using the Fortran language templates. Use LSE to edit any Fortran program. When entering in continuation lines, tab in once to put the continuation character ('1'..'9'), then twice to start the code. Use a continuation line on the next line and tab again. The cursor will be indented an extra space. As more lines are entered, the code will continue to line up with an extra space. For example: $ LSE temp.FOR 1 T 1 E 1 S 1 T This only happens using the Fortran language templates. o Bug 2151 - LSE RECOVER BUFFER/ALL command is not recovering buffers. Known Problems 4-1 Attempting to recover multiple buffers using the command RECOVER BUFFER/ALL or RECOVER BUFFER *, after an LSE session has been abnormally aborted, will result in the message `Recovering from all journal files...' but no buffers will be recovered. The workaround is to recover all the buffers indi- vidually using the command RECOVER BUFFER [BUFFER_ NAME]. o Bug 2155 - Internal error compiling DECforms program after an Ada program. LSE will crash with an internal error when attempting to follow the compilation of an Ada program with the compilation of DECforms source. The source of the two programs appears to be unimportant. The workaround is to compile the DECforms source first. o Bug 2156 - SCA LOAD and ANALYZE command parameters don't default to current buffer. The file-spec[,..] parameter cannot be defaulted, the HELP information incorrectly says the default is the current buffer. o Bug 2158 - Cannot define an ALT key sequence as the Gold key. LSE cannot accept an ALT key sequence as the Gold key. When an attempt is made, LSE accepts the key definition without errors, but does not recognize the ALT key sequence as the Gold key (this definition does however disable PF1 as the Gold key), however if you show the key definitions the newly defined key has the correct definition. Different results are apparent depending on whether the DECwindows interface to LSE is used or if the character-cell mode interface to LSE is used. For example, in the DECwindows mode, ALT/G can be defined as the Gold key. LSE accepts the key definition, but ALT/G is not recognized as the Gold key. However, if SHIFT/ALT/G is pressed then LSE recognizes it as the Gold key. In the character-cell interface not even SHIFT/ALT/G is recognized. Again, LSE accepts the definition of ALT/G as the Gold key without errors. 4-2 Known Problems The workaround is to define the key via TPU: LSE> do/tpu "set(shift_key,key_name('g',alt_modified) o Bug 2161 - Loop doing CTRL/C when reading in a file. While a file is being read into an LSE session via the READ/BUFFER command, CTRL/C cancels the command and LSE will loop displaying the message 'Command Canceled' repeatedly. The workaround is not to use CTRL/C. o Bug 2164 - TPU$_WINDNOTMAPPED error reading TPU procedure into DECwindows LSE. DECwindows LSE may report the following error when trying to read in and compile a TPU procedure at startup: The window is not mapped to a buffer (TPU$_WINDNOTMAPPED). When this problem occurs, LSE will display an invalid window format (one that does not have a status line). The errors themselves will not be visible unless you display the contents of the message buffer. For example: DO LSE> GOTO BUFFER $MESSAGES ! a normal window is display for buffer $MAIN DO LSE> GOTO BUFFER $MESSAGES The workaround is to start LSE with the command LSE /COMMAND=DE_TAB.TPU and add the following line at the bottom of the DE_TAB.TPU procedure: LSE_NEW_KEY( "TAB", "TPU REM_TABS" ); This will automatically read in the TPU procedure, compile it and define an LSE key to run it. o Bug 2165 - DECwindows SET DEFAULT does not change default disk after OPEN FILE. Known Problems 4-3 In the LSE DECwindows interface, the SET DEFAULT command does not change the default device when issued after using the OPEN FILE command. It correctly changes the default directory but not the device. Prior to calling OPEN FILE, SET DEFAULT works as required. When you exit LSE your default device is changed. The workaround is to perform the SET DEFAULT command before opening any files in the DECwindows interface or specify the default directory as the filter specification in the open file window. o Bug 2166 - Cursor returned to wrong window after compile. LSE does not always correctly position the cursor following the completion of a command. For example after the compile command has completed, the cursor does not return to the window that the COMPILE command was invoked from. The workaround is to manually position the cursor to the desired window. o Bug 2168 - Channel leak in LSE WRITE if writing files across the network. Channels that are opened to write files across the network are not released. Using the WRITE command repeatedly will result in a fatal error upon exhausting the resources available to the process. There is no workaround to this problem. o Bug 2173 - Directory not found. If a new file is created using the NEW FILE command or the `New File' option without specifying a directory, the following error is reported : Directory not found Message number 00000000 No workaround is required, the message can be ignored. o Bug 2174 - Cursor positioning across split screens. 4-4 Known Problems When splitting a file into two or more screens, the cursor correctly maintains its position when going back and forth between the windows. However, using the up or down arrows can cause the cursor to change column position to the same position in the other screen. This problem occurs only when moving up or down or the last operation is an up/down motion. For example, moving up in the top screen in column 30, then switching to the bottom screen and trying to move up in column 10: the cursor jumps to column 30. If you first move the cursor left/right or perform any other action, the cursor stays in the column expected. The problem only occurs when using the portable command language interface. o Bug 2181 - DECwindows LSE cannot change default window size. Changing the default size of the LSE DECwindows Main window by changing the values of Tpu.Tpu$MainWindow.Columns and Tpu.Tpu$MainWindow.Rows in DECW$USER_DEFAULTS: LSE$DEFAULTS.DAT may not work. The workaround involves using the Window Attributes window to set the desired values and then saving the section file. If LSE is invoked with the new section file it will come up with the new window size. o Bug 2193 - Files selected from CMS DECwindows not placed into LSE DECwindows buffer. When the DECwindows topShadowColor color is the same as the DECwindows background color or the monitor being used is monochrome, files reserved or fetched using the CMS DECwindows interface are not placed into the LSE DECwindows buffer. The file is, however, correctly fetched or reserved from the CMS library. o Bug 2196 - The portable interface to LSE does not recognize new file types. Using the portable command language, if a language is modified to recognize new file types via SET LANGUAGE FILE TYPES, new buffers created with the new file types may not be set to that language. The SHOW LANGUAGE Known Problems 4-5 command however shows that the file types have been added. The workaround is to ensure that the file types are specified in upper case. Another workaround is to use the VMSLSE interface (MODIFY LANGUAGE/FILE_TYPES=(...) command). o Bug 2198 - Cannot access help text after using ENABLE VMS INTEGRATION. After issuing the ENABLE VMS INTEGRATION command, a HELP FIND returns "No help available for the topic specified". HELP GOTO DECLARATION has the same problem, but the other HELP commands work fine. The workaround is to issue a DISABLE VMS INTEGRATION before the HELP command. o Bug 2199 - Errors when re-sizing LSE window in portable interface. In the DECwindows interface, with the Portable command language, after expanding a command token on the LSE command line, re-sizing the LSE window causes a series of errors including "unexpected internal error" and repeatedly re-sizing the window causes LSE to access violate. There is no known workaround. o Bug 2212 - Error in initialization if editing a file in a CMS library. If LSE is started by specifying a file in a CMS library directory, LSE asks if the file should be fetched. If the reply is No, LSE then gives an "Error occurred during initialization. The editor may not function properly." message. LSE also starts up with a $DEFAULTS buffer rather than $MAIN. Everything else appears normal. o Bug 2216 - SET DIRECTORY DEFAULT not propagated to current compile subprocess. LSE's portable command language does not propagate changes in the default directory to an already existing compile subprocess; causing the next COMPILE REVIEW command to fail with "Error opening ". 4-6 Known Problems o Bug 2220 - UNDO access violation changing lines using keys bound to TPU procedures. The fault can occur if user written TPU code is associated with a key. The fault can occur in the setting up of information required to support undo/redo processing for user written TPU code associated with a key. When the key is used the call of the associated code is not jacketed by any LSE code and can not be protected against undo/redo problems. Four possible workarounds are: 1. Disabling undo/redo processing by means of the SET MODE UNDO (SET UNDO portable) command. 2. Setting the value of MAX_UNDO to zero for each buffer being edited; this may be done via a key definition: For example: LSE Command> DEFINE KEY "F17" "SET MAX_UNDO 0" 3. Defining all your keys using the LSE "DEFINE KEY" or "NEW KEY" commands. For example: LSE Command> DEFINE KEY _Key: "GOLD-Z" _String: "do/tpu """"" or: LSE> NEW KEY Key Name: GOLD-Z LSE Command: tpu "" 4. Making the TPU code to be executed by the defined key a parameter of the routine lse_tpu. This routine protects against undo/redo problems by deleting the undo/redo information for all buffers and inhibiting the setting up of any undo/redo information during the execution of the TPU code associated with the key. Known Problems 4-7 For example:- define_key("lse_tpu('position(buffer_begin)')", key_name("x",shift_key)) o Bug 2222 - Incorrect undo after expanding a menu placeholder. An undo following the expansion of a menu placeholder may not produce the correct result. For example: An UNDO after CONTINUE has been selected from a placeholder menu for the following Pascal code program test (input, output); begin REWRITE( %{file_variable}%, ERROR := CONTINUE ) end. produces program test (input, output); begin REWRITE( %{file_variable}%, ERROR := ) end. instead of program test (input, output); begin REWRITE( %{file_variable}%, ERROR := %[error_recovery]% ) end. o Bug 2223 - Incorrect undo after replacing a placeholder with undelete line. An undo following the replacement of a placeholder by undeleting a line may not produce the correct result. o Bug 2225 - A very long command line can produce inappropriate errors. A very long command can produce inappropriate errors such as 'Compilation aborted'. 4-8 Known Problems For example: LSE> NEW FILE AAAAAA:[BBBBBBBBBBBBBBBBBBBBBBBB.... Line truncated to 256 characters ; 0001 LSE_NEW_FILE("AAAAAA:[BBBB.... ; ^ Missing quote ; 0002 One of the following symbols was expected: ; , ) ; 0002 ; ^ Premature end-of-file detected Compilation aborted Execution aborted Execution aborted (TPU$_EXECUTEFAIL) unexpected internal error in lse$$command_undefined_key_proc at line 4922. Please submit an SPR. o Bug 2227 - SHOW TOKEN/PLACEHOLDER may not show all relevant items. SHOW TOKEN and SHOW PLACEHOLDER do not show aliased tokens or placeholders. For example with the language Ada :- SHOW TOKEN A* does not show any tokens. SHOW TOKEN ACCEPT shows information for (aliased) token ACCEPT token : ACCEPT description : Specifies the resulting action of a task entry call help topic : Statements Accept_Statement language : ADA o Bug 2228 - LSE may fail when executing user's TPU code via a pull-down menu or a user command language. This is similar to bug 2220. Known Problems 4-9 o Bug 2229 - A spurious error message may be produced when the help command is issued for a long non-existent topic. For example: LSE> HELP Nonexistent_topic Error opening LSE$HELP as input No help available for the topic specified o Bug 2230 - LSE fails with an access violation if a DO /LSE or DO/TPU command is executed when there are no buffers set up in the editor. o Bug 2231 - If a buffer which has been reviewed is deleted using the DELETE BUFFER command the REVIEW information associated with the buffer is not cleaned up. For example, following the deletion, the END REVIEW command does not produce the error "NO REVIEW IN PROGRESS". o Bug 2236 - The LSE$CURRENT_FILE logical name is not updated after exit from LSE editor if there is an error encountered during compile/review. o Bug 2237 - An UNDO of a PASTE command may be done incorrectly. o Bug 2243 - CTRL/C may not be correctly handled if issued while a DO command is processing a buffer. o Bug 2245 - The VMS and portable syntax commands are not consistent in their generation of brief or full information. The /FULL qualifier does not always result in a full display and the /BRIEF qualifier does not always produce a brief display. o Bug 2246 - The SHOW KEY key-specifier command can display an incorrect value when a key defined with the qualifier STATE=GOLD is redefined. For example: LSE> DEFINE KEY/STATE=GOLD ALT/G LSE> SHOW KEY ALT/G key name : ALT/G *** set STATE=GOLD *** topic : GOLD legend : GOLD 4-10 Known Problems LSE> DEFINE KEY ALT/G LSE_BOTTOM LSE> SHOW KEY ALT/G does not show new value of ALT/G key name : ALT/G *** set STATE=GOLD *** topic : GOLD legend : GOLD LSE> SHOW KEY correctly shows new value of ALT/G ... ALT/C TPU LSE$KEY_COPY_TO_CLIPBOARD ALT/G LSE_BOTTOM GOLD-L LSE ENTER COMMENT LINE ... o Bug 2247 - Command mode prompt problem. The 'LSE>' prompt is at times improperly displayed when the 'LSE Command>' prompt for single command mode is expected. o Bug 2248 - Initial entry to command mode problem. In DECwindows mode if the first action is a PF1,KP7 key sequence this may not result in LSE entering command mode. If command mode is not entered the KP7 key will perform it's non PF1 action (PAGE) and this may result in the error 'Attempt to move past the end of buffer $MAIN'. o Bug 2253 - Undo of soft tab conversion of hard tab produces a space. With hard tabs off if a tab is inserted after a hard tab character the tab is converted to spaces. If the insert is then undone the converted tab character is not replaced instead a single space is left. o Bug 2254 - Unavailable SCA commands. The SCA commands IMPORT, SAVE QUERY and @file-spec are not available from LSE. Known Problems 4-11 5 ________________________________________________________________ Restrictions The following restrictions apply to LSE Version 4.6: o LSE does not support VT500 series terminals. A VT500 series terminal should be set to emulate a supported terminal such as a VT300 series terminal. o The UNDO operation has no effect for the LSE FOCUS command. When the FOCUS command is executed, the UNDO buffers will be reset. No previous operations can be undone. o No UNDO support for TPU commands. For example : TPU "erase (current_buffer)" (PLSE) DO/TPU "erase (current_buffer)" (VMSLSE) When a TPU command is executed, the UNDO buffers will be reset. No previous operations can be undone. o UNDO and REDO commands are disabled in OVERSTRIKE mode. If the buffer is in OVERSTRIKE mode (not insert), initiating the UNDO or REDO command will have no effect. When the mode is changed to INSERT, undoing and redoing is possible again. o DIGITAL Fortran - Fortran 90 Language Support. Automatic generation of continuation lines is not supported. o DECnet/OSI Phase V support. When using portable syntax commands, file names that start with a quote must be enclosed in quotes (single or double) with inner quotes of the same type as the enclosing quotes doubled up. Restrictions 5-1 For example: LSE> NEW FILE '"A&=BCD"::B.C' LSE> NEW FILE """AAAAAAAAAAAAAAA""::B.C" 5-2 Restrictions 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 problems 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 now 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 report, please include the following information: 1. DIGITAL Language-Sensitive Editor version 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 diskettes, or tape cassettes. 6-2 Reporting Problems and Suggestions