[Moabusers] QOSCFG OMAXJWC with USERCFG QLIST and MAX.WCLIMIT

[Michael Santos]

Hi,

	I get a strange difference of behavior when using the following two  
policies.

Policy 1:

USERCFG[msantos] QLIST=qos1,qos2 MAX.WCLIMIT=8:00:00
QOSCFG[qos1]
QOSCFG[qos2]         OMAXJWC=10:00:00

Policy 2:
USERCFG[msantos] QLIST=qos2,qos1 MAX.WCLIMIT=8:00:00
QOSCFG[qos1]
QOSCFG[qos2]         OMAXJWC=10:00:00

(The only difference is the ordering of QLIST's arguments.)

	Under each policy user msantos submits two jobs, each asking for  
9:00:00 of wallclock, like so:

msub -l qos=qos1 nine-hour-job.pbs
msub -l qos=qos2 nine-hour-job.pbs

Under policy 1, both job submissions get rejected with the same error:

ERROR:    cannot submit job - wclimit too high for user  
'msantos' (32400 > 28800)

Under policy 2, both job submissions are accepted, the qos1 job is  
blocked, and the qos2 job is run.

	Policy 2 gives the behavior I expected; policy 1 does not.  I  
understand that the ordering of QoSs in QLIST affects the default QoS  
assigned to the jobs of user msantos; however, in both cases I  
explicitly specified the QoS on the command line.

	Is this a bug, or expected behavior?  If expected behavior, I don't  
think it is documented in the Admin's Guide (at least in Section  
7.3.2.3, where I would have expected it).

	Thank you.

Best regards,
Michael Santos
Space Telescope Science Institute