1                                                                   1
-
              INSTALLATION INSTRUCTIONS FOR NEW INSTALLATIONS
+             ____________ ____________ ___ ___ _____________
0                                May 1980
-    The first five steps in this procedure relate to bringing up the
     distribution 4.2 (D4.2) version of MTS.  This is necessary  only
     because an MTS environment must be available in which to run the
     DASDI  and  DISKCOPY  programs used in restoring the D4.3 system
     from tape.  After the D4.3 system has been  restored,  the  D4.2
     system generated in these first five steps is no longer needed.
-    1.   DASDI a VAM2 disk pack and restore the system from the D4.2
          dump/restore  tape(s)  provided using the IBM TSS DASDI and
          DUMP/RESTORE programs.  The D4.3 General Notes (item 10065)
          contain instructions on the use of  these  programs.   This
          pack should be labeled MTS421 and have public volume number
          1.   It  will  be the "system residence pack" for D4.2 MTS.
          You may also want to DASDI any HASP SPOOL packs you plan to
          use and a VAM2 paging disk at this time.
-    2.   Run DECKGEN to prepare a set of TABLES  for  your  machine.
          To  load  DECKGEN,  IPL  from  the pack prepared in step 1.
          This will probably put the machine in  wait  state  (unless
          you have a 3066, 3270, or 1052-compatable device at address
          740).  To get the IPLREADER to talk to you, press "request"
          on  a  1052  or  "enter"  on a 3066 or 3270 (i.e., cause an
          attention interrupt).  When it asks if you want to run  the
          current system, reply "NO" and enter the commands:
0              LOAD NAME=*IPL.DECKGEN
               START
0         See the DECKGEN writeup (item 10073) for information on how
          to  proceed  from  here.   Since  DECKGEN was loaded by the
          IPLREADER (instead of from  tape)  and  therefore  is  told
          where  the  console  is,  it  is  not  necessary to give an
          attention interrupt on the console to wake  it  up.   Since
          you  are  only  going  to  use  the  D4.2 system to run the
          programs which restore the D4.3 system from tape, you don't
          really need to define an elaborate  I/O  configuration;  in
          fact, all you really need is a tape, two disks, a terminal,
          your  operator's  console, and a paging device (a 2305 or a
          third disk).  If you decide  to  define  all  of  your  I/O
          configuration,  it would be a good idea to run DECKGEN from
          a hardcopy terminal if  this  is  possible.   If  not,  you
          should  take notes as you go along because you will need to
          run DECKGEN again as part of step 9 and it will  save  time
          if you keep a record of your first DECKGEN run.  You should
          note that the MTS naming convention used for IBM 2305 fixed
          head  files  has  been changed between D4.2 and D4.3.  When
          you run DECKGEN this first time (to build the D4.2 system),
          be sure that your 2305s have names  that  begin  with  FHF.
          When you run it again in step 9 (to build the D4.3 system),
1                                                                   2
-
          be sure that the names begin with FF.
-    3.   You  are  now  ready to load MTS itself.  IPL from the pack
          prepared in step 1, and again reply NO when  asked  if  you
          want the current system.  This time enter the commands:
0              LOAD NAME=*IPL.D4.2
               REPLACE TABLES FROM xxx
               (Reply to the prompt for a printer address for a map)
               START
0         where  xxx  is  the address of the tape written by DECKGEN.
+                ___
          MTS should now be running.
-    4.   Proceed with the start-up procedures described in  the  MTS
          operators' manual (item 10075).  Some additional points not
          mentioned in the operators' manual are:
0         A.   The  prompt  for  the time and date will occur only if
               the TOD clock is not set.  For example,  entering  the
               time and date as
0                      2 41 pm 5 23 78 EDT
0              will  set  the time and date to 14:41 Eastern Daylight
               Time on 23 May 1978.  The timezone need not  be  given
               if you gave the correct timezone when you ran DECKGEN,
               i.e., MTS will use that one by default.
0         B.   MTS  keeps GMT in the TOD clock.  Although this agrees
               with the standard set by IBM for the use  of  the  TOD
               clock,  some  IBM  systems do not do this.  This means
               that even if the clock has been set by another system,
               it may be off by several hours and you  will  want  to
               reply "NO" when asked if the time is correct.  You can
               then  enter the correct local time, which MTS will use
+                                      _____
               to load the TOD clock with GMT.
-    5.   After MTS has finished the start-up procedures, you  should
          prepare  a  new  IPL  system containing the TABLES for your
          machine.  First, you must start an MTS job, preferably on a
          terminal, but the operator's console may also be used.  For
          example, to start a job on a 3270 which you named  DS10  in
          your DECKGEN run, enter
0              MTS DS10
0         on  the  operator's console.  To start a job on the console
          itself, enter
0              MTS OPER
0         on the console.  Then signon and enter the following:
1                                                                   3
-
               SIGNON MTS
               password (see below)
               RUN RAMROD
               CREATE xxxxx FROM D4.2SYS
               enter comments if desired
               REPLACE TABLES.DUMMY FROM >Tyyy
               enter comments if desired
               enter null line or date when prompted for version
               reply "OK" to confirmation request
               DELETE SEG0.NCA.TABLES
               reply "OK" to confirmation request
               DELETE SEG1.NCA.TABLES
               reply "OK" to confirmation request
               RENAME TABLES.DUMMY TABLES
               reply "OK" to confirmation request
               CURRENT
               reply "OK" to confirmation request
0         The passwords for most of the userids  on  the  distributed
          test  pack  are the same as the userids, e.g., the password
          for MTS is MTS.  The only userids for which  the  passwords
          are  different  are  the  terminal  benchmark IDs (Bnnn and
          BBnn) since the passwords for these are irrelevant.   (Note
          that  a  password  is  not  required  if  you are using the
          operator's console as your  terminal.)  The  xxxxx  on  the
+                                                      _____
          CREATE command is a name for the new system, which normally
          would  be  the MTS "model number" for the date, e.g., UG157
          for August 15, 1977.  Tyyy is the name of  the  tape  drive
+              __    __     _   ____
          containing the tape written by DECKGEN.
0         This  procedure  will  cause  the  "current" system on your
          MTS421 pack to correspond to your machine configuration  so
          that  the next time you IPL you can reply "YES" (or enter a
          null line) when asked  if  you  want  to  run  the  current
          system.   See  the  RAMROD (item 10038) and IPLREADER (item
          10072) writeups for more information.
-    6.   You now have a working D4.2 version of MTS (hopefully).  As
          mentioned above, the only need for the D4.2  system  is  to
          provide the MTS environment needed to run the MTS DASDI and
          DISKCOPY programs which are used to restore the D4.3 system
          from  tape.   To  do this, you must first restore these two
          programs to your MTS421 pack from  the  D4.3  FS  tapes  by
          entering the following commands from any terminal:
0              SIGNON FILE
               FILE (the password)
               MOUNT XXX 9TP *T* VOL=4.3Tn LBLTYPE=VLO
               RUN *FS 0=*T*
               RESTORE (nnn) D4.3DASDI
               RESTORE (mmm) D4.3DISKCOPY
               STOP
               RELEASE *T*
0         Since there are two versions of the D4.3 FS tapes (6250 and
1                                                                   4
-
          1600  bpi),  you  will  have  to  consult  the  appropriate
          distribution driver file index (item 10067A or 10067B)  for
          the  object  files  for  the  components  DASDI (598/2) and
          DISKCOPY  (724/3).   (Note  that  724/3  is  a  version  of
          DISKCOPY  designed to run in a pre-D4.3 MTS system.  DO NOT
          try to use the D4.3 regular DISKCOPY object  (724/2)  since
          it  won't  work  in  a  pre-D4.3  system.)  The  index will
          indicate on which tape each is located and  what  the  file
          numbers  are.   Replace  "4.3Tn" in the above MOUNT command
          with the  correct  volume  name  and  replace  "(nnn)"  and
          "(mmm)"  with the correct file numbers, which must be given
          in parentheses.  The *FS program is described in MTS Volume
          2 if you need more information on its use.
-    7.   Use this DASDI to initialize a VAMX  disk  pack  as  public
          volume  1  with  a  volume  name other than MTS421.  MTS431
          would  be  a  good  choice.   See  the  General  Notes  for
          instructions  on  using FILE:DASDI.  The following commands
          illustrate the use of this program:
0              RUN D4.3DASDI
               Dxxx MTS431 VX 1 IPL
               $ENDFILE
0         where  "Dxxx"  is  the  device  name  of  the  disk  to  be
          initialized  and "MTS431" is the volume name to be used for
          the disk pack.
-    8.   Use  DISKCOPY  to  restore  the  D4.3   system   from   the
          distributed  VAMX dump/restore tape(s).  You should specify
          the IPL option, but SLOW and SWAP  aren't  necessary.   See
          the General Notes for information on running DISKCOPY.  The
          following commands illustrate the use of this program:
0              RUN D4.3DISKCOPY
               TAPE
               >Tnnn
               DISK
               Dxxx MTS431
               IPL
               $ENDFILE
0         where  >Tnnn  is  the  device  name  on which the D4.3 VAMX
          dump/restore tape is mounted.  If you received the 1600 bpi
          distribution, you will be prompted to enter a  second  tape
          device name when DISKCOPY is ready for the second tape.
-    9.   Stop  your  machine, remove the D4.2 system pack and repeat
          steps 2, 3, 4, and 5 using the D4.3 system  pack  and  D4.3
          names  (NAME=*IPL.D4.3  and  CREATE  xxxxx FROM D4.3SYS) in
          place of the D4.2 system pack and D4.2  names.   Note  that
          you  must  run  DECKGEN again for the D4.3 generation since
          the tape generated in step 2 for the D4.2 system  will  not
1                                                                   5
-
          work  correctly  with  the  D4.3  system.  Also, you should
          remember to name any 2305s in your D4.3 system  with  names
          FF00-07,  FF08-0F,  FF10-17, etc.  rather than the old FHFn
          names used in earlier distributions of MTS.
-    10.  You now have a working D4.3 version  of  MTS  (presumably).
          You  can  start  to  run user programs after you've created
          some user IDs.  To do this,  see  the  description  of  the
          accounting  maintenance  procedures  (104/112),  which  you
          should obtain from the *FS tapes.
0         There are several things that you will probably want to  do
          to  clean  up  a  few loose ends before going much further.
          Some of these are:
0         A.   Fix HASP for whatever local options you  desire.   See
               the  description  of  these options (item 10077).  You
               may also want  to  change  some  of  the  commands  in
               STRT:HSP, the command file for *HSP, which can be used
               by  the operators to issue the appropriate HASP $START
               commands after starting HASP.
0         B.   You will also want to change the contents of STRT:LAS,
               the command file for *LAS, which can be  used  by  the
               operators to start up the terminal lines.
0         C.   Fix TSFO (the 2703/1270 MTS Device Support Routine) to
               agree  with whatever hardware is available.  There are
               several assembly parameters described in the source.
0         D.   Fix  up  the   command   statistics   directory   file
               SYS:CMDDIR for the appropriate tapes.  If you don't do
               this,  the  system will occasionally mount a tape with
               rack number CMDTP (which must be  labeled  CMD001)  to
               dump  the  command  statistics  data.  Eventually this
               tape will fill up with command statistics data and the
               system  will  get  mad  unless  you  have   fixed   up
               SYS:CMDDIR  to  give  it more tapes to use.  A writeup
               describing the structure of  this  file  is  available
               (531/35) on the *FS tapes.
0         E.   Write  new  versions  of  the  IPLBOOT  and  IPLREADER
               programs to the system pack with  the  correct  device
               address  for  your  system  console (see the IPLREADER
               description, item 10072).
-    11.  General things new installations should know.
0         A.   How to sign on using the operators console:
0              1. Enter "MTS OPER" on the operators' console
               2. It will come back immediately for input.
               3. Enter the signon command.
               4. You are  now  signed  on  if  the  ID  exists.   No
1                                                                   6
-
               password is required for signon from OPER and SIGFILEs
               are not processed.  Also the "last signon" message and
               the "signed on at" message are not printed.
0         B.   A 2301 drum must have device name DRM1.  If you have a
               second  2301,  it  must  be named DRM2.  Similarly, in
               pre-D4.3 systems 2305s must be named FHF0 to FHF7  for
               the  first  one, FHF8 to FHFF for the second one, FHFG
               to FHFN for the third, etc.  Starting  with  D4.3  the
               names  should  be  FF00->FF07, FF08->FF0F, FF10->FF17,
               etc.
0         C.   A "privileged" ID is one with X'80' on in  the  second
               byte  (byte  1)  of  the  accounting  record  (set  by
               accounting maintenance program on request).  If the ID
               is privileged then  no  checking  for  maximum  money,
               etc.,  is  made.  The expiration date and maximum file
               space, however, are checked.  Also this bit allows the
+                              ___
               user to run programs  with  PROT=OFF,  allows  "public
               file  privilege"  (see  next),  and  allows privileged
               SYSTEMSTATUS commands to be given.
0         D.   A "public file privileged" ID is one with X'08' on  in
               the second byte of the accounting record.  This allows
               the user to create a public file.
0         E.   A  user  with  the  ACCPUSE  bit  on in his accounting
               record can also declare  a  program  to  be  run  with
               PROT=OFF   and   can   issue  privileged  SYSTEMSTATUS
               commands.
0         F.   A  user  with  either  ACCTLB  or  ACCPLB  on  in  his
               accounting  record can set LSS (Limited-Service State)
               off even if the load is too high.
0         G.   Certain IDs are used automatically during the start-up
               sequence (INIT, SEG2, SYS., STRT).  These IDs must  be
               part  of  project WOPN on the test pack system so that
               they can signon even  if  the  "in  use"  bit  in  the
               accounting record is set.  The project number used for
               this  test in your production system may be changed by
               using a different project or project substring (or set
               of   them)   on   the   &IPLPROJ   SETC   symbol    in
               COPY:GLOBALSETS.
0         H.   MTS makes certain checks to be sure that only IDs that
               belong  to  individuals  that  work  for the computing
               installation   can   perform   certain    "privileged"
               operations.   This  check  is  made  by  checking  the
               project number associated with the ID.  At UM  and  in
               the D4.3 system, only projects that start with "W" are
               assumed  to belong to installation staff.  This may be
               changed by altering the setting  of  the  SETC  symbol
               &SYSPROJ   in   COPY:GLOBALSETS   and  assembling  and
               installing a new version of MTS.
