IBM System/370 VM/CMS Kermit 4.0 Installation Instructions: 1. Get the necessary files from the Kermit distribution tape or from BITNET KERMSRV or elsewhere onto your A disk. As distributed by Columbia, the files are named as follows (all with prefix IKC or IK0): IKCBOO.ASM Assembler source for Kermit bootstrap program IKCKER.ANN Text of Kermit-CMS 4.0 Announcement IKCKER.BWR A "beware" file, listing known bugs and problems IKCKER.DOC Kermit User Guide chapter for CMS, plain text IKCKER.HLP Kermit-CMS help file, CMS HELP (Script) format IKCKER.INS Kermit-CMS installation instructions (this file) IKCKER.MSS Scribe source for IKCKER.DOC IKCKER.UPD Updates for CMS version of Kermit-370 IKCMAC.ASM Assembler source for CMS-specific macros IKCUTL.ASM Assembler source for CMS-specific routines IK0CMD.ASM Assembler source for command handler IK0COM.ASM Assembler source for global code IK0DEF.ASM Assembler source for parameter definitions IK0DOC.ASM Assembler source with brief history IK0KER.DOC Kermit User Guide chapter for Kermit-370, plain text IK0KER.MSS Scribe source for IK0KER.DOC IK0KER.UPD Update history for Kermit-370 IK0MAC.ASM Assembler source for generic Kermit macros IK0MAI.ASM Assembler source for storage initialization IK0PRO.ASM Assembler source for generic routines 2. Rename and reformat, if necessary, the source files on the A disk. If you received the program from Columbia on tape or over a network, the assembler source files probably have the prefix IK and the filetype ASM. In this case, you must change the filetype to ASSEMBLE so that the assembler will find the files, and then change the program's name to KERMIT: COPY IK0DOC ASM A KERMIT ASSEMBLE A (RECFM F LRECL 80 REP COPY IK0MAC ASM A KERMIT ASSEMBLE A (APP COPY IKCMAC ASM A KERMIT ASSEMBLE A (APP COPY IK0DEF ASM A KERMIT ASSEMBLE A (APP COPY IK0MAI ASM A KERMIT ASSEMBLE A (APP COPY IK0COM ASM A KERMIT ASSEMBLE A (APP COPY IK0CMD ASM A KERMIT ASSEMBLE A (APP COPY IKCUTL ASM A KERMIT ASSEMBLE A (APP COPY IK0PRO ASM A KERMIT ASSEMBLE A (APP COPY IKCBOO ASM A KERMBOOT ASSEMBLE A (RECFM F LRECL 80 COPY IKCKER HLP A KERMIT HELPCMS Y2 For the last item, you must be linked in R/W mode to the Y disk. The file IKCKER HLP should be stored on the system's Y disk as KERMIT HELPCMS so that the CMS HELP KERMIT command, and Kermit-CMS's built-in HELP command, can find it. Although the Y disk is probably the best choice, some other disk could, in principle, be used. One consequence of using the Y disk is that the files must have a filemode number of 2. The last item also depends on what level of CMS is running at your installation, since the format of on-line HELP files changed at CMS/SP Release 4. If your installation has Release 4 or later, you should replace the last command with the following: HELPCONV IKCKER HLP A COPY IKCKER $HLPCMS A KERMIT HELPCMS Y2 The new HELP file differs from the old in that it is pre-formatted, i.e., it may be printed "as is". The Kermit User Guide for CMS is distributed in two parts: IKCKER DOC and IK0KER.DOC; these may be kept wherever you keep online documentation files, renamed appropriately. Note that the foregoing procedure preserves the sequence numbers in columns 73-80 of the source files. If you elect to use an editor to merge files, be absolutely sure that you don't inadvertantly lose the original sequence numbers (something editors are prone to do). 3. GLOBAL the necessary MACLIBs. Under VM/SP, these are DMSSP, CMSLIB, OSMACRO, and TSOMAC. Issue the command: GLOBAL MACLIB DMSSP CMSLIB OSMACRO TSOMAC 4. Assemble the source files: ASSEMBLE KERMIT ASSEMBLE KERMBOOT These commands generate relocatable object files KERMIT TEXT and KERMBOOT TEXT. You should be sure to examine IKCKER.BWR to find out what, if any, updates should be applied to the Kermit source. If necessary, follow the instructions there to obtain the corrected object file KERMIT TEXT. 5. There are 4 choices for installing the runnable modules, of which the last (and best) is available starting with VM/SP Release 4: a) Install the Kermit-CMS program alone, to run in low memory. This means it can't invoke some programs beneath itself (see the DOC file for more information about this): LOAD KERMIT GENMOD KERMIT MODULE Y2 b) Install the Kermit bootstrap program alone. This loads the KERMIT TEXT object file into high memory, allowing it to run any other programs beneath itself: LOAD KERMBOOT GENMOD KERMIT MODULE Y2 COPY KERMIT TEXT A = = Y2 c) Install both, to give users a choice: LOAD KERMIT GENMOD KERMIT MODULE Y2 LOAD KERMBOOT GENMOD KERMBOOT MODULE Y2 COPY KERMIT TEXT A = = Y2 d) With VM/SP Release 4 and later, create a dual-purpose module. Note: with VM/SP Release 5, KERMBOOT will no longer work, and this method is the only recommended method: LOAD KERMIT (RLDSAVE GENMOD KERMIT MODULE Y2 The module created this way may be permanently pre-loaded by the user as follows: NUCXLOAD KERMIT 6. To run Kermit-CMS, simply type "KERMIT" to the CMS system prompt. There is an alternative procedure for assembling Kermit. Instead of steps 3 and 4 above, perform the following: a. Create a file called KERMIT COPY A (RECFM F, LRECL 80) containing one line with "*COPY KERMIT" in columns 1-12. b. Create a file called $KERMIT ASSEMBLE A (also RECFM F, LRECL 80) containing the following text (the K in KERMIT marks column 1): KERMIT TITLE 'Kermit for IBM 370 VM/CMS' * See the version and system symbols below under 'Constants' * Copyright (C) 1982, 1985 Columbia University * Permission is granted to any individual or institution to copy or * use this program, except for explicitly commercial purposes. * COPY IK0DEF COPY IK0MAI COPY IK0COM COPY IK0CMD COPY IKCUTL COPY IK0PRO c. Issue the commands COPY KERMIT ASSEMBLE A KERMIT COPY A (APP MACLIB GEN KERMIT KERMIT GLOBAL MACLIB KERMIT DMSSP CMSLIB OSMACRO TSOMAC ASSEMBLE $KERMIT ASSEMBLE KERMBOOT ERASE KERMIT TEXT RENAME $KERMIT TEXT A KERMIT = = The foregoing alternate procedure produces the same object module, but leaves the maintenance history and macro definitions out of the assembly listing. The IBM mainframe and its communications front end (3705, 7171, etc.) usually require that parity be used by any asynchronous ASCII device that wishes to communicate with it. Exactly which kind of parity is site-dependent. At Columbia, the 3705 requires Mark parity, and the 7171 requires Even parity. Make sure your users know to use the appropriate parity setting, as well as any other settings required for IBM mainframe communication (see p.36-39 of the Kermit book). Kermit-CMS uses an ASCII/EBCDIC translation table which conforms to the one given in the IBM System/370 Reference Summary. If your site's translation table does not conform to the one Kermit uses, then enter the appropriate SET ATOE/ETOA/TATOE/TETOA commands in the SYSTEM KERMINI file. If your system's ASCII/EBCDIC translation is not invertible, Kermit will not and cannot work unless you change your system's table. See the DOC files for more information. When CMS Kermit is to be used with a 7171, make sure the 7171 is set up with its "keyboard lock delay" parameter set to 0. Otherwise, the "terminal" will hang whenever CMS Kermit clears the screen. This happens consistently when the parameter is set to 10, and not at all when set to 0. For numbers in between, the higher the number, the more it happens. --------------------------------------------------------------------