Choose the Testing menu to access operations that relate directly to DTM's testing functions; recording tests, executing tests as part of collections, and reviewing test results. After you choose an operation from the menu or one of its submenus, use the resulting dialog boxes to view and specify options. Operations in the Testing menu apply to the selection in the active view window. When you begin an operation, DTM fills in the name of the selection from the active view in the text field of the dialog box. DTM also dims (disables) the selection in the active view. If you do not make a selection in the active view when you begin an operation, you must enter the selection in the text field of the dialog box.
1 – t_rvm
After running and comparing a collection, use the Review menu item to place a selected collection in the review state (locks the database), to update benchmark files, and to access Display functions. The Review menu item produces a submenu that contains the Open, Update, and Close operations. Initially, the Update and Close submenu items are disabled; you cannot access their functions until you open a collection for review.
1.1 – t_rom
Choose the Open submenu item to place a previously selected collection, from an active collection view window, into the review state. The resulting dialog box enables you to choose to be either a primary or read-only reviewer. As a primary reviewer, only you are able to update benchmarks, a procedure that locks the database. As a read- only reviewer, you can display the contents of the collection; DTM does not lock the database. You must use the Open submenu item before you can use the Update submenu item and Display functions.
1.1.1 – t_rodb
Use the Review Collection dialog box to review a collection that you previously selected from an active collection view window. The dialog box enables you to choose to be a primary or read-only reviewer. As a primary reviewer, you are able to update benchmarks, a procedure that locks the database. As a read-only reviewer, you can display the contents of the collection; DTM does not lock the database. You must choose the Open submenu item before you can use the Update submenu item and Display functions.
1.1.1.1 – t_rodb_sl
The Selected field lists the collection that you first select (highlight) in an active collection view window. For the collection that you select, DTM can make its result files available for updating (or creating) benchmarks. This collection's result, benchmark, and difference files are also available for display. Optionally, you can explicitly specify a collection name in the Collection field.
1.1.1.2 – t_rodb_cl
Use the Collection field to enter the name of the collection whose benchmarks you want to update or whose result, benchmark, and difference files you want to display. You can specify a collection to DTM by first selecting (highlighting) it in an active collection view window, or explicitly specifying its name in the Collection field.
1.1.1.3 – t_rodb_rk
Use the Remark field to optionally enter text that becomes associated with the current operation. The text is logged in the history file of the DTM library. You can selectively display and delete history entries (see additional topics).
1.1.1.4 – t_rodb_rd
If you do not want to be a primary reviewer for a selected collection, click on the Read only button. As a read-only reviewer, you and other reviewers can display the contents of the collection; DTM does not lock the database. You must choose the Open submenu item before you can choose the Update submenu item and Display functions.
1.1.1.5 – t_ro_ok
Click on the OK button to apply the current settings in the dialog box and remove the dialog box. The border on this button indicates that it is the default choice. You can also choose the default by pressing the RETURN or ENTER key.
1.1.1.6 – t_ro_cn
Click on the Cancel button to remove the dialog box without applying any of the settings to the selection.
1.2 – t_rupm
Choose the Update submenu item to update benchmark files. Use this submenu item to create the first benchmark file for a noninteractive test or to replace the existing benchmark with the current test results. You can create a new benchmark file from the existing result file for selected result descriptions. To update a benchmark file, a result description must have a comparison status of comparison aborted, unsuccessful, or new. DTM automatically deletes the result file for successful tests.
1.2.1 – t_rupmdb
The Update dialog box enables you to update benchmark files. You can select the result description from the collection view and choose the Update submenu item; this places the result description in the Selected list. If you do not select any result descriptions from the collection view, you must specify the result description you want to update.
1.2.1.1 – t_rupmdb_sel
When you click on the OK button, the result file for the selected result description becomes the updated benchmark file for the test. This field is disabled if no result descriptions were selected from the collection view.
1.2.1.2 – t_rupmdb_test
Use the Test field to specify the result descriptions to be updated. This field is disabled if you selected a result description from the collection view for updating.
1.2.1.3 – t_rupmdb_rem
Use the Remark field to optionally enter text that becomes associated with the updated files. The text is logged in the history file of the DTM library. You can selectively display and delete history entries (see additional topics).
1.2.1.4 – t_rupmdb_cnf
When Confirm button is enabled, DTM requests confirmation before updating the benchmark files associated with the result description.
1.2.1.5 – t_rupmdb_ok
Click on the OK button to update the selected files (or the file specified in the Test field). The border on this button indicates that it is the default choice. You can also choose the default by pressing the RETURN or ENTER key.
1.2.1.6 – t_rupmdb_can
Click on the Cancel button to remove the dialog box without applying any of the settings to the selection.
1.3 – t_rclm
Choose the Close submenu item to remove a collection from the review state. When you open a collection, the database is locked, enabling the primary reviewer to update benchmarks. Read-only reviewers can display the contents of the collection. The Close submenu item is accessible only when a collection within the active view is in the review state.
2 – t_dm
Choose the Display menu item to view information about a specific test's benchmark, result, or difference file that you selected in an active view window. DTM provides display control boxes to help you navigate through displays for interactive terminal and DECwindows tests. The control boxes vary, depending on the type of file you choose to display. No control boxes are necessary for displaying files associated with noninteractive tests. Scroll bars provided in the display window let you move through the selected files.
2.1 – t_d_bkdb
Use the Display dialog box for interactive tests to navigate through the screen displays for result or benchmark files.
2.1.1 – t_d_bkdb_sn
The Screen number button toggles the screen number display.
2.1.2 – t_d_bkdb_pb
The following table shows the four buttons that enable
you to navigate from one screen to the next in a result
or benchmark file.
Button Description
Next Enables you to display the next screen
in the file. The border on this push
button indicates that it is the default
choice; you can also choose the default by
pressing the RETURN or ENTER key, as well
as clicking on it with the mouse.
First Enables you to display the first screen in
the file.
Previous Enables you to display the previous screen
in the file.
Dismiss Removes the control box.
2.2 – t_d_nidb
Use the Display dialog box for noninteractive tests to navigate through the test output for result, benchmark, or difference files.
2.2.1 – t_d_nidb_txt
The text window displays the test output.
2.2.2 – t_d_nidb_dmsb
The Dismiss button removes the display window.
2.3 – t_d_dfdb
Use the Display Control dialog box for interactive tests to navigate and display differences information. The Display Control box enables you to move from screen to screen and provides options for how DTM displays the difference information.
2.3.1 – t_d_dfdb_sn
The Screen number button toggles the screen number display.
2.3.2 – t_d_dfdb_d
The Shift Display button shifts the screen display to enable parts not initially visible to be seen.
2.3.3 – t_d_dfdb_fo
By clicking on the options field and dragging the
mouse to one of the buttons, you can choose the format
for highlighting differences between the result and
benchmark files.
o Bold: DTM highlights differences by bolding them in
the result file.
o Underline: DTM highlights differences by underlining
and flashing them in the result file.
Note that once a screen is displayed, the difference
format for that screen cannot be changed.
2.3.4 – t_d_dfdb_npb
The following table shows you four buttons that enable
you to navigate from one screen to the next when
displaying differences.
Button Description
Next Enables you to display the next screen
in the file. The border on this push
button indicates that it is the default
choice; you can also choose the default by
pressing the RETURN or ENTER key, as well
as clicking on it with the mouse.
First Enables you to display the first screen in
the file.
Previous Enables you to display the previous screen
in the file.
Dismiss Removes the control box.
3 – t_sbm
Choose the Submit menu item to specify an existing collection for DTM to submit to the batch queue. You can execute collections in batch that combine all three types of tests: noninteractive, interactive terminal, and DECwindows tests.
3.1 – t_sbdb
Use the Submit dialog box to specify collections for DTM to submit to the batch queue. This dialog box also provides standard OpenVMS options for submission of the collection.
3.1.1 – t_sbdb_c
Use the Collection field to enter the name of the collection you want to execute. You can specify a collection to DTM by first selecting (highlighting) it in an active collection view window, or explicitly specifying its name in the Collection field.
3.1.2 – t_sbdb_rk
Use the Remark field to optionally enter text that becomes associated with the current operation. The text is logged in the history file of the DTM library. You can selectively display and delete history entries.
3.1.3 – t_sbdb_cfm
When the Confirm Submission button is enabled, DTM requests confirmation that you want to submit the specified collection to the batch queue.
3.1.4 – t_sbdb_nf
Enable the Notify on Completion Button to indicate that you want to receive a message on any terminal on which you are logged in, notifying you that your job is completed or aborted.
3.1.5 – t_sbdb_q
You can specify three queue settings:
o Name field: Use this field to enter the name of the
batch queue.
o Hold until field: Use this field to specify when
the job is to be executed; you can specify either an
absolute time or a combined absolute and delta time.
o Hold until released button: Use this field to
control when the job is to made available for
processing. You must specifically release the job
using the OpenVMS command, SET QUEUE/ENTRY with
either the /NOHOLD or /RELEASE qualifier.
3.1.6 – t_sbdb_jb
The following table identifies the Job settings
available:
Setting Use
Name Specifies a string to be used as the job
name
User name Enables you to submit a job on behalf of
another user (requires CMKRNL privilege
and read access to the UAF)
Priority Specifies the job scheduling priority
(0 to 255) (requires OPER or ALTPRI to
raise the priority of the default SYSGEN
parameter)
CharacteristicsSpecifies one or more characteristics
desired for the job; codes can be names
or values and are installation-defined
CPU time Defines a CPU time limit for the job;
limit use a delta time, the value 0, or the
keyword NONE or INFINITE
Working set Overrides the base queue value if you
default want to set a lower value than that set
by the system manager or that exists in
your UAF
Working set Overrides the base queue value if you
extent want to set a lower value than that set
by the system manager or that exists in
your UAF
Working set Overrides the base queue value if you
quota want to set a lower value than that set
by the system manager or that exists in
your UAF
3.1.7 – t_sbdb_lf
The following table identifies the Log file settings
available:
Setting Use
Log file When active, creates a log file for the job
button
Name Specifies a name for the log file; the log
field file is written to a file in the default
directory with the same name as the first
command file with a file type of LOG
Print When active, queues the log file for
button printing
Queue Specifies the printer queue for the log file
name
field
Delete When active, deletes the log file after
after printing
printing
button
3.1.8 – t_sbdb_ok
Click on the OK button to apply the current settings in the dialog box and remove the dialog box. The border on this button indicates that it is the default choice. You can also choose the default by pressing the RETURN or ENTER key.
3.1.9 – t_sbdb_cn
Click on the Cancel button to remove the dialog box without applying any of the settings to the selection.
4 – t_rm
Choose the Run menu item to run a collection interactively. You should execute large collections in batch, unless you need to see the test output displayed on the screen.
4.1 – t_rdb
The Run dialog box enables you to specify options for running a collection interactively. DTM creates a terminal emulator and runs the collection as a task. You can direct DTM to create a log file for the run operation. You can also specify where DTM is to display or write the output of the run operation.
4.1.1 – t_rdb_cl
Use the Collection field to enter the name of the collection you want to run. You can specify a collection to DTM by first selecting (highlighting) it in an active collection view window, or explicitly specifying its name in the Collection field.
4.1.2 – t_rdb_rk
Use the Remark field to optionally enter text that becomes associated with the current operation. The text is logged in the history file of the DTM library. You can selectively display and delete history entries.
4.1.3 – t_rdb_cf
When the Confirm button is enabled, DTM requests confirmation that you want to run the specified collection.
4.1.4 – t_rdb_lf
When the Log file button is enabled, DTM creates a log file for the collection. The log file contains output that the test run generates other than the output from the test itself. Use the Log file field to enter a file specification for the created log file. If the button is enabled with an empty field, DTM writes the log file to the task output window.
4.1.5 – t_rdb_op
When the Output button is enabled, DTM displays or writes a copy of the output of the run operation (that is, the test result files). When the button is disabled, DTM suppresses output. Use the Output field to specify the file or device to which DTM directs the output of the run operation. If the button is disabled with an empty field DTM directs the output to the task output window.
4.1.6 – t_rdb_ok
Click on the OK button to apply the current settings in the dialog box and remove the dialog box. The border on this button indicates that it is the default choice. You can also choose the default by pressing the RETURN or ENTER key.
4.1.7 – t_rdb_cn
Click on the Cancel button to remove the dialog box without applying any of the settings to the selection.
5 – t_cm
Choose the Compare menu item to manually compare test
results to benchmark files.
DTM will not complete the comparison process
automatically for any of the following reasons:
o You chose the option not to compare when you created
the collection
o A test in the collection is only partially run
o Some of the tests in the collection do not run
In any of these cases, you need to compare the test
results manually before you can review the results.
5.1 – t_cdb
Use the Compare dialog box to specify the collections you want to compare and to choose comparison options.
5.1.1 – t_cdb_c
Use the Collection field to enter the names of the collections you want to compare. You can specify collections to DTM by first selecting (highlighting) them in an active collection view window, or by explicitly specifying them in the Collection field by specifying a collection name.
5.1.2 – t_cdb_tp
Use the Comparison Type buttons to control the type of comparison that DTM carries out. The Default button causes DTM to default to the comparison setting you chose for each test when you created it. The remaining three buttons produce a comparison that is screen by screen (default for interactive terminal and DECwindows tests), record by record (default for noninteractive tests) or character by character. By clicking on one of the remaining three buttons, you cause DTM to compare all tests in the collection using the specified comparison type, no matter what the individual test comparison setting might be.
5.1.3 – t_cdb_df
Use the Full and Parallel buttons and the Width field to modify the content and format of a printed difference file for noninteractive tests.
5.1.4 – t_cdb_fl
Click on the Full button to modify the contents of a printed difference file for noninteractive tests. When the button is enabled, DTM includes in the difference file a complete listing of the text that is identical, as well as a listing of the differences DTM encounters when it compares the result file to the benchmark file. When the button is disabled, DTM includes only a listing of differences.
5.1.5 – t_cdb_pl
Use the Parallel button to modify the format of a printed difference file for noninteractive tests. When the Parallel button is enabled, DTM places the lines that do not match from the result and benchmark files side by side in the difference file. When the Parallel button is disabled, DTM places the benchmark lines above and the corresponding result lines below in the difference file.
5.1.6 – t_cdb_wd
Use the Width field to specify the width of the difference file's output. The minimum width is 48 columns, the maximum width is 511 columns, and the default is 132 columns.
5.1.7 – t_cdb_ig
The Ignore buttons enable you to specify that various
aspects of benchmark and result files are to be ignored
during comparison.
The following buttons and their effects apply to
noninteractive and interactive terminal tests, only.
Button Result
Case Ignores any differences between the case
of alphabetic characters (A,a,B,b, . . . )
Form-feeds Ignores form-feed characters
Spacing Treats multiple blanks and tabs as a
single space
Leading Ignores leading blanks and tabs
blanks
Trailing Ignores trailing blanks and tabs
blanks
The following button and its effect applies to
DECwindows tests only.
Button Result
Mask Ignores masked areas defined on
DECwindows benchmark images
5.1.8 – t_cdb_se
Use the Skip Text fields to enter a pair of strings used to delimit a section of text to be ignored during the comparison of result and benchmark files for noninteractive tests. The delimiters can be up to 256 characters per line, and must be unique. Any text between and including the delimiters is ignored by DTM.
5.1.9 – t_cdb_ap
Click on the OK button to apply the current settings in the dialog box and remove the dialog box. The border on this button indicates that it is the default choice. You can also choose the default by pressing the RETURN or ENTER key.
5.1.10 – t_cdb_cn
Click on the Cancel button to remove the dialog box without applying any of the settings to the selection.
6 – t_sm
Choose the Stop menu item to stop the execution of a collection that has been submitted to the batch queue. The batch job stops and is removed from the queue; DTM cleans up the database and displays a message. You can compare and review all tests that were completed before you stopped the collection. Click on the Delete task button in the Task dialog box to stop a collection that is running interactively.
6.1 – t_stdb
Use the Stop dialog box to specify collections for DTM to remove from the batch queue.
6.1.1 – t_stdb_c
Use the Collection field to enter the name of the collection you want to stop. You can specify collections to DTM by first selecting (highlighting) them in an active collection view window, or by explicitly specifying them in the Collection field by specifying a collection name.
6.1.2 – t_stdb_rk
Use the Remark field to optionally enter text that becomes associated with the current operation. The text is logged in the history file of the DTM library. You can selectively display and delete history entries.
6.1.3 – t_stdb_cf
Click on the Confirm button to confirm the stop operation for the collection. When you click on the Confirm button, DTM produces a dialog box that enables you to acknowledge the stop operation for the selected collection.
6.1.4 – t_stdb_ap
Click on the OK button to apply the current settings in the dialog box and remove the dialog box. The border on this button indicates that it is the default choice. You can also choose the default by pressing the RETURN or ENTER key.
6.1.5 – t_stdb_cn
Click on the Cancel button to remove the dialog box without applying any of the settings to the selection.
7 – t_rcm
Choose the Record menu item to produce a submenu for recording an interactive terminal or DECwindows test. The DTM Record functions let you run applications and record all input and output generated on the screen. The input goes into a template file (.SESSION) and the output goes into a benchmark file. If an input file is associated with the test, DTM records from the input file; otherwise, DTM records interactive input from the screen. You must create a test description for each interactive terminal and DECwindows test before you can successfully use the Record functions (see additional topics).
7.1 – t_rcm_dw
Choose the DECwindows Test... submenu item to record an interactive DECwindows test. The resulting dialog box enables you to specify recording options for the test.
7.1.1 – t_rcm_dwdb
Use the Record DECwindows Test dialog box to specify the test name and options for the record operation. DTM creates a task when you record a test with a prologue file, epilogue file, filters, or variables.
7.1.1.1 – t_rcm_dwdb_test
Use the Test field to enter the name of the DECwindows test you want to record. This field accepts only a single test description object. Optionally, you can first select the test in an active test view window.
7.1.1.2 – t_rcm_dwdb_rem
Use the Remark field to optionally enter text that becomes associated with the current operation. The text is logged in the history file of the DTM library. You can selectively display and delete history entries (see additional topics).
7.1.1.3 – t_rcm_dwdb_disp
The display field specifies the workstation screen on which the test will be recorded. The default is DECW$display.
7.1.1.4 – t_rcm_dwdb_keysym
Use the Keysym field to specify a new DECwindows command key to replace the default F9.
7.1.1.5 – t_rcm_dwdb_ifbf
Click on the Input file button and specify a DECwindows input file to be used in recording a DECwindows test.
7.1.1.6 – t_rcm_dwdb_pb
Click on the Prologue button to direct DTM to execute the test prologue file, specified in the test description, before interactive recording begins.
7.1.1.7 – t_rcm_dwdb_eb
Click on the Epilogue button to direct DTM to execute the test epilogue command file, specified in the test description, when interactive recording stops.
7.1.1.8 – t_rcm_dwdb_pmb
Click on the Pointer Motion button to direct DTM to record all pointer motion events. If this button is not selected, when the test is played, the pointer will move directly to the location of button presses and releases.
7.1.1.9 – t_rcm_dwdb_vb
Click on the Variables button to direct DTM to define symbols and logical names as specified by the variables associated with the test before recording starts.
7.1.1.10 – t_rcm_dwdb_log
Click on the Log button to direct DTM to place the messages pertaining to the test recording in a log file.
7.1.1.11 – t_rcm_dwdb_ok
Click on the OK button to apply the current settings in the dialog box and remove the dialog box. The border on this button indicates that it is the default choice. You can also choose the default by pressing the RETURN or ENTER key.
7.1.1.12 – t_rcm_dwdb_can
Click on the Cancel button to remove the dialog box without applying any of the settings to the selection.
7.2 – t_rcm_tt
Choose the Terminal Test... submenu item to record an interactive terminal test. The resulting dialog box enables you to specify recording options for the test. DTM creates a task when you record a test.
7.2.1 – t_rcm_ttdb
Use the Record Terminal Test dialog box to specify the test name and options for the record operation. DTM creates a task when you record a test with a prologue file, epilogue file, filters, or variables.
7.2.1.1 – t_rcm_ttdb_test
Use the Test field to enter the name of the interactive terminal test that you want to record. This field accepts only a single test name. Optionally, you can first select the test in an active test view window.
7.2.1.2 – t_rcm_ttdb_rem
Use the Remark field to optionally enter text that becomes associated with the current operation. The text is logged in the history file of the DTM library. You can selectively display and delete history entries (see additional topics).
7.2.1.3 – t_rcm_ttdb_term
Use the Termination character field to specify a new termination character to replace the default termination character, CTRL/P. Specify a different termination character if the application you are testing interprets CTRL/P. You use the termination character to suspend a recording session. You can then issue Record key sequences. For example, you can mark screens for comparison, you can add wait values to applications that take a long time to respond, or you can abort the recording session without saving the session file and without creating or modifying the test description.
7.2.1.4 – t_rcm_ttdb_ac
Click on the Auto Compare button to automatically compare screens at the start of an interactive terminal recording session. An active button indicates that you want DTM to compare screens automatically. Each time you are prompted during an interactive terminal recording session, DTM can automatically mark the screen for comparison in the benchmark file. DECwindows recording sessions do not automatically mark screens for comparison.
7.2.1.5 – t_rcm_ttdb_iff
Enable the Input File button to direct DTM to use the specified file as input to the test recording. Use the Input file field to enter the name of a file that contains a text representation of all user input, nonprintable control characters, and recording functions in a session file. You can use an input file to record the session file rather than recording the session file interactively. You must create the input file by extracting it from a previously recorded session file.
7.2.1.6 – t_rcm_ttdb_app
Click on the Append button to direct DTM to continue recording a test after the input from a specified input file is exhausted.
7.2.1.7 – t_rcm_ttdb_real
Click on the Realtime button to instruct DTM to record and forward key presses to the application as they are entered, and not when the application requests them. This button is intended for use in recording tests where an application will not read from the terminal until data appears in its terminal input buffer.
7.2.1.8 – t_rcm_ttdb_pb
Click on the Prologue button to direct DTM to execute the test prologue file, specified in the test description, before interactive recording begins.
7.2.1.9 – t_rcm_ttdb_eb
Click on the Epilogue button to direct DTM to execute the test epilogue command file, specified in the test description, when interactive recording stops.
7.2.1.10 – t_rcm_ttdb_vb
Click on the Variables button to direct DTM to apply the variables that were specified in the test description to the test being recorded.
7.2.1.11 – t_rcm_ttdb_fb
Click on the Filters button to direct DTM to apply the filters that were specified in the test description to the test being recorded.
7.2.1.12 – t_rcm_ttdb_ok
Click on the OK button to apply the current settings in the dialog box and remove the dialog box. The border on this button indicates that it is the default choice. You can also choose the default by pressing the RETURN or ENTER key.
7.2.1.13 – t_rcm_ttdb_can
Click on the Cancel button to remove the dialog box without applying any of the settings to the selection.
8 – t_plm
Choose the Play... menu item to replay an interactive terminal test or DECwindows test. The Play operation executes the specified session file. The file is not part of a collection and DTM does not compare the results. For terminal session files, DTM executes the session file as if it were being run on the same type of display device on which it was recorded. If the display device characteristics are different than those for the recording display device, the output may not appear as expected.
8.1 – t_pldw
8.1.1 – t_pldwdb
Use the DECwindows Play dialog box to specify the DECwindows test whose session file you want to replay. The dialog box also provides options for specifying the device and provides the file that receives a copy of the output. DTM creates a task when you play a test.
8.1.1.1 – t_pldwdb_ff
Use the File field to enter the name of the test whose session file you want to replay. Optionally, you can first select (highlight) the test in an active test view window.
8.1.1.2 – t_pldwdb_dis
For terminal tests, DTM displays the output from the session file to the task output window. To specify a different terminal for display, click on the Output button and specify the device in the Output field. For DECwindows tests, DTM displays the output to the device defined by the logical name DECW$DISPLAY.
8.1.1.3 – t_pldwdb_res
Enable the result file button to indicate a specific file to receive a copy of the output of the replay. Use the Result file field to name the file that receives the output from the replay. If you enable the Result File button but leave the field blank, DTM places the output into the file that has a file type of .RES.
8.1.1.4 – t_pldwdb_comm
Use the Command field to invoke an application or run
a command file at the start of a playing a DECwindows
session file.
For example, the following generic command would run an
application undergoing testing:
RUN sys$system:my$application
8.1.1.5 – t_pldwdb_ok
Click on the OK button to apply the current settings in the dialog box and remove the dialog box. The border on this button indicates that it is the default choice. You can also choose the default by pressing the RETURN or ENTER key.
8.1.1.6 – t_pldwdb_cb
Click on the Cancel button to remove the dialog box without applying any of the settings to the selection.
8.2 – t_pltt
8.2.1 – t_plttdb
Use the Terminal Play dialog box to specify the interactive test whose session file you want to replay. The dialog box also provides options for specifying the device and provides the file that receives a copy of the output. DTM creates a task when you play a test.
8.2.1.1 – t_plttdb_ff
Use the File field to enter the name of the test whose session file you want to replay. Optionally, you can first select (highlight) the test in an active test view window.
8.2.1.2 – t_plttdb_dis
For terminal tests, DTM displays the output from the session file to the task output window. To specify a different terminal for display, click on the Output button and specify the device in the Output field. For DECwindows tests, DTM displays the output to the device defined by the logical name DECW$DISPLAY.
8.2.1.3 – t_plttdb_res
Enable the result file button to indicate a specific file to receive a copy of the output of the replay. Use the Result file field to name the file that receives the output from the replay. If you enable the Result File button but leave the field blank, DTM places the output into the file that has a file type of .RES.
8.2.1.4 – t_plttdb_ok
Click on the OK button to apply the current settings in the dialog box and remove the dialog box. The border on this button indicates that it is the default choice. You can also choose the default by pressing the RETURN or ENTER key.
8.2.1.5 – t_plttdb_cb
Click on the Cancel button to remove the dialog box without applying any of the settings to the selection.
9 – t_xtm
Choose the Extract... menu item to extract an input file from a terminal session file without changing the session file. You can use an input file to create a new terminal session file from an existing session file.
9.1 – t_xmdwsi
Choose the DECwindows submenu item to create an DECwindows Input file from a DECwindows session file.
9.1.1 – t_xmdwdb
Use the DECwindows Extract dialog box to specify the DECwindows session file from which DTM creates an input file.
9.1.1.1 – t_xmdwdb_ses
Use the Session File field to enter the name of the session file from which DTM creates an input file.
9.1.1.2 – t_xmdwdb_in
Use the Input file field to specify the file specification for the input file. If you leave this field blank, DTM uses the session file name with the file type of .INP.
9.1.1.3 – t_xmdwdb_au
To be supplied.
9.1.1.4 – t_xmdwdb_ap
Click on the OK button to apply the current settings in the dialog box and remove the dialog box. The border on this button indicates that it is the default choice. You can also choose the default by pressing the RETURN or ENTER key.
9.1.1.5 – t_xmdwdb_cn
Click on the Cancel button to remove the dialog box without applying any of the settings to the selection.
9.2 – t_xm
Choose the Terminal submenu item to create a terminal Input file from a terminal session file.
9.2.1 – t_xmdwdb
Use the Terminal Extract dialog box to specify the terminal session file from which DTM creates an input file. The dialog box also enables you to specify the termination character for the session file, if you used something other than the default, CTRL/P.
9.2.1.1 – t_xmttdb_ses
Use the Session file field to enter the name of the session file from which DTM creates an input file.
9.2.1.2 – t_xmttdb_in
Use the Input file field to specify the file specification for the input file. If you leave this field blank, DTM uses the session file name with the file type of .INP.
9.2.1.3 – t_xmttdb_trm
Use the Termination character field to specify a termination character other than the default, CTRL/P. DTM interprets the character in this field as the termination character when the input file is extracted from the session file. If you did not use the default termination character when you recorded the session file, specify the correct character in this field.
9.2.1.4 – t_xmttdb_ap
Click on the OK button to apply the current settings in the dialog box and remove the dialog box. The border on this button indicates that it is the default choice. You can also choose the default by pressing the RETURN or ENTER key.
9.2.1.5 – t_xmdb_cn
Click on the Cancel button to remove the dialog box without applying any of the settings to the selection.
10 – t_res
Choose the Restore menu item to create a DECwindows session file from a DECwindows Input file.
10.1 – t_resdwsi
Choose the DECwindows... menu item to create a DECwindows session file from a DECwindows Input file.
10.1.1 – t_resdwdb
Use the DECwindows Extract dialog box to specify the DECwindows session file from which DTM creates an input file.
10.1.1.1 – t_resdwdb_in
Use the Input file field to specify the input file to which DTM translates to a session file.
10.1.1.2 – t_resdwdb_ses
Use the Session File field to enter the name of the session file that DTM is to create from the input file.
10.1.1.3 – t_resdwdb_ap
Click on the OK button to apply the current settings in the dialog box and remove the dialog box. The border on this button indicates that it is the default choice. You can also choose the default by pressing the RETURN or ENTER key.
10.1.1.4 – t_resdwdb_cn
Click on the Cancel button to remove the dialog box without applying any of the settings to the selection.
11 – t_memi
Choose the Mask... menu item to invoke the DTM Screen Editor, which enables you to define areas on a DECwindows benchmark image that DTM will not compare against the test results when the test is run in a collection. You can automatically read a DECwindows benchmark image (if it exists) into the Screen Editor by clicking on a DECwindows test in the view window, then pulling down the Testing menu and choosing the Mask... menu item. The Screen Editor operates on DDIF files only.
12 – t_ftm
Choose the Filter... menu item to run filters interactively on a specified file. The filters provided by DTM mask data in result files that varies from one test run to the next. You can also use the filters on files that are not provided by DTM. The filter operation enables you to prepare benchmarks for association with tests or to see how result files would look if filters were run on them. Be aware that when you use filters, DTM deletes the original unfiltered result file, leaving only the filtered file. Using some filters on interactive tests that contain escape sequences can cause DTM to delete information that is essential to the test.
12.1 – t_ftdb
Use the Filter dialog box to specify the file that you want to filter. The dialog box provides buttons that let you indicate which filters you want to apply to the file.
12.1.1 – t_ftdb_fi
Use the File field to enter the name of a file that you want to filter. Optionally, you can first select (highlight) in an active test view window the test whose benchmark file you want to filter.
12.1.2 – t_ftdb_ftb
Click on one or more of the Filter buttons to apply the filters to the selected file. The filters remove run-time variables from the file. The buttons of applied filters become active after you choose them.
12.1.2.1 – t_ftdb_dt
Where the date form is abbreviated, the Date button
replaces date stamps by substituting a "d" for each
displayed number of the day of the month, an "m" for
each displayed letter of the month, and a "y" for each
displayed number of the year. Where the date form is
spelled out, the month name is replaced by "month",
the numeric day is replaced by "day", and the year is
replaced by "year".
The following list shows some examples of the date
filtering functions; this list is not all inclusive.
17-OCT-1998 with dd-mmm-yyyy
17 OCT 98 with dd mmm yy
98.OCT.17 with yy.mmm.dd
10/17/98 with mm/dd/yy
1998/10/17 with yyyy/mm/dd
October 17, 1998 with month day, year
Oct. 17, 1998 with month day, year
17.October.1998 with day.month.year
98-October-17 with year-month-day
12.1.2.2 – t_ftdb_tm
When enabled, the Time button replaces time stamps with
the following forms:
15:37:53.22 with hh:mm:ss.xxxx
15:37:53 with hh:mm:ss
15:37 with hh:mm
3:37 PM with hh:mm xm
15H37m with hhHmmm
15H37' with hhHmm'
15.37 h with hh.mm h
15 h 37"53 s with hh h mm"ss s
15 h 37 min with hh h mm min
kl 15.37 with kl hh.mm
h 15.37 with h hh.mm
12.1.2.3 – t_ftdb_fn
When enabled, the File names Button replaces the file names with FILENAME.EXT.
12.1.2.4 – t_ftdb_dr
When enabled, the Directory button replaces the directory specification field in the file specification with DISK:[DIRECTORY]
12.1.2.5 – t_ftdb_tk
When enabled, the Traceback button replaces 32-bit memory addresses with xxxxxxxx and 64-bit memory addresses with xxxxxxxx xxxxxxxx.
12.1.2.6 – t_ftdb_vrs
When enabled, the Version button replaces file versions with VERSION.
12.1.3 – t_ftdb_ap
Click on the OK button to apply the current settings in the dialog box and remove the dialog box. The border on this button indicates that it is the default choice. You can also choose the default by pressing the RETURN or ENTER key.
12.1.4 – t_ftdb_cn
Click on the Cancel button to remove the dialog box without applying any of the settings to the selection.