A Scripting Language Summary
Job Specification vs Job Authoring in Python
...
...
...
- Remote Servers, Launch Expressions, and Runtime Substitution
- Sharing One Server Check-Out Among Several Commands
- Special Characters and Escapes in Tractor Scripts
- Shell Pipelines and other Expressions
...
Job Specification vs Job Authoring in Python
NOTE See the Python Job Authoring API discussion for details on creating and spooling jobs from your own Python scripts.
For simple single-command jobs such as rendering a network mounted RIB file, you can also use tractor-spool command-line options to create the job for you:
tractor-spool -c prman -Progress /net/myfiles/frame1.rib or tractor-spool -c /usr/bin/printenv
The section below describes a different concept: The format and syntax of the "classic" job files used to statically define a single job's structure, as a data file. Job files like this are usually written by other programs and then spooled into the Tractor job queue using the tractor-spool program.
Static Job Specification Synopsis
Tractor Job files are typically represented as TCL scripts using special job definition operators recognized by the Tractor job parser. This format was first introduced for the Alfred system, and Tractor remains compatible with nearly all Alfred constructs.
Tractor also supports an evolving set of JSON job specification formats, described in a separate document.
Tractor job input scripts (in alfscript format) are composed of expressions using the following Tcl operators:
Job [options] Task {title} [options] RemoteCmd {launch_expr} [options] Cmd {launch_expr} [options] Instance {task_title_to_reference} Iterate varname -from n -to m -by i -template {script} [options] Assign varname {value_string}
See the Operator Details for detailed descriptions of options and operator syntax.
...