|
I don't know if they're running CFG390 - I'll check. This shop is kind of a unique place - every order is a 'special' or one-time order. As in most companies, once things settle down after a conversion and become routine, the users stop concentrating on the system. In this case, they're not bothering to look at the last time this 'special' item was ordered - they get into the pattern of allowing the configurator to quote every item every time... I'll see if they're running it and get back to the list. Thanks for your information :) -----Original Message----- From: owner-bpcs-l@midrange.com [mailto:owner-bpcs-l@midrange.com]On Behalf Of Chick Doe Sent: Thursday, November 30, 2000 1:35 PM To: BPCS-L@midrange.com Subject: Re: Performance here's a couple of comments that we have learned. we allow only one active job in the QINTER job queue. this is where the ORD701B and CFG640B jobs (some of them) run. there are a couple of reasons for this. one is to insure that the ORD701B job actually completes before any of the CFG640B jobs that is submits start to process. the second reason is to insure that only one CFG640B job runs at a time. the last step of the CFG640B job is a cost roll-up. if you process an order with multiple configured lines, and these lines are for similar products, you could get two cost roll-ups running at the same time for related products and that is an open invitation to create duplicate cost records in the CMF file. can you answer a question for me? when you perform a reconfiguration using CFG390, where does that CFG640B job run. in our system (V6.04) the CFG640B jobs that get submitted via CFG390 run in the QBATCH job queue. this is the job queue that the interactive bpcs program submit jobs to. on our system QBATCH can run multiple jobs. thus it is possible for multiple CFG640B jobs to be running simultaneously, either multiple jobs in QBATCH (via CFG390) or one in QBATCH and on in QINTER (via ORD701B). either way, this invites corruption of the CMF file. i have asked SSA why this is and cannot get an answer. we will be converting to 6.1.01 soon. does these problems still exist or has SSA addressed them? chick doe barton instrument systems >>> stagis@fansteelvrwesson.com 11/30/00 08:29AM >>> BPCS V6.1.01, OS/400 V4R4 current cum packs, I guess. To all: On panel ORD820D-06 (Order Parameters) - how do the parallel validation and posting parameters affect system performance? I'm still having issues with this box. If a user posts a large (like 25 line) order or a couple users are trying to post orders at the same time, the WRKSYSSTS display will show act-to-wait numbers that can range over 100,000. With the system usually running around 50-100 in that column, it's quite shocking to watch it 'burp' that high. I have a commensurate lag in performance during the time the orders are posting. With the configurator CFG640B and Order Post ORD701B programs being submitted to a job queue that feeds QINTER, I can all of a sudden show a dozen or more CFG640B's and ORD701B's either in an active or LCKW state. What do I do? -----Original Message----- From: owner-bpcs-l@midrange.com [mailto:owner-bpcs-l@midrange.com]On Behalf Of Devin Bowen Sent: Wednesday, November 29, 2000 10:41 PM To: BPCS-L@midrange.com Subject: RE: Converting from 4.05 CD to 6.1.01 all net change docs for your task are on OGS online. you will need to get docs for 6.0.02, 6.0.02 to 6.0.04, 6.0.04 to 6.1 (sounds like you have this one). code tables are kept in ZCC. most will be hard to populate intelligently until you do analysis on what has changed in terms of how you will use the new BPCS (this knowledge will likely come out of your prototyping and conference room pilot of eBPCS). Think of it as a new ERP implementation with easily converted data and you'll do fine. Devin -----Original Message----- From: owner-bpcs-l@midrange.com [mailto:owner-bpcs-l@midrange.com]On Behalf Of Roger.Henady@thorco.com Sent: Wednesday, November 08, 2000 1:44 PM To: BPCS-L@midrange.com Subject: Converting from 4.05 CD to 6.1.01 Does anyone know of a list of new fields / files since 4.05 that are required to be populated? With the 6.1 CD Doc., there was a net change spread sheet listing the new fields between 6.04 and 6.1. There is also a CODE MASTER TABLE maintenance. Do you know what files this is updating? We thought we could write programs to populate these files. EX. planning codes, country codes, routes, etc........ Thanks for your help Roger +--- | 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 +--- +--- | 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 +--- +--- | 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.