DECset________________________________________ Release Notes for DIGITAL Test Manager Version 3.9 November 1998 These release notes for DIGITAL Test Manager Version 3.9 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 Test Manager for OpenVMS Systems, Version 3.9 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 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 1994, 1995, 1996, 1997, 1998. All rights reserved. © Electronic Data Systems Limited 1994, 1995, 1996, 1997, 1998. The following are trademarks of Digital Equipment Corporation: DEC Ada, DEC BASIC, DEC C, DECdocument, DECnet, DEC Pascal, DECset, DECwindows, DIGITAL, DIGITAL COBOL, DIGITAL Fortran, eXcursion, OpenVMS, OpenVMS Cluster, VAX, VAX BLISS-32, VAX DOCUMENT, and the DIGITAL logo. All other trademarks and registered trademarks are the property of their respective holders. This document was prepared using VAX DOCUMENT, Version 2.1. ________________________________________________________________ Contents Preface.................................................. v 1 General Information 1.1 Introduction.................................... 1-1 1.1.1 Documentation ................................ 1-1 1.2 Installation Requirements....................... 1-2 2 New Features 2.1 Improved DECwindows Support..................... 2-1 2.1.1 DECwindows Test Performance .................. 2-1 2.1.2 Button Arrangement ........................... 2-2 2.1.3 DECterm Window Configuration ................. 2-2 2.1.4 Screen Editor Enhancements ................... 2-2 2.2 64-bit Traceback Filtering...................... 2-3 2.3 Installation CMS Question....................... 2-3 2.4 Date Ambiguity Resolution....................... 2-4 3 Problems Fixed 4 Known Problems 4.1 General......................................... 4-1 4.2 DECwindows Interface............................ 4-5 iii 5 Restrictions 6 Reporting Problems and Suggestions Tables 1 Conventions .................................. vi iv ________________________________________________________________ Preface These release notes characterize the Version 3.9 release of DIGITAL Test Manager 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 DIGITAL Test 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 outstanding issues in the current release. o Chapter 5 describes all restrictions in the current release. o Chapter 6 describes how to report problems. v Sending DIGITAL Your Comments We welcome your comments on these release notes or any other pieces of documentation. See Chapter 6 for details of 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 Test Manager Version 3.9. 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 Test Manager Version 3.9 is a minor release. 1.1.1 Documentation The documentation of DIGITAL Test Manager 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 Test Manager are: o Guide to DIGITAL Test Manager for OpenVMS Systems o DIGITAL Test Manager 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 VAX V12.3 Software Product Description o DECset OpenVMS Alpha V12.3 Software Product Description General Information 1-1 o DECset Guide to Detailed Program Design for OpenVMS Systems o Using DECset for OpenVMS Systems New with this release is the "DECset Cookbook". This document contains technical articles giving instructions on the use of DECset components in particular situations. This document is provided online, in PostScript format, and can be found in: SYS$SYSROOT:[SYSHLP.EXAMPLES.DECSET]DECSET_COOKBOOK.PS 1.2 Installation Requirements For a new installation of DIGITAL Test Manager the following is required: OpenVMS Alpha Systems Global Pages 2100 Global Sections 10 Disk Blocks 25000 OpenVMS VAX Systems Global Pages 800 Global Sections 15 Disk Blocks 15000 1-2 General Information 2 ________________________________________________________________ New Features The following enhancements were added to DIGITAL Test Manager Version 3.9. 2.1 Improved DECwindows Support A number of enhancements to DIGITAL Test Manager have been made to improve the support for testing DECwindows applications. 2.1.1 DECwindows Test Performance The pointer motion during a test is recorded in XY records in the session file. Most of these records are unnecessary for the correct operation of the test. With this release these records are eliminated, except when one or more buttons are held pressed. On playback the pointer moves directly to the location of each button press, which speeds up the test execution. In some cases, it may be necessary to record all pointer motion, so a /POINTER_MOTION qualifier has been added to the RECORD command to specify whether pointer motion should be recorded. The default is /NOPOINTER_MOTION. A new toggle button has been added to the Record window to control this feature from the DECwindows interface. The SetSpeed and SetDelay records have been re-implemented to improve performance. These records give the user control over the test playback speed, allowing faster execution. New Features 2-1 2.1.2 Button Arrangement The Session Manager Pointer Options includes the choice of Button Arrangement as Right Handed or Left Handed. Tests which are recorded with DIGITAL Test Manager Version 3.9 take account of the Pointer Options Button Arrangement. Tests can be recorded and played with any combination of Button Arrangement and will operate correctly. Tests recorded with a version of DIGITAL Test Manager prior to Version 3.9 must be played with the same Button Arrangement as when they were recorded. 2.1.3 DECterm Window Configuration For the DECwindows interface to DIGITAL Test Manager, DECterm windows are created during RECORD, PLAY and RUN operations. Prior to Version 3.9, the position of these windows varied, resulting in test failures. From Version 3.9, the position and size of these DECterm windows is under user control. By default, the DECterm windows are created at screen coordinates (20,800) and contain 8 rows of text. This can be changed by defining logical names as described in section 2.2.3 of Guide to DIGITAL Test Manager for OpenVMS Systems. 2.1.4 Screen Editor Enhancements The Screen Editor is the tool that is used to review DECwindows test results and to create and modify masks. For DIGITAL Test Manager Version 3.9, the user interface has been improved in a number of ways: o The layout has been changed to make better use of the available space o The radio buttons which control the contents of the main display have been rationalized for greater clarity o The screen slider has been replaced with a scrolled list of screens, which shows the comparison status of each screen 2-2 New Features o The behavior when the number of screens in the test result is different from the benchmark has been improved, and the difference is explicitly shown in the scrolled list o The comparison status of each screen is retained when another screen is selected o The comparison status of a screen is updated when the screen is selected from the scrolled list o A "Compare All" button has been added to update the comparison status of all screens o A global mask, which applies to all screens, has been added o Radio buttons have been added to select the mask to be displayed o "on Context" help has been added The global mask is useful when tests fail due to a difference which affects several screens, for example if an unexpected window is present in the test results. By eliminating this area from the screen comparisons, other reasons for unsuccessful comparisons are more easily detected. The global mask is not included when masks are saved, so it does not affect collection comparisons involving the test. 2.2 64-bit Traceback Filtering The traceback filter has been extended to include filtering of 64-bit tracebacks produced on Alpha systems. 2.3 Installation CMS Question Using the version of DIGITAL Test Manager with built-in CMS support consumes a CMS license, which can result in a CMS license shortage. Before Version 3.9, the version with built-in CMS support was always installed if CMS was already installed. The installation procedure has been enhanced to give the option to install the version of DIGITAL Test Manager without built-in CMS support. New Features 2-3 2.4 Date Ambiguity Resolution In date formats where the year is represented as a two- digit number, dates in the range 1-JAN-2001 to 31-DEC-2031 are ambiguous. For example, 03-JUN-04 could be 3-JUN-2004 or 4-JUN-2003. Therefore, tests that use the date filter on dates in the affected formats might fail to match their benchmarks when these dates occur in the result. The affected date formats are those in which the year comes first. For example, the date 98-JUN-02 is filtered into yy-mmm-dd since there is no ambiguity in resolving the day versus year, but 01-JUN-02 is filtered into dd- mmm-yy. However, formats where the year comes last are not affected. For example, both 02-JUN-98 and 02-JUN-01 are filtered into dd-mmm-yy. The affected date formats, with their allowed punctuation characters, are the following: yy-mm-dd yy.mm.dd yy/mm/dd yy-mmm-dd yy.mmm.dd yy mmm dd year-month-day year.month.day year month day The alternative punctuation characters can be used in either or both positions, such as yy-mm/dd. Tests which use the date filter on dates in the affected formats will fail to match their benchmarks once dates in the affected range occur in the result. A new logical variable, DTM$DATE_FILTER_FIRST, has been added to provide control over how this ambiguity should be resolved. If this variable is defined to the value "YEAR", then ambiguities will be resolved so that the year occurs first. If this variable is not defined or the value is not "YEAR", then ambiguities will be resolved so that the day or month occurs first. 2-4 New Features In order to detect if any action is required, the benchmark files can be searched for any occurrences of the filtered text resulting from the affected formats. This can be done with the commands: $ SEARCH benchmark_files yy,mm,dd /MATCH=AND $ SEARCH benchmark_files year,month,day /MATCH=AND Any occurrences can then be examined to see if they are in the affected formats. The DTM$DATE_FILTER_FIRST variable can then be applied globally or to individual tests as necessary, as described in section 6.3.4.6 of Guide to DIGITAL Test Manager for OpenVMS Systems. It will not then be necessary to update any benchmark files. An alternative solution, which also works if there are dates which conflict on how the ambiguity should be resolved within a single test, is to fix the filter text for all dates. This can be done by defining the logical variable DTM$DATE_FILTER_STRING, as described in section 6.3.4.5 of Guide to DIGITAL Test Manager for OpenVMS Systems. This method will also require benchmark files to be updated. Note also that in formats where the month is a number, rather than a month name, the possible replacement strings are yy-mm-dd and mm-dd-yy, but not dd-mm-yy. This is because in order to support both USA and European date formats, the range of values accepted as months has always been extended to include the full range of valid days i.e. 1 to 31. The consequence is that for dates between 1-JAN-2013 and 31-DEC-2031, the formats where the month is a number and the year is a two-digit number will be filtered into mm-dd-yy by default, even though the first number is not a valid month number. For example, 15-10-07 will be filtered into mm-dd-yy by default. Once again, the variable DTM$DATE_FILTER_FIRST can be used if the correct interpretation is yy-mm-dd. New Features 2-5 3 ________________________________________________________________ Problems Fixed The following bugs were fixed and restrictions were removed in DIGITAL Test Manager Version 3.9. o Bug 699 - FILTER command purged all previous versions of filtered file. The FILTER command no longer generates any intermediate files, so no purging is performed. o Bug 797 - DCL help for DEFINE/KEY topics generated errors. On-line help is now provided for the topics listed under DTM HELP DEFINE /KEY. o Bug 892 - Redefining default KEYSYM caused problems. The problems associated with redefining the default KEYSYM for DECwindows tests have been rectified. In order to change the KEYSYM that applies to the RUN or SUBMIT commands, modify the DXDTMPLAYREC.DAT resource file as described in section 9.2.2 of Guide to DIGITAL Test Manager for OpenVMS Systems. o Bug 894 - The RECORD/INPUT=file command for DECwindows tests now functions correctly. o Bug 911 - DECwindows review display widget did not function properly. The following improvements have been made to the DECwindows display widget that controls the review of screen terminal tests when the difference file is displayed: o The screen number is now displayed in the review window, and can be toggled on and off to reveal any hidden text. Problems Fixed 3-1 o The selection box to enable the way that differences are shown to be changed from Bold to Underline now works. o The 'Working' marker, a flag that has the blinking video attribute set to show that DIGITAL Test Manager is searching for the next screen, is now visible. A new button has been added to shift the display to enable all parts of the screen to be viewed. The screen number is also displayed in the review window for the benchmark and result file displays. o Bug 915 - The Internal error that occurred recreating a collection which performs masking has been fixed. o Bug 932 - Directory specifications were not filtered correctly. Directory specifications are now filtered and masked as intended and invalid specifications are not filtered or masked. o Bug 933 - The access violation that occurred when viewing an empty result file has been fixed. o Bug 935 - Filename filtering added spurious characters. The filename filter no longer adds spurious characters to the end of some lines. o Bug 936 - The FILTER command ignored input file version number The FILTER command now processes the correct file version when a version number is specified for the input file. o Bug 938 - Applying multiple masks resulted in unsuccessful comparisons. For interactive tests, using more than one mask, other than filename and version, always resulted in unsuccessful comparisons. Multiple masks are now processed correctly. o Bug 939 - Masks were applied in the wrong order. 3-2 Problems Fixed For interactive tests, when the directory mask and the filename and/or version masks were applied, the directory mask was applied first. This was not as described in the help information, and could cause filenames and versions not to be masked, resulting in unsuccessful comparisons. The directory mask is now applied after the filename and version masks. o Bug 940 - Comparing collections updated masks. For DECwindows tests, each time a test with a benchmark held in a CMS library was compared, the corresponding mask file was updated in CMS. This behavior has been corrected. o Bug 949 - Problems with collections created /NOVERIFY When a collection was created /NOVERIFY and any of the prologue, template or epilogue for a test were not accessed from a CMS library, the files not accessed from CMS and subsequent files were executed with message output turned off and with the wrong CMS library set. The absence of messages could cause tests that failed to appear to pass. The problem of setting the wrong CMS library could cause CMS operations to fail or to affect the wrong library. This problem affected tests that set a CMS library in one file and used it in another. For example, a test that set the CMS library in a prologue and used it in the template was affected. These problems have now been corrected. o These documentation problems are addressed in the revised documentation set issued with this release: o Bug 901 - Formatting tag "only/bold" in the Guide to DIGITAL Test Manager for OpenVMS Systems has been corrected. o Bug 902 - NOMSGBLK error message is now documented. o Bug 910 - Updating a benchmark file example has been corrected. Problems Fixed 3-3 o Bug 912 - Default mask file extension is now correctly shown as .MXK. o Bug 913 - Window borders added to Figure 2-1 "Title Bar and Main Menus". 3-4 Problems Fixed 4 ________________________________________________________________ Known Problems 4.1 General The following known problems exist for DIGITAL Test Manager Version 3.9: o Bug 404 - SUBMIT/CHARACTERISTICS command fails to set multiple characteristics. When using the DCL qualifier /CHARACTERISTICS for the DIGITAL Test Manager command SUBMIT, DIGITAL Test Manager sets only the first characteristic specified on the created batch job. All other characteristics are ignored. o Bug 558 - Character comparison works incorrectly. The character comparison facility incorrectly stops comparison upon detection of the first difference between a result and benchmark file. o Bug 621 - Use of DTM$OMIT_SCREENS causes erroneous error messages. Using the variable DTM$OMIT_SCREENS to prevent the creation of .RES_SCREENS and .BMK_SCREENS files will result in erroneous error messages being displayed when attempting to update the benchmark file for an interactive terminal test. The messages will state that the .BMK_SCREENS file could not be updated. These messages can be ignored. o Bug 623 - Global variables not used when recording using RECORD/VARIABLE. Known Problems 4-1 The RECORD /VARIABLE command does not define the global variables defined in the library for the recording session. It only defines the local variables associated with the test. Global variables are defined when a test is executed. The consequence is that global variables cannot be referenced during recording or in test prologue or epilogue files if /PROLOGUE or /EPILOGUE was specified on the RECORD command. o Bug 645 - Rooted logicals cause failures when tests are compared. Rooted logical names are not valid in the specification of test benchmark files. If used, the test will execute successfully but the comparison of the test result file and the benchmark file will fail. The test benchmark file can be amended using the commands: CREATE, MODIFY TEST /BENCHMARK and SET BENCHMARK_DIRECTORY. An example of a rooted logical definition is DISK$:[USER.]. o Bug 671 - Drawing using REGIS causes DIGITAL Test Manager to hang. Using the interactive terminal record function to record tests of applications which perform drawing using REGIS causes DIGITAL Test Manager to hang. This occurs due to a buffer limit inside DIGITAL Test Manager. o Bug 693 - Embedded quotes not valid with /COMMAND qualifier. Embedded quotes are not valid with the /COMMAND qualifier for CREATE and MODIFY TEST. The command will be accepted, but the embedded quotes will be removed when the command is executed as part of test execution or recording. o Bug 744 - DTM STOP command can delete the wrong batch job. If a collection is submitted to batch and terminates, DIGITAL Test Manager will believe the collection is still running. If the DIGITAL Test Manager STOP command is specified for this collection, DIGITAL Test Manager will attempt to delete the batch job created for the collection when it was submitted by using the entry 4-2 Known Problems number for the job. However, the job created for the collection no longer exists, which then allows the queue manager to use the original entry number. The result is that DIGITAL Test Manager can delete the wrong batch job. The DCL commands SHOW QUEUE and/or SHOW ENTRY should be used to verify that the collection is still executing, before using the DIGITAL Test Manager STOP command. If the collection is not currently executing, the VERIFY /RECOVER command should be used to correct the inconsistency in the DIGITAL Test Manager library. o Bug 753 - DCL help on keypad definitions generates errors. On-line help for the DCL interface does not contain information for keypad definitions. Pressing PF2 to access this help topic will generate an error message. For information on the keypad definitions, see the Guide to DIGITAL Test Manager for OpenVMS Systems. o Bug 835 - Using /REALTIME qualifier with RECORD/INPUT can result in slow test execution. Specifying the /REALTIME qualifier on the RECORD /INPUT command to record an interactive terminal test, where the input file contains WAIT records, results in duplication of wait records in the new session file. This causes substantially slower test execution. The workaround is to remove unwanted WAIT records from the session file. See the Guide to DIGITAL Test Manager for OpenVMS Systems for information about these topics. o Bug 893 - DECwindows testing problems repositioning windows. A test recording containing an action to reposition a window will cause the test to hang and the mouse pointer to change to the "+ with arrowheads". The test will only continue, from the original reposition action, if the window is repositioned manually and MB1 clicked. A similar problem occurs if windows are resized, except the mouse pointer changes to a resize cursor. Known Problems 4-3 The workaround to the repositioning problem is to set the Workspace Options to "When moving a window, show the entire window" rather than showing the outline only. This works whichever option was applicable when the test was recorded. There is no equivalent workaround for the resizing problem. o Bug 947 - Failure with DECwindows test on OpenVMS V7.1 Alpha The screensave operation for DECwindows tests may fail on systems with OpenVMS V7.1 Alpha. The problem occurs on systems with some TGA graphics cards. When the failure occurs, the following messages are displayed: X Error of failed request: BadColor (invalid Colormap... Major opcode of failed request: 91 (X_QueryColors) Resource id in failed request: number Serial number of failed request: number Current serial number in output stream: number %XLIB-E-ERROREVENT, error event received from server The failure can occur when the tests are recorded or played. The test will continue, but the screen is not saved. The workaround for this problem is to install DIGITAL Open3D for OpenVMS Alpha Version 4.6. Note that no license is required to install Open3D and use only its 2D graphics capabilities which include a resolution of this problem. o Bug 950 - Spurious warning message running collections created /NOVERIFY When a collection that was created with the /NOVERIFY qualifier is run, the following warning message may be output: %DCL-W-IVVERB, unrecognized command verb... \01DEF\ The warning message is written to the collection log file for collections executed with the SUBMIT command. For collections executed with the RUN command, the message is written to the terminal. 4-4 Known Problems Test results are not affected by this bug. No user action is required. The message can be ignored. 4.2 DECwindows Interface The following known problems exist for the DECwindows interface in DIGITAL Test Manager Version 3.9: o Bug 49 - Variable View remarks missing Remarks associated with variables are not displayed in the Variable View. To determine the remarks associated with variables, use the SHOW VARIABLE command from the DCL interface. o Bug 364 - Subgroups remarks missing in Group View Remarks associated with subgroups are not displayed in the Group View. To determine the remarks associated with subgroups, use the SHOW GROUP command from the DCL interface. o Bug 398 - "^P W" and "^P !" commands for interactive terminal tests do not work When recording interactive terminal tests using the DECwindows interface, the "^P W" and "^P !" commands to enter wait records and comments do not work. If these capabilities are required, record interactive terminal tests from the DCL interface. o Bug 678 - Create and Modify Test dialog boxes do not allow a variable value containing commas The Modify Test and Create Test dialog boxes do not allow variables where the variable value contains commas. For example, a variable X with a value of "A,B,C" cannot be specified. Use the CREATE TEST and MODIFY TEST commands under the DCL interface. o Bug 686 - Stop using Tasks dialog box corrupts collection The Tasks dialog box stops active tasks by killing the process associated with the task. If an executing collection is stopped using the Tasks dialog box, it is necessary to recover the DIGITAL Test Manager library from the DECwindows interface via the Verify dialog box Known Problems 4-5 accessible from the Library option of the File menu, or via DCL command VERIFY /RECOVER. o Bug 914 - Access violation running interactive tests which use SET HOST in DECwindows. An interactive test that performs a SET HOST command will crash, and the test window disappear, if it is run from the DECwindows interface. o Bug 931 - Failure with DECwindows V1.2-4. Operations which create a DECterm to display messages may hang when DIGITAL Test Manager is used with DECwindows Motif V1.2-4. After two minutes the hang times out and an error message may be displayed. The operations affected include recording and playing interactive terminal and DECwindows tests, running and comparing collections and displaying interactive test result files, benchmark files or difference files. The problem arises from a DECwindows Motif defect which prevents the creation of the DECterm. Specifically, DECwindows creates a terminal controller with the wrong language information and therefore the terminal controller never connects with DIGITAL test manager's request to create a terminal. The problem does not occur if the display used for the DIGITAL Test Manager windows is running the New Desktop. The workaround for this problem is to set the "*xnlLanguage" X-resource to the value "NO_LANG". The easiest way to set this resource is to add to the SYS$LOGIN:DECW$XDEFAULTS.DAT file (creating it if need be) the line: *xnlLanguage: NO_LANG When next logging in to a new session this will take effect. In a purely English language environment this workaround should not have any drawbacks. In a multi- lingual environment there may be side effects on some applications as their language defaults are overridden. These will need to be determined empirically. 4-6 Known Problems o Bug 945 - Error creating collection containing terminal test Creating a terminal test, recording it and then creating a collection containing the test gives an error indicating that the session file for the test does not exist. The problem only occurs if all the operations are carried out within a single invocation of DIGITAL Test Manager. The workaround is to create a dummy session file before starting DIGITAL Test Manager. Alternatively, exit and reenter DIGITAL Test Manager when the problem occurs. o Bug 946 - Collection View remarks missing Remarks associated with collections are not displayed in the Collection View. To determine the remarks associated with variables, use the SHOW COLLECTION command from the DCL interface. o Bug 948 - Updating benchmark held in CMS library may fail Using the DECwindows interface to update a benchmark which is held in a CMS library may not work. The behavior depends on the sequence of mouse operations performed and the type of test involved. If the update fails, an error message is reported. In some circumstances the benchmark file is updated in the CMS library, but the update operation fails when the new generation cannot be inserted into a CMS class. In this case, the status of the test in the collection being reviewed becomes "Result Description Error". The workaround is, after opening the collection for review, to select tests for update without any intervening mouse clicks. To facilitate this, double click on the collection to display the list of tests before opening the collection for review. Known Problems 4-7 5 ________________________________________________________________ Restrictions The following restrictions exist for DIGITAL Test Manager Version 3.9: o Under OpenVMS V7.2 the syntax of a valid filename has been enhanced to allow additional characters. If test results contain a filename adjacent to one of these characters then the directory and filename filters will treat the character as part of the filename whereas on previous versions of OpenVMS it would have been left in the filtered output. For example, the string: ~dev:[ddd]ffff.eee~ would have been filtered as: ~DISK:[DIRECTORY]FILENAME.EXT~ but will now be filtered as: DISK:[DIRECTORY]FILENAME.EXT the leading and trailing '~' having been absorbed into the file specification. The characters that are now treated differently are '^', '-' and '~'. 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 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 Test Manager 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