Preflight checks for IBM Db2 for z/OS
Before running the IBM Db2 for z/OS crawler, run preflight checks to perform necessary technical validations.
Before running the IBM Db2 for z/OS crawler, you can run preflight checks to perform the necessary technical validations. The following preflight checks are completed:
Connectivity check
Verifies that Atlan can reach your subsystem and confirms it's a Db2 for z/OS system by reading the product version.
✅ IBM Db2 for z/OS version: $version
❌ Version string '$version' does not start with 'DSN' — the endpoint may not be a IBM Db2 for z/OS system; verify the connection URL
❌ Version check failed: $error
A version string that doesn't begin with DSN means the connection reached a Db2 server that isn't a z/OS subsystem. Use the IBM Db2 for LUW connector for a Db2 for Linux, UNIX, and Windows server.
Common connection failures include SQL30081N when the host, port, or DDF status is wrong, SQL30082N when the credentials are rejected, and ERRORCODE=-4230 when a Db2 Connect 12.1 license isn't activated for the subsystem. See the setup steps for each prerequisite.
Permissions check
Verifies that the authorization ID can read the Db2 system catalog.
✅ All required catalog permissions verified
❌ SELECT permission denied (vendor error -551): $error
⚠️ Skipped — connectivity failed
A -551 failure means the authorization ID can't read one of the catalog tables Atlan queries - check the catalog privileges.
Object count check
Counts the non-system schemas that match the include and exclude filters.
✅ Found $schemaCount non-system schemas
❌ No non-system schemas are visible — nothing would be crawled. Verify the login's catalog visibility and the include/exclude filter.
⚠️ Skipped — permissions check failed
⚠️ Skipped — connectivity failed
See also
- Crawl IBM Db2 for z/OS: Run the crawler after preflight checks pass
- Set up IBM Db2 for z/OS: Configure connection and authentication