|
On 03/27/2025 9:21 PM EDT Michael Quigley <michaelquigley@xxxxxxxxxx> wrote:
Yeah, you have to love it when auditors just follow a written script without any understanding or reasoning. All we can do is laugh--it'll help us maintain sanity.
In the case where *ALWPTF is required, the suggested policy is to change it to *ALL or *ALWADP before a restore and then change it back to *ALWPTF when the restore is done.
Thanks,
Michael Quigley
Computer Services
www.TheWay.org
-----Original Message-------
------------------------------
message: 4
date: Thu, 27 Mar 2025 15:56:45 -0400
from: smith5646midrange@xxxxxxxxx
subject: RE: QALWOBJRST
"Whatever setting you use, you should have and document clear reasons for
the setting. (As Rob suggests, setting it to your auditors recommendation can
be a good, clear reason.)"
I chuckled at this line. We keep bumping heads doing restores that adopt
authority so I pushed back with the question of why it couldn't be *ALL. The
auditor's answer was "because they were told that it should not be *ALL".
They had no other reason and didn't even know what the option was for.
I gave up. Not a hill worth dying on. ?
------------------------------
Subject: Digest Footer
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) digest list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.
midrange.com%2Fmailman%2Flistinfo%2Fmidrange-
l&data=05%7C02%7Cmichaelquigley%40theway.org%7C9145f5a4ef3f45d56da
008dd6d698866%7Cdfc3789155b94fe0bc8b34a0f4b6650f%7C0%7C0%7C63878
7022210418344%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydW
UsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D
%3D%7C0%7C%7C%7C&sdata=vjXAnt30Cn%2FxSSBZNcLVRXQSvGrSeWtFO3
Z9FtUB8%2Bw%3D&reserved=0
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Farchi
ve.midrange.com%2Fmidrange-
l&data=05%7C02%7Cmichaelquigley%40theway.org%7C9145f5a4ef3f45d56da
008dd6d698866%7Cdfc3789155b94fe0bc8b34a0f4b6650f%7C0%7C0%7C63878
7022210439076%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydW
UsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D
%3D%7C0%7C%7C%7C&sdata=UycltAfITCa6hK1NR1qYDqf25ADK%2Bk8Pw5P
1Qd93n3I%3D&reserved=0.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
------------------------------
End of MIDRANGE-L Digest, Vol 24, Issue 324
*******************************************
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-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.