Oninit
Talk to an expert →

Informix Error -16327: Cannot locate file filename.

Cause and resolution

Cannot locate file filename.

Possibly you omitted or misspelled the filename of a .4db input file (either in a READ command or following the -F command-line option), or you misspelled the filename or pathname of a .4gl source file in a VIEW command or on the command line.

If filename is spelled correctly and names a file that exists, then you might need to specify a complete pathname. You must specify the full pathname of a file when you refer to a .4db file that is not in the current directory, or to a .4gl source file that is not in the current directory or any directory that you specify with the -I command-line option.

Oninit® Troubleshooting Guidance

Reasons / Common Causes

-16327 fires when the Debugger can't find a named .4db or .4gl file — per the official guidance.

  1. An omitted or misspelled .4db filename, per the official guidance — in a READ command or following -F.
  2. A misspelled .4gl source filename or pathname, per the official guidance — in a VIEW command or on the command line.
  3. A file that exists but needs its full pathname, per the official guidance — required for a .4db file outside the current directory, or a .4gl file outside the current directory and any -I search paths.
Solutions / Resolution
  1. Check the filename's spelling, per the official guidance.
  2. Specify the full pathname if the file isn't in the current directory (or, for .4gl files, an -I search path), per the official guidance.
Examples
A file reference without its full pathname
> VIEW myprogram.4gl
Corrected
> VIEW /usr/local/src/myprogram.4gl
Diagnostic Checks
  1. Check the filename's spelling, and whether it needs a full pathname given its actual location relative to the current directory and any -I search paths.
Related Errors / Related Topics
  • -16314 — "Missing filename." A related file-reference error, about the filename being entirely absent rather than misspelled or needing a full path.
  • -16329 — "Pathname too long." A related file-reference error, about the pathname exceeding the Debugger's 70-character limit.

The named file couldn't be located — check its spelling and whether it needs a full pathname.