|
Sheesh, that's a pretty extreme setup to have to go to just because of Mgt Central choking on something and damaging those collections! (not criticizing, just observing...) IBM should be able to resolve the Mgt Central/SQL oriented issue at hand rather than you needing to go to such measures just to get a full save done! I would think you could escalate this one pretty well and get a fix in light of the hoops you're needing to jump through to facilitate something as basic as a full save. rob@xxxxxxxxx Sent by: midrange-l-bounce To s@xxxxxxxxxxxx Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> 08/25/2005 03:54 cc PM Subject RE: RCLSTG (Was: Preventative Please respond to Maintenance For AS400) Midrange Systems Technical Discussion <midrange-l@midra nge.com> <snip> Historically, it has seemed like if you do them regularly they don't take as long. <snip> I don't find that to make a difference. Here's a catch22. We run the RCLSTG before the saves to avoid a save crashing because of damaged objects. (Management central is really bad at creating damaged collections.) However an object will not be marked as damaged prior to the first attempt to save it. The scenario. System is brought down to restricted state. Unbeknownst to us we have yet another damaged *MGTCOL. Doing a DSPOBJD would not have the damaged flag set yet. Full RCLSTG is run. Full system save is run. Crashes when we hit the damaged *MGTCOL. At this time the DSPOBJD should now have the damaged flag set. This is one of the reasons why Al Barsa recommends doing a full save immediately upon a full system restore. Right Al? It's bitter medicine to swallow because it significantly increases your downtime in one of your most stressful situations. Now we do a SAVOBJ of all objects in QMGTC2 to a save file and delete any damaged ones prior to the RCLSTG. What a pain in the bum. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com "Jones, John \(US\)" <John.Jones@xxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 08/25/2005 02:19 PM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> cc Subject RE: RCLSTG (Was: Preventative Maintenance For AS400) We run them as needed; maybe about every 14-18 months normally. Maybe also in front of an upgrade, but not necessarily. The last one on our 730, in June, with 65 17GB drives at about 45% took 1 hour 40 minutes. Our dev/DR box last did one in June of 2003; at that time it would have beena 720 with 30 17GB drives and (guessing) 35-40% full. That RCLSTG took 1 hour 9 minutes. Our 570, installed late last year, has yet to do an RCLSTG. Historically, it has seemed like if you do them regularly they don't take as long. Scott, yours is the first day+ reclaim I've heard about since the white box days. For those who don't know, DSPDTAARA QRCLSTG gives the starting and ending date & time of the last RCLSTG along with the then-OS release, system name, and serial number. At a former employer, we havd a D10 or D20 with 4 drives. It was not on power protection as it was just a small test box. It eventually ran out of DASD & locked up. As part of the recovery process we RCLSTGed it. Some hours later it finished and the DASD usage had dropped to 35%. -- John A. Jones, CISSP Americas Information Security Officer Jones Lang LaSalle, Inc. V: +1-630-455-2787 F: +1-312-601-1782 john.jones@xxxxxxxxxx -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of ChadB@xxxxxxxxxxxxxxxxxxxx Sent: Thursday, August 25, 2005 1:44 PM To: Midrange Systems Technical Discussion Subject: Re: RCLSTG (Was: Preventative Maintenance For AS400) Wow... that's the type of RCLSTG horror story i've rumours of, but never heard any specifics about! I'm wonder how common these types of RCLSTGs really are... i'm betting Larry, Al, and some of the others might have some idea... I've always been lucky to end up with the 2-4 hour ones. "Ingvaldson, Scott" <SIngvaldson@guid To eone.com> <midrange-l@xxxxxxxxxxxx> Sent by: cc midrange-l-bounce s@xxxxxxxxxxxx Subject RCLSTG (Was: Preventative Maintenance For AS400) 08/25/2005 02:33 PM Please respond to Midrange Systems Technical Discussion <midrange-l@midra nge.com> I was always in the "run a RCLSTG before very upgrade" camp, but we just had a bad experience with our last RCLSTG. We're getting ready to upgrade V5R2-->V5R3 on an 810 with 4GB main storage, 225 GB internal DASD at 66% and 565 GB fiber-attached shark external DASD at 69%. The last RCLSTG was run two years ago and took about two hours. We haven't had any system crashes in this time, however the external DASD was added after that and has about 7M documents stored on it. I SWAGed a guesstimate of 8 hours and requested 24 hours of downtime to run the RCLSTG. The first part of the RCLSTG took about 24 hours. (to get to 100%) Next it sat at message CPI8218 - Directory recovery in progress for about 10 hours before going on to message CPIA916. After determining that we were going to miss our SLA Monday morning the boss ordered an abort. It only took about a minute to end after an ALT SYSREQ 2 and then I did a RCLSTG *DBXREF, which only ran about 6 minutes. Then I IPLed (B-N) and all looked normal, a *FULL restart went very quickly. There were 12 objects in QRCL: 2 data queues and 9 user spaces beginning with Q, and 1 file (EKDDSPOBJD, which may have been a WAF temp file as it no longer exists or seems to be needed.) There were no /QReclaim or /QOpenSys/QReclaim directories. The bottom line is that it is unlikely that we will run a Reclaim Storage again, at least not until we have an HA environment with a backup production LPAR. Regards, Scott Ingvaldson iSeries System Administrator GuideOne Insurance Group -----Original Message----- date: Thu, 25 Aug 2005 11:27:03 -0400 from: "Doug Hart" <DougHart@xxxxxxxxxxxx> subject: RE: Preventative Maintenance For AS400 I work at a large (8 systems/23 partitions) iSeries datacenter and they have not done a RCLSTG in well over 10 years. They simply say that they can't be down that long. They also feel that since they replace machines on about 3 year cycles they are never that over due for the cleanup. I'm not totally in agreement but they run OK. I if you run RTVDSKINF then PRTDSKINF *SYS look down the report for the line 'Storage affected by RCLSTG'. It should show the impact of objects to recover/cleanup. -- Doug Hart -- 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. ________________________________________________________________________ _____ Scanned by IBM Email Security Management Services powered by MessageLabs. For more information please visit http://www.ers.ibm.com ________________________________________________________________________ _____ ForwardSourceID:NT00029806 ________________________________________________________________________ _____ Scanned by IBM Email Security Management Services powered by MessageLabs. For more information please visit http://www.ers.ibm.com ________________________________________________________________________ _____ This email is for the use of the intended recipient(s) only. If you have received this email in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not keep, use, disclose, copy or distribute this email without the author's prior permission. We have taken precautions to minimize the risk of transmitting software viruses, but we advise you to carry out your own virus checks on any attachment to this message. We cannot accept liability for any loss or damage caused by software viruses. The information contained in this communication may be confidential and may be subject to the attorney-client privilege. If you are the intended recipient and you do not wish to receive similar electronic messages from us in the future then please respond to the sender to this effect. -- 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. _____________________________________________________________________________ Scanned by IBM Email Security Management Services powered by MessageLabs. For more information please visit http://www.ers.ibm.com _____________________________________________________________________________ ForwardSourceID:NT00029886 _____________________________________________________________________________ Scanned by IBM Email Security Management Services powered by MessageLabs. For more information please visit http://www.ers.ibm.com _____________________________________________________________________________
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.