|
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:stop
/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
you from using it.while
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:and
http://rd.radile.com/rdweb/info2/iasp01.html
At the same time I committed to a goal of ensuring that our web portal
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
yetstoring your "database objects" in IASPs that are linked to PowerHA forand
remote mirroring. However we store our ILE programs, service programs,
other native objects in IASPs too.well
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
someknown and been in the AS/400/iSeries/System i/IBM i space for quite
ittime. I was asking if the software they sell would run in an iASP so
SBMJOBcould be replicated by PowerHA.values,
Then I went on to discover that rather than use the job description
in all of the software the values were hard coded into the various
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
thesupport the new technology available. Clearly I will not identify
mailingcompany but geesh.
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
affiliatelist
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
listlistlink: http://amzn.to/2dEadiD--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
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
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
As an Amazon Associate we earn from qualifying purchases.
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.