For the  reasons that Hank  mentioned, there is  a relatively large  number of
inter-LISTSERV command  jobs that  got corrupted.  Although there  aren't more
than 10 on today's  console log, all came in via DIST2,  ie through FRMOP11. I
saw a  small number  (2-3) of jobs  coming directly from  other places  in the
network which do not seem to be affected.
 
Thanks to  the checksum system, the  LISTS database is not  being updated with
this corrupted  data; however,  each server  that gets such  a garbled  job is
immediately going to request a re-ship from the originating server, so that we
may expect a dramatic increase in  inter-LISTSERV traffic until the problem is
solved. However,  that should  allow us  to find out  whether this  problem is
really due to FRMOP11 or not, since the re-ships will be sent directly and not
via DIST2.
 
Netwide  SIGNOFF and  DELETE commands  are,  however, completely  lost in  the
process. Please  stop submitting  those until  the problem  is fixed,  as they
usually cause a syntax error, resulting in an error message being sent back to
the originator  by EACH AND EVERY  LISTSERV receiving the corrupted  data. The
jobs will have to be resent after the problem is fixed.
 
  Eric