Informix Error -21602: Input file could not be opened.
Cause and resolution
Input file could not be opened.
If this internal error recurs, note all circumstances and contact IBM Informix Technical Support.
Oninit® Troubleshooting Guidance
Reasons / Common Causes
-21602 is an internal mkmessage error — per the official guidance, no user-actionable
cause is documented beyond the input file failing to open.
- The input file failing to open, per the official guidance — no further named detail; check the file's existence and permissions.
Solutions / Resolution
- If this internal error recurs, note all circumstances and contact IBM Informix Technical Support, per the official guidance.
Examples
N/A
No specific triggering statement is documented — this is reported as an internal error.
Diagnostic Checks
- Check that the input file exists and is readable, and escalate to IBM Informix Technical Support if the error recurs.
Related Errors / Related Topics
- -21603 — "Output file could not be created." The mirror-image error, on the output file rather than the input file.
- -21615 — "Output file could not be opened for read/write." A related output-file error, on opening for read/write rather than creating.
mkmessage couldn't open its input file — check that it exists and is readable.