C-KERMIT 5A INSTALLATION INSTRUCTIONS FOR STRATUS VOS -*-text-*- 5A(190) Thursday Jan 20, 1994 David Lane F. da Cruz, Columbia University Copyright (C) 1985, 1994, Trustees of Columbia University in the City of New York. The C-Kermit software may not be, in whole or in part, licensed or sold for profit as a software product itself, nor may it be included in or distributed with commercial products or otherwise distributed by commercial concerns to their clients or customers without written permission of the Office of Kermit Development and Distribution, Columbia University. This copyright notice must not be removed, altered, or obscured. DISCLAIMER: The C-Kermit software is provided in source code form by Kermit Development and Distribution, Columbia University. The software is provided "as is;" no other warranty is provided, express or implied, including without limitations, any implied warranty of merchantability or implied warranty of fitness for a particular purpose. Neither Columbia University nor any of the contributors to the C-Kermit development effort, including, but not limited to, AT&T, Digital Equipment Corporation, Data General Corporation, or International Business Machines Corporation, warrant C-Kermit software or documentation in any way. In addition, neither the authors of any Kermit programs, publications or documentation, nor Columbia University nor any contributing institutions or individuals acknowledge any liability resulting from program or documentation errors. DOCUMENTATION C-Kermit 5A is documented in the book "Using C-Kermit" by Frank da Cruz and Christine M. Gianone, Digital Press, Burlington, MA, USA. Price: US $34.95. Available at book and computer stores, or to order from Columbia University, call +1 212 854-3703. OVERVIEW This file contains VOS-specific information. For a description of general (system-independent) configuration options for C-Kermit, please read the file CKCCFG.DOC. For information about known limitations or bugs, and possible workarounds, see the files CKCKER.BWR and CKUKER.BWR. Once you have built C-Kermit according to the instructions in this file, you should install it in a directory that is in the users' library paths, but that is not likely to be overwritten when you install a new version of the operating system. A good candidate would be >system>application_library. It might also be a good idea to make a "Kermit library" directory for sample files and non-man-page-style documentation. (master_disk)>kermit might be a good place for this. Some of the files that could go there are: ckermit.ini The standard initialization file. Users should copy this to their home directories. (In C-Kermit 5A(190), you can designate a single copy as the system-wide initialization file; details below). ckermod.ini A sample customization file. Users should copy this file to their home directories, and make any desired modifications (user- or site-specific customizations). ckermit.kdd A sample dialing directory file. ckermit.ksd A sample services directory. ckermit.env A sample "environment variable" file ckedemo.ini Macro definitions from "Using C-Kermit". ckevt.ini Command file to demonstrate special screen effects from "Using C-Kermit" ckcker.upd A file listing the updates, changes, and corrections made to C-Kermit since publication of "Using C-Kermit". ckcker.bwr The general C-Kermit beware file. ckuker.bwr The UNIX-specific C-Kermit beware file. READING A C-KERMIT DISTRIBUTION TAPE If you have received C-Kermit on tape from Columbia University, it will most likely be written as ANSI labeled, and certainly is not VOS save format. To read the files onto your system, do something like this, substituting your tape device name and supplying the density written on the tape. create_dir kermit_tape change_current_dir kermit_tape attach_port tape %s1#mt1.0 mount_tape tape -tape_format ansi -density 1600 -access_rights readonly If your site is not running system_operator, the mount_tape command will ask if it has understood your command line and show you what it thinks you want; if the information looks good, say yes to mount the tape volume. It will then show you the information on the ANSI tape label, and ask if that information is correct. If it is, say yes, to proceed to use the loaded tape. read_tape tape -file_ids * detach_port tape You should at this point have all the files on the tape in your kermit_tape directory, and can procede to either build C-Kermit yourself, or use the pre-built version on the tape. BUILDING C-KERMIT FOR VOS VOS C-Kermit is built with a command macro called cklmak.cm. This macro recompiles and binds ALL the modules involved. It does allow you to build into a different directory than the one containing the sources, so you can build for different machines into different directories if you need to. If you want to define a system-wide initialization file for C-Kermit, rather than making each user have her/his own copy, define the symbol CK_SYSINI to be the full pathname of the file, in the -kermit_options add: 'CK_SYSINI %s1#m1_d01>kermit>ckermit.ini' It is important that the string above get quoted properly, so if you are using a command line to do this it would come out something like: cklmak -kermit_options 'STRATUS DYNAMIC DCMDBUF CLSOPEN STRATUSX25 &+ ''CK_SYSINI %s1#m1_d01>kermit>ckermit.ini''' Note: if you build Kermit to execute a system-wide initialization file, this file can (and probably should) (be modified to) "chain" to the user's own initialization file (if any) by ending (or starting, depending on the desired precedence) with a command like: if exist \v(home)ckermit.ini take \v(home)ckermit.ini After you have built and tested the C-Kermit program successfully, you can discard the object (ck*.obj) files, which are no longer needed. Then you can copy the program modules to an application directory. There are several utility programs that come with C-Kermit you may or may not want. Most of them have documentation files (*.doc) that come along that explain what they are for. None of them are vital to using C-Kermit, though some are required to build it; these are built by cklmake.cm whether you ask for them or not. You can have cklmak delete the required files and not build the others by specifying -no_tools, but generally they are helpful programs to have. IF YOU DO NOT HAVE A C COMPILER Some of the files that come with the C-Kermit distribution are hex-coded versions of the compiled and bound C-Kermit executables. Versions are provided for both the 68k and i860 processors. To bootstrap C-Kermit onto your system, you only need the command macro cklxtr.cm and the hex file for C-Kermit itself; the name of that file will vary depending on your processor type. The basename will be cklker, and the suffix will be .h68 for 68k machines, and .h86 for i860 machines. Also included is hex version of a compiled extraction program, which runs much faster than the command macro version. Use the command macro to convert the conversion program and the compiled program to extract the main C-Kermit program. The extraction program is called cklxtr.pm, and is made from the appropriate hex file. Both the command macro and the program take two positional parameters, the input file, and the output file. The input file is the hex coded version of the program and the output file is resulting program module. The C source for the hex-ifying program is also included. After unloading all the necessary files into a directory, presumably using read_tape, convert the compiled conversion program (use the appropriate suffix for your system type): cklxtr cklxtr.h86 extract.pm Then extract C-Kermit: extract.pm cklker.h86 kermit.pm If you get an error that says something like "This program contains instructions not available on this processor," the most likely cause is that you have extracted the 68k program on a i860 machine or vice versa. Change the suffixes and try it again. The file formats used by the command macro and by the program are identical, so you can simply extract C-Kermit directly, but this two step process can save a great deal of time. The C-Kermit versions that are included in hex format are built without symbol tables, with optimization, and include support for X.25 and TCP/IP networking.