System messages

With two exceptions, system messages are the result of missing executables, inadequate PC memory, or internal program errors.

Error message exceptions

The two exceptions are the messages related to the User ABORT and STOP_RUN commands. The messages for these commands indicate that the user terminated the map run.

Error messages described as “Internal program error” are present to catch program logic errors and do not display. If they do display, note the message number and any associated error number, and call Sybase support for assistance immediately.

ECMap relies on the dynamic allocation and deallocation of memory. If memory allocation errors occur, call Sybase support for help in analyzing your transaction set databases and your PC memory limits.

Memory error work arounds

Two work arounds could allow work to continue when memory errors occur:

If a Memory Allocation Error message displays during map run or compile, examine the data dictionary and rules databases, as well as the map flow database used with the current transaction. If particular rules, map flow levels, records, fields or memory variables are not needed for the current transaction, reduce the amount of memory required to process the transaction by creating a smaller rules, map flow or data dictionary database.
If a Memory Allocation Error occurs when an option other than map run or compile was executed, restart ECMap and try running your map again.

Table 1-1 lists the format, cause, and solution (if applicable) for the ECMap system messages in numeric order by message number.

**Table 1-1: ECMap system messages**
Message	Cause	Solution
`(0003) FATAL: undefined database type- <internal program code>`	Internal program error.	Call support for assistance.
`(0021) OK: executed STOP_RUN command`	Information Only. User STOP_RUN rule was executed.	A command placed in the map by a user. Find where the command is located in the map and remove it if the command is not desired.
`(0100/<ERRNO-NO>) FATAL: call to program module- <program name>`	An attempt to spawn “PROGRAM” failed. The ERRNO-NO is the error code from the ‘C’ “errno” table. The most likely reasons are “errno” number 2, which means that the executable file does could not be found on disk, or “errno” number 12, which means that there is not enough memory available to load the called program.	For “errno” value of 2, the corrective action is to do a DIR on the directory where the MAPPER executable are stored. WWIXMAP – The default installation directory for executables is “MAPEXE”. ECMAP – The default installation directory for executables is Program Files\Sybase\ECMap. If the file is not on the disk, reinstall the WWIX executable files using the installation disks. If the executable does exist on disk but was not found, then make sure that the WWIX executable directory is included in the DOS PATH environment variable. For “errno” value of 12, call support for assistance.
`(0102) FATAL: program call- incorrect parameters`	One or more wrong parameters was called.	Recheck the list of valid parameters and apply those parameters to the command line.
`(0103) FATAL: parameter<parameter switch> exceeds Max Length number <maximum length>`	You have too many parameters for your map.	Reduce the number of parameters.
`(0105) FATAL: invalid or undefined input parameter(s)`	Internal program errors. A parameter has been called or accessed that has not been defined, or is not defined correctly.	Call support for assistance.
`(0200) FATAL: memory allocation`	MAPPER was unable to allocate enough memory to execute a critical function.	Call support for assistance.
`(0202) FATAL: memory allocation; loading database- <database>`	Indicates that there was not enough memory to create a temporary memory table from a database. If this message occurs while performing the Define Map Flow function, then the size of your Map Flow database has exceeded the size that can be loaded into memory. Examine the Map Flow to determine if all of the defined levels are required.	Call support for assistance.
`(0208) FATAL: memory allocation; loading < > for Map: <filename>`	Insufficient memory available to load map.	Call support for assistance.
`(0209) ERROR: USING EDIFACT MAP with NON-EDIFACT ENVELOPE`	Occurs when envelope information does not contain EDIFACT standards.	Call support for assistance.
`(0210) ERROR: USING NON-EDIFACT MAP with EDIFACT ENVELOPE`	Occurs when envelope information contains EDIFACT standards or a non-EDIFACT map.	Call support for assistance.
`(0211) FATAL: memory allocation loading map`	An internal program error. The length of the text keyed in for a rule operand by the user is greater than the space that has been allocated to store the text rule operand.	Call support for assistance.
`(0212) FATAL: Trading Partner <trading partner> Has No Mailbox`	No directory has been defined in the Trade Agreement record	Define the directory.
`(0213) FATAL: Can’t Set Transaction level`
`(0214) FATAL: Can’t Retrieve WIXSET Record`	The wixset database is damaged or the wixset database has no record inside.	Check the wixset database
`(0215) FATAL: Attempt to run < > with < > MAP`	Attempt to run “inbound” with an “outbound” map.