A user asked me to replace the contents of a file listed in the
   <listname> FILELIST for his list.
 
1) I received the updated file and did an LSVPUT on it.
2) I received a notice from LISTSERV that the file had been stored.
3) Issuing the command INDEX <listname> obtains a filelist identical
   to what it was before the LSVPUT ( date & lincnt for file unchanged )
4) Get FILE NAME retrieves the OLD copy of the file
5) looking at LISTSERV disks, the new version of the file is found on
   LISTSERV's 'A' disk ( 191 ) instead of the disk pointed to by the
   *DEFAULTS* line of the <listname> FILEID file on LISTSERV's A disk
   ( file stored with original name ! )
 
   We used to have only one disk for logs and files (300) but recently
   created a second disk (200).  The list header NOTEBOOK keyword
  points to the 300 disk and the DEFAULTS line in the FILEID entry
  points to the 200 disk.  Can the notebooks and the files for a list
  reside on different disks ?
 
  what else should I check ?
 
  TIA - mike