Re: What's an IASP?

Jim:

The only requirement for "/dev/IASPname/" in the path name is for naming the *BLOCKSF when creating a UDFS.

Prompt the CRTUDFS command and press F1=Help in the UDFS (first) input field.


Once the UDFS is created, you can mount it anywhere in the IFS directory tree. For example:

mount type(*UDFS) mfs('/dev/MYIASP/MYUDFS.udfs') mntovrdir('/myspace')

where "myspace" is an empty directory in the root of the IFS (in this example).

Prompt the MOUNT command and press F1=Help, then F2= Extended Help, and page down to the section on MFS and MNTOVRDIR.

So, then, once mounted, we can refer to files within this UDFS as:

/myspace/zero-or-more-subdirectories/target-streamfile.name

Hope that helps to clarify the situation.

Mark S. Waterbury

> On 6/13/2013 7:39 AM, Jim Oberholtzer wrote:

...(snip)...

James, the biggest issue with iASP and the application is to remember
that work management to the extent you need to worry about it does
change. You have to be sure each job has the iASP set properly, which
is easy to do but requires an extra step. Also referring to the IFS
changes since you will have to set the path as
'/myiASP/nowmydirectorystring/whatever' so the IFS objects are found in
the iASP IFS instead of *SYSBAS. A few symbolic links can ease that
effort quite a bit.

...(snip)...