Informix Error -16301: A syntax error has occurred.
Cause and resolution
A syntax error has occurred.
A syntax error has been detected in a Debugger command. Check that you have not misspelled or omitted a keyword or identifier, included an extra command argument, or placed keywords out of sequence. Check if you have omitted parentheses after a function name in a CALL command or included them in a VIEW command. To display a two-page synopsis of all the commands, enter help all.
Oninit® Troubleshooting Guidance
Reasons / Common Causes
-16301 fires when a syntax error is detected in a Debugger command — per the official guidance.
- A misspelled or omitted keyword or identifier, per the official guidance.
- An extra command argument, or keywords placed out of sequence, per the official guidance.
- Omitted parentheses after a function name in a
CALLcommand, or included parentheses in aVIEWcommand, per the official guidance.
Solutions / Resolution
- Check for a misspelled/omitted keyword, an extra argument, or keywords out of sequence, per the official guidance.
- Check
CALL/VIEWcommand parentheses usage, per the official guidance. - Enter
help allfor a two-page synopsis of all commands, per the official guidance.
Examples
Checking the command reference
> help all
Diagnostic Checks
- Check the command's spelling, argument count, and keyword order, and consult
help allif unsure of the correct syntax.
Related Errors / Related Topics
- -16302 — "An illegal character has been found in the command." A related command-syntax error, about disallowed characters rather than structural syntax.
- -16311 — "Command name is not recognized." A related command error, about the command name itself being unrecognized rather than a syntax error within an otherwise valid command.
A Debugger command has a syntax error — check spelling, argument count, and keyword order,
or run help all.