Title: <*> MIYAZAKI FILESERVER MEMO <*> Subject: helpful hints on how to access the list's file and message archive Updated: Tue, 1 Nov 94 22:05:00 EST Authors: original version: Steven Feldman update & rewrite: Mauricio Tavares update & editing: Michael S. Johnson updated file indices: Steven Feldman Dear People, The "Hayao Miyazaki Discussion Group" list has a fileserver from which anyone--even non-subscribers--can retrieve weekly archives and long files (like scripts). The following is an updated version of the list's FILESERVER MEMO (please discard any and all previous versions, as they are obsolete): This memo is biased towards users of VM/CMS, but instructions are also provided for persons with Internet e-mail, or VAX computer accounts. Here are some common listserv commands relevant to the Miyazaki list that you might want to use: NOTE ------------------------------------------------------------------------ ---- Examples are marked with "EX:". Parts of the examples will contain words in [square brackets] or . The brackets are not part of the command. They are placeholders, put there to let you know where to type in the commands *you* want to use. [Square brackets] tend to highlight parts of commands which are optional. tend to indicate parts of commands which are required, but should be replaced by key words appropriate to your desired result. In addition, e-mail addresses are often printed inside of , just to set them apart from the rest of the sentence. is an example. Examples in this text may also contain words in (parentheses). These are explanatory comments to the reader and are not meant to be part of the commands being described. WARNING --------------------------------------------------------------------- ------- These commands are used by the FILESERVER, not by the Mailing List. DO NOT send them to the mailing list or you may get nasty mail from other subscribers. Please also avoid including any .signature or tagline text in your messages to as the list server will attempt to interpret it as commands it should execute. Typically, this will result in a series of error messages from the list server, and a suggestion that you should send the "help" command for instructions on how to correctly send commands to it. If there are too many such lines, LISTSERV may even block you from sending any further commands, with the assumption that you have made too many mistakes already. If that is the case, send e-mail to and the list owners (Michael or Steve) will do their best to resolve the situation. USAGE ----------------------------------------------------------------------- ----- To use these commands, send e-mail to or (if you are on Bitnet) or or (for those on the Internet). No "Subject:" line is needed or heeded by LISTSERV. In the body of the message, you would have the following: command_1 command_2 . . . command_n where command_1, command_2, ... command_n are the commands you gave to the listserv. EX: (Princess Kushana calling from her internet account) To: listserv@brownvm.bitnet From: kushana@3rd-army.torumekia.gov (this field is included automagically by your system) Subject: Mostly Harmless (the subject is ignored anyway, so...) help subscribe nausicaa kushana@3rd-army.torumekia.gov Princess Kushana thanks ESSENTIAL COMMANDS ---------------------------------------------------------- --------- -------- SUBSCRIBE o New subscription (send a subscription request to the list administrator) subscribe nausicaa EX: subscribe nausicaa kushana@3rd-army.torumekia.gov Princess Kushana o Change the way your name appears in the subscriber list and on received mailings (if you are already a susbcriber). Beware that if you change your e-mail address, you will have to unsubscribe first and then subscribe again. subscribe nausicaa EX: subscribe nausicaa Kushana UNSUBSCRIBE signoff nausicaa TEMPORARILY HALT E-MAIL DELIVERY (without unsubscribing) set nausicaa nomail o The above command is useful to those subscribers leaving their e-mail accounts unattended for long periods of time (typically: students on vacation or staff on leave). This command will prevent LISTSERV from flooding your account with unread messages while you are away. Please read on for instructions on how to resume e-mail delivery when you return. RESUME E-MAIL DELIVERY (without subscribing from scratch) set nausicaa mail o The above command is useful for those subscribers who have been away and are now ready to continue receiving messages from the mailing list. Please note, however, that none of the messages that were sent while you were away will be delivered to you. You will only receive messages sent *after* this command was sent to the list server. To receive copies of messages that you have missed, please follow the instructions provided below in the section "GETTING ARCHIVES OF PAST MESSAGES POSTED TO THE LIST". OTHER COMMANDS -------------------------------------------------------------- ----- -------- HELP [COMMAND] With no argument - gives a quick brief of all listserv commands. With COMMAND as argument - sends a help file on how to use COMMAND EX: help get (this will send you a help file on how to use "get" on listserv) GETTING FILES get nausicaa (this will send you a file from "nausicaa filelist," i.e. a weekly archive or a long file. Examples would be "get SHUNABY PARAGRAF nausicaa" and "get CASTLCAG SCRIPT nausicaa".) GETTING A LIST OF AVAILABLE NAUSICAA-RELATED FILES index nausicaa or get nausicaa filelist Below is what the Nausicaa Filelist looks like: * NAUSICAA FILELIST for LISTSERV@BROWNVM. * * LISTSERV files associated with the NAUSICAA list. * * ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: * * The GET/PUT authorization codes shown with each file entry describe * who is authorized to GET or PUT the file: * * ALL = Everybody * OWN = List owners * * ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: * rec last - change * filename filetype GET PUT -fm lrecl nrecs date time File description * -------- -------- --- --- --- ----- ----- -------- -------- ---------------- MIYAZAKI FILMLIST ALL OWN V 77 718 93/09/10 18:44:32 Miyazaki & Taka MIYAZAKI BOOKLIST ALL OWN V 78 712 93/09/29 14:18:24 Miyazaki Biblio MIYAZAKI NTRVIEWS ALL OWN V 73 994 93/05/15 18:08:15 Miyazaki interv MIYAZAKI ARTICLES ALL OWN V 76 2148 93/06/23 20:25:56 Various article TAKAHATA ARTICLES ALL OWN V 80 1349 93/09/29 17:06:10 Various article FBCONAN SYNOPSES ALL OWN V 73 835 93/05/15 18:11:53 Future Boy Cona LUPINTV SCRIPTS ALL OWN V 73 1581 93/05/15 18:12:54 Lupin III: "Alb CASTLCAG SCRIPT ALL OWN V 80 3232 93/05/15 18:14:32 Lupin III: Cast SHUNABY PARAGRAF ALL OWN V 73 926 93/05/15 18:15:55 Shuna script (p SHUNABY PANEL ALL OWN V 73 865 93/05/15 18:16:36 Shuna script (p NAUSICAA OLDSCRPT ALL OWN V 69 1345 93/05/15 18:17:38 Nausicaa script NAUSICAA NEWSCRPT ALL OWN V 79 1567 93/05/15 18:18:44 Nausicaa script LAPUTA SCRIPT ALL OWN V 77 3514 93/05/15 18:37:35 Laputa script TOTORO SCRIPT ALL OWN V 80 1119 93/05/15 18:38:50 Totoro script KIKI SCRIPT ALL OWN V 73 2177 93/05/15 18:39:49 Kiki's Delivery PORCO SYNOPSIS ALL OWN V 73 487 93/05/15 18:41:28 Porco Rosso syn PORCO SCRIPT ALL OWN V 78 2715 93/09/12 16:59:58 Porco Rosso scr FIREFLY SCRIPT ALL OWN V 78 2099 93/05/15 18:43:12 Grave of the Fi OPP SYNOPSIS ALL OWN V 75 687 93/05/15 18:44:07 Omo(h)ide Poro OPP SCRIPT-A ALL OWN V 72 2386 93/05/15 18:44:56 Omo(h)ide Poro OPP SCRIPT-B ALL OWN V 72 2309 93/05/15 18:45:35 Omo(h)ide Poro ONNEAMIS SYNOPSIS ALL OWN V 73 597 93/05/15 18:46:33 Wings of (H)onn ONNEAMIS SCRIPT ALL OWN V 80 3852 93/05/15 18:47:28 Wings of (H)onn GETTING THE LIST OF SUBSCRIBERS review nausicaa (this will send you a file containing the following three things: 1. a copy of the list description -- including the list's parameters 2. the names and e-mail addresses of the current listowners 3. an itemization of all current non-concealed list subscribers) get listserv refcard (this will send you a REFerence CARD for listserv commands) set nausicaa repro (the nausicaa list ordinarily does not send a copy of your message back to you. This command will make it so that you *do* get a copy.) set nausicaa norepro (this nullifies the comman above, i.e. "set nausicaa repro.") set nausicaa DUALhdr (generates complete mail headers for people with flukey mail programs like Microsoft Mail that don't otherwise reveal a received message's true address. Fro more info, request a copy of LISTSERV REFCARD from listserv.) GETTING ARCHIVES OF PAST MESSAGES POSTED TO THE LIST The following list of archived message logs are a continuation of the list of files retrieved with the index nausicaa or get nausicaa filelist commands described above. If you are a recent subscriber, or have recently returned to the list (after using the SET NAUSICAA NOMAIL and SET NAUSICAA MAIL commands) after being away, you may want to use the above command to get lists of available message archives, then use the GET commands described below to receive copies of the "back-issues" that you can use to catch up on what you missed. Below is an example of what the Nausicaa Filelist of message logs looks like: * * NOTEBOOK archives for the list * (Weekly notebook) * rec last - change * filename filetype GET PUT -fm lrecl nrecs date time Remarks * -------- -------- --- --- --- ----- ----- -------- -------- --------------- NAUSICAA LOG9210A ALL OWN V 80 462 92/10/07 23:07:33 Started on Thu, NAUSICAA LOG9210B ALL OWN V 80 1365 92/10/15 00:13:56 Started on Thu, NAUSICAA LOG9210C ALL OWN V 80 1092 92/10/21 21:54:18 Started on Thu, NAUSICAA LOG9210D ALL OWN V 80 2571 92/10/28 23:39:48 Started on Thu, NAUSICAA LOG9210E ALL OWN V 80 1004 92/10/31 17:19:55 Started on Thu, NAUSICAA LOG9211A ALL OWN V 80 2985 92/11/07 18:50:04 Started on Sun, NAUSICAA LOG9211B ALL OWN V 80 2332 92/11/13 23:28:21 Started on Sun, NAUSICAA LOG9211C ALL OWN V 80 527 92/11/21 23:20:02 Started on Sun, NAUSICAA LOG9211D ALL OWN V 80 320 92/11/28 08:44:30 Started on Mon, NAUSICAA LOG9211E ALL OWN V 80 392 92/11/30 21:50:49 Started on Sun, SPECIAL NOTE TO THOSE WITH VM/CMS XEDIT (eg. people on IBM mainframes): Notice that the information at the right cuts off. This is because XEDIT cuts off anything over 80 columns. To see the rest of each line, "right 30" must be typed on a command line (to return to where you started, "left 30" must be typed). Note that the number "30" is simply the number of columns to shift the text. You could choose another number as appropriate. When you use the "get nausicaa filelist" command *yourself*, you will get a copy of the filelist that will become visible in its *entirety* once you type "right 30" (unlike the truncated copy used in the example above). The archives are broken down into weeks. Their filetype is actually a code: after "LOG," the first two numbers are the year, the second two numbers are the month, and the letter (A, B, C, D, or E) is the week. Week A holds messages posted during the first seven days of the month, B holds the second seven days... and E holds the remainder (29th-31st). The procedure for file retrieval is simple and almost immediate for Bitnet users of VM/CMS, who use syntax like "tell listserv at brownvm get CASTLCAG SCRIPT nausicaa". For Internet VM/CMS users, the procedure is to send e-mail to and make the message read "get CASTLCAG SCRIPT nausicaa". Capitalization is unimportant, but used for emphasis in this example. If you want more than one file at a time, and you're on Bitnet, you have to key in each command separately. (A recall command will speed up the process a little, though.) If you want more than one file at a time, and you're on Internet, you can request multiple files by putting each command on a new line. BITNET EXAMPLE: tell listserv at brownvm get LUPINTV SCRIPTS nausicaa (push "Return") tell listserv at brownvm get SHUNA BYPANEL nausicaa (push "Return") tell listserv at brownvm get NAUSICAA LOG9310A nausicaa (push "Return") INTERNET EXAMPLE: get LUPINTV SCRIPTS nausicaa get SHUNABY PANEL nausicaa get NAUSICAA LOG9310A nausicaa (mail the multiple-command message) For a more advanced example, say you really only want the LAPUTA script, but you're mildly curious what the mailing list is like, so you'd like to see who's subscribed and what the last week's messages have been like. This can be done with three simple commands, as shown below: ADVANCED BITNET EXAMPLE: tell listserv at brownvm get LAPUTA SCRIPT nausicaa (push "Return") tell listserv at brownvm review nausicaa (push "Return") tell listserv at brownvm get NAUSICAA LOG9410D nausicaa (push "Return") ADVANCED INTERNET EXAMPLE: get LAPUTA SCRIPT nausicaa review nausicaa get NAUSICAA LOG9410D nausicaa (mail the multiple-command message) Internet folks can also get the files via FTP by typing "FTP BROWNVM.BROWN.EDU", then "ANONYMOUS", then "A", then "CD LISTSERV.1AC", then "LS", then "GET ". The archives will show up as they really are, but the long files will *not* show up with their true filenames. There will be an eight-digit number, instead. Furthermore, these long files are in a different order than those available through the fileserver. 8( Here is a key by which you can tell which ftp file is which: 00000002.NAUSICAA is actually SHUNABY PARAGRAF 00000003.NAUSICAA is actually MIYAZAKI ARTICLES 00000004.NAUSICAA is actually TOTORO SCRIPT 00000005.NAUSICAA is actually LAPUTA SCRIPT 00000006.NAUSICAA is actually LUPINTV SCRIPTS 00000007.NAUSICAA is actually MIYAZAKI NTRVIEWS 00000008.NAUSICAA is actually MIYAZAKI FILMLIST 00000009.NAUSICAA is actually NAUSICAA NEWSCRPT 00000010.NAUSICAA is actually NAUSICAA OLDSCRPT 00000011.NAUSICAA is actually CASTLCAG SCRIPT 00000012.NAUSICAA is actually KIKI SCRIPT 00000013.NAUSICAA is actually FBCONAN SYNOPSES 00000014.NAUSICAA is actually SHUNABY PANEL 00000015.NAUSICAA is actually PORCO SYNOPSIS 00000016.NAUSICAA is actually OPP SYNOPSIS 00000017.NAUSICAA is actually ONNEAMIS SCRIPT 00000018.NAUSICAA is actually FIREFLY SCRIPT 00000019.NAUSICAA is actually TAKAHATA ARTICLES 00000020.NAUSICAA is actually MIYAZAKI BOOKLIST 00000021.NAUSICAA is actually PORCO SCRIPT 00000022.NAUSICAA is actually OPP SCRIPT-B 00000023.NAUSICAA is actually OPP SCRIPT-A 00000024.NAUSICAA is actually ONNEAMIS SYNOPSIS Well, now you know. If you ever accidentally zap something from your files that you got from the nausicaa list -- and you really wanted to keep it -- you can go in and get a new copy. If you decide you *do* want those LUPIN III TV scripts (episodes #145 and #155) after all, you can get them anytime! If you haven't seen any interesting postings for awhile, you can go in and read some previous ones which might catch your fancy. . . . The filelist can be accessed at your convenience; feel free to use it. 8) -----------------------------cut here----------------------------------- Finally, for those who want *more* information, here is some info right off of a listserv memo: -----------------------------cut here----------------------------------- | Document fileid: "LISTPRES MEMO" (from "Info PResentation") | +---------------------------------------------------------------+ [XEDITED FOR BREVITY'S SAKE] ************************************ * General presentation of LISTSERV * ************************************ LISTSERV is a VM/CMS based Mailing Lists Manager, designed and written by Eric Thomas of the Ecole Centrale de Paris, France. Subscribers can query and change their distribution and acknowledge- ment options; change their names as recorded by LISTSERV; and, of course, leave the list. LISTSERV accepts commands in three forms: As interactive messages; As mail; And as "Command Jobs" in any of several transmission formats. Interactive messages should be sent in the usual manner for your system: CMS: TELL LISTSERV AT (node) (command) TSO: TRANSMIT (node).LISTSERV '(command)' NOPROLOG VAX: SEND LISTSERV@(node) (command) Commands sent by messages will generally cause responses to be sent as messages, except where inappropriate. Commands can be enclosed in mail, where the mail text following the headers is treated as a file of commands. Each line is treated as a separate command, and the remainder of the file is flushed when an error occurs, such as an invalid command or bad syntax. Responses will normally be sent by mail back to the sender's mailbox. Command Jobs can either be a file of one line commands, processed exactly like the mail form, or a more flexible and of course more complex form. This form uses a control language that closely resem- bles MVS JCL, for ease of use by MVS users who are expected to need it most. An entry in a FILELIST specifies the name of the file, its format and size, a brief comment, and the identities of those users who can store and retrieve, or PUT and GET, the file. These identities are recorded as File Access Codes, or FACs. A FAC is a three character abbreviation for an address or list of addresses, and must be unique within a FILELIST. Several special, or hard-coded, FACs have been defined for common cases: OWN, meaning the owner of a list; PRV, meaning Private, for the subscribers of a list; NAD, meaning Node ADministrators; ALL, meaning anyone; and N/A meaning that the process (GET or PUT) is not applicable to the file. Some of you may recognize this description as that of the EARN Network Server, NETSERV. The LISTSERV File Server was designed to resemble NETSERV as much as possible, so the commands and FILELISTs should be quite familiar to NETSERV initiates. Through the GET, AFD, FUI and INDEX commands, any user can obtain files stored by a LISTSERV. The INDEX command will cause a FILELIST to be sent back to the requestor, listing the available files and their access limitations. The GET command is used to request a file from a particular FILELIST. The AFD, or Automatic File Distribution, command requests LISTSERV to send a copy of a certain file each time it is changed. The FUI, or File Update Information, command is similar to AFD, but causes a short mail message to be sent noting that a new copy of the file is available. -----------------------------cut here----------------------------------- I hope that the above proves helpful. -- Steven Feldman -- Michael S. Johnson -----------------------------cut here----------------------------------- Date: November 1, 1994 Subject: Indexes for MIYAZAKI NTRVIEWS, MIYAZAKI ARTICLES, TAKAHATA ARTICLES, OPP SYNOPSIS, and FIREFLY SCRIPT NOTE: "L#" means "Line Number." All files on the fileserver have been indexed so that users can access a desired subject immediately. filename/filetype MIYAZAKI NTRVIEWS Subject: 1.) Interview re animating TOTORO (ANIME-CLUB #19, 6/10/87) L#00277 2.) Miyazaki and SF [interview snippet] (COMIC BOX, 11/82) L#00310 3.) "Why I don't Make Slapstick . . . Now" (COMIC BOX, 10/89) L#00525 4.) "Money Can't Buy Creativity" (PACIFIC FRIEND, January 1991) L#00646 5.) Foreword to THE ART OF KIKI'S [by Hayao Miyazaki] (1989) L#00738 6.) "Imoto He" [graphic Miyazaki poem] (Yohei Honda, 10/25/92) L#01000 7.) Moebius Comments on Miyazaki (AnimeLand #1, 4/13/91) L#01170 8.) Isao Takahata Interview (AnimeLand #6, July/August 1992) L#01495 9.) MONONOKE-HIME book synopsis (Brad J. Lucido, Jan. 26, 1994) L#01808 10.) MONONOKE-HIME book "making of article" (Lucidos, 1/31/94) filename/filetype MIYAZAKI ARTICLES Subject: 1.) NAUSICAA "video-single" CD review (THE ROSE, 9/91) L#00079 2.) KIKI'S DELIVERY SERVICE review (THE JAPAN TIMES, 8/29/89) L#00174 3.) NAUSICAA & DUNE (JAPANESE ANIMATION NEWS & REVIEW, 7/91) L#00396 4.) Japanese film [KIKI is mentioned] (L.A. TIMES, 4/4/90) L#00595 5.) Culled comments from THE ART OF TOTORO re the Totoros' ages L#00630 6.) KIKI video insert translation (THE ROSE, November 1991) L#00700 7.) Miyazaki retrospective, i.e. "Totoro Power" (JAN&R, 9/91) L#00802 8.) PORCO ROSSO preview (THE ROSE, February 1992) L#00886 9.) Pre-NAUSICAA BOOK 5 Synopsis (ANIMAGE, 4/4/90 [AH, 3/92]) L#01179 10.) PORCO ROSSO & HASHIRE MEROSU (ASASHI EVENING NEWS, 7/24/92) L#01255 11.) PORCO ROSSO review (THE JAPAN TIMES, 7/28/92) L#01346 12.) TOTORO review (Steven Feldman, November 20, 1989) L#01418 13.) TOTORO review (THE LOS ANGELES TIMES, May 7, 1993) L#01518 14.) TOTORO review (NEWSDAY, May 14, 1993) L#01575 15.) TOTORO review (THE NEW YORK DAILY NEWS; May 13-15?; 1993) L#01614 16.) TOTORO review (THE NEW YORK TIMES, May 14, 1993) L#01673 17.) TOTORO review (Robert Plamondon, May 18, 1993) L#01748 18.) TOTORO review (THE SAN FRANCISCO CHRONICLE, May 8, 1993) L#01846 19.) TOTORO review (THE SAN JOSE MERCURY, May 10, 1993) L#01920 20.) TOTORO review (SISKEL & EBERT, May 9, 1993) L#02093 21.) TOTORO review (VARIETY, May 10, 1993) L#02155 22.) Studio Ghibli & Retirement (Rheault Sylvain, 12/15/93) L#02274 23.) Nausicaa in LUM episode #185 (Jefery Roberts, May 19, 1994) L#02381 24.) Troma's MY NEIGHBOR TOTORO presskit (from before May 1993) L#02947 25.) Allegory in LAPUTA (Bryan Wilkinson, January 20, 1994) L#03008 26.) BATMAN & Fleischer 'toons re Miyazaki (two quotes, 1/13/94) filename/filetype TAKAHATA ARTICLES Subject: 1.) LITTLE NORSE PRINCE synopsis/review (THE ROSE, 11/90) L#00164 2.) GRAVE OF THE FIREFLIES review (Steven Feldman, May 1992) L#00320 3.) GRAVE OF THE FIREFLIES review (Rafael Brown, June 24, 1992) L#00424 4.) OMOIDE POROPORO review (ANIMAGE, 1/91; THE ROSE, 1/91) L#00489 5.) OMOIDE POROPORO review (THE JAPAN TIMES, August 7, 1991) L#00672 6.) OMOIDE POROPORO review (Bryan Wilkinson, August 18, 1992) L#00890 7.) OMOIDE POROPORO review (John W. Yung, April 14, 1992) L#00973 8.) GOSHU THE CELLIST mini-synopsis (Walter M. Amos, 8/3/93) L#01013 9.) UMI GA KIKOERU mini-synopsis (Alan Takahashi, 7/18/93) L#01085 10.) COLLISION! AKIRA KUROSAWA VS. HAYAO MIYAZAKI (9/13/93) L#01280 11.) Jo Hisaishi Discographies (Atsushi Fukumoto, 6/2/94) L#01487 12.) Isao Takahata Interview (AnimeLand #6, July/August 1992) L#01812 13.) HEISEI TANUKI GASSEN PONPOKO synopsis (B. Lucido, 7/17/94) filename/filetype OPP SYNOPSIS Subject: 1.) OMOIDE POROPORO synopsis (Bryan Wilkinson, July 22, 1992) L#00478 2.) OMOIDE POROPORO review (Bryan Wilkinson, August 18, 1992) L#00696 3.) UMI GA KIKOERU mini-synopsis (Alan Takahashi, 7/18/93) L#00768 4.) UMI GA KIKOERU timing file (Blue Shield, [July 29,] 1994) filename/filetype FIREFLY SCRIPT Subject: 1.) GRAVE OF THE FIREFLIES script (Miho Nishida, Mar. 28, 1992) L#01278 2.) ANGEL'S EGG synopsis (Bryan Wilkinson, December 22, 1991) L#01432 3.) ANGEL'S EGG script (Enrique Conty, October 8, 1992) L#01563 4.) ANGEL'S EGG timing file, in JACOsub (Fred Leggett, 1/5/93) L#01687 5.) ROBOT CARNIVAL script (Ron Azuma, January 17, 1990?) L#02231 6.) PLEASE BLINK, GRANDMA synopsis (JAPAN TIMES, July 30, 1992) -----------------------------cut here----------------------------------- Date: Wed, 28 Jul 93 06:07:12 EDT Subject: list nausicaa DATABASE MEMO NOTE: listserv database functions can only be implemented if you are on Bitnet (and even then, some Bitnet users in foreign countries may not be able to take advantage of this feature due to the nature of their links). In other words, the database will not work via Internet nor ftp. Sorry. To access listserv's database, send a command to listserv that says, "get listdb memo". This will tell you all you need to know. I admit, it *is* a little arcane, though, so here's a mini-primer for how to use listserv's database function. First of all, certain files must be requested from listserv that are or act as execs. Here's part of the LISTDB MEMO (after that, I'll try to explain things a little): | Accessing the database | ---------------------- | | The database can be accessed either interactively or in "batch" mode. | In the former case, you must obtain the LDBASE user interface by | sending the following commands to your nearest LISTSERV: | | o For VM/SP CMS systems: | | - TELL LISTSERV AT nodeid GET LDBASE EXEC | | - TELL LISTSERV AT nodeid GET LSVIUCV MODULE | | The command to start the user interface is simply LDBASE to access | your "home" server, or LDBASE nodeid to access the LISTSERV server | at nodeid. | | o For VAX/VMS systems: | | - SEND LISTSERV@nodeid GET LDBASE COM | | The command to start the user interface is @LDBASE. This will | install the required files in your directory and display more | detailed instructions about the program. In other words (for VM/CMS users like *me*, at least), first send these three commands: tell listserv at brownvm get LISTDB MEMO tell listserv at brownvm get LDBASE EXEC tell listserv at brownvm get LSVIUCV MODULE Then, type the following command: ldbase brownvm (Note: do NOT type "tell listserv at brownvm ldbase brownvm", but simply "ldbase brownvm". Failure to observe this goofy ideosyncracy will prevent you from accessing the database.) The Ldbase command will link you to the database at brownvm. Then, use a syntax like, "search fileserver in nausicaa". A message will tell you how many items turn up with the description "fileserver", and will identify them as "hits". (In this case, there were 39 hits.) Next, type "index", and the hits will be listed. Write down the dates, and then request the appropriate archives from listserv. It's also possible to make the search request more specific so as to narrow down the field of inquiry. For example, try a search like, say, search fileserver memo in nausicaa or even more precise than that: search <*> miyazaki fileserver memo <*> in nausicaa The first command yielded a total of 15 hits, whereas the second command yielded 13. What remains is to match the results of the Index command to a archival log on the fileserver. In the case of the search for <*> miyazaki fileserver memo <*>, the first four hits revealed via the Index command are listed as being posts from the dates 91/08/14, 91/09/03, 91/10/24, and 91/11/13. These correspond to nausicaa logs 9108b, 9109a, 9110c, and 9111b, thusly: 91/08/14 ..... nausicaa log9108b |[log = year/month/week] 91/09/03 ..... nausicaa log9109a |[a, b, c, d & e = weeks of the month] 91/10/24 ..... nausicaa log9110c |[week = 7 days (or less, in e's case)] 91/11/13 ..... nausicaa log9111b |[e = day(s) 29(-31) of a given month] -- Steven Feldman ** PLEASE NOTE: ** The machine (BrownVM) which stores archives of postings to the list has allocated us a finite storage capacity, and so very early postings (such as shown in this LDBASE example) are no longer present on BrownVM. You will be able to find archives of messages up to about two years old, since as the space allotted to us is filled, we purge archives of messages of approximately that age or older. -- Michael S. Johnson