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).
A programmer that has QPGMR or QECOFR rights has those rights on the
_machine_. AN IASP runs _inside_ the machine
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.
Sounds like you really need another machine or an LPAR.
Hi Evan and Al,
Thanks for replying.
The main thing for using iasp'S would be to keep our developers from
touching data on the other asp. The main idea is to create some sort of
lpar envioronment without the lpar overhead and costs.
What time frame are we looking at if we want to create this setup.
Currently we have a lot of jobdescriptions, susbsystems, hardcoded library
names and so on. However, we are currently in the process of cleaning up
al qualified things.
Thanks again for replying.
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.