DECUS Essential Tools Collection, 1996 for OpenVMS Alpha and OpenVMS VAX (VS0174)
Files in this directory:
AAAREADME.DOC This file.
AAAREADME.TOO Revision information.
KILL.ALPHA_OBJ AXP object file for KILL.B32.
KILL.CLD CDU file for the KILL command (to add to a command
table).
KILL.HLP HELP text for the KILL command.
KILL.OBJ VAX object file for KILL.B32.
KILL_CLD.ALPHA_OBJ AXP object file for KILL_CLD.CLD.
KILL_CLD.OBJ VAX object file for KILL_CLD.CLD.
KILL_MSG.ALPHA_OBJ AXP object file for KILL_MSG.MSG.
KILL_MSG.OBJ VAX object file for KILL_MSG.MSG.
LINK.COM Command procedure to build KILL.EXE.
Files in [.SOURCE]:
DESCRIP.MMS MMS file to build KILL.
FIELDS.R32 Matt Madison's field macros.
KILL.B32 BLISS source for KILL.
KILL.SDML DOCUMENT source file for KILL.HLP.
KILL_CLD.CLD CDU file for the KILL command (linked into KILL.EXE).
KILL_DEFS.R32 Structure definitions for KILL.B32.
KILL_MSG.MSG KILL MESSAGE file.
BUILDING KILL.EXE
KILL.EXE is generated from the KILL, KILL_CLD, and KILL_MSG object files.
A command procedure, LINK.COM, is provided to link these object files. It
will create an OpenVMS VAX executable when executed under OpenVMS VAX and
an OpenVMS AXP executable when executed unter OpenVMS AXP.
SETTING UP THE KILL COMMAND
The KILL command can be set up as either a DCL verb or a foreign command.
KILL.CLD has been provided to set up KILL as a DCL verb. For information
on adding verbs to a command table, see the documentation on the SET
COMMAND command. You will need to edit KILL.CLD and change the line
IMAGE MADGOAT_ROOT:[EXE]KILL.EXE
if this is not where you put KILL.EXE. To set up KILL as a foreign
command, you need to define a symbol that points to KILL.EXE. For example,
$ KILL:==$MADGOAT_ROOT:[EXE]KILL.EXE
This symbol should be defined in a command procedure that will be executed
by the segment of the user population that needs access to KILL.
COPYRIGHT NOTICE
This software is COPYRIGHT © 1993.1994 MADGOAT SOFTWARE. ALL RIGHTS RESERVED.
Permission is granted for not-for-profit redistribution, provided all
source and object code remain unchanged from the original distribution, and
that all copyright notices remain intact.
DISCLAIMER
This software is provided "AS IS". The author and MadGoat Software make no
representations or warranties with repsect to the software and specifically
disclaim any implied warranties of merchantability or fitness for any
particular purpose.
MADGOAT SOFTWARE MAILING LISTS
MadGoat Software has set up the following mailing lists for discussions and
support of its products:
Info-MadGoat@wkuvx1.wku.edu
Discussion of MadGoat Software products by users and MadGoat
developers. To subscribe, send a message to
Info-MadGoat-Request@wkuvx1.wku.edu
with the word SUBSCRIBE in the first line of the body of the
message.
MadGoat-Announce@wkuvx1.wku.edu
Announcements of new releases and new products from MadGoat.
To subscribe, send a message to
MadGoat-Announce-Request@wkuvx1.wku.edu
with the word SUBSCRIBE in the first line of the body of the
message.
MadGoat-Bugs@wkuvx1.wku.edu
Address for reporting bugs in MadGoat Software products. Please
include the name of the package and version in the subject header
of the message, so the report can be more easily directed to the
appropriate developer.
MadGoat-Register@wkuvx1.wku.edu
Address for registering your use of MadGoat Software. Registration
of your installation is at your discretion and is used by MadGoat
Software only to determine the size of the user base for each product
and the future directions of the products.
To register, simply mail a message to:
MadGoat-Register@WKUVX1.WKU.EDU
with the following information:
Installer's name
Company name and address
System(s) on which the MadGoat software is running
Which products you're using
Any comments and/or suggestions you might have
Darrell Burkhead burkhdr@wkuvx1.wku.edu
Click on FTP to download from the FTP archives.
![[FTP]](http://www2.encompassus.org/hidedecus/graphics/i_ftp.gif)