Re: Batch jobs performance problems

[DAsmussen@xxxxxxx]

Luc,

In a message dated 4/6/99 6:33:01 AM Eastern Daylight Time, 
LDEBONDT@am.pnu.com writes:

<<snip>>
>      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.
<<snip>>

Not all BPCS jobs must be run in a single threaded JOBQ.  I could by no means 
offer a definitive list, as it would vary by installed options, 
modifications, and release levels.  However, my current primary client runs 
everything except MRP/CAP generation in multi-threaded JOBQs.  The rule of 
thumb would be to test in a seperate environment and see what works and what 
doesn't.  Anything with a suffix of 200 should be pretty safe...

HTH,

Dean Asmussen
Enterprise Systems Consulting, Inc.
Fuquay-Varina, NC  USA
E-mail:  DAsmussen@aol.com

"The greatest joy in life is doing what others say you cannot do." -- Walter 
Bagehot
+---
| 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
+---