..  _jobs:

JOBS
====

+----------+------------------------------------------------------------------+
| Syntax   | JOBS [#channel]   or                                             |
|          |                                                                  |
|          | JOBS \\file                                                      |
+----------+------------------------------------------------------------------+
| Location | Toolkit II, THOR XVI                                             |
+----------+------------------------------------------------------------------+

This command lists all jobs currently loaded into the QL to the given
channel (default #1). Five pieces of information are given: jobnumber
(job), tag, owner, priority and jobname

JobNumber / Tag
    The jobnumber and the jobtag are internally combined to form the job-ID
    (jobnumber+tag\*2^16) in order to identify jobs.

Owner
    The Owner of a job is not necessarily the job which started it nor must
    it be connected with it. If a job is removed, all jobs owned by it will
    disappear too.

Priority
    The higher the Priority of a job, the more processor time is given to it
    and therefore the faster it runs.

    An "s" in front of the priority means
    that the job is currently suspended, so the priority does not matter.

Jobname
    The jobname is another method of identifying the job, being the name
    given to the job when it was programmed.

**NOTE 1**

If the second syntax does not work, you should update your Toolkit
version.

**NOTE 2**

Minerva users will be dismayed to learn that current versions of this
command do not display negative priorities.

**CROSS-REFERENCE**

Commands like :ref:`rjob`,
:ref:`spjob`, :ref:`rel-job`,
:ref:`job-name`
and :ref:`sjob` change job settings;
:ref:`job-dlr`, :ref:`ojob`,
:ref:`nxjob`, :ref:`pjob` return
the same information as appears on the :ref:`jobs`
list for single jobs. :ref:`list-tasks` is
similar.