RE: SAVLIB LIB(*ALLUSER)

Yes, of course:

use 'tap01.devd' instead of TAP01

Mit freundlichen Gru?en

i.A. Erich W. Schasse

WIEDEMANN GmbH & Co. KG
IT/ORG
Wiedemannstr.
31157 Sarstedt
Tel. 05066/997-190
Fax  05066/997-366
mailto:schasse@xxxxxxxxxxxx
www.wiedemann.de



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Ryan Hunt
Sent: Wednesday, May 10, 2006 4:27 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: SAVLIB LIB(*ALLUSER)


Thanks for all the replies.  I am currently reviewing our backup strategy
and thought I noticed a peculiararity - maybe not.  Via CL, we are currenlty
backing up our IFS to a SAVF in qsys and then backing up the SAVF along with
all other qsys data using SAVLIB LIB(*ALLUSR) DEV(TAP01)...etc.  The goal
was to have the IFS information on tape with everything else.  Although,
this means a portion of my IFS information hits me twice on DASD usage.

I'm looking at the SAV command and I see Device as an option.  Couldn't I be
backing up my IFS to the same tape SAVLIB is using (TAP01)?


"Jan Rockstedt" <jan.rockstedt@xxxxxxxxxx>
wrote in message
news:A927050AEEE3DE40988FF63FD72EE0BD2BA83D@xxxxxxxxxxxxxxxxxxxxxxxx
> All user libraries, including IBM libraries containg user data (e.g.
> QGPL and QUSRSYS).
> Not the IFS.
>
> Sav is the command for saving the IFS.
>
>
> Regards Jan Rockstedt
> Avinova AB
> nic-hdl: JR1543-RIPE
>
> See you at Common Congress Stockholm 11-13 juni 2006!
> Common Europe and Data3 in partnership with IBM     www.comeur.org
>
>
>
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On
Behalf Of Ryan Hunt
> Sent: Wednesday, May 10, 2006 3:06 PM
> To: midrange-l@xxxxxxxxxxxx
> Subject: SAVLIB LIB(*ALLUSER)
>
> Does the SAVLIB command for V5R2 save qsys.lib only...or does it also
> save the IFS?
>
>
>
> --
> 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.