IBM DB2 (AS/400) - Lineage
This article outlines the lineage coverage, configuration requirements, metadata handling, supported scenarios, component behaviors, transformation coverage, and known limitations for lineage extraction in IBM DB2 (AS/400). The connector enables SQL-based lineage extraction from DB2 datasets using a common lineage engine to provide table-level and column-level lineage visibility. It integrates DB2 datasets into the standard lineage pipeline (parse → build → visualize), enabling visibility into data flows across transformations and queries. Lineage accuracy depends on SQL compatibility with supported parser dialects.
Lineage Configuration Requirements
Accurate lineage extraction depends on DB2 connectivity, metadata availability, SQL accessibility, and lineage configuration settings. These requirements must be properly configured and available to ensure successful lineage generation and source-target resolution.
Configuration Requirements Table
DB2 (AS/400) Connection
A valid DB2 (AS/400) connection and crawler configuration must be available
Dataset Queries
Dataset queries must be available for lineage processing
connectionsPriorityForLineage
Connection priority settings must be configured to support accurate source and target object resolution during lineage processing
supportingDialects
Must include the appropriate SQL dialects required for parsing DB2 dataset queries
Query Log Integration
Query log integration can be enabled for query-based lineage extraction
Metadata Availability
A complete metadata crawl is required for schema and table resolution
Missing metadata, unavailable dataset queries, or incorrect dialect configuration may result in incomplete lineage generation or unresolved lineage paths.
Lineage Components
Tables
✅
Views
✅
Columns
✅
SQL Queries (Dataset-based)
✅
Query Logs (Connection Lineage)
✅
Stored Procedures
⚠️
Functions
⚠️
Triggers
⚠️
Dynamic SQL
⚠️
DB2AS400-specific Parsing
❌
Reports / ETL Tools
❌
The ⚠️ icon indicates partially supported functionality with limited lineage coverage in applicable scenarios.
Column Creation Support
This section outlines lineage support for column creation and transformation scenarios.
Column Creation from Lineage
Expressions
⚠️
Aggregations
⚠️
Calculated Fields
⚠️
Renamed Columns
✅
Temp Columns
⚠️
Semantic Columns
⚠️
The ⚠️ icon indicates partially supported functionality with limited lineage coverage in applicable scenarios.
Supported Use Cases
The connector supports lineage extraction for standard SQL-based DB2 workloads and query-driven transformations. These use cases represent scenarios where lineage extraction functions as expected.
Supported Lineage Scenarios
SQL-based Lineage from DB2 Datasets
Lineage extraction from the dataset SQL definitions
Table-to-Table Lineage
Lineage for standard SQL transformations
Column-Level Lineage
Lineage for SELECT, INSERT, and UPDATE queries
Incremental Lineage Processing
Incremental processing of lineage changes
Query Log-Based Lineage
Lineage generated from query log information
Views and Table Relationships
Relationships derived from SQL definitions and object references
Lineage extraction is based on SQL parsing and metadata available through datasets, query logs, and crawled database objects.
Partial or Limited Coverage
Certain scenarios provide only partial lineage coverage due to dialect limitations, parser dependencies, SQL complexity, or metadata resolution challenges.
Scenarios
DB2-specific Syntax
Coverage depends on the supported parser dialect compatibility
Stored Procedures and Functions
Lineage extraction is limited for procedural logic
Dynamic SQL and Runtime-generated Queries
Runtime-generated SQL may not be fully resolved
Complex Transformations and Nested SQL Logic
Complex logic may reduce lineage accuracy
Schema Resolution for Partially Qualified Objects
Object resolution may be incomplete
Trigger-based or Procedural Lineage
Limited support for procedural execution paths
Expressions
Expression-level lineage may be incomplete in complex scenarios
Aggregations
Aggregation lineage may not fully capture transformation details
Calculated Fields
Coverage depends on expression parsing success
Temporary and Semantic Columns
Column resolution may be incomplete when metadata is unavailable
Complex SQL patterns, dialect-specific syntax, and runtime-generated logic may result in incomplete table-level or column-level lineage.
Unsupported Scenarios
The connector does not support lineage extraction for certain DB2 AS/400-specific processing patterns and non-SQL lineage scenarios.
Unsupported Lineage
Non-SQL Lineage
Lineage outside SQL-based processing is not supported
XML-based Lineage Processing in DB Context
XML-based lineage generation is not supported
Full DB2 AS400 Dialect-Native Parsing
Native DB2 AS400 parsing capabilities are not available
Advanced Procedural Constructs or Macros Specific to AS400
AS400-specific procedural logic is not fully supported
Complete Lineage for Dynamic or Runtime-generated SQL
Runtime-generated SQL cannot be fully resolved
Unsupported scenarios will not produce lineage and may appear disconnected in lineage visualization.
Current Functional Status
This section outlines the present state of lineage coverage supported by the IBM DB2 (AS/400) connector based on the available capabilities and limitations.
Overall Coverage
Partial coverage across DB2 SQL workloads
Lineage Depth
Table-level lineage and limited column-level lineage support
Supported Inputs
Tables, views, SQL datasets, query logs, and supported database objects
Functional Scope
SQL-based lineage extraction using a common lineage engine
Limitation Areas
DB2-specific syntax, procedural logic, dynamic SQL, nested transformations, and AS400-native SQL constructs
Resulting Output
Reliable lineage for standard SQL workloads with reduced coverage for complex, dynamic, and DB2-specific scenarios
Coverage remains partial because lineage relies on a generic SQL parser with dialect fallback rather than DB2-specific parsing optimizations. This approach provides reliable SQL-based lineage for standard workloads but introduces limitations when handling complex transformations, dynamic SQL, procedural logic, and AS400-native SQL scenarios.
Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.
Last updated
Was this helpful?