OctetView
0x00000…00100 (0, 0, 0) Sector 01574130313537 ┆ WA0157A ┆
0x00100…00200 (0, 0, 1) Sector 00000000000000 ┆ ┆
0x00200…00300 (0, 0, 2) Sector ff00fcffffffff ┆ | p| @ ┆
0x00300…00306 (0, 0, 3) WangDocument {d00=0x20, d01=0x12, d02=0x41, ptr=(29,0, 0), d05=0x00}
0x00306…0030c WangDocument {d00=0x20, d01=0x25, d02=0x41, ptr=(32,0, 0), d05=0x00}
0x0030c…00312 WangDocument {d00=0x20, d01=0x58, d02=0x41, ptr=(47,0, 8), d05=0x00}
0x00312…00318 WangDocument {d00=0x20, d01=0x64, d02=0x41, ptr=(47,0, 0), d05=0x00}
0x00318…0031e WangDocument {d00=0x20, d01=0x65, d02=0x41, ptr=(40,0, 0), d05=0x00}
0x0031e…00320 20 65 ┆ e┆
0x00320…00340 41 3c 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 ┆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 B 7 Q? > 7 " \ . ( d d N ~<) 0uH &4'>( 1c5 & & ┆
0x00600…00700 (0, 0, 6) Sector 421c402600415b ┆B @& A[' X% % PO P ; XA\ C g x g V WD O B : ! N 2058A g n < {C < { ; 8 b b bD 8 K : 9 8 ! t wyyy % " " # - FL" ┆
0x00700…00800 (0, 0, 7) Sector 00000000000000 ┆ ┆
[…0x8…]
0x01000…01100 (1, 0, 0) WangDocumentBody
[…0x5…]
0x01600…01700 (1, 0, 6) Sector 00000000000000 ┆ ┆
[…0x1…]
0x01800…01900 (1, 0, 8) WangDocumentBody
[…0x23…]
0x03c00…03d00 (3, 0, 12) Sector 030dff00205841 ┆ XA reloaded from the NCC. This is done by the command VARY NET, LOAD, parameters. In the parameter field the name of the node to be loaded is given. When the node has been reinitialized it is reactivated by VARY NET, ACT, major node name. - Trunk Fa┆
0x03d00…03e00 (3, 0, 13) Sector 030eff00205841 ┆ XAilure: All sessions using this trunk will be rerouted through alternative trunks. If anode becomes unreachable due to multiple trunk failures, the line defined in VTAM to connect that node to the Host is forced deactivated. This is provided with ┆
0x03e00…03f00 (3, 0, 14) Sector 030fff00205841 ┆ XAthe link-inoperative SNA request. A failing node or a failing trunk is always reported back to the network control center. The costs are not informed if the logical network configuration has not changed. 4.14.2.3 Host Access Synchronization upon ┆
0x03f00…04000 (3, 0, 15) Sector 0300ff00205841 ┆ XAHost Failure A lost subarea SNA request is sent to the other hosts. Sessions running between logical units and application programs in the failing host are lot. Both the VTAM tables and NCC tables are updated according to this event. The list of┆
0x04000…04100 (4, 0, 0) WangDocumentBody
[…0x5…]
0x04600…04700 (4, 0, 6) Sector 0407ff00205841 ┆ XAo Node failure o EMH failure o NCC failure 4.14.2.1 Node Failure If a node fails, its local network is excluded and the node is forced to its basic state by a CLEAR command. In this state, it can be dumped and reloaded remotely. The restart and┆
0x04700…04800 (4, 0, 7) Sector 0308ff00205841 ┆ XA following initialization follows the scheme from network initialization, except the state of the local network, can be synchronized with the state stored in the NCC at the time of node failure. A node failure causes all sessions passing through t┆
0x04800…04900 (4, 0, 8) WangDocumentBody
[…0x187…]
0x1d000…1d100 (29, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(29,0, 1), len=0xff, h3=41201241}, f00=»2012A «, f01=»Air Canada Proposal «, f02=»ut «, f03=»HBA «, f04=»DOC III Chapt. 8 «, f05=14-04-82 14:10, f06=» «, f07=»11 «, f08=» 298 «, f09=24-04-82 13:48, f10=» «, f11=»01 «, f12=» 23 «, f13=14-04-82 15:01, f14=22-06-82 13:24, f15=»0157A «, f16=» 14 «, f17=» «, f18=»12 «, f19=» 224 «, f20=» 329 «, f21=» «, f22=» «, f99=100010000110056610110180aaca15050000000000000042034600df}
0x1d100…1d200 (29, 0, 1) WangDocumentBody
[…0x2e…]
0x20000…20100 (32, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(32,0, 1), len=0xff, h3=41202541}, f00=»2025A «, f01=»AIR CANADA PROPOSAL «, f02=»pc «, f03=»LSJ «, f04=»Chapter 5. «, f05=15-04-82 15:19, f06=» «, f07=»52 «, f08=» 5640 «, f09=27-04-82 18:00, f10=» «, f11=»00 «, f12=» 27 «, f13=27-04-82 17:55, f14=09-08-82 20:36, f15=»0157A «, f16=» 63 «, f17=» 5 «, f18=»39 «, f19=» 572 «, f20=» 24999 «, f21=» «, f22=» «, f99=200020000110056610110180aaca1505000000000000004203d000df}
0x20100…20200 (32, 0, 1) WangDocumentBody
[…0x8…]
0x20a00…20b00 (32, 0, 10) Sector 200bff00202541 ┆ %A different CR80 computer systems are placed, as shown in figure III 5.2.1. The types of CR80 computer systems which are proposed to interface to the "site supra net" are: NSP: Nodal Switch Processor NCP: Nodal Control Processor NMH: Network Ma┆
0x20b00…20c00 (32, 0, 11) Sector 200cff00202541 ┆ %Anagement Host EMH: Electronic Mail Host It is underlined that each of the above mentioned systems are totally independent computer systems, only connected to one or more of the others by the "Site Supra Net". In this way it is seen that expansi┆
0x20c00…20d00 (32, 0, 12) Sector 200d8100202541 ┆ %Aon with new or existing functions are simply done by adding new CR80 computer systems to the existing "Site Supra Net". l Units (CU) 9 5.3.1.2.3 Bus Structures 11 5.3.1.2.4 Watchdog System ┆
0x20d00…20e00 (32, 0, 13) Sector 200eaa00202541 ┆ * %A 1 PROPOSED NETWORK CONFIGURATION Fig. III.5.2.1 21 5.3.1.2.7.1 Rack Dimensions 21 5.3.1.2.7.2 Periph┆
0x20e00…20f00 (32, 0, 14) Sector 200fff00202541 ┆ %A 1 5.3 System Configuration 5.3.1 Network Elements Each individual subsystem is described, and on related figures the subsystem is shown in block diagrams. Furthermore rach and crat┆
0x20f00…21000 (32, 0, 15) Sector 20007c00202541 ┆ | %Ae layout is shown. 5.3.1.1 Computing Elements The overall proposed computing elements are CR80 system elements. 3.3.3 Network Management Processor 30 5.3.3.4 Electronic Mail Processor 31 5.3.3.5 Channel Units ┆
0x21000…21100 (33, 0, 0) WangDocumentBody
[…0x6f…]
0x28000…28100 (40, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(40,0, 1), len=0xff, h3=41206541}, f00=»2065A «, f01=»AIR CANADA PROPOSAL «, f02=»kk «, f03=»HBA «, f04=»DOC. III Chapter 7 «, f05=23-04-82 09:56, f06=» 4 «, f07=»07 «, f08=» 14495 «, f09=22-06-82 10:38, f10=» «, f11=»05 «, f12=» 18 «, f13=27-04-82 19:13, f14=22-06-82 13:25, f15=»0157A «, f16=» 23 «, f17=» 4 «, f18=»57 «, f19=» 356 «, f20=» 15505 «, f21=» «, f22=» «, f99=100010000110056610110180aaca15050000000000000042037200df}
0x28100…28200 (40, 0, 1) WangDocumentBody
[…0x6e…]
0x2f000…2f100 (47, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(47,0, 1), len=0xff, h3=41206441}, f00=»2064A «, f01=»Air Canada «, f02=»sdv «, f03=»Chris «, f04=»fra 6.6 «, f05=23-04-82 09:44, f06=» 5 «, f07=»25 «, f08=» 30683 «, f09=25-06-82 10:21, f10=» «, f11=»05 «, f12=» 49 «, f13=28-04-82 01:01, f14=04-08-82 16:12, f15=»0157A «, f16=» 34 «, f17=» 6 «, f18=»57 «, f19=» 416 «, f20=» 31946 «, f21=» «, f22=» «, f99=021059000110056610110280aaca15050000000000000142038c00df}
0x2f100…2f200 (47, 0, 1) WangDocumentBody
[…0x6…]
0x2f800…2f900 (47, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(47,0, 9), len=0xff, h3=41205841}, f00=»2058A «, f01=»AIR CANADA PROPOSAL «, f02=»ut «, f03=»JSL «, f04=»DOC III Chap. 4.10- «, f05=22-04-82 09:26, f06=» 4 «, f07=»38 «, f08=» 32084 «, f09=10-08-82 10:38, f10=» «, f11=»01 «, f12=» 12 «, f13=27-04-82 21:25, f14=10-08-82 10:41, f15=»0157A «, f16=» 33 «, f17=» 5 «, f18=»45 «, f19=» 684 «, f20=» 33316 «, f21=» «, f22=» «, f99=020078000110056610110180aaca1505000000000000014203ce00df}
0x2f900…2fa00 (47, 0, 9) WangDocumentBody
[…0x6…]
0x30000…30100 (48, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(48,0, 1), len=0xff, h3=41206441}, f00=»2064A «, f01=»Air Canada «, f02=»sdv «, f03=»Chris «, f04=»fra 6.6 «, f05=23-04-82 09:44, f06=» 5 «, f07=»25 «, f08=» 30683 «, f09=27-04-82 19:55, f10=» «, f11=»07 «, f12=» 90 «, f13=28-04-82 01:01, f14=05-05-82 09:55, f15=»0157A «, f16=» 34 «, f17=» 6 «, f18=»52 «, f19=» 484 «, f20=» 31897 «, f21=» «, f22=» «, f99=021059000110056610110280aaca15050000000000000142038c00df}
0x30100…30200 (48, 0, 1) Sector 30022200206441 ┆0 " dA 0 0 / / / / . . - - - - , , , , + + + + + + * * * * * * * * ) DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: S S S S┆
0x30200…30300 (48, 0, 2) Sector 3003fb00206441 ┆0 { dA 1 CHAPTER 6 Page # DOCUMENT III TECHNICAL PROPOSAL Apr. 29, 1982 .=M2┆
0x30300…30400 (48, 0, 3) Sector 3004ff00206441 ┆0 dA 1 6.6 Terminal Access Software The scope of this section is to present the functions supported by the Terminal Access Software and to indicate the underlying structure of the softwa┆
0x30400…30500 (48, 0, 4) Sector 3005ff00206441 ┆0 dAre package. The description in this section indicates data flow, protocols, and control sequences that can be associated with individual software components. 6.6.1 Introduction The Terminal Access Software is interfaced to the nodal switch sof┆
0x30500…30600 (48, 0, 5) Sector 3006ff00206441 ┆0 dAtware (NSS). The interface can be either with the Datagram services of the NSS or the virtual transport services of the NSS. The basic components of the TAS are Line handlers, device handlers, emulators, connection allocation services, and Node l┆
0x30600…30700 (48, 0, 6) Sector 3007ff00206441 ┆0 dAogical unit services. External Resources Manager, Configuration Manager and Status Reporter, and Node Session Manager. For the sole purpose of description in this chapter, the basic components referenced above are equalled to "tasks". The softwar┆
0x30700…30800 (48, 0, 7) Sector 2f088200206441 ┆/ dAe packaging method employed combines the tasks into appropriate processes. Fig. 6.6.-1 shows the typical software package. : #wI>K!8=>R 2!8=6 #4 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=!┆
0x30800…30900 (48, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(48,0, 9), len=0xff, h3=41206541}, f00=»2065A «, f01=»2064CANADA PROPOSAL «, f02=»kk «, f03=»HBA «, f04=»DOC. III Chapter 7 «, f05=23-04-82 09:56, f06=» 4 «, f07=»07 «, f08=» 14495 «, f09=26-04-82 22:00, f10=» «, f11=»14 «, f12=» 221 «, f13=27-04-82 19:13, f14=05-05-82 09:56, f15=»0157A «, f16=» 23 «, f17=» 4 «, f18=»52 «, f19=» 444 «, f20=» 15487 «, f21=» «, f22=» «, f99=100010000110056610110180aaca15050000000000000042037200df}
0x30900…30a00 (48, 0, 9) Sector 300a1700206541 ┆0 eA 0 0 0 ) ( ' ' & & & % % % % $ $ $ $ $ $ # # # # DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAGAG┆
0x30a00…30b00 (48, 0, 10) Sector 300bfb00206541 ┆0 { eA 1 CHAPTER 7 Page # DOCUMENT III TECHNICAL PROPOSAL Apr. 29, 1982 .=M2┆
0x30b00…30c00 (48, 0, 11) Sector 300cff00206541 ┆0 eA 1 LIST OF CONTENTS Page 7. RMA 2 7.1 Introduction 2 7.2 RMA Analysis 4 7.3 Reliability Models and Block Diagrams 6 7.3.1 Reliability Models ┆
0x30c00…30d00 (48, 0, 12) Sector 300dff00206541 ┆0 eAfor PU's 8 7.4 Availability of a Single Node 12 7.5 Availability Access to destination 14 7.5.1 Availability Access to destination including alternative rouling 15 7.5.2 Availability End User to VIA Host 7.6 EMH availability 17 7.7 NMH availabil┆
0x30d00…30e00 (48, 0, 13) Sector 300e6800206541 ┆0 h eAity 18 7.8 Equipment Mean Time Between Failures (MTBF) 19 7.9 Equipment Maintainability (MTTR) 22 Rp0C%0! <6 M1' R 0C 0! <6 M1' R 0C 0! <6 M1' Z 0CR0Mc&!.=6 ! <6 M1' R40C.1! <6 M1' RC0C.1! <6 M1' RR0C.1!$<5CQ0!$<6 !&<6 Mc&! "(=6 E '<M% ! "2<┆
0x30e00…30f00 (48, 0, 14) Sector 300fff00206541 ┆0 eA 1 7 RELIABILITY,MAINTAINABILITY AND AVAILABILITY ANALYSIS This chapter provides the detailed analysis of the reliability and maintainability provided by the proposed equipment. Emp┆
0x30f00…31000 (48, 0, 15) Sector 2900ff00206541 ┆) eAhasis has been given to include the analysis for the range covered by the proposed system architecture. Furthermore, detailed information with respect to failure rates and repair times is provided for the various components and modules included in t┆
0x31000…31100 (49, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(49,0, 1), len=0xff, h3=41205841}, f00=»2058A «, f01=»AIR CANADA PROPOSAL «, f02=»ut «, f03=»JSL «, f04=»DOC III Chap. 4.10- «, f05=22-04-82 09:26, f06=» 4 «, f07=»38 «, f08=» 32084 «, f09=27-04-82 21:21, f10=» «, f11=»03 «, f12=» 23 «, f13=27-04-82 21:25, f14=05-05-82 09:54, f15=»0157A «, f16=» 33 «, f17=» 5 «, f18=»44 «, f19=» 768 «, f20=» 33304 «, f21=» «, f22=» «, f99=020078000110056610110180aaca1505000000000000014203ce00df}
0x31100…31200 (49, 0, 1) Sector 31022100205841 ┆1 ! XA 1 1 " entarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG Oprettet / ttet / ANSLAG Oprettet / tt/ tt / ttet / ANSLAGAGAG Oprettet / tt/ tt / ttet / ANSLAGAGAGAG┆
0x31200…31300 (49, 0, 2) Sector 3103fb00205841 ┆1 { XA 1 CHAPTER 4 Page # DOCUMENT III TECHNICAL PROPOSAL Apr. 29, 1982 .=M2┆
0x31300…31400 (49, 0, 3) Sector 3104ff00205841 ┆1 XA 1 4.10 Nodal Site Operations and Interfaces 4.10.1 Nodal Control Operations In the ACDN network the NCC supervisor staff is provided with total control of the entire network. The ┆
0x31400…31500 (49, 0, 4) Sector 3105ff00205841 ┆1 XAACDN network nodal computers are fully capable of unattended operation. However, to provide for local control of a nodal subsystem and its local external user network, a subset of the network control and monitoring functions may be exercised local┆
0x31500…31600 (49, 0, 5) Sector 3106ff00205841 ┆1 XAly at a nodal site operator work position. This command subset is specified in the command summary, section 4.6 The functions that will be available from a nodal site operator position includes the following o Status awareness functions (all┆
0x31600…31700 (49, 0, 6) Sector 3107ff00205841 ┆1 XA network status) o External resource control (line, concentrator, device and host participants) o Remote node control (dumping and diagnosing) o Local H/W and S/W fault isolation and verification 4.10.2 Node Operator Position The No┆
0x31700…31800 (49, 0, 7) Sector 2200ff00205841 ┆" XAdal Control Processor is equipped with an engineering position consisting of a VDU terminal/keyboard and a hardcopy printer. The work position is described in section 4.4.4. 4.10.3 Operator Categories The Node may be accessed locally by network┆
0x31800…31900 (49, 0, 8) Sector 3109ff00206441 ┆1 dAbatch access as long as they provide the standard HASP work station multileaving protocol or the Univac NTR protocol. Application to application file transfer between IBM Univac hosts or between two IBM hosts is supported by the above batch access┆
0x31900…31a00 (49, 0, 9) Sector 310aff00206441 ┆1 dA procedures. 6.6.3.3.1 IBM 2780 and 3780 BSC BSC batch devices can only be supported by SNA if they are given the appearance of the SNA batch terminal IBM 3790. JES3 is able to support an SNA work station with the following characteristics: ┆
0x31a00…31b00 (49, 0, 10) Sector 310bff00206441 ┆1 dAo Physical Unit PU.T2 o plus up to 5 LU.T1s, each consisting of: - zero or more console devices, - up to 15 reader devices, - up to 15 printer devices - up to 15 punch devices o each logical unit may contain up to 15 consoles, readers ┆
0x31b00…31c00 (49, 0, 11) Sector 310cff00206441 ┆1 dAand printers/punches, where at any time, only one can be active (i.e. selected by a Function Management Header type 1 (FMH1)). o supports for SNA character string (SCS) NL (new line) CR (carriage return) FF (form feed) IRS (inter recor┆
0x31c00…31d00 (49, 0, 12) Sector 310d5000206441 ┆1 P dAd separator) SVF (set vertical form) SEL (select) TRN (transparent) e devices are defined to the host as: o Conversational Devices (Category 3) o Buffered, Printing (Class 2) o Type: DCT1000 (Type 1) The support given by the devic┆
0x31d00…31e00 (49, 0, 13) Sector 310eff00206441 ┆1 dA 1 o FM Profile is 3 o TS Profile is 3 Only Point to Point is implemented, but multipoint may be installed, if required. Consoles for 2780, 3780 are supported in two ways: 1) Sh┆
0x31e00…31f00 (49, 0, 14) Sector 310fff00206441 ┆1 dAared on the same device (console input in reader stream, output on printer) as currently supported by JES3 for BSC-devices and 2) Shared console on another different device (TTY, 3270 or another batch station). Each 2780/3780 must be assigned to┆
0x31f00…32000 (49, 0, 15) Sector 3100ff00206441 ┆1 dA a shared console. 6.6.3.3.2 IBM S/3 HASP Work Station BSC A HASP work station is supported by the HASP multi leaving BSC protocol where the device handler in the TAS plays the role of a central HASP station. 6.6.3.3.4 Univac NTR Work Statio┆
0x32000…32100 (50, 0, 0) Sector 3201ff00206441 ┆2 dA3270 SNA, U100, U200, UTS 4000 running under UNISCOPE line discipline device handlers are provided. 6.6.3.2.1 IBM 3270 The IBM 3270 Information Display System consists of a variety of cluster controllers, display stations and printers. ACDN s┆
0x32100…32200 (50, 0, 1) Sector 3202ff00206441 ┆2 dAupports the models which are specified for remote attachment according to the following classification. IBM 3270 BSC o 3271 control unit, model 2 o 3274 control unit, model 1c o 3275 control unit, model 2 o 3276 control unit, model 2 o assoc┆
0x32200…32300 (50, 0, 2) Sector 3203ff00206441 ┆2 dAiated 3277 display stations o associated printers IBM 3270 SNA o 3274 Control Unit, model 1C o 3276 Control Unit, model 12 o associated 3278 display stations, o associated printers All devices are given an SNA appearance. Control units ar┆
0x32300…32400 (50, 0, 3) Sector 3204ff00206441 ┆2 dAe represented by a Physical Unit and their attached display stations and printers appear as associated Logical Units. IBM 3270 SNA Since these device follow truly, the SNA protocols, no special support needs to be given. Control Units attach as┆
0x32400…32500 (50, 0, 4) Sector 3205af00206441 ┆2 / dA PU.T2, display stations as LU.T2, and printers as LU.T1 or LU.T3, depending on whether they must support SNA Character String (SCS) control codes or 3270 data streams. a whole page has been received. Output is resumed when the data for- warding┆
0x32500…32600 (50, 0, 5) Sector 3206ff00206441 ┆2 dA 1 6.6.3.3 Batch Device Support Batch mode access for the purposes of description in this chapter is defined as an access procedure in which bulk data transfer is initiated. The ty┆
0x32600…32700 (50, 0, 6) Sector 3207ff00206441 ┆2 dApe of terminals that are supported by the batch access procedure are IBM 3780, IBM 2780, S/3 qualifying for HASP work station support and the UNIVAC NTR. From the IBM application program point of view, the IBM 2780, 3780 and HASP work stations are┆
0x32700…32800 (50, 0, 7) Sector 3108ff00206441 ┆1 dA supported by ACDN through the appearance of IBM 3790. From the Univac application program point of view, the NTR and IBM 2780 are supported by ACDN for batch access through RB2 protocol. Minicomputers with installed emulators are supported for ┆
0x32800…32900 (50, 0, 8) Sector 3209c200206441 ┆2 B dA 1 Fig. 6.6-2 Example of TTY Device Handler and Emulator Operations TTY with the following assumption: o TTY terminals appear a┆
0x32900…32a00 (50, 0, 9) Sector 320aff00206441 ┆2 dA 1 Teletype on IBM The IBM 3767 emulator accepts a BIND SNA-request for a type 1 session with the same restrictions as a proper IBM 3767. This means: o Function Management (FM) p┆
0x32a00…32b00 (50, 0, 10) Sector 320bff00206441 ┆2 dArofile must be 3. o Transmission Subsystem (TS) profile must be 3. o No FM headers are allowed. Input data is always sent as an Only-In-Chain Request Unit, whereas output RUs may be chained. If the BREAK key is depressed, an SNA SIGNAL request┆
0x32b00…32c00 (50, 0, 11) Sector 320cff00206441 ┆2 dA is transmitted to the host. Figure 6.6-3 shows a sequence of typical operations on the terminal, the corresponding states of the device handler and the SNA requests sent and received by the emulator. Teletype of UNIVAC Sessions between Telety┆
0x32c00…32d00 (50, 0, 12) Sector 320dff00206441 ┆2 dApes and UNIVAC hosts are fully supported via the INT-1 protocol. Teletype devices are defined to the host as: o Conversational Devices (Category 3) o Buffered, Printing (Class 2) o Type: DCT1000 (Type 1) The support given by the devic┆
0x32d00…32e00 (50, 0, 13) Sector 320e9800206441 ┆2 dAe handler is as described in section 6.7.3. In addition, the emulator will recognize a TTY commands and set line handler parameters accordingly. ned: *TTY Parameter-1: value-1, ...parameter-n: value-n, where a combination of the parameters in ta┆
0x32e00…32f00 (50, 0, 14) Sector 320f8400206441 ┆2 dA 1 Fig.6.6-3 ng, if any. Each tabulator stop is indicated by a non-blank character. If the user wants to change the tabulator setting,┆
0x32f00…33000 (50, 0, 15) Sector 3200ff00206441 ┆2 dA 1 PF6 NETWORK used to toggle between network control mode and data mode. PA1 is used as break key. 6.6.3.2 VDU Support In support of interactive host access IBM 3270 BSC, IBM ┆
0x33000…33100 (51, 0, 0) Sector 3301ff00206441 ┆3 dAset by the user not from the host. The tabulator function is performed when the HT character is received from the terminal. The HT character becomes part of the input string and, if a tabulator stop is defined to the right of the current input pos┆
0x33100…33200 (51, 0, 1) Sector 3302a400206441 ┆3 $ dAition, a sufficient number of spaces are output to reach the tabulator stop position. HT characters received from the host do not cause special processing. ing preceded by a DLE character. o Point-to-point or multipoint line discipline is mainta┆
0x33200…33300 (51, 0, 2) Sector 3303ff00206441 ┆3 dA 1 1 Parameter Function Default Value E Echo. 1 = Echo on, = echo off 1 0/1 C Character delete. Th┆
0x33300…33400 (51, 0, 3) Sector 3304ff00206441 ┆3 dAe previous character is deleted and if echo is on, BS-SP-BS is echoed. DEL character L Line delete. The input line is discarded and if echo is on, -X-CR-LF is echoed. CAN character P Page length 24 1 number 100 W Output pag┆
0x33400…33500 (51, 0, 4) Sector 3305ff00206441 ┆3 dAe width 80 1 number 256 I Maximum input line length 80 1 number 256 R Roll/scroll mode. 0=roll, 1=scroll roll 0/1 In scroll mode, output is halted when a whole page has been received. Output is resumed when the data for- warding┆
0x33500…33600 (51, 0, 5) Sector 3306ff00206441 ┆3 dA character is input. S Solicit. Indication of ready for input conduction id LF-solicit character. character T Data forwarding character. This character terminates the input line and causes it to be forwarded to the emulator. CR ┆
0x33600…33700 (51, 0, 6) Sector 3307ff00206441 ┆3 dAcharacter D Padding after carriage return 0 0 number 7 Number of NUL characters send after carriage return. X XON (DC1) and XOFF (DC3) control 0 0/1 1 = used, 0 = not used Note: A parameter value which is a character can either b┆
0x33700…33800 (51, 0, 7) Sector 32088300206441 ┆2 dAe specified directly, or by its decimal or octal ASCII value. Octal values are preceded by the letter 0. Table 6.6.-1 ent terminal types to the ACDN. The device handlers are concerned with providing the necessary device control functions and┆
0x33800…33900 (51, 0, 8) Sector 3309ff00206441 ┆3 dA are not concerned with presentation control and protocol functions for a particular device. The following descriptions of the device support for TTY presents the baseline facilities for TTY with the following assumption: o TTY terminals appear a┆
0x33900…33a00 (51, 0, 9) Sector 330ab700206441 ┆3 7 dAs IBM3767 terminals for IBM host access. o TTY terminals appear as conversational devices (category 3, Buffered printing (class 2), DCT1000 terminals for Univac host access. d outputs it, character by character on the line. The following charac┆
0x33a00…33b00 (51, 0, 10) Sector 330bff00206441 ┆3 dA 1 6.6.3.1 TTY Support The TTY device handler has the following characteristics: o The 7 bit ASCII character set is used. o Two modes are supported: system mode and normal mode┆
0x33b00…33c00 (51, 0, 11) Sector 330cff00206441 ┆3 dA. o Device characteristics may be changed by commands. The terminal is initially in system mode. When a Log on has been carried out, the terminal enters normal mode. As long as the terminal is engaged in a session, it is possible to switch bet┆
0x33c00…33d00 (51, 0, 12) Sector 330dff00206441 ┆3 dAween the two modes by pressing the DLE key as first input character. In normal mode, data is passed between the emulator and the terminal according to the current setting of the device characteristics which are explained below. Device handler co┆
0x33d00…33e00 (51, 0, 13) Sector 330eff00206441 ┆3 dAmmands are used either to signal special conditions to the emulator, or to change presentation service functions. The following commands are defined: *TTY Parameter-1: value-1, ...parameter-n: value-n, where a combination of the parameters in ta┆
0x33e00…33f00 (51, 0, 14) Sector 330fff00206441 ┆3 dAble 6.6-1 are allowed. *TAB Set tabulator. The device handler will display a line showing the current input tabulator setting, if any. Each tabulator stop is indicated by a non-blank character. If the user wants to change the tabulator setting,┆
0x33f00…34000 (51, 0, 15) Sector 3300ff00206441 ┆3 dA he can input a line where non-blank characters will define the tabulator stops. Example: DLE *TAB x X (old set of tab stops) x x x (new set of tab stops) DLE Tabulator stops can only be ┆
0x34000…34100 (52, 0, 0) Sector 3401ff00206441 ┆4 dAcol is supported as defined in: the IBM publication General Information - Binary Synchronous Communications, GA27-3004, with the following provisions: o Among the speeds mentioned above, the line speed can be selected in the range from 1200 to 960┆
0x34100…34200 (52, 0, 1) Sector 3402ff00206441 ┆4 dA0 bps. o The pad character used for line turn around can be specified. o The protocol can or cannot be in transparent mode, i.e. all control characters being preceded by a DLE character. o Point-to-point or multipoint line discipline is mainta┆
0x34200…34300 (52, 0, 2) Sector 3403ff00206441 ┆4 dAined. On a multipoint line, the line handler acts as a master. o The character set used is EBCDIC. o The following parameters which have a direct impact of the BSC protocol operation can be specified: - the number of consecutive negative res┆
0x34300…34400 (52, 0, 3) Sector 3404ff00206441 ┆4 dAponses to polling which are accepted before scanning continues, - the number of retries performed when a text block is negatively acknowledged, o The following parameters can be specified to manage the traffic mix on a line: - the poll time ┆
0x34400…34500 (52, 0, 4) Sector 3405ee00206441 ┆4 n dAinterval for devices not in sessions, - service order for devices on the line, - number of devices on the line which are considered in each scan. These parameters may be changed by the NCC operator during normal operation. vices, and Node l┆
0x34500…34600 (52, 0, 5) Sector 3406ff00206441 ┆4 dA 1 6.6.2.3 SDLC Protocol The synchronous bit oriented SDLC protocol is supported as defined in: IBM SDLC General Information GA27-3093, with the following provisions: o Among the ┆
0x34600…34700 (52, 0, 6) Sector 3407ff00206441 ┆4 dAspeeds mentioned above, the line speed can be selected in the range from 1200 to 19200 bps. o The line handler acts as the master. 6.6.2.4 HDLC Protocol The synchronous bit oriented protocol is supported as defined in CCITT recommendations Ye┆
0x34700…34800 (52, 0, 7) Sector 3308ff00206441 ┆3 dAllow book (1980). 6.6.3 Device Handlers The device handlers are individual tasks provided to support attachment of different terminal types to the ACDN. The device handlers are concerned with providing the necessary device control functions and┆
0x34800…34900 (52, 0, 8) Sector 3409ff00206441 ┆4 dA 1 6.6.2 Line Handlers The TAS provides support for one asynchronous and two synchronous line protocols. These protocols may work in several modes. 6.6.2.1 Asynchronous Start/Sto┆
0x34900…34a00 (52, 0, 9) Sector 340aff00206441 ┆4 dAp Protocols This protocol collects a string of characters from the line and forwards it to the device handler, or it receives a string of characters from the device handler and outputs it, character by character on the line. The following charac┆
0x34a00…34b00 (52, 0, 10) Sector 340bff00206441 ┆4 dAteristics apply: o The line speed can be selected among one of the speeds mentioned above in the range from 300 - 4800 bps. o The number of bits per character can be specified between 5 and 8. Characters are forwarded to the device handler i┆
0x34b00…34c00 (52, 0, 11) Sector 340cff00206441 ┆4 dAn 8-bit bytes, with the significant bits in the low order positions, and the remaining bits set to zero. o Even, odd, or no parity can be specified. Parity errors are signalled to the device handler and all bits in the erroneous byte are set to o┆
0x34c00…34d00 (52, 0, 12) Sector 340dff00206441 ┆4 dAne. o The stop bit can have a length of 1, 1 1/2, or 2 normal bits. o When characters are received, they may or may not be echoed back on the transmitting circuit. o A time out value can be specified. When time out occurs, any received charac┆
0x34d00…34e00 (52, 0, 13) Sector 340eff00206441 ┆4 dAters are forwarded to the device handler. o A data forwarding character can be specified. When this character is encountered, all received characters are sent to the device handler. o The numbers of nulls to be sent as time fill characters afte┆
0x34e00…34f00 (52, 0, 14) Sector 340f9800206441 ┆4 dAr a carriage return can be specified. o The break condition, defines as the signal being low min. 150 ms, can both be received and transmitted. 6.6.4 Emulators .............................. 6.6.4.1 IBM 3270 BSC ...................┆
0x34f00…35000 (52, 0, 15) Sector 3400ff00206441 ┆4 dA 1 The above parameter specification facilities are exploited to realize the necessary implementations for ACDN. 6.6.2.2 BSC Protocol The synchronous character oriented BSC proto┆
0x35000…35100 (53, 0, 0) Sector 3501ff00206441 ┆5 dA Interface .............. 6.6.4.7 Terminal Interface Support Summary . 6.6.5 External resources Manager ............. 6.6.6 Node Logical Unit Services ............. 6.6.7 Node Session Manager ................... ┆
0x35100…35200 (53, 0, 1) Sector 35027500206441 ┆5 u dA 6.6.8 Connection and Allocation Services ..... 6.6.9 Configuration Manager and Status Reporter g=~ J 4Cq5M")IMy,M1' R 4 'M, CV4:g=~ Bg4M73~ B)4Cq5! ="(=*(=N#FMC 2.=M ':>=V V u:A=!>= AH1 R^4 ]M, C 4:>=2A=Ms!:g=~ Jr4Mj2:g=~ B}4C75! ┆
0x35200…35300 (53, 0, 2) Sector 3503ff00206441 ┆5 dA 1 6.6 Terminal Access Software The scope of this section is to present the functions supported by the Terminal Access Software and to indicate the underlying structure of the softwa┆
0x35300…35400 (53, 0, 3) Sector 3504ff00206441 ┆5 dAre package. The description in this section indicates data flow, protocols, and control sequences that can be associated with individual software components. 6.6.1 Introduction The Terminal Access Software is interfaced to the nodal switch sof┆
0x35400…35500 (53, 0, 4) Sector 3505ff00206441 ┆5 dAtware (NSS). The interface can be either with the Datagram services of the NSS or the virtual transport services of the NSS. The basic components of the TAS are Line handlers, device handlers, emulators, connection allocation services, and Node l┆
0x35500…35600 (53, 0, 5) Sector 3506ff00206441 ┆5 dAogical unit services. External Resources Manager, Configuration Manager and Status Reporter, and Node Session Manager. For the sole purpose of description in this chapter, the basic components referenced above are equalled to "tasks". The softwar┆
0x35600…35700 (53, 0, 6) Sector 35078200206441 ┆5 dAe packaging method employed combines the tasks into appropriate processes. Fig. 6.6.-1 shows the typical software package. 25 04 82 18 59 00 6 25 04 82 16 58 25 04 82 19 19 0157A 36 6 27 508 31625 f *J B % _┆
0x35700…35800 (53, 0, 7) Sector 3408b500206441 ┆4 5 dA 1 Fig. 6.6-1 Framework Package for Terminal Access Software ┆
0x35800…35900 (53, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(53,0, 9), len=0xff, h3=41206441}, f00=»2064A «, f01=»Air Canada «, f02=»sdv «, f03=»Chris «, f04=»fra 6.6 «, f05=23-04-82 09:44, f06=» 5 «, f07=»25 «, f08=» 30683 «, f09=25-04-82 18:59, f10=» «, f11=»00 «, f12=» 6 «, f13=25-04-82 16:58, f14=25-04-82 19:19, f15=»0157A «, f16=» 36 «, f17=» 6 «, f18=»27 «, f19=» 508 «, f20=» 31625 «, f21=» «, f22=» «, f99=020010000110056610110480aaca15050000000000000142039400df}
0x35900…35a00 (53, 0, 9) Sector 350a2400206441 ┆5 $ dA 5 5 5 5 4 4 4 3 3 2 2 2 2 2 1 1 1 1 0 0 0 0 0 0 / / / / / / / / . . - DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: S S┆
0x35a00…35b00 (53, 0, 10) Sector 350bfb00206441 ┆5 { dA 1 CHAPTER 6 Page # DOCUMENT III TECHNICAL PROPOSAL Apr. 29, 1982 .=M2┆
0x35b00…35c00 (53, 0, 11) Sector 350cff00206441 ┆5 dA 1 1 6.6 Terminal Access Software ................... ┆
0x35c00…35d00 (53, 0, 12) Sector 350dff00206441 ┆5 dA 6.6.1 Introduction ........................... 6.6.2 Line Handlers .......................... 6.6.2.1 Asynchronous Start/Stop Protocols .. 6.6.2.2 BSC Protocol ....................... 6.6.2.3 SDLC Protocol ...┆
0x35d00…35e00 (53, 0, 13) Sector 350eff00206441 ┆5 dA................... 6.6.2.4 HDLC Protocol ...................... 6.6.3 Device Handlers ........................ 6.6.3.2 VDU Support ........................ 6.6.3.2.1 IBM 3270 ....................... 6.6┆
0x35e00…35f00 (53, 0, 14) Sector 350fff00206441 ┆5 dA.3.3.1 IBM 2780 and 3780 BSC .......... 6.6.3.3.2 IBM S3 HASP Work Station BSC .. 6.6.3.3.4 Univac NTR Work Station ........ 6.6.4 Emulators .............................. 6.6.4.1 IBM 3270 BSC ...................┆
0x35f00…36000 (53, 0, 15) Sector 3500ff00206441 ┆5 dA.... 6.6.4.2 IBM 2780 & 3780 BSC ................ 6.6.4.3 HASP Work Station BSC .............. 6.6.4.4 IBM SNA PU.T1 ...................... 6.6.4.5 IBM SNA PU.T2 ...................... 6.6.4.6 Transparent┆
0x36000…36100 (54, 0, 0) Sector 3601ff00201241 ┆6 A 1 8.4.6 Components The CR80 equipment is designed and produced according to detailed internal standards and procedures. This practice yields a product of high quality and reliabilit┆
0x36100…36200 (54, 0, 1) Sector 3602ff00201241 ┆6 Ay,which has been produced and delivered to several military systems. The components used in the design are standard components available from more than one manufacturer and to a great extent MIL-specified and used in military projects all over the┆
0x36200…36300 (54, 0, 2) Sector 3603ff00201241 ┆6 A world which ensures that the components will be available on the market during the lifetime of the system. The critical components are tested to be in accordance with the procurement specification, either by the component manufacturer or by speci┆
0x36300…36400 (54, 0, 3) Sector 3604ff00201241 ┆6 Aal test houses like the Danish Elektronikcentralen. The electrical design is performed in accordance with CR internal standards which ensures that no component in the system is overexposed to stressful conditions or used under conditions for which┆
0x36400…36500 (54, 0, 4) Sector 3605e200201241 ┆6 b A the component is not intended, thus securing a very low module failure rate. The only expendable items are things like air filters, fuses and indicator lamps. They are all standard types which are readily available. on built-in test, meaning tha┆
0x36500…36600 (54, 0, 5) Sector 3606ff00201241 ┆6 A 1 8.4.7 Testing In addition to the test performed on the components all units are tested before release from the production to comply with the specifications for the unit. This test ┆
0x36600…36700 (54, 0, 6) Sector 3607ff00201241 ┆6 Awhich to a great extent is based upon automatic test equipment, includes a burn-in test to ensure that the initial, comparitively high, failure rate for components is removed before the units are released. When the units are released they will be ┆
0x36700…36800 (54, 0, 7) Sector 0200ff00201241 ┆ Atested at system level before shipment. Upon arrival to the site, the units will be installed and integrated in the system and thereafter be subject to extensive tests at system level. Coding straps and jumpers are mounted during the unit producti┆
0x36800…36900 (54, 0, 8) Sector 36095800206541 ┆6 X eA1129 Hour MTTR = 30 Min. Avail = 99.9557% or the NCC CU DISK CTRL DISK CU ┆
0x36900…36a00 (54, 0, 9) Sector 360aff00206541 ┆6 eA 1 7.8 EQUIPMENT MEAN TIME BETWEEN FAILURES(MTBF) The high reliability of the proposed equipment is achieved through use of proven failure rate equipment similar to that supplied by C┆
0x36a00…36b00 (54, 0, 10) Sector 360bff00206541 ┆6 eAhristian Rovsing for the NICS-TARE, FIKS and CAMPS programmes. Early in the design phase, a major objective for each module is to achieve reliable performance. CR80 modules make extensive use of carefully chosen components; most of the IC's are te┆
0x36b00…36c00 (54, 0, 11) Sector 360cff00206541 ┆6 eAsted to the requirement of MIL-STD 883 level B. The inverse of MTBF representing failure rate which applies to system elements and modules is listed in Table 7-8 entitled CR80 Reliability Factors. The MTBF data has been derived from reliability ┆
0x36c00…36d00 (54, 0, 12) Sector 360dff00206541 ┆6 eAdata maintained on the NICS-TARE and CAMPS and similar programmes. Inherent MTBF values are in general derived from the reliability predictions accomplished in accordance with the U.S. MIL-HDBK-217 "Reliable Predictions of Electronic Equipment". Thi┆
0x36d00…36e00 (54, 0, 13) Sector 360eff00206541 ┆6 eAs document, adopted by Christian Rovsing through their involvement with NICS-TARE, is used extensively on current military and aerospace programmes. Failure rate data for terminal and periphal equipment is generally provided by the vendor in accor┆
0x36e00…36f00 (54, 0, 14) Sector 360f3100206541 ┆6 1 eAdance with the subcontract specifications. MTTR = 15 Min. = 5.20 ility model for the processing part of the Nodal Control is shown below Nodal Control Processor (NCP) ┆
0x36f00…37000 (54, 0, 15) Sector 1c00b800206541 ┆ 8 eA 1 R & M VALUES FOR MODULES AND PERIPHALS Table 7-8 (Cont'd) in the primary path. ┆
0x37000…37100 (55, 0, 0) Sector 37015f00206541 ┆7 _ eA MTBF = 9.777 Hours MTTR = 30 Min. Avail = 99.9949% Management Processor (NMP) MTBF = 1241 Hours MTTR = 30 min ┆
0x37100…37200 (55, 0, 1) Sector 3702ff00206541 ┆7 eA 1 7.5.1 Availability access to destination, including alternative routing The availability of access to access point to destination point is not improved by use of alternative routi┆
0x37200…37300 (55, 0, 2) Sector 3703c100206541 ┆7 A eAng. This is due to the small network, i.e. the two access nodes and the two access LTU's still have to work, and nearly all the unavailability is associated with these four components. MTTR = 30 min. Avail =┆
0x37300…37400 (55, 0, 3) Sector 3704ff00206541 ┆7 eA 1 7.5.2 Availability End User to VIA Host The reliability model for an end User's access to the VIA Host in shown below MTBF ┆
0x37400…37500 (55, 0, 4) Sector 3705c700206541 ┆7 G eA = 44.803 Hours MTTR = 30 Min. Avail = 99.9989% Legend Non CR, estimated *) Note that the availability is calculated ??????? e following Criteria are used in the calculations * Th┆
0x37500…37600 (55, 0, 5) Sector 3706ff00206541 ┆7 eA 1 7.6 Electronic Mail Host Availability The Electronic Mail Host (EMH) availability model is shown in the figure below: MTBF ┆
0x37600…37700 (55, 0, 6) Sector 37076700206541 ┆7 g eA = 249.513 Hours MTTR = 30 Min. Avail = 99.9998% grp. 1 grp. 2 grp. 3 grp. 4 0.74 1.59 8.81 5.2 5.2 5.2 5.2 ┆
0x37700…37800 (55, 0, 7) Sector 3608ff00206541 ┆6 eA 1 7.7 Network Management Host Availability Shown below is the availability model for the Network Management Host: MTBF = ┆
0x37800…37900 (55, 0, 8) Sector 3709ff00206541 ┆7 eA 1 Availability for the NCC CU DISK CTRL DISK CU ┆
0x37900…37a00 (55, 0, 9) Sector 370aff00206541 ┆7 eA 54.4 250 Crate ASS 1.4 DISK DISK ┆
0x37a00…37b00 (55, 0, 10) Sector 370bff00206541 ┆7 eA CTRL 54.4 250 ┆
0x37b00…37c00 (55, 0, 11) Sector 370cff00206541 ┆7 eA MTBF = 630.915 Hours MTTR = 30 Min. = 1.59 Availability for NSP LTU Group ┆
0x37c00…37d00 (55, 0, 12) Sector 370dff00206541 ┆7 eA CU CU CU LTU LIA-N Crate Crate Crate Assy. Assy. Assy. ┆
0x37d00…37e00 (55, 0, 13) Sector 370eff00206541 ┆7 eA 1.4 1.4 1.4 36.4 0.1 35 of 36 1 ┆
0x37e00…37f00 (55, 0, 14) Sector 370f7400206541 ┆7 t eA MTBF = 192.308 Hours MTTR = 15 Min. = 5.20 ility model for the processing part of the Nodal Control is shown below Nodal Control Processor (NCP) ┆
0x37f00…38000 (55, 0, 15) Sector 3700ff00206541 ┆7 eA 1 7.5 Availability Access to destination Shown below is the reliability model for access point to access point in the primary path. ┆
0x38000…38100 (56, 0, 0) Sector 3801ff00206541 ┆8 eA 1 Network Management Processor (NMP) MTBF = 1241 Hours MTTR = 30 min ┆
0x38100…38200 (56, 0, 1) Sector 38026300206541 ┆8 c eAAvail = 99.960% = 806 Fig. III 7.2.1.3 MTBF ┆
0x38200…38300 (56, 0, 2) Sector 3803ff00206541 ┆8 eA 1 Electronic Mail Processor MTBF = 1453 Hours MTTR = 30 min. Avail =┆
0x38300…38400 (56, 0, 3) Sector 38045c00206541 ┆8 \ eA 99.995% = 688 Fig. III 7.2.1.4 1 7.3 RELIABILITY MODELS AND BLOCK DIAGRAMS The computer system is partitioned into system el┆
0x38400…38500 (56, 0, 4) Sector 3805ff00206541 ┆8 eA 1 7.4 Availability of a Single Node Shown below is the availability model for a single node, which includes the dual NCC. The following Criteria are used in the calculations * Th┆
0x38500…38600 (56, 0, 5) Sector 3806ff00206541 ┆8 eAe Nodal Switch LTU's are partioned in groups of 36 LTU's of which only 1 may have failed. * A nodal switch processer will still work, even if the V24 connection to the Nodal Control Processor does not work. NCP CU CP NSP Nodal ┆
0x38600…38700 (56, 0, 6) Sector 3807ff00206541 ┆8 eA Nodal Nodal Nodal 1 of 2 5 of 6 LTU LTU LTU LTU grp. 1 grp. 2 grp. 3 grp. 4 0.74 1.59 8.81 5.2 5.2 5.2 5.2 ┆
0x38700…38800 (56, 0, 7) Sector 3708a300206541 ┆7 # eA MTBF = 31.308 Hours MTTR = 30 Min. Avail = 99.9984 ================== d. System elements are essentially stand-alone and free of chain failures. Careful attenti┆
0x38800…38900 (56, 0, 8) Sector 3809de00206541 ┆8 ^ eAon has been paid in the design to eliminate series risk elements. Redundant units are repairable without interruption of service. Maintenance and reconfiguration is possible without compromising system performance. E n(n┆
0x38900…38a00 (56, 0, 9) Sector 380aff00206541 ┆8 eA 1 The primary source selected for authenticated reliability data and predictions is the MIL-HDBK-217. The failure rate data are primarily obtained from experience from previous progr┆
0x38a00…38b00 (56, 0, 10) Sector 380be700206541 ┆8 g eAammes and continuously revised as part of the maintenance programme on concurrent programmes. The relialibility models which apply to the proposed configurations are identified in the figures shown on the following pages. ement mean time to repai┆
0x38b00…38c00 (56, 0, 11) Sector 380cff00206541 ┆8 eA 1 7.3.1 Reliability Models for Processing Elements The reliability models MTBF and availability predictions for the Processing Units are shown in the figure below: Nodal Switch P┆
0x38c00…38d00 (56, 0, 12) Sector 380dff00206541 ┆8 eArocessor Unit (NSP) MTBF = 1305 Hours MTTR = 30 min. Avail = 44.962% = 766 Fig. III 7.2┆
0x38d00…38e00 (56, 0, 13) Sector 380e0b00206541 ┆8 eA.1.1 E 2 ┆
0x38e00…38f00 (56, 0, 14) Sector 380fff00206541 ┆8 eA 1 Nodal Control Processor (NCP) The reliability model for the processing part of the Nodal Control is shown below Nodal Control Processor (NCP) ┆
0x38f00…39000 (56, 0, 15) Sector 3800ce00206541 ┆8 N eA MTBF = 1161 Hours MTTR = 30 min. Avail = 99.957% = 861 Fig. III 7.2.1.2 ┆
0x39000…39100 (57, 0, 0) Sector 3901ff00206541 ┆9 eA 1 c. Availability The availability corresponds to the ratio between the MTBF and the total operative time, which is equal to the sum ┆
0x39100…39200 (57, 0, 1) Sector 3902ff00206541 ┆9 eAof MTBF and MTTR for the element thus: H MTBF ┆
0x39200…39300 (57, 0, 2) Sector 3903ff00206541 ┆9 eA A = E E MTBF + MTTR E E ┆
0x39300…39400 (57, 0, 3) Sector 3904ff00206541 ┆9 eA 1 7.3 RELIABILITY MODELS AND BLOCK DIAGRAMS The computer system is partitioned into system el┆
0x39400…39500 (57, 0, 4) Sector 3905ff00206541 ┆9 eAements and the models used for reliability and availabilty predictions show how the proposed equipment provides the high degree of reliability required. The system reliability characteristics for the system are stated in numerical terms by mathema┆
0x39500…39600 (57, 0, 5) Sector 3906ff00206541 ┆9 eAtical models; the supporting detailed predictions are presented in this chapter. The system models are partitioned into modular units and system elements that reflect the redundancy of the configuration; it accounts for all interconnections and swit┆
0x39600…39700 (57, 0, 6) Sector 3907ff00206541 ┆9 eAching points. The MTBF and MTTR for the individual elements used in the calculations were obtained from experience with similar equipment on the NICS-TARE, FIKS and CAMPS programmes. The figures quoted on peripheral equipment are based on data suppl┆
0x39700…39800 (57, 0, 7) Sector 3808ff00206541 ┆8 eAied by the manufacturers. The equipment has been partitioned and functions apportioned so that system elements can have only two states - operable or failed. System elements are essentially stand-alone and free of chain failures. Careful attenti┆
0x39800…39900 (57, 0, 8) Sector 3909ff00206541 ┆9 eA 2 Element MTBF = (n+1)*MTBF*MTTR + MTBF , or E n(n┆
0x39900…39a00 (57, 0, 9) Sector 390aff00206541 ┆9 eA+1)MTTR 2 MTBF = MTBF provided (n + 1)*MTTR MTBF ┆
0x39a00…39b00 (57, 0, 10) Sector 390bff00206541 ┆9 eA E n(n + 1)MTTR 1 b. Mean Time To Repair The element mean time to repai┆
0x39b00…39c00 (57, 0, 11) Sector 390cff00206541 ┆9 eAr, MTTR E , corresponds to the period where more than n out of the n+1 units are not available i.e. the element is not fully operative. 1 of 2 Parallel Elements H ┆
0x39c00…39d00 (57, 0, 12) Sector 390dff00206541 ┆9 eA MTTR = MTTR ┆
0x39d00…39e00 (57, 0, 13) Sector 390ed900206541 ┆9 Y eA E 2 ┆
0x39e00…39f00 (57, 0, 14) Sector 390fff00206541 ┆9 eA H n of n + 1 Parallel Elements MTTR = MTTR ┆
0x39f00…3a000 (57, 0, 15) Sector 3900ff00206541 ┆9 eA E 2 ┆
0x3a000…3a100 (58, 0, 0) Sector 3a012100206541 ┆: ! eA ments. The CR80 fault tolerant computers are designed to avoid single point errors of all critical system elements by provision of redundancy paths, processor capabilities and power supplies. The architecture reflects th┆
0x3a100…3a200 (58, 0, 1) Sector 3a02ff00206541 ┆: eA 1 where LAMBDA i denotes the failure rate of the i'th element. The availability of a system of n different serial RMA elements is determined by: A = A 1 *A 2 *....*i*....*A n ┆
0x3a200…3a300 (58, 0, 2) Sector 3a03ff00206541 ┆: eA 7.2.2 Parallel Elements When RMA elements are in parallel, it is required that one or more of the parallel units are operative simultaneously to obtain the required system performance. The actual number of parallel units required is dependent on┆
0x3a300…3a400 (58, 0, 3) Sector 3a04ff00206541 ┆: eA the actual models. Assuming operational redundancy and neglible recovery time, the calculation rules are: a. Mean Time Between Failure When the parallel elements have defined MTBF and MTTR values the following rules apply: 1 of 2 equal par┆
0x3a400…3a500 (58, 0, 4) Sector 3a05ff00206541 ┆: eAallel elements H 2 Element MTBF = 2 * MTBF * MTTR + MTBF , or ┆
0x3a500…3a600 (58, 0, 5) Sector 3a06ff00206541 ┆: eA E 2 x MTTR 2 ┆
0x3a600…3a700 (58, 0, 6) Sector 3a07ff00206541 ┆: eA MTBF = MTBF Provided MTTR MTBF E 2xMTTR ┆
0x3a700…3a800 (58, 0, 7) Sector 3908ff00206541 ┆9 eA 1 n of n+1 Equal Parallel Elements H ┆
0x3a800…3a900 (58, 0, 8) Sector 3a09ff00206541 ┆: eAMA analysis of a system provides information on how much of the time the system provides a given set of required functional capabilities, i.e. provides operative availability. It shows how many times the system is not operative during a given perio┆
0x3a900…3aa00 (58, 0, 9) Sector 3a0aff00206541 ┆: eAd and for how long. A system may be operative even with one or more elements of the total system down or taken off-line for the purpose of repairing and/or replacement of delect modules/units. Note that this is operative as seen by a user of the f┆
0x3aa00…3ab00 (58, 0, 10) Sector 3a0bff00206541 ┆: eAunctional capabilities, not as seen by maintenance personnel. The basis for determining the system level availability is an RMA model of serial and parallel system elements. Each of these elements defines a specific subset of the total system wit┆
0x3ab00…3ac00 (58, 0, 11) Sector 3a0cff00206541 ┆: eAh a well defined state either functioning or not. Serial elements refer to elements all of which have to be available for that set to be available. Parallel elements describes those sets where not all elements need to be available, the number det┆
0x3ac00…3ad00 (58, 0, 12) Sector 3a0dff00206541 ┆: eAermined by the required service level or the redundancy provided. The subsequent section introduces the basic RMA building stones. 7.2.1 Series Element The mean time between failures of a series of n different RMA elements is made up as follow┆
0x3ad00…3ae00 (58, 0, 13) Sector 3a0eff00206541 ┆: eAs: H MTBF 6 5 = 10 ┆
0x3ae00…3af00 (58, 0, 14) Sector 3a0fff00206541 ┆: eA LAMBDA 5 1 ┆
0x3af00…3b000 (58, 0, 15) Sector 3a00ff00206541 ┆: eA where the series failure rates is determined by the sum of the failure rates of the elements: LAMBDA 5 = LAMBDA 1 + LAMBDA 2 +...+LAMBDA i +....+LAMBDA n 1 ┆
0x3b000…3b100 (59, 0, 0) Sector 3b01ff00206541 ┆; eAactual availability requirements. The CR80 fault tolerant computers are designed to avoid single point errors of all critical system elements by provision of redundancy paths, processor capabilities and power supplies. The architecture reflects th┆
0x3b100…3b200 (59, 0, 1) Sector 3b02ff00206541 ┆; eAe fact that the reliability of peripheral devices is lower than that of the associated CR80 device controllers. This applies equally well to communication lines where modems are used as part of the transmission media. Thus, the peripheral devices, m┆
0x3b200…3b300 (59, 0, 2) Sector 3b03ff00206541 ┆; eAodems, communication lines, etc., impact the system availability much more than the corresponding device controllers. To assure this very highly reliable product, several criteria were also introduced on the module level: An extensive use of hi┆
0x3b300…3b400 (59, 0, 3) Sector 3b04ff00206541 ┆; eA-rel, mil-spec components, ICs are tested to the requirements of MIL-STD 883 level B or similar. All hardware is designed in accordance with the general CR80 H/W design principles. These include derating specifications, which greatly enhance the ┆
0x3b400…3b500 (59, 0, 4) Sector 3b05ff00206541 ┆; eAreliability and reduce the sensibility to parameter variations. Critical modules feature a Built-In(BIT) capability as well as a display of the main states of the internal process by Light Emitting Diodes on the module front plate. This greatly i┆
0x3b500…3b600 (59, 0, 5) Sector 3b06ff00206541 ┆; eAmproves module maintainability, as it provides debug and trouble shooting methods, which reduce the repair time. A high quality production line, which includes high quality soldering, inspection, burn-in and an extensive automatic functional test┆
0x3b600…3b700 (59, 0, 6) Sector 3b070a00206541 ┆; eA. s has been given to include the analysis for the range covered by the proposed system architecture. Furthermore, detailed information with respect to failure rates and repair times is provided for the various components and modules included in t┆
0x3b700…3b800 (59, 0, 7) Sector 3a08ff00206541 ┆: eA 1 7.2 RMA Analysis This section provides information with respect to RMA analysis of a system. It includes the detailed formulas which apply as part of the RMA calculations. The R┆
0x3b800…3b900 (59, 0, 8) Sector 3b09ff00206541 ┆; eAs automatically substitute each other in case of failure. Overall system availability has been calculated. The high system availability has been achieved by use of highly reliable modules, redundant processor units and line termination units, and ┆
0x3b900…3ba00 (59, 0, 9) Sector 3b0aff00206541 ┆; eAautomatic reconfiguration facilities. Care has been taken to ensure that single point errors do not cause total system failure. The reliability criteria imposed on the computer systems have been evaluated and the proposed hardware/software operati┆
0x3ba00…3bb00 (59, 0, 10) Sector 3b0bff00206541 ┆; eAonal system analysed to determine the degree of availability and data integrity provided. In this chapter reliability is stated in numerical terms and the detailed predictions derived from mathematical models presented. The availability prediction┆
0x3bb00…3bc00 (59, 0, 11) Sector 3b0cff00206541 ┆; eAs are made in accordance with system reliability models and block diagrams corresponding to the proposed configuration. This procedure involves the use of module level and processor unit level failure rates, or MTBF, (mean time between failure) and ┆
0x3bc00…3bd00 (59, 0, 12) Sector 3b0dff00206541 ┆; eArepair times or MTTR, (mean time to repair); these factors are used in conjunction with a realistic modelling of the configuration to arrive at system level MTBF and availability. Tabulated results of the analysis are presented including the relia┆
0x3bd00…3be00 (59, 0, 13) Sector 3b0e3700206541 ┆; 7 eAbilty factors: system MTBF and repair time MTTR. erouted through alternative trunks. If anode becomes unreachable due to multiple trunk failures, the line defined in VTAM to connect that node to the Host is forced deactivated. This is provided with ┆
0x3be00…3bf00 (59, 0, 14) Sector 3b0fff00206541 ┆; eA 1 The basic elements of the proposed system architecture are constituted by standard CR80 units. Reliabilty and maintainability engineering was a significant factor in guiding the dev┆
0x3bf00…3c000 (59, 0, 15) Sector 3b00ff00206541 ┆; eAelopment of the CR80. The CR80 architecture is designed with a capability to achieve a highly reliable computer system in a cost-effective way. It provides a reliable set of services to the users of the system, because it may be customised to the ┆
0x3c000…3c100 (60, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(60,0, 1), len=0xff, h3=41206541}, f00=»2065A «, f01=»AIR CANADA PROPOSAL «, f02=»kk «, f03=»HBA «, f04=»DOC. III Chapter 7 «, f05=23-04-82 09:56, f06=» 4 «, f07=»07 «, f08=» 14495 «, f09=25-04-82 18:58, f10=» «, f11=»01 «, f12=» 6 «, f13=25-04-82 18:02, f14=25-04-82 19:18, f15=»0157A «, f16=» 23 «, f17=» 4 «, f18=»37 «, f19=» 436 «, f20=» 15223 «, f21=» «, f22=» «, f99=020010000110056610110480aaca15050000000000000042037100df}
0x3c100…3c200 (60, 0, 1) Sector 3c021700206541 ┆< eA < < < ; ; : 9 8 8 8 8 8 8 7 7 7 7 7 7 6 6 DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAGAG┆
0x3c200…3c300 (60, 0, 2) Sector 3c03fb00206541 ┆< { eA 1 CHAPTER 7 Page # DOCUMENT III TECHNICAL PROPOSAL Apr. 29, 1982 .=M2┆
0x3c300…3c400 (60, 0, 3) Sector 3c04ff00206541 ┆< eA 1 LIST OF CONTENTS 7. RMA 7.1 Introduction 7.2 RMA Analysis 7.3 Reliability Models and Block Diagrams 7.3.1 Reliability Models for PU's 7.4 Availability of a Single Node 7.5 Avail┆
0x3c400…3c500 (60, 0, 4) Sector 3c05be00206541 ┆< > eAability Access to destination 7.5.1 Availability Access to destination including alternative rouling 7.5.2 Availability End User to VIA Host 7.6 EMH availability 7.7 NMH availability RM/!/=6iM (*(=~ R`/!/=6WM (*(=~ Rt/!/=6lM (*(=~ R ┆
0x3c500…3c600 (60, 0, 5) Sector 3c06ff00206541 ┆< eA 1 7 RELIABILITY,MAINTAINABILITY AND AVAILABILITY ANALYSIS This chapter provides the detailed analysis of the reliability and maintainability provided by the proposed equipment. Emp┆
0x3c600…3c700 (60, 0, 6) Sector 3c07ff00206541 ┆< eAhasis has been given to include the analysis for the range covered by the proposed system architecture. Furthermore, detailed information with respect to failure rates and repair times is provided for the various components and modules included in t┆
0x3c700…3c800 (60, 0, 7) Sector 3b08ff00206541 ┆; eAhe architecture. 7.1 INTRODUCTION The availablity of the proposed equipment is very high due not only to a high reliability of individual system elments, but not least due to the chosen CR80 computer configuration, where functional like element┆
0x3c800…3c900 (60, 0, 8) Sector 3c09ff00201241 ┆< Aen used, test points will be located at easily accessible places on front panels etc. Sensitiive test points are protected if misuse can cause serious disturbance. Due to the extensive use of microprocessors the system can perform basic operations┆
0x3c900…3ca00 (60, 0, 9) Sector 3c0aff00201241 ┆< A; even if a major part of the hardware is out of service. The modules are self-contained mechanical units which slide into the frame aligned by the frame itself so that the contacts are not damaged when modules are replaced. On the mechanics use┆
0x3ca00…3cb00 (60, 0, 10) Sector 3c0bf500201241 ┆< u Ad for alignment no limit for exchange of modules exists. The connectors used for interfacing the modules to the remaining part of the system, normally edge connectors, are a high quality type which allow for more than 500 module exchanges.has also b┆
0x3cb00…3cc00 (60, 0, 11) Sector 3c0cff00201241 ┆< A 1 8.4.4 Expandibility The systems are of a modular construction, where the modules are mechanical self-contained circuit-boards operating in accordance with a set of interface speci┆
0x3cc00…3cd00 (60, 0, 12) Sector 3c0dff00201241 ┆< Afications which are completely independent of the actual design and technology used for implementing the modules' function. This means that system extension is very easy to perform just by adding the required hardware modules, crates, and racks. ┆
0x3cd00…3ce00 (60, 0, 13) Sector 3c0eff00201241 ┆< A8.4.5 System Life Time As mentioned above, the modules in the system are designed to be compatible with a set of interface specifications which covers mechanical, electrical, and functional interfaces thereby allowing the modules to be changed wit┆
0x3ce00…3cf00 (60, 0, 14) Sector 3c0fff00201241 ┆< Ah modules of a new generation without adjustments and without affecting the remaining part of the system soft- or hardware. By using this approach in the complete hardware, central processor and interface modules, procurement of new modules for sy┆
0x3cf00…3d000 (60, 0, 15) Sector 3600b200201241 ┆6 2 Astem expansion, and spare parts are not dependent on one single manufacturer or a specific component and can therefore be guaranteed during the long lifetime of the system.ease the normal use,maintenance and repair. The basic design is therefore a m┆
0x3d000…3d100 (61, 0, 0) Sector 3d01ff00201241 ┆= Aodular self-contained construction where all normally used fuses,switches,controls and displays are located is such a way as to make them easily accesible on front or near panels. The colour of LED indicators are standardised, Red means alarm or er┆
0x3d100…3d200 (61, 0, 1) Sector 3d02ff00201241 ┆= Aror, Yellow is a status indicator and Green means Power On or Working. 8.4.3 Maintenance and Repair In the design of the equipment great emphasis has been put on maintenance. Meaning that the system can be changed, updated or repaired without ┆
0x3d200…3d300 (61, 0, 2) Sector 3d03ff00201241 ┆= Aaffecting the traffic handling. Repais is very easy due to the modular construction where a module can be exchanged without use of special tools. All the modules except the direct interface to the lines can be changed without affecting the operat┆
0x3d300…3d400 (61, 0, 3) Sector 3d04ff00201241 ┆= Aion due to the redundancy. This is applicable for both the central processor and the input/output system. The design is based upon distributed processing with processors in more levels from the CR80 central processor configuration to the LTU's. ┆
0x3d400…3d500 (61, 0, 4) Sector 3d05ff00201241 ┆= ABesides the operational work performed by the different processors in the system these are also running tests to ensure proper system operation. The principle used in the design of programs is to a great extent based upon built-in test, meaning tha┆
0x3d500…3d600 (61, 0, 5) Sector 3d068f00201241 ┆= At the modules will perform a self-test when requested from the central processor and present a status specifying the result of the test. one per second. The equipment will not emit more interference voltage on the mains wires than specified in CI┆
0x3d600…3d700 (61, 0, 6) Sector 3d07ff00201241 ┆= A 1 If a failing module is detected, it will, if possible, be bypassed and the type and exact position of the module will be printed out on the system console so that it can be replaced┆
0x3d700…3d800 (61, 0, 7) Sector 3c08ff00201241 ┆< A by means of an operator. In addition to the console print-out specifying the location of the failing module, most of the modules have built-in light emitting diodes on the front panel which shows the status of the module (operating or faulty). Wh┆
0x3d800…3d900 (61, 0, 8) Sector 3d095700201241 ┆= W Aary to provide the equipment with special line overvoltage protection circuitry. capsulated type. ┆
0x3d900…3da00 (61, 0, 9) Sector 3d0aff00201241 ┆= A 1 8.4 Common Aspects 8.4.1 Safety The CR equipment is designed to meet the requirements of IEC 435, Safety of Data Processing Equipment and the Danish Safety Regulations. Human Sa┆
0x3da00…3db00 (61, 0, 10) Sector 3d0bff00201241 ┆= Afety considerations have been taken into account to protect the operating and maintenance personnel against dangerous voltage levels or items with high temperature by means of suitable protective covering and warning labels. The equipment has also b┆
0x3db00…3dc00 (61, 0, 11) Sector 3d0cff00201241 ┆= Aeen designed to eliminate the possibility of physichal injury to the personnel under normal opertaing and maintenance conditions.. Equipment Safety has been taken into account by inherent protection against overcurrent and other dangerous error co┆
0x3dc00…3dd00 (61, 0, 12) Sector 3d0dff00201241 ┆= Anditions. The equipment will not emit dangerous fumes when exposed to light or normal heating sources below 70 deg C. The equipment is manufactured from self-extinguishing materials, but it may still be involved in a fire accident, in which case┆
0x3dd00…3de00 (61, 0, 13) Sector 3d0eff00201241 ┆= A the equipment will not give off more poisonous gases than electronic equipment or building materials normally do. The acoustic noise emitted from the fan unit or other units like terminals and disc drives will not exceed 70dB(A) re 20uPa measured┆
0x3de00…3df00 (61, 0, 14) Sector 3d0f3800201241 ┆= 8 A in a distance of 2m under free-field conditions. with 10mS half-sine pulse. Note: These limits apply to the outer surfaces of the packaging container, not to the equipment inside. During transport and storage the equipment will be properly prot┆
0x3df00…3e000 (61, 0, 15) Sector 3d00ff00201241 ┆= A 1 8.4.2 Human Engineering The equipment is designed with great emphasis on human engineering aspects to ease the normal use,maintenance and repair. The basic design is therefore a m┆
0x3e000…3e100 (62, 0, 0) Sector 3e010f00201241 ┆> Aes etc. ndards and Specifications. Unless otherwise stated, the Christian Rovsing equipment will furthermore be in accordance with the CCITT recommendations specified in the Christian Rovsing Technical Specification at the issue applicable at the┆
0x3e100…3e200 (62, 0, 1) Sector 3e02ff00201241 ┆> A 1 8.3. Electrical Environmental Characteristics 8.3.1 Static Electricity All the equipment will perform their intended functions in a normal ESD environment. In order to reduce the ┆
0x3e200…3e300 (62, 0, 2) Sector 3e03ff00201241 ┆> Arisk of ESD-induced failures however, high-insulating floors should be avoided, and semiconducting floors should be used instead. The equipment will normally not be affected by a discharge through 500 Ohm from a 150 pF capacitor charged to 5kV. ┆
0x3e300…3e400 (62, 0, 3) Sector 3e04ff00201241 ┆> A 8.3.2 Electromagnetic Waves The equipment will function according to the specifications when exposed to an electromagnetic field of 1V/m in the frequency range from 30 MHz to 500 MHz. The equipment will not radiate electromagnetic waves stronge┆
0x3e400…3e500 (62, 0, 4) Sector 3e05ff00201241 ┆> Ar than specified in CISPR B (secr)16. 8.3.3 Interference on Power Feed Lines The equipment is as standard designed to be fed from 110 V AC source. All the equipment is supplied with siutable mains filters and are able to sustain noise pulses ┆
0x3e500…3e600 (62, 0, 5) Sector 3e06ff00201241 ┆> Aon main wires with amplitudes less than 1000V and rise time longer than 35nS, pulse duration 0.1 uS to 10uS and repetition rate less than one per second. The equipment will not emit more interference voltage on the mains wires than specified in CI┆
0x3e600…3e700 (62, 0, 6) Sector 3e071600201241 ┆> ASPR B (secr) 16.f 1g with 10 mS half-sine pulse. Not to be repeated more often than one per ten seconds. The units are furthermore able to withstand normal use and handling during service and maintenance periods. The different pieces of equipmen┆
0x3e700…3e800 (62, 0, 7) Sector 3d08ff00201241 ┆= A 1 8.3.4 Overvoltage Protection The equipment is not connected directly to the signalling lines, but to other equipment which then interfaces to the lines. It is therefore not necess┆
0x3e800…3e900 (62, 0, 8) Sector 3e096700201241 ┆> g A sand. The only moving parts are fan motors and switches, which are all of the encapsulated type. ┆
0x3e900…3ea00 (62, 0, 9) Sector 3e0aff00201241 ┆> A 1 The peripheral devices like printers and disc drivers contain more moving parts, and are therefore basically more sensitive to dust and sand. To avoid problems these units are there┆
0x3ea00…3eb00 (62, 0, 10) Sector 3e0bff00201241 ┆> Afore supplied with appropriate air filters and dust covers. In case of high contents of dust and sand the maintenance intervals between cleaning and replacement of air filters must be shortened. The equipment will not be discoloured or emit harm┆
0x3eb00…3ec00 (62, 0, 11) Sector 3e0ce500201241 ┆> e Aful substances when exposed to light or normal heating sources below 70 deg C. All metal parts are adequately protected against corrosion in a normal office environment by means of suitable forms of painting and plating. haracteristics 2 8.2.1 Ge┆
0x3ec00…3ed00 (62, 0, 12) Sector 3e0dff00201241 ┆> A 1 8.2.3 Storage and Transport Characteristics These limits apply to equipment properly packed for storage and transport. Temperature: -40 deg C to 70 deg C. Relative Humidity: 10┆
0x3ed00…3ee00 (62, 0, 13) Sector 3e0eff00201241 ┆> A%RH - 90%RH, non-condensing Absolute Humidity: 0.1g H 2 O/m 3 - 35g H 2 O/m 3 Altitude: 0-10000 m Sinusodial Vibration: Accelaration amplitude of 1.5 g limited by a displacement amplitude of 10 mm in the frequency range 5-150 Hz. Mec┆
0x3ee00…3ef00 (62, 0, 14) Sector 3e0fff00201241 ┆> Ahanical Shock: Shock accelaration amplitude of 25g with 10mS half-sine pulse. Note: These limits apply to the outer surfaces of the packaging container, not to the equipment inside. During transport and storage the equipment will be properly prot┆
0x3ef00…3f000 (62, 0, 15) Sector 3e00ff00201241 ┆> Aected against attacks from fungi,insects and rodents by the packaging material. Furthermore, the inherent properties of the different materials will also prevent such attacks on the equipment because they do not contain natural rubber,natural fibr┆
0x3f000…3f100 (63, 0, 0) Sector 3f01ff00201241 ┆? Ang CR Standards and Specifications. Unless otherwise stated, the Christian Rovsing equipment will furthermore be in accordance with the CCITT recommendations specified in the Christian Rovsing Technical Specification at the issue applicable at the┆
0x3f100…3f200 (63, 0, 1) Sector 3f02ca00201241 ┆? J A time of tender. 8.2 Climatic Environmental Characteristics 8.2.1 General The equipment is designed and constructed to be used in normal office environments or air conditioned computer rooms. >= AH1 R^4 ]M, C 4:>=2A=Ms!:g=~ Jr4Mj2:g=~ B}4C75! ┆
0x3f200…3f300 (63, 0, 2) Sector 3f03ff00201241 ┆? A 1 8.2.2 Operating Characteristics These limits apply to the equipment installed as specified and operating or under maintenance in a normal office or computer room environment: 1 ┆
0x3f300…3f400 (63, 0, 3) Sector 3f04ff00201241 ┆? A Room Temperature: 15 deg C - 32 deg C Temperature Change: Less than 6 deg C/hour Relative Humidity: 20% RH - 80% RH non-con- ┆
0x3f400…3f500 (63, 0, 4) Sector 3f05ff00201241 ┆? A densing Humidity Change: Less than 10% RH/hour Absolute Humidity: Less than 22g H 2 O/m 3 air Altitude: 0-2000m Sinusodial Vibration: Accelaration amplitude of 0.2┆
0x3f500…3f600 (63, 0, 5) Sector 3f06ff00201241 ┆? A g limited by a maximum displacement amplitude of 0.02mm in the frequency range 5-150Hz Mechanical Shock: Shock accelara┆
0x3f600…3f700 (63, 0, 6) Sector 3f07ff00201241 ┆? Ation amplitude of 1g with 10 mS half-sine pulse. Not to be repeated more often than one per ten seconds. The units are furthermore able to withstand normal use and handling during service and maintenance periods. The different pieces of equipmen┆
0x3f700…3f800 (63, 0, 7) Sector 3e08ff00201241 ┆> At are designed to operate in the comparatively benign environment in normal offices or computer rooms. They are therefore able to tolerate normal amounts of dust and sand. The CR80 equipment itself is very insensitive to normal amounts of dust and┆
0x3f800…3f900 (63, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(63,0, 9), len=0xff, h3=41201241}, f00=»2012A «, f01=»Air Canada Proposal «, f02=»ut «, f03=»HBA «, f04=»DOC III Chapt. 8 «, f05=14-04-82 14:10, f06=» «, f07=»11 «, f08=» 298 «, f09=24-04-82 13:48, f10=» «, f11=»01 «, f12=» 23 «, f13=14-04-82 15:01, f14=26-04-82 22:15, f15=»0157A «, f16=» 14 «, f17=» «, f18=»12 «, f19=» 224 «, f20=» 329 «, f21=» «, f22=» «, f99=100010000110056610110180aaca15050000000000000042034600df}
0x3f900…3fa00 (63, 0, 9) Sector 3f0a0e00201241 ┆? A ? ? ? ? > > > > = = = < 6 6 DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG Oprettet / / : : S S┆
0x3fa00…3fb00 (63, 0, 10) Sector 3f0bfb00201241 ┆? { A 1 CHAPTER 8 Page # DOCUMENT III TECHNICAL PROPOSAL Apr. 29, 1982 .=M2┆
0x3fb00…3fc00 (63, 0, 11) Sector 3f0cff00201241 ┆? A 1 LIST OF CONTENTS Page 8. ENVIRONMENTAL CHARACTERISTICS & COMMON ASPECTS 2 8.1 General 2 8.2 Climatic Environmental Characteristics 2 8.2.1 Ge┆
0x3fc00…3fd00 (63, 0, 12) Sector 3f0dff00201241 ┆? Aneral 2 8.2.2 Operating Characteristics 3 8.2.3 Storage and Transport Characteristics 5 8.3 Electrical Environmental Characteristics 6 8.3.1 Static Electricity 6 8.3.2 Electromagnetic Waves 6 8.3.3 Interference on Power Feed Lines 6 8.3.4 ┆
0x3fd00…3fe00 (63, 0, 13) Sector 3f0eff00201241 ┆? AOvervoltage Protection 7 8.4 Common Aspect 8 8.4.1 Safety 8 8.4.2 Human Engineering 9 8.4.3 Maintenance and Repair 9 8.4.4 Expandability 11 8.4.5 System Life Time 11 8.4.6 Components 12 8.4.7 Testing 13 8.4.8 Marking 13 8.4.9 Changeabl┆
0x3fe00…3ff00 (63, 0, 14) Sector 3f0f4c00201241 ┆? L Ae Marking 13 8.4.10 Mechanical Dimensions 14 8.4.11 Power Supplies 14 sM & E 0= u M% :^=~ Bl1{M40sI:^=~ J 1!"<6;!#<6 !&<6 ! "$<! <6 {M;(s! 9"c=! "(= Z=q#p!"<6 !&<6 ! "$<!#<6 ! <6 {M)(sC I! <6 ! "(= <q#p!"<6 !#<6 ! "$<!&<6$`i6 {M)(sM &M7 ┆
0x3ff00…40000 (63, 0, 15) Sector 3f00ff00201241 ┆? A 1 8. ENVIRONMENTAL CHARACTERISTICS AND COMMON ASPECTS 8.1 General The Christian Rovsing equipment will be designed,manufactured,tested, and installed according to the prevaili┆
0x40000…40100 (64, 0, 0) Sector 4001ff00202541 ┆@ %A paging. Messages are transmitted from one PU to the memory of another via the Supra Net. As all data transfers via the Supra Net are approved by both PU's Memory Map, full hardware protection against unintended interference between PU's is ensured.┆
0x40100…40200 (64, 0, 1) Sector 4002ff00202541 ┆@ %A The PU is highly flexible because the selectance of contained modules can be changed. The modules are interfaced via a dual bus structure for reduction of bus contention as shown in figure below. Figure III 5.3.┆
0x40200…40300 (64, 0, 2) Sector 40031000202541 ┆@ %A1.2.1.1 5. EQUIPMENT CHARACTERISTICS 5.1 Introduction The scope of this chapter is to show how the proposed network are configured with dedicated CR80 processor systems. A descriptio┆
0x40300…40400 (64, 0, 3) Sector 4004ff00202541 ┆@ %A 1 5.3.1.2.2 The Channel Units (CU) contain the CR80 I/O Controller modules for interfacing towards peripheral equipment, communication lines etc. The CU has an internal dual transfe┆
0x40400…40500 (64, 0, 4) Sector 4005ca00202541 ┆@ J %Ar bus structure to ensure that no single failure can stop operation of more than one I/O Controller as shown in the figure below. Figure III 5.3.1.2.2.1 ed up to 256 M bps. Around the "site supra net" the┆
0x40500…40600 (64, 0, 5) Sector 4006ff00202541 ┆@ %A 1 The transfer buses, Data Bus A and Data Bus B, are connected to two different PU's to ensure continuous access to the controller modules (CTRL, LTU). The characteristics of Data Bu┆
0x40600…40700 (64, 0, 6) Sector 4007ff00202541 ┆@ %As A and Data Bus B correspond to the internal buses of the PU. The CIA-modules constitute the interface between the word oriented internal transfer buses and the byte oriented Data Channels. The I/O Controller modules are all based on the same p┆
0x40700…40800 (64, 0, 7) Sector 1908bd00202541 ┆ = %Arinciple for interfacing to the Channel Unit bus structure and for the external interfaces as illustrated in figure below. Figure III 5.3.1.2.2.2 ┆
0x40800…40900 (64, 0, 8) Sector 4009aa00202541 ┆@ * %A 1 PROPOSED NETWORK CONFIGURATION Fig. III.5.2.1 ┆
0x40900…40a00 (64, 0, 9) Sector 400aff00202541 ┆@ %A 1 5.3 System Configuration 5.3.1 Network Elements Each individual subsystem is described, and on related figures the subsystem is shown in block diagrams. Furthermore rach and crat┆
0x40a00…40b00 (64, 0, 10) Sector 400b7c00202541 ┆@ | %Ae layout is shown. 5.3.1.1 Computing Elements The overall proposed computing elements are CR80 system elements. CHAPTER 5 Page # DOCUMENT III TECHNICAL PROPOSAL Apr. 29, 1982 .=M2┆
0x40b00…40c00 (64, 0, 11) Sector 400cff00202541 ┆@ %A 1 5.3.1.2 CR80 General Description The Network elements are constructed by means of the modular fault tolerant CR80 computer system by use of various standard modules (Printed Circu┆
0x40c00…40d00 (64, 0, 12) Sector 400de800202541 ┆@ h %Ait Boards) organized in units which are interconnected by galvanic isolated transfer bus structured as illustrated below, and shortly described in the following. Figure III 5.3.1.2.1 .3.1.2.7 Mechanical Dim┆
0x40d00…40e00 (64, 0, 13) Sector 400eff00202541 ┆@ %A 1 The CR80 system units are housed in 19" Crates (Card Magazine) for installation in standard 19" Racks as shown in figure below. Figur┆
0x40e00…40f00 (64, 0, 14) Sector 400f1700202541 ┆@ %Ae III 5.3.1.2.2 ent Processor 5.3.3.4 Electronic Mail Processor 5.3.3.5 Channel Units. 5.3.4 Network Nodes general 5.3.4.1 Node Toronto 5.3.4.1.1 Configuration 5.3.4.1.2 Equipment List 5.3.4.2 Node Montreal 5.3.4.2.1 Configuration 5.3.4.2.2 Equipm┆
0x40f00…41000 (64, 0, 15) Sector 4000ff00202541 ┆@ %A 1 5.3.1.2.1 The Processor Units (PU) The PU is a multiprogrammable multiprocessor (up to 5 central processor Units CPU's) utilizing virtual memory (16 mega 16 bits words) and demand┆
0x41000…41100 (65, 0, 0) Sector 4101ff00202541 ┆A %A 1 LIST OF CONTENTS Page 5.4 Electrical Interfaces 5.4.1 Host Interfaces 5.4.1.1 Univac Interface 5.4.1.2 IBM Interface 5.4.1.3 Other Host Interfaces 5.4.2 ┆
0x41100…41200 (65, 0, 1) Sector 41026a00202541 ┆A j %ACommunication Interfaces 5.4.2.1 X20 bis, X21 bis, V24 5.4.2.2 X21 5.4.2.3 X75 5.4.3 LIA-S Option Mj ~ B 4:g=~ J 4Cq5M")IMy,M1' R 4 'M, CV4:g=~ Bg4M73~ B)4Cq5! ="(=*(=N#FMC 2.=M ':>=V V u:A=!>= AH1 R^4 ]M, C 4:>=2A=Ms!:g=~ Jr4Mj2:g=~ B}4C75! ┆
0x41200…41300 (65, 0, 2) Sector 4103ff00202541 ┆A %A 1 5. EQUIPMENT CHARACTERISTICS 5.1 Introduction The scope of this chapter is to show how the proposed network are configured with dedicated CR80 processor systems. A descriptio┆
0x41300…41400 (65, 0, 3) Sector 4104ff00202541 ┆A %An of the flexible CR80 architecture are given in section 5.3, and at last the configuration drawings and equipment lists for the different computers are given. 5.2 Network Configuration The proposed network are based on 3 sites, and can in a mo┆
0x41400…41500 (65, 0, 4) Sector 4105ff00202541 ┆A %Adular way be expanded to an unlimited number of sites. The sites themselves are computer systems built around a high speed dualized "site supra net" with a speed of 16 M bps. which can be expanded up to 256 M bps. Around the "site supra net" the┆
0x41500…41600 (65, 0, 5) Sector 4106ff00202541 ┆A %A different CR80 computer systems are placed, as shown in figure III 5.2.1. The types of CR80 computer systems which are proposed to interface to the "site supra net" are: NSP: Nodal Switch Processor NCP: Nodal Control Processor NMH: Network Ma┆
0x41600…41700 (65, 0, 6) Sector 4107ff00202541 ┆A %Anagement Host EMH: Electronic Mail Host It is underlined that each of the above mentioned systems are totally independent computer systems, only connected to one or more of the others by the "Site Supra Net". In this way it is seen that expansi┆
0x41700…41800 (65, 0, 7) Sector 40088100202541 ┆@ %Aon with new or existing functions are simply done by adding new CR80 computer systems to the existing "Site Supra Net". ┆
0x41800…41900 (65, 0, 8) Sector 4109ff41202541 ┆A A %A2025A AIR CANADA PROPOSAL pc LSJ Chapter 5. 15 04 82 15 19 52 5640 26 04 82 21 56 01 5 26 04 82 21 03 26 04 82 22 15 0157A 63 5 13 600 23488 f *J B K _┆
0x41900…41a00 (65, 0, 9) Sector 410a3f00202541 ┆A ? %A A A A A @ @ @ @ @ @ @ IGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO T T T T┆
0x41a00…41b00 (65, 0, 10) Sector 410bfb00202541 ┆A { %A 1 CHAPTER 5 Page # DOCUMENT III TECHNICAL PROPOSAL Apr. 29, 1982 .=M2┆
0x41b00…41c00 (65, 0, 11) Sector 410cff00202541 ┆A %A 1 LIST OF CONTENTS Page 5. EQUIPMENT CHARACTERISTICS 5.1 Introduction 5.2 Network Configuration 5.3 System Configuration 5.3.1 Network Elements 5.3.1.1 ┆
0x41c00…41d00 (65, 0, 12) Sector 410dff00202541 ┆A %AComputing Elements 5.3.1.2 CR80 General Description 5.3.1.2.1 The Processor Units (PU) 5.3.1.2.2 The Channel Units (CU) 5.3.1.2.3 Bus Structures 5.3.1.2.4 Watchdog System 5.3.1.2.5 CR80 Modules 5.3.1.2.6 Peripheral Equipment 5.3.1.2.7 Mechanical Dim┆
0x41d00…41e00 (65, 0, 13) Sector 410eff00202541 ┆A %Aensions 5.3.1.2.7.1 Rack Dimensions 5.3.1.2.7.2 Peripheral Dimensions 5.3.1.2.8 Power Consumption 5.3.2 H/W Monitor 5.3.2.1 Automatic Test Equipment 5.3.3 Network elements 5.3.3.1 Nodal Switch Processor 5.3.3.2 Nodal Control Processor 5.3.3.┆
0x41e00…41f00 (65, 0, 14) Sector 410fff00202541 ┆A %A3 Network Management Processor 5.3.3.4 Electronic Mail Processor 5.3.3.5 Channel Units. 5.3.4 Network Nodes general 5.3.4.1 Node Toronto 5.3.4.1.1 Configuration 5.3.4.1.2 Equipment List 5.3.4.2 Node Montreal 5.3.4.2.1 Configuration 5.3.4.2.2 Equipm┆
0x41f00…42000 (65, 0, 15) Sector 4100fa00202541 ┆A z %Aent List 5.3.4.3 Node Winnipeg 5.3.4.3.1 Configuration 5.3.4.3.2 Equipment List 5.3.5 Electronic Mail Host 5.3.5.1 Configuration 5.3.5.2 Equipment List 5.3.6 Standard Expansion 5.3.6.1 Expansion Element Configurations 5.3.6.2 Equipment List I:A=!┆
0x42000…42100 (66, 0, 0) Sector 4201ff00202541 ┆B %A paging. Messages are transmitted from one PU to the memory of another via the Supra Net. As all data transfers via the Supra Net are approved by both PU's Memory Map, full hardware protection against unintended interference between PU's is ensured.┆
0x42100…42200 (66, 0, 1) Sector 4202ff00202541 ┆B %A The PU is highly flexible because the selectance of contained modules can be changed. The modules are interfaced via a dual bus structure for reduction of bus contention as shown in figure below. Figure III 5.3.┆
0x42200…42300 (66, 0, 2) Sector 42031000202541 ┆B %A1.2.1.1 5. EQUIPMENT CHARACTERISTICS 5.1 Introduction The scope of this chapter is to show how the proposed network are configured with dedicated CR80 processor systems. A descriptio┆
0x42300…42400 (66, 0, 3) Sector 4204ff00202541 ┆B %A 1 5.3.1.2.2 The Channel Units (CU) contain the CR80 I/O Controller modules for interfacing towards peripheral equipment, communication lines etc. The CU has an internal dual transfe┆
0x42400…42500 (66, 0, 4) Sector 4205ca00202541 ┆B J %Ar bus structure to ensure that no single failure can stop operation of more than one I/O Controller as shown in the figure below. Figure III 5.3.1.2.2.1 ed up to 256 M bps. Around the "site supra net" the┆
0x42500…42600 (66, 0, 5) Sector 4206ff00202541 ┆B %A 1 The transfer buses, Data Bus A and Data Bus B, are connected to two different PU's to ensure continuous access to the controller modules (CTRL, LTU). The characteristics of Data Bu┆
0x42600…42700 (66, 0, 6) Sector 4207ff00202541 ┆B %As A and Data Bus B correspond to the internal buses of the PU. The CIA-modules constitute the interface between the word oriented internal transfer buses and the byte oriented Data Channels. The I/O Controller modules are all based on the same p┆
0x42700…42800 (66, 0, 7) Sector 4108bd00202541 ┆A = %Arinciple for interfacing to the Channel Unit bus structure and for the external interfaces as illustrated in figure below. Figure III 5.3.1.2.2.2 ┆
0x42800…42900 (66, 0, 8) Sector 4209aa00202541 ┆B * %A 1 PROPOSED NETWORK CONFIGURATION Fig. III.5.2.1 ┆
0x42900…42a00 (66, 0, 9) Sector 420aff00202541 ┆B %A 1 5.3 System Configuration 5.3.1 Network Elements Each individual subsystem is described, and on related figures the subsystem is shown in block diagrams. Furthermore rach and crat┆
0x42a00…42b00 (66, 0, 10) Sector 420b7c00202541 ┆B | %Ae layout is shown. 5.3.1.1 Computing Elements The overall proposed computing elements are CR80 system elements. CHAPTER 5 Page # DOCUMENT III TECHNICAL PROPOSAL Apr. 29, 1982 .=M2┆
0x42b00…42c00 (66, 0, 11) Sector 420cff00202541 ┆B %A 1 5.3.1.2 CR80 General Description The Network elements are constructed by means of the modular fault tolerant CR80 computer system by use of various standard modules (Printed Circu┆
0x42c00…42d00 (66, 0, 12) Sector 420de800202541 ┆B h %Ait Boards) organized in units which are interconnected by galvanic isolated transfer bus structured as illustrated below, and shortly described in the following. Figure III 5.3.1.2.1 .3.1.2.7 Mechanical Dim┆
0x42d00…42e00 (66, 0, 13) Sector 420eff00202541 ┆B %A 1 The CR80 system units are housed in 19" Crates (Card Magazine) for installation in standard 19" Racks as shown in figure below. Figur┆
0x42e00…42f00 (66, 0, 14) Sector 420f1700202541 ┆B %Ae III 5.3.1.2.2 ent Processor 5.3.3.4 Electronic Mail Processor 5.3.3.5 Channel Units. 5.3.4 Network Nodes general 5.3.4.1 Node Toronto 5.3.4.1.1 Configuration 5.3.4.1.2 Equipment List 5.3.4.2 Node Montreal 5.3.4.2.1 Configuration 5.3.4.2.2 Equipm┆
0x42f00…43000 (66, 0, 15) Sector 4200ff00202541 ┆B %A 1 5.3.1.2.1 The Processor Units (PU) The PU is a multiprogrammable multiprocessor (up to 5 central processor Units CPU's) utilizing virtual memory (16 mega 16 bits words) and demand┆
0x43000…43100 (67, 0, 0) Sector 4301ff00202541 ┆C %A 1 LIST OF CONTENTS Page 5.4 Electrical Interfaces 5.4.1 Host Interfaces 5.4.1.1 Univac Interface 5.4.1.2 IBM Interface 5.4.1.3 Honeywell Interface 5.4.1.4 O┆
0x43100…43200 (67, 0, 1) Sector 43029f00202541 ┆C %Ather Host Interfaces 5.4.2 Communication Interfaces 5.4.2.1 X20 bis, X21 bis, V24 5.4.2.2 X21 5.4.2.3 X75 5.4.3 Future Interfaces 5.4.4 LIA-S Option 3~ B)4Cq5! ="(=*(=N#FMC 2.=M ':>=V V u:A=!>= AH1 R^4 ]M, C 4:>=2A=Ms!:g=~ Jr4Mj2:g=~ B}4C75! ┆
0x43200…43300 (67, 0, 2) Sector 4303ff00202541 ┆C %A 1 5. EQUIPMENT CHARACTERISTICS 5.1 Introduction The scope of this chapter is to show how the proposed network are configured with dedicated CR80 processor systems. A descriptio┆
0x43300…43400 (67, 0, 3) Sector 4304ff00202541 ┆C %An of the flexible CR80 architecture are given in section 5.3, and at last the configuration drawings and equipment lists for the different computers are given. 5.2 Network Configuration The proposed network are based on 3 sites, and can in a mo┆
0x43400…43500 (67, 0, 4) Sector 4305ff00202541 ┆C %Adular way be expanded to an unlimited number of sites. The sites themselves are computer systems built around a high speed dualized "site supra net" with a speed of 16 M bps. which can be expanded up to 256 M bps. Around the "site supra net" the┆
0x43500…43600 (67, 0, 5) Sector 4306ff00202541 ┆C %A different CR80 computer systems are placed, as shown in figure III 5.2.1. The types of CR80 computer systems which are proposed to interface to the "site supra net" are: NSP: Nodal Switch Processor NCP: Nodal Control Processor NMH: Network Ma┆
0x43600…43700 (67, 0, 6) Sector 4307ff00202541 ┆C %Anagement Host EMH: Electronic Mail Host It is underlined that each of the above mentioned systems are totally independent computer systems, only connected to one or more of the others by the "Site Supra Net". In this way it is seen that expansi┆
0x43700…43800 (67, 0, 7) Sector 42088100202541 ┆B %Aon with new or existing functions are simply done by adding new CR80 computer systems to the existing "Site Supra Net". ┆
0x43800…43900 (67, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(67,0, 9), len=0xff, h3=41202541}, f00=»2025A «, f01=»AIR CANADA PROPOSAL «, f02=»pc «, f03=»LSJ «, f04=»Chapter 5. «, f05=15-04-82 15:19, f06=» «, f07=»52 «, f08=» 5640 «, f09=25-04-82 15:45, f10=» «, f11=»08 «, f12=» 505 «, f13=25-04-82 16:25, f14=25-04-82 19:17, f15=»0157A «, f16=» 65 «, f17=» 5 «, f18=»00 «, f19=» 624 «, f20=» 23188 «, f21=» «, f22=» «, f99=020010000110046610110480aaca1505000000000000004203d500df}
0x43900…43a00 (67, 0, 9) Sector 430a4100202541 ┆C A %A C C C C B B B B B B B A A IGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO T T┆
0x43a00…43b00 (67, 0, 10) Sector 430bfb00202541 ┆C { %A 1 CHAPTER 5 Page # DOCUMENT III TECHNICAL PROPOSAL Apr. 29, 1982 .=M2┆
0x43b00…43c00 (67, 0, 11) Sector 430cff00202541 ┆C %A 1 LIST OF CONTENTS Page 5. EQUIPMENT CHARACTERISTICS 5.1 Introduction 5.2 Network Configuration 5.3 System Configuration 5.3.1 Network Elements 5.3.1.1 ┆
0x43c00…43d00 (67, 0, 12) Sector 430dff00202541 ┆C %AComputing Elements 5.3.1.2 CR80 General Description 5.3.1.2.1 The Processor Units (PU) 5.3.1.2.2 The Channel Units (CU) 5.3.1.2.3 Bus Structures 5.3.1.2.4 Watchdog System 5.3.1.2.5 CR80 Modules 5.3.1.2.6 Peripheral Equipment 5.3.1.2.7 Mechanical Dim┆
0x43d00…43e00 (67, 0, 13) Sector 430eff00202541 ┆C %Aensions 5.3.1.2.7.1 Rack Dimensions 5.3.1.2.7.2 Peripheral Dimensions 5.3.1.2.8 Power Consumption 5.3.2 H/W Monitor 5.3.2.1 Automatic Test Equipment 5.3.3 Network elements 5.3.3.1 Nodal Switch Processor 5.3.3.2 Nodal Control Processor 5.3.3.┆
0x43e00…43f00 (67, 0, 14) Sector 430fff00202541 ┆C %A3 Network Management Processor 5.3.3.4 Electronic Mail Processor 5.3.3.5 Channel Units. 5.3.4 Network Nodes general 5.3.4.1 Node Toronto 5.3.4.1.1 Configuration 5.3.4.1.2 Equipment List 5.3.4.2 Node Montreal 5.3.4.2.1 Configuration 5.3.4.2.2 Equipm┆
0x43f00…44000 (67, 0, 15) Sector 4300fa00202541 ┆C z %Aent List 5.3.4.3 Node Winnipeg 5.3.4.3.1 Configuration 5.3.4.3.2 Equipment List 5.3.5 Electronic Mail Host 5.3.5.1 Configuration 5.3.5.2 Equipment List 5.3.6 Standard Expansion 5.3.6.1 Expansion Element Configurations 5.3.6.2 Equipment List I:A=!┆
0x44000…44100 (68, 0, 0) Sector 4401e100205441 ┆D a TA PASCAL. Over and above these considerations, certain aspects of software structuring have been adopted that facilitates understanding in terms of mainframe communication architecture like IBM's SNA and Univac's DCA. ┆
0x44100…44200 (68, 0, 1) Sector 4402ffdd205441 ┆D ] TA 1 6.1 Introduction The software proposed for the ACDN is anchored on existing networking solutions from Christian Rovsing,and is supported by the system software for the CR80,namely┆
0x44200…44300 (68, 0, 2) Sector 4403ffdd205441 ┆D ] TA DAMOS. Section 6.2 introduces the functions and facilities of DAMOS. Section 6.3 focuses on a key internal transport mechanisms designated as Basic Transport Service (BTS) and Basic Datagram Service (BDS) that is a part of the DAMOS Kernel. ┆
0x44300…44400 (68, 0, 3) Sector 4404ffdd205441 ┆D ] TASection 6.4 introduces data flow aspects and table structures. This section provides a first level bridge between concepts introduced in Chapter 3 and functional software description that follows in 6.5 to 6.11. Section 6.5 to 6.11 describes the ┆
0x44400…44500 (68, 0, 4) Sector 4405d1dd205441 ┆D Q] TAsoftware complexion and functions of NSS, TAS, HAS, interfaces to other networks, NCS and Network Management Subsystem. Section 6.12 presents the electronic mail system oriented software capabilities. n User Environment (CUE)....... 6.5.1.1 ┆
0x44500…44600 (68, 0, 5) Sector 4406ffdd205441 ┆D ] TA 1 6.1.1 Design Goals The Christian Rovsing network solution is designed to create a communication mechanism to support a wide range of user applications, host computer systems and i┆
0x44600…44700 (68, 0, 6) Sector 4407ff00205441 ┆D TAnterconnect technologies. Specifically, the goals are the following: 1. Create a Common User Interface: The application interface to the network should support a broad spectrum of application communication requirements and should be common acros┆
0x44700…44800 (68, 0, 7) Sector 2d00ff00205441 ┆- TAs the varied implementations. Within such a network environment, applications may be moved among the systems in the network, with the common interface hiding the internal characteristics and topology of the network. 2. Support a Wide Range of Comm┆
0x44800…44900 (68, 0, 8) Sector 4409ff00205441 ┆D TAion Service (VTCS). 6.5.2.3.1 VTCS Standards.............................. 6.5.2.4 Data Link Environment....................... 6.8 Internal Network Access Software............ 6.8.1 ACDN Interfaces..........................┆
0x44900…44a00 (68, 0, 9) Sector 440aff00205441 ┆D TA... 6.8.2 Network Interface........................... 6.8.3 Modules of the Internal Network Access S/W.. 6.8.3.1 The ICC Module.............................. 6.11 Network Management Host Software............ 6.11.1 NM┆
0x44a00…44b00 (68, 0, 10) Sector 440bff00205441 ┆D TAH Interfaces and Functional Overview...... 6.11.2 Software Development and Maintenance Functions 6.11.3 Maintenance of the Data Base................ 6.11.4 Data Base Management System User Groups..... 6.11.5 Data Base Managemen┆
0x44b00…44c00 (68, 0, 11) Sector 440cff00205441 ┆D TAt Tools.................. 6.11.6 Report Generation........................... 6.11.7 Network Modelling Software and Support for Automatic Network Tests..................... 6.11.8 Network Testing by Means of ATES............ ┆
0x44c00…44d00 (68, 0, 12) Sector 440db300205441 ┆D 3 TA 6.12 Electronic Mail Software Package............ 6.12.1 Interfaces to the EMH....................... 6.12.2 Functional Description of the EMH .......... 10 4 0 1 1 1989 5 5 90 11 7 0 0 0 1990 5 5 99 13 6 1 1 1 1991 6 6 10┆
0x44d00…44e00 (68, 0, 13) Sector 440eff00205441 ┆D TA 1 6. SOFTWARE CHARACTERISTICS This section attempts to present a comprehensive view of the software structure supporting the proposed ACDN. To assist in understanding the implied s┆
0x44e00…44f00 (68, 0, 14) Sector 440fff00205441 ┆D TAoftware linkages, certain typical and relevant data flow descriptions are presented. The primary design objectives for the networking software provided by Christian Rovsing has been: - a realistic adherence to the proposed architecture for Open ┆
0x44f00…45000 (68, 0, 15) Sector 4400ff00205441 ┆D TASystems Interconnection - a well conceived strategy to exploit the inherent architectural strength of the CR80 environment. (this is illustrated by software components BTS & BDS) - exploitation of the program development environment supported by┆
0x45000…45100 (69, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(69,0, 1), len=0xff, h3=41205441}, f00=»2054A «, f01=»AIR CANADA PROPOSAL «, f02=»ut «, f03=»MEB «, f04=»DOC. III Chapter 6 «, f05=21-04-82 12:17, f06=» 4 «, f07=»23 «, f08=» 23589 «, f09=25-04-82 18:21, f10=» «, f11=»43 «, f12=» 1324 «, f13=25-04-82 17:56, f14=25-04-82 19:17, f15=»0157A «, f16=» 59 «, f17=» 11 «, f18=»26 «, f19=» 1044 «, f20=» 64788 «, f21=» «, f22=» 0 «, f99=440093000110056610110480aaca15050000000000000042032301df}
0x45100…45200 (69, 0, 1) Sector 45023b00205441 ┆E ; TA E E D D D - , , , , , + + + * * * * ) ) ) ) ) ( ( ( ' ' ' ' & & % % % % $ $ $ $ # # " " ! ! DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Foat]r: Fovn: Operat]r: Foat]r: ┆
0x45200…45300 (69, 0, 2) Sector 4503fb00205441 ┆E { TA 1 CHAPTER 6 Page # DOCUMENT III TECHNICAL PROPOSAL Apr. 29, 1982 .=M2┆
0x45300…45400 (69, 0, 3) Sector 4504ff00205441 ┆E TA 1 LIST OF CONTENTS Page 6. SOFTWARE CHARACTERISTICS.................... 6.1 Introduction................................ 6.1.1 Design Goals.........................┆
0x45400…45500 (69, 0, 4) Sector 4505ff00205441 ┆E TA....... 6.1.2 Network Topology............................ 6.1.3 C-NODE Software Structure................... 6.5 Communications Environment.................. 6.5.1 Commmunication User Environment (CUE)....... 6.5.1.1 ┆
0x45500…45600 (69, 0, 5) Sector 4506ff00205441 ┆E TASession-Conversion Management............... 6.5.1.1.1 Session-Conversation Establishment.......... 6.5.1.1.2 Session-Conversation Data Transfer.......... 6.5.1.1.3 Session-Conversation Termination............ 6.5.2 Data Tran┆
0x45600…45700 (69, 0, 6) Sector 4507ff00205441 ┆E TAsmission Environment............... 6.5.2.1 DTrE Services............................... 6.5.2.2 Datagram Services (DGS)..................... 6.5.2.2.1 Addressing Structure........................ 6.5.2.2.2 Datagram Format...┆
0x45700…45800 (69, 0, 7) Sector 4408ff00205441 ┆D TA.......................... 6.5.2.2.3 Datagram Primitives......................... 6.5.2.2.4 Datagram Routing............................ 6.5.2.2.5 Flow and Congestion Control................. 6.5.2.3 Virtual Transport Connect┆
0x45800…45900 (69, 0, 8) Sector 00000000000000 ┆ ┆
[…0x77…]
