Re: Survey: What do you use more? RCLSTG or GO SAVE 21? -- MIDRANGE-L

I created my own GO 21 save as well, as we have imaged documents on the
harddrive that we don't want to save with the rest of the system.

Jim

On 6/6/07, Ingvaldson, Scott <SIngvaldson@xxxxxxxxxxxx> wrote:

The basic theory of the problem was that it was due to the large number
of small objects, (which was a change to the system with that RCLSTG)
though I'm sure that the user ASP and external DASD contributed. Sorta
hit the trifecta...

Now we're looking into reconfiguring it as an iASP (ugh) to aid in DR.
Not pretty, but hopefully will ease recovery.

Regards,

Scott Ingvaldson
System i Administrator
GuideOne Mutual Insurance Company

-----Original Message-----
From: rob@xxxxxxxxx [mailto:rob@xxxxxxxxx]
Sent: Wednesday, June 06, 2007 9:15 AM
To: Midrange Systems Technical Discussion
Subject: Re: Survey: What do you use more? RCLSTG or GO SAVE 21?

I pretty much do run my own GO SAVE 21. For two reasons, One, to log
the times (which the new enhancement will alleviate).
Two, to string the RCLSTG and saves together so that I can do this from
home with my handy remote access to my HMC and not have to lose time
after the RCLSTG and before starting the saves.
While I have had one lpar that seems to take a lot longer on RCLSTG than
seems reasonable (significantly smaller than other lpars, and much more
horsepower than some other lpars) I've not experienced your
difficulties.
And, I don't use user asps or independent asps, etc.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

"Ingvaldson, Scott" <SIngvaldson@xxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
06/06/2007 09:32 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>

To
"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
cc

Fax to

Subject
Survey: What do you use more? RCLSTG or GO SAVE 21?

Neither, ever!

We used to do RCLSTG prior to O/S upgrades. The last time we tried to
run a RCLSTG I had to kill it after about 60 hours. Previously they had
run 4-6 hours. We now have about 8 million documents in a 1.2 TB UDFS
on external DASD. Support was very clear: "DON'T DO RCLSTG UNLESS WE
TELL YOU TO!"

We used to do Opt 21 saves at year-end. Now they have the same issue as
above. We use BRMS and have to omit /dev/QASP03/ESS800.UDFS from every
save, or they will run for 60-90 hours.

A status display would be nice for both. Before BRMS we used a Line 27
Break Message monitor to send status messages to the bottom of the
screen during the SAVSYS. Many times that saved waiting for hours to
find out that the backup wasn't running!

Just an FYI, it is possible to write your own version of an Opt 21 save.
As long as you follow the basic format a GO RESTORE 21 will restore from
your version.

Regards,

Scott Ingvaldson
System i Administrator
GuideOne Mutual Insurance Company

-----Original Message-----
From: rob@xxxxxxxxx [mailto:rob@xxxxxxxxx]
Sent: Wednesday, June 06, 2007 7:50 AM
To: Midrange Systems Technical Discussion
Subject: Re: FW: Marketing Field Requirement -- MR0131076214

Good going. Must have been their day to respond to those. I've heard
that IBM is going to add a new data area to record the times of the
steps of the GO SAVE 21. Even record up to the last 5 saves! The new
data area will have pretty much the same layout as QRCLSTG. And they
are waffling on my other request to add a status screen on the GO SAVE
21 to utilize this new data area to give you a status screen during the
save much like the cool status screen on RCLSTG in V5R4. Survey: What
do you use more?
RCLSTG or GO SAVE 21? Which would you rather have a status screen on?

And I just submitted another DCR to allow us to specify on the initial
GO SAVE 21 screen to NOT do the STRSBS of the controlling subsystem
after the save. We IPL and stuff right after the save and would rather
not have to bring stuff back down to restricted state twice.

Gotta go, doing a GO RESTORE 21 to a new mimix lpar today...

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

"Ingvaldson, Scott" <SIngvaldson@xxxxxxxxxxxx>
Sent by: midrange-l-bounces+rob=dekko.com@xxxxxxxxxxxx
06/05/2007 04:55 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>

To
<midrange-l@xxxxxxxxxxxx>
cc

Fax to

Subject
FW: Marketing Field Requirement -- MR0131076214

Woo Hoo! Check this out.

Now the score is Me 1, IBM 17

Regards,

Scott Ingvaldson
System i Administrator
GuideOne Mutual Insurance Company

________________________________

From: DCRREQ [mailto:dcrreq@xxxxxxxxxx]
Sent: Tuesday, June 05, 2007 12:53 PM
To: Ingvaldson, Scott
Subject: Marketing Field Requirement -- MR0131076214

User Group Number - MR0131076214
Document Status - Available
Title - BRMS - Automate Tape location from 3494 Library

IBM believes that the request described has been solved with a current
product / service / policy / etc.
This should be fixed by the latest BRMS PTFs released March 21, 2007:
V5R4 PTF: SI26908
V5R3 PTF: SI26903
V5R2 PTF: SI26893

______________________________________________
Design Change Requests
IBM eServer iSeries
DCRREQ@xxxxxxxxxx

--

-----------------------------------------

DISCLAIMER:
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.