312 Chapter 4
Command Definition F-K
LIMIT
LIMIT
Limits the number of concurrently running jobs/sessions. (Native Mode)
Syntax
LIMIT[ { [+ | - ] numberjobs [+ | - ] ,numbersessions | numberjobs,numbersessions ]
[;JOBQ=queuename]
Parameters
+ Increment the limit value
- Decrement the limit value
numberjobs The number of jobs.
number-
sessions The number of sessions.
<omitted> If you specify no parameter, a message is displayed listing the current
limits.
queuename The name of the job queue whose limit is being changed or displayed.
Operation Notes
Maximum job and session limits are established by the system supervisor during system
configuration. Within these limits, the operator may redefine the job and session limit with
the LIMIT command. When the system is restarted from disk in a START RECOVERY, the
operator defined limits are retained. When any other startup option is used, the values
configured by the supervisor take effect.
If you enter one parameter and omit the other, the limit of the omitted parameter remains
unchanged.
No new jobs or sessions are dispatched that would cause either of these limits to be
exceeded, unless they are initiated with the HIPRI parameter of the JOB or HELLO
commands.
Jobs that belong to individual job queues cannot begin execution while the specific job
queue limit is exceeded. Even if a specific job queue limit is not exceeded, the global system
job limit must also not be exceeded in order for the job to begin execution.
Non-HIPRI jobs can still be introduced when the limit is achieved, but they do not execute.
If you attempt to log on to a non-HIPRI session after the limit has been reached, you
receive the message:
CAN'T INITIATE NEW SESSIONS NOW
The specified limits may be exceeded at the time the command is issued. This does not
cause jobs or sessions executing at the time to abort. They continue to execute, but no new
jobs are allowed to enter the executing state, and no new sessions are initiated.
