OctetView
0x00000…00100 (0, 0, 0) Sector 02764130323736 ┆ vA0276A ┆
0x00100…00200 (0, 0, 1) Sector 00000000000000 ┆ ┆
0x00200…00300 (0, 0, 2) Sector ff00c0fffffffc ┆ @ |x ~ ` ┆
0x00300…00306 (0, 0, 3) WangDocument {d00=0x31, d01=0x60, d02=0x41, ptr=(13,0, 8), d05=0x00}
0x00306…0030c WangDocument {d00=0x31, d01=0x75, d02=0x41, ptr=(27,0, 0), d05=0x00}
0x0030c…00312 WangDocument {d00=0x31, d01=0x98, d02=0x41, ptr=(62,0, 8), d05=0x00}
0x00312…00318 WangDocument {d00=0x32, d01=0x16, d02=0x41, ptr=(44,0, 8), d05=0x00}
0x00318…0031e WangDocument {d00=0x33, d01=0x26, d02=0x41, ptr=(29,0, 8), d05=0x00}
0x0031e…00320 00 00 ┆ ┆
0x00320…00340 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 ┆ ┆
[…0x5…]
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 86312020202020 ┆ 1 8 7 Q? > 7 | W d N N v <)&4'>( 1c5 & & ┆
0x00600…00700 (0, 0, 6) Sector 421c402600415b ┆B @& A[' X% % PO P ; 1uA M C g x g V W O B :#@ #D O 3175A g r < {C < { ; 5 b b bD K 8 9 : t yySy "E"F"G"N"O B ┆
0x00700…00800 (0, 0, 7) Sector 00000000000000 ┆ ┆
[…0x8…]
0x01000…01100 (1, 0, 0) WangDocumentBody
[…0x1…]
0x01200…01300 (1, 0, 2) Sector 00000000000000 ┆ ┆
[…0x5…]
0x01800…01900 (1, 0, 8) WangDocumentBody
[…0x1d…]
0x03600…03700 (3, 0, 6) Sector 0307ff00321341 ┆ 2 Astem records a log on abnormal conditions which may be extracted directly from each IDM system, the back end computer records a log on abnormal conditions and restarts precedures. From this the following information may be extracted: - communica┆
0x03700…03800 (3, 0, 7) Sector 0208ff00321341 ┆ 2 Ation failures to IDM systems (IDM number, start and end time, error code) - communication failures to host computers (host number, start and end time, error code) - per data base failure: - data base identification - error code -┆
0x03800…03900 (3, 0, 8) WangDocumentBody
[…0x4…]
0x03d00…03e00 (3, 0, 13) Sector 00000000000000 ┆ ┆
[…0x2…]
0x04000…04100 (4, 0, 0) WangDocumentBody
[…0x97…]
0x0d800…0d900 (13, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(13,0, 9), len=0xff, h3=41316041}, f00=»3160A «, f01=»S F S Architecture «, f02=»amn «, f03=»PEH «, f04=»Doc SFS/TN/001 «, f05=15-12-82 11:14, f06=» 4 «, f07=»56 «, f08=» 20681 «, f09=13-01-83 09:13, f10=» «, f11=»00 «, f12=» 18 «, f13=21-12-82 15:14, f14=10-10-83 16:20, f15=»0276A «, f16=» 33 «, f17=» 10 «, f18=»15 «, f19=» 520 «, f20=» 35155 «, f21=» «, f22=» «, f99=020010000110262710110480aaca1505000000000000014203a500df}
0x0d900…0da00 (13, 0, 9) WangDocumentBody
[…0x15…]
0x0ef00…0f000 (14, 0, 15) Sector 00000000000000 ┆ ┆
0x0f000…0f100 (15, 0, 0) WangDocumentBody
[…0xbf…]
0x1b000…1b100 (27, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(27,0, 1), len=0xff, h3=41317541}, f00=»3175A «, f01=»SEC. Fil. Architecture «, f02=»amn «, f03=»KFL «, f04=»general «, f05=17-12-82 13:29, f06=» 5 «, f07=»34 «, f08=» 43276 «, f09=10-10-83 14:15, f10=» «, f11=»00 «, f12=» 32 «, f13=23-12-82 15:15, f14=11-10-83 16:14, f15=»0276A «, f16=» 27 «, f17=» 11 «, f18=»11 «, f19=» 712 «, f20=» 48032 «, f21=» «, f22=» «, f99=110011100111362710110480aaca1505000000000000014203cf00df}
0x1b100…1b200 (27, 0, 1) WangDocumentBody
[…0x26…]
0x1d800…1d900 (29, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(29,0, 9), len=0xff, h3=41332641}, f00=»3326A «, f01=»SECURITY FILTER STUDY «, f02=»amn «, f03=»PEH «, f04=»MINUTES OF MEETING «, f05=31-01-83 14:41, f06=» 1 «, f07=»35 «, f08=» 10372 «, f09=09-02-83 12:53, f10=» «, f11=»09 «, f12=» 542 «, f13=09-02-83 13:17, f14=10-03-83 14:31, f15=»0276A «, f16=» 11 «, f17=» 2 «, f18=»03 «, f19=» 200 «, f20=» 11543 «, f21=» «, f22=» «, f99=110021000110052710110280aaca15050000000000000042033600df}
0x1d900…1da00 (29, 0, 9) WangDocumentBody
[…0xee…]
0x2c800…2c900 (44, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(44,0, 9), len=0xff, h3=41321641}, f00=»3216A «, f01=»ACCESS, TECHNICAL PROP. «, f02=»ja «, f03=»alf «, f04=»OVERVIEW subpart E «, f05=30-12-82 14:33, f06=» «, f07=»40 «, f08=» 1775 «, f09= - - : , f10=» «, f11=» «, f12=» «, f13= - - : , f14=02-06-83 09:28, f15=»0276A «, f16=» 64 «, f17=» «, f18=»40 «, f19=» 800 «, f20=» 1775 «, f21=» «, f22=» «, f99=020010000110056610a10a80aaca15050000000000000142030a01df}
0x2c900…2ca00 (44, 0, 9) WangDocumentBody
[…0x9…]
0x2d300…2d400 (45, 0, 3) Sector 2d04ff00321641 ┆- 2 A 1 2. Please illustrate how the following queries would be coded in the system that you are proposing. Include simulation of any necessary file or data specification statements and a┆
0x2d400…2d500 (45, 0, 4) Sector 2d05ff00321641 ┆- 2 Assume that the response will be directed back to the inquirer's Video Display Unit (VDU). a. List all non-high school gruduates in Division 123 showing name, rank, serial number, years of service, and unit. It is assumed that airman and offi┆
0x2d500…2d600 (45, 0, 5) Sector 2d06ff00321641 ┆- 2 Acer data all are placed in one relation named "PERSONNEL" with the data elements shown in RFP figure C-11, and C-12 and that o non-high school graduates means ED-LVL B o division 123 means ORG-DET-NO = 123 o name means NAME o rank mea┆
0x2d600…2d700 (45, 0, 6) Sector 2d07ff00321641 ┆- 2 Ans the abbreviation from nomenclature table in RFP figure C-23 identified by GR-CURR o serial number means SSAN o years of service means 82-(year of ADSCD (name of ADSCY)) o unit means ORG-NR The conversion from GR-CURR to RANK is made ┆
0x2d700…2d800 (45, 0, 7) Sector 2c08ff00321641 ┆, 2 Aby a table lookup in the relation NOMENCLATURE with GR-CURR as key and RANK as target data. The query will then be phrased RANGE OF N IS NOMENCLATURE RANGE OF P IS PERSONNEL SHOW (P.NAME, N.RACK, P.SSAN, AGE = (82-P.ADSCY), P.ORG-NR) ┆
0x2d800…2d900 (45, 0, 8) WangDocumentBody
[…0x10f…]
0x3e800…3e900 (62, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(62,0, 9), len=0xff, h3=41319841}, f00=»3198A «, f01=»ACCESS, TECHNICAL DATA «, f02=»pan «, f03=»URH «, f04=»Fra 4.2.1 «, f05=22-12-82 14:39, f06=» 5 «, f07=»31 «, f08=» 21990 «, f09=29-12-82 10:59, f10=» «, f11=»10 «, f12=» 356 «, f13=28-12-82 11:47, f14=02-06-83 09:27, f15=»0276A «, f16=» 52 «, f17=» 6 «, f18=»26 «, f19=» 916 «, f20=» 23323 «, f21=» «, f22=» «, f99=020010000110052710110190aaca15050000000000000142031b01df}
0x3e900…3ea00 (62, 0, 9) WangDocumentBody
[…0x6…]
0x3f000…3f100 (63, 0, 0) Sector 3f01ff00319841 ┆? 1 Amit in 2 slots' time". The destination address (in this case: 1) remains in the frame. Timing signals are also added. Time X + 4 slots. All the devices look at the destination field of the current frame on the lower bus. In this example, device 1┆
0x3f100…3f200 (63, 0, 1) Sector 3f02ff00319841 ┆? 1 A realises that this frame is for itself, and accepts it. Various error checks are performed by the device and if all is well it extracts the useful data bits. If all is not well, it issues a special frame (when it gets a chance via the MUX number me┆
0x3f200…3f300 (63, 0, 2) Sector 3f03ff00319841 ┆? 1 Achanism) to the controller. This frame requests device 3 to re-transmit the data. This sequence is illustrated in figure 4.2.1.1.4-2. Note that the lower bus has continous transmission. If no device has recently taken up its option to transmit, ┆
0x3f300…3f400 (63, 0, 3) Sector 3f04ff00319841 ┆? 1 Athen the controller "invents" a frame and sends it along to a bogus device. Conversely, if a device tries to send out frames more frequently than the MUX table currently allows, it just has to wait. However, the MUX table may be altered by the contr┆
0x3f400…3f500 (63, 0, 4) Sector 3f058e00319841 ┆? 1 Aoller if the device makes a habit of trying to flood the bus. This mechanism is the Dynamic Bandwidth Allocation mentioned previously. ransmit on the upper bus at any time. The bandwidth allocation is determined by the Mux table which is changeab┆
0x3f500…3f600 (63, 0, 5) Sector 3f06ac00319841 ┆? , 1 A 1 DATA TRANSFER ON THE TDX BUS Figure 4.2.1.1.4-2 e system bandwidth is too small. The answer (ACK, NACK) is sent to the requesting d┆
0x3f600…3f700 (63, 0, 6) Sector 3f07ff00319841 ┆? 1 A 1 4.2.1.1.5 TDX Bus Host Interface (STI/TIA) In the range of TDX-devices the STI makes the high performance end interfacing of a CR80 minicomputer to the TDX-bus system. The STI i┆
0x3f700…3f800 (63, 0, 7) Sector 3e08ff00319841 ┆> 1 As a high bandwidth device which is able to interface to other devices connected to the TDX-bus. It may address 4096 logical lines through the TDX-system, and each line may have bandwidth allocated individually. The current implementation of STI-hand┆
0x3f800…3f900 (63, 0, 8) Sector 3f09ff00319841 ┆? 1 Aered, the device is perceived as not connected to the system. The upper bus switch-over feature is achieved by counting errorfree received frames from the upper bus (both frames destined to the controller and frames swapped to the lower bus) each ┆
0x3f900…3fa00 (63, 0, 9) Sector 3f0aff00319841 ┆? 1 Atime the Mux table has been read completely. If this count is less than 1:4 of the previous count, the bus is switched. This implies that one device may be removed every 1.28 sec. without changing buses, but removing a number of devices instantly ca┆
0x3fa00…3fb00 (63, 0, 10) Sector 3f0b4f00319841 ┆? O 1 Auses a switch of upper buses. FIG. 4.2.1.1.2-1 TDX FRAME LAYOUTthrough CR80 host-to-host suprabus. er Handling .............. 4.2.2.1.5.5 Disk Integrity ............. 4.2.2.1.5.5.1 Security ............... ┆
0x3fb00…3fc00 (63, 0, 11) Sector 3f0cff00319841 ┆? 1 A 1 4.2.1.1.4 TDX Bus Data Transfer In the following is given an example of a data transfer between devices on a TDX bus shown in figure 4.2.1.1.4-1. Figure 4.┆
0x3fc00…3fd00 (63, 0, 12) Sector 3f0dff00319841 ┆? 1 A2.1.1.4-1 TDX-bus Let us suppose that device 3 wants to send some data to device 1. The sequence of events is as follows. Time X. The controller inserts a '3' into the MUX field of the frame currently passing through it. Time X + 1 slot. Dev┆
0x3fd00…3fe00 (63, 0, 13) Sector 3f0eff00319841 ┆? 1 Aice 3 notices its own address (3) as a MUX number on the lower bus, so it prepares itself for transmission of a frame. Time X + 2 slots. Device 3 generates and transmits a frame containing 128 bits of useful data and a '1' in the destination addr┆
0x3fe00…3ff00 (63, 0, 14) Sector 3f0fec00319841 ┆? l 1 Aess field. This frame is transmitted on the upper bus. Meanwhile, as always, one frame is being processed by the controller and another frame is transmitted on the lower bus and is accepted by the device that it is addressed to. 0 (the Controller ┆
0x3ff00…40000 (63, 0, 15) Sector 3f00ff00319841 ┆? 1 A 1 Time X + 3 slots. Data from device 3 has arrived at the controller. The controller adds a MUX number to the frame. This is a message to some other device that means "you may trans┆
0x40000…40100 (64, 0, 0) Sector 4001ff00319841 ┆@ 1 Aidth to a given TDX device (BW-request). The synchronization is achieved by inserting as second byte in the HDLC frame on the lower bus, a Device No. taken from a Mux table that is scanned according to the speed level assigned to each device of th┆
0x40100…40200 (64, 0, 1) Sector 40021a00319841 ┆@ 1 Ae TDX system. minal Controllers ... 4.2.2.1.7.3.2 Lines .................. 4.2.2.1.7.3.3 Units .................. 1 ┆
0x40200…40300 (64, 0, 2) Sector 40036900319841 ┆@ i 1 A 1 Figure 4.2.1.1.3-1 TDX-Frame .... 4.2.2.1.9 Highlevel Operating System (HIOS) ....................... 4.2.2.1.10 System Generation Software ... 4┆
0x40300…40400 (64, 0, 3) Sector 4004ff00319841 ┆@ 1 A 1 All devices with their unique Device No. on the TDX-BUS look at the Mux byte, and if it is identical to its Device No., this device has the use of the upper bus, to transmit data a┆
0x40400…40500 (64, 0, 4) Sector 4005ff00319841 ┆@ 1 At the end of the frame on the lower bus, provided that the lower bus CRC check shows no errors. This ensures that only one device will transmit on the upper bus at any time. The bandwidth allocation is determined by the Mux table which is changeab┆
0x40500…40600 (64, 0, 5) Sector 4006ff00319841 ┆@ 1 Ale (dynamic). A request for a changed bandwidth to a specified device received on the upper bus is accepted if the system bandwidth is large enough or reflected if the system bandwidth is too small. The answer (ACK, NACK) is sent to the requesting d┆
0x40600…40700 (64, 0, 6) Sector 4007ff00319841 ┆@ 1 Aevice, when a free time slice occurs on the lower bus. The dummy Device No.FF (which is inserted in the MUX table, to allow the Controller access to the lower bus in the following frame) has a minimum bandwidth on 100 bit/sec. giving a free time slo┆
0x40700…40800 (64, 0, 7) Sector 3f08ff00319841 ┆? 1 At to answers at least every 1.28 sec. The diagnostic information is collected by polling each device connected to the system. If an answer is not received within 4 scans in the Mux table, a retransmission is executed. After three requests not answ┆
0x40800…40900 (64, 0, 8) Sector 4009ff00319841 ┆@ 1 Aesign complies with the International Standards Organization's seven-level Open Systems Interconnection Reference Model. This facilitates the integration of the TDX-net with networks supplied by other manufacturers. 4.2.1.1.2 Network Configuratio┆
0x40900…40a00 (64, 0, 9) Sector 400aff00319841 ┆@ 1 An Each TDX bus configuration consists of: - a double twisted pair cable (bus) - a TDX-Controller - up to 140 I/O devices The I/O devices can be divided into: - CR80 host interfaces (up to 12) - serial link interfaces (up to 122) Individ┆
0x40a00…40b00 (64, 0, 10) Sector 400b7600319841 ┆@ v 1 Aual TDX buses are interconnected either through mutual host computers or through CR80 host-to-host suprabus. er Handling .............. 4.2.2.1.5.5 Disk Integrity ............. 4.2.2.1.5.5.1 Security ............... ┆
0x40b00…40c00 (64, 0, 11) Sector 400cff00319841 ┆@ 1 A 1 4.2.1.1.3 Functional Description A single or dualized TDX bus is monitored and controlled by the TDX Controller which performs the following tasks: - Synchronize communication o┆
0x40c00…40d00 (64, 0, 12) Sector 400dff00319841 ┆@ 1 An the upper bus by inserting a MUX-No. in the HDLC frame on the lower bus. - Answer a bandwidth request and allocate bandwidth according to the request. - Poll and appended devices to collect diagnostic information. - Communicate with a Watchd┆
0x40d00…40e00 (64, 0, 13) Sector 400eff00319841 ┆@ 1 Aog (in a dualized TDX Controller Configuration). - Select one of two upper buses to optimize performance in a dualized bus system. The TDX Controller outputs a continous bitstream of 1.8432 Mbit/Sec. on the lower bus. This stream is organized in┆
0x40e00…40f00 (64, 0, 14) Sector 400fff00319841 ┆@ 1 A frames of 288 bits each, 6400 per second. All frames received from the "upper" bus are transmitted on the "lower" bus delayed one frame. Only if the CRC of a received frame is not correct or if the frame is destined to Host No. 0 (the Controller ┆
0x40f00…41000 (64, 0, 15) Sector 4000ff00319841 ┆@ 1 Aitself), the frame will not be swapped to the transmitter buffer. When a received frame is distined to host No. 0, it is loaded to the controller processor which is managing the Mux table. The received frame may contain a request for a changed bandw┆
0x41000…41100 (65, 0, 0) Sector 4101ff00319841 ┆A 1 A 4.2.2.1.7.1 Transfer of I/O Data ....... 4.2.2.1.7.1.1 File Mode .............. 4.2.2.1.7.1.2 Communication Mode ..... 4.2.2.1.7.2 User Handling .............. 4.2.2.1.7.3 Hardware Categories ........ ┆
0x41100…41200 (65, 0, 1) Sector 4102ff00319841 ┆A 1 A 4.2.2.1.7.3.1 Terminal Controllers ... 4.2.2.1.7.3.2 Lines .................. 4.2.2.1.7.3.3 Units .................. 1 ┆
0x41200…41300 (65, 0, 2) Sector 4103ff00319841 ┆A 1 A 4.2.2.1.8 System Initialization .......... 4.2.2.1.9 Highlevel Operating System (HIOS) ....................... 4.2.2.1.10 System Generation Software ... 4┆
0x41300…41400 (65, 0, 3) Sector 4104ff00319841 ┆A 1 A.2.2.1.11 Diagnostic Programs .......... 4.2.2.1.11.1 Off-line Diagnostic Programs .................. 4.2.2.1.11.2 On-Line Diagnostic Programs .................. 1 ┆
0x41400…41500 (65, 0, 4) Sector 4105ff00319841 ┆A 1 A 4.2.2.3 Language Processors ................ 4.2.2.4 General Utilities .................. 4.2.2.10 Statistics ......┆
0x41500…41600 (65, 0, 5) Sector 41065000319841 ┆A P 1 A.................. 4.2.2.11 Optical Character Reader ......... 4.2.1.1.5 TDX Bus Host Interface (STI/TIA) 4.2.1.1.6 TDX Bus Terminal Adapter ....... 4.2.1.2 Long-Haul Communication Network Interface .....┆
0x41600…41700 (65, 0, 6) Sector 4107ff00319841 ┆A 1 A 1 4.2.1 Communication software 4.2.1.1 Local Area Network 4.2.1.1.1 Network Topology The Local Area Network topology is based on a star mesk of individually dualized, time div┆
0x41700…41800 (65, 0, 7) Sector 4008ff00319841 ┆@ 1 Aision multiplexed TDX buses. Each TDX bus is via a front-end processor (STI) connected to a dualized CR80 host computer. Communica- tion between individual TDX buses is established through the connected CR80 host computer. The TDX local network d┆
0x41800…41900 (65, 0, 8) Sector 4109ff00319841 ┆A 1 A....... 4.2.2.1.3.6 Processing Unit Management . 4.2.2.3.7 Transport Mechanisms ........... 4.2.2.3.7.1 Basic Transport Service .... 4.2.2.3.7.2 Basic Datagram Service ..... 4.2.2.1.4 DAMOS Inpu┆
0x41900…41a00 (65, 0, 9) Sector 410aff00319841 ┆A 1 At/Output ............. 4.2.2.1.5 File Management System ......... 4.2.2.1.5.1 Device and Volume Handling . 4.2.2.1.5.2 Directories ................ 4.2.2.1.5.3 Files ...................... 4.2.┆
0x41a00…41b00 (65, 0, 10) Sector 410bff00319841 ┆A 1 A2.1.5.3.1 File Types ............. 4.2.2.1.5.3.2 File Commands .......... 4.2.2.1.5.4 User Handling .............. 4.2.2.1.5.5 Disk Integrity ............. 4.2.2.1.5.5.1 Security ............... ┆
0x41b00…41c00 (65, 0, 11) Sector 410c6b00319841 ┆A k 1 A 4.2.2.1.5.5.2 Redundant Disks ........ 4.2.2.1.5.5.3 Bad Sectors ............ side: (Sletter) (S]ger) (Udf]rer) Inds`t hvilket? Slette hvilket? Flytte hvilket? Kopiere hvilket? Bytte hvilket? Bytte med? S]ge hvilket? ┆
0x41c00…41d00 (65, 0, 12) Sector 410dff00319841 ┆A 1 A 1 4.2.2.1.5.6 Access Methods ............. 4.2.2.1.5.6.1 Unstructured Acces┆
0x41d00…41e00 (65, 0, 13) Sector 410eff00319841 ┆A 1 As .... 4.2.2.1.5.6.2 Indexed Sequential Access ................. 4.2.2.1.6 Magnetic Tape File Management System ......................... 1 ┆
0x41e00…41f00 (65, 0, 14) Sector 410fff00319841 ┆A 1 A 4.2.2.1.6.1 Device functions ........... 4.2.2.1.6.2 Volume functions ........... 4.2.2.1.6.3 File functions ............. 4.┆
0x41f00…42000 (65, 0, 15) Sector 4100ff00319841 ┆A 1 A2.2.1.6.4 Record functions ........... 1 4.2.2.1.7 Terminal Management System ..... ┆
0x42000…42100 (66, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(66,0, 1), len=0xff, h3=41319841}, f00=»3198A «, f01=»ACCESS, TECHNICAL DATA «, f02=»pan «, f03=»URH «, f04=»Fra 4.2.1 «, f05=22-12-82 14:39, f06=» 5 «, f07=»31 «, f08=» 21990 «, f09=29-12-82 10:59, f10=» «, f11=»10 «, f12=» 328 «, f13=28-12-82 11:47, f14=16-03-83 15:03, f15=»0276A «, f16=» 52 «, f17=» 6 «, f18=»26 «, f19=» 1140 «, f20=» 23295 «, f21=» «, f22=» «, f99=020010000110052710110190aaca15050000000000000142031b01df}
0x42100…42200 (66, 0, 1) Sector 42023400319841 ┆B 4 1 A B B A A @ @ @ ? ? ? ? > > > > = = = < < ; ; ; : : 9 9 9 9 8 8 8 8 7 7 7 6 6 5 5 4 4 4 3 3 3 2 2 2 1 1 1 0 tarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLD ANSLSL AKTIVITET DATO TID ANV.TID ANSLD ANSLSLD ANSLSLD ANSLSLSLD ANSLSLSLSL┆
0x42200…42300 (66, 0, 2) Sector 4203e300319841 ┆B c 1 A 1 3198A ACCESS SYS/1983-01-25 PART II - TECHNICAL DATA Page # #<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x42300…42400 (66, 0, 3) Sector 4204ff00319841 ┆B 1 A 1 TABLE OF CONTENTS 1 ┆
0x42400…42500 (66, 0, 4) Sector 4205ff00319841 ┆B 1 A 4.2.1 Communication Software ................. 4.2.1.1 Local Area Network ................. 4.2.1.1.1 Network Topology ............... 4.2.1.1.2 Network Configuration .......... 4.2.1.1.3 Functional Descri┆
0x42500…42600 (66, 0, 5) Sector 4206ff00319841 ┆B 1 Aption ......... 4.2.1.1.4 TDX Bus Data Transfer .......... 4.2.1.1.5 TDX Bus Host Interface (STI/TIA) 4.2.1.1.6 TDX Bus Terminal Adapter ....... 4.2.1.2 Long-Haul Communication Network Interface .....┆
0x42600…42700 (66, 0, 6) Sector 4207ff00319841 ┆B 1 A..................... 4.2.2.1 Operating System ................... 4.2.2.1.1 Overview of DAMOS Operational Software ....................... 4.2.2.1.2 Security ....................... 4.2.2.1.3 Kerne┆
0x42700…42800 (66, 0, 7) Sector 4108ff00319841 ┆A 1 Al ......................... 4.2.2.1.3.1 Resource Management ........ 4.2.2.1.3.2 Process Management 4.2.2.1.3.3 Memory Management 4.2.2.1.3.4 Process Communication ...... 4.2.2.1.3.5 CPU Management ......┆
0x42800…42900 (66, 0, 8) Sector 00000000000000 ┆ ┆
[…0xa7…]
