Don Amby's SYS$LOGIN Environment V1.0-7
               ---------------------------------------

         Donald E. Amby
         Delco Systems Operations
         P.O. Box 471, M/S 1A21
         Milwaukee, WI 53201
         (414)768-2682 or (414)281-1296
         Amby%Wizard.GM@Hac2Arpa.Hac.Com         (Internet)
         AMBY                                    (DECUServe)
         AMBY                                    (DCS)

This directory is the root of my (Don Amby) login  environment,  which
has  a  LOGIN.COM  file  that  is  run  at login time. There is also a
SETUP.COM file that defines all of my logical names,  global  symbols,
keys, etc. that define my working environment.

These were designed to function on the VAXcluster where I do all of my
real work, and these files expect certain things to be defined (in the
system logical name table).

1  Backgound

Many years ago I adopted  the  convention  of  making  software  tools
available  as part of a set of tools, which I refer to as a 'toolkit'.
Basically, a toolkit refers to  a  directory  somewhere  in  the  file
system where there is to be found a SETUP.COM file that you can run.

Running this SETUP.COM file will then define all that you need to make
the   tools  in  the  toolkit  available.  This  typically  means  the
definition of logical names (in order to point to files,  directories,
etc.) and global symbols (to run *.COM or *.EXE files that implement a
tool). In addition, sometimes it may use a Command Definition  Utility
(CDU)  to  define  new  DCL  command verbs (with the SET COMMAND and a
*.CLD file).

Much of this philosophy is the result of some of the good things  that
I have seen on numerous DECUS SIG tapes.

A goal of mine has always been to make tools as portable as  possible,
across  VAX/VMS systems (running the same version of VMS). I currently
am running VMS V5.3-1, so I would expect everything to work on similar
systems.