Several very good points made below - but there are still times when you want to use batch mode and 
CS together -  we have several jobs that logon every hour to tidy up some parts of the database 
- we want them to run as quickly as possible to release the database back to the users

However, do check your system as suggested below - also look for the less obvious - I've 
written programs that work fine for ages until the data built up and then they suddenly went 
into data access overdrive. Check in Glance for any CPU hogs or impedes or any process 
hogging masses of memory.  And, to be really sure, why not try a reboot - this might clear
some corrupt system table causing allocation problems etc... 

>>> "Schlosser, Robert (Contractor)" <[log in to unmask]> 01/09/99 >>>
Steve

        A question or two about your environment -

        How many online users do you currently have and has this number
increased recently?
        How many batch jobs are executing at one time beyond jobs like SLEEPER?
        Have you recently added new code that references the same data?
        Is the data that the online users and batch jobs reference in a
TurboImage database, an Allbase set of tables?

        You will generally achieve the best batch performance with one active
batch job at a time. If you are now experiencing a slow down in batch processing
and nothing has changed recently, then you may want to see if some database
locks are being held longer than they need be. Finally, do you really want your
batch jobs to compete on an equal footing with your online users?

        To answer you question - use the JOBPRI command to set the maxjobpri to
CS.

Bob Schlosser
(407) 727-5893

        -----Original Message-----
        From:   Steve Hammond [SMTP:[log in to unmask]] 
        Sent:   Wednesday, September 01, 1999 10:50
        To:     [log in to unmask] 
        Subject:        Performance question

        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