Oninit
Talk to an expert →

Informix Error -4601: No 4GL module by specified name found.

Cause and resolution

No 4GL module by specified name found.

The source module specified cannot be found as a file module.4gl. The system looks in the current directory and in directories named in the DBPATH environment variable. Possibly the module name was misspelled, or the file might have been renamed, or possibly the DBPATH variable is not set correctly.

Oninit® Troubleshooting Guidance

Reasons / Common Causes

-4601 fires when the Application Builder can't locate a named 4GL source module — per the official guidance, it looks for module.4gl in the current directory and in each directory named in the DBPATH environment variable.

  1. The module name was misspelled, per the official guidance — the first named cause.
  2. The module file was renamed, per the official guidance — the second named cause.
  3. DBPATH is not set correctly, per the official guidance — the third named cause.
Solutions / Resolution
  1. Check the spelling of the module name.
  2. Confirm the module file (module.4gl) hasn't been renamed or moved.
  3. Verify DBPATH includes the directory containing the module file.
Examples
Checking DBPATH for a module
$ echo $DBPATH
$ find . $(echo $DBPATH | tr ':' ' ') -name "order_entry.4gl" 2>/dev/null
Diagnostic Checks
  1. Check the module name's spelling, confirm module.4gl exists where expected, and verify DBPATH includes that directory.
Related Errors / Related Topics
  • -4600 — "No form by specified name found." The same lookup failure, for .frm form files rather than .4gl source modules.
  • -4602 — "No 4GL program by specified name found." A related lookup failure, for a multi-module program in the program database rather than a single source file.
  • -4603 — "No executable 4GL program by specified name found." The same lookup failure, for module.4go executable files rather than .4gl source modules.

A named 4GL source module (module.4gl) couldn't be located via the current directory or DBPATH — check its spelling, location, and the DBPATH setting.