1 1 - INSTALLATION INSTRUCTIONS FOR NEW INSTALLATIONS + ____________ ____________ ___ ___ _____________ 0 August 1977 - 1. DASDI a disk pack and restore the tape(s) provided using TSS DASDI and DUMPRESTORE. The D4.0 General Notes (item 10000) contain instructions on the use of these programs. The version of DASDI and DUMPRESTORE on the restore tape supports 3330s (and 7330s). This pack should be labeled xxxx01 where xxxx is any 4 characters (normally MTS0), and + ____ will be the "system residence pack" for MTS. - 2. DASDI any other packs desired. Each should have a label of the form xxxxnn where xxxx is the same as above and nn goes + ____ __ from 2 on up sequentially. The public volume number of each pack should also be nn. + __ - 3. 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 or 1052 compatable device at address 440). To get IPLREADER to talk to you, press "request" on a 1052 or "enter" on a 3066 (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 10009) for information on how to proceed from here. - 4. 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 (or LOAD NAME=*IPL.D4.360 if a 360) 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. + ___ D4.0 MTS should now be running. - 5. Proceed with the start-up procedures described in the MTS operators' manual (item 10013). Some additional points not mentioned in the operators' manual are: 0 A. The prompt for the time and date will always occur on a 360 but will occur on a 370 only if the TOD clock is not set. On a 360 you will not be asked to verify the 1 2 - time and date, nor will you be asked for a time zone. 0 B. On a 370, MTS keeps GMT in the TOD clock. Although this agrees with the standard set by IBM for the use of the TOD clock, very few IBM systems do this. This means that even if the clock is set, it probably will be off by a few hours if an IBM system was the last system used on the machine. 0 C. The D4.0 system will produce several messages on the operators' console as it updates various public files which change depending on whether the system is being run on a 360 or a 370; ignore these. - 6. Prepare a correct IPL system containing the TABLES for your machine by signing on from some terminal and entering: 0 SIG MTS password (see below) RUN RAMROD CREATE xxxxx FROM D4SYS ( or D4SYS.360 if a 360) 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 all userids on the distributed test pack are the same as the userids, e.g., the password for MTS is MTS. 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. The next time you IPL you can reply "YES" when asked if you want to run the current system. See the RAMROD (item 10008) and IPLREADER (item 10007) writeups for more information. - 7. You now have a working version of MTS (presumably) and can start to run user programs. There are several things that you will probably want to do to clean up a few loose ends, however. Some of these are: 0 A. Fix HASP for whatever local options you desire. See the description of these options (item 10020). 0 B. Fix TSFO to agree with whatever hardware is available. 1 3 - There are several assembly parameters described in the source. 0 C. Replace various other parts of the system object deck to use either the SLT RPQ or the second CPU on a 360 if they are available. See the TABLES (item 10006) and Object Deck (item 10005) descriptions for more information. Multiple CPU 370s are not supported by MTS yet. The 360 system on the disk pack supports a standard model 67 360 with a possible 3270 operators' console. To support a duplex system, the CSTMDL field in the PSA (at 785) must be changed from X'01' to X'02'. The 370 system supports any model 370 or Amdahl machine with virtual memory. It allows a 3066, 3270, or 1052 compatible operators console. 0 D. Change the files INIT:INITCMD and *S2L to not do the extra things that are required to IPL on either a 360 or a 370. Each of these runs a program (CNFGSOU) to select one of two sets of commands depending on the machine type. INIT:INITCMD also copies several files which are different on the two machine types. All of this can be deleted if desired. 0 E. Fix up the command statistics directory file SYS:CMDDIR for the appropriate tapes. - 8. General things new installations should know. 0 A. How to sign on using the operators console. 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 password is required for signon from OPER and SIGFILEs are not active for signon from OPER. Also the "last signon" message and the "signed on at" message are not printed if MSOURCE is OPER. 0 B. A 2301 drum must have device name DRM1. If you have a second 2301, it must be named DRM2. Similarly, 2305s must be named FHF0 to FHF7 for the first one and FHF8 to FHFF for the second one. 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 + ___ declare a program to be run 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 1 4 - 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.