|
Check your library list in WDSc. They are not necessarily the same as when you are in Green Screen. Ron Power Programmer Information Services City Of St. John's, NL P.O. Box 908 St. John's, NL A1C 5M2 709-576-8132 rpower@xxxxxxxxxx http://www.stjohns.ca/ ___________________________________________________________________________ Success is going from failure to failure without a loss of enthusiasm. - Sir Winston Churchill "Bill Barnes" <bbarnes@xxxxxxxxxxxxx> Sent by: wdsci-l-bounces@xxxxxxxxxxxx 2006/11/15 11:39 AM Please respond to Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx> To <wdsci-l@xxxxxxxxxxxx> cc Subject [WDSCI-L] New fields not showing in outline Anybody got any ideas? In the deepest recesses of my mind, I recall something like this happening with the Code verifier a bunch of releases ago. Try opening your DDS for edit and recompile it. Then re-verify your RPG and see if you don't get a new copy of the DDS (with the new fields) in the cache. 'cause it still sounds like a stale cache to me. I have cleared cache twice. A recompile of the DDS is not an option because the PF has 3 years of history in it. I did a CHGPF on it which should have the same results as a recompile. In fact if memory serves me a CHGPF does a copy clear compile and then copy back and rebuild all access paths. I have this crazy idea that WDSC should work as well as SEU and STRDBG. Maybe I'm wrong. Needless to say this latest problem is frustrating to say the least and is making my life difficult trying to convince others in this shop to switch to WDSc. They see me having to go back to SEU and ask, "why should I go through the aggravation of learning to use this new tool and still have to rely on SEU and STRDBG to do my job?" I don't have an answer for them. Thanks Bill Barnes Sr Analyst/Programmer The Pantry, Inc 919-774-6700 ext 5211
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.