Fixed Length File Parsing
Infoveave Data Automation — Format Parsing
Mainframe flat file in. Structured table out. Columns defined by position.
Mainframe systems, government APIs, and banking institutions frequently deliver data in fixed-width flat files — each field starting at a fixed character position with a fixed length. Reading these files requires knowing the exact layout specification. Fixed Length File Parsing lets you define that specification — column name, start index, character length — and automatically extracts all fields from every row, producing a structured table ready for analytics or database loading.
What Fixed Length File Parsing does
Parse fixed-width flat files by defining each column's name, start index, and character length. Handle mainframe exports, COBOL data files, and government reporting formats without custom code or manual extraction.
When to use Fixed Length File Parsing
- You receive data from a mainframe, COBOL system, or legacy application in fixed-width format
- A government body or regulatory agency delivers reports where each field occupies a defined character range
- Your banking or insurance data provider delivers flat files with a positional column layout specification
- You need to automate ingestion of fixed-width files that arrive regularly and have a consistent layout
When to avoid it
- Your files use delimiters (comma, tab, pipe) — use Read CSV Files instead
- Your files have a complex multi-segment structure — use Custom File Parsing with a JSON template
- Your files are binary formats (DBF, fixed-width Excel) — contact Infoveave support for binary format handling
Where it fits in your Infoveave automation
Fixed Length File Parsing is one step inside a multi-step Infoveave workflow. Chain it with other activities — no code, no manual hand-offs.
Build this workflow visually in Infoveave Data Automation — drag, connect, and schedule with no infrastructure setup.
How teams use Fixed Length File Parsing
Real scenarios where this transformation saves hours of manual work.
Mainframe GL Export
A legacy general ledger system produces a nightly fixed-width export with account codes, journal entries, and amounts in defined character positions. Fixed Length File Parsing extracts all fields using the layout spec, feeding the reconciliation pipeline without any manual column splitting.
Regulatory Filing Ingestion
A tax authority delivers compliance datasets as fixed-width flat files. The workflow uses Fixed Length File Parsing to extract taxpayer ID, filing period, amount, and status from each 120-character-wide record, loading results into the compliance tracking database.
Insurance Eligibility File Processing
Insurance eligibility data from a clearing house arrives as a fixed-length file with member ID, plan code, and coverage dates at fixed positions. Fixed Length File Parsing extracts all member records, enabling the workflow to update the eligibility database automatically.
See Fixed Length File Parsing in action
Input data (left) is transformed using the configuration below. The output table (right) is ready for dashboards or downstream steps.
CustomerID (0,6), LastName (6,10), FirstName (16,10), Amount (26,8), Units (34,3), Date (37,10)UTF-8\n10000Input Data
| Raw fixed-width record |
|---|
| JOH001Smith John 0034560042026-04-11 |
| JAN002Jones Janet 0018900012026-04-11 |
Output Data
| CustomerID | LastName | FirstName | Amount | Units | Date |
|---|---|---|---|---|---|
| JOH001 | Smith | John | 003456 | 004 | 2026-04-11 |
| JAN002 | Jones | Janet | 001890 | 001 | 2026-04-11 |
Configuration
Key fields to configure in the Infoveave workflow builder. Full reference available in the documentation.
Column Definitions
Define each column with three properties: Name (the column label in the output), Start Index (the 0-based character position where the field begins), and Length (the number of characters in the field). Obtain the layout specification from the file provider's technical documentation.
File Encoding
Character encoding of the source file. Mainframe files often use IBM EBCDIC or ISO-8859-1. Confirm with the source system — a wrong encoding will produce garbled output.
Line Separator
Character sequence separating rows. Typically \n (Unix) or \r\n (Windows/mainframe exports). Some mainframe exports use no separator (each row is exactly N characters); consult the spec.
Max Row Lookup Count
Maximum rows the parser processes. Default 10,000. Increase for large compliance files; reduce for performance constraints.
Frequently asked questions
Everything you need to know about Fixed Length File Parsing in Infoveave.
Also in Format Parsing — and what runs before & after
Transformations in the same family as Fixed Length File Parsing, often chained together in the same Infoveave workflow.
Part of Infoveave Data Automation
80+ transformations. Zero manual steps.
Fixed Length File Parsing is one of over 80 transformation activities available inside Infoveave workflows. Chain transformations together — no code, no exports, no waiting for IT.
Ready to see Infoveave in action?
