RDI: Enable change of sources only in specific libraries

We have evaluated this request and determined that it cannot be implemented at this time.

IBM Power Systems Development - RDi team

Thank you for your suggestions.

I'm fully aware that it can be bypassed in the PDM.
Thus being very carefull when doing something in the PRDLIB ie scanning in it.

While waiting for IBM's solution (which could take years, if ever), here's a suggestion:

1. Create a new test source file in the production and test environments (so everything already there will work as before).

2. Create a new user profile that will have *ALL authority for the new production test source file.

3. Change the authority of the new production test source file so that all users have only *USE authority (including *PUBLIC but not the new user profile which has *ALL authority).

4. To move source from the new test source file in the test environment to the production environment, log on as the new user profile and run your third party app.

You can do this as a proof of concept with just the one new source file (no need to modify the library's authority). If the concept works, then you can apply it to the other source files in the production environment and your problem will be solved, or you can wait until IBM provides a solution, assuming they do.

By the way, the production source files could be edited with PDM directly by bypassing your third party app, which is what RDi is doing.

First of all the source management system is a third party green screen environment. And it is old.
If you try to edit a source it checks if a specific object exists in the library.
If it does you are allowed to open the source with PDM.
Otherwise access is rejected.

Compilation is also controlled via this system.

I don't dare changing object level authority on these libraries and will not be allowed to do so.
Because I risk all hell breaks loose.

You stated "You can only browse the sources in the source library it is not possible to edit them." How is this being done if not by object level security (rhetorical question, it can't be done)? Unless you have object security on the production source files, that statement is false, if they can be edited by RDi, then they can be edited by any other means of editing source files.

If it causes other problems your procedures/way of working is not correct.

I suggest to solve this first.

Implementing object level authority will cause a lot of other problems. So this is not an option.

No need for any of that, just use object level authority. Change the authority of the source files to *USE for *PUBLIC and any user that has specific authority to the source files. RDi allows users with *USE authority to open source members in browse mode only, you'll get an error if you attempt to edit a source member.