On file I/O

Some of the messages in this section are the result of system errors from opening, reading, writing and closing files. Other errors result from users performing MAPPER program definitions for User Files, Map Directory Sets, Map I/O Rules or Map Flows.

Some of the messages in this section are described as internal program errors. Internal program error messages are not expected to display. If an internal error message occurs or if the suggested corrective action does not solve a problem, note the message number and any associated DBCIII error number and call Sybase support for assistance.

Table 1-3 lists the format, cause, and solution (if applicable) for the ECMap messages related to File I/O (including databases and indexes), by message number.

**Table 1-3: ECMap messages related to File I/O**
Message	Cause	Solution
`(1101) FATAL: file <file name> has non-numeric < >`
`(1102) FATAL: file <file name> has invalid zero delimiter`
`(1104) FATAL: file number out of range - < >`	A run time map message that is 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 a rule that is incorrectly referencing a file.	Regenerate the map for the current transaction. If message reoccurs, call support for assistance.
`(1105) FATAL: filename is blank on read`	Displays if a map is run and the generated tables contain a blank file name. This message is not expected to be displayed since the “Define Rules” option checks for valid file names.	Examine the Map Rules for any incorrect File I/O rules. Regenerate the map for the current transaction and examine the map generation error log. Correct any generation error log messages. If message reoccurs, call support for assistance.
`(1106) FATAL: file- <file name> used both as <READ/WRITE> and KEYED`	A run time map message that is written to the error log along with other detailed information to identify the exact cause of the message. This message occurs if the name file has been used as both a keyed index file and as a sequential user file.	Examine the file I/O rules that uses the FILE NAME in question. Correct the rules so that FILE NAME is not referenced as both a keyed file and a sequential file.
`(1110) FATAL: can’t open file- < file name >` `(1113) FATAL: can’t open index- <index name> database- <database>`	Messages 1110 and 1113 are displayed as a result of a failed open file command. When a file cannot be opened, it could be due to file damage or the file might not exist on disk. The full path name of the file that cannot be opened displays in the error message.	Check that the file exists, and directory path exists. If the directory does not exist create it. If it cannot be determined why the database or index cannot be opened, call support for assistance. ECMap automatically creates the required directories; however, it is possible one of the needed directories has been deleted. If the directory exists but the file does not, determine what type of file it is by the file name and directory location. For example, the file could be a standards database that has not been loaded into the directory specified. Or perhaps the problem is a missing data file that has not been loaded into the directory. Or perhaps the map flow databases or the rules database have not been created, and the user is trying to generate a map.
`(1118) FATAL: can’t open EDI file- <EDI file name>`	The specified EDI file cannot be opened. This Run Time map message is written to the error log along with other detailed information to identify the exact cause of the message.	Verify that the file exists on disk. If the file does exist, call support for assistance.
`(1119) ERROR: not found- <file type>: <file name>`	A map run time error message that occurs when a Look Up Table, or Keyed index file does not exist. The displayed file name contains the full path name of the needed file.	Place the needed file in the indicated directory or modify the map so that the file is not referenced and regenerate the map. If the file is a keyed index file, then use the “Define Rules” to remove file I/O rules using this keyed index file. If the file is a table lookup file, then “Mapping” options can be used to either create the look up table or delete any reference to it.
`(1120) WARNING: file not found- create?`	Verifies that file creation is desired. MAPPER is designed to create some files when they are not present. For example, empty User file databases, and empty map flow databases are created by the MAPPER program. Before creation of these databases, MAPPER verifies that the user wants to create the new database for the currently selected map.	If the user responds with “Y”, MAPPER creates the file. If the user responds with “N”, MAPPER terminates the function.
`(1122) ERROR: file <file name> not found`	A file specified in the rules and/or directory structure is not found. This is a read only problem.	Check directory and filename specifications, to ensure that there is a file of that type present on the system.
`(1124) FATAL: unexpected EOF while processing level <map flow level number>`	An outbound map run time error message that occurs when a level’s I/O rule is performed to read a user file and the read results in End Of File. The End of File is considered to be unexpected if the level has not been defined as “Optional” by the user in the “Mapper Flow” options, and the level is either not a repeating level or is a repeating level but the repeating level is executed for the first time in the loop. If this message displays, then either the user files for this transaction are incomplete or the map flow does not correctly describe the user files.	Call support for assistance.
`(1125) FATAL: DBF Error`	Displays when any errors have been detected by the Run Time while accessing dBASE files.	May indicate the Trading Partner file is not present. Ensure that directory location and Trading Partner status has been established.
`(1126) FATAL: Directory <directory> Does Not Exist`
`(1130) FATAL: can’t read file- <file name>`	Messages 1130 through 1132 are displayed when an error occurs as a result of a read file command and the end of file has not been reached. Verify that the file name displayed exists on the disk. This message is usually displayed only after the file has been successfully opened, and if the file does exist on disk these messages should be regarded as internal program errors.	Call support for assistance.
`(1140) FATAL: can’t write to file- <file name>` `(1141) (DBCIII ERR #) FATAL: can't write to file- <file name>`	Messages 1140 and 1141 are displayed if an attempt to write a record to an open database or file fails. Could be the result of a full disk, or not enough free memory.	Exit MAPPER and check for free disk space. If there is free disk space, restart MAPPER and retry the MAPPER option that caused the error. If the write fails again, call support for assistance.
`(1142) ERROR: Rename <File 1> to <File2> Failed.`	Rename command did not execute correctly.	Ensure that: directory exists filenames are correct and valid File 2 does not already exist since the rename command can not update.
`(1177) ERROR: on Breakfield`	An internal program error that should never occur. If it does, it occurs when a outbound map is running, and the size of a breakfield for a user file exceeds the space that has been dynamically allocated to hold the breakfield value.	Call support for assistance.
`(1181) ERROR: file- <file name> has multiple records, but record- <record name> doesn’t have record type field.`	A run time map message. A User file has been defined to contain several different records but the displayed RECORD NAME that belongs to FILE NAME file does not have a record type field.	Correct this by defining a record type field for the record or by changing the definition of the displayed FILE NAME to contain only one record.
`(1190) ERROR: Missing <record name> Record in Map <map name>`	Required type of record is not in map, such as outstat and flow record	Check flow, and/or record definitions to ensure that record is defined. Run Generate to regenerate the map.
`(1191) ERROR: Invalid header line in map <map name> at line <line number>`	*.MAP file is incorrect. Somehow this file has been corrupted.	Run Generate to regenerate the map.
`(1192) ERROR: Unexpected < > of < > records at line < line number> Map <map name>`	Map was not completed correctly i.e.: the flow is missing,	Ensure that all map components are present (including the flow) and regenerate the map.
`(1193) ERROR: Level <level number> Current Record Name Cannot be Blank`	Outbound map flow has errors.	Current record is not defined in outbound flow. Define record and regenerate the map.
`(1194) ERROR: Level <level number> Parent Record Name Cannot be Blank`	Outbound map flow has errors.	Parent record is not defined in outbound flow. Define parent record and regenerate the map.
`(1195) ERROR: Level <level number> Not Linked to Prior Level`	Outbound map flow has errors.	Modify flow to include prior level and regenerate the map.
`(1196) ERROR: Level <level number> Multiple Link Only's Attached to Same Prior Level`	Outbound map flow has errors.	Modify flow to eliminate multiple “link onlys” attached to the same level. This is not a legal condition.
`(1197) ERROR: Level <level number> Link Only Must Attach to Repeat or Master Level`	Link only has been specified where it is not needed. Link only’s are only needed after repeats on the master level.	Delete the link only that is attached to the instance where this error message occurs and change the level numbers for the segments so that they are attached to the appropriate level.
`(1198) ERROR: Level <level number> Should Be Placed Directly Beneath Parent Level`	Outbound map flow has errors.	Check placement of entries in this flow table to ensure that parent and child levels flow correctly.
`(1199) ERROR: Flow Errors In Outstate Map – Run Aborted`	Outbound map flow has errors.	Check placement of entries in flow table.

Table 1-3: ECMap messages related to File I/O

Message

Cause

Solution

(1101) FATAL: file <file name> has non-numeric < >

(1102) FATAL: file <file name> has invalid zero delimiter

(1104) FATAL: file number out of range - < >

A run time map message that is 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 a rule that is incorrectly referencing a file.

Regenerate the map for the current transaction. If message reoccurs, call support for assistance.

(1105) FATAL: filename is blank on read

Displays if a map is run and the generated tables contain a blank file name. This message is not expected to be displayed since the “Define Rules” option checks for valid file names.

Examine the Map Rules for any incorrect File I/O rules. Regenerate the map for the current transaction and examine the map generation error log. Correct any generation error log messages. If message reoccurs, call support for assistance.

(1106) FATAL: file- <file name> used both as <READ/WRITE> and KEYED

A run time map message that is written to the error log along with other detailed information to identify the exact cause of the message. This message occurs if the name file has been used as both a keyed index file and as a sequential user file.

Examine the file I/O rules that uses the FILE NAME in question. Correct the rules so that FILE NAME is not referenced as both a keyed file and a sequential file.

(1110) FATAL: can’t open file- < file name >

(1113) FATAL: can’t open index- <index name> database- <database>

Messages 1110 and 1113 are displayed as a result of a failed open file command. When a file cannot be opened, it could be due to file damage or the file might not exist on disk. The full path name of the file that cannot be opened displays in the error message.

Check that the file exists, and directory path exists. If the directory does not exist create it. If it cannot be determined why the database or index cannot be opened, call support for assistance.

ECMap automatically creates the required directories; however, it is possible one of the needed directories has been deleted. If the directory exists but the file does not, determine what type of file it is by the file name and directory location. For example, the file could be a standards database that has not been loaded into the directory specified. Or perhaps the problem is a missing data file that has not been loaded into the directory. Or perhaps the map flow databases or the rules database have not been created, and the user is trying to generate a map.

(1118) FATAL: can’t open EDI file- <EDI file name>

The specified EDI file cannot be opened. This Run Time map message is written to the error log along with other detailed information to identify the exact cause of the message.

Verify that the file exists on disk. If the file does exist, call support for assistance.

(1119) ERROR: not found- <file type>: <file name>

A map run time error message that occurs when a Look Up Table, or Keyed index file does not exist. The displayed file name contains the full path name of the needed file.

Place the needed file in the indicated directory or modify the map so that the file is not referenced and regenerate the map. If the file is a keyed index file, then use the “Define Rules” to remove file I/O rules using this keyed index file. If the file is a table lookup file, then “Mapping” options can be used to either create the look up table or delete any reference to it.

(1120) WARNING: file not found- create?

Verifies that file creation is desired. MAPPER is designed to create some files when they are not present. For example, empty User file databases, and empty map flow databases are created by the MAPPER program. Before creation of these databases, MAPPER verifies that the user wants to create the new database for the currently selected map.

If the user responds with “Y”, MAPPER creates the file.

If the user responds with “N”, MAPPER terminates the function.

(1122) ERROR: file <file name> not found

A file specified in the rules and/or directory structure is not found. This is a read only problem.

Check directory and filename specifications, to ensure that there is a file of that type present on the system.

(1124) FATAL: unexpected EOF while processing level <map flow level number>

An outbound map run time error message that occurs when a level’s I/O rule is performed to read a user file and the read results in End Of File. The End of File is considered to be unexpected if the level has not been defined as “Optional” by the user in the “Mapper Flow” options, and the level is either not a repeating level or is a repeating level but the repeating level is executed for the first time in the loop. If this message displays, then either the user files for this transaction are incomplete or the map flow does not correctly describe the user files.

Call support for assistance.

(1125) FATAL: DBF Error

Displays when any errors have been detected by the Run Time while accessing dBASE files.

May indicate the Trading Partner file is not present. Ensure that directory location and Trading Partner status has been established.

(1126) FATAL: Directory <directory> Does Not Exist

(1130) FATAL: can’t read file- <file name>

Messages 1130 through 1132 are displayed when an error occurs as a result of a read file command and the end of file has not been reached. Verify that the file name displayed exists on the disk. This message is usually displayed only after the file has been successfully opened, and if the file does exist on disk these messages should be regarded as internal program errors.

Call support for assistance.

(1140) FATAL: can’t write to file- <file name>

(1141) (DBCIII ERR #) FATAL: can't write to file- <file name>

Messages 1140 and 1141 are displayed if an attempt to write a record to an open database or file fails. Could be the result of a full disk, or not enough free memory.

Exit MAPPER and check for free disk space. If there is free disk space, restart MAPPER and retry the MAPPER option that caused the error. If the write fails again, call support for assistance.

(1142) ERROR: Rename <File 1> to <File2> Failed.

Rename command did not execute correctly.

Ensure that:

directory exists
filenames are correct and valid
File 2 does not already exist since the rename command can not update.

(1177) ERROR: on Breakfield

An internal program error that should never occur. If it does, it occurs when a outbound map is running, and the size of a breakfield for a user file exceeds the space that has been dynamically allocated to hold the breakfield value.

Call support for assistance.

(1181) ERROR: file- <file name> has multiple records, but record- <record name> doesn’t have record type field.

A run time map message. A User file has been defined to contain several different records but the displayed RECORD NAME that belongs to FILE NAME file does not have a record type field.

Correct this by defining a record type field for the record or by changing the definition of the displayed FILE NAME to contain only one record.

(1190) ERROR: Missing <record name> Record in Map <map name>

Required type of record is not in map, such as outstat and flow record

Check flow, and/or record definitions to ensure that record is defined. Run Generate to regenerate the map.

(1191) ERROR: Invalid header line in map <map name> at line <line number>

*.MAP file is incorrect. Somehow this file has been corrupted.

Run Generate to regenerate the map.

(1192) ERROR: Unexpected < > of < > records at line < line number> Map <map name>

Map was not completed correctly i.e.: the flow is missing,

Ensure that all map components are present (including the flow) and regenerate the map.

(1193) ERROR: Level <level number> Current Record Name Cannot be Blank

Outbound map flow has errors.

Current record is not defined in outbound flow. Define record and regenerate the map.

(1194) ERROR: Level <level number> Parent Record Name Cannot be Blank

Outbound map flow has errors.

Parent record is not defined in outbound flow. Define parent record and regenerate the map.

(1195) ERROR: Level <level number> Not Linked to Prior Level

Outbound map flow has errors.

Modify flow to include prior level and regenerate the map.

(1196) ERROR: Level <level number> Multiple Link Only's Attached to Same Prior Level

Outbound map flow has errors.

Modify flow to eliminate multiple “link onlys” attached to the same level. This is not a legal condition.

(1197) ERROR: Level <level number> Link Only Must Attach to Repeat or Master Level

Link only has been specified where it is not needed. Link only’s are only needed after repeats on the master level.

Delete the link only that is attached to the instance where this error message occurs and change the level numbers for the segments so that they are attached to the appropriate level.

(1198) ERROR: Level <level number> Should Be Placed Directly Beneath Parent Level

Outbound map flow has errors.

Check placement of entries in this flow table to ensure that parent and child levels flow correctly.

(1199) ERROR: Flow Errors In Outstate Map – Run Aborted

Outbound map flow has errors.

Check placement of entries in flow table.