Informix Error -35038: This statement uses an Informix extension to the X/Open standard, near identifier or symbol name

Reasons / Common Causes

-35038 fires only when the ESQL preprocessor is run with the -xopen option — per the official guidance, it flags any statement using Informix-specific SQL syntax that the X/Open standard doesn't define.

1. The -xopen compile option being used, per the official guidance — this warning is suppressed entirely without it.
2. An Informix-specific extension appearing in the flagged statement, per the official guidance, near the named identifier or symbol.

Solutions / Resolution

1. Revise the statement to meet the X/Open standard, per the official guidance, if X/Open portability is actually required.
2. If X/Open compliance isn't actually a requirement, drop the -xopen option instead of rewriting the statement.

Examples

N/A

No specific triggering statement is documented beyond "an Informix extension... near identifier or symbol name" — the exact offending syntax varies per statement.

Diagnostic Checks

1. Confirm whether -xopen is actually required for this build before investing in rewriting the flagged statement.
2. Identify the specific Informix extension in use at the named identifier/symbol.

Related Errors / Related Topics

• -35227 — Shares this exact message text; appears to be the same X/Open-extension warning reused at a second code position in this set.
• -35036 — "This line uses an Informix extension to ISO/ANSI SQL..." The ANSI-compliance-mode counterpart to this X/Open-compliance-mode warning.
• -35226 — Shares -35036's message text; the ANSI counterpart to -35227.

An Informix-specific SQL extension triggered this only because -xopen was in effect — revise the statement, or drop -xopen if X/Open portability isn't actually needed.