|
Thanks, Peter...I'll look it up. -----Original Message----- From: owner-bpcs-l@midrange.com [mailto:owner-bpcs-l@midrange.com]On Behalf Of pgreenfi@ssax.com Sent: Thursday, November 30, 2000 5:59 PM To: BPCS-L@midrange.com Subject: RE: Performance Rob, See the Red Book "Implementing SSA's eBPCS on the AS/400" Chapter 11.6.3.3. regards, Peter I hope I didn't say 4.05CD. This is running COM on V6.1.01. What I've found is that every job description and workstation data area points to QBATCH. All reports, etc., are running in there. The problem is that the posting and validation programs are being submitted to jobq QINTER. I've gotta find how to change the name of the jobq that they're being submitted to. The recommendation that I move the BPCSJOBQ from QINTER sbs to QBATCH sbs won't work because it's actually using jobq QINTER...did that make sense? All my system parameters point to QBATCH. For some reason, these programs are being submitted to QINTER. The user's screen is clear and he/she is free to enter another order, but the order that they just posted won't be 'valid' for a couple moments while it's being processed. Does that make more sense? +--- | 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 +--- +--- | 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 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.