PGU-41110
field name string appears multiple times in data definition string
Cause
A REDEFINE specifies the field name fld; this field name is multiply defined in the data definition dnm. The field name must be sufficiently qualified to remove the ambiguity so that a unique field may be referenced.
Action
Replace the ambiguous field name fld with a sufficiently qualified field name. An example of a qualified field name is SUBFIELD2 OF FIELD1 (or the generic equivalent, FIELD1.SUBFIELD2). It may be easier to just spool the output for a REPORT of the DATA definition for dnm into an output file, edit the output file, and DEFINE the DATA object named dnm anew.
PGU-41110
field name string appears multiple times in data definition string
Cause
A REDEFINE specifies the field name fld; this field name is multiply defined in the data definition dnm. The field name must be sufficiently qualified to remove the ambiguity so that a unique field may be referenced.
Action
Replace the ambiguous field name fld with a sufficiently qualified field name. An example of a qualified field name is SUBFIELD2 OF FIELD1 (or the generic equivalent, FIELD1.SUBFIELD2). It may be easier to just spool the output for a REPORT of the DATA definition for dnm into an output file, edit the output file, and DEFINE the DATA object named dnm anew.
PGU-41110
field name string appears multiple times in data definition string
Cause
A REDEFINE specifies the field name fld; this field name is multiply defined in the data definition dnm. The field name must be sufficiently qualified to remove the ambiguity so that a unique field may be referenced.
Action
Replace the ambiguous field name fld with a sufficiently qualified field name. An example of a qualified field name is SUBFIELD2 OF FIELD1 (or the generic equivalent, FIELD1.SUBFIELD2). It may be easier to just spool the output for a REPORT of the DATA definition for dnm into an output file, edit the output file, and DEFINE the DATA object named dnm anew.
