Variables

TA provides a rich set of variables representing system, job and job event data points. In addition, users can define their own variables to represent dynamic information. You can use variables for command parameters, in various action messages and in job and job group dependencies. You can update user-defined variables through variable actions.

Variables are useful for specifying information that continually changes or is only available at certain times.

Example: If you want to know which queue your job enters when it runs, you can use the Queue Name variable to specify that information. Using the Queue Name variable in a mail action message, you can email yourself the name of the queue your job enters at every runtime.

TA’s variables function is a blend of power and flexibility that you expect in a world-class application.

Any argument that either explicitly has a space in it or could have a space in the argument should be enclosed in quotation marks; otherwise, the argument is returned as separate arguments wherever the spaces occur.

Example: A job called Section 59 Tally would be returned as separate arguments, “Section,” “59” and “Tally.” Similarly, if a variable like <jobname> could return an argument containing a space, it also should be enclosed in quotation marks.