× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re:Batch jobs performance problems
  • From: "Larry Fry"<lfry@xxxxxxxxxxx>
  • Date: Tue, 06 Apr 1999 08:32:54 -0500

A follow-up question to the "Batch jobs performance problems.

Is it documented anywhere that BPCS batch jobs should (or must) be run
single-thread, or is it "common knowledge/common sense with BPCS"?  We are a new
BPCS install and did not have the best guidance during the installation.  We do
not this and as far as I am aware the problems we have had that may be related
to this type of environment have are all been corrected by various BMRs.

On our old system, the operating system took care of file and reocrd locking by
specifications wihtin each batch job.  We could also make one or more files
unavailable to the on-line (interactive) users.  This would allow us to run
batch jobs in a controlled environment without impacting users more than was
necessary.  Not so with AS/400 & BPCS.

I have not been able to find anything in the limited documentation we have that
indicates this should (or must) be done.

Any advice would be helpful.

+---
| 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
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.