Troubleshooting
Problem
An iASP (independent auxiliary storage pool) can show as available and still not be available for use by applications using ODBC, JDBC, etc.
Diagnosing The Problem
The IBM i system will create a relational database directory entry when a IASP is created with the relational database name the same as the IASP name.
Displaying the detail on a IASP RDB entry will show the following before the IASP is varied on:
Note the Relational database type parameter shows *REMOTE.
When a IASP is varied on, the Relational database type will change to *LOCAL as shown below:
Notice the ASP group, ASP group status, and ASP group number parameters are also added when the IASP is varied on.
If a error occurs when the IASP is varied on, it is possible for the database part to not be active even though the IASP shows available.
The Relational database type might not change from *REMOTE to *LOCAL.
If this occurs, check the job log from when the IASP was varied on and see if any error messages were logged.
Use command DSPDEVD DEVD(<iASP device name>) to check the Relational Database parameter to see which RDB entry the iASP will point to when varied on.
Was this topic helpful?
Document Information
Modified date:
24 April 2026
UID
nas8N1020711