|
This is an AS/400 feature. Won't work on Unix. "Nick Smith" <nick.smith@powerbar.com> on 98/11/18 10:15:00 AM Please respond to BPCS-L@midrange.com To: BPCS-L@midrange.com cc: (bcc: Deb Marabotti/SSA/US) Subject: RE: Poor Performance in INV900 How exactly are you able to do this? Can you provide more details on the process? BPCS-L@midrange.com on 11/18/98 06:34:00 AM To: BPCS-L@midrange.com cc: (bcc: Nick Smith/Powerfood) Subject: RE: Poor Performance in INV900 From: BPCS-L@midrange.com Date: Wed, Nov 18, 1998 6:34 AM Subject: RE: Poor Performance in INV900 To: 'BPCS-L@midrange.com' One thing I have been experimenting on to improve performance is to set the all the logical files except the one's being used by INV900 to REBLD(*YES) at the beginning of the procedure and at the end of the procedure setting them back to REBLD(*IMMED). That way it does not have to update the indexes of all the logical files over the ITH file while it runs. Another thing that can be done is move the ITH purge to a separate program that can run when time is available - like the next weekend. Best Regards, Roger Wolf > -----Original Message----- > From: Michael Ozanne [SMTP:mozanne@midori-no-ryu.demon.co.uk] > Sent: Tuesday, November 17, 1998 6:47 PM > To: BPCS-L@midrange.com > Subject: Re: Poor Performance in INV900 > > In message <912f9aa8.3651ef07@aol.com>, Devinbowen@aol.com writes > >Does anyone know if INV900 is stricken with the same inefficient SQL > >statement(s) as ACR900 (earlier messages)? We are in prototyping and are > >experiencing the same kind of poor performance in the inventory month-end > >close as was described for ACR900. We're on v6.0.02 (HP Oracle). Any > >specifics anyone can give on a fix would be appreciated. > > INV900 has always been a dog, ITH is usually the biggest file in the > database, INV900 purges old records from ITH then re-indexes it and all > its 30 plus logical views. > > -- > Michael Ozanne (Also ozannem@pacific.co.uk) > +--- > | 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 > +--- ---------- Received: from KITTEN.MCS.com by pearl.fabrik.com with ESMTP (Fabrik F07.3-000) id SINN.5009145@pearl.fabrik.com ; Wed, 18 Nov 1998 07:40:27 -0800 Received: from uucphost.mcs.net (Uucp1.mcs.net [192.160.127.93]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id JAA06480; Wed, 18 Nov 1998 09:39:41 -0600 (CST) Received: (from uucp@localhost) by uucphost.mcs.net (8.8.8/8.8.8) id JAA29677; Wed, 18 Nov 1998 09:39:40 -0600 (CST) Received: (from majordom@localhost) by midrange.com (8.9.1/8.9.1) id JAA17685 for bpcs-l-outgoing; Wed, 18 Nov 1998 09:16:55 -0600 Received: (from uucp@localhost) by midrange.com (8.9.1/8.9.1) with UUCP id JAA17324 for BPCS-L@midrange.com; Wed, 18 Nov 1998 09:02:53 -0600 Received: from dresden.garmin.com (dresden.garmin.com [208.196.167.131]) by uucphost.mcs.net (8.8.8/8.8.8) with ESMTP id IAA24034 for <BPCS-L@midrange.com>; Wed, 18 Nov 1998 08:34:02 -0600 (CST) Received: from dresden.garmin.com (root@localhost) by dresden.garmin.com with ESMTP id IAA28449 for <BPCS-L@midrange.com>; Wed, 18 Nov 1998 08:27:12 -0600 (CST) Received: from dallas.garmin.com ([10.1.0.44]) by dresden.garmin.com with ESMTP id IAA28432 for <BPCS-L@midrange.com>; Wed, 18 Nov 1998 08:26:52 -0600 (CST) Received: by DALLAS with Internet Mail Service (5.5.2232.9) id <W83DX1SD>; Wed, 18 Nov 1998 08:34:04 -0600 Message-ID: <71471DFD03A7D11191E000600852EC6FD4313A@DALLAS> From: "Wolf, Roger" <Roger.Wolf@garmin.com> To: "'BPCS-L@midrange.com'" <BPCS-L@midrange.com> Subject: RE: Poor Performance in INV900 Date: Wed, 18 Nov 1998 08:34:00 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BE1300.7D62B060" Sender: owner-bpcs-l@midrange.com Precedence: bulk Reply-To: BPCS-L@midrange.com X-List-Name: BPCS Users Mailing List (BPCS-L@midrange.com) ---------- Content-Type: text/plain ---------- Content-Type: text/html Content-Transfer-Encoding: quoted-printable ----------Title: RE: Poor Performance in INV900
One thing I have been experimenting on to improve performance is to set the all the logical files except the one's being used by INV900 to REBLD(*YES) at the beginning of the procedure and at the end of the procedure setting them back to REBLD(*IMMED). That way it does not have to update the indexes of all the logical files over the ITH file while it runs.
Another thing that can be done is move the ITH purge to a separate program that can run when time is available - like the next weekend.
Best Regards,
Roger Wolf
-----Original Message-----
From: Michael Ozanne [SMTP:mozanne@midori-no-ryu.demon.co.uk]
Sent: Tuesday, November 17, 1998 6:47 PM
To: BPCS-L@midrange.com
Subject: Re: Poor Performance in INV900
In message <912f9aa8.3651ef07@aol.com>, Devinbowen@aol.com writes
>Does anyone know if INV900 is stricken with the same inefficient SQL
>statement(s) as ACR900 (earlier messages)? We are in prototyping and are
>experiencing the same kind of poor performance in the inventory month-end
>close as was described for ACR900. We're on v6.0.02 (HP Oracle). Any
>specifics anyone can give on a fix would be appreciated.
INV900 has always been a dog, ITH is usually the biggest file in the
database, INV900 purges old records from ITH then re-indexes it and all
its 30 plus logical views.
--
Michael Ozanne (Also ozannem@pacific.co.uk)
+---
| 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.