|
Thanks for your response. We will probably do as others on the list suggested and just replace IMHIST with a physical file of just the records we want to keep. We probably generate two or three million inventory transactions a year and need an easier way to purge. Perhaps it was the COM history, and not the IM trans history that our manager (no longer here), took 3 days to purge before out upgrade to 5.5 in May of 2000. All I know is that he needed a huge window for our 620 with 94g DASD and 1g of memory. You can be sure I will be real careful about specifying IHNEW! Bryan Burns AS/400 System Operator ECHO Incorporated 847-540-8400 ext. 493 <Burnsbm@echoincorporated.com <mailto:Burnsbm@echoincorporated.com> > -----Original Message----- From: Rusty Jackson [SMTP:rustyjackson@ntown.com] Sent: Friday, August 10, 2001 12:51 PM To: mapics-l@midrange.com Subject: RE: Questions on on purging IMHIST Hello: I am an independent consultant that works with quite a several mid-sized to large MAPICS accounts. Here are the answers to your questions: 1. I have NEVER know anyone that I work with to print a transaction history report of what they are going to purge nor print the optional list during the purge. Unless you just want to get rid of a LOT of paper, I would definitely suggest not to do it. If for some reason you ever need to get back at the transactions, you can use the Restore Transaction History option and restored the required history file to IMHGEN. 2. Obviously, the size of your machine as well as how much history is being purged dictates the time required. I have never seen an IM archive take more than several hours HOWEVER most of the systems have been mid-sized AS/400s and usually the number of records involved is not 8 million! COM however is a different story as far as long times! 3. You are right, this is not a dedicated mode function. 4. You will be okay if you perform a clear on the IMHNEW member in IMHIST. BE SURE TO SPECIFY THE MEMBER OF IMHNEW! i.e.,: CLRPFM AMFLIB?/IMHIST MBR(IMHNEW) Rusty Jackson Rusty Jackson & Associates Knoxville, TN rustyjackson@ntown.com >===== Original Message From mapics-l@midrange.com ===== >Hello All, > >We are running XA5.5 and I need some help with IMHIST. It has more than 8 >million records and is due for a purge. I have the following questions: > >1) The MAPICS documentation says to run a transaction history report >before a purge, but with 8 million records, how long would that take and how >much DASD would it use? How necessary is this report? > >2) I have been told the purge will have to be done on a three day >weekend as it will take 50 hours or more. Any tips on speeding the purge >up? > >3) If the purge is not finished when the work shift begins, I assume >that IM transactions will be locked out. What other parts of MAPICS would >be locked? This is not a dedicated mode task from what I can see. > >4) The IMHIST file has a member IMHNEW with 1.3 million records. The >MAPICS web site has indicated that IHNEW is built on the fly for >Transaction History reports. A DSPFD indicates IMHNEW was last changed on >7/11/01. We think that it got created but not cleared on that date when we >abended a transaction history report that had no limits. Can we just do a >clear it with a CLRPFM? > >Thanks for any help. > > Bryan Burns > AS/400 System Operator > ECHO Incorporated > 847-540-8400 ext. 493 ><Burnsbm@echoincorporated.com <mailto:Burnsbm@echoincorporated.com> > > >_______________________________________________ >Mapics-L mailing list >Mapics-L@midrange.com >http://lists.midrange.com/cgi-bin/listinfo/mapics-l _______________________________________________ Mapics-L mailing list Mapics-L@midrange.com http://lists.midrange.com/cgi-bin/listinfo/mapics-l
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.