RE: Object authority

The issue is custom objects in custom libraries, not IP. Sorry, I should have been clearer on that. Don't want to give IP a black eye. 😊

Profiles are setup with the correct authority. It is the objects that are not.



-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Bryan Dietz
Sent: Thursday, June 9, 2022 3:40 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Object authority

you should see if IP has a document for locking down their software.
Change management software is a must.

you must remove *ALLOBJ from programmers or anything you try will not work.

Bryan


smith5646midrange@xxxxxxxxx wrote on 6/9/2022 1:42 PM:

We are having problems with developers "installing" new objects
outside of the change management software and also renaming existing
objects and creating new versions of them.



We are an IP based company so we rely heavily on adding and removing
PF and LF members.



Is there a level of security that I am overlooking that will allow us
to lock down a library to prevent the creation of new objects and the
renaming of existing objects yet still allow the ADDPFM/ADDLFM and RMVM commands?

--
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.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com