I am testing version 16.5 with the intention to upgrade from 16.0.  I use UODBC support with the QUERY() function; I don't implement the entire RDBMS interface.  With my production system using 16.0, everything works fine.  For example, I use these keywords:

Sub-Lists= Query(BY_ROLE,jim-test-mh,member)

Editor= Query(BY_ROLE,ADVISING-P017-NDEG,EDITOR)

with my new test system using 16.5, things aren't going so well.  The system OS is the same, the UODBC libraries are the same, but I'm having problems with 16.5 that don't happen with 16.0.  Here are some things I observed so far:

1) the first attempt after restarting the listserv daemon to APPROVE a message using a URL hangs in the web interface.  The approval works, but the "wa" program never returns anything to the browser, resulting in an eventual time-out.  After the first failure, subsequent approvals appear to work fine.

2) each successful distribution that uses a QUERY() to retrieve a sub-list is delayed by two minutes and six seconds.

3) only a handful of test distributions work after a restart of the listserv daemon.  After about 4 or 5 successes, they fail, logging this message:

I'd like to enable more debugging, both for the "wa" program and the distribution mechanism.

Jim Liebgott

NU UNIX admin