Re: Disabling edit and copy of source program in production library -- MIDRANGE-L

Dwayne,

Well, I was just outlining how to keep them out of your program source files.  
That would include all source files that you choose to secure using this method 
whether they are CL, RPG, COBOL or whatever else you have.

Do you also want to keep them from running programs?  If so, they you can 
extend this same method to the *PGM objects that you would like to prevent them 
from running.

Rich Loeber
Kisco Information Systems
http://www.kisco.com
  ------------------------------------------------------------------------

Dwayne Allison wrote:

Is this true for programs and CL?

        -----Original Message-----
        From: midrange-l-bounces@xxxxxxxxxxxx on behalf of Rich Loeber
        Sent: Fri 10/6/2006 6:09 AM
        To: Midrange Systems Technical Discussion
        Cc:
        Subject: Re: Disabling edit and copy of source program in production 
library



        Dwayne,

        The simple solution is to make sure that the developer's profile does 
not have *ALLOBJ authority, then just make sure their profile is set up as 
*EXCLUDE on the source physical file.  The developer will probably scream 
bloody murder at being denied *ALLOBJ authority, but it is the right way to 
handle it and, after all, whose source code is it at this point?

        Rich Loeber
        Kisco Information Systems
        http://www.kisco.com
          
------------------------------------------------------------------------

        Dwayne Allison wrote:

        > Good Morning Group,
        >
        > We have ALDON change management on our test box; which has a 
development, intergration, test, and production library.  The development is 
the developer's library that's used when the developer check out a source 
from the production library.  The intergation environment is used for the BA 
testing and the Test environment is used for the User testing.  Than we have 
the production environment where the source and object is stored and the 
obect is sent over to our Production box.
        >
        > Our problem now is we want to make sure our developer can not edit 
or copy over the source that in our production box.  Is there a way to 
disable the edit command or the compiler for the production environment.  We 
also need a way to stop the developer from copying the the source from their 
development library into the production library.  We can allow them to copy 
from the production library, but we do not want them to copy it back to it.
        >
        > Thanks
        >
        > --
        > This is the Midrange Systems Technical Discussion (MIDRANGE-L) 
mailing list
        > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
        > To subscribe, unsubscribe, or change list options,
        > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
        > or email: MIDRANGE-L-request@xxxxxxxxxxxx
        > Before posting, please take a moment to review the archives
        > at http://archive.midrange.com/midrange-l.


  ------------------------------------------------------------------------
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.