The first  problem I  noticed after  the installation  of 1.5n  is that,  as I
expected it, postmasters have NOT  changed their local lists to "Confidential=
Service Service=  Local". The  result is that  I now have  335 entries  in the
LISTS database  for a  mere 23 servers  that have sent  in their  X-LUPD jobs.
There is  a significant amount of  local bridge clubs, local  VM systems group
blah subcommittee, and so on. This is  definitely not going to help users find
their way out in the database, and this  is not going to help the network yes.
So, could you please try to change  all your local lists, test lists included,
to  either  "Confidential=  Yes"  or  "Confidential=  Service"  and  "Service=
something". Thanks.
 
After playing with the  LISTS database for a while, I noticed  a stupid bug in
LSVDBLS  EXEC, which  you  might  wish to  correct  using  XEDIT. After  label
"Rebuild:", there  is an  'EXECIO 1 DISKR  LISTS DBNAMES...'  instruction. For
some reason  the record  number ('recno')  has been  omitted. The  line should
read:
 
    'EXECIO 1 DISKR LISTS DBNAMES' filedisk recno '(VAR LINE'
 
This bug  may cause  improper formatting  of the index  entries, and  hence an
error 100 from LSVDBS while trying to search the affected entries. A 'DATABASE
REBUILD LISTS' will properly rebuild the index.
 
Then I noticed another bug, in LSVDBS this time. Actually it's not a bug but a
limitation:  database keyword  values were  not allowed  to exceed  256 bytes,
which I  found to be  a reasonable value  since you cannot  conveniently print
more than 80 lines on a terminal. Well, the COCO list has an "Editor=" keyword
longer than 256 bytes, and this caused some searches to fail where they should
not have. I also  got a loop once, but I don't remember  whether this was with
the standard version or the first fix  I had attempted; in any case, the final
version (temporarily available from LCOORD  FILELIST as LSVDBS MODULE) is free
from this loop. I've also added an entry for LSVDBLS EXEC, although the fix is
really easy to put in.
 
I will  wait for a  few days before distributing  a fix shipment.  Please note
that if you got an error 100  from CARD LOAD during the shipment installation,
it probably  means LISTSERV's A-disk  is full and part  of the new  files have
been loaded. In that  case you should expect your server  to malfunction as it
is working with half of 1.5m and half of 1.5n. That's one of the reasons why I
recommend setting an INSTPW ^= ''.
 
  Eric