From: HENRY::IN%"RCONN%SIMTEL20.ARPA%relay.cs.net@rca.com" 6-SEP-1986 20:47 To: EVERHART%ARISIA%rca.com@CSNET-RELAY.ARPA Subj: Welcome to the Ada Software Repository WELCOME TO THE ADA SOFTWARE REPOSITORY ON SIMTEL20 You are now on the ADA-SW mailing list, through which users of the Ada Software Repository (ASR) communicate with each other. This is your Welcome to the Ada Software Repository, and a copy of this message is kept in PD:WELCOME.DOC if you want to see it again or copy it for other uses. Feel free to distribute this message and any other files in PD: that you wish to take. You may publish these files (in PD:) in any newsletter or commercial publication you desire without restriction. This message contains the following files: FILE CONTENTS PD:ADAREPOS.DOC Overview of Repository PD:AAREAD.ME Pointers to Answers to Common Questions PD:OPERATE.DOC Statement of Operation PD:FTP.DOC How to Use FTP and Other Info PD:MLIST.DOC About the ADA-SW Mailing List PD:FINDME.DOC How to Find Things PD:DIRLIST.DOC Summary of ADA Directories PD:TAPEDIST.DOC Acquiring Magtape of Repository PD:UUCPBIT.DOC For non-DDN-resident users PD:NEWSLTR.DOC About the ASR Newsletter PD:INDEX.DOC About the ASR Master Index This Repository has been set up for YOU, and I heartily encourage your interaction, comments, questions, and support. If you like it, use it, and find it to be of value, it has succeeded in its purpose. If there is something about it that you don't like, use the ADA-SW mailing list to let all the users know or send a message to ADA-SW-REQUEST@SIMTEL20 if you want to address the maintainer of the repository directly. Welcome to the Ada Software Repository on SIMTEL20! Richard Conn ----> ADAREPOS.DOC <---- The Ada Software Repository (ASR) on SIMTEL20 A repository of Ada programs, software components, and educational material has been established on the SIMTEL20 host computer on the Defense Data Network. This repository has been accessible to any host computer on the network since November 26, 1984. This repository provides a free source for Ada programs and information. By employing the File Transfer Protocol (FTP) program, users of DDN hosts are able to scan the directories of the repository and transfer files to their hosts. If the files are Ada programs, they may then compile these programs and use them as they desire. Modifying these programs may be within their rights, and they may freely distribute these programs within and without the DoD as they desire, subject to the restrictions specified for each piece of software in its prologue. The Ada Software Repository is divided into several subdirectories. These directories are organized by topic, and their names and a brief overview of their topics are contained in the file DIRLIST.DOC in PD:. The Ada Software Repository on SIMTEL20 serves two basic roles: to promote the exchange and use (reusability) of Ada programs and tools (including components) and to promote Ada education (especially by providing several working examples of programs in source form for people to study and modify). All members of the Ada community are encouraged to freely extract information and programs from the repository as well as make contributions to it. The only restrictions which apply to the access and use of this software are presented in the "Distribution and Copyright" section of the prologue associated with each piece of software. ----> AAREAD.ME <---- COMMONLY ASKED QUESTIONS AND WHERE TO FIND THE ANSWERS SUBJECT: ADA SOFTWARE REPOSITORY ON SIMTEL20 The following is a collection of questions and the names of files which contain complete or partial answers to these questions. Unless otherwise noted, these files are contained in PD:. QUESTION FILES 1. What is the Ada Repository on SIMTEL20? ADAREPOS.DOC, AAREAD.ME WELCOME.PRO 2. How do I Access the Ada Repository? FTP.DOC, UUCPBIT.DOC TAPEDIST.DOC 3. How do I Find Out What is in the Ada Repository? FINDME.DOC, MLIST.DOC DIRLIST.DOC, NEWSLTR.DOC INDEX.DOC 4. How do I Submit Software and other Items to the Ada Repository? How do I Modify and Resubmit Software that is already in the Ada Repository? SUBMIT.DOC, CHECKOUT.DOC 5. How do I Contact the Repository Maintainer and other Users of the Repository? MLIST.DOC 6. How do I get Started with Using the Ada Repository? WELCOME.DOC, MLIST.DOC INDEX.DOC 7. How do I Contact the Authors of Software in the Ada Repository? PROLOGUE.DOC, SUBMIT.DOC ----> OPERATE.DOC <---- Statement of Operation - Ada Software Repository The Ada Software Repository on SIMTEL20 and the tape copy service are unfunded activities and have been so since Richard Conn proposed the idea to Frank Wancho in November, 1984. The disk drive on which the repository is sharing space with other collections is funded by the Logistics System Support Activity (LSSA), an Army Materiel Command (AMC, formerly DARCOM) activity. LSSA provided the funds for the disk drive to support the UNIX/C collection for the AMC community, which, because of the availability via ANONYMOUS FTP on DDN, is available to the entire DDN community. The Ada Software Repository resides on SIMTEL20 because there happens to be space available on that disk drive. SIMTEL20 is owned and operated by the Computer Systems Directorate at White Sands Missile Range in New Mexico, which is an Installation/Field Operating Activity (I/FOA) under the Test and Evaluation Command (TECOM) at Aberdeen Proving Ground in Maryland. TECOM is, in turn, a major subordinate command under AMC. AMC is a major command under the Department of the Army. Richard Conn is the maintainer/operator of the Ada Software Repository and also maintains the ADA-SW electronic mailing list. Frank Wancho is the sponsor of the Ada Software Repository and runs the tape distribution service. Both Richard and Frank work on a voluntary, unfunded basis. The Ada Software Repository is not associated with the Ada Joint Program Office. All software, documentation, and other items of information in the Ada Software Repository are in the public domain. ----> FTP.DOC <---- THE SIMTEL20 ARCHIVES SIGNIFICANT CHANGES New MSDOS archive added: SIMTEL20 now has a new archive, PD:. This archive, like the PD: archive, contains software for the MSDOS and PCDOS operating systems. But unlike PC- BLUE, this archive is locally managed, and will be updated more often (the PC-BLUE archive is updated only when new disks are issued by the PC-BLUE Users Group). For a list of files, get a copy of the directory file, PD:MSDOS.CRCLST. Newsgroup correspondence archive files moved: Newsgroup correspondence archives have been moved from directory PS: to individual directories having names of the form PS:, where "KEYWORD" has been chosen to indicate the associated newsgroup. See the section entitled "NEWSGROUP CORRESPONDENCE ARCHIVES" for additional details. Public domain archive files moved: A new large disk device called PD: has been installed to house the entire public domain software collection. All files are now accessible using file specifications of the form: PD:file_name Example: PD:LU310.COM New logical names: Files in the archive can also be specified with a new shortened notation using a logical name for each directory. Thus, the file in the above example can also be specified as: STARTER-KIT:LU310.COM Note that the part of the directory name following the dot has been used as the logical name (followed by a colon). But remember, this new form of file specification applies only to the archive. To avoid confusion, all examples in the text to follow will use the PD: specification, as this form works with ALL of the archives. Getting started: The above example provides a sneaky introduction to yet another new feature that should greatly ease the "bootstrap phase" for new archive users. Now in one place, PD:, you will find all of the basic essentials needed to begin using the archives. These programs provide the means for transferring, unsqueezing and de-librarying archive files, and more will be said about them later in this document. Special kudos to archive maintainer Keith Petersen for this worthwhile addition. Finally, a reminder: For quite some time now, "ITS binary format" has not been used for storage of binary files in the SIMTEL20 archives. If you are a new user of the archives and you don't know what ITS binary format is, don't worry about it; it no longer matters. But apparently, some "veteran archive users" are still unaware of the change. Therefore, please note that stripping the first four bytes of binary files, once necessary for removal of the special "ITS header", is no longer required. Indeed, if you do this now, YOU WILL DESTROY THE FILES. OVERVIEW There is a collossal amount of free public domain software for the CP/M, PCDOS/MSDOS and UNIX operating systems, and for the DoD standard programming language, Ada, in several archives on SIMTEL20.ARPA, a DECsystem-20 running the TOPS-20 operating system at White Sands Missile Range. Archives of correspondence for several newsgroups, including INFO-CPM, are also available. You can obtain these files using the InterNet file transfer protocol, FTP (described in a following paragraph), with user-name "anonymous". For a login password, use your host-name or any other string of printing characters. Throughout this message, FTP examples are given in a GENERIC syntax. You will have to consult either local documentation or your friendly system wizard to learn the actual syntax used with your local mainframe operating system. For the sake of brevity, the domain suffix ".ARPA" will be dropped from further references to SIMTEL20 in this discussion. To obtain directory listings, connect to SIMTEL20 via FTP and do this: get pd:cpm.crclst get pd:cpmug.crclst get pd:sigm.crclst get pd:pc-blue.crclst get pd:msdos.crclst get pd:unix.crclst get pd:ada.crclst The archive is the one to watch for the very latest CP/M offerings, as it is updated frequently. The , and archives contain software distributed by the CP/M Users Group, the SIG/M Users Group and the PC-Blue Users Group respectively. This software is available on diskettes from the associated users groups, and the archives are updated as new volumes are issued. The archive contains software for the IBM-PC and similar machines. Some runs under CP/M, and some under PCDOS/MSDOS. The archive also contains software for the MSDOS and PCDOS operating systems; but this archive is locally managed, and therefore is updated more frequently than the archive. The archive contains a variety of UNIX tools. Those which apply specifically to CP/M are in the directory . The archive is growing rapidly. Information about this archive is in directory PD:. In general, the archived software is very good, having been worked-over and refined by many users. The documentation and comments tend to be complete and informative. Files in all of these archives can be obtained using the FTP procedures described in this message. But please note that due to the large number of files available, the archive maintainers cannot possibly attempt to validate the proper operation of the various programs. When a program bug is reported, immediate action is taken to either correct the error or remove the offending program from the archives. Still, users must understand that all archive programs are offered AS IS, and the archive maintainers specifically disclaim any liability should these programs malfunction or cause damage, incidental or otherwise. When testing ANY new software, be certain that all information stored on disk is backed-up before you start, so that you can recover if files are damaged or erased. This is particularly true if you have a hard disk, in which case malfunctions can be spectacularly disasterous. FILE TYPES Files are stored in two formats: Text files such as those with names that end with DOC, HEX, INF and ASM are sometimes stored as ASCII files, but usually these files are stored in binary squeezed form. Binary storage is also used for executable (COM) and library files. Squeezed and library files are described below. All binary data are stored as four 8-bit bytes per 36-bit SIMTEL20 word, with the low-order four bits of each word filled with zeros. If such a file is interpreted as a contiguous string, as will happen if a straight binary transfer is made to a 16 or 32-bit UNIX machine, the four zero filler-bits per 36-bit group will cause rather bizarre and frustrating results. The methods for dealing with this situation, which differ from machine to machine, are explained in a following paragraph. Squeezed files have been compressed using programs available in directory to obtain an approximate 35-percent size reduction. These files can be identified by the letter Q in the extension field. For example, the file PD:RMACPAT.AQM is a squeezed file. It must be transferred as a binary file, and then unsqueezed. The unsqueezing can be done on a CP/M system using USQ- xx.COM (where "xx" is the current version) from directory , or there are several host-based unsqueezers in the and archives (see for example, directories and ). CP/M library files (those with names ending in LBR) combine several regular CP/M files into a single BINARY file which contains an internal directory of its contents. They are created using the CP/M library utility LUxxx.COM (where "xxx" is the current version) or some other compatible utility. The complete packages for LUxxx and a newer compatible program called NULUxx (where "xx" is the version) can be found in directory PD:. C-language source code for a compatible UNIX utility called LAR (library archiver) is in directory PD:. Although the type of storage used for a particular file can usually be inferred from the file-name, this is not always true. It is a good idea to check the appropriate "crclst" file to ascertain the storage format used for each file of interest. Now, and for the foreseeable future, storage formats for files in the , and archives can be determined from their "generation numbers", as shown by the FTP directory command. For example, the FTP command: dir pd: will yield results of the form: -CATALOG.001.2 ABSTRACT.001.2 BW.ASM.2 BW.BAS.1 BW.EXE.1 COLOR.ASM.2 COLOR.BAS.1 COLOR.EXE.1 ...and so on All files with names ending in ".1" are stored in binary format, and those with names ending in ".2" are stored in ASCII. This relationship will continue to apply for files in the , and archives until further notice. WARNING: Because the public domain archives on SIMTEL20 consume a huge amount of disk-space, storage capacity will be conserved by the greatest practical use of libraries and squeezed files, both of which are stored in binary format. If you cannot properly transfer binary files, you are going to be VERY FRUSTRATED! If you need help, please contact your local system wizard and provide him/her with a copy of this message. Having done that, if you are still unable to make things work correctly, send a message to INFO-CPM- REQUEST at AMSAA.ARPA and I will try to help you. Please provide the following information: 1. Machine and operating system (e.g., VAX-11/780, 4.2 BSD UNIX) 2. Network software in use (e.g., 3-Com UNET) 3. Complete list of available FTP commands (e.g., GET, PUT, etc.) Important files in the and archives are the CATALOG files. These files, which are stored in ASCII, contain the "- CATALOG.nnn" files from all the volumes of their respective archives. To obtain these composite catalog files, connect to SIMTEL20 via FTP and do this: get pd:cpmug.cat get pd:pcblue.cat A similar file exists for the archive, but it is stored in squeezed form. This file, when unsqueezed, yields SIG.CAT (the catalog). It can be obtained using the FTP command: get pd:sig.cqt (NOTE: That's "L-and-three-zeros" in "vol000") FILE TRANSFER VIA FTP FTP stands for File Transfer Protocol, a formalized procedure for moving files among machines on the Defense Data Network (DDN) and other networks that connect with the DDN. The protocol is implemented by a program often called FTP. The different mainframe operating systems implement FTP with variations in command syntax. Some systems have the remote-file-name precede the local- file-name in the command. Others reverse this order. Some versions have the whole command on a single input line, while others use multiple lines. Read the documentation for your local system, or consult a friendly system wizard for the details of your local FTP command syntax. UNIX users can do something like "man ftp" for on-line instructions. However, not all UNIX FTP programs are called "ftp", so you may have to snoop around in the system directories or ask a system wizard for the correct local name to use with the "man" command. ITS users can do ":INFO FTP", and "HELP FTP" works on TOPS-20 and some other operating systems. I will be happy to update this message with pointers to other sources of on-line documentation if they are sent to INFO-CPM-REQUEST@AMSAA.ARPA. FTP transfers from SIMTEL20 can be made with user-name "anonymous". Use your host-name or any other string of printing characters for a password. For anonymous logins, SIMTEL20 supports the FTP "change working directory" command. (Your local syntax may be something like CD, or CWD.) Ignore the message that prompts you to enter a password. This command allows you to specify a default SIMTEL20 directory to be used for all file retrievals, and thereby relieves you from having to repeatedly type "pd:" as part of each filename. For example, you can do something like this: cd pd: get filename-1 get filename-2 ...and so on instead of using the longer filename forms shown in previous examples. Users of TOPS-10, TENEX, TOPS-20 or ITS systems can use "image" or "paged" mode for ALL transfers. UNIX users must use "ascii" mode for ASCII files, and "tenex" or "type L 8" mode for binary files. MULTICS users can use "ascii" mode for ASCII files, but binary files require special treatment that is best described by the following example provided by Paul Schauble : !ftp simtel20 220 SIMTEL20.ARPA FTP Server Process 5Z(14)-7 at Mon 10-Sep-84 00:27-MDT user_ftp: !login anonymous 331 ANONYMOUS user ok, send real ident as password. Password: !guest user_ftp: !quote "type l 8" <--(NOTE: That's lowercase "L" 8.) 200 Type L bytesize 8 ok. user_ftp: !get micro:alias.hlp alias.hlp 150 Retrieve of MICRO:ALIAS.HLP.1 started. 226 Transfer completed. Total elapsed time: 35.7 seconds. 4348 bytes transferred in 18.5 seconds (1850 bits/sec). user_ftp: !quit 221 QUIT command received. Goodbye. Lines beginning with "!" are typed by the terminal user. The received files are stored on MULTICS with one 8-bit byte per 9-bit word, and can be trans- ferred to a microcomputer with Kermit (described in a following paragraph). All aspects of the FTP process for UNIX machines have been automated to a high degree by a program in directory PD:. With this program, a simple command like "mb modm700.com" can connect to SIMTEL20 and transfer the binary file "modm700.com" from directory PD: to a local file also named "modm700.com", all with no user intervention. Batch command files containing multiple lines of the form in the above example can be run in no-hangup background mode to transfer whole directories without the user even remaining logged- in on his local system. For more information, get the file PD:AUTOFTP.DOC. PROGRAMS FOR FILE TRANSFER BETWEEN MAINFRAMES AND MICROS Christensen Protocol Mainframe Programs: For a micro to reliably exchange files with a mainframe, cooperating file transfer programs with automatic error detection and retransmission of faulty blocks must be running on both computers. One such family of programs uses a popular protocol created by Ward Christensen and enhanced by others. Directory PD: contains two programs, UC and the older UMODEM (both written in C), which implement this protocol on UNIX machines. See the file PD:UNIX.CRCLST for a list of other useful UNIX utilities. On ITS machines, file transfer using the Christensen protocol can be done using MMODEM (type :MMODEM for instructions), or LMODEM. Documentation for LMODEM is in file .INFO.;LMODEM HELP. Other useful ITS utilities include: TYPE8 - types an ASCII file stored in ITS binary format. TYPESQ - types an ITS binary format "squeezed" file (see the first paragraph under FILE TYPES). USQ - creates an unsqueezed version of a squeezed file. HEXIFY - creates an Intel hex format file from an ITS binary format COM file. COMIFY - creates a COM file from an Intel hex file. CRC - computes the Cyclic Redundancy Check value for a file, using the same algorithm that is used by the CP/M program CRCK. Brief instructions for any of these utilities except LMODEM can be obtained by typing ":utility_name" (for example, :CRC). The ITS utilities listed above are also available for use with TOPS-20, but since ITS binary format is no longer being used for the SIMTEL20 archives, these utilities have been converted to work with TOPS-20 binary formats. A collection of TOPS-20 utilities for transferring and manipulating files can be found in directory PD:. See PD:CPM.CRCLST for a list of available programs. File transfer and conversion utilities for use with VAX/VMS machines are contained in directory PD:. See CPM.CRCLST for details. Christensen Protocol Microcomputer Programs: An excellent program for transferring files between micros, or between micros and mainframes is called MODM7xx, where the "xx" is replaced with two digits to give the current version number. This program, often referred to as MODEM7 (the name of its easier to pronounce ancestor), uses the popular Christensen protocol to transfer files with automatic error detection and retransmission of erroneous blocks. To get started with MODM7xx, you should first FTP and examine the "DOC" and "MSG" files from the binary library file PD:MODM7xx.LBR. The "DOC" and "MSG" files are actually stored in the library in squeezed form, so you will have to perform three steps to get them: 1. FTP the binary library file. 2. Extract the elements having filename extensions of "DQC" and "MQG". If you have no facilities for doing this on your mainframe host (see the earlier comments on mainframe-based library utilities), then you will have to transfer the library to a microcomputer and extract the necessary elements there. If this requirement seems to put you in a "Catch-22" situation because you have no facilities for mainfrome-to- microcomputer transfers, there is a way out; read the "Getting Started" section which follows|. 3. Use an "unsqueezer" (described above) to convert the "DQC" and "MQG" files extracted from the library into "DOC" and "MSG" files. As in the case of the library extractions, unsqueezing can be done on either a mainfrome host or a microcomputer, depending on your circumstances. Together, these files will tell you just about all there is to know about getting MODM7xx to run on your machine. Take the time to read them; they're quite informative. You will also get some helpful insights from reading some of the overlay files. These overlays, described in file PD: M7OVL-yy.LST, are used to customize MODM7xx for particular machines without having to edit and assemble the huge MODM7xx source file. Complete instructions for performing this procedure are contained in each overlay file. The letters "yy" in the above filename should be replaced with two digits giving the current version number as determined from CPM.CRCLST. And then, there is MEX. MEX stands for "modem executive", and it is just what the name implies, a communications and file-transfer program with a built-in mini operating system that runs under CP/M. This program can do file transfers using either the Christensen or Compuserve protocol, and it has an enormous potential for highly automated operations because it can read and execute command-scripts pre-stored in disk files. These scripts can include sending commands to a remote computer, as if they had been sent manually from the microcomputer in terminal-mode. Users of this relatively new program are still exploring its possibilities. For more information, look in CPM.CRCLST under the heading "PD:", and then get the various files that have "DQC" and "IQF" in their names. These DOCumentation and INFormation files are stored in squeezed form (note the "Q" in the filename extensions), so you will have to unsqueeze them. Overlays for MODM7xx will also work with MEX, but they will not provide all of the extended MEX features. Kermit: Another excellent program for transferring files is called KERMIT. This program has the advantage of being available for an impressively large number of mainframes and micros. It is, for example, available for the IBM-PC, and it DOES NOT require CP/M. To get started with KERMIT, connect to CU20B.ARPA using FTP, and do this: get ker:aaaread.me Note that this file is NOT on SIMTEL20, and the name is subject to change. If you cannot find a file with this name, snoop around in the first half- dozen or so files in the alphabetical listing obtainable using the FTP DIRectory command. You should find something useful. Questions can be addressed to INFO-KERMIT-REQUEST at CU20B.ARPA. Getting Started: In order to get MODM7xx, MEX or KERMIT running on your micro, you must first transfer the necessary files from mainframe to micro. If you already have a receive-to-disk communications program of some sort, you can use it to move the needed files. In the long-run it is essential to be able to transfer 8-bit binary files, but initially it is not absolutely necessary. Some of the files are quite large. For example, MODM7xx.COM is over 18K bytes, and the HEX file (which you will need if you can't transfer 8-bit files) is over 45K. Moving large files to your micro without using an error detecting protocol can result in frustrating errors, but it can be done by receiving multiple copies and using manual or machine-assisted comparisons to locate and repair bad parts of the code. However, there IS a better way. Directory PD: contains a short starter-program called PIPMODEM.ASM that can be FTPed to your mainframe, printed, and then entered into your microcomputer by hand and assembled. This can then be used to down- load either MBOOT3.ASM or BMODEM.BAS (depending on whether you prefer assembly language or BASIC), both of which can receive files using the error detecting Christensen protocol. Once you have this capability, you can download the full-function file transfer program of your choice. To examine this option, connect to SIMTEL20 via FTP and do this: get pd:pipmodem.asm get pd:pipmodem.doc get pd:mboot3.asm get pd:bmodem.bas get pd:bmodem.doc All are ASCII files. Read PIPMODEM.DOC first, then look at MBOOT3.ASM and BMODEM.DOC. PIPMODEM.DOC explains the situation very nicely. Questions concerning these programs should be sent to INFO- CPM@AMSAA.ARPA (NOT to INFO-CPM-REQUEST). NEWSGROUP CORRESPONDENCE ARCHIVES Copies of correspondence for several newsgroups are kept on SIMTEL20 in directories with names of the form PS:, where "KEYWORD" has been chosen to indicate the associated newsgroup. At present, the following correspondence archives are available: newsgroup mail archive filename --------------- --------------------- ADA-SW PS: AMETHYST-USERS PS: INFO-68K PS: INFO-APPLE PS: INFO-CPM PS: INFO-FORTH PS: INFO-HAMS PS: INFO-MICRO PS: INFO-MODEM7 PS: INFO-MODEMXX PS: INFO-MODULA-2 PS: NORTHSTAR-USERS PS: INFO-PASCAL PS: UNIX-SW PS: INFO-XENIX310 PS: Descriptions of these and other newsgroups can be obtained via FTP with anonymous login (as for SIMTEL20) from the Network Information Center's host SRI-NIC.ARPA. Ask for the file PS:INTEREST-GROUPS.TXT (an ASCII file). And please note, this is NOT on SIMTEL20. File names for SIMTEL20 newsgroup correspondence archives have two forms. For example, PS:CPM.ARCHIV.ymmdd is a group of files containing INFO-CPM correspondence going back several years. The characters "ymmdd" in the file names are actually digits giving the year, month and day of the last message in each particular file. Current correspondence is kept in the file PS:CPM- ARCHIV.TXT, which is constantly changing. Although INFO-CPM has been used as an example here, the same naming scheme is used for the other newsgroup files as well. For a complete list of available files, connect to SIMTEL20 via FTP and do this: dir ps: You will receive a list of names of the form: KEYWORD.DIRECTORY.n where "n" is one or more digits. For example, the INFO-CPM listing currently appears as "CPM.DIRECTORY.1" To then get a list of files in a particular archive, do this: dir ps: where "keyword" (for example, "cpm") is chosen from the preceding list, and the word "directory" and the number "n" are not used. At present, all of these files are stored in ASCII. ADDITIONS, IMPROVEMENTS AND CORRECTIONS Suggestions for additions, improvements and corrections to this message are always welcome. Please send them to INFO-CPM- REQUEST@AMSAA.ARPA. Contributions of public domain software are actively solicited. If you have something that seems appropriate for inclusion in the archive, please contact Keith Petersen . Likewise, contact Richard Conn if you wish to contribute to the archive, and Sue Tabron if you have something for the archive. Happy computing! Dave Towson INFO-CPM-REQUEST@AMSAA.ARPA ----> MLIST.DOC <---- An electronic mailing list exists for those who are interested in accessing and contributing software to the Ada Repository on SIMTEL20. To subscribe to this mailing list, send a request via electronic mail to: ADA-SW-REQUEST@SIMTEL20 After you have been logged into the repository's mailing list, you will receive a welcome message which provides introductory information on how to access the repository. The mailing list serves two purposes: to help exchange information between the repository users and to mail repository submissions to the maintainer of the Ada Software Repository for inclusion in the archives. PS:ADA-SW-ARCHIV.TXT contains all recent messages passed over the ADA-SW mailing list. New users on the list are invited to get a copy of this file and scan it for background; older users may use it for reference. In either case, a WARNING: this is a BIG file! PS:ADA-SW.ARCHIVE.ymmdd contains older messages by year/month. A hardcopy newsletter and other hardcopy documentation on the Ada Software Repository are published by Echelon, Inc. and available for reasonable charges. Contact Echelon for details: Echelon, Inc. 885 North San Antonio Road Los Altos, CA 94022 415/948-3820 Richard Conn ----> FINDME.DOC <---- HOW TO FIND THINGS IN THE ADA REPOSITORY ON SIMTEL20 The contents of the Ada Repository are organized in a number of different ways to make finding software and documentation easier for the user of the repository. The following summarizes the information sources. WELCOME MESSAGE The Welcome Message is a rather large text file which is sent to all new subscribers to the ADA-SW electronic mailing list. This message contains a large amount of introductory material on the Ada Software Repository, the operation and use of the Ada Software Repository, and the Defense Data Network. The Welcome Message is stored in PD:WELCOME.DOC. SIMPLE DIRECTORY DISPLAYS FTP can provide most users with a directory display of all files in any of the archives in the Ada Repository. See the following files for more information: PD:ADAREPOS.DOC -- general info on repository contents PD:AAREAD.ME -- archive structures PD:FTP.DOC -- introduction to FTP and file transfer PD:UUCP-BIT.DOC -- accessing via UUCP and BITNET ONLINE DOCUMENTATION SYSTEM The directory PD: contains the source code (in Ada), instructions, and data base for the online documentation system. You can copy all of these files over to your host computer, compile the programs, and then run them to query the data base, which gives you data on each directory in the repository. This data includes a brief description of the directory, a listing of its contents with file sizes, and descriptions of each program and piece of software in the directory. The data base may be copied from SIMTEL20 from time to time as more software is added to the repository. NEWSLETTERS Newsletters are published monthly and placed in the directory PD:. They are also available in hardcopy form for a nominal annual subscription fee. See the file PD:NEWSLTR.DOC for details. MASTER INDEX A Master Index of all software and information in the Ada Software Repository is published by Echelon, Inc. This 300+ page loose-leaf book is updated periodically as the repository grows. See the file PD:INDEX.DOC for details. PROLOGUE FILES Each piece of software has an associated PROLOGUE file of type PRO (eg, SAFEIO.PRO) which contains the Ada Repostory standard header. See the file PD:PROLOGUE.DOC for more information. GENERAL The files in PD: contain information on what is in the Ada Repository, how to access and use the Ada Repository, and other items of interest to the community. ----> DIRLIST.DOC <---- The following presents a summary of the directories in the Ada Repository on SIMTEL20. Ada PD: This is the top-level directory. The names of the subdirectories (*.DIRECTORY) can be seen here. The listing of all files in all subdirectories (ADA.CRCLST) is also stored here. Also, the file FILEUSE.DOC, which contains a listing of all files in the repository, ordered by frequency of use (popularity), is contained here. Ada-SQL PD: This subdirectory contains files associated with the development of a standard Ada DBMS interface (Ada/SQL) based on the dpANS Data Base Language SQL. It is anticipated that SQL will be adopted as the Air Force standard Relational data base query language. . AI PD: This subdirectory contains programs relating to the fields of artificial intelligence, such as expert systems, pattern recognition, and heuristic analysis. . ANSI-LRM PD: This subdirectory contains a machine-readable copy of the ANSI Version of the Ada Language Reference Manual (LRM). The files were obtained from the directory on ECLB, and the file FTPFILES.SUB shows the FTP process used to copy the files over and the renaming that was done. Chapters 1-14 and Appendices A-F are included as CHAPxx.DOC (like, CHAP01.DOC or CHAPA.DOC). Error files are also included as CHAPxx.ERR. The Foreword (FOREWORD.DOC, ERR), Postscript (POSTSCRPT.DOC, ERR), and Table of Contents (TOC.DOC) are included. INDEX.DOC contains the index. . Benchmarks PD: This subdirectory contains various Ada compiler benchmarks. An attempt has been made to see that entries in this subdirectory do not duplicate entries in the directory on ECLB. Benchmarks submitted in conjunction with the NOSC tools are located in the Ada Repository BENCHMARKS directory. . CAIS This directory contains software associated with the Common APSE Interface Set (CAIS). The CAIS is defined in MIL-STD-CAIS. . CAIS_Tools PD: This subdirectory contains tools which are compatable with and modified or implemented to run under the CAIS presented in the directory PD:. These tools have been modified or implemented by Mitre Corporation and internally funded by Mitre. . Compilation_Order PD: This subdirectory contains software which deals with the analysis of groups of Ada programs to determine the proper compilation order. Other information pertaining to the interrelationship of software segments of a system may be obtained as well. . Components PD: This is the components subdirectory. Software components, including general-purpose procedures, packages, and generics, are stored here. Examples are: math packages, TERMCAP routines, generic linked list packages, and dynamic string packages. . Cross_Reference PD: This subdirectory contains tools which generate cross- reference listing of Ada programs. . Data Base Management PD: This directory contains Ada software components and programs directly related to Data Base Management functions. . DDN PD: This subdirectory contains tools and components related to the Defense Data Network, its file transfer, mail, and communications facilities. Implementations of the TCP/IP communications protocol, the FTP file transfer tool, and the SMTP mail handler are included. . Debuggers PD: This subdirectory contains Ada source-level debuggers. A Symbolic Debugger is included. . Editors PD: This directory contains the source code and documentation on some text editors written in Ada. . Education PD: This is the education subdirectory. Sample programs, tutorials, and online courseware are located here. . External_Tools PD: This subdirectory contains several miscellaneous tools which are helpful in developing Ada code but are not written in Ada or pertain to specific environments. For example, an Ada language development interface for the EMACS editor can be found here. . Forms_Generator PD: This subdirectory contains tools for the generation of forms for use by Ada programs. The forms generator will display and accept input into a form (in a screen-oriented fashion via the virtual terminal) in such a way that this mechanism is transparent to the Ada program using it. Instead, the program simply reads fields from the form via procedure interfaces. . General PD: This is the General Information subdirectory. Notes, comments, usage information, and other data are stored here. . Graphical_Kernel_System PD: This subdirectory contains routines associated with a Graphical Kernel System. . Management_Tools PD: This subdirectory contains tools for use in managing an Ada software development project. Status tracking and Manpower estimation tools are included. . Math_Library PD: This subdirectory contains packages of math routines. All routines are written in Ada. Routines for trig functions, exponential functions, matrix manipulation, bit manipulation, and others are contained here. . Menu PD: This subdirectory contains software used in the generation of menus. Applications programs may use these menu generators as front- ends. . Message_Handling PD: This subdirectory contains tools for use in message handling facilities and message transfer. . Metrics PD: This subdirectory contains tools used to perform metrics analysis of Ada software. Tools for path analysis, performance analysis, and other metrics reports are included. . Miscellaneous_Tools PD: This is the miscellaneous tools subdirectory. Sources to various tools which do not fit into the categories of the other subdirectories are placed here. . Newsletters PD: This subdirectory contains the Ada Software Repository (ASR) Newsletters. They are numbered sequentially, starting at 001. File names are ASRnnn.DOC. . Online_Documentation PD: This directory contains supporting files for the online documentation system of the Ada Repository. . Pager PD: This subdirectory contains tools which create and manipulated paged files. All SRC files are paged files, which are files composed of several smaller files separated by a special flag. . PDL PD: This subdirectory contains software associated with Ada Program Design Languages and tools to support the Ada program designer. Such tools include tools for data dictionary manipulation and design analysis. There may be some overlap between this directory and software which may fall into the PDL category that is scattered among the other subdirectories. . Pointers PD: This is the pointers subdirectory. Information on other sources of software and information (such as the USC-ECLB resources) is presented here. This data pertains to both on- and off- net resources. . Pretty_Printers PD: This subdirectory contains pretty printers for Ada source programs. The pretty printers reformat the Ada source programs in order to outline the structure of the programs and provide other useful information for the programmer. . Program_Stubber PD: This subdirectory contains Ada program body stubber tools. They analyze the definition of an Ada software design and generate software bodies as stubs to be filled in later during development. . Simulation PD: This subdirectory contains programs and tools associated with performing simulations, such as queuing simulations. . Spelling_Checkers PD: This subdirectory contains spelling checkers written in Ada. Dictionaries are also included here. . Starter_Kit PD: This subdirectory contains tools which are useful in accessing the software in the repository. It includes the PAGER tool, which is used to assemble and disassembled SRC (paged) files. . Style_Checkers PD: This subdirectory contains Ada style checking tools. They analyze Ada source code and report on various aspects of the programming style, such as consistent indentation and use of long variable names. . Virtual_Terminal PD: This subdirectory contains tools for a virtual terminal package, which performs screen-oriented functions by reading terminal characteristics from a UNIX-like TERMCAP data base. The application program can call routines in these packages and not be concerned with the type of terminal being addressed. . WIS_ADA_Tools PD: This directory contains information about the software tools submitted by the Naval Oceans Systems Center (NOSC). An abstract of the tools is included. These tools were paid for by WIS (WWMCCS Information Systems). . ----> TAPEDIST.DOC <---- Subject: Ada Software Repository available on tape Tape copies of the files in PD: may be made on 9TRK, 1600 BPI tapes in TOPS-20 DUMPER, TOPS-10 INTERCHANGE, and Unix Tar formats. Send a tape, a stamped, self-addressed mailing label, and a short, informal cover letter stating that you would like a copy of this collection and specifying the format. Personnel at White Sands will make the tape at their convenience and mail it back to you. There is no charge for this service. Please use the following address to send your tape. White Sands cannot accept cash, checks, money orders or purchase orders. Send sufficient return postage in stamps. Commander USA White Sands Missile Range STEWS-IM-CM-S (Bldg. 362, Frank Wancho) White Sands Missile Range, New Mexico 88002-5072 DDN electronic mail address is WANCHO@SIMTEL20. Frank's telephone number is 505/678-6257. ----> UUCPBIT.DOC <---- "How can a user of a USENET host access the public domain microcomputer software collection on the DDN/MILNET host SIMTEL20?" is being asked with increasing frequency as that software collection continues to grow. Unfortunately, direct access is not possible as there is no UUCP gateway for file transfer between SIMTEL20 (running TOPS-20) and a USENET host (as there is for electronic mail). DDN, formerly known as ARPANET, is the Defense Data Network. DDN, along with Arpanet, SATNET, SRINET, etc. are all members of a TCP/IP protocol-based, multiple gateway network called InterNet.) USENET has been built on adjacent hosts voluntarily agreeing to store- and-forward relatively short messages across the USENET over dialup lines at 300 or 1200 bps. In the past, helpful InterNet users would fetch the file(s) requested and then e-mail them to the requestor. However, it has been pointed out that large file transfers disrupt the service, delay the shorter messages, and generate unacceptably large phone bills, all of which add up to threaten the tenuous connections that some USENET hosts can barely afford to have. Therefore, we have been asked to encourage InterNet users not to pass archive programs this way. Now for the good news. Some InterNet users, if sent a suitable disk, will download files and return mail the floppy to the requestor. To find a friendly InterNet user, send a message to INFO- CPM at DDN host AMSAA.ARPA via net.micro.cpm identifying your disk format and your request. Usually, someone will respond and come to your aid. If not, don't be bashful, wait a week and try again. But please remember, any such arrangements are strictly between you and your respondent. This is not, repeat NOT, a service of either the InterNet or INFO-CPM. If the above arrangement is inconvenient, or doesn't work, here are several other sources for public domain software. ---------------------------------------------------------------------- Information (and prices) are subject to change without notice. A volume is usually one floppy disk. 1. Echelon, Inc. The Ada Software Repository newsletters and Master Index are available from Echelon, Inc., for nominal fees: Echelon, Inc. 885 N. San Antonio Road Los Altos, CA 94022 415/948-3820 Echelon also supports the Z System (ZCPR3 and ZRDOS). 2. CP/M User's Group The CP/MUG volumes are available from: CP/M User's Group 1651 3rd Avenue New York, NY 10028 3. Special Interest Group/Microcomputers (SIG/M) The SIG/M volumes are distributed by: SIG/M Amateur Computer Group of New Jersey, Inc. Box 97 Iselin, NJ 08830 4. New York Amateur Computer Club PC-BLUE software volumes for the IBM-PC are available from: S-100, CP/M User Group The New York Amateur Computer Club P.O. Box 106 Church Street Station New York, NY 10008 5. PicoNet CP/M Users Group PicoNet, CP/MUG, and SIG/M software volumes are available from: PicoNet P.O. Box 391566 Mountain View, CA 94039 6. Other sources: Compuserve Information Service is another source of public domain software. There are a number of special interest groups (SIGs) devoted to specific hardware as well as CP-MIG, the generic CP/M SIG, a repository for a large quantity of public domain software downloadable by the Compuserve file transer protocol (Christensen protocol is expected by late summer, 1984). There is no charge for access to CP-MIG other than the standard CIS connect charges, and Compuserve can be accessed through their own communications network or through Tymnet. Many Remote CP/M (RCPM) systems around the country, where software is available for downloading for the price of a phone call. I would like to thank Dave Towson, Frank Wancho and Charlie Strom for all their assistance in putting this blurb together. If anybody out in InterNet Land has any questions or comments about the above blurb, feel free to contact any one of us. Jeff Edelheit (edelheit at mitre) Revised 7/14/86 by Richard Conn (ADA-SW-REQUEST at SIMTEL20) --> NEWSLTR.DOC <-- The Ada Software Repository (ASR) newsletter is published monthly by Echelon, Inc. Users of the ASR may freely transfer copies of the newsletter from PD: via FTP (the newsletters are in the files matching ASR*.DOC). A hardcopy mailing of the newsletter is also available by contacting Echelon (for current prices and placing orders): Echelon, Inc. 885 N. San Antonio Road Los Altos, CA 94022 415/948-3820 --> INDEX.DOC <-- The Master Index of the Ada Software Repository (ASR) is a loose-leaf book which contains details on the software and information in the ASR. Each item of software is described by an abstract, information on the host compiler/operating system and target environment, and a listing of all associated files and their locations in the ASR. Each item of information is described by an abstract and a listing of all associated files. The Master Index breaks down the ASR into the following major categories, each presented as separate chapters: o ASR-Specific Information and Programs o Artificial Intelligence o Benchmarks o Communications o Reusable Software Components o Data Base Management o Documentation o Graphics o Project Management o Ada Software Development Tools o Other Tools o the WIS Ada Tool Set Selected items of information from the ASR are included in the Master Index. These items include the Welcome Message, which gives an extensive introduction to the Ada Software Repository (its operation and use) and the Defense Data Network (with emphasis on the use of FTP to transfer files from the archives on SIMTEL20). Appendices include (1) a Snapshot of the ASR (ADA.SNP) which names each directory of the ASR and gives the total size of its contents in terms of bytes and lines of code, (2) a listing of all files in each directory of the ASR with file sizes and CRC data (ADA.CRCLST), and (3) a listing of all files in each directory of the ASR with file sizes, line counts, and PAGER hashes (ADA.RPT). The Master Index includes a complete table of contents, which is helpful in quickly locating specific items of interest, and an extensive index. The first publication of the Master Index exceeded 300 pages in size. As the ASR grows, updates to the Master Index will be issued. The loose-leaf format of the Master Index was selected to facilite the update process and to permit the users to assemble the Master Index and the ASR Newsletters conveniently in loose-leaf notebooks. The Master Index is available only through Echelon, Inc. The ASR Newsletters may be obtained from the ASR in the directory PD: or by hardcopy subscription through Echelon, Inc. To contact Echelon (for current pricing information and orders): Echelon, Inc. 885 N. San Antonio Road Los Altos, CA 94022 415/948-3820 -------