Re: Large variables in debug

Yes, that works. Thanks.

I must say that I have not used the debugger enough to be proficient and
learn most of its functions. I learned quickly how to display more
variable detail early but ended up not using the WDSC debugger much at
all because I cannot get to the command line (F9 in STRDBG) and work
with QTEMP objects (we often use QTEMP work files).

(Another wrench goes in the box.)

Since, were on the functions of the debugger, can anyone explain why I
cannot set a break point on a CL IF statement (but I can in STRDBG)?

Thanks, Matt

-----Original Message-----
From: MichaelQuigley@xxxxxxxxxx [mailto:MichaelQuigley@xxxxxxxxxx]
Sent: Friday, January 16, 2009 10:02 AM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] Large variables in debug

If you're referring to times when you've jumped around in the code and
need to return to the point in the source where the program is stopped,
click on the top line for the program in the Debug view. The Debug view

is the view in the top left corner (by default).

wdsci-l-bounces@xxxxxxxxxxxx wrote on 01/16/2009 07:59:43 AM:

----- Message from "Tyler, Matt" <matt.tyler@xxxxxxxxxxxxxx> on Thu,
15 Jan 2009 13:40:28 -0700 -----

To:

"Websphere Development Studio Client for iSeries"

<wdsci-l@xxxxxxxxxxxx>

Subject:

Re: [WDSCI-L] Large variables in debug

I just monitor the expression. The field will show in the Monitors
view. On the field right click and choose Monitor Expression. You

get

a pop-up with an entry line. Key in stuff like FIELD :X len or FIELD

:C

len (where len is the max size of the field). I though there was a
option to see the field attributes in the default debug views, but I
guess you just use the outline view for that.

Anyone have an idea how to just to the current stopped location? F5
does that for you in STRDBG, but I cannot find the same functionality

in

WDSC Debug.

Thanks, Matt