Overview of Job Priorities and Priority Precedence
When a job is started, the Job Manager assigns it a three-digit job priority number, representing the operation, agent, and client priorities. The lower the job priority number is, the higher the priority assigned to the job, which determines its position in the job queue. If there is contention for resources, the job with the highest priority gets the resources first. When multiple jobs have the same priority, resources are allocated on a first-come, first-served basis. After a job is completed, the Job Manager automatically assigns newly freed resources to the next job.
By default, the Job Manager automatically assigns the same priority to all clients and all agents. However, you can prioritize them according to your requirements by changing the default values to user-defined values.
You can select one of the following to have priority precedence:
- Agent Type
If you select Client, each client's priority setting will be considered before the agent type priority setting is considered. If you select Agent Type, the priority setting of the agent type will be considered before the client's priority setting.
Job priority can be assigned to the following:
- a specific client
- an agent type
- a job type
- a specific job
The following table illustrates how the priority settings for client and agent type impact the overall job priority based on which priority precedence setting is selected - Client or Agent Type.
|Client (Priority)||Agent (Priority)||Job Priority if Priority Precedence = Client||Job Priority if Priority Precedence = Agent Type|
|Client A (1)||Windows File System Agent (9)||2nd||4th|
|Client B (1)||SQL Server Agent (5)||1st||2nd|
|Client C (2)||UNIX File System Agent (7)||4th||3rd|
|Client D (2)||Oracle Agent (3)||3rd||1st|