Page Operations
Browse SpaceDescription
You can use the Job job entry to execute a previously defined job.
Warning: Although it is possible to create a recursive, never ending job that points to itself, you should be aware that such a job will eventually fail with an out of memory or stack error.
Options
| Option | Description | |
|---|---|---|
| Name of the job entry | The name of the job entry. This name has to be unique in a single job. A job entry can be placed several times on the canvas, however it will be the same job entry. | |
| Name of transformation | The name of the job to start. | |
| Repository directory | The directory in the repository where the job is located. | |
| Filename | If you're not working with a repository, specify the XML filename of the job to start. | |
| Specify log file | Check this if you want to specify a separate logging file for the execution of this job. | |
| Name of log file | The directory and base name of the log file (for example C:\logs) | |
| Extension of the log file | The filename extension (for example: log or txt) | |
| Include date in filename | Adds the system date to the filename. (_20051231) | |
| Include time in filename | Adds the system time to the filename. (_235959) | |
| Logging level | Specifies the logging level for the execution of the job. See also the logging window in .14 Logging | |
| Copy previous results to arguments | The results from a previous transformation can be sent to this job using the "Copy rows to result" step in a transformation. | |
| Arguments | Specify the strings to use as arguments for the job. | |
| Execute once for every inputrow | This implements looping. If the previous job entry returns a set of result rows, you can have this job executed once for every row found. One row is passed to this job at every execution. For example you can execute a job for each file found in a directory using this option. | Note: you can use variables $
Unknown macro: {path}
in the filename and job name fields to specify the job to be executed. |