Logic error and warning messages

The tables in this section list the logic warning messages that result from a logic analysis of a type tree.

The following table lists the warnings than can result when a map is compiled.

Warnings should be resolved because they may produce unpredictable results at mapping time.

Return Code

Message

L199

COMPONENT # is not distinguishable from COMPONENT # that may follow in TYPE: `type name'.

Hint: Make the first COMPONENT bound, or look at the tables in "Distinguishable objects" to see how you can define the two component types as distinguishable.

L201

Different data objects of COMPONENT # are not distinguishable in TYPE: `type name'.

Hint: See "Distinguishable objects" for more information about distinguishable objects.

L202

RESTRICTION list deleted: TYPE is not an ITEM - TYPE: `type name'

Hint: Type class was changed from an item to a group or category, so the restriction list was deleted. If this was not your intent, change it back to the way it was.

L203

COMPONENT list deleted: TYPE is an ITEM - TYPE: `type name'

Hint: Type class was changed from a group to a item or category, so the program deleted its component list. If this was not your intent, change it back to the way it was.

L204

DELIMITER deleted: TYPE is not a DELIMITED GROUP - TYPE: `type name'

Hint: Group format was changed from delimited to something else, so the program deleted its delimiter. If this was not your intent, change it back to the way it was.

L205

COMPONENT RULE deleted: TYPE is a CATEGORY - TYPE: `type name' (warning)

Hint: Type class was changed from a group to a category, so its component rule was deleted. If this was not your intent, change it back to the way it was.

L206

DELIMITER cannot be found (because first component is not required) - TYPE: `type name' (warning)

Hint: If the delimiter is missing, a previously set initiator value or the default value is used.

L251

COMPONENT NAME could apply to more than one type:'type name' in TYPE: `type name' (warning).