SAVCHGOBJ -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: SAVCHGOBJ
From: fiona.fitzgerald@xxxxxxxxxxxxxxxxxx
Date: Fri, 2 Nov 2001 23:01:50 +0000
List-Archive: <http://archive.midrange.com/midrange-l/>
List-Help: <mailto:midrange-l-request@midrange.com?subject=help>
List-Id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-Post: <mailto:midrange-l@midrange.com>
List-Subscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=subscribe>
List-Unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=unsubscribe>


We backup changes , without the access paths during the week, & do a full
SAVLIB *ALLUSR at weekends with access paths.
Should the nightly save changes job save access paths just like the weekly
full saves ?

We've been using this strategy to minimise tape & offline batch-window
usage for 5 years, but I'm wondering if this is wrong for effective
disaster-recovery, when it slows down to rebuild them. Our application
files rarely change, only the pgms get upgraded weekly. Does anyone have an
opinion on the pros & cons of this ?

Fiona

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: SAVCHGOBJ , John Earl

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.