| 1 | Welcome to the IBM System/3 Model 10 SIMH simulator.\r |
| 2 | ---------------------------------------------------\r |
| 3 | \r |
| 4 | To compile under linux:\r |
| 5 | \r |
| 6 | cc s3*.c scp*.c sim_rev.c -o s3\r |
| 7 | \r |
| 8 | This code can be compiled and run as a console application using\r |
| 9 | Microsoft Visual C++.\r |
| 10 | \r |
| 11 | \r |
| 12 | \r |
| 13 | To IPL the provided SCP distribution disk:\r |
| 14 | \r |
| 15 | ./s3\r |
| 16 | sim> at r1 m10scp.dsk\r |
| 17 | sim> at f1 f1f1f1.dsk\r |
| 18 | sim> at lpt print.txt\r |
| 19 | sim> d sr 5471\r |
| 20 | sim> boot r1\r |
| 21 | \r |
| 22 | \r |
| 23 | // DATE 06/14/01\r |
| 24 | // NOHALT\r |
| 25 | // LOAD $MAINT,R1\r |
| 26 | // RUN\r |
| 27 | // COPY FROM-R1,LIBRARY-ALL,NAME-DIR,TO-PRINT\r |
| 28 | // END\r |
| 29 | \r |
| 30 | \r |
| 31 | (A printout of the libraries and directories on the SCP DTR\r |
| 32 | disk will be in the file print.txt)\r |
| 33 | \r |
| 34 | \r |
| 35 | The text file "system3.txt" gives details on the simulators\r |
| 36 | implementation of System/3 hardware.\r |
| 37 | \r |
| 38 | A write up on the use of the SCP and the OCL job control language is\r |
| 39 | in the text file "userguide.txt". This includes examples of using the\r |
| 40 | utility programs, and a tutorial guiding you thru a sysgen.\r |
| 41 | \r |
| 42 | A nearly complete listing of all possible SCP halts is in the \r |
| 43 | document "haltguide.txt".\r |
| 44 | \r |
| 45 | IMPORTANT NOTES:\r |
| 46 | \r |
| 47 | 1) How to correct typing errors when using the System/3 console:\r |
| 48 | If you make an error, press ESC, which will cancel the current\r |
| 49 | line being typed and print a quote in position 1. Then you\r |
| 50 | can use CTRL/R to retype characters up until the error, then\r |
| 51 | type correctly. Or simply retype the line. BACKSPACE DOES NOT\r |
| 52 | WORK with the SCP.\r |
| 53 | \r |
| 54 | 2) While the simulator allows disk images to be independently\r |
| 55 | attached to any disk unit, on the real hardware R1 and F1 were on\r |
| 56 | a single spindle, and R2 and F2 likewise. It is not possible using\r |
| 57 | SCP to attach R1 without attaching a disk image to F1 also, because\r |
| 58 | SCP will always look at F1 even when IPLed off R1.\r |
| 59 | \r |
| 60 | The OS distributed with the simulator is version 16 of the Model \r |
| 61 | 10 SCP. This is sysgenned with support only for R1 and F1. If you\r |
| 62 | do a sysgen to support R2 amd F2 also, you must have images attached\r |
| 63 | to all 4 disks when you IPL, because SCP looks at all drives when\r |
| 64 | it starts up, and you will get an "Unattached Unit" error if you\r |
| 65 | fail to have one attached.\r |
| 66 | \r |
| 67 | 3) The 1442 card reader had in reality one card input hopper\r |
| 68 | and two stackers. This means the same path is used for reading and\r |
| 69 | punching cards. When punching cards, SCP does a read operation\r |
| 70 | and inspects the card read for blanks, and if it is not blank,\r |
| 71 | issues a YH halt. SCP will not punch data onto non-blank cards.\r |
| 72 | This feature causes problems in the simulator, and as a result\r |
| 73 | if you punch cards from SCP, YOU MUST not have any file attached\r |
| 74 | to the CDR device. Leaving this device unattached presents an\r |
| 75 | infinite supply of blank cards to SCP for punching. \r |
| 76 | \r |
| 77 | \r |
| 78 | -- End of README_S3.txt --\r |