Skip to main content

Masking Engine Requirements for DB2 on Mainframe zOS (KBA1543)


With the Illium release of the Masking Engine, support for DB2 on the Mainframe/zOS has been re-instated using IBM's JDBC Type 4 Driver (db2jcc4.jar), which is re-distributed with the Masking Engine. 

However, a DB2 Connect license from IBM must be supplied by the customer in order for the Masking Engine to connect to DB2 on the Mainframe using this driver. You can use the "Mainframe DB2" connector to create DB2 on the Mainframe rulesets only after the DB2 Connect license is activated for the Masking Engine. The following types of jobs can be run against their rulesets:

  • Profiling

  • Masking In-Place (Batch Update and Bulk Data options available)

  • Masking On-the-Fly (Batch Update and Truncate options available)

  • Tokenization and Re-Identification

  • Certify

  • Provisioning by Masking Engine

Troubleshooting DB2  Connector

If the Masking Engine fails to connect to DB2 on the Mainframe, you should perform Test Connection on the Edit Connector: Mainframe DB2 screen:


If you encounter the following message as indicated below, this shows that a DB2 Connect license has not been activated for the Masking Engine:



You can use any licensed edition of DB2 Connect:

  • Personal Edition 
  • Enterprise Edition 
  • Application Server Edition
  • Unlimited Edition

Each of these editions appear to use one of two DB2 Connect licensing schemes: 

  • IBM DB2 Connect Activation Package for unlocking the mainframe to client applications (e.g.,
  • IBM DB2 Client license installed with the client application (db2jcc_license_cisuz.jar) 

If you use a DB2 Connect Activation package that has not been previously activated for their client applications, the Activation package needs to be extracted and executed on any customer system with TCP/IP connectivity to the mainframe. 
For example, on a Linux system for a customer licensed  for DB2 Connect Unlimited Edition, you need to:

  1. unzip 
  2. cd consv_zs/db2/license
  3. ./ -host <hostname> -port <portnumber> -database <dbname> -user <dbuser> -password <userpassword>
    hostname = host running DB2 on the mainframe
    portnumber = port number for DB2 on the mainframe

    If the customer uses a DB2 Connect Client license, they must download and copy (using sudo) their db2jcc_license_cisuz.jar to the following locations on the Masking Engine:
  • /opt/delphix/dmsuite/tomcat/webapps/dmsuite/WEB-INF/lib (for the Masking Engine UI)
  • /opt/delphix/dmsuite/DMSApplicator/libext/JDBC (for Kettle job execution)


Related Articles

External Links: