|
On 04-Nov-2011 03:12 , Dennis Lovelady wrote:list
Point is, you are trying to defeat a _feature_ of Save/Restore that
most everyone wants.
If I were trying to do same, I might go about it by using the
security feature.
Restore as a user who has *EXCLUDE privileges to the Journal. That
might do the trick.
Another feature of the SR is to allow save\restore activity to
complete successfully with just the *SAVSYS special authority, in part
without any regard to the authority of the user performing that activity
to the objects being saved or restored; an operator can be assigned the
B&R tasks without also having to have the *ALLOBJ special authority. I
am confident that the authority of the journal for the user performing
the restore, will have no impact on the ability of the database restore
function to effect the feature of reestablishing the journaling on the
restored files; the database restore will use the adopted QSYS authority
to make the restored files match the saved files to the intent intended.
Regards, Chuck
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
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.