Re: [Bulk] Re: iASP security

[DrFranken <midrange@xxxxxxxxxxxx>]

I would disagree that the list of what cannot be in an iASP is long. 
Effectively that list is configuration stuff and active work management 
items. From an application perspective "it's in there."

Oddly in my experience the older your application is the simpler a move 
to an iASP is.

Mostly it's understanding of the job description and then creating links 
as needed in the IFS to access anything there that's in the iASP.


        - Larry "DrFranken" Bolhuis

www.frankeni.com
www.iDevCloud.com
www.iInTheCloud.com

On 10/3/2014 10: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