Data Transformation Engine Type Designer Reference Guide

Appendix A - Return Codes and Error Messages Type Tree Analysis Logic Error Messages
Return Code Message
L129 COMPONENT RULE references a COMPONENT later in the
component list – ‘type name’ – TYPE: ‘type name’
Hint: Move the component rule to the component later in the list.
L130 COMPONENT RULE references undefined type –
COMPONENT # of TYPE: ‘type name’
Hint: Verify the spelling of the data object name. The rule should
reference a data object name of the component or a data object
name of a component earlier in the component list.
L131
Reserved for future use.
L132 Invalid partitioning: TYPE has no SUBTYPES – TYPE:
‘type name’
Hint: Remove the partitioned option from the class window or add
sub-types to the Type in error.
L133 Type of COMPONENT exists, but its relative name is
not valid: ‘type name’ in TYPE: ‘type name’
Hint: To get the correct relative name, drag the type you want to
use as a component and drop it in the component list of the Type.
(Remember to delete the invalid component!)
L134 Reference to ‘ANY’ not allowed: COMPONENT number #
of TYPE: ‘type name’
Hint: In this case, the Type in error is a group and it is not the
root of a partitioned tree. ANY cannot be used if that component
needs to be validated. So, if that group is partitioned, you cannot
use ANY for a component up to and including the identifier (if
there is one). If that group is not partitioned, you cannot use ANY
at all.
L135 COMPONENT number # cannot reference a CATEGORY in
TYPE: ‘type name’ (because group is not
partitioned)
Hint: In this case, the Type in error is a group and it’s not the root
of a partitioned tree. A category cannot be used if the component
must be validated. So, if that group is partitioned, you cannot use
a category for a component up to and including the identifier (if
there is one). If that group is not partitioned, you cannot use a
category as a component at all.