Informix Error -35200: Fatal parse error; string.
Cause and resolution
Fatal parse error; string.
If you get this error, note all circumstances and contact IBM Technical Support.
Oninit® Troubleshooting Guidance
Reasons / Common Causes
-35200 is a critical internal preprocessor error — per the official guidance, no application-level cause is named; the only documented response is to escalate it.
- A genuine internal fault in the ESQL/Ada preprocessor's parser, per the official guidance's framing — no other documented application-level cause is named.
Solutions / Resolution
- Note all circumstances and contact IBM Technical Support, per the official guidance — this is the documented, only resolution path.
Examples
N/A
No specific triggering statement is documented — this is a critical internal parser fault, and
the official text itself is just a string placeholder for whatever detail the parser attaches.
Diagnostic Checks
- Capture the exact circumstances (source file, statement being compiled, the
stringdetail the parser attached) at the time -35200 occurred, per the official guidance's own escalation path.
Related Errors / Related Topics
- -35202 — "Too many nested blocks." Another "contact IBM Technical Support" internal preprocessor fault.
- -35208 — "INTERNAL ERROR... case error." Same internal-fault family, explicitly labeled
INTERNAL ERROR. - -35209 — "INTERNAL ERROR: ...assertion error." Same family.
- -35210 — "INTERNAL ERROR: feature... not yet implemented." Same family.
A critical internal parser fault with no documented application-level trigger — capture full
circumstances, including the attached string detail, and escalate to IBM Technical Support.