RE: [Bulk] Re: [Bulk] Re: iASP security

Mark,

True an LPP has to exist in *SYSBAS but that does not stop that same LPP
from installing whatever it would like into an iASP. So put the minimum set
of objects in *SYSBAS needed and restore everything else into an iASP. PTF
application can be done the same way. You cite a restriction that is
trivial.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mark
S Waterbury
Sent: Friday, October 03, 2014 10:14 AM
To: Midrange Systems Technical Discussion
Subject: Re: [Bulk] Re: [Bulk] Re: iASP security

Vern:

When ISVs use IBM's software packaging APIs so that customers can install
their software as an LPP using the RSTLICPGM command, all of the
software components installed by RSTLICPGM must reside in *SYSBAS.
(This is just one more example.)

Each vendor or ISV product in use will be different -- some will fully
support IASPs and others may support IASPs only in a limited way, or not at
all.

Mark

On 10/3/2014 11:02 AM, Vernon Hamberg wrote:
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

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.