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.

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).

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
(905) 413-3769 T/L 969-3769
xuanchen@xxxxxxxxxx




                                                                           
             Mike                                                          
             <koldark@xxxxxxxx                                             
             m>                                                         To 
             Sent by:                  "Websphere Development Studio       
             wdsci-l-bounces@m         Client for iSeries"                 
             idrange.com               <wdsci-l@xxxxxxxxxxxx>              
                                                                        cc 
                                       Li Ding/Toronto/IBM@IBMCA           
             08/10/2006 05:27                                      Subject 
             PM                        Re: [WDSCI-L] Error 316 when trying 
                                       to Debug RPG on V5R3                
                                                                           
             Please respond to                                             
                 Websphere                                                 
                Development                                                
             Studio Client for                                             
                  iSeries                                                  
             <wdsci-l@midrange                                             
                   .com>                                                   
                                                                           
                                                                           




I can debug a batch program just fine. When I try to debug an interactive
program, it gives me the mentioned error. I start up the 5250 emulatator
and
type "STRRSESVR NAME(Mankato)". I then start up my debug session in WDSC.
Let me know how much more you need. I could take screen shots.

On 8/10/06, Xuan Chen <xuanchen@xxxxxxxxxx> wrote:

Mike,

Could you please check if you have all the PTFs required?  (please right
click on one of the subsystem in RSE, and choose "Verify Connection...")

And please also try if you close the Variable view in the Debug
perspective
before you start your next debug session.

If you still have problem, please let me know how  you start your debug
session (step by step instructions).  Thanks.

Thanks,

Xuan Chen,  Problem Determination Tools for iSeries
(905) 413-3769 T/L 969-3769
xuanchen@xxxxxxxxxx


--
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 thread ...

Follow-Ups:
Replies:

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.