^     ^
                                  / \   / \
                                 /   \ /   \
                                /     O     \
                               /             \
                               --------------- 


This submission from Medtronic, Inc. contains the following utilities.  They
were discussed in the session "So Much To Do, So Little Time ..." at the 
regional DECUS symposium in Minneapolis, MN on September 28th, 1989.


  1. MAINT.  This provides a user-friendly interface to general system
       management tasks.  Its features include adding/deleting a user or
       UIC group from the system, reenabling a user's signon, modifying a
       user's diskquota, displaying all active signons, making a user's
       signon captive / uncaptive with respect to using All-in-1, and giving
       our production fiche library world read access (needed for our batch
       production environment below).  Its intended audience is system
       managers and "Help Center" (trouble desk) personnel. 
            *** NOTE: Full documentation is provided in OPERDOC. ***

  2. BACKUP/RESTORE.  These utilities provide a user-friendly interface to
       backing up and restoring disks.  Using online journal files created 
       during the backup, restores are performed by first verifying the file
       (or files) was backed up and then performing the actual restore.
            *** NOTE: Full documentation is provided in OPERDOC. ***

  3. OPLOGEXTRACT.  (This is in [.OPLOG].)  This program provides a summary
       of all events in the SYS$MANAGER:OPERATOR.LOG files, with usually 1 line
       per event to save space.  At our shop, this is appended to historical
       files and then retained indefinitely.  Used in coordination with the
       "SET AUDIT" command, this is useful for tracking changes to the UAF, 
       when breakins were attempted, etc.  A summary report of selected events
       (the actual selection is under site control) is also created and sent to
       system manager.  As we cycle our OPERATOR.LOG files nightly during
       backup, I automatically get a summary report of the previous day's
       activities first thing the next morning.  The versions included are
       for clustered and non-clustered environments between VMS 4.7 and 5.2.
       Since we just installed VMS 5.2 and substantial changes were made to
       the format of the OPERATOR.LOG file, the 5.2 version formats most
       messages correctly, but hasn't been thoroughly tested.  This will be
       resubmitted at a later time with an updated version.

  4. Performance Monitor. (This is in [.PMON].)  These programs are based on
       MONITOR, a free alternative to VPA and SPM.  They provide a flat file
       for input to a customized capacity planning and performance database,
       which is not included.  It also produces an exception report for those
       items which exceed a given tolerance.

  5. DECnet Monitor.  (This is in [.DNMON].)  The purpose of these programs
       is to gather statistics about the DECnet environment and summarize them
       into historical files for later manipulation by a capacity planning and
       performance system, which is not included.  Samples of the output
       reports are included.  These programs work whether the lines are
       synchronous DECnet, asynchronous DECnet, or Ethernet.

  6. Batch Production Environment.  (This is in [.BPROD].)  We have a need for
       scheduling large batch jobs during non-prime hours.  The jobs must
       follow a schedule and certain order, like a traditional mainframe 
       production environment.  We also need to charge back for system
       resources.

  7. Q Utility.  This allows all users to get basic information about all batch
       and print queues on the system.  Certain queues may be excluded.  There
       is usually 1 line per entry.  This is an updated version of the original
       submitted on the 1987 Fall VAX SIG tape.

  8. FTNLIB.  This FORTRAN library contains callable subroutines that include
       number conversion between display and binary formats with options for
       left- or right-justification, sign overpunch (a la COBOL), leading, or
       trailing, and space- or zero-filling; banner page subroutine, to 
       simulate a VAX banner page (used by our Xerox interface program); and
       sending and receiving operator messages.

  9. Operator Documentation.  (This is in [.OPERDOC].)  These files are all
       of the documentation that we use in house.  It includes information
       about normal system operations as well as documentation of our
       utilities, all of which are included in this saveset.

 10. Miscellaneous.  (This is in [.MISC].)  These include programs to convert
       from carriage return carriage control to FORTRAN carriage control;
       a BRIDGE utility to exchange large amounts of data via tape between our
       VAXes, IBM S/38 and AS/400, and Sperry 1100 systems; shared printer
       routing between the Sperry, Prime, and VAX systems; and an interface to
       our Xerox 8700 laser printer.

              October 31st, 1989
              Roger G. Ruckert
              Senior Software Analyst
              Medtronic, Inc.
              Mail Stop B100
              7000 Central Ave. 
              Minneapolis, MN  55432

              (612) 574-4742