DECset________________________________________ Release Notes for DIGITAL Test Manager Version 3.8-2 August 1997 These release notes for DIGITAL Test Manager Version 3.8-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, Version 6.1 - Version 7.1 OpenVMS Alpha, Version 6.1 - Version 7.1 DECwindows Motif, Version 1.1 - Version 1.2 Software Version: DECset for OpenVMS, Version 12.2 Software Version: DIGITAL Test Manager for OpenVMS Systems, Version 3.8-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 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. All rights reserved. © Electronic Data Systems Limited 1994, 1995, 1996, 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.................................................. v 1 General Information 1.1 Introduction.................................... 1-1 1.2 Installation Requirements....................... 1-1 2 New Features 2.1 Logical Name Search Lists....................... 2-1 2.2 DECnet/OSI Phase V.............................. 2-2 2.3 Default Filter/Mask Maximum Year................ 2-2 3 Problems Fixed 4 Known Problems 4.1 General......................................... 4-1 4.2 DECwindows Interface............................ 4-6 4.3 Documentation................................... 4-8 5 Restrictions 5.1 General......................................... 5-1 iii 6 Reporting Problems and Suggestions Tables 1 Conventions .................................. vi iv ________________________________________________________________ Preface These release notes characterize the Version 3.8 release of DIGITAL Test Manager for DIGITAL OpenVMS VAX and DIGITAL 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 Associated Documents For more information on DIGITAL Test Manager, refer to the following documents o DECset OpenVMS V12.2 Software Product Description o DECset Guide to Detailed Program Design for OpenVMS Systems o Using DECset for VMS Systems o Guide to DEC Test Manager for OpenVMS Systems o DEC Test Manager for OpenVMS Reference Manual 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. (continued on next page) vi 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._______________________ vii 1 ________________________________________________________________ General Information The information in these release notes pertain to DIGITAL Test Manager Version 3.8. 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.8 is a maintenance release. 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 General Information 1-1 2 ________________________________________________________________ New Features The following enhancements were added to DIGITAL Test Manager Version 3.8. 2.1 Logical Name Search Lists DIGITAL Test Manager supports logical name search lists for the following files: o Collection Prologue/Epilogue o Test Prologue/Epilogue o Test Template/Session o Benchmark o Template directory o Benchmark directory The search list logical can specify any combination of OpenVMS directories or files and CMS libraries. By default, search list logical names are resolved to explicit file specifications at the point a collection is created or recreated. If files or directories that are referenced by a search list are created, deleted or moved, any collections dependent on these search lists may have to be recreated to resolve the new file specifications. If the /NOVERIFY qualifier is used when a collection is created, the search list logical is not resolved until the point during the collection run when the file is accessed. New Features 2-1 2.2 DECnet/OSI Phase V The qualifiers that support remote operation, /INPUT and /OUTPUT, have been enhanced to function under DECnet/OSI Phase V. 2.3 Default Filter/Mask Maximum Year The date filter/mask default maximum year has been changed to 2500. 2-2 New Features 3 ________________________________________________________________ Problems Fixed The following bugs were fixed and restrictions were removed in DIGITAL Test Manager Version 3.8. o Bug 917 - Version is erroneously filtered. If a file specification is terminated with a semicolon, the phantom version is erroneously filtered to "VERSION". o Bug 918 - Access Violation during DTM VERIFY (OpenVMS Alpha only). Performing a VERIFY on a library containing at least one collection causes an access violation when the collection directory structure is verified. o Bug 920 - Large result files are truncated by filtering. Filtering of files with sizes greater than 150 blocks causes the resulting output file to be truncated. o Bug 921 & 930 - Date filter has problems with spaces and certain date formats. The date filter does not filter all common date formats and fails to filter dates with leading spaces. o Bug 923 & 929 - Time filter has problems with spaces. The time filter does not handle spaces correctly and therefore filters when it should not. For example, the string " : " should not be filtered. o Bug 924 - Traceback filter fails on dumps that are not contiguous. The traceback filter fails at times on dumps that are not contiguous. Problems Fixed 3-1 The following traceback example is only filtered up to the condition handler message. %TRACE-E-TRACEBACK, symbolic stack dump follows module name routine name line rel PC SEDECLFO SEK_OBJ_XXX 2746 000004E5 ----- above condition handler called with exception 0000000C: %SYSTEM-F-ACCVIO, access violation, reason mask=00 ----- end of exception message UNI_ARITHMETIC COMPARE__1 635 00000010 o Bug 925 - Version not filtered on a filename without an extension. The version number is not filtered to "VERSION" on filenames without extensions and directory specifications. o Bug 926 - Access control string not valid with RECORD /INPUT. Remote operation with the /INPUT qualifier is valid in DIGITAL Test Manager, but the use of an access control string, i.e. NODE"username password":: with the RECORD command produces the following error. %DTM-E-RECORDFAILED, session file for test description TEST has... ...not been recorded -DTM-E-FILNAMERR, error in input file name... ...NODEusername password::filename.ext -RMS-E-NOD, error in node name o Bug 927 - DIGITAL Test Manager fails with a concurrent user license (OpenVMS Alpha only). When using a single user concurrent license, the following error will occur. %LICENSE-F-NOAUTH, DEC DTM-USER use is not authorized on this node -LICENSE-F-EXCEEDED, attempted usage exceeds active license limits -LICENSE-I-SYSMGR, please see your system manager 3-2 Problems Fixed 4 ________________________________________________________________ Known Problems 4.1 General The following known problems exist for DIGITAL Test Manager Version 3.8: 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 665 - Time and date filters fail to filter correctly. Specifying both the date and time filters for a test can result in erroneous differences being reported when the test is executed. The problem is due to date and time strings being filtered differently when they should be filtered identically. For example: JULY 18, 1990, 10:30 AM filters to: month day, year, hh:mm xm JULY 18, 1990, 9:30 AM filters to: month day, year,hh:mm xm 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 and/or 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. 4-2 Known Problems 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 699 - FILTER command purges all previous versions of filtered file. The FILTER command incorrectly purges all previous versions of a file being filtered, rather than only those versions it creates. 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 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 DEC Test Manager for OpenVMS Systems. o Bug 797 - DCL help for DEFINE/KEY topics generates errors. Known Problems 4-3 On-line help for the DCL interface generates errors for any of the topics listed under DTM HELP DEFINE /KEY. See the DEC Test Manager for OpenVMS Reference Manual for information about these topics. 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 DEC Test Manager for OpenVMS Systems for information about these topics. o Bug 892 - DECwindows redefining default KEYSYM causes problems. Redefining the default KEYSYM (F9) and then recording a test works as expected. However, when the test is run, the application definition of F9 is not recognized and the following error occurs. %DTM-W-INVKBDCMD, invalid keyboard command 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. o Bug 894 - DECwindows problems with RECORD/INPUT=file. The RECORD/INPUT command with DECwindows testing does not function as described in the documentation or on- line help. Extracting a DECwindows test into an input file and then specifying the file as an input for the RECORD command has no effect. For example: 4-4 Known Problems DTM> EXTRACT /DECWINDOWS test-name %DTM-S-EXTRACTED, input file $disk$:[directory]file.INP created DTM> RECORD /INPUT=$disk$:[directory]file.INP test-name %DTM-I-XTRAPVERSION, Display _WSA6: is running XTrap V3.3-0 %DTM-I-RECORDING, Recording to file $disk$:[directory]file.SESSION at line 9 <----- It waits here. Only the DCL command specified at the test creation is executed and the recording waits for user input to record. o Bug 905 - Messages occur out of order (OpenVMS Alpha). Messages occur out of order during a DTM COMPARE on OpenVMS Alpha 7.0. For example: %DTM-W-ALRDYCOMPARED, test AAA has already been compared -DTM-I-TEXT, this test was successful on previous Compare %DTM-I-UNSUCCESS, the comparison for the test BBB was unsuccessful %DTM-W-ALRDYCOMPARED, test CCC has already been compared -DTM-I-TEXT, this test was successful on previous Compare %DTM-I-UNSUCCESS, the comparison for the test DDD was unsuccessful -DTM-S-FILMOVED, benchmark screens file BBB.BMK_SCREENS moved to CMS library disk:[directory] -CMS-I-NOCHANGES, no changes o Bug 915 - Internal error recreating a collection which performs masking. The following error may occur while attempting to recreate a collection containing interactive tests that have been created in the DECwindows interface with the masking option set: %DTM-F-BUG, There is a bug in DEC Test Manager or something it calls -DTM-F-COLLCREATERR, failure creating collection -CLI-F-IVKEYW, unrecognized keyword - check validity and spelling If the recreation attempt is made from the DCL interface, the following line is added to the beginning of the message: %CLI-W-IVKEYW, unrecognized keyword - check validity and spelling \MASK\ o Bug 916 - Execution of an interactive test using SET HOST and filters does not work properly. Known Problems 4-5 The benchmark file for an interactive test that performs a SET HOST command and uses all of the filters will not be recorded properly during execution. All the output from the test will appear on the top line of the screen in the benchmark file after the SET HOST command is executed. All output is also written to the first line of the screen within the benchmark screens file. o Bug 932 - Directory specifications are not filtered correctly. Some valid directory specifications are not filtered when they should be and some invalid specifications are incorrectly filtered. 4.2 DECwindows Interface The following known problems exist for the DECwindows interface in DIGITAL Test Manager Version 3.8: o Bug 890 - DECwindows modify library window - missing epilogue box. The DECwindows Modify Library, when accessed via: "File -> Library -> Modify..." contains two benchmark directory boxes and no epilogue box. o Bug 891 - DECwindows Work in Progress windows are left empty for some time. The Work in Progress windows may appear and be empty for some time before anything is written into them. For example, after clicking OK in the "Query Test System" window, the "Displaying New View..." message only appears shortly before the window disappears. o Bug 911 - DECwindows review display widget does not function properly. The following problems occur with the DECwindows display widget that controls the review of screen terminal tests when the difference file is displayed: a. The screen number is permanently fixed at zero. 4-6 Known Problems b. The selection box to enable the way that differences are shown to be changed (e.g. from Reverse to Underline) does not work. c. There is no 'Working' marker. In the command line interface, a flag has the blinking video attribute set to show that Test Manager is searching for the next screen. o Bug 914 - ACCVIO 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 - DIGITAL Test Manager hangs when using record and play. On OpenVMS V7.1 systems recording/playing a test using the DECwindows interface will cause DIGITAL Test Manager to hang. o The Modify Test dialog box does not allow the DCL command associated with a DECwindows test to be modified. To modify this field, use the MODIFY TEST command under the DCL interface. o There is no mechanism for accessing the history records in a library. The only mechanism is via the SHOW HISTORY command under the DCL interface. o Attempting to access context sensitive help for some artifacts in the DIGITAL Test Manager DECwindows interface will produce "could not find frame" errors. The problem is that help frames that are not defined for all DIGITAL Test Manager window artifacts. o 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 accessible from the Library option of the File menu, or via DCL command VERIFY /RECOVER. Known Problems 4-7 o 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 When reviewing interactive terminal tests, do not set input focus and type into the result, benchmark, or differences display window. This will terminate the subprocess controlling the window. Only interact with the window via the Display control panel. o The DECwindows Mask Editor does not purge benchmark files when new versions are created due to modifying the masks defined for a benchmark file. The older versions must be manually purged. This also applies if the benchmark files are located in a DIGITAL Test Manager library. o When recording interactive terminal tests, do not use the "^P W" and "^P !" commands to enter wait records and comments. If these capabilities are required, record interactive terminal tests from the DCL interface. o Remarks associated with sub-groups are not displayed in the Group View. To determine the remarks associated with sub-groups, use the SHOW GROUP command from the DCL interface. o 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. 4.3 Documentation The following known problems exist in the DIGITAL Test Manager Version 3.8 documentation: o Bug 901 - Unresolved formatting tag "only/bold" in the Guide to DEC Test Manager for OpenVMS Systems. 4-8 Known Problems There is an unresolved text formatting tag on page 9-8 of Section 9.2. The second to last sentence on the page reads: "...if a collection is being run, only/bold that test will abort..." The word "bold" is a formatting tag that should cause the word "only" to be in bold print. o Bug 902 - NOMSGBLK error message is not documented. The DIGITAL Test Manager message NOMSGBLK, signaled as a fatal error, is not documented in Appendix A of the DEC Test Manager for OpenVMS Reference Manual. This error occurs when an attempt to allocate memory for an error message block fails. o Bug 910 - DOC: Updating a benchmark file example is incorrect. Section 2.2.7 contains an incorrect description for updating a benchmark file. To update a benchmark file, use Review -> Update from the Testing pull-down menu. o Bug 912 - DOC: Default mask file extension is .MXK not .MSK. Section 2.2.8 (last sentence) describes the mask file extension as being .MSK. The correct file extension is .MXK. o Bug 913 - DOC: Missing window borders in Figure 2-1 "Title Bar and Main Menus". The borders are missing from the windows and menus in Figure 2-1. Known Problems 4-9 5 ________________________________________________________________ Restrictions 5.1 General The following restrictions exist for DIGITAL Test Manager Version 3.8: o Interactive terminal testing does not provide support for VT400 or greater series terminals. Tests recorded or executed on these terminals may cause screen comparisons to fail. When using interactive terminal testing features, VT400 or greater series terminals should have the characteristics set to a VT100, VT200, or VT300 series terminal. 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