|
Things to be careful of are symbolic links, etc. There are a lot of these. You want to ensure that you are reporting the space of the symbolic link and not the object it references. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 08/19/2003 03:38 PM Please respond to Midrange Systems Technical Discussion To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> cc: Fax to: Subject: Re: IFS Space Utilization Report? There's always PASE - call qp2term. 'df' is not there - probably not very meaningful on a 400, if I remember what it does. 'du' IS there, and the same redirection options are there, of course. 'du -a' resulted in the following (all files in all subdirectories) - numbers on the left are the number of 512-byte blocks. 'du -ak' would list 1024-byte blocks: 13312 /tmp/brms/flightrec 16 /tmp/brms/install 20480 /tmp/brms/flightrec.bku 33824 /tmp/brms 8 /tmp/.NOTESMEM_please_do_not_remove.f8000000.SEMLOCK 8 /tmp/.NOTESMEM_please_do_not_remove.f8fa0000.SEMLOCK 8 /tmp/s.slapd 8 /tmp/QACX6QF13F 8 /tmp/QACX5P2HCT 8 /tmp/QACXCSSVSH 16 /tmp/fault_recovery.log.FLASH 8 /tmp/QACXHZNZBM 8 /tmp/QACXDT3H18 8 /tmp/QACXFZKCW2 1024 /tmp/QACX3D1TSM 1024 /tmp/QACXKFTKGS 1280 /tmp/test/testver.iso etc. It looks like one could run a shell script using QP2SHELL, right? So this could also be automated. I redirected this to a physical file - see previous post - and it used CCSID 819. I see there is an API that lets you specify the CCSID. Cool! Vern At 01:50 PM 8/19/2003 -0600, you wrote: >Nathan M. Andelin wrote: >>What is the best way to monitor utilization of the IFS root file system? Is >>a report available, listing stream files and the amount of disk space they >>use? > >Typically tools like 'df' and 'du' tell how disk is being used. I just >tried running those commands in QSH on my V5R2 system and unfortunately >they aren't there. > >James Rich _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-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.