Back to Index |

The Execution Object

Execution is a shell command object that gives you the capability to call external programs (.exe, .bat, etc.) at different times throughout the life of your job. For instance, you want to call a batch file to FTP a file somewhere after the job completes...

Properties

Alias | Alias identifier. Aliases are used on all design objects to simplify coding and to ensure each object has a unique identifier.
Command | Shell process command to run. Path and filename to the executable file, or batch file you want to execute. Example: c:\myprograms\runme.exe
CommandLineArguments | Command line arguments to pass to the Command. If your executable program or batch file requires parameters, enter them here. Example: file=myfile.txt So, given the above examples the program will execute: c:\myprograms\runme.exe file=myfile.txt
Comments | Comment area to give descriptive text about the data object and its purpose.
Execute | BeforeJob / AfterJob. When the job should execute the given command.
ExecutionOrder | In the case where multiple execution objects are used, this parameter specifies the order in which the execution objects should be called. (0, 1, 2, 3...)
Name | Descriptive name for this object. You can enter any text to describe the object.
TailOutput | If the Command that executes returns output, this property specifies the maximum number of characters to return from the output. Use this in cases where the output may be very large and you only need to see the last 'x' characters to ensure its successful completion. *Note: 0 returns all characters. (default) WaitType must be set to Wait otherwise this property is ignored.
Timeout | If WaitType = Wait, you can specify a timeout period based on seconds. If the command does not complete in 'x' seconds the process will timeout. Can be used to ensure a job doesn't hang forever. *Note 0 waits forever (default)
WaitType | Wait / NoWait: specifies if the job should wait until the command has completed, or continue on without waiting.

© 2003 - 2007 Relational Solutions, Inc. - All rights reserved