|
Mike, I did remember there was a problem wtih debugger because of problems in SQL pre-compiler. Which version of OS400 you are using? I will try to dig out the SQL PTF number for it. Thanks. Thanks, Xuan Chen, Problem Determination Tools for iSeries (905) 413-3769 T/L 969-3769 xuanchen@xxxxxxxxxx Mike <koldark@xxxxxxxx m> To Sent by: "Websphere Development Studio wdsci-l-bounces+x Client for iSeries" uanchen=ca.ibm.co <wdsci-l@xxxxxxxxxxxx> m@xxxxxxxxxxxx cc Li Ding/Toronto/IBM@IBMCA Subject 08/11/2006 10:37 Re: [WDSCI-L] Error 316 when trying AM to Debug RPG on V5R3 Please respond to Websphere Development Studio Client for iSeries <wdsci-l@midrange .com> See below for answers. On 8/10/06, Xuan Chen <xuanchen@xxxxxxxxxx> wrote:
Mike, If you run your batch program as interactive debug session, did you still get the same error? I want to see if it is program specific, or debug session invocation specific.
This works fine as well does another interactive program. The program I am trying to debug can be debugged using STRDBG on the command line. Could you please also try to see if you could use service entry point to
debug that program (instead of using STRRSESVR command)? (if your
program
is an ILE program).
I tried this, the batch report worked. The interactive one didn't. Another interactive program does work. To do that, please follow the steps below:
Locate your program in RSE, right click and choose Debug (Service Entry) -> Set Service Entry Point. After the service entry point is set, go to your 5250 session (not the
one
associated with RSE), and invoke your application. Do you get the same error? Thanks, Xuan Chen, Problem Determination Tools for iSeries
It apprears like it might be something with that program. The only other "weird" thing about this program is that I had problems compiling it at one point. To make a long story short. Something I have done many times previously, the SQL precompiler wouldn't recognize. I copied similar code from another program compiled (worked), inserted all of my code replacing only what was needed to be replaced. This worked as well and I was able to continue on. Could this problem have affected the debuging somehow? -- Mike Wills http://mikewills.name - Blog http://theriverbendpodcast.com - Podcast -- This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l 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.
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.