Re: [Bulk] Re: iASP security

Mark

I was involved in getting some RJS products to work in an iASP - it really wasn't all that difficult - not completely trivial, but the restrictions have become less onerous over time.

It is necessary to consider the things you cite, AND I think it your caution is a bit over-stated, based on my own experience.

RJS did not have any objects that had to be in *SYSBAS only - other products and applications will need to look at those objects - largely configuration objects and other system things, as I recall.

Vern

On 10/3/2014 9:44 AM, Mark S Waterbury wrote:

Thanks, Charles.

That helps somewhat.

There are still many restrictions on what kinds of objects can be placed in an IASP, and other considerations, so that it is definitely non-trivial to deploy and use IASPs. It is not simply a matter of just setting them up. Many 3rd party vendor ISV software packages are not certified for use with IASPs, or have some restrictions on exactly how you must install and use their products to work with IASPs. And, your in-house applications code may require some modifications to work correctly in an IASP environment.

Mark

> On 10/3/2014 10:27 AM, Charles Wilt wrote:

The library can't be in SYSBAS, but you can have the same library in two
different iASP.

When a job starts, it is assigned to a single iASP + SYSBAS

Charles