IBM Support

Specifying ASP When Using Integrated File System

Troubleshooting


Problem

This document explains a process for specifying a specific ASP to be used with Integrated File System commands and APIs.

Resolving The Problem

Integrated File System commands, such as MKDIR, and Integrated File System APIs do not provide an option to specify which ASP to use. This is because UNIX/POSIX APIs, on which Integrated File System APIs are based, do not have a concept of ASP. The following steps show how you can use a particular ASP when using Integrated File System APIs or commands on an IBM System i system.

To determine if you have multiple ASPs on the IBM i OS System, on the operating system command line type the following:

WRKLNK OBJ('/DEV')

Press the Enter key. Select Option 5 to move to the Next Level.

If your system has only one ASP, you will see only QASP01. Otherwise, you will see additional QASP0x links (where x = the ASP number). You can have as many as 98 user ASPs, plus one system ASP on the System i system.

Note: The System i system must be IPLed for the Integrated File System to recognize a new auxiliary storage pool (ASP) if you create a new ASP IPL is required before you can continue with the CRTUDFS Command.

Before you can use a particular ASP from Integrated File System, a User-Defined File System (UDFS) must be created in that ASP. To create the UDFS on the operating system command line, type the following:

CRTUDFS UDFS('/DEV/QASP02/ASP02.UDFS') DTAAUT(*RWX) OBJAUT(*ALL) CASE(*MONO)

Notes:
1. Run the above command one time only.
2. To have the file system case-sensitive, select *MIXED; however, this is not recommended. This command creates an User-Defined File system called ASP02 in ASP02.
3. Before using this file system, it must be mounted using the MOUNT command. Mount is not preserved across IPLs. Therefore, you must mount after every IPL. It is recommended that you place the MOUNT command in the start-up program for the system.
Next create the Directory to be mounted over:

MKDIR DIR('/M1')

It is recommended that you do not use Object-Link '/M1' when the file system is not mounted. If you created Object Links under '/M1', those are no longer available when the UDFS is mounted over this directory (Note they are not deleted but the path will be point to the udfs and not the local path).

To mount the User-Defined File System on a object-link '/M1', type the following on the operating system command line:

MOUNT TYPE(*UDFS) MFS('/DEV/QASP02/ASP02.UDFS') MNTOVRDIR('/M1')


Once the UDFS is mounted, you can create new links that will be stored in ASP02. For example, the following command creates a directory in ASP02, and the second command copies a CL source file there:

MKDIR DIR('/M1/ALAM')

CPYTOSTMF FROMMBR('/QSYS.LIB/QGPL.LIB/QCLSRC.FILE/QSTRUP.MBR') +
TOSTMF('/M1/ALAM/STRUP.TXT') DBFCCSID(037) STMFCODPAG(437)


The file system is unmounted during IPL or you can use the following command when you are done:

UNMOUNT TYPE(*UDFS) MFS('/dev/QASP02/ASP02.UDFS')

[{"Type":"MASTER","Line of Business":{"code":"LOB68","label":"Power HW"},"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m0z0000000CGvAAM","label":"Integrated File System"}],"ARM Case Number":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"All Versions"}]

Historical Number

10764513

Document Information

Modified date:
10 July 2024

UID

nas8N1018454