AOS KERMIT in RATFOR -------------------- This AOS version of KERMIT was written on a DATA GENERAL S/250 running AOS Rev. 4.0 and Fortran 5 Rev. 6.14. The source code is written in RATFOR, which translates into FORTRAN 5 code before compilation. For those of you who need to make modifications to the program, it is recommended that you examine the RATFOR source code where there is at least some documentation on various sections of program code. In evaluating the merits of this KERMIT-AOS program one should keep in mind that the main purpose of implemented KERMIT-AOS on our system was for understanding and evulation of the KERMIT protocol itself. Therefore more effort was spent on the file transfer function than on the terminal emulation function. Our computing facility also includes the availability of a local area network hence the issues of controlling baud rate or parity bit were not addressed. I was a little bit reluctant in releasing this program because I felt it is not in a desirable state; however I was persuaded by others that something is better than nothing at all. I can only added that this AOS version of KERMIT works on our system. It transferred files sucessfully between an IBM/PC and IBM 370/CMS; the latter programs came from Columbia University via DECUS tape. Credit should also be given to Fred Brehm who installed the RATFOR translator onto D.G. machines for RCA and it makes my implementation of AOS-KERMIT from the C listing found in the PROTOCOL manual much simpiler. Permission is granted to any individual or institution to copy or use this program, except for explicitly commercial purposes. John Lee RCA LABS (Princeton) 609-734-3157 1/23/84 Terminology and features ------------------------ LOCAL - An user will be using KERMIT-AOS in logon to other KERMIT, - file transfer will occur on a TTY line other than the TTY - line this user used in activating KERMIT-AOS. REMOTE - An user will be using other KERMIT in logon to the AOS - system and activiating KERMIT-AOS. File transfer will - occur on this same TTY line. IN REMOTE sending mode, there - is a 15 second delay before the first SINIT packet is send. - This would permit the user time to jump back to his/her - KERMIT and enter the RECEIVEING state. 9600/1200 - It is only valid in LOCAL mode. It gives users a choice of - baud rate. If user choose 9600 baud, KERMIT will used @CON4 - which is already sysgened as 9600 baud. If user choose 1200 - baud, KERMIT will used @CON11 which is already sysgened as - 1200 baud. The AOS system is rather slow in handling terminal - I/O hence 'CHAT' mode works better at 1200 baud while higher - baud rate does not show much improvement in file transfer mode - because our system is always heavily loaded with other more - priviledged programs. UNHUNG - AOS KERMIT does not support time-out READ which mean if a - packet is lost, it will goes into an indefinite wait state - unless the other KERMIT is smart enough to detect a dead- - lock situation. As each data packet is exchange, the packet - frame sequence number is display on the screen ( in LOCAL - mode only). Hitting the NEWLINE key while in file transfer - mode will resulted in KERMIT-AOS sending out a NAK packet - which may or may not resolved dead-lock problem. CONNECT - Enters into the 'CHAT' mode, whatever you typed on the - local keyboard is transmitted to the remote host, and - information from the remote host are transmitted to the - local terminal. 'CHAT' mode is used in establishing - login sessions and invoking remote KERMIT program. - CNTR-] will cause exit from 'CHAT' mode. - NOTE : When not in IBM mode, KERMIT does a line read rather - a single byte read, hence information from remote - system not ending with a CR or LF will not be - displayed until the next CR or LF is detected. EXIT - EXIT from this KERMIT program and returns to the CLI. HELP - Displays the content of a help file. QUIT - QUIT from this KERMIT program and returns to the CLI. RECEIVE - Enters the 'RECEIVE' state of file transfer mode, - program waits for in-coming packet with no time-out - detection capability provided. Unhung feature in LOCAL - mode may or maynot resolved the problem. SEND - Enters the 'SEND' state of file transfer mode, program - will then prompts for either a filename or a directory - of filenames (i.e. @directory) to be transmitted. E.G. - a filename of 'TEST' means send the file with the filename - of 'TEST', whereas a filename of '@TEST' means each line of - file 'TEST' is to be interpreted as a filename to be send. - This acts as a work around with the wildcard feature found - on other system. SET IBM OFF- In 'CHAT' mode, expects remote system to echo back - transmitted characters. In file transfer mode, does - not wait for the detection of DC1 before sending out - the next packet. SET IBM ON - In 'CHAT' mode, performs local echoing of transmitted - characters. In file transfer mode, wait for the - detection of DC1 from CMS before sending out the next - packet. STATUS - Displays the current values of various setting. Installation ------------ The Ratfor source comes in 56 small pieces; to simplify KERMIT distribution, these are collected into a single file. The file boundaries are marked by a line of the form # -->> FILE name where "name" is the name of the original file ("#" is the Ratfor comment character). To build the program, you can pick this monolithic file apart and then use the AOSCOM.CLI procedure to compile it, and the AOSLOD.CLI procedure to load it. It is assumed that you have a Ratfor compiler and the various required support libraries. If you don't, you can get them from the Software Tools User Group.