RE: Keeping old records on system in application files

["Jones, John (US)" <John.Jones@xxxxxxxxxxxxxxxxxxxxxxx>]

As I just mentioned in the file reorg thread, we just purged a bunch of
records from our account detail file.  We worked with the accountants
and determined that what was actively needed on a daily basis was 2 full
years + current year YTD (or, right now, 1/1/2002 through present).  All
prior transactions were moved to an Archive copy of the database on our
business continuity box.  The few who need detail that old are granted
IDs.  We plan on refreashing the archive annually with the next year's
transactions.

As to Cognos, we don't use it.  But if needed, we could do the update
more often to keep the archive db up to date.  Then let Cognos or
whatever query product work with it.

I should also note that with the account ledger purge in JDE, summary
records replace the detail records so the original info is not actually
purged; just summarized.

John A. Jones
Americas Security Officer
Jones Lang LaSalle, Inc.
V: +1-630-455-2787 F: +1-312-601-1782
John.Jones@xxxxxxxxxxxxxxxxxxxxxxx

-----Original Message-----
From: Mike Berman [mailto:mikeba777@xxxxxxxxx] 
Sent: Saturday, May 01, 2004 8:51 PM
To: Midrange-l@xxxxxxxxxxxx
Subject: Keeping old records on system in application files

I noticed that the Order Header file has records from 1995. Is there
really a need to keep this in  your apps and not move this to a
repository? Is this something that can be easier kept on say an idle 270
or on an Windows server? I am thinking in terms of a solution like
Cognos. Does the AS/400 have a solution that would be compatible with
Cognos? I am concerned that Cognos seems to be the industry standard, am
not sure to what extent decisions are made on 'what others might think'.

This email is for the use of the intended recipient(s) only.  If you have 
received this email in error, please notify the sender immediately and then 
delete it.  If you are not the intended recipient, you must not keep, use, 
disclose, copy or distribute this email without the author's prior permission.  
We have taken precautions to minimize the risk of transmitting software 
viruses, but we advise you to carry out your own virus checks on any attachment 
to this message.  We cannot accept liability for any loss or damage caused by 
software viruses.  The information contained in this communication may be 
confidential and may be subject to the attorney-client privilege. If you are 
the intended recipient and you do not wish to receive similar electronic 
messages from us in future then please respond to the sender to this effect.