Choose the Create menu item, which produces a submenu of the objects that you can create. The submenu contains these objects: o Test o Collection o Group o Variable o History
1 – m_ctm
Choose the Test submenu item to create a test description in the DTM library. A test description is all the information associated with a specific test. DTM uses this information to execute the test.
1.1 – m_ct_dw
Choose the DECwindows... submenu item to create a DECwindows test description in the DTM library. A DECwindows test description is all the information associated with a specific DECwindows test. DTM uses this information to execute the test.
1.1.1 – m_ct_dwdb
Use the Create DECwindows Test dialog box to create a DECwindows test description in the DTM library.
1.1.1.1 – m_ct_dwdb_tf
Use the Test field to enter the name of the DECwindows test description. The test name is the unique identifier of the test description and is the only means of access to a test description. A test name can have a maximum of 39 characters and must follow the same OpenVMS syntax as for file names. You cannot use wildcards to specify the test name.
1.1.1.2 – m_ct_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).
1.1.1.3 – m_ct_dwdb_tem
Use the Template field to specify the command file that runs a test, the file that is the test itself, or the file containing the DECwindows session. DTM supplies a template file name of test_name.SESSION for DECwindows tests. If you include a directory specification with the file name, DTM ignores the default template directory.
1.1.1.4 – m_ct_dwdb_ben
Use the Benchmark field to specify the file to contain the expected output from the test's execution. DTM supplies a file name and file type of test_ name.BMK. If you include a directory specification with the file name, DTM ignores the default benchmark directory.
1.1.1.5 – m_ct_dwdb_pro
Use the Prologue field to add a specific prologue file to the test description; otherwise, no prologue is associated with the test description. DTM runs the test prologue file immediately before executing the test template file. This prologue is independent of the collection prologue.
1.1.1.6 – m_ct_dwdb_epi
Use the Epilogue field to add a specific epilogue file to the test description; otherwise, no epilogue is associated with the test description. DTM runs the test epilogue file immediately after executing the test template file. This epilogue is independent of the collection epilogue.
1.1.1.7 – m_ct_dwdb_var
Use the Variables field to specify variables to associate with the test description; otherwise, no variables are associated with the test description. Valid variable names must be defined in the DTM library. A variable specified in this field becomes local in scope. You cannot use wildcards to specify variable names. Use commas to separate more than one variable name. If you do not specify a value for the variable, it uses the value defined when the variable is created. If you specify an optional variable value, the variable takes on that value for this test description only.
1.1.1.8 – m_ct_dwdb_comm
Use the Command field to invoke an application or run
a command file at the start of a DECwindows recording
session.
For example, the following generic command would run an
application undergoing testing:
RUN sys$system:my$application
1.1.1.9 – m_ct_dwdb_comp
Choose one of the Comparison Type buttons to specify
how you want DTM to compare the result and benchmark
files.
The table below defines the selectable comparison
types.
Type Meaning
Screens Compares marked screen images only. The
default type for DECwindows tests.
Default No local override, uses test type default
If not selected, the default is no local override.
The result file is compared based on the collection
comparison type if set, otherwise the default test
comparison type is used.
1.1.1.10 – m_ct_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.
1.1.1.11 – m_ct_dwdb_cb
Click on the Cancel button to remove the dialog box without applying any of the settings to the selection.
1.2 – m_ct_tt
Choose the Terminal... submenu item to create a terminal test description in the DTM library. A terminal test description is all the information associated with a specific terminal (character cell) test. DTM uses this information to execute the test.
1.2.1 – m_ct_ttdb
Use the Create Terminal Test dialog box to create a terminal test description in the DTM library.
1.2.1.1 – m_ct_ttdb_tf
Use the Test field to enter the name for the terminal test description. The test name is the unique identifier of the test description and is the only means of access to a test description. A test name has a maximum of 39 characters and follows the same OpenVMS syntax as for file names. You cannot use wildcards to specify the test name.
1.2.1.2 – m_ct_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).
1.2.1.3 – m_ct_ttdb_tem
Use the Template field to specify the command file that runs a test, the file that is the test itself, or the file containing the interactive terminal session. DTM supplies a template file name of test_name.SESSION for interactive terminal tests. If you include a directory specification with the file name, DTM ignores the default template directory.
1.2.1.4 – m_ct_ttdb_ben
Use the Benchmark field to specify the file to contain the expected output from the test's execution. DTM supplies a file name and file type of test_ name.BMK. If you include a directory specification with the file name, DTM ignores the default benchmark directory.
1.2.1.5 – m_ct_ttdb_pro
Use the Prologue field to add a specific prologue file to the test description; otherwise, no prologue is associated with the test description. DTM runs the test prologue file immediately before executing the test template file. This prologue is independent of the collection prologue.
1.2.1.6 – m_ct_ttdb_epi
Use the Epilogue field to add a specific epilogue file to the test description; otherwise, no epilogue is associated with the test description. DTM runs the test epilogue file immediately after executing the test template file. This epilogue is independent of the collection epilogue.
1.2.1.7 – m_ct_ttdb_var
Use the Variables field to specify variables to associate with the test description; otherwise, no variables are associated with the test description. Valid variable names must be defined in the DTM library. A variable specified in this field becomes local in scope. You cannot use wildcards to specify variable names. Use commas to separate more than one variable name. If you do not specify a value for the variable, it uses the value defined when the variable is created. If you specify an optional variable value, the variable takes on that value for this test description only.
1.2.1.8 – m_ct_ttdb_comp
Choose one of the Comparison Type buttons to specify
how you want DTM to compare the result and benchmark
files.
The table below defines the selectable comparison
types.
Type Meaning
Screens Compares marked screen images only. The
default type for interactive tests.
Records Compares the files record by record
Characters Compares the files character by character
Default No local override, uses test type default
If not selected, the default is no local override.
The result file is compared based on the collection
comparison type if set, otherwise the default test
comparison type is used.
1.2.1.9 – m_ct_ttdb_fil
DTM does not automatically associate any filters with the test description. You must click on one or more of the Filter buttons to apply the filters to the test description's results. The filters remove run-time variables from the result file produced by the collection run. The buttons of applied filters become enabled after you choose them.
1.2.1.9.1 – m_ct_ttdb_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
1.2.1.9.2 – m_ct_ttdb_dr
When enabled, the Directory button replaces the directory specification field in the file specification with DISK:[DIRECTORY]
1.2.1.9.3 – m_ct_ttdb_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
1.2.1.9.4 – m_ct_ttdb_tk
When enabled, the Traceback button replaces 32-bit memory addresses with xxxxxxxx and 64-bit memory addresses with xxxxxxxx xxxxxxxx.
1.2.1.9.5 – m_ct_ttdb_fn
When enabled, the File names Button replaces the file names with FILENAME.EXT.
1.2.1.9.6 – m_ct_ttdb_vrs
When enabled, the Version button replaces file versions with VERSION.
1.2.1.10 – m_ct_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.
1.2.1.11 – m_ct_ttdb_cb
Click on the Cancel button to remove the dialog box without applying any of the settings to the selection.
1.3 – m_ct_ni
Choose the Noninteractive... submenu item to create a noninteractive test description in the DTM library. A noninteractive test description is all the information associated with a specific noninteractive (character cell) test. DTM uses this information to execute the test.
1.3.1 – m_ct_nidb
Use the Create Noninteractive Test dialog box to create a noninteractive test description in the DTM library.
1.3.1.1 – m_ct_nidb_tf
Use the Test field to enter the name for the noninteractive test description. The test name is the unique identifier of the test description and is the only means of access to a test description. A test name has a maximum of 39 characters and follows the same OpenVMS syntax as for file names. You cannot use wildcards to specify the test name.
1.3.1.2 – m_ct_nidb_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).
1.3.1.3 – m_ct_nidb_tem
Use the Template field to specify the command file that runs a test, the file that is the test itself. DTM supplies a template file name of test_name.COM for noninteractive tests. If you include a directory specification with the file name, DTM ignores the default template directory.
1.3.1.4 – m_ct_nidb_ben
Use the Benchmark field to specify the file to contain the expected output from the test's execution. DTM supplies a file name and file type of test_ name.BMK. If you include a directory specification with the file name, DTM ignores the default benchmark directory.
1.3.1.5 – m_ct_nidb_pro
Use the Prologue field to add a specific prologue file to the test description; otherwise, no prologue is associated with the test description. DTM runs the test prologue file immediately before executing the test template file. This prologue is independent of the collection prologue.
1.3.1.6 – m_ct_nidb_epi
Use the Epilogue field to add a specific epilogue file to the test description; otherwise, no epilogue is associated with the test description. DTM runs the test epilogue file immediately after executing the test template file. This epilogue is independent of the collection epilogue.
1.3.1.7 – m_ct_nidb_var
Use the Variables field to specify variables to associate with the test description; otherwise, no variables are associated with the test description. Valid variable names must be defined in the DTM library. A variable specified in this field becomes local in scope. You cannot use wildcards to specify variable names. Use commas to separate more than one variable name. If you do not specify a value for the variable, it uses the value defined when the variable is created. If you specify an optional variable value, the variable takes on that value for this test description only.
1.3.1.8 – m_ct_nidb_comp
Choose one of the Comparison Type buttons to specify
how you want DTM to compare the result and benchmark
files.
The table below defines the selectable comparison
types.
Type Meaning
Records Compares the files record by record. The
default type for noninteractive tests.
Characters Compares the files character by character
Default No local override, uses test type default
If not selected, the default is no local override.
The result file is compared based on the collection
comparison type if set, otherwise the default test
comparison type is used.
1.3.1.9 – m_ct_nidb_fil
DTM does not associate any filters with the test description unless you click on one or more of the Filter buttons to apply the filters to the test description's results. The filters remove run-time variables from the result file the collection run produces. The buttons of applied filters become enabled after you choose them.
1.3.1.9.1 – m_ct_nidb_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
1.3.1.9.2 – m_ct_nidb_dr
When enabled, the Directory button replaces the directory specification field in the file specification with DISK:[DIRECTORY]
1.3.1.9.3 – m_ct_nidb_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
1.3.1.9.4 – m_ct_nidb_tk
When enabled, the Traceback button replaces 32-bit memory addresses with xxxxxxxx and 64-bit memory addresses with xxxxxxxx xxxxxxxx.
1.3.1.9.5 – m_ct_nidb_fn
When enabled, the File names Button replaces the file names with FILENAME.EXT.
1.3.1.9.6 – m_ct_nidb_vrs
When enabled, the Version button replaces file versions with VERSION.
1.3.1.10 – m_ct_nidb_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.3.1.11 – m_ct_nidb_cb
Click on the Cancel button to remove the dialog box without applying any of the settings to the selection.
2 – m_c_cl
Choose the Collection... submenu item to create a set of files that DTM uses to run the tests in the collection. A collection can contain noninteractive tests, interactive terminal tests, and DECwindows tests in any combination. DTM constructs the set of tests in the collection by taking a "snapshot" of the test descriptions when you create the collection. If you subsequently change any of the test descriptions, you must re-create the collection. Changes made to files referenced by the collection do affect the collection at run time.
2.1 – m_ccdb
Use the Create Collection dialog box to create a set of files for running one or more tests. This dialog box enables you to specify the tests and groups in the collection. Use the Create Collection Options dialog box to choose the options for the collection.
2.1.1 – m_ccdb_cl
Use the Collection field to enter the collection name. This name uniquely identifies a set of tests to run. A collection name can have a maximum of 39 characters and follows the same OpenVMS syntax as file names. You cannot use wildcards in the collection name.
2.1.2 – m_ccdb_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 under additional topics.
2.1.3 – m_ccdb_tst
Use the Tests field to enter test description names or wildcard forms of these names into the test collection. Separate test names with commas.
2.1.4 – m_ccdb_gp
Use the Groups field to enter group names or wildcard forms of these names into the test collection. Separate group names with commas.
2.1.5 – m_ccdb_vtb
When you click on the Verify button, you perform one
of the following operations, depending on the status of
the button:
Enabled DTM verifies that all files associated with
button all test descriptions in the collection
exist. If a referenced file does not exist,
DTM will not create the collection.
Disabled DTM creates the collection without verifying
button the existence of files.
2.1.6 – m_ccdb_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.
2.1.7 – m_ccdb_o
Click on the Options... button to specify values for additional collection fields. These options are not required to create a collection. You can specify the following options: o Prologue file o Epilogue file o Variables o Benchmark directory o Benchmark class o Template directory o Template class o Comparison type o Differences format o Ignore options o Skip text delimiters
2.1.7.1 – m_cco_db
Use the Create Collection Options dialog box to specify values for collection fields. These options are not required to create a collection.
2.1.7.1.1 – m_cco_pg
Use the Prologue field to specify a prologue file that DTM associates with the collection. The collection prologue is independent of any test prologues associated with specific tests.
2.1.7.1.2 – m_cco_eg
Use the Epilogue field to specify epilogue file DTM associates with the collection. The collection epilogue is independent of any test prologues associated with specific tests.
2.1.7.1.3 – m_cco_vr
The collection uses the default values for global variables. Use the Variables field to override the values of specific global variables for this collection. Valid variable names are the names for the global variables you want to override. The variable must already exist in the DTM library. You must include a variable value for each variable name. Separate variables with commas.
2.1.7.1.4 – m_cco_bkd
The directory that DTM uses to locate benchmark files depends on the directory you specify in this collection Benchmark directory field and the Benchmark field in the Create Test Options dialog box.
2.1.7.1.5 – m_cco_bkc
Use the Benchmark class field to specify the optional Code Management System (CMS) class for benchmark files stored in a CMS library. If you do not specify a class and the file is stored in a CMS library, DTM uses the latest generation on the main line of descent.
2.1.7.1.6 – m_cco_tpd
The directory that DTM uses to locate template files depends on the directory you specify in this Collection Template Directory field and the Template field in the Create Test Options dialog box.
2.1.7.1.7 – m_cco_tpc
Use the Template class field to specify the optional Code Management System (CMS) class for template files stored in a CMS library. If you do not specify a class and the file is stored in a CMS library, DTM uses the latest generation on the main line of descent.
2.1.7.1.8 – m_cco_tp
Click on the Compare button to determine whether DTM compares the results of each test to its benchmark file after the collection is executed. If the Compare button is enabled, DTM compares all tests. A collection must be compared before you can review it. DTM records any differences in a difference file for that test. DTM compares tests without benchmarks, but it marks these tests with a new test status. When you review these tests, you can generate benchmarks for them.
2.1.7.1.9 – m_cco_tprb
Click on one of the following Comparison type buttons
to specify the type of comparison:
o Test Default button causes DTM to keep the setting
you chose for each test when you created it.
o Screens button to produce a screen by screen
comparison (default for interactive terminal and
DECwindows tests)
o Records button to produce a record by record
comparison (default for noninteractive tests).
o Characters to produce a character by character
comparison.
By clicking on either the Screens, Records or
Characters button, DTM compares all tests in the
collection using the specified comparison type,
regardless of the individual test comparison setting
might be.
2.1.7.1.10 – m_cco_df
Click on the Full and Parallel buttons to modify the content and format of a printed difference file for noninteractive tests. Use the Width field to specify the width of the difference file's output.
2.1.7.1.11 – m_cco_fl
Click on the Full button to modify the contents of a printed difference file for interactive tests. When the Full 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 Full button is disabled DTM includes only a listing of differences.
2.1.7.1.12 – m_cco_par
Click on the Parallel button to modify the format of a printed difference file for noninteractive tests. An enabled button causes DTM to place the lines that do not match from the result and benchmark file side by side in the difference file. A disabled button causes DTM to place the benchmark lines above and the corresponding result lines below in the difference file.
2.1.7.1.13 – m_cco_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.
2.1.7.1.14 – m_cco_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
2.1.7.1.15 – m_cco_se
Use the Skip Text fields to enter a pair of strings 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.
2.1.7.1.16 – m_cco_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.
2.1.7.1.17 – m_cco_cn
Click on the Cancel button to remove the dialog box without applying any of the settings to the selection.
2.1.8 – m_ccdb_cn
Click on the Cancel button to remove the dialog box without applying any of the settings to the selection.
3 – m_cgpm
Choose the Group submenu item to create an empty group in the DTM library. Once created, you can insert tests and other groups into the newly created group by using the Insert function under the Maintenance menu. A group enables you to manipulate a set of tests as one entity.
3.1 – m_cgpdb
Use the Create Group dialog box to create a group. This dialog box contains fields for the group name and an associated remark.
3.1.1 – m_cgpdb_g
Use the Group field to enter the name of the group. A group name can have a maximum of 39 characters and follows the same OpenVMS syntax as for file names. You cannot use wildcards to specify the group name.
3.1.2 – m_cgpdb_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).
3.1.3 – m_cgpdb_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.
3.1.4 – m_cgpdb_cn
Click on the Cancel button to remove the dialog box without applying any of the settings to the selection.
4 – m_cvm
Choose the Variable... submenu item to define a variable in the current DTM library. You can only include variables in test descriptions or collections after defining variables in the library.
4.1 – m_cvdb
Use the Create Variable dialog box to create a variable
in the current DTM library.
When you define a variable, you must specify the
following information in the dialog box:
o The variable's value
o Whether the variable is local or global
o Whether the variable is a symbol or a logical name
o Whether the variable value is a string or a numeric
value (if the variable is a symbol)
4.1.1 – m_cvdb_vr
Use the Variable field to enter a unique name for the variable. A variable name can have a maximum of 39 characters and must follow OpenVMS syntax for file names. You cannot use wildcards to specify the variable name. You cannot use the variable names P1 through P8, nor can you use variable names beginning with DTM$.
4.1.2 – m_cvdb_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).
4.1.3 – m_cvdb_vl
Use the Value field to specify the default value for this variable. DTM uses the default value unless you override it when you create a specific test description or collection.
4.1.4 – m_cvdb_sp
Click on either the Local or Global buttons to specify the scope of the variable. A local variable is accessible only to an individual test that references the variable in its test description. A global variable is accessible to all tests in all collections.
4.1.5 – m_cvdb_us
You must specify the defined variable as either a symbol or logical name. Click on the Symbol button to define the variable as a OpenVMS symbol. If you define the variable as a symbol, you must also specify its type. Click on the Logical button to define the variable as a OpenVMS logical name.
4.1.6 – m_cvdb_tp
If you have defined the variable's usage as a symbol,
you must also define its type. The following table
shows your options:
Button Description
Default Causes DTM to define the symbol type as
a numeric value if the variable value is
not enclosed in quotation marks (") and
as a string value if the variable value is
enclosed in quotation marks.
Numeric Defines the symbol type as a numeric value.
String Defines the symbol type as a string.
4.1.7 – m_cvdb_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.
4.1.8 – m_cvdb_cn
Click on the Cancel button to remove the dialog box without applying any of the settings to the selection.
5 – m_chym
Choose the History... submenu item to add a remark to the DTM history file. Use this operation to record an unusual occurrence or a testing milestone. DTM provides remark fields for most operations in their dialog boxes. DTM logs these remarks with a record of the operation in the history file.
5.1 – m_chydb
Use the Create History Remark dialog box to add a specific remark to the DTM history file. Use the text entry field to enter the remark text that you want to add to the DTM history file.
5.1.1 – m_chydb_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.
5.1.2 – m_chydb_cn
Click on the Cancel button to remove the dialog box without applying any of the settings to the selection.