Re: iASP

At one level the IASP is just a path in the IFS - so you might be able
to get the images by supplying a path tho them in the IFS that
includes the IASP device. something like
/iaspdevice/path/images/imagenam.jpg.

The IASP would need to be varied on so that you could get your images.

This would have some issues if it was the database but for images
might be workable.

Personally I'd reconsider having dev in *SYSBAS - to easy to have the
dev environment and the production IASP mounted in the same job.

On Wed, May 23, 2012 at 9:00 AM, Graap, Kenneth
<Kenneth.Graap@xxxxxxxxxxxxx> wrote:

What particular problem are you trying to solve ?

Right now I'm trying to decide how to configure my disk storage in preparation for an implementation of IBM PowerHA SystemMirror for i ...

I'm currently thinking I'll move the Production Application in to and iASP with the Journal Receivers in a Secondary iASP. These iASP's would be mirrored.

Our Development environment would be kept in a *SYSBAS ASP along with common system programs and tools, and not mirrored.

Then I have about a Terabyte of customer Bill Images that I currently store in a separate *SYSBAS ASP. I was thinking about storing these in another iASP and mirroring it since in a recovery scenario it takes DAYS and DAYS to restore these millions of small files. But once I have them mirrored, the only changes would be adding and deleting a gigabyte or 2 a day.

So my question was if I'm running my application out of one iASP, could those jobs "easily" access data in the iASP full of Bill Images, when they need to view one?


Reply or Forwarded mail from: Kenneth E Graap