Comments on: Searching out and eliminating unuse files on AS/400

By: slack400

slack400 — Thu, 11 Dec 2008 18:15:43 +0000

Hit up Vision Solutions for the SATLITE tool. (it’s free)
It will scan and assess the size, use frequency of all the objects on your system.
And it will generate some user friendly reports to show you what your most active objects are.
It will also help you assess your data replication needs if you ever decide to implement High Availability.

You’ll still need to scan your code base for these file names before moving.
I agree with Gilly400, you’ll want to move the objects first.

Don’t delete until you’re certain they’re not needed.
You’ll need keep them around for Monthend and possibly yearend to ensure you don’t have any applications that still need them.

By: reg

reg — Wed, 10 Dec 2008 20:47:52 +0000

I have a developed a utility we use periodically that uses DSPOBJD across a library or whole system (your choice) that lists by library, all files (PFs & SAVFs) over 1 meg in size and over 6 months old. You can change those parameters if you wish in the code. It lists size, create date, last used date & owner.
Will send it to you free of charge if you’re interested. roger.stein@swansonhealth.com

By: philpl1jb

philpl1jb — Wed, 10 Dec 2008 15:59:33 +0000

When I did this on one system I discovered files with thousands of members.
Focusing on those, it turned out that they were all temporary — used typically within 5 minutes of creation. I wrote a CL to delete any that were over a month old. Scheduled as part of the monthly cleanup processes.

What about deleted records..some of your files may need to be reorganized.

By: gilly400

gilly400 — Wed, 10 Dec 2008 10:58:40 +0000

Hi,

I would suggest checking the last used and last updated dates on the files and members and moving the suspectedly unused files to another library on the production machine (and keeping the files there for a year). If you have problems in your application, because a file is not found, you can then move the file back and give the program a retry.

Not a perfect solution, but it should help.

Regards,

Martin Gilbert.