API tools faq
paste
Advertisement
Guest User

Untitled

a guest
May 14th, 2013
29
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 32.88 KB | None | 0 0
raw download clone embed print report
  1. .r mongen
  2.  
  3. Write MONGEN.MIC (YES,NO) : yes
  4.  
  5. % DSK:MONGEN.MIC will not be written
  6. % File DSK:MONGEN.MIC already exists
  7. MONGEN for 704 monitors
  8.  
  9. MONGEN will generate any known TOPS-10 configuration. For information
  10. about which configurations are supported, please refer to the SPD.
  11.  
  12. /HELP (PROMPT,SHORT,LONG) ]: long
  13. Which GEN (SYS,F) [
  14. Type SYS to define hardware and software configuration, or type F to define
  15. software features. To EXIT, type CTRL/Z.]: sys
  16. Output(DSK:SYSCNF.MAC):
  17. DECsystem10 (KL,KS) [
  18. The KL is a system with KL10 CPUs. The KS is a system with a KS10 CPU.]: kl
  19. CPUs (1,1-6) [
  20. Respond with the total number of CPUs in the system you are configuring.
  21. The maximum number of CPUs supported in an SMP configuration is defined in
  22. the SPD.]: 1
  23. System name [
  24. Type a system name of 24 characters or less. The system name is displayed
  25. in the banner line that is printed when the INITIA monitor command is
  26. issued.]: MARLEY TOPS-10
  27. CPU0 serial number (1-10000) [
  28. Respond with the serial number of the CPU, in the range 1 to 10000. If your
  29. installation has more than one processor, this question is asked for each
  30. CPU. Each serial number must be unique.]: 1022
  31. Exclude monitor overhead from user run time (YES,NO) [
  32. Overhead is CPU time spent clock queue processing, command decoding,
  33. swapping, and scheduling. User run time always includes UUO execution and,
  34. unless EBOX/MBOX runtime accounting is selected (KL10 systems only),
  35. includes IO interrupt service time.
  36. If you exclude monitor overhead from user runtime, users recieve a more
  37. accurate accounting of their processor usage because user runtime is
  38. calculated independently of any monitor overhead. However, installations
  39. that charge their customers for processor usage should be aware that the
  40. exclusion of monitor overhead decreases the user runtime totals by 10 to
  41. 20 percent.
  42. If you include monitor overhead with user runtime, apportioned monitor
  43. overhead is included in each user's runtime. Regardless of how you
  44. respond to this question, monitor overhead is calculated as a separate
  45. statistic that can be used in determining the amount of CPU time spent for
  46. overhead.]:
  47. EBOX/MBOX runtime accounting (YES,NO) [
  48. If EBOX/MBOX runtime accounting is selected, user runtime is computed using
  49. the KL10 internal accounting clocks.
  50. With EBOX/MBOX accounting, meters are turned off at the beginning of
  51. the overhead period and turned on again at the end. For the most accurate
  52. user runtime calculation, answer YES to this question and exclude priority
  53. interrupt (PI) time from the runtime calculation by answering YES to the
  54. next question.]:
  55. Exclude PI time from user runtime (YES,NO) [
  56. If you exclude PI time from user runtime, the EBOX and MBOX accounting
  57. clocks are stopped whenever a priority interrupt is in progress, and users
  58. will not be charged for CPU time used during interrupts.]:
  59. Account verification (YES,NO) [
  60. LOGIN and the batch system will verify that the user has specified a valid
  61. account.
  62. If you answer YES, when accounts are associated with their PPNs and
  63. when ACTDAE is running, users can log in only if they specify a valid
  64. account string. If you answer NO, no verification test is made.]: no
  65. MOS memory (YES,NO) [
  66. Include support for the user-mode MOS memory diagnostic TGHA. TGHA
  67. collects statistics on single bit memory errors and substitutes the spare
  68. bit when a single bit error is determined to be hard.
  69. If you answer YES, the module MOSSER will be loaded with the monitor.
  70. If you answer NO, MOSSER will not be loaded.]:
  71.  
  72. Autoconfigured device options:
  73. Include SCA (NO,YES,PROMPT)[
  74. SCA (Systems Communications Architecture) provides the ability to
  75. communicate with devices on a CI bus. SCASER and KLPSER are the driver
  76. modules.
  77. Respond with one of the following:
  78. NO Exclude driver
  79. YES Include driver
  80. PROMPT Include driver and prompt for parameters]:
  81. Include Ethernet service (NO,YES,PROMPT)[
  82. Load monitor modules needed to communicate using Ethernet. These modules
  83. include ETHSER and ETHUUO, plus the hardware driver specific to the type of
  84. DECsystem-10 being built.
  85. Respond with one of the following:
  86. NO Exclude driver
  87. YES Include driver
  88. PROMPT Include driver and prompt for parameters]: yes
  89. Include SA10 device support (NO,YES,PROMPT)[
  90. SA10 support provides the ability to communicate with IBM channel devices
  91. using a Systems Concept SA10 channel interface. SAXSER is the driver
  92. module.
  93. Respond with one of the following:
  94. NO Exclude driver
  95. YES Include driver
  96. PROMPT Include driver and prompt for parameters]:
  97. Include RP01/2/3 disks (NO,YES,PROMPT)[
  98. RP01, RP02, and RP03 disks are available through the use of an RP10
  99. interface. DPXKON is the driver module for these disks.
  100. Respond with one of the following:
  101. NO Exclude driver
  102. YES Include driver
  103. PROMPT Include driver and prompt for parameters]:
  104. Include Swapping drums (NO,YES,PROMPT)[
  105. Burroughs disks and Bryant drums are available through the use of an RC10
  106. interface. FHXKON is the driver module for these disks.
  107. Respond with one of the following:
  108. NO Exclude driver
  109. YES Include driver
  110. PROMPT Include driver and prompt for parameters]:
  111. Include RS04/5 Massbus disks (NO,YES,PROMPT)[
  112. RS04 and RS05 disks are available through the use of an RH10/DF10C
  113. interface. FSXKON is the driver module for these disks.
  114. Respond with one of the following:
  115. NO Exclude driver
  116. YES Include driver
  117. PROMPT Include driver and prompt for parameters]:
  118. Prompt for RP0x/RM0x Massbus disks (NO,YES)[
  119. RP0x and RM0x disks are available through the use of Massbus hardware.
  120. RPXKON is the driver module for these disks.
  121. Respond with one of the following:
  122. NO Do not prompt
  123. YES Prompt for parameters]: yes
  124. Device code (CR,0-774) [
  125. Press RETURN to accept the standard device code definitions.]:
  126. Massbus device (0,0-7) [
  127. Type the Massbus device number for the RPX controller.]:
  128. Drive, slave, or unit: [
  129. Type a decimal drive, slave, or unit number, "ALL" for all units, or "NONE"
  130. if defining a controller parameter. An answer to this question must be
  131. supplied.]all
  132. Data: [
  133. You may provide device-specific information. The response to this may
  134. contain a symbolic expression. If you press RETURN, this indicates that
  135. there is no device-specific data other than the previously specified device
  136. code information.]
  137. Do you want to specify more data (NO,YES):
  138. Include DX20/RP20 disks (NO,YES,PROMPT)[
  139. RP20 IBM channel disks are available through the use of a DX20 channel
  140. interface with an RP20CT controller. RNXKON is the driver module for these
  141. disks.
  142. Respond with one of the following:
  143. NO Exclude driver
  144. YES Include driver
  145. PROMPT Include driver and prompt for parameters]:
  146. Include TM02/TM03 magtapes (NO,YES,PROMPT)[
  147. TU45 and TU77 magtape units are available through the use of TM02 or TM03
  148. controllers. TM2KON is the driver module for these magtapes.
  149. Respond with one of the following:
  150. NO Exclude driver
  151. YES Include driver
  152. PROMPT Include driver and prompt for parameters]:
  153. Include DX10/TX01/TX02 tapes (NO,YES,PROMPT)[
  154. TU70, TU71, TU72, and TU73 IBM channel magtapes are available through the
  155. use of a DX10 channel interface and a TX01 or a TX02 controller. TX1KON is
  156. the driver module for these magtapes.
  157. Respond with one of the following:
  158. NO Exclude driver
  159. YES Include driver
  160. PROMPT Include driver and prompt for parameters]:
  161. Include DX20/TX02 tapes (NO,YES,PROMPT)[
  162. TU70, TU71, TU72, and TU73 IBM channel magtapes are available through the
  163. use of a DX20 channel interface and a TX02 controller. TD2KON is the
  164. driver module for these magtapes.
  165. Respond with one of the following:
  166. NO Exclude driver
  167. YES Include driver
  168. PROMPT Include driver and prompt for parameters]:
  169. Include TM78/TU78/TU79 magtapes (NO,YES,PROMPT)[
  170. TU78 and TU79 magtapes are available through the use of a TM78 controller.
  171. T78KON is the driver module for these magtapes.
  172. Respond with one of the following:
  173. NO Exclude driver
  174. YES Include driver
  175. PROMPT Include driver and prompt for parameters]:
  176. Include TM10B magtapes (NO,YES,PROMPT)[
  177. TU40 and TU41 magtapes are available through the use of a TM10B controller.
  178. TMXKON is the driver module for these magtapes.
  179. Respond with one of the following:
  180. NO Exclude driver
  181. YES Include driver
  182. PROMPT Include driver and prompt for parameters]:
  183. Include TC10C magtapes (NO,YES,PROMPT)[
  184. TU43 magtapes are available through the use of a TC10C controller. TCXKON
  185. is the driver module for these magtapes.
  186. Respond with one of the following:
  187. NO Exclude driver
  188. YES Include driver
  189. PROMPT Include driver and prompt for parameters]:
  190. Include BA10/LP100 printers (NO,YES,PROMPT)[
  191. This option provides support for I/O bus line printers.
  192. Respond with one of the following:
  193. NO Exclude driver
  194. YES Include driver
  195. PROMPT Include driver and prompt for parameters]: yes
  196. Include CFE/LP20 printers (NO,YES,PROMPT)[
  197. This option provides support for line printers on the RSX-20F front-end.
  198. Respond with one of the following:
  199. NO Exclude driver
  200. YES Include driver
  201. PROMPT Include driver and prompt for parameters]: yes
  202. Include XY10 plotters (NO,YES,PROMPT)[
  203. This option provides support for I/O bus plotters.
  204. Respond with one of the following:
  205. NO Exclude driver
  206. YES Include driver
  207. PROMPT Include driver and prompt for parameters]:
  208. Include CR10 card readers (NO,YES,PROMPT)[
  209. This option provides support for I/O bus card readers.
  210. Respond with one of the following:
  211. NO Exclude driver
  212. YES Include driver
  213. PROMPT Include driver and prompt for parameters]:
  214. Include CFE/CD20 card readers (NO,YES,PROMPT)[
  215. This option provides support for card readers on the RSX-20F front-end.
  216. Respond with one of the following:
  217. NO Exclude driver
  218. YES Include driver
  219. PROMPT Include driver and prompt for parameters]:
  220. Include CP10/CP10D card punches (NO,YES,PROMPT)[
  221. This option provides support for card punches.
  222. Respond with one of the following:
  223. NO Exclude driver
  224. YES Include driver
  225. PROMPT Include driver and prompt for parameters]:
  226. Include PC04 paper tape punches (NO,YES,PROMPT)[
  227. This option provides support for paper tape punches.
  228. Respond with one of the following:
  229. NO Exclude driver
  230. YES Include driver
  231. PROMPT Include driver and prompt for parameters]:
  232. Include PC04 paper tape readers (NO,YES,PROMPT)[
  233. This option provides support for paper tape readers.
  234. Respond with one of the following:
  235. NO Exclude driver
  236. YES Include driver
  237. PROMPT Include driver and prompt for parameters]:
  238.  
  239. Types of DTE service to load:
  240. Load ANF-10 DTE service (YES,NO) [
  241. Do you want to load the driver to support DTE based ANF-10 front ends?]: no
  242. Load IBMCOMM DTE service (YES,NO) [
  243. Do you want to load the driver to support DTE based IBM communications
  244. front ends?]: no
  245. Load DECnet DTE service (YES,NO) [
  246. Do you want to load the driver to support DTE based DECnet-36 front
  247. ends?]: no
  248.  
  249. Local terminal configuration:
  250. Configure old terminal scanners (NO,YES) [
  251. If you answer YES, you will be prompted to provide information about DC10s,
  252. DC68s, and DC76s.]:
  253. How many RSX-20F TTYs on CPU0 (0,0-128) [
  254. Respond with the number of terminals on the RSX-20F console front-end for
  255. this CPU. Include only timesharing (DH11) lines, not CTY or KLINIK.]: 1
  256.  
  257. OPR octal line number (CTY,0-4) [
  258. Respond with the octal number of the terminal you want to designate as
  259. device OPR, the operator-privileged terminal. This is normally the
  260. terminal that will be running OPR, the operator service program, to control
  261. the system utility programs such as the device spoolers and the mount
  262. request processor. The default is the console terminal (CTY).]: cty
  263. Data set lines [
  264. Class of terminal for LOGIN, LOGIN resets line to computer echoing and no
  265. hardware tabs.
  266. This question accepts a list of octal terminal line numbers. The
  267. terminal line can be indicated by its number (n), a range of terminal lines
  268. can be indicated by the lowest and highest numbers in the range separated
  269. by a hyphen (m-n), and the CTY is always indicated by CTY. Type each
  270. designator on a separate line and end the list with an extra carriage
  271. return.]
  272.  
  273.  
  274. Number of Jobs (1-511) [
  275. Respond with the maximum number of jobs, attached and detached, not
  276. counting the null job. Specify only the maximum number of jobs needed.
  277. Monitor size increases proportionally to the maximum number of jobs.]: 511
  278. Maximum pages of core for each job (0,0-16384) [
  279. Answer this question with the maximum amount of physical memory that any
  280. one job may use. This value is specified in number of 512-word pages. A
  281. response of 0 indicates all of core, or the maximum number of pages
  282. possible. The value you specify here can be overridden by the SET CORMAX
  283. monitor command.]:
  284. Total amount of system core in K (512-4096) [
  285. ONCE-only reports if there is less core at startup. Answer this question
  286. with the total amount of physical memory that the system has. At monitor
  287. startup time, ONCE prints a message if the actual amount of memory on line
  288. is less than your response to this question.]: 4096
  289. Number of real-time devices (0,0-77) [
  290. Answer this question with the maximum number of real-time devices that can
  291. be put on PI channels simultaneously.]:
  292. Allow jobs to be locked in core (YES,NO) [
  293. If you answer NO, no users will be allowed to lock their jobs in core
  294. memory.
  295. The ANF-10 network programs DTELDR and NETLDR require the ability to
  296. lock a job in memory. Therefore, if you intend to use these programs, you
  297. must answer this question YES. This question is always asked for KS
  298. systems, and is asked for KL systems only if no real-time devices are
  299. employed.]:
  300. Guaranteed number of pages for unlocked jobs (0,0-16384) [
  301. Answer this question with the number of pages of memory guaranteed to all
  302. jobs that are not locked in core. The default, 0, indicates that all of
  303. memory is available to unlocked jobs.
  304. If your answer is 0, no jobs are allowed to be locked, as a safeguard
  305. against locked jobs usurping all of the system's memory. The value
  306. specified in your answer to this question can be overridden by the SET
  307. CORMIN monitor command.]:
  308. Number of pages reserved for locking jobs in Exec Virtual Memory (10,0-?) [
  309. The default, 10, is needed for DTELDR. Extra pages are required for
  310. running performance analysis tools such as SNOOPY and DNSNUP or for any
  311. real-time applications using indirect CONSO masks or fast mode. Reserving
  312. pages for EVM reduces the amount of available system free core by an
  313. equivalent amount.]:
  314. Number of high priority interrupt queues (0,0-15): 5
  315. Meter (NO,YES) [
  316. Do you want to include performance analysis metering with the METER UUO?
  317. This option has officially been superseded by the PERF. UUO.]:
  318. KASER (NO,YES) [
  319. Do you want to include support for simulation of KA10 long floating point
  320. instructions?]:
  321. MPXSER (YES,NO) [
  322. Do you want to include support for device MPX? MPX allows more than one
  323. device to be associated with a given I/O channel. This feature is required
  324. for DTELDR. If you answer YES, the multiplexed-channel software MPX will
  325. be loaded.]:
  326. PSISER (YES,NO) [
  327. Do you want to load the Programmed Software Interrupt SERvice software?
  328. PSISER supports the PISYS. UUO, which allows users to specify the
  329. conditions for which an interrupt is to occur. PSISER is required for the
  330. operation of GALAXY-10.]:
  331. IPCF (YES,NO) [
  332. Do you want to load the Inter-Process Communication Facility software?
  333. IPCF allows jobs and/or system processes to communicate with each other.
  334. IPCF is required for the operation of MCS-10 and GALAXY-10.]:
  335. ENQ/DEQ (YES,NO) [
  336. Do you want to load the ENQ/DEQ software? ENQ/DEQ provides sychronization
  337. functions which allow simultaneous file updates by multiple co-operating
  338. processes.]:
  339. Disk sets (ALL) [
  340. Answer this question with the list of disk sets to be mounted by this
  341. system. If the list is empty, ALL disk sets will be mountable. Disk set
  342. numbers range from 1 through 36. List entries in the form:
  343.  
  344. 3,9-12,14,...
  345.  
  346. ]:
  347. Configure non-autoconfigured hardware (NO,YES) [
  348. Do you want to include unsupported hardware in your configuration?]:
  349. Number of PTYs (20,1-504) [
  350. A PTY is a pseudo-terminal. OPSER subjobs and batch jobs use PTYs for I/O.
  351. Each operator service program and batch stream needs at least one PTY. You
  352. must include at least one PTY for your monitor. Respond with the number of
  353. pseudo-terminals that your monitor must support.]: 100
  354.  
  355. Network software (YES,NO) [
  356. Do you want to include support for communications with other Digital
  357. operating systems?]: yes
  358. Node name [
  359. The name may one to six characters in length.]: marley
  360. Number of remote TTYs (404,0-404) [
  361. Respond with the maximum number of terminals from remote nodes to be
  362. handled at any one time.]: 404
  363.  
  364. ANF-10 software (YES,NO) [
  365. Answer YES if you want to load the monitor modules needed to communicate
  366. with ANF-10 hosts and remote stations.]: no
  367.  
  368. DECnet software (YES,NO) [
  369. Answer YES if you want to load the monitor modules needed to communicate
  370. with other DECnet nodes.]: yes
  371. Node name (MARLEY) [
  372. Provide a node name, independent of that used as the system-wide node name.
  373. The name can be one to six characters in length. DECnet-10, Version 4
  374. requires that the first character of the node name be an alphabetic
  375. character. The same node name will be used for both ANF-10 and DECnet-10
  376. communications.]:
  377. Area number of central site (1,1-63) [
  378. Provide a decimal area number for multi-area DECnet network configurations.]: 9
  379. Node number of central site (1,1-1023) [
  380. Provide a unique decimal number to identify this system to other nodes in
  381. the DECnet network.]: 10
  382. Router type (ROUTING,NONROUTING) [
  383. Specify router type. ROUTING nodes can have multiple circuits and perform
  384. DECnet routing. NONROUTING nodes have only an ethernet circuit and perform
  385. no DECnet routing.
  386. If you have a KL and want to communicate with a Multifunctions
  387. Communications Base (MCB), or if you have a KS, answer this question with
  388. ROUTING.]: nonr
  389. Transmit password (DECNET20) [
  390. The transmit password is used when initializing a point-to-point KDP, DTE,
  391. or DMR link. You may provide a password of 64 characters or less, or press
  392. RETURN to accept the default password.]:
  393. Remote terminals (YES,NO) [
  394. Answer YES to include code that allows incoming jobs using DECnet
  395. connections. The module loaded will be NRTSER.]: yes
  396.  
  397. LAT software (YES,NO) [
  398. Answer YES if you want to communicate with Local Area Terminal
  399. concentrators using Ethernet. The module loaded will be LATSER.]: yes
  400. Node name (MARLEY) [
  401. Provide a node name, independent of that used as the system-wide node name.
  402. The name can be one to six characters in length. DECnet-10, Version 4
  403. requires that the first character of the node name be an alphabetic
  404. character. The same node name will be used for both ANF-10 and DECnet-10
  405. communications.]:
  406. Number of circuits (20,1-100) [
  407. Provide the maximum number of simultaneous LAT circuits required by your
  408. system. One is required for each active LAT server.]:
  409. Service groups [
  410. Provide the list of LAT service groups to be enabled by default at system
  411. start-up time. If the list is empty, no service groups will be enabled.
  412. List entries in the form:
  413.  
  414. 3,4-7,9,12-14,...
  415.  
  416. LAT group numbers must be listed in ascending order, may include a range of
  417. numbers, and each entry must be separated from the next with a comma. The
  418. range of valid service group numbers is 0 through 255.]:
  419.  
  420. Decimal "symbol,value" [
  421. For any decimal symbols to be defined, type one "symbol,value" pair per
  422. line and terminate the list with an extra carriage return. The symbols and
  423. values that you enter here are those that deviate from the defaults defined
  424. in the distributed common modules (COMMON, COMDEV, and COMMOD). The radix
  425. is set automatically for each symbol, in accordance with the radix
  426. specified in the question. (In this case, decimal. You will be given the
  427. opportunity to change the values for symbols with octal and SIXBIT values
  428. in the questions that follow.) For example, to increase the length of a
  429. memory cycle from 1,000 nanoseconds to 1,760 nanoseconds,
  430. type:
  431.  
  432. NSPMEM,1760
  433.  
  434. followed by a carriage return. Unless you specify otherwise, the symbols
  435. will be defined with the default values. If the default values are
  436. acceptable, press RETURN in response to this question.]
  437.  
  438.  
  439. Octal "symbol,value" [
  440. For any octal symbols to be defined, type one "symbol,value" pair per line
  441. and terminate the list with an extra carriage return. For example, to
  442. change the standard magtape density from 6250 bits per inch (BPI) to 1600,
  443. type:
  444.  
  445. STDENS,4
  446.  
  447. followed by a carriage return. In this example, 1 = 200 BPI, 2 = 556 BPI,
  448. 3 = 800 BPI, and 5 = 6250 BPI. If the default values are acceptable,
  449. press RETURN in response to this question.]
  450.  
  451.  
  452. SIXBIT "symbol,value" [
  453. For any SIXBIT symbol to be defined, type one "symbol,value" pair per line
  454. and terminate the list with an extra carriage return. For example, to
  455. change the name of the mail program from MS to PO, type:
  456.  
  457. M.MAIL,PO
  458.  
  459. followed by a carriage return. If the default values are acceptable,
  460. press RETURN in response to this question.]
  461.  
  462.  
  463. Type "device-mnemonic,PI-channel" for special devices [
  464. This question allows you to build the monitor to support a device driver
  465. that is not part of the standard monitor. Type the device name and the
  466. priority-interrupt channel for a device driver that does not save the ACs
  467. on a priority interrupt, and that does not require Device Data Blocks
  468. (DDBs) in the monitor. A driver of this type can support only one device.
  469. The device mnemonic must be 3 characters or less in length. Type an extra
  470. carriage return when through.]
  471.  
  472.  
  473. Type "device-mnemonic,PI-channel,no.-of-devices" [
  474. This question allows you to define a device driver that requires Device
  475. Data Blocks (DDBs) and will support multiple devices. Specify the device
  476. name, priority-interrupt channel, and number of devices to be supported.
  477. The device-mnemonic must be 3 characters or less in length. Type an extra
  478. carriage return when through.]
  479.  
  480.  
  481. Type "device-mnemonic,PI-channel,highest-ac-to-save" [
  482. This question allows you to define device drivers that include a channel
  483. save routine to save ACs up to the "highest AC to save". Specify the
  484. device name, priority-interrupt channel, and the number of the highest AC
  485. to save on an interrupt. The device-mnemonic must be 3 characters or less
  486. in length. Type extra carriage return when through.]
  487.  
  488.  
  489. Type "ersatz-device,P,Pn,search-list-type" [
  490. This question allows you to define your own ersatz device names.
  491. Monitor-standard ersatz device names must not be redefined. To create
  492. additional site-specific ersatz device names, type a device name in exactly
  493. 3 characters, the Project,Programmer Number (P,PN) associated with the
  494. device, and which search list to use (either ALL, SYS, or JOB) and press
  495. RETURN. You may define another ersatz device, or press RETURN again to
  496. finish.]
  497.  
  498.  
  499. Type "command-name,dispatch,flags,unique-bits,PRVTAB-name" [
  500. This question allows you to create new monitor commands or to redefine
  501. existing monitor commands. The command name that you specify here will run
  502. the program that you specify, using the characteristics that you specify.
  503. Type each new command name followed by the information that the monitor
  504. needs to process the command. This information is specified by each of the
  505. following components. All components must be separated by commas, as shown
  506. above. To omit a component, include only the comma in its place. The
  507. components are:
  508.  
  509. 1. Command-name. The command-name is the name of the monitor command to
  510. be added. Type the command name as a single SIXBIT alphanumeric word
  511. or a single SIXBIT character enclosed in angle-brackets, or omit the
  512. name if you only want to extend PRVTAB.
  513.  
  514. 2. Dispatch address. The dispatch address identifies the program or
  515. routine to run when the command is processed. This may be the name
  516. of the program to run from SYS (file name only), or it may be
  517. omitted if the program name and command name are equivalent. The
  518. dispatch address may also be a location (label) of a routine in the
  519. monitor. For example, #RUNQUE.
  520.  
  521. 3. Flags. Flags are defined in COMMON to specify the type of command
  522. processing for the monitor to use. Separate the flags with an
  523. exclamation point (!). Some of the possible flags are:
  524.  
  525. Flag Meaning
  526.  
  527. APPFLG saves your current context
  528. CMWRQ requeues the job after command processing
  529. CUSTMR reserved for customer implementation
  530. INCORE requires that the job be in memory
  531. NBATCH not allowed from a batch job
  532. NOACT delayed if any devices are active
  533. NOCORE core is not required
  534. NOINCK can be processed if issued without a job
  535. NOJOBN does not require a job number
  536. NOLOGIN does not require that a job be logged in
  537. NOMESS suppresses output of SET WATCH statistics
  538. NOPER monitor must not prompt after command completion
  539. NORUN requires that the job be halted
  540. NXONLY is not legal if the job is execute-only
  541. TTYRNC monitor should put job in monitor mode
  542. TTYRNU monitor should put job in user mode
  543. TTYRNW continue I/O wait after command processing
  544.  
  545. 4. Unique bits. Unique bits are bit numbers you can define to specify
  546. the number of characters that make this command unique. This is
  547. specified in the form INIQ.n, where 'n' is the number of characters
  548. from 1 to 4.
  549.  
  550. 5. PRVTAB-name. The PRVTAB-name is the name of the program to place in
  551. the monitor table PRVTAB. This should be equivalent to the dispatch
  552. program name and may be omitted if the command should not be included
  553. in PRVTAB. PRVTAB is the monitor's list of priviledged CUSPs.
  554.  
  555. Type extra carriage return when through.]
  556.  
  557.  
  558. Terminal class [
  559. A terminal class is defined by the set of attributes and characteristics
  560. exhibited by the class as a whole. If you want to define a terminal class,
  561. type a 1 to 5 character class name and press RETURN. To end this section,
  562. just press RETURN.]:
  563.  
  564. Additional terminals for classes:
  565.  
  566. Class to extend [
  567. Type the name of the terminal class you wish to extend, or press RETURN to
  568. end this section.]:
  569.  
  570. System default terminal type (TTY) [
  571. Type the name of the default termainl type for your system. The terminal
  572. type name must be 1 to 6 characters in length. The monitor will assign
  573. this type to all lines at system start-up, before INITIA runs.]:
  574. File DSK:SYSCNF.MAC Closed [
  575. The SYSGEN portion of the dialogue is finished.
  576. Type CTRL/Z to exit from MONGEN, or select another dialogue option.]
  577.  
  578. Which GEN (SYS,F) [
  579. Type SYS to define hardware and software configuration, or type F to define
  580. software features. To EXIT, type CTRL/Z.]: f
  581. Output(DSK:F.MAC):
  582. Feature set (KL10,KS10) [
  583. KL10 includes all supported TOPS-10 features for KL10 systems. KS10
  584. includes all supported TOPS-10 features for KS10 systems.]: kl10
  585. Standard settings (YES,NO) [
  586. Type YES to use the standard DEC-supported feature test settings. Type NO
  587. to change or define the feature test settings to non-standard values.]:
  588. File DSK:F.MAC Closed [
  589. The FGEN portion of the dialogue is finished.
  590. Type CTRL/Z to exit from MONGEN, or select another dialogue option.]
  591.  
  592. Which GEN (SYS,F) [
  593. Type SYS to define hardware and software configuration, or type F to define
  594. software features. To EXIT, type CTRL/Z.]: ^Z
  595.  
  596. EXIT
  597.  
  598. .compile/compile f,s
  599. MACRO: F
  600. MACRO: S
  601.  
  602. EXIT
  603.  
  604. .compile/compile devprm,dteprm,netprm,d36par
  605. MACRO: DEVPRM
  606. MACRO: DTEPRM
  607. MACRO: NETPRM
  608. MACRO: D36PAR
  609.  
  610. EXIT
  611.  
  612. .compile/compile syscnv+<common,comdev,commod>
  613. ?CMLLRE (0) file was not found - SYSCNV
  614. .compile/compile syscnf+<common,comdev,commod
  615. ?CMLCME Command error detected before:
  616. .compile/compile syscnf+<common,comdev,commod>
  617. MACRO: COMMON
  618. MACRO: COMDEV
  619. MACRO: COMMOD
  620.  
  621. EXIT
  622.  
  623. .del system.exe
  624. Files deleted:
  625. DSKB:SYSTEM.EXE
  626. 1824 Blocks freed
  627.  
  628. .r link
  629.  
  630. *SYSTEM/SAVE/NOINITIAL/HASH:13K = /LOCALS -
  631. #COMMON,COMDEV,COMMOD,TOPS10/SEARCH-
  632. #/PATCH:2000/COUNTERS/GO
  633. [LNKRLC Reloc. ctr. initial value current value limit value
  634. .LOW. 0 155246 330000
  635. .HIGH. 340000 637613 734000
  636. .CSUB. 330000 333466 340000
  637. .INIT. 740000 766606 771000
  638. .TWIC. 771000 772714 1000000
  639. .XHGH. 2630000 2703030 2734000
  640. .SYMS. 2000000 2000000 2630000
  641. Absolute code loaded]
  642.  
  643. EXIT
  644.  
  645. .COPY SYS:SS^C
  646.  
  647. .DEL SYS:SYSTEM.EXE
  648. Files deleted:
  649. DSKB:SYSTEM.EXE
  650. 1824 Blocks freed
  651.  
  652. .copy sys:system.exe=system.exe
  653.  
  654. .dir sys:system.exe
  655.  
  656.  
  657. SYSTEM EXE 1784 <155> 14-May-13 704(33461) DSKB: [1,4]
  658.  
  659. .r opr
  660.  
  661. OPR>set ksys stop
  662. ? Unrecognized switch or keyword: "stop "
  663. OPR>? one of the following:
  664. ABORT ALIGN BACKSPACE CANCEL CLOSE
  665. CONTINUE DEFINE DISABLE DISMOUNT ENABLE
  666. ENTER EXIT FORWARDSPACE HELP HOLD
  667. IDENTIFY LOCK MODIFY MOUNT NEXT
  668. PUSH RECOGNIZE RELEASE REPORT REQUEUE
  669. RESPOND RESTRICT ROUTE SEND SET
  670. SHOW SHUTDOWN START STOP SUPPRESS
  671. TAKE UNLOCK UNRESTRICT WAIT
  672. or one of the following:
  673. CATALOG CONFIG LCP NCP QUOTA
  674. OPR>set ksys now
  675. OPR>
  676. 14:52:35 -- Event KSYS queued, request #3 --
  677.  
  678. 14:52:35 -- Timesharing is over --
  679. Wait for "KSYS processing complete" message before SHUTDOWN
  680.  
  681. 14:52:35 -- Waiting for BATCON to start for KSYS logouts --
  682. OPR>
  683. ;;SYSTEM: - Timesharing is over!
  684.  
  685. 14:52:35 -- KSYS processing completed --
  686.  
  687. OPR>quit
  688. ? Invalid OPR command specified: "quit"
  689. ? : "quit"
  690. OPR>
  691. .[HALTED: FE interrupt]
  692. KLH10> quit
  693. Are you sure you want to quit? [Confirm]
  694. Shutting down...Bye!
  695. b4@maelona ~/pdp10/tops10 $ sudo ./kn10-kl twonky.ini
  696. KLH10 V2.0A release (MyKL) built May 12 2013 04:19:50
  697. Copyright � 2001 Kenneth L. Harrenstien -- All Rights Reserved.
  698. This program comes "AS IS" with ABSOLUTELY NO WARRANTY.
  699.  
  700. Compiled for LINUX on I386 with word model USEINT
  701. Emulated config:
  702. CPU: KL10-extend SYS: T20 Pager: KL APRID: 1
  703. Memory: 8192 pages of 512 words (SHARED)
  704. Time interval: INTRP Base: OSGET
  705. Interval default: 60Hz
  706. Internal clock: OSINT
  707. Other: MCA25 JPC DEBUG PCCACHE CTYINT EVHINT
  708. Devices: DTE RH20 RPXX(DP) TM03(DP) NI20(DP)
  709. [MEM: Allocating 8192 pages shared memory, clearing...done]
  710.  
  711. KLH10> ; KLH10 configuration for TOPS-10 test system
  712. KLH10>
  713. KLH10> ; DTE requires ackdly to avoid T10 race condition
  714. KLH10> devdef dte0 200 dte master ackdly=5
  715. KLH10> devdef rh0 540 rh20
  716. KLH10> devdef rh1 544 rh20
  717. KLH10> devdef dsk0 rh0.0 rp type=rp06 sn=4747 format=dbd9 path=T10-RP06.0-dbd9
  718. KLH10> devdef dsk1 rh0.1 rp type=rp06 sn=1026 format=dbd9 path=T10-RP06.1-dbd9
  719. KLH10> ;devdef dsk2 rh0.2 rp type=rp06 sn=3737 format=dbd9 path=T10-RP06.cust.0-dbd9
  720. KLH10> devdef dsk3 rh0.3 rp type=rp06 sn=5858 format=dbd9 path=stag.dsk
  721. KLH10> devdef mta0 rh1.0 tm03 type=TU77
  722. KLH10>
  723. KLH10> ; NI: param "c3dly" to avoid T10 race.
  724. KLH10> ; NI: param "rdtmo" to avoid system hangups with OSF/1 V3.0
  725. KLH10> ;
  726. KLH10> ; Decnet node TWONKY, 9.429
  727. KLH10> devdef ni0 564 ni20 dedic=1 decnet=1 doarp=0 enaddr=aa:00:04:00:aa:24 ifc=eth0 dpdelay=12 c3dly=10 rdtmo=3
  728. KLH10>
  729. KLH10> load klboot.exe
  730. Using word format "c36"...
  731. Loaded "klboot.exe":
  732. Format: DEC-PEXE
  733. Data: 0, Symwds: 0, Low: 01000000, High: 0, Startaddress: 0703667
  734. Entvec: 0 wds at 0
  735. KLH10> [EOF on twonky.ini]
  736. KLH10> go
  737. Starting KN10 at loc 0703667...
  738. BOOT V4(100)
  739.  
  740. BOOT>system\metsys\
  741. BOOT>
  742. BOOT>
  743. BOOT>dskb:
  744. [Loading from DSKB:SYSTEM.EXE[1,4]]
  745.  
  746. MARLEY TOPS-10 14-May-13
  747. Why reload: new
  748. Date: may-14-2013
  749. Time: 14:53
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!