qstat reports urgency slots rather than real/range value

[wish]

If you set the urgency slots of a pe to a constant then a normal 'no flags' qstat will report that as the number of slots a job requesting the job requires:
wish@iseisd-ws113:~$ qstat|tail -n +3 |awk '{print $1}'|xargs -n 1 qstat -j '{}' |grep '^{parallel';qstat
parallel environment: smp range: 2
parallel environment: smp range: 2
parallel environment: smp range: 4
parallel environment: smp range: 4
parallel environment: smp range: 2-4
parallel environment: smp range: 2,3
job-ID prior name user state submit/start at queue slots ja-task-ID}

---

10 0.42045 fellow wish r 03/26/2013 09:13:40 all.q@… 2
13 0.41629 fellow wish r 03/26/2013 09:21:55 all.q@… 2

9 0.75000 fellow wish qw 03/26/2013 09:08:27 4

11 0.74968 fellow wish qw 03/26/2013 09:08:34 4
12 0.25536 fellow wish qw 03/26/2013 09:08:40 1
14 0.25000 fellow wish qw 03/26/2013 09:10:37 1

[dlove]

If you set the urgency slots of a pe to a constant then a normal 'no
flags' qstat will report that as the number of slots a job requesting the
job requires:

I don't see a good reason to change the documented behaviour. Feel free
to re-open if there really is one.