About cookies on this site Our websites require some cookies to function properly (required). In addition, other cookies may be used with your consent to analyze site usage, improve the user experience and for advertising. For more information, please review your options. By visiting our website, you agree to our processing of information as described in IBM’sprivacy statement. To provide a smooth navigation, your cookie preferences will be shared across the IBM web domains listed here.
Troubleshooting
Problem
A IASP 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 may not change from *REMOTE to *LOCAL.
If this occurs, check the joblog from when the IASP was varied on and see if any error messages were logged.
[{"Product":{"code":"SWG60","label":"IBM i"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"General Information","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"Version Independent","Edition":"","Line of Business":{"code":"LOB57","label":"Power"}}]
Was this topic helpful?
Document Information
More support for:
IBM i
Software version:
Version Independent
Operating system(s):
IBM i
Document number:
646251
Modified date:
18 December 2019
UID
nas8N1020711
Manage My Notification Subscriptions