OctetView
0x00000…00100 (0, 0, 0) Sector 02754130323735 ┆ uA0275A ┆
0x00100…00200 (0, 0, 1) Sector 00000000000000 ┆ ┆
0x00200…00300 (0, 0, 2) Sector ff00c0fffffff8 ┆ @ x p x ` ┆
0x00300…00306 (0, 0, 3) WangDocument {d00=0x31, d01=0x81, d02=0x41, ptr=(52,0, 8), d05=0x00}
0x00306…0030c WangDocument {d00=0x32, d01=0x23, d02=0x41, ptr=( 2,0, 8), d05=0x00}
0x0030c…00312 WangDocument {d00=0x32, d01=0x45, d02=0x41, ptr=(65,0, 8), d05=0x00}
0x00312…00318 WangDocument {d00=0x32, d01=0x63, d02=0x41, ptr=(61,0, 8), d05=0x00}
0x00318…0031e WangDocument {d00=0x32, d01=0x64, d02=0x41, ptr=(59,0, 8), d05=0x00}
0x0031e…00320 32 64 ┆2d┆
0x00320…00340 41 3b 08 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 ┆A; ┆
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 86312020202020 ┆ 1 8 8 7 Q? > 7 | Z d N 0u v <.&4'>( 1c5 & & ┆
0x00600…00700 (0, 0, 6) Sector 421c402600415b ┆B @& A[' G X% % PO P ; 2EA ? C g x g V WD O 8 :W W ) 3245A g r < {C < { ; 5 p! p pv * 9 8 : t xZy# ^0 ^4 ┆
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
[…0xf…]
0x02800…02900 (2, 0, 8) WangDocumentHead {hdr=WangSectHead {next=( 2,0, 9), len=0xff, h3=41322341}, f00=»3223A «, f01=»ACCESS, Maintenance Req. «, f02=»ja «, f03=»PM «, f04=»Ej slet «, f05=05-01-83 13:26, f06=» 1 «, f07=»22 «, f08=» 11676 «, f09=13-04-83 13:42, f10=» «, f11=»07 «, f12=» 61 «, f13=13-01-83 10:01, f14=02-06-83 09:53, f15=»0275A «, f16=» 5 «, f17=» 2 «, f18=»04 «, f19=» 76 «, f20=» 12161 «, f21=» «, f22=» «, f99=020010000110052710110390aa8a37040000000000000042031a00df}
0x02900…02a00 (2, 0, 9) WangDocumentBody
[…0xb…]
0x03500…03600 (3, 0, 5) Sector 00000000000000 ┆ ┆
[…0x2…]
0x03800…03900 (3, 0, 8) WangDocumentBody
[…0x6b…]
0x0a400…0a500 (10, 0, 4) Sector 0a05ff00324541 ┆ 2EAsion of external user-id into IDM user/host-id. A control process reads the transaction-log to check that the IDM systems are both running, and uses it for sysnchronization of the tow IDM systems after breakdown; see 7. above. The IDM system nmai┆
0x0a500…0a600 (10, 0, 5) Sector 0a06ff00324541 ┆ 2EAntains the data dictionary automatically as changes are made in contents of tuples, relations, indices and in the physical position of data. Any reference to data is checked for user access permission and the data dictionary is used to reach the dat┆
0x0a600…0a700 (10, 0, 6) Sector 0a07c000324541 ┆ @ 2EAa. For recovery and audit purposes, the transaction log, the check points and the database dumps are established if so requested. (Ref. IDM Software Reference Manual page 3-3, part 3.2). o user id of relation's owner (creator) o internal relatio┆
0x0a700…0a800 (10, 0, 7) Sector 0908ff00324541 ┆ 2EA 1 11. Describe the capabilities and techniques used to expand/contract records, create/delete relationships, and any other dynamic restructuring functions available in your DBMS. Des┆
0x0a800…0a900 (10, 0, 8) WangDocumentBody
[…0x29f…]
0x34800…34900 (52, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(52,0, 9), len=0xff, h3=41318141}, f00=»3181A «, f01=»ACCESS, TECHNICAL PROP. «, f02=»amn «, f03=»ALF «, f04=»PART II Subpart D «, f05=20-12-82 09:57, f06=» 17 «, f07=»44 «, f08=» 73103 «, f09=15-03-83 14:02, f10=» «, f11=»52 «, f12=» 1867 «, f13=15-03-83 14:00, f14=17-10-83 10:51, f15=»0275A «, f16=» 92 «, f17=» 39 «, f18=»20 «, f19=» 1884 «, f20=»148296 «, f21=» «, f22=» «, f99=190098000110462710110290aaca17040000000000000142033502df}
0x34900…34a00 (52, 0, 9) WangDocumentBody
[…0x6b…]
0x3b500…3b600 (59, 0, 5) Sector 00000600326441 ┆ 2dA ┆
0x3b600…3b700 (59, 0, 6) Sector 3b07ff00318141 ┆; 1 Ater. The X-net local network design complies with the International Standards Organization's seven-level Open Systems Interconnection Reference Model. This facilitates the integration of the X-Net with networks supplied by other manufacturers. N┆
0x3b700…3b800 (59, 0, 7) Sector 3a08ff00318141 ┆: 1 Aetwork Configuration Each X-Net bus configuration consists of: - a double twisted pair cable (bus) - a X-net-Controller - up to 140 I/O devices The I/O devices can be divided into: - CR80 host interfaces (up to 12) - serial link interface┆
0x3b800…3b900 (59, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(59,0, 9), len=0xff, h3=41326441}, f00=»3264A «, f01=»ACCESS «, f02=»amn «, f03=»LU «, f04=»PART II - Subpart I «, f05=18-01-83 10:59, f06=» «, f07=»05 «, f08=» 138 «, f09=02-06-83 09:50, f10=» «, f11=»01 «, f12=» 5 «, f13=26-05-83 19:20, f14=02-06-83 09:54, f15=»0275A «, f16=» 5 «, f17=» «, f18=»21 «, f19=» 24 «, f20=» 521 «, f21=» «, f22=» «, f99=400010000110462710110280aaca15050000000000000142030d00df}
0x3b900…3ba00 (59, 0, 9) WangDocumentBody
[…0x11…]
0x3cb00…3cc00 (60, 0, 11) Sector 3c0cff00318141 ┆< 1 Aralized error reporting - a data transfer mechanism - a PU service module The File Management System (FMS) implements files on disks. The FMS provides functions for manipulating and accessing files and acts as an operating system for a group ┆
0x3cc00…3cd00 (60, 0, 12) Sector 3c0dff00318141 ┆< 1 Aof disks units. The FMS may exist in several incarnations in each PU where each incarnation controls its own devices. The Terminal Management System (TMS) is similar to the FMS. It provides functions for manipulating and accessing communication ┆
0x3cd00…3ce00 (60, 0, 13) Sector 3c0eff00318141 ┆< 1 Alines and terminals including line printers. The objects accessed via the TMS are called units. A unit may be an interactive terminal, a line printer or a virtual circuit. The TMS acts as an operating system for a group of communication devices a┆
0x3ce00…3cf00 (60, 0, 14) Sector 3c0f3900318141 ┆< 9 1 Attached via LTUs, LTUXs or a parallel controller. DAMOS OPERATIONAL SUPPORT SOFTWARE ┆
0x3cf00…3d000 (60, 0, 15) Sector 3c00ff00318141 ┆< 1 A 1 The TMS may exist in several incarnations in each PU, each incarnation controlling its own devices. The Magnetic Tape File Management System handles files on magnetic tape units. ┆
0x3d000…3d100 (61, 0, 0) WangDocumentBody
[…0x7…]
0x3d800…3d900 (61, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(61,0, 9), len=0xff, h3=41326341}, f00=»3263A «, f01=»ACCESS «, f02=»amn «, f03=»LU «, f04=»PART I - Subpart D «, f05=18-01-83 10:39, f06=» «, f07=»19 «, f08=» 2234 «, f09=15-03-83 13:30, f10=» «, f11=»02 «, f12=» 72 «, f13=15-03-83 09:44, f14=02-06-83 09:54, f15=»0275A «, f16=» 4 «, f17=» «, f18=»28 «, f19=» 52 «, f20=» 2597 «, f21=» «, f22=» «, f99=400030000110462710110280aaca15050000000000000142031300df}
0x3d900…3da00 (61, 0, 9) WangDocumentBody
[…0x3e…]
0x41800…41900 (65, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(65,0, 9), len=0xff, h3=41324541}, f00=»3245A «, f01=»ACCESS «, f02=»amn «, f03=»BHB «, f04=»PART II SUBPART B «, f05=12-01-83 10:44, f06=» 9 «, f07=»14 «, f08=» 54627 «, f09=15-03-83 13:31, f10=» «, f11=»07 «, f12=» 244 «, f13=14-03-83 14:12, f14=03-11-83 12:46, f15=»0275A «, f16=» 72 «, f17=» 18 «, f18=»25 «, f19=» 1288 «, f20=» 83655 «, f21=» «, f22=» 0 «, f99=930073000110462710110290aaca15050000000000000042038c01df}
0x41900…41a00 (65, 0, 9) WangDocumentBody
[…0x6…]
0x42000…42100 (66, 0, 0) Sector 4201ff41324541 ┆B A2EA3245A ACCESS amn BHB PART II SUBPART B 12 01 83 10 44 9 14 54627 15 03 83 13 31 04 152 14 03 83 14 12 02 06 83 09 53 0275A 72 18 22 1288 83563 0 s F' *J B _┆
0x42100…42200 (66, 0, 1) Sector 42024800324541 ┆B H 2EA B B B A A A A A A @ @ @ @ ? ? ? ? > > > < < : : : 9 9 8 8 8 7 7 6 6 6 5 5 : Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DADADADADA┆
0x42200…42300 (66, 0, 2) Sector 42038e00324541 ┆B 2EA 1 REV. 1 1983-03-18 =6'C*-:!<~ B%-!/=6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x42300…42400 (66, 0, 3) Sector 4204b400324541 ┆B 4 2EA 1 3245A ACCESS - PART II TECHNICAL PROPOSAL SYS/1983-01-25 SUBPART B - SYSTEM CHARACTERISTICS Page # I! <6 M8)I!h=6 ! =6 M")IM"):g=~ J /:h=2>=M?.Mj': < Zn.C / E*:=k 0wM% !;=4C┆
0x42400…42500 (66, 0, 4) Sector 4205ff00324541 ┆B 2EA 1 A C C E S S AUTOMATED COMMAND AND CONTROL EXECUTIVE SUPPORT SYSTEM PART II TECHNICAL PROPOSAL SUBPART B SYSTEM CHARACTERISTICS DOC. NO. ACC/8004/PRP/001 ISSUE 1 ┆
0x42500…42600 (66, 0, 5) Sector 4206ff00324541 ┆B 2EA SUBMITTED TO: AIR FORCE COMPUTER AQUISITION CENTER (AFCC) DIRECTORATE OF CONTRACTING/PK HANSCOM AFB MA 01731 U S A IN RESPONSE TO: SOLICITATION NO. F19630-82-R-001 AFCAC PROJECT 211-81 PREPARED BY: CHRISTIAN ROVSING A/S ┆
0x42600…42700 (66, 0, 6) Sector 4207ff00324541 ┆B 2EASYSTEMS DIVISION LAUTRUPVANG 2 2750 BALLERUP DENMARK c Christian Rovsing A/S - 1982 This document contains information proprietary to Christian Rovsing A/S. The information, whether in the form of text, schematics, tables, drawi┆
0x42700…42800 (66, 0, 7) Sector 4108ff00324541 ┆A 2EAngs or illustrations, must not be duplicated or used for purposes other than evaluation, or disclosed outside the recipient company or organisation without the prior, written permission of Christian Rovsing A/S. This restriction does not limit the┆
0x42800…42900 (66, 0, 8) Sector 4209ff41324541 ┆B A2EA3245A ACCESS amn BHB PART II SUBPART B 12 01 83 10 44 9 14 54627 15 03 83 13 31 02 132 14 03 83 14 12 13 04 83 14 07 0275A 72 18 20 1288 83543 0 s F' *J B _┆
0x42900…42a00 (66, 0, 9) Sector 420a4800324541 ┆B H 2EA B B B B B B B A A A @ @ @ @ @ ? ? ? > > > > : : : 9 9 8 8 8 7 7 6 6 6 5 5 : Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DADADADADA┆
0x42a00…42b00 (66, 0, 10) Sector 420b8e00324541 ┆B 2EA 1 REV. 1 1983-03-18 =6'C*-:!<~ B%-!/=6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x42b00…42c00 (66, 0, 11) Sector 420cb400324541 ┆B 4 2EA 1 3245A ACCESS - PART II TECHNICAL PROPOSAL SYS/1983-01-25 SUBPART B - SYSTEM CHARACTERISTICS Page # I! <6 M8)I!h=6 ! =6 M")IM"):g=~ J /:h=2>=M?.Mj': < Zn.C / E*:=k 0wM% !;=4C┆
0x42c00…42d00 (66, 0, 12) Sector 420dff00324541 ┆B 2EA 1 A C C E S S AUTOMATED COMMAND AND CONTROL EXECUTIVE SUPPORT SYSTEM PART II TECHNICAL PROPOSAL SUBPART B SYSTEM CHARACTERISTICS DOC. NO. ACC/8004/PRP/001 ISSUE 1 ┆
0x42d00…42e00 (66, 0, 13) Sector 420eff00324541 ┆B 2EA SUBMITTED TO: AIR FORCE COMPUTER AQUISITION CENTER (AFCC) DIRECTORATE OF CONTRACTING/PK HANSCOM AFB MA 01731 U S A IN RESPONSE TO: SOLICITATION NO. F19630-82-R-001 AFCAC PROJECT 211-81 PREPARED BY: CHRISTIAN ROVSING A/S ┆
0x42e00…42f00 (66, 0, 14) Sector 420fff00324541 ┆B 2EASYSTEMS DIVISION LAUTRUPVANG 2 2750 BALLERUP DENMARK c Christian Rovsing A/S - 1982 This document contains information proprietary to Christian Rovsing A/S. The information, whether in the form of text, schematics, tables, drawi┆
0x42f00…43000 (66, 0, 15) Sector 4200ff00324541 ┆B 2EAngs or illustrations, must not be duplicated or used for purposes other than evaluation, or disclosed outside the recipient company or organisation without the prior, written permission of Christian Rovsing A/S. This restriction does not limit the┆
0x43000…43100 (67, 0, 0) Sector 4301ff00324541 ┆C 2EA 1 1 1. CR ACCESS 1/CPU EQUIPMENT ITEM DESCRIPTION QTY 1 CR80 WATCHDOG MODULE 12 CR8066M/010AB/00 LTU,WD 3 13 ┆
0x43100…43200 (67, 0, 1) Sector 4302ff00324541 ┆C 2EACR8076M/010--/00 WCA 3 14 CR8089M/010--/00 CCA 6 15 CR8091M/000--/00 CCBA 3 2 CR80 PROCESSOR UNIT MODULES 21 CR8003M/040PC/00 CPU/CACHE 12 22 CR8016M/512C/00 512K RAM 12 25 CR8020M/000PC/00 MAP 6 26 CR8071M/010--/00 MIA 6 27 CR8021M/010-C/01 S┆
0x43200…43300 (67, 0, 2) Sector 4303ff00324541 ┆C 2EATI 20 28 CR8073M/010--/00 TIA 16 29 CR8072M/010--/00 SBA 24 3 CR80 CHANNEL UNIT MODULES 31 CR8081M/010A-/00 CIA-A 5 32 CR8081M/010-B/00 CIA-B 5 33 CR8044M/041AB/02 DISC CTL/32K 10 34 CR8084M/010--/00 DCA 10 37 CR8066M/010AB/00 LTU,SYNC/16K 6 38 ┆
0x43300…43400 (67, 0, 3) Sector 4304ff00324541 ┆C 2EACR8082M/010--/00 LIA-N 6 39 CR8046M/040AB/00 PAR CTRL 3 3A CR8086M/010--/00 PCA 3 3C CR----M/-----/00 IEEE CTRL 2 3D CR----M/-----/00 IEEE CTRL AD 2 3B CR8045M/040AB/00 TAPE CTRL 3 TABLE 2.2-1 (1 of 5 Pages) EQUIPMENT LIST ACCE┆
0x43400…43500 (67, 0, 4) Sector 43051900324541 ┆C 2EASS, FIRST INCREMENT b) One Back-End Processor, which mainly supports the database. The 3 PE's are structured as a CR80 FATOM configuration specially modelled to meet the ACCESS requirements. Each ┆
0x43500…43600 (67, 0, 5) Sector 4306ff00324541 ┆C 2EA 1 3E CR8085M/010--//00 TCA 3 4 DATA BASE PROCESSOR 41 IDM 500 BASE SYSTEM 2 42 DATABASE ACCET 2 43 1 MBYTE MEMORY 2 44 DISK CONTROLLER 2 45 RACK MOUNT SLIDES 2 7 CR80 RACK, CR┆
0x43600…43700 (67, 0, 6) Sector 4307ff00324541 ┆C 2EAATES, ACCESSORIE 72 CR8101-/036--/00 RACK 36U 11 73 CR8102-/000--/00 RACK 18U 2 74 CR8106-/110-/00 MAINS FILTER 13 7D CR8107-/010--/00 PWR DIST PNL 22 7E CR8050M/010--/00 PWR SUPPLY 22 7G CR8125M/225PC/00 POU CRATE 6 7H CR8125M/425AB/00 CU CRATE ┆
0x43700…43800 (67, 0, 7) Sector 4208ff00324541 ┆B 2EA5 7J CR8105M/020--/00 FAN UNIT 11 7K CR8055M/020--/00 MBT 34 7L CR8211M/738--/00 DATA CH TERM 6 8 CR80 CABLES 81 CR8211M/030--/00 DATA CH. CAB 10 8H CR8201M/015--/00POWER CABLE 44 8J CR8215M/030--/00 SUPRABUS CAB 24 8K CR8215M/778--/00 SUPRABUS TE┆
0x43800…43900 (67, 0, 8) Sector 4309ff00324541 ┆C 2EAnction with CU #1 is the stand-by Processor The CU #1 is constructed to be a dualized unit, contained within one physical crate. Each I/O controller module is supported by the two independent data buses A and B. Each I/O controller module can be┆
0x43900…43a00 (67, 0, 9) Sector 430ad500324541 ┆C U 2EA accessed through both bus A and bus B, though it is only accessed through one bus at a time from the PU which has claimed access most recently. In the CU the power supply is completely dualized as well. bus is actively transmitting at a time. T┆
0x43a00…43b00 (67, 0, 10) Sector 430ba700324541 ┆C ' 2EA 1 FIG. 2.1.1-3 FRONT END PROCESSOR STRUCTURE l Adapters (XTA's). The XTA is a microprocessor-controlled unit. The application S/W is ┆
0x43b00…43c00 (67, 0, 11) Sector 430cb300324541 ┆C 3 2EA 1 FIG. 2.1.1-4 BACK-END AND DATABASE PROCESSOR STRUCTURE SUBPART B SYSTEM CHARACTERISTICS DOC. NO. ACC/8004/PRP/001 ISSUE 1 ┆
0x43c00…43d00 (67, 0, 12) Sector 430dff00324541 ┆C 2EA 1 2.2 CONFIGURATION A specific list of all items included in the HW configuration is provided in this section. Table 2.2-1 lists the equipment proposed for the first increment. T┆
0x43d00…43e00 (67, 0, 13) Sector 430eff00324541 ┆C 2EAhe table reflects the equipment items requested in the RFP, Table C-1. Table 2.2-2 lists the equipment proposed for augmentation as requested in the RFP, Table C-2 Table 2.2.-3 lists the equipment posposed for augmentation as requested in the RF┆
0x43e00…43f00 (67, 0, 14) Sector 430fff00324541 ┆C 2EAP, Table C-3 The equipment manufactured by Christian Rovsing A/S, i.e. the Processors and the X-Net, is described in subpart C of this Part of the Proposal (Part II) Characteristics for all the equipment proposed can be found in the appended tec┆
0x43f00…44000 (67, 0, 15) Sector 43005d00324541 ┆C ] 2EAhnical literature, which is listed in subpart A of this part of the proposal (Part II). required, this modem connection is established using an X-NET Communication Port link (XCP-link). The X-NET behind the XCP-link has its own controllers but is in┆
0x44000…44100 (68, 0, 0) Sector 4401ff00324541 ┆D 2EA fact considered a subbranch of the X-NET branch to which it is attached. The dualized buses are connected to the Front-End Processors through the Interface Adapter modules (TIA's). All modules described above are connected to the X-NET buses by┆
0x44100…44200 (68, 0, 1) Sector 4402ff00324541 ┆D 2EA an X-NET wall outlet (XWO). This XWO provides galvanic isolation from the bus and features protection to the bus for component failures in the attached modules, thus allowing the bus-communication to continue independent of single-point-failures. ┆
0x44200…44300 (68, 0, 2) Sector 4403ff00324541 ┆D 2EA If communication on an X-NET bus is made impossible due to H/W failure, communication is handed over to the dual X-NET bus. 2.1.1.4 Central Processors The Central Processors include 3 processing elements (PE's): a) Two Front-End Processors. Th┆
0x44300…44400 (68, 0, 3) Sector 44048600324541 ┆D 2EAese are mainly supporting the remote terminals connected through the X-NET and the terminals placed in the main computer room. s implemented using CR's unique X-NET concept. In the following the features and characteristics of the X-NET will be h┆
0x44400…44500 (68, 0, 4) Sector 4405ff00324541 ┆D 2EA 1 b) One Back-End Processor, which mainly supports the database. The 3 PE's are structured as a CR80 FATOM configuration specially modelled to meet the ACCESS requirements. Each ┆
0x44500…44600 (68, 0, 5) Sector 4406ff00324541 ┆D 2EAPE is completely dualized in order to create a Processor with a very high reliability. FIG's 2.1.1-3 and 2.1.1-4 are showing the structure of the two types of PE's. When a Front-End Processor is in normal operation, Processor Unit #1 (PU #1) and┆
0x44600…44700 (68, 0, 6) Sector 4407ff00324541 ┆D 2EA Channel Unit #1 (CU #1) are operating as one processor serving traffic on two X-NET branches. PU #2/CU #2 are operating as another processor serving traffic on two other X-NET branches. Each of the two processors has the capacity to handle all 4 ┆
0x44700…44800 (68, 0, 7) Sector 4308ff00324541 ┆C 2EAX-NET branches, and in normal operation the one is stand-by for the other. In the Back-End Processor the dualization concept is a little different. In normal operation PU #1 in conjunction with CU #1 is the active Processor, while PU #0 in conju┆
0x44800…44900 (68, 0, 8) Sector 4409ff00324541 ┆D 2EAus a dualized X-Net bus uses 2 pairs of cables. The units and elements included in one dualized X-NET branch are shown on FIG. 2.1.1-2. In the proposed system, data is transferred between each remote terminal and one Processor Unit (PU) within a┆
0x44900…44a00 (68, 0, 9) Sector 440aff00324541 ┆D 2EA Front-End Processor by the one X-Net bus which is active. The other X-Net bus is connecting the remote terminal to the other PU within the same Front-End Processor. This bus is in stand-by mode. Only one bus is actively transmitting at a time. T┆
0x44a00…44b00 (68, 0, 10) Sector 440bff00324541 ┆D 2EAwo dualized Front-end Processors are in this application hosts for all remote terminals. The remote terminals are connected to the X-NET buses by X-NET Terminal Adapters (XTA's). The XTA is a microprocessor-controlled unit. The application S/W is ┆
0x44b00…44c00 (68, 0, 11) Sector 440c4c00324541 ┆D L 2EAdown-line loaded from the Front-End Processors through the X-Net bus. A C C E S S AUTOMATED COMMAND AND CONTROL EXECUTIVE SUPPORT SYSTEM PART II TECHNICAL PROPOSAL SUBPART B SYSTEM CHARACTERISTICS DOC. NO. ACC/8004/PRP/001 ISSUE 1 ┆
0x44c00…44d00 (68, 0, 12) Sector 440da300324541 ┆D # 2EA 1 FIG. 2.1.1-2 X-NET STRUCTURE AND UNITS ITATION NO. F19630-82-R-001 AFCAC PROJECT 211-81 PREPARED BY: CHRISTIAN ROVSING A/S ┆
0x44d00…44e00 (68, 0, 13) Sector 440eff00324541 ┆D 2EA 1 Data is transferred serially between the remote terminal and the XTA. The transfer rate is up to 9.6 Kbps. The XTA is connected to both X-NET buses but as explained above it is┆
0x44e00…44f00 (68, 0, 14) Sector 440fff00324541 ┆D 2EA only communicating on one bus at a time. The traffic on the X-NET buses is controlled by the X-NET controller (XCT). The X-NET Amplifier and Branching Unit (XAB) are used for extending the bus-length and for creation of subbranches. When remo┆
0x44f00…45000 (68, 0, 15) Sector 4400ff00324541 ┆D 2EAte terminals are placed so far from the Front-End Processors that a modem connection is required, this modem connection is established using an X-NET Communication Port link (XCP-link). The X-NET behind the XCP-link has its own controllers but is in┆
0x45000…45100 (69, 0, 0) Sector 4501df00324541 ┆E _ 2EA 1 TABLE OF CONTENTS 2. SUBPART B - SYSTEM CHARACTERISTICS 2.1 SYSTEM OVERVIEW 2.2 CONFIGURATION 2.3 SYSTEM QUESTIONNAIRE RESPONSE &! =6 !,<6 :]=2'< AMD MB&!,<6 ! ┆
0x45100…45200 (69, 0, 1) Sector 4502ff00324541 ┆E 2EA 1 2.1 SYSTEM OVERVIEW 2.1.1 Hardware 2.1.1.1 Introduction In this section is provided a general overview of the H/W included in the proposed system. In subpart C of PART II,┆
0x45200…45300 (69, 0, 2) Sector 4503ff00324541 ┆E 2EA specifications and characteristics are given for each component of the proposed equipment. 2.1.1.2 General The two main elements of the system are the local area network and the central processors with the databasesystem, see FIG. 2.1.1-1. The┆
0x45300…45400 (69, 0, 3) Sector 4504ff00324541 ┆E 2EA local area network interfaces the system to the remote terminals. 2.1.1.3 X-NET, Local Area Network The local area network is implemented using CR's unique X-NET concept. In the following the features and characteristics of the X-NET will be h┆
0x45400…45500 (69, 0, 4) Sector 4505b700324541 ┆E 7 2EAighlighted in order to show how perfect the net fits this application. The X-NET bus is a serial bus. Data travels on the X-NET bus at a max. rate of 0.8192 Mbits per second. Fundet I brug nu Allerede p> systemdiskette ┆
0x45500…45600 (69, 0, 5) Sector 4506a200324541 ┆E " 2EA 1 FIG. 2.1.1-1 HARDWARE SYSTEM OVERVIEW ┆
0x45600…45700 (69, 0, 6) Sector 4507ff00324541 ┆E 2EA 1 In order to handle the required number of remote terminals, the network is divided into 8 branches. Each of these branches has a maximum data transfer rate of 0.8192 Mbps adding up┆
0x45700…45800 (69, 0, 7) Sector 4408ff00324541 ┆D 2EA to 8 x 0.8192 = 6.5536 Mbps. In order to meet the required functional availability, each branch is dualized, i.e. the branch contains 2 buses. Physically each bus in a non-dualized X-NET consists of a pair of cables running through the site. Th┆
0x45800…45900 (69, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(69,0, 9), len=0xff, h3=41324541}, f00=»3245A «, f01=»ACCESS «, f02=»amn «, f03=»BHB «, f04=»PART II SUBPART B «, f05=12-01-83 10:44, f06=» 9 «, f07=»14 «, f08=» 54627 «, f09=21-01-83 14:13, f10=» «, f11=»00 «, f12=» 10 «, f13=21-01-83 14:18, f14=24-01-83 13:29, f15=»0275A «, f16=» 72 «, f17=» 17 «, f18=»52 «, f19=» 1472 «, f20=» 81882 «, f21=» «, f22=» 0 «, f99=020033000210052710110290aaca15050000000000000042038401df}
0x45900…45a00 (69, 0, 9) Sector 450a4800324541 ┆E H 2EA E E E E E E D D D C C C C C B B B A A A A @ @ @ ? ? > > > : : : 9 9 : Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DADADADADA┆
0x45a00…45b00 (69, 0, 10) Sector 450bb400324541 ┆E 4 2EA 1 3245A ACCESS - PART II TECHNICAL PROPOSAL SYS/1983-01-25 SUBPART B - SYSTEM CHARACTERISTICS Page # I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x45b00…45c00 (69, 0, 11) Sector 450cff00324541 ┆E 2EA 1 A C C E S S AUTOMATED COMMAND AND CONTROL EXECUTIVE SUPPORT SYSTEM PART II TECHNICAL PROPOSAL SUBPART B SYSTEM CHARACTERISTICS DOC. NO. ACC/8004/PRP/001 ISSUE 1 ┆
0x45c00…45d00 (69, 0, 12) Sector 450dff00324541 ┆E 2EA SUBMITTED TO: AIR FORCE COMPUTER AQUISITION CENTER (AFCC) DIRECTORATE OF CONTRACTING/PK HANSCOM AFB MA 01731 U S A IN RESPONSE TO: SOLICITATION NO. F19630-82-R-001 AFCAC PROJECT 211-81 PREPARED BY: CHRISTIAN ROVSING A/S ┆
0x45d00…45e00 (69, 0, 13) Sector 450eff00324541 ┆E 2EASYSTEMS DIVISION LAUTRUPVANG 2 2750 BALLERUP DENMARK c Christian Rovsing A/S - 1982 This document contains information proprietary to Christian Rovsing A/S. The information, whether in the form of text, schematics, tables, drawi┆
0x45e00…45f00 (69, 0, 14) Sector 450fff00324541 ┆E 2EAngs or illustrations, must not be duplicated or used for purposes other than evaluation, or disclosed outside the recipient company or organisation without the prior, written permission of Christian Rovsing A/S. This restriction does not limit the┆
0x45f00…46000 (69, 0, 15) Sector 4500fd00324541 ┆E } 2EA recipient's right to use information contained in the document if such information is received from another source without restriction provided such source is not in breach of an obligation of confidentiality towards Christian Rovsing A/S. =!┆
0x46000…46100 (70, 0, 0) Sector 00000000000000 ┆ ┆
[…0x6f…]
