Data Transformation Engine Integration Flow Designer Reference Guide

Appendix A - Return Codes and Error Messages A
Integration Flow Designer Reference Guide
162
Systems Using Wildcards Analysis Structure Error Messages
Wildcards can be used to specify a variable name for a source or target. The
asterisk and question mark characters are used according to the conditions
described in the SE103 thru SE110 error messages detailed in the System Analysis
Structure Error Messages section. The System Analyzer verifies that these
conditions are satisfied. When a condition is not satisfied, it is flagged as an error.
Note For more information about wildcards, refer to the Event Server Reference Guide.
Return Code Message
SE500 Map component name has no triggers. [Warning].
Maps that will be executed by an Event Server should have a
trigger, otherwise the map will never run.
SE501 System name has no components. [Warning].
A system should have at least one component.
SE502 Pseudo map component name1 exists in system name2 .
[Warning].
Pseudo maps should be converted to source map components.
SE503 Triggers are defined for a map that will be
executed by a Command Server - Map Component name1 .
[Warning].
Triggers should not be defined for a map that will be executed by
a Command Server.
SE504 The execution mode of system name does not match
the execution mode of subsystems that it contains.
[Warning].
The execution mode specified for a system should be the same as
the execution modes specified for its subsystems.
SE505 Drive letters should not be used in UNIX paths -
Map Component name1 , Card Name name2 . [Warning].
Drive letters should not be used in UNIX paths.