I use verify, esp on SQL programs. When a SQL program is compiled and
there is an error in the program, if you click on the error from the
generated iseries error list, WDSC shows the error in a separate source
member, not the member you are working on. I recently upgraded to V7,
but in V6 this new source member was editable. Many times I started
making changes to the source member showing the errors, very annoying
when I discovered what I was doing. Now in V7, the source member does
not allow changes, just shows the errors.
With verify, you can click on an error in the list and go straight to
the line in your source member.
Roger Rettig
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Bryce Martin
Sent: Wednesday, January 13, 2010 4:19 PM
To: Rational Developer for IBM i / Websphere Development Studio Client
forSystem i & iSeries
Cc: wdsci-l@xxxxxxxxxxxx; wdsci-l-bounces@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] WDSC can't see files anymore in Verify
Don't worry Buck, I never use the verify command either. I really don't
see the point since I can just compile. Then if it compiles ok I can
run
it if I would like to test it.... Maybe someone can enlighten me on why
you use verify over compiling... other than the fact that you don't have
to be connected to the remote system, which I always am.
Thanks
Bryce Martin
Programmer/Analyst I
570-546-4777
Buck <kc2hiz@xxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
01/13/2010 04:04 PM
Please respond to
Rational Developer for IBM i / Websphere Development Studio Client for
System i & iSeries <wdsci-l@xxxxxxxxxxxx>
To
wdsci-l@xxxxxxxxxxxx
cc
Subject
Re: [WDSCI-L] WDSC can't see files anymore in Verify
Kenneth wrote:
I use the Verify feature often to validate my code and use other
features related to it.
Suddenly sometime this morning, the Verify feature couldn't find the
files to validate against. As such, I have a number of severity 40
messages ("External descriptions for file...not found; file is
ignored.")
The library they are in has the files, and the library has been added
to
the library list in WDSC (it is automatically done upon startup, and I
verified under the iSeries Command Log that it was successful).
Any clue as to why WDSC suddenly (without any changes I am aware of)
can
no longer see the files even with the library they're in within the
library list?
I read your response about the cache box being checked, but still,
consider clearing both caches and trying again. Either the FAQ
(faq.midrange.com) or the Wiki (wiki.midrange.com) have instructions to
do that, and if you can't find them, let me know what search terms you
used and I'll update the Wiki so that it's findable.
I haven't bothered with verify since I discovered it is slower to do the
local verify than to to the remote compile. It's a perversion, I know.
Maybe I'm paying myself back for the years I spent 'compiling and
debugging on the desk' before actually punching up my source decks...
--buck
midrange.com
