Re: Compile Commands -- possible to remove the defaults?

Thanks for the feedback. Much to the dismay of a couple of green-screeners, that avenue is locked down pretty tight as well. Only the version control program can change production source files, and I monitor for objects not owned by that user to identify anyone who might try to compile from their own library into production.

Removing the defaults is purely a cosmetic thing for me.


-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Thierry Bernard
Sent: Monday, September 03, 2012 11:25 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] Compile Commands -- possible to remove the defaults?

I think trying to remove the default compile commands in RD Power does not really accomplish what you want. People will still be able to CRTBNDRPG, CRPRPGMOD, CRTPGM etc. from the green screen.

IBM i OS Object security needs to be set for the libraries/objects controlled by your version control system so that developers cannot change the objects. The version control system programs runs under a profile that has enough authority to change the objects, for instance, it could use USRPRF(*OWNER) authority with an owner that is *ALLOBJ.
The idea is that the version control system validates and logs everything, that's where you define the rules.

Have a nice day.
Thierry.


--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.