Re: iASP security

I can confirm this, as well - once you go to using iASPs for multi-hosting - or for test setups vs prod setups - you must take some libraries out of *SYSBAS.

Now an idea could be to have the executables in a library in *SYSBAS and the data (changeable objects) in a different library - with that same library being in each iASP.

Or you could set up 2 iASPs where you put a copy of a product or application - licensing issues!!! - you could put a new version in the test iASP and have part of the signon process be a branch to one or the other, for production work or for testing.

This kind of usage is different from the HA stuff - just a different way to use iASPs.

At RJS there were a few customers who went the route of using iASPs, and they had no trouble. There are some kinds of objects that have to stay in *SYSBAS, so be careful about that.

Vern

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

On Fri, Oct 3, 2014 at 10:25 AM, Mark S Waterbury <
mark.s.waterbury@xxxxxxxxxxxxx> wrote:

All:

In this thread, a proposal being discussed in "multi-hosting" is the idea
that if each customer has their own IASP, they could potentially have the
same OS/400 library (*LIB) name(s) ... but I do not think this is true,
for the following reasons:

AFAIK, you cannot ever VARY ON an IASP if it contains a library name that
is already in *SYSBAS or in another IASP that is already varied on.

Perhaps someone can "test" this in an LPAR using virtual DASD to create
multiple IASPs (they could be small virtual disks, just one disk each, for
such a test), to experiment to prove this hypothesis empirically ...

I think support for IASPs was added to OS/400 mainly to support "High
Availability" with the ability to VARY OFF an IASP and then vary it on to
another LPAR (or another physical system, when using disk clusters) e.g.
to do "back-ups" of IASP1 while IASP2 is still "in use" ...

SUMMARY
Absent the ability to VARY ON two IASPs (dsk pools) that contain the same
library name, how could you ever have two jobs active at the same time on
the same OS/400 image (or LPAR) where one job access LIB1 in IASP1 and the
other job accesses LIB1 in IASP2? Because if IASP2 cannot be varied on, how
can you ever issue SETASPGRP to access it, or start a job with that IASP in
the *JOBD?

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.