RE: rpg debug issue

To see the hex values in debug you can simply add :X to the end of the
eval statement.  On the debug line EVAL MYFIELD:X will show the hex
values.  I *think* if you press the Enter key afterh an eval it shows
you the complete variable.... 


Thanks,
Tommy Holden


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Michael Ryan
Sent: Thursday, January 18, 2007 11:28 AM
To: Midrange Systems Technical Discussion
Subject: Re: rpg debug issue

You won't see contents until the record is read for instance. Also,
debug only shows the first 1024 (?) btes of a field by default. Also,
debug doesn't necessarily show hex values, like x'00'.

On 1/18/07, Dave Snyder <Dsnyder@xxxxxxxxxx> wrote:

I am trying to debug an RPG program. While running and debugging the
program I am trying to display certain fields getting read into the
program from an externally defined input primary file. When I do an

EVAL

to display some field values, they are blank or zeroes when I know

they

should have values. Other fields contain correct values. What could
cause this to happen? I am not manipulating the fields in the program

at

all.



Dave




***********************************************
PRIVILEGED AND CONFIDENTIAL:
This communication, including attachments, is for the exclusive use of

the addressee and may contain proprietary, confidential and/or
privileged information. If you are not the intended recipient, any use,
copying, disclosure, dissemination or distribution is strictly
prohibited.  If you are not the intended recipient, please notify the
sender immediately by return e-mail, delete this communication and
destroy all copies.

***********************************************

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.