Customers need to execute Toad automation actions without manually opening Toad or interacting with the Automation Designer. Common use cases include:
Without correct command-line syntax, actions may not execute, may run against the wrong connection, or may fail due to naming conflicts.
Issues with command-line execution typically occur due to:
-a (action) or -c (connection) parametersUnderstanding how Toad resolves actions, parameters, and connections is critical for successful execution from the command line.
To execute actions from the command line, use the -a parameter and specify:
If only an action name is specified, it must be unique across all Toad Apps. If more than one action with the same name exists, Toad logs an error and the action does not run.
To avoid ambiguity, fully qualify the action using:
ActionSet->ActionName
When executing multiple actions or apps:
Action parameter files allow you to override settings defined in an action without creating multiple copies of the same automation.
property=value pairsParameter files are specified after the action name using a pipe (|) character.
Connection information is normally stored with the action and passwords are retrieved from Connections.xml if Save passwords is enabled.
Connections can be overridden using the -c parameter with a connection string:
-c schema/password@database
When multiple connection sources exist, Toad resolves them in the following order:
Notes:
-c is usedRuns the Toad App MondayQueries and executes all actions within it.
Executes the action Email Report. This only works if the action name is unique across all Toad Apps.
Executes EmpQuery from the CommonQueries Toad App, avoiding naming conflicts.
Executes a qualified action and overrides settings using an INI parameter file.
Runs a combination of Toad Apps and individual actions in sequence.
Runs the MondayReport action using the specified connection instead of the one defined in the Automation Designer.
Executes the same action once for each specified connection.