I wonder if you are doing the "Wrong Debug" for Java, versus for the IBM i...
Have you tried the View: "IBM I Service Entry Points" yet? Add the program to break on a Service Point. And it pops up in Debug no matter where the program is called, Call at command line, submitted to batch, from Stored-Procedure, etc...
When debugging a job, be sure to use "DEBUG Configuration" versus the Java-Debug. Sadly, it has happen to me. Not really sure if you are doing that by mistake or not... Just thought I would toss that out...
Run>Debug Configurations. And then pick "IBM i: Debug Job" to set up your debug.
Hope this might help...
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Mark Brier
Sent: Monday, May 12, 2014 10:08 AM
Subject: [WDSCI-L] SQLRPLGE Debug Issue in RPD 8.5.1
I recently had to reload this version of RDP on my new PC, and since
then I can no longer see variables when debugging an SQLRPGLE program.
When the program hits a break point, the variable box shows "*No local
variables are available for the selected stack frame". This was
working fine on my old pc, so I'm guessing that there is a setting to
fix this, but I can't see to find where it is. Any suggestions?
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,
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l
As an Amazon Associate we earn from qualifying purchases.