RE: Disabling edit and copy of source program in production library

[vhamberg@xxxxxxxxxxx]

I worked with Dave for a while at Old Republic and was there when ALDON was 
brought in - a bit of a culture shock for a while. But the basic thing was to 
allow access for most folks only through ALDON - you should go to them or your 
CMS vendor to see how it should be done - they all have this basic concept down 
cold.

And access to production machines there was beginning to be rigidly controlled 
when I left. We'd put in some nice controls and auditing for that, asI recall, 
and that Dave is fighting with now, right?   ;-)

So put in proper controls - no developer should be able even to SEE data on a 
production machine without tight monitoring and auditing of his/her sojourn 
there. And make the only access on development machines via some defined 
controlled pathway.

Vern

-------------- Original message -------------- 
From: "Turnidge, Dave" <DTurnidge@xxxxxxxxxxxxxxxxxxxx> 

> We have ALDON as well, but it really doesn't matter which package you 
> use, if any. The bottom line is that if you have a user with *ALLOBJ 
> authority - you're shot. You have to take that away. The way it works 
> here is we blame it on the government... SOX ...and that resolves most 
> issues. :-) 
>
> -----Original Message----- 
> From: midrange-l-bounces@xxxxxxxxxxxx 
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dwayne Allison 
> Sent: Friday, October 06, 2006 6:06 AM 
> To: midrange-l@xxxxxxxxxxxx 
> Cc: Cathy Worthington 
> Subject: Disabling edit and copy of source program in production library 
>
> 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.