Built-in DB2 z/OS driver support plugin

For instructions on how to enable/disable Drop Constraints and Drop Triggers on DB2 z/OS jobs, see API Calls for Managing Masking Job Driver Support Tasks.

Unlike other database platforms, DB2 does not support disabling constraints or triggers. Therefore, this plugin has Drop Constraints and Drop Triggers tasks.

Tasks

For in-place jobs:

  1. Drop Constraints drops and re-creates constraints on masked columns only.

  2. Drop Triggers drops and re-creates triggers on tables with masked columns only.

For on-the-fly jobs, the tasks will execute on all columns and tables in the ruleset.

Task execution order

The order of task execution for built-in driver support plugins is fixed/unmodifiable.

The order of the tasks is as follows:

Pre-job:

  1. Drop Constraints

  2. Drop Triggers

Post-job (mirrored order):

  1. Create Triggers

  2. Create Constraints

Important considerations

  1. There is no Drop Indexes task available.

  2. If masking primary key fields, use the same deterministic algorithms on primary key fields that reference each other so that referential integrity is maintained when the masking transformation completes and all constraints are re-created.

Known limitations

  1. Drop Constraints is unable to detect or drop foreign key constraints with PERIOD BUSINESS_TIME in their keys.

  2. Foreign key constraints dropped and recreated by Drop Constraints will not have the ENABLE QUERY OPTIMIZATION clause if originally specified.

  3. If both a foreign key column and the primary key or unique column it references are not masked with the same deterministic algorithm (guaranteeing referential integrity), the job will fail due to an integrity constraint violation.