Re: RDI 9.5.a "**ERROR decoding EStdSgring**"

On 11/15/2016 2:53 PM, Ken Killian wrote:

Brand new test program works:

**free
dcl-s x int(10);
x = 2 + 2;
*inlr = *on;
return;

The other program is using Java, so maybe something on Java got reset or something. I don't have a clue.

Green Screen Debug works, RDI 9.5.1 debug works "most of the time", but not all the of the time.

Question: When you debugged via green screen, did you start a new job,
or debug in the same job that threw the error with SEP?

I recall that you debug different to the way I do it; are you jumping
into a running program, or setting the SEP and then calling the program?

Recompile the program, and now I can add a SEP, but it doesn't not start up in debug...

This sounds different to your first post. What are the symptoms now?
What does 'does not start up in debug' mean? Does the program run but
RDi not break?

Architecture-wise, RDI / SEP debugging is done via a debug server. Is
there an error message relating to the debug server? If your colleagues
are free, perhaps you can try ENDDBGSVR / STRDBGSVR (ending the debug
server will kick everyone out of SEP).