The Hacker's Encyclopedia 1998

home *** CD-ROM | disk | FTP | other *** search

/ The Hacker's Encyclopedia 1998 / hackers_encyclopedia.iso / hacking / internet / trickle.doc < prev next >

Wrap

Text File | 2003-06-11 | 41.7 KB | 863 lines

The TRICKLE Server (C)1987-1993 Turgut Kalfaoglu <TURGUT@TREARN> Last Document Revision: Mar 1993 Contents: * What is TRICKLE? * The server site list * Sending commands to TRICKLE: How? * What does it provide (directories and sites) * Trickle at a glance (statistics) * How Does It Work? * How to use /PDDIR * How to conduct global searches * How to use /PDGET * Subscribing to files * FTP Delivery to you * Other commands of interest * Local (optional) commands * Receiving your files: * Format of the arriving files * Receiving your file in a different format(Sending/Encoding options) * VAX/VMS Users - how to receive the files.. * A last word on options * How to Use BITSEND/BITRCV (IBM and VAX) * How to receive the file that arrives (via PC3270 or Kermit) * How to Donate files to SIMTEL-20 archives * The .ARC format * The .ZIP format * Server Internals: * How Does the Cache Work? * The amazing life of a /PDGET request * Quotas and other Ugly Limitations * Sending files to TRICKLE * Delay Periods (How long will it take?) * Additional Help (lists, online docs, human help) * Glossary that does not exist What is TRICKLE? This server holds different server's files in its shared cache, thus speeding up the delivery of the requested files with a reduced network load. It uses efficient listserv delivery if the file has multiple recipients, and among the server network there is up to one copy of any given file. The Server Sites (listed in connection order:) Location EARN/BITNET Internet -------------- ---------------- ---------------------------------- In Turkey: TRICKLE@TREARN TRICKLE@EGE.EDU.TR In Italy: TRICKLE@IMIPOLI In Belgium: TRICKLE@BANUFS11 TRICKLE@CCS.UFSIA.AC.BE In Austria: TRICKLE@AWIWUW11 In Germany: TRICKLE@DEARN TRICKLE@VM.GMD.DE In Israel: TRICKLE@TAUNIVM TRICKLE@VM.TAU.AC.IL In Netherlands: TRICKLE@HEARN TRICKLE@HEARN.NIC.SURFNET.NL In France: TRICKLE@FRMOP11 TRICKLE@FRMOP11.CNUSC.FR In Colombia: TRICKLE@UNALCOL TRICKLE@UNALCOL.UNAL.EDU.CO In Sweden: TRICKLE@SEARN TRICKLE@SEARN.SUNET.SE In Turkey: TRICKLE@TRMETU TRICKLE@3090.CC.METU.EDU.TR You are urged to use the one that is closer to your location. In this tutorial, we will be using 'TELL TRICKLE AT FRMOP11',but this can be replaced with 'TELL TRICKLE AT <your location of preference>' Sending Commands To Trickle: How? We also will use the 'TELL' command to send a single line message. It should be replaced with whatever is appropriate for your system. (Like XMIT , SEND, etc.) If you are on a node that cannot reach a TRICKLE directly, for example, an internet node, then you must send MAIL files to the server. Simply put the commands, one per line, into the text portion of your mail. If you are using MAIL, you do not need to put 'TELL TRICKLE AT FRMOP11' in front of every command -every line has to begin with a slash (all valid trickle commands begin with a slash). You can also place more than one command per command file, up to your daily command limit. RED now accepts command files in MAIL, NOTE, or regular file format. Use your system's (and yours) favorite utility to prepare your command, and mail it to the server. If you are using MAIL, you may need to place Reply-To: tag to ensure that the server replies to the address that you specify, instead of your 'obvious' address from your 'From:' field. The command files may contain any number of instructions, one per line. These lines must all start with a slash, since all server commands begin with a slash. If you are on a site that is not part of BITNET/EARN, you will receive the files you request UUENCODED. You may tell the server otherwise by specifying (XXE (HEX or (BTOA at the end of your command. If you wish to make sure that the server replies via mail, you need to append (MAIL to the end of your command. What Does it Provide? A Milnet node, SIMTEL20.ARMY.MIL at White Sands Missile Range, New Mexico contains a large selection of public domain and 'shareware' software. This DECsystem-20 machine, running the Tops-20 operating system provides many files of interest, especially to CP/M and MSDOS users. The Trickle (or RED) server mirrors these SIMTEL's files,plus any number of other FTP sites, currently including, but not limited to nic.funet.fi, wuarchive.wustl.edu, and ftp-os2.nmsu.edu. The server operators are free to choose the directories that they would like to support. Thus the exact directories supported varies from server to server. The non-standard directories are considered to the be "Global Directories" meaning, regardless of locations, users requesting files from these archives are honored. The Current List of Provided Directories Let us stress that this list can change at any moment, and new directories can be added at any time: Directory Mirrored FTP Site Provided Via Comments --------- ----------------- ------------ --------------- MSDOS SIMTEL20.ARMY.MIL LISTSERV@RPITSVM All servers have it MISC SIMTEL20.ARMY.MIL LISTSERV@RPITSVM " " " " SIGM SIMTEL20.ARMY.MIL LISTSERV@NDSUVM1 " " " " PC-BLUE SIMTEL20.ARMY.MIL LISTSERV@NDSUVM1 " " " " CPM SIMTEL20.ARMY.MIL LISTSERV@NDSUVM1 " " " " ARCHIVES SIMTEL20.ARMY.MIL LISTSERV@RPITSVM " " " " UNIX-C SIMTEL20.ARMY.MIL LISTSERV@FRORS12 A "global" directory MACINTOS SIMTEL20.ARMY.MIL LISTSERV@FRORS12 " " " OS2 FTP-OS2.NMSU.EDU LISTSERV@FRORS12 " " " AMIGA NIC.FUNET.FI LISTSERV@FRORS12 " " " KERMIT WATSUN.CC.COLUMBIA.EDU LISTSERV@FRORS12 " " " TEX RUSINFO.RUS-UNI- LISTSERV@FRORS12 " " " STUTTGART.DE WUARCHIVE wuarchive.wustl.edu BULLETIN@AWIWUW11 " " " EXPO-MIT export.lcs.mit.edu BULLETIN@AWIWUW11 " " " UUNET ftp.uu.net BULLETIN@AWIWUW11 " " " SUMEX-AIM sumex-aim.stanford.edu BULLETIN@AWIWUW11 " " " In most cases, the Provided-Via server either limits the commands from users, or does not accept them. It is provided here as a reference. You are advised to use them via the TRICKLE server. These directories are mirrored identically - meaning, for example, anything that is in the /pub/amiga directory of NIC.FUNET.FI can be obtained from trickle as <AMIGA.subdirname>. They are refreshed with the originals every 1 to 7 days, depending on the activity of the directory. The "global" directories are the directories that are open to everyone, regardless of geographical location. These directories are "optional" and thus the server administrator decides if his or her site should support it. We, the server operators, would like to stress that we have no affiliation with the US Army, with White Sands Missile Range, nor with any of the other file providing sites. These servers are made available in the true spirit of volunteerism, without any outside sponsorship for the service. TRICKLE At A Glance Trickle has sent 4.5 gigabytes of software in Februrary 1993 to users. It has received 1 gigabyte of software from FTP sites during the same period. Your "average" TRICKLE has 12 directories, 2860 subdirectories, 58371 files in 2.6 gigabytes! TRICKLE code has been worked on since 1988, and in 1993, it is still being enhanced. Just the code itself takes 750 Kilobytes, without any optional commands. With directories, help files, external commands, it occupies 11 megabytes of disk space. How does it work? It provides faster file delivery than remote file servers, because it holds the most recently requested files, and it also asks its peers, to find out if any of them has the file. It has two major commands. /PDDIR and /PDGET.. As the names indicate, the /PDDIR provides the names of the files, and /PDGET delivers files. How to use /PDDIR: On IBM/VM systems, you can get a list of the 'major directory' names by simply typing this command: TELL TRICKLE AT FRMOP11 /PDDIR If you are mailing in your commands, you simply need to put /PDDIR at the body of your mail message. RED should now send you a list of the major directory names. Now, you can obtain a list of the sub-directories of any of the displayed names by putting the name between less-than and greater-than symbols.. For example, TELL TRICKLE AT FRMOP11 /PDDIR <MSDOS> RED will mail you a file containing the names of the sub-directories. Once you choose a subdirectory to examine, type in the main directory name, a period, then the name of the subdirectory name. For example, if you chose STARTER sub-directory of MSDOS, then you may type this: TELL TRICKLE AT FRMOP11 /PDDIR <MSDOS.STARTER> RED will first notify you of the number of files found, then will go ahead and mail you this list.. Once you choose your file(s) to order, then read on.. How to conduct Global Searches: Let's say you know the filename, but have no idea about the location of the file. There is an optional command that can help you perform searches based on a wild-card you specify. It's called /GENERIC. You basically specify all you can, and it does the rest. Let's say the file you are trying to find is called SCAN, and it runs under MS-DOS. You can send something like: /GENERIC <MSDOS.*>SCAN*.* This will match any file in a subdirectory of MSDOS that starts with the word SCAN. You can get very exotic with the pattern, and the only limitation is that the 'root' directory, namely MSDOS must be specified. How to use the /PDGET command: Once you have a filename in hand, then tell RED to send you this file by providing it with the full directory name, and the filename.. If you wish to order a game called MADMAX.ARC that resides in the <MSDOS.GAMES> directory, then you may type in this command: TELL TRICKLE AT FRMOP11 /PDGET <MSDOS.GAMES>MADMAX.ARC Naturally, the above is only an example, and ever since the GAMES directory has vanished from SIMTEL (managerial problems), the above example is guaranteed not to work. Note that it is now possible to order multiple files with /PDGET. If you just specify '*' wildcards in your /PDGET command, TRICKLE uses the '/generic' command to itself, finds out which files match, and orders those files for you. So, if you want to get the files starting with 'CSD' from the OS2 directory, you may say: TELL TRICKLE AT FRMOP11 /PDGET <OS2.*>CSD* Subscribing to Files: This new feature allows you to subscribe to a 'pattern' on the server, and whenever new files that match that pattern arrive to the server, a /PDGET command will be automatically entered for you, for those files. Basically, you tell the server the directory, the subdirectory and a 'keyword' - the first few characters of a filename. If a few files match your request, your entry is recorded, and from there on, if that pattern shows up in the 'New Files Listing' mail of the server, the command /PDGET for that file will be entered for you. LIMITATIONS: ..You are still bound by your daily quotas and server quotas. The server simply 'simulates' that you are sending /PDGET commands to it. So, if you have too many subscriptions, you MAY get 'you issued too many commands today' error, or 'the server's outstanding bytes count is too high, cannot order another file from SIMTEL right now.' errors. The simulated /PDGET command is assumed to have come in as an interactive message to the server, so if you are not logged in at that time, you may miss the server's reply message - don't think that it did not work. Try a /TRLIST before ordering the file (again). HOW TO USE: Actually, there are three new commands: /SUB <directory.subdir>keyword /UNSUB <directory.subdir>keyword /SUB QUERY /SUB now has double purpose - you can still subscribe to 'new directory listings' announcement file by using /SUB <directory> , but you can also use it with a subdirectory option as well. Let me give an example, I like getting the SCAN utility whenever a new one is available, so I can send this (and I already did :) /SUB <MSDOS.VIRUS>SCAN (UUE Now I am subscribed to all files in the <MSDOS.VIRUS> directory that start with the word SCAN. Note that it would be useless to subscribe to "SCAN91" since the trailing numbers keep changing - in the near future, no files would match your pattern. The UUE option just tells the server to encode the file for me before sending. It's an optional parameter. (See the help file for encoding options). If you don't specify it, the server will send it NETDATA (..if your "From:" address is not a domain-address. If so, the default is the UUE encoding.) It is also possible to subscribe to ALL files in a subdirectory. Let's say that you want to receive all patches available to OS/2, as soon as they are made available. You could send: /SUB <OS2.OS2_PATCHES>* to a server that supports this directory. From now on, any new or changed file will be delivered to you. Likewise, /UNSUB removes an entry from your subscription list. Finally, /SUB QUERY allows you to review your subscriptions. It will display a list of the keywords stored for you. There is currently no artificial limit on the number of subscriptions, and hopefully we will not have to build such limits. Remember: You CAN exceed daily limits if you have too many subscriptions. Since the filedates of 00INDEX, INDEX.TXT and such files are usually changed without changing the contents, this causes problems for users who are subscribed to entire directories - they keep getting the INDEX for that directory regardless of if it was changed or not. To prevent this, TRICKLE no longer includes such files in its New Files Listings, nor does it deliver it to the people who are /SUBscribed to them. Note: This new option also allows for 'mirroring' of server archives. If thre are those who are working on a server which can receive feed from a TRICKLE server, please contact your closest server's administrator. TRICKLE can subscribe your server to ALL the files in a subdirectory, and order ALL new files - but for this, you need the approval of your administrator. Finally, a disclaimer: A file subscription can be terminated by the server maintainer, if it deemes to be too resource-consuming (such as, if you subscribe to too many things). FTP Delivery to you TRICKLE now has an option to deliver the files you requested directly to your PC or workstation! For this, your system must be on the internet, so that TRICKLE can FTP it to you. Basically, you tell the server to which host name and to which directory you want your software delivered to, and the server uses this information whenever it "wants" to send you files. You need to provide the information once, and the server broadcasts this info to its peers, and records it on disk. How to configure TRICKLE for FTP Delivery You need to use the /FTP ADD address directory command to define where you want the software sent. "address" can be an IP address, or a domain address, like "earn-ps.circe.fr". The directory is the name of the directory where you want the stuff sent to. The server will use this next to its "cd " command when it connects to your ftp server. Let's say you are at myhost.somewhere.here, and you want TRICKLE to send your software to your /pub/incoming directory. Your /FTP ADD command needs to look like: /FTP ADD myhost.somewhere.here /pub/incoming Once you have this defined, TRICKLE will use one of its "ftp slaves" to deliver you all files. Informational messages will always come thru by mail, including output of commands, like /PDDIR. How To Configure Your Workstation or PC for FTP Delivery TRICKLE will always use "anonymous" as userid, and "-trickle@nodename.bitnet" as password. nodename is the name of the local node where the server is running. So, you need to configure your workstation or PC to accept someone trying to connect to you as "anonymous." Most software packages permit anonymous users, but you may have to configure your network software. When things go wrong TRICKLE's "ftp slaves" (called TRFTP servers) will try to connect to you up to five times. Then it will send you a mail message showing you the transcript of the failure. It will keep your file in HOLD status, until someone restarts that slave. Then it will re-try your file again. Since TRFTP servers are brand new code, we hope to enhance it soon so that it re-tries the connection every day, or even every x hours. In any case, the file is not lost, but can be delayed at the trftp server. Warning! FTP service is only for those whose hardware/software and network connection are capable of running a ftp deamon. If you do not have a functioning FTP deamon on your system, you should NOT use the /FTP ADD command. Otherwise, NONE of the files you requested will be delivered to you, and the TRFTP servers will try forever to connect to you. Other Commands of Interest: /NEWS sends you our 2-page newsletter. Currently not used, ever since we started discussion lists ('discussed' later on in this document) /FTP ADD domainaddress directoryname /FTP QUERY /FTP DELETE These commands are related to the FTP delivery of files to your workstation or PC. See the chapter called "FTP Delivery". /STAT provides you the statistics of daily usage. /HELP sends you this file. /CAC Sends you a list of the files that are stored on its disk right now. These files can be sent faster than the other files. /OPS displays the RED operators /QUO Shows you the RED's quota, and how much of that quotait has used. Once RED exceeds its quota, it cannot order files, until it receives some of the requested files. /SUB <dirnam> Allows you to subscribe to a directory. Whenever a new listing comes in, RED will send you a file containing the names of the new files. /SUB <dirnam.subdir>pattern Allows you to subscribe to a particular set of files on the server. See chapter on "Subscribing to Files" for more info. /SUB QUERY Displays the file patterns you are subscribed to. /UNSUB <dirnam> is to stop RED from sending you the new files listings. Please issue this command if you will not use the server anymore. /UNSUB <dirnam.subdir>pattern Terminates a file subscription. /NEW <dirnam> nnn This command, displays the files that have arrived within 'nnn' days, in the 'dirnam' directory. If 'nnn' is omitted, it defaults to the last time you issued this command, for that directory. If you are issuing this command for the first time, then it simply looks for files that are at most a month old. /POLL forces RED to check its peer servers. Normally the server checks its peer servers at regular intervals to find out if they are running. This command quickens this check. Useful if your own trickle server is down, and you wish to use a remote server. If you send this command to the remote server, it will recognize that your closest server is down more quickly. Local Help Commands: Several versions of this help file have been written in other languages. However, not all RED servers support all languages. For example, the server at DKTC11 supports /HJELP command, the TREARN server has /IMDAT, the FRMOP11 server has /AIDE. To determine the correct local command, send a '?' command to your nearest server. Local (optional) TRICKLE Commands: A whole range of optional commands have been written for TRICKLE by the server administrators. These commands are listed when you send a "/?" command to the server. Here is a brief summary of the local commands that you are likely to encounter: /GENERIC <dir.subdir>fn.ft This command allows you to do wildcard searches within the directories. Excluding the 'dir', which must be specified, the other fields can be filled with generic patterns. Here are some examples: /GENERIC <MSDOS.*>SCAN*.* /GENERIC <MSDOS.TR*>ARJ*.ZIP /GENERIC <UNIX-C.*>GREP*.* /GENERIC is one of the few commands that accepts '*' as a wild- card character. This is in contrast with /PDDIR which can be supplied with the first few characters of a filename. /DISTANCE node1 node2 This command calculates the distance between two BITNET/EARN/Netnorth nodes. The calculation is done based on the number of hops and the link speeds and resistances. /TRLIST This command is very useful: It displays the files you have already ordered from the server. It also lists the status of each file - whether it is being checked at other TRICKLE servers, or if it has been ordered from an FTP-NJE gateway server. /PDSNEWS This is a local utility that replaces VM login messages. If this command is installed at the local TRICKLE, it can store system messages, and display only those messages that the user have not seen before. Receiving your files: Format of the Arriving Files: For the below chart, we shall assume that you have not placed any conversion options at the end of your command. If you have used: You can expect the file to arrive: --------------------- ---------------------------------- 'tell' style message: BITSEND, NETDATA format. MAIL command file: UUENCODED, in numbered pieces. A regular file, or Just like 'tell' messages, IBM's NOTE command: replies in BITSEND, NETDATA. If the file is small enough, BITSEND reverts to SENDFILE, to send your file in one piece. You can just use RECEIVE for such files. TRICKLE will send the files in a NETDATA format, -unless you use the (OLD option-. On IBM systems, these files can be LOOKed and RECEIVEd, but the PEEK command cannot handle NETDATA format properly. However, since most files are ASCII, it is of little use to LOOK at them. (LOOK is a utility that can be obtained from your country NETSERV, it is similar to PEEK, and it displays the contents of the files in your reader. Since SIMTEL (and your personal computer) keeps its files in ASCII format, so does TRICKLE. So, you may not be able to examine your file on the VM system. However, some of the description files (recognized by their names) can be ordered with the (EBC80 or (EBC32 option, if you wish to look at these files on the VM. However, never order files ending with .ZIP or .ARC using EBC options - the result will not be decypherable! Such files are binary files that need to be sent to the PC for proper processing. Normally, SIMTEL files are sent AS-IS, meaning, ASCII. If you would like to receive your file in a different format, you may want to append any of the below to the end of any of your your commands: Encoding options: You may use up to one from this list per command. (EBC80 Converts the file to 80-Column EBCDIC format (EBC32 Converts the file to 132-Column EBCDIC format (UUE uuencodes the file (XXE xxencodes the file that is to be sent to you. (HEX Turns the file to HEX format - use it if even (XXE doesn't work for you, since the file doubles in size with this option. (BTOA BTOA-Encrypts the file. Useful for Unix systems. Sending Options: You may use up to one of these at a time: (OLD Sends the file using DISK DUMP or PUNCH format (SF Supresses BITSEND, and forces SENDFILE to be used for the transfer. (MAIL Forces results to be sent via MAILER. (This option is automatically added for MAIL command files) (MSG Useful for /PDDIR command if you do not wish to receive the reply as a mail message (long /PDDIR replies are sent via mail, short ones are sent as messages by default) You may put one of the sending options and one of the encoding options. So, to receive a file called UUDECODE.C in PUNCH format and UUENCODEd: TELL TRICKLE AT FRMOP11 /PDGET <MSDOS.C>UUDECODE.C (OLD UUE To receive a file in EBCDIC format, you may enter a command that looks like this: TELL TRICKLE AT FRMOP11 /PDGET <MSDOS.GAMES>MADMAX.ARC (EBC80 However, it is not useful at all to receive an .ARC file in EBCDIC format. The above is not a terribly good example. Oh well. VAX/VMS Users: If your host is a DEC VAX system running VMS with Jnet networking software, you can avoid the need for uuencoding. You can tell the Jnet software to bypass the usual EBCDIC/ASCII conversion, but there are a few additional steps needed before downloading a file. * Receive the file with the Jnet command RECEIVE/BINARY. The BINARY modifier suppresses the normal EBCDIC/ASCII conversion. Let's assume that the file is called MYFILE.ARC. This file, as received, is almost correct; there may be an error is how VMS interprets the records. * Generate an FDL file for MYFILE.ARC using: ANALYZE/RMS/FDL MYFILE.ARC * Edit the FDL file with the command EDIT/FDL MYFILE Examine the CARIAGE_CONTROL setting. Change it to NONE. Exit the editor. * Use the edited FDL to correct carriage control interpretation errors in the original MYFILE.ARC: CONVERT/FDL=MYFILE.FDL MYFILE.ARC FIXED_MYFILE.ARC * Download the FIXED_MYFILE.ARC as a binary file using any reliable means. (For VAX Kermit, use SET FILE TYPE BINARY command before starting the download.) A Last Word on Options: Some of the options are not compatible, such as (MAIL SF, and should not be used together - the behavior of the server may be unpredictable. Also, the (SF option may result in a file that is too large for shipment. If that is the case, a network control program may detect it, and delete it before it reaches you - use (SF carefully. Also, (SF and (OLD options would be ignored if you send in your commands in a MAIL file. If you wish to receive your files AS-IS, and still be able to put your commands in a file, you can either send a NOTE to the server, or simply create a file using your editor, then send this file directly to the server, without first going through the mailer. How to use BITSEND/BITRCV: From now on, RED is sending its files in a special format called BITSEND - Unless you include the (SF option while issuing your command. In this format, the files that are sent are broken into smaller pieces, if the entire file is too big to be sent. If the file you request is over the size limit, then the server will first send you a file called <fn> BITCTRL - this is the control file, where BITSEND has written the protocol used, the number of pieces that make up that file, etc. ------------------------------------------------------- Important: You should NOT 'RECEIVE' any files that have BITCTRL or just numbers as filetype! ------------------------------------------------------- If you wait a little longer, the rest of the file will arrive, the filename will be the same as the <fn> BITCTRL file, but the filetype will consist of just numbers. Once you have all the pieces that make up that file, you can then issue the BITRCV command. You must also specify the 'spool ID' of the file that has BITCTRL as filetype. From RDRList, you can simply type BITRCV in front of the file that has BITCTRL as filetype. If you get back an error message, saying "UNKNOWN CP/CMS COMMAND" it simply states that your installation does not have the BITRCV program. Contact your network manager/system operator. Note: BITRCV EXEC can be obtained from your country NETSERV as well. Simply send "GET BITRCV EXEC" to your NETSERV. ----------------------------------------------------------- VAX users: There is also an identical file for your installation, however, it is called 'BITRCV COM', and can be obtained from a NETSERV by issuing GET BITRCV COM to your country NETSERV. ----------------------------------------------------------- If you get back an error saying that not all of the file is in the reader, it simply means that you have to wait a little longer for the rest of the file to arrive. If you are on a different system, thus cannot use neither BITRCV EXEC nor COM, you can simply merge the files you receive using your editor. How to receive the file that arrives (via PC3270 or Kermit): Once the file you requested arrives, and is stored on your disk, you will most likely wish to 'download' this file to your personal computer. There are many types of mainframe computers, many kinds of personal computers, so it is impossible for me to give you direct, and precise directions. However, here are some clues: * If you have a PC with a 3270 Emulation program, and an IBM mainframe, you should request your files from the server without options, or with (SF option, and use the built-in transfer protocol of the emulation program, without any options again. * If you have KERMIT at your installation, request your file without options, or with (SF option, then set the KERMIT's FILE-TYPE to BINARY before transferring your file. * Remember that if you send a MAIL command file to the server to request your file, and you use a domain address as the reply address (in your From: or Reply-To: fields), the file will arrive via mail as well, in UUEncode format. You can override this by specifying another format like (XXE or (HEX or (BTOA. If this file is big enough, you may receive it in several pieces, as you can see from the subject header, which says 'Part x of y '. If this is the case, you should edit the received pieces so that all the headers and the blank lines are removed. You may either transfer this file to your personal computer and UUDECODE (or UN-HEX, XXDECODE, etc) it there, or do this at the mainframe level and send the resulting binary file to your PC. How to DONATE files to SIMTEL-20 Archives: Files that you receive from here are sent from another network called ArpaNet. The person-in-charge for the programs is: Keith Petersen <w8sdz@WSMR-SIMTEL20.ARMY.MIL>. Since it's another network, you will need to use MAIL to send the message. He urges that you talk to him before you send in the file, so that he can check where it should be put, if it already exists, etc. After getting his approval, you need to UUENCODE your file (perhaps using PDUTIL), then MAIL it to him. The .ARC format: ARC is a special compression method that provides substential reduction on file size. There are one or more files contained within an .ARC archive. In order to extract the files from an archive, you will need a utility called ARC, or PKUNPAK. These are available from <MSDOS.ARC-LBR> directory. The actual file names of these files vary, but you may try: TELL TRICKLE AT FRMOP11 /PDGET <MSDOS.ARC-LBR>PK361.EXE or: TELL TRICKLE AT FRMOP11 /PDGET <MSDOS.ARC-LBR>ARC512.EXE If these attempt s fail, it will probably mean that the file version has changed, and so has the file name. You may wish to try TELL TRICKLE AT FRMOP11 /PDDIR <MSDOS.ARC-LBR> and guess the new name of these files. Once you receive either ARC or PKXARC and an .ARC file, transmit them to your personal computer and issue the following command: ARC X <filename.arc> or PKUNPAK <filename> There is also a second utility called ARCUTIL, which runs on the VM systems, and extracts files. It also provides ASCII to EBCDIC conversion of the extracted files. To request ARCUTIL, enter: TELL TRICKLE AT HEARN /PDGET <MISC.IBM-VM>ARCUTIL.LBR The directories of SIMTEL change often. So, the above files may or may not be in the same directories as I have indicated. So you may have to do some searching to find them.. A good place to check would be the <MSDOS.STARTER> directory, where additional help, and the mentioned archive managers can be found. The .ZIP Format The ZIP format was recently introduced to SIMTEL archives. It works just like .ARC, it provides an even better compression ratio. The 'current' file to process ZIP files is PKZ110EU.EXE, which is a self-extracting file, meaning that you run it, and it extracts several files from 'itself'. Very odd indeed. To order this file, use: TELL TRICKLE AT FRMOP11 /PDGET <MSDOS.ZIP>PKZ110EU.EXE Again, the filenames change, so if TRICKLE replies that no such file exists, try a: TELL TRICKLE AT FRMOP11 /PDDIR <MSDOS.ZIP>EXE The EXE bit is called a 'keyword' and will cause all files that contain 'EXE' in their names to be displayed, instead of the whole <MSDOS.ZIP> directory, which held 76 entries when I was working on this chapter. Server Internals * * Abandon All Hope Ye Who Enter Here * * How Does the Cache Work? Imagine that you ask for a file, and the server brings this file from a distant site for you. Thinking that others may wish to have this file as well, the server keeps this file in an area called 'cache.' When someone else requests this file, the server simply uses the stored copy of the file, instead of asking for the file again from far away. All the servers that you see on top of this document have different files in their caches. So, if you wish to see the files they are holding right now, you will have to issue '/CAC' to each one of them. Note that a file does not stay in cache forever. As new files arrive, the older ones are deleted to make room. The Amazing Life of a /PDGET request: Once you order your file via /PDGET, the server will first check its local cache listings. If the file is not there, then it will check the SIMTEL20 listings to ensure that a such file indeed exists. After this, the server sends the request to all other servers, asking them if they have your file in cache. If a server replies 'YES!', then that server has to send you the file. Everything fails: none of the servers have your file, or even some servers don't respond. Your server will give up waiting for a reply in a day, and order your file from the United States. Once the file requested arrives from there, it will be sent to you, and put into the cache directory. Quite a trip for one /PDGET command. Quotas, and Other Ugly Limitations You may be surprised that even though most TRICKLE servers have some kind of quota, we still get several hundred requests daily. Without them, this number may easily rise to thousands. The impact of a such usage rate on the local computer can be very 'tiring.' So, the following quota schemes have been implemented: 1) Total outstanding bytes quota: This quota is not really put by the server's operators. It is the amount that a TRICKLE server can order from The United States. This is currently set at 10 megabytes for most servers. 2) Prime times: Some of the servers, do not function during the day, they record the commands received, and process these commands later, when the load on the computer is low. 3) User request limitations: Most TRICKLE servers have a limit on how many requests a user can make on the server per day. The request can be a simple /OPS command, or a file order via /PDGET. It still counts as one. The server will warn you that you are approaching the limit, once you have 3 more commands left. There is also a 'cost' feature that states that some of the commands cost more than others. The following commands: /CACHE, /PDGET, and if implemented, /TRLIST and /GENERIC commands cost as two commands. So, if the site's quota limit is 40-commands-per-user, you may only issue 20 of the above commands. The commands that are not listed above are counted as one command. 4) Outstanding files per user: This scheme is also employed by some servers, and it limits the number of files a user can order from The United States. 5) Delayed Sendfile: This last scheme is simple: it delays sending your file until a specified time comes. Usually at night, when the network load is low. If a site uses delayed sendfile, you will see a '* Your file will be mailed' notice, instead of '* Your file is being mailed.' Delay Periods: If the file that you requested already exists in the cache directory, then you may expect to receive your file overnight, at the latest. However, the system that RED is running is often slowed down by the other processes that are running. This negatively affects the response time of RED. If the file requested does not exist in the cache directory, then RED will have to order this file from its list server.. If this is the case, the response time of RED is dependent upon the list server. RED will give up waiting for a file after five to twelve days after its request. Additional Help: 1) A Discussion List We now have several online discussion lists that gives assistance on the server. To join one or more of these lists, simply send the following command to either LISTSERV@TREARN, or LISTSERV@HEARN: SUB <the listname> My-full-name where the listname is one of these, depending on which list you would like to join: RED-UG about the software provided by the servers. RED-SYS Server system news/problems list. For example, if you wish to learn how to use the new program you got from the server, or if you are looking for a program that would remove the virus from your diskettes, you can consult the RED-UG list. If the server crashes on you, or doesn't send you the file that you asked for, you should write this to RED-SYS list. Remember that you can use MAIL to interact with both TRICKLE and LISTSERV, and if you do, you need to put the commands in the mail body, and not in the subject section, like some other servers. 2) Other online documentation on the server You may request additional documentation on the workings of the server by issuing: INDEX RED-UG to LISTSERV@TREARN.BITNET. Then order any of the listed files via GET fn ft ..to LISTSERV@TREARN, where fn and ft are the filename and filetype of the listed files. 3) Human Help Also, you may get in touch with your local TRICKLE operator. You can get his/her network address by using the /OPS command. We wish you great benefits from using TRICKLE - we know that the software it provides can accomplish that.