terminator / error
EL2006
terminator.edifact-segment
Applies to: edifact
What it catches and why it matters
Segment is not closed by the segment terminator in force, which in practice means the file was truncated mid-segment.
Failing example
These synthetic fragments illustrate the defect; they are not complete interchange files. Backslash escapes name bytes such as \r (CR) and \n (LF).
UNZ+1+EXAMPLE (end of file without the declared apostrophe terminator)
How to fix it
Check for truncation. Restore the complete export, or append the active segment terminator if that is the only missing byte. Respect the UNA release character.
False positives and limits
A malformed UNA declaration or a released apostrophe can change where a segment ends. Verify the service string before editing terminators.
Acknowledgments and suppression
No direct acknowledgment code is mapped for this rule. CONTRL references use syntax-error element 0085, not action element 0083. UCI, UCF and UCM report interchange, group and message service-segment errors respectively. A missing or unreadable header can prevent a valid CONTRL response. Truncation, orphaned envelopes and data outside an interchange have no single mapping here. Sources: https://service.gefeg.com/jwg1/Archive/v3/mt/m01.htm https://service.gefeg.com/jwg1/Archive/cl/v3/21a/cl16.htm Suppress the rule with --disable EL2006, or list it under "disable" in .edilint.yml. To accept the occurrences a file already has without suppressing the rule, record them with --write-baseline and run with --baseline. Reference: https://crb2nu.github.io/edilint/rules/EL2006.html