Introduction
Process classes limit the number of jobs that are running concurrently. Process classes specify remote JobScheduler Workload instances and Agents on which jobs should be executed.
A process class is an object that can be assigned to a job. It has two functions:
- To limit the number of processes that can start in parallel.
- If that limit were reached then an additional job would be caused to wait for the process class to become available.
- Jobs waiting for a process class to become available will not consume system resources such as CPU or memory.
- To run a job on a remote JobScheduler Workload instance or Agent.
- Process classes can reference remote JobScheduler instances for execution of a job:
- At the time of job execution the initiating JobScheduler hands over the job configuration to the remote JobScheduler instances.
- After completion of the job the initiating JobScheduler regains full control and would continue execution e.g. with the next job in a job chain.
- Process classes can be used as a means to implement high availability:
- A sequence of JobScheduler Agents can be specified that would be checked for availability by the initiating JobScheduler instance at run-time.
- If a JobScheduler Agent were not avaiable then the next Agent would be selected for execution of a job.
- Process classes can reference remote JobScheduler instances for execution of a job:
See also