RE: Object authority -- MIDRANGE-L

I am looking for a very specific solution of that blocks the
manipulation of objects (creating, deleting, renaming) while still
allowing the use of member commands like ADDPFM, RNMM,
and RMVM.

There is no practical difference between DLTF FILE(LIB/FILE) and RMVM FILE(LIB/FILE) MBR(*ALL)

It appears that IBM has tied the execution of the member
commands to the authority of the file AND LIBRARY which
makes no sense to me.

From your story, your programmers do not see the complete picture of their actions. In that case, you have no choice but to block the library and only allow access via the change management software (which probably needs replacing if your programmers are dodging it).

To manipulate members in this restricted environment, you create specific commands that adopt authority to allow access to the members, or do as Rob suggested; assign specific authority to certain commands. The latter will be system-wide, so it also affects other libraries.

Best regards,

Wim Jongman

Embrace Change. Remain In Control.
https://remainsoftware.com

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.