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.

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