Fixed Length Parser

FREE

More actions

Fixed-length input

Layout definition

Positions and lengths are counted in Unicode code points. Byte-based offsets, including EBCDIC and legacy encodings, must first be converted or mapped to Unicode positions; they are not supported directly. Leading and trailing spaces are removed from each field, and fields containing only spaces are returned as empty.

Parsed preview

No parsed output generated yet.

Found something we could improve?

Practical usage guide

A practical workflow for Fixed Length Parser

Parse fixed-length and fixed-width files, inspect field positions, validate layouts and analyze flat file structures.

1. Prepare

Provide fixed-width text and a layout. Example: ABC001 with CODE,0,3 and NUMBER,3,3 produces CODE ABC and NUMBER 001.

2. Review

Inspect parsed fields, trimming and overlap diagnostics. Offsets start at zero and lengths count Unicode code points, not bytes.

3. Apply

Confirm the source layout uses the same position convention. Byte-based mainframe layouts can differ for multibyte characters; preserve leading zeros when fields are identifiers.

Verification before operational use

Use a representative case with the inputs needed to reproduce it.
Confirm the result in the authorized target environment when runtime versions, namespaces, extensions, permissions or system configuration can change the outcome.
Record the source, assumptions, tool settings and expected result so another reviewer can reproduce the check and distinguish verified facts from recommendations.