version of RSTS/E must be 8.0 or later for Kermit to function correctly. Kermit will run on version 7.2, but there will be random problems with file access. This is due to the use of RMS11 version 2 in Kermit-11 for all file activity; version 7 of RSTS/E supports only RMS version 1.8. .br Kermit's use of RMS11 costs you NOTHING. You have the option of using an image that contains RMS in disk overlays (K11NRS.TSK), or you can use one that's linked to the segmented RMS resident library, RMSRES (K11.TSK). The pros and cons of using RMS will not be discussed; there aren't any valid reasons NOT to use it. .s 1 Be sure that the SYSGEN question relating to multiple private delimiters was answered YES, otherwise Kermit will tell you it can't run without it as soon as you attempt a file transfer. Multiple delimiter masks cost you one word in executive data space to be used as a pointer to a small buffer containing the delimiter mask; the small buffer is not allocated until Kermit requests the monitor to do so. .s 2 Tape distribution: .s 1 There are many different possibilities here. You may have an ANSI-D tape from Columbia, a backup tape from a friend, a DOS format tape from DECUS, or even RX50's for a Micro-11 system. All following examples are done under RSTS/E version 9.0 or later. .s 1 .lit (1) DOS format Kermit-11 tape $ MOU MM0:/FOR=DOS $ PIP MM0:[*,*]*.*/L:S $ PIP SY:[1,2]=MM0:[*,*]K11.TSK $ PIP SY:[1,2]=MM0:[*,*]K11HLP.HLP $ PIP SY:[1,2]=MM0:[*,*]K11USR.DOC $ SET FILE [1,2]K11.TSK/RUN=RSX/PRO=104 $ SET FILE [1,2]K11HLP.HLP/PRO=40 $ DEFINE/COMMAND/SYSTEM KER-MIT [1,2]K11.TSK/LINE=30000 The above commands did the following: (1) Insure the tape label format is DOS-11 (2) Get a directory to make sure the files are really there (3) Copy the executable task image (linked to RMSRES) (4) Copy the online help file (5) Copy the Kermit-11 users guide (6) Set protection and runtime system name (7) Create a CCL definition for Kermit to be invoked with .eli .test page 10 .lit (2) Ansi D format tape from Columbia $ MOU MM0:/FOR=ANS KERMIT ! RSTS/E 9.0 or 9.1 $ MOU MM0:/OV=ID ! RSTS/E 9.2 or later $ PIP SY:=MM0:K11.HEX $ PIP SY:=MM0:K11HEX.BAS $ PIP SY:[1,2]=MM0:K11HLP.HLP $ PIP SY:[1,2]=MM0:K11USR.DOC $ BASIC old k11hex run K11HEX- Decode Kermit-11 Hex files (RSTS/E Basic+) Input Hex file ? K11.HEX Output Task image? K11.TSK $ $ COP/REP K11.TSK [1,2] $ SET FILE [1,2]K11.TSK/RUN=RSX/PRO=104 $ SET FILE [1,2]K11HLP.HLP/PRO=40 $ DEFINE/COMMAND/SYSTEM KER-MIT [1,2]K11.TSK/LINE=30000 Again, the sequence of operations is: (1) Insure current tape labeling is ANSI (2) Copy a hexified version of the task image (3) Copy a simple Basic+ program to create the task image (4) Copy online help file and user documentation (5) Switch to Basic+ (6) Run the K11HEX program, creating a task image (7) Copy the task image to [1,2] (8) Set runtime system, protection and ccl command. .eli If the tape label for an ANSI tape is unknown, you can switch to Basic+ or RSX keyboard monitors and do an ASSIGN MM0:.ANSI as the RSTS/E DCL Mount command lacks an override switch for volume identification. If the DCL command BASIC fails, try the ccl command SY/R to find out what Basic is called, and then try a SWITCH nnnnnn ccl command, where 'nnnnnn' is the Basic+ run time system name. For example, the author always uses BAS4F for the basic run time system (to designate 4 word FP11/KEF11 support), and the DCL symbol BASIC is defined as BASIC :== CCL SWI BAS4F. .br If PIP gives you an error message regarding insufficient buffer space, redefine the CCL command definition for PIP to extend PIP to 28KW; this is done by specifying a line number in the form 8192+size(KW). .s 2 (3) RX50 or RX01 floppy diskettes .s 1 The DECUS Library Micro-RSTS distribution is on RT-11 formatted RX50 diskettes; the Decus Library (Decus number 11-731) alternate distribution media on RX01's is also a set of RT-11 formatted floppy diskettes. These aK11INSRNO[.050032]K11INS.RNO[.050032]    X14|H [4;Ik(&'( k ߫H&P` \RrPP2PPzPP{PPPPP2P~\$\\TD 0D \~ hi) +\ ^( n ^( np\^txY\^ˀ\!kVk<\F˰<˴ˬ\VVkˤ1`@lP ABCDEFGHIJKLMNOPQRSTUVWXYZ$.?0123456789<@<SЬTЬ UQS>?\\\\\\\\\`:#@'="\abcdefghi\\\\\\\jklmnopqr\\\\\\\~stuvwxyz\\\\\\\\\\\\\\\\\\\\\\{ABCDEFGHI\\\\\\}JKLMNOPQR\\\\\\\\STUVWXYZ\\\\\\0123456789\\\\\  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`ABCDEFGHIJKLMNOPQRSTUVWXYZ{|}~@ggh<i|o<m<4p<p<k|Zn<l fr rwx<x<x<x޺<w@]@@fjnr]Ze@@|> | |v<H|  |  |xz|  |zt f r   < &^ @&@'*/V,"?Lh:hmBmz|z{x`y~|fN|@@|@͂|@ ݃ƃ<ns<|Ŏ |️|ep|u|-@率|<ﾲ2ֻr||ZRM | ntB|xyvZw|J=|R>|J? nnaa|bddfSET LIN TT: force use of the console line .eli Kermit-11 also requires the presence of timer support in the executive. This is required to support the .TWAIT directive; FB and XM systems always have support for this; SJ systems by default do not. If Kermit decides that it does not have a clock, which it would think if .TWAIT support is missing, it will try to fake .TWAIT's with cpu bound loops. The best thing is to insure that you have a FB or XM monitor available for use with Kermit. .s 2 TSX+ .s 1 Kermit-11 is used on TSX+ (a product of S_&H Computing) as both a LOCAL Kermit (you connect out to another system using the CL handler) and a REMOTE Kermit (you log into a TSX+ system and run Kermit-11 to communicate with your local Kermit system). The second is identical to Kermit use on most multiuser systems (for example, TOPS-20 and RSTS/E), while the former is similar to Kermit use on RT-11 with the XL/XC handler. In order to CONNECT out from TSX Kermit to another system, you need to associate the appropriate CL line with the logical name XL, or, if you are running Kermit-11 2.44 or later and have 8 CL lines or less, you can directly specify the CL unit number: .lit .SET CLn LINE=4 .SET CL NOLFOUT .ASS CLn XL .KERMIT Kermit-11>SET LIN XL Kermit-11>CONNECT or: Kermit-11>SET LIN CLn .eli where 'N' is the CL unit number, or just CL for CL0:. Please consult the Kermit-11 User's Guide for further information regarding serial line support. .s 1 The image K11XM.SAV will use approximately 100 blocks of PLAS swapfile space; if that is excessive, or if Kermit fails to load, then the disk overlayed image K11RT4.SAV may be used. Alternately, the TSGEN.MAC parameter SEGBLK may be too small to contain K11XM's virtual overlay; the TSX+ system manager will need to increase SEGBLK and reboot TSX+. .s 2 Installing Kermit on RT-11 and TSX+ .s 2 As in the case of RSTS/E, there are so many media formats that may be used for Kermit that we must restrict the discussion to the more likely media. First of all, the files of interest are: .lit K11XM.SAV For use on RT-11 XM, PRO/RT-11 and TSX+ K11RT4.SAV For use on RT-11 SJ and FB, also usable on TSX+ K11HLP.HLP The online help file K11USR.DOC The user's guide .eli The most common media that RT-11 and TSX+ users may get Kermit-11 is on 8 inch RX01 diskettes and 5 1/4 inch RX50 floppies. Both examples reference RX50 devices, the use of RX01 and RX02 disks is the same except that a RX01 (RX11-BA and RXV11-BA) drive is called DX and the RX02 drive is called DY. Additionally, the eight inch floppies have a lower capacity than an RX50, thus Kermit-11 files may be split across two or more diskettes. The RX50 drives are known as DZ0: and DZ1: on the PRO/350, and they are known as DUn: and DUn+1: on other QBUS processors, when N is the number of fixed drives (RD50,51 and 52). If your system is NOT a PRO/3xx series systems, you would need to replace the references to DZn: with the appropiate DU device names. For example, if you have one RD52 winchester drive and two RX50 units, then the first RX50 would be DU1: and the second DU2:. The RC25 is an exception; if your system had one RC25 and an RX50, then the first RX50 would be called DU4:. If your system contained no MSCP disk drives other than the RX50, then the units would be DU0: and DU1:. .lit (1) RT-11 5.2 and PRO/350, files on RX50 media .COPY DZ0:K11XM.SAV DK:KERMIT.SAV .COPY DZ0:K11HLP.HLP DK: .COPY DZ0:K11USR.DOC DK: .SET XC SPEED=9600 .KERMIT Kermit-11 T3.44 Last Edit: 04-Feb-86 PRO/350 comm port set to XC0: Kermit-11>EXIT .eli Since this was a PRO/350, we must use the K11XM.SAV executable image, since only RT-11XM will run on the PRO. Had this been a PDP-11 running RT-11 SJ or RT-11 FB, we would have copied K11RT4.SAV to KERMIT.SAV rather than K11XM. .lit (2) RT-11 5.2 FB and LSI-11/23 .COPY DU1:K11RT4.SAV DK:KERMIT.SAV .COPY DU1:K11HLP.HLP DK: .COPY DU1:K11USR.DOC DK: .SET XL CSR=176510 .SET XL VEC=310 .KK11INSRNO[.050032]K11INS.RNO[.050032]    X14|H [4;Ik(&'( k ߫H&P` \RrPP2PPzPP{PPPPP2P~\$\\TD 0D \~ hi) +\ ^( n ^( np\^txY\^ˀ\!kVk<\F˰<˴ˬ\VVkˤ1`@lP ABCDEFGHIJKLMNOPQRSTUVWXYZ$.?0123456789<@<SЬTЬ UQS>?\\\\\\\\\`:#@'="\abcdefghi\\\\\\\jklmnopqr\\\\\\\~stuvwxyz\\\\\\\\\\\\\\\\\\\\\\{ABCDEFGHI\\\\\\}JKLMNOPQR\\\\\\\\STUVWXYZ\\\\\\0123456789\\\\\  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`ABCDEFGHIJKLMNOPQRSTUVWXYZ{|}~@ggh<i|o<m<4p<p<k|Zn<l fr rwx<x<x<x޺<w@]@@fjnr]Ze@@|> | |v<H|  |  |xz|  |zt f r   < &^ @&@'*/V,"?Lh:hmBmz|z{x`y~|fN|@@|@͂|@ ݃ƃ<ns<|Ŏ |️|ep|u|-@率|<ﾲ2ֻr||ZRM | ntB|xyvZw|J=|R>|J? nnaa|bddfX programs are intended to convert the 'HEX' file format into an executable task image; instructions are contained in the respective source files for compiling and task building. Please note that whenever a task image is transferred to an RSX based system, as P/OS is, the image MUST be made contiguous, as in: .lit $ COPY/CONT K11POS.TSK K11POS.TSK P/OS under DCL > PIP K11POS.TSK/CO=K11POS.TSK RSX-11M under MCR .eli .s 1 The last note regards FUNCTION key mapping; K11POS will, while in CONNECT mode, map the following keys: .lit F5 (Break) Control\ B will send a break to the remote system as well as typing F5. F6 (Interrupt) Send a Control C (03 octal) to remote F10 (Exit) Send a Control Z (032 octal) to remote F11 (ESC) Send Escape (033 octal) to remote F12 (BS) Send Backspace (011 octal) to remote F13 (LF) Send LineFeed (012 octal) to remote .eli .subtitle RSX-11M/M+ Installation .test page 10 .index RSX-11M and RSX-11M Plus installation .s 3 .c;Installation of Kermit-11 on RSX-11M and RSX-11M Plus .s 1 Kermit-11 runs under RSX-11M 4.0 or later, RSX-11M Plus 2.1 or later, and MicroRsx version 3. All file activity is done through RMS11 version 2; this is one compelling reason why Kermit can not function on earlier versions of RSX. The use of RMS11 does, however, give you transparent support for Decnet and compatability of Kermit's file system between RSX, P/OS and RSTS/E. .br There are two distributed task images for RSX. The file K11RSX.TSK is used on RSX-11M and can also be used on RSX-11M Plus, and has DECNET support linked into the image. The other image, K11POS.TSK, is usable only on RSX-11M Plus and MicroRSX, as it is linked to the segmented RMSRES resident library. It is NOT linked to DAPRES, thus if Decnet access is required, the former task image must be used. .s 1 The main distribution methods for Kermit on RSX are via DOS-11 formatted magnetic tape, Ansi-D tape from Columbia University and the RSX SIG symposia tape (in BRU or VMS Backup format). The former, DOS-11, is the format that the Decus library's copy of Kermit-11 (Decus number 11-731). There is an alternative distribution from DECUS on either RT-11 formatted RX01 diskettes, or on ODS1 RX50 diskettes. .lit (1) DOS format magtape > MOU MM0:/FOR > INS $FLX > FLX SY:/RS=MM0:[*,*]K11RSX.TSK/DO > FLX SY:/RS=MM0:[*,*]K11POS.TSK/DO > FLX SY:/RS=MM0:[*,*]K11HLP.HLP/DO > FLX SY:/RS=MM0:[*,*]K11USR.DOC/DO > PIP [1,54]/CO=K11RSX.TSK > PIP [1,2]/CO=K11HLP.HLP > PIP [1,54]K11RSX.TSK/PR/WO:R > PIP [1,2]K11HLP.HLP/PR/WO:R > INS $K11RSX/TASK=...KER (1) The tape is mounted foreign (2) FLX is installed, if it is not already (3) The main Kermit-11 RSX task image is copied (4) The alternate task image is copied (5) The online HELP file is copied (6) The users guide us copied (7) The task is copied to [1,54] and made contiguous (8) The help file is copied to [1,2] and made contiguous (9) The task image's protection is set to WORLD read access (10) The HELP file's protection is set to WORLD read access (11) The task image is installed as KER .eli .s 2 .lit (2) ANSI D format tape from Columbia University >MOU MM0:/OV=ID >PIP SY:=MM0:K11RSX.HEX >PIP SY:=MM0:K11HEX.FTN >PIP SY:=MM0:K11HLP.HLP >PIP SY:=MM0:K11USR.DOC .eli The tape set, as it comes from Columbia University, is blocked at 8192 bytes per tape block. This could cause PIP to fail unless PIP is installed with a very large size increment. If this should occur, you will get an error message similar to: .lit PIP - open failure on input file MM0:[5,20]K11RSX.HEX;1 No buffer space available for file To correct this you can do one of two things: >INS $PIP/TASK=...XPP/INC=50000 >XPP SY:=MM0:K11RSX.HEX >XPP SY:=MM0:K11HEX.FTN >XPP SY:=MM0:K11HLP.HLP >XPP SY:=MM0:K11USR.DOC >REM XPP or: >RUN $PIP/INC=50000 PIP>SY:=MM0:K11RSX.HEX PIP>SY:=MM0:K11HEX.FTN PIP>SY:=MM0:K11HLP.HLP PIP>SY:=MM0:K11USR.DOC PIP>^Z > .eli .K11INSRNO[.050032]K11INS.RNO[.050032]    X14|H [4;Ik(&'( k ߫H&P` \RrPP2PPzPP{PPPPP2P~\$\\TD 0D \~ hi) +\ ^( n ^( np\^txY\^ˀ\!kVk<\F˰<˴ˬ\VVkˤ1`@lP ABCDEFGHIJKLMNOPQRSTUVWXYZ$.?0123456789<@<SЬTЬ UQS>?\\\\\\\\\`:#@'="\abcdefghi\\\\\\\jklmnopqr\\\\\\\~stuvwxyz\\\\\\\\\\\\\\\\\\\\\\{ABCDEFGHI\\\\\\}JKLMNOPQR\\\\\\\\STUVWXYZ\\\\\\0123456789\\\\\  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`ABCDEFGHIJKLMNOPQRSTUVWXYZ{|}~@ggh<i|o<m<4p<p<k|Zn<l fr rwx<x<x<x޺<w@]@@fjnr]Ze@@|> | |v<H|  |  |xz|  |zt f r   < &^ @&@'*/V,"?Lh:hmBmz|z{x`y~|fN|@@|@͂|@ ݃ƃ<ns<|Ŏ |️|ep|u|-@率|<ﾲ2ֻr||ZRM | ntB|xyvZw|J=|R>|J? nnaa|bddfof IAS Kermit-11 is based on base 2.30 of Kermit-11. It will likely stay at this base level forever; the conversion was done for use with RMS11 version 1, which will be superceded by RMS11 version 2 in IAS 3.2 Update C. At that point the IAS 3.1 Kermit task image, K11I31.TSK, will no longer function since it is linked to an RMS version 1 resident library. The RMS resident libraries were redone for RMS v2 in order that (1) the library can be segmented into multiple libraries and (2) the entry point addresses are never changed, thus new versions of the reslib do not force the user to relink ones task images. .s 2 Restrictions and notes: .s 1 1) Dial-out lines must not be interactive terminals. That is, if you are going to use a line as a dial- out line, you must not allocate it to PDS or SCI. .s 1 2) Spawning installed tasks is currently done via a SPWN$ directive rather than via RUN$T. Therefore, anyone wanting to spawn installed tasks must have the PR.RTC (real-time) privilege. A workaround is to exit from Kermit, run the program, and then run Kermit again. Kermit will first try to run an installed task named $$$xxx, where xxx is the system command requested; if that fails, Kermit will try to run an installed task named ...xxx. .s 1 3) Wild-card file operations are supported (for example, DIR *.DAT, DEL *.TSK, SEND *.MAC). Under RSX, Kermit uses RMS version 2 to do wild-card operations; this is available under IAS V3.2 but not under IAS V3.1. Therefore, on IAS V3.1 (the version that the EPA is running), there are the following restrictions on file operations:: .lm 5 .s 1 a) Wild-cards must be specified for the entire field or not at all. For example, TEST.* is OK but TEST*.* is not. .s 1 b) If a wild-card file operation is executed, with either the file-name or the file-type specified as a wild-card, the file version number is also taken to be a wild-card. .s 1 c) Wild-card operations are not allowed on directories. Therefore, [*,*]*.DAT is not a legal wild-card operation in Kermit-IAS. It is legal to use explicit directories, such as [200,200]*.DAT. .s 1 d) RMS Version 2 supports transparent DECNET remote file operations, while RMS Version 1 does not. Therefore, Kermit-IAS under IAS V3.1 does not support DECNET file transfers. .s 1 e) Renaming files within Kermit is not supported under V3.1 of IAS. .lm 0 .s 2 4) Kermit under IAS currently reads packets one character at a time, and so can use up a fair amount of the CPU if it is receiving files. If it is sending packets (sending files or remote command responses), or if it is reading commands rather than its file transfer packets, it will use long I/O operations and will not put an excessive burden on the system. .s 2 Installation: .s 1 Kermit is built as a multi-user task, with a task name of $$$KER. It can be run as an installed "foreign command" task: .s 1 .lit PDS> install k11ias PDS> kermit Kermit-11 T2.30 Kermit-11>... You can also specify another name for the installed command: PDS> install/sys:k11 k11ias PDS> k11 Kermit-11 T2.30 Kermit-11>... Or you can just run it as a non-installed task: PDS> run k11ias 16:30:15 Kermit-11 T2.30 Kermit-11>... The following files are supplied for Kermit-IAS to run: K11I31.TSK - The Kermit task image K11HLP.HLP - The Kermit help file. For this to be used by Kermit, it must be in the default directory. K11I31.DOC - This file, describing Kermit on IAS .eli .s 4 .subtitle Obtaining updates of Kermit-11 .index Obtaining updates of Kermit-11 .s 1 .c;Obtaining Kermit-11 updates from the University of Toledo .s 1 From Bitnet server on U of Toledo's 11/785 .s 1 .lit from VM/CMS: CP SMSG RSCS MSG UOFT02 KERMSRV DIR CP SMSG RSCS MSG UOFT02 KERMSRV SEND K11*.* from VMS Jnet: $ SEN/REM UOFT02 KERMSRV SEND K11*.* Dialup access to the 11/785: (419) 537-4411 Service class VX785A User: KERMIT Password: KERMIT Source and hex files are in KER:, binaries are in KERBIN: .eli K11INSRNO[.050032]K11INS.RNO[.050032]   X14|H [4;Ik(&'( k ߫H&P` \RrPP2PPzPP{PPPPP2P~\$\\TD 0D \~ hi) +\ ^( n ^( np\^txY\^ˀ\!kVk<\F˰<˴ˬ\VVkˤ1`@lP ABCDEFGHIJKLMNOPQRSTUVWXYZ$.?0123456789<@<SЬTЬ UQS>?\\\\\\\\\`:#@'="\abcdefghi\\\\\\\jklmnopqr\\\\\\\~stuvwxyz\\\\\\\\\\\\\\\\\\\\\\{ABCDEFGHI\\\\\\}JKLMNOPQR\\\\\\\\STUVWXYZ\\\\\\0123456789\\\\\