User-defined file system and independent auxiliary storage pools

 

When you vary on an independent auxiliary storage pool (ASP), several changes occur within the "root" (/) file system.

These changes are:

• A directory is created inside the /dev directory for the independent ASP. The name of this directory matches the name of the device description associated with the ASP. If this directory exists before the vary on request, and this directory is not empty, then the vary on will proceed but you will not be able to work with any UDFS's on the ASP. If this occurs, vary off the independent ASP, either rename the directory or remove its contents and then try the vary on request again.

• Within the /dev/asp_name directory you will find the block special file objects associated with all UDFS's that reside on the independent ASP. There will always be a system-provided default UDFS. The path to the default UDFS's block special file is: /dev/asp_name/QDEFAULT.UDFS

• The default UDFS is mounted over the directory /asp_name. The /asp_name directory does not need to exist before the vary on request. However, if it does exist, it must be empty. If it is not empty, the ASP will still be varied on, but the default UDFS will not be mounted. If this occurs, either rename the directory or remove its contents and then either vary off and try the vary on again or use the MOUNT command to mount the default UDFS.

• If the independent ASP is either a primary or secondary ASP, and the default UDFS was successfully mounted, then an additional file system will be mounted. The independent ASP QSYS.LIB file system will be mounted over /asp_name/QSYS.LIB.

  This file system cannot be mounted or unmounted independently of the default UDFS. It will always be mounted or unmounted automatically.

 

Parent topic:

User-defined file systems (UDFSs)

 

Related reference

Independent ASP QSYS.LIB