|
Hello, Not sure if this will help, but there is a performance BMR on OGS for INV300 in 6004 (check to see if the same thing works for 6002, it may or may not). If this doesn't help, I suggest analyzing with DBMON. The Optimizer on the AS/400 will change the way it accesses your data based upon many factors, with file size changes causing it to reconsider what it is doing. If your ITH file has been growing, the optimizer may have choosen a different way to access the data, which in this case was not the best choice (but because of missing logicals, the optimizer may have made the best 'guess' it could - it uses logicals to get lots of information to make the access plans). At any rate, here is one suggested BMR to follow, which lists a workaround of some logicals to build. I analyzed this and wrote the BMR some time ago, so not sure if the code has changed since then. If building these logicals doesn't help, then don't keep them on the system. At that point you may want to run a DBMON analysis yourself or phone into SSA's AS/400 Helpline to have them assist you to see if a new BMR should be written. Thanks Genyphyr Novak SSA BMR Number: 49552 Priority Code: D Version Reported: 6004 Platform Reported: AS400 Program: INV300 Origin Code: E Completed Date: 00-00-00 Rejected Date: 00-00-00 Rejected Reason: INV300 Slow performance INV300 ( Material Status Inquiry )is not finishing. Analysis with DBMON shows in INV300D, the DECLARE for ITH1 cursor is not using ITHL01 as expected. It is instead using ITHL18 for the Select/Omit criteria, and does a subquery off that. The subquery takes excessive CPU with large ITH files. Also, program SYS020B in the same job stream changed under MR 39012, and this added a statement for which no good logical exists. Client copied ITHL01 and added SELECT for THNII NE '1', and one more key by TTDTE. Made TPROD and TSEQ DESCENDING also. Added logical over HPO with SELECT PID, HOUTS and PONIIT and keyed by PPROD, PWHSE and POFAC. Response time went to 1-2 seconds. -----Original Message----- From: Mark Bazer <mbazer@dynomerch.com> To: BPCS-L@midrange.com <BPCS-L@midrange.com> Date: Friday, June 23, 2000 12:37 PM Subject: RE: INV300 History Delay >Did you recently do an OS upgrade or make some other change? In any event, >look at the file description for ITHL01 and check the setting for access >path maintenance. We once had the setting changed to *REBLD for some reason, >and every time the file was accessed the index had to be rebuilt. We >normally have most logical files set at *IMMED, so the access path is >maintained as file changes occur. > >Mark Bazer >Dyno Merchandise >Pompano Beach, FL > > > -----Original Message----- >From: Staunton,Wade [mailto:WStaunton@burco.com] >Sent: Friday, June 23, 2000 11:17 AM >To: 'bpcs-l@midrange.com' >Subject: INV300 History Delay > >We are running v602 MM on the AS/400 v4r4. Just in the last week or so we >have experienced a very long delay when trying to get the history of an item >when in INV300. Each new item that we search for has the delay. Does >anyone have an idea as to what may have happened? What file could the >problem be in and what could the problem be? >This problem has just began and no changes have been made to the BPCS >configuration. > >Thanks in advance for any assistance you can give. > >Wade Staunton >Burlington Chemical Company >Burlington, NC +--- | 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-2025 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.