Some of the ECMap informational messages are the result of an attempt to add a record whose key field already exists in a database. Some are the result of trying to reference a User File record field that does not exist in the User file database. Some are the result of User File record fields whose definitions in the User File have been changed since the User Field/Element Mapping defined. And, some of the messages in this section are described as internal program errors. Internal program error messages are not expected to ever be displayed. If an internal error message occurs or if the suggested corrective action does not solve a problem, note the message number and any associated DBCIII error number and call support for assistance.
Table 1-5 lists the format, cause, and solution (if applicable) for the ECMap messages related to fields, in numeric order by message number.
Message |
Cause |
Solution |
|---|---|---|
|
A run time map message that is written to the error log, which indicates that the map generated tables are incorrect. |
Regenerate the map. If problem is not corrected, call support for assistance. |
|
User has overridden the flow to branch to different levels other than the defaults, and has specified a flow number that no longer exists. |
Modify level number entries in outbound flow table. |
