Informix Error -21615: Output file could not be opened for read/write.
Cause and resolution
Output file could not be opened for read/write.
If this internal error recurs, note all circumstances and contact IBM Informix Technical Support.
Oninit® Troubleshooting Guidance
Reasons / Common Causes
-21615 is an internal mkmessage error — per the official guidance, no user-actionable
cause is documented beyond the output file failing to open for read/write.
- The output file failing to open for read/write, 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 the output file's existence and read/write permissions, and escalate to IBM Informix Technical Support if the error recurs.
Related Errors / Related Topics
- -21602 — "Input file could not be opened." A related file-open error, on the input file rather than the output file.
- -21603 — "Output file could not be created." A related output-file error, on creating the file rather than opening an existing one for read/write.
mkmessage couldn't open its output file for read/write — check its existence and
permissions.