|
Adam, Savsys doesnt do Savlib(*IBM) If you do option 21/22/23 and F1 they explain the CL code that it actually runs. I've just written a CL EOD rtn to do the same backup steps that are covered by IBM's 23, Alluser data, including dir's,flrs,etc - comes from their "Are you saving the right stuff?" paper. I do some other stuff in it as well, so it was a bit more flexable than relying on IBM's std options of the "Go Backup" menu. All seems to work fine. I also included an SMTP email msg send to "IT DEPT" based on MAILTOOL from BVSTOOLS. Saves me having to remeber to manually check if all OK. Ian. -----Original Message----- From: Adam_Driver@kaz.com.au [mailto:Adam_Driver@kaz.com.au] Sent: Friday, 7 December 2001 16:59 To: midrange-l@midrange.com Subject: RE: GO SAVE operations -- Rick, Can I just confirm that the SAVSYS command DOES NOT do a SAVLIB(*IBM) ? I know option 22 does, but we have a backup and media utility (written in house) that uses the SAVSYS command in it's weekly and monthly backups. We only use the GO SAVE menu options for things like full saves immediately prior to an upgrade. We were having this discussion the other day, specifically whether we needed to a SAVLIB(*IBM) after the SAVSYS or not. Thanks Adam Driver Technical Consultant Kaz Computer Services Level 7, 66 Wentworth Ave Surry Hills, Sydney NSW 2010 Phone : + 61 2 9844 0386 www.kaz.com.au ----- Forwarded by Adam Driver/Sydney/KAZ/AU on 07/12/01 04:25 PM ----- "Andy Nolen-Parkhouse" To: <midrange-l@midrange.com> <aparkhouse@mediaon cc: e.net> Subject: RE: GO SAVE operations Sent by: midrange-l-admin@mi drange.com 07/12/01 02:12 AM Please respond to midrange-l Rick, Yes, option 21 will save all data on your system except for spool files. It is what you want to do, probably twice. This tape would be all that is needed for a full recovery. SAVSYS may be old, but it is still there and works just fine. Option 22 does more than a SAVSYS, and performs the equivalent of SAVSYS, plus some IBM-supplied directories and a 'SAVLIB *IBM'. Before beginning, it probably would benefit you to review the procedures for a system restore. Check the 'Backup and Recovery Manual' for your release. It is very well spelled out there. You shouldn't need it, but for planning purposes I always want to plan in a recovery window, just so I know how long the system will be unavailable in the event of a full restore. Regards, Andy Nolen-Parkhouse (Embedded image moved to file: pic24539.pcx) -- [ pic24539.pcx of type application/octet-stream deleted ] -- _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com 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.