|
On May 8, 2024, at 7:51 PM, James Ash via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx> wrote:
I'm trying to clean up my IFS backups and I've had problems in the past with objects not being saved because the attribute to allow an object to be saved was *NO.
I'm having a hard time grasping why I wouldn't want to save this object (or any object) on my system and why this attribute even exists. It just seems like a setup for failure.
If I change all the *NO attributes to *YES, am I causing the failure of some process or is this all just about saving space and time on my backups?
Jim Ash
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.
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.