Re: "Verify" test

I have a new workspace, verify is working as it should, although, now I'm 
wondering, as I create more filters and  add more members to my workspace, 
it this when my verifier is going to slow down to a crawl?  I will monitor 
it's performance as I add new members. 

Diane 



Reeve <rfritchman@xxxxxxxxx> 
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
05/23/06 01:40 PM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
"Websphere Development Studio Client for iSeries" <wdsci-l@xxxxxxxxxxxx>
cc

Subject
Re: [WDSCI-L] "Verify" test






Charles, you might be right; now all we have to do is decide if that 
action
is a bug or not.  I don't remember seeing an option to disable host 
checking
but that doesn't mean anything.  Based on the my tests, I assume it's
downloading everything (including /COPY members) and not just doing
comparing (compiled file) level-check ID's.  Regardless, something is not
right.

-reeve

On 5/22/06, Wilt, Charles <CWilt@xxxxxxxxxxxx> wrote:
>
> Reeve,
>
> I've noticed that WDSCi's verify function seems to be much, much quicker
> when verifying offline after the first on-line verify.
>
> It is my belief that as long as you are still connected, verify makes
> multiple trips to the iSeries to confirm that everything it has is up to
> date.
>
> I'd be interested to see the difference an offline test does.
>
> Charles Wilt
> --
> iSeries Systems Administrator / Developer
> Mitsubishi Electric Automotive America
> ph: 513-573-4343
> fax: 513-398-1121
>
>
> > -----Original Message-----
> > From: wdsci-l-bounces+cwilt=meaa.mea.com@xxxxxxxxxxxx
> > [mailto:wdsci-l-bounces+cwilt=meaa.mea.com@xxxxxxxxxxxx] On
> > Behalf Of Reeve
> > Sent: Sunday, May 21, 2006 1:41 PM
> > To: Websphere Development Studio Client for iSeries
> > Subject: [WDSCI-L] "Verify" test
> >
> > I tested the Verify function on a 4,700-line order entry ILE RPG
> > program containing 37 database files and a multi-format
> > display file.  Using
> > a development-only Dell XPS600 with 2 gB main storage, a 3.2
> > gHz processor,
> > and a 10,000 RPM C: drive (where everything's located), the
> > second Verify
> > using the Eclipse/WDSCi interface took 205 seconds and the
> > second Verify
> > using CoDe took 7 seconds.  I confirmed caching was active and did two
> > Verify's to make sure everything was cached.
> >
> > This may be a (serious) bug or it may be the nature of
> > Eclipse.  Many shops
> > have batch production and compiles get backed in in the job
> > queue.  A slow
> > Verify and poor compile throughput could play havoc with productivity,
> > problem fixes, and project schedules.
> >
> > While the CoDe option remains available and is superior to
> > Eclipse in many
> > ways, numerous CoDe problems uncorrected for the at least five years
> > (lockups, problem with MAXDEV(*FILE), cache corruption, flakey
> > communications manager) leave it in the "marginally reliable"
> > category.
> >
> > -reeve
> > --
> > 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.
>