RE: Rép. : Option 21 Save - QSTRUPPGM

["Ingvaldson, Scott" <scott.ingvaldson@xxxxxxxxxx>]

DUPTAP works great (in my experience) with virtual tape.  We have even duplicated encrypted tapes to virtual and back to physical volumes with no problems.  This can use significant amounts of DASD, however.

Regards,

Scott Ingvaldson
Senior IBM Support Specialist
Midwest Region Data Center
Fiserv.


-----Original Message-----
From: Luis Rodriguez [mailto:luisro58@xxxxxxxxx] 
Sent: Thursday, October 29, 2009 11:13 AM
To: Midrange Systems Technical Discussion
Subject: Re: Rép. : Option 21 Save - QSTRUPPGM

Sorry, at item 3) I wanted to express that I "Don't *know* if it could work with them".


Luis Rodriguez
IBM Certified Systems Expert - eServer i5 iSeries



On Thu, Oct 29, 2009 at 11:29 AM, Luis Rodriguez <luisro58@xxxxxxxxx> wrote:
> David,
>
> 1.) No problems, as long as you code, in your custom script, the saves 
> corresponding to each of the restores included in the Option 21.
>
> 2.) Concur. Changing SysVals is something to be approached with a lot 
> of consideration. It is very easy to forget you changed them and,as 
> always, there is a lot of potential for creating havoc (unintentional 
> and otherwise).
>
> 3.) AFAIK, yes. There is always, of course, the option of creating 
> virtual tape devices. Don't if it could work with them, though.
>
> Regards,
>
> Luis Rodriguez
> IBM Certified Systems Expert - eServer i5 iSeries
>
>
>
> On Thu, Oct 29, 2009 at 10:43 AM, David Charmatz 
> <dcharmatz@xxxxxxxxxxxxxx> wrote:
> > Thanks for everyone's suggestions.
> >
> > A couple follow up questions/statements:
> >
> > 1. If I create a custom script as suggested by a few, are there any potential issues when our partner attempts to restore using the Option 21 Restore?
> >
> > 2. I'm a little hesitant to have our operator changing the system 
> > value - especially if he forgets.  Also, I'm somewhat sure our SOX 
> > auditors wouldn't be too thrilled with the idea of operators changing 
> > system values
> >
> > 3. The DUPTAP option... Does this require a second tape drive?
> >
> >
> > Thanks for everyone's input!
> >
> > David
> >
> >
> >
> > -----Original Message-----
> > From: midrange-l-bounces@xxxxxxxxxxxx 
> > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Denis 
> > Robitaille
> > Sent: Thursday, October 29, 2009 10:47 AM
> > To: midrange-l@xxxxxxxxxxxx
> > Subject: Rép. : Option 21 Save - QSTRUPPGM
> >
> > There are 2 things you could do:
> >
> > First, as was suggested by someone else, change the start up program to *NONE before doing the option 21 and reset it before doing the IPL.
> >
> > Second, instead of doing 3 full saves, do just one and the dulicate the tape (DUPTAP command).
> >
> > Denis Robitaille
> > Directeur Service technique TI
> > CASCADES INC.
> > 412 Marie Victorin
> > Kingsey falls(Québec) Canada J0A 1B0
> > T : 819 363-6130
> > F : 819 363-6155
> >
> >
> > > > > Noah Sandestin <nsandestin@xxxxxxxxx> 2009-10-29 09:02 >>>
> > HI All,
> >
> > On a monthly basis we run a full system (option 21) save and IPL our system.  To do this, we have an operator who manually brings the system into a restricted state, goes to the save menu and executes option 21.  As part of the option 21, when the save completes, it starts the controlling subsystem which then executes the qstruppgm.  As I mentioned earlier, we IPL the system after the save finishes but our operator is having to wait for the system to start, then end back to a restricted state before he can IPL the system.  It's been awhile since I have been through the option 21 save options, and I've done some reading online, but there doesn't appear to be an option to bypass the startup.  Can anyone suggest a way around this?
> >
> > Also, we are preparing for our DR test this December and want to execute 3 consecutive option 21 saves (2 to send to out DR partner, 1 to keep).  As you can image, if the system starts after each one it would add a lot of time to this procedure.  Any suggestions would be appreciated!
> >
> > Thanks,
> >
> > David Charmatz
> >
> >
> >
> > --
> > 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.