Hi folks: I have a V6R1 question that that deals with IFS placement I thought I would throw out there for the real gurus! My customer is moving from a V5R4 model 550 to a new V6R1 box and will be implementing a shared IASP storage pool for multiple partitions. They use Vision Solutions for mirroring.
They are asking if they should place the Application IFS directory in the IASP e new IASP or *SYSBAS.
Any suggestions?
Thanks! /George
Software/Hardware used:
iSeries, V6R1, Infinium
ASKED:
August 26, 2011 4:37 PM
UPDATED:
March 31, 2012 5:29 PM
If it’s an “Application IFS directory”, it needs to be in whatever ASP is available when the “Application” is started and during the time that it will be accessed. The application, of course, needs to be aware of the path wherever it leads.
I’m not sure there’s an easy way to answer the question without knowing more. Are the developers familiar with iASPs at all? Will there be any lead time to become familiar?
Tom
Thanks for the response, Tom. The developers here are not familiar with IASP, and frankly, I am not well versed either, from the Application standpoint. We will stick with *SYSBAS for now and see what happens.
Thanks again for all of your help.
A lot of the configuration elements may be external for an iASP. For example, the INLASPGRP() parameter of a job description can make a library name-space available to jobs, assuming that the iASP itself is available.
Certainly iASPs have their uses and can be extremely handy. But make sure that there is some experience before migrating any application to an iASP. In a sense, they can be similar to switching from the *LOCAL database to a remote database. Data can be stored and retrieved with the same program code as long as the connection is established before doing work. (Not a perfect analogy, but it can be useful for some concepts.)
Tom