Re: verify -- WDSCI-L

I was going to suggest the same thing.  Could be a cached /COPY with a 
different procedure definition.

I would also add just to triple-check that you have properly defined the 
library list for your RSE connection so that the verifier can find all of 
the right pieces.

Have you tried compiling from WDSC?  That would use the same *LIBL as the 
verify, but would not use the cache.  It might help isolate where the 
problem was.  If compile fails, it is a *LIBL problem, if it works, then 
is likely a cache problem.

Mark



wdsci-l-bounces@xxxxxxxxxxxx wrote on 08/05/2004 01:22:36 PM:

> You might want to try verifying with a prompt (Source menu then verify
> with prompt) select the cache and click on refresh check box. then click
> ok. 
> 
> Refreshing the cache brings in the file definitions for the verify.
> 
> HTH
> 
> Dave Boettcher
> 
> >>> TKredlo@xxxxxxxxxxxxxxxx 08/05/2004 11:44:52 AM >>>
> I just started using WDSCI (Version: 5.1 Build id: 20030908_2154)
> regularly
> a couple of weeks ago and was having a problem getting a new source to
> successfully be verified.
> I was getting a lot of 'undefined' field errors, for fields that were
> defined as far as I could tell.
> I switched back and worked in PDM until I could get the program
> compiled
> successfully.
> Once that was done, I decided to finish the program modifications in
> WDSCI.
> 
> Started WDSCI.
> Brought up the program in the editor and 'verified'.
> Got a bunch of 'undefined' error messages again.
> Closed the source and went back to PDM.
> Compiled the program again to make sure it was OK.
> Program compiled fine. 
> 
> Closed and opened WDSCI.
> Not knowing what could be wrong, I manually refreshed the sources for
> the
> program, included /Copy members, DDS for program screens, and DDS for
> referenced files.
> Looked at the source to see that they were current -Yep.
> Cleared the error message list.
> Verified again.
> Got the similar ( maybe identical) list of errors back.
> 
> Example:
> >From /Copy prototype member:
>      D CIpB00          Pr                  ExtPgm('CIPB00')
>      D  CaldBy                        8A 
> Program inferface in program:
>      D CIpB00          Pi
>      D  CaldBy                        8A
> RNF3764: Definition of parameter (A(8)) not same as definition of
> parameter
> in prototype (A(15))
> 
> I did a search through all the RPG and DDS sources on our system and
> these
> were the only 2 places this field was found. 
> 
> Example 2:
>      D PrvInput02      S              1    Dim(%Len(Input02))
> RNF7451: Built-in function %LEN(INPUT02) is not defined; built-in
> function
> is ignored.
> RNF7030: The name or indicator PRVINPUT02 is not defined. 
> 
> This compiles fine using PDM.
> 
> I thought originally that the 'undefined' errors were limited to
> 'qualified'
> names, but that was not the case, although many of the errors do
> pertain to
> qualified field names.
> 
> I really want to make WDSCI my primary development tool, but I need to
> get
> it to work for me first.
> What could I be doing wrong here?
> 
> TIA for any help or suggestions.
> 
> Tim Kredlo
> Exterior Wood, Inc. 
> 
> 
> 
> 
> _______________________________________________
> 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.
> 
> 
> _______________________________________________
> 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.
> 
> 
_____________________________________________________________________________
> Scanned for SoftLanding Systems, Inc. by IBM Email Security Management 
> Services powered by MessageLabs. 
> 
_____________________________________________________________________________


_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services 
powered by MessageLabs. 
_____________________________________________________________________________