Oninit
Talk to an expert →

Informix Error -16387

-16387 Program is not currently being executed.

A WHERE command cannot display your active functions until after execution begins. Invoke the RUN or CALL command to begin execution, and then repeat the command. (You might first have to set a breakpoint to suspend execution before normal termination.) See the topic "Active Functions and Variables" in the Debugger manual.

Oninit® Troubleshooting Guidance

Reasons / Common Causes

-16387 fires when WHERE is used before execution has begun — per the official guidance.

  1. WHERE used before RUN/CALL has started execution, per the official guidance — the direct, only cause.
Solutions / Resolution
  1. Invoke RUN or CALL to begin execution, then repeat WHERE, per the official guidance.
  2. Set a breakpoint to suspend execution before normal termination, per the official guidance, if needed.
  3. See "Active Functions and Variables" in the Debugger manual, per the official guidance, for more detail.
Examples
WHERE before execution starts
> WHERE
Corrected
> RUN
> BREAK mymodule.10
> CONTINUE
> WHERE
Diagnostic Checks
  1. Check whether execution has started before using WHERE.
Related Errors / Related Topics
  • -16362 — "No current function." A related execution-state error, about no function being active generally.
  • -16373 — "Cannot print or make assignments before execution has started." The same execution-state restriction, applied to LET/DUMP/PRINT rather than WHERE.

WHERE was used before execution started — start it with RUN/CALL first.