1                                                                   1
-
                   M T S _ D I S T R I B U T I O N _ 3.0
+                  _ _ _   _ _ _ _ _ _ _ _ _ _ _ _   ___
0                               August 1973
0                              General Notes
-         Distribution 3.0 consists of 6 tapes for the 1600 bpi  copy
     or  9  tapes  for  the 800 bpi copy.  All tapes are unlabeled to
     save space.  The last tape of each set is a  dump/restore  tape,
     designed  to  be  used to get started (for new installations) or
     for conversion (for old installations).  Instructions for  these
     procedures are given in items 1001 and 1002 of the documentation
     list   (later   in  this  writeup).   The  remaining  tapes  are
     "Distribution Utility" tapes containing source, object, command,
     data, and print files, designed to be read  by  *FS  or  by  the
     Distribution program, which is a superset of *FS.  A writeup for
     this distribution version of *FS is enclosed (item 1003).
0         Throughout   the   documentation   for  this  distribution,
     reference  is  made  to  the  components  of  the  distribution.
     Generally  these  references  are  made by the 3-digit component
     number, sometimes followed by a slash and a 1- or  2-digit  sub-
     component number.  For example, the G assembler (*ASMG) has been
     assigned  component number 066.  However, the assembler actually
     has many "pieces" and so the assembler  consists  of  components
     066/1  through  066/60.   Component  numbers 001 through 481 are
     compatible with the numbers used in  distribution  2.0;  numbers
     above  481  are new components, or in some cases, old components
     which have been grouped under a new number.
0         Two versions of the distribution driver file are  provided:
     461/11 for the 1600 bpi tapes, and 461/16 for the 800 bpi tapes.
     The  driver  file  is  the  master file used by the distribution
     program when it generated the tapes.  Each line  in  the  driver
     file describes a component (or sub-component) including its name
     and  sub-name,  SHARE  installation  code, type (source, object,
     commmands, etc.), location (what file or tape  it  was  obtained
     from),  the  output  tape  name and file on which it was written
     (tapes are named D3Tn, file numbers start at 1  on  each  tape),
     the  FS name used on the output tape, the person responsible for
     the component, information about the file size of the  component
     or tape blocking information if the component came from a non-FS
     tape, the time and date when the file was saved, and, finally, a
     line  number  pointer  into  a  comment  file  where descriptive
     comments for the component have been saved.  A paper copy of the
     appropriate driver file (800 or  1600),  including  interspersed
     comments, is included.  Additional copies of this listing may be
     printed  using the LIST command in the DEDIT program which is on
     the dump/restore tape.  Note: the two  versions  of  the  driver
     file  are  identical  except  for the output tape names and file
     numbers for each component since these were different at 800 and
     1600 bpi.  Both files (MTS:D3DESCR and MTS:D3DESCR.800)  are  on
     the dump/restore tape along with the comments file (MTS:D3COMM).
1                                                                   2
-
          The tapes are as follows:
0    1600 bpi copy:
+    ____ ___ _____
0         Tape 1    Distribution Utility (*FS) Format
                    459 files
                    Contains 458 components: 1 through 192 except for
                    004/4, 004/5, 004/6, 104/98, and 104/99 which are
                    on tape 5.
0         Tape 2    Distribution Utility (*FS) Format
                    374 files
                    Contains 373 components: 193 through 443.
0         Tape 3    Distribution Utility (*FS) Format
                    253 files
                    Contains  252  components: 444 through 505 except
                    for  461/11,  461/12,  461/14,  461/15,   461/16,
                    468/1, and 468/2 which are on tape 5.
0         Tape 4    Distribution Utility (*FS) Format
                    478 files
                    Contains 477 components: 506 through 577.
0         Tape 5    Distribution Utility (*FS) Format
                    262 files
                    Contains  261  components:  578  through 624, and
                    004/4,  004/5,  004/6,  104/98,  104/99,  461/11,
                    461/12, 461/14, 461/15, 461/16, 468/1, and 468/2.
                    (1200 foot reel)
0         Tape 6    Dump/Restore  Tape  (written  at 800 bpi to avoid
                    chaining checks which sometimes occur when IPLing
                    1600 bpi tapes)
                    Contains:
                         1.  TSS DASDI (IPLable deck)
                         2.  TSS DUMP/RESTORE (IPLable deck)
                         3.  TABLES deck generator (IPLable deck)
                         4.  "Regular" DASDI (IPLable  deck)  to  use
                             only  for  DASDIng SPOOL packs for HASP.
                             (Actually this is ISSDASDI - if you have
                             400 cylinder drives specify TODEV=5625)
                         5.  Simplex system  object  deck  (data  for
                             TABLES deck generator)
                         tape mark
                         6.  Dump/Restore data
                         tape mark
                         7.  Dump/Restore trailer
                         tape mark
                         tape mark
                         8.  Source for TABLES (format FB(4000,80))
                         tape mark
                         9.   Assembly  listing  of  TABLES generator
                             (format FB(6650,133))
                         tape mark
1                                                                   3
-
     800 bpi copy:
+    ___ ___ _____
0         Tape 1    Distribution Utility (*FS) Format
                    147 files
                    Contains 146 components: 1 through  66/74  except
                    for 004/4, 004/5, and 004/6 which are on tape 8.
0         Tape 2    Distribution Utility (*FS) Format
                    363 files
                    Contains 362 components: 66/75 through 212 except
                    for 104/98 and 104/99 which are on tape 8.
0         Tape 3    Distribution Utility (*FS) Format
                    266 files
                    Contains   265  components:  223  through  387/6.
                    (Note: 223 is the first one after 212.)
0         Tape 4    Distribution Utility (*FS) Format
                    207 files
                    Contains 206 components: 387/7 through 497 except
                    for  461/11,  461/12,  461/14,  461/15,   461/16,
                    468/1, and 468/2 which are on tape 8.
0         Tape 5    Distribution Utility (*FS) Format
                    141 files
                    Contains 140 components: 498 through 508/18.
0         Tape 6    Distribution Utility (*FS) Format
                    383 files
                    Contains 382 components: 508/19 through 572.
0         Tape 7    Distribution Utility (*FS) Format
                    269 files
                    Contains 268 components: 573 through 618.
0         Tape 8    Distribution Utility (*FS) Format
                    53 files
                    Contains  52  components:  619  through  624, and
                    004/4,  004/5,  004/6,  104/98,  104/99,  461/11,
                    461/12, 461/14, 461/15, 461/16, 468/1, and 468/2.
                    (600 foot reel)
0         Tape 9    Dump/Restore Tape
                    Same as Tape 6 for 1600 bpi.  See above.
1                                                                   4
-
     USE OF DASDI AND DUMP/RESTORE
+    ___ __ _____ ___ ____________
-         Two  versions  of  DASDI  are  included on the dump/restore
     tape.  The first is TSS DASDI which is used  to  initialize  MTS
     disk  packs, which are now page formatted.  The TSS DASDI should
     also be used to DASDI a 2314 paging pack if a paging disk is  to
     be  used.   The  volume  serial  numbers for MTS packs should be
     MTS001,  MTS002,  etc.   For  a   paging   pack,   use   PAG001.
     Documentation  item  1009 is the IBM TSS DASDI description, with
     an attached listing of an example control card deck for  MTS001.
     There  is no 400 cylinder page-formatted "2314" DASDI available.
     Component 598 (DASDI 7330) will initialize  an  ITEL  7330,  but
     this  program  is  designed  to run under MTS.  The TSS DASDI is
     invoked by IPLing the dump/restore tape just once.
0         The second DASDI version is the "regular"  DASDI  used  for
     initializing  HASP  packs (SPOOL1, SPOOL2, etc.).  It will DASDI
     400 cylinder "2314" packs (TODEV=5625) or  normal  200  cylinder
     packs  (TODEV=2314).  This version of DASDI is invoked by IPLing
     the dump/restore tape 4  times.   The  following  control  cards
     indicated how to DASDI a HASP pack.
0    JOB   INITIALIZE 400 CYL SPOOL1
     MSG   TODEV=1052,TOADDR=009
     DADEF TODEV=5625,TOADDR=210,VOLID=SCRATCH,FLAGTEST=NO
     VLD   NEWVOLID=SPOOL1
     VTOCD STRTADR=1,EXTENT=1
     END
0         Documentation   item  1010  is  the  IBM  TSS  DUMP/RESTORE
     description, with an attached listing of a control card deck for
     restoring pack MTS001 from the  distributed  dump/restore  tape.
     DUMP/RESTORE is invoked by IPLing the dump/restore tape twice.
1                                                                   5
-
     LISTINGS IN THE DISTRIBUTION
+    ________ __ ___ ____________
-         Listings  have  been included on the distribution tapes for
     those components every installation will likely change  so  they
     don't have to assemble it once to see what it is before they can
     change it.  Their names and component/sub-component numbers are:
-        MTS             042/5
         MTS SUBR        042/6
         SUPERVISOR      045/6     (simplex listing)
         CONFIG          046/4
         HASP            387/9     (simplex listing)
1                                                                   6
-
     DOCUMENTATION IN THE DISTRIBUTION
+    _____________ __ ___ ____________
-         The    following   lists   all   of   the   paper-copy-only
     documentation and the machine-readable documentation sent on the
     distribution tapes, grouped into five categories.   An  asterisk
     (*)  in  front of an item in the following list indicates that a
     paper copy was shipped.  Some  documentation  is  sent  only  on
     paper copy - this is indicated by a "P" following the asterisk.
0         Since  some  items  on  the list below are not distribution
     components and do not appear on the source tapes and hence don't
     have a component number, another number (the one in front of the
     entry below) was produced.  This other number  also  facilitates
     the  packing  list.  The component number for all items on tapes
     is given in parentheses after the items in the list.  The  paper
     copy  that  is  sent with this distribution is stamped with both
     numbers (if applicable), except for  CCMEMOs  and  MTS  Manuals.
      To  make them readily distinguishable, distribution numbers are
     always given with a slash and are  less  than  1000;  the  other
     numbers start with 1000 and go up.¬
0    Distribution Documentation
+    ____________ _____________
0    This  is  documentation  concerned with the installation of this
     distribution.
         *     1000.  General Notes (461/15)
         *     1001.  Installation instructions for New Installations
                         (461/13)
         *     1002.  Installation instructions for Old Installations
                         (461/14)
         *     1003.  Writeup on the Distribution Program (461/4)
         *     1004.  Description of System Object Deck (468/3)
         *     1005.  Tables writeup (004/3)
         *P    1006.  DEDIT (distribution editor (461/5))
         *     1007.  D3DESCR printout (LIST command to DEDIT) of the
                         distribution components with comments.
         *     1008.  DECK GEN instructions (004/6)
         *P    1009.  TSS DASDI instruction
         *P    1010.  TSS DUMP/RESTORE instructions
         *P    1011.  D3DESCR listing sorted by component names which
                         serves as an index for 1007.
         *P    1012.  Restore Pack File List
-    General
+    _______
0        *     2001.  Message Manual (555)
                            (see comments in the 1007 printout)
-    Operations
+    __________
0        *     3001.  Operator's Manual (592)
         *     3002.  Operator Messages part of Message Manual (555)
         *     3003.  HASP Operator's Guide (387/20)
1                                                                   7
-
         *P    3004.  HASP Remote 360/20 Operator's Guide
         *P    3005.  HASP Remote 360/non-20 Operator's Guide
         *P    3006.  HASP Remote 1130/1800 Operator's Guide
         *P    3007.  HASP Remote System/3 Operator's Guide
-    Installation Descriptions (Internals)
+    ____________ ____________ ___________
0        *     4001.  HASP installation notes (387/21)
               4002.  Catalog description (482/34)
               4003.  Line File description (482/35)
               4004.  Sequential File description (482/36)
               4005.  Sharing description (482/37)
               4006.  *ASMG implementation (066/79)
               4007.  PLC installation (485/2)
               4008.  GASP internal description (552/5)
               4009.  Machine Check Recovery (577/46)
               4010.  SVC descriptions (045/7, 045/8)
               4011.  BASIC installation (508/33)
               4012.  UMLOAD (001/4)
               4013.  APL-GMRL installation (595/1)
               4014.  IG installation (498/30)
               4015.  PL1 installation (506/15)
         *P    4016.  SDS Storage Allocation
         *P    4017.  System copy sections
         *P    4018.  TSATBL macro description (MTS)
-    How-To-Use Information
+    __________ ___________
0    For systems or administrative users:
0              5001.  Accounting system (104/97)
               5002.  Billing program (500/9, 500/10)
               5003.  File System Test program (482/47)
         *P    5004.  Patching the system
         *P    5005.  JOBS notes
         *P    5006.  REX instructions
         *P    5007.  Filesave Copy instructions
         *P    5008.  OLTS instructions
         *P    5009.  Printing jobdumps
0    For general user:
0              6001.  *ASMG users guide (0066/77)
               6002.  Virtual 67 writeup (558/5)
               6003.  SLT diagram (601)
               6004.  *DITTO (335/3)
               6005.  ASMTIDY (410/3)
               6006.  IG Users Guide (498/29)
               6007.  FRISK (533/2)
               6008.  *ASMT (TSS Assembler) (619/26)
               6009.  Labelsniff (314/3)
         *     6010.  Projectaccount (499/2)
         *     6011.  MTS MANUALS Volume 1 (504)
         *     6012.  MTS MANUALS Volume 2 (444)
1                                                                   8
-
         *     6013.  MTS MANUALS Volume 3 (501)
         *     6014.  MTS MANUALS Volume 4 (575)
         *     6015.  MTS MANUALS Volume 5 (573)
         *     6016.  MTS MANUALS Volume 10 (574)
         *     6017.  MTS MANUALS Volume 11 (512)
         *     6018.  CCMEMO 133 (*8LINK) (234/26)
         *     6019.  CCMEMO 135 (*LISP) (210/7)
         *     6020.  CCMEMO 137 (FORTRANG) (204/6)
         *     6021.  CCMEMO 161 (WATFIV) (483/7)
         *     6022.  CCMEMO 164 (FTN addendum) (551/4)
         *     6023.  CCMEMO 165 (*8ASR) (234/27)
         *     6024.  CCMEMO 171 (*ASMG) (066/78)
         *     6025.  CCMEMO 175 (Ftn Libr) (422/14)
         *     6026.  CCMEMO 178 - PLC Users Guide (485/3)
         *     6027.  CCMEMO 179 (*SNOBOL4) (182/8)
         *     6028.  CCMEMO 181 - Wirewrap (306/21)
         *     6029.  CCMEMO 182 (REDUCE2) (556/8)
         *     6030.  CCMEMO 195 (PL1) (163/20)
         *     6031.  CCMEMO 197 (SLIP) (261/3)
         *     6032.  CCMEMO 199 - ALGOLW (528/17)
         *     6033.  CCMEMO 200 (ANALYSIS) (140/7)
         *     6034.  CCMEMO 201 (OMR) (576/3)
         *     6035.  CCMEMO 202 - SIOC (526/3)
         *     6036.  CCMEMO 203 (APL) (465/10)
         *     6037.  CCMEMO 208 - 11ASR (515/12)
         *     6038.  CCMEMO 209 (COBOL) (538/16)
         *     6039.  CCMEMO 210 (FTN I/O) (422/15)
         *     6040.  CCMEMO 214 - EFL (525/51)
         *     6041.  CCMEMO 215 (GASP) (552/4)
         *     6042.  CCMEMO 218 - TRACER (527/3)
         *     6043.  CCMEMO 220 (8LINK/8ASR) (234/28)
         *     6044.  CCMEMO 223 (SORT) (303/11-13)
         *     6046.  CCMEMO 230 (XPL) (318/14)
         *     6047.  CCMEMO 232 (FTN) (551/3)
         *     6048.  CCMEMO 236 (APL-GMRL) (595/93)
         *     6049.  CCMEMO 240 (EXPL) (495/6)
         *     6050.  CCMEMO 241 (LINKEDIT) (297/10)
         *     6051.  CCMEMO 243 (Vol 1 Update 1) (already in 504)
         *     6052.  CCMEMO 244 (CALC CLS) (585/3)
         *     6053.  CCMEMO 245 (FTN H) (551/7)
         *P    6054.  Other CCMEMOs
         *P    6055.  List of CCMEMOs
         *P    6056.  Memo crossreference
         *P    6057.  Introduction to SNOBOL4
         *P    6058.  Polygraphics Users Manual
         *P    6059.  Display File (DF) Users Guide
         *P    6060.  QUIC documentation
         *P    6061.  KWIC documentation
               6062.  PIL/2   preliminary   documentation    (566/51,
                      566/52)   (This   will   be  MTS  Vol  12  when
                      finished.)
0        *P    6063.  Computing Center Newsletter (v2n9 through v3n7)
1                                                                   9
-
     DESCRIPTION OF THE FIELDS IN THE D3DESCR PRINTOUT (1007)
+    ___________ __ ___ ______ __ ___ _______ ________ ______
-
          The following is a description of the  output  produced  by
     the  LIST  command  in the DEDIT program (461/5).  A copy of the
     output for your driver file (MTS:D3DESCR or MTS:D3DESCR.800)  is
     included  as  documentation  item  1007.  For each component (or
     sub-component), every field in the driver file line is  printed;
     this requires two lines of output.  Following the two lines from
     the  driver file, any comments associated with the component are
     printed.
-
0    LINE 1
+    ____ _
0         Num - component number and sub-number (if any)
+         ___
          Component_Name - name of the component
+         _________ ____
          Sub-name - name (if any) of the sub-component
+         ________
          Type - component type as follows:
+         ____
               B - binary (non-360) 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=TEXT/360)
               S - source code  (SA=assembler,  SF=FORTRAN,  SP=PL/I,
                    SS=SNOBOL4,    SM=assembler    macros,    SX=XPL,
                    S3=PL360)
               U - update deck (UU=*UPDATE, UI=*IEBUPDAT)
               W - writeup input (WF=*FORMAT, WT=TEXT/360)
          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  blocking  format
               and DSNAME (if any).
          File  -  the file number if the component was obtained from
+         ____
               tape (optional for labeled and *FS tapes)
1                                                                  10
-
     LINE 2
+    ____ _
0         Tape - name of output tape on which the component was saved
+         ____
          File - *FS file number on output 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 logical record length of the component
+         _____
          Siz - 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 - SHARE installation code
+         _____
          Person - the person responsible for the component (see  the
+         ______
               list below)
          Date and Time - date and time component was saved
+         ____     ____
          C_LNR  -  line number in comments file for the comments (if
+         _ ___
               any)  associated  with  this   component   (implicitly
               negative)
1                                                                  11
-
        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
     (1007).  An asterisk (*) before a  name  means  that  his  phone
     number  is  (313)  764-9595,  otherwise his number is (313) 764-
     2121.  All correspondence should be addressed to:
0              The University of Michigan
               Computing Center
               1075 Beal Avenue
               Ann Arbor, MI 48105
               USA
-
          BERSTIS     Berstis, Viktors
          BLINN       Blinn, James F.
          DE JONG     DeJong, Kenneth A.
       *  DWB         Boettner, Donald W.
       *  EMERY       Emery, Allan R.
       *  ENGLE       Engle, Charles F.
          FLANIGAN    Flanigan, Larry K.
          FRANK       Frank, Randall
          FRONCZAK    Fronczak, Edward J.
       *  GALLER      Galler, Bernard A.
          GOODRICH    Goodrich, Andrew
          HAMILTON    Hamilton, James A.
          HARDING     Harding, Leonard J.
          HENRIKSEN   Henriksen, James O.
          JWS         Sanguinetti, John W.
          LANDWEHR    Landwehr, Carl E.
          LEADER      Leader, Lynn R.
          LUBBERS     Lubbers, Clark E.
       *  MTA         Alexander, Michael T.
       *  PIRKOLA     Pirkola, Gary C.
          SALISBURY   Salisbury, Richard A.
          SMITH       Smith, Douglas B.
          TIFFANY     Tiffany, L.  Bernard
       *  WSG         Gerstenberger, W. Scott
          YOUNG       Young, Howard B.
-    Correspondence related to the administration of the UM Computing
     Center should be sent to the director:
0              Dr.  Robert C.  F.  Bartels
               The University of Michigan
               Computing Center
               1075 Beal Avenue
               Ann Arbor, MI 48105
0              Telephone (313) 764-9572
1                                                                  12
-
                   DISTRIBUTION 3.0 INITIAL MAILING LIST
+                  ____________ ___ _______ _______ ____
-
          The following is a list of  persons  to  whom  the  initial
     shipment of MTS Distribution 3.0 has been sent:
-              John Hogg
               Computing Centre
               The University of British Columbia
               Vancouver 8, British Columbia
               CANADA
-              Gerald F.  Gabel
               Computing Services
               The University of Alberta
               Edmonton 7, Alberta
               CANADA
-              J.  Keith R.  Barnett
               Computing Laboratory
               The University of Newcastle upon Tyne
               Claremont Tower
               Claremont Road
               Newcastle upon Tyne   NE1 7RU
               ENGLAND
-              Pimporn C.  Zelany
               W.  R.  Church Computer Center
               Code 0211
               Naval Postgraduate School
               Monterey, CA 93940
-              Henry Bodzin
               Computing and Data Processing Center
               Wayne State University
               Detroit, MI 48202
-              James H.  Moore
               Computation Center
               Stanford University
               Stanford, CA 94305
-              Sandra Ward
               Computing Centre
               The University of Waterloo
               Waterloo, Ontario
               CANADA
1                                                                  13
-
               Mike Randall
               University of Illinois
               Digital Computer Laboratory
