Due to the facility of folder mapping on the iSeries, users merrily dump their PC files (in fact, at times, a full PC backup) on the iSeries folders (in QDLS). It is an administrator's nightmare tracing such files. Here's how life can be made simpler. On a daily basis, schedule the following command to run on the system:
DSPOBJD OBJ(QDOC/*ALL) OBJTYPE(*ALL) OUTPUT(*OUTFILE) OUTFILE(lib-name/file-name)
This will create information about all the of the files in your QDLS file-system in an outfile. Run a query on this outfile, sorting the objects in the descending order of their sizes. The output of this query will give you the major culprits in a glance (say, the top 10 files with large sizes).
However, the file-names will be in the *SYSOBJNAM format ( viz. PPSN080338, PPSN176554 etc. ). To translate these to the actual DOS file format, use the following command: DSPDLONAM DLO(*SYSOBJNAM) SYSOBJNAM(PPSN080338)
In the above example, replace the 'PPSN0...'entry with the relevant names as per your list. The output of this command will clearly identify which folder files are taking up large disk space and causing the system ASP (generally) to bloat up.
The output is as follows:
Document library object . . . . . : AP.PPT Folder . . . . . . . . . . . . . : TMP/S Document identifier . . . . . . . : 20021 0080338S44C LADN timestamp . . . . . . . . . . : 07D20C0F0A080326 System object name . . . . . . . . : PPSN080338 Object class . . . . . . . . . . . : *DOC Auxiliary storage pool ID . . . . : 1 Object overflowed . . . . . . . : N
MORE INFORMATION ON THIS TOPIC
The Best Web Links: Tips, tutorials and more.
Ask your systems management questions--or help out your peers by answering them--in our live discussion forums.
Read this Search400.com Featured Topic: Managing your iSeries.
Ask the Experts yourself: Our systems management gurus are waiting to answer your technical questions.