job_ptr is really the already existing job_ptr minus the task that was
just scheduled.

job_ptr's db_index was reset.

Make "srun --gres=none ..." work when executed without a job allocation
(i.e. srun creates the allocation plus the step). Previous logic would
try to create the job with a gres value of "none".

Fix for possible error if job has GRES, but the step explicitly requests a
GRES count of zero.

BlueGene/Q's runjob command requires a fully qualified pathname,
so only for that machine type, resolve the name in srun. This
partitially reverts commit 57efc873
but only for BGQ systems.

Each node was logged loaded to the layouts table was being logged
using debug(), which produces a great number of messages with
minimal value. I changed the message to debug3() and moved it
in the code so it would not be generated when an error() message
is also generated.

If this failed previously, it would leave an open file descriptor
and pass that to spawned applications without logging anything.
However, test7.9 would fail.

bug 754

There was bad logic if an update was being performed on multiple tasks
of a job record resulting in a fatal error.

works for update, hold, release, suspend, resume, requeue and
requeuehold operations

confusion and wasn't ever handled in the allocation.  A user can now only
specify the option with srun.

Conflicts:
	src/sbatch/opt.c

and only caused confusion since the cpu_bind options mostly refer to a
step we opted to only allow srun to set them in future versions.

Defer job step initiation of required GRES are in use by other steps rather
than immediately returning an error.
bug 1056

without this change, slurmd would abort on reconfiguration

Prevent fatal error on "scontrol reconfig"