Conflict Detection and Resolution Messages

The messages issued from Conflict Detection and Resolution are intended to inform the user of the nature of the problem detected between the collections of metadata, data elements, and rules. Details are included to qualify the problem item so the user can fix the issue with knowledge of the problem. Following are examples of the messages presented from Coverage Display (and Coverage Analysis and Reporting).

Conflict Detection Messages

The following are error messages:

DPCB301-8 Conflict for Rule(EMP_ENC) due to Metadata(USERID.FASAMP.LAYOUTS(EMPLOYEE):EMPLOYEE-MAP) Field#1(XXX-NUMBER) detected by Data Element definitions(D_NUMBER and DE_EMP-Num).

This message illustrates a rule conflict between two Data elements that are targeting the same field. This message is also reported with DPCB302-8, which also references this field via one of these Data Element definitions. The Rule in question is listed along with the Metadata field and the Data Elements that reference the field.

DPCB302-8 Conflict for Metadata(USERID.FASAMP.LAYOUTS(EMPLOYEE):EMPLOYEE-MAP) Field#1(XXX-NUMBER) because multiple rules cannot operate on the same field. Conflict is between Rules(EMP-NUMBER-ENC, EMP_ENC).

This message illustrates the conflict on a field between two rules that are targeting it for disguise. This may be subject to Conflict Resolution processing. The Metadata field is shown along with the Rule Names that conflict.

DPCB307-8 Conflict for Data Element(EMPL_NUMBER) in Rule(EMPL_NUM_ENC) due to an ambiguous definition that detected other field references in addition to Field#3(EMP-FIRST-NAME) in Metadata(USERID.FASAMP.LAYOUTS(EMPLOYEE):EMPLOYEE-MAP).

This message illustrates the conflict on a data element definition that discovered multiple fields for a disguise. This is triggered by one or more other rules that use a Data Element that also discovered this field. There will be multiple occurrences of DPCB307, one for each field that has been discovered with these Data Elements. This may be subject to Conflict Resolution processing. If resolution processing cannot clear the conflict, the definitions for the rule usage of the data elements will probably require modification to eliminate the dual data element reference, or the data elements will need to be made more specific to tighten the field names they resolve to. The data element and the rule name are listed that resolved to the field. The other occurrences of DPCB307 can be used to coordinate to the data element/rules that conflict.

DPCB308-8 Conflict for Metadata(FADB2610:EMP_PHOTO_RESUME) Field#1(EMPNO) due to relational integrity conflict between Rule(PR1-thread[37]) and Rule(PR2-thread[38]).

This message illustrates a conflict between two rules that are targeting a single field. The two rules are identified by name along with the logical relationship thread number. This is an invalid condition where two rules are attempting to operate on a field through separate logical relationships. This cannot be allowed because the independent modification would corrupt the data integrity of the two logical relations.

DPCB311-8 Conflict for Metadata(EMPLOYEE-MAP) Field#5(EMP-CONTACT-PHONE) on rule(ENC-CONTACT-PHONE) because the OCCURS clause dimensions do not match the OCCURS for Field#6(EMP-CONTACT-ID).

This example illustrates the conflict on fields that are defined with an OCCURS clause. The problem presented here has to do with the field EMP-CONTACT-ID having an OCCURS different than EMP-CONTACT. This mismatch on the array definitions is ambiguous for aligning the entries for disguise, thus the error.

DPCB312-8 Conflict for Metadata(USERID.FASAMP.LAYOUTS(EMPLOYEE):EMPLOYEE-MAP) Field#1(XXX-NUMBER) because rule(s)(EMP_ENC) cannot operate on the field identified from DataElement(s)(D_NUMBER, DE_EMP-Num).

This message illustrates the conflict between two Rules or two Data Elements targeting a single field . This message is issued in conjunction with DPCB302 to clarify the issue. This may be subject to Conflict Resolution processing. The Metadata field is shown as well as the Rule Names or Data Elements that conflict.

DPCB317-8 Conflict for Rule(USERID.FASAMP.LAYOUTS(EMPLOYEE):EMPLOYEE-MAP) multiple non-target or translation lookup fields identified. Field#1 and Field#2 are identified by Data Element definition(D_NUMBER).

This message illustrates the conflict on a data element definition that discovered multiple non-target or translation lookup fields for a disguise. This is triggered by one or more other rules that use a Data Element that discovered multiple non-target fields. There will be multiple occurrences of DPCB317, one for each rule that uses this Data Element. The data element will need to be made more specific to tighten the field names they resolve to. The data element and the field numbers are shown in the conflict message.

DPCB318-8 Conflict for Metadata(USERID.FASAMP.LAYOUTS(EMPLOYEE):EMPLOYEE-MAP) Field#1(EMP-NUMBER) between Referential Integrity Rule(EMP_UNAME_ENC) thread[28]) and a Rule (EMP_Nstar-ENC) with multiple target fields.

This message illustrates the conflict on a field between two rules that are targeting a single field (one rule that is on a referential integrity thread and one rule that has multiple target fields). This conflict is similar to DPCB302, the difference is one of the rule involved in this conflict is referential integrity rule thread. The Metadata field is shown along with the Rule Names that conflict.

Conflict Resolution Messages

When conflicts are processed through the Resolution phase, there are two possible outcomes, either the conflicts are not resolvable thus the disguise will fail, or, the conflicts are resolved based on the guidelines for rule dismissal and a disguise will be performed under the modified rules. The following are informational messages:

DPCB305-1 Conflict resolved for Metadata(USERID.FASAMP.LAYOUTS(EMPLOYEE):EMPLOYEE-MAP) Field#1(EMP-NUMBER) between Rules(EMP_UNAME_ENC and EMP_Nstar-ENC). In order to maintain relational integrity on thread [28], Rule(EMP_Nstar-ENC) was removed.

This message explains that the conflict between two rules was resolved for this field. The disguise proceeded after the noted rule was removed from the disguise criteria.

DPCB316-1 Conflict resolved for Metadata(USERID.FASAMP.LAYOUTS(EMPLOYEE):EMPLOYEE-MAP) Field#1(EMP-NUMBER) to use Rule(EMP_UNAME_ENC) because it is more specific than Rule(EMP_Nstar-ENC) for this disguise.

This message explains that one of the conflicts for this field was resolved. Other conflicts may still be unresolved for this project, but the conflicts for the selected rule were resolved after another rule was removed from the disguise project.