Re: Getting products to run in IASPs

[Evan Harris <auctionitis@xxxxxxxxx>]

Hi Nathan

the only tip I can recommend is that JOBd become very important; you need
to have the INLASPGRP set in those and grouping them or managing them
(maybe by an application library) is pretty important.

I think if I was engineering this again I would think about using the
JOBD/INLASPGRP thing to set the IASP for anythign that was gogni to live
out it's entire life in one IASP. For anything else I would maybe use
SETASPGRP to allow setup of an environment as required,

Vern mentioned the RDB entry; this is important for environments that use
ODBC or similar connections a lot as the database name becomes a
significant part of the connection string. So you might need multiple
connections or connection strings where there are multiple IASPs.



On Fri, Jan 12, 2018 at 9:45 AM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

> It takes some work. I've learned that much by trial and error. The purpose
> of this discussion is to share tips about getting products to run in IASPs.
>
> In a prior discussion I asked about the pros and cons of using IASPs. I
> concluded that the pros outweighed the cons. Now I'm testing that
> hypothesis. If we're using IASPs in our development environment, I figure
> we'll be able to support IASPs at customer sites.
>
> I've configured 3 IASPs, so far. I have a number of use cases in mind. I
> saved non-IBM product libraries from *SYSBAS, deleted them, then restored
> them to IASPs. That part works. No problem having the same library names in
> multiple IASPs and using SETASPGRP to switch between them.
>
> While attempting to get our products to run, I discovered that our Our HTTP
> server configurations needed to be changed to reference objects in IASP
> directories.
>
> I discovered that application-specific  job queues, job descriptions,
> message queues, subsystem descriptions, and subsystem-class definitions
> needed to be moved back into *SYSBAS in order to use IBM i commands like
> STRSBS, SBMJOB, and others that utilize such configuration objects.
>
> I envision changing some application-specific commands to optionally prompt
> for IASP name in order to install and configure product environments.
>
> Do you have any other tips or gotchas to share?
> --
> 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