priority

Sets the priority of a job or job stream. By assigning a different priority to jobs or job streams you determine which one starts first, if the dependencies are solved.

Assuming the jobs and job streams are ready to be launched , if you set a priority for the job streams and for the jobs in the job streams:
  • The job stream that starts first is the one with the highest priority.
  • Among the jobs in the job stream with the highest priority, the job that starts first is the one with the highest priority.

Syntax

priority number | hi | go

Arguments

number
Specifies the priority. Possible values are 0 through 99. A priority of 0 prevents the job or job stream from launching. The default value is 10 and is not displayed when viewing the job stream definition.
hi
Represents a value higher than any value that can be specified with a number. When set, the job or job stream is immediately launched as soon as it is free from all dependencies.
go
Represents the highest priority that can be set. When set, the job or job stream is immediately launched as soon as it is free from all dependencies.

Comments

Jobs and job streams with hi or go priority levels are launched as soon as all their dependencies are resolved. In this case:
  • Job streams override the cpu job limit.
  • Jobs override the cpu job limit, but they override neither the schedule job limit nor the cpu job fence.

Examples

The following example shows the relationship between job stream and job priorities. The two job streams, sked1 and sked2 have the following definitions in the database: 
schedule sked1 on tu
priority 50
:
job1 priority 15
job2 priority 10
end
schedule sked2 on tu
priority 10
:
joba priority 60
jobb priority 50
end

Since the job stream sked1 has the highest priority then the jobs are launched in the following order: job1, job2, joba, jobb.

If, instead, the job stream priorities are the same, the jobs are launched in the following order: joba, jobb, job1, job2.

If job2 has a dependency A and job1 has a dependency B and the dependency A becomes solved (while B remains not solved) then job2 starts before job1 even though job2 has a priority lower than the one set for job1.