Some of the ECMap informational messages are related to map directories, application file directories, and ECMap environment variables.
ECMap provides great flexibility in deciding where to place directories and files on the disk. But with this flexibility comes the responsibility for accurately describing these locations to the mapping program.
ECMap depends on the user to correctly define map directory sets for each inbound and outbound EDI transaction. This is done through setting project map directories on the Project/Map window.
Each of the map directory sets defined is identified by a unique map name that is assigned on the Map window.
ECMap also relies on the user to have entered valid directory locations for all application files using the Directories (Mailboxes), Files/Databases, and Records/Tables windows.
Table 1-2 lists the format, cause, and solution (if applicable) for the ECMap messages related to map selection and directories, by message number.
Message |
Cause |
Solution |
|---|---|---|
|
The map name was not found in the database table of defined map names, MTABLE. |
If this error displays as a result of direct window entry of a map name or at ECMap startup ensure that the map name is correctly spelled. If this error occurs when running an inbound or outbound map, examine the trade agreement records that are associated with the transaction set for the trading partner processed. One of the map names that has been specified in the trade agreement records is not a valid map name (i.e. is not contained in MTABLE). WWIXMAP – Valid map names can be viewed from the trade agreement record window by moving the cursor to the map name field and pressing <F2> (option to display valid map names). |
|
The currently selected map name has not been defined completely. |
Examine all of the directory entries for this map name. One of the directories has been left blank. Enter a directory name into this field. |
|
The environment variable must be set to an existing directory prior to invoking the MAPPER program. The MAPPER program checks this directory for control databases at start up. If the control databases do not exist they are automatically created. WWIXMAP default directory is MAPEXE |
Control databases, such as the database table of defined map names, MTABLE, are located under the ECMap environment directory. Changing the value of ECMap causes a new MTABLE to be created under the new ECMap directory. This new MTABLE does not contain previously defined map names. |
|
Messages 1012 – 1014 are displayed when the environment variable is either not set or set to a name that is not a valid directory name. |
Check the setting and correct it. The values of environment variables can be checked at the DOS prompt by keying “SET” and pressing the ENTER key. At the DOS prompt, you can assign a new value to the environment variable by keying: SET [WWIXMAP] = “FULL PATH DIRECTORY NAME”. For example, the DOS command, “SET [WWIXMAP]= C:\MAPDATA”, sets the environment directory to the directory C:\MAPDATA.
|
|
ECMap cannot point to the root directory. |
Modify environment variables to include drive and directory. |
|
ECMap was unable to locate the designated directory. |
Modify variable to include drive and directory. |
|
System cannot get current working directory or pathname can be longer than 260 characters (default for Windows). |
Verify that all path directories should be less than 260 characters. |
|
Creating a new environment variable, modifying, or removing existing environment variables failed. |
System error. Call Technical Support. |
|
Cause 1: The MAPPER program was unable to create the designated directory. This message displays because either the directory name is invalid or the DOS limit has been reached for the number of directories on the PC. |
Solution 1: Verify that the directory name is a valid directory for the PC. For example if the PC in use does not have a D drive, then attempts to create a directory on the D drive fails. |
Cause 2: This message can be the result of keying in an incorrect directory name. |
Solution 2: Key in a correct directory name in the window field. |
|
Cause 3: Directory Names are stored in the User Files and in the map name Definition databases. When these directory names are entered they are verified as correct. However, changing the Configuration of a PC or copying data files between PC's could result in invalid directories in use. |
Solution 3: Verify that all file directories are valid. When the current map name is highlighted, verify that the Map directories for this map name are correct |
|
Cause 4: If the directory name is valid, then the DOS limit for the number of directories on your hard disk could have been reached. For most hard disks, the total number of directories allowed depends on how the hard disk was formatted. Double sided 40 track diskettes can have a total of 112 directories, and high capacity double sided 80 track diskettes can have a total of 224 directories. |
Solution 4: Delete a directory that is unrelated to the MAPPER to free up a directory entry space and execute the program again. |
|
|
ODBC could not establish a connection to the database specified in the filename. |
Check that the DSN specified is correct. Connection between ODBC drivers and the actual database has been broken. For example, the database server is down, and communication is not taking place. |
|
The internal record field definitions and the table structures do not match. |
Re-import the table definitions from the database. Re-export and create a new table in the database based on the new table definition in ECMap. |
|
Cause 1: Select statement could not execute because maximum number of connections (cursors) has been exceeded. |
Solution 1: Examine tables that establish the maximum number of cursors. Check Select Statement for correct syntax. |
Cause 2: Select statement could not execute because database connection has been terminated. |
Solution 2: Ensure that database has not gone inactive at the current location. |
|
|
Fetch was issued against a particular record type that had not been selected. |
Examine rules to ensure that table has been “selected” prior to issuing the “fetch” command. |
|
Cause 1: ODBC code failed to insert a record into the database because maximum number of connections (cursors) has been exceeded. |
Solution 1: Examine tables that establish the maximum number of cursors. Check Insert Statement for correct syntax. |
Cause 2: ODBC code failed to insert a record into the database because database connection has been terminated. |
Solution 2: Ensure that database has not gone inactive at the current location. |
|
|
ODBC could not establish a connection to the database specified in the filename. |
Check that the DSN specified is correct. |
|
Cause 1: Select statement could not execute because maximum number of connections (cursors) has been exceeded. |
Solution 1: Examine tables that establish the maximum number of cursors. Check Update Statement for correct syntax. |
Cause 2: Select statement could not execute because database connection has been terminated. |
Solution 2: Ensure that database has not gone inactive at the current location. |
|
|
||
|
No ODBC connection or no cursor handler. |
Call Support assistance. |
|
ODBC manager detected an error. Passed back to ECMap. |
See the ODBC error messages in Section 15 – Microsoft Standard ODBC Error Messages. |
|
A Bad Transaction has been processed. SQL statements that insert data into database are rolled back. |
Informational Message accompanied by other error messages that detail the transaction errors that occurred. |
|
A user-invoked SQL rollback has occurred. |
Informational Message |
|
Record definition and database records do not match. |
Ensure that the database definitions and the record definitions are synchronized. |
|
Cause 1: Procedure Call failed because of environment issue |
Solution 1: Examine procedure call in database to ensure that environment settings are correct |
Cause 2: Procedure Call failed because of a bad parameter. |
Solution 2: Examine procedure call in database to ensure that a bad parameter was not passed to the program. |
|
|
Error occurs on Map Switching when using different maps for the same messages. The record definitions in one map do not match the Record Definitions in the initial map. |
If different maps are used, ensure that they contain the same record definition for the same table. |
|
||
|
ODBC Trading Partner |
Set up the company information. |
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
Tag in data does not match tag in Read Rule at that level or the following level |
This is an informational message; you might not need to do anything. You can make sure the matching tag exists in the input data at this level or the following level. |
|
There are no more starting tags at the top of the loop in the input data and the end of the file has been reached. |
Verify that the looping tag exists in the input data. |
|
The element in the input data is not present in the map definition. |
Verify that the input data is correct or element exists in the map. |
|
The specified attribute in the input data is not present in the map definition. |
Verify that the input data is correct or the specified attribute exists in the map. |
Place the SET command that assigns
a full path directory name in the DOS autoexec.bat file.