|
-> We are currently running DTM V3.3. I know that we need to upgrade to at
-> least 3.5 (since I know that a bug that we are running into is fixed
-> int 3.5), and will probably upgrade to the most recent release.
-> We are running VMS 6.2
There are some filter problems in DTM V3.7 so I recommend upgrading your
DTM v3.3 to DEC Test Manager Version V3.6-4.
-> Will this be a transparent upgrade, or will there be any library
-> conversions/test modifications/system parameter changes?
See Release Note.
-> Does DTM rely on any other DECset tools being at a certain level?
No.
-> Are the release notes anyplace on line?
You may find the release notes from the DECset kits:
The DECset kits should be located in subdirectories of
UHUH::DECSET$:[PUBLIC]
-James
BTW: Release Notes for V3.6
---------------------------------------------------------------------------
DECset
Release Notes for DEC Test Manager Version V3.6-4
March 1995
These are the release notes for DEC Test Manager V3.6-4 on
OpenVMS VAX and OpenVMS Alpha. Version V3.6-4 is a maintenance
release.
Field Test
Proprietary Information
Furnished for Field Test Purposes Only.
The information contained herein is furnished in confidence and
is subject to the terms and conditions of a License Agreement
for Field Testing Digital Software.
Operating System and Version: OpenVMS VAX, Version 5.5 or
higher
OpenVMS Alpha, Version 1.5 or
higher
DECwindows Motif, Version 1.1 or
higher
Software Version: DECset for OpenVMS, Version T12.0
Software Version: DEC Test Manager for OpenVMS
Systems, Version V3.6-4
<COMPANY_INFO>(Digital Equipment Corporation\Maynard, Massachusetts)
Digital Equipment Corporation
Maynard, Massachusetts
________________________
First Printing, January 1995
Revised, March 1995
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 writ-
ten license from Digital, an authorized sublicensor, or the
identified licenser.
Digital Equipment Corporation or EDS makes no representations
that the interconnection of its products in the manner de-
scribed in this document will not infringe existing or future
patent rights, nor do the descriptions contained in this doc-
ument imply the granting of licenses to make, use, or sell
equipment or software in accordance with the description.
� EDS Defense Limited 1994.
� Digital Equipment Corporation 1994. All rights reserved.
<TRADEMARK_PARA>(INTRO\Alpha, DEC, DEC Ada, DECnet, DECset,
DECwindows, OpenVMS, VAX, VAX Ada, VAX BASIC, VAX BLISS-
32, VAX C, VAXcluster, VAX COBOL, VAX DIBOL, VAX DOCUMENT,
VAX FORTRAN, VAX Pascal, VAX SCAN, VMS, and the DIGITAL logo.)
The following are third-party trademarks:
Motif is a registered trademark of the Open Software Foundation,
Inc.
PostScript is a registered trademark of Adobe Systems, Inc.
This document was prepared using VAX DOCUMENT, Version 2.1.
Contents
1 NEW FEATURES 1
2 PROBLEMS FIXED IN VERSION V3.6-4 1
3 KNOWN PROBLEMS 4
4 RESTRICTIONS 8
5 REPORTING PROBLEMS AND SUGGESTIONS 8
iii
1 New Features
The following enhancements were added to DEC Test Manager for
V3.6-4:
o Duplicate screen elimination.
DEC Test Manager now eliminates duplicate screens images
from the files containing the printable benchmark and result
screen images for an interactive test. Duplicate screen
images are defined as any two consecutive screen images that
are completely identical. This is the default behavior for
DEC Test Manager. No modifications have been made to the DEC
Test Manager's user interface.
2 Problems Fixed in Version V3.6-4
The following bugs were fixed and restrictions were removed in
DEC Test Manager Version V3.6-4:
o DTM_BUGS Bug 880 - A database corruption bug that existed in
both CMS and DEC Test Manager has now been fixed in DEC Test
Manager. CMS had fixed this bug prior to release V3.6. The
following text was included with the CMS release notes about
the fix for this database corruption bug, and is modified
for use in the DEC Test Manager release notes.
DEC Test Manager V3.6-4 (and later) Libraries
A change has been made to the format of the DEC Test Manager
database for libraries starting with V3.6-4. This change re-
solves a serious and destructive data corruption error in
the database. This change is automatically and transparently
made by DEC Test Manager V3.6-4 at the time it accesses any
existing library or a new library created. The side effect
of this change is that you CANNOT and MUST NOT use versions
of DEC Test Manager earlier than V3.6-4 to access any li-
brary that has been used by V3.6-4 or later. Attempting to
do so will cause serious data corruption problems. A dif-
ference between DEC Test Manager version V3.6-4 and DEC Test
Manager Version 3.5 is to make SURE that no earlier versions
of DEC Test Manager can access the altered database (as
described in the V3.6-4 change above) and thereby corrupt
the new format database. This has been done by changing the
name of the DEC Test Manager master control files in the top
level of a DEC Test Manager library from 00DTM.* to 01DTM.*.
This will guarantee that no-one will accidentally access a
new/updated library from older versions of DEC Test Manager.
1
To convert any existing version 3 libraries to the format
needed for V3.6-4 (or later), simply execute the following
command for any of your existing DEC Test Manager libraries.
(to convert pre-version 2 libraries, you MUST use the DEC
Test Manager CONVERT command instead):
$ RENAME disk:[directory]00DTM.* 01DTM.*
NOTE: the above change to DEC Test Manager only resolves the
problem of corrupting a valid database. It does NOT repair
already existing corruption in the database. Already exist-
ing corruption (where VERIFY shows MISBLKSTR or MSSBLKSTR
errors in the database) cannot be repaired using VERIFY
/REPAIR. Already existing corruption can be overcome by
using valid backups of the DEC Test Manager library or by
creating a completely new library from scratch.
IMPORTANT RESTATEMENT: Once you have used DEC Test Manager
V3.6-4 or later on any DEC Test Manager library, you MUST
NOT ever attempt to use it with any earlier version of DEC
Test Manager (for example, by renaming the 01DTM.* files
back to 00DTM.*, as has been attempted in at least one
case). Once you have moved forward to the new format, there
is NO going back.
o DTM_BUGS Bug 881 - DEC Test Manager was allocating IO chan-
nels and then not releasing the IO channels if a search list
logical name or a wildcard was used in a command that modi-
fies a test. This could cause DEC Test Manager to terminate
with a SYSTEM-F-NOIOCHAN error if the CHANNELCNT SYSGEN pa-
rameter limit was reached. These channel are now released
after the modify command completes.
o DTM_BUGS Bug 882 - On a system with a single user DEC Test
Manager license, DEC Test Manager would generate the error:
LICENSE-F-EXCEEDED, ATTEMPTED USAGE EXCEEDS ACTIVE LICENSE
LIMITS when the RUN command was issued. DEC Test Manager is
now able to successfully run tests on a system with a single
user license.
o DTM_BUGS Bug 883 - The DEC Test Manager image that executes
without using CMS features was improperly checking to see if
CMS was licensed on the system. If CMS was not licensed on
the system, DEC Test Manager would terminate with an error
condition stating that CMS was not authorized on the system.
The DEC Test Manager image that does not use CMS features
is now fixed such that it does not to check that CMS is
licensed on the system.
o DTM_BUGS Bug 884 - After modifying an interactive test the
session file remained locked until DEC Test Manager was
terminated. If many modify commands were performed during a
DEC Test Manager session, DEC Test Manager could run out of
2
IO channels and terminate abnormally. DEC Test Manager now
closes a test's session file and releases IO channels after
the modify command has completed.
o DTM_BUGS Bug 885 - The DEC Test Manager mask editor could
cause an access violation if invoked many times during a DEC
Test Manager session. The work around was to run the mask
editor only once per DEC Test Manager session. This is now
fixed so that the mask editor can be run multiple during a
DEC Test Manager session.
o DTM_BUGS Bug 886 - The DEC Test Manager EXTRACT command
was not looking in the default template directory for an
interactive test's session file if the file's directory
path name was not specified on the command line. If a file's
directory path name was not specified, the DEC Test Manager
would only locate the file if it existed in the current
directory. The DEC Test Manager now searches in the default
template directory for an interactive test's session file
if the file's directory path name is not specified on the
command line.
o DTM_BUGS Bug 887 - The DECwindows interface to the DEC test
manager would ACCVIO if attributes of library objects were
expanded multiple times. When expanding attributes by dou-
ble clicking on selected tests, collections, variables, or
groups multiple times, the DECwindows interface to the DEC
Test Manager would terminate with an ACCVIO exception. This
problem only occurred on OpenVMS Version 6.1 This is now
fixed in the DEC Test Manager.
o DTM_BUGS Bug 888 - The DEC Test Manager was not properly
masking date strings when comparing results for interac-
tive terminal tests. When fields of the date string were
separated by spaces, the dates were not masked out. A date
string that produced this problem is: "15 FEB 1995". The DEC
Test Manager now properly masks out date strings where the
fields of the date string are separated by spaces.
o The DECwindows interface to the DEC Test Manager now allows
font and window size DECwindows resources to be specified in
its DECwindows resource data file. The name of this resource
data file is: DECW$SYSTEM_DEFAULTS:DTM$DW_DEFAULTS.DAT. See
that file for more information on modifying the DECwindows
interface to the DEC Test Manager.
o The DEC Test Manager library is properly updated on a con-
text switch from the DECset environment manager. The title
bar of the main window in the DECwindows interface to the
DEC Test Manager is now properly updated on a context switch
from the DECset environment manager.
3
3 Known Problems
The following known problems exist for DEC Test Manager Version
V3.6-4:
1. The DEC Test Manager interactive terminal record function
can access violate when recording tests of applications
which perform drawing using REGIS and/or SIXEL. This occurs
due to a buffer limit inside DEC Test Manager.
A potential workaround is to define the logical DTM$PCDRIVER
to 1 prior to recording or executing interactive terminal
tests. This will result in the DEC Test Manager PCDRIVER
being used instead of the VMS FTDRIVER. You will need to
ensure that DTM$PCDRIVER is defined when tests are run in
batch. One way to do this is to define it within a test or
collection prologue file.
2. The SHOW /BENCHMARK command in the DEC Test Manager Review
subsystem can fail if the collection being reviewed was
executed while the DEC Test Manager library was set to a
directory specification containing a concealed logical.
3. Specifying the /REALTIME option on the DEC Test Manager
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 results in substantially slower test execution. You can
edit the session file to remove the unwanted WAIT records.
See the Guide to DEC Test Manager for OpenVMS Systems for
information about these topics.
4. The DEC Test Manager interactive terminal testing does not
provide support for VT400 or greater series terminals. Tests
recorded or executed on VT400 or greater series terminals
may cause DEC Test Manager screen comparisons to fail. VT400
or greater series terminals should have the characteristics
set to a VT100, VT200, or VT300 series terminal when using
DEC Test Manager interactive terminal testing features.
5. On-line help for the DEC Test Manager DCL interface gener-
ates errors if you attempt to access help information for
any of the topics listed when you do a DTM HELP DEFINE /KEY.
See the DEC Test Manager for OpenVMS Reference Manual for
information about these topics.
6. The DEC Test Manager EXTRACT /DECWINDOWS command is used
to convert DECwindows session files recorded with DEC Test
Manager V3.2 to V3.3 format. Specifying EXTRACT /DECWINDOWS
for a DECwindows session file in V3.3 format will erro-
neously display DTM-E-NOEXTRACT messages. The session file
is unaffected and already is in the correct format.
4
7. On-line help for the DEC Test Manager DCL interface does
not provide help information for the DEC Test Manager key-
pad definitions. Pressing PF2 to access this help topic
will generate an error message. For information on the DEC
Test Manager keypad definitions, see the Guide to DEC Test
Manager for OpenVMS Systems.
8. The DEC Test Manager STOP command is used to stop collec-
tions which are executing. If a collection is submitted to
batch and terminates abnormally DEC Test Manager will be-
lieve the collection is still running. If STOP is specified
for this collection, DEC Test Manager will attempt to delete
the batch job created for the collection when it was sub-
mitted. It does this by using the entry number for the job.
The problem is that the job created for the collection no
longer exists which allows the queue manager to re-use the
entry number originally assigned to it. The result is that
DEC Test Manager can delete the wrong batch job. You should
use the DCL commands SHOW QUEUE and/or SHOW ENTRY to ver-
ify that your collection is still executing before using the
DEC Test Manager STOP command. If the collection is not cur-
rently executing, you should use the DEC Test Manager VERIFY
/RECOVER command to correct the inconsistency in your DEC
Test Manager library.
9. The comment directives {BEGIN_COMMENT} and {END_COMMENT} do
not work in input files created from interactive terminal
session files. If used they will generate errors when you
attempt to convert the input file to a session file using
the DEC Test Manager RECORD /INPUT command.
10.The DEC Test Manager FILTER command incorrectly purges all
previous versions of a file being filtered. It should only
purge those versions it creates. When using the FILTER com-
mand you must be careful that versions of files you need are
not lost.
11.You cannot specify commands with embedded quotes with the
/COMMAND option for the DEC Test Manager CREATE and MODIFY
TEST commands. DEC Test Manager will accept the command but
removes the embedded quotes when the command is executed as
part of test execution or recording.
12.Specifying both DEC Test Manager's 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. An example of this follows:
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
5
13.Do not include rooted logical names in the specification of
test benchmark files. If you do so, DEC Test Manager will
be able to successfully execute the test but will fail when
it attempts to compare the test result file to the test
benchmark file. You can affect the name of a test benchmark
file via the DEC Test Manager commands CREATE and MODIFY
TEST /BENCHMARK and SET BENCHMARK_DIRECTORY. An example of a
rooted logical definition would be DISK$:[USER.].
14.The DEC Test Manager RECORD /VARIABLE command does not de-
fine the global variables defined in your DEC Test Manager
library for the recording session. It only defines the lo-
cal variables associated with the test. Global variables are
defined when a test is executed. The consequence of this is
that you cannot reference global variables during recording
or in your test prologue or epilogue files if /PROLOGUE or
/EPILOGUE was specified on the RECORD command.
15.If you use the DEC Test Manager variable DTM$OMIT_SCREENS
to prevent DEC Test Manager from creating .RES_SCREENS and
.BMK_SCREENS files, DEC Test Manager will display erroneous
error message when attempting to update the benchmark file
for an interactive terminal test. The messages will state
the DEC Test Manager could not update the .BMK_SCREENS file.
These messages can be ignored.
16.The DEC Test Manager character comparison facility incor-
rectly stops comparison upon detection of the first differ-
ence between a result and benchmark file.
17.When using the DCL qualifier /CHARACTERISTICS for the DEC
Test Manager command SUBMIT, DEC Test Manager sets only the
first characteristic specified on the created batch job. All
other characteristics are ignored.
The following DECwindows interface known problems exist for DEC
Test Manager Version V3.6-4:
1. The Modify Test dialog box in the DEC Test Manager DECwindows
interface does not allow you to modify the DCL command as-
sociated with a DECwindows test. To modify this field, you
need to use the MODIFY TEST command in the DEC Test Manager
DCL interface.
2. There is no mechanism for accessing the history records
in a DEC Test Manager library from then DEC Test Manager
DECwindows interface. The only mechanism to access history
records is via the DEC Test Manager SHOW HISTORY command
from the DEC Test Manager DCL interface.
6
3. Attempting to access context sensitive help for some ar-
tifacts in the DEC Test Manager DECwindows interface will
produce "could not find frame" errors. The problem is that
help frames are not defined for all DEC Test Manager window
artifacts.
4. The DEC Test Manager Tasks dialog box in the DEC Test
Manager DECwindows interface allows you stop active tasks.
It does this by actually killing the process associated
with the task. If you stop an executing collection using the
Tasks dialog box, you will likely need to recover your DEC
Test Manager library either from the DECwindows interface
via the Verify dialog box accessible from the Library option
of the File menu, or via the DEC Test Manager DCL command
VERIFY /RECOVER.
5. The DEC Test Manager Modify Test and Create Test dialog
boxes in the DEC Test Manager DECwindows interface do not
allow you to specify variables where the variable value con-
tains commas. For instance, you could not define a variable
X with a value of "A,B,C". If you require this ability, you
will need to use the CREATE TEST and MODIFY TEST commands in
the DEC Test Manager DCL interface.
6. When using the DEC Test Manager DECwindows interface to
review 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. You should only interact with the window via the DEC
Test Manager Display control panel.
7. The DEC Test Manager DECwindows Mask Editor does not purge
benchmark files when new versions are created by modifying
the masks defined for a benchmark file. You must manually
purge the older versions. This applies even if the benchmark
files are located in a DEC Test Manager library.
8. When recording interactive terminal tests from the DEC Test
Manager DECwindows interface, you can not use the "^P W"
and "^P !" commands to enter wait records and comments. If
you require these capabilities, you will have to record your
interactive terminal tests from the DEC Test Manager DCL
interface.
9. The DEC Test Manager DECwindows interface does not dis-
play the remarks associated with sub groups in the DEC Test
Manager Group View. To determine the remarks associated with
sub groups, you need to use the DEC Test Manager SHOW GROUP
command from the DCL interface.
7
10.The DEC Test Manager DECwindows interface does not dis-
play the remarks associated with variables in the DEC Test
Manager Variable View. To determine the remarks associated
with variables, you need to use the DEC Test Manager SHOW
VARIABLE command from the DCL interface.
4 Restrictions
The following restrictions apply to DEC Test Manager Version
V3.6-4:
1. Correction to "DECset Installation Guide for OpenVMS
Systems", Installing the DEC Test Manager chapter, section
on installation procedure requirements:
- For OpenVMS VAX systems, a minimum of 15,000 blocks of
free disk space are required during installation; 10,000
blocks are used after installation.
- For OpenVMS Alpha systems, a minimum of 25,000 blocks of
free disk space are required during installation; 16,500
blocks are used after installation.
- For OpenVMS Alpha systems, a minimum of 1,200 free global
pages, plus the size of the file SYS$LIBRARY:DCLTABLES.EXE
at installation are required.
- For OpenVMS Alpha systems, a minimum of 8 global sections
are used after installation.
2. When installing DEC Test Manager on OpenVMS VAX Version 5.5,
the following warning message is displayed:
%DECSET-I-LINKPCDRIVER, Linking PCDRIVER.EXE, ignore no transfer address warning.
%LINK-W-USRTFR, image DKA200:[SYS0.SYSUPD.DECSET120]PCDRIVER.EXE;1 has no user
transfer address.
This warning message can be ignored. It does not affect the
performance of DEC Test Manager. This warning message is not
displayed when installing DEC Test Manager on OpenVMS VAX
Version 6.0 or higher, or when installing DEC Test Manager
on any version of OpenVMS Alpha.
5 Reporting Problems and Suggestions
If an error occurs while you are running the DEC Test Manager
and you have reason to believe that the error is due to a prob-
lem in the DEC Test Manager, and you have a support contract,
contact your Digital support representative. Otherwise, con-
tact your Digital account representative or your authorized
reseller. This method should also be used to make requests for
additional features or modifications to existing features.
8
When reporting a problem, please include the following informa-
tion:
o The version of the DEC Test Manager and the VMS operating
system being used.
o The problem reduced to as small a size as possible trying
not to overlook any details.
o Any stack dumps that occurred, if applicable.
o All files should be submitted on machine-readable media
(magnetic tape `*preferred`*, floppy diskette, or tape cas-
sette).
9
|