|
Hello All, I've just came back from the client place and found the audit journal receiver is taking a large portion of it. I've cleared it and managed to clear about 100GB and now the DASD utilization is down to 65%. Is it normal for audit journal to take up so much space? I went it to check and found out that all the options are turned on. But strange this is, why it started to grow tremendously for the past few days. My client will have a close watch on the receiver and considered case close. Thanks for everybody's help! =) Regards, Daniel On 8/4/06, Jim Franz <franz400@xxxxxxxxxxxx> wrote:
will wait with eager anticipation...<grin> jim ----- Original Message ----- From: "IGS Ang" <igsang@xxxxxxxxx> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> Sent: Thursday, August 03, 2006 7:51 PM Subject: Re: Disk 99% full, what to do? > Not yet, it's still 7:50AM over my area, i will be going over in an > hour time. that wrksyssts screen is own 810. > > regards, > daniel > > On 8/4/06, Jim Franz <franz400@xxxxxxxxxxxx> wrote: >> Assuming you have already cleaned things up now & resolved your problem? >> >> % system ASP used . . : 40.4056 - this says you are at 40% >> disk >> used >> >> these are pretty normal.... >> % perm addresses . . . . : .007 Current unprotect used : >> 2029 M >> % temp addresses . . . . : .010 Maximum unprotect . . : >> 2126 M >> >> jim franz >> >> ----- Original Message ----- >> From: "IGS Ang" <igsang@xxxxxxxxx> >> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> >> Sent: Thursday, August 03, 2006 1:22 PM >> Subject: Re: Disk 99% full, what to do? >> >> >> > Sorry to sound a noob, but i dont see temp in the wrksyssts screen >> > below. Am i missing something? >> > Work with System Status >> > IGS810 >> > 08/04/06 >> > 01:19:13 >> > % CPU used . . . . . . . : .6 Auxiliary storage: >> > % DB capability . . . . : .0 System ASP . . . . . . : >> > 87.74 G >> > Elapsed time . . . . . . : 00:00:00 % system ASP used . . : >> > 40.4056 >> > Jobs in system . . . . . : 187 Total . . . . . . . . : >> > 87.74 G >> > % perm addresses . . . . : .007 Current unprotect used : >> > 2029 M >> > % temp addresses . . . . : .010 Maximum unprotect . . : >> > 2126 M >> > >> > Type changes (if allowed), press Enter. >> > >> > System Pool Reserved Max -----DB----- ---Non-DB--- >> > Pool Size (M) Size (M) Active Fault Pages Fault Pages >> > 1 175.30 89.66 +++++ .0 .0 1.3 1.3 >> > 2 884.49 .73 62 .0 .0 .0 .0 >> > 3 429.19 .00 19 .0 .0 4.1 4.1 >> > 4 15.03 .00 5 .0 .0 .0 .0 >> > >> > Regards, >> > daniel >> > >> > On 8/4/06, Wayne McAlpine <wayne.mcalpine@xxxxxxxxxxxxxxxxx> wrote: >> >> Do a WRKSYSSTS and take a look at the amount of temporary storage >> >> used. >> >> Both the maximum (since the last IPL) and the current temp storage >> >> are >> >> shown. This will tell you whether it is your user objects that are >> >> gobbling up the storage or system objects, e.g., QTEMP libraries, >> >> joblogs. >> >> >> >> Pete Massiello wrote: >> >> > If you can re-ipl to get some minor space back. Then you can >> >> > probably >> >> > apply all your PTFs permanently. This should give you 1 to 2% of >> >> > disk, >> >> > where you can run gather and retrieve DSKINFO to figure out the real >> >> > culprit. >> >> > >> >> > Pete >> >> > >> >> > ---------------------------- Original >> >> > Message ---------------------------- >> >> > Subject: Disk 99% full, what to do? >> >> > From: "IGS Ang" <igsang@xxxxxxxxx> >> >> > Date: Thu, August 3, 2006 6:09 am >> >> > To: MIDRANGE-L@xxxxxxxxxxxx >> >> > -------------------------------------------------------------------------- >> >> > >> >> >> Hello All, >> >> >> >> >> >> Out of nowhere, my disk utilization is 99% (total 500gb). I can go >> >> >> disktasks, but i doubt the job will ever finish. The system is >> >> >> development, hence i can re-ipl anything. >> >> >> >> >> >> Please advise what i can do, or is there any ways to locate those >> >> >> big >> >> >> files via search command? >> >> >> >> >> >> Regards, >> >> >> Daniel >> >> >> -- >> >> >> 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. >> >> >> >> >> >> >> >> > >> >> > >> >> -- >> >> 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. >> >> >> >> >> > -- >> > 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. >> > >> >> >> -- >> 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. >> >> > -- > 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. > -- 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.