RE: Debugger question....

[Chris Proctor <cproctor@xxxxxxxxxxxxxx>]

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]
Wow! Thanks for the information, Xuan. I'll give it a try.  Great way to
start the day! ha ha.
Thanks again

Chris

-----Original Message-----
From: xuanchen@ca.ibm.com [mailto:xuanchen@ca.ibm.com]
Sent: Wednesday, November 14, 2001 8:02 AM
To: code400-l@midrange.com
Cc: berestet@ca.ibm.com
Subject: Re: Debugger question....


Chris,

I tried to find out the notes I sent before, but couldn't find it.  I will
explain your second question here.

Due to some problem exists in CODE editor and debugger integration, we do
not provide the user the chance to enter ProgramToDebug and ProgramToCall
separately.  This problem will be fixed by next debugger release.  To walk
around with this problem right now, you have two alternatives.

   If your ProgramToCall  is also debuggable, you could load its source
   into CODE editor, and start the debug session with this program.  Once
   debugger stops at the first debugger statement of the ProgramToCall ,
   you could switch to the Program Pane in the debugger UI, and choose
   Program -> Add Program menu items to invoke Add Program dialog to add
   the ProgramToDebug into debugger.  You could set breakpoint at the
   ProgramToDebug and start debugging it.
   If your ProgramToCall  does not have debug data, you need to invoke
   debugger outside CODE editor.  You could do the following steps:
     From Start --> Program -->...  to invoke your debugger.
     In the AS400 pane of the debugger Attach dialog, enter the name of the
     ProgramToDebug in it Program to Debug field.
     Entry the job name of the job you want to debug.  Make sure Step into
     is checked.  Press Attach... button.
     A message will show up asking you to start your application in the
     AS/400.  Go to your 5250 screen, and call your ProgramToCall.  Since
     ProgramToCall does not have any debug data, debugger should stop at
     the first debuggable statement in ProgramToDebug.


   Thanks,

   Xuan Chen, Debug for iSeries
   (905) 413-3769 T/L 969-3769
   xuanchen@ca.ibm.com



Vadim Berestetsky/Toronto/IBM@IBMCA@midrange.com on 11/13/2001 06:16:13 PM

Please respond to code400-l@midrange.com

Sent by:  code400-l-admin@midrange.com


To:   code400-l@midrange.com
cc:
Subject:  Re: Debugger question....


Hi Chris,

To answer your first question:
It is sufficient to set 'Update Production Files' to YES via the 'Debugger
Settings' dialog
for a specific AS/400 host once. This setting is remembered as long as you
use the same
TCP/IP name for that AS/400.

The second topic I believe has been discussed by Xuan Chen at length in her
previous postings.
Let me know if you can't find her notes, then I'll try to dig them out for
you.

Regards,
Vadim Berestetsky
Distributed Debugger Development
Phone (905) 413-4403; T/L  969-4403
Internet:  berestet@ca.ibm.com


Chris Proctor <cproctor@gartsports.com>@midrange.com on 11/13/2001 03:59:10
PM

Please respond to code400-l@midrange.com

Sent by:  code400-l-admin@midrange.com


To:   "CODE400-L (E-mail)" <CODE400-L@midrange.com>
cc:
Subject:  Debugger question....


This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]
Hi all,

Well, I'm trying to "master" the debugger, but I still run into problems.
My
question is, can I start the debugger from codeedit for a program that
updates a file? I always get the error that says "Cannot update while file
is UPDPROD(*NO)", but I don't see a prompt for it when going from codedit
into debug.

Also, in this case I'm calling a program that calls the program I'm trying
to debug. So, in that scenario where would I enter the program I want in
debug and where would I enter the program to call? Thanks for any
assistance!

Chris
_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l
or email: CODE400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.




_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l
or email: CODE400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.




_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l
or email: CODE400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.