2 .;MONGEN.RNO 1-20-71 MT
\r
5 ^^PROGRAMMING SPECIFICATION\\
\r
11 ^^THE PROGRAM FOR DEFINING A PDP-10 MONITOR
\r
13 HARDWARE AND SOFTWARE CONFIGURATION
\r
19 ^FILE:##^^MONGEN.RNO\\
\r
27 ^THE INFORMATION IN THIS DOCUMENT IS SUBJECT TO CHANGE WITHOUT NOTICE
\r
28 AND SHOULD NOT BE CONSTRUED AS A COMMITMENT BY ^DIGITAL ^EQUIPMENT
\r
31 ^ACTUAL DISTRIBUTION OF THE SOFTWARE CONTAINED IN THIS SPECIFICATION
\r
32 WILL B
\0E SUBJECT TO TERMS AND CONDITIONS TO BE ANNOUNCED AT SOME FUTURE
\r
33 DATE BY ^DIGITAL ^EQUIPMENT ^CORPORATION.
\r
41 ^^TABLE OF CONTENTS\\
\r
50 2.0 PROCEDURE FOR CREATING A NEW MONITOR
\r
52 2.2 CONFIGURATION DIALOGUE
\r
53 2.3 PRODUCE COMMON.REL
\r
57 3.0 DESCRIPTION OF CONFIG.MAC
\r
58 4.0 DESCRIPTION OF COMMON.MAC
\r
59 5.0 DESCRIPTION OF COMMOD.MAC
\r
60 APPENDIX A - SAMPLE DIALOGUE
\r
61 APPENDIX B - DECIMAL DEFAULT VALUES
\r
62 APPENDIX C - OCTAL DEFAULT VALUES
\r
69 1.0##^^INTRODUCTION\\
\r
71 ^^MONGEN\\ (^MONITOR ^GENERATOR) IS A DIALOGUE PROGRAM THAT ALLOWS A
\r
72 USER TO DEFINE HIS HARDWARE AND SOFTWARE CONFIGURATION AS A PREREQUISITE
\r
73 TO CREATING A NEW MONITOR. ^WITH THE ANSWERS TO THE CONFIGURATION
\r
74 QUESTIONS, ^^MONGEN\\ PRODUCES A THREE-PAGE ^^MACRO\\ SOURCE FILE CALLED
\r
75 ^^CONFIG.MAC\\. ^THE USER ASSEMBLES ^^CONFIG.MAC\\ WITH ^^S.MAC\\
\r
76 (SYMBOL DEFINITION FILE) AND ^^COMMON.MAC\\ (MONITOR NON-DISK DATA BASE)
\r
77 TO PRODUCE A RELOCATABLE BINARY FILE CALLED ^^COMMON.REL\\. ^IF THE
\r
78 USER IS BUILDING A 5-SERIES DISK MONITOR, HE MUST ALSO ASSEMBLE
\r
79 ^^CONFIG.MAC\\ WITH ^^S.MAC\\.
\r
80 AND ^^COMMOD.MAC\\ (MONITOR DISK DATA BASE) TO PRODUCE ^^COMMOD.REL\\.
\r
81 ^THE FILE ^^DATDMP.MAC\\ (CORE BLOCK DUMPER) IS AN OPTIONAL
\r
82 DEBUGGING TOOL THAT MAY BE ASSEMBLED WITH ^^S, CONFIG\\, AND
\r
83 ^^COMMOD\\ IF DESIRED.
\r
85 2.0##^^PROCEDURE FOR CREATING A NEW MONITOR
\r
87 2.1##MONGEN\\ STARTUP
\r
89 ^THE USER INITIATES THE EXECUTION OF THE ^^MONGEN\\ PROGRAM BY TYPING
\r
97 ^^TYPE #DEVICE:NAME.EXT<CR>" FOR WHERE TO PUT RESULTS OF THIS DIALOG\\
\r
98 ^^CR ASSUMES "DSK:CONFIG.MAC\\"
\r
101 REQUESTING THE DEVICE AND THE FILENAME ON WHICH TO STORE THE RESULTS
\r
102 OF THE ^^MONGEN\\ DIALOGUE. ^THE USER RESPONDS WITH A SPECIFIC DEVICE AND FILENAME,
\r
103 SUCH AS ^^DEC\\TAPE 1 (SEE EXAMPLE BELOW) OR THE SYSTEM ASSUMES DISK
\r
104 STORAGE AND FILENAME ^^CONFIG.MAC\\.
\r
107 ^^DTA1:CONFIG.MAC\\
\r
112 ^^ANSWER THE FOLLOWING QUESTIONS WITH A Y OR N OR
\r
114 A DECIMAL NUMBER SHORT DIALOG\\?
\r
116 ^THE USER RESONDS WITH ^N IF HE WOULD LIKE THE BRACKETED, EXPLANATORY
\r
117 COMMENTS PRINTED WITH EACH QUESTION. ^THE USER TYPES ^Y IF THE SHORT
\r
118 DIALOGUE IS SUFFICIENT. ^IT IS RECOMMENDED THAT USERS NOT FAMILIAR WITH THIS VERSION OF
\r
119 ^^MONGEN\\ TYPE ^N IN RESPONSE TO THIS QUESTION.
\r
121 2.2##^CONFIGURATION ^DIALOGUE
\r
123 ^THE USER DEFINES HIS HARDWARE AND SOFTWARE CONFIGURATION BY ANSWERING
\r
124 ^^MONGEN'\\S QUESTIONS IN CONVERSATIONAL MODE. ^^MONGEN\\ TRANSMITS
\r
125 ONE QUESTION AT A TIME TO THE USER'S ^TELETYPE. ^DEPENDING UPON THE
\r
126 CONTENT OF THE QUESTION, THE USER RESPONDS BY TYPING ^Y FOR YES, ^N
\r
127 FOR NO, OR A DECIMAL NUMBER, FOLLOWED BY A CARRIAGE RETURN. ^CERTAIN
\r
128 QUESTIONS PERMIT THE USER TO RESPOND BY TYPING ONLY A CARRIAGE RETURN,
\r
129 THEREBY ACCEPTING A PREDETERMINED ANSWER. ^THE QUESTIONS AND THEIR
\r
130 DEFAULT OR STANDARD ANSWERS ARE IDENTIFIED BY THE BRACKETED COMMENTS
\r
131 ASSOCIATED WITH THE LONG DIALOGUE.
\r
132 ^MOST OF ^^MONGEN\\'S QUESTIONS AND THE USER'S ANSWERS ARE NOT DESCRIBED
\r
133 IN THIS DOCUMENT BECAUSE THEY ARE CONSIDERED TO BE SELF-EXPLANATORY.
\r
134 ^READERS UNFAMILIAR WITH THE GENERAL FORMAT AND CONTENT OF THE
\r
135 QUESTIONS AND ANSWERS ARE REFERRED TO ^APPENDIX ^A FOR A
\r
136 SAMPLE DIALOGUE. ^^MONGEN'\\S LESS OBVIOUS QUESTIONS ASSOCIATED WITH
\r
137 THE FOLLOWING, ARE DESCRIBED BELOW.
\r
141 1.##^DEFINING A ^TERMINAL ^CONFIGURATION,
\r
143 2.##^ANSWERING "SYMBOL, VALUE" QUESTIONS WITH DEFAULT ANSWERS
\r
145 3.##^ASSIGNING PRIORITY INTERRUPT CHANNELS TO SPECIAL DEVICES
\r
148 2.2.1##^DEFINING A ^TERMINAL ^CONFIGURATION
\r
150 ^THE ^^MONGEN\\ DIALOGUE REQUIRES THAT THE USER BE THOROUGHLY FAMILIAR
\r
151 WITH HIS INSTALLATION'S TERMINAL CONFIGURATION. ^IT IS RECOMMEMDED
\r
152 THAT THE USER READ THE DOCUMENT ENTITLED ^^SCNSER,\\ ^LEVEL ^D
\r
153 ^SCANNER ^SERVICE IN THE ^^PDP\\-10 ^SOFTWARE ^NOTEBOOK, AND OBTAIN
\r
154 ALL THE NECESSARY INSTALLATION INFORMATION BEFORE ATTEMPTING
\r
155 TO ANSWER THE QUESTIONS.
\r
160 ^^COMMON.MAC ALREADY EDITED FOR YOUR CONFIGURATION?\\
\r
162 ^TO WHICH THE USER ANSWERS ^Y IF HE HAS PREVIOUSLY DEFINED HIS TERMINAL
\r
163 CONFIGURATION BY EDITING ^^COMMON.MAC,\\ AND PREFERS TO SKIP THIS PORTION
\r
164 OF THE DIALOGUE. ^THE USER ANSWERS ^N TO THIS QUESTION IF HE WISHES
\r
165 TO DEFINE HIS TERMINAL CONFIGURATION WITH THE ^^MONGEN\\ DIALOGUE. ^IF
\r
166 THE USER HAS ANSWERED ^N, THE NEXT QUESTION ASKS WHETHER OR NOT HIS
\r
170 ^^BOTH DC10 AND 680?\\
\r
172 LINE INTERFACES. ^AN ANSWER OF NO IMPLIES THAT THE USER HAS ONLY
\r
173 ONE TYPE OF LINE INTERFACE, EITHER THE ^^DC10\\ OR THE 680.
\r
174 ^^MONGEN\\ THEN PRODUCES DIALOGUE THAT DETERMINES THE APPROPRIATE LINE
\r
175 INTERFACE AND DEFINES THE INSTALLATION'S CONFIGURATION. ^AN ANSWER OF
\r
176 YES PRODUCES A SERIES OF QUESTIONS RELATED TO BOTH THE ^D^C10 AND THE
\r
177 680. ^THIS IS THE MOST COMPLEX TERMINAL CONFIGURATION TO DEFINE.
\r
178 ^THE FOLLOWING PARAGRAPHS DESCRIBE THE QUESTIONS ASSOCIATED WITH THIS CASE.
\r
179 ^READERS UNFAMILIAR WITH THE ^D^C10 AND THE 680^I ARE REFERRED TO THE
\r
180 FOLLOWING HARDWARE MANUALS:
\r
183 1.##^^DC10 DATA LINE SCANNER (DEC-10-I8AA-D)\\
\r
186 2.##^^DATA COMMUNICATIONS SYSTEM-680I (DEC-08-I7CA-D)\\
\r
191 ^^HOW MANY DC10B 8-LINE DATA GROUPS?\\
\r
194 ^^HOW MANY DC10E DATA SET CONTROL GROUPS?\\
\r
199 ^^HOW MANY OCTAL LINES ON YOUR 680(I)?\\
\r
201 ^THE USER ANSWERS EACH QUESTION BY SPECIFYING THE NUMBER OF LINE GROUPS (AT LEAST 1) IN
\r
202 EACH CATEGORY THAT IS INSTALLED AT HIS INSTALLATION.
\r
204 ^THE NEXT QUESTIONS ASK FOR INFORMATION ABOUT TERMINAL LINE ASSIGNMENT.
\r
205 ^THE USER SHOULD PREPARE A PICTORIAL REPRESENTATION OF HIS CONFIGURATION BASED
\r
206 ON THE INSTALLATION'S TERMINAL LINE ASSIGNMENT. ^SOFTWARE ^^TTY\\
\r
207 LINE NUMBERS ARE ASSIGNED ACCORDING TO THE FOLLOWING FORMAT:
\r
212 1.##^ALL ^D^C10^B 8-LINE DATA GROUPS MUST BE ASSIGNED FIRST. ^THE
\r
213 SOFTWARE LINE NUMBERS, (^^TTY0, TTY1,...,\\ ETC.) MAP DIRECTLY TO THE PHYSICAL PORT
\r
217 2.##^NEXT THE ^D^C10^E DATA SET CONTROLLERS, IF ANY, ARE ASSIGNED TO THE
\r
218 PHYSICAL PORTS IMMEDIATELY FOLLOWING THE ^D^C10^B'S. ^SINCE EACH
\r
219 CONTROLLER IS ASSOCIATED WITH A DATA SET LINE, ^D^C10^E'S DO NOT
\r
220 HAVE THEIR OWN SOFTWARE ^^TTY\\ NUMBER. ^THE ASSOCIATION BETWEEN THE
\r
221 INDIVIDUAL DATA SET LINES (^D^C10^B) AND THE DATA SET CONTROLLERS
\r
222 (^^DC10E)\\ IS DETERMINED BY WIRING IN THE ^D^C 10 AT THE TIME THE
\r
223 DATA SETS ARE INSTALLED. (^THIS ^^DC10E, DC10B\\ CORRESPONDENCE
\r
224 IS REQUESTED BY A LATER ^^MONGEN\\ QUESTION.)
\r
227 3.##^THE SOFTWARE LINE NUMBERS (^^TTY\\N) FOR THE 680 TERMINALS FOLLOW
\r
228 DIRECTLY AFTER THE ^^DC10B\\ LINE NUMBERS, AND ARE ASSIGNED IN NUMERICAL
\r
229 ORDER IMMEDIATELY AFTER THE LAST ^^DC10B.\\
\r
232 ^FOR EXAMPLE, IF AN INSTALLATION HAS
\r
235 A.##^THREE ^^DC10B\\ 8-LINE DATA GROUPS
\r
238 B.##^ONE ^^DC10E\\ DATA SET CONTROL GROUP, AND
\r
241 C.##^SIXTEEN 680 LINE TERMINALS
\r
244 THE LINE ASSIGNMENT IS REPRESENTED AS FOLLOWS:
\r
251 ^^PHYSICAL SOFTWARE LINE NOS.
\r
257 .TAB STOPS 15,20,36,44,50
\r
258 #0 \L-----------------------------\L
\r
264 \L-----------------------------\L
\r
266 \L \L \L DC10 LINES
\r
268 DC10B'S \L \L \L (3 GROUPS)
\r
270 (3 GROUPS) \L \L \L
\r
272 \L-----------------------------\L
\r
275 \L##########\\DATA SETS^^ \L
\r
278 \L-----------------------------\L-----------
\r
279 30 \L \L\L TTY30 \L
\r
280 \L \\DATA SET \L\L \L
\r
281 \L CONTROLLERS^^ \L\L \L
\r
283 DC10E'S \L \\(CORRESPOND^^ \L\L \L
\r
285 (1 GROUP) \L \\TO LINE 20-27)^^\L\L \L
\r
286 \L \L\L \L 680 LINES
\r
287 37 \L \L\L TTY37 \L
\r
289 --------------------\L-----------------------------\L
\r
304 ^I\\N ADDITION TO LINE ASSIGNMENT THE USER MUST BE PREPARED TO ANSWER
\r
305 QUESTIONS ABOUT THE LINES AND TERMINAL HARDWARE, SUCH AS:
\r
309 1.##^WHICH TERMINALS HAVE HARDWARE TABS?
\r
311 ^MOST ^TELETYPE MODEL 35'S AND 37'S HAVE HARDWARE TABS, AND MOST
\r
312 MODEL 33'S DO NOT. ^HOWEVER, SINCE THE VARIETY OF FEATURES FOUND
\r
313 ON MODEL 33, 35, AND 37 ^TELETYPES IS SO GREAT, IT IS EACH USER'S
\r
314 RESPONSIBILITY TO DETERMINE THE PHYSICAL CHARACTERISTICS OF HIS INSTALLATION'S
\r
317 ^THE MONITOR SIMULATES TABS ON LINES WHICH DO NOT HAVE
\r
318 TABS BY ECHOING FROM ONE TO EIGHT SPACES.
\r
320 ^ALTHOUGH NOT RECOMMENDED IT IS POSSIBLE TO OVERRIDE ^^MONGEN\\
\r
321 TAB SETTINGS WITH THE ^^SET TTY TAB\\ AND ^^SET TTY NO TAB\\
\r
325 2.##^WHICH LINES ARE CONSIDERED REMOTE?
\r
327 ^ALL DATA SETS ARE IMPLICITLY REMOTE, AND THE INSTALLATION MAY GIVE "REMOTE"
\r
328 STATUS TO ANY TERMINAL, EVEN THOSE HARDWIRED. ^IN THIS CONTEXT REMOTE
\r
329 IS A SOFTWARE CHARACTERISTIC OF THE TERMINAL THAT IMPOSES CERTAIN
\r
330 RESTRICTIONS, SUCH AS PROJECT 1 CANNOT LOGIN.
\r
331 (^NOT TO BE CONFUSED WITH TERMINALS AT ^REMOTE ^STATIONS.)
\r
334 3.##^WHICH LINES ARE HALF-DUPLEX?
\r
336 ^THE USER MUST DETERMINE WHICH LINES TRANSMIT IN HALF-DUPLEX MODE.
\r
337 ^HALF-DUPLEX LINES PROVIDE TWO-WAY, ALTERNATE, INDEPENDENT TRANSMISSION OVER
\r
338 THE SAME PAIR OF WIRES.
\r
344 ^THE TERM HALF DUPLEX IS OCCASIONALLY USED INCORRECTLY. ^TRUE HALF
\r
345 DUPLEX LINES ARE RELATIVELY RARE. ^THEY INCLUDE CERTAIN ^^TWX\\ DATA
\r
346 SETS AND SOME LOCAL TERMINALS CONNECTED BY ^^DC10C\\ INTERFACES.
\r
347 ^SOME LINES LOOSELY CALLED HALF DUPLEX ARE ACTUALLY LOCAL COPY FULL DUPLEX.
\r
348 ^THE IDENTIFICATION OF LOCAL COPY LINES IS ASKED BY ANOTHER ^^MONGEN\\
\r
349 QUESTION. ^READERS INTERESTED IN A DEFINITION OF THESE TERMS ARE REFERRED
\r
350 TO A DOCUMENT ENTITLED ^^SCNSER,\\ ^LEVEL ^D ^SCANNER ^SERVICE (SECTION 3.0,)
\r
351 IN THE ^^PDP-10\\ ^SOFTWARE ^NOTEBOOK.
\r
355 4.## ^WHICH LINES ARE LOCAL COPY?
\r
357 ^THE USER MUST DETERMINE WHICH LINES ARE CONSIDERED LOCAL COPY FULL DUPLEX.
\r
358 ^IN LOCAL COPY LINES, ECHOING IS PROVIDED BY THE TERMINAL RATHER
\r
362 5.##^WHICH LINES ARE SLAVES?
\r
364 ^SLAVE IS A SOFTWARE CLASSIFICATION FOR TERMINALS THAT CANNOT LOGIN OR
\r
365 CONTROL JOBS. ^THEY GENERALLY PROVIDE ONLY ^^I/O\\ FOR JOBS CONTROLLED BY OTHER TERMINALS. ^A TERMINAL MAY BE CLASSIFIED AS A SLAVE BY
\r
366 ANY USER, BUT CAN ONLY BE RESTORED TO NORMAL STATUS AT THE OPERATOR'S
\r
370 6.##^WHICH LINES HAVE HARDWARE FORMFEED?
\r
372 ^MOST ^TELETYPE MODEL 35'S HAVE HARDWARE FORMFEED AND MOST MODEL 33'S
\r
373 DO NOT. ^SINCE THE VARIETY OF FEATURES FOUND ON VARIOUS TERMINALS IS SO GREAT,
\r
374 THE USER MUST INDIVIDUALLY DETERMINE THE HARDWARE CHARACTERISTICS OF HIS
\r
375 INSTALLATION'S TERMINALS.
\r
378 7.##^WHICH LINES RUN ^^INITIA\\ AT STARTUP?
\r
380 ^^INITIA\\ IS A PROGRAM THAT PERFORMS CERTAIN JOB INITIALIZATION FUNCTIONS.
\r
381 ^WHEN THE MONITOR STARTS UP, ^^INITIA\\ IS RUN AUTOMATICALLY FOR THE
\r
383 ^AT THE VERY LEAST DEVICE ^^OPR\\ SHOULD RUN ^^INITIA\\. ^IT IS
\r
384 RECOMMENDED THAT ALL LOCAL TERMINALS RUN ^^INITIA\\. (^REMOTE TERMINALS,
\r
385 DATASET TERMINALS, AND REMOTE STATION TERMINALS SHOULD NOT
\r
389 ^THE LAST ^^TTY\\ CONFIGURATION QUESTION ASKS FOR THE
\r
392 ^^CORRESPONDENCE BETWEEN THE DC10E AND DC10B LINES?
\r
394 ^T\\HE USER MUST DETERMINE WHICH ^^DC10E\\ DATA SET CONTROLLERS ARE WIRED
\r
395 TO WHICH ^^DC10B\\ LINES. ^IN OUR EXAMPLE (SEE FIGURE 1), LINE NUMBERS
\r
396 20 THROUGH 27 ARE ^^DC10B\\ DATA SET LINES THAT ARE HARDWIRED TO THE
\r
397 ^^DC10E\\ CONTROLLER LINES 30 THROUGH 37. ^THE CORRESPONDENCE IS THEN
\r
414 ^THE ACTUAL QUESTIONS AND ANSWERS USED TO DEFINE THE ^TERMINAL CONFIGURATION
\r
415 DESCRIBED BY THE ABOVE EXAMPLE ARE INCLUDED AS PART OF THE SAMPLE
\r
416 DIALOGUE IN ^APPENDIX ^A.
\r
419 2.2.2##^EXPLANATION OF ^QUESTIONS WITH ^DEFAULT ^ANSWERS
\r
421 ^^MONGEN\\ TYPES THE STATEMENT
\r
424 ^^TYPE "SYMBOL,VALUE" (VALUE IN DECIMAL)\\
\r
426 ASKING THE USER TO TYPE ONLY THOSE CONSTANTS RELATED TO HIS CONFIGURATION
\r
427 THAT DEVIATE FROM THE STANDARD. ^^MONGEN\\ DEFINES EACH OF THE SYMBOLS
\r
428 IN ACCORDANCE WITH PREDETERMINED, STANDARD VALUES UNLESS THE USER SPECIFIES
\r
429 OTHERWISE. ^A LIST AND EXPLANATION OF THE STANDARD SYMBOLS AND
\r
430 DECIMAL DEFAULT VALUES APPEAR IN ^APPENDIX ^B. ^FOR EXAMPLE, TO SPECIFY
\r
431 50 AS THE POWER FREQUENCY IN ^HERTZ INSTEAD OF THE STANDARD 60, THE USER
\r
437 ^IF THE USER HAS MORE THAN ONE ENTRY, EACH "SYMBOL, VALUE" COMBINATION
\r
438 IS TYPED ON A SEPARATE LINE, WITH AN EXTRA CARRIAGE RETURN AFTER THE LAST
\r
439 ENTRY. ^IF ALL STANDARD VALUES ARE ACCEPTABLE, THE USER TYPES
\r
440 ONLY ONE CARRIAGE RETURN IN RESPONSE TO THE QUESTION.
\r
442 ^NEXT THE PROGRAM TYPES
\r
445 ^^TYPE "SYMBOL,VALUE" (VALUE IN OCTAL)
\r
448 REQUESTING OCTAL VALUES THAT ARE TO BE CHANGED FROM THE STANDARD.
\r
449 ^THE PROCEDURE FOR THIS QUESTION IS EXACTLY THE SAME AS FOR THE
\r
450 PREVIOUS QUESTION. ^DEVIATIONS TO THE LIST OF DEFAULT VALUES ARE THE
\r
451 ONLY RESPONSES REQUIRED. ^APPENDIX ^C LISTS AND EXPLAINS THE STANDARD
\r
452 SYMBOLS AND OCTAL VALUES. ^IF NO CHANGES TO THE STANDARD ARE REQUIRED,
\r
453 THE USER TYPES ONLY A CARRIAGE RETURN.
\r
456 2.2.3##^ASSIGNING ^^PI\\ ^CHANNELS TO ^SPECIAL ^DEVICES
\r
458 ^THE NEXT THREE QUESTIONS ASK THE USER FOR SPECIAL INFORMATION RELATED
\r
459 TO NON-STANDARD PERIPHERAL DEVICES AND THEIR ASSOCIATED PRIORITY
\r
460 INTERRUPT CHANNELS.
\r
461 ^IF THE USER HAS NO SPECIAL DEVICES, HIS RESPONSE TO EACH OF THE THREE
\r
462 QUESTIONS IS SIMPLY A CARRIAGE RETURN.
\r
464 ^UNDER ORDINARY CIRCUMSTANCES
\r
465 WHEN ^^COMMON\\ IS ASSEMBLED, DEVICES ARE ASSIGNED TO CHANNELS
\r
466 ACCORDING TO THEIR GROUP PRIORITY.
\r
467 (^REFER TO ^TABLE 1-1).
\r
468 ^IF THE USER HAS A DEVICE NOT LISTED AS A STANDARD DEVICE IN
\r
469 ^TABLE 1-1, AND HAS WRITTEN HIS OWN ^MONITOR ^DEVICE ^SERVICE ^ROUTINE
\r
470 HE MUST SPECIFY THE DEVICE MNEMONIC AND DESIGNATE AN APPROPRIATE
\r
471 PRIORITY INTERRUPT CHANNEL. ^THE USER MUST ANSWER ALL THREE QUESTIONS
\r
472 AS THEY APPLY TO HIS CONFIGURATION. ^THE FIRST QUESTION REQUESTS THE
\r
473 ^^"DEVICE-MNEMONIC, CHANNEL"\\ FOR NON-STANDARD DEVICES FOR WHICH THE
\r
474 SPECIAL DEVICE SERVICE ROUTINES DO NOT NEED EITHER A ^CHANNEL
\r
475 ^SAVE ^ROUTINE OR A ^DEVICE ^DATA ^BLOCK. ^THE SECOND QUESTION REQUESTS
\r
476 ^^"DEVICE-MNEMONIC, CHANNEL, NO.-OF-DEVICES"\\ FOR DEVICES WITH SPECIAL SERVICE ROUTINES THAT HAVE
\r
477 A ^DEVICE ^DATA ^BLOCK BUT NO ^CHANNEL ^SAVE ^ROUTINE. ^THE
\r
478 THIRD QUESTION REQUESTS, ^^"DEVICE-MNEMONIC, CHANNEL, HIGHEST-AC-TO-SAVE"\\
\r
479 FOR DEVICES WITH SPECIAL SERVICE ROUTINES THAT HAVE A ^CHANNEL
\r
480 ^SAVE ^ROUTINE, BUT NO ^DEVICE ^DATA ^BLOCK.
\r
482 ^SPECIAL DEVICES ADDED BY A USER DURING THE ^^MONGEN\\ DIALOGUE ARE
\r
483 CHAINED TO THE REQUESTED CHANNEL. ^TO GIVE A DEVICE THE EXCLUSIVE
\r
484 USE OF A CHANNEL, THE USER RESPONDS TO THE "SYMBOL, VALUE (VALUE IN
\r
485 DECIMAL)" QUESTION WITH
\r
490 WHERE N IS THE PRIORITY INTERRUPT CHANNEL TO BE RESERVED. ^REFER
\r
491 TO THE LAST ENTRY IN ^APPENDIX ^B.
\r
498 ^DEVICE ^GROUPS FOR ^^PI\\ ^CHANNEL ^ASSIGNMENT
\r
503 ^DEVICE ^MNEMONIC######^GROUP ^NAME
\r
505 ---------------######----- ----
\r
509 ^^DCB\\ ^A 136 ^DATA CONTROL FOR 270 DISK
\r
512 ^^MTA\\ ^B ^^TM10A\\ ^MAGTAPE DATA CHANNEL
\r
515 ^^DCT C\\ 136 DATA CONTROL FOR 551 OR 516 TAPE CONTROLS
\r
518 ^^DTA\\ ^D ^^TD10 DEC\\TAPE DATA CHANNEL
\r
521 ^^CDR\\ ^E 461 OR ^C^R10 ^CARD READER
\r
524 ^^APR\\ ^E ^K^A10 OR 166 ARITHMETIC PROCESSOR
\r
527 ^^SCN\\ ^F ^D^C10, 680, OR 630 ^TELETYPE SCANNER
\r
530 ^^PTR\\ ^F ^PAPER TAPE READER
\r
533 ^^LPT\\ ^F ^LINE PRINTER
\r
536 ^^DTA\\ ^F ^^DEC\\TAPE FLAG CHANNEL (^^DTA \O\R DTC\\)
\r
539 ^^MTA\\ ^F ^MAGTAPE FLAG CHANNEL
\r
542 ^^CTY\\ ^F ^CONSOLE ^TELETYPE
\r
545 ^^DSK\\ ^G ^DISK FLAG CHANNEL (^^FHD,MDF,DPC, \O\R DPD\\)
\r
548 ^^PEN\\ ^G ^LIGHT PEN
\r
551 ^^PTP\\ ^G ^PAPER TAPE PUNCH
\r
554 ^^CDP\\ ^G ^CARD PUNCH
\r
557 ^^PLT\\ ^G ^PLOTTER
\r
560 ^^DIS\\ ^H ^DISPLAY DATA CHANNEL
\r
564 ^^CLK\\ ^I ^SCHEDULER, CLOCK ROUTINES (ALWAYS ASSIGNED TO CHANNEL 7)
\r
568 ^^I/O\\ DEVICES ARE GROUPED BY THE RELATIVE SPEEDS OF INTERRUPTS.
\r
569 ^IF ANY DEVICE OF A PARTICULAR GROUP IS PRESENT, A ^^PI\\ CHANNEL IS
\r
570 ASSIGNED TO THAT DEVICE ACCORDING TO ITS GROUP PRIORITY. ^GROUP
\r
571 PRIORITIES FOR STANDARD DEVICES MAY BE REVISED BY REARRANGING THE
\r
572 DEVICES IN ^^INTTAB\\, IN THE SOURCE OF ^^COMMON\\.
\r
574 ^AFTER ALL THE QUESTIONS ARE ANSWERED ^^MONGEN\\ PRODUCES ^^CONFIG.MAC\\,
\r
575 A THREE-PAGE ^^MACRO\\ SOURCE FILE. ^THE ORIGINAL ^^MONGEN\\ QUESTIONS
\r
576 APPEAR AS COMMENTS IN ^^CONFIG.MAC\\. ^IF THE USER PREFERS HE MAY
\r
577 MAKE MINOR MODIFICATIONS TO ^^CONFIG.MAC\\ WITH AN EDITOR, RATHER
\r
578 THAN RERUN THE ENTIRE ^^MONGEN\\ PROGRAM.
\r
582 2.3##^PRODUCE ^^COMMON.REL\\ AND ^^COMMOD.REL\\
\r
584 2.3.1#-#^THE USER ASSEMBLES ^^CONFIG.MAC\\ WITH ^^S.MAC\\ AND ^^COMMON.MAC\\ TO
\r
585 PRODUCE A RELOCATABLE BINARY FILE CALLED ^^COMMON.REL.\\ ^IF THE
\r
586 USER IS BUILDING A 5-SERIES DISK MONITOR, HE ALSO ASSEMBLES
\r
587 ^^CONFIG.MAC\\ WITH ^^S.MAC,
\r
588 AND ^^COMMOD.MAC\\, TO PRODUCE ^^COMMOD.REL\\. ^TO ASSEMBLE
\r
589 A DISK MONITOR THE USER TYPES
\r
592 ^^COMPIL#/CREF#S+CONFIG+COMMON,S+CONFIG+COMMOD\\
\r
597 2.3.2##^ASSEMBLY ^ERROR ^MESSAGES
\r
599 ^ONE OR MORE OF THE FOLLOWING ERROR MESSAGES ARE TYPED ON THE USER'S TERMINAL
\r
600 IF ATTEMPTS TO ASSEMBLE ^^CONFIG.MAC\\ ARE UNSUCCESSFUL.
\r
604 1.##^^MORE THAN 127. TTYS + PTYS EXCEED FIELD OF DDB.\\
\r
606 ^THIS MESSAGE INDICATES THAT THERE IS A SPECIFICATION ERROR IN THE DATA SET
\r
607 CONTROL TABLE. ^THE USER MUST CORRECT IT.
\r
609 ^THIS INDICATES THAT THE SYSTEM CAPACITY OF 127 ^^TTYS\\ AND ^^PTYS\\ HAS
\r
610 BEEN EXCEEDED. ^THE USER MUST RERUN ^^MONGEN\\, ANSWERING QUESTIONS
\r
611 FOR FEWER ^^TTYS\\ AND ^^PTYS\\.
\r
614 2.##^^NOT ENOUGH PI'S TO SERVICE THIS CONFIGURATION SUGGEST EDITING COMMON
\r
615 TO PUT MORE DEVICES ON A SINGLE CHANNEL.\\
\r
617 ^THIS MESSAGE INDICATES THAT THE SYSTEM CAPACITY OF 7 PRIORITY INTERRUPT
\r
618 CHANNELS HAS BEEN EXCEEDED. ^THE USER SHOULD ASSIGN MORE DEVICES TO EACH
\r
619 ^P^I CHANNEL BY EDITING ^^INTTAB\\ IN THE SOURCE OF ^^COMMON\\.
\r
622 3.##^^FT2REL MUST BE -1 WHEN 2 RELOC REGISTERS EXIST.
\r
625 4.##PLEASE ASSEMBLE SOURCES WITH FTRTTRP = -1.
\r
628 5.##PLEASE ASSEMBLE SOURCES WITH FTLOCK = -1.
\r
631 6.##PLEASE ASSEMBLE SOURCES WITH FTHPQ = -1.\\
\r
633 ^THESE MESSAGES INDICATE THAT THE USER EDITED ^^S.MAC\\ INCORRECTLY.
\r
634 ^THE USER MUST REEDIT ^^S.MAC\\ TO CORRECT THE IMPROPER SYMBOL
\r
638 7.##^^SPECIFICATION ERROR - DSCTAB.\\
\r
640 ^THIS MESSAGE INDICATES THAT THERE IS A SPECIFICATION ERROR IN
\r
641 THE DATA SET CONTROL TABLE. ^THE USER MUST CORRECT IT.
\r
646 2.4##^LOAD THE ^MONITOR
\r
648 ^THE USER LOADS USING ^^COMMON.REL\\ WITH A REGULAR LOADER UNDER TIMESHARING, ^^MONLOD\\, OR
\r
649 UNDER A SMALL SINGLE-USER MONITOR (^^SPMON\\).
\r
650 ^SYSTEMS WITH 32^K OR 48^K
\r
651 OF MEMORY MUST LOAD A TIMESHARING MONITOR USING ^^SPMON\\ AND A
\r
652 REGULAR 10/30 LOADER (^^LOADER.SVE\\).
\r
654 ^OBSERVE THAT THERE IS A DISTINCTION BETWEEN THE EXTENSIONS ^^.SVE\\
\r
655 AND ^^.SAV.\\ ^^.SVE\\ IS THE STANDARD EXTENSION FOR FILES SAVED
\r
656 BY THE 10/30 ^^SAVE\\ COMMAND. ^^.SAV\\ IS THE STANDARD EXTENSION
\r
657 FOR FILES SAVED BY THE 10/40 OR 10/50 ^^SAVE\\ COMMAND. ^UNDER ORDINARY
\r
658 CIRCUMSTANCES THE TWO EXTENSIONS CANNOT BE INTERCHANGED BECAUSE THE
\r
659 JOB DATA AREAS ARE INCOMPATIBLE. ^SAVE FILES WRITTEN BY ^^SPMON\\
\r
660 ARE AN EXCEPTION TO THIS. ^ALTHOUGH ^^SPMON\\ IS A 10/30 MONITOR, IT
\r
661 CREATES ^^.SVE\\ FILES WHICH ARE COMPATIBLE WITH A 10/40 OR A 10/50
\r
662 MONITOR. ^THESE FILES CAN BE LOADED WITH A 10/40 OR 10/50 ^^GET\\ COMMAND
\r
663 FOR ^^DDT\\ PATCHING.
\r
666 ^TO LOAD AND SAVE THE MONITOR USING ^^COMMON.REL\\
\r
674 *DSK:COMMON,COMMOD,DSK:TOPS10/L
\r
682 2.5##^LIBRARY ^SEARCH
\r
684 ^THE USER INITIATES A LIBRARY SEARCH OF THE APPROPRIATE MONITOR FILE
\r
685 E.G., ^^TOPS10.REL\\, TO MAKE A MULTIPROGRAMMING
\r
686 NON-DISK 10/40 MONITOR OR A DISK SWAPPING 10/50 MONITOR.
\r
689 2.6##^MONITOR ^^SAVE\\
\r
691 ^THE USER EXECUTES THE MONITOR ^^SAVE\\ COMMAND TO WRITE THE LOADED
\r
692 MONITOR ONTO A ^^DEC\\TAPE, A DISK, OR A MAGTAPE AS A FILE THAT CAN
\r
693 LATER BE READ INTO EXEC CORE BY THE ^^DTBOOTS, BOOTS, \O\R MAGRIM\\
\r
694 LOADERS, RESPECTIVELY.
\r
697 3.0##^^DESCRIPTION OF CONFIG.MAC\\
\r
699 ^THE ^^CONFIG.MAC\\ FILE PRODUCED BY ^^MONGEN\\ CONTAINS THE FOLLOWING FOR
\r
700 EACH QUESTION ASKED.
\r
704 1.##^THE QUESTION ASKED BY ^^MONGEN\\, AS A COMMENT.
\r
707 2.##^THE ANSWER GIVEN BY THE USER, AS A COMMENT.
\r
710 3.##^ONE, TWO, OR THREE ^X^P#XXX^N,N MACRO DEFINITIONS THAT DEFINE
\r
711 SYMBOL XXX^N TO BE EQUAL TO N. ^A YES ANSWER HAS THE VALUE 1; A NO
\r
712 ANSWER HAS THE VALUE 0.
\r
715 ^^MONGEN\\ ALWAYS DEFINES ALL THE SYMBOLS THAT APPEAR IN ^^CONFIG.MAC\\,
\r
716 REGARDLESS OF THE ANSWER. ^THEREFORE, THE USER NEED NOT STUDY
\r
717 THE ^^MONGEN\\ PROGRAM IN ORDER TO UNDERSTAND WHAT HAPPENS ON
\r
718 CERTAIN QUESTIONS. ^IT IS SUFFICIENT TO LOOK AT THE LISTING OF ^^CONFIG.MAC\\
\r
719 THAT IS ASSEMBLED WITH ^^COMMON.MAC\\.
\r
721 4.0##^^DESCRIPTION OF COMMON.MAC\\
\r
723 ^WHEN THE THREE-PAGE ^^CONFIG.MAC\\ FILE PRODUCED BY ^^MONGEN\\ IS
\r
724 ASSEMBLED WITH ^^S.MAC\\ AND ^^COMMON.MAC\\, THERE IS NO FEATURE FILE,
\r
725 E.G., ^^FT50S,\\ BECAUSE THE DIALOGUE HAS ALREADY DEFINED THE
\r
728 ^SINCE ^^COMMON.MAC\\ SELECTIVELY ASSEMBLES ONLY ITEMS NEEDED FOR THE
\r
729 DEFINED CONFIGURATION, IT CONTAINS THE FOLLOWING (IN THIS ORDER):
\r
733 1.##^THE DEFAULT SYMBOLS THAT CAN BE OVERRIDDEN BY THE USER DURING THE
\r
734 ^^MONGEN\\ DIALOGUE.
\r
737 2.##^THE MONITOR STARTUP LOCATIONS.
\r
740 3.##^SPECIAL LOWER-CORE LOCATIONS (BELOW 140) IN THE MONITOR.
\r
743 4.##^VARIABLE DATA LOCATIONS FOR MOST OF THE MONITOR. (^THEREFORE,
\r
744 THE NAME ^^COMMON.\\)
\r
747 5.##^THE JOB AND HIGH SEGMENT TABLES. ^LENGTH IS DEFINED BY THE
\r
748 ANSWER TO A QUESTION.
\r
751 6.##^LOCATIONS SET BY ONCE-ONLY DIALOGUE.
\r
754 7.##^SYSTEM ERROR STOP CODE (147 RESTART.)
\r
757 8.##^COMMON SUBROUTINE RETURNS.
\r
760 9.##^COMMON BYTE POINTERS.
\r
763 10.##^SPECIAL ^^MACRO\\'S TO DEFINE THE ^^PI\\ ASSIGNMENT IF DEVICE IS
\r
764 PRESENT. ^THESE ^^MACRO\\'S CREATE A TWO-WORD-PER-ENTRY TABLE
\r
769 A.##^DEVICE DATA BLOCK ADDRESS.
\r
772 B.##^NUMBER OF DEVICES.
\r
775 C.##^PRIORITY ^INTERRUPT CHANNEL FOR DEVICE.
\r
778 D.##^INTERRUPT LOCATION FOR DEVICE.
\r
781 E.##^LENGTH OF DEVICE DATA BLOCK IF MULTIPLE DEVICE.
\r
785 11.##^ONCE-ONLY CODE TO LINK DEVICE DATA BLOCKS AND TO CREATE MULTIPLE
\r
786 COPIES FOR ALL MULTIPLE DEVICES, WITH THE EXCEPTION OF DISK.
\r
789 12.##^THE ^P^I CHANNEL SAVE AND RESTORE ROUTINES.
\r
792 13.##^A LIST OF ^^EXTERN\\'S TO SELECTIVELY LOAD ALL THE PROGRAMS THAT
\r
793 ARE REQUIRED, IF THE USER IS LOADING FROM A MONITOR LIBRARY FILE.
\r
796 14.##^DEVICE-DEPENDENT BIT DEFINITION AND ^^EXTERN\\'S.
\r
799 5.0##^^DESCRIPTION OF COMMOD.MAC\\
\r
801 ^WITH A 5-^SERIES DISK MONITOR, THE USER ALSO ASSEMBLES ^^CONFIG.MAC\\
\r
802 WITH ^^S.MAC\\, ^^COMMOD.MAC\\ AND ^^DATDMP.MAC\\.
\r
804 ^^COMMOD.MAC\\ SELECTIVELY ASSEMBLES THESE ITEMS REQUIRED FOR THE
\r
805 DEFINED CONFIGURATION. ^IT CONTAINS:
\r
809 1.##^THE ASSEMBLY INSTRUCTIONS.
\r
812 2.##^THE DEFAULT SYMBOLS THAT CAN BE OVERRIDDEN BY THE USER DURING
\r
813 THE ^^MONGEN\\ DIALOGUE.
\r
816 3.##^THE INSTRUCTIONS FOR WRITING A NEW CONTROLLER ROUTINE.
\r
819 4.##^THE SYMBOL NAMING CONVENTIONS
\r
823 A.##3-LETTER PREFIXES
\r
826 B.##3-LETTER SUFFIXES
\r
830 5.##^THE LIST OF UPPER AND LOWER LIMITS FOR VARIOUS DISK PARAMETERS.
\r
833 6.##^THE DATA STRUCTURE DESCRIPTION.
\r
836 7.##^THE CORE AND DISK BLOCK SYMBOL DEFINITIONS
\r
841 A. GENERALIZED CORE BLOCK
\r
842 B. ^ACCESS TABLE (FIRST HALF)
\r
844 D. ^DEVICE ^DATA ^BLOCK
\r
846 F. ^MONITOR JOB TABLES
\r
847 G. ^CONTROLLER DATA BLOCK
\r
850 J. ^PROJECT-^PROGRAMMER NUMBER BLOCK
\r
853 M. ^FILE STRUCTURE DATA BLOCK
\r
854 N. ^SYSTEM VARIABLES
\r
856 P. ^UNIT DATA BLOCK
\r
863 ^^APPENDIX A - SAMPLE DIALOGUE\\
\r
865 ^THE FOLLOWING IS A SAMPLE ^^MONGEN\\ DIALOGUE WITH REPRESENTATIVE
\r
866 QUESTIONS AND ANSWERS. ^THE OPTIONAL COMMENTS [ENCLOSED IN SQUARE
\r
867 BRACKETS] ARE INCLUDED FOR THE READER'S CONVENIENCE.
\r
870 .TAB STOPS 8,16,24,32,40,48
\r
875 TYPE "DEVICE:NAME.EXT<CR>" FOR WHERE TO PUT RESULTS OF THIS DIALOG
\r
876 CR ASSUMES "DSK:CONFIG.MAC"
\r
878 ANSWER THE FOLLOWING QUESTIONS WITH Y OR N OR A DECIMAL NUMBER
\r
879 SHORT DIALOG?[N = LONGER QUESTIONS]
\r
881 10/50 SYSTEM TO BE BUILT?[N = 10/40]
\r
883 NAME OF THIS SYSTEM (24 CHARS OR LESS)?
\r
885 WHAT IS THE SERIAL NUMBER OF YOUR ARITHMETIC PROCESSOR?
\r
887 NAME OF SYSTEM DEVICE?[DTA0 USUAL FOR 10/40 SYSTEM,
\r
888 DSK USUAL FOR 10/50 SYSTEM]
\r
890 LEVEL D SOFTWARE?[N = LEVEL C OR EARLIER]
\r
892 HOW MANY DF10 DATA CHANNELS FOR DISKS?
\r
895 FOR EACH CHANNEL ANSWER THE FOLLOWING QUESTIONS:
\r
896 HOW MANY RC10 (FIXED HEAD) CONTROLLERS DO YOU HAVE?
\r
897 FOR EACH CONTROLLER, HOW MANY UNITS (BURROUGHS DISK
\r
899 HOW MANY RP10 (MEMOREX DISK PACK) CONTROLLERS?
\r
900 FOR EACH CONTROLLER, HOW MANY UNITS (DRIVES)?
\r
901 HOW MANY RA10 (BRYANT DISK) CONTROLLERS?
\r
902 FOR EACH CONTROLLER, DUAL POSITIONER?]
\r
922 HOW MAY JOBS?[1 TO 128, ATTACHED AND DETACHED, COUNTING NULL JOB]
\r
924 MAX SIZE OF CORE (IN K) FOR ANY SINGLE USER?
\r
925 0 MEANS ALL OF CORE
\r
927 PDP-10 PROCESSOR?[N = PDP-6]
\r
929 2 RELOCATION REG. SOFTWARE?[Y = MUST HAVE KT10A,
\r
930 N = JUST 1 RELOC. REG.]
\r
932 HOW MANY MORE SEGMENTS THAN JOBS?[0 UNLESS YOU
\r
933 ANTICIPATE A LOT OF DORMANT SEGMENTS]
\r
935 LOAD EXEC DDT?[N = ONLY IF LOADER HAS RUN OUT OF CORE BEFORE]
\r
937 LOAD LOCAL SYMBOLS?[N = ONLY IF LOADER HAS RUN OUT OF ROOM BEFORE]
\r
939 COMMON.MAC ALREADY EDITED FOR YOUR TTY CONFIGURATION?[
\r
940 N = WILL ALLOW YOU TO DEFINE NOW]
\r
942 BOTH DC10 AND 680?[N WILL ASK FOR DC10,680 OR 630 ALONE]
\r
944 HOW MANY DC10B (OR 632) 8-LINE DATA GROUPS?[
\r
945 1=TTY0-7, 2=TTY0-17, ... , 8=TTY0-77]
\r
947 HOW MANY DC10E DATASET CONTROL GROUPS?
\r
949 HOW MANY (OCTAL) LINES ON YOUR 680(I), INCLUDING
\r
950 ITS CONSOLE TELETYPE?
\r
952 ANSWER THE FOLLOWING QUESTIONS ABOUT YOUR TELETYPE LINES:
\r
953 [TYPE OCTAL LINE NUMBERS, ONE PER LINE.
\r
954 TYPE EXTRA CR WHEN DONE.]
\r
956 DATA SET LINES?[PROJECT 1 CAN'T LOGIN, LOGIN RESETS
\r
957 LINE TO COMPUTER ECHOING AND NO HARDWARE TABS]
\r
975 LINES WITH HARDWARE TABS?[MONITOR SIMULATES REST WITH SPACES]
\r
991 REMOTE LINES?[PROJECT 1 CAN'T LOGIN,]
\r
1005 LOCAL COPY LINES? [ECHOING PROVIDED BY TERMINAL RATHER
\r
1006 THAN BY COMPUTER. OFTEN (INCORRECTLY) CALLED "HALF DUPLEX".]
\r
1008 HALF DUPLEX LINES?[TWX OR HALF DUPLEX WIRED SCANNED(DC10C)]
\r
1011 SLAVES? [NO COMMANDS MAY BE TYPED]
\r
1013 LINES WITH HARDWARE FORMFEED? [LEAVE OUT IF USERS WOULD RATHER
\r
1014 NOT GET FORMFEEDS UNTIL THEY DO TTY FORM COMMAND]
\r
1024 LINES WHICH RUN INITIA AT STARTUP?
\r
1031 WHAT IS THE CORRESPONDENCE BETWEEN THE DC10E LINES
\r
1032 AND THE DC10B LINES? TYPE "_#,_#" FOR EACH DATASET. FIRST _# IS
\r
1033 DC10E LINE, SECOND _# IS DC10B LINE.[_# IS AN OCTAL NUMBER.
\r
1034 TYPE ONE _#,_# PER LINE, EXTRA CR WHEN DONE.]
\r
1050 HOW MAY LINE PRINTERS?[0,1 OR 2]
\r
1052 MOVIE?[DYNAMIC MONITORY DUMP ON LPT]
\r
1056 CR10?[Y = CR10A TOO, N IF PDP-6 CARD READER]
\r
1062 HOW MANY DECTAPES?[0 TO 8]
\r
1064 TD10 DECTAPE CONTROL?[N = PDP-6 DECTAPE]
\r
1066 HOW MANY MAGTAPES?[0 TO 8]
\r
1068 TM-10A CONTROL?[N = WILL ASK TM-10B, THEN PDP-6 MAGTAPES]
\r
1070 HOW MANY PSEUDO-TTY'S?[0 TO 64, EACH CONCURRENT BATCH NEEDS ONE]
\r
1072 DO YOU WNAT CCL COMMANDS TO STAY IN CORE?[
\r
1075 HOW MANY WORDS?0 GIVES STD[AVERAGE 20 WORDS/JOB]
\r
1077 WHAT LIMIT PER JOB? 0 GIVES STD[40 WORDS]
\r
1079 DO YOU WANT TO LOCK JOBS IN CORE?[REQUIRED FOR REAL-TIME]
\r
1081 WHAT IS THE MINIMUM AMOUNT OF CORE (IN K) TO BE GUARANTEED TO JOBS
\r
1082 THAT ARE NOT LOCKED? [0 ASSUMES MAXIMUM]
\r
1084 HOW MANY REAL-TIME DEVICES? [TYPE THE MAXIMUM NUMBER OF REAL-
\r
1085 TIME DEVICES WHICH COULD BE PUT ON THE PI LEVELS SIMULTANEOUSLY]
\r
1087 HOW MANY HIGH PRIORITY QUEUES?[MAX 15]
\r
1089 TYPE "SYMBOL,VALUE" (VALUE IN DECIMAL)[FOR ANY SYMBOLS
\r
1090 TO BE DEFINED. NEXT QUESTION WILL ASK FOR OCTAL DEFINITION.
\r
1091 TYPE EXTRA CARRIAGE RETURN WHEN THROUGH.]
\r
1094 TYPE "SYMBOL,VALUE" (VALUE IN OCTAL)[FOR ANY SYMBOLS
\r
1095 TO BE DEFINED. TYPE EXTRA CARRIAGE RETURN WHEN THROUGH.]
\r
1097 TYPE "DEVICE-MNEMONIC,CHANNEL"FOR SPECIAL DEVICES[
\r
1098 WITH NEITHER CHANNEL SAVE ROUTINE NOR DEVICE DATA BLOCK.
\r
1099 "DEVICE" MUST BE 3 CHARACTERS OR LESS.
\r
1100 TYPE EXTRA CARRIAGE RETURN WHEN THROUGH.]
\r
1102 TYPE "DEVICE-MNEMONIC, CHANNEL, NO.-OF-DEVICES"[
\r
1103 FOR SPECIAL DEVICES WITH DEVICE DATA BLOCKS
\r
1104 "DEVICE" MUST BE 3 CHARS. OR LESS.
\r
1105 TYPE EXTRA CARRIAGE RETURN WHEN THROUGH.]
\r
1107 TYPE "DEVICE-MNEMONIC,CHANNEL,HIGHEST-AC-TO-SAVE[
\r
1108 FOR SPECIAL DEVICE WITH CHANNEL SAVE ROUTINES TO SAVE AC'S UP TO
\r
1109 "HIGHEST-AC-TO-SAVE". "DEVICE" MUST BE 3 CHARS. OR LESS.
\r
1110 TYPE EXTRA CARRIAGE RETURN WHEN THROUGH.]
\r
1112 DO YOU WANT REMOTE STATION SOFTWARE?
\r
1114 WHAT IS THE OCTAL STATION NUMBER OF THE PDP-10 CENTRAL SITE (1-77)?[
\r
1115 THE CENTRAL SITE IS THE LOCATION OF THE PDP-10]
\r
1117 HOW MANY PDP11 FRONT END'S DO YOU HAVE[
\r
1118 NEXT TWO QUESTIONS ASK FOR DS10'S AND DP01-CA'S, RESPECTIVELY]?
\r
1120 HOW MANY DS10'S ?[NEXT QUESTION WILL ASK FOR DP01-CA'S]
\r
1122 HOW MANY DP01-CA'S?
\r
1124 ANSWER THE FOLLOWING QUESTIONS FOR EACH REMOTE
\r
1125 SATELLITE STATION YOU INTEND TO SUPPORT [WHETHER PERMANENTLY
\r
1126 CONNECTED OR DIAL UP].
\r
1127 REPLY 0 STATION NUMBER TO END LOOP.....
\r
1128 TYPE OCTAL STATION NUMBER TO BE DEFINED:[
\r
1129 1 TO 77, NOT EQUAL CENTRAL NUMBER]
\r
1131 LINE PRINTER?[AT THIS STATION]
\r
1135 TYPE OCTAL STATION NUMBER TO BE DEFINED:[
\r
1136 1 TO 77, NOT EQUAL CENTRAL NUMBER]
\r
1138 LINE PRINTER?[AT THIS STATION]
\r
1142 TYPE OCTAL STATION NUMBER TO BE DEFINED:[
\r
1143 1 TO 77, NOT EQUAL CENTRAL NUMBER]
\r
1146 NEXT YOU MUST ASSEMBLE COMMON
\r
1149 THEN LOAD IT AND REST OF MONITOR WITH LOADER
\r
1150 AND FINALLY SAVE IT WITH MONITOR COMMAND SAVE
\r
1152 TO ASSEMBLE, TYPE:
\r
1154 DSK:COMMON,LPT:__DSK:S,CONFIG,COMMON
\r
1155 DSK:COMMOD,LPT:__DSK:S,CONFIG,COMMOD
\r
1156 TO LOAD NEW MONITOR, TYPE:
\r
1159 DSK:COMMON,COMMOD,DSK:TOPS10/L
\r
1161 TO SAVE MONITOR, TYPE:
\r
1164 END OF CONFIGURATION DEFINITION
\r
1177 ^^APPENDIX B - DECIMAL DEFAULT VALUES\\
\r
1180 ^THE FOLLOWING LIST IS A DESCRIPTION OF THE STANDARD SYMBOLS AND
\r
1181 DEFAULT DECIMAL VALUES, ASSUMED BY THE ^^MONGEN\\ PROGRAM.
\r
1187 ^POWER FREQUENCY IN ^HERTZ (CYCLES PER SECOND). ^INSTALLATIONS WITH
\r
1188 A POWER FREQUENCY OF ^^50H\\Z SHOULD CHANGE THE SYMBOL FOR CORRECT
\r
1189 ACCOUNTING AND TIME OF DAY.
\r
1194 ^NO. OF TIMES TO TRY ON ^^DEC\\TAPE ERRORS.
\r
1199 ^SIZE OF MAGTAPE RECORDS IN 36-BIT WORDS. ^THE USER CAN
\r
1200 OVERRIDE THIS VALUE BY THE .^^SET BLOCK MTA\\N: SIZE COMMAND.
\r
1201 ^PROGRAMS CAN OVERRIDE THIS PARAMETER BY BUILDING SPECIAL BUFFERS.
\r
1207 ^SIZE OF ^^LPT\\ BUFFER+2. ^ALLOWS A FULL LINE TO BE
\r
1208 TYPED ON A 132 CHARACTER LINE PRINTER IN ONE BUFFER.
\r
1209 ^THIS CONSTANT SHOULD BE CHANGED TO 26 WITH A 120 CHARACTER LINE
\r
1215 ^NUMBER OF NANOSECONDS PER MEMORY CYCLE. ^THIS SYMBOL IS USED TO
\r
1216 COMPUTE THE AMOUNT OF TIME SPENT CORE SHUFFLING AND IS PRINTED BY THE
\r
1217 ^^SYSTAT\\ COMMAND. ^FOR ^^MB\\10 MEMORIES, THE CONSTANT SHOULD BE CHANGED
\r
1221 ^^MINCOR,JOBN\\*90 [^^DISK SYSTEMS\\]
\r
1223 ^THE MONITOR RESERVES A TABLE OF AT LEAST ^^MINCOR\\ WORDS OR POSSIBLY
\r
1224 UP TO THE NEXT 1K BOUNDARY FOR ALLOCATING DISK DEVICE DATA BLOCKS
\r
1225 AND EXTENDED PUSH DOWN LISTS.^^MINCOR\\ IS NORMALLY ^^JOBN\\*90 WORDS ALLOWING 2.5 OPEN DISK FILES
\r
1226 PER JOB. ^IF THIS VALUE IS TOO SMALL A LARGER VALUE MAY BE SUPPLIED.
\r
1227 ^THE TOTAL SIZE OF THE MONITOR IS PRINTED AFTER THIS SPACE IS
\r
1228 RESERVED IN THE LONG ONCE ONLY DIALOGUE.
\r
1231 ^^MINCOR,JOB*40 [NON-DISK SYSTEMS\\]
\r
1233 ^THE MONITOR RESERVES SPACE FOR AT LEAST ^^MINCOR\\ WORDS OR POSSIBLY
\r
1234 UP TO THE NEXT 1K BOUNDARY FOR ALLOCATING EXTENDED PUSH DOWN LIST
\r
1235 SPACE. ^THIS PARAMETER SHOULD BE SET SMALLER IF CORE SPACE IS A PROBLEM,
\r
1236 SINCE THE EXEC PUSHDOWN LIST IS ALLOCATED DYNAMICALLY ON OVERFLOW,
\r
1237 AND NOT ALL JOBS HAVE OVERFLOW AT THE SAME TIME.
\r
1242 ^MINIMUM AMOUNT OF VIRTUAL CORE REQUIRED FOR A USER TO BE LOGGED IN.
\r
1243 ^THIS VALUE MUST BE AT LEAST AS LARGE AS THE ^^LOGIN CUSP\\, CURRENTLY
\r
1244 3^K. ^IF THE AMOUNT OF CORE IS INSUFFICIENT THE USER RECEIVES
\r
1245 THE USUAL CORE UNAVAILABLE MESSAGE, WHICH INCLUDES THE AMOUNT OF
\r
1246 VIRTUAL CORE REMAINING.
\r
1252 ^THE MAXIMUM NUMBER OF DISK FILE STRUCTURES THAT CAN BE ON LINE
\r
1253 SIMULTANEOUSLY. ^DECREASING THIS VALUE SAVES ONE WORD PER VALUE.
\r
1258 ^THE MAXIMUM LENGTH IN WORDS OF A DISK CHANNEL COMMAND LIST. ^ALTERING THIS
\r
1259 VALUE AFFECTS EFFICIENCY AND SPACE.
\r
1264 ^THE MAXIMUM NUMBER OF DISK UNITS THAT MAY BE USED FOR SWAPPING.
\r
1265 (1 WORD PER UNIT).
\r
1270 ^THE HIGHEST CLASS NUMBER FOR SWAPPING.
\r
1275 ^NUMBER OF TIMES TO TRY ON DISK ERRORS BEFORE RECALIBRATING, INCLUDING
\r
1281 ^NUMBER OF TIMES TO TRY ON SEARCH ERRORS BEFORE RECALIBRATING, INCLUDING
\r
1287 ^NUMBER OF TIMES TO RECALIBRATE AND TRY ON "^^DSKTRY\\" DISK ERRORS
\r
1288 OR ON "^^SERTRY\\" SEARCH ERRORS, INCLUDING THE INITIAL TRY. ^TOTAL
\r
1289 NUMBER OF DISK TRIES WITH RECALIBRATION, IS ^^DSKTRY\\*^^RCLTRY\\
\r
1290 (10*10=100). ^TOTAL NUMBER OF SEARCH TRIES WITH RECALIBRATION IS
\r
1291 ^^SERTRY\\*^^RCLTRY\\(3*10=30).
\r
1296 ^STANDARD FAIRNESS COUNT FOR POSITIONING. ^THE MONITOR CHOOSES
\r
1297 THE NEAREST REQUEST FOR POSITIONING (^^CHVFP\\ TIMES -1) BEFORE TAKING
\r
1298 THE LONGEST WAITING REQUEST.
\r
1301 ^^CH\\0^^IFP\\, ^^CHVIFP\\ ... ^^CH7IFP,CHVIFP\\
\r
1303 ^FAIRNESS COUNT FOR POSITIONING ON CHANNEL 0....7.
\r
1308 ^STANDARD FAIRNESS COUNT FOR TRANSFERS. ^THE MONITOR CHOOSES THE
\r
1309 SHORTEST LATENCY FOR A TRANSFER (^^CHVIFT\\ TIMES -1) BEFORE TAKING
\r
1310 THE LONGEST WAITING REQUEST.
\r
1313 ^^CH0IFT,CHVIFT ... CH7IFT,CHVIFT\\
\r
1315 ^FAIRNESS COUNT FOR TRANSFERS ON CHANNEL 0,...7.
\r
1320 ^NUMBER OF IN-CORE RETRIEVAL POINTERS PER DISK ^^DDB\\.
\r
1325 ^ONE-FOURTH THE LENGTH OF THE MAXIMUM EXEC PUSH DOWN LIST WHEN
\r
1331 ^NUMBER OF 4 WORD BLOCKS ALLOCATED PER JOB IN A COMMON POOL OF MONITOR
\r
1332 FREE CORE. ^THE VALUE OF ^^FIL4WD\\ SHOULD BE INCREASED IF ^^ENTER#UUO\\
\r
1333 ERROR CODE 16 (.^^ERNET\\) IS RECEIVED REGULARLY. ^TO ASSIGN THIS
\r
1334 SPACE THE ONCE ONLY CODE MULTIPLIES THIS FACTOR BY THE NUMBER OF
\r
1335 JOBS. ^THESE BLOCKS ARE USED BY THE ^^LEVEL D DISK\\ SERVICE FOR ACTIVE,
\r
1336 DORMANT, AND FREE ^^ACC, AKB, NMB, PPB\\, AND ^^UFB\\ BLOCKS. ^THIS
\r
1337 POOL IS PERMANENTLY RESERVED FOR THESE BLOCKS AND IS NOT USED FOR ANY
\r
1338 OTHER PURPOSE. ^ANOTHER POOL IS USED FOR VARIABLE LENGTH CORE BLOCKS
\r
1339 SUCH AS DISK DEVICE DATA BLOCKS, AND EXTENDED EXEC PUSH DOWN LISTS.
\r
1340 ^THE SYSTEM SETS THE MINIMUM NUMBER OF 4 WORD CORE BLOCKS AT (10 TIMES 5 OR)
\r
1341 50 WITH 5 OR FEWER JOBS.
\r
1346 ^THE RECIPROCAL FACTOR OF THE TOTAL DISK SIZE. ^THIS AMOUNT
\r
1347 OF DISK SPACE IS SUBTRACTED FROM THE NUMBER OF FREE BLOCKS WHEN THE
\r
1348 MONITOR IS STARTED UP. ^THIS AREA IS NOT
\r
1349 AVAILABLE FOR USERS' DATA. ^IT IS A SAFETY FACTOR THAT ENSURES THERE
\r
1350 IS ROOM TO WRITE THE SECOND ^^RIB\\, ETC. ^THE STANDARD RESERVED FOR
\r
1351 THIS PURPOSE IS ONE-FIVE HUNDREDTH OF THE DISK SPACE.
\r
1357 ^STANDARD LOGICAL BLOCK NUMBERS ON EACH UNIT THAT CONTAIN THE HOM BLOCK.
\r
1362 ^NUMBER OF BLOCKS ALLOCATED TO THE ^^MFD\\ BY THE REFRESHER IN EACH FILE
\r
1363 STRUCTURE. ^THE ^^MFD\\ CAN BE LONGER THAN THIS BUT THERE IS A SPEED
\r
1364 ADVANTAGE TO CONSECUTIVE BLOCKS. ^INCREASE THIS VALUE IF THE ^^MFD\\
\r
1365 IS NORMALLY LONGER THAN 8 BLOCKS.
\r
1370 ^NUMBER OF 128-WORD MONITOR BUFFERS USED FOR READING AND WRITING NON-USER
\r
1371 DATA. (^MUST BE AT LEAST 2.)
\r
1374 ^^UNIQ1,1 UNIQ2,1.......UNIQ6,1\\
\r
1376 ^REPRESENT PRIORITY INTERRUPT CHANNELS RESERVED FOR THE EXCLUSIVE USE
\r
1377 OF A SPECIAL DEVICE. ^IF PRIORITY INTERRUPT CHANNELS ARE TO BE
\r
1378 RESERVED, SET THE VALUE OF ^^UNIQ\\N TO 1, WHERE N IS THE CHANNEL
\r
1379 NUMBER. ^FOR EXAMPLE, IF A REAL TIME DEVICE REQUIRES EXTREMELY FAST
\r
1380 RESPONSE TIME, IT IS NECESSARY TO SET ^^BLKI\\/^^BLKO\\ POINTER
\r
1381 IN THE CHANNEL LOCATION. (^CHANNEL 7 CANNOT BE RESERVED, IT IS
\r
1382 ALWAYS USED FOR THE CLOCK.
\r
1385 ^^MINMAX\\,10240 [10^K]
\r
1387 ^SMALLEST VALUE OF ^^CORMAX\\ ALLOWED TO BE SET AFTER SYSTEM STARTS
\r
1392 ^^APPENDIX C - OCTAL DEFAULT VALUES\\
\r
1395 ^THE FOLLOWING LIST IS A DESCRIPTION OF THE STANDARD SYMBOLS AND
\r
1396 DEFAULT OCTAL VALUES ASSUMED BY THE ^^MONGEN\\ PROGRAM.
\r
1402 ^STANDARD MAGTAPE DENSITY IF THE USER PROGRAM DOES NOT OVERRIDE WITH
\r
1403 NON-ZERO VALUES IN ^^INIT, OPEN\\, OR ^^SETSTS UUO\\.
\r
1408 1##^^BINARY (ODD) PARITY + 200 BPI\\
\r
1410 2##^^BINARY (ODD) PARITY + 556 BPI\\
\r
1412 3##^^BINARY (ODD) PARITY + 800 BPI\\
\r
1415 5##^^BCD (EVEN) PARITY + 200 BPI\\
\r
1417 6##^^BCD (EVEN) PARITY + 556 BPI\\
\r
1419 7##^^BCD (EVEN) PARITY + 800 BPI\\
\r
1426 ^IF ^^INDPPN\\=0, THEN EACH PROGRAMMER NUMBER REFERS TO THE SAME PERSON IN
\r
1429 ^IF ^^INDPPN\\=777777, THEN PROGRAMMER NUMBERS MAY BE
\r
1430 ASSIGNED INDEPENDENTLY WITHIN EACH PROJECT. ^THIS AFFECTS ONLY THE
\r
1431 DISK FILE ACCESS PROTECTION MECHANISM.
\r
1436 ^STANDARD FILE PROTECTION.
\r
1441 ^STANDARD ^^UFD\\ PROTECTION.
\r
1446 ^NON PROTECTED FILES IN ^^SYS\\ (^^HOME.SYS, SAT.SYS\\). ^SET BY
\r
1452 ^PRIVILEGED FILE PROTECTION IN ^^SYS\\ (^^CRASH.SAV, SNAP.SYS, RECOV.SYS,
\r
1453 BADBLK.SYS, SWAP.SYS\\). ^USED BY REFRESHER.
\r
1458 ^^MFD\\ PROTECTION. ^ALL CAN READ, LOOKUP, BUT NOT CREATE.
\r
1459 ^SET BY REFRESHER.
\r
1464 ^^SYS UFD\\ PROTECTION [PROJECT, PROGRAMMER=1,4] (^PROJECT 1 CAN ^^READ,
\r
1465 CREATE, LOOKUP\\; OTHERS CAN ^^READ, LOOKUP\\ ONLY.) ^SET BY REFRESHER.
\r
git://git.sky-visions.com / retro-software/dec/tops10/v4.5.git / blob