× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.





Hi,

I'm using WDSC v7 (V 7.0.0.1 (7.0.0.20070402_0533)) on WinXPsr2 and
OS400 v5r4. Verify Connection reports all PTFs are correct, but the
callback to the RSE daemon fails (I don't need that for SEPs AFAIK.)

I am having trouble debugging two (or more) RPGLE programs with service
entry points. Both programs will stop in debug on the first call and at
any breakpoints I set when either is set up as a single SEP, but if I
set up two SEPs to stop either program (one calls the other via a CL
pgm) then the second program never stops.

Normally, I can step into the call from the first program to the second
program and it will come up correctly in the debug perspective without
having to set another SEP, but the two programs are linked by a CL (OPM)
program so I can not step into that from the first.

I have seen a note recently from Xuan Chen about using the "Clear
Service Entry Points" option on the SEP view's triangle menu, but this
made no difference. I couldn't see anything else relevant in the
archives.

I have had problems on and off with 'authority' for some time (due to
SOX) but as the SEP works on each program individually then this
probably isn't the problem. Does anyone else know what could be wrong?


Thanks in advance,
Paul.


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.