Symptom
A batch XML file contains many customers and one of them is missing a closing tag.
The engine stops while parsing the input instead of continuing with the later customers.
Raising or changing SYS_CustInvalidDataLevel makes no difference, which is usually the point where the investigation stalls: the setting that is supposed to handle bad customers does nothing.
Cause
SYS_CustInvalidDataLevel governs invalid data mappings and validation behavior for structurally valid records. It cannot repair malformed XML structure.
A missing end tag is a document-level parsing failure. Without the closing tag the parser cannot reliably determine where the broken customer ends and where the next one begins, so there is no safe resume point. No skip setting can restore structure the document does not contain.
Fix
Repair the structure before the engine sees it. The upstream producer should emit well-formed XML, or an integration step should split and validate customer records before composition. A lightweight pre-parse validation in the job chain costs seconds and converts a batch abort into a rejected record with a clear report.
For the requirement people usually have in mind here, skipping a structurally valid customer whose mapped value is missing or invalid, use the controls built for it: the data area's Action if data not found behavior, including Missing skip document where appropriate, plus variable validation for invalid values.
Test the two failure classes separately: one XML with a broken closing tag, one well-formed XML with an invalid customer value. They fail in different layers and are handled by different mechanisms, and a test that mixes them proves nothing about either.
Parser recovery is decided before composition
A later engine error can appear after composition starts, but the parser's ability to recover the XML hierarchy was already decided at parse time. Log timing does not turn a structural error into a skippable customer error.