Re: IASP, HA and development

[Wim <midrange-l@xxxxxxxxxxxxx>]

Hi Evan,

> if "the main thing for using iasp'S" is to prevent your developers 
> from getting at production data I am afraid you are barking up the 
> wrong tree. An IASP is just an environment on a box. There is no 
> security separation that I am aware of at present (wouldn't surprise 
> me if it was added/coming).

We where thinking in putting the mirrored libraries of the production 
machine into a separate storage group in order to avoid accidental 
object manipulations by the developers. As we understood, if the library 
is not in the namespace of the job than it cannot be referenced without 
intent. And that this can be achieved by implementing IASP.

> What access does *PUBLIC have to your data have at the moment ?

> I'm willing to bet that it is more than you want the programmers to have.

Okay, how much!! (sound of rattling keyboard)

Best Regards,

Wim Jongman

>