******** ************************************************** * * * * * The independent guide to BITNET * * * * * * October, 1989 * * * * * * Volume 4, Number 3 * ******** * * * * *** * * * * * * * * * * * * * * * * Greetings from Pisa * * ** * * * * * * * * * * ****** * * * * * * * * * * ******** * * * * ======== * * * TTTTTTTT * * * ã0ã0ã0ãã * * * =========== * * * TTTTTTTTTTT * ******** * ãã ãã ãã ãã * * ãã ãã ãã ãã * *** * ãã ãã ãã ã * * * * ãã ãã ãã ã * * * * TTTTTTTTTTTT * * * * ãã ãã ãã ãã * *** * ãã ãã ãã ãã * * ãã ãã ãã ã * ****** * ãã ãã ãã ã * * * TTTTTTTTTTTT * * * ãã ãã ãã ãã * * * ãã ãã ãã ãã * **** * ãã ãã ãã ãã _-- --_ ãã ãã ãã ãã ___------- * -----__=============== _______---------------------- * ---------------------------------------------------- ****** --------------------_________----------------------- * --------------------------_____--------------------- * -------------------------------___------------------ -----------------------------------__--------------- ******** ---------------------------------------__----------- * --------------------------------------------_------- * ---------------------------------------------------- * ---------------------------------------------------- **** -------------------------------------------------- 1 * * ****** ******* * * ***** * * ******* * * ** * * * ** ** * * ** * * * * * * * * * * * * * * * * * * * * * * * * ***** * * * * * * * * * * ******* * * * * * * * * * * * * * * * * ** * * * * * * * ** * * * * * ****** * * * ***** * * * * * * * * * *********************** ******************************* Editor: Christopher Condon CONDON @ YALEVM ********************* Contents - Issue 34 ********************* ********* * *** * EDITORIAL PAGE____________________________________ * *** * * *** * Bitnotes ....................................... 1 *** *** CREN is Here! .................................. 4 * *** * To Where Should You Reply? ..................... 5 * *** * The Best Way to Subscribe ...................... 7 * *** * ********* ********* * *** * FEATURES__________________________________________ * *** * * **** * Announcing ASTRA ............................... 8 * ***** * International Intercultural Newsletter ........ 11 * ****** * FTP from BITNET ............................... 13 * *** *** * * *** **** ********* ********* * * DEPARTMENTS_______________________________________ * ***** * *** * Headlines ..................................... 15 * *** * New Mailing Lists ............................. 16 * *** * Helpdesk ...................................... 20 ***** * Feedback ...................................... 23 * * NetMonth Policies ............................. 27 ********* ********************** 5595 Subscribers ************************ 1 Page 1 ********* * *** * Bitnotes * *** * * *** * by Christopher Condon *** *** * *** * Yale University * *** * * *** * CONDON@YALEVM ********* The following communique was intercepted by one of our more connected NetMonth Covert Operations Staff members. On the advice of our lawyers, we won't go into the gory details of exactly how we received this letter. Rather, we will let it speak for itself: To: CREN Board of Directors Fm: Nick Snotchi (Snotchi & Snotchi Media Relations) Re: BITNET, Inc. becomes CREN Sirs; Let me begin by saying that Snotchi & Snotchi has been more than proud to have been your Media Relations Firm for the past three years. However, we are somewhat taken aback at recent decisions on your part where the Board failed to take advantage of our thirty years experience in matters public. As a result, the effectiveness of our actions on your behalf have been severely limited. This is not the first time we have been in this situation. If you recall, BITNET had already been growing for several years when we were hired to assist and advise in your dealings with a (then) hostile public. Yet, despite our recommendations, you insisted on retaining the woefully ineffective slogan "Because It's There, Because It's Time." Time for what? Time to make the doughnuts? Time to take out the garbage? Time for "The Love Boat"? WHAT? Likewise, the phrase "Because It's There" implys a task or action taken for no reason except its difficulty; hardly the the way to promote computer networking as 1 Page 2 something simple and effective. The idea is to avoid hinting that networking is akin to tackling Everest. You repeatedly rejected suggestions which scored rather highly in our research with the public: "Because It's Terrific," "Because It's Titillating," "Because It's The Right Thing to Do," "Because Nine Out of Ten Doctors Who Use Educational Computer Networks Recommend It To Their Patients Who Use Educational Computer Networks." Alas, the adoption of the name CREN against our wishes is far worse than your BITNET situation could have ever been. Our surveys indicate that 46% of the public believes that CREN is a substance which forms between your toes. Another 34% think that CREN is the poison found of the backs of brightly colored frogs in the Brazilian rain forest ("The warrior brushes his arrowheads against the back of the warty toad, covering them with the deadly CREN.") Still another 16% believe that CREN is the brand of glue used to hold chest wigs in place. The remaining 14% don't know what CREN is, but indicate that they would move to another country if it were found in their water supply. All things considered, a rather negative reaction. We are currently thinking of ways to put a positive spin on this situation. However, the Board has reduced our options considerably by deciding that the CREN acronym should stand for the rather dry "Corporation for Research and Educational Networking." We might have suggested something more enticing, for example, "Cool Researchers / Exciting Networking" or "Cher Really Enjoys Networks." To be blunt, the CREN Board is paying for our services and would benefit greatly if they were used. We implore you, keep us in the loop; if not for CREN, then for the reputation of Snotchi & Snotchi. ***** I was vaguely surprised at some of the reactions to last month's editorial (A Tourist's Guide to BITNET), particularly those concerning the visit to Relay. In all fairness, I have seen Relay conversations significantly more intelligent and 1 Page 3 insightful than the example I gave, but that is the exception, not the rule. On the positive side, a group of enterprising individuals have formed a "Computer Science Channel." On Wednesday and Sunday nights (beginning at 7:00pm Central time) Relay Channel 816 is devoted to talk of computers and computer science. On Wednesdays the talk is about small systems (PCs, etc.) and Sundays the conversations center on mainframes and minis. Some weeks the discussion is targeted; for example, one Wednesday night was devoted to the Commodore Amiga. More people should follow this example. If you have a topic, you can probably create a channel for it. Lest I forget, thanks to all of the people who sent in articles and information for this issue. Your contributions have made for an especially interesting issue! Virtually, Chris Condon@YALEVM 1 Page 4 ********* * *** * CREN is Here! * *** * * *** * by Jim Conklin *** *** * *** * BITNET Network Information Center * *** * * *** * CONKLIN@BITNIC ********* Õfrom Bitnewså Effective September 18, BITNET, Inc., became the Corporation for Research and Educational Networking, CREN (to be pronounced KREN, not see-ren). Of the 413 BITNET Class A and B members eligible to vote on the change, 187 voted for it, there were 3 abstentions, and no "no" votes were cast, according to the BITNET (now CREN) counsel, whose office counted the votes. (Ballots were sent to all the BITNET members, but only votes from the eligible members were counted.) The proposed slate of Board members was approved by similar votes. The new Board of Trustees held its first meeting on the same day, and minutes of that meeting will soon be made available on the BITNEWS list and posted to LISTSERV@BITNIC and the CSNET InfoServer. New officers of CREN are: Bernard Galler, Chairman; Ira Fuchs, President and CEO; Philip Long, Secretary; Martin Solomon, Treasurer. EDUCOM will be the prime contractor for CREN, with continuing responsibility for the BITNET Network Information Center, and new oversight responsibility for CSNET. BBN will continue to have line responsibility for the CSNET Coordination and Information Center. Both BITNET and CSNET will continue to operate as they have operated in the recent past, with the combined efforts of EDUCOM and BBN devoted to their support and improvement. 1 Page 5 ********* * *** * To Where Should You Reply? * *** * * *** * by Michael J. Steiner *** *** * *** * Arizona State University * *** * * *** * AUMXS@ASUACAD ********* I just completed a survey in which I asked the members of the mailing lists IBM-MAIN (at RICEVM1), VM-UTIL (at OHSTVMA), and REXXLIST (at OHSTVMA) if they thought that replies to questions should be always sent to the list, always sent to the original sender of the question, or both (depending on the nature of the question). I sent the following message to these lists: Over the past few weeks, there have been several times when someone would ask an interesting question on one of these lists, but the answers wouldn't be posted to the list. I find these lists very interesting and valuable, and I would really like to see replies to all questions, except ones about how to sign on/off, and flames, and file requests. I propose that everyone, when replying to a message, should either send the reply to the list, or to both the sender and the list. The results are as follows (in ambiguous cases I used my "good judgement" Reply to list: 35 Reply to individual: 18 Depends on question: 12 ------ Total: 65 (I personally voted for "reply to list".) Some good points brought up were that replying to the list would allow everyone to benefit from any knowledge discussed, and that if someone makes an error in a reply, it is more likely to be caught and corrected. Many people expressed that there were times when they didn't receive any answers to an interesting question because answers were sent directly to the originator of the question. Also, some people stated that replying to the list is "what a list is for". 1 Page 6 An advantage of replying to an individual, and then either asking that individual for his replies, or having him post a summary to the list, is a significant reduction in network traffic. Simple questions can be answered without the list being swamped with replies. Unfortunately, the quest to reduce network traffic can be taken to an extreme, such as eliminating blank lines, abbreviating lots of words, etc. which decreases readability, and therefore, the flow of information. The third option, using one's good judgement, seems to be the best solution until we remember that each person's "good judgement" is different, and what may be a simple question to one may be a toughie to another. In summary, list subscribers have to choose between the free flow of information, and network traffic. You can't easily have both. I think that the free flow of information is more important than extra network load, since networks were created for that purpose. HOWEVER, questions about subscribing, unsubscribing, etc., rejected mail, or multiple copies of mail should be intercepted by the list moderator. (Every list should have an active moderator to at least skim each message for non- relevance.) Only in cases where a list is very active, or where certain links are heavily used by a list, should the idea of not always replying to the list be given thought. We can also keep network load to a minimum by not reducing the flow of information, but by reducing the size of signature lines and reducing the amount of text included from a previous note (the >xxxxxxx stuff). For example, snail mail addresses are usually not necessary, and can be requested from the originator when needed. People should only have large signature areas if there is a good joke or quote in it. :-) 1 Page 7 ********* * *** * The Best Way to Subscribe * *** * * *** * by Ben Geer *** *** * *** * Hampshire College * *** * * *** * BGEER@HAMPVMS ********* Ever since I've been using BITNET, I've seen a lot of messages on various lists (I'll use PSI-L as an example) that say something like "SUB PSI-L Susan Smith," or "Please add me to this list," or "Please cancel my subscription," or "How do I subscribe to this list?" These messages clutter up mailboxes and list archives, and may not get you subscribed. LISTSERV (the list server program that manages most BITNET lists) can handle subscription requests automatically, but not if you send them to the list address. You must send them to LISTSERV. In the case of PSI-L, the address to use is LISTSERV@RPIECS. If you send a subscription request to the list address (e.g. PSI- L@RPIECS), it will be sent to all the subscribers of the list, but not to the list server; it may be ignored, and even if it isn't, it will irritate the list owner and the other subscribers. It's fine to send subscription requests directly to the list owner (e.g. I'm the owner of PSI-L, so you could send a request to BGEER@HAMPVMS), but it's simpler to handle your own subscription. Suppose you wanted to subscribe to PSI- L, and your name is Susan Smith. All you have to do is send this message to LISTSERV@RPIECS (*not* PSI-L@RPIECS): SUB PSI-L Susan Smith LISTSERV will then send you a message to let you know that you've been added to the list. No muss, no fuss, and it gets the job done quickly and reliably. 1 Page 8 ********* * *** * Announcing ASTRA * *** * * **** * by Patrizia Cecaloni * ***** * * ****** * Istituto del C.N.R, Pisa * *** *** * * *** **** ASTRA@ICNUCEVM ********* ASTRA (Application Software and Technical Reports for Academia) is a joint project of IBM and CNR (the Italian National Research Council). The aim is to design and implement a free European service through EARN (European Academic and Research Network) for the distribution of information, software in public domain and documentation about academic projects in education and research. The project started in January 1988 and has a 2-year duration The first year has been dedicated to the design and implementation of an experimental service based on prototype software, as well as to the collection of enough data to start the service at the beginning of the second year. In 1989, the activity of the project is directed to the implementation of a distribuited Data Base System. Using this system the user can access several different databases located everywhere in EARN/BITNET. The final version of the service is to be available to all EARN/BITNET users in January 1990. At the end of the project, the results (including database, software and documentation) will be passed on to EARN or CNR, they will then be free to activate an ongoing service or drop it depending on the user demand. As is well known, it is possible to exchange messages and/or files with other users through EARN. Based on this capability, ASTRA searches documents in a remote database and obtains results of queries such as the number of occurrences, list of documents, the documents themselves, software and documentation of a particular project. The service allows EARN users to retrieve documents located either in the ASTRA database at CNUCE or in other databases located elsewhere but accessible from ASTRA with the same user interface. The search is performed on the machine where the database is located and the search time is not charged to the ASTRA user. 1 Page 9 Furthermore the ASTRA server's software can trasform every STAIRS/CMS system (in EARN) in one of the accessible Data Base server for the remote user. Also, other different Data Base systems (like ISIS and SQL) are accessible by the ASTRA user through the same user interface. Data gathering and database management (i.e. updating) is performed directly by the ASTRA staff only on one of the Data Bases: its name is STAR. It is what we call the ASTRA (Application, Software, Technical Reports for Academia) database. STAIRS/CMS has been chosen, mainly for its powerful information retrieval capabilities, for the creation of the ASTRA database. The basic unit of information in the ASTRA database is the so- called 'bibliographic document', or 'abstract'. For every research/educational project an abstract has to be prepared according to the format and rules described in the booklet 'How to submit data to ASTRA'. The abstract contains information about the project: title, name of the participants and their institutions, project description, HW and SW used, starting date and duration of the project. It also contains information about all the products of the project. And, for each product, a product description, HW and SW requirements, availability status, and the name and address of the author are included. ASTRA provides a central European Data Base of information about projects in education and research, and about their products (software, reports, prototypes, etc) and distributes these products if they are in machine readable form. Initial data include information and products regarding IBM Europe joint projects with academic institutions. At the present time in Pisa, in addition to the IBM Europe projects database (STAR), several databases are available, like the CNR patents database (BREV) and the AEP database produced by the University of Texas. Through ASTRA, it is possible to access the CNR projects database resident in Milan at the CNR institute SIAM. A list of the accessible databases is included in the ASTRA documentation. To access ASTRA the user must apply for a subscription. This is done by sending the following command to ASTRADB@ICNUCEVM: SUBSCRIBE firstname lastname 1 Page 10 The user receives the software ASTRA EXEC and a guide manual file through EARN. The ASTRA EXEC has to be received by the user and must be resident in the virtual machine in order to be able to access ASTRA. Note that this EXEC only runs on IBM VM systems. Once the software is received, the user has to simply type the command ASTRA to access the service. After ASTRA is typed, the logo of the ASTRA service appears on the screen. By pressing ENTER, the ASTRA user interface panel appears and the ASTRA session may start. The ASTRA service includes the distribution of a newsletter (a periodic collection of information on the service) to all the members of the ASTRA user group. Any user can subscribe to the Astra User Group by sending the following command to LISTSERV@ICNUCEVM: SUB ASTRA-UG firstname lastname Academic and Research Institutions may submit data about their projects in education and research, provided that the results are of public domain and of interest to the academic world. To submit data, the provider must prepare the bibliographic document or abstract in English, according to the format and rules described in the booklet 'How to submit data to ASTRA', which can be obtained by mail, or directly via EARN by sending the following command to NETSERV@ICNUCEVM: SENDME ASTRA FORM 1 Page 11 ********* * *** * International Intercultural Newsletter * *** * * **** * by Joyce Neu * ***** * * ****** * Pennsylvania State University * *** *** * * *** **** JN0@PSUVM ********* XCULT-L is an international intercultural newsletter written by undergraduate and graduate students at Penn State University who are enrolled in Speech Communication 497B: Cross-cultural Communication. Each week, students write on a topic being discussed in class. Topics range from non-dominant cultures in the U.S. to corporate cultures to the use nonverbal communication in international communication. Participants who receive the newsletter are encouraged to join in the discussions or contribute their own topics and issues. You can subscribe to XCULT-L by sending the following command to LISTSERV@PSUVM: SUB XCULT-L firstname lastname * A Note from the Editor: Joyce sent me some articles from past issues of XCULT-L, which I found extremely interesting. While there isn't enough space here to reprint them all, here at least is one of the more topical ones: A Glimpse into East Germany by Joan Kruhoeffer JBK103@PSUVM Many people assume that the countries of East Germany and West Germany must be quite similar since they were at one time one large country. Through my visits to both West and East Germany, however, I have discovered that the 2 countries are very different from each other. My father lived in East Germany when he was young; prior to our first visit to East Germany in 1985, my father had not been in the East since 1949. We travelled toward his former home on the East German Autobahn, which was paid for by West Germany, and drove to the small town where my father had gone to school. This, and other towns we visited, were surprisingly not "modern" by western standards; according to my father, it was 1 Page 12 as if time had stood still. He said the town looked exactly like it did in the 1930's and 1940's. Missing in East Germany, the most highly-developed East-Bloc country, is the urban sprawl surrounding towns in West Germany and the U.S. (By urban sprawl, I am referring to shopping centers, car dealerships, fast-food restaurants, etc.) I should point out that large cities, such as East Berlin and Neubrandenburg are fairly modern; East Berlin stands out as a beautiful city, but other cities are characterized by drab high-rises which appear to be of lowquality construction. After speaking with some of my father's old neighbors, we noted some large differences between their lives and ours. Many of them were farmers, but sharing a common heritage and language gave us a common bond as we discussed a few things that had happened since World War II. Katrina, a young woman who was about 22 years old, told us that she wanted to be a salesper- son, but she had to become a waitress because that was the only job opening. Her fiancee raised pigs to supplement his official job as a bee-keeper. Katrina was saving money to buy a moped; she told us she would probably not be able to get a car until she was 30 or older. My father and I never told her family that everyone in our family had a car; we felt guilty because of our material possessions in America. Katrina's family seemed to be content with their lives in East Germany, although we have never asked them if they would like to come to the West. Driving away from my father's village, we passed a group of about ten teenagers on bicycles. As we drove by, they cheered and waved at us; our Volvo was obviously from the West, but we are not exactly sure why these young East Germans seemed so happy to see us. Maybe one or two of them has been lucky enough to join the thousands of East Germans who have gone to West Germany through Hungary and Austria in the past few months. If East Germany is the industrial and economic leader of Eastern Europe, then why do so many citizens wish to leave? 1 Page 13 ********* * *** * FTP from BITNET * *** * * **** * by Melinda Varian * ***** * * ****** * Princeton University * *** *** * * *** **** MAINT@PUCC ********* ÕThanks to Murph Sewall for finding this.å Many people who subscribe to mailing lists on the Internet hear the that files are "available for FTP, login ANONYMOUS" from some site or another. Until recently, people on BITNET nodes have been unable to access these files. (The exceptions to this rule are computers which are linked to both networks, for example, YALEVM.) FTP (or File Transfer Protocol) is the Internet method of transferring non-mail files (be they text, formatted data, or programs). People on the Internet can "login" to an FTP server at a remote site and download files. The process is in many ways similar to dialing up a bulletin board with a PC, although it is thankfully much faster. BITNET users can now access these FTP servers through BITFTP. To use BITFTP, send mail containing your FTP commands to "BITFTP@PUCC". The first command to BITFTP must be "FTP" or "HELP". The recommended syntax for FTP requests is: FTP hostname USER username password BITFTP implements a subset of the FTP subcommands provided in the IBM TCP/IP and uses the same syntax. Therefore, you may find it useful to obtain the "IBM TCP/IP for VM Command Reference Manual", IBM order number GC09-1204. The files you request will be sent to you in NETDATA format. You will also receive a mail file containing a log of your FTP session. In that mail file, entries prefixed by ">" are your original commands; those prefixed by ">>" are your commands as interpreted by BITFTP and passed to FTPSERVE; those prefixed by ">>>" are messages from FTPSERVE; and those prefixed by ">>>>" are completion messages from BITFTP. 1 Page 14 If BITFTP is unable to connect to the host you specify, it will send you mail after the first attempt, but will keep trying at intervals over three days. The only additional mail files you will receive will be when the connection is made successfully or when BITFTP gives up after three days. This service is currently under development and is far from complete. Current plans for improvements include: 1. Acknowledgments via MSG when mail is received and when processing has been completed. 2. A much more complete HELP facility. 3. Ability to accept requests in IBM NOTE and PROFS formats. 4. Support for more of the FTP subcommands, such as MGET. * Note from the Editor: There are hundreds of FTP servers in the Internet. You can get a list of them by sending the following command to LISTSERV@MARIST: SENDME BITNET FTPLIST 1 Page 15 ********* * * Headlines * ***** * *** * edited by Christopher Condon * *** * * *** * Yale University ***** * * * Send your Headlines to BITLIB@YALEVM ********* * CYBSERV Moved (thanks to Ferhat Djavidan): "CYBSERV at ACADIA has been changed to CYBSERV at TRBOUN. CYBSERV@ACADIA will be closed down. It is now sending notification to each request and soon it will not answer to any requests." * BITNET Technical Meeting (from Jim Conklin): "Going to DECUS in Anaheim? Join the professional BITNET volunteers who make the network work, at the pre-DECUS BITNET Technical Meeting on November 4. Fly in on Friday and get the weekend reduced airfare; share your ideas about BITNET with the others at the Technical Meeting. Details to be announced as they are worked out, on the list BITTECH@BITNIC. Subscribe by sending a message to LISTSERV@BITNIC with the command: SUBscribe BITTECH your_name" * More TRICKLEs (from Otto Stolz): Two more trickle software archive servers have been set up: Another in Germany (TRICKLE@DTUZDV1) and one in Spain (TRICKLE@EB0UB011). * Another VMSSERV (from J. James Belonis): "I have started VMSSERV@UWAPHAST to make available my XMODEM for VMS program. I expect to add a few other utilities in the next few months." * QNAMES (from Michel Daulie): "QNAMES@BANUFS11 (University of Antwerp) provides organizational information about UFSIA as well as info about mail and file paths to our users. Commands are provided for information retrieval of organizational data, locating users with exact keyword match or phonetic search; as well as the posibility to do organizational tree walk-through if the commands arrive within a certain time span. Commands in both English and Dutch are accepted. For the moment only MESSAGE access is provided." 1 Page 16 ********* * * New Mailing Lists * ***** * *** * edited by Christopher Condon * *** * * *** * Yale University ***** * * * Send new list descriptions to NEW-LIST@NDSUVM1 ********* Each of the lists described here is maintained on a LISTSERV machine unless otherwise noted. To subscribe to one of these lists you would send the following command to the the appropriate server via mail or message. SUBSCRIBE listname Your_full_name For example, if your name is Kristen Shaw and you want to subscribe to a list described as "DIAPERS@YALEVM" you would send the following command to LISTSERV@YALEVM: SUBSCRIBE DIAPERS Kristen Shaw To make contributions to the list you would send mail to DIAPERS@YALEVM. Please note that this is just and example and to my knowledge there are no mailing lists about diapers (although you never know). ***** QUAKE-L@NDSUVM1 - Earthquake News / Discussion After hearing about the earthquake in the San Francisco, California area this evening I have been wondering if there are ways the various national and international computer networks can help or the help can be enhanced. Perhaps this is best carried out privately or via other means. But if people want to discuss this I am willing to provide a list for that. Of course one of the basic problems discussed might be network reconfigurations which would be temporarily required. Others might be in actually putting various groups in electronic contact with each other. I realize this may be a list without any use, but I wanted to make the facility available in the event the need arises. I am sure folks in the area of the earthquake have very pressing needs on their mind right now like trying to gather their families. If there are ways those of us outside the area can help I am sure we would like to do what we can. - Marty Hoag 1 Page 17 CHESS-L@GREARN - Chess discussion The purpose of the list is to offer to chess players inside the network, a way to communicate, share ideas and participate in tournaments which can be organised through this list. LACROS-L@VILLVM - Lacrosse List I ÕAlec Plotkin-Manager of Villanova Lacrosseå am starting a Men's Lacrosse Information List. I will post information such as scores and standings as I receive them. Also any discussion about Lacrosse is encouraged. I will try to bring up topics of interest: new rules or coaching changes or anything else which effects the Lacrosse world. I-FINGER@SPCVXA - Finger Utility Discussions Discussion of the Finger program and related utilities. Finger is a utility which performs username lookup, WHOIS functions, and system status functions. This list is hosted on the system where VMS Finger and RSTS/E Finger are maintained, so initial discussions will probably center around these versions. However, discussions about any Finger variant or similar utilities are welcomed. EDI-L@UCCVMA - Electronic Data Interchange Issues Discussion of electronic transmission and receipt of business documentation including purchase orders, invoices, payment, academic transcripts, standardized test scores. ANSI X12 and international EDIFACT standards. CONFOCAL@UBVM - Confocal Microscopy We would appreciate the announcement of our new list CONFOCAL which is a discussion group dealing with all aspects of confocal microscopy and confocal microscope design. DB2-L@AUVM - DB2 Data Base Discussion List This list is intended to serve those interested in discussions of IBM's DB2 Data Base Product and any associated topics such as SQL and QMF. Archives of DB2-L back issues can be listed by sending the command INDEX DB2-L to LISTSERV@AUVM. 1 Page 18 CASE-L@UCCVMA - Computer Aided Software Engineering Discussion of use of computer techniques in the systems development life cycle. Includes use of computers to aid in system analysis and design, description (including graphical representation of functions), coding, and documentation. Emphasis is on *practical* applications, especially those of value to commercial firms and administrative type computer facilities. CSP-L@TREAN - Cross System Product A new list about CSP (Cross System Product) has been created. Its aim is to discuss the problems about the maintenance, installation and administration of CSP. It is not a User Group. Mostly technical issues will be discussed. To be added to the list please send a request to the owner, Esra Delen (ESRA@TREAN). SLART-L@PSUVM - Second Languages SLART-L is a list for those involved in or interested in second or foreign language acquisition research and/or teaching (SLART). This list is intended as a means of forming a "community of scholars" in SLA. Individuals may choose to discuss research in progress, "publish" papers for feedback, solicit advice on teaching methods, etc. Anyone interested in issues in second or foreign language acquisition is encouraged to join. INFO-GCG@UTORONTO - Genetics Computer Group This list covers topics in computer aided molecular biology and is of particular interest to users and managers of the "Genetics Computer Group" software from the Unviversity of Wisconsin. DBASE-L@TECMTYVM - The dBase Language DBASE-L is a list dedicated to the use of the dBase language for manipulating databases. Emphasis will be given on comments of how to build and maintain working systems using any of the dialects of these languages (Clipper, Fox, dbase II, III, IV, etc). 1 Page 19 Users of the list are encouraged to participate on topics such as: transaction processing, system implementation on networks, concurrency, library construction, modular design, function design, etc. All the above topics will be treated under the light of the dBase language. So the focus will be on implementing algorithms using this language. MINISTRY-L@GACVAX1 - Entering the Ministry An open forum for the discussion of concerns and experiences of people who are planning a career in religious ministry, or for those considering such a move. All denominations are welcome (at least!), and a variety of personal backgrounds would probably be helpful. What is intended here, if it will work, is a discussion the issues one faces as one apporaches the question of the ministry as a career. To subscribe to MINISTRY-L, send the following command to MAILSERV@GACVAX1 via mail text or interactive message: SUBSCRIBE MINISTRY-L Your_full_name 1 Page 20 ********* * * Helpdesk - a Question and Answer Column * ***** * *** * by Murph Sewall * *** * * *** * University of Connecticut ***** * * * SEWALL@UCONNVM ********* Send your questions to BITLIB@YALEVM! *Q* Can one get to and from FIDONET from bitnet? If yes, how? *A* ÕChriså It is sometimes possible, but not probable. Look in the September, 1988 issue of NetMonth for details. *Q* USENET: how does one access this, or subscribe (whichever term applies...)? *A* ÕMurphå USENET is the Unix User's network, based upon the UUCP (Unix to Unix Copy) file transfer system distributed with Unix version 7. It is commonly referred to as the UUCP network after the transport protocol. USENET came into being in late 1979 when two Duke University grad students in North Carolina thought of hooking computers together to exchange information with the Unix community. There are now about 11,000 nodes worldwide. USENET interest groups are an integral part of the USENET distritution service. It is NOT possible to access groups that are not gateway'd to Internet or LISTSERV groups *unless* your system administrator arranges to carry USENET on your system (not easy to do on a host running an operating system other than UNIX, but not impossible). *Q* I was absolutly delighted to hear in NetMonth that it was possible to send mail to MCI from a BITNET node. So I promptly set off to do so. To my dismay I received a reply from XB.DAS@TANFORD that this was a 'for-fee' service and that my BITNET node was not a DASNET subsriber. So much for a MCI gateway. *A* ÕMore on MCI from Murph Sewall and June Geniså: It turns out that there is gateway to MCI other than the DASnet one. David K. Ely wrote the following explanation: 1 Page 21 The InternetMCI Mail Gateway is an experimental mail system being developed by the Corporation for National Research Initiatives (NRI), a non-profit research organization. NRI is currently researching interconnecting various mail services. Currently, there is no charge for sending mail from the Internet to MCI Mail. In order to send mail to users on MCI Mail, use one of the following addresses: accountname@mcimail.com ci_id@mcimail.com full_user_name@mcimail.com For instance, I have a mailbox on MCI Mail. You could send mail to me via either dely@mcimail.com or 379-3286@mcimail.com or David_Ely@mcimail.com. Users on MCI Mail can also send messages to the Internet. At the "Command:" prompt, type "create . Then the user performs the following: (NOTE the "TO:", "EMS:" and "MBX:" strings are prompts provided by MCI Mail. Command: create TO: David K. Ely (EMS) EMS: INTERNET MBX: dely@NRI.Reston.VA.US This address is translated to: "David K. Ely" by the Gateway. Mail sent from MCI Mail to the Internet is charged by MCI Mail. One final note: Feel free to use the gateway as often as you'd like, but be forewarned: The gateway is still not considered fully operational; sometimes mail will be delayed (usually less than 24 hours.) *Q* I read your Helpdesk column in this month's NetMonth and found it most interesting and helpful. I have 2 questions for you if you please. 1. You explained how you get a list of locations on the UUCPnet. (by sending messages to LISTSERV@BITNIC requesting files such as uucp.usakentu for a list of those hosts in Kencucky, USA.) My question is where you can find locations of 'nodes' on other networks such as ARPA, COM, MIT, EDU etc. 2. Is there a way to get a list of users & locations on these other nets such as the one you mentioned here on BITNET at Listserv@marist (via the WHOIS command) 1 Page 22 *A* ÕChriså You can get lists of nodes in other networks by requesting sitelist files from NETSERV@BITNIC. If you request the file NETWORKS FILELIST, you will find sitelists and information on most of the networks to which you can send mail. *Q* How you can see I am on UUCP and I have problems on receiving mail from LISTSERV@BITNIC or LISTSERV@MARIST (and I think that from other listservers too). *A* ÕMurphå LISTSERV doesn't like UUCP very much, particularly when 'from' lines arrive with non-existant domains in the address. REPLY from BITNET mailers won't work, and the UUCP maps don't recognize fcaglp (psuvax1 does know dcfcen however). *Q* Another question, what are MX and A records ? What means 'fubar' or 'foo-bar'? *A* ÕMurphå An 'A' record contains informmation about a host that is connected directly to the Internet. An 'MX' record identifies the Mail eXchanger (the Internet host which forwards mail) for a host that has a domain style address, but is NOT part on the Internet). FUBAR (pronounced foo-bar) is Fouled (or less socially acceptable expletive) Up Beyond All Repair (see SNAFU - Situation Normal; All F***ed Up). 1 Page 23 ********* * * Feedback - a letters column * ***** * *** * edited by Christopher Condon * *** * * *** * Yale University ***** * * * Send your letters to BITLIB@YALEVM ********* From: Hank Nussbacher Subject: User Directory Servers From: Pierre Wauters Subject: Are User Directory Servers useful? There seem to be so many user directory servers that they become useless since you have to know where the person you're looking for has registered (if he has). Or am I wrong? Couldn't you discuss this topic in a future netmonth and tell the people where and how they should register first? We should also agree on some sort of standard format for the entries. Isn't it possible to build a list of basic keywords the people would choose from? I know, I know. It not so easy! In general, all the people writing directory servers have stopped writing and are waiting to see the outcome of X.500. As you have pointed out, there are no standards currently and things take on a haphazard nature. Part of the ISO and OSI initiative is to establish X.500 "White Pages" directories that will resolve all the problems you raised and more (such as how do entries "age" and are later deleted, how are entries owned especially when my id can change as quickly as my computer center migrates me to another Sun, etc.). Various places are working on X.500 implementations but it will require some patience before users get to see the results of the work. Also consider the fact that the OSI committees have not finished drafting the X.500 standard and you begin to see why things are as they are today. If you are interested in reading more on X.500 you should pick up DIS 9594 (parts 1-7) "Information Processing Systems - Open Systems Interconnection - The Directory". 1 Page 24 From: Damon K. Subject: WOWWWWW! A new net merges with BITNET! But exactly how will this benefit me?? Of course it may eliminate puting an extra domain specification (like, I do it regularly--heh!) but all it does for myself is speculate what is in THAT net. I have a hard time figuring out what's in BITNET! Let's hope these persons will at least let us know what they have. From: Barry Floyd Subject: CREN I recently finished reading the latest NETMONTH (8909), which prompted a couple of thoughts. While most everyone may agree that the merger of BITNET and CSNET is going to be a positive event I believe the chosen acronym "CREN" leaves a lot to be desired. Unfortunately the only alternative that I could come up with was "CRED- NET". (I tend to favor including the abbreviation "NET" in names referring to networks.) As to the non-standard name servers in use on BITNET, I don't believe that in the near term we will see one software package or even standard protocol which addresses all of the various user directory concerns. However, given the current manner of usage it seems technically feasible to programmatically gather all of the existing directory information and store it under a LISTSERV or series of regional LISTSERVS. As mentioned in the 8909 NetMonth, there are legal issues to contend with - What are these? Minimally I suspect that all subscribers to public lists have no legal recourse if their "name" and e-mail address are included in a master list. Think of the multimillion dollar industry based on buying, selling and maintaining US-mailing lists - would not the same lack of severe limitations apply to E-mailing lists? From: William Wisner Subject: Satellites Not *all* BITNET links are terrestrial. The U of Alaska uses a satellite link to Seattle to get to the world. (We are in an, ah, somewhat unique situation here, though..) 1 Page 25 From: Richard A. Schafer Subject: BITSERVE I couldn't help responding to the letter from Pierre Wauters in the most recent NETMONTH, where he referred to BITSERVE@CUNYVM. BITSERVE has been dead (at least as far as adding new articles) for at least 2 or 3 years now, and *no one* should bother accessing it any longer. * You're right, of course. I should have mentioned that. From: Peter Coleman Subject: New name for NetMonth How about "CREN DE MONTH"? Of course you need a green monitor to view it! * Congratulations! Yours was the best (if only) entry. You win! From: Subject: Your article on Relay. Gee, I didn't know relay was so exciting. It must be your dazzling wit and conversation. * Actually, its my sparkling personality and good looks. From: Robert Skegg Subject: Relay I am sending you a copy this mail which I sent to the RELAY User's list because I mention your Bitnotes column. Whilst I stand by the comments I make, I would like to assure you that in general I think the NetMonth publication is fine, and I wish there was more of 'the good stuff'. It's a pity about the timing of the article in question. To: RELUSR-L Dave Phillips posted in a recent message: As typical relay convos are now page 1 (well, maybe page 2) in NetMonth, we can bet that there's some other net administrator wondering *why* bother with resources for relay at his/her node. Why push the administrator to the conclusion that relay usage is not only vacuous but harmful, when it's usually just the former? 1 Page 26 I was surprised that Chris Condon put the article "A Tourists Guide To BITNET" in his column in NetMonth. While it might be faintly amusing to regular Relay users, its impression on that 'net administrator' may well make him wonder! It is my opinion that such articles are more suitable for 'The National Enquirer.' Seriously though - the reason for the existence of the RELAY network is still valid: To provide a more efficient mechanism for transporting personal interactive messages. Right now that mechanism DOES NOT EXIST between Canada and the USA. One might WRONGLY suppose that this results in the reduction of such traffic. Be assured - it does not! Canadian RELAY users are far to used to RELAY outages, they (we) all know how to 'send direct' to all the people they would otherwise talk to through the efficiency of RELAY. The result, of course, is an increased message load. From: J. Martin Wehlou Subject: CompuServe gateway Your latest example for sending email from CIS into bitnet is correct: >INTERNET:CONDON%YALEVM.BITNET@CUNYVM.CUNY.EDU but the same can actually be accomplished in a shorter form: >INTERNET:CONDON@YALEVM.BITNET This second form works just as well. Reason to do this: the first form is too long to fit into the user id field in TapCis, one of the most popular comms programs for CIS. The second form fits, making life easier for CIS folks that want to regularly send us bitnet folks a message. 1 Page 27 ********* * * NetMonth Policies * ***** * *** * Everything you ever wanted to know... * *** * * *** * ...but were afraid to ask. ***** * * * BITLIB@YALEVM ********* NetMonth is a network service publication distributed free of charge to students and professionals in BITNET and other networks. This magazine and its companion file, BITNET SERVERS, are the work of the BITNET Services Library (BSL) staff and contributors from around the network. BITNET SERVERS is BITNETs list of servers and services. If you know of servers not listed in BITNET SERVERS, or if some listed are no longer available, please contact the NetMonth Editor. * Subscribing to NetMonth and BITNET SERVERS: Send the following command to LISTSERV@MARIST by mail or messgage: SUBSCRIBE NETMONTH Your_full_name A subscriber can delete him/herself from the mailing list by sending LISTSERV@MARIST the command: UNSUB NETMONTH Internet users may use these methods, but must address the mail to LISTSERV@MARIST.BITNET * Back issues: BITNET users may get NetMonth back issues from the file server LISTSERV@CMUCCVMA. For a list of files, send the server the the command: INDEX NETMONTH * Letters to the Editor: If you have questions or comments about BITNET or NetMonth that you would like to see printed here, mail your letter to BITLIB@YALEVM. Make sure that you specify in the "Subject:" header or somewhere in the letter that it is for the NetMonth letters column. 1 Page 28 * Article Submissions: The only requirements for NetMonth articles and columns are that they be informative, interesting, and concern some BITNET-related topic. Send your articles and to BITLIB@YALEVM. * Printing this file: VM users can print this file by using the "( CC" option of the PRINT command. VAX/VMS users should RECEIVE NetMonth with a format of FORTRAN. John McMahon of the NASA Goddard Space Flight Center has written a program or VAX/VMS users which changes Fortran form feeds in an issue of NETMONTH to ASCII form feeds. This allows a user on a VAX/VMS system to RECEIVE a copy of NETMONTH, reformat it using this procedure, and print it using the standard VMS PRINT command. The program is internally documented, and you can get a copy by sending the following command to LISTSERV@CMUCCVMA or MARIST: SENDME NETMONTH COM _ __- __--- The __----- BITNET __------- Services ___________ Library "Because We're Here." ***************************************************************