IBM Db2 for IBMi - Precisely Data Integrity Suite

Data Integrity Suite

Product

Spatial_Analytics

Data_Integration

Data_Enrichment

Data_Governance

Precisely_Data_Integrity_Suite

geo_addressing_1

Data_Observability

Data_Quality

dis_core_foundation

Services

Spatial Analytics

Data Integration

Data Enrichment

Data Governance

Geo Addressing

Data Observability

Data Quality

Core Foundation

ft:title

Data Integrity Suite

ft:locale

en-US

PublicationType

pt_product_guide

copyrightfirst

2000

copyrightlast

2026

Set up IBM Db2 for IBM i as a data connection for replication pipelines in the Data Integrity Suite, including replication options, manual installation of required Db2 packages, and system restore configuration.

Before you configure IBM Db2 for IBMi as a replication connection, ensure you have the following:

IBM Db2 for IBMi database server hostname or IP address
Database port number (default is 446)
Database location name
User credentials (username and password)
An agent configured to access the database
Knowledge of whether IASP (Independent Auxiliary Storage Pool) is enabled

IBM Db2 for IBM i supports both continuous data replication and mainframe data replication. You can configure this connection as both a source and target for replication pipelines.

In the Data Integrity Suite, navigate to Datasources.
Click Add connection or select an existing PostgreSQL connection to edit.
For detailed configuration instructions, refer to the IBM Db2 for IBMi documentation.
Toggle ON the replication option to use the conenction in replciation pipelines

Complete the following fields for replication:

IBM Db2 for IBM i supports two types of replication connections:

Continuous data replication
Mainframe data replication

Table 1. IBM Db2 for IBMi Replication Configuration Fields
Field	Description
Replication Engine	Select the type of replication connection: Continuous Data Replication Connection Mainframe Data Replication Connection
Installation Library	Specify the library where the replication engine is installed.
Additional Runtime URL parameters	Available for replication pipeline purposes.

Click Test Connection to verify that the connection is configured correctly.
Click Save to save the IBM Db2 for IBMi replication connection.

You've successfully configured IBM Db2 for IBMi as a replication connection. The connection is now available for use in replication pipelines. You can now create or edit replication pipelines that use this IBM Db2 for IBMi connection as a source or target.

Manually install Db2 packages for IBM i

When a Db2 for i (Db2i) database is used for the first time by the Progress JDBC driver, the driver automatically creates all required Db2 packages in the NULLID collection (library), provided the user has BINDADD privilege. Manual intervention is not required in most cases.

However, if automatic package creation fails or you need explicit control over the process, follow these steps to download and install the packages manually.

Important: The user ID creating the Db2 packages must have BINDADD privilege on the database. Consult your database administrator to confirm that the user has the necessary privileges. For more information, see IBM Documentation: GRANT (Package Privileges).

Download the save files from the Progress iSeries Save Files repository.
Create a library on your IBM i system by running the following command:
```
CRTLIB MYLIB
```
Create a save file in the library by running the following command:
```
CRTSAVF MYLIB/DDJV6R1
```

Transfer the save file to your IBM i system using FTP in binary mode.

Select the file appropriate for your IBM i version:

V7R1: DDJV7R1.savf
V6R1: DDJV6R1.savf
V5R4: DDJV5R4.savf
V5R3: DDJV5R3.savf
V5R2: DDJV5R2.savf

Use the following FTP commands:

ftp> bin
200 Representation type is binary IMAGE.
ftp> put DDJV6R1.savf /qsys.lib/mylib.lib/DDJV6R1.savf
200 PORT subcommand request successful.
150 Sending file to member DDJV6R1 in file DDJV6R1 in library MYLIB.
226 File transfer completed successfully.

(Optional) Verify the save file transfer by logging in to your IBM i system and running the following command:

DSPSAVF MYLIB/DDJV6R1

This command displays the saved objects. You should see output similar to the following:

Display Saved Objects
Library saved . . . . . . . : NULLID
Type Options press Enter.
5=Display
Opt   Object    Type    Attribute Owner        Size (K)   Data
DDJC510A  *SQLPKG PACKAGE   NCDDTEK            96   YES
DDJC510B  *SQLPKG PACKAGE   NCDDTEK           100   YES
DDJN510A  *SQLPKG PACKAGE   NCDDTEK            96   YES
DDJN510B  *SQLPKG PACKAGE   NCDDTEK           100   YES
DDJR510A  *SQLPKG PACKAGE   NCDDTEK            96   YES
DDJR510B  *SQLPKG PACKAGE   NCDDTEK           100   YES
DDJS510A  *SQLPKG PACKAGE   NCDDTEK            96   YES
DDJS510B  *SQLPKG PACKAGE   NCDDTEK           100   YES
DDJU510A  *SQLPKG PACKAGE   NCDDTEK            96   YES
DDJU510B  *SQLPKG PACKAGE   NCDDTEK           100   YES

If necessary, create the NULLID library by running the following command:
```
CRTLIB NULLID
```
Restore objects into the NULLID collection by running the following command:
```
RSTOBJ OBJ(*ALL) SAVLIB(NULLID) DEV(*SAVF) SAVF(MYLIB/DDJV6R1)
```

Grant execute privileges to the PUBLIC group for all packages by running the following commands:

GRANT EXECUTE ON PACKAGE NULLID.DDJR510A TO PUBLIC
GRANT EXECUTE ON PACKAGE NULLID.DDJR510B TO PUBLIC
GRANT EXECUTE ON PACKAGE NULLID.DDJS510A TO PUBLIC
GRANT EXECUTE ON PACKAGE NULLID.DDJS510B TO PUBLIC
GRANT EXECUTE ON PACKAGE NULLID.DDJU510A TO PUBLIC
GRANT EXECUTE ON PACKAGE NULLID.DDJU510B TO PUBLIC
GRANT EXECUTE ON PACKAGE NULLID.DDJC510A TO PUBLIC
GRANT EXECUTE ON PACKAGE NULLID.DDJC510B TO PUBLIC
GRANT EXECUTE ON PACKAGE NULLID.DDJN510A TO PUBLIC
GRANT EXECUTE ON PACKAGE NULLID.DDJN510B TO PUBLIC

You've successfully installed the Db2 packages on your IBM i system. The packages are now available in the NULLID collection and ready for use by the Progress JDBC driver.

IBM i system restore configuration for SQLPKG objects

When restoring save files containing SQLPKG objects on the same IBM i system and the same OS release, you must configure specific system values and restore parameters. This ensures compatibility and improves restore efficiency.

Configure the QALWOBJRST system value.
Initial Value: QALWOBJRST = *ALWPTF (default and secure setting)

Required Value for NULLID Restoration: For restoring objects associated with NULLID, the system value must temporarily allow all object restores.

Run the following command to change the system value:
```
CHGSYSVAL SYSVAL(QALWOBJRST) VALUE(*ALL)
```
Important: This change is required only during the restore operation.

Post-Restore Action: After the restore is complete and the new connection is created, revert the system value back to its original setting:
```
CHGSYSVAL SYSVAL(QALWOBJRST) VALUE(*ALWPTF)
```
Restore Parameter: QFRCCVNRST (Force Conversion on Restore)
- Allowed Values:
  - *NO
  - *YES
- Recommended Value (Same System / Same Release): QFRCCVNRST(*NO)
- Rationale: When restoring on the same IBM i system and the same OS release, no object format conversion is required. *SQLPKG objects are already compatible with the target environment. Using *YES will not cause a failure, but it is unnecessary and adds extra processing.

Configure the restore parameters as described in the following table:

The following table describes the recommended restore parameters for SQLPKG objects:

Table 2. Recommended Restore Parameters for SQLPKG Objects
Parameter	Value	Reason
QALWOBJRST	*ALL (temporary)	Required for NULLID restoration
QFRCCVNRST (Force Conversion on Restore)	*NO	When restoring on the same IBM i system and the same OS release, no object format conversion is required. SQLPKG objects are already compatible with the target environment. Using *YES will not cause a failure, but it is unnecessary and adds extra processing.
QVFYOBJRST (Verify Object on Restore)	*NONE	SQLPKG objects are not digitally signed and do not behave like program objects such as PGM or SRVPGM. Signature verification provides no benefit for SQL packages. Disabling verification avoids unnecessary checks and improves restore efficiency.
QSAVACCPTH	*NO (recommended)	Access paths are rebuilt if required

You've successfully configured the system values and restore parameters for SQLPKG object restoration on your IBM i system.