Adding FAQs and other List files that you, your subscribers or anyone can retrieve using the GET FILENAME command is easy and basically a Three step process: (1) GET your List's Catalog; (2) Enter a sub-catalog entry for the file and PUT your list's catalog then (3) PUT the file itself.

The following Step by Step instructions are for Non-VM servers. If you are not sure what version your LISTSERV host is using send the following command to the LISTSERV command address:
SHOW VERSION

1. First, find out if you have a list catalog by sending the following command to the Listserv command address: GET LIST_NAME CATALOG
   If you don't have a list catalog, contact your Listserv Postmaster and request that s/he install one for you. If you do have a list catalog: you'll get an email that looks similar to the following:
   

   Date sent: Fri, 25 Sep 1998 13:03:03 -0400 From: "L-Soft list server @ Listserv Place (1.8c)" <LISTSERV@LISTSERV DOMAIN> Subject: File: "LISTNAME CATALOG" To: Me <my1@address.COM>   OLD.FILE OLD.FILE PRIVATE(ListName) OWNER(ListName)

2. Now You have to add the file name(s) of the file(s) you want placed on the listserv to the catalog by sending an email to the Listserv command address that looks something like the following:
   You will be overwriting this file so make SURE you include any information you want from the ListName catalog file you received from your GET LISTNAME CATALOG command in your PUT LISTNAME CATALOG PW=XXXX email to the listserv command address.
   

   Date sent: Fri, 25 Sep 1998 13:03:03 -0400 From: Me <my1@address.COM> Subject: anything here To: LISTSERV@LISTSERV DOMAIN; CC: Not a bad idea to send a copy to yourself PUT ListName.CATALOG PW=xxxxxx OLD.FILE OLD.FILE PRIVATE(ListName) OWNER(ListName) File Already on LISTSERV Host * New file for ListName comment line NEW.FILE NEW.FILE PRIVATE(ListName) OWNER(ListName) New File You are going to Place

   Warning: If your list has an alias, then you might have problems using the list's name in the filename [NEW part of NEW.FILE]. For example, say ALIAS-NAME is an alias for the OLD-NAME list you may need to enter your file into the catalog similarly to:

   • A-N.FAQ A-N.FAQ PRIVATE(LISTNAME) OWNER(LISTNAME)
     or
   • OLD-NAME.FAQ ALIAS-NAME.FAQ PRIVATE(LISTNAME) OWNER(LISTNAME)
     or like so:
     
   • OLD-NAME.FAQ OLD-NAME.FAQ PRIVATE(LISTNAME) OWNER(LISTNAME)
   [ PUTting the actual file as named either A-N.FAQ or OLD-NAME.FAQ ]

   HERE IS THE RUN DOWN ON WHAT IS REQUIRED and OPTIONAL:

   (1) *New file for ListName
   NEW.FILE	NEW.FILE	PRIVATE(ListName)	OWNER(ListName)
   (2)	(3)	(4)	(5)

   (1) = optional. You can add lines of descriptions of your files by putting a * at the start of each line

   (2) = required. This defines the name of the file as seen by LISTSERV users. That is, the command to retrieve the file will be GET NEW.FILE.

   (3) = required. This defines the name of the actual disk file where the contents of LISTNAME.NEW will be stored. Normally, you should specify the same as (2), or just an equal sign (LISTSERV will then substitute the name you provided for (2)). However, in some cases you may want to make a particular file available under multiple names. This can be done by registering multiple files (ie multiple values for (2)), and using the same (3) value every time.

   (4) = required. This file access code determines who can order the file through a GET command. The following file access codes are available:

   • ALL universal access.
   • PRIVATE(ListName) only members of the list have access.
   • OWNER(ListName) only the owners of the list have access.
   • SERVICE(ListName) only users in the service area of the list have access.
   • NOTEBOOK(ListName) same access as the archives of the list.
   • user@host the user in question is granted access.
   Except for ALL, which must occur on its own, multiple file access code entries can be specified, separated by a comma with no intervening space. For instance:
   MY.FILE C:\FILES\XYZ\MY.FILE JOE@XYZ.EDU,JACK@XYZ.EDU,PRIVATE(XYZ-L)
   defines a file that Joe, Jack and the subscribers of the XYZ-L list can order via the GET command, but that only the LISTSERV administrator can update.

   (5) = required. This file access code determines who can update the file with the PUT command. Uses the same information as #4.

   Of Note: You can simply add a file's name without the other stuff and listserv's defaults will go into affect. So ListName.FAQ On a line by itself will allow for a file named ListName.FAQ to be put with that actual name, GETable by ALL and PUTable by the list's owner(s) by default.

3. Once you've PUT your new sub-catalog entry and received the confirmation message back, you can PUT your new file(s). For each new file, send an email to the LISTSERV command address that looks similar to the following:
   

   Date sent: Fri, 25 Sep 1998 13:03:03 -0400 From: Me <my1@address.COM> Subject: anything here To: LISTSERV@LISTSERV DOMAIN; CC: Not a bad idea to send a copy to yourself PUT NEW.FILE pw=xxxxxx This is the ListName FAQ file where you will find the purpose of the list, it's rules and suggestions to make your stay as a subscriber a happy and fulfilling one. Yada Yada Yada Yada Yada Yada Yada Yada Yada Yada Yada Yada Yada Yada Yada Yada Yada Yada Yada Yada Yada Yada Yada Yada Yada Yada Yada Yada Yada Yada Yada Yada Yada Yada Yada Yada Yada Yada Yada Yada Yada Yada Yada Yada Yada Yada Yada Yada Yada Yada Yada Yada

   Once you've received confirmation from Listserv that the file has been successfully PUT, it can be retrieved by sending the GET NEW.FILE command to the listserv command address.

You can delete a list's file from the listserv by simply sending the following to the listserv command address: PUT NEW.FILE pw=xxxxxx

Don't enter any lines or even hit the RETURN or ENTER key after the PUT line. You should get confirmation back that the file has been deleted.