Before altering job priorities and queues may I suggest you spend a little
time and attempt to identify the source of the performance bottleneck.

If you determine your batch jobs simply aren't getting enough CPU, and you
haven't access to Glance and it's Work Group process management
capability... you might consider tuning your D queue to overlap the C queue
and set the D queue to oscillate while the C queue decays.

To illustrate... (I've forgotten the normal priority numbers)  If the C
queue is currently set to priority range 150 - 200 and the D queue is set to
range 210 - 250 a potential solution is to change the D queue range to
175-250 and have it oscillate while the C queue decays.

When a process is introduced to the C queue it will start at priority 150
then work it's way down the scale to 200.  In decay mode, the process, if it
runs long enough, will remain at priority 200.

When a process is introduced to the D queue it would start at priority 175
then work it's way down the scall to 250.  In oscillate mode, when the
priority hits 250 it would then be reset to priority 175 and cycle it's way
back down to 250.  This would continue until the process completed.

Please beware, this may not be suitable for your environment and would
negatively impact any online process of a lengthy duration.  The net effect
should be... your batch processes will get more CPU, short online tasks will
be unaffected, BUT... longer online tasks will now require more time to
complete.

Another trick to consider... define the E queue to be a subset of the C
queue priority range and place your 'special' jobs in the E queue.

YMMV... and your results may not be to everyones benefit.

Good Luck,
Jim Alton
[log in to unmask]
eSystem Solutions

Steve Hammond wrote in message ...
I am running a 987 with over a gig of memory.

I have some users who have lately seen a degradation of performance on jobs
running during the day. They would like their jobs to run in the C queue.

I know I can put ";pri=CS" in their job card, but I can't remember if there
is anythig else I need to do to allow jobs to run in the C queue.

Also is there anything different I can do to allow the jobs to run in the C
queue, in particular, anything like th TUNE command that targets specific
jobs and moves them to the C queu when they start up?

thx
steve hammond
aamc
wash dc