RE: IFS dir size, hard links only

' you have to map a network drive to the root directory of the system'

OMG, don't ever do that! That's an epic security no-no.



-----Original Message-----
From: Musselman, Paul [mailto:pmusselman@xxxxxxxxxxxxxxxx]
Sent: Tuesday, August 21, 2018 3:24 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: RE: IFS dir size, hard links only

We sometimes use "Tree Size." It's a PC-based program; you have to map a network drive to the root directory of the system and let it run... so it's not as fast as some other solutions. But it works relatively smoothly.

You need to omit some directories when using TREESIZE that are obnoxious--

QSYS.LIB
QNTC
QFILESVR.LIB
QNETWARE
QOPT
QFILESVR.400
QOPENSYS

PS-- I know you didn't mention backups, but use ASYNCBRING while saving the IFS. It makes the save 'read ahead.' Big issue with saves (of any sort) is the number of objects. My partner in crime found an IFS directory about 1 Gig in size with over 1,000,000 objects. Clearing them out saved over 3 hours of backup time!

Paul E Musselman
PaulMmn@xxxxxxxxxxxxx<mailto:PaulMmn@xxxxxxxxxxxxx>