Re: [Bulk] Re: iASP security

+1

On 10/3/2014 11:30 AM, Jim Oberholtzer wrote:

As Mark pointed out some of those APIs require some heavier lifting the
first time you use them. After you have the shell created, it's not as bad
of an effort to produce PTFs. Anyone that has delved into APIs have the
skills needed to produce an LPP and use the APIs. The difference between an
LPP that uses iASP and one that does not is not significant. So my
statement stands, just because there is an iASP in the LPP only complicates
it by very small amounts and therefore the differences are 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 11:18 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: [Bulk] Re: iASP security [PRIVATE REPLY]

Hi, All:

I was going to reply privately, but then I changed my mind and forgot to
remove the "PRIVATE REPLY" tags -- sorry for any confusion caused.

In any case, though it is possible to support IASPs using e.g.RSTLICPGM, it
is not automatic because you must write programs that conform to IBM
specifications for exit programs for SAVLICPGM/RSTLICPGM and the PTF
processing exits. And that is a non-trivial effort. That's all I was trying
to say.

Mark S .Waterbury

> On 10/3/2014 11:59 AM, Mark S Waterbury wrote:

Jim:
* >>>---> private reply off-list <---<<<*

To support installing an LPP's objects into an IASP, you must code
IBM-supplied exit programs that work with those software packaging
APIs and the RSTLICPGM command, and these exits are not very
well-documented.

The process is even worse when creating, loading and applying PTFs for
your own LPPs. All LPP objects to be PTFed _must exist_ in *SYSBAS.
Then, you have to use a PTF exit program to optionally replicate some
or all of those objects into one or more IASPs -- but, this hardly
what I would call /a trivial exercise/ by any stretch of the imagination.

Mark S. Waterbury

--
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.