Re: Speed of Verifier/Outline view refresh

[MichaelQuigley@xxxxxxxxxx]

Nnnnnnooooooo  JJJJJJJJooooooooonnnnnnn, IIII''''vvvee aaallllllssssooo 
ssseeeeennn hhhhoooowwww ssssssllllllllllloooooowwwwwwww verifies are.  I 
never use the function anymore.  A compile is *MUCH* faster.  CODE would 
have been a much easier sell to other developers.  The verify in CODE was 
lightning-fast, but it's a joke in WDSC.  I've tried it on medium sized 
programs (COBOL and RPG) -- with refresh cache on, it took something like 
5 or 6 minutes; with refresh cache off, I saved an amazing 30 or 40 
seconds.  (And yes if anyone can't tell, that last remark is intended to 
be sarcastic.)

Michael Quigley
AS/400 Programming Coordinator
The Way International
www.TheWay.org

Original message:

------------------------------
date: Tue, 14 Mar 2006 14:15:11 -0500
from: "Jon Paris" <Jon.Paris@xxxxxxxxxxxxxx>
subject: Re: [WDSCI-L] Speed of Verifier/Outline view refresh

 >> The outline view for RPG does a verify in order to populate itself. 

I've been meaning to ask this for a while now and V's reply reminded me.

Am I the only one to notice how much slooooowwwwweeeeeerrrrr the WDSC 
verify
is compared with CODE?  When I request verify in CODE it completes almost
instantly.  In WDSC even with everything cached there is a very 
perceptible
pause.  Many of my clients have just given up on verify and simply submit
compiles.

Jon Paris
Partner400

www.Partner400.com
www.RPGWorld.com