Re: CODE/400

>>  - Completely verify a program (i.e. a full compiler type check, not just
>> syntax) in seconds _before_ wasting time submitting (and waiting for) a batch
>> compile just to find that you mis-spelled a field name!!
>>           We're going to have to compile it on the /400 to test it anyway
>
>How many times? Aren't you tired of the performance bottlenecks? Do you
>have any idea how much you pay in salaries for people waiting for their
>compiles to come off the queue? 

Well, this is one point that wouldn't apply to our shop.  We have the
horsepower to have enough queues for compile jobs where no one has to
wait for a compile to run.  If your compile goes to jobq status, there
is always another queue you can move it to in order to get it to run.
And because we don't develop on the same machine as our production
applications, we are not impacting our end users' response times.
Of course I realize not everyone has a 530 to develop on, but that's
what we have here.  The only other job the second 530 has is to run
the target portion of our mirroring software, which probably takes 10%
of the CPU max, and to be there in the event we lost the primary
system and have to fail over to it.  99.99% of the time, we have 90%
of a 530 system to develop on.  Ergo, no waiting for compiles.  :-)

Terry Herrin
therrin@isaac.net
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---