"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