1 1 - INSTALLATION INSTRUCTIONS FOR NEW INSTALLATIONS + ____________ ____________ ___ ___ _____________ 0 MTS Distribution 6.0 0 April 1988 - 1. The starter system requires a minimum of one 3270 terminal, one 3380 disk drive, and one 9-track tape drive. Each device may appear at any of the addresses for the corresponding device type in the following default configuration (for XA machines, "address" indicates the device number): 0 Device Type Address Device name + ______ ____ _______ ______ ____ 3287 0000 PTR1 3270 0001-0007 DS01-DS07 3270 0009 CON1 2540R 000C RDR1 2540P 000D PUN1 1403 000E PTR2 3270 001F CON2 0 3287 0100 PTR3 3270 0101-011F DS21-DS3F 3420 0180-018F T900-t90F 0 3330 0200-020F D100-D10F 3350 0220-022F D200-D20F 3370 0240-024F D300-D30F 3380 0260-026F D400-D40F 0 3420 0C70 T920 0 9335 0D00-0D03 D500-D503 9335 0E00-0E03 D600-D603 0 MTS refers to devices by name rather than by address (or device number, in XA mode). You'll need to know the device addresses only for purposes of defining your configuration and IPLing the system; once MTS is running, use the "Device Name" column to determine the name of any device. 0 The starter system will select any one of CON1, CON2, DS01, or DS21 as the operator's console (whichever it finds first). At least one of these devices must be included in the configuration. DS01 is preferred, because the IPLREADer (see step 2) will talk to that device without any special prompting. 0 In addition, you must determine which architecture your machine supports (XA or 370) and, for the 370 architecture, whether your machine supports 2K or 4K storage protect keys, and whether your machine supports one-megabyte segments. Each possible combination of options is identified by a code; you will use the code later to 1 2 - specify which version of MTS to run. For XA machines, the code is "MP"; for "standard" 370 machines (2K keys and 1M segments) the code is "370"; for 370 machines with 4K keys and 1M segments, the code is "4K"; for 370 machines with 2K keys and 64K segments, the code is "64". - 2. You are now ready to load MTS. Mount the Dump/Restore tape and IPL from it. The message "Do you want to run the current system" will appear on the console (the first usable terminal in the sequence DS01, CON1, CON2, DS21). Enter the command: 0 RUN NAME=*IPL.xxx.NDSK ADDR=yyy 0 where xxx is the code indicating the type of machine and + ___ yyy is the address of the tape drive where the utility tape + ___ has been mounted. The no disk version of MTS should now start running. - 3. The system may prompt for the current time and date if you are running in a real machine and if the TOD clock is not set. For example, entering the time and date as For example, entering the time and date as 0 14:41:00 5/1/88 EDT 0 will set the time and date to 14:41 Eastern Daylight Time on 1 May 1988. 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. - 4. At this point you will be told that MTS600 couldn't be found (which is reasonable since you haven't restored it yet) and you should respond by entering CANCEL. This will result in a fairly serious looking message about an error in catalog initialization which can be ignored. - 5. Start the job status master job by typing 0 JOBS MAS 0 at the operator's console. - 6. The following steps can be done from the operator's console or from a 3270 terminal. If you are going to work from the operator's console you'll need to start an MTS job by 1 3 - typing 0 MTS NDSK OPER 0 at the console. If you are going to work from a terminal you'll need to start an MTS job on that terminal by typing 0 MTS NDSK xxxx 0 at the operator's console, where xxxx is the MTS device + ____ name of the terminal to be used. The NDSK parameter tells MTS to avoid using the file system. - 7. Next, signon by entering 0 SIGNON MTS. MTS. (the password) 0 If you are working at the operator's console you won't be asked to enter a password. If you are working from a terminal you will need to enter a password and because you are using the no disk system the password will be the same as the ccid used on the signon command (MTS. in this case). - 8. Next attach the MTS Utility tape to your job by entering 0 $GET >Txxx $CONTROL *AFD* VOLUME=MTSUTL 0 where Txxx is the MTS device name of the tape drive where + ____ the MTS Utility tape is mounted. - 9. Next DASDI the public volume to be restored by entering: 0 $CONTROL *AFD* POSN=DASDI $RUN *AFD* PROT=OFF Dxxx MTS600 VX 1 IPL $ENDFILE 0 where Dxxx is the name of the device where the pack to be + ____ restored is mounted. See the General Notes (comp. 461/19) for further instructions on using FILE:DASDI. - 10. Use DISKCOPY to restore the D6.0 system from the distributed dump/restore tape(s). You should specify the IPL option (SLOW and SWAP aren't necessary). See the General Notes for information on running DISKCOPY. 0 $CONTROL *AFD* POSN=DISKCOPY $RUN *AFD* PROT=OFF TAPE 1 4 - >Tnnn DISK Dyyy MTS600 IPL $ENDFILE 0 where >Tnnn is the name of the MTS device on which the D6.0 + ____ dump/restore tape is mounted and Dyyy is the MTS device + ____ name of the disk drive to which the data will be restored. - 11. Stop your machine, and IPL from the new disk. Enter the command: 0 RUN NAME=*IPL.xxx 0 where xxx is the code indicating the your machine type. + ___ The D6.0 version of MTS should now be running. - 12. Proceed with the start-up procedures described in the MTS Operators' Manual (comp. 592). This time you shouldn't be told that MTS600 couldn't be found. 0 After initialization is complete you should do the following from the operator's console or a terminal 0 SIGNON MTS password (see below) $RENAME *IPL.xxx *IPL.0 0 where xxx is the code indicating your machine type. This + ___ sets up the version of MTS appropriate for your machine as the "current" system; this version will be selected by the IPLREADer each time you reload and either just hit ENTER or type "YES" in response to "Do you want to run the current system." 0 There are two classes of userids on the distributed test system: shared system userids and private userids. The shared system userids are those userids like MTS. or FILE. The private userids are ST00 through ST99. The password for the shared system userids is "AARDVARKS". The passwords for the STnn userids is the same as the userid. (Note that if you are using the operator's console as your terminal, a password is not required for the shared system userids, but is required for the STnn userids.) The shared + __ system userids are protected by the program *CKID. If you attempt to sign on to one of those userids from a terminal other than the operator's console, you will be prompted for a password. After entering AARDVARKS, you will be prompted for a second userid and password. As distributed, the userids ST00 through ST09 have access to the shared system userids, so a typical signon to one of the shared system userids might look like: 1 5 - signon mts aardvarks (password for userid MTS) st01 (second level userid, in response to the "ID?" prompt) st01 (second userid's password, in response to the "PW?" prompt) 0 You should note that this set of passwords provides essentially no security, and you should change the + __ passwords for both the shared system userids and the private userids before beginning any kind of production use of the system. 0 13. You now have a working D6.0 version of MTS. 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/137) and (104/138), 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 (comp. 387/26). 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 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 description of the structure of this file is available in the Operators' Manual on the *FS tapes (comp. 592). 0 D. Install ASMH. Once you have a signed and paid license agreement with IBM for ASMH contact UM for a starter version of ASMH (ASMH is an IBM program product and as a result cannot be included on the standard MTS distribution tapes). 0 E. Build a new set of tables which describe your configuration. Building TABLES is described in the XA or 370-mode TABLES macros writeup. 0 F. If you are planning to run with more than one disk 1 6 - pack, you should use the utilities under the CCID BNCH to "smear" the one-pack system across several disk volumes to improve system performance (as opposed to just adding several empty volumes to the system). 0 G. If you add additional disk volumes, you should allocate additional spooling and paging extents on some of the volumes to further improve system capacity and performance. See the TABLES writeup for details. - 14. General things new installations should know. 0 A. How to sign on using the operator's console: 0 1. Enter "MTS OPER" on the operator's 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 for "staff" IDs and SIGFILEs are not processed. Also the "last signon" message and the "signed on at" message are not printed. 0 B. 2305 paging devices must be named FF00 to FF07 for the first one, FF08 to FF0F for the second one, FF10 to FF17 for the third, etc. 3805s and 3825s should be named FB00, FB01, etc. 0 C. A "rich" 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 rich then no checking for maximum money, etc., is made. The expiration date and maximum file space, however, are checked. (Just to confuse things, the accounting + ___ utilities refer to a rich ID as "privileged.") 0 D. A "PROT=OFF" ID is one with X'02' on in the third byte of the accounting record. This bit allows the user to run programs with PROT=OFF, and to use other privileged facilities, including privileged SYSTEMSTATUS commands. (The accounting utilities refer to a prot=off ID as a "PROT" ID.) 0 E. 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 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 1 7 - 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 and reassembling MTS. 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 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. 0 I. The distributed system contains a dummy version of the rate number subroutine (RNBR) which gives zero rates. You will almost certainly want to replace this routine with a version that calculates rate numbers according to the rules of your installation and also update the file *RATEFILE to include your MTS rates.