IBM Db2 for z/OS lineage configuration
To import lineage metadata from IBM Db2 for z/OS, create a connection, data source definition and metadata import job.
Db2 for z/OS is an enterprise data server for IBM Z. It manages core business data across an enterprise and supports key business applications.
Supported IBM Db2 for z/OS versions
- IBM Db2 for z/OS 12 and 13
Processed metadata
The following IBM Db2 for z/OS metadata is processed and displayed in lineage:
- Data dictionaries
- Scripts
- Stored procedures
- SQL
- Modules
- Functions
- Triggers
- Views
- Packages
- Aliases / Synonyms
- Oracle compatibility mode
Limitations
- You can do data lineage import for Db2 for z/OS only with Db2 Connect Unlimited Edition for System z, activated through the Activation Program. Other Db2 for z/OS configurations that require a JDBC license JAR are not supported.
Prerequisite configuration
Before you import lineage metadata, ensure that the following prerequisites are met:
- You have the following rights:
- CONNECT ON DATABASE
- SELECT on the following system tables and views:
SYSIBM.SYSCOLUMNSSYSIBM.SYSDATATYPESSYSIBM.SYSDEPENDENCIESSYSIBM.SYSDUMMY1SYSIBM.SYSFOREIGNKEYSSYSIBM.SYSINDEXESSYSIBM.SYSKEYSSYSIBM.SYSPACKSTMTSYSIBM.SYSPARMSSYSIBM.SYSRELSSYSIBM.SYSROUTINESSYSIBM.SYSSCHEMAAUTHSYSIBM.SYSSEQUENCESSYSIBM.SYSTABLESSYSIBM.SYSTRIGGERSSYSIBM.SYSVARIABLESSYSIBM.SYSVIEWS
- SELECT on the following special registers:
CURRENT CLIENT_WRKSTNNAMECURRENT MEMBERCURRENT SERVER
- BIND ON PACKAGE
nullid.db2lksp
Creating a metadata import asset
Data source connection
To connect to the data source from which you want to import lineage metadata, you need to select a data source definition and a connection. You can create them before you start creating the metadata import, or you can create them when you create and configure the metadata import asset.
Data source definition
Śelect IBM Db2 as the data source type.
Connection
For connection details, see IBM Db2 for z/OS connection.
Connection mode
You can connect to Db2 for z/OS by using one of the following connection modes:
- Direct connection
- Remote connection with a Manta agent. When an agent is configured, select it from the list. For more information, see Configuring agents for lineage metadata import.
Include and exclude lists
You can include or exclude assets up to the schema level. Each value is evaluated as a regular expression. Assets which are added later in the data source will also be included or excluded if they match the conditions specified in the lists. Example values:
mySchema:mySchemaschema.mySchema[1-5]: any schema with a name that starts withmySchemaand ends with a digit between 1 and 5.
External inputs
If you use external Db2 PL/SQL scripts, you can add them in a .zip file as an external input. You can organize the structure of a .zip file as subfolders that represent schemas. After the scripts are scanned, they are added under respective schemas in the selected catalog or project. The .zip file can have the following structure:
<schema_name>
<script_name.sql>
<script_name.sql>
replace.csv
The replace.csv file contains placeholder replacements for the scripts that are added in the .zip file. For more information about the format, see Placeholder replacements.
Advanced import options
- Extract extended attributes
- You can extract extended attributes like primary key, unique and referential integrity constraints of columns. By default these attributes are not extracted.