Configuring a re-usable .cmd script: mandatory parameters

Search Knowledge Base by Keyword

< Back

This Knowledge Base article provides an overview of how to configure and run Subset Actions. Each Action draws upon a set of optional and mandatory parameters. The parameters are set using standardised and re-usable .cmd scripts. This article explains how to edit and run the script, and how to analyse the results.

Mandatory Parameters

Each Subset Action is run by a standardised .cmd script. You should have downloaded this script as “subset.cmd”. You can clone and rename the script if you would like to create repeatable, re-usable Actions.

You must edit the re-usable .cmd to specify the mandatory parameters:

  1. The database type
  2. The location of the flow that will execute the Subsetting
  3. The location of the Basic Control Spreadsheet
  4. The Actions that will be executed
  5. The location where the Log file will be saved
  6. The location where the Subset Report will be saved

The .CMD script should be edited using a text editor before executing a new Action.

The parameters should already be present in the re-usable .cmd script, and you simply need to edit them. Perform a find in the script to locate the existing parameter and specify a new one. If not, simply the standard code to the script and specify the parameter.

First, edit -parDatabaseType=”” to specify one of the following four database types:

  1. -parDatabaseType=”MySQL”
  2. -parDatabaseType=”SQL Server”
  3. -parDatabaseType=”Postgres”
  4. -parDatabaseType=”Oracle”

For example:

Data Subsetting

Next, specify location of the .vip workflow under the parameter


Subsetting uses the flow. Enter the location of this flow:

Data Subsetting

Next, you must specify the location of your Control Spreadsheet under


For example:

Data Subsetting

Next, specify the Subset Actions that you would like to perform under


Multiple Actions can be executed by one Script. To execute multiple actions, separate list the Action name in a comma separated list.

For example, to perform TABLES and then GETKEYS, specify:

Data Subsetting

Next, specify where the folder in which the generated Log files will be stored. Use


For example:

Data Subsetting

Finally, specify the name of the Subset Report, and the folder into which it will be generated. Use


to specify the directory. For example:

Data Subsetting

These are the mandatory parameters for executing a Subset Action using Test Data Automation. They must be set each time an Action is run.