|
I use a program that does all the commands from go save, 21. Prior to that it also RCLSTG, RCLDLO, RGZDLO. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com "Jeff Crosby" <jlcrosby@xxxxxxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 09/22/2004 09:03 AM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx> cc Fax to Subject Backup before release update I am planning on installing V5R3 (from V5R2) this weekend. In the past I have always done a GO SAVE option 21 just prior to upgrading releases. In thinking about this, I have a question in regards as do I really have to do this. Every Friday night we do the following backup: SAVSECDTA SAVCFG (along with RTVCFGSRC and saving that object as well) SAVLIB *NONSYS SAVDLO DLO(*ALL) SAV OBJ(('/*') ('/QSYS.LIB' *OMIT) ('/QDLS' *OMIT) + ('/ImageCatalogs' *OMIT)) Friday morning I will do the following backup: SAVSYS SAVLIB LIB(*IBM) If I do both the above, does the option 21 save really gain me anything? If a recovery is necessary to where I have to reload everything, I know I can reload from the option 21 save. Can I reload from the SAVSYS? The upgrade guide says on page 55 "Tapes that are created with the Save System (SAVSYS) command cannot be used with the automatic install process. These tapes also do not provide a complete backup." I understand the second sentence. Is the first sentence telling me I can't _reload_ from the SAVSYS or that I just can't do an automatic install? Do the rest of you do an option 21 save just before any release upgrade, or use your regular backup strategy as being sufficient? Thanks. -- Jeff Crosby Dilgard Frozen Foods, Inc. P.O. Box 13369 Ft. Wayne, IN 46868-3369 260-422-7531 The opinions expressed are my own and not necessarily the opinion of my company. Unless I say so. -- 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-2024 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.