1 1 - INSTALLATION INSTRUCTIONS FOR NEW INSTALLATIONS + ____________ ____________ ___ ___ _____________ 0 August 1981 - 1. Run DECKGEN to prepare a set of TABLES for your machine. To load DECKGEN, IPL from the Dump/Restore tape. This will probably put the machine into wait state (unless you have a 3066, 3270, or 1052-compatable device at address 009). 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 ADDR=xxx START 0 where xxx is the device address of a tape drive on which + ___ the MTS Utility tape is mounted. See item 20012 for more information about the IPLREADER. 0 See the DECKGEN writeup (item 20014) for information on how to proceed from here. Since DECKGEN was loaded by the IPLREADER and therefore is told where the console is, it is not necessary to give an attention interrupt on the console to wake it up. It is 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 may need to rerun DECKGEN if you make a mistake and you can save some time if you keep a record of what you've done. You should include at least one public volume, MTS001, in these tables. The tables you produce should be written to tape for use in steps 2 and 15 below. - 2. You are now ready to load MTS itself. Rewind the Dump/Restore tape and IPL from it again. Reply NO when asked if you want the current system. This time enter the commands: 0 LOAD NAME=*IPL.NDSKSYS ADDR=xxx REPLACE TABLES FROM yyy (Reply to the prompt for a printer address for a map) START 0 where xxx is the address of the MTS Utility tape and yyy is + ___ ___ the address of the tape written by DECKGEN in step 1. The no disk version of MTS should now be running. - 3. Proceed with the start-up procedures described in the MTS operators' manual (item 20016). Some additional points not mentioned in the operators' manual are: 1 2 - 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 81 EDT 0 will set the time and date to 14:41 Eastern Daylight Time on 23 May 1981. 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. - 4. At this point you will be told that MTS001 (or whatever name(s) you told DECKGEN to use) couldn't be found (which is reasonable since we 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 initilization 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 1052, 3066, 3036, 3277, 3278 or 3279 terminal. If you are going to work from the operator's console you'll need to start an MTS job by 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 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 ccid 1 3 - ccid (the password) 0 where ccid is any four character string. 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. - 8. Next attach the MTS Utility tape to your job by entering 0 $SET PROT=OFF $GET >Txxx $CONTROL *AFD* VOLUME=MTSUTL 0 where Txxx is the device name of the tape drive where the + ____ MTS Utility tape is mounted. - 9. If you have 2305s or 4305s to use for paging, you must format them by entering 0 $CONTROL *AFD* POSN=FMT2305 $RUN *AFD* FFnn FFnn . . . $ENDFILE - 10. If you are going to use 2301s for paging, format them by entering 0 $CONTROL *AFD* POSN=DRUMINIT $RUN *AFD* - 11. If you have 2305s, 3805s, 4305s or 2301s to use for paging, start the paging device processor by typing 0 PDP 0 at the operator's console. - 12. Next DASDI a paging disk and at least one public volume by entering 0 $CONTROL *AFD* POSN=DASDI $RUN *AFD* Dxxx PAG001 VX PAGING Dyyy MTS001 VX 1 IPL . . . 1 4 - $ENDFILE 0 where Dxxx is the name of the device where the new paging + ____ pack is mounted and Dyyy is the name of the device where + ____ the new file system volume(s) is mounted. See the General Notes (item 20000) for instructions on using FILE:DASDI. - 13. If you started the PDP in step 11, add the paging disk by typing 0 PGET Dxxx 0 at the operator's console. If you didn't start the PDP before, start it now by typing 0 PDP 0 at the console. - 14. Use DISKCOPY to restore the D5.0 system from the distributed dump/restore tape(s). You should specify the IPL option, but SLOW and SWAP aren't necessary. See the General Notes (item 20000) for information on running DISKCOPY. 0 $CONTROL *AFD* POSN=DISKCOPY $RUN *AFD* TAPE >Tnnn DISK Dyyy MTS001 IPL $ENDFILE 0 where >Tnnn is the name of the device on which the D5.0 + ____ dump/restore tape is mounted and Dyyy is the name of the + ____ disk drive to which the data will be restored. 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. - 15. Stop your machine, and IPL from the new disk. Again reply NO when asked if you want to run the current system and enter the commands: 0 LOAD NAME=*IPL.D5.0 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 in + ___ step 1. The D5.0 version of MTS should now be running. 1 5 - 16. Proceed with the start-up procedures described in the MTS operators' manual (item 20016). This time you shouldn't be told that MTS001 couldn't be found. 0 After initilization is complete you should do the following from the operator's console or a terminal 0 SIGNON MTS password (see below) $RUN RAMROD CREATE xxxxx FROM D5.0SYS 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) 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., UG151 for August 15, + __ __ 1981. Tyyy is the name of the tape drive containing the + _ ____ tape written by DECKGEN. 0 This procedure will cause the "current" system on your MTS001 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 20013) and IPLREADER (item 20012) writeups for more information. - 17. You now have a working D5.0 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/118), 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 1 6 - the description of these options (item 20023). 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/40) 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 20012). 0 F. In the tables produced by DECKGEN none of the file system disks are flagged as being under disk manager control. You can place them under disk manager control using the DMGRSTAT job program or the *-file job *DSK. This will need to be done after each IPL until you hand-code a version of tables for your configuration. - 18. 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 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, 2305s must be named FF00 to FF07 for the first one, FF08 to FF0F for the second one, FF10 to FF17 for the third, etc. 1 7 - 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 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. 1 8 - Because some of the steps outlined above require running a version of MTS without a file system, some error messages that would normally be obtained from the file *SMDS will not be available and an error number will be printed instead. The various error numbers and their associated text is given here. - 10 SOURCE and SINK are same file. 11 You have not signed on yet. 13 No more logical device numbers available. 14 Non-zero return code from output subroutine. 15 Output file or device same as input file or device. List terminated. 16 Too many system components loaded. Command terminated. 17 Input line is too ling. Line truncated to 255 characters. 18 Password incorrect. Try again. 22 Can't rename: is SOURCE, SINK, MSOURCE, or MSINK. 23 First parameter must be FDname. 25 Control command not available for this device type. 26 Illegal parameters 27 Illegal SOURCE file or device. 28 Illegal SINK file or device. 29 SOURCE or SINK file or device must be specified. 30 There is no previous SOURCE or SINK. 31 Insufficient space available. 32 Illegal size parameter. 33 Illegal file name specified. 34 "Pseudodevice names" cannot be created. 35 *...* nnnnnn {CANCELLED|RELEASED ...} 36 Invalid or missing parameter. 37 Invalid "$ENDFILE" line encountered. 38 HELP: RC=4 from SDUMP. 39 Device specified is not an output device. 40 You must give display parameters. 41 Last parameter did not request output. 42 Invalid parameters gave RC=4 from sdump. 43 Questionable use of "from" or "to" 44 Questionable use of "on" 45 Error return from GDINFO 48 Device specified for input is not an input device. 49 Device specified for output is not an output device. 50 There is no active file to use. 51 Inconsistent or improper line number parameters 52 Can't destroy: is SOURCE, SINK, MSOURCE, or MSINK. 53 Can only renumber line files 55 The data cells have been removed. Sequential disk file assumed. 57 But that's not a file... 58 Help - unit exception on SSF. 59 Help - unit exception on punch. 61 Hardware error or software inconsistency in create possibly due to bad volume name. 63 Illegal old filename in rename 64 Illegal new filename in rename 65 You must sign on as a library file. 1 9 - 66 There is no active file to put that in. 67 You have already signed on. 68 Illegal user id 69 Too many parameters were given. 71 Illegal or missing address. 72 Improper boundary alignment. 74 Hex number too long or not valid. 75 Invalid register designation. 76 Enter user password. 78 Password incorrect. 79 Illegal command for this signon id 80 No interaction is possible in batch mode. 81 Missing comma. 82 Attempt to change msource using "$continue with". 83 Illegal file name for create command. 84 Illegal blank before left parenthesis. 85 Hardware error or software inconsistency in rename 86 File to be destroyed must be specified. 87 Warning: Specifying PW=password or PASSWORD=password on the $SIGNON command is a risky practice. 89 Invalid file or device name for control command. 92 Enter "OK", "YES", or "!" to confirm; "NO" or return to decline; or "CANCEL" to cancel. 94 File already exists 95 Line files are not allowed on data cell 96 Unable to get input record length 97 Current size n pages, n pages recovered. 98 nP, nP recovered. 100 No more storage index numbers 101 Too many levels of link 103 You must destroy some files before you can create more. 104 You have exceeded your allotted space. You must destroy some files before you can create more. 107 Enter replacement or "CANCEL". 108 Cancel what? 109 You must give receipt number 110 Can't cancel at this time. Try again later. 111 Is *SINK*; will not be cancelled until released. 112 Illegal line number or delimiter. 114 Illegal or missing parameter 115 Number has too many digits after decimal point 116 Number has too many digits before decimal point 117 System error -- can't open the new file. 118 Invalid parameter 119 Illegal command for limited-service state (LSS) 120 This is a limited signon: Execution time limited to .25 sec. per run. 121 LSS is already on 122 LSS is already off 123 Can't set LSS off now - load too high 124 But for you I'll do it anyway 125 Libsrch string contains null library name 126 Loader tables not available 129 Can't "control" that 130 No space 132 Not input device 1 10 - 133 Not output device 135 Command terminated due to previous error in SDS. 136 Illegal CANCEL command in batch job 137 Incorrect use of I on COPY or LIST command. 140 Enter "CONTINUE" to continue what was interrupted; Enter "MTS" to return to MTS command mode. 142 Unable to read project sigifle. 143 LSS mode has been turned off. 144 .25 sec. time limit imposed due to LSS. 145 Time estimate too big for LSS mode. 146 Execpkey may not be prefixed by a userid other than your own. 147 Program key has been set to default value (*EXEC). 148 There is no loaded program. 149 "LIBSRCH=" library not searched because of nondefault program key. 150 Program key of loaded program has been set to default value. 151 Enter "OK" or "YES" to confirm; "CANCEL" to cancel. 152 System error in attention interrupt handling. 153 System error in program interrupt handling. 154 ILLEGAL FILE NAME FOR DESTROY COMMAND. 155 No jobs are waiting for this file. 156 This job has no files open or locked and is not waiting for any file. 157 None. 158 Error return from "ICSTAT" (System error). 159 Illegal file name specified for LSTATUS command. 160 Illegal job number "xxx" specified for LSTAT command. 161 Illegal MTS command while a Run-Only program is loaded 162 Password has been changed. 163 Protection has been enabled. 164 Run-only program has been unloaded. 165 WARNING: Program being run with no local time limit. 166 Due to concatenation or replacement the output file is the same as the input file. List terminated. 168 Line number ranges, I/O modifiers and concatentaton may not be used 169 Invalid "$CONTINUE WITH" line encountered. 170 Once PWCONFIRM has been set on during a given session it may not be set off again during that session. 172 I/O call from xxxx uses illegal parameters, part of parameter list is not addressable. 173 I/O call from xxxx uses illegal parameters, parameter list is not addressable. 174 I/O call from xxxx uses illegal parameters, FDUB pointer is invalid. 175 I/O call from xxxx uses illegal parameters, FDUB is invalid. 176 I/O call from xxxx uses illegal parameters, unit parameter is not addressable. 177 I/O call from xxxx uses illegal parameters, I/O modifiers are not addressable. 178 I/O call from xxxx uses illegal parameters, line number is not addressable. 179 I/O call from xxxx uses illegal parameters, 1 11 - Input/Output buffer is not addressable. 180 I/O call from xxxx uses illegal parameters, length halfword is not addressable. 181 I/O call from xxxx uses illegal parameters, output request specifies negative length. 182 I/O call from xxxx uses illegal parameters, unit parameter is invalid. 183 Reading line xxxx from "Fdname". 184 New passwords do not agree - password not changed. 185 Giving a password on the $SET command is a bad practice. The preferred method is: $SET PW newpw 187 Enter new user password. 188 Password too short - Passwords must be between 1 and 12 characters long with no embedded blanks or commas. 190 Reenter new user password to confirm. 191 Password not changed. 192 Enter old user password. 193 Password incorrect - password not changed. 194 Enter new PW. 195 Reenter new PW. 196 Enter old PW. 197 Password too long - Passwords must be between 1 and 12 characters long. 198 Password too long. 199 File "xxxx" is to be destroyed. Please confirm. 200 File "xxxx" is to be emptied. Please confirm. 201 File "xxxx" is to be renamed as "yyyy". Please confirm. 202 OK? "filename" 203 OK? "file1" as "file2" 204 Command Cancelled. 205 $SET PW 206 newpw 207 $ENDFILE may not be used as a password. 208 EXPRESS TERMINAL: Please limit your session to 5 minutes. 209 EXPRESS TERMINAL: You have used more than 5 minutes. Please signoff now if others are waiting for the termina 215 Default *PRINT* route is xxxx, Default *PUNCH* route is CN 216 Default *PRINT* and *PUNCH* routes are xxxx. 217 LOAD call uses illegal parameters. 218 Warning: PRINT=xx may not be used with ROUTE=xxxx, PRINT=ANY will be assumed unless ROUTE is changed. 219 I/O call from xxxx uses illegal parameters, I/O buffer is not convertible to upper case. 220 CLS can't be executed due to loading errors. 222 Error in program interrupt processing: Exit area unaddressable. 223 Error in attention interrupt processing: Exit area unaddressable. 224 No previous $RUN command. 225 Edited $RERUN text too long (>255 characters). 226 Max. signons exceeded, Job xxxx re-queued. CCID=xxxx 227 Error during GETIN call, please show this to a CC staff member. 228 Attempt to run a null program. 1 12 - 229 Too many parameters or invalid confirmation. 230 Use "OK" or "YES" to confirm. 231 Too many parameters or invalid confirmation. 232 Enter "OK" or "YES" to confirm; "NO" or "CANCEL" to cancel 233 MESSSUBS RC n. Show this to CC staff. 234 Software or hardware error while searching the *Userdirectory database. No user name could be set. 236 System error in {program interrupt | SVC intercept} processing. 237 Unaddressable exit region in {program interrupt | SVC intercept} processing. 500 Program will be run with protection enabled. 501 Program will be $DEBUGged with protection enabled. 502 LIBSRCH is being ignored. 504 Error occurred within system subroutine $RESTART inadvisable. 505 Try again after a few minutes. 506 $SIGNON command is a risky practice. 507 User passwords may no longer be specified on the $SIGNON or $CANCEL commands. 509 File does not exist. 510 Job not found. 511 Warning: Linenumber wrap-around has occured.