On outbound map level changes

Table 1-13 lists the format, cause, and solution (if applicable) for the ECMap messages related to outbound map level changes, in numeric order by message number.

Table 1-13: ECMap messages related to trading partners

Message

Cause

Solution

(5030) TRACE: Level <level number>, combined files Break flag was set

This message occurs when Verbose Trace is on. Informational message indicates that when a read record was performed, the record did not match the defined record type and the Multiple Files switch has been turned off. Map continues to search for the correct level to go to, based on this record type.

(5031) TRACE: Level <level number>, End-of-File Break, normal end of transaction

This message occurs when Verbose Trace is on. Informational message occurs at the Master Record level indicating the end of the file has been reached and the transaction has ended normally.

(5033) TRACE: Level <level number>, End-of-File Break

This message occurs when Verbose Trace is on. Informational message indicates the end of the file has been reached.

(5034) TRACE: Level <level number>, generated Keyfield Break - Old Keyfield: <value> New Keyfield: <value> Length: <length>

(5035) TRACE: Level <level number>, Keyfield Break - Old Keyfield: <value> New Keyfield: <value>

(5036) TRACE: Level <level number>, generated Breakfield Break - Old Breakfield: <value> New Breakfield: <value> Length: <length>

(5037) TRACE: Level <level number>, Breakfield Break - Old Breakfield: <value> New Breakfield: <value>

(5038) TRACE: Level <level number>, generated Keyfield Linkfield Break, Keyfield: <value> Linkfield: <value> Length: <length>

Occurs when Verbose Trace is on. Informational message indicates a mismatch for the Keyfield and Linkfield. Values of the various fields are displayed in the message.

(5039) ERROR: Level <level number>, Keyfield does not match Linkfield and current record is not optional; Keyfield: <field name> Linkfield: <field name>

Is received when processing multiple files. A record has just been read that is defined as a key field and must match a field in another record, and the field is not optional.

Flow can be incorrect. Modify flow to indicate you are reading this record out of sequence.

(5040) TRACE: Level <level number>, Keyfield does not match Linkfield and current record is optional; Keyfield: <field name> Linkfield: <field name>

Occurs when Verbose Trace is on. Informational message occurs when reading multiple files where the key fields do not match. No error is generated since the record is optional.

(5041) TRACE: after Keyfield/Linkfield Break

Occurs when Verbose Trace is on. Informational message reports progress after encountering a Keyfield / Linkfield Break.

(5042) TRACE: Level <level number>, TOP-OF-LOOP processing <file type> files < > Loop Depth:- < > New Level: < > Brk Level: < >

Occurs when Verbose Trace is on. Informational message appears at the top of the Trace file that reports the level, the file type, the loop depth, the new level and break level.

(5043) TRACE: Level <level number>, Processing LINK ONLY

Occurs when Verbose Trace is on. Informational message reports level number during link only process.

The format, cause, and solution (if applicable) for the ECMap messages related to map level changes are listed below, in numeric order by message number.

(5044) FATAL: Record Type Break and Level <level number>, Not Optional

(5045) ERROR: Level <level number>, Missing Optional Record

(5046) FATAL: File <file name> Missing No Record Type Field

Received when processing multiple files in that you are reading two files and matching them up by fields. A record has just been read that is defined as a key field and must match a field in another record, and the field is not optional.

Solution 1: This record can in fact by optional. Change inbound flow so that reading this record is optional.

Solution 2: Flow can be incorrect. Modify flow to indicate you are reading this record out of sequence.

Solution 3: Using wrong field to link the two records. Change inbound flow.

(5047) TRACE: Reading File <file name> Record <record name>

Occurs when Verbose Trace is on. Informational message indicates current reading of a file and record. Also indicates end of file for the file name specified.

(5048) TRACE: <I/O operation > File <file name> Record <record name>

Occurs when Verbose Trace is on. Informational message indicates reads, writes and SQL selects and inserts for a file and record.

(5049) TRACE: Rule <rule number> Executing Procedure <procedure name>

Occurs when Verbose Trace is on. Informational message indicates execution of procedure.

(5050) TRACE: < > Writing File <file name> Record <record name>

(5051) FATAL: Combined File Missing Record Type

(5052) TRACE: Writing File < > < > < >

(5999) ERROR: Failed to Get Status Information on File <file name>