Since  I was  bored  of mispelling  LISTSERV userid@nodes,  I  have written  an
exec to  assist in  sending commands  to LISTSERV. The  thing, inspired  in the
NETSRV and NETS programs written by  Berthold Pasch and available from NETSERV,
works as follows:
 
* LISTS  listserv_cmdline  is  equivalent  to  TELL  LISTSERV  listserv_cmdline
* If you  define an appropiate nickname  for a LISTSERV, say  LUGA for LISTSERV
  at  UGA, and  a synonym  ( LISTS  - LUGA  in the  example), you  can use  the
  synonym  as  the  command name  and  the  listserv  command  will go  to  the
  right  LISTSERV   (i.e.,  LUGA   listserv_cmdline  will  be   the  equivalent
  of TELL LISTSERV AT UGA listserv_cmdline).
 
It's also  possible to  select all  commands to  be sent  via files  instead of
messages, be  it for  all nodes or  only for  selected ones (via  a tag  in the
NAMES file  definition --> useful  for nodes  where link availability  is bad).
 
In  addition, the  command,  when  invoked alone,  will  display  a short  text
with the destination  server, method of sending commands and  a list of general
user LISTSERV commands.
 
Please note  that support  is NOT  included for commands  that must  send files
to LISTSERV  (i.e., PUT  or DISTRIBUTE) --  for the moment,  it could  be added
later.
 
If anybody is interested, you can try a
 
  TELL LISTSERV AT EB0UB011 GET LISTS PACKAGE DISKMAN
 
(DISKMAN is the name of the FILELIST where LISTS is stored. It's *not* a public
FILELIST, but specifying  it will help LISTSERV a lot  in finding the package).
 
Jose Maria
 
P.S.  If you  order  the package,  you  can immediately  define  a synonym  for
LISTSERV AT EB0UB011, I know it's ugly :-)