On Mon, Jan 11, 2010 at 7:51 AM, Yoon-suk Cho <[email protected]> wrote:
> Thanks so much. Just now i solved this problem using by SET DUMP OFF > which I know you wouldn't recommend it. > If I trying to close this rdr file before purge it, how can i do that? > > Would you let me know how do i close and purge this rdr files? The dump is a fake spool file that represents a reserved amount of space that VM allocates so a dump can be made when a problem occurs. You should not disable that since IBM can't help you fix problems anymore. You need to find what real spool files are filling up the system. There may have been system failures that actually created dumps that now sit in spool space. I tend to run this quick & dirty program to show that /* SPOOLPIG EXEC Show top-10 spool users */ /* Author: Rob van der Heij, 9 Oct 2009 */ 'PIPE (end \) literal RDR PRT PUN', '| split ', '| spec ,QUERY, 1 w1 nw ,EXP, nw ', '| cp ', '| nlocate 77.4 ,SIZE,', /* Drop the headers */ '| change 80 ,K,000,', /* More than 9999 blocks */ '| spec 77-* 1.10 1.8 n', /* Blocks & ownerid */ '| l: lookup autoadd before count increment', '\ l: \ l: ', '| sort 1.10 d', /* Biggest ones first */ '| take 10 ', /* Show me top-10 */ '| spec 11.8 1 1.10 n ', '| literal Userid #blocks', '| cons' If that does not show an obvious offender, it may be just the gradual growth of spool files in the system. If you have not done yet, you should look at SFPURGER to clean up old spool files. Rob ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
