How shall we track down sources of corruption? I had one job kicked out here this morning. It had several capital letters in the middle of words, and when I changed them back to lower case and resubmitted the job it was accepted. Has anyone else seen a reject with any of the same VIA nodes? Here is the failing job. --- File: BANYAN-L BAD-DIST --------------------------------------------------- //BANYAN-L JOB Echo=No,Reply-to="D1SLR@AKRONVM" //To DD * CHANB QUCDN bob chan JOSLIN QUCDN Bill Joslin /* // DIST2 MAIL FROM=BANYAN-L@AKRONVM I=Y FORW(CRC VIA) HOST(79 79) //CRC DD * 1-E1845D2D /* //Via DD "AKRONVM OHSTVMA PSUVM" //Data DD *,EOF,Res=Disk Date: Tue, 9 Jul 1991 08:11:39 EDT Reply-To: Banyan Networks Discussion List <[log in to unmask]> Sender: Banyan Networks Discussion List <[log in to unmask]> From: Brian Sullivan <[log in to unmask]> Subject: Re: EISA ethernet Card X-To: [log in to unmask] To: Multiple recipients of list BANYAN-L <BANYAN-L@AKRONVM> In-Reply-To: <[log in to unmask]> I'm not sure about the performance of the 32 bit cards, but it should improve the performance on the server. But the real bottleneck in a server should be getTing the information from the disk to memory and not from main memory to ethernet board. I would take a look at the cashE hit rate (Netman/IO/File stats), if it was below 90% and you Haven't already got the max mem in the sErver I would increaSe the memory. A note on putting 32bit boards in client PC's. I don't know if this applies and it's just a theory some of us have batted around ... If the network is busy, and you go to 32 bit cards, you allow user applications to put an increased load on the network. Traffic to the point where collisions increase, at which point the whole thing snowballs. And response time drops exponentially??? Just a theory ... -------------------------------------------------------------------------------