Informix Error -16346: Cannot open output file filename.
Cause and resolution
Cannot open output file filename.
Check if the output file already exists but is damaged or write protected. In UNIX, check that you have permission to write in the specified directory (or in the current directory if you specified no pathname).
Oninit® Troubleshooting Guidance
Reasons / Common Causes
-16346 fires when the Debugger can't open a named output file — per the official guidance.
- The output file already existing but damaged or write-protected, per the official guidance — the first named cause.
- On UNIX, no write permission in the target directory (or the current directory, if no pathname was given), per the official guidance — the second named cause.
Solutions / Resolution
- Check whether the output file exists but is damaged or write-protected, per the official guidance.
- On UNIX, check write permission on the target directory, per the official guidance.
Examples
Checking directory write permission
$ ls -ld .
Diagnostic Checks
- Check the output file's existing state and the target directory's write permissions.
Related Errors / Related Topics
- -16330 — "Cannot open file filename for reading." The mirror-image error, about opening a file for reading rather than writing.
The Debugger couldn't open the named output file — check for a damaged/write-protected existing file, or a permissions issue on the target directory.