Re: Single-System Independent Auxiliary Storage Pools

It does support small virtual disks, we do it all the time! You just need a hosting partition of some flavor to host said disks.

Your list is excellent and all are valid.

Additional pros

A) your library list can be the same for multiple companies or test - vs - dev - vs - prod just switch the asp group used. Same as an LPAR but with much less work.

B) You can do backups by IASP. Again same as LPAR but less work.

Additonal cons

A) Compared to LPARs you MUST take everyone down to do PTFs.

B) You MAY need multiple QBATCH and QINTER subsustems to support the various iASPS. Not a lot different than LPARS but actual changes required to subsystems.

C) IFS use can be tricky. If not careful you could be crushing stuff in your other IASPS if you use links rather than code your applications with the the IASP path links.


- Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.

On 12/6/2017 3:41 PM, Nathan Andelin wrote:

I've been reading about IASPs at:

https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_73/rzaly/rzalypdf.pdf?view=kc

Along with reading archived discussions.

IASPs are fundamental component of PowerHA and Geographic Mirroring. But
what about using them alone on a single system? Are there pros and cons?

The biggest con appears to be that they require a disk drive (2 for
mirrored protection), for each IASP. A case could be made to enhance IBM i
to support small internal virtual disks.

A number of use cases come to mind.

1. Reduce IPL time by separating application IASPs from SYSBAS.
2. Reduce SAVSYS time by separating application IASPs from SYSBAS.
3. Host multiple versions of applications by dividing them between IASPs.
4. Host an open-source project and external developers on an IASP (easy to
secure).
5. Use an IASP version of your application to create an installation
package.

Can you think of IASP pros and cons, compared to separate libraries and
directories, or compared to LPARs?