Hi Greg,
Thanks for the response. I did notice that the value of the last positional field in the inbound flat file is shorter than the schema defined. For instance, the last positional field of the Body schema is defined as 30, but the actually flat file data shows only few characters followed by line-feed. I am not sure how the flat file parser interprets it and what schema attributes can do anything about it. I did set \”Allow early termination\” to true, without luck.
The error indicates the parser doesn’t know when to stop parsiing the Body section of the data. It treats the Trailer as Body section, which cause the pipeline validation failed.
I tried both single schema mapping and separate Body/Trailer schema ways, but no luck yet. It could be the issue of schema attribute(s) setting. One is using single Positional Flat File schema with both Body and Trailer schema in it, and map to another XML schema file with only Body in it.
The other is using separate Body and Trailer schema, as well as custom Flat File pipeline. I was able to validate both Body and Trailer instances successfully. However, it error out when I ran through the Receive pipeline.
It seems either way is fine with inbound file having single record and trailer in it, but not with multiple records in Body section of the file.
For example:
1. Inbound file works:
Filed1a Field1b field1c …
EOF
2. Inbound file doesn’t work:
Filed1a Field1b field1c …
Filed2a Field2b field2c …
Filed3a Field3b field3c …
EOF
Any thought?
Thanks in advance,