Batch jobs performance problems

     We are live with V6.0.04 C/S since january the 4th and during the last 
     couple of weeks we are having a serious problem with batch jobs 
     performance due to queuing in the BPCS job queue.
     
     Since all BPCS jobs should be processed in one, single threaded job 
     queue (apart from the orderpost en the ceapost job queues), it only 
     takes one large job to block the entire queue.  As a consequence, 
     people are waiting more than 30 minutes to several hours for a job 
     that takes only 15 seconds to process, because one or several other 
     long running jobs are blocking the job queue.
     
     We would like to run the jobs in different job queues, running as many 
     jobs in parallel as possible.  However, this is not without risk and 
     SSA don't know which jobs can be directed to another queue and still 
     ensuring that dependency between jobs is preserved as well as data 
     integrity is preserved.
     The only jobs that can be directed to another queue are jobs having a 
     '1' or '2' in the fourth position of the program name.  But these are 
     not the kind of jobs that are most heavily used.
     
     Typical jobs that block the job queue are BIL501B, CLD501B, CEA520B, 
     CST940B, but there are others.
     
     Anyone experiencing the same problem ?  Anyone having a clue ?
     
     
     Luc De Bondt
     Systems coordinator.
+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com
+---