Matt,
Understood, you can find all keys and what they are assigned to by doing Ctrl+Shift+L and then another Crtl+Shift+L. When you get the display click on the When column and the first section it shows you is the Debug keys, F9 is Show Stopping Threads.
Douglas Belcher
KV Pharmaceutical
St Louis, MO
Opinions expressed are not necessarily those of my employer
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Tyler, Matt
Sent: Friday, January 16, 2009 9:11 AM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Large variables in debug
No. I know about all those function keys. In STRDBG set a break point
on a line of code some where down in the code. Start the program so
that the debugger will stop at the break point. Then navigate to
another part of the source view. Now press F5 and you will be returned
to the last line stopped on in the debug session.
I want to know if WDSC Debugger has that same capability. I have not
found it so far myself.
Thanks, Matt
-----Original Message-----
From: DBelcher@xxxxxxxx [mailto:DBelcher@xxxxxxxx]
Sent: Thursday, January 15, 2009 2:21 PM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] Large variables in debug
Matt,
F5 will step through the code line by line and F8 will execute the
program to the next breakpoint, is that what you mean? Also if you
put a line of code in focus and right-click you can select Run To
Location. Ctrl+Shift+L should give you all the shortcuts.
(Ctrl+Shift+L again to get the Preferences)
Douglas Belcher
KV Pharmaceutical
St Louis, MO
Opinions expressed are not necessarily those of my employer
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Tyler, Matt
Sent: Thursday, January 15, 2009 2:40 PM
To: Websphere Development Studio Client for iSeries
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
P.S. I am using WDSC 7.0.0.
-----Original Message-----
From: Austin, Mark [mailto:Mark.Austin@xxxxxxxxxx]
Sent: Thursday, January 15, 2009 7:25 AM
To: Websphere Development Studio Client for iSeries
Subject: [WDSCI-L] Large variables in debug
Hi everyone,
I'm trying to debug a SQL ILE Cobol program in RDi 7.1 to find out the
SQL statement that is being executed in the program. The statement is
strung together at runtime and then executed. The variables view only
seems to show the first 1024 bytes of the variable. My SQL statement is
larger than this & I want to see it all. How can I do this?
I have tried using the monitors view but can't seem to get it to show
more than 1024 bytes or show an offset.
I have also tried to monitor the memory but I can't cut and paste the
whole contents (I want to run the generated SQL in Quantum so I can
tweek it).
Any help would be much appreciated.
Best regards,
Mark Austin
IT Consultant
Universal Music Publishing International
Email: mark.austin@xxxxxxxxxx
Tel: +44 (0) 20 8742 5520
Fax: +44 (0) 20 8742 5699
Universal Music Publishing International Limited
Registered in England. Number 02050403
Registered Office: 347-353 Chiswick High Road, London W4 4HS
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of MichaelQuigley@xxxxxxxxxx
Sent: 14 January 2009 20:48
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] COPY LINES FROM ONE RPG SOURCE TO ANOTHER
I agree--if you want LPEX to work like SEU, you'll never be happy. It
is
a different editor and it works different (and in my opinion better).
But
e-mail is also different than a stone tablet and a chisel. I only use
SEU
when I'm forced to because I'm not at a PC or I'm at one without
WDSc/RDi
installed. The copying method described below has worked for me
starting
from at least version 5. I may have even tried it in version 4. (Yes I
was crazy enough to try using it there, but I ended up just going with
the
CODE editor at that point. I think the same basic process worked in
CODE,
but the keys were probably different.)
wdsci-l-bounces@xxxxxxxxxxxx wrote on 01/14/2009 10:06:18 AM:
----- Message from "Jim Essinger" <dilbernator@xxxxxxxxx> on Wed, 14
Jan 2009 07:37:43 -0700 -----
To:
"Websphere Development Studio Client for iSeries"
<wdsci-l@xxxxxxxxxxxx>
Subject:
Re: [WDSCI-L] COPY LINES FROM ONE RPG SOURCE TO ANOTHER
Mary,
I've got to go with David here. Get away from those line commands if
you can re-train yourself just a little. It slows me down to get over
to the numbers and key line commands, and as others have said, this
only works within the same member.
I open the two members I want to edit. As an added bonus, If your
display is wide enough to show both members at the same time, drag the
tab heading to the right edge of the LPEX editor. When the outline of
the member shows, you drop, and you now can look at both members.
Now I go to the member I want to copy from and use alt+L to select the
first line, alt-down arrow to select all the lines I want, and
alt-left arrow (or right arrow) to change to the other member being
edited. Then I position my cursor to where I want the copied lines to
go and use alt-C to copy the lines.
All this without taking my hands off the keyboard, after getting both
members loaded in the editor. I usually open the source member in
browse so I don't accidentally alter it.
Once highlighted you can use alt-D to delete, and alt-M to move as
well. Works between and within members in the LPEX editor.
I am on V7 version of some sort. I have been using this at least
since
V6.
HTH
Jim
--
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.
--
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.
--
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.
midrange.com
