On Tue, 25 Nov 2008 16:45:12 -0600, Mickey Chandler <[log in to unmask]>
wrote:

>ldd lsv
>        linux-gate.so.1 =>  (0x00110000)
>        libldap-2.3.so.0 => /usr/lib/libldap-2.3.so.0 (0x00505000)
>        libodbc.so.1 => /usr/lib/libodbc.so.1 (0x00b62000)

This shows the link to the UnixODBC libraries.

>I think that there should be a link to one of these:
>
>/usr/lib/libmyodbc3-3.51.12.so
>/usr/lib/libmyodbc3.so
>/usr/lib/libmyodbc3_r-3.51.12.so
>/usr/lib/libmyodbc3_r.so

No.  LISTSERV does not 'talk' directly to  MySQL so there is no need to link to
any myodbc libraries.  LISTSERV 'talks' to UnixODBC which 'talks' to MyODBC,
which in turn 'talks' to MySQL.  I assume you installed and configured UnixODBC
per the instructions in Sect 4.8 of the LISTSERV Advanced Topics Manual:

 http://www.lsoft.com/manuals/15.5/LISTSERV15.5_AdvancedTopicsManual.pdf

Going back to the original error message:

> >>> Error X'01000033' opening DBMS list <<<
>-> Severity: Error
>-> Facility: DBMS interface
>-> Abstract: DBMS driver failed to initialize

when doing any work with LISTSERV and DBMS it helps to get the fullest error
logging possible.  Be sure to add this to go.user as well:

DEBUG_DBMS_FLAGS=1
export DEBUG_DBMS_FLAGS

then stop/restart LISTSERV with './go bg' and additional logging should show in
the log file.