Map build error messages

Build errors prevent a map from being compiled. If build errors occur, view the errors, correct the problem(s), and build the map again. A map cannot be run if it has not been built.

DataPower maps in addition to the ones listed below. See Map build errors for DataPower maps for a consecutive list of these additional map build error codes for a DataPower map.

Return Code

Message

M100

Analysis aborted by user.

M101

Map: x

Unresolved rules exist.

Hint: Go to map x. If you want to use the unresolved rules, copy and paste them. Delete any unwanted unresolved rules.

M102

Map: x Output: y

Functional map referenced in rule must have one (and only one) output.

Map referenced: map-name.

Hint: Go to the functional map. Delete the extra card(s).

M103

Map: x Output: y

Number of arguments for functional map map-name is incorrect.

Number specified: #specified Number required: #required

Hint: Add or delete arguments from the rule, or add or delete input cards in the functional map.

M104

Map: x Output: y

Empty rule cell. Rule required.

Hint: Go to map x. Enter rules in each empty rule cell.

M105

Map: x Output: y

Rule references unknown type: type name.

Hint: You may have made a change in the schema. If the card object is unknown, edit the card, and choose a valid type. You may have incorrectly typed in the name. If you drag and drop the type, the correct name is automatically entered.

M106

Map: x

Circular map reference from map map-name.

Analysis must terminate.

Hint: Two different maps contain rules that reference each other. Remove the reference from one of the maps.

M107

Map: x Output: y

Rule syntax is invalid starting at character position: position#.

Rule

Hint: This error may occur if a previous version did not catch the syntax error. Generally, syntax errors are caught as rules are entered. See the release notes for any changes in rule syntax.

M108

Map: x Output: y

Rule references unknown map: map-name.

Hint: Re-enter the map name in the rule. You may have typed the map name incorrectly. Map names are case-sensitive. You may have forgotten to create the functional map. If so, create it.

M109

Map: x Card: cardname

Card is invalid.

Hint: The type name is either misspelled or you may have made a change in the schema by deleting or renaming the type. Edit the card, and choose a valid type.

M110

Map: x Card: cardname

Card type is not a group or item.

Hint: You probably changed your schema. Edit the card, and choose a group or item.

M111

Map: x Output: y

Argument #w for map map-name does not match type of input card #z.

Hint: Change argument #w so that it matches the type of input card #z, or change the type of input card #z so that it matches argument #w.

M112

Map: x Output: y

Argument #w for map map-name does not match item sub-class of card #z.

Hint: Change argument #w so that it matches the item sub-class of input card #z, or change the type of input card #z so that its item sub-class matches argument #w.

M113

Map: x Output: y

Argument #w for function function name is invalid.

Hint: Select the rule for output, y. Right-click the map rule and choose Properties on the context menu. The Rule Properties dialog box allows you to view function arguments and object properties. You have either referenced an invalid object, or used the wrong type of argument.

M114

Map: x Output: y

Output argument of rule does not match output type: rule.

Hint: The map rule is resulting in a data object of the wrong type. Check the functions and the maps used within the map rule and make sure that the entire rule evaluates to the correct type.

You may have dragged and dropped a group that is a different type to this output. Use a functional map instead. If the rule contains the name of a functional map, go to the functional map and edit the output card. Make sure the type of the output card is the output y.

M115

Map: x Output: y

Output argument of rule does not match output item sub-class: rule.

Hint: Notice the output y. The output argument of the rule must have the same item sub-class as y.

M116

Map: x Output: y

Type Tree for this card is not used in executable map.

Hint: Edit the card and select a schema that is used in the executable map.

M117

Map: x Output: y

Cannot assign an output to itself.

Hint: You might have accidentally dragged and dropped an output into its own rule cell. Edit the rule.

M118

Map: x Output: y

Rule references unknown comment: commentname @ inputname

Hint: The input card type does not have a floating component, or you have incorrectly typed in the name. If the input card has a floating component, on the Card menu, the Show Floating Component Type option will be activated.

M119

Map: x Output: y

Output argument of rule is not a partition of output type.

Hint: If the rule contains the name of a functional map, go to the functional map and edit the output card. Make sure the type of the output card is the output y, or a partition of the output y.

M120

Map: x Output: y

Operand is an invalid operand.

Hint: For information on operands, see the Functions and Expressions documentation.

M121

Map: x

Input card #cardnumber uses invalid schema.

Hint: You may have moved the schema or map source from its original location. You may have incorrectly entered the name of the schema.

M122

Map: x

Output card #cardnumber uses invalid schema.

Hint: You may have moved the schema or map source from its original location. You may have incorrectly entered the name of the schema.

M123

Map: x Card: cardname

Card updates input, but card type and data file do not match an input.

Hint: Edit the card and re-define the update information.

M124

Map: x Output: y

Rule references type later in output: rule

Hint: If possible, enter an equivalent rule in a later output. An output referenced in a rule must appear above the rule within the output card.

M125

Map: x

Invalid audit: audit statement

Hint: Look at the Audit Settings window. An asterisk * appears next to any invalid audit statement. Re-enter the audit statement.