Map execution error and warning messages
After a map is executed, map execution messages indicate the execution results. If audit is enabled, these messages are also recorded in the appropriate audit log for the map.
The following list describes the codes and messages that can be returned as a result of running a map.
The return codes marked with an asterisk (*) are warning codes. See Map Execution Warning Messages for a consecutive list of the warning codes for a map.
- Return Code
- Message
- 0
- Map completed successfully
- 1†
- User aborted map
If you cancel the Server before the map completes, this message is displayed.
- 2
- Not enough memory to execute map
There is not enough memory to initialize the map. Try closing all other running applications.
- 3
- Could not open map
The .mmc file cannot be found. Ensure the file name or path is correct.
- 4†
- Could not read map
If you have ported your map and sent it with FTP to another platform, make sure you have done so using the BINARY option so the map's contents will not be corrupted.
- 5
- Could not read inputs
- 6
- Invalid map handle
- 7
- Invalid card number was specified
Your map may be corrupt.
- 8
- One or more inputs was invalid
Turn the input trace on, run the map again and read the trace file.
- 9†
- Target not available
An incorrect file name or path for a target may be specified.
- 10†
- Internal error
- 11
- Could not build one or more outputs
An attempt may have been made to write to a read-only directory, or an output file directory may be missing.
- 12†
- Source not available
An incorrect file name or command for a source may be specified.
- 13
- Could not open work files
An invalid path for work files may be specified.
- 14*
- One or more outputs was invalid
A number produced an overflow condition. Enable the Trace Output option, run the map again, and read the trace file.
- 15
- Map must be recompiled
You may be trying to run a map with a server that has a different version from the map designer version used to compile the map. Make sure the map designer and the Server versions match.
- 16
- Disk write error
An attempt may have been made to write to a read-only directory or file. Also, check the amount of available disk space.
- 17
- Disk read error
An attempt may have been made to access a file on a shared resource that is not accessible. Also, check the amount of available disk space.
- 18*
- Page usage count error
Your data mapped correctly; however, an internal paging problem exists.
- 19
- Internal calling error
- 20
- Reopen file failed
Your map did not run correctly.
- 21*
- Input valid but unknown data found
Enough of the input data to conform to the card definition was recognized, but there was more data at the end of the input stream. Enable the Trace Input setting, re-run the map and read the map trace file (.mtr).
- 22
- Page size too small
Increase the page size or decrease the number of types in the schema that are used to define the input.
- 23
- Unable to reuse work file
Use the same page settings that were used when you created the existing work file.
- 24
- Database error
A problem was encountered attempting to write to an output database. Read the database trace file (.dbl) for information about possible causes.
- 25
- File attribute error
The Command Server failed to write data to either the work or data file. Check the output card definition on the map to see if it matches the platform-specific data definition specified for the file the map is attempting to create.
- 26*
- Output type in error
The entire card object is in error.
- 27*
- Output type contains errors
One or more components failed restrictions or a component rule.
- 28*
- Input type contains errors
This occurs when mapping data of a component that has a RESTART assigned to it, and at least one instance of the component in the input data is invalid.
- 29*
- Output valid, but unknown data found
This occurs when enough of the output data is recognized to conform to the card definition, but there was more data at the end of the output stream.
- 30
- FAIL function aborted map
This occurs when the FAIL function is used within the map to cause map execution to cease. The return message specified as the second argument of the FAIL function appears in place of the xxx in the Execution Audit section of the Audit Log. See the Functions and Expressions documentation for more information about using the FAIL function.
- 31
- (No longer used)
- 32
- Invalid map instance handle
- 33
- Map instance handle in use
- 34*
- Too few pages requested, more allocated
The map can complete but it can be better optimized by increasing the page count.
- 35
- Insufficient number of pages to execute map
The map could not complete because not enough pages were specified.
- 36
- Could not open work files
A scratch file for the HANDLEIN function could not be created.
- 37†
- Operation is not supported on the platform
- 50
- Not enough memory to execute map
There is not enough memory to initialize the map. Try closing all open applications.
- 51
- Card override failure
There is a problem with the command line entered for an -I or -O option.
(Applicable to Command Server )
- 52
- I/O initialization failure
A run map was called and could not allocate memory for input or output.
- 53†
- Open audit failure
The audit file was not accessible.
- 54
- No command line
There was no map or command line specified.
(Applicable to run maps and the Command Server)
- 55
- Recursive command files
A command file was specified within a command file.
(Applicable to run maps and the Command Server)
- 56
- Invalid command line option - <option>
An invalid argument was entered on the command line.
(Applicable to run maps and the Command Server)
- 57
- Invalid `W' command line option
An invalid parameter for the -W option was specified.
(Applicable to run maps and the Command Server)
- 58
- Invalid `B' command line option
An invalid parameter for the -B option was specified.
(Applicable to run maps and the Command Server)
- 59
- Invalid `R' command line option
An invalid parameter for the-R option was specified.
(Applicable to run maps and the Command Server)
- 60
- Invalid `A' command line option
An invalid parameter for the -A option was specified.
(Applicable to run maps and the Command Server)
- 61
- Invalid `P' command line option
An invalid parameter for the -P option was specified.
(Applicable to run maps and the Command Server)
- 62
- Invalid `Y' command line option
An invalid parameter for the -Y option was specified.
(Applicable to run maps and the Command Server)
- 63
- Invalid `T' command line option
An invalid parameter for the -T option was specified.
(Applicable to run maps and the Command Server)
- 64
- Invalid `G' command line option
An invalid parameter for the -G option was specified.
(Applicable to run maps and the Command Server)
- 65
- Invalid `I' command line option for input <2>
An invalid parameter for the -I option was specified for input card <number>.
(Applicable to run maps and the Command Server)
- 66
- Invalid size in echo command line for input < 2 >
A size (nnn) was specified for -IE2Snnn that is outside of the boundaries for input card <number>.
(Applicable to run maps and the Command Server)
- 67
- Invalid adapter type in command line for input <2>
Using the -IAadapter_name or -IMadapter_name, <adapter_name> is not a valid adapter type.
(Applicable to run maps and the Command Server)
- 68
- Invalid `O' command line option for output <1>
An invalid parameter for the -O option was specified for output card <number>.
(Applicable to run maps and the Command Server)
- 69
- Invalid adapter type in command line for output <1>
Using the -OAadapter_name or -OMadapter_name, adapter_name is not a valid adapter type.
(Applicable to run maps and the Command Server)
- 70
- Command line memory failure
Memory allocation failure during processing of command line.
(Applicable to run maps and the Command Server)
- 71
- Invalid `D' command line option
An invalid parameter for the -D option was specified.
(Applicable to run maps and the Command Server)
- 72
- Invalid `F' command line option
An invalid parameter for the -F option was specified.
(Applicable to run maps and the Command Server)
- 73
- Resource manager failure
The resource manager could not reserve the resources (sources/targets) due to a resource contention that is most likely a run map.
(Applicable to run maps.)
- 74
- Invalid `Z' command line option
An invalid parameter for the -Z option was specified.
(Applicable to run maps and the Command Server)
- 75
- Adapter failed to get data on input
During the commit/rollback phase, the source had a failure
- 76
- Adapter failed to put data on output
During the commit/rollback phase, the target had a failure.
- 77
- Invalid map name: <map_name>
The map path and name exceed 2000 bytes.
(Applicable to run maps and the Command Server)