Page History

...

• Title: A title can be added to the job that will be displayed with the respective views.
• Job Class: 

  • Status
    colour Yellow title TODO

• Compatibility: For users of JobScheduler branch 1.x a compatibility mode is available.
  • For use of environment variables compatibility enables
    • to automatically create environment variables for shell jobs from any available order variables and job arguments.
    • to use the prefix SCHEDULER_PARAM_ for any environment variable created.
  • For use of job arguments the compatibility mode offers a corresponding tab.
• For Shell Jobs: Environment Variables Subtab
  • Any environment variables for job scripts have to be specified by a mapping:
    
    
    
    
  • The mapping includes to specify a name for the environment variable that has to comply with OS requirements. Names are automatically converted to uppercase. The GUI offers the list of order variable names for the mapping to environment variables.
  • The value of an environment variable is an expression that can be specified like this:
    • as a reference to a variable using the syntax $variableName
      • consider that no leading or trailing spaces are allowed for references.
    • as a string which is a sequence of characters
      • excluding enclosed with single quotes to allow literal use of any characters, including the $ character that prefixes variables.character. The only character not allowed for a string is a single quote.
      • enclosed with double or being enclosed with single quotes to allow literal mixed use of the characters and variables. A $ character .
      as a reference to
      • is considered to prefix a variable
      using the syntax $variableName
      • .
  • The advantage of the above mapping is the fact that
    • you publish environment variables only that are required by a job instead of creating an arbitrary number of environment variables from any order variables and job arguments,
    • you limit the risk to overwrite existing shell environment variables, e.g. when passing an order variable with the name "PATH" then this would overwrite a shell environment variable with the same name.

...