Re: Debug issue in RDP V8.0

["Tarr, Kenneth" <Kenneth.Tarr@xxxxxxxxxxxxxxxxxx>]

I've seen the QB5SERVER job out there (I'm often the person who starts it after the system is IMLed), so next time this happens I will immediately look at that to see if the cause can be identified.  It's not a big issue given I just click on the debug icon a second time and it then seems to work.  I'll advise if it turns out to be something not on our end.

Thanks.

Ken

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Xuan Chen
Sent: Friday, March 25, 2011 3:51 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] Debug issue in RDP V8.0

Kenneth,

If you ran into problem "Connection with the debug server was lost", it 
probably meant some problem in the debugger server.  Please try to see if 
you can find any job name QB5SERVER under your user profile.  If yes, try 
to see if any error in that job log.  If you cannot find those job running 
any more, please try to see if any of the spool file related to that job. 
You need to open PMR for us to look more into the problem.

If the program you want to debug is ILE program, I recommand you use 
Service Entry Point support.  You just need to right click on the program 
and choose Debug (Service Entry) -> Set Service Entry Point.  Then just 
invoke whateven command you need to run in green screen.  When this 
program is executed, a debug session should be started with the program 
under debug.

Thanks,

Xuan Chen,  Problem Determination Tools for IBM i
(905) 413-3769 T/L 313-3769
xuanchen@xxxxxxxxxx





"Tarr, Kenneth" <Kenneth.Tarr@xxxxxxxxxxxxxxxxxx> 
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
25/03/2011 03:19 PM
Please respond to
Rational Developer for IBM i / Websphere Development Studio Client for 
System i & iSeries  <wdsci-l@xxxxxxxxxxxx>


To
"'Rational Developer for IBM i / Websphere Development Studio Client for 
System i & iSeries'" <wdsci-l@xxxxxxxxxxxx>
cc

Subject
[WDSCI-L] Debug issue in RDP V8.0






One of the features I am finding very useful is the debugger.  It's been 
able to accomplish some things that often are tedious to do in setting up 
a debug session.  One thing I especially like is the ability to jump into 
a program that is currently running.  This feature however doesn't always 
work, and I am wondering if anyone else has run into this problem.

I have a program running and it is currently running a CPYLIB command.  I 
start the debugger and am expecting a debug view of the program, with the 
ability to set breakpoints, etc.   Here's what happens:
 -- On some attempts, it works.  I am then able to catch a program while 
it's running, set breakpoints, view variables, etc.
 -- On some attempts, it returns "Connection with the debug server was 
lost".  When this happens, I try again and usually it then works.

I've also used this to hook into a program when an error occurs, which has 
helped me to get some variable values without the need to do a program 
dump.  I have more successes than failures in hooking up then.

Just curious if anyone has run into the above issue with the "Lost" 
message.

Thanks.
This e-mail and attachment(s) may contain information that is privileged, 
confidential, and/or exempt from disclosure under applicable law. If the 
reader of this message is not the intended recipient, you are hereby 
notified that any dissemination, distribution, or copy of this message is 
strictly prohibited. If received in error, please notify the sender 
immediately and delete/destroy the message and any copies thereof. 
Although Associated Banc-Corp and/or its affiliates (collectively 
"Associated") attempt to prevent the passage of viruses via e-mail and 
attachments thereto, Associated does not guarantee that either are 
virus-free, and accepts no liability for any damage sustained as a result 
of any such viruses. Any federal tax advice contained in this 
communication (including any attachments) is not intended or written to be 
used or referred to in the promoting, marketing, or recommending of any 
entity, investment plan or agreement, nor is such advice intended or 
written !
 to be used, and cannot be used, by a taxpayer for the purpose of avoiding 
penalties under the Internal Revenue Tax Code