Running Transaction at the command line (version 10.7)

New features in TRANSACTION version 10.6/10.7 > Running Transaction at the command line (version 10.7)

Back to

New features in TRANSACTION version 10.6/10.7

Running Transaction at the command line (version 10.7)

When you run a Transaction script from the command line, you can pass any number of Transaction Script commands as parameters. See the Transaction script command reference for a complete description of the Transaction Script Command set.

Syntax

To run a Transaction script from the command line, use this syntax:

"<Path>TxShuttlecom.exe" <Central Site>/ShuttleFiles/<script file name>,#f1<Local data file path><data file name>,#AL<Local ALF path><ALF file name>

Note: Ensure that there is a single space between "<Path>TxShuttlecom.exe" and the Transaction script name with full path.

Example

For example, suppose you want to execute FB50_kt1.TxR. In this case, the command line syntax is:

"C:\Program Files (x86)\Winshuttle\TRANSACTION\TxShuttlecom.exe" http://ws8-sp10- 64:28116/sites/10.7FCS/ShuttleFiles/FB50_kt1.TxR,#f1C:\Users\vkumar\Documents\FB50_kt1.xlsx,#ALC:\Users\vkumar\Desktop\WE6800.ALF

This command launches Transaction with the FB50_kt1.TxR loaded and starts executing the Transaction script. You can test this command line operation by running this command in the Windows Run dialog box.

Mandatory parameters

When you run a Transaction script from Central, you must include the following parameters:

"Path of TxShuttlecom.exe"
"Central path of the script"
#F1 To Provide Local data file path
#AL To Provide ALF File path (if the ALF file is not embedded in the script)

Also, if the Run Reason Required option is selected on the Central site, the +RT field is required.

Using Transaction script commands

When you enter Transaction Script commands, separate each command using a comma as the delimiter. The order in which you include these commands is not significant. If the Transaction Script command you specified does not exist in the Transaction script you are using, the command is added at run-time.

Example:

In this example, Transaction runs, opens FB50_kt1.TxR, reads the file, and then replaces or adds these SHUTTLEScript commands to the file:

+DB5000 adds a delay before logon for 5000 milliseconds (ignores +DB command in the Transaction script if present).

+SR4 starts from row 4 (ignores the Start Row specified in the Transaction script).

+SA3 stops after three transactions (ignores the End Row specified in the Transaction script).

After modifying the Transaction script with the new parameters, Transaction runs the recording.

Important: Be sure to test these commands in a nonproduction system with a limited number of transactions before you deploy the Transaction script.

In addition:

All Transaction script commands take precedence over the same commands already contained in the Transaction script. Transaction overwrites the existing Transaction script commands in memory with the commands passed from the command line.
Commands passed as parameters are saved when you save your Transaction script after the run is completed.
To discard the parameter values, either refresh the file (select Edit, and then Refresh) or open the same file without saving the current one. Once you save the current file, the command line parameters entered overwrite the same commands stored in the Transaction script.
Avoid passing transaction-related Transaction Script commands (avoid +Sp, +Sn, +Fn, +Fv, *Fv and ?Fn) as parameters as this might lead to unpredictable results. (These commands usually appear more than once.)

The Transaction Evaluation version might not support this feature.

In this section

Transaction script command reference