========> [VAX84A]AAAREADME.TXT;3 <========


  SPRING 1984 VAX SYSTEMS SIG SYMPOSIUM TAPE (CINCINNATI)




                       assembled by:
                        Joe Bingham
                 VAX Systems SIG Librarian
                   ManTech International
                       2320 Mill Road
                    Alexandria, VA 22314
                       (703) 838 5600





     Someone asked me in Cincinnati what I did to  the  tape
and  why  it  took so long to get it out.  I am afraid I did
not give a very satisfactory answer, partly because  what  I
do  does  not  seem  like  very  much  when you look at each
submission individually.  It is  a  little  more  impressive
when  you realize that this tape comprises 42 submissions in
299 directories, a total of 5629 files with a total size  of
109703  blocks.   I  must  admit  that  when  you log on the
computer to work on something that size it is intimidating -
it's easy to decide that EMPIRE is a better way to spend the
evening.

     First a little about what I do not do.

      .  I do not  reword  the  authors  remarks  about  his
         submission.   I may occasionally correct a spelling
         error if I have to  edit  the  file  for  something
         else,  but  I  do  not  look for spelling errors to
         correct.  If I have to construct the  AAAREADME.TXT
         file  I  try  to  extract the author's words from a
         documentation file or from program comments.

      .  I do not try to verify that the programs  will  run
         on a VAX, much less try to verify that they do what
         the author says they do.  I may try something  that
         strikes  my fancy as I go through the material and,
         if  I  have  problems  I  will  say   so   in   the
         AAAREADME.TXT.

      .  As a rule I do not restructure the submissions.  On
         the  Fall  1983 tape I did bring games out to there
         own  directory  tree  and   I   put   the   command
         procedures/programs  used  to  do the "SET DEFAULT"
         command into their own structure.   I  did  not  do
         anything like that with this tape.

Now for a little more about what I do do in constructing the
tape:
                                                      Page 2


      .  First we consolidate  the  submissions  by  copying
         them to disk and back to the tapes I take home with
         me.  We usually get the  bulk  of  this  work  done
         Tuesday  evening,  leaving  some  time  to  resolve
         problems and plenty of time for people to  pick  up
         their  tapes  before  the exhibition hall closes on
         Friday afternoon.  This time I was assisted by  Tom
         Gerhard  of  Advanced Data Management and Al Zirkle
         of the Naval Surface  Weapons  Center.   Everything
         else is done after the symposium.

      .  I try to find a name for the subdirectory  which  I
         think  will  be  meaningful  to  most of the people
         using the tape.  This is usually the  company  name
         or  an  abbreviation  of  it, especially for large,
         multi-category    submissions.     (Examples    are
         FORDAERO,  BATTELLE, GEMEC.) If I can find one name
         to describe the submission, usually a name provided
         by  the  author,  I  use it.  (Examples are RMTPRT,
         PLOTS, SLIDES.)  One  name  used  this  time  is  a
         combination of these methods - SAOSTOIC.  Usually a
         resubmission  will  have  the  same  name  as   the
         submission  it replaces, but that is violated three
         times (that I am aware of) on this tape - SAO  used
         the  name  SAOSTOIC  in their submission and I went
         along with it, the LBLTOOLS submittor  requested  a
         name   change  to  SWTOOLS,  and  Glenn  Everhart's
         PORTACALC spreadsheet is under SHEET.

      .  I do what I can to reduce the size of the  tape  by
         deleting  listing  files, compressing libraries and
         truncating files.  I do not generally delete things
         which  appear to be redundant because it is hard to
         be sure that they really  are.   I  did  delete  an
         entire  subdirectory  this  time - PSDI submitted a
         directory of KERMIT material  which  as  far  as  I
         could tell was also in the KERMIT submissions.

      .  I make sure that each first level subdirectory  has
         a  AAAREADME.TXT  file  which briefly describes the
         contents of the submission.  If there is a suitable
         file  by  another name I rename it.  If there is no
         suitable file  I  construct  one.   This  is  where
         submittors  can  help  the  most about making their
         submission easy to integrate into the tape.  It  is
         suggested that you use runoff to produce this file.
         [VAX000]TEMPLATE.RNO contains the suggested runnoff
         skeleton.

              The [VAX000]BUILDREAD command  procedure  will
         concatenate these files into a very nice summary of
         the tape.
                                                      Page 3


      .  I try to identify  other  documentation  files  and
         ensure that they have a .DOC extension, renaming as
         necessary.  DIRECTORY  [VAX84A...]*.DOC  will  give
         you a pretty good idea what documentation is on the
         tape.  However, look for comments  inside  programs
         and  watch  out  for the cases I have overlooked or
         chosen not to rename.

      .  Tom Gerhard then generates a new composite index of
         the  VAX  SIG  tapes  and  of  this  tape.   We are
         changing the algorithm for generating  the  indexes
         this  time  and  hope  to have shorter, but just as
         useful, index files.


     At the Tapecopy User's Forum session in Cincinnati  the
submissions  were referred to by submission number.  For the
benefit of those of you who were there  or  have  the  audio
tape  of  the  session  here is a table which can be used to
cross submission number to the directory name  used  on  the
SIG tape.  An X next to the submission number means that the
author was at the Forum and made  some  comments  about  his
submission.

SUBMISSION      SUBMITTOR       ORGANIZATION            SUBDIRECTORY NAME
NUMBER

1       Thurston Carleton       NASA/GSFC               GODDRD

3       Glenn Everhart          RCA                     SPREAD

4       Frank Nagy              Fermilab                FERMILAB

5       Erick Husby             Project Software        PSDI

6       John Beasley            Westinghouse            RMTPRT

8  X    Louis Krupp             Univ of Denver          UDENVER

9       Walter Schmeichel       NWSC Crane              PLOTS

10      Kathleen Morse          DEC                     SLIDES

17 X    Ted Frohling            Mountain States         DIGITIZER

19 X    Scott Sibley            Ford Aerospace          FORDAERO

20      Eric Ogren              DEC                     DTRWHIZ

21 X    Allen Watson            Bergen Record           RECORD

25      James Downward          KMS Fusion              KMSKIT

27      John Briggs             SPACECOM                LOGINDATE

                                                      Page 4


28 X    Richard Garland         Columbia University     VAXDIAL

29 X    Richard Garland         Columbia University     KERMIT (partialy 
                                                        replaced by 58 and 78.

31      Mark Oakley             Battelle Columbus       BATTELLE

32      Thomas Hahaney          Naval Air Propulsion    DISASTER
                                Center

33      Eric Scott              Jet Propulsion Lab      JPLVLSI

34      Mark Vevle              Univ of Alabama in      RMDEMO
                                Birmingham

35 X    Robert Harris           Leeds & Northrup        LN

39      Dennis Jensen           Ames Labortory          HGRAPH
                                ISU/USDOE

41      Peter George            DEC                     DEALLOC

43      Robert L. Boyd          GE Microelectronics     GEMEC
                                Center

48 X    Alan Zirkle             Naval Serface Weapons   NSWC
                                Center

50 X    Dennis Fitzgerald       Computer Sciences       CSC
                                Corporation

52 X    Mark Frank              Washington Univ Med     RMS
                                School

53      Tom Gerhard             Advanced Data           ADM
                                Management

56      Keven Mallory           Texas Inst              TI

57      Robert Wells            TDC                     DFWLUG

58      Nick Bush               Stevens Institute       KERMIT.KERMIT10
                                                        KERMIT.PROKERMIT
                                                        KERMIT.VMSKERMIT

59 X    David Johnson           Synertek Inc            ARGUS

61      Larry Kilgallen                                 PAGESWP

63      John Heffernan          RCA/AS                  PASCALUSE

64      Roger Hauck             Smithsonian Astro-      SAOSTOIC
                                physical Observatory

65      Fredrick Knight         Smithsonian Astro-      NAMELIST
                                                      Page 5


                                physical Observertory

66 X    Steve Swenson           Harris Farinon          HARRIS

67      Kevin Carosso           Hughes Aircraft Co      HUGHESSCG

70 X    Scott Smith             Telex Computer          HEX
                                Products

71 X    John Clement            Bonner Lab              BONNER

72 X    Frank Roberson          System Dev Corp         SDC

78      Brian Nelson            Univ of Toledo          KERMIT.PDP11

        David Martin            Hughes Aircraft Co      SWTOOLS

        Frank Borger            Reese Medical Center    RSXSIG
========> [VAX84A.ADM]AAAREADME.TXT;1 <========


 Files on this directory were submitted by:

           Tom Gerhard (VTERM and DISKUSE)
           Advanced Data Management
           P.O. Box 601
           15 Main Street
           Kingston, NJ  08528
           (609) 799-4600
           Pete Herrick (PFL)
           same address and phone

 The submissions on this directory include:

  o  VTERM -  A  virtual  terminal  emulator  program  which
     allows  use of an auto-dial modem and VAX terminal port
     to communicate with other computers.   In  addition  to
     the  terminal emulation, VTERM can log a remote session
     on your local disk.  VTERM uses an  input  buffer  that
     dynamically  changes  size  to reduce CPU overhead when
     receiving data from the remote computer.  See VTERM.DOC
     for more information.

  o  PFL - A utility to load the function keys  on  a  VT220
     (and presumably VT240) terminal.  The string definition
     may include non-printable characters.  See PFL.DOC  for
     more information.

  o  DISKUSE  -  A  resubmission  of  the  DISKUSE   program
     originally  submitted  on  the  81B  SIG tape.  DISKUSE
     allows a 'soft' disk quota enforcement policy.  The new
     version  includes  a  form  of 'group-wide' disk quota.
     See   also   the   submission    on    the    directory
     [VAX83C.DISKUSE]  for  a  version that handles multiple
     disks.  See the comments in the beginning of the source
     for more information.
========> [VAX84A.ARGUS]AAAREADME.TXT;1 <========


                                David A. Johnson
                                 Synertek, Inc.
                                3001 Stender Way
                             Santa Clara, CA 95054
                                 (408) 988-5839


     ARGUS3 is a complete rewrite of a program I got from  an  earlier  SIG
     tape  which  deletes  users  whose  terminals have gone idle.  The old
     version (the author's identity has been lost in  antiquity)  used  the
     slot,  sequence  number  structure of the PID.  This structure will be
     changing in VMS 4.0;  this rewrite uses a full search of PID,  so  all
     it requires is that PID's be unique.

     The old ARGUS also ignored subprocesses (it was written in the days of
     VMS  2.0).   This  one  will  only consider the end-nodes of a process
     tree;  if the entire tree is idle, it will be pruned from the  outside
     in.

     ARGUS3 is written in PASCAL, and the source is included.
========> [VAX84A.BATTELLE]AAAREADME.TXT;2 <========


                             Battelle's Submissions


                                 submitted by:


             Gary L.  Grebus              Mark D.  Oakley
             Battelle Columbus Labs       Battelle Columbus Labs
             505 King Avenue              505 King Avenue
             Columbus, OH 43201           Columbus, OH 43201
             (614)424-7156                (614)424-5086


     This submission consists of assorted tools and procedures  for  system
     programming and management functions.  The authors would be interested
     in hearing of any problems or  suggestions  which  anyone  might  have
     regarding  these submissions.  As usual, this submission was assembled
     at the last moment.  As a result,  the  documentation  may  be  a  bit
     sketchy.  Please feel free to call if you need further information.

     1.  [.FILES]
         FILES is a program to locate  large  files  stored  on  disk.   It
         understands volume sets and executes quickly by mapping INDEXF.SYS
         into process space.  FILES can also perform a  directory  by  uic.
         This  software will probably break when Version 4 is released, but
         we will try to fix it in time for the next tape.

     2.  [.FINDFILE]
         FINDFILE  is  a  program  to  locate  a  file  given  a   physical
         (cylinder/track/sector)  or  logical  (lbn) address.  The complete
         filespec is returned if a file is  occupying  the  given  address.
         FINDFILE  is  understands  volume sets and runs quickly by mapping
         INDEXF.SYS into process space.  This software will probably  break
         when  Version 4 is released, but we will try to fix it in time for
         the next tape.

     3.  [.PTY] This directory contains  software  to  support  a  "pseudo"
         terminal  (PTY)  device  on a VAX/VMS system.  A PTY is a software
         device similar to a mailbox which properly executes  all  terminal
         specific  I/O functions.  Included is a program which uses the PTY
         device to LOG A TERMINAL SESSION TO A DISK FILE.

     4.  [.REMOTECMD] This directory commands two DCL procedures that allow
         one  to execute DCL commands on a remote node, via DECnet, without
         actually logging in.

========> [VAX84A.BONNER]AAAREADME.TXT;1 <========







                                     ABSTRACT

                              Bonner Lab Runoff (RNO)

     Bonner  Lab Runoff is a text formatter which when used with your favorite
     editor makes a complete word processor.  Its syntax is almost a  complete
     emulation of DSR (Digital Standard Runoff) and it is very compatible with
     previous versions of Runoff.  The intent of this program  is  to  support
     complete  scientific  word  processing  to  produce  publication  quality
     output.  It has been  used  to  produce  thesis,  progress  reports,  and
     scientific papers here at Rice University.  

     This version allows complete control of any special printer available via
     user definable escape sequences.  In addition  a  macro  facility  allows
     text  or  sequences  of commands to be abbreviated to a single label.  If
     the printer has the correct features then variable  spacing,subscripting,
     superscripting, and equation formatting are possible.  By properly defin-
     ing escape sequences  the  user  may  support  different  printers  in  a
     transparent  fashion.   In  other words the same input text will print in
     identical fashion on different printers with different control codes  and
     escape sequences.  

     Table of contents, indexing and sub-indexing are all supported.  Multiple
     table of contents or multiple indexing may be constructed from the avail-
     able  commands.   A  variety  of LAYOUT and STYLE commands may completely
     change the look of the  pages.   Table  layout  is  simplified  by  right
     justified and 'decimal' justified tabs.  Permanent margins which apply to
     the page headers are available.  These simplify the setting of header and
     text margins.  

     This  runs  under  VMS,  RSX, IAS, RT11, TSX, and probably RSTS.  RNO oc-
     cupies a minimum of 31 to 37 kbytes depending on the operating system.  

     BONNER LAB RUNOFF                                                 Page  2
     

     This  distribution  contains all files necessary for building RNO for any
     supported operating systems.  Once you have built the  executable  image,
     you can use it to generate documentation and help files for you operating
     system.  Instructions are in the BUILD.DOC file.  


                                       NOTE

          If  you find any bugs I would appreciate getting a copy of both
          the .RNO and .DOC files containing these bugs.   If  you  could
          isolate the bug and demonstrate it in just a few lines of input
          I would appreciate the effort.  I will try to fix bad  bugs  or
          at  least  create  a workaround.  I will answer letters, but do
          not expect an immediate reply.  If you need fast answers try my
                                                      Page 2


          phone number.  I do not guarantee anything!  


                                                                  John Clement
                                                            Bonner Nuclear Lab
                                                               Rice University
                                                                      Box 1892
                                                             Houston Tx, 77251
                                                                (713) 527-4018

========> [VAX84A.CSC]AAAREADME.TXT;1 <========


This directory is a collector for several sets of programs / command files
developed by the staff of Computer Sciences Corporation at the Goddard
Space Flight Center in Greenbelt, Maryland.  The following subdirectories
are included:

        [.CALC]         Interactive calculator program with full FORTRAN
                        expression syntax and support for most FORTRAN
                        intrinsic functions (SIN, COS, SQRT, etc.).
                        Supports 32 character variable names, is
                        very forgiving of arithmetic and other errors,
                        and has routines to load, dump, list, and
                        edit the internal symbol table.  Supports
                        hexadecimal and octal constants and output.


        [.COMPARE]      Program which compares the contents of two disks
                        or directory trees and produces a report much 
                        like DIFFERENCES/PARALLEL produces.  The
                        comparison is based upon file name, version
                        number, creation and modification date, and 
                        file size.  Since actual file contents are 
                        not checked, COMPARE runs quite fast.


        [.EXP]          Expression parser and interpreter packages with
                        test driver program.  Supports essentially the
                        same expression syntax as the CALC program, but
                        optionally treats the "=" operator as an arithmetic 
                        operator much the way the C language does.  The
                        expression parser and interpreter are coupled 
                        through a reverse polish notation "program"
                        and a set of user-defined symbol table subroutines.
                        (The test driver includes a set of symbol table
                        subroutines based upon the DEC Run-time Library
                        balanced binary tree facility.)


        [.STAT]         A simple statistics subroutine and program.
                        Nothing fancy, but it might save someone a
                        little time looking the formulas up and
                        coding them, etc.  Performs mean, standard
                        deviation, variance, least-squares fit, and
                        correlation coeficient computations.


        [.UTILITY]      A mixed bag of utility programs and command files.
                        Some of these are unique, some are variants on
                        similar utilities from previous tapes, all have
                        built in HELP invoked by a "?" as the first
                        parameter.  See the AAAREADME.TXT file for
                        details.


Please feel free to write or phone (though I am extremely difficult
to get hold of by phone) with any questions, comments, etc.
                                                      Page 2


Point of contact for any questions or comments is:


                Dennis K. Fitzgerald
                Computer Sciences Corporation
                4600 Powder Mill Road
                Beltsville, MD.  20705

                (301) 937 0760 x4166

========> [VAX84A.DEALLOC]AAAREADME.TXT;1 <========


                                 submitted by:
                                  Peter George
                                      DEC
                             ZK1-1/D42 Spitbrook Rd
                                Nashua, NH 03062



     1.  [.DEALLOC]

              This program will prompt for a  device  name,  determine  the
         allocator of the device, and force on him/her/it a deallocation of
         the device.  The forced deallocate is done via a kernel-mode AST.

========> [VAX84A.DFWLUG]AAAREADME.TXT;2 <========


 


                         DFWLUG OVERVIEW




     The following sub-directories hold the contribution from the
DFW Lug area:

     The [.DIGITALSW] sub-directory contains  command  files  for
DELDIR,  which  is  a  delete directory tree program, TELL, which
will execute a single  command  on  a  remote  DECnet  node,  and
SCHEDULER,  which  is a program which will aid in scheduling jobs
at a given time or day of the week.

     The [.NETPRINT] sub-directory contains a rewrite of  REMPRT.
This  version  uses logical names to define printers which belong
to other nodes on a DECNET network.

     The [.OU] sub-directory contains updates to Fall 83  FUN.DIR
directory,   a   command  file  which  will  alert  the  user  of
'unnecessary' files, and aid  in  deleting  them,  and  the  game
MORIA, another DnD type game but a very good one.

     The [.SOHIO] sub-directory contains a collection  of  system
manager  'helpers',  a  modified (for V4.0 DECnet) version of the
DECUS NETMAP program, and a program which will broadcast commands
to multiple nodes in a DECnet VAX network simultaniously.

     The  [.TECHDEVEL]  sub-directory  contains  updates  of  VMS
Security  related  command  files  which can be included with the
System and will monitor various 'areas of  interest'  within  the
system  and  report back to the System Manager whenever something
out of the ordinary appears, as well as a command file  which  is
designed  to  locate 'World read' command files which may need to
be changed prior to V4.0 making is appearence.

     The  [.VEECO]  sub-directory  has  a  rather   comprehensive
'Directory  Manager' program which wil allow the user to move and
control actions within the directory  tree.   (Librarian's  note:
see [.TI.DM] for another version of this program.)

     The [.WESTELECT] sub-directory contains an  updated  version
of  REMINDER,  which  is a very good personal Reminder program to
keep up with the day to day fire-drills.
========> [VAX84A.DIGITIZER]AAAREADME.TXT;1 <========


This is the first submission from Mountain States Engineers.  Hooray, 
we are no longer takers only!

Dev.com  -  This command procedure allows you to look at 'any number' of 
            disk drives on your system and get a quick status check.  
            Pretty printing is accomplished with the f$fao lexical 
            function.  Just change the installation specific noted lines.

Dig*, etc - A digitizing tablet interface program is presented here.
            Looking at the runoff sources and outputs will get you 
            the information here.  The programs are written in 
            VAX-11 Basic.  They all make use of the minimum line
            numbering possible for easy recoding in your favorite
            language.  All important strings are fixed length.

Unfortunately, due to time constraints more documentation is lacking.

Mountains States Engineers
P. O. Box 17960
Tucson, Az 85731

Ted Frohling
========> [VAX84A.DISASTER]AAAREADME.TXT;2 <========


     [VAX84A.DISASTER]AAAREADME.TXT


                                 submitted by:


                                  Tim Mahaney
                          Naval Air Propulsion Center
                                  PO Box 7176
                               1440 Parkway Ave.
                               Trenton, NJ 08628

                                 (609) 896-5728



          This   directory   contains   programs   for    retrieving    and
     reconstructing files from a disk that cannot be read by VMS.

     1.  SEARCHER

              prepares a listing of possible file headers

     2.  GETFILE

              is used to retrieve files and rebuild them.



     For those with access  to  Datatrieve,  some  record  definitions  and
     procedures are provided to allow manipulation of SEARCHER's output.


     See DISASTER.DOC for further, albeit sketchy, information.


     The basis for these routines was submitted by Ray Stone on the  Spring
     82  SIG  tape  in  [VAX82A.DISKFILES].  His original code is included,
     with extension .VIR.
========> [VAX84A.DTRWHIZ]AAAREADME.TXT;1 <========




        ********************************************************
        ***                                                  ***
        ***             DTRWHIZ Version 3.0                  ***
        ***                                                  ***
        ********************************************************


DTRWHIZ is a DATATRIEVE interface to DECalc, Multiplan and Visicalc.
The kit should contain the following files:

        DTRWHIZ.OPT - An option file pointing to the DATATRIEVE shareable image
        DTRWHIZ.BLD - A command file for linking DTRWHIZ
        DTRWHIZ.HLP - A copy of the DTRWHIZ HELP file - this can be printed
        DTRWHIZ.MEM - A copy of this file
        DTRWHIZ.BAS - The source code (BASIC)

To build DTRWHIZ type     -  @DTRWHIZ.BLD
Then to run DTRWHIZ type  -  RUN DTRWHIZ
Once inside DTRWHIZ type  -  HELP

NOTE: This version of DTRWHIZ is not fully compatible with DATATRIEVE V2.x.

      DTRWHIZ may be used with DATATRIEVE V2.x, but the EDIT, and DTR HELP
      will not function properly.

      DTRWHIZ works ONLY with VT100 class terminals (eg. VT100,VT125,VT102).
      An Advanced Video Option helps, but it is not necessary.
========> [VAX84A.FERMILAB]AAAREADME.TXT;4 <========


                Fermilab Accelerator Control System Submissions


                                 submitted by:


                               Dr. Frank J. Nagy
                     Fermi National Accelerator Laboratory
                P. O. Box 500 Mail Stop 306, Batavia, IL. 60510
                                 (312)-840-4935



          This directory tree is a submission from the Fermilab Accelerator
     Division.   The programs and command procedures in this directory tree
     are general utilities and system management utilities  either  written
     at  Fermilab  or  acquired  from  DECUS  (via  a  SIG tape or from the
     library) and modified.  In many cases the  software  can  be  used  at
     other  sites  without  modification;   some  of  the system management
     utilities are included as starting points from which sites can produce
     their custom versions.  Each of the next-level subdirectories includes
     a README.1ST  file  which  provides  additional  details;   this  file
     provides an overview of the entire submission.




     [.ARGUS]


          This area contains the Argus program executed as a subprocess  to
     watch  for  and  delete idle processes.  This is a major rewrite of an
     earlier version submitted on the Spring 1983 tape.   The  program  has
     been  made  considerably  easier  to customize for a site's particular
     needs.


     [.ENDTAPE]


          The  ENDTAPE  program  will  fix  the  file   structure   on   an
     ANSI-|standard tape.  The program was written to repair tapes in which
     the last file on the tape is incomplete (no end labels) because  of  a
     failure  of  the program writing the tape.  The user tells the program
     the name of the last good file on the tape.  The program searches down
     the   tape   for  this  file  and  places  the  end-|of-|volume  label
     immediately after the end of file label for this last good file  (thus
     eliminating the bad partial file).


     [.GETQUOTA]


          The  GETQUOTA  program  is  DCL  command  to  return  disk  quota
     information  in  DCL  symbols.   It can return permanent and overdraft
     quota and current disk usage for the current user or for  a  specified
     UIC.  It replaces long command procedures which run DISKQUOTA and then
                                                                          Page 2


     extract the information from the DISKQUOTA printout.


     [.GETUAF]


          This  program  extracts  information   from   the   system   User
     Authorization File (UAF) and returns the information in DCL symbols.


     [.HELP]


          This area contains several files  suitable  for  creation  of  or
     inclusion  in  help  libraries.   These  include  notes useful for the
     system manager and help on the usage  of  the  command  procedures  in
     SYS$UPDATE:.


     [.LIBRARY]


          This area contains object, macro and text libraries which provide
     extensions  to  the  system  libraries  in  SYS$LIBRARY:.  Most of the
     programs in the remainder of the submission make use of one or more of
     these  libraries.   The  sources for the macros and object modules are
     included in subdirectories.


     [.MAKEINCS]


          The command procedures  in  this  area  are  useful  in  creating
     include  files  for  FORTRAN,  C  and PASCAL from macro definitions or
     FORTRAN include files.  These procedures were used to prepare many  of
     the modules in the text libraries in the [.LIBRARY] area.


     [.OPERATOR]


          The command procedures in this area illustrate the implementation
     of  a  turnkey  OPERATOR account at Fermilab.  This account is used to
     provide  open  shop  access  to  privileged   system   functions   for
     non-|privileged  users  and  to  provide support for utility functions
     such as the normal disk  backups  by  the  technicians  without  their
     having to type in long and elaborate commands.


     [.PROCCNTRL]


          These programs provide for additional process  control  commands.
     The RESUME and SUSPEND programs have been (somewhat) superceded by the
     /RESUME and /SUSPEND qualifiers of the  SET  PROCESS  command.   Other
     commands  provide  a  means  to  force  a process to exit (via $FORCEX
     rather than directly deleting it with STOP) or to wake  a  hibernating
                                                                          Page 3


     process.


     [.SETUSER]


          The SETUSER program is a foreign DCL command which permits a user
     with  CMKRNL  privilege  to change his UIC, username and account name.
     This is very useful in submitting batch jobs to  be  run  under  other
     user's accounts.


     [.SYSMGR]


          This area contains several command procedures  useful  to  system
     managers.


     [.TIME]


          The TIME program is a foreign DCL command  used  to  manipulation
     time  and  date  information  and  return  the results in DCL symbols.
     Amoung its capabilities are the calculation of an absolute  time  from
     an  absolute  time  and  a  delta time, the comparison of two absolute
     times and several other useful time operations.


     [.UAC]


          The User Access Checker program is a combination of LOGINOUT  and
     AUTHORIZE  to  permit  a  turnkey account to include a second level of
     security or to establish a set of "subaccounts" under a single turnkey
     account.


     [.USS]


          The  FERMIUSS  protected   shareable   image   contains   several
     general-|purpose user-|written system services in use at Fermilab.


     [.UTILPROCS]


          This area contains several command procedures of general use.
========> [VAX84A.GEMEC]AAAREADME.TXT;9 <========


                     System Management Tools and Utilities

                                    from the

                    General Electric Microelectronics Center

                     Research Triangle Park, North Carolina


                                 Robert L. Boyd

                        GE MEC, POB 13049, RTP, NC 27709

                     (919) 549-3627, GE DIALCOMM 8*278-3627


                                  1-June-1984

         At the time  of  this  submission,  the  GE  Microelectronics
    Center   is  operating  3  VAX  11/780  systems  in  a  VAXCLUSTER
    configuration with a total of approximately 5  Gigabytes  of  disk
    storage.  We service about 220 users on a regular basis.  We first
    started our operation in January 1981 and  have  expanded  rapidly
    over  the  3  years since then.  Most of the system management and
    operations work has been performed by no more than  2  individuals
    at  any one time until the last few months.  We are in the process
    of expanding our system support staff to a total of 4  individuals
    in the near future.

         Contained in this directory tree are a collection of  various
    command  procedures,  data files and executable images and sources
    which are used on a daily basis at the GE Microelectronics Center.

         Many of these submissions could  be  converted  from  command
    procedures  to  programs,  and may be re-submitted in that form at
    future symposia.  No claim  is  made  that  these  procedures  are
    perfected.   There  are  many  things on our wish list in terms of
    improvements and additions to the materials you will find in  this
    submission.

         We do believe that these procedures and programs  demonstrate
    many  usefull  applications of DCL, some of which are particularly
    innovative.  If you have comments, suggestions, or re-work any  of
    the  material  you  will  find in these directories, please let me
    know about it.  I will be glad to answer questions, either by mail
    or by phone as time permits.

         The various  subdirectories  are  primarily  related  to  the
    purposes that each of their names suggest:

    1.  Accountng -- command  procedures  we  have  used  for  routine
        summaries of the accounting files.

    2.  Backups -- command procedures that perform  our  daily  backup
        routines and a sample data file to drive it.

    3.  Disk -- command procedures and data files specifically related
        to routine procedures with disk drives aside from backups.

    4.  Logins -- command procedures specifically  related  to  system
        wide login procedure.
                                                                          Page 2


    5.  Queues -- command  procedures  related  to  the  starting  and
        stopping  of  queues,  as  well as examples of self scheduling
        jobs.

    6.  Syscom -- general procedures, particularly those  we  use  for
        system startup and shutdown.

    7.  Sysmgr -- command procedures  which  we  keep  in  the  system
        manager's directory.

    8.  Utility -- multipurpose command procedures and programs.


         In general the command procedures found in these  directories
    depend on a set of selected logical names:

    1.  accnt -- points to the accountng directory

    2.  backups -- points to the backups directory

    3.  diskcom -- points to the disk directory

    4.  quecom -- points to the quecom directory

    5.  syscom -- points to the syscom directory

    6.  sys$mgr -- points to the same place as sys$manager:

    7.  utility -- points to the utility directory

========> [VAX84A.GODDRD]AAAREADME.TXT;1 <========



   This package contains various routines described in the talk "Software
Aids for the VAX System Manager" presented at the Fall '83 Symposium.

  USER.DAT store in SYS$MANAGER: is an informational file containing an entry
for each system user giving ID, name, UIC, other UICs which he is allowed to
use, and parameters indicating acounting group, purge status, etc.

  NEWUSER.COM is a command procedure for entering new users into the system.

  USER.COM cross references and displays information from USER.DAT

  IMAGE.FOR displays a list of interactive and batch images which are running.

  MIDNIGHT.COM is an automatic scheduling routine.

  SCRATCH, WEEKLY, SCRLOG and WEEKLOG.COM are scratch area cleanup routines
and usage report generators.

  DISKLOG.COM maintains a cumulative list of daily error counts and free space
for each disk.

  ACCOUNT.COM is a self scheduling monthly accounting report generator.
 
  SYHDIRALL.COM creates a directory file for an entire disk. SYHBIG.COM and
SYHFIND.COM are two sample procedures which search this directory for specific
types of files.

  SEND.FOR is a message transmission routine which will send a one line message
to a specified terminal. It may be used interactively or from a batch job .COM
file. (See PURGE.COM for example.)
  
  SHOWDEV.FOR displays the status (free or allocated) and owner if allocated
of certain commonly used devices.

  WHO.MAR and USER.FOR are a user display command giving more infor-
mation than SHOW USER. They are modified from code submitted to DECUS
by J.Thompson of INTERMETRICS. The modified version uses file USER.DAT.

  TERMINAL.COM uses informational file TERMINALS.LIS to give infor-
mation about a user terminal.

  STARTMOD.LIS shows modifications to STARTUP.COM and SYSTARTUP.COM
which allow an offline startup when system work is being performed.

  TRUNCATE.COM is automatically scheduled once a week to free allocated
but unused blocks.

  Please address any comments, questions, contributions to:

          Thurston Carleton
          Code 694
          NASA/GSFC
          Greenbelt, Md. 20771      Ph. 301-344-7623

========> [VAX84A.HARRIS]AAAREADME.TXT;5 <========


Contained in this tape for distribution through DECUS are two programs:

  1.  TYPIST (BASIC):    A touch typing tutor program to help with 
                         learning the typewriter keyboard and developing
                         higher typing speeds.

  2.  QD (FORTRAN):      A program to display the output (print) queues
                         on a VAX/VMS system.  It shows, among other
                         standard items, an approximation of the length
                         of each active queue in minutes.

Also, a listing of the differences in SCRFT.MAR to match a paper presented
at the Fall 83 DECUS by Steve Swenson on using SCRFT.MAR (file: SCRFT.DIF)

This information replaces the [HARRIS] directory on earlier VAX SIG tapes.


Contacts:
        
        Steve Swenson or John Chong
        Harris / Farinon Division
        1691 Bayport Avenue
        San Carlos, CA   94070
        (415) 594-3524 or -3582




                        - end of text -
========> [VAX84A.HEX]AAAREADME.TXT;1 <========


                           Submitted by: Scott Smith
                         Telex Computer Products, Inc.
                         Raleigh, North Carolina 27604



     1.  HEX

              The HEX utility is designed to manipulate ASCII hex formatted
         files    as   output   by   cross-assemblers   and   linkers   for
         microprocessors (Z80, 8085, 68000, etc.).  HEX supports all of the
         popular  ASCII  hex  formats:   Intel,  Motorola,  Rockwell,  RCA,
         TekHex, Extended TekHex, Texas,  Mostek,  Hex-space,  Octal-space,
         and  TCI,  plus  several binary ones:  Whitesmiths', PDP-8 RIM and
         BIN, and PDP-11 object and task formats.

========> [VAX84A.HGRAPH]AAAREADME.TXT;5 <========


                        submitted by:  Dennis V. Jensen
                                Ames Laboratory
                                 310 Metallurgy
                                Ames, Iowa 50011
                                 (515) 294 4823



          This is release 2 of the HGRAPH plotting package.  See README.DOC
     for further information.
========> [VAX84A.HUGHESSCG]AAAREADME.TXT;1 <========


Hughes Aircraft, Space and Communications Group, PWB Dept.
Spring 1984 VAX/VMS DECUS tape submission

More goodies from the spaced-out communications at Huge Aircrash...

In this submission you will find three major entries:

1> CALLOUT   -- this is a useful program for transparently connecting your
        terminal to another terminal line on the system.  Most useful
        for attaching to auto-dialing modems and terminal lines to other
        systems or devices.  This comes complete with a .CLD file for a
        VMS command and a .HLP file for system help library entry.  No
        system should be without it!

2> EMACS     -- No, this is not actual EMACS.  But for those of you who
        have this awesome editor, here is a small library of very useful
        MLisp routines, particularily to the MLisp hacker.  There is also
        an emulator for TECO's VT-EDIT, and the truly definitive (that is,
        until the next version...) EMACS EDT emulator.  No system should be
        without these! 

finally, the program you have all been waiting for...
3> STRATEGO   -- Plays a two-terminal, two-player game of the popular board
        game of STRATEGO.  Very slick.
        It features full advanced-video VT100 screen features, inter-process
        communications (for sending threats to your opponent), the ability
        to make notes to yourself, SPAWN capability (to temporarily go back
        to work...), full in-game help, and a scrolling text buffer that
        exposes a firmware bug in the standard VT100 terminal!  
        No system should be without it!

authors:
Gordon Howell
Kevin Carosso

Hughes Aircraft Co.
Space and Communications Group
PWB Department
PO Box 92919
Bldg S50/X342
Los Angeles, CA  90009

========> [VAX84A.JPLVLSI]AAAREADME.TXT;8 <========



                  ._____.  .____________________     ._____.
                  !     !  !                    `.   !     !
                  !     !  !     .__________      \  !     !
                  !     !  !     !          \      ! !     !
                  !     !  !     !           ;     ! !     !
                  !     !  !     !__________/      ' !     !
                  !     !  !     !\               /  !     !
                  ;     !  !     ! \____________,'   !     !
       __________/      !  !     !                   !     `___________
      /                 ;  !     !                   !                 \
     /_________________/   !_____!                    \_________________\

                                  Eric P. Scott
                         Networked Computer Systems Group
                     Computer Science and Applications Section
                             Jet Propulsion Laboratory
                        California Institute of Technology


1. FREE
  .COM file to display the amount of free space on a mounted
  disk volume.  From the Radio Astronomy/VLBI hackers.  Gee I
  wish you could pass more than eight parameters to a .COM file!
2. INUSE
   An INUSE is some sort of display to leave on your terminal
   when you leave, but not for long enough to justify logging
   out.  INUSE.COM produces the "Caltech Standard In Use"
   display on a VT100+AVO or equivalent.  KZLINUSE.COM was
   written by a Caltech student whose name has since been
   forgotten... it's a little unusual in that it cycles
   through six frames.  Works on any 24x80 CRT; best viewed
   from a distance.  "Everyone writes an INUSE; it's easy to do
   and makes you feel important."  Apologies to Rob Pike (now at
   AT&T Bell Laboratories).
3. MAILCHECK
   If I had to pick one "most useful .COM file" this would have
   to be it.  Given a list of usernames (default is your own) it
   displays how many unread MAIL messages there are for each.
   Requires read access to SYS$SYSTEM:SYSUAF.DAT.
4. RMS Cheat Sheets
   These have literally saved hours of my time.  A must for the
   true RMS hacker.
5. SCRFT
   I promised this at the last (Las Vegas) Symposium.  Intended
   for publication in Pageswapper.  Read the .DOC file.
6. USERS
   VMS version of the program of the same name written by
   yours truly a few years back for the DECsystem-20, and
   incorporating some improvements suggested by Ian Macky
   (now with the Network Information Center at SRI
   International).  Read the .DOC file.
========> [VAX84A.LN]AAAREADME.TXT;2 <========


                                 submitted by:


                                Robert A. Harris
                                     MD-115
                              Leeds & Northrup Co.
                                 Dickerson Road
                            North Wales, Pa.  19454
                             (215)-643-2000 (x2380)



          This directory tree  contains  programs  and  command  procedures
     developed at L&N which we find useful.

          This software is furnished for free and may be used and copied as
     desired.  This software or any other copies thereof may be provided or
     otherwise made available  to  any  other  person.   No  title  to  and
     ownership  of  the  software  is  hereby transferred or allowed.  This
     software may not be sold for profit.

          The information in this software is  subject  to  change  without
     notice and should not be construed as a commitment by Leeds & Northrup
     Co.  to supply support.

          Leeds &  Northrup  assumes  no  responsibility  for  the  use  or
     reliability  of  this  software  on  any  equipment  whatsoever.  This
     software is also not guaranteed to work.  After all this is

                              +-----------------+
                              | FREEBE SOFTWARE |
                              +-----------------+


          Each  of   the   subdirectories   supplied   contains   its   own
     AAAREADME.1ST  file  explaining  the files contained within and how to
     installed them for use.

          ---- ---- ---- ----

          Many of the command procedures and  programs  supplied  from  L&N
     reference the logical name

          SYS$COM:

          where we store common  programs,  command  procedures,  and  data
     files.   You  may  either  define  this  logical  name to point to the
     directory where you keep your common files (and have stored the  files
     needed  by  the  L&N  procedures),  or you can modify the L&N files to
     reference your common storage directory.

          ---- ---- ---- ----

          The one  command  procedure  used  frequently  by  other  command
     procedures is
                                                                          Page 2


          UNIQUE.COM

          This command procedure will obtain a unique file name  which  can
     be used by other procedures for the creation of temparary files.

          This  command   procedure   is   stored   in   the   subdirectory
     [...LN.UNIQUE]  and  should  be  installed  in the SYS$COM:  directory
     before trying to use any of the other command procedures supplied.

     1.  [...LN.CALENDAR]

              This  directory  contains  a  Snoopy  Calendar  program.   It
         generates  a  2  page  per  month  calendar.   The first page is a
         picture and the second page is a month of the year.  The data file
         contains  14 pictures so that you can run a calendar from December
         of the ending year, 12 months of the new year, and January of  the
         following year.

     2.  [...LN.COM]

              This directory contains many useful command procedures in use
         at L&N.

         a)  EDTSEARCH.COM

                  This is command procedure to search a wildcarded/list  of
             files  for  the  specified  character  string.  When a file is
             found that contains the specified  character  string,  EDT  is
             invoked to allow the user to make editing changes to the file.
             This is extreamly useful when the changes necessary to a large
             group  of  files  are  more  complex  than a simple search and
             replace can perform, yet you don't know  exactly  which  files
             require the necessary changes.

         b)  HOME.COM

                  This is a command procdure which will return  a  user  to
             his   login   directory   (Main   directory),   optionally   a
             subdirectory attached to the main directory may be  specified.
             With GETUAF.EXE properly installed it may also be used to find
             another users Home directory.

         c)  EDT.COM

                  This is a command procedure to invoke  EDT  and  remember
             the name of the last file edited.  Makes jumping in and out of
             a file during development much easier.

         d)  UIC.COM

                  This is a command procedure to  change  the  UIC  of  the
             current  user  to  whatever  is  specified,  or  if nothing is
             specified, change it to be the same  as  the  current  default
             directory's    UIC    (including   rooted   directories   like
             SYS$MANAGER:).  Privilege is required.
                                                                          Page 3


         e)  SETTIMER.COM & DISPTIMER.COM

                  These 2 command procedures are used to obtain performance
             information    about    programs    or   command   procedures.
             SETTIMER.COM invoked just before the program or  procedure  to
             be  studied  is executed and records the processes current CPU
             time  usage,  page  faults,  direct  I/O,  and  buffered  I/O.
             DISPTIMER.COM  is  then  called  after  the  study  target has
             completed so that the amount  of  CPU  time,  number  of  page
             faults,  number  of direct I/O's, and number of buffered I/O's
             the target used may be calculated and displayed.


     3.  [...LN.DATES]

              This directory contains some simple routines for dealing with
         dates.

         a)  DAY.FOR

                  This is a program to calculate what day of the  week  its
             for either the current date or for a user specified date.

         b)  HOLIDAY.COM

                  This is a procedure to compare  the  current  date  or  a
             specified  date against a list of holidays and return a status
             value indicating if the date is a holiday.

         c)  NUMDATE.COM

                  This is a procedure to  take  the  specified  dd-mmm-yyyy
             date  and convert it into a yyyymmdd format sutable for naming
             dated files with.

         d)  CHARDATE.COM

                  This is a procedure to take NUMDATE.COM  yyyymmdd  format
             file names and convert them to dd-mmm-yyyy format.


     4.  [...LN.DETAB]

              DETAB is a program that will remove tabs  from  a  file.   It
         only  works  on  standard  column of 8 tab stops.  However it is a
         fast implementation.  It uses RMS I/O and Macro  code  to  perform
         fast detabbing.  Also see ENTAB.

     5.  [...LN.DOWN]

              DOWN is a program to move down  the  directory  tree  to  the
         subdirectory  specified.   If  you  specify a value between 1 & 8,
         then DOWN will look on the logical name stack  created  by  UP  to
         determine  the name(s) of the subdirectory to go down to (also see
         UP)
                                                                          Page 4


     6.  [...LN.ENTAB]

              ENTAB is a  program  to  replace  multiple  blanks  with  tab
         characters.   It  only  implements standard column of 8 entabbing,
         however it is a fast implementation.  It uses RMS  I/O  and  Macro
         code to entab the records as fast a possible.  Also see DETAB

     7.  [...LN.GETQUOTA]

              GETQUOTA.FOR is a program for working with  a  modified  disk
         quota  system.   As  you may have already discovered, the DEC disk
         quotas are difficult to live with.  Programers almost  always  use
         up  all  the  quota they are allowed and then don't have enough to
         edit  a  file,  compile  a  program,  or  any   other   productive
         activities.  GETQUOTA is a tool that can be used as part of a more
         flexable quota system.

     8.  [...LN.GETTERM]

              GETTERM is a program to obtain information about  a  terminal
         (default  is the terminal attached to the interactive process) and
         return  this  information  in  a  symbol  for  use  by  a  command
         procedure.

     9.  [...LN.GETUAF]

              The GET User Authorization File data (GETUAF) program  allows
         a  privileged  VAX/VMS  user to obtain from the User Authorization
         File (UAF) information about another user by specifying either the
         Username  or  the  user's  UIC.   This  is a copy of the program I
         submitted to the DECUS Library.

    10.  [...LN.HLP]

              This is a useful subroutine for interfacing with the  VAX/VMS
         help  facilities.  It allows you to supply VAX/VMS style help from
         within your own programs.  The interface it supplies is very  easy
         to  use and the program supplies the '?' instant action keyin just
         like DCL's HELP does.

    11.  [...LN.IFMOD]

              The IF  MODified  (IFMOD)  program  is  a  poor  mans  Module
         Management  System (DEC/MMS).  It supplies one of the key features
         of DEC/MMS, which is the ability to determine if a source file has
         been  modified  since  the  last  time  it  was  compilied.  IFMOD
         compares the modification dates of specified files, and  depending
         on  whether  the  results  are  true  or false, it executes a user
         specified DCL command (the syntax of the IFMOD command is  similar
         to  the DCL IF command).  The basic idea is:  If file A is used to
         generate file B, then IFMOD can be used to determine if file A has
         been  changed  (since  the  last  time  file  B  was  created) and
         re-generate file B if necessary.  This is a copy of the program  I
         submitted to the DECUS Library.
                                                                          Page 5


    12.  [...LN.MAIL]

              This directory contains some  utilities  useful  for  dealing
         with mail files without calling MAIL.

         a)  MAILDIR.FOR

                  This is a program to generate a directory listing of  the
             user's  mail  file.   Optionally  a specified mail file may be
             examined (assuming you have read privilege to the file).

         b)  MAILNEW.FOR

                  This is a program to read the user's  mail  file  and  if
             there  is  any  new  mail  in the file to generate a directory
             listing of the new mail entries.  This turns out  to  be  very
             useful  if you are attached via a 300 baud modem and you don't
             want to read excess mail or mail that  could  wait  until  you
             have access to a faster terminal.


    13.  [...LN.OFFLOAD]

              This directory contains a command procedure that  will  build
         another  command  procedrue  which  will correctly read or write a
         BACKUP  format  tape  (using  the  DEC  BACKUP  program).   It  is
         extreamly useful for user's who need to write a BACKUP format tape
         but don't have much experience dealing with magtapes or the BACKUP
         program.

    14.  [...LN.OWNER]

              This directory contains the OWNER program which if  installed
         with the right privileges (BYPASS) will allow a user to change the
         ownership of a file stored in one of his directories to match  the
         UIC of the directory it is stored in.

              There are other programs which do the  same  thing,  HOWEVER,
         this  version  DOES NOT use the directory pathname supplied by the
         user to determine its parent directory.  Instead the  target  file
         is  opened  and  its  back link pointer is used to find its parent
         directory.  This gets around the problem  of  a  user  creating  a
         duplicate  file name in one of his directories with PIP or his own
         RMS program and then using OWNER to take  over  the  ownership  of
         someone elses file (such as MAIL.MAI, SYSUAF.DAT, etc...).

    15.  [...LN.PROMPT]

              The PROMPT program allows a command procedure to  prompt  for
         input  from the specified device and have the response returned in
         a specified local symbol.  This program works very much  like  the
         INQUIRE  command  execpt it has some features which makes it ideal
         for some special applications (such as allowing the system startup
         command  procedure  to  prompt  for  options  during system boot).
         These features include a timeout  so  the  prompt  will  not  wait
         forever  (that way startup will continue booting if an operator is
         not present to answer questions) and the terminal that the  prompt
                                                                          Page 6


         is  sent  to  & reply taken from may be specified (such as OPA0:).
         This is a copy of the program I submitted to the DECUS Library.

    16.  [...LN.REMOTE]

              REMOTE is a program that will allow you to send commands to a
         remote  node,  have them executed, and any output results returned
         to your SYS$OUTPUT device.  When the remote node is specified with
         a  privileged  account  and  password (typically done with logical
         names so that nothing is typed) you can have REMOTE perform system
         maintenance  functions without having to login to the remote node.
         It  is  also  extreamly  useful  when  used  inside   of   command
         procedures.

    17.  [...LN.RIM]

              This is a re-worked copy of the RIM  documentation  found  of
         the  '83  SIG  tapes.   It  has  had  extensive  RUNOFF formatting
         commands inserted,  the  Index  has  been  expanded,  a  table  of
         contents  has  been  added,  and input syntax information has been
         added (obtained from the .HLP file).

    18.  [...LN.RMSIO]

              This directory contains the example source files  and  RUNOFF
         source which went into the March, 1984, PageSwapper article:

                 "RMS I/O for Improved Fortran I/O Performance"
                                       By
                                Robert A. Harris


              The files are included here for anyone  that  would  like  to
         test  out  how  RMS  I/O may help performance on their system, but
         don't want to keyin the code from the written article.

    19.  [...LN.SU]

              This directory contains programs for raising and  lowering  a
         privileged user's privileges

         a)  SU.FOR

                  This is a program to take a user with SETPRV,  grant  him
             all  privileges,  and change his UIC to [1,4].  The command is
             call Super User since that is  what  the  user  becomes  after
             running this program.

                  The program will save the previous privileges and UIC  of
             the  user  so  he  may  reduce  his  privileges  back to their
             previous state later.

                  The program may be called multiple times and the previous
             states  are  saved in a stack like maner.  This makes it ideal
             for placing within command procedure that could  be  run  when
             you  have  all privilege or when you have no privileges, since
             you will be returned to you previous state when NU is run.
                                                                          Page 7


         b)  NU.FOR

                  This is a program to restore the  user's  privileges  and
             UIC sometime after having run SU


    20.  [...LN.TIME]

              The  TIME  calculator  allows  a  VAX/VMS  user  to   perform
         Addition,  Substraction,  Multiplication, Division, and Comparison
         on  time  values  when  using  DCL   (Digital   Command   Language
         interpreter).   This  ability is very useful when time values have
         to be calculated for use in various  DCL  commands  (ie.   BACKUP,
         SUBMIT,  PRINT,  DELETE,  DIRECTORY,...).  The calculator can deal
         with Absolute time and Delta time  formats  as  well  as  handling
         month  and  year  transistions.  It also has the ability to return
         the results in a DCL symbol which can then  be  used  by  the  DCL
         commands  which  follow.   Once the calculator is defined as a DCL
         foreign command, it is then used just like any  other  command  on
         the  system.   The  TIME calculator converts all time values to 64
         bit binary values which are then used to perform all  calculations
         and  comparisons.   The  system services SYS$BINTIM and SYS$ASCTIM
         are used for the time conversions.  This is a copy of the  program
         I submitted to the DECUS Library.

    21.  [...LN.TRANSFORM]

              TRANSFORM is a program that will transform the specified file
         from  one  type  of  carriage  control  to  another.  It will also
         perform bolding, right  justification,  and  top  of  page  margin
         inserting services as well.

    22.  [...LN.UNIQUE]

              UNIQUE.COM is a command procedure  that  generates  a  unique
         file  name  for  use  by  command  procedures  that need to create
         temparary files and can not affort to get in trouble by  having  2
         users  run the same command procedure in the same directory at the
         same time.  If this were to happen and the procedure  in  question
         did  not use unique temparary file names, then it is very easy for
         the users to get very screwed up results, by  one  user's  process
         grabing the other user's temparary file.

    23.  [...LN.UP]

              UP is a program to move up the directory tree.  If a  numeric
         parameter  is  specified, then that number of directory levels are
         moved up until [000000] is reached.

              As you move up, the subdirectories you left are  saved  in  a
         logical  name stack so that you can move DOWN later without having
         to specify the subdirectory name (see the  DOWN  subdirectory  for
         that program).

    24.  [...LN.USERON] This is a program which will  check  to  see  if  a
         specified user is currently logged onto the system.  The user must
         have World privilege or the program must  be  installed  with  the
                                                                          Page 8


         privilege (the preferred way).

    25.  [...LN.WHAT]

              This is my version of SHOW SYSTEM or FINGER.  It was  written
         as  my  introduction into using VAX/VMS systems services.  It also
         has the ability to obtain information about a remote VAX/VMS  node
         (assuming WHAT is installed on the remote).

    26.  [...LN.WHO]

              WHO was my very first attempt at writing anything on  a  VAX.
         It  started out as a command procedure which reformated one of the
         unsupported programs supplied with the early  2.0  VMS.   Next  it
         became  a  proc  which  used  the VMS program and then call my own
         program to do the reformatting.  Finally I decided to  figure  out
         how to use the SYS$GETJPI system service and wrote this version of
         the program.  It supplies the same information as SHOW  USERS  but
         in a more desirable format (at least I think so).

========> [VAX84A.LOGINDATE]AAAREADME.TXT;1 <========


                           submitted by: John Briggs
                                    SPACECOM
                            1300 Quince Orchard Blvd
                             Gaithersburg, MD 20878



     1.  LOGINDATE

              The LOGINDATE package prompts users to change their passwords
         every 30 days (or other selected interval).  It is invoked as part
         of the system wide login command procedure.

========> [VAX84A.NAMELIST]AAAREADME.TXT;6 <========


NAMELIST, Version 2:  June 1984

Author:  Frederick  K.   Knight,  Smithsonian  Astrophysical
Observatory 60 Garden St.  Cambridge, MA 02138

Operating System:  VAX/VMS Source language:  VAX 11  Fortran
and Macro

Submitted by:  Bijoy Misra

Abstract:  NAMELIST is a set of Fortran-callable subroutines
to  perform  formatted I/O within the calling program and is
an augmentation of the namelist submitted  by  Derek  Rowell
and Douglass Wilson of MIT.  Namelist allows selective input
and output of values for variables defined  in  the  calling
program.   Other  features  include  variable initialization
with defaults, reading from files, access to  DCL  commands,
on-line help, and options that can be personalized.

The tape contains an AAAREADME file, all source code, a help
file,  a  document,  the  object  and  object library, and a
command procedure for updates.

Contents:  The files on the tape are:

     AAAREADME.RNO  - the runoff input file for AAAREADME.TXT
     AAAREADME.TXT  - the synopsis of namelist files
     NML.FOR        - the Fortran code
     NML.DOC        - the current namelist document
     NMLORIG.DOC    - the original DECUS document
     NMLHLP.RNO     - the runoff input file for NML.HLP
     NMLDOC.JOU*    - the EDT script to convert NMLHLP.RNO to NMLDOC.RNO
     NMLDOC0.RNO*   - the runoff input for the NML.DOC introduction
     NMLNEWDOC.COM* - the DCL script to make NML.DOC from NMLDOC.RNO
     NML.HLP        - the help library input file
     NML.HLB        - the namelist help library, NML$HELP
     NML.OBJ        - the object code
     NML.OLB        - the namelist object library, NML$LIB
     NML.MAR        - the macro code

     * see also the NML$HELP topic "logical_names NML$DIR."
========> [VAX84A.NRL]AAAREADME.TXT;1 <========


                         submitted by: Stanley S. Leroy
                               Code Code 5707.11
                           Naval Research Laboratory
                              4555 Overlook Avenue
                             Washington D.C. 20375



     1.  BLDSHR

              This procedure  enables  one  to  create  a  shareable  image
         library   from   an  existing  object  module  library.   This  is
         accomplished by generating the transfer vectors for all the  entry
         points  in the library.  In addition, all PSECTS other than $TRANS
         are changed from GBL,SHR to LCL,NOSHR.

========> [VAX84A.NSWC]AAAREADME.TXT;2 <========




        MIRACLE MESSAGE PROGRAM
        -----------------------

        Prints specified text  in  large  letters  (capitals  are  2.7
        inches tall), four rows at a time, vertically 'down the page'.
        Spacing  is  proportional;  characters  are even overlapped to 
        equalize white space (e.g. the '4' in '74' is tucked under the
        '7').  Vertical and Italic Roman  fonts  are  available.   For 
        proper  proportions, the printer must be set to print at eight
        lines per inch.  Additional formats  are  available  on  LA120 
        DECwriters.

        To see an example, print MMSAMPLE.LIS  at eight lines per inch
        with /NOFEED.   For further information, see MIRACLE.DOC.
        
        This version corrects a problem reported in the version on the
        Spring 1983 (VAX83B) tape.


        REMINDER UTILITY
        ----------------

        This is yet another  appointment-reminding utility.   This one
        reminds you when you log in, and 'tickles' you at fixed inter-
        vals as the time  of an appointment approaches.   The reminder
        message  tells  you  when  the appointment is, and what it is.
        The message is formatted in reverse video for VT100+ terminals
        and the bell rings.   It is very easy to add, remove, and show
        appointments.   For  further  information,  see REMINDERS.HLP.
        See REMINDERS.DOC for installation instructions.  This utility
        uses a batch job  (which is usually hibernating)  to send  the
        'tickler' messages.   Use REMINDBLD.COM to rebuild the package
        from its sources.


        SYSMAIL.COM
        -----------

        System Manager's command procedure to compose, send, and arch-
        ive a mail message for all system users.   The message is sent
        to all users in the UAF, except for users specifically exclud-
        ed.   Users can be excluded in two ways--by having their user-
        name hard coded in SYSMAIL.COM,  or by having an ACCOUNT field
        of 'INACT'  in the UAF.   EDT is called from the procedure for
        entry of the message.  When EDT is exited,  the procedure then
        prompts for the 'subject',  and pauses to  allow  cancellation
        of the mail sending.  After the mail is sent, an archival copy
        is prepared, and appended to the file SYS$MANAGER:OLDMAIL.MAI.


        SYLOGIN.COM (partial)
        ---------------------

                                                      Page 2


        This fragment of a System-Wide Login Command Procedure changes
        the process name of batch processes, and interactive processes
        of a user who has logged in multiple times, to names which are
        more descriptive than the VMS defaults  (examples of which are
        _JOB532: or _TTA2:).



        NOTIFY COMMAND
        --------------

        This is a general message-sending utility.   It can be used in
        a batch process to send a message to the submitting user.   It
        can  be used in  an interactive command procedure  to format a
        message on the screen  (centered, bold reverse video,  bells).
        It can be used to send messages to other terminals  (either by
        terminal name or by user name).   See NOTIFY.HLP  and the com-
        ments in  NOTIFY.FOR  for more information.  Use NOTIFYBLD.COM
        to rebuild the program from its source.


        REFORMAT COMMAND
        ----------------

        This is a utility to easily make a copy of a file in a differ-
        ent format.   Its main purpose is  to change the carriage con-
        trol attribute of the file  (List, Fortran, or None),  but  it
        can also change tabs to blanks,  shift or delete columns, make
        an Indexed Sequential file, etc.   It has two optional methods
        of changing  the carriage control type:   it can copy the file
        verbatim and just change  the attribute, or it can restructure
        each record to conform to the new type.   See REFORMAT.HLP for
        more information.   Use  REFORMBLD.COM  to rebuild the program
        from its source.


        NSWCLIB.OLB
        -----------

        This object library, whose sources are the  files  NSWCLIB.FOR
        and NSWCLIB1.MAR, is required for linking the programs NOTIFY,
        REFORMAT, REMINDER, and REMINDERS.   The routines on this lib-
        rary may also be  useful to you for other applications.   Each
        routine is documented (after a fashion)  internally.   Use the
        procedure NSWCLIB.COM to build the library from the sources.



        Submitted by:  ALAN L. ZIRKLE     NAVAL SURFACE WEAPONS CENTER
                                          CODE K105
                                          DAHLGREN, VIRGINIA  22448
========> [VAX84A.PAGESWPR]AAAREADME.TXT;2 <========


                                 submitted by:


                             Lawrence J. Kilgallen
                              Box 81, MIT Station
                              Cambridge, MA 02139



          Copies of Pageswappers published since the last tape.
========> [VAX84A.PASCALUSE]AAAREADME.TXT;1 <========


          John Heffernan

          RCA/AS

          BOX 588

          Burlington, MA 01803

          (617)229-3887



          This directory contains a copy of a paper called "Using  DEC  VAX
     Software  From  Pascal"  given  at  the  spring  1984 DECUS symposium.
     Included are  examples  of  using  the  librarian,  tparse,  RMS,  set
     message, and set command.  Also, the librarian status codes are given.
     These examples can be reused for  your  applications.   A  program  to
     generate  set  message  error  constants  for a PASCAL include file is
     given.  Another example of using lib$tparse is  given.   This  program
     finds all valid binary coded Turing machine programs.
        The files in this directory are as follows.

        These file make up the paper source :
        ABSTRACT.RNO
        PAPER.RNO
        LBRFUN.REQ
        TBLOCK.REQ
      
        A copy of the paper is in:
        PAPER.MEM

        A program to generate an PASCAL include file for set message constants
        is in the two modules:
        GENERRMSG.PAS which is the main module
        RMSERROR.PAS  which is a giant case statement which spits out 
                      the pascal I/O errors message.  Note that these 
                      constants are NOT compatable with the set message
                      utility and can not be lib$signalled. 
                      These two files are should be linked.

        GEN.COM invokes set message and generrmsg.  The input is a sample set 
                message source in file ERRORS.MSG.  Set message creates 
                the file ERRORS.LIS whcih is the input to generrmsg. 
                Generrmsg outputs the include file errors.pas.
                Note that the errors.obj created by set message must be 
                linked in with your program so that the text messages can
                be found by lib$signal.
        

        ENUMTM.PAS is another example of using lib$tparse.  This program 
                   finds and lists all valid Turing machine programs.

        PARSETAB.MAR is the state table for the above.  It must be linked 
                     with ENUMTM to produce the image.  (This table 
                     actually those programs with up to two instructions;   
                     there are many such programs!).
========> [VAX84A.PLOTS]AAAREADME.TXT;1 <========


                          Naval Weapons Support Center
                   (Bill Combs, Walter Schmeichel, Code 6054)
                              Crane, Ind.   47522
                                  812-295-4911

     1.  NTRACE

              NTRACE uses the VAX/VMS LXY11 plot routine package  purchased
         from  Digital  Equipment  Corporation  to  plot lines on the LXY11
         printer/plotter  which  is  the  same  as   the   Centronics   300
         printer/plotter.   If  this library package has not been installed
         on your system , NTRACE will not function.

========> [VAX84A.PSDI]AAAREADME.TXT;2 <========


               Project Software and Development, Inc. Submissions


                         coordinated by: M. Erik Husby


                     Project Software and Development, Inc.
                                14 Story Street
                              Cambridge, Ma. 02138
                                  617-661-1444


     This year PSDI is submitting new version of its previous  submissions.
     The  ever  popular  VAXNET  is  now at version 8.  It includes several
     important  new  features  including  support  for  the   XMODEM   file
     transmission  protocol,  wild  cards  in the SEND/GET filenames, batch
     mode operation, and improved HELP.  A  slightly  improved  version  of
     AUX,  the auxillary keypad DCL program, is included.  It has been made
     more efficent as well as correcting a problem with the  help  display.
     The  third submission is a set of DECnet procedures that make managing
     a network easier.  Included are examples  of  the  technique  used  to
     write  privileged command procedures that can be used by nonprivileged
     users.

     1.  Subdirectory VAXNET --  This  directory  contains  everything  one
         needs to build Version 8 of VAXNET.

     2.  Subdirectory AUX -- This directory contains everything  one  needs
         to build AUX, the auxillary keypad DCL program.

     3.  Subdirectory  NETWORK  --  This  directory  contains  the  command
         procedures  used  at PSDI to manage its network.  It also contains
         examples of privileged command procedures that can be executed  by
         nonprivileged users.

========> [VAX84A.RECORD]AAAREADME.TXT;2 <========


                                  Allen Watson
                               THE BERGEN RECORD
                                150 River Street
                              Hackensack, NJ 07602
                                 (201) 646-4111



          My apologies, but I was unable to complete the documentation  for
     all of the files submitted in this directory.  AAW.

          The files are all  here  but  may  not  be  in  the  subdirectory
     described;  most of the COM files are in the VAXDOC directory.  Sorry.
     I am writing this five minutes before departure to Cincinatti.



          There are three subdirectories in this submission,  VAXDOC,  COM,
     and   TEXT.    In   general   what  we  have  here  is  a  menu-driven
     word-processing system based on EDT and RUNOFF (VAXDOC);  a collection
     of  command  procedures,  mostly  for  system-management but some very
     useful to the average VAX user;  and some text files containing Runoff
     sources  for some VAX-related articles I have written for the VAX/RSTS
     Professional Magazine.

          There is a .RNO file for VAXDOC containing a user  manual.   Some
     (but  not  all)  of  the  COM  files  are  documented in a file called
     COMFILES.HLB which should be accessed with the HELP  command,  or  you
     can  use  LIBRARY  to  extract  certain modules.  The undocumented COM
     files have enough comments in them to explain what they  are  for  and
     how  to  use  them.  I have also included (in the TEXT directory) some
     help files (extension .HLP) for other programs not included  here,  in
     particular ROF.HLP, which is a help file for the RSX version of Runoff
     by John Clement discussed in the article comparing three  versions  of
     Runoff in the April, 1984 Pageswapper.

     1.  [RECORD.VAXDOC] A series of command procedures and required  files
         that  implement  a  document  (word) processing system using video
         screen menus.  Similar to, but completely independent from, the WP
         function in Jim Downward's VPW system on earlier tapes.

              I wrote VAXDOC.COM because Jim's implementation did not quite
         satisfy  me.  I wanted (and had, on RSX) the ability to create new
         documents containing preformatted, standard  RUNOFF  commands  for
         memos,  letters,  and  system documents.  I wanted a better way to
         index the .RNO files that were created.  I wanted to  be  able  to
         choose  whether  to use DSR RUNOFF, or the version by John Clement
         from the RSX tapes.  And finally I wanted to choose between  using
         EDT or the EMACS editor (see the TEXT directory below).

              VAXDOC uses lots of other peoples' stuff,  such  as  ROF  (my
         name  for  Clement's  Runoff),  some  of  the  tools  from the LBL
         submission (delta, ar, get), and EMACS.   But  never  fear;   even
         with  only  standard  VMS  stuff such as EDT and RUNOFF you should
         find this quite useful.  You can (and probably will have to)  edit
         VAXDOC.COM somewhat to change the Runoff formats we use for memos,
         letters, and documents.  Where possible  (with  free  software)  I
                                                                          Page 2


         have  included  executable  images for those folks who haven't had
         the earlier VAX or RSX SIG tapes.  You will have to  decide  where
         to  put  them,  and redefine the foreign commands that invoke them
         (in VAXDOC.COM).

              Full user documentation on VAXDOC is found in  VAXDOC.RNO  in
         the [RECORD.VAXDOC] directory.

     2.  [RECORD.COM] Contains various command procedures for  general  use
         and for system management.  Among them:

         1.  BIGFILE.COM Creates  a  sorted  listing  of  a  directory  and
             (optionally)  its  subdirectories,  sorted  by  file size, and
             indicating which directory contains the files.   Uses  several
             other utilities.

         2.  CMD.COM and UTL.COM Modified from earlier  versions  submitted
             by  Jim  Downward  (a bit more bullet proof).  CMD looks for a
             command file in a directory with the logical name  of  SYS$COM
             and  executes  it,  passing  along parameters.  Saves defining
             foreign commands for every useful command procedure.  UTL does
             basically  the  same  thing  except  it RUNs images found in a
             directory  named  SYS$UTILITY,  which  is   where   we   stash
             everything  not supplied by DEC.  Works for both .EXE and .TSK
             images (native and compatible).

         3.  SIDE.COM Easy way to move sideways  in  parallel  directories,
             e.g.   from  [RECORD.VAXDOC]  to [RECORD.TEXT], just by typing
             "SIDE  TEXT".   With  no  parameter,  lists   available   side
             directories  you could change to and asks which you want.  Has
             smarts to unravel concealed device names;  however,  this  has
             the effect of unconcealing concealed names.  Uses PUSHDEF.COM,
             also contained here.

         4.  PUSHDEF.COM and POPDEF.COM These two work together to maintain
             a  "stack"  of device and directory defaults of where you have
             been, so you can POP back to them later  on.   VERY  NICE  for
             System Managers who directory hop all the time.  Taken from an
             article in DEC  or  VAX  Professional  magazine  and  modified
             slightly.   You  can  do  "@PUSHDEF  H"  or "@POPDEF HE" for a
             built-in help facility on how to use them.

         5.  MINE.COM Lists  out  files  owned/not  owned  by  the  current
             default  UIC in the current default directory.  Again, this is
             mainly useful for system managers who can switch  into  system
             directories  or  other  peoples' directories and create files,
             forgetting they are using their own disk quota to do so.


     3.  [RECORD.TEXT]

              Contains VAXDOC documentation.

========> [VAX84A.RMDEMO]AAAREADME.TXT;1 <========


                                 Mark R. Vevle
                      X-Ray Crystallographic Core Facility
                      University of Alabama in Birmingham
                              SDB Box 13, 244 LHR
                               University Station
                           Birmingham, Alabama  35294
                             (205) 934 - 2212/2149


     RMDEMO     -       A dynamic, user information, display program.

          This is yet  another  program  that  uses  the  $GETJPI  utility.
     RMDEMO displays all interactive users and batch processes.  RMDEMO can
     also add/remove system processes from the display.  All  files  needed
     by RMDEMO are contained in this directory.
========> [VAX84A.RMS]AAAREADME.TXT;1 <========


This submission is yet another (and we think most extensive) high
level language interface to RMS on the VAX.  It is compatible with
Fortran, Basic, and Pascal (at least), and version 3.x of VMS.


The documentation is in RMS.DOC.

An interactive help file RMS.HLB is included.

The subroutines are in RMS.OLB.

A sharable image library  RMSSHRLIB.OLB and RMSSHRLIB.EXE
are included.

For comments or questions contact:
  Mark Frank
  Washington Univ Med School
  Dept Genetics--Olson Lab
  660 S. Euclid Ave.
  St Louis, MO  63110

========> [VAX84A.RMTPRT]AAAREADME.TXT;1 <========


                       Westinghouse VMS DECUS Submission
                               Westinghouse DESC
                                  Spring 1984


                         John Beasley and Paul Orszula
                       Westinghouse Electric Corporation
                           Baltimore, Maryland 21203
                             P.O. Box 746  (MS 491)
                         (301)765-2122 or (301)765-9783


     RMTPRT - Remote Print Utility

          These programs provide a mechanism for sharing printers among any
     number of VAX computers connected via DECnet.  With this package print
     jobs can be sent to remote VAXs, have  the  username  printed  on  the
     banner  page,  allow the printing to be charged to the user's account,
     allow multiple file specifications within the command  and  individual
     file  qualifiers.   The  program  also  allows  for remote print queue
     display and remote print abort capability.
========> [VAX84A.RSXSIG]AAAREADME.TXT;2 <========


                         submitted by:  Frank R. Borger
                            Dept. of Medical Physics
                          Michael Reese Medical Center
                              2929 So. Ellis Ave.
                              Chicago, Ill. 60616
                                 (312) 791-2515


     Modified for the VAX by Joe Bingham, VAX  Systems  SIG  Librarian  and
     Glenn Everhart, RSX SIG Librarian



          These programs were submitted  for  the  RSX  SIG  tape  but  are
     included  here  because  they  are  probably  of  interest  to the VAX
     community.

     1.  [.BASIC]

              This directory contains the Michael Reese BASIC  interpreter.
         You  can just give the command RUN [.BASIC]RSXBASIC to try it out,
         but define a symbol as a foreign command in your system  login.com
         (e.g.   BAS*IC  == "$SYS$SYSDEVICE:[VAX84A.RSXSIG.BASIC]RSXBASIC")
         for general use so you can include the file you want to use on the
         command line (e.g.  BAS MYFILE).  Macro-11 sources and other files
         from the RSX distribution are included.  See [.BASIC]AAAREADME.DOC
         for  some  VAX  specific  information,  [.BASIC]BASIC.MEM  for the
         reference manual.

     2.  [.MURPHY]

              This directory contains MAY and  MURPHY,  two  more  programs
         with a (fortune) COOKIE flavor.

========> [VAX84A.SAOSTOIC]AAAREADME.TXT;1 <========


                           submitted by: Roger Hauck
                            Smithsonian Institution
                           Astrophysical Observatory
                                60 Garden Street
                              Cambridge, MA 02138
                         (617)495-7151 or (FTS)830-7151



     1.  STOIC

              A stack oriented language similar to FORTH.

     2.  RED

              An associated text editor.

     3.  CALC

              An RPN calculator which runs under STOIC.

========> [VAX84A.SDC]AAAREADME.TXT;4 <========


 This submission contains three corrections/updates to previous submissions
to the VAX tape.

1) ASK.MAR is a utility to "inquire" for an answer from a command procedure
and timeout if there is no reply within some time frame.  It is on the
Fall 82 VAX tape.  There is a comment that this is very useful for booting
the system (if no operator is present, optional features will default in).
However, you need to add the line
        $ASSIGN OPA0: SYS$COMMAND
to SYSTARTUP so the ASK knows where the answer is coming from...  Hopefully
this will lessen the number of calls from people getting invalid I/O messages.

 2) USS.MAR is an example of a user written system service submitted on the
Fall 83 VAX tape.  It is used to read the microsecond clock.  Unfortunately 
the version copied out to tape was not the version I was using; there is 
one small error.  The DIFFTIME routine should save all the registers it uses
in the entry mask.  There haven't been any questions about this one yet, but
my face is red anyway.

 3) SNOBOL was submitted on the Fall 82 VAX tape.  The source for the macros
on the tape was accidentally truncated, however, so people wishing to modify 
and reassemble had a problem.  The full source for the SNOBOL interpreter is 
included in this submission.

Librarian's note:  Note that items 1 and 2 are comments regarding the Fall 
1984 tape - ASK.MAR and USS.MAR are not repeated on this tape.
========> [VAX84A.SLIDES]AAAREADME.TXT;13 <========


                                Kathleen D. Morse
                                VAX/VMS Software Development
                                Digital Equipment Corporation
                                ZK01-1/D42
                                110 Spit Brook Road
                                Nashua, NH  03061
                                603-884-8396
                                (Please don't call/write me.)


These are the slides for most of the sessions given by the
VAX/VMS developers at Spring DECUS in Cincinnati.

Listed below are the summaries of the sessions, and the
name of the text file that contains the slides.  One session
VAXCluster Technical Concepts, consists of slide text files
(*.TXT) and pictures in Regis format (*.PIC).  (The pictures
should only be printed on a graphics terminal.)  All other
sessions are just text files and can be printed on any terminal
or line-printer (*.TLK).

         
A USER'S GUIDE TO AUTOGEN:                      AUTOGEN.TLK

         This session will discuss how AUTOGEN, VMS's automatic system 
         tuning command procedure works, and how a system manager can 
         effectively control and use it.  Information on how to tune 
         specific system parameters will not be presented here.
         

DCL AND THE COMMAND DEFINITION UTILITY:         DCL.TLK
         
         This session will discuss the enhancements made to DCL and 
         the Command Definition Utility (CDU) in the Version 4 
         release.  The presentation assumes basic familiarity with 
         Version 3 DCL and the CDU.


VAX/VMS PACKAGING AND DISTRIBUTION:             PACKAGING.TLK

         This session will discuss how VMS will be packaged and 
         distributed for Version 4.0.  It will provide information on 
         how the system packaging and installation have been enhanced 
         to support system growth and clusters efficiently.


VAX/VMS UTILITIES - ENHANCEMENTS IN V4.0:       UTIL.TLK

         This session will present an overview of what is new in the 
         VMS Utilities for Version 4.0.  It will discuss new features, 
         enhancements, and the advantages they provide.


MICROVMS - VMS SUPPORT FOR MICROVAX I:          UV1.TLK

                                                      Page 2


         This presentation describes the MicroVMS product.  It is an 
         overview of MicroVAX I system and the VMS support for it.  
         The MicroVAX architecture, the MicroVAX I hardware, and the 
         MicroVMS software are described.


MICROVAX ARCHITECTURE SUPPORT IN MICROVMS:      UV4.TLK

         This is a detailed technical presentation that describes the 
         differences between the VAX and MicroVAX architectures and 
         the code in MicroVMS that makes these differences invisible 
         to the programmer.  It describes the hardware-assisted 
         emulation that is done for some of the VAX instruction set, 
         as well as other VMS software changes made to support 
         MicroVAX I.
         

WRITING PRIVILEGED SOFTWARE FOR MICROVAX SYSTEMS:  UV2.TLK/DRIVER.MEM

         This presentation addresses the issues in writing software 
         for a MicroVAX system.  Topics will include converting UNIBUS 
         drivers to QBUS drivers, privileged (non-user mode) code, and 
         hardware differences between VAX and MicroVAX systems.  This 
         presentation describes what one needs to know about moving 
         software between VAX and MicroVAX systems.

         (Also refer to the document on how to write a Q-bus driver
         called DRIVER.MEM.)

SUPPORTING NEW PROCESSORS UNDER VMS:            UV3.TLK

         This presentation describes the design and coding changes 
         that are required in VMS to support another VAX processor in 
         the VAX family.  Examples will be drawn from the support done 
         for the 11/730, 11/750, and MicroVAX I machines.  This is a 
         detailed technical presentation.
         

FILE NAMES, LOGICAL NAMES AND SEARCH LISTS IN VMS V4:   LOG.TLK

         This session will discuss in detail features in logical names 
         and RMS filename syntax being developed for VMS V4.0.  Topics 
         covered include: logical name table enhancements, additional 
         filename characters, extended length filenames, additions to 
         concealed devices and search list capabilities for filenames.


VAX-11 RMS ENHANCEMENTS FOR VMS V4.0:           RMS.TLK

         This session will discuss enhancements to VAX-11 RMS for VMS 
         V4.  Topics covered include: using the VMS lock manager, 
         cluster file sharing support, additional indexed file prolog 
         3 support, additional key datatypes, and extended terminal 
         support.

                                                      Page 3



VMS EXECUTIVE ENHANCEMENTS TO THE NEXT MAJOR RELEASE OF VAX/VMS:   EXECENH.TLK

         This talk will highlight changes made in the VMS executive 
         for VMS Version 4.0.  The topics to be discussed will be of 
         interest to system managers and system programmers.  Topics 
         include:  changes in process creation; changes in image 
         activation; an overview of new logical name services; changes 
         in the swapper's memory trimming algorithm; and other 
         miscellaneous topics.

         
USER WRITTEN PRINT SYMBIONTS:                   USERSYMB.TLK

         User written output symbionts are supported in Version 4 of 
         VMS and this talk discusses the design, implementation, and 
         debugging of user symbionts.  Techniques for modifying the 
         standard print symbiont as well as generating entirely new 
         symbionts are presented.  The talk describes how symbionts 
         operating under the unsupported interface of previous 
         releases must be modified for Version 4.


VMS V4 BATCH AND PRINT:                         BATCHPRNT.TLK

         This talk provides an overview of the batch and print 
         capabilities of VAX/VMS.  Topics include the job controller, 
         and related DCL commands and system services with emphasis on 
         new features for Version 4.  The distribution and control of 
         jobs in a VAXcluster is also described.


VAXCLUSTER TECHNICAL CONCEPTS:                  CNXMAN*.*,CLMGMT*.*

         This session will focus on the major software components of 
         the VAX/VMS operating system that comprise the VAXcluster 
         functionality present in Version 4.  Topics covered will 
         include System Communication Services (SCS), basic I/O 
         structure, device naming issues, VAXcluster connection 
         management, the distributed lock manager, the distributed 
         file system, the batch and print system, and system 
         management and configuration considerations.
         
         This presentation will assume some familiarity with the 
         VAXcluster concept, such as the VAXcluster Technical Summary 
         provides.  This talk should provide insight into how the 
         various components within VMS are layered and interact with 
         each other.


SECURITY MECHANISMS FOR VAX/VMS:                SECURITY.TLK

         This presentation will describe various security mechanisms, 
         how such mechanisms might be implemented within the VAX/VMS 
         operating system, and the criteria that must be considered in 
                                                      Page 4


         the design of such implementations.

         Access control lists, non-discretionary controls, data 
         encryption, security auditing, and network proxy logins will 
         be described.  Possible implications of their implementation 
         and use within the VMS operating system will be presented.


DECnet SECURITY:                                NETSECUR.TLK


        This presentation discusses network security issues.


========> [VAX84A.SPREAD]AAAREADME.TXT;1 <========


                                 Glenn Everhart
                                  409 High St
                              Mt. Holly, NJ 08060


     Major subdirectories in this submission are:

     1.  [.LSTUTL]

              This directory contains the latest version of BIGTPC, a  fast
         tape copying routine.

     2.  [.PCCPDP]

              This is  the  PDP-11  version  of  the  PORTACALC  electronic
         spreadsheet.

     3.  [.PCCVAX]

              This the the  VAX-11  version  of  the  PORTACALC  electronic
         spreadsheet.

========> [VAX84A.TI]AAAREADME.TXT;1 <========


                          submitted by:  Kevin Mallory
                               Texas Instruments
                            P.O. Box 226015, MS 238
                                Dallas, TX 75266

     1.  [.DM]

              This  directory  contains  rewrites  of  the  DM   (directory
         management) and SF (show file) programs.

     2.  [.EDIT]

              This directory contains enhancements to the user interface to
         the EDT editor.

========> [VAX84A.UDENVER]AAAREADME.TXT;1 <========


                           submitted by:  Louis Krupp
                              University of Denver
                                  2020 S Race
                                Denver, CO 28028

     1.  [.SCRFT]

              SCRFT is a screen package for foreign terminals.

     2.  [.TPDUMP]

              TPDUMP contains a tape dump routine.

========> [VAX84A.VAXDIAL]AAAREADME.TXT;1 <========


[VAXDIAL]

        VMS dialout and connect program

        Submitted by 
                Richard Garland
                Columbia University Chemistry Department
                Box 351 havemeyer Hall
                Columbia University
                New York NY 10027

                (212) 280-3183

Purpose:
        This program will connect to another port on a VMS system
which can be used for DIALOUT to other systems and then connect to
the other system as a terminal.  It allows session logging, and 
can spawn DCL or a KERMIT subprocess.  Another protocol (MODEM7,
VAXNET etc.) could easily be put in as a subprocess.  This assumes
the use of the latest VMS KERMIT (Stevens) version 3.0.051 available
on this DECUS tape.  The program writes a message to the accounting file
so that accounting of use of a dialout line can be done.


        The DIALOUT subroutine assumes a Vadic VA212PAR autodialer
modem but should be easy to change for other dialers.  There is 
a SIGNON routine which can be used for automated or blind log ins.

I wish to add a command interface and make the DIALOUT and SIGNON 
routines table driven but there was no time.  If someone does any
thing please send me your results.

Routines
        VAXDIAL.FOR     - source
        VAXDIAL.CMN     - include file
        VAXDIAL.COM     - builds the program with debugging on
        VAXDIAL.EXE     - executable (no debugging)
        DIAL.COM        - prototype file to run the program.  You
                          must change this for your installation.

The routine will generate 2 files:
        VAXDIAL.LOG     - if session logging is on
        VAXDIAL.DBG     - if D_LINES are enabled: useful for
                          getting a new dialer or new signon to work.



Enjoy
                                        Rg
