|
haha .. we saved about 1% of our 200 GB be getting rid of all the old job logs. It helps! ----- Original Message ----- From: <rob@xxxxxxxxx> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> Sent: Monday, April 05, 2004 4:18 PM Subject: Re: History Job Logs > In that case I can see picking nits to get by. > > However, I'd still start on the RTVDSKINF / PRTDSKINF *SYS combo. > > Rob Berendt > -- > Group Dekko Services, LLC > Dept 01.073 > PO Box 2000 > Dock 108 > 6928N 400E > Kendallville, IN 46755 > http://www.dekko.com > > > > > > "Adam Lang" <aalang@xxxxxxxxxxxxxxxxxxxx> > Sent by: midrange-l-bounces@xxxxxxxxxxxx > 04/05/2004 03:14 PM > Please respond to > Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> > > > To > "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> > cc > > Subject > Re: History Job Logs > > > > > > > Well, apparently history logs have not been deleted since we first turned > the system on. go cleanup was set to Y for autmatic running, but the time > was set to *NONE. We had a few. ;) > > As for DASD, we use it for a test and production environment. We are awar > eof the space problem, we are just tyring to hold on till we order the new > box. To add any more space, we have to get an external cabinet and a > shame > to spend money on it when we are just gettign a new one anyway. We've > been > doing a lot of code moves and addign new lines of business for our > insurance > company and it is just chewing it all up. > > ----- Original Message ----- > From: "Ingvaldson, Scott" <SIngvaldson@xxxxxxxxxxxx> > To: <midrange-l@xxxxxxxxxxxx> > Sent: Monday, April 05, 2004 2:27 PM > Subject: RE: History Job Logs > > > > Adam - > > > > The ROI on deleting old history logs is usually limited, assuming that > you > > have cleanup set to a reasonable length of time, say 30 days. What is > your > > DASD capacity and utilization? You may want to search for (unneeded) > large > > objects, especially in programmer libraries. > > > > If the cause of your space issue is production data, do you monitor your > > rate of growth? > > > > Regards, > > > > Scott Ingvaldson > > AS/400 System Administrator > > GuideOne Insurance Group > > > > -----Original Message----- > > date: Mon, 5 Apr 2004 13:32:33 -0400 > > from: "Adam Lang" <aalang@xxxxxxxxxxxxxxxxxxxx> > > subject: History Job Logs > > > > We are starting to run tight on space on our iSeries, and one of the > things > > it says to do is delete old history logs. How do you go about doing > this? > > > > Adam Lang > > Systems Engineer > > Rutgers Casualty Insurance Company > > http://www.rutgersinsurance.com > > > > This message and accompanying documents are covered by the Electronic > > Communications Privacy Act, 18 U.S.C. §§ 2510-2521, and contains > information > > intended for the specified individual(s) only. This information is > > confidential. If you are not the intended recipient or an agent > responsible > > for delivering it to the intended recipient, you are hereby notified > that > > you have received this document in error and that any review, > dissemination, > > copying, or the taking of any action based on the contents of this > > information is strictly prohibited. If you have received this > communication > > in error, please notify us immediately by e-mail, and delete the > original > > message. > > > > _______________________________________________ > > 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-2025 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.