Jeff and Steve,
 
    Yes, to make files available from  LISTSERV, you have to list them
in a filelist.   The good news is that LISTSERV  itself generates most
of the information you see in the filelist entry.  The best idea is to
start with  a copy of  another FILELIST (like LISTSERV  FILELIST), and
edit the  heck out  of it.   Since the  PUT command  can't be  used on
FILELISTs yet, you'll have to sign  on to LISTSERV.  You don't have to
STOP it, all of this can be done while LISTSERV is running.
 
    XEDIT the FILELIST  you want this new FILELIST to  be contained in
(it's a tree structure).  Typically, this means LISTSERV FILELIST, the
root of the tree.  Add an entry that looks like:
 
0    0        1          2   3   3      4     4  5        5        6
1    6        5          6   0   4      1     7  0        9        8
V    V        V          V   V   V      V     V  V        V        V
/F/  <myname> FILELIST   ALL CTL .      .     0  ........ ........ Description
 
    The "/F/" tells LISTSERV that this entry describes a FILELIST (no,
that's not implied  by the FILELIST filetype).  Don't put  this on the
start of  an entry  that describes  a regular file  (just delete  it -
don't  leave  the  columns blank.   FILELISTs  are  position-oriented,
exactly as you see above).  The ALL is the "GET" File Access Code, and
the CTL is the "PUT" FAC.  The two dots are RECFM and LRECL, and the 0
is  the number  of  records (0  means the  file  isn't available  from
LISTSERV yet).   The two strings of  dots are the file  date and time.
The description is whatever you want  to say about this FILELIST.  The
"CTL" FAC means that this file  can only be stored by the Postmasters,
and the "ALL" means  that anyone can get a copy of  it.  Now store the
FILELIST,  and use  the LISTSERV  REFRESH  command to  get the  proper
RECFM,  LRECL, NRECS,  date  and  time into  the  entry.  Simply  type
"REFRESH LISTSERV" to do so.
 
    Use the  XEDIT command to  edit a sample FILELIST,  like LISTSERV.
Change   the  descriptive   information  at   the  top   to  something
meaningfull,  and  delete all  of  the  entries  (but not  the  column
headings).   Add any  entries you  want  to it,  and then  FILE it  as
<myname> FILELIST.
 
    To store  one of these files  you've just set up  entries for, use
LSVPUT:
 
LSVPUT <filename> <filetype> <filelist>
 
    LISTSERV will  automatically update  the <filelist>  FILELIST file
with the proper information, and then  refresh each FILELIST on up the
list until it gets to LISTSERV FILELIST.
 
Ross Patterson
Rutgers University
Does this help?