Allow override of built-in BRNAME and BRADDR standardization rules

We are migrating standardization rules from IBM InfoSphere Information Server (IIS) to Cloud Pak for Data (CP4D) DataStage NextGen.

During the migration, our customized Brazilian standardization rules BRNAME and BRADDR cannot be imported because CP4D already provides built-in rules with the same names.

The import fails with:

data_quality_spec_creation_error - Failed to create standardization rule: rule name = BRNAME

data_quality_spec_creation_error - Failed to create standardization rule: rule name = BRADDR

Our existing IIS environment contains customized versions of these rules, and existing DataStage jobs already reference them using the original names BRNAME and BRADDR. The built-in CP4D versions are not functionally equivalent to our customized implementations.

The current workaround is to create copies using different names and modify all existing jobs and flows to reference the renamed rules. This would require significant migration effort and introduce unnecessary risk.

We request a supported mechanism to import customized BRNAME and BRADDR rules and override the corresponding built-in rules while preserving the original rule names and existing job references.

Support for the Brazilian rules only (BRNAME and BRADDR) is acceptable for the initial implementation.

This enhancement would significantly improve migration compatibility between InfoSphere Information Server and CP4D DataStage and minimize changes required to existing DataStage assets.