Re: Hover eval in debug not working

Assuming your source code and your object match ...

Option 1: In RDi, right click on the source code anywhere on a
calculation spec. In the pop-up menu select 'Set Service Entry Point
...'

Option 2: In RSE right click on the source member and select 'Debug or
Code Coverage' and on the sub-menu select 'Set Service Entry Point'

Then when you execute the program on your 5250 terminal RDi debug will
kick in and open you source member automatically at the first instance
of executable code.

I compile my RPG modules and programs with DBGVIEW(*SOURCE).

Paul

On 2018-09-20 11:22, Ken Killian wrote:

That usually happens, when you change the source and did not recompile after the source update. So, it is awesome that RDi tells you the source does not match! <thumbs up>

Anyway, end debug, recompile. Then refresh debug and restart. Then no more warning message. Assuming you are using SEP, Service Entry Points!

Sent from my iPhone

On Sep 18, 2018, at 4:43 PM, Dan <dan27649@xxxxxxxxx> wrote:

On Tue, Sep 18, 2018 at 2:02 PM, Therrien, Paul <ptherrien@xxxxxxxxxxx>
wrote:

I never debug in listing mode though. I usually debug right in the member
source.

Um, can you explain this? I compile with DBGVIEW(*ALL) and I get a "live"
source member in my debug perspective. (RDi warns me if the source being
displayed doesn't match the program being debugged.) I never knew there
were alternatives.

- Dan
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/wdsci-l.