>2) Then TELL LISTSERV AT UBVM SF COAUNX-L FILEID
 
You don't need to do that unless you want to impose a particular fileid to
the file, which won't be necessary unless the file is on a public disk that
people LINK to. That also requires full postmaster privs and the storepw.
 
>3) After your RECEIVE them, you XEDIT COAUNX-L FILEID to add the line(s)
>   filename filetype E filename filetype E, where filename and filetype
>   are the real names of the file(s) you want to store in COAUNX-L
>   FILELIST.
 
No, that's 'external_fn external_ft internal_fn internal_ft internal_fm'. The
'E' would be there only once, at the end, if it's the filemode as I assumed it
to be.
 
>   Don't bother putting
>   anything on the rest of the line except under File Description where you
>   might put a short blurb about the file.
 
You ought to put something under the various headings, even though the actual
contents are irrelevant. This is because LISTSERV will often use the REXX
PARSE instruction to extract this data.
 
>6) After you RECEIVE it, you can then LSVPUT COAUNX-l FILEID (CTRL and then
>   LSVPUT COAUNX-L FILELIST.
 
That's PUTC on the first command, and it requires full postmaster privs.
 
>7) When you receive word from LISTSERV that it successfully stored these files,
>   you can LSVPUT filename filetype (PUTC for each of the files you want to
>   store.
 
Well it would work, more or less, but you're supposed to do a regular
PUT, not PUTC.
 
>8) When you receive word that everything went ok, you TELL LISTSERV AT UBVM
>   REFRESH COAUNX-L.
 
Not required if you store the files via PUT.
 
>tell listserv at ubvm get coaunx-l filelist (ctl
>R;
> DMTRGX171I FROM UBVM(LISTSERV): * You are not authorized to GET (CTL format) f
> ile "COAUNX-L FILELIST".
 
 
He's not authorized to PUT the filelist (to GET/CTL, you must be allowed to
PUT the file).
 
  Eric