Re: WDSC Debugging the LDA -- WDSCI-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: WDSC Debugging the LDA
From: David Gibbs <david@xxxxxxxxxxxx>
Date: Thu, 16 Oct 2008 11:44:31 -0500
List-archive: <http://archive.midrange.com/wdsci-l>
List-help: <mailto:wdsci-l-request@midrange.com?subject=help>
List-id: Websphere Development Studio Client for iSeries <wdsci-l.midrange.com>
List-post: <mailto:wdsci-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/wdsci-l>, <mailto:wdsci-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/wdsci-l>, <mailto:wdsci-l-request@midrange.com?subject=unsubscribe>
Openpgp: id=D1980033; url=http://pgp.mit.edu:11371/

Fred Horvat wrote:

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

Well, if the LDA is defined to the program, then it's just a field (AFAIK). It should be debuggable as any other field.

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.

I'm not near a system at the moment ... but if you do a DSPPGM I think it will tell you what optimization level the program is set at. At the higher levels some variables may not contain the right information.

david

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