If a batch command script is associated with an upgrade task, it will be executed along with the major batch operations. For example, during the deploy operation, gmStudio executes the following command line:
The batch command script is a template file: it supports an extensive set of parameter variables (i.e. %parameter%) that will be replaced by actual values associated with the upgrade project/task to create an actual batch command script. The replacements produce the Actual Batch Command Script in the workspace\log folder. That Actual Batch Command Script is executed before and after the associated batch operation being performed by gmStudio. A listing of the actual batch script in the log folder may be viewed at the bottom of the Deploy Log display on the Information panel.
The UsrCmds field on each task record is where you specify the name of your batch script template. You will not typically specify the full path to your batch file, rather you will specify just the filename then place the script in the workspace\usr folder.
The steps to associate a batch command script with an upgrade task are as follows:
Once you have associated a batch command script with a task, clicking [Edit Task Script(s)] on the Task context menu will open the file in the editor along with the main translation task script.
A listing of a sample batch command script template is shown below. Notice there are examples of the script parameters and labeled sections that correspond to the different execution points.
This particular script has code in the TEST section which executes the .NET binary and compares its output with the output generated by running the VB6 code.