× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



The other way to display is to use the the Monitor's view to see a very
large buffer.

Right click on the variable, and choose Monitor Memory -> Hex and
Character.
Make sure you click the Toggle split pane button in the Memory view to see
both the Hex and Character value of this variable.

Thanks,

Xuan Chen, Problem Determination Tools for iSeries
(905) 413-3769 T/L 969-3769
xuanchen@xxxxxxxxxx





"albartell" <albartell@xxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
07/16/2007 09:04 AM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
"'Websphere Development Studio Client for iSeries'" <wdsci-l@xxxxxxxxxxxx>
cc

Subject
Re: [WDSCI-L] SEP debugging & monitoring variables > 1024 bytes






In the Monitor view there is a green plus sign that you can click to add a
variable to the Monitor view. Click that and then enter "varname:c 2048"
into the popup window (minus the double quotes). You should now be able
to
see 2048 bytes of that variable.

HTH,
Aaron Bartell
http://mowyourlawn.com


-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On
Behalf Of GKern@xxxxxxxxxxxxxxxx
Sent: Monday, July 16, 2007 7:57 AM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] SEP debugging & monitoring variables > 1024 bytes

Michael:

"I don't know about a monitored variable, but with the EVAL on the command
line you can specify EVAL varname:c 2048 (or some number) to see 2048
bytes
of the variable."

I don't recall 'command line' access in wdsci while debugging RPG. Are you
referring to STRDBG? Or am I missing out on a command line feature in
wdsci?

Adam:

"I believe most of the commands from green screen debug also work in WDSC.


:x to see hex value, for example. It might be worth trying that out ...
I'm pretty sure there are details about where exactly you put the :x or :c


in the 'Monitor variable' dialogue if you look in the WDSC help for the
debugger."

Tried that too, and putting the variable in hex did show 2048, but that
still didn't allow me to view bytes beyond 1024. The help wasn't much
help,
but I will continue and try again.

Regards, Jerry

Gerald Kern - MIS Project Leader
Lotus Notes/Domino Administrator
IBM Certified RPG IV Developer
The Toledo Clinic, Inc.
4235 Secor Road
Toledo, OH 43623-4299
Phone 419-479-5535
gkern@xxxxxxxxxxxxxxxx



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.