|
Violaine, Thanks, that corrected the issue. It would seem that the refresh button on the outline view should fetch a new copy of the file definitions, but i guess not. Steve Steven Morrison Fidelity Express 903-885-1283 ext. 479 Violaine Batthish <batthish@xxxxxxxxxx> Sent by: wdsci-l-bounces@xxxxxxxxxxxx 09/20/2006 07:19 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] WDSC problem - Outline view - For IBM developers Hi Steven, The outline view for ILE RPG is driven by the RPG verifier. The default setting for the verifier is to use cached information, and this is most likely the reason you are not seeing your new field. The simplest way to accomplish your goal would be to Verify with prompt from the Source menu and select the Refresh cache option. Then refresh your outline view. The new field should then appear. We already have a requirement to select refresh the cache from the outline view. thanks, Violaine Batthish WebSphere Development Studio Client, IBM Toronto Lab wdsci-l-bounces@xxxxxxxxxxxx wrote on 09/19/2006 05:34:38 PM:
I've been working with a project to add a new field to a file. This file exists in two different versions in my library list, but the new version appears first in the library list. When I compile the program from
within
WDSC, it compiles correctly, and displays the added field in the
compiler
listing. However, the outline view does not show this field. I have refreshed the outline view several times, and have ended and restarted WDSC. I do run a startup job from Users Commands in WDSC to set the library list that WDSC sees. Any help with this is appreciated. Thanks, Steve Steven Morrison Fidelity Express 903-885-1283 ext. 479
As an Amazon Associate we earn from qualifying purchases.
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.