qlimit(1) CLIX qlimit(1)
NAME
qlimit - Shows supported batch limits and shell strategy for local host
SYNOPSIS
qlimit
DESCRIPTION
The qlimit command displays the batch request resource limits that can be
directly enforced on the local host and the batch request shell strategy
for the local host.
Network Queuing System (NQS) supports many batch request resource limits
that can be applied to an NQS batch request. However, this implementation
does not support the entire set of limits that NQS provides. The limits
supported are a per-process nice value and a per-process file size.
The limits applied to a batch request are always restricted to the limits
that can be directly supported by the underlying implementation. If a
batch request specifies a limit that cannot be enforced by the underlying
implementation, the limit is ignored and the batch request will operate as
though a limit (other than the physical maximums) had not been placed on
that resource.
When an attempt is made to queue a batch request, each limit specified by
the request (that can also be supported by the local implementation) is
compared to the corresponding limit for the destination batch queue. If a
limit for a batch queue is defined to be ``unlimited'' or greater than or
equal to the corresponding limit of the batch request, the request will be
successfully queued (barring other abnormal conditions). If a request
specifies a limit of ``infinity'', the corresponding limit for the queue
must also be ``infinity''.
The limit checks are performed regardless of whether the batch request was
submitted by directly using the qsub command or by indirectly placing the
request in a pipe queue. It is impossible for a batch request to be
queued in an NQS batch queue if any of these limit checks fail.
If a request does not specify a limit that is supported on the local host,
the corresponding limit as configured for the destination queue becomes
the limit for the request.
Upon the successful queuing of a request in a batch queue, the limits
under which the request executes are frozen and are not modified by
subsequent qmgr commands that alter the limits of the containing batch
queue.
As mentioned above, this command also displays the shell strategy as
configured for the local host. Without a shell specification for a batch
2/94 - Intergraph Corporation 1
qlimit(1) CLIX qlimit(1)
request, NQS must choose the shell that should be used to execute the
request. NQS supports three different strategies to solve this problem:
fixed, free, and login.
⊕ A fixed shell strategy means that all batch requests will be executed
using the shell chosen by the system administrator.
⊕ A free shell strategy means that the batch requests will be run the
same as an interactive invocation of the request would be run.
⊕ A login shell strategy means that the batch requests will be executed
by the user's normal login shell.
The default shell strategy is free. Host machines which reach the maximum
number of process's allowed on the system should use a fixed or login
strategy because a single shell will be exec'd to run all commands in the
request script. qlimit will display the chosen shell if the fixed
strategy has been selected.
DIAGNOSTICS
Seek staff support
An internal or NQS error occurred. Seek help from the NQS or
system administrator.
EXIT VALUES
Value Explanation
__________________________________________________________
1 Could not change directories to NQS root directory
2 Could not open parameters database
0 Successful
RELATED INFORMATION
Commands: qdel(1), qdev(1), qpr(1), qstat(1), qsub(1), qmgr(8)
2 Intergraph Corporation - 2/94