×
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.
On 29-Jul-2014 10:48 -0500, Steinmetz, Paul wrote:
rob@xxxxxxxxx on Tuesday, July 29, 2014 11:10 AM wrote:
<<SNIP>>
You will find out that IBM went hog wild with 7.2 and flagged a
plethora of directories with CHGATR ATR(*ALWSAV) VALUE(*NO)
/PSF400 was not one of them changed.
<<SNIP>>
How does IBM expect to recover IFS directories if they are setting
the save attribute to *NO.
I've had previous restores/recoveries fail exactly because of this
issue, some parts of a LPP were NOT being restored, which resulted
in the LPP being in an *ERROR state.
If a restore for Disaster Recovery (DR) results in such a failure due
to IBM having negated the Allow Save attribute for a directory that is
required for an LPP [the base OPTION() or another], then IMO, report
that effect as a defect. That is because either the directory requires
being backed-up as part of save\backup portion of DR processing [thus DR
is incompatible with a choice by IBM to effect change to AlwSav=No], or
the LPP needs to [change to] be accepting\tolerant of the missing
directory for both its run-time and for the Check Product Option
(CHKPRDOPT) processing performed against that option.
FWiW, on a somewhat related note:
For a customized DR whereby such omissions are not the result of IBM
actions, those could be resolved by additional customizations on the
save and\or the restore portions of DR, or with any necessary [create or
restore] activity that could be inserted after DR restore but prior to
starting the feature that requires existence of the objects that had
been omitted from the backups [by user customization]. If for example
the PSF feature requires that the /PSF400 exists [and to be owned by and
authorized to particular user(s)] but anything in the directory is
inconsequential to the feature, then if that directory were marked as
AlwSav=No per user customization, then after a restore for Disaster
Recovery from the media that would be missing the save of that
directory, a complete recovery may require adding a MKDIR and any
necessary CHGOWN and CHGAUT [or RST PVTAUT(*YES) from an alternate
backup, e.g. saved to a save file while AlwSav-Yes, that was included
with the standard saves for DR].
Note: Although the run-time required directories and objects may not
be easy to know\learn, those required for an option I believe should be
stored in the Product Load (*PRDLOD) objects for the base or numeric
OPTION(). If an option requires something for run-time but does not
check for that definitionally, then a failure at run-time rather than an
implicit create to satisfy that requirement would seem suspect IMO.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.