1                                                                             1
-
                             M T S   D I S T R I B U T I O N   4.0
-            |                  (Revised for Distribution 4.3)
-            |                             May 1980
-                                        General Notes
-
                    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.
-
0                   MTS, the Michigan Terminal System, is distributed using two
+                            _        _        _
             | types of tapes:  (1) 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.  The
             | dump/restore tapes sent as part of D4.0, D4.1 and D4.2 were  IBM
             | TSS  VAM2 format, while the D4.3 dump/restore tapes are MTS VAMX
             | format.
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 10068 or 10069); both are available on the *FS tapes.
0                   Distribution  4.0   (September   1977)   was   a   complete
               distribution  of  the  system.  Supplemental distributions D4.1,
             | D4.2, and D4.3 were completed in May 1978, March 1979,  and  May
             | 1980, respectively.  They differ from D4.0 in that the *FS tapes
               contain  only  those  components  which  have  been added to the
               system  or  changed  since  the  previous  distribution.   Other
               components  are not included since they may be obtained from the
               D4.0 *FS tapes.  For installations  which  have  not  previously
               received  a  distribution  of MTS, the *FS tapes for D4.0, D4.1,
             | and D4.2 are included  with  D4.3.   However,  the  dump/restore
             | tapes  for  D4.0,  and  D4.1  are  not  included  since the D4.3
             | dump/restore tapes provide a complete, current system.  The D4.2
             | dump/restore tapes are included  so  that  the  TSS  stand-alone
             | utilities  may  be  used to restore the D4.2 system which may in
             | turn be used to restore the  D4.3  system.   This  is  necessary
             | because  there  is currently no stand-alone program to restore a
1                                                                             2
-
             | VAMX pack.
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.   A  component  will  almost always have the same
             | number, but subcomponent numbers  may  be  changed.   Thus,  for
             | example,  something  may  have been distributed on D4.2 with the
             | number 104/15, while on D4.3 it may be 104/16 (this could happen
             | if a subcomponent containing an  update  were  inserted  between
             | source and object).  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  (there is a 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
                   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)
             |     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, a 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  (revision  levels  "A"
             | and  "C"  have  been  used to mark the subset of the driver file
             | which is included in D4.3).
0            |      Revision level "A" denotes subcomponents  which  have  been
             | changed  in  the  UM  production  system since D4.2 (March 1979)
             | (these may, however, have  been  included  in  a  redistribution
             | since   D4.2).    Subcomponents  with  revision  level  "C"  are
             | completely new for D4.3, i.e., they  have  never  been  seen  by
             | other  installations  before,  either  on  a  distribution  or a
             | redistribution.
1                                                                             3
-
                    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.  This is  also  a  convenient  way  to
             | inform  other  installations of who is currently responsible for
             | various components at your installation.
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  D4Tn,  D4.1Tn,  D4.2Tn, and 4.3Tn), 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.   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/5 for the 6250 bpi tapes, and 461/6 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 LIST  command  in  *DEDIT.
               The   listing  is  ordered  by  component  number  and  includes
               descriptive comments about each component.  The  revision  level
             | "A" or "C" is printed immediately after the component number for
             | those  components  which have been included in D4.3.  For these,
             | the tape name will be shown as 4.3Tn, whereas  other  components
             | which  have  not  changed  since D4.0, D4.1, or D4.2 will have a
             | tape name of the form D4Tn,  D4.1Tn,  or  D4.2Tn.   Both  driver
               files  are on the *FS tapes and on the dump/restore pack (in the
               files  DIST:DRIVER6250  and  DIST:DRIVER1600)  along  with   the
               comment  file  (DIST: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 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
               6250  index  is  component   461/13   (DIST:INDEX6250   on   the
               dump/restore   pack);   the   1600  index  is  component  461/14
               (DIST:INDEX1600 on the pack).
1                                                                             4
-
                    MTS Distribution 4.1 was the last distributed system  which
               included  support  for  the  IBM  System/360  Model  67;  it was
               designed in such a way that it could be used on either a 360/67,
               System 370, or Amdahl 470.   MTS  distributions  beginning  with
               D4.2 support only the IBM 370 and Amdahl 470 systems.
0            |      Support  for  IBM  2250  displays was dropped starting with
             | D4.2 of MTS.
0            |      Components 764 thru 791  are  new  since  D4.2;  components
             | 779-791 are new since redistribution D4.2C.
0            |      The following components were made obsolete for D4.3:
0            |           XALGOLW (528/57) and ALGOLWXLIB replaced by new ALGOLW
             |           (528)
             |           STDTV (535/3) moved into CMDS (636)
             |           COPY:STATDSECT (620/1) moved to COPY:MTS.MACROS (344)
             |           FILE:DS.O (644) replaced by SYS:DSKMAN (073)
             |           RAMP (661)
             |           PL1LINK (670)
-            |      The   following  components  were  assigned  new  component
             | numbers for D4.3:
0            |      UC3330: changed from (603) to (787)
             |      Online File Save: changed from (716) to (067)
             |      File System - DASDUC: changed from (482/1) to (787/7)
-                   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.
               UNSP software is not actively supported by the Computing  Center
               staff.   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/3.
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.
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/1).   A
               printed  copy  of the appropriate listing (for 6250 or 1600 bpi)
               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.
-
0              LINE 1
+              ____ _
0                   Num - component number and subcomponent number (if any)
+                   ___
                    R - revision level (if any) of the component or
+                   _
                         subcomponent:
             |           A or C - D4.3
                    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, S+=PLUS, S*=SNOSTORM)
                         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=shaky (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                                                                             6
-
               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 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                                                                             7
-
             |              USE OF DASDI, DUMP/RESTORE and DISKCOPY
+                           ___ __ ______ ____________ ___ ________
0            |      Three different disks formats are currently  used  in  MTS:
             | new  VAMX, VAM2 and SAM.  New VAMX or simply VAMX format is used
             | by the MTS file system.  It is slightly different than  the  old
             | VAMX  format  which  was used by several installations when they
             | began using 3350 type disks.  Old VAMX format allowed both  VAMX
             | and  VAM2  disk  addresses  to  coexist in the same file system.
             | VAM2 format is  currently  only  required  by  the  Paging  Drum
             | Processor  (PDP), but was the format used by the MTS file system
             | before the switch to VAMX format.  As used by the PDP, the  only
             | difference  between  VAM2  and  VAMX  is  the volume label.  SAM
             | format is used by HASP for its spool pack(s).
0            |      Four programs are provided to initialize and restore disks.
             | 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
             | TSS  DASDI  and  DUMP/RESTORE  programs cannot use 3350 disks or
             | VAMX dump/restore tapes.  The MTS programs FILE:DASDI (598)  and
             | FILE:DISKCOPY (724) require a working MTS system in which to run
             | (they   aren't   stand  alone  programs)  and  may  be  used  to
             | initialize, dump, restore or copy VAM2  and  VAMX  format  2311,
             | 2314,  3330-1,  3330-11,  and  3350 disks (although the programs
             | have never been tested with 2311s, 2314s or real 3330-1s).
0            |      The MTS programs FILE:DASDI and FILE:DISKCOPY  are  located
             | on  the  the  D4.3  *FS tapes.  These programs must be run in an
             | existing MTS system to restore the VAMX dump/restore tapes.  For
             | old MTS  installations  this  should  be  no  problem,  but  new
             | installations will have to restore the D4.2 version of MTS using
             | the  IBM  TSS  utilities and then use that system to restore the
             | D4.3 system by running FILE:DASDI  and  FILE:DISKCOPY  (see  the
             | instructions  for  new  installations  for  details).   The next
             | distribution of MTS will include a version of MTS  that  can  be
             | IPLed directly from tape so that the use of the IBM TSS programs
             | will no longer be required.
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)  item  10075  and  in
             | comments at the beginning of the source program.
0            |      MTS  file  system  volumes  are  normally  labeled  MTS001,
             | MTS002, etc.  D4.0, D4.1 and D4.2  volumes  must  be  VAM2  (V2)
             | format,  while  D4.3 packs 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 the DASDI program 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 MTS431 and public volume 1.
0            |     $RUN FILE:DASDI
             |     EXECUTION BEGINS
             |     MTS DASDI PROGRAM (version).  ENTER INPUT
             |     D001 MTS431 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
             | VAM2 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 V2 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.  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 MTS431
             |     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 2.0)  DASDI,  DUMP/RESTORE,  and  VAM2
             | UTILITIES  programs  are  at  the  beginning of the dump/restore
             | tapes that were included with D4.0,  D4.1  and  D4.2.   Starting
             | with D4.3 the dump/restore tapes are in MTS VAMX format which do
             | not  include  the  TSS  utility programs.  Printed copies of the
             | writeups for TSS DASDI and TSS DUMP/RESTORE are included in  the
             | distribution  as  item  10010, previously distributed with D4.0,
             | and therefore not included for old installations.
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 TSS dump/restore tape once will load TSS DASDI.
0            |      MTS  packs  should  be VOLTYPE=PUBLIC and the PAT should be
+                                                                     ______ __
             | placed on a cylinder boundary  (on  3330  type  disks  the  PATD
+              ______ __ _ ________ ________
             | STRTADR  parameter  should  be  evenly divisible by 57) near the
             | middle of the pack.
1                                                                            10
-
                    The following TSS DASDI control cards are for a 3330-1 with
               volume  label  MTS421.   To  DASDI  a  3330-11,  use  TODEV=333B
               (instead of 3330) and STRTADR=23199 (instead of 11685).
0                  JOB     INITIALIZE 3330-1 AS MTS421
                   MSG     TODEV=1052,TOADDR=53F
                   DADEF   TODEV=3330,TOADDR=440,FORMTYPE=VAM2,               X
                           VOLID=SCRATCH,VOLTYPE=PUBLIC,PUBVOLNO=1
                   VLD     NEWVOLID=MTS421
                   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.
             | The Paging Drum Processor (PDP) won't accept a pack with a  VAMX
             | label.
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 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
-                   To load TSS DUMP/RESTORE, IPL from a TSS dump/restore  tape
               and,  when  the tape stops, IPL again.  The following are sample
               control cards for restoring a TSS dump/restore tape to a  3330-1
               which has been initialized with the label MTS421.  To restore to
               a 3330-11, use TODEV=333B (instead of 3330).
0                  JOB     RESTORE MTS421 FROM TAPE
                   MSG     TODEV=1052,TOADDR=53F
                   RESTORE FROMDEV=2400,FROMADDR=681,TODEV=3330,              X
                           TOADDR=440,FORMTYPE=VAM2,VOLID=MTS421,             X
                           NEWVOLID=MTS421
                   END
0                   After  restoring  a  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 10068) and another for installations which have previously
               used MTS (item 10069).
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.
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
                    10072) 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,
                    which was sent with D4.1, 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.  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
-
                           PRINTED DOCUMENTATION IN THE DISTRIBUTION
+                          _______ _____________ __ ___ ____________
-                   The following lists all  of  the  paper-copy  documentation
             | included  in  D4.3.  For installations which previously received
             | D4.0, D4.1, and D4.2 only those  printed  documents  which  have
             | changed  since  then  (items  10065 and above) have been shipped
             | with D4.3.  Items 10000 to 10029  were  sent  with  D4.0,  items
             | 10030  to  10046  with D4.1, items 10047 to 10064 with D4.2.  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                   Since some paper-copy items are not distribution components
               (do not appear on the *FS tapes) and hence don't have  component
               numbers, hard-copy "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  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 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                  Elizabeth A. Sweet
                   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            |           10065.    General Notes, what  you  are  reading  now.
                                   (461/10)
             |           10066A and 10066B.   Driver file listing (LIST command
                                   output from *DEDIT).
             |           10067A and 10067B.   Driver  file  index;  a   listing
                                   sorted by component names which serves as an
1                                                                            15
-
             |                     index for 10066.  (461/13 and 461/14)
             |           10068.    Installation     instructions     for    New
                                   Installations.  (461/8)
             |           10069.    Installation    instructions     for     Old
                                   Installations.  (461/9)
             |           10070.    Description   of  D4.3  System  Object  Deck
             |                     (468/7)
             |           10071.    TABLES writeup (004/3)
             |           10072.    Documentation for the IPLREADER and friends.
             |                     (1021/12)
                         10038.    Documentation   for   the   RAMROD    System
                                   Maintenance Utility.  (1019/9)
             |           10073.    DECKGEN instructions (004/7)
                   *     10010.    TSS DASDI and DUMP/RESTORE instructions.
             |     *     10074.    UM Machine Configuration Chart.
             |     *     10081A and 10081B.  List of D4.3 tapes.
-              General
+              _______
0                        10012.    Message Manual (555/5)
-              Operations
+              __________
0            |           10075.    MTS Operator's Manual (592)
             |           10076.    HASP Operator's Guide (387/22)
                   *     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            |           10077.    HASP Notes.  (387/25)
                   *     10021.    SDS Storage Allocation.
-              How-To-Use Information
+              __________ ___________
0              For systems or administrative users:
                   *     10023.    Modifying *LIBRARY.
                   *     10024.    Specifying keywords for EREP/370 (IFCEREP0)
0              For general user:
             |           10078A and 10078B.  List of current  CCMemos  (461/15)
             |                     and the CCMemos themselves.
                   *     10026.    Computing  Center  Newsletter  (v5n6 through
                                   v7n14)
                   *     10045.    Computing Center Newsletter  (v7n15  through
                                   v8n9)
                   *     10061.    Computing  Center  Newsletter (v8n10 through
                                   v9n7)
1                                                                            16
-
             |     *     10079.    Computing Center  Newsletter  (v9n8  through
             |                     v10n7)
             |           10080.    List   of   Computing   Center  Publications
                                   (461/22)
                   *     10028.    MTS Reference Summary
-              MTS Documentation
+              ___ _____________
0                  *     10063.    Permission  to  reproduce  Computing  Center
                                   publications
1                                                                            17
-
                                 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/5     MTS
                   0045/4     SUPERVISOR
                   0046/4     CONFIG
                   0198/4     GUINFO/CUINFO
                   0354/4     LLXU
                   0387/10    HASP
                   0400/6     SSCN SUBR
                   0464/4     PLIMIT
                   0513/4     DYSSUB
                   0531/4     CMDSTAT
                   0539/4     TIMNTRP
                   0578/4     RSF
                   0635/4     FSUB
                   0636/4     CMDS
                   0637/4     DSRS
                   0638/4     USUB
                   0639/4     DSRI
                   4000/4     GATE
1                                                                            18
-
                  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            |      BLOCK       Block, Frederick
                    BODWIN      Bodwin, James M.
                    BRILL       Brill, Robert C.
             |      CASHMAN     Cashman, Brian
                    DONNELLY    Donnelly, Stephen M.
                 *  DWB         Boettner, Donald W.
             |      EADIE       Eadie, Gavin R.
                 *  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.
             |      GREENING    Greening, Daniel
                    H YOUNG     Young, Howard B.
                    HANSEN      Hansen, James H.
                 *  HARDING     Harding, Leonard J.
                    HELFFRICH   Helffrich, George R.
                 *  LIFT        Lift, Gail H.
                    LUBBERS     Lubbers, Clark E.
                    MANUAL      (see SALISBURY)
             |      MERIT       (see EADIE)
                 *  MTA         Alexander, Michael T.
                    MTS         (see HELFFRICH)
                    OGDEN       Ogden, Jeffrey C.
                    PICKELMAN   Pickelmann, Paul
                 *  PIRKOLA     Pirkola, Gary C.
             |   *  P.O.        (see Salisbury) |2
             |   *  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 PICKELMANN)
                    VALERIO     Valerio, Thomas
                    WELTER      Welter, Mark
             |   *  WSG         Gerstenberger, W. Scott
1                                                                            19
-
                    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                                                                            20
-
             |               DISTRIBUTION 4.3 INITIAL MAILING LIST
+                            ____________ _ _ _______ _______ ____
0                   The following is a list of  persons  to  whom  the  initial
             | shipments of MTS Distribution 4.3 have been sent.
-
               UBC       Computing Centre                  6250 bpi
             |           ATTN:  Ron Hall
                         University of British Columbia
                         6356 Agricultural Road
                         University Campus
                         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:  Daryl Webster
                         The University of Alberta
                         Edmonton, Alberta T6G 2H1
                         CANADA
0              WSU       Computing Services Center         6250 bpi
                         ATTN:  Tony Falzon
                         Wayne State University
             |           5925 Woodward Ave., Room 284
                         Detroit, MI 48202
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              AMD       Amdahl Corporation                6250 bpi
                         ATTN:  Bill Ehrman
                         1250 East Arques Avenue
                         Sunnyvale, CA 94086
0              EMB       Programa Flora                    1600 bpi
             |           Attn: Stan Engilley
                         CNPq - S.I.P.
                         W3 NORTE QUADRA 507 BLOCO B
                         70.000 Brasilia D. F.
                         BRAZIL
1                                                                            21
-
             | RIO       CBPF/CNPq                         1600 bpi
             |           Attn: Julio L.  Botelho
             |           Av.  Wenceslau Bras 71
             |           CEP 22.290 Rio de Janeiro - RJ
             |           BRAZIL
