Informix Error -1381: Cannot execute another runner when debugging.
Cause and resolution
Cannot execute another runner when debugging.
An instance of the 4GL runner is currently executing. While you are debugging, you cannot launch additional instances of the runner through a RUN command, the RUN accelerator button, or directly from Windows. To launch a new instance of the runner, first quit the currently running 4GL application.
Oninit® Troubleshooting Guidance
Reasons / Common Causes
-1381 fires when a second instance of the 4GL runner is launched while already debugging — per
the official guidance, this applies whether the second instance is started via a RUN command,
the RUN accelerator button, or a direct Windows launch.
- A second runner instance launched while a debugging session is already active, per the official guidance — the direct, only cause.
Solutions / Resolution
- Exit the currently running 4GL application before launching a new instance, per the official guidance.
Examples
N/A
No specific triggering statement is documented — this is an environment-state restriction in the Programmer's Environment/debugger.
Diagnostic Checks
- Check whether a 4GL debugging session is already active, and exit it before launching another instance.
Related Errors / Related Topics
No closely related error codes are cross-referenced for -1381 in this set yet.
A second runner instance was launched while already debugging — exit the current session first.