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.
This is true. If you are happy that the programmers won't touch your data
except unintentionally then this will possibly work. I had taken your
statement to mean you want to prevent them from touching the data. Remember
that one command (SETASPGRP) allows them to swap from a development
namespace into a production namespace; If they have access to a command
line they can run this command at any time, although I guess you could
secure it :)
If they do support calls and regularly swap between environments as opposed
to using an alternative sign-on there are bound to be accidents.
At this stage I have to confess to preferring to keep developers doing
development away from production so I may have read more into your desire
to separate the environments than you intended.
I still think on balance you will get more mileage and more value out of a
separate machine than the added administration an IASP will probably cost
you, but what the hey, it's fun to play with, that's for sure :)
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)
OK, if *PUBLIC is *EXCLUDE you win :)
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.