Re: Communications Failure when Debugging

OK, I've narrowed it down a bit. 

It started happenning after I added a procedure that has an extra bit of
SQL  in it (The already-existing SQL is embedded in a subroutine called
from the mainline).  So I commented out that procedure and it's
prototype, recompiled, and now I can debug again.  

When the procedure is in there, the program compiles and the procedure
works, so I can't imagine there could be anything fundamentally wrong
with including SQL statements inside of procedures, but is there
something the debugger doesn't like about it ?  

(Oh, and I also wanted to mention the secondary issue after the error
occurs: I can't remove the service entry point without completely
locking up RSE.  I did find a work around to this, which is to end the
remote server debug job, which also terminates my SEP).  

G

|-----Original Message-----
|From: wdsci-l-bounces@xxxxxxxxxxxx
[mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
|Behalf Of Fleming, Greg (ED)
|Sent: Wednesday, May 17, 2006 8:42 AM
|To: wdsci-l@xxxxxxxxxxxx
|Subject: [WDSCI-L] Communications Failure when Debugging
|
|Here's a weird one.
|
|I've been working on an RPGSQL program and happily debugging using the
|service entry point, when I started receiving a communications error
|each time after I submit my job and the debugger starts to kick in.
|
|The weird bit is that it only seems to affect this particular program.
|I can debug other programs without trouble, and I can even debug this
|one if I set the service entry point on the program that calls it, then
|step into it.  But if I set the SEP on this particular program, I get
|the communications error.
|
|We're at 6.0.1.1 and the updater says there aren't any updates
|available.
|
|Any ideas ?
|Greg Fleming
|Programmer/Analyst