
========> [LT89A.AVEN_MAKE]AAAREADME.TXT;1 <========




        The contents of this directory constitute MAKE/VMS version 3.4
        by  Todd  Aven/the Software Sweatshop. This   is  a  UNIX make
        look-alike optimized for the VMS environment.  Much effort has
        been expended  to keep  makefiles as closely   compatible with
        UNIX  makefiles as  possible,  but some  differences naturally
        arise.

        Please  refer to  MAKE.DOC or MAKE.HLP  for online information
        about  MAKE. The most recent  modifications  are documented in
        RELEASE.V33.

        Two example makefiles are provided,  MAKEFILE. and  PMDF.MAKE.
        Simply running MAKE.EXE *should* rebuild MAKE (if necessary).

        Comments, suggestions, and bug reports should be directed to
        one of  the addresses at the end of MAKE.DOC.

        Todd Aven
        6/1/89

========> [LT89A.BAUER]AAAREADME.TXT;1 <========



---------------------------------------------------------------------------
Space Telescope Science Institute Tools Group DECUS Atlanta '89 Submissions
---------------------------------------------------------------------------

This saveset contains all source, objects, and executables for a series
of tools developed in the OSB Tool Group at the Space Telescope Science 
Institue in Baltimore Md.  

The source languages include VAX C, FORTRAN, SCAN, MACRo, and MESSAGE.  
If you do not have one of these compilers, yuo can still link with the objects.

There are LaTeX documents for most of the tools also included.  The
LaTeX include files have also been included should you want to try
to LaTeX these.

Some of the tools have logical names associated with them that you will
need to define before running/building the tool.

Tool descriptions follow:

===========================================================================

Tool:           Check Map (CKMAP) Tool

Description:    The CKMAP tool scans a VMS link map for PSECT 
                mismatches and undefined symbols and reports 
                these accordingly.

===========================================================================

Tool:           Disk Report Tool

Description:    The Disk Report tool scans one or more directory log files 
                creating a series of reports summarizing disk space 
                utilization.

===========================================================================

Tool:           Show Merged CMS Classes

Description:    The Show Merged CMS Classes tool compares all of the elements
                in a CMS library class (typically an SPR class) to see if they 
                are also inserted, or ``merged'' into another class (typically 
                a PENDING class) in that same CMS library.


===========================================================================

Tool:           Image Definition Tool (IMGDEF)

Description:    An image definition file contains the information on how 
                to build an executable image.  It is the primary input to 
                IMGDEF, which is used to produce an options file, an MMS 
                file to describe the LINK process, and an MMS file for 
                building the image and its components. 

                                                                Page 2



===========================================================================

Tool:           Remote CMS Server

Description:    The Remote CMS tool provides an interface to CMS libraries 
                on a different DECnet node.  This lets the user issue CMS 
                commands that access a CMS library on a different VAX 
                without having to log onto that node.

===========================================================================

Tool:           DCOPY Tool (Delete/Copy Tool)

Description:    The DCOPY is a modified version of the VMS COPY command that
                deletes a file in the destination directory before it copies 
                into it. Before it copies the file to the destination 
                directory, it checks for the existence of the file, and if it 
                exists already AND the revision date of the existing file is 
                older than the revision date on the file to be copied, DCOPY 
                deletes the file.  This is useful when disk space is tight on 
                the destination device.  Stretched logicals are also supported 
                such that only the first version of a file is copied over a 
                stretched directory list.

===========================================================================

Tool:           MMS Generator For Source (MMSGEN)

Description:    The MMSGEN tool is used to generate a compile MMS for files 
                with the following extensions:  .FOR, .EQF, .EQE, .FBL, .C, 
                .SCN, .MSG, .MAR, .MBL, .X.  It scans one or more input 
                files creating one or more MMS files with the correct 
                dependency list and action lines to build or compile to target
                object file.

===========================================================================

Tool:           Link Check Tool (LNKCHK)

Description:    
                The Link Check tool verifies the existence of all input 
                files on a link command, passing the command onto the Linker 
                if all inputs exist.  Link Check is a workaround for a bug 
                in the Linker that causes it to go into an endless loop when 
                processing many objects with logical searchlists when one of 
                the objects is missing (either from the command line or an 
                options file).

===========================================================================

========> [LT89A.GNUSOFTWARE]AAAREADME.TXT;1 <========



GNU Software

This area contains several programs from the Free Software Foundation,
a group working on a complete replacement for Un*x which will solve
performance and reliability problems with the Un*x OS and add new
functionality.
        Included are BISON (a YACC superset), an AWK, Gnu Emacs,
Gnu C, Gnu C++, and several more. The VMS binaries for a bootstrap
Gnu C for VMS are included also.
        Also included are VMS ports of GAWK, BISON, and GNU Grep.
        Please note that these utilities are primarily for GNU with
VMS variants in some cases. Also, Gnu C is a BETA version. It is fairly
usable nonetheless, and version 1.34 here is quite recent. The diffs
to go to 1.35 GCC are present, but GCC 1.35 does not compile itself
under VMS (yet) so is not included. GCC 1.34 for VMS is here.
        When Gnu C finishes compiling all of Berkeley Un*x, it will
be called a "real" C. (This effort is reportedly going very well.)
        Gnu C has been reported to generate much better code than
VAX11 C and to emulate Un*x C better also.
        Complete sources to all files are present, but are presented
in compressed TAR saveset form. Tools able to pull these distributions
apart under VMS are furnished in the [vax000.tools] directory on these
tapes.
        Various messages from the GNU Mailing lists can be found in the
ZOO archive CHANGES_CORRECTIONS.ZOO.  Use the ZOO executable found in
[VAXLT_89A.TOOLS] to read the ZOO file.

        Thanks to Richard Stallman et. al. for this software.

========> [LT89A.LOMASKY]AAAREADME.TXT;3 <========



AAAREADME.TXT                                           V1.0 5/3/89

This directory contains the actual BASIC Source files that were
referenced at the DECUS 1989 Spring Symposium held at Atlanta, GA.
during the "LT029 - VAX BASIC Toolkit of Useful Callable Functions"
session.

These routines form the beginning of a "Toolkit" of useful and
frequently-used functions that VAX BASIC programmers may need.

These functions can be compiled and linked into any VAX BASIC
program (or any other VAX language, as long as you take into
account the subtleties and differences between the languages).

See AAAREADME.ABSTRACT for a description of all of the contained
functions.

========> [LT89A.MDRAW]AAAREADME.TXT;2 <========



This contains the initial release of MDRAW code and assorted utilities.

Included are source files and executable for mdraw itself along with
the converter for mdraw files into sixel files.

Also included are files describing how to set up and how to use mdraw. These
come in TeX format and in plain text. The user guide is in `help.txt' and
the setup stuff is in `start.txt'.

There is a command file start.com which sets up the directories needed and 
the symbols and logicals that need to be set up. (Hows that for repetitive 
redundancy?) Just change the directory path and anything else you like.

There is a directory `[.samples]' that has, guess what, samples in it.
There is a read.me in there describing how to look at them and print them
out, once mdraw and company is set up.

If problems arise, or major bugs strike, feel free to contact me at:

        S. Mike Dierken
        (206) 885 8408
        Sundstrand Data Control
        P.O 97001
        M/S 25
        Redmond, WA 98073-9701

Note: 
 The two fortran programs are slight modifications of the originals from a 
 previous DECUS tape. The previous author (Strickland) is in no way responsible
 for anything that might go wrong. Nothing should go wrong, but if it does, 
 complain to me. Thank you.


========> [LT89A.MEMOREX_TELEX]AAAREADME.TXT;1 <========




                DECUS Submissions from
                        Memorex Telex 3270 Networks
                        3301 Terminal Drive
                        Raleigh, North Carolina 27604

        The Spring '89 submission consists of two directories:


     [.ethernet]   Contains a couple of programs for monitoring network
                   traffic on an Ethernet.

     [.sde]        The latest version of the Software Development Environment
                   we use at Memorex Telex.  SDE is a general model software
                   development methodology that incorporates DEC/CMS and
                   DEC/MMS.


        Further documentation is included in the AAAREADME files found in
        each of these subdirectories.

========> [LT89A.REMTAB]AAAREADME.TXT;1 <========





                                R E M T A B


                      REMOTE TABLE HANDLING ROUTINES

                                Version 2.0

                              September, 1988

                             INTRODUCTION



WHAT IS REMTAB?

REMTAB is a collection of routines written in VAX COBOL and MACRO that
were  designed to ease the task of dealing with static and semi-static
data definitions that are used by multiple programs.   These  routines
were  developed  by  TERADYNE,  Inc.   in  conjunction with a VAX DBMS
application  which  is  now  used  by  Teradyne's   Customer   Service
Organization.

Early on in the development cycle of the  system  we  determined  that
there  would  be  certain types of data that we would need to maintain
that would not require any or would require very  little  in  the  way
modifications.   We  quickly  learned that a DBMS database was not the
kind of place to be storing these small data  sets.   We  experimented
with  the idea of having separate RMS files for each table and decided
that this too was not going to suffice.  In both  cases  the  overhead
involved in loading the tables was too costly.  In certain programs up
to ten different tables would need to be loaded and in the case of the
RMS  file  idea  the amount of time invloved in simply opening each of
the separate table files was sufficient enough that we decided to look
at other alternatives.

The Remote Table concept soon started to evolve.  Our  first  attempts
were much better than the RMS file concept but it was still taking too
long to load all of the tables  required  by  certain  programs.   The
subroutine  that  loaded  the  tables  was  written  in  COBOL  and we
determined that this was likely part of the problem.  After  scrapping
the  table  loader  module and rewritting it in VAX MACRO we noticed a
considerable improvement over  the  prior  version.   Finally  we  has
something we could use.

========> [LT89A.TEX]AAAREADME.TXT;1 <========



Here are some TeXware items that didn't make it on to the February 1989
DECUS TeX Collection.  The files ending in .TAR_LZW are compressed Tar
files from UNIX.

SPIDERWEB is a utility to generate versions of WEB for different languages.

TEXPS-R1 is a TeX DVI to postscript system that will use the built in
postscript fonts.

TEXX_2_8_6 is a X11 Windows previewer for TeX DVI files.

MAKEINDEX is a LaTeX utility for creating indexes ported to VMS.

PROFILE is a program to profile PASCAL programs.

XDVI is a port of the DVI viewer for X windows to DEC Windows.

========> [LT89A.TPUVI_V5]AAAREADME.TXT;1 <========

This is a clone of the Vi editor written in TPU; this version runs under
VMS V5 and its' flavor of TPU. Complete sources, documents, and executable
are present.

------------------------
Gregg Wonderly
Department of Mathematics
Oklahoma State University

INTERNET:      gregg@nemo.math.okstate.edu
UUCP:          {ihnp4, rutgers, isucs1}!okstate!nemo.math.okstate.edu!gregg

US MAIL:
401 Mathematical Sciences
Oklahoma State University
Stillwater, OK  74078


========> [LT89A.XEVE5]AAAREADME.TXT;3 <========



                                 submitted by:


                                   Tom Wolfe
                           Jet Propulsion Laboratory
                               Mail Stop 510/202
                              4800 Oak Grove Drive
                              Pasadena, CA  91109
                                 (818) 397-9280

                            My Extended EVE Editor.

     This is the VAX/VMS 5.x version of the the XEVE spelling checker.

     Some of the other edit functin in the 4.x version  of  XEVE  have  not
     been conver to 5.x and are not included in this distribution.

     The XEVE spelling checker includes the following:

     Three dictionaries are used to test the spelling of words.   A  common
     dictionary  (standard  english words), a project dictionary (acronyms,
     etc).  and a user defined dictionary.  The user defined dictionary can
     be  created/updated  while  in  an  EVE  edit  session.  Utilities are
     provided to build all three dictionaries from  text  files  containing
     one  word  per  line.   The source word file for the common dictionary
     must be in ascending (lexical)  sort  order.   The  project  and  user
     source word files do not.

     The EVE spelling checker also has special commands that understands  a
     little about C, DCL, FORTRAN, DCL and MACRO source code files and only
     checks appropriate things.  For example, The "SPELL  FORTRAN"  command
     checks only comments and character constants.  The special command are
     currently very primitive.

     A separate (standalone)  spelling  checker  patterned  after  the  LBL
     software tools SPELL utility is also available.

     The common dictionary currently contains 91,000+ words.

     The project dictionary can contain 1,000 word (or 10,000 bytes).

     The user dictionary can contain 200 words (or 2,000 bytes).

     The maximum word size is currently 31 bytes.

     Documentation can be found in the file XEVE.MEM.

        Editor's note:
        In the interests of gaining a bit of (badly needed) space, the file
COMMON.DICT was put into a VMS BACKUP saveset with the command
$ BACKUP/BLOCK=4096 COMMON.DICT COMMONDICT.BCK/SAVE
  and was compressed with the LZCOMP tool. It may be decompressed with the
command
$ LZDCMP COMMONDICT.BCK_LZW COMMONDICT.BCK
and the original file restored. This has brought the storage from over 6000
blocks to about 1300.

