Details are earlier in this e-mail thread.
Wed Oct 11 8:00am:
Jobs that wouldn't finish before the scheduled maintenance
outage starts won't be able to start at all, until after the
scheduled maintenance outage has ended (planned for
Wed night at midnight).
Because, by this approach, such jobs can run for
the full wall clock time limit that they've requested.
So, if you want a job to run before the scheduled
maintenance outage begins, then in your batch scripts,
you might need to reduce the amount of wall clock
time limit you request.
(Once the maintenance period ends, this won't apply
any more.)
If you have jobs that you've already submitted that are
pending in the queue, then you might want to reduce
their requested wall clock time limit, to give them
a chance to start before the scheduled maintenance
outage begins.
The command is:
scontrol update JobId=######## TimeLimit=DD-HH:MM:SS
except REPLACE ######## with the job ID number, and
REPLACE DD-HH:MM:SS with 2-digit number of days,
2-digit number of hours (beyond the number of days),
2-digit number of minutes (beyond the days and hours)
and 2-digit number of seconds (beyond the days, hours
and minutes).
You have to pick a wall clock time limit short enough that
the job can run to its time limit before the start of the
scheduled maintenance outage.
For example, suppose job 123456 had requested 48 hours of
wall clock time limit, but now there are less than 48 hours
before the start of the scheduled maintenance outage.
So job 123456 won't be able to run until after the
scheduled maintenance outage ends.
But, we could change the requested wall clock time limit
for job 123456 to, for example, 30 hours, like this:
(but NOT A GUARANTEE) to run before the outage starts.