1                                                                   1
-
                               GENERAL NOTES
+                              _______ _____
-                          MTS Distribution 5.1
-                               August 1983
-
          Note: Installations receiving this distribution of MTS
+         ____
          should obtain approval from the University of Michigan
          Computing Center before distributing any part  of  the
          distribution  to  any  installation  other than one of
          those listed at the end of these notes.   In  addition
          some parts of the distribution are copyrighted, either
          by   the   University   of   Michigan   or   by  other
          organizations.  Conditions on the use  of  copyrighted
          material vary, but redistribution or redistribution to
          installations  other  than  those listed at the end of
          these notes is often restricted.
-
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  and  one  for
     existing  installations.   A hardcopy of the appropriate writeup
     is included with your distribution tapes; both are available  on
     the tapes as components 461/20 and 461/21.
0         MTS,  the  Michigan  Terminal  System, is distributed using
+                    _         _         _
     three types of tapes:  (1) dump/restore tapes for a single  pack
     MTS  system  designed  to  be  used  as  the base system for new
     installations  or  for  testing  and  conversion  for   existing
     installations, (2) a tape with several utility programs that can
     be  used  with  the  dump/restore  tapes  to build a single pack
     system at new installations where no working version of  MTS  is
     available,  and (3) tapes generated by the MTS *FS program which
     contain the source, object, command, data, and print  files  for
     the  system.   The dump/restore tapes are unlabeled, the utility
     tape uses standard labels (VOL=MTSUTL), and the  *FS  tapes  are
     "Volume  Label  Only"  tapes  which  must  be  mounted using the
     keyword LBLTYPE=VLO (VOL=5.1T1, VOL=5.1T2, ...).
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.   From  distribution to distribution, a component
     will almost  always  have  the  same  number,  but  subcomponent
     numbers  may  be changed.  Thus, for example, something may have
1                                                                   2
-
     been distributed on D5.0 with the number 104/15, while  on  D5.1
     it may be 104/16 (this could happen if a subcomponent containing
     an  update  were  inserted  between  source  and  object).   New
     component 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 (there  is
     an   installation   code  for  that),  just  which  installation
     originally assigned the number.
0         The installation assignment ranges are as follows:
0          Range         Code      Installation Name
0        0001-0999        UM       University of Michigan
         1000-1199        UBC      University of British Columbia
         2000-2199        UNE      University of Newcastle upon Tyne
         2200-2399        UD       University of Durham
         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        UZ       University of Zagreb
         4800-4999        RIO      CNPq/CBPF/GPD (Rio de Janeiro)
         9000-9999        UM       Used for redistributions only
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, an optional subcomponent
     name, an installation code, a type  code  (source,  object,  MTS
     commands, etc.), a location (the file name or tape from which it
     was  obtained), a contact person at the installation principally
     responsible for its maintenance, a  locally  responsible  person
     (optional), an optional disk name (which gives the file name, if
     any,  on  the  dump/restore  pack  where  this component is also
     located), and an optional revision level.  If a file name in the
     disk name field has the string "@E" appended, an empty  file  is
     moved  to  the test pack.  This is handy for log files which are
     usually not included on the *FS tapes, but which must be present
     on the test pack.  File names in the disk name  field  may  also
     include  sufixes  of the form "@UM" to indicate that the file is
     to be included on the UM test pack, but is not normally sent out
     on the standard distribution test pack.
0         Revision level "A" denotes subcomponents  which  have  been
     changed  in  the  UM  production system since D5.0 (Sept.  1981)
     (however,  these  may  have  been  included  in   one   of   the
     redistributions  since  D5.0 -- D5.0A, Feb/82; D5.0B, Dec/82; or
     D5.0C, Mar/83).  Subcomponents with revision level "C"  are  new
     since  the  last redistribution, D5.0C (Mar/83).  Revision level
     "D" is used to flag preliminary versions that are available  for
     testing,  but  which  may still contain many "bugs" or which may
     change significantly.
0         The driver file editor program, *DEDIT (461/3), may be used
     to manipulate a driver file.  Indexing information  is  kept  in
1                                                                   3
-
     the driver file, which makes the line numbers in the driver file
     and  its associated comment file very important.  Care should be
     used when copying or changing the file.  Finally, only a D5.0 or
     later version of *DEDIT should be used to change the D5.1 driver
     file.
0         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.  This is also a  convenient  way  to  inform  other
     installations  of  who  is  currently  responsible  for  various
     components at your installation.
0         Some of the components in the driver file have the  letters
     "UNSP" in the field that indicates the person who is responsible
     for  the  component.   The  ID  UNSP exists on the University of
     Michigan  system  to  provide  a  common  location  from   which
     unsupported  programs  and  subroutines  can  be made available.
     Most UNSP software is not actively supported by  the  University
     of  Michigan  Computing  Center.   This  means that there are no
     guarantees about  its  reliability,  performance,  or  continued
     availability.   UNSP  software  has received a minimal amount of
     testing to insure that it operates  correctly  for  most  common
     cases.   A  complete  list  of  UNSP  programs  is  available in
     component 685/1.
0         A number of "dummy" driver file entries have been added for
     components from other MTS installations that are  not  installed
     as  part  of  the  production  system  at UM.  These entries are
     simply an aid in assigning component numbers.
0         As *FS generates the distribution tapes, it adds additional
     information to each line in the driver file, such as the name of
     the distribution tape on which  it  has  written  the  component
     (tapes  are  named  5.1Tn),  the file number on the distribution
     tape, a unique name for the component (known as  the  FS  name),
     information  about the file size or tape blocking information if
     the component was obtained from a regular (non-FS) tape, and the
     time and date when the file was saved.
0         Components may be obtained from the *FS tapes using the *FS
     RESTORE command, either by reference to the  FSname  or  to  the
     file  number.   In  distribution mode, if the RESTORE command is
     given with the parameters "(m) (n) filename", where filename  is
+                                                        ________
     the  name  of  a  driver file which was used to construct the FS
     tape, then that  RESTORE  command  and  all  subsequent  RESTORE
     commands which have "(m)" or "(m) (n)" as parameters will use as
     the  new  name  the  original  name  given in the driver file in
     columns 59-117.  For example, to restore a file with the UM name
     MCP:APPLE.DOS (on tape 5.1T2, file 898), run *FS in distribution
     mode from the ID MCP on the tape 5.1T2.  Assuming that you  have
     previously   restored   the   D5.1  driver  file  to  file  name
     DIST:DRIVER, the following command will cause  the  file  to  be
1                                                                   4
-
     restored  to  the  name  specified  in  the driver file location
     field: RESTORE (898) (898) DIST:DRIVER
0         Starting with the  D5.0  version,  *FS  generates  checksum
     information   as  it  saves  files  on  the  distribution  tape.
     Previous versions of *FS should accept this checksum information
     even though they don't normally generate it themselves.
0         Beginning with D5.1, *FS writes  tape  blocks  longer  than
     4096  characters.   However,  the  D5.1 *FS tapes were generated
     using an old version of *FS and so  do  not  have  long  blocks.
     Future  distributions  of  MTS  will be generated using the D5.1
     version of *FS and will have long blocks which can not  be  read
     by pre-D5.1 versions of *FS.
0         A  printed  copy  of the driver file listing is included in
     the distribution.  Additional copies  of  this  listing  may  be
     printed  using  the  LIST  command  in  *DEDIT.   The listing is
     ordered by component number and  includes  descriptive  comments
     about  each  component.   The  driver  file  and  its associated
     comment file are on the *FS tapes and on the  dump/restore  pack
     (in the files DIST:DRIVER and DIST:COMM).
0         A  printed  copy of the driver file index is also included.
     It provides an 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  index  is  component  461/18
     (DIST:INDEX6250 on the dump/restore pack).
0         The  following components are new since D5.0 (Sept.  1981),
     but were sent out on the indicated redistribution:
0              Components     Redist.   Date
+              __________     _______   ____
0              826 - 833      D5.0A     Feb/82
               834 - 844      D5.0B     Dec/82
               845 - 847      D5.0C     Mar/83
0    Components 848-867 are new since D5.0C.
0         The following components have become obsolete  since  D5.0:
     355, 390, 510, and 817.
1                                                                   5
-
                  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/3).   A
     printed  copy  of  the  listing is included in the distribution.
     For each component (or subcomponent),  two  or  three  lines  of
     output are printed, followed by any comments associated with the
     component.
-
     LINE 1
+    ____ _
0         Num - component number and subcomponent number (if any)
+         ___
          R - revision level (if any) of the component or
+         _
               subcomponent:
               A, C, or D for D5.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 - commands
               D - data
               L - listing
               M - messages
               O - object (OC=unlinkedited, OE=linkedited,
                    OL=library, OV=MVS load modules in VSS format)
               P - printed output (PF=FORMAT, PT=TEXT360,
                    PX=TEXTFORM)
               S - source code (SA=assembler, SB=ALGOLW, SF=FORTRAN
                    (FORTRAN 66), SG=GOM, SI=ICON, SM=assembler
                    macros, SP=PL/I, SQ=PLUS, SR=CLPARSER grammar,
                    SS=SNOBOL4, SW=PASCAL,SX=XPL, S3=PL360,
                    S4=RATFOR, S6=ALGOL68, S7=VS/FORTRAN (FORTRAN
                    77), S*=SNOSTORM)
               U - update deck (UC=*CDUPDATE, UE=$EDIT, UI=*IEBUPDAT,
                    UU=*UPDATE commands)
               W - writeup input (WF=FORMAT, WT=TEXT360, WX=TEXTFORM)
               X - Xerox 9700 (XF=form definition, XJ=job description
                    library, XT=font definition)
          G - "goodness" code (G=good, O=OK, S=shaky (has bugs),
+         _
               B=bad (needs rewrite))
          Seq ID - sequence id applied to component as it was saved
+         ___ __
               (if any)
          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), followed by an optional parameter "VLO",
               denoting a volume-label-only tape.  Then follow
               keywords for the label type, blocking format, and
1                                                                   6
-
               DSNAME (if any).
          File - the file number if the component was obtained from
+         ____
               tape (optional for labeled or *FS tapes)
-
0    LINE 2
+    ____ _
0         6250 Tape - name of 6250 bpi distribution tape on which the
+         ____ ____
               component was saved
          6250 File - *FS file number on the 6250 bpi 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 obtai
+         ____
               ed (PAGE for non-FS tapes and files, DISK for items
               obtained from older (before the page-formatted file
               system) *FS tapes)
          Inst - installation 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         1600 Tape - name of 1600 bpi distribution tape on which the
+         ____ ____
               component was saved
          1600 File - *FS file number on the 1600 bpi distribution
+         ____ ____
               tape
0         NOTE: Currently there are no MTS installations requiring
          1600 bpi tapes, so no 1600 bpi version of D5.1 was written
          when the original version was sent out.  A 1600 bpi version
          will be generated later if it becomes necessary.
0         Disk Name - name of the file (if any) on the dump/restore
+         ____ ____
               test pack where the component is located (the save
               control field controls whether it is also on the *FS
               tapes).  One of two modifiers may be added to this
               field: @E indicates that the file is to be empty when
               it is moved to the dump/restore pack; @UM indicates
               that the file is to go be included on the UM
               dump/restore test, but is not normally sent out on the
               standard distibution pack.
1                                                                   7
-
                  USE OF DASDI, DUMP/RESTORE and DISKCOPY
+                 ___ __ ______ ____________ ___ ________
0         Two different disks formats are currently used in MTS: VAMX
     and  SAM.   VAMX  format  is used by the MTS file system.  It is
     slightly different than the TSS VAM2 format that was used in the
     MTS file system for many years or the old VAMX format which  was
     used  by  several  MTS installations when they first began using
     3350 type disks.  SAM format is  used  by  HASP  for  its  spool
     pack(s).
0         Four programs are provided to initialize and restore disks.
     The  MTS program FILE:DASDI (598) may be used to initialize VAM2
     and VAMX format 2311, 2314,  3330-1,  3330-11,  and  3350  disks
     (although  the  program  has  never  been  tested with 2311s, or
     2314s).  The MTS program FILE:DISKCOPY  (724)  may  be  used  to
     dump,  restore or copy VAM2 and VAMX format 3330-1, 3330-11, and
     3350 disks.  FILE:DISKCOPY could be  used  with  2311  and  2314
     disks if the proper unit check routines were developed.  The IBM
     TSS  DASDI  and  DUMP/RESTORE  programs are stand-alone programs
     that may be used to initialize, dump, restore or copy  VAM2  and
     SAM  format  2311,  2314, 3330-1 and 3330-11 disks.  The IBM TSS
     DASDI and DUMP/RESTORE programs cannot be used with VAMX  format
     disks.
0         The  MTS  programs FILE:DASDI and FILE:DISKCOPY are located
     on the *FS tapes, the dump/restore tapes, and the utility  tape.
     These  programs  require  a  working version of MTS to run.  For
     existing MTS installations  this  should  be  no  problem.   New
     installations  must  use a special version of MTS that will work
     without  a  disk  subsystem  to  run  these  programs  (see  the
     instructions for new installations for details).
0         The MTS program FILE:DASDI will initialize a pack in either
     VAM2  or  VAMX  format.   Directions  for running FILE:DASDI are
     given in the MTS Operator's Manual (592) and in comments at  the
     beginning of the source program.
0         MTS  file  system  volumes  are  normally  labeled  MTS001,
     MTS002, etc.  and must be VAMX (VX) format.  The  public  volume
     number  for  the first pack in the system must be 1 and go up by
     one for each additional pack.  No two packs at  an  installation
     should  have  the  same  volume label and the same public volume
+                                          ___
     number.  If you are running DASDI or DISKCOPY on your production
     system, the SLOW option may be used to  keep  the  program  from
     monopolizing the disk system.
1                                                                   8
-
          The  following  example  initializes  the pack on D001 as a
     VAMX pack with volume label MTS501 and public volume 1.
0        $run file:dasdi
         EXECUTION BEGINS
         MTS DASDI PROGRAM (version).  ENTER INPUT
         d001 mts501 vx 1 slow ipl
         D001 CURRENTLY LABELED AS "NEW001".  PLEASE CONFIRM.
         ok
         PAT TO BE WRITTEN ON PAGES X'009178' THRU X'00918A'.
         NEXT?
         $endfile
         EXECUTION TERMINATED
-         The following example initializes the pack  on  D002  as  a
     VAMX pack with volume label PAG001 for use as a paging volume.
0        $run file:dasdi
         EXECUTION BEGINS
         MTS DASDI PROGRAM (version).  ENTER INPUT
         d002 pag001 vx paging slow
         D002 CURRENTLY LABELED AS "NEW002".  PLEASE CONFIRM.
         ok
         PAT TO BE WRITTEN ON PAGES X'009178' THRU X'00918A'.
         NEXT?
         $endfile
         EXECUTION TERMINATED
-         The  MTS program FILE:DISKCOPY may be used to copy VAM2 and
     VAMX disk data from pack to pack as well as to and  from  tapes.
     The  program will not convert VAM2 format data to VAMX format or
     vice-versa.  It will copy from one disk type to another (3330 to
     3350 or 3330-11 to 3330-1 for  example)  as  long  as  the  "to"
     volume  is  large  enough  to  hold all of the data and there is
     sufficient space in the PAT for any relocation  entries  needed.
     VAM2  format  tapes  produced  by  FILE:DISKCOPY can be restored
     using the IBM TSS DUMP/RESTORE program  and  FILE:DISKCOPY  will
     restore   from  VAM2  format  tapes  produced  by  the  IBM  TSS
     DUMP/RESTORE program.
1                                                                   9
-
          Instructions for running  FILE:DISKCOPY  may  be  found  as
     comments  at the beginning of the source.  The following example
     shows a tape-to-disk restore:
0        $run file:diskcopy
         EXECUTION BEGINS
         Enter "FROM" device type (DISK/TAPE):
         tape
         Enter tape device or pseudo-device names(s):
         >T908
         Enter "TO" device type (DISK/TAPE):
         disk
         Enter device name and volume label (Dxxx MTSyyy):
         d008 mts501
         Enter options (SLOW, SWAP, IPL):
         slow swap ipl
         Volume copied: 29453 data pages copies, 2 relocations
         Enter "FROM" device type (DISK/TAPE):
         $endfile
         EXECUTION TERMINATED
0    The SLOW option keeps the program  from  monopolizing  the  disk
     system.   The  SWAP  option  causes the volume label on the "TO"
     device to be replaced with the  volume  label  from  the  "FROM"
     device  (in  a  disk-to-disk copy both labels would be changed).
     The IPL option causes any IPL records to be copied.  IPL records
     are always included on a disk-to-tape copy, but are not normally
     included on a tape-to-disk  or  disk-to-disk  copy.   These  IPL
     records should not be confused with the IPLAREA data used by the
     IPLREADER,  both  types  of  IPL data are needed.  More than one
     tape device may be specified at a time, but this is not required
     even when the dump/restore data spans more than one tape reel.
0         The IBM TSS (Release 3.0)  DASDI,  DUMP/RESTORE,  and  VAM2
     UTILITIES  programs  are  at  the  beginning of the dump/restore
     tapes following the IPLREADER and friends as well as on the  *FS
     tapes (730/1).  Starting with D4.3 of MTS the dump/restore tapes
     are in MTS VAMX format which is not supported by the TSS utility
     programs, but the TSS utilities must still be used to format the
     HASP  spool  pack(s)  when  2311 or 2314 type disks are used.  A
     printed copy of the writeup for TSS DASDI  is  included  in  the
     distribution sent to new installations (see comp.  461/25).
0         The  TSS  DASDI  program  (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 a dump/restore tape once will load  the  IPLREADER.
     IPLing again will load TSS DASDI.
1                                                                  10
-
          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 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                                                                  11
-
                            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 (component 592).
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
          (component 1021/12) 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.  Component
          1019/16 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                                                                  12
-
          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                                                                  13
-
     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,  generally using *OBJUTIL's PATCH command.  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                                                                  14
-
1                                                                  15
-
                 PRINTED DOCUMENTATION IN THE DISTRIBUTION
+                _______ _____________ __ ___ ____________
-         The  following  lists  all  of the paper-copy documentation
     included in D5.1.  Of course, all of the documents listed  below
     are  available  on the *FS tapes except for those marked with 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 MTS 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         Printed  copies  of  many items have been omitted from this
     distribution for existing installations  when  machine  readable
     versions are available on the *FS tapes or when the material has
     not  changed  from that included in the previous distribution of
     MTS.  If your installation needs a printed copy of  any  of  the
     omitted items, send a request to:
0        Elizabeth A. Sweet
         The University of Michigan
         Computing Center
         1075 Beal Avenue
         Ann Arbor, MI 48109
         USA
-    Printed copies of the following items are included with D5.1 for
     both new and existing installations.
+         ___     ________
0              461/15    Driver  file  listing  (*DEDIT  LIST command
                         output)
               461/18    Driver file  index  (6250  bpi);  a  listing
                         sorted by component names which serves as an
                         index for 461/15.
               461/19    General Notes, what you are reading now
               461/20    Installation     instructions     for    New
                         Installations.
               461/21    Installation   instructions   for   Existing
                         Installations.
               461/22    List of current CCMemos.
         *     461/24    UM Machine Configuration Chart.
         *     711/12    Computing  Center Newsletter (v11n15 through
                         v13n13).
         *     711/13    Permission  to  reproduce  Computing  Center
                         publications.
0    Printed copies of the following items are included with D5.1 for
     new   installations   only,   but   are  available  to  existing
+    ___
     installations upon request.
0              004/4     TABLES writeup.
               004/8     DECKGEN instructions.
               387/23    HASP Operator's Guide.
               387/26    HASP Notes.
1                                                                  16
-
         *     387/41    HASP Remote 360/20 Operator's Guide.
         *     387/42    HASP Remote 360/non-20 Operator's Guide.
         *     387/43    HASP Remote 1130/1800 Operator's Guide.
         *     387/44    HASP Remote System/3 Operator's Guide.
         *     387/45    HASP  2780  Remote  Workstation   Operator's
                         Guide.
         *     461/25    TSS DASDI instructions.
               468/07    Description of D5.1 System Object Deck.
               592       MTS Operator's Manual.
         *     673/23    Documentation   to  supplement  the  machine
                         readable documentation for the FLECS FORTRAN
                         preprocessor.
               711/2     List of Computing  Center  Publications  and
                         the publications themselves.
         *     711/14    MTS Reference Summary.
               1021/12   Documentation for the IPLREADER and friends.
               1019/16   Documentation    for   the   RAMROD   System
                         Maintenance Utility.
0    The following items are not automatically included with D5.1  of
     MTS  for  either  existing  or new installations, but copies are
     available upon request.
0        *     583/06    Documentation for the KWIC (583) program.
         *     584/04    Documentation for the QUIC (584) program.
         *     646/02    Audio tapes of 33 system lectures  given  by
                         the UM staff during 1973.
1                                                                  17
-
            COMPONENTS WHICH DEPEND ON THE SYSTEM CONFIGURATION
+           __________ _____ ______ __ ___ ______ _____________
0     1.  The  TABLES (004) assembly depends almost completely on the
          hardware configuration being used.  It is  described  in  a
          separate write-up (004/4).
0     2.  There  are two disk file backup processes available to save
          files on tape:  the weekly FILE SAVE and the  daily  online
          FILE  SAVE.   There  are  command files associated with the
          weekly file save which will have  to  be  changed  at  each
          installation  so  that  they  indicate correctly which disk
          volumes are to be saved.  See the driver file comments  for
          these components (067).
0     3.  DINIT (097/10) - the program that initializes a 2301 drum -
          assumes  two drums called DRM1 and DRM2.  If you have fewer
          it will complain but work anyway, but if you have more  you
          must  change it.  The distributed system assumes that 2305s
          (rather  than  2301s)  are  used  for  paging.   The   file
          INIT:INITCMD   (097/2)  should  be  changed  to  run  DINIT
          (instead of FMT2305) if this is not the case (see also  the
          words about the PDP below).
0     4.  INIT:INITCMD  (097/2) runs FMT2305 to initialize four 2305s
          (or 4305s).  If you have fewer it will  complain  but  work
          anyway, but if you have more you must change it.
0     5.  The  PDP  (comp.   044)  assumes no more than 2 3805s and 2
          3330  disks.   It  will  work  with  fewer  (even  zero  if
          necessary),  but  must  be  reassembled  for more or if you
          intend to use 2305s.  The PDP will automatically  grab  any
          3805  that is online and use it when it is started so if it
          is not to be used, OFFLINE it before  the  PDP  is  started
          (before  giving  the  reason  for reloading).  The PDP will
          also automatically use any 3330 disks that are labeled with
          the prefix "PAG" (e.g.  PAG001) and  that  are  labeled  as
          PAGING  packs.   Again, OFFLINE these if they are not to be
          used by the PDP.  The PDP has also been assembled to assume
          2 2305s but they will not work properly since the number of
          slots per device is set to 8.  Sites using 2305s will  need
          to  reassemble  the  PDP  with  NOSLOTS  set to 3 (the only
          number of slots for which the 2305s  will  work  properly).
          For this reason, all 2305s should be offline before the PDP
          is  started.  Note: the PDP has an assembly parameter which
          determines whether 2301s or  2305s  are  to  be  used;  the
          distributed  version  assumes 2305s.  It can be reassembled
          for 2301s.  The PDP can also be reassembled with  the  3805
          and/or disk support removed, making it a bit smaller.
0     6.  MOUNT  (101)  includes  support  for  mounting  paper  tape
          readers and punches, audio response units, floppy disks and
          connections on the Merit Computer Network  in  addition  to
          magnetic  tapes.   Assembly  parameters  allow  support for
          these other (non mag tape) devices to be deleted.   Support
          for  the  Adage  Graphics  terminal may be included, but UM
          doesn't have one so this code has never been fully tested.
1                                                                  18
-
      7.  In MTS (042) the subroutine NEXTJOB will do a  binary  read
          from  a 2540 or 2501 when it is looking for the next job in
          a batch stream.  Since a 2540 without binary feature ("card
          image" feature) will accept the command and treat it as  an
          EBCDIC  read,  NEXTJOB will never find a job.  This affects
          only non-HASP batch (rarely, if ever, used).
0     8.  HASP (387) contains several assembly parameters that depend
          on the machine configuration.  A  separate  description  of
          these  is  included in component 387/26.  Both HASP and the
          HASPLING (388) have  assembly  parameters  related  to  RJE
          support.   The HASP master source and distributed object is
          for the UM RJE configuration.
0     9.  TAPERTN (135) - the magnetic tape routines  -  has  several
          assembly  parameters  (see  comments  in  the  source).  In
          addition, the local system name used in the data set labels
          generated by MTS is obtained from the CIINAME field in  the
          CNFGINFO table described above.
0    10.  TSFO  (038)  has  a  built-in  table of the device names of
          hardwired 2703/1270 lines.  All other lines are assumed  to
          be   dial-up.   This  table  should  be  updated  and  TSFO
          reassembled as appropriate.
0    11.  The file COPY:GLOBALSETS (1026/2) has  global  set  symbols
          for various hardware and software features.  In most cases,
          this   file  is  copied  by  system  components  which  are
          dependent on these features.
0    12.  The 3270 DSR (629) has several global set symbols that  may
          be used to tailor the DSR for use at a given installation.
0    13.  The  GRAB3270 table (629) has entries for a fixed number of
          displays.  It will work for fewer, but must be  reassembled
          if more displays are allowed to GRAB and FLIP.
1                                                                  19
-
                       LISTINGS IN THE DISTRIBUTION
+                      ________ __ ___ ____________
-         Listings  have  been  included  on  the  *FS  tapes for the
     following components of the system.
-    Comp._Name   5.0_Comp.   5.0_Tape,    5.1_Comp.   5.1_Tape,
+    _____ ____   ___ _____   ___ _____    ___ _____   ___ _____
                  number      file_#       number      file_#
+                 ______      ____ _       ______      ____ _
0    MTS          0042/5      5.0T4 #277   0042/4      5.1T1 #22
     SUPERVISOR   0045/4      5.0T4 #283   0045/4      5.1T1 #30
     CONFIG       0046/4      5.0T4 #290   0046/4      5.1T1 #38
     GUINFO       0198/4      5.0T4 #296   0198/4      5.1T1 #208
     LLXU         0354/4      5.0T4 #303   0354/4      5.1T1 #265
     HASP         0387/10     5.0T1 #136   0387/10     5.1T1 #276
     SSCN SUBR    0400/7      5.0T4 #311   0400/7      5.1T1 #297
     PLIMIT       0464/4      5.0T4 #327   0464/4      5.1T1 #324
     DYSSUB       0513/4      5.0T4 #331   0513/4      5.1T1 #517
     CMDSTAT      0531/4      5.0T4 #334   0531/4      5.1T1 #550
     TIMNTRP      0539/5      5.0T4 #338   0529/5      5.1T1 #568
     RSF          0578/4      5.0T4 #376   0578/4      5.1T1 #636
     FSUB         0635/4      5.0T4 #405   0635/4      5.1T1 #759
     CMDS         0636/4      5.0T4 #408   0636/3      5.1T1 #762
     DSRS         0637/5      5.0T4 #412   0637/4      5.1T1 #765
     USUB         0638/4      5.0T4 #415   0638/4      5.1T1 #768
     DSRI         0639/4      5.0T4 #418   0639/4      5.1T1 #771
     TAXIR        0668/3      5.0T2 #1132  0668/3      5.1T1 #962
     DAVE/M       0765/15     5.0T3 #586               not on 5.1
     TBLS         new for 5.1              0829/4      5.1T2 #694
     ICON         new for 5.1              0831/8      5.1T2 #704
     PROFORT      new for 5.1              0847/2      5.1T2 #882
     MCP PDP-11   new for 5.1              0848/154    5.1T2 #1046
     PLUS/470     1042/5      5.0T3 #1209              not on 5.1
     PLUS/470     1042/53     5.0T3 #1257              not on 5.1
     GATE         4000/4      5.0T4 #644   4000/4      5.1T3 #317
1                                                                  20
-
1                                                                  21
-
        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;  an  M  indicates  that  the  person  should be
     contacted  at  the  Merit  Computer  Network,  (313)   764-9423;
     otherwise  call  (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         BRILL       Brill, Robert C.
       *  BURLING     Burling, Steven R.
          CASHMAN     Cashman, Brian
          DONNELLY    Donnelly, Stephen M.
       *  DWB         Boettner, Donald W.
       *  D BODWIN    Bodwin, Diane L.
          EADIE       Eadie, Gavin R.
       *  EMERY       Emery, Allan R.
       *  ENGLE       Engle, Charles F.
       *  FLANIGAN    Flanigan, Larry K.
          FLOWER      Flower, David S.
          FRONCZAK    Fronczak, Edward J.
       *  GLUSKI      Gluski, Kari
          HANSEN      Hansen, James H.
       *  HARDING     Harding, Leonard J.
       *  HARTMANN    Hartmann, Forrest
       *  HELFFRICH   Helffrich, George R.
          HERSEY      Hersey, Mark
       M  HUSAK       Husak, Robert L.  (MERIT)
          J BODWIN    Bodwin, James M.
       M  KNOPPER     Knopper, Mark  (MERIT)
          KRAUSE      Krause, Robert
       *  LIFT        Lift, Gail H.
          MANUAL      (see SALISBURY)
          MENDAL      Mendal, Geoffrey
       *  MTA         Alexander, Michael T.
          MTS         (see BURLING, STERKEN, OGDEN, MTA)
       *  OGDEN       Ogden, Jeffrey C.
       *  PICKELMAN   Pickelmann, Paul
       *  PIRKOLA     Pirkola, Gary C.
          RAMANUJAN   Ramanujan, Chitraleka
       *  RIOLO       Riolo, Rick
          ROTHWELL    Rothwell, Steven
       *  SALISBURY   Salisbury, Richard A.
       *  SHERRY      Sherry, Patrick M.
       M  STARK       Stark, John  (MERIT)
       *  STERKEN     Sterken, James J.
          SWARTZ      Swartz, Fred G.
       *  SWEET       Sweet, Elizabeth A.
1                                                                  22
-
          TIFFANY     Tiffany, L. Bernard
          TOKARSKI    Tokarski, Dennis
          UNSP        (see PICKELMANN)
       *  VALERIO     Valerio, Thomas
          WHIPPLE     Whipple, David
       *  WOLFSON     Wolfson, Genie R.
       *  WSG         Gerstenberger, W. Scott
          YOUNG       Young, Howard B.
-
0    Correspondence related to the administration of the UM Computing
     Center should be sent to the director:
0              Dr. Aaron Finerman, Director
               The University of Michigan
               Computing Center
               1075 Beal Avenue
               Ann Arbor, MI 48109
               USA
0              Telephone (313) 764-9572
1                                                                  23
-
                   DISTRIBUTION 5.1 INITIAL MAILING LIST
+                  ____________ _ _ _______ _______ ____
0         The following is a list of  persons  to  whom  the  initial
     shipments of MTS Distribution 5.1 have been sent.
-
     AMD       Amdahl Corporation                  6250 bpi
               ATTN:  Bill Ehrman
               1250 East Arques Avenue
               Sunnyvale, CA 94086
0    RIO       LCC - CNPQ                          6250 bpi
               Attn: Jayme S. P. Goldstein
               R.  Lauro Muller, 455
               22290 - Botafoga - Rio de Janeiro
               R.J.  - BRAZIL
0    RPI       Office of Computer Services         6250 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    UBC       Computing Centre                    6250 bpi
               ATTN:  Ron Hall
               6356 Agricultural Road
               University of British Columbia
               Vancouver, B. C.  V6T 1W5
               CANADA
0    UD        Computer Unit                       6250 bpi
               Science Laboratories
               ATTN: Ian Bell
               South Road
               University of Durham
               Durham   DH1 3LE
               ENGLAND
0    UNE       Computing Laboratory                6250 bpi
               ATTN:  Program Librarian
               The University
               Newcastle upon Tyne   NE1 7RU
               ENGLAND
0    UQV       Computing Services                  6250 bpi
               ATTN:  Garry Jackson
               The University of Alberta
               Edmonton, Alberta T6G 2H1
               CANADA
1                                                                  24
-
     UZ        University Computing Centre - SRCE  6250 bpi
               ATTN:  Miroslav Gacesa
               Engelsova bb
               41000 Zagreb
               YUGOSLAVIA
0    WSU       Computing Services Center           6250 bpi
               ATTN:  Tony Falzon
               Wayne State University
               5925 Woodward Ave., Room 284
               Detroit, MI 48202
