On rules

(4000) ERROR: Rule out of valid range

The message indicates that one rule number (rule index in the rule table) is over the total rule number (in the rule table). It is not expected to occur, and would normally be caught at data entry time or map generated time.

If this error does occur, regenerate the map. If the error occurs again, call Support for assistance.

(4001) ERROR: Rule out of valid range for level - <level number> Segment - <segment name>

This message indicates that the rule with <rule number> with <segment number> is out of valid rule range that is defined in the map. It is not expected to occur and would normally be caught at map-generation-time.

Regenerate the map. If it occurs again, call Support for assistance.

(4002) ERROR: Rule #(<beginning rule number> - <ending rule number>)out of valid range for level <level number>

These messages are run time map messages that are written to the error log along with other detailed information to identify the exact cause of the message. The message indicates that the generated map has an undefined rule number. This message is not expected to occur. Errors of this type would normally be caught at data entry time, or map generation time.

If it does occur, examine the error log to determine the rule number that was invalid. Then locate where this rule was used in the User Field/Element Map or the Map Flow. Correct by adding the Defining the Map rule or eliminating reference to it. Then regenerate the map.

(4006) ERROR: invalid conditional check value

An outbound run time map message that is written to the error log along with other detailed information to identify the exact cause of the message. It indicates that a map record had the first field of a map condition line defined correctly but did not have the required second field of the map condition defined as a valid RECFLD, MEMVAR or STRVAR.

Examine the error log to determine the map record in error, and use the User Field/Element option to correctly define the second map condition field. Then regenerate the map.

(4009) ERROR: Rule command undefined

Occurs during Map Rule definition if the user attempts to use an undefined rule number as part of a rule command.

Use Map Rule definition to define the rule to be used in another rule.

(4013) ERROR: Rules for SQL Stored Procedure are obsolete. Please run Generate Map

Occurs when running a map created in a previous release with the new release of ECMap. The rules for Stored Procedure in the new version have changed

Map rules must be modified to use the latest rule definitions. Then regenerate the map under the new release.

(4019) TRACE: Level <level number> -> <level number> processing Segment: <rule number >-No<line number>

Occurs before executing the OK Rule in the <level> to <level> processing and the rule number is <rule number>, line number is <line number>

(4020) TRACE: Level <level number> processing Rule: <rule number >-No<line number>

Occurs before the command executed, which is at <line number> of <rule number> during the <level number> processing.

(4021) TRACE: Level <level number> No <Before/After> Rules to process

Indicates that the rule with rule <level number> does not have a “before and after” command to process.

(4022) TRACE: Rule <rule number> Changed Level To <level number>

(4023) TRACE: Performing Rule <rule number>

Indicates that at runtime the rule <rule number> is executed.

(4024) TRACE: Rule <rule number> Line <line number> Start Perform While on Rule <rule number>

These informational messages occur when Verbose Trace is on. They report progress at particular points in time when running the map.

(4040) ERROR: Parameter <parameter> is empty on assignment

You try to assign a parameter to a system variable or a memory variable but this parameter is empty.

Verify that the parameter in parameters tab at Run Map window of ECMap. Verify that the command that assigns the parameter to a system variable or a memory variable.

(4050) FATAL: MemVar <memory variable> has uncompleted sql statement