OctetView
0x00000…00100 (0, 0, 0) Sector 00514130303531 ┆ QA0051A ┆
0x00100…00200 (0, 0, 1) Sector 00000000000000 ┆ ┆
0x00200…00300 (0, 0, 2) Sector ff0080f0ffffff ┆ p ` | ` ┆
0x00300…00306 (0, 0, 3) WangDocument {d00=0x06, d01=0x18, d02=0x41, ptr=(50,0, 0), d05=0x00}
0x00306…0030c WangDocument {d00=0x08, d01=0x14, d02=0x41, ptr=(17,0, 0), d05=0x00}
0x0030c…00312 WangDocument {d00=0x08, d01=0x26, d02=0x41, ptr=(22,0, 0), d05=0x00}
0x00312…00318 WangDocument {d00=0x08, d01=0x28, d02=0x41, ptr=(68,0, 8), d05=0x00}
0x00318…0031e WangDocument {d00=0x08, d01=0x36, d02=0x41, ptr=(20,0, 0), d05=0x00}
0x0031e…00320 08 43 ┆ C┆
0x00320…00340 41 4c 00 45 08 43 41 4c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆AL E CAL ┆
0x00340…00360 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ ┆
[…0x4…]
0x003e0…00400 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1e ┆ ┆
0x00400…00500 (0, 0, 4) Sector 00000000000000 ┆ ┆
0x00500…00600 (0, 0, 5) Sector 00514130303531 ┆ QA0051A ┆
0x00600…00700 (0, 0, 6) Sector 421c402600415b ┆B @& A[' H X% % PO P ; (Ar C f x f V W O B : b 0828A f %F < {C < { ; 0 ` r b bD K : 9 8Xm xyW 0618A0828A 7 <)(& " ┆
0x00700…00800 (0, 0, 7) Sector 00000000000000 ┆ ┆
0x00800…00900 (0, 0, 8) Sector aaaaaaaaaaaaaa ┆****************************************************************************************************************************************************************************************************************************************************************┆
[…0x7…]
0x01000…01100 (1, 0, 0) WangDocumentBody
0x01100…01200 (1, 0, 1) Sector 0102ff00061841 ┆ A multiprocessing as it becomes obvious in section 4.2. 4.3.2 Terminal Load Any buffering due to limited amounts of terminals on output or insufficient amount of terminals to deliver the specified input shall not be considered in the performance┆
0x01200…01300 (1, 0, 2) Sector 0103ff00061841 ┆ A calculations. As it will be seen from the following presentation of input and output requirements for terminals on the maximum configuration site, assuming wired capacity for maximum configuration, there is no serious limitation although the limi┆
0x01300…01400 (1, 0, 3) Sector 0104ff00061841 ┆ At is exceeded in some cases with a small amount. The supervisor input due to service messages, table updates, etc. has not been included; since these actions may be assumed to present a load not higher than the one due to message service they wil┆
0x01400…01500 (1, 0, 4) Sector 00005c00061841 ┆ \ Al present no problem. The load to the supervisory printers is listed in table 2.19. ffer contents is further transferred to the printers or VDUs. Similarly, the TDX is also transferring buffer contents from LTUXs to the PU-memory. Characters to┆
0x01500…01600 (1, 0, 5) Sector aaaaaaaaaaaaaa ┆****************************************************************************************************************************************************************************************************************************************************************┆
[…0x2…]
0x01800…01900 (1, 0, 8) WangDocumentBody
[…0x3…]
0x01c00…01d00 (1, 0, 12) Sector 010dff00081441 ┆ Asoftware modules resident in the MAP microprocessor PROM, in the MIA Bootload PROM and on a Disk Pack, alternatively Floppy Disk, enables the operator via the VDU + keyboard to perform a step-by-step troubleshooting procedure down to module level. ┆
0x01d00…01e00 (1, 0, 13) Sector 00000600081441 ┆ A on the front panel. The pin lay out of the BSM-X cannon connector is shown in fig. 2.4-2. As seen +5v is present on pin 12. When a TDX controller is "connected" this implies that Bus select (see CSD- MIC/005/TCM/0015) is equal to "1" thus selecting┆
0x01e00…01f00 (1, 0, 14) Sector 010f4f00081441 ┆ O Asoftware modules resident in the MAP microprocessor PROM, in the MIA Boothe BSM-X is part of each TU, and a TDX controller is only present in two of the TU's, it will be necessary to simulate a correct combination of status signals from a TDX contro┆
0x01f00…02000 (1, 0, 15) Sector 0000b500081441 ┆ 5 Aload PROM and on a Disk Pack, alternatively Floppy Disk, enables the operator via the VDU + keyboard to perform a step-by-step troubleshooting procedure down to module level. hat the +5v and GND on the BSM-X is present in the cannon connector on the┆
0x02000…02100 (2, 0, 0) WangDocumentBody
[…0xef…]
0x11000…11100 (17, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(17,0, 1), len=0xff, h3=41081441}, f00=»0814A «, f01=»WATCHDOG H/W REQ.SPEC. «, f02=»rt/vhn «, f03=»SRA «, f04=»CPS/SRS/003 «, f05=25-03-81 13:06, f06=» 3 «, f07=»20 «, f08=» 13924 «, f09=24-06-81 17:15, f10=» «, f11=»00 «, f12=» 5 «, f13=24-06-81 17:16, f14=24-06-81 17:29, f15=»0051A «, f16=» 23 «, f17=» 7 «, f18=»32 «, f19=» 236 «, f20=» 19102 «, f21=» «, f22=» «, f99=990030000110056610110480aaca15050000000000000038035400df}
0x11100…11200 (17, 0, 1) WangDocumentBody
[…0x9…]
0x11b00…11c00 (17, 0, 11) Sector 110c9e00082641 ┆ &A 1 Fig. 5.2 Remote-site Configuration aking V24 connections between the main sites and the remote sites. Mainly to support 4 terminals┆
0x11c00…11d00 (17, 0, 12) Sector 110da800082641 ┆ ( &A 1 6 APPENDIX A Equipment Breakdown. 6.1 Notes to Appendix A 6.2 Equipment Matrix . 4.1 p. 6). This does not mean an expansion in the connectivity of the CAMPS, only a ┆
0x11d00…11e00 (17, 0, 13) Sector 110eff00082641 ┆ &A 1 6.1 Notes to Appendix A 1. The main site numbers are according to CAMPS Contract p. 15. These are now stated as CR standard. 2. The equipment matrix (p. 13) shows the equipme┆
0x11e00…11f00 (17, 0, 14) Sector 110fff00082641 ┆ &Ant quantity on each site, for the design of the CRT. 3. The spare remote site OMDTs are added to make the spare terminals (VDUs and MSPs) valid spare parts in both V24 and opto connections. 4. The underlined numbers of the Grand- and Remote Tota┆
0x11f00…12000 (17, 0, 15) Sector 01002e00082641 ┆ . &Als represent the total equipment list. Fig. 4.1 CRT LINE CONFIGURATION ┆
0x12000…12100 (18, 0, 0) WangDocumentBody
[…0x1d…]
0x13e00…13f00 (19, 0, 14) Sector aaaaaaaaaaaaaa ┆****************************************************************************************************************************************************************************************************************************************************************┆
[…0x1…]
0x14000…14100 (20, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(20,0, 1), len=0xff, h3=41083641}, f00=»0836A «, f01=»CPS/QAR/003 «, f02=»kk «, f03=»SVO «, f04=»QA Rapport, SSO «, f05=30-03-81 08:34, f06=» 1 «, f07=»15 «, f08=» 2305 «, f09=06-04-81 10:00, f10=» «, f11=»03 «, f12=» 44 «, f13=06-04-81 10:04, f14=07-04-81 12:29, f15=»0051A «, f16=» 2 «, f17=» 3 «, f18=»00 «, f19=» 52 «, f20=» 6481 «, f21=» «, f22=» «, f99=020020000110056610a10a80aaca15050000000000000038030e00df}
0x14100…14200 (20, 0, 1) WangDocumentBody
[…0x1e…]
0x16000…16100 (22, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(22,0, 1), len=0xff, h3=41082641}, f00=»0826A «, f01=»CPS/TCN/024 - issue 4 «, f02=»sdv/am] «, f03=»DL «, f04=»CPS Remote terminals «, f05=27-03-81 10:57, f06=» «, f07=»35 «, f08=» 3437 «, f09=30-06-81 16:23, f10=» «, f11=»01 «, f12=» 10 «, f13=30-06-81 16:25, f14=13-07-81 16:10, f15=»0051A «, f16=»017 «, f17=» 3 «, f18=»53 «, f19=»00232 «, f20=» 16311 «, f21=» «, f22=» «, f99=310041000110050710110480aaca15050000000000000038033300df}
0x16100…16200 (22, 0, 1) WangDocumentBody
[…0x31…]
0x19300…19400 (25, 0, 3) Sector 1904ff00082841 ┆ (A 1 DISC CONTROLLER RAM ACCESS MANAGEMENT The controller cannot manage the receipt of instructions and data from transmission of data to the I/O Channel together with the receipt┆
0x19400…19500 (25, 0, 4) Sector 1905ff00082841 ┆ (A of data from or transmission of data to the disc. Since the time t CONTR is of the same order as the transfer time on the I/O Channel (refer section 4.4) we may, however, assume this constraint to be negligible. Disc Seek Time For calculation ┆
0x19500…19600 (25, 0, 5) Sector 1906ff00082841 ┆ (Aof seek time it is assumed that the data are uniformly distributed, i.e. the probability of the data being located on a certain track is the probability of the head having to move from that track to any other track and equal to 1/N where N is the nu┆
0x19600…19700 (25, 0, 6) Sector 1907ff00082841 ┆ (Amber of tracks per head. From J. Martin, Design of Real Time Computer System, Chapter 28, page 441 the mean number of tracks to be traversed and the variance are found as X = (N 2 - 1)/3N N/3 6 x 2 = (N 4 + N 2 - 2) / 18N 2 N 2 /18 ┆
0x19700…19800 (25, 0, 7) Sector 1808ff00082841 ┆ (AFig. 4.5.1-2 presents the SEEK TIME as a function of tracks moved and the CAMPS linear approximation to the seek time: It is important to notice that the CAMPS data may be constrained to the first 200 tracks per head: the 5 heads will provide one ac┆
0x19800…19900 (25, 0, 8) WangDocumentBody
[…0x187…]
0x32000…32100 (50, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(50,0, 1), len=0xff, h3=41061841}, f00=»0618A «, f01=»CAMPS Perform. Report «, f02=»sdv/rt «, f03=»FAH «, f04=»CPS/REP/001 «, f05=05-02-81 11:37, f06=» 2 «, f07=»44 «, f08=» 4894 «, f09=21-09-82 13:26, f10=» «, f11=»05 «, f12=» 31 «, f13=04-11-82 08:45, f14=05-11-82 10:06, f15=»0051A «, f16=» 73 «, f17=» 116 «, f18=»52 «, f19=» 1304 «, f20=»207871 «, f21=» «, f22=» p «, f99=170017000110052710110290aa4a55050000000000000138039101df}
0x32100…32200 (50, 0, 1) WangDocumentBody
[…0x126…]
0x44800…44900 (68, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(68,0, 9), len=0xff, h3=41082841}, f00=»0828A «, f01=»CPS/REP/001 «, f02=»ba «, f03=»FAH «, f04=»PERF.REPORT fra 3.6 «, f05=27-03-81 12:45, f06=» 5 «, f07=»51 «, f08=» 22396 «, f09=04-11-82 13:13, f10=» «, f11=»00 «, f12=» 10 «, f13=04-11-82 13:12, f14=05-11-82 10:06, f15=»0051A «, f16=» 95 «, f17=» 55 «, f18=»15 «, f19=» 1676 «, f20=»112625 «, f21=» «, f22=» «, f99=590000000110056610110290aa4a55050000000000000138030302df}
0x44900…44a00 (68, 0, 9) WangDocumentBody
[…0x6…]
0x45000…45100 (69, 0, 0) Sector 4501ff00082841 ┆E (A 1 3.6.2 Terminal Loading Requirements This subsection presents the TDX-system load and the I/O channel load due to terminals: Refer the tables 3.6.2. Since the TDX-system and I/O ┆
0x45100…45200 (69, 0, 1) Sector 4502ff00082841 ┆E (Achannel systems are conditioned to accept the full load corresponding to the total terminal capacity (refer sections 4.3 and 4.4) we shall in section 3.6 be concerned with the load per terminal relative to the required capacity. This comparison is d┆
0x45200…45300 (69, 0, 2) Sector 4503ff00082841 ┆E (Aone in subsections 3.6.3 and 3.6.4. It is seen that even in busy minute the maximum terminal load of 70 per cent of capacity specified for busy hour is not exceeded; consequently the figures implied by the traffic flow will be used (since not violat┆
0x45300…45400 (69, 0, 3) Sector 4504ff00082841 ┆E (Aing the required capacity). VDU and PRINTER output is treated en block in section 3.6.3, reflecting the fact that printer output of messages may in some cases be guided to a VDU, or vica versa, in case of overload. Here we shall consider the load ┆
0x45400…45500 (69, 0, 4) Sector 4505ff00082841 ┆E (Aof the printers and VDU's separately: It is seen that the load of each user printer is about 70 ch/sec and thus below the specified limit for busy hour of 70 per cent of capacity which is 84 ch/sec. The load of the VDU's and other Printers (they hav┆
0x45500…45600 (69, 0, 5) Sector 4506ff00082841 ┆E (Ae the same capacity) is also below the limit for busy hour. Similarly, the OCR and PTR's are not overloaded. The load of the OCR, which has a capacity of 240 ch./sec., is well below the limit of 0.7 x 240 = 168 ch./sec. in busy hour. It is a b┆
0x45600…45700 (69, 0, 6) Sector 45074f00082841 ┆E O (Aasic assumption that the loads are equally distributed on the terminals. nute figure, whereas section 3.6.3 and 3.6.4 will concentrate on the busy second requirements. 3.6.1 Loading Resulting from Data Collection, CPU's and DISCs This subsectio┆
0x45700…45800 (69, 0, 7) Sector 4408ff00082841 ┆D (A 1 1 BUSY MIN BUSY HOUR ITEM TRSFER/SEC BYTE/SEC TRSFE┆
0x45800…45900 (69, 0, 8) Sector 4509ff00082841 ┆E (A 1 1 ITEM BUSY HOUR/3600 DIRECT CPU 0.08 Q┆
0x45900…45a00 (69, 0, 9) Sector 450aff00082841 ┆E (AMON *) 0.006 MMON *) 0.13 MMS **) 0.19 XFER *) 0.25 CPT *) 0.02 FMS **) 0.02 FMST **) 0.03 TMP *) 0.10 TMS *) 0.20 LTU HANDLER *) 0.003 TDX HANDLER *) 0.08 DCM (DISC CACHE MANAG.)**) 0.08 DISC HANDLER 0.15 OTHERS 0.15┆
0x45a00…45b00 (69, 0, 10) Sector 450bff00082841 ┆E (A CPU TOTAL 1.48 CPU TOTAL BUSY MIN/60 = 2.20 TABLE 3.6.1-1 CPU Time Consumption in seconds per seconds of time available in one┆
0x45b00…45c00 (69, 0, 11) Sector 450c4200082841 ┆E B (A CPU *), **): Non-concurrent **) Same process, coroutines hvor? Dokument: Hvilken kommando? Hvilken side: (Sletter) (S]ger) (Udf]rer) Inds`t hvilket? Slette hvilket? Flytte hvilket? Kopiere hvilket? Bytte hvilket? Bytte med? S]ge hvilket? ┆
0x45c00…45d00 (69, 0, 12) Sector 450dff00082841 ┆E (A 1 1 NUMBER OF ACCESS BUSY MIN. BUSY HOUR ┆
0x45d00…45e00 (69, 0, 13) Sector 450eff00082841 ┆E (A DISC READ 22.8 15.7 DISC WRITE 8.85 4.76 Number of disc accesses per second ┆
0x45e00…45f00 (69, 0, 14) Sector 450fff00082841 ┆E (A BUSY MIN BUSY HOUR DISC LOAD 74.6% 46.4% TABLE 3.6.1-2 Disc load assuming: NO CACHE HITS and CAPABILITY = 27.2 ACCESS/SEC*), where READ's are equa┆
0x45f00…46000 (69, 0, 15) Sector 45004400082841 ┆E D (Ally distributed on mirrorred discs. *) refer section 4.5.2 ┆
0x46000…46100 (70, 0, 0) Sector 4601ff41082841 ┆F A (A0828A CPS/REP/001 ba FAH PERF.REPORT fra 3.6 27 03 81 12 45 5 51 22396 19 10 82 14 15 00 6 19 10 82 14 38 25 10 82 09 46 0051A 95 53 50 1760 112510 @ t f *J 8 _┆
0x46100…46200 (70, 0, 1) Sector 46025f00082841 ┆F _ (A F F E E E E D D D D C C C C C B B B B A A @ @ ? ? > > = = < < < < ; ; ; : : : 9 9 9 8 8 8 7 7 7 7 6 6 6 5 5 4 4 4 4 & & % % $ $ # # # " " " ! ! ! ┆
0x46200…46300 (70, 0, 2) Sector 46039400082841 ┆F (A 1 CPS/REP/001 FAH/820107 # CAMPS PERFORMANCE REPORT CAMPS :!<~ B%-!/=6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x46300…46400 (70, 0, 3) Sector 4604ff00082841 ┆F (A 1 3.6 RESULTING LOADING REQUIREMENTS Loading requirements may be finally broken dawn into CPU time, TDX system access, I/O Channel access, and DISC access requirements. The requirem┆
0x46400…46500 (70, 0, 4) Sector 4605ff00082841 ┆F (Aents may be further divided amongst different processes, coroutines, and procedures. The loading requirements are presented in section 3.6.1 as based on the Data Collection Sheets of the sections 3.3 - 3.5. The TDX system access requirements may a┆
0x46500…46600 (70, 0, 5) Sector 4606ff00082841 ┆F (Also be expressed in terms of the character transfer. Section 3.6.2 presents the total load on the following types of terminals: VDU's and printers for user and supervisory functions. Section 3.6.2 also presents the I/O Channel character transfer l┆
0x46600…46700 (70, 0, 6) Sector 4607ff00082841 ┆F (Aoad. Sections 3.6.1 and 3.6.2 will include busy hour as well as busy minute figure, whereas section 3.6.3 and 3.6.4 will concentrate on the busy second requirements. 3.6.1 Loading Resulting from Data Collection, CPU's and DISCs This subsectio┆
0x46700…46800 (70, 0, 7) Sector 45089a00082841 ┆E (An presents the total load requirements for CPU's and DISC's. Queuing considerations resulting from these figures are found in the sections 4 and 5. E*8=k L<M% :8=F 28=I!#<:"<>R<2> I E*#<& "< DM L<M% :#<F 2#<> I:g= Ro2M/2 Rl2> IC13!?=4~~ B|2> I:A=!┆
0x46800…46900 (70, 0, 8) Sector 4609ff00082841 ┆F (AR/SEC BYTE/SEC CHECKPOINTS, TDX 5.79 92.7 4.54 72.7 USER VDU's (28) 3.07 72.8 3.05 65.2 MSO + MDCO VDU's 0.24 37.1 0.24 37.1 OCR (1) 0.03 12.8 0.01 6.4 PTR 0.08 4.┆
0x46900…46a00 (70, 0, 9) Sector 460aff00082841 ┆F (A3 0.04 2.1 PTR, DEDICATED (1) 0.04 20.5 0.01 6.8 EXT CHAN., TRC 0.26 132 0.10 52.2 (24) EXIT CHAN., P-T-P 0.15 78.5 0.05 26.3 TOTAL 9.66 451 8.04 269 ┆
0x46a00…46b00 (70, 0, 10) Sector 460b6500082841 ┆F e (A TABLE 3.6.2-1 TDX READ CPU TOTAL BUSY MIN/60 = 2.20 TABLE 3.6.1-1 CPU Time Consumption in seconds per seconds of time available in one┆
0x46b00…46c00 (70, 0, 11) Sector 460cff00082841 ┆F (A 1 BUSY MIN BUSY HOUR ITEM TRSFER/SEC BYTE/SEC TRSFER/SEC BYTE/SEC ┆
0x46c00…46d00 (70, 0, 12) Sector 460dff00082841 ┆F (A CHECK POINTS, TDX 5.79 1668 4.54 1254 USER VDU's (28) 4.75 1627 4.72 1619 MSO + MDCO VDU's 0.26 101 0.26 101 USER PRINTERS (12) 1.65 844 1.65 844 LOG PRINTER (1) 0.16 80 0.16 80 STATISTIC PRINTER (1) 0.16 80 0.16 80 R┆
0x46d00…46e00 (70, 0, 13) Sector 460eff00082841 ┆F (AEPORT PRINTER (1) 0.01 4.2 0.01 4.2 P-T-P,DEDICATED (1) 0.04 20.5 0.01 6.8 EXT.CHAN., TRC 0.08 40.2 0.03 16.2 (24) EXT.CHAN.,P-T-P 0.44 223 0.15 76.7 TOTAL 1┆
0x46e00…46f00 (70, 0, 14) Sector 460f7e00082841 ┆F ~ (A3.3 4688 11.7 4082 TABLE 3.6.2-2 TDX WRITE TABLE 3.6.1-2 Disc load assuming: NO CACHE HITS and CAPABILITY = 27.2 ACCESS/SEC*), where READ's are equa┆
0x46f00…47000 (70, 0, 15) Sector 4600ff00082841 ┆F (A 1 BUSY MIN BUSY HOUR ITEM TRSFER/SEC BYTE/SEC TRSFER/SEC BYTE/SEC ┆
0x47000…47100 (71, 0, 0) Sector 4701ff00082841 ┆G (A 1 3.6.2 Terminal Loading Requirements This subsection presents the TDX-system load and the I/O channel load due to terminals: Refer the tables 3.6.2. Since the TDX-system and I/O ┆
0x47100…47200 (71, 0, 1) Sector 4702ff00082841 ┆G (Achannel systems are conditioned to accept the full load corresponding to the total terminal capacity (refer sections 4.3 and 4.4) we shall in section 3.6 be concerned with the load per terminal relative to the required capacity. This comparison is d┆
0x47200…47300 (71, 0, 2) Sector 4703ff00082841 ┆G (Aone in subsections 3.6.3 and 3.6.4. It is seen that even in busy minute the maximum terminal load of 70 per cent of capacity specified for busy hour is not exceeded; consequently the figures implied by the traffic flow will be used (since not violat┆
0x47300…47400 (71, 0, 3) Sector 4704ff00082841 ┆G (Aing the required capacity). VDU and PRINTER output is treated en block in section 3.6.3, reflecting the fact that printer output of messages may in some cases be guided to a VDU, or vica versa, in case of overload. Here we shall consider the load ┆
0x47400…47500 (71, 0, 4) Sector 4705ff00082841 ┆G (Aof the printers and VDU's separately: It is seen that the load of each user printer is about 70 ch/sec and thus below the specified limit for busy hour of 70 per cent of capacity which is 84 ch/sec. The load of the VDU's and other Printers (they hav┆
0x47500…47600 (71, 0, 5) Sector 4706ff00082841 ┆G (Ae the same capacity) is also below the limit for busy hour. Similarly, the OCR and PTR's are not overloaded. The load of the OCR, which has a capacity of 240 ch./sec., is well below the limit of 0.7 x 240 = 168 ch./sec. in busy hour. It is a b┆
0x47600…47700 (71, 0, 6) Sector 47074f00082841 ┆G O (Aasic assumption that the loads are equally distributed on the terminals. nute figure, whereas section 3.6.3 and 3.6.4 will concentrate on the busy second requirements. 3.6.1 Loading Resulting from Data Collection, CPU's and DISCs This subsectio┆
0x47700…47800 (71, 0, 7) Sector 4608ff00082841 ┆F (A 1 1 BUSY MIN BUSY HOUR ITEM TRSFER/SEC BYTE/SEC TRSFE┆
0x47800…47900 (71, 0, 8) Sector 4709ff00082841 ┆G (A 1 1 ITEM BUSY HOUR/3600 DIRECT CPU 0.08 Q┆
0x47900…47a00 (71, 0, 9) Sector 470aff00082841 ┆G (AMON *) 0.006 MMON *) 0.13 MMS **) 0.19 XFER *) 0.25 CPT *) 0.02 FMS **) 0.02 FMST **) 0.03 TMP *) 0.10 TMS *) 0.20 LTU HANDLER *) 0.003 TDX HANDLER *) 0.08 DCM (DISC CACHE MANAG.)**) 0.08 DISC HANDLER 0.15 OTHERS 0.15┆
0x47a00…47b00 (71, 0, 10) Sector 470bff00082841 ┆G (A CPU TOTAL 1.48 CPU TOTAL BUSY MIN/60 = 2.20 TABLE 3.6.1-1 CPU Time Consumption in seconds per seconds of time available in one┆
0x47b00…47c00 (71, 0, 11) Sector 470c4200082841 ┆G B (A CPU *), **): Non-concurrent **) Same process, coroutines hvor? Dokument: Hvilken kommando? Hvilken side: (Sletter) (S]ger) (Udf]rer) Inds`t hvilket? Slette hvilket? Flytte hvilket? Kopiere hvilket? Bytte hvilket? Bytte med? S]ge hvilket? ┆
0x47c00…47d00 (71, 0, 12) Sector 470dff00082841 ┆G (A 1 1 NUMBER OF ACCESS BUSY MIN. BUSY HOUR ┆
0x47d00…47e00 (71, 0, 13) Sector 470eff00082841 ┆G (A DISC READ 22.8 15.7 DISC WRITE 8.85 4.76 Number of disc accesses per second ┆
0x47e00…47f00 (71, 0, 14) Sector 470fff00082841 ┆G (A BUSY MIN BUSY HOUR DISC LOAD 74.6% 46.4% TABLE 3.6.1-2 Disc load assuming: NO CACHE HITS and CAPABILITY = 27.2 ACCESS/SEC*), where READ's are equa┆
0x47f00…48000 (71, 0, 15) Sector 47004400082841 ┆G D (Ally distributed on mirrorred discs. *) refer section 4.5.2 ┆
0x48000…48100 (72, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(72,0, 1), len=0xff, h3=41082841}, f00=»0828A «, f01=»CPS/REP/001 «, f02=»ba «, f03=»FAH «, f04=»PERF.REPORT fra 3.6 «, f05=27-03-81 12:45, f06=» 5 «, f07=»51 «, f08=» 22396 «, f09=13-10-82 10:53, f10=» «, f11=»14 «, f12=» 19 «, f13=13-10-82 09:51, f14=15-10-82 09:44, f15=»0051A «, f16=» 95 «, f17=» 53 «, f18=»04 «, f19=» 1892 «, f20=»111141 «, f21=» «, f22=» @ «, f99=020074000110056610110280aaca15050000000000000138030202df}
0x48100…48200 (72, 0, 1) Sector 48025f00082841 ┆H _ (A H H G G G G F F F F E E E E E D D D D C C B B A A @ @ ? ? > > > > = = = < < < ; ; ; : : : 9 9 9 9 8 8 8 7 7 6 6 6 6 5 5 4 4 & & % % % $ $ $ # # # " " " " ! ! ! ┆
0x48200…48300 (72, 0, 2) Sector 48039400082841 ┆H (A 1 CPS/REP/001 FAH/820107 # CAMPS PERFORMANCE REPORT CAMPS :!<~ B%-!/=6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x48300…48400 (72, 0, 3) Sector 4804ff00082841 ┆H (A 1 3.6 RESULTING LOADING REQUIREMENTS Loading requirements may be finally broken dawn into CPU time, TDX system access, I/O Channel access, and DISC access requirements. The requirem┆
0x48400…48500 (72, 0, 4) Sector 4805ff00082841 ┆H (Aents may be further divided amongst different processes, coroutines, and procedures. The loading requirements are presented in section 3.6.1 as based on the Data Collection Sheets of the sections 3.3 - 3.5. The TDX system access requirements may a┆
0x48500…48600 (72, 0, 5) Sector 4806ff00082841 ┆H (Also be expressed in terms of the character transfer. Section 3.6.2 presents the total load on the following types of terminals: VDU's and printers for user and supervisory functions. Section 3.6.2 also presents the I/O Channel character transfer l┆
0x48600…48700 (72, 0, 6) Sector 4807ff00082841 ┆H (Aoad. Sections 3.6.1 and 3.6.2 will include busy hour as well as busy minute figure, whereas section 3.6.3 and 3.6.4 will concentrate on the busy second requirements. 3.6.1 Loading Resulting from Data Collection, CPU's and DISCs This subsectio┆
0x48700…48800 (72, 0, 7) Sector 47089a00082841 ┆G (An presents the total load requirements for CPU's and DISC's. Queuing considerations resulting from these figures are found in the sections 4 and 5. E*8=k L<M% :8=F 28=I!#<:"<>R<2> I E*#<& "< DM L<M% :#<F 2#<> I:g= Ro2M/2 Rl2> IC13!?=4~~ B|2> I:A=!┆
0x48800…48900 (72, 0, 8) Sector 4809ff00061841 ┆H A 1 MAPPING OF REQUIREMENTS FUNCTION REQUIREMENTS IOC TEP SFM THR=THROUGHPUT TIM=TIMING ┆
0x48900…48a00 (72, 0, 9) Sector 480aff00061841 ┆H A RELEASE THR: BUSY MIN, Validate re- Fetch release and BUSY HOUR lease format format + msg. WAR 2048 ch/msg queue notifi- Accept assu- out cation for med 512 ch/msg distributi┆
0x48a00…48b00 (72, 0, 10) Sector 480b9b00061841 ┆H Aon inp. Queue msg. to traffic hand- ling. TABLE 2-5 entering msg. inp 3 SIC/MSG (last ch. Incl. transmitted PLA's, AIG's request from VDU) ┆
0x48b00…48c00 (72, 0, 11) Sector 480cff00061841 ┆H A 1 MAPPING OF REQUIREMENTS FUNCTION REQUIREMENTS MDP TEP IOC THR=THROUGHPUT TIM=TIMING ┆
0x48c00…48d00 (72, 0, 12) Sector 480dff00061841 ┆H A DISTRIBUTION THR: BUSY HOUR, Fetch Distr. Transfer to of outg. msg WAR inf.; check terminals locally, and queue security int. coord, com- for TEP. ments, re- lease no- For outg. ┆
0x48d00…48e00 (72, 0, 13) Sector 480eff00061841 ┆H Amsg. tification. ass. 3 SIC & 2 SDL. Add. SCDs from prepara- tion, when lo- cally generated RECEPTION of the same Outg. msg. 1792 ch/msg Coordination COORDINATION: 1792 ch/msg 15 msg are coord 2 times with 5 copies; Release ┆
0x48e00…48f00 (72, 0, 14) Sector 480fe600061841 ┆H f A256 ch/notif. notification 10 msg are presented once, Comments and coord once 256 ch/comm. with 5 copies (ie. 10x6 coord) TABLE 2-6 HPUT TIM=TIMING ┆
0x48f00…49000 (72, 0, 15) Sector 4800ff00061841 ┆H A 1 MAPPING OF REQUIREMENTS FUNCTION REQUIREMENTS THP THR=THROUGHPUT TIM=TIMING ┆
0x49000…49100 (73, 0, 0) Sector 4901c600061841 ┆I F A. send release TIM: as prep. 2 edit per (Operator msg will change 256 ch per edit). TABLE 2-2 lations may be carried through as in section 5. ┆
0x49100…49200 (73, 0, 1) Sector 4902ff00061841 ┆I A 1 MAPPING OF REQUIREMENTS FUNCTION REQUIREMENTS IOC TEP SFM THR=THROUGHPUT TIM=TIMING ┆
0x49200…49300 (73, 0, 2) Sector 4903ff00061841 ┆I A COMMENT PREP THR: BUSY HOUR, Validation Fetch format WAR of total com- reserve file, 256 ch/comm ment store out 512 ch/comm. inp. TIM: Time from ent┆
0x49300…49400 (73, 0, 3) Sector 4904ff00061841 ┆I Ary (last character transmitted from VDU of fully prep. comment to first ch. Resp.: as prep. = 10 sec (90%) VDU PAGES THR:(BUSY HOUR), 256 ch out As above As above PREP. WAR 2x1024 ch inp ┆
0x49400…49500 (73, 0, 4) Sector 49052e00061841 ┆I . A TABLE 2-3 character from VDU until reception of first character on VDU. - Timing requirements for incoming message handling shall apply from reception of last character until delivery of first character to printer or┆
0x49500…49600 (73, 0, 5) Sector 4906ff00061841 ┆I A 1 MAPPING OF REQUIREMENTS FUNCTION REQUIREMENTS IOC TEP SFM THR=THROUGHPUT TIM=TIMING ┆
0x49600…49700 (73, 0, 6) Sector 4907ff00061841 ┆I A COMMENT THR: BUSY HOUR, Complete re- As prep. EDITING WAR 256 ch/comm. evaluation as out prep. 1 edit/comm. 512 ch/comm. TIM: As com- inp. ment prep. (Operator will chan┆
0x49700…49800 (73, 0, 7) Sector 4808c900061841 ┆H I Age 50 ch) VDU PAGES THR:(BUSY HOUR), 2x1024 ch out As above As above EDIT WAR 1 edit/page 2x1024 ch inp TABLE 2-4 5.2 RESPONSE TIMES ........................... ┆
0x49800…49900 (73, 0, 8) Sector 4909ff00061841 ┆I A 1 MAPPING OF REQUIREMENTS FUNCTION REQUIREMENTS IOC TEP/THP SFM THR=THROUGHPUT TIM=TIMING ┆
0x49900…49a00 (73, 0, 9) Sector 490aff00061841 ┆I A OUTG. MSG THR: BUSY Format Trans- TEP: MSG. Fetch Prep. PREP. HOUR, WAR fer to VDU Validation; format; Header & Reserve File Text Separa- & Store tely and in tota┆
0x49a00…49b00 (73, 0, 10) Sector 490bff00061841 ┆I Al. Msg. Trans- fer from VDU Separate 512 ch/msg. Prep. of out Header TIM: CHECK TABLES and Time from 2 x 1024 ch/ 5 PLA, 0.1 AIG, Text entering msg. inp 3 SIC/MSG (last ch. Incl. transmitted PLA's, AIG's request from VDU) ┆
0x49b00…49c00 (73, 0, 11) Sector 490cff00061841 ┆I A SIC's are for coord. header or text ass. to result and release for validation in only one to first ch. disc access response: each. 10 sec (90%) OCR INPUT THR: BUSY HOUR, WAR 2 x 1024 ch/ As above As above msg inp. except for prep┆
0x49c00…49d00 (73, 0, 12) Sector 490dff00061841 ┆I A. format. PTR INPUT THR: BUSY HOUR, 1536 ch/msg TRAF. HANDL.: Reserve file WAR inp. Routing vali- & store dation of non- encrypted msg Check tables: 5 PLA, 0.1 AIG ┆
0x49d00…49e00 (73, 0, 13) Sector 490e1500061841 ┆I A TABLE 2-1 ements: These requirements are listed and treated in section 5.3 separately. In section 3 data for usage of CPU-time, number of accesses to disc, and character transfer on TDX and Channel system are collected for each function which┆
0x49e00…49f00 (73, 0, 14) Sector 490fff00061841 ┆I A 1 MAPPING OF REQUIREMENTS FUNCTION REQUIREMENTS IOC TEP SFM THR=THROUGHPUT TIM=TIMING ┆
0x49f00…4a000 (73, 0, 15) Sector 4900ff00061841 ┆I A MSG EDITING THR:BUSY HOUR, Complete re- As prep. WAR evaluation as As prep. but 2x1024 ch/msg prep. with 1/2 out. send for coordina- 2x1024 ch/msg tion and no inp┆
0x4a000…4a100 (74, 0, 0) Sector 4a01f600061841 ┆J v A. Based on the results from section 3 a system model shall be selected, hereby including system hardware characteristics. This discussion is found in section 4. Finally, performance calculations may be carried through as in section 5. ┆
0x4a100…4a200 (74, 0, 1) Sector 4a02ff00061841 ┆J A 1 2 MAPPING OF REQUIREMENTS The requirement sheets presented are a straight forward listing of performance requirements related in each case to one of the functions known from the┆
0x4a200…4a300 (74, 0, 2) Sector 4a03ff00061841 ┆J A system requirements specification. For each requirement is further specified the system packages involved. The following general notes shall apply in all cases as specified here: - throughput requirements correspond to busy hour traffic durin┆
0x4a300…4a400 (74, 0, 3) Sector 4a04ff00061841 ┆J Ag war as shown in fig. 2-1. Busy minute figures are 3 times busy hour figures for incoming messages and 2 times for outgoing message traffic. - Timing requirements are valid for busy hour only. - Timing requirements for interactive transactio┆
0x4a400…4a500 (74, 0, 4) Sector 4a05ff00061841 ┆J Ans shall apply from transmission of last character from VDU until reception of first character on VDU. - Timing requirements for incoming message handling shall apply from reception of last character until delivery of first character to printer or┆
0x4a500…4a600 (74, 0, 5) Sector 4a06ff00061841 ┆J A VDU. - Security interrogation shall not be included in timing requirements. In certain cases (e.g. Statistics, and Log collection and print) discussions are carried through in order to derive figures for section 3. Whenever CPU time consumpti┆
0x4a600…4a700 (74, 0, 6) Sector 4a07f300061841 ┆J s Aon is quoted, CPU time for disc access is not included. Storage requirements are listed and discussed in 5.3. Discussion and listing of certain connectivity oriented throughput requirements are postponed to the sections 4.3 and 4.4. STEM .......┆
0x4a700…4a800 (74, 0, 7) Sector 49089a00061841 ┆I A 1 CAMPS TRAFFIC FLOW BUSY HOUR WAR THROUGHPUT ............................... 5.2 RESPONSE TIMES ........................... ┆
0x4a800…4a900 (74, 0, 8) Sector 4a094000061841 ┆J @ A 5.3 SIZING ................................... M *y= "(= q#p! =6 M] : =V V I: =~ B 3: = R 3*$<MMY *%<MMY !\<6 C 3M, !\<6 : =~ B 5: = R$3C/4!e=6 !f=6 !g=6 !h=6 Ml+M;) RE3C#4: 2i=:g=~ JV3C/4!"<6 #6 MB&! =6 !,<6 :]=2'< AMD MB&!,<6 ! ┆
0x4a900…4aa00 (74, 0, 9) Sector 4a0aff00061841 ┆J A 1 1 INTRODUCTION Performance requirements shall be mapped upon system components and checked against system capabilities. Performance requirements have been taken from section ┆
0x4aa00…4ab00 (74, 0, 10) Sector 4a0bff00061841 ┆J A3.4.1 of the CPS/210/SYS/0001: All sections until 3.4.1.6 (included) and 3.4.1.8. Section 2 will list all requirements in the form in which they shall be checked against the system and the system components involved in each case: - Throughput re┆
0x4ab00…4ac00 (74, 0, 11) Sector 4a0cff00061841 ┆J Aquirements: Performance calculations shall be based on busy hour figures except for incoming messages until first storage and outgoing message from release (included) until dispatch for external channels, in these exceptional cases, the busy minute ┆
0x4ac00…4ad00 (74, 0, 12) Sector 4a0dff00061841 ┆J Atraffic shall be considered as well (throughput only). - Timing requirements: These requirements are stated in CPS/210/SYS/0001 as applicable for busy hour traffic only: This has not been specifically stated in each case but applies in general. ┆
0x4ad00…4ae00 (74, 0, 13) Sector 4a0eff00061841 ┆J A- Sizing requirements: These requirements are listed and treated in section 5.3 separately. In section 3 data for usage of CPU-time, number of accesses to disc, and character transfer on TDX and Channel system are collected for each function which┆
0x4ae00…4af00 (74, 0, 14) Sector 4a0fff00061841 ┆J A is addressed in section 2, thereby also listing data for system packages: The final data for system package resource consumption will provide the data necessary for a final performance estimate. However, the data collected in section 2 may also ┆
0x4af00…4b000 (74, 0, 15) Sector 4a00ff00061841 ┆J Abe taken as a set of requirements to the system packages: As long as the system packages do not exceed the resource consumption listed here, the estimated performance within the requirements shall hold. This is the approach which shall be followed┆
0x4b000…4b100 (75, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(75,0, 1), len=0xff, h3=41061841}, f00=»0618A «, f01=»CAMPS Perform. Report «, f02=»sdv «, f03=»FAH «, f04=»CPS/REP/001 «, f05=05-02-81 11:37, f06=» 2 «, f07=»44 «, f08=» 4894 «, f09=29-04-81 11:22, f10=» «, f11=»01 «, f12=» 15 «, f13=29-04-81 11:48, f14=06-05-81 13:02, f15=»0051A «, f16=» 98 «, f17=» 86 «, f18=»35 «, f19=» 1760 «, f20=»123380 «, f21=» «, f22=» «, f99=081072000110056610a10a80aaca1505000000000000013803e901df}
0x4b100…4b200 (75, 0, 1) Sector 4b026200061841 ┆K b A K K J J J I I I I H H H H H G G G G F F F F E E E D D D D C C C C B B A A A A A @ @ @ ? ? ? ? > > > = = < < ; ; : : 9 9 9 8 8 8 7 7 7 6 6 5 5 5 4 4 4 4 3 3 3 3 2 2 2 2 1 1 0 0 0 / / / / . . . - - j i k k k k ┆
0x4b200…4b300 (75, 0, 2) Sector 4b039500061841 ┆K A 1 CPS/REP/001 FAH/810403 # CAMPS PERFORMANCE REPORT CAMPS !<~ B%-!/=6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x4b300…4b400 (75, 0, 3) Sector 4b04ff00061841 ┆K A 1 TABLE OF CONTENTS 1 INTRODUCTION ................................. 2 MAPPING OF REQUIREMENTS ...................... 3 DATA COLLECTION FOR MODEL CALCULATIONS ..┆
0x4b400…4b500 (75, 0, 4) Sector 4b05ff00061841 ┆K A..... 4 MODEL SELECTION CONSIDERATION ................ 4.1 GENERAL MODEL LAYOUT AND MECHANISMS ...... 4.2 PU SYSTEM ................................ 4.2.1 Introduction .......................... 4.2.2 Time Sli┆
0x4b500…4b600 (75, 0, 5) Sector 4b06ff00061841 ┆K Acing .......................... 4.2.3 Multiserver Queuing ................... 4.2.4 Priority Queuing ...................... 4.2.5 CPU Time and Processor Bus Loading .... 4.2.6 Final Conclusions ..................... ┆
0x4b600…4b700 (75, 0, 6) Sector 4b07ff00061841 ┆K A 4.3 TDX SYSTEM ............................. 4.3.1 TDX System Load ....................... 4.3.2 Terminal Load ......................... 4.4 CHANNEL SYSTEM ........................... 4.5 DISC SYSTEM .......┆
0x4b700…4b800 (75, 0, 7) Sector 4a08ff00061841 ┆J A....................... 4.6 CONCLUSIVE MODEL CONSIDERATIONS .......... 5 PERFORMANCE CALCULATIONS ..................... 5.1 THROUGHPUT ............................... 5.2 RESPONSE TIMES ........................... ┆
0x4b800…4b900 (75, 0, 8) Sector 4b09ff00084341 ┆K CA READ OF BYTE WRITE OF BYTE NO. OF TDX 2 ┆
0x4b900…4ba00 (75, 0, 9) Sector 4b0ada00084341 ┆K Z CA READ 0.008 OF 1024 BYT WRITE 0.004 1 OF 512 BYTE TABLE 3-4 C 4:>=2A=Ms!:g=~ Jr4Mj2:g=~ B}4C75! ┆
0x4ba00…4bb00 (75, 0, 10) Sector 4b0bff00084341 ┆K CA 1 SUBSYSTEM: TEP FUNCTION: VDU PAGE PREPARATION BUSY HOUR TRAFFIC (WAR): 5 (Mult = 0.0014) 1 ┆
0x4bb00…4bc00 (75, 0, 11) Sector 4b0cff00084341 ┆K CA DIR- CHAN. TDX QUEUE ..... MSG FCTS. ... FILE TABLE ECT FCTS. FCTS. FCTS. CRE- OBT. FIELDS FCTS MANAG. TOTAL/SEC. ┆
0x4bc00…4bd00 (75, 0, 12) Sector 4b0dff00084341 ┆K CACPU R W R W R W CP ATE REF. R W M R W M R W M MS 20 2 1 2 2 1 CPU (ms) 0.48 ┆
0x4bd00…4be00 (75, 0, 13) Sector 4b0eff00084341 ┆K CA NO. OF DISC 2 1 READ 0.0042 2 2 WRITE 0.0056 ┆
0x4be00…4bf00 (75, 0, 14) Sector 4b0fff00084341 ┆K CA NO. OF CHAN. READ OF BYTE ┆
0x4bf00…4c000 (75, 0, 15) Sector 2d00ff00084341 ┆- CA WRITE OF BYTE NO. OF TDX 2 READ 0.0028 OF 1024 BYTE 1 ┆
0x4c000…4c100 (76, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(76,0, 1), len=0xff, h3=41084341}, f00=»0843A «, f01=»Skemaer Performance rep. «, f02=»sdv «, f03=»FAH «, f04=»CPS/REP/001 «, f05=30-03-81 15:41, f06=» «, f07=»05 «, f08=» 182 «, f09=29-04-81 08:17, f10=» «, f11=»00 «, f12=» 11 «, f13=29-04-81 08:18, f14=06-05-81 13:03, f15=»0051A «, f16=» 45 «, f17=» 2 «, f18=»34 «, f19=» 1432 «, f20=» 3060 «, f21=» «, f22=» «, f99=910056000110056610a10a00aa4a55050000000000000138035b01df}
0x4c100…4c200 (76, 0, 1) Sector 4c022d00084341 ┆L - CA L L K - , , + + + * * ) ( ( ' ' & & & % $ $ # # " " ! ! okument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG Oprettet / / : : S S┆
0x4c200…4c300 (76, 0, 2) Sector 4c03cd00084341 ┆L M CA 1 - # - CPS/REP/001 x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x4c300…4c400 (76, 0, 3) Sector 4c04ff00084341 ┆L CA 1 SUBSYSTEM: TEP FUNCTION: MSG. PREPARATION BUSY HOUR TRAFFIC (WAR): 15 (MULT = 0.0042) Separate validation of header and text: 5 PLAs, 0.1 AIG, 3 SIC. Send for release an┆
0x4c400…4c500 (76, 0, 4) Sector 4c05ff00084341 ┆L CAd send for coordination included. 1 DIR- CHAN. TDX ┆
0x4c500…4c600 (76, 0, 5) Sector 4c06ff00084341 ┆L CA QUEUE ..... MSG FCTS. ... FILE TABLE ECT FCTS. FCTS. FCTS. CRE- OBT. FIELDS FCTS MANAG. TOTAL/SEC. CPU R W R W R W CP ATE REF. R W M R W M R W M MS ┆
0x4c600…4c700 (76, 0, 6) Sector 4c07ff00084341 ┆L CA 100 2 1 2 2 1 5 1 8.1 CPU (ms) 4.7 NO. OF┆
0x4c700…4c800 (76, 0, 7) Sector 4b08ff00084341 ┆K CA DISC 1 1 8.1 READ 0.04 2 2 5 WRITE 0.04 NO. OF CHAN. ┆
0x4c800…4c900 (76, 0, 8) Sector aaaaaaaaaaaaaa ┆****************************************************************************************************************************************************************************************************************************************************************┆
[…0x7…]
