|
Hi Rob, I thnk that much of your questin can be answered in OGS Online databases or documentation. 1. The Net Changes for 6.1.00 show that "COM" does not exist in 6.1.01. This was replaced by a thin client Order Entry. The term 'COM' specifically refers to an older 'fat client' implementation which was in 6002 and 6004. The details of the changes are listed in the Net Change document, available on OGS. 2. Searching the BMRs for 'Parallel' shows several things, basically that the Parallel options do nothing in the new Order Entry interface. Parallel processing options were left on the screens, but a BMR 51998 exists to ask they be removed. They affect nothing. You can obtain BMR 55960 to update your help text for this panel so that it says that the options do not work. Two open Enhancement request E BMRs 51187 and 43094 asks that the options which used to exist for COM be used to do parallel for different functions instead, to improve performance. 3. Check out the ORDERPOST job description. I believe this may be the one which has QINTER listed on it and this job description is used when posting orders is set to BATCH. You can use this to set up another job queue to direct those jobs to. 4. There is a BMR to disallow the following combination in the User Preferences for Order Entry: Processing preferences: Post Mode 1 (0=Interactive, 1=Batch, 2=Parallel) Print Mode 1 (0=Interactive, 1=Batch) You should set Print Mode to Interactive if your Post Mode is set to batch. This is to avoid a 2nd batch job getting submitted to do the printing. The 2nd job does not get submitted with the name of the workstation, so this results in a bug that the Workstation data area is not used to set the proper output queue for printing, and it will use the system default printer in the SSASYS data area instead. The BMR is 56772 and would have to be escalated. 5. If you use Promotions and Deals heavily, there is an outstanding performance BMR regarding the coding of the declaration of the LINEP cursor in the PRO770B program. A change to the SQL statement plus one logical is required to make this run much faster. The BMR is 56177. I suggest you contact Helpline regarding this BMR and escalating it or obtaining the workaround. If you have ADK, you can correct this statement yourself and create the logical until the BMR is completed. Hope this helps. If not, then I suggest you run some DBMON to document the issue more thoroughly and open a call with the Helpline. Thanks Genyphyr Novak SSA Global Technologies ----- Original Message ----- From: "Rob Stagis" <stagis@fansteelvrwesson.com> To: <BPCS-L@midrange.com> Sent: Thursday, November 30, 2000 3:38 PM Subject: RE: Performance > 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? > > -----Original Message----- > From: owner-bpcs-l@midrange.com [mailto:owner-bpcs-l@midrange.com]On > Behalf Of MacWheel99@aol.com > Sent: Thursday, November 30, 2000 3:18 PM > To: BPCS-L@midrange.com > Subject: Re: Performance > > > > They're submitted to QINTER cuz that was the BPCS default. I can't for > the > > life of me find the parameter that'll change 'em to another job queue. > The > > machine has enough steam to handle it, but there is a noticeable > performance > > hit. > > That is not the BPCS default for 405 CD so someone has modified rules in the > interim. Take a look at WRKJOBQ & see what subsystems various JOBQ are in & > if you can reassign some. I have never done this. I just go into WRKSBMJOB > & move a job that has not yet started to a different JOBQ. > > Check the SSALOG00 on-line BPCS documentation on your environment setup. > > There is stuff off the SYS menu that says which JOBD & *DTAARA stores info > for BPCS interactive vs. batch rules & reviews IBM commands needed for > maintaining them. So if you know which of your JOBQ are in a batch sub > system, these tools will help you change defaults so that BPCS JOBQ work > does > not default to QINTER. > > You might also look into the IBM Redbook specifically on optimizing your 400 > for BPCS performance. > > MacWheel99@aol.com (Alister Wm Macintyre) (Al Mac) > AS/400 Data Manager & Programmer for BPCS 405 CD Rel-02 mixed mode (twinax > interactive & batch) @ http://www.cen-elec.com Central Industries of > Indiana--->Quality manufacturer of wire harnesses and electrical > sub-assemblies - fax # 812-424-6838 > > +--- > | 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.