|
V5R3 has added a few options to compression: Data compression *DEV *NO *YES *LOW *MEDIUM *HIGH I took something in a save file saved with *HIGH and only got a ?17%? further compression when I zipped it. Use a simple *YES and zip will get a higher ratio. They both end up with the same size zip file. So I recommend the *HIGH. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com "Jones, John (US)" <John.Jones@xxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 10/01/2004 02:19 PM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> cc Fax to Subject RE: Tape backup strategy Add DTACPR(*YES) to your SAVLIB commands to use compression on the save file. That should dramatically reduce the amount of disk space required for the SAVF. John A. Jones, CISSP Americas Information Security Officer Jones Lang LaSalle, Inc. V: +1-630-455-2787 F: +1-312-601-1782 john.jones@xxxxxxxxxx -----Original Message----- From: Steve Morrison [mailto:smorrison@xxxxxxxxxxxxx] Sent: Friday, October 01, 2004 1:28 PM To: Midrange Systems Technical Discussion Subject: RE: Tape backup strategy The previous message was incomplete. The simplest approach is to save to a savefile, on the AS/400, then save the savefile to tape during the day. Do you have enough empty disk space to accomplish this? The command would be SAVLIB LIB(libname) DEV(*SAVF) SAVF(savefile) The save file will have to be created before you run this command. To copy the savefile to tape use SAVSAVFDTA SAVF(savefile) DEV(TAPxx) Steve Morrison Beacon Insurance 940-720-4672 This email is for the use of the intended recipient(s) only. If you have received this email in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not keep, use, disclose, copy or distribute this email without the author's prior permission. We have taken precautions to minimize the risk of transmitting software viruses, but we advise you to carry out your own virus checks on any attachment to this message. We cannot accept liability for any loss or damage caused by software viruses. The information contained in this communication may be confidential and may be subject to the attorney-client privilege. If you are the intended recipient and you do not wish to receive similar electronic messages from us in future then please respond to the sender to this effect. -- 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.