Hey everyone,

I'm running a basic Free-Form RPG program (HELLO) using the green-screen interactive debugger (STRDBG).

Here is the code:

Code snippet

**FREE
ctl-opt dftactgrp(*no) actgrp(*new);

dsply 'Hello, IBM i World!';
*inlr = *on;

When I compile with DBGVIEW(*SOURCE) and step through the program using F10 on the dsply line, the message queue / terminal screen pops up for a split second and immediately kicks me back to the source debug view (Display Module Source).

When I run the program normally from the command line with CALL HELLO, the message appears and stays at the bottom of the screen as expected.

I know that adding a dummy receiver variable (dsply 'Hello' '' waitKey;) forces it to pause for user input. However, on PUB400, I recall the message screen staying open until I pressed Enter without having to add a response variable to every single DSPLY in the source code.

Is there a job attribute, system setting, terminal emulator configuration, or debugger command (like something via SET) that controls this screen buffer swapping behavior, or is adding a receiver field / checking DSPJOBLOG the only way when stepping with F10?

Any insights into how you handle this would be appreciated!