NetHistory

VM/COM, June 1985

1
-
## ## ### ### ### ###### ###### ### ###
## ## ## ### ## ## ## ## ## ## ## ### ##
## ## ## # ## ## ## ## ## ## # ##
## ## ## ## ## ## ## ## ## ## ##
## ## ## ### ###### ###### ## ##
- --- Volume 2 Number 1 ---------------------------- June 1985
-
CSNEWS Newsletter and Bulletin
-
-
-
0 Staff:
0 Geert K. Marien (GKMXU@CUNYVM) Editor-in-chief;
Andrew T. Robinson (ANDY@MAINE) Managing Editor;
0 Prof. G. Markowsky (MARKOV@MAINE) Faculty Advisor;
- WE NEED MORE STAFF !!!!!
-
0 Ôçççççççççççççççççççççççççççççççççççççççççççççççççä
³ Newsletter contribution userid: CSNEWS@MAINE ³
³ ³
³ ³
Contributions from readers welcomed and encouraged!
¨ççççççççççççççççççççççççççççççççççççççççççççççççç]
1
0 PAGE 2
0 TABLE OF CONTENTS
-
0 Article/Column Page
0 CSNEWS Notes ............................................ 3
Staff Changes at CSNEWS ................................. 4
An RSCS Tutorial ........................................ 5
'JES 2 Give U an MVS Perspective ........................ 7
Terminal Sickness ....................................... 9
An Operator's Viewpoint ................................. 12
SERVERS ................................................. 14
1
0 PAGE 3
0 CSNEWS Notes:
+ CSNEWS Notes:
0 by Andrew T. Robinson and Geert K. Marien
-
- We would like to extend a warm welcome to all new and
veteran BITNAUTS and to start this VM/Com issue on a
positive note. CSNEWS is expanding and we are doing this in
many ways. First of all, VM/Com will be a monthly
newsletter. We are putting together a staff and invite all
to join. Any articles will be appreciated. Second, we are
expanding our services all the time. Not only are new
facilities being added, such as the Bulletin Board, but
other services are being combined with CSNEWS. CSDEPT at
MAINE is one example.
0 As if that isn't enough, we are enlarging the number of
CSNEWS local 'contacts' and reorganizing their roles into
one that could include chapters at some universities. The
main goal of these chapters will be to educate and assist
users on the uses of BITNET, and indeed even to help users
on a one-to-one or group basis with their day-to-day
academic work. All this means that we will need a larger
support staff for VM/Com in the near future. Anyone who
wishes to help out, please contact Geert on GKMXU@CUNYVM.
0 There is now a new central operators id for CSNEWS, which
is CSNEWSOP at MAINE. This id serves as an alternate
priviledged id for operators, and a vehicle for testing new
CSNEWS software. This machine may be running the CSNEWS
system from time to time, but it will not be accessible to
the general user community.
0 You may leave mail and inquiries about CSNEWS or mail to
any of the operators on CSNEWSOP, and it will find its way
to the appropriate person.
0 For information regarding new CSNEWS developments, and
new services, it may be worth your time to check out the
following CSNEWS public files:
0 CS_SERV CSNOTICE
CSNEWS UPDATES
SERVER CSNOTICE
0 You might also want to try the following commands on CSNEWS:
0 NEWS
QUERY LOGMSG
1
0 PAGE 4
0 Andy Robinson
Director of CSNEWS Info Services
0 Geert K. Marien
VM/Com Editor-in-Chief
1
0 PAGE 5
0 STAFF CHANGES
+ STAFF CHANGES
-
0 In the past couple of months, there have been some
changes in the operations staff of the CSNEWS server, as
well as some of our operational policies (which will be
discussed at a future date).
0 Barry Gates, one of the original writers of the BIT
software on CSNEWS, as well as much of the support software,
is no longer working for the server directly. Barry is now
maintaining our new info-disk, the COMDISK, and will be
graduating this August. He was one of the major influences
that has made CSNEWS what it is today.
0 One of our operators, Sean C. Colbath, will be leaving
for college at the University of Rochester this fall. Sean
will continue in his operator status while in Maine this
summer, and will be authorized on his id at UOR. Sean is
also working with Barry Gates on the COMDISK service.
0 Amongst all the departures, we would like to welcome
David Gridely to the CSNEWS staff as a restricted operator.
David is now a sophomore in a local high school, and we have
decided to start training him now so we will have some new
people available when the current crew graduates. David
will be working on software testing and user interface
development over the summer. His id is IOR00609@MAINE,
which is a restricted ID on the Maine system.
1
0 PAGE 6
0 An RSCS Tutorial
+ An RSCS Tutorial
or
The DOs and DONT's of BITNET
+ The DOs and DONT's of BITNET
- by
Daniel Oliverfeld
0 Weizmann Institute of Science
Rehovot, Israel
-
0 This article is meant to explain the "ins and outs" of
RSCS/N - Remote Spooling Communications Subsystem /
Networking (a real mouthful); the thing that BITNET is based
on. Without RSCS/N, we would still be in the stone ages of
sending messages to local users and never knowing the
pleasure of logging on and having 10 pieces of mail from all
over the world waiting in our virtual readers.
0 1) Large files - have a tendency to block the network.
RSCS/N works on the basis of SIFO (you've heard of LIFO,
FIFO and GIGO - so now you have another) - smallest in,
first out. Before RSCS/N sends any file over a link, it
orders the files for that link in size order with the
smallest being at the top of the heap. It then sends the
smallest file over the link and then repeats the process.
But when a very large file arrives at the top of the queue
(nothing else is there), it begins to be transmitted and
RSCS/N will not transmit any other file until the large file
is completed. If the transmission time is an hour, then all
small files that arrive at that node to be transmitted will
be held up until the large file is sent over. In general,
when you have a large file, try to split it up into smaller
chunks. ÕNote: File PRIORITY is dominant over file SIZE
-Ed.þ
0 2) Priorities - As many of you have found out, RSCS/N
allows users to specify the priority of a file for
transmission through the network. In general, MAIL files
get sent with a priority of 50 and NOTE acknowledgements get
sent with a priority of 90. If you have a very large module
that cannot be broken up into smaller pieces, why not send
it with a priority of 99?
0 For those unfamiliar with the TAG command:
0 CP TAG DEV {PUN³PRT} nodename vmuserid 99
0 3) QBIT - Many users have come to enjoy the QBIT
CHATTER=YES command. But it too can harm the network if
used unwisely. Suppose you have 100 users in your NAMES
1
0 PAGE 7
0 file with CHATTER=YES, and you do a QBIT with CHATTER=YES.
A hundred CPQ USER commands will be going out over the
network (each command and message buffer is 160 bytes long,
in case you were ever interested), and you will receive in
return 100 responses from various nodes in the network.
These CPQ USER commands will usurp the line away from file
transmission. Have you ever noticed that when you send a
CPQ U or a CPQ T to a relatively close node the response
comes back in 2 minutes instead of the normal 3 or 4
seconds? You figure it is a glitch and when you try it
again, network response time is back to normal. The reason
this occurred was because some user issued a QBIT
CHATTER=YES with many users listed and you had the
misfortune of being queued behind him.
0 The author of QBIT, Yossie Silverman (VSYOSSIE@WEIZMANN),
has modified QBIT to count the number of CPQ USER commands
you have sent over the network in the past hour and if it
exceeds 100, QBIT starts asking you to be kind to the
network and stop using QBIT.
0 4) Chat - There are various Chat server machines located
throughout the network as Henry Nussbacher (VSHANK@WEIZMANN)
has brought to everyones attention. To summarize his
lengthy tirades, as you get closer to the node that is the
Chat server machine, the RSCS/N links begin to get
overloaded with rebroadcasted messages. William Guttenplan
(BILLY@BMACADM) even mentioned to Henry that there was a
time when there were about 15 users on his Chat and *NO*
files were able to come across the RSCS/N link for the 4
hours that people were chatting. Currently, various Chat
authors have implemented usage limitations (message counts,
access times). Hopefully in the future, CUNY/BITNIC will
come through with a better solution. In the meantime,
please exercise some restraint when using a Chat server.
0 5) Chain letters - This area has become very popular via
the local post office and currently it is considered "cute"
to send out an electronic chain letter. This type of
activity never advanced anyones computer knowledge, nor did
it bring together people of similar interests (like Chat
does). Chain letters are just a plain abuse of the network
and falls into the category of obscene messages and mass
mailings to 800 Bitnauts users looking for new games.
0 Now that you know what you can do to help BITNET out, let
me leave you with one thing that you can point out to your
computer center if it happens. As with all TP lines, I/O
errors can occur. In general, if the error count becomes
too high, then you probably have a loose wire or a noisy
Telco line. How can you help out? There is a command:
0 SM rscsid Q linkid SUM
1
0 PAGE 8
0 The response from RSCS/N will indicate how many blocks
were sent (TOT=nnnnnnnn), how many blocks sent were flagged
as errors (ERRS=nnnnnnnn), and how many timeouts have
occurred on the link (TMOUTS=nnnnnnnn). Take the TOT and
the ERRS and add them together. Then see what percentage of
that number were blocks that were sent in error (Equation:
errs/errs+tot). If the percentage is higher than 10%, you
should contact your computer center and inform them that
they have a communications problem.
0 Well, I hope this has helped you in understanding more of
how RSCS/N works and what is considered harmful in a large
network like BITNET.
1
0 PAGE 9
0 'JES 2 Give U an MVS Perspective
+ 'JES 2 Give U an MVS Perspective
0 by
0 Daniel B. M. Spillane III
(F1.DYN@ISUMVS)
-
- Being the very first BITNAUT in the world from an MVS
node, I am in a very unique position among a mainly VMish
network environment. Indeed, as an undergrad at ISUMVS,
(Iowa State University -- NO I'm not a farmer!), I am also
one of the first (and only) users of BITNET, (the "NET"),
here.
0 Iowa State has four VAX-11/780 CPU's running VAX/VMS 3.7,
on which I have had most of my undergrad experience. Iowa
State also employs node ISUMVS (an IBM 360-165), which is
connected to BITNET. ISUMVS runs under MVS/JES2, which
turns out to be a limitation as far as BITNET goes (more on
this later).
0 MVS/JES2 is much different than anything that runs VM.
0 I have had limited experience with Cornell CMS (Thanks,
Steve!), and CMS seems just about as strange to me as I
imagine that MVS would seem to a VMer.
0 Rather than plunging into a deeper (boring) discussion of
MVS, I will first give you VMers a basic description of how
our MVS system is set up and its relationship to the NET...
0 In the world of MVS, there exists a node in the forsaken
state of Iowa called ISUMVS. Within this node exist three
intimately related virtual creatures known as WYLBUR, ORVYL,
and MILTEN. WYLBUR is the wise man, ORVYL the librarian,
and MILTEN the messenger. These three fellows are the
subjects of (and ultimately there jobs are under the control
of), a ruthless dictator known as JES2 - (JES1, the first in
the JES dynasty, was apparently usurped from his throne by
dissatisfied users and all records of him were wiped from
memory)...
0 MILTEN is a very generous creature, and just loves to
help all of us at Iowa State share time with WYLBUR. WYLBUR
is very energetic and doesn't mind being shared either. He
is always very quick to respond, and ORVYL is always there
if WYLBUR needs him to store or retrieve something.
0 Now back to what is known to most as "reality"...
1
0 PAGE 10
0 The existence of the NET is not so apparent to MVS users
as it is to a VMer. There is nothing that is called the NET
as far as WYLBUR, ORVYL, and MILTEN are concerned. This
perhaps in part explains the lack of users from MVS nodes
who are "out" on the NET. Besides, WYLBUR, ORVYL, and
MILTEN are somewhat socially retarded when it comes to
relationships with other machines on the NET. One example
of this is MILTEN's apparently unsuppressable vanity when it
comes to inter-node messaging. (The TO command is the MVS
equivalent of CP SMSG NET MSG ). MILTEN
feels that he must tell everyone on the the NET exactly what
MILTEN "line #" an ISUMVS user is on when a msg is sent.
This "line #" is meaningless to everyone who is off-node.
Not only that, but at first CSNEWS was unable to understand
my messaging until the CSNEWS program was modified (Thanks,
ANDY!), to compensate. It is also possible to set a name to
be associated with this number. This means that a message
from ISUMVS (as received by a VMer) may have the following
format:
0 GG.UUU "name" (line #) :
0 There are also two other unfortunate shortcomings I have
found. One is that if I am messaged from another node, the
message lines I get may not be received by me in the same
order they were sent. Another is that for some reason, we
are limited to only a subset of the available BITNET nodes.
There are no international nodes available to me for
messaging or mail. WYLBUR, ORVYL, and MILTEN apparently
need face-lifts!
0 ÕDan is a junior in the Computer Science program at ISU.
He is originally from the north suburban Chicago area, and
his interests (besides BITNET) include physical fitness and
the TV series DYNASTY.þ
1
0 PAGE 11
0 TERMINAL SICKNESS
+ TERMINAL SICKNESS
0 or
0 What to Do When Your Terminal Doesn't
+ What to Do When Your Terminal Doesn't
- by
0 Andrew T. Robinson
(ANDY@MAINE)
-
- As computer users, I am sure most of you have had to deal
with terminals at one time or another. Whatever the
terminal, IBM 3270, 3101, Televideo, Dec VT terminals, etc.
etc., and whatever protocall simulator, SIM3278, Series/1,
you have probably run into the 'Branch And Hang' syndrome at
one time or another. It is my purpose here to suggest some
possible solutions to this dilemma.
0 There are basically two types of terminals -- those that
hang in TTY mode and those that hang in full-screen mode.
Whenever I get the chance, I try to hop onto a Televideo 924
on series/1, but more often, I live at home on an Atari 800
at 300 baud. If you want to do any work, take my advice and
stick to full-screen terminals.
0 First, a discussion of what MAKES a terminal stop. The
first and most obvious cause is outright system failure (or
in more eloquent terms, a 'crash'). The crash is usually
not accompanied by the sound of human screams and crunching
metal and shattered glass... as a matter of fact there is
usually no sound at all, and often no warning. On the
series/1, your cursor goes over to the lower-right corner of
the screen and stays there... you hold your breath hoping
it is just CP sticking you back in queue after a long idle
time, or the series/1 having a hickup. After a few seconds
of pounding the return key, you start looking around...
0 'you hung?' you ask the person next to you...
'yup' he answers...
- You look up and see several other people looking
perplexed, and banging on the return key, and hear a few
announcements of 'crash' or 'system's down', and an
occasional 'oh ____, I just lost my 3000 line operating
systems project...!'. A few suicides are comtemplated,
occasionally brought to fruition.
1
0 PAGE 12
0 On a TTY terminal, the symptoms are similar: the cursor
stays... it doesn't move... it stays... and it stays... and
nothing happens...
0 A 3270 may be nice to you, and give you a 'lightning-
bolt-505' or it say just sit there and say 'SYSTEM' at you.
0 Now, at this point either the CPU has gone down, or the
terminal controller has died, or the operator is playing a
cruel trick and has disabled all the lines. The most
important thing to remember about a crash is that IT WILL
HAPPEN TO EVERYONE ELSE, TOO. If you are sitting there all
alone and hung while Joe User is working right along, you
have other problems...
0 What to do about a crash? Sit down, sit back, put your
feet on the table, order a pizza, talk to the person next to
you (who is still modifiying his XEDIT screen and hasn't
noticed the crash yet, and wonders why everyone is making
such a fuss). Basically, all you can do is wait. Murdering
the operator will only delay recovery, and detonating the
CPU will only result in a much longer down-time still....
If you are bigger than the person next to you, you can take
your frustrations out there, but this is also discouraged
since it often brings men in little blue suits to take you
off to put you in an involuntary wait state. Reefing on the
terminal has no effect, and often prevents anyone from using
it when the system DOES come back up...
0 Now, if you are that lonely soul who finds him/herself
hung while all others are doing fine... Well... you have a
wider range of options... God only knows whats makes a
single terminal hang. Maybe the communications line, the
controller being twitty, occasionally an operator playing
games and HALTing a specific line (that you happen to be
on)... In any event, your cursor goes over to the corner of
the screen and stays. You are not worried about the cause,
just about finding a solution. You have several
alternatives:
0 1) Find a new terminal that nobody is using, and log on
to it; assuming the other terminal is not holding your id in
limbo.
0 2) Kick an l-user or rugrat off a terminal and take it
over. This often is a satisfying pursuit, even when you
aren't hung.
0 3) Pick your terminal up by the power cord, spin it
around over your head, and let it fly the length of the user
area, and crash into the far wall. In its reduced state, it
is unlikely to hang another user in the near future...
1
0 PAGE 13
0 4) Punch the keyboard until key-caps start flying off.
Sometimes the terminal will surrender, and start working
again. Usually it will end up in a state like (3).
0 5) Put your fist through the screen. Similar to (4) but
often more painful for you than the terminal. After you
have done it once, you will usually passively accept
whatever the terminal does to you in the future.
0 6) Punch a wall. Like (5) it hurts, but does not destroy
valuable (??) equipment. If you really MUST punch
something, punch a wall; It costs less to fix/replace.
0 7) Sit and fume. Maybe not the most satisfying, but
perhaps the most impressive if you put on a good act. Often
you will find people slowly edging away from you giving you
wary sidelong glances, leaving a plethora of terminals open
for you to choose from.
-
Of course there are other problems that plaugue
terminals. Bad keyboards (one of the 924s here won't type
'e', 'o', or a space), bad screens (the 'underwater'
effect), and bad communications lines (had your terminal
talk in APL to you lately, when you didnt ask it too???).
The list goes on...
0 If you ever try the solutions above you will find that
either a) you are in jail (or facing vandalism charges,
possibly a murder rap), or b) none of them work. But I bet
it felt good to see that terminal byte the dust...
0 I guess the ultimate solution is not to use a terminal,
but to communicate with the computer by power of thought.
If anyone finds out how to do this please tell me (although
I sometimes think my 'terminal' would hang more often under
those circumstances).
- Computer say:
+ Computer say:
'He who shift left too far, fall into bit-bucket.'
1
0 PAGE 14
0 An Operator's Viewpoint
+ An Operator's Viewpoint
0 by
0 Walter G. Horbert
(WALT@MAINE)
-
- ÕNote: This article is specific to the University of
Maine, but the basic ideas can apply to almost any
installation. -Ed.þ
0 This article describes some proceedures that will help
you to best make use of the facilities of the IBM 3033 and
it's associated hardware. It's a new term, and for the
operators of the machine, it's business as usual. Sure,
there is a heavier load on the system, and more jobs get run
in the course of the day, but overall things are status quo.
Well, almost. With the influx of new users there is an
increase in user-operator interaction.
0 Unfortunately (for both the users and the operators)
there is sometimes a misunderstanding about what an operator
is. It is the operator's job to oversee the production
activities of the cpu. This involves scheduling tasks to
execute, changing disk volumes for applications that need
them, mounting new forms on the printers, and mounting tapes
for both batch and interactive users.
0 The operator is kept pretty busy by all this, so much so
that he or she usually can be seen eating lunch while
keeping one eye on the machine. In the operator's spare
time (if he has any) he might work on a program, read a page
or two out of some new documentation, or perhaps just sit
and relax for a moment before deciding what to run next.
0 Now is a good time to point out that the operator is not
a consultant - it is not the operator's job to answer
questions. The computing center has several full-time
consultants, as well as many students that consult at
regular times during the day and evening. The consultants
don't operate the machine, and the operator doesn't consult.
0 Operators often don't have time for chit-chat either.
The operator's complex has four terminals that contain
system information, task scheduling data, job status data,
etc. The operator's console isn't a place for conversation.
Most of the operators have userids of their own, and if they
have time, will log on. If you happen to know an operator
personally, that operator's personal id is the place to
contact him for non-computer things. The reverse is also
1
0 PAGE 15
0 true - don't send a message to an operator's personal id
when you need a tape mounted, chances are he or she is miles
away from the nearest tape drive!
0 Speaking of tapes, the computing center has over 5,000 of
them. Between 200 and 300 of them get mounted every day,
some for the batch services, and some for interactive users.
0 If you are an interactive user and you want a tape
mounted on your virtual machine, there are a number of ways
to communicate your desire to the operator. You can try
pantomiming your thoughts through the plexiglass, or perhaps
shouting from the dispatcher's window, but the best way is
to send a message directly to the system operator with the
CP MESSAGE command. A sample request might be:
0 M OP PLEASE MOUNT TAPE TO9876 RING IN PASS PIGEON
- This message will go to the system operator, and he will
get your tape from the tape library and attach it to your
virtual machine at address x'181'. If you don't specify
RING IN, the operator will mount it RING OUT (Read only).
0 If the tape is not assigned to the id/account code that
you are using at the moment, a password must be supplied.
If for any reason the tape can't be mounted within five
minutes (that's the time it takes to get your tape, etc),
the operator will send you a message describing the problem.
During the daytime hours tape drives are often heavily used
- one may not become available for ten minutes or more.
0 Remember too, the operator has other tasks that may keep
him or her from mounting your tape right away. Very often
the beep from your message cannot be heard when the operator
is aligning a form on a printer, or putting on a new box of
paper.
0 Speaking of printers (what a smooth transition eh?), the
computing center on the Orono campus has two. Both print at
about 1,000 lines per minute when printing uppercase
material. Printing speed is cut in half when printing mixed
case text.
0 Most of the time the printers are set up for uppercase
output - this gets the greatest number of print files out of
the computer's file space and into our user's hands in the
shortest time .
0 Special forms - something other than the standard form
"A" - are printed at the end of each shift. This includes
any of the hundreds of forms used by the University, as well
as the more common 9x11 forms used for term papers and the
like. If you create a file to be printed on 9x11 paper
1
0 PAGE 16
0 during the day, it will likely be out of the system that
evening. If you wait till nighttime to create your file, it
might not be out until the next morning (there is no
dispatcher after midnight).
0 I guess that's a fair summary. Please be aware that this
essay consists only of my own thoughts and opinions, not
necessarily those of the University or the Computing Center.
I have not covered all facets of the operator's tasks, there
is a lot more, but this wasn't meant to put you to sleep!
1
0 PAGE 17
0 SERVERS
+ SERVERS
0 by
0 Michael R. Dow
(CSNM065@MAINE)
-
- Today's subject is Servers. Just what IS a server, such
as the CSNEWS virtual machine running on the University of
Maine's central IBM mainframe, node (MAINE)?
0 For the most part, a lot of people have wrong impressions
of what servers actually are or can be - or should be.
Certainly, computer servers exist in many forms, for many
functions. In this short piece, I'll try to share my own
views on servers, hopefully to wet your appetite for
experimenting with those machines we have readily available
on the BITNET.
0 A server is installed on a network to do just what the
name implies -- to serve. Usually, on BITNET, a server is a
virtual machine running unattended that monitors spool files
and messages, and responds automatically. Some act as CHAT
machines, allowing many people to have on-line conferences
or gab sessions easily. Others act as repositories for
general-interest documents or semi-public-domain software,
and forward copies upon request. A good many are
experimental, and are used as learning exercises into the
field of artificial intelligence and machine/human
interaction. And, of course, a few simply waste computer
time.
0 A real server should offer needed and useful services.
CSNEWS offers all BITNET users a collection of public domain
files, both for academic and private use. CSNEWS also
houses the famed BITNAUTS LIST, a large file containing the
userids, names, and listed interests of hundreds of
University researchers, instructors, and students.
0 A little more about the BITNAUTS list. This service was
aimed at maximum utility and accuracy - users can, by
interacting with the CSNEWS software, add, delete, or change
their own personal information, and request a copy of the
complete list - similar to the USER information file
available at the BITSERVE server at CUNYVM. Why is this
list vital, or even desirable? The designers of CSNEWS
realized the value of the human contact - rare in the
computer mainframe business - and knew that perhaps the most
valuable service is one which helps people find people.
1
0 PAGE 18
0 Other servers such as CUNYVM's BITSERVE offer files which
give general and specific information about BITNET to
inexperienced users so that they can learn more about this
communications/file transfer system. Files such as 'BITNET
TOPOLOGY' map the nodes connected to BITNET and the gateways
to other networks such as ARPANET as CSNET.
0 The list of servers goes on endlessly - new ones appear
weekly - sometimes daily. Most are helpful, offering unique
services.
0 The best thing to do when you find out about a server is
to send it a message saying 'HELP'. It nearly always works,
and can get you started on the way to new and interesting
experiences. So, when enjoying your next Coke and sitting
in front of your terminal, try talking to a server. Find
out what it has to offer. You'd be surprised..... The
things actually do serve a purpose other than chatting.
0 To get you started on CSNEWS, try sending (from your CMS
ID):
0 TELL CSNEWS AT MAINE HELP
- Here is a small list of servers on the BITNET to help get
you on your way:
- BITSERVE at CUNYVM (BITNET info. and userlists)
CANSERVE at CANADA01 (BITNET-NetNorth file server)
CSNEWS at MAINE (Public files; BITNAUTS LIST)
NETSERV at DEARN (European BITSERVE type server)
NICSERVE at BITNIC (Will replace BITSERVE at CUNYVM)
VMBBOARD at WEIZMANN (Israeli BITNET server)