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



Yes the field is used through out the program. Other fields through out the
program I can see the values just not the ones from the LDA (UDS).


As far as the optimization level how can I check that from the Object? To
compile our ERP programs we have to use Infor's tool "N4" to compile and it
only gives you 3 parameters. Source Member, Source Library, and Object
Library.


-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
Behalf Of David Gibbs
Sent: Wednesday, October 15, 2008 5:39 PM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] WDSC Debugging the LDA

Fred Horvat wrote:
I'm new to WDSC debugging and when trying to debug a RPGLE program I
wanted to see the value of a field in the LDA and WDSC would not allow
it. The field was defined in the D specs with UDS.

Was the field used in the program? What optimization level did you compile
the program at?

david

--
IBM i on Power -- For when you can't afford to be out of business.
--
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-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.