I always use Verify. I really miss my RDi trial where the Verify (and Outline) worked much slicker.
My only problem with it is if I'm missing an End* opcode, the error message given is at the very top of the program. Is it different for a compile?
To be honest, I still compile in PDM. For issues like the one above, I can then go into SEU browse mode and search the spool file for *ERR to find where the issue is. I thought I had more reasons, but they're eluding me right now (too much work!).
I really dislike the compile listing WDSCi (7) gets - it's like an image, I can't search it.
That's all I got.
- Kurt Anderson
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Ryberg, James
Sent: Wednesday, January 13, 2010 3:36 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Cc: wdsci-l-bounces@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] WDSC can't see files anymore in Verify
Same here I never use verify anymore.
James L. Ryberg, Sr.
Associated Bank Corp.
Programmer Analyst
Mail Stop : 7055
Work : (920) 405-2522
Fax : (920) 405-2533
Email : James.Ryberg@xxxxxxxxxxxxxxxxxxx
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Bryce Martin
Sent: Wednesday, January 13, 2010 3:19 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System 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
