Informix Error -16351
-16351 Variable variable-name could not be located.
The Debugger cannot reference a variable unless it is defined in a 4GL module. For 4GL variables, check that you entered the variable name correctly. If the variable is not in the current function or module, you must qualify its name. See the section on "Scope of Reference" in the Debugger manual. (This message can appear if you enter what you intend to be a module name in a BREAK or TRACE command, but you omit the dot at the end of the name.)
Oninit® Troubleshooting Guidance
Reasons / Common Causes
-16351 fires when the Debugger can't reference a named variable — per the official guidance. A variable must be defined in a 4GL module to be referenced.
- A misspelled variable name, per the official guidance — the first named cause.
- A variable outside the current function/module referenced without qualification, per the official guidance — the second named cause; see "Scope of Reference" in the Debugger manual.
- A module name in a
BREAK/TRACEcommand missing its trailing dot, per the official guidance — a noted cause of this same message appearing unexpectedly.
Solutions / Resolution
- Check the variable name's spelling, per the official guidance.
- Qualify the variable's name if it isn't in the current function/module, per the official guidance.
- Check for a missing trailing dot after a module name in
BREAK/TRACE, per the official guidance.
Examples
A module name missing its trailing dot
> BREAK mymodule
Corrected
> BREAK mymodule.10
Diagnostic Checks
- Check the variable's spelling and scope-qualification, and whether the intended
input was actually a
BREAK/TRACEmodule reference missing its dot.
Related Errors / Related Topics
No closely related error codes are cross-referenced for -16351 in this set yet.
A variable couldn't be located — check its spelling, scope qualification, or whether a
BREAK/TRACE module reference is missing its trailing dot.