The purpose of parlib is to support comp.parallel readers in several ways.

1. To serve a function similar to netlib. Rather than concentrating
on the latest working subroutines or complete systems---
these really belong on something like netlib---the goal here is to get lots
of different codes for the same problems---one for each language and/or
machine. I am actively soliciting vendors and programmers for codes
representing simple problems. These codes are available through parlib.

2. To serve as an information source. There are two basic issues here,
I think. One is the so-called FAQs (frequently asked questions). We have not
had an organized attempt to keep track of FAQs. I have some ideas about a way
of automating this. (Anyone got a spare student looking for a project?).
The other information source is through bibliographies. I would like for
people who are willing to share their bibliographies but who do not want to
give up control to send me a message so I can set up a directory. I'll think
about accepting full text bibliographies as soon as I get under motion.

3. I'm open to other ideas in support of the community as long as it does
not become a time sink.

4. All this is on a friendly user basis!!!!!!!!

Instructions for using Parlib

A very rudimentary version of the parlib is available by using the following
method. You use your mailer (NOT the news software unless it lets you escape
to the mailer). It will hopefully improve as I get more time to smooth things
out.

prompt> mail parlib@hubcap.clemson.edu
        Subject: <cr>
        send index
        <eot>
prompt>

Your request will be returned by e-mail. All this works like netlib. I
have stolen their directions and suitably modified them. The message you
get back will have the mail headers and assorted bureacracy, followed by
the message. The message is actually a shell script. In order to get your
information, you need to 
	a. Get in your favorite editor after saving the message in a file.
	   For example, let the file be "message".
	b. Remove all the mail information.
	c. The first line of the new file should read "#!/bin/sh".
	d. Save the file and exit the editor.
	e. Run the shell against the file: "sh message".
The shell script will remove the shell information and produce a file with
the correct name BUT is usually is also in a directory created. For example,
the response to "send index" produces a directory (master) with two files
"disclaimer" (these instructions) and "index" (the name of all directories).

Example Requests
 Here are examples of the various kinds of requests.
 *  get the full index for a library
 	send index from intel860
 * get the index to the intel860 C programs (illustrates directory paths)
	send index from intel860/c
 *  get a particular routine and all it depends on
 	send hello.f from intel860
 *  set the chunk size used for reply
 	mailsize 100k
 *  (optional) end of request
 	quit

 The Internet address "parlib@hubcap.clemson.edu" refers to a VAX
 machine at Clemson University in Clemson, SC.
 This address should be understood on all the major networks.  

 An excellent guide to the mysteries of networks and address syntax is:
 Donnalyn Frey and Rick Adams (1989) "!%@:: A Directory of Electronic
 Mail Addressing and Networks", O'Reilly & Associates, Inc, 632 Petaluma
 Ave, Sebastopol CA 95472.  Background about netlib is in Jack J.
 Dongarra and Eric Grosse, Distribution of Mathematical Software Via
 Electronic Mail, Comm. ACM (1987) 30,403-407 and in a quarterly column
 published in the SIAM News and SIGNUM Newsletter.