Re: What's an iASP?

Sure, all the replication vendors including IBM have that analysis it will, however, be slanted analysis.

Keep in mind the PowerHA come in two varieties, whole system replication and iASP replication. iASP is closer to application replication since it does not cover the OS and things in *SYSBAS. The application replication products can replicate more of *SYSBAS than PowerHA can, points for that.

On the other side PowerHA can replicate the entire partition, however that requires either i hosting i, or SAN storage. The thing I really like about SAN storage and PowerHA is you can let the SAN do the replication removing that workload from the partition. And on the same communication line it's faster too.

Disk storage, about the same in both. Journaling in both varieties is an absolute must have, but with PowerHA you can use system managed journals. The App replications mostly have journal management built in. Those two are a wash.

RTO/RPO are about the same too, within minutes of each other, the difference there being with PHA and partition replication the recovery point will always be as of the break in communication, so basically real time.

Role swap, not much difference there either.

Costs vary wildly based on how good you are at negotiating, except for IBM, it has a price per core.

iASP implementation can be tricky depending on the OEM software vendors, (the start of this thread) as many of them are still living in the V5R4 days with lots of excuses. Experience counts there.

All the other vendors are about even in the set up realm so not real differences there.

Before all the vendors start getting on my case, my customers have most all of the different packages installed so I get real time experience not Lab experience and that's what drives my observations. Do I have a favorite sure, but that's for a different discussion.

Jim Oberholtzer
Agile Technology Architects

On Aug 15, 2018, at 3:12 AM, Jack Kingsley <iseriesflorida@xxxxxxxxx> wrote:

Has there been any analysis done on the benefits of IASP compared to
application replication.


- Time to install
- Costs overall
- Disk storage needs
- Journal management
- RTO/RPO
- Role swap functionality
- Etc.

On Tue, Aug 14, 2018 at 7:35 PM, Evan Harris <auctionitis@xxxxxxxxx> wrote:

Hi Nathan

I understand where you are coming from, but I still disagree with your
premise.

At one client I worked with we created a command that was analogous to the
SETASPGRP command that among other things set a "root path" property value
so that applications could write to the IFS in the relevent IASP.
Conceptually we had a command that provided some context to what
environment the application was operating in and which IASP path should be
used.

I might be missing something but even though you have to roll your own tool
and maybe observe some minor conventions, it's not really any more
difficult than the SETASPGRP command.

On Wed, Aug 15, 2018 at 11:11 AM, Nathan Andelin <nandelin@xxxxxxxxx>
wrote:

Evan and Jim,

Thanks for your input regarding the IFS. However, my understanding is

that

there is a relevant distinction in regard to IASP support for Libraries

in

that any number of libraries may be created and stored in an IASP and
referenced from library lists, whereas there is only one IFS directory in
the root file system that becomes available when an IASP is varied on.

The SETASPGRP command provides a slick way of switching Jobs from one

IASP

to another without changing references to libraries. But in the case of

the

one IFS directory that pertains to its IASP, the directory name is the

same

as the IASP name. It's often harder for applications to change references
to IFS directories.



On Tue, Aug 14, 2018 at 4:18 PM, Jim Oberholtzer <
midrangel@xxxxxxxxxxxxxxxxx> wrote:

iASP has IFS just the same as SYSBAS objects do. The path is:
/iaspname/mydir1 /iaspname/mydir1/mydir2

If you absolutely need to access IFS object from the root rather than

the

iASP directory, then you put a symbolic link in. IE:

ln -s /iasp/mydir1/ /mydir1/

By doing it this way PowerHA will ensure the entire IFS in the iASP is
replicated right along with the QSYS.LIB objects.

By the way the path to the QSYS.LIB objects in the iASP is:
/iaspname/qsys.lib/mylib.lib.

So if you think about it there is no limitation on the IFS that should

stop

you from using it.



Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects

On Tue, Aug 14, 2018 at 4:43 PM, Nathan Andelin <nandelin@xxxxxxxxx>
wrote:

Last year I listed some of the benefits of IASPs in the following

link:

http://rd.radile.com/rdweb/info2/iasp01.html

At the same time I committed to a goal of ensuring that our web

portal

and

applications would support them, which has been something of a

journey.

In regard to "software", a good chunk of it stored in IFS stream

files

these days, whereas IASPs are only designed for Libraries. If you

have

"software" in Libraries, technically that might be stored in SYSBAS

while

storing your "database objects" in IASPs that are linked to PowerHA

for

remote mirroring. However we store our ILE programs, service

programs,

and

other native objects in IASPs too.

A few of our software components such as subsystem descriptions and

Job

descriptions must be stored in SYSBAS in order to work.









On Tue, Aug 14, 2018 at 1:39 PM, Jim Oberholtzer <
midrangel@xxxxxxxxxxxxxxxxx> wrote:

That question was just asked of me by an OEM software vendor that

is

well

known and been in the AS/400/iSeries/System i/IBM i space for quite

some

time. I was asking if the software they sell would run in an iASP

so

it

could be replicated by PowerHA.

Then I went on to discover that rather than use the job description

values,

in all of the software the values were hard coded into the various

SBMJOB

commands in the software.

How do these guys stay in business?

If you are an OEM software vendor, at least try and keep up with

the

terminology so you don't sound as ignorant as this one is. Better

yet

support the new technology available. Clearly I will not identify

the

company but geesh.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects
--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our

affiliate

link: http://amzn.to/2dEadiD

--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our

affiliate

link: http://amzn.to/2dEadiD

--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

--

Regards
Evan Harris
--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD