limit

The limit keyword limits the number of jobs that can run simultaneously in a job stream. This keyword works only if all the jobs in the job stream are defined on workstations that are managed by the same batchman process. There are three possible cases:
The workstation on which batchman runs is a fault-tolerant agent
In this case, the limit keyword limits the number of jobs, defined in the fault-tolerant agent and in the extended agents defined on this fault-tolerant agent, that can run simultaneously in the job stream. The job stream must contain only jobs defined in the fault-tolerant agent or in the extended agents running on the fault-tolerant agent.
The workstation on which batchman runs is a domain manager
In this case, in addition to workstations of the previous case, the job stream can contain jobs running on standard agents connected to the domain manager, or to any fault-tolerant agent managed by this domain manager, configured with the FULLSTATUS parameter set to on.
The workstation on which batchman runs is a dynamic domain manager
In addition to workstations of the previous cases, the job stream can contain jobs defined on the broker and its dynamic agents.
In other scenarios, the use of the limit keyword to limit the number of jobs that can run simultaneously might not work as expected.

Syntax

limit joblimit

Arguments

joblimit
Specifies the number of jobs that can be running at the same time in the job stream. Possible values are 0 through 1024. If you specify 0, you prevent all jobs from being launched, including the one with priority set to GO or HI.

Examples

The following example limits to five the number of jobs that can run simultaneously in job stream sked2:

schedule sked2 on fr
  limit 5 :