From: AR402004%BROWNVM.BITNET@VTVM1.CC.VT.EDU (Steven Feldman, Miyazaki listowner)
Newsgroups: rec.arts.anime
Subject: <*> MIYAZAKI FILESERVER MEMO <*> [new scripts added!]
Date: 1 Sep 92 02:23:12 GMT
To: Hayao Miyazaki Discussion Group <nausicaa%BROWNVM.BITNET@VTVM1.CC.VT.EDU>,
        Japanese animedia and other animation news <anime-l@VTVM1.CC.VT.EDU>

Hello Everyone,
     This version of the FILESERVER MEMO features several changes.  First
among them is the addition of a DATABASE MEMO.  Second is the changing of
SHUNA BYPANEL to SHUNABY PANEL (so that it now matches SHUNABY PARAGRAF).
Third and most dramatic is the addition of the following five new files:

TAKAHATA ARTICLES   Various articles about or by Isao Takahata
PORCO    SYNOPSIS   David Oakey's Porco Rosso synopsis
FIREFLY  SCRIPT     Miho Nishida's Grave of the Fireflies script
POROPORO SYNOPSIS   Bryan Wilkinson's Omo(h)ide Poro Poro synopsis
ONNEAMIS SCRIPT     Neil Nadelman's Wings of (H)onneamis(e) script

     Nothing in the TAKAHATA ARTICLES file is new.  It was created to
free up more space in the MIYAZAKI ARTICLES file.  Likewise, the POROPORO
SYNOPSIS and PORCO SYNOPSIS files were moved from within the MIYAZAKI
ARTICLES file.
     Using listserv's database can make locating strings in the archives
a joy (rather than the chore it used to be).  Give it a look.

                          -- Steven Feldman <ar402004@brownvm.brown.edu>
+          +          +          +          +          +          +

Subject:  list nausicaa FILESERVER MEMO
Date:     Mon, 31 Aug 92 19:50:54 EDT

Dear People,
     The "Hayao Miyazaki Discussion Group" list <nausicaa@brownvm> 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.  Some tips on command
syntax for users of other systems is given towards the end of the memo.

     Here are some common listserv commands relevant to the Miyazaki list
that you might want to use:

subscribe nausicaa <login@address> <Your Name>
  (this will send a subscription request to the list administrator)

signoff nausicaa
  (this will unsubscribe you from the list)

review nausicaa
  (this will send you a list of all the current list subscribers)

stats nausicaa
  (this will tell you who is posting to this list and how often)

|index nausicaa
| (this will send you a list of all the available long files and weekly
|  archives from Nausicaa Filelist; same as "get nausicaa filelist")
|
|get nausicaa filelist
| (this will send you a list of all the available long files and weekly
|  archives from Nausicaa Filelist; same as "index nausicaa")

get <filename> <filetype> 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".)

help get
  (this will send you a help file on how to use "get" on listserv)


Below is an example of 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      76   597 92/07/30 19:30:38 Miyazaki & Taka
  MIYAZAKI NTRVIEWS   ALL OWN V      73   728 92/04/08 23:25:06 Miyazaki interv
  MIYAZAKI ARTICLES   ALL OWN V      76  1167 92/08/31 20:41:09 Various article
  TAKAHATA ARTICLES   ALL OWN V      75   616 92/08/31 20:57:00 Various article
  FBCONAN  SYNOPSES   ALL OWN V      73   833 92/02/24 16:45:18 Future Boy Cona
  LUPINTV  SCRIPTS    ALL OWN V      73  1579 91/07/25 16:06:47 Lupin III: "Alb
  CASTLCAG SCRIPT     ALL OWN V      80  3230 91/08/29 17:56:59 Lupin III: Cast
  SHUNABY  PARAGRAF   ALL OWN V      73   924 91/10/28 20:18:18 Shuna script (p
  SHUNABY  PANEL      ALL OWN V      73   863 91/12/14 03:07:24 Shuna script (p
  NAUSICAA OLDSCRPT   ALL OWN V      69  1343 91/09/03 20:18:28 Nausicaa script
  NAUSICAA NEWSCRPT   ALL OWN V      79  1565 92/02/01 17:10:03 Nausicaa script
  LAPUTA   SCRIPT     ALL OWN V      77  3512 92/03/28 20:19:30 Laputa script
  TOTORO   SCRIPT     ALL OWN V      80  1006 92/03/12 15:45:15 Totoro script
  KIKI     SCRIPT     ALL OWN V      73  2175 92/03/12 15:44:13 Kiki's Delivery
  PORCO    SYNOPSIS   ALL OWN V      73   350 92/08/31 20:00:08 Porco Rosso syn
  FIREFLY  SCRIPT     ALL OWN V      73  1257 92/08/31 20:03:20 Grave of the Fi
  POROPORO SYNOPSIS   ALL OWN V      75   685 92/08/31 21:00:47 Omo(h)ide Poro
  ONNEAMIS SCRIPT     ALL OWN V      72  3725 92/08/31 20:13:03 Wings of (H)onn

*
*  NOTEBOOK archives for the list
*  (Weekly notebook)
*                             rec               last - change
* filename filetype   GET PUT -fm lrecl nrecs   date     time   Remarks
* -------- --------   --- --- --- ----- ----- -------- -------- ---------------
  NAUSICAA LOG9104B   ALL OWN V      79   448 91/04/14 23:21:52 Started on Thu,
  NAUSICAA LOG9104C   ALL OWN V      80  2002 91/04/21 22:22:40 Started on Mon,
  NAUSICAA LOG9104D   ALL OWN V      80  1439 91/04/28 21:45:08 Started on Sun,
  NAUSICAA LOG9104E   ALL OWN V      79   407 91/04/30 13:48:25 Started on Sun,
  NAUSICAA LOG9105A   ALL OWN V      80  1086 91/05/07 20:29:31 Started on Tue,
  NAUSICAA LOG9105B   ALL OWN V      78   173 91/05/14 20:29:53 Started on Wed,
  NAUSICAA LOG9105C   ALL OWN V      79   308 91/05/21 23:17:37 Started on Tue,
  NAUSICAA LOG9105D   ALL OWN V      80  1629 91/05/28 22:33:22 Started on Wed,
  NAUSICAA LOG9105E   ALL OWN V      79   307 91/05/31 18:39:37 Started on Wed,

SPECIAL NOTE TO THOSE WITH XEDIT (like me):
     Notice that the information at the right cuts off.  To see the rest
of the file, type "right 30" on your command line.  (To return to where
you started, type "left 30".)  [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.

     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
<listserv@brownvm.brown.edu> and make the message read "get CASTLCAG
SCRIPT nausicaa".

     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 LOG9104B nausicaa  (push "Return")

     INTERNET EXAMPLE:
get LUPINTV SCRIPTS nausicaa
get SHUNA BYPANEL nausicaa
get NAUSICAA LOG9104B 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, who's posting, and what the last
week's messages have been like.  This can be done with four 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 stats nausicaa  (push "Return")
tell listserv at brownvm get NAUSICAA LOG9204A nausicaa  (push "Return")

     ADVANCED INTERNET EXAMPLE:
get LAPUTA SCRIPT nausicaa
review nausicaa
stats nausicaa
get NAUSICAA LOG9204A 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 <filename.filetype> <NewName.notebook>".  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 POROPORO SYNOPSIS
          00000017.NAUSICAA is actually ONNEAMIS SCRIPT
          00000018.NAUSICAA is actually FIREFLY  SCRIPT
          00000019.NAUSICAA is actually TAKAHATA ARTICLES

     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)

     Finally, for those who want *more* information, here is some info
right off of a listserv memo:


    |  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 <ERIC@FRECP11> 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.
^^^^^^^^^^^^^^^

     I hope that the above proves helpful.

                           -- Steven Feldman <ar402004@brownvm.brown.edu>

-----------------------------cut here-----------------------------------

Date:     July 11, 1992
Subject:  Indexes for MIYAZAKI NTRVIEWS, MIYAZAKI ARTICLES, and
          TAKAHATA ARTICLES [all 3 files are on the fileserver]

filename/filetype MIYAZAKI NTRVIEWS

Subject:  1.) Interview re animating TOTORO (ANIME-CLUB #19, 6/10/87)
L#00270   2.) Miyazaki and SF [interview snippet] (COMIC BOX, 11/82)
L#00303   3.) "Why I don't Make Slapstick . . . Now" (COMIC BOX, 10/89)
L#00518   4.) "Money Can't Buy Creativity" (PACIFIC FRIEND, January 1991)
L#00639   5.) Foreword to THE ART OF KIKI'S [by Hayao Miyazaki] (1989)

filename/filetype MIYAZAKI ARTICLES

Subject:  1.) NAUSICAA "video-single" CD review (THE ROSE, 9/91)
L#00069   2.) KIKI'S DELIVERY SERVICE review (THE JAPAN TIMES, 8/29/89)
L#00164   3.) NAUSICAA & DUNE (JAPANESE ANIMATION NEWS & REVIEW, 7/91)
L#00386   4.) Japanese film [KIKI is mentioned] (L.A. TIMES, 4/4/90)
L#00585   5.) Culled comments from THE ART OF TOTORO re the Totoros' ages
L#00620   6.) KIKI video insert translation (THE ROSE, November 1991)
L#00690   7.) Miyazaki retrospective, i.e. "Totoro Power" (JAN&R, 9/91)
L#00792   8.) PORCO ROSSO preview (THE ROSE, February 1992)
L#00876   9.) Pre-NAUSICAA BOOK 5 Synopsis (ANIMAGE, 4/4/90 [AH, 3/92])

|NOTE: the following four items used to be stored in this file, but
|      are now stored under the filename/filetype TAKAHATA ARTICLES:
|
|Subject: a.) LITTLE NORSE PRINCE synopsis/review  (THE ROSE, 11/90)
|         b.) OMOIDE POROPORO review (ANIMAGE, 1/91; THE ROSE, 1/91)
|         c.) OMOIDE POROPORO review (THE JAPAN TIMES, August 7, 1991)
|         d.) OMOIDE POROPORO review (Bryan Wilkinson, August 18, 1992)

filename/filetype TAKAHATA ARTICLES

Subject:  1.) LITTLE NORSE PRINCE synopsis/review  (THE ROSE, 11/90)
L#00153   2.) OMOIDE POROPORO review (ANIMAGE, 1/91; THE ROSE, 1/91)
L#00218   3.) OMOIDE POROPORO review (THE JAPAN TIMES, August 7, 1991)
L#00401:  4.) OMOIDE POROPORO review (Bryan Wilkinson, August 18, 1992)

-----------------------------cut here-----------------------------------

Date:         Mon, 31 Aug 92 18:46:03 EDT
Subject:      list nausicaa DATABASE MEMO

     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 <ar402004@brownvm.brown.edu>
Newsgroups: rec.arts.anime