Re: [Bulk] Re: [Bulk] Re: iASP security -- MIDRANGE-L

Subject: Re: [Bulk] Re: [Bulk] Re: iASP security
From: Mark S Waterbury <mark.s.waterbury@xxxxxxxxxxxxx>
Date: Fri, 03 Oct 2014 11:13:38 -0400
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

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

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: [Bulk] Re: [Bulk] Re: iASP security , Jim Oberholtzer
Re: [Bulk] Re: [Bulk] Re: iASP security , Vernon Hamberg

This mailing list archive is Copyright 1997-2024 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 [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.