1                                                                   1
-
                   M T S   D I S T R I B U T I O N   4.0
-                     (Revised for Distribution 4.1)
-                                May 1978
-                              General Notes
-
          MTS, the Michigan Terminal System, is distributed using two
+                  _        _        _
     types of tapes:  (1) IBM TSS VAM2 format dump/restore tapes  for
     a single pack (3330 mod 1) MTS system designed to be used as the
     base   system   (for  new  installations)  or  for  testing  and
     conversion (for old installations), and (2) tapes  generated  by
     the  MTS  *FS program which contain the source, object, command,
     data, and print files for the system.  The *FS tapes are "volume
     label only" (VLO) tapes; they must be mounted using the  keyword
     LBLTYPE=VLO.
0         In  addition  to  the general information contained in this
     writeup, there are two other writeups which give  more  specific
     information  about installing MTS, one for new installations and
     one for old.  A hardcopy of the appropriate writeup is  included
     (item 10033 or 10034); both are available on the *FS tapes.
0         Distribution   4.0   (September   1977)   was   a  complete
     distribution of the system.  Supplemental distribution D4.1  was
     completed  in  May  1978.   It differs from D4.0 in that the *FS
     tapes contain only those components which have been added to the
     system or changed since D4.0.  Other components are not included
     since they may  be  obtained  from  the  D4.0  *FS  tapes.   For
     installations  which did not receive D4.0 when is was originally
     issued, the *FS tapes for D4.0 are included with D4.1.  However,
     the dump/restore tapes for D4.0 are not included since the  D4.1
     dump/restore tapes provide a complete, current system.
0         Throughout  the  distribution,  reference  is  made  to the
     components of  the  distribution.   Generally  these  references
     consist of a 3- or 4-digit component number, usually followed by
     a  slash  and  a  subcomponent  number.   For  example,  the MTS
     accounting  system  has  been  assigned  component  number  104.
     However, the accounting system actually has many "pieces" and so
     it  consists  of  well  over  100  subcomponents, beginning with
     number 104/1.
0         New  components  numbers   are   assigned   by   each   MTS
     installation  in  ranges.   The  number  of  a component doesn't
     necessarily indicate which installation is responsible  for  its
     maintenance   (see   the   SHARE  code  for  that),  just  which
     installation originally assigned the number.
1                                                                   2
-
          The installation assignment ranges are as follows:
0          Range         SHARE     Installation Name
0        0001-0999        UM       University of Michigan
         1000-1199        UBC      University of British Columbia
         2000-2199        UNE      University of Newcastle upon Tyne
         3000-3199        UQV      University of Alberta
         4000-4199        WSU      Wayne State University
         4200-4399        RPI      Rensselaer Polytechnic Institute
         4400-4599        SFU      Simon Fraser University
         4600-4799        EMB      EMBRAPA (Brasilia)
0         The *FS tapes are generated by the MTS *FS program based on
     information contained in a data file (known as a  driver  file),
     each  line  of  which describes a component (or subcomponent) of
     the system.  Each component has a name, a subcomponent  name,  a
     SHARE  installation  code, a type (source, object, MTS commands,
     etc.), a location (the file or tape  where  it  is  located),  a
     contact  person  at the installation principally responsible for
     its maintenance, a locally responsible person, a revision  level
     (revision  level  "A"  has  been  used to mark the subset of the
     driver file which is included in D4.1), and a disk  name  (which
     gives the file name, if any, on the dump/restore pack where this
     component is located).
0         The driver file editor program (*DEDIT) may be used to edit
     and  print  a  driver file.  In the distributed driver file, the
     local persons, when given, are UM people for non-UM  components;
     each  other  installation  should  use *DEDIT to fill in its own
     local names for components assigned to other installations.   In
     this  way,  a  printout  may be produced (using the *DEDIT PLIST
     command) for each programmer, showing the components  for  which
     he or she is responsible.
0         As *FS generates the distribution tapes, it adds additional
     information  to  each  line  in  the  driver  file  such  as the
     distribution tape name and file number on which it  has  written
     the  component  (tapes  are  named D4Tn and D4.1Tn), a generated
     name for the component (known as the FS name), information about
     the file size or tape blocking information if the component  was
     located  on  a regular (non-FS) tape, and the time and date when
     the file was saved.  Components may be obtained from these tapes
     using the *FS RESTORE command, either by  reference  to  the  FS
     name or to the file number.
0         Two  versions of the distribution driver file are provided:
     461/6 for the 6250 bpi tapes, and 461/7 for the 1600 bpi  tapes.
     The  two  versions  are  identical except for the tape names and
     file numbers which differ because of the need for more tapes  at
     1600 bpi.
0         A printed copy of the appropriate driver file listing (6250
     or  1600) is included in the distribution.  Additional copies of
     this listing may be printed using the FULL and LIST commands  in
     *DEDIT.  The listing is ordered by component number and includes
1                                                                   3
-
     descriptive  comments  about each component.  The revision level
     "A" is printed immediately after the component number for  those
     components  which  have  been  included in D4.1.  For these, the
     tape name will be shown  as  D4.1Tn,  whereas  other  components
     which  have  not changed since D4.0 will have a tape name of the
     form D4Tn.  Both driver files are on the *FS tapes  and  on  the
     dump/restore    pack    (in   the   files   MTS:DRIVER6250   and
     MTS:DRIVER1600) along with the comment file (MTS:COMM), which is
     used by *DEDIT for the descriptive comments associated with each
     component.  Care should  be  taken  to  never  change  the  line
     numbers  in  a  comment  file  since there are pointers (by line
     number) from the driver files into the comment file.
0         A printed copy of the appropriate driver file  index  (6250
     or  1600)  is also included.  It provides a alphabetized list of
     the components facilitating  use  of  the  driver  file  listing
     (which  is  in numerical order).  Additional copies of the index
     may be printed by copying the appropriate file to *PRINT*.   The
     6250   index   is   component   461/13   (MTS:INDEX6250  on  the
     dump/restore  pack);  the  1600  index   is   component   461/14
     (MTS:INDEX1600 on the pack).
1                                                                   4
-
                  DESCRIPTION OF THE DRIVER FILE LISTING
+                 ___________ __ ___ ______ ____ _______
-
          The  following  is a description of the driver file listing
     produced by the LIST and PLIST commands in  *DEDIT  (461/1).   A
     printed  copy  of the appropriate listing (for 6250 or 1600 bpi)
     is  included  in  the  distribution.   For  each  component  (or
     subcomponent),  two lines of output are printed, followed by any
     comments associated with the component.
-
0    LINE 1
+    ____ _
0         Num - component number and subcomponent number (if any)
+         ___
          R - revison level (if any) of the component or
+         _
               subcomponent:
               A - D4.1
          Component Name - name of the component
+         _________ ____
          Subname - name (if any) of the subcomponent
+         _______
          Type - component type as follows:
+         ____
               B - binary (non-360/370) object
               C - MTS commands
               D - data
               L - listing
               M - messages
               O - object (OC=cards, OE=link-edited, OL=library)
               P - printed output (PF=FORMAT, PT=TEXT360,
                    PX=TEXTFORM)
               S - source code (SA=assembler, SF=FORTRAN, SG=GOM,
                    SP=PL/I, SS=SNOBOL4, SM=assembler macros, SX=XPL,
                    S3=PL360, S6=Algol68)
               U - update deck (UC=*CDUPDATE, UU=*UPDATE,
                    UI=*IEBUPDAT, UE=$EDIT commands)
               W - writeup input (WF=FORMAT, WT=TEXT360, WX=TEXTFORM)
          G - "goodness" code (G=good, O=OK, S=shakey (has bugs),
+         _
               B=bad (needs rewrite))
          Seq ID - sequence id applied to component as it was saved
+         ___ __
          S - save control (blank means normal, "#" means not
+         _
               distributed, "@" means information incomplete, "="
               means temporary hold, ">" means very large component)
          Location - file or tape from which the component was
+         ________
               obtained.  For tapes, the first parameter is the rack
               number, the second and third are the volume name (if
               labeled) and the tape id (if different from the volume
               name), then follow keywords for the label type,
               blocking format, and DSNAME (if any).
          File - the file number if the component was obtained from
+         ____
               tape (optional for labeled or *FS tapes)
1                                                                   5
-
     LINE 2
+    ____ _
0         Tape - name of distribution tape on which the component was
+         ____
          saved
          File - *FS file number on distribution tape
+         ____
          FS Name - FS name assigned to component as it was saved
+         __ ____
          Ver - *FS version number assigned to component as it was
+         ___
               saved
          Ftype - the file type (LINE or SEQ)
+         _____
          LRECL - the maximum record length of the component
+         _____
          Size - the size of the component (in pages if the DevT
+         ____
               field is PAGE, in tracks if DISK)
          DevT - the device type from which the component was
+         ____
               obtained (PAGE for non-FS tapes and files, DISK for
               items obtained from older (before the page-formatted
               file system) *FS tapes)
          SHARE - installation SHARE code for the installation
+         _____
               responsible for maintenance
          Person - the person responsible for the component at the
+         ______
               installation given in the SHARE field
          Local Per - the person responsible for the component at the
+         _____ ___
               local installation
          Date and Time - date and time component was saved
+         ____     ____
-
0    LINE 3
+    ____ _
0         Disk Name - name of the file (if any) on the dump/restore
+         ____ ____
               pack where component is located (the save control
               field controls whether it is also on the *FS tapes)
1                                                                   6
-
                        TAPES FOR NEW INSTALLATIONS
+                       _____ ___ ___ _____________
0    6250 bpi:
+    ____ ___
0         D4.1T1    *FS format (854 files)
          D4T1      *FS format (1327 files)
          D4T2      *FS format (1206 files)
          D4T3      *FS format (777 files)
          D/R       IBM TSS VAM2 Dump/Restore  Tape,  beginning  with
                    IPLable   decks  for  the  TSS  utilities  DASDI,
                    DASDDR, and VAM2UT.
-
     1600 bpi:
+    ____ ___
0         D4.1T1    *FS format (181 files)
          D4.1T2    *FS format (251 files)
          D4.1T3    *FS format (411 files)
          D4.1T4    *FS format (11 files)
          D4T1      *FS format (487 files)
          D4T2      *FS format (414 files)
          D4T3      *FS format (426 files)
          D4T4      *FS format (388 files)
          D4T5      *FS format (483 files)
          D4T6      *FS format (335 files)
          D4T7      *FS format (457 files)
          D4T8      *FS format (320 files)
          D/R #1    IBM TSS VAM2 Dump/Restore  Tape,  beginning  with
                    IPLable   decks  for  the  TSS  utilities  DASDI,
                    DASDDR, and VAM2UT.
          D/R #2    IBM TSS VAM2 Dump/Restore Tape
1                                                                   7
-
                        TAPES FOR OLD INSTALLATIONS
+                       _____ ___ ___ _____________
0    6250 bpi:
+    ____ ___
0         D4.1T1    *FS format (854 files)
          D/R       IBM TSS VAM2 Dump/Restore  Tape,  beginning  with
                    IPLable   decks  for  the  TSS  utilities  DASDI,
                    DASDDR, and VAM2UT.
-
     1600 bpi:
+    ____ ___
0         D4.1T1    *FS format (181 files)
          D4.1T2    *FS format (251 files)
          D4.1T3    *FS format (411 files)
          D4.1T4    *FS format (11 files)
          D/R #1    IBM TSS VAM2 Dump/Restore  Tape,  beginning  with
                    IPLable   decks  for  the  TSS  utilities  DASDI,
                    DASDDR, and VAM2UT.
          D/R #2    IBM TSS VAM2 Dump/Restore Tape
1                                                                   8
-
                     USE OF TSS DASDI AND DUMP/RESTORE
+                    ___ __ ___ _____ ___ ____________
0         The IBM TSS (Release 2.0)  DASDI,  DUMP/RESTORE,  and  VAM2
     UTILITIES  programs  are  at  the  beginning  of the distributed
     dump/restore tapes.  Printed copies of the  writeups  for  DASDI
     and DUMP/RESTORE are included in the distribution as item 10010,
     previously distributed with D4.0, and therefore not included for
     old installations.
0         The  MTS  DASDI program (598) (not stand-alone) may be used
     (if MTS is available) to initialize a pack in VAM2  format;  use
     of  this program is described in the MTS Operator's Manual (item
     10041).  The TSS DASDI (stand-alone) on the  dump/restore  tapes
     will initialize a pack in either VAM2 or SAM format; it has been
     modified  at  UM  to  accept  device  addresses  as high as FFF.
     IPLing the dump/restore tape once will load TSS DASDI.
0         MTS  file  system  volumes   (such   as   the   distributed
     dump/restore  pack) must be VAM2 format and are normally labeled
     MTS001,  MTS002,  etc.   The  public  volume  number   for   the
     distributed  dump/restore  pack  must be 1.  MTS packs should be
     VOLTYPE=PUBLIC and the  PAT  should  be  placed  on  a  cylinder
+                                 ______  __  ______  __  _  ________
     boundary  (the PATD STRTADR parameter should be evenly divisable
+    ________
     by 57) near the middle of the pack.
0         The following TSS DASDI control cards are for a 3330-1 with
     volume  label  MTS001.   To  DASDI  a  3330-11,  use  TODEV=333B
     (instead of 3330) and STRTADR=23199 (instead of 11685).
0        JOB     INITIALIZE 3330-1 AS MTS001
         MSG     TODEV=1052,TOADDR=53F
         DADEF   TODEV=3330,TOADDR=440,FORMTYPE=VAM2,               X
                 VOLID=SCRATCH,VOLTYPE=PUBLIC,PUBVOLNO=1
         VLD     NEWVOLID=MTS001
         PATD    STRTADR=11685
         END
         LASTCARD
0         If  a  paging  disk  is  to  be  used,  it  should  also be
     initialized as a VAM2 pack  with  VOLTYPE=PAGING  and  a  volume
     label of PAG001.  No PUBVOLNO keyword is required in this case.
0         The  HASP  spooling  pack(s)  should  be initialized as SAM
     pack(s) with volume label(s) SPOOL1, SPOOL2, etc.  The following
     are sample control cards (which have not been tried) for a  HASP
+                                         ___
     DASDI:
0        JOB     INITIALIZE 3330-1 AS SPOOL1
         MSG     TODEV=1052,TOADDR=53F
         DADEF   TODEV=3330,TOADDR=440,FORMTYPE=SAM,                X
                 VOLID=SCRATCH,FLAGTEST=NO
         VLD     NEWVOLID=SPOOL1
         VTOCD   STRTADR=1,EXTENT=1
         END
         LASTCARD
1                                                                   9
-
          To   load   TSS  DUMP/RESTORE,  IPL  from  the  distributed
     dump/restore tape and, when the  tape  stops,  IPL  again.   The
     following are sample control cards for restoring the distributed
     dump/restore  tape  to  a 3330-1 which has been initialized with
     the label MTS001.  To  restore  to  a  3330-11,  use  TODEV=333B
     (instead of 3330).
0        JOB     RESTORE MTS001 FROM TAPE
         MSG     TODEV=1052,TOADDR=53F
         RESTORE FROMDEV=2400,FROMADDR=681,TODEV=3330,              X
                 TOADDR=440,FORMTYPE=VAM2,VOLID=MTS001,             X
                 NEWVOLID=MTS001
         END
0         After  restoring the distributed dump/restore pack, you are
     ready to proceed with the installation of MTS.  We have provided
     two writeups to assist in doing this, one for new  installations
     (item 10033) and another for installations which have previously
     used MTS (item 10034).
1                                                                  10
-
                            PATCHING THE SYSTEM
+                           ________ ___ ______
-    Patching shared memory:
+    ________ ______ _______
0         Find out where the deck to be patched is loaded by checking
          a current map, by checking the file SEG2:S2MAP, or by using
          the  LOADINFO CLS (enter the MTS command "#CLS W009:I" from
          a privileged user id, i.e., an id that can set PROT=OFF).
0         Use the System Status Routine (SSRTN) command
0              DISPLAY   loc[+disp[+disp ...]]  [n]
0         to display memory and the SSRTN command
0              MODIFY  loc[+disp[+disp ...]]  value[[,]value ...]
0         to change it.  For example
0              DISPLAY 218500+6DBA
0              MODIFY  218500+6DBA  47F0
0         These SSRTN commands are legal  from  the  3270  operator's
          console  when  prefixed  with  a slash (/), as input to the
          JOBS job which may be run from any operator's  console,  or
          as  input to the $SYSTEMSTATUS command when signed on using
          a privileged MTS user id.  For a  complete  description  of
          these  and  the other privileged SSRTN commands see the MTS
          Operator's Manual.
0         SDS may also be used to modify shared memory when used from
          a privileged id.  In addition, the supervisor commands  DIS
          and  MOD  may be used to display and modify routines loaded
          into unpaged memory (segment 0), but these commands are not
          legal when issued from a 3270 operator's console.
0         The IPLREADER has commands  which  allow  a  system  to  be
          patched  at  IPL  time, see the IPLREADER description (item
          10037) for more information.
-    Patching the System Object Deck:
+    ________ ___ ______ ______ _____
0         Using RAMROD (MTS:RAMROD), CREATE a  new  system  from  the
+                                    ______
          current system or GET a previously created system which has
+                           ___
          not  yet  been  made  current,  but  which  will become the
          current system after the  patches  are  made.   Item  10038
          contains  a description of the use of RAMROD.  Enter enough
          comments so that other people can tell what you've been  up
          to.   You  will  have  been  prompted  for  comments if you
          created a new system, otherwise you may  use  the  ANNOTATE
+                                                            ________
          command to add comments.
0         Add REP cards to the deck(s) using the PATCH command.
+                                                _____
1                                                                  11
-
          RENAME  the  new  system  with the correct version name and
          make it CURRENT.
+                 _______
0         For example:
0          # run mts:ramrod
           # EXECUTION BEGINS
             Using file "MTS:ROD"
             Proceed.
             list current
             UG117 created from UG057 23:06:01 08-11-77
               08-11 23:00 REPLACED UMMPS TO FIX BUG IN GETSTK//SETSTK
             create newsys from ug117
             Enter comments :
           ? 08-24 21:05 Just an example
           ?
             Done.
             patch taskstat
             Address Esdid Text <comments> :
           ? 30 01 58F0 just an example patch
           ?
             Enter comments :
           ? 08-24 just an example patch
           ?
              REP  000030  0158F0 example patch 21:15:25 08-24-77 W163
             OK  ? ok
             Done.
             rename newsys ug247
             "NEWSYS" is a system.
             ** RENAME system "NEWSYS" as "UG247" :
             OK  ? ok
             Done.
             current
             There are 3 IPL files with prefix "*IPL.   "
             Loading system "UG247"
             LOAD: Resident: 1000-27D80 UMLOAD Psect: 58000
                   Pageable: 6C000-ACD90 End: AFFFF
             Contents of IPL file "*IPL.2":
             UL177 ENTRY=26E08 PSECT=100008 VIRTUAL=58000...ACD90
             WRITTEN BY ID MTA. AT 06:24:38 07-17-77
             COM 07-14 20:00 CHANGED CONFIG.CARD TO GIVE MORE SPACE TO
                             SEGMENT 0 FOR BIG MACHINES
             COM 07-14 21:59 REPLACE TASKSSTAT, MINOR CHANGES.
             COM 07-15 13:35 NEW TABLES TO ADD MORE JOB TABLES.
             COM 07-17 06:20 REPLACED PDP WITH WHAT I HOPE IS THE D4.0
                             VERSION.
             ** Write system "UG247" to IPL file "*IPL.2":
             OK  ? ok
             System "UG247" has been written to  IPL file "*IPL.2"
             IPL file stacked has been pushed.
             System "UG247" is now the current system.
             "UG247" : Released.
             System "UG247" has been Frozen.
             Done.
             stop
           # EXECUTION TERMINATED
1                                                                  12
-
     Remember to Change the Source:
+    ________ __ ______ ___ _______
0         It seems almost silly to mention this, but ....
-    Patching Decks Loaded by PISTLE:
+    ________ _____ ______ __ _______
0         Decks loaded into shared VM by PISTLE (the post IPL  system
          loader)  can  be patched in memory as described above.  REP
          cards are added to the files from which  PISTLE  loads  the
          object.  It is a good idea to use PISTLE without specifying
          PAR=NOTEST to make sure the patched version will load.
0         PISTLE  can also be used to load complete new versions of a
          deck into shared VM so long as all references to the module
          are made using a low core symbol table rather than external
          references that are already  resolved,  i.e.,  if  the  IPL
          option is not used to load it.  PISTLE allows the automatic
          replacement  of  symbols  in  the  low  core  symbol  table
          LCSYMBOL; other low core symbol tables must be  patched  by
          hand.
1                                                                  13
-
                 PRINTED DOCUMENTATION IN THE DISTRIBUTION
+                _______ _____________ __ ___ ____________
-         The  following  lists  all  of the paper-copy documentation
     included in D4.1.  For installations which  previously  received
     D4.0, only those printed documents which have changed since then
     (items 10030 and above) have been shipped with D4.1.  Of course,
     all of the documents listed below are available on the *FS tapes
     except  for  those  marked an asterisk (*), which indicates that
     only a paper copy was  shipped  (no  machine  readable  copy  is
     available).   In  addition,  there are many more writeups on the
     *FS tapes for which paper copies have not been  shipped.   Using
     the  editor  on  the driver file to match for the letters "W" or
     "P" in column 45 will produce a complete list of all the machine
     readable documentation.
0         Since some paper-copy items are not distribution components
     (do not appear  on  the  *FS  tapes)  and  hence  don't  have  a
     component  numbers,  item numbers (see the list below) have been
     assigned.  The component number for all items on tape  is  given
     in  parentheses  after  the  items  in the list.  The paper copy
     which is sent with the distribution is stamped with both numbers
     (if  applicable).   [To  make  them   readily   distinguishable,
     component  numbers  are  always  given with a slash and are less
     than 10000; the printed documentation item  numbers  start  with
     10000 and go up.]
0         No  printed copies of the volumes of the UM MTS Manual have
     been included with the initial shipments of  this  distribution,
     but  the  TEXT360 master and print files are included on the *FS
     tapes.  If your installation needs a printed copy of any of  the
     MTS volumes, send a request to:
0        W. Scott Gerstenberger
         The University of Michigan
         Computing Center
         1075 Beal Avenue
         Ann Arbor, MI 48109
         USA
0    The  audio tapes of the 33 system lectures given by the UM staff
     during 1973 have not been updated and are not  included  in  the
     distribution,  but  are  available on request.  In addition, the
     documentation for the QUIC (584) and KWIC (583) programs has not
     been included, but is available on request.
-    Installation of MTS
+    ____________ __ ___
0              10030.    General Notes, what  you  are  reading  now.
                         (461/10)
               10031A and 10031B.   Driver file listing (LIST command
                         output from *DEDIT).
               10032A and 10032B.   Driver  file  index;  a   listing
                         sorted by component names which serves as an
                         index for 10031.  (461/13 and 461/14)
1                                                                  14
-
               10033.    Installation     instructions     for    New
                         Installations.  (461/8)
               10034.    Installation    instructions     for     Old
                         Installations.  (461/9)
               10035.    Description   of  D4.1  System  Object  Deck
                         (468/7)
               10036.    Tables writeup (004/3)
               10037.    Documentation for the IPLREADER and friends.
                         (1021/9)
               10038.    Documentation   for   the   RAMROD    System
                         Maintenance Utility.  (1019/9)
               10039.    DECKGEN instructions (004/7)
         *     10010.    TSS DASDI and DUMP/RESTORE instructions.
         *     10040.    UM Machine Configuration Chart.
-    General
+    _______
0              10012.    Message Manual (555/5)
-    Operations
+    __________
0              10041.    MTS Operator's Manual (592)
               10014.    HASP Operator's Guide (387/26)
         *     10015.    HASP Remote 360/20 Operator's Guide
         *     10016.    HASP Remote 360/non-20 Operator's Guide
         *     10017.    HASP Remote 1130/1800 Operator's Guide
         *     10018.    HASP Remote System/3 Operator's Guide
         *     10019.    HASP   2780  Remote  Workstation  Operator's
                         Guide
-    Software Internals
+    ________ _________
0              10042.    HASP Notes.  (387/30)
         *     10021.    SDS Storage Allocation.
-    How-To-Use Information
+    __________ ___________
0    For systems or administrative users:
               10043.    Printing jobdumps.  (400/14)
         *     10023.    Modifying *LIBRARY.
         *     10024.    Specifying keywords for EREP/370 (IFCEREP0)
0    For general user:
               10044A and 10044B.  List of current  CCMemos  (461/15)
                         and the CCMemos themselves.
         *     10026.    Computing  Center  Newsletter  (v5n6 through
                         v7n14)
         *     10045.    Computing Center Newsletter  (v7n15  through
                         v8n9)
               10046.    List   of   Computing   Center  Publications
                         (461/22)
         *     10028.    MTS Reference Summary
1                                                                  15
-
                       LISTINGS IN THE DISTRIBUTION
+                      ________ __ ___ ____________
-         Listings have been included on the *FS tapes for  the  most
     important components of the system.
-        Comp #     Component Name
0        0042/6     MTS                 (370 listing)
         0042/7     MTS                 (360 listing)
         0045/5     SUPERVISOR          (370 listing)
         0045/6     SUPERVISOR          (360 listing)
         0046/5     CONFIG              (370 listing)
         0046/6     CONFIG              (360 listing)
         0198/5     GUINFO/CUINFO       (370 listing)
         0198/6     GUINFO/CUINFO       (360 listing)
         0354/5     LLXU                (370 listing)
         0354/6     LLXU                (360 listing)
         0387/14    HASP
         0464/5     PLIMIT              (370 listing)
         0464/6     PLIMIT              (360 listing)
         0539/5     TIMNTRP             (370 listing)
         0539/6     TIMNTRP             (360 listing)
         0578/5     RSF                 (370 listing)
         0578/6     RSF                 (360 listing)
         0635/5     FSUB                (370 listing)
         0635/6     FSUB                (360 listing)
         0636/5     CMDS                (370 listing)
         0636/6     CMDS                (360 listing)
         0637/5     DSRS                (370 listing)
         0637/6     DSRS                (360 listing)
         0638/5     USUB                (370 listing)
         0638/6     USUB                (360 listing)
         0639/5     DSRI                (370 listing)
         0639/6     DSRI                (360 listing)
         4000/4     GATE                (370 listing)
         4000/5     GATE                (360 listing)
1                                                                  16
-
        PEOPLE LIST FOR THE UNIVERSITY OF MICHIGAN COMPUTING CENTER
+       ______ ____ ___ ___ __________ __ ________ _________ ______
-         The following is a list of UM Computing Center people whose
     names  appear  in the "person" field of the driver file listing.
     An asterisk (*) before a name means that  the  phone  number  is
     (313)   764-9595,   otherwise   it   is   (313)  764-2121.   All
     correspondence should be addressed to:
0              The University of Michigan
               Computing Center
               1075 Beal Avenue
               Ann Arbor, MI 48109
               USA
0         BODWIN      Bodwin, James M.
          BRILL       Brill, Robert C.
          DONNELLY    Donnelly, Stephen M.
       *  DWB         Boettner, Donald W.
       *  EMERY       Emery, Allan R.
       *  ENGLE       Engle, Charles F.
       *  FLANIGAN    Flanigan, Larry K.
          FLOWER      Flower, David S.
          FRONCZAK    Fronczak, Edward J.
          GOEN        Goen, William
          GOODRICH    Goodrich, Andrew C.
          H YOUNG     Young, Howard B.
          HANSEN      Hansen, James H.
       *  HARDING     Harding, Leonard J.
          HELFFRICH   Helffrich, George R.
       *  K YOUNG     Young, Kathleen A.
       *  LIFT        Lift, Gail H.
          LUBBERS     Lubbers, Clark E.
          MANUAL      (see SALISBURY)
          MERIT       (see OGDEN)
       *  MTA         Alexander, Michael T.
          OGDEN       Ogden, Jeffrey C.
       *  PIRKOLA     Pirkola, Gary C.
       *  SALISBURY   Salisbury, Richard A.
          SHERRY      Sherry, Patrick M.
          STERKEN     Sterken, James J.
          SWARTZ      Swartz, Fred G.
       *  SWEET       Sweet, Elizabeth A.
          TIFFANY     Tiffany, L. Bernard
          UNSP        (see OGDEN)
       *  WSG         Gerstenberger, W. Scott
1                                                                  17
-
          Correspondence related to  the  administration  of  the  UM
     Computing Center should be sent to the acting director:
0              Dr. Allan R. Emery, Acting Director
               The University of Michigan
               Computing Center
               1075 Beal Avenue
               Ann Arbor, MI 48109
               USA
0              Telephone (313) 764-9572
0    or,  after  1  September  1978,  to  the  new director Dr. Aaron
     Finerman at the same address.
1                                                                  18
-
                   DISTRIBUTION 4.1 INITIAL MAILING LIST
+                  ____________ _ _ _______ _______ ____
-
          The following is a list of  persons  to  whom  the  initial
     shipment of MTS Distribution 4.1 has been sent:
-
     UBC       Computing Centre                  6250 bpi
               ATTN:  John Hogg
               University of British Columbia
               Vancouver, B. C.  V6T 1W5
               CANADA
0    UNE       Computing Laboratory              1600 bpi
               ATTN:  Program Librarian
               The University
               Newcastle upon Tyne   NE1 7RU
               ENGLAND
0    UQV       Computing Services                6250 bpi
               ATTN:  John Stasiuk
               The University of Alberta
               Edmonton, Alberta T6G 2H1
               CANADA
0    WSU       Computing and Data Processing     6250 bpi
               ATTN:  Natalie Frazis
               Wayne State University
               Detroit, MI 48202
0    RPI       Office of Computer Services       1600 bpi
               ATTN:  Wilson Dillaway
               Rensselaer Polytechnic Institute
               Troy, NY 12181
0    SFU       Computing Centre                  6250 bpi
               ATTN:  Charlie Benet
               Simon Fraser University
               Burnaby, B. C.  V5A 1S6
               CANADA
0    AMD       Amdahl Corporation                6250 bpi
               ATTN:  Bill Ehrman
               1250 East Arques Avenue
               Sunnyvale, CA 94086
0    EMB       EMBRAPA DMQ                       1600 bpi
               ATTN:  Stanley Angilley
               Venancio 2000, 7 Andar, W3 Sul
               70.000 Brasilia D. F.
               BRAZIL
