<div>
Sounds like your developer profiles are set up to own objects themselves.<br />
<br />
Developer user profiles could be configured to all have the same primary group profile, and to assign ownership of new objects to the group. &nbsp;<br />
<br />
I'd think that would solve the issue. &nbsp;<br />
<br />
If not, you could include standard code in your scripts where you create procedures to assign the desired default authority. &nbsp;Change management software (Turnover, for example) can also be configured to handle setting object authority on an object type basis.
</div>


Sounds like your developer profiles are set up to own objects themselves.

Developer user profiles could be configured to all have the same primary group profile, and to assign ownership of new objects to the group.  

I'd think that would solve the issue.  

If not, you could include standard code in your scripts where you create procedures to assign the desired default authority.  Change management software (Turnover, for example) can also be configured to handle setting object authority on an object type basis.

<div>
<div class="content wysiwyg-content">
Our developers have been creating a lot of SQL Stored Procedures lately. &nbsp;When they are doing this - the default authority that is &quot;granted&quot; to the new object is basically *PUBLIC *USE and then *ALL access to the user profile who created the Stored Procedure. The problem is that the other developers who work on the application are then not able to work with the new stored procedure.<br />
<br />
Is there an option to &quot;adopt&quot; the authority of the library which the Stored Procedure is created in? &nbsp;It would be ideal to just adopt the authority of the parent library - which is set up the way we want it to be.<br />
<br />
I appreciate any guidance.
</div>
</div>


Our developers have been creating a lot of SQL Stored Procedures lately.  When they are doing this - the default authority that is "granted" to the new object is basically *PUBLIC *USE and then *ALL access to the user profile who created the Stored Procedure. The problem is that the other developers who work on the application are then not able to work with the new stored procedure.

Is there an option to "adopt" the authority of the library which the Stored Procedure is created in?  It would be ideal to just adopt the authority of the parent library - which is set up the way we want it to be.

I appreciate any guidance.

SQL Stored Procedure Authority

SQL (Structured Query Language) is designed to be used in conjunction with relational database products as of a means of working with sets of data. SQL consists of data definition, data manipulation, and procedural elements. Its scope includes data insert, query, update and delete, schema creation and modification, and data access control.

IBM i, formerly known as AS/400, is a proprietary, midrange, object-based operating and application system. It includes a relational database, a menu-driven interface, support for multiple users, block-oriented terminal support and printers, and supports security, communications, and web-based application servers including Websphere, Apache and Tomcat.