This code was originally put here to enforce checks to make sure jobs
didn't go over the limit.  If they didn't request the amount then we set
the limit and worked off that as if it were a request.

If we do this now we could get jobs deigned which would cancel the job at
submit with a very unrelated note as to why the job failed.

Since we now check this these limits after the node selection this isn't
needed.

In addition to accepting a job ID argument to the hold and release
commands also accept a job name (e.g. "scontrol hold my.bash")

Add a job's exit state (COMPLETED, FAILED, etc) and exit code to
email message
bug 737

Added job reason of "SchedTimeout" if the scheduler was not able to reach
the job to attempt scheduling it.

Added SchedulerParameter of batch_sched_delay to permit many batch jobs
to be submitted between each scheduling attempt to reduce overhead of
scheduling logic.

I plan to make this configurable soon

Set "Reason" field for all elements of a job array on short-circuited
scheduling for job arrays.
bug 748

Jobs dependent upon multiple other jobs may start prematurely, after
only some of the depdendencies are satisfied.
bug 746

Arguments of "abe" and "aeb" both failed.
bug 743

of limited non NPC jobs.

Advise user to specify network option at job allocation time on
Cray systems rather than within a job step.
bug 741

This reverts commit 3b676075.

b6bb8311

Fixed better way by only using the MAJOR and MINOR without MACRO in
the AC_INIT for version

This job option was removed long ago. Remove references to it
from our web pages.

If a job is submitted that is dependent upon a job array in which
the first task of that array is already purged from slurmctld, then
find another element of that array and properly handle the dependency.