OctetView
0x00000…00100 (0, 0, 0) Sector 02104130323130 ┆ A0210A ┆
0x00100…00200 (0, 0, 1) Sector 00000000000000 ┆ ┆
0x00200…00300 (0, 0, 2) Sector ff00f8ffffffff ┆ x @@ ┆
0x00300…00306 (0, 0, 3) WangDocument {d00=0x24, d01=0x12, d02=0x41, ptr=(23,0, 8), d05=0x00}
0x00306…0030c WangDocument {d00=0x24, d01=0x92, d02=0x41, ptr=(38,0, 0), d05=0x00}
0x0030c…00312 WangDocument {d00=0x34, d01=0x57, d02=0x41, ptr=(40,0, 0), d05=0x00}
0x00312…00318 WangDocument {d00=0x34, d01=0x90, d02=0x41, ptr=(54,0, 0), d05=0x00}
0x00318…00320 34 90 41 36 00 00 00 00 ┆4 A6 ┆
0x00320…00340 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ ┆
[…0x5…]
0x003e0…00400 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 18 ┆ ┆
0x00400…00500 (0, 0, 4) Sector 00000000000000 ┆ ┆
0x00500…00600 (0, 0, 5) Sector 86312020202020 ┆ 1 8 7 Q? > 7 | ] d N ~< v <.&4'>( 1c5 & & ┆
0x00600…00700 (0, 0, 6) Sector 421c402600415b ┆B @& A[' / X% % PO P ; $ A C g x g V W O : 2412A g < {C < { ; 2 % h ┆
0x00700…00800 (0, 0, 7) Sector 00000000000000 ┆ ┆
[…0x8…]
0x01000…01100 (1, 0, 0) WangDocumentBody
[…0x4…]
0x01500…01600 (1, 0, 5) Sector 0106ff00241241 ┆ $ A 1 WBS Title 5 QA 6 Reliability 7 Transport and Installation 8 Acceptance Testing 9 Training 10 ┆
0x01600…01700 (1, 0, 6) Sector 0107ae00241241 ┆ . $ A Maintenance and Spares / TEST EQ & TOOLS/NATO CODIFICATION 11 Documentation 12 Options 6.4 Planning Network The PIP - to be created at pment efforts. 5.10.4 Problem Resolution Whenever internal problems and devia┆
0x01700…01800 (1, 0, 7) Sector 00006900241241 ┆ i $ Athe start of the project - will include a Planning Network showing work package interdependencies. Manager takes action if responsibility for the problem discovered is difficult to place. Questions relating to the financial and economic schedules┆
0x01800…01900 (1, 0, 8) WangDocumentBody
[…0x15f…]
0x17800…17900 (23, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(23,0, 9), len=0xff, h3=41241241}, f00=»2412A «, f01=»Management Proposal (1) «, f02=»ja «, f03=»ART «, f04=»Revised Edition «, f05=02-07-82 14:04, f06=» 1 «, f07=»40 «, f08=» 2372 «, f09=26-10-82 14:17, f10=» «, f11=»00 «, f12=» 12 «, f13=25-10-82 15:55, f14=15-11-83 17:54, f15=»0210A «, f16=» 82 «, f17=» 5 «, f18=»15 «, f19=» 1124 «, f20=» 16520 «, f21=» «, f22=» «, f99=020008000220056610110401aaca15050000000000000142036d01df}
0x17900…17a00 (23, 0, 9) WangDocumentBody
[…0x7…]
0x18100…18200 (24, 0, 1) Sector 1802ff00249241 ┆ $ A The calculated availability of 99,6% is higher than the requested reliability of 99%. These reliability figures give the availability for a completety operational system, but the equipment figures show that it is the peripheral equip┆
0x18200…18300 (24, 0, 2) Sector 1803bb00249241 ┆ ; $ Ament like VDU and printers, which are most unreliable. Because these items are multiredundent in the MEDS the availability of a partly but acceptable working system is much higher. e taking into account the individual demands of each project and cus┆
0x18300…18400 (24, 0, 3) Sector 00004a00249241 ┆ J $ A 1 12.4.2 Corrective Maintenance Corrective maintenance, i.e. fault identification and module replacement will be carried out by the site technician. Repair of defective subassemblie┆
0x18400…18500 (24, 0, 4) Sector 1805ff00109441 ┆ A 1 Time Stamp Time allocated to a transaction, for example a storage process or release of message. Timer monitor The part of CSF supplying timer facilities. Tracing Retrieval of ┆
0x18500…18600 (24, 0, 5) Sector 1806ff00109441 ┆ Aspecific log records. Translation Table A table used by Memory Map Module to perform logical address to physical address translation and determination of access right to memory locations. User a) Person with responsibility for input and output o┆
0x18600…18700 (24, 0, 6) Sector 1807ff00109441 ┆ Af messages. b) Person located at the user terminals in the staff cells. The user is identical with the term operator in the CPS/210/SYS/0001 and replaces it in CPS/SDS/001. User Group A set of processes. A vehicle for access control each pro┆
0x18700…18800 (24, 0, 7) Sector 1708ff00109441 ┆ Acess belongs to exactly one user group. User Group Unique identifier for a user group Identification User process Process within CAMPS representing a logical line. User profile To each user a user profile is associated. (Identical to operator┆
0x18800…18900 (24, 0, 8) WangDocumentBody
[…0xd7…]
0x26000…26100 (38, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(38,0, 1), len=0xff, h3=41249241}, f00=»2492A «, f01=»MWHQ (part 3) «, f02=»amn «, f03=»ART «, f04=»Revised Edition «, f05=20-07-82 09:47, f06=» 1 «, f07=»35 «, f08=» 7639 «, f09=25-10-82 14:36, f10=» «, f11=»02 «, f12=» 36 «, f13=25-10-82 13:32, f14=08-03-83 10:21, f15=»0210A «, f16=» 65 «, f17=» 10 «, f18=»00 «, f19=» 632 «, f20=» 39642 «, f21=» «, f22=» 0 «, f99=830033000210056610110480aaca1505000000000000004203e100df}
0x26100…26200 (38, 0, 1) WangDocumentBody
[…0x8…]
0x26a00…26b00 (38, 0, 10) Sector 260b8e00249241 ┆& $ A 1 SYS/820728 # PART III ENGINEERING PROPOSAL MWHQ-MEDS =6'C*-:!<~ B%-!/=6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x26b00…26c00 (38, 0, 11) Sector 260c9800249241 ┆& $ A 1 PART III ENGINEERING PROPOSAL MWHQ MESSAGE ENTRY and DISTRIBUTION SYSTEM :]=2#<:^=~ J6.! <6 M8) R6.> I! <6 M8)I!h=6 ! =6 M")IM"):g=~ J /:h=2>=M?.Mj': < Zn.C / E*:=k 0wM% !;=4C┆
0x26c00…26d00 (38, 0, 12) Sector 260dff00249241 ┆& $ A 1 TABLE OF CONTENTS 1 1 INTRODUCTION ................................ 4 2 STATEMENT OF COMPLIANCE ........┆
0x26d00…26e00 (38, 0, 13) Sector 260eff00249241 ┆& $ A............. 4 3 TRAINING .................................... 5 3.1 REQUIREMENTS ANALYSIS ................... 5 3.2 MANAGEMENT .............................. 5 3.3 COURSES ................................. 7 3.4 ┆
0x26e00…26f00 (38, 0, 14) Sector 260fff00249241 ┆& $ ACOURSE DEVELOPMENT ...................... 10 3.5 TRAINING METHOD ......................... 11 3.6 CONDUCT OF COURSES ...................... 14 4 SPARE PARTS ................................. 15 4.1 REQUIREMENTS ANALYSIS .....┆
0x26f00…27000 (38, 0, 15) Sector 2600ff00249241 ┆& $ A.............. 15 4.2 RSPL .................................... 15 4.3 PROVISIONING CONFERENCE ................. 16 4.4 SPARE PARTS DELIVERY .................... 16 4.5 INITIAL SPARE PARTS LIST ................ 18 4.6 P┆
0x27000…27100 (39, 0, 0) WangDocumentBody
[…0x1…]
0x27200…27300 (39, 0, 2) Sector 2703ff00249241 ┆' $ ADEPOT TEST EQUIPMENT .................... 24 7 SPECIAL TOOLS ............................... 25 8 DOCUMENTATION ............................... 26 8.1 GENERAL ................................. 26 8.2 OVERVIEW ................┆
0x27300…27400 (39, 0, 3) Sector 2704ff00249241 ┆' $ A................ 26 8.3 REQUIREMENTS ............................ 31 8.4 IMPLEMENTATION .......................... 34 8.5 DELIVERY ................................ 35 8.6 PERFORMANCE TEST ........................ 36 9 A┆
0x27400…27500 (39, 0, 4) Sector 2705ab00249241 ┆' + $ ACCEPTANCE TESTING .......................... 38 10 OPTIONS ..................................... 40 11 QUALITY AND SECURITY REQUIREMENTS ........... 41 S/W d at regular intervals according to negotiation between Christian Rovsing and ┆
0x27500…27600 (39, 0, 5) Sector 2706ff00249241 ┆' $ A 1 12 MAINTENANCE AND SUPPORT ..................... 44 12.1 REQUIREMENTS ANALYSIS ................... 44 12.2 MAINTENANCE PLAN ........................ 44 12.3 MAINTENA┆
0x27600…27700 (39, 0, 6) Sector 2707d500249241 ┆' U $ ANCE ACTIVITIES .................. 46 12.4 PREVENTATIVE MAINTENANCE ................ 46 12.5 TECHNICAL SUPPORT ....................... 48 13 RELIABILITY ................................. 49 8 38637 ' *J B ~ _┆
0x27700…27800 (39, 0, 7) Sector 2608ff00249241 ┆& $ A 1 1 INTRODUCTION Part III of the proposal for the MESSAGE ENTRY and DISTRIBUTION SYSTEM of the MOBILE WAR HEADQUARTERS (MWHQ-MEDS) for the Dutch Army is the Christian Rovsing A/┆
0x27800…27900 (39, 0, 8) WangDocumentBody
[…0x7…]
0x28000…28100 (40, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(40,0, 1), len=0xff, h3=41345741}, f00=»3457A «, f01=»Amendment to L.of.C 7497 «, f02=»pan «, f03=»FE «, f04=»IKKE SLET «, f05=18-03-83 10:14, f06=» «, f07=»48 «, f08=» 2844 «, f09=18-03-83 16:54, f10=» «, f11=»05 «, f12=» 150 «, f13=18-03-83 16:49, f14=13-04-83 12:53, f15=»0210A «, f16=» 1 «, f17=» 1 «, f18=»10 «, f19=» 84 «, f20=» 5094 «, f21=» «, f22=» «, f99=020000000010052710110380aa8a37040000000000000042031200df}
0x28100…28200 (40, 0, 1) WangDocumentBody
[…0x6…]
0x28800…28900 (40, 0, 8) Sector 00009900348941 ┆ 4 A 1 Sharing of Peripherals less than 10 milliseconds (T o ) We have then the worst case total delay time in case of no content┆
0x28900…28a00 (40, 0, 9) Sector 280aff00110041 ┆( A 1 4.1.5.2 Checkpoint Area in Active PU MMS and CPT share a data segment MMS-CPT-DS with the following layout: MAX-CIF-BUFS 4 ┆
0x28a00…28b00 (40, 0, 10) Sector 280bff00110041 ┆( A BUF-SIZE 512 bytes buffer 1 buffer 2 buffer 3 ┆
0x28b00…28c00 (40, 0, 11) Sector 280c8e00110041 ┆( A buffer 4 The buffer layout is defined in section 4.1.5.3. &C process. The non-arrival of a keep alive message is signalled to the SYS M&C process by the PU-HANDLER. 4.1┆
0x28c00…28d00 (40, 0, 12) Sector 280dff00110041 ┆( A 1 4.1.5.3 Checkpoint Area in Standby PU CPR and MMS share a data segment (MMS-CPR-DS) in the standby PU with the following layout: CIF-ARRAY BUF┆
0x28d00…28e00 (40, 0, 13) Sector 280eff00110041 ┆( AFER 1 BUF-SIZE = 512 bytes 2 MAX-CIF- RECORDS = 150 A single buffer has the following layout: 1 LENG┆
0x28e00…28f00 (40, 0, 14) Sector 280fc600110041 ┆( F ATH 512 bytes 2 CP-NO 1..150 corresponds to buffer no. 3 VERSION 256 - the time of day - the PU to which communication is d┆
0x28f00…29000 (40, 0, 15) Sector 2800ff00110041 ┆( A 1 4.1.5.4 System Parameters COPSY updates via TMP: - time of day (disk resident) - AT-RISK / NORMAL-MODE boolean. 4.1.6 Interfaces COPSY Use of Queue Request / Reply Dialogu┆
0x29000…29100 (41, 0, 0) Sector 2901ff00348941 ┆) 4 Ad the cost per channel can be significantly reduced as compared to the one-channel Line Terminator. However, the basic security characteristics of the filter with Multichannel Line Terminators will be adversely affected since unintended paths with┆
0x29100…29200 (41, 0, 1) Sector 2902ff00348941 ┆) 4 Ain the Line Terminator (e.g. caused by design error or hardware failure) may cause a security breach. A design which minimises this risk is likely to cost more on a per-channel basis than the single Channel Line Terminator. A particular case whe┆
0x29200…29300 (41, 0, 2) Sector 2903ff00348941 ┆) 4 Are sharing of hardware could be cost efficient is the case where a number of single channel and/or Multi channel filters is collocated. Here, the tape recorder and/or the Operator Terminal could be readily shared among the collocated filters. Th┆
0x29300…29400 (41, 0, 3) Sector 2904ca00348941 ┆) J 4 Ae only prerequisite for sharing these peripherals is a switch (e.g. mechanical or electro-optical) which provides a secure separation between the individual filters. See the figure overleaf. ransferred to the MPP. b) LT to MPP transfer time ┆
0x29400…29500 (41, 0, 4) Sector 2905ff00348941 ┆) 4 A 1 3.2 SECURITY The use of common tape recorder will require a secure switch in order to efficiently separate the individual filters. The use of a common terminal will also req┆
0x29500…29600 (41, 0, 5) Sector 2906ff00348941 ┆) 4 Auire a secure switch. In addition, the requirements to the security of the erasure of the storage areas of the terminal may be strengthened if the same terminal shall serve channels of different classification levels. 3.3 CONCLUSION The pr┆
0x29600…29700 (41, 0, 6) Sector 2907ff00348941 ┆) 4 Aimary objective for optional sharing of hardware is accommodated by the Multi Channel Security Filter. The particular case of several collocated filters can use common tape recorder and operator terminal if a simple (but secure!) switch is introduce┆
0x29700…29800 (41, 0, 7) Sector 28080c00348941 ┆( 4 Ad. eady to receive the message immediately o Internal parallel transfers are controlled by Direct Memory Access at a rate of 500 Kbytes per second, giving a total transfer time of 16 milliseconds (T tr) o MPP processing time is less than 30 ┆
0x29800…29900 (41, 0, 8) Sector 2909ff00348941 ┆) 4 Amilliseconds (T Pr ) o Validation time m GK is less than 240 milliseconds (T va ) (see previous subsection) o The other contributions totals to less than 10 milliseconds (T o ) We have then the worst case total delay time in case of no content┆
0x29900…29a00 (41, 0, 9) Sector 290aff00348941 ┆) 4 Aion: T tot = T o + 3 x T tr + T pr + T va = 10 + 3 x 16 + 30 + 240 = 328 milliseconds The worst case if a worst case contention occurs is the situation where the GK has just delivered a message of maximum size to the Line Terminator┆
0x29a00…29b00 (41, 0, 10) Sector 290bff00348941 ┆) 4 A (output) and another very short message follows immediately after on the same channel and in the same direction. The transmission out of the filter will in this case be delayed by approximately the time required for transmitting the previous messag┆
0x29b00…29c00 (41, 0, 11) Sector 290c2300348941 ┆) # 4 Ae, i.e. approx. 27 seconds. required in the common path, i.e. the Multi-Purpose Processor and the Gate Keeper for automatically validated messages. Here, the bottlenect will obviously be the Gate Keeper. The requirements for the processing of a ┆
0x29c00…29d00 (41, 0, 12) Sector 290dff00348941 ┆) 4 A 1 3 SHARING OF HARDWARE 3.1 ANALYSIS Target applications of the filter show generally several channels emerging from the same computer site. It is therefore obvious to see┆
0x29d00…29e00 (41, 0, 13) Sector 290eff00348941 ┆) 4 Ak for possibilities to reduce the overall cost by sharing hardware if possible. Regarding the Multi Channel Filter Configuration it is seen that it actually represents such a sharing of hardware. Additional channels require only additional Line Te┆
0x29e00…29f00 (41, 0, 14) Sector 290fff00348941 ┆) 4 Arminators and the validation Table firmware required for that particular channel. The other hardware modules i.e. the Multi Purpose Processor, the Gate Keppers, the Operator Terminal and the logging recorder are shared among the channels. A more┆
0x29f00…2a000 (41, 0, 15) Sector 2900ff00348941 ┆) 4 A efficient sharing of hardware is not achievable unless use of the same Line Terminator to serve several channels is considered. It is a rather straight forward task to design a Multi- channel Line Terminator (e.g. four channels in one module) an┆
0x2a000…2a100 (42, 0, 0) Sector 2a01ff00348941 ┆* 4 Arocessing time of less than 0.33 seconds. Hence, the throughput of the common path for automatically validated messages is more than 3 messages/ second. The worst case load from one channel is less than 2400 Band ┆
0x2a100…2a200 (42, 0, 1) Sector 2a02ff00348941 ┆* 4 A 8000 characters x 8 bit/character or one message each 27 seconds in each direction. This gives a capability of servicing up to 40 channels by one Gate Keeper. The throughput for the operator assisted validation will obviously be set b┆
0x2a200…2a300 (42, 0, 2) Sector 2a03ff00348941 ┆* 4 Ay the human validation process and is therefore determined by factors external to the filter. The conclusion is that the processing performance of the Multi Channel Security Filter is sufficiently high for handling several channels. 2.3.3 Delay┆
0x2a300…2a400 (42, 0, 3) Sector 2a04ff00348941 ┆* 4 A The total delay of a message caused by the Multi Channel Security Filter is composed of the following a) Time elapsed from reception of the last character of a message to the message can be transferred to the MPP. b) LT to MPP transfer time ┆
0x2a400…2a500 (42, 0, 4) Sector 2a05ff00348941 ┆* 4 A c) MPP preprocessing time d) MPP to GK transfer time e) GK processing time f) Time elapsed from completion of the validation to start of transfer g) GK to LT transfer time h) Time elapsed from the message has been transferred to the LT un┆
0x2a500…2a600 (42, 0, 5) Sector 2a063300348941 ┆* 3 4 Atil the first character appears on the line s number is stored into the register in the Bus Supervisor of the GK which by a simple hardware circuit controls as well the request for output line number as the validation table to be used. o The set ┆
0x2a600…2a700 (42, 0, 6) Sector 2a07ff00348941 ┆* 4 A 1 The following estimates and assumptions are made o The message is a worst case message o The MPP is ready to receive the message immediately o The Line Terminator (output┆
0x2a700…2a800 (42, 0, 7) Sector 2908ff00348941 ┆) 4 A) is ready to receive the message immediately o Internal parallel transfers are controlled by Direct Memory Access at a rate of 500 Kbytes per second, giving a total transfer time of 16 milliseconds (T tr) o MPP processing time is less than 30 ┆
0x2a800…2a900 (42, 0, 8) Sector 2a09f300348941 ┆* s 4 As. Messages are physically separated in separate memory areas. o Buffer areas used for storage of messages are erased before the next message arrives. o Buffer areas are fixed i.e. no software controlled dynamic memory allocation. bsequently b┆
0x2a900…2aa00 (42, 0, 9) Sector 2a0aff00348941 ┆* 4 A 1 2.3.1.3 Cross-talk The risk of transfer of information to other channels in parallel with the intended by failure caused by e.g. electromagnetic coupling or galvanic leakage is ┆
0x2aa00…2ab00 (42, 0, 10) Sector 2a0bff00348941 ┆* 4 Aminimised by o Physical separation and shielding of Line Terminators o Galvanic isolation between the Line Terminators by opto-isolators. See the separate section on electronic switches. 2.3.2 Throughput The throughput at the filter is dete┆
0x2ab00…2ac00 (42, 0, 11) Sector 2a0cff00348941 ┆* 4 Armined by the processing time required in the common path, i.e. the Multi-Purpose Processor and the Gate Keeper for automatically validated messages. Here, the bottlenect will obviously be the Gate Keeper. The requirements for the processing of a ┆
0x2ac00…2ad00 (42, 0, 12) Sector 2a0dff00348941 ┆* 4 A"worst case message" is given by the following: A "Worst case message" is here defined as a message with the following characteristics a) Message size is 8000 characters b) The mean field size is 10 characters c) The message is divided into 20┆
0x2ad00…2ae00 (42, 0, 13) Sector 2a0eff00348941 ┆* 4 A0 sets of 4 fields each d) All fields shall be validated either against discrate tabular values or the format shall be checked The following estimates have been made: 1 Check s┆
0x2ae00…2af00 (42, 0, 14) Sector 2a0ffb00348941 ┆* { 4 Ayntax: 40 instructions/set Check against tabular values or check field formats: 50 instructions/field This gives the following number of instructions for the validation of each message: 40 x 200 + 50 x 800 = 48.000 instructions/msg. ntro┆
0x2af00…2b000 (42, 0, 15) Sector 2a00ff00348941 ┆* 4 A 1 Assuming an instruction time of 5 micro-seconds (mean), the worst case message is processed in 240 milliseconds. Adding the transfer time and processing time in the MPP gives a p┆
0x2b000…2b100 (43, 0, 0) Sector 2b01ff00348941 ┆+ 4 A Termnination Module responds with module address and device status on the Output Bus. The two Gate Keepers are serviced alternately. 2.3 PERFORMANCE 2.3.1 Security The Multichannel Configuration introduces in principle a number of risks i┆
0x2b100…2b200 (43, 0, 1) Sector 2b02ff00348941 ┆+ 4 An addition to those of the single channel filter as described in section 2.1.3.1. These risks are listed in the following subsections together with the precautions made. 2.3.1.1 Illegal Source/Validation table/sink relationship This is the ri┆
0x2b200…2b300 (43, 0, 2) Sector 2b039300348941 ┆+ 4 Ask of performing the Validation with a table, specified for another channel or the risk of transferring the message to a wrong output line. us register is readable. The serial interface to the terminal is unidirectional. Simple handshaking is provi┆
0x2b300…2b400 (43, 0, 3) Sector 2b04ff00348941 ┆+ 4 A 1 The mechanisms which shall assure the correct relation- ship are the following: o The set up of the path from the Line Terminator to the Multi Purpose Processor is controlled an┆
0x2b400…2b500 (43, 0, 4) Sector 2b05ff00348941 ┆+ 4 Ad monitored using feedback by a simple hardware circuit in the Input Control to assure a secure knowledge of the source. o The Line Terminator (input) writes the input line number in the header of the message Block. o The Gate Keeper reads the h┆
0x2b500…2b600 (43, 0, 5) Sector 2b06ff00348941 ┆+ 4 Aeader for determining the channel number. This number is stored into the register in the Bus Supervisor of the GK which by a simple hardware circuit controls as well the request for output line number as the validation table to be used. o The set ┆
0x2b600…2b700 (43, 0, 6) Sector 2b07ff00348941 ┆+ 4 Aup of the path from the Gate Keeper to the Line Terminator (output) is controlled and monitored using feedback by a simple hardware circuit in the Output Control to assure a secure routing. o The Line Terminator (output) checks the input line numb┆
0x2b700…2b800 (43, 0, 7) Sector 2a08ff00348941 ┆* 4 Aer of the header for correct relationship with the output line number. 2.3.1.2 Residue The risk of by failure to have information from one message adhered to another is minimised by the following precautions: o Multiplexing is on message basi┆
0x2b800…2b900 (43, 0, 8) Sector 2b09ff00348941 ┆+ 4 A with the expected. The transfer is initiated if they compare, otherwise, this error situation will be indicated in the status word on the Input Bus, the Buffer Ready will be overridden by the Input Control and the channel select will subsequently b┆
0x2b900…2ba00 (43, 0, 9) Sector 2b0aff00348941 ┆+ 4 Ae removed. If there is no full buffer in this module, the counter is incremented and the next module is interrogated. 2.2.5.4 Output Control The Output Control logic performs the set-up and supervision of the message transfer from the Gate Ke┆
0x2ba00…2bb00 (43, 0, 10) Sector 2b0bff00348941 ┆+ 4 Aeper to the Line Termination module. The destination address for the validated message is supplied by the Bus Supervisor module of the Gate Keeper. This address is decoded to one out of m separate lines which are connected to the Channel select ┆
0x2bb00…2bc00 (43, 0, 11) Sector 2b0c4100348941 ┆+ A 4 Alines of each Input Interface of the Termination module. Bus interface o Serial interface to tape recorder o Control inputs o Dual Buffer memory o Monitoring and control The incoming message is stored in one of the two buffers and will rema┆
0x2bc00…2bd00 (43, 0, 12) Sector 2b0dff00348941 ┆+ 4 A 1 The Input Enable is activated when the Output Address Ready line indicates Valid address. This causes that the selected module to output its module address together with device sta┆
0x2bd00…2be00 (43, 0, 13) Sector 2b0eff00348941 ┆+ 4 Atus. This address is compared with the address from the Gate Keeper, and the status is checked. Destination Module Ready is signalled to the Output Interface of the Gate Keeper if the addresses compare and if there is a free buffer and the data tran┆
0x2be00…2bf00 (43, 0, 14) Sector 2b0fff00348941 ┆+ 4 Asfer can commence. Service is offered to the other Gate Keeper if both buffers of the Line Termination module are full. The Bus Supervisor takes down the Output Address Ready when the last byte has been transferred. This causes the Output Contro┆
0x2bf00…2c000 (43, 0, 15) Sector 2b00ff00348941 ┆+ 4 Al to deactivate Destination Module Ready, which in turn causes deactivation of the Buffer Ready line by the Output Interface of the Gate Keeper. This change is sensed by the Line Termination module and interpreted as an End of Transfer. The Output┆
0x2c000…2c100 (44, 0, 0) Sector 2c01ff00348941 ┆, 4 Ator points which may be required. Output lines are the Alert Line which activates the audible alarm and the (optional) Warning Line which could activate a light indicator. 2.2.5.2.3.7 Terminal Interface Ter Terminal Interface is a small dedic┆
0x2c100…2c200 (44, 0, 1) Sector 2c02ff00348941 ┆, 4 Aated microprocessing system. The main elements are o Common bus interface o Serial interface to the terminal o Buffer Memory o General control and monitoring The incoming message is stored in the buffer and remains there until a command is gi┆
0x2c200…2c300 (44, 0, 2) Sector 2c03ff00348941 ┆, 4 Aven, either causing erasure or output to the terminal prior to erasure. The interface to the common bus is designed such that only the status register is readable. The serial interface to the terminal is unidirectional. Simple handshaking is provi┆
0x2c300…2c400 (44, 0, 3) Sector 2c04ff00348941 ┆, 4 Aded such that transmission will take place only when the terminal is ready. 2.2.5.2.4 Summary of characteristics General o Performs message preparation o Interfaces to the terminal, logging recorder and provides for control and monitoring in┆
0x2c400…2c500 (44, 0, 4) Sector 2c059700348941 ┆, 4 Aput/output Parallel interface o Standardized parallel input and output o Byte-serial DMA transfer with handshake o Destructive readout Input Interface The Input Interface performs all the functions required for the transfer of data from ┆
0x2c500…2c600 (44, 0, 5) Sector 2c06ff00348941 ┆, 4 A 1 Serial interface o Mag Tape and Terminal interface is RS232 serial interface Monitor and Control o Separate digital lines are provided for optional monitor and control point┆
0x2c600…2c700 (44, 0, 6) Sector 2c07ff00348941 ┆, 4 As 2.2.5.3 Input Control The Input Control is a small, dedicated controller which performs set-up and supervision of the data transfer between the Line Termination modules and the Multi Purpose Processor. A single of the Channel Select Lines a┆
0x2c700…2c800 (44, 0, 7) Sector 2b08ff00348941 ┆+ 4 Are activated at a time. The selected Line Termination module will respond with an active level on the Buffer Ready Line if a full buffer is available simultaneously the module will output the Module Address on the Input Bus. This address is composed┆
0x2c800…2c900 (44, 0, 8) Sector 2c094f00348941 ┆, O 4 Ahe Buffer Memory which is outside the area used for the Message Block. normal frequency of rejected messages. The frequency is currently updated by an algorithm, implemented in software and a separate output line is activated when the frequency ┆
0x2c900…2ca00 (44, 0, 9) Sector 2c0aff00348941 ┆, 4 A 1 2.2.5.2.3.3 Buffer Memory The Buffer Memory is organized into one memory bank corresponding to one buffer and an area which can be accessed by the microprocessor for both read and┆
0x2ca00…2cb00 (44, 0, 10) Sector 2c0bff00348941 ┆, 4 A write. 2.2.5.2.3.4 Program Memory The program memory is a non-volatile Read-only memory the contents of which can not be changed without using external programming equipment. 2.2.5.2.3.5 Mag Tape Interface (MTI) The MTI is a small dedicat┆
0x2cb00…2cc00 (44, 0, 11) Sector 2c0cff00348941 ┆, 4 Aed microprocessing system. The main elements are o Common Bus interface o Serial interface to tape recorder o Control inputs o Dual Buffer memory o Monitoring and control The incoming message is stored in one of the two buffers and will rema┆
0x2cc00…2cd00 (44, 0, 12) Sector 2c0dff00348941 ┆, 4 Ain there until a command is given, either causing erasure or logging onto tape prior to erasure. The interface to the Common Bus is designed such that the only readable memory is a status register. The serial interface to the tape recorder carri┆
0x2cd00…2ce00 (44, 0, 13) Sector 2c0eff00348941 ┆, 4 Aes as well control as data. The interface is hardware in such a way that reading the recorder is not possible. The control inputs are connected to the Gate Keeper. The Gate Keeper will issue a signal indicating either accept or reject of each mess┆
0x2ce00…2cf00 (44, 0, 14) Sector 2c0f6c00348941 ┆, l 4 Aage. This causes either erasure of the corresponding buffer or logging onto tape prior to erasure. upon completion of the Message prepraration depends upon the result. a) A message which has been destinated for automatic validation is transfer┆
0x2cf00…2d000 (44, 0, 15) Sector 2c00ff00348941 ┆, 4 A 1 2.2.5.2.3.6 Monitor and Control I/O This interface provides a number of separate digital input and output lines. Input lines comprise on-line/ off-line switch and additional moni┆
0x2d000…2d100 (45, 0, 0) Sector 2d01ff00348941 ┆- 4 Amessage which has been destinated for operator assisted validation is transferred to the Operator Terminal from the copy at the Message Block stored in the Terminal Interface and the buffer area is erased. The copy in the Buffer Memory is erased, bu┆
0x2d100…2d200 (45, 0, 1) Sector 2d02ff00348941 ┆- 4 At the copy in the Mag Tape Interface is retained for possible logging. c) A message which has been rejected is logged onto the Tape recorder. The copies, the Buffer Memory and the Terminal Interface are erased. 2.2.5.2.2.7 Logging All rejecte┆
0x2d200…2d300 (45, 0, 2) Sector 2d036900348941 ┆- i 4 Ad messages are logged on tape recorder together with the approximate time and date of occurrence. n for operator assisted validation f) Data output and erasure g) Logging h) Loop test 2.2.5.2.2.1 Data Input The Message Block is transferred ┆
0x2d300…2d400 (45, 0, 3) Sector 2d04ff00348941 ┆- 4 A 1 2.2.5.2.2.8 Loop Test The test program can be activated in off-line state with the line outputs connected externally to the line inputs. The program performs the test by transmitt┆
0x2d400…2d500 (45, 0, 4) Sector 2d05ff00348941 ┆- 4 Aing a set of preprogrammed messages (some legal, some illegal) around the loop and verify the result. 2.2.5.2.3 Design Details 2.2.5.2.3.1 Input Interface The Input Interface performs all the functions required for the transfer of data from ┆
0x2d500…2d600 (45, 0, 5) Sector 2d06ff00348941 ┆- 4 Athe Output Interface of the Line Terminator to the MPP. The interface comprises the necessary address counter and memory write control circuit. The Buffer Memory and the compartmentalised memories of the Mag Tape Interface and the Terminal Inter┆
0x2d600…2d700 (45, 0, 6) Sector 2d07ff00348941 ┆- 4 Aface are addressed simultaneously. 2.2.5.2.3.2 Microprocessor The microprocessor performs the overall control and monitoring functions of the MPP. In addition, the following functions are performed o Type identification o Calculation of the ┆
0x2d700…2d800 (45, 0, 7) Sector 2c08ff00348941 ┆, 4 Afrequency of ellegal messages o Identification of the fields which shall be subject to validation by the operator o Data output set-up o Loop test generation The memory write function is restricted, both by hardware and firmware to an area of t┆
0x2d800…2d900 (45, 0, 8) Sector 2d09ff00348941 ┆- 4 Anitoring The alert function activates an audible alarm in case of an abnormal frequency of rejected messages. The frequency is currently updated by an algorithm, implemented in software and a separate output line is activated when the frequency ┆
0x2d900…2da00 (45, 0, 9) Sector 2d0aff00348941 ┆- 4 Aexceeds a pre-specified limit. The alert function may also be triggered by signals on the Monitor Lines, indicating e.g. physical access (green door) while on-line or data integrity error under CRC check. The warning function activates a visible┆
0x2da00…2db00 (45, 0, 10) Sector 2d0bff00348941 ┆- 4 A indicator upon detection of conditions which are neither normal nor critical e.g. off-line condition. 2.2.5.2.2.4 Preparation for automatic validation TBS Finally a command is given to the Terminal Interface, specifying that the messag┆
0x2db00…2dc00 (45, 0, 11) Sector 2d0c2600348941 ┆- & 4 Ae in question shall be erased. 2.2.5.1.3.6 Opto Isolator The Opto Isolator provides the required isolation between data on the Output Bus and the Line Terminators which are not selected for the current transfer┆
0x2dc00…2dd00 (45, 0, 12) Sector 2d0dff00348941 ┆- 4 A 1 2.2.5.2.2.5 Preparation for operator assisted validation The preparation involves identification of the field or fields which requires validation by the operator. The fields are┆
0x2dd00…2de00 (45, 0, 13) Sector 2d0eff00348941 ┆- 4 A described by a table (with one or more elements) of pointers to each field. This table is written to the Terminal Interface and finally a command is given to the Interface, specifying that the message in question shall be subject to operator assi┆
0x2de00…2df00 (45, 0, 14) Sector 2d0fff00348941 ┆- 4 Asted validation. 2.2.5.2.2.6 Data Output and erasure The operation performed on the Message Block upon completion of the Message prepraration depends upon the result. a) A message which has been destinated for automatic validation is transfer┆
0x2df00…2e000 (45, 0, 15) Sector 2d00ff00348941 ┆- 4 Ared to the Gate Keeper. The entire Message Block is transferred from the Buffer Memory and the buffer area is erased. The copy in the Mag Tape Interface is retained for possible logging and the copy in the Terminal Interface has been erased. b) A ┆
0x2e000…2e100 (46, 0, 0) Sector 2e01ff00348941 ┆. 4 Aon includes a check of the status byte of the received message and identification of the type of message for the purpose of selecting between automatic and operator assisted validation. In the latter case, the fields which require validation by the ┆
0x2e100…2e200 (46, 0, 1) Sector 2e02ff00348941 ┆. 4 Aoperator are identified and the message is transmitted to the Operator Terminal. The loop test program also resides in this module. 2.2.5.2.2 Functional Specification The functions are divided into the following groups a) Data input b) Typ┆
0x2e200…2e300 (46, 0, 2) Sector 2e03ff00348941 ┆. 4 Ae identification c) Control and monitoring d) Preparation for automatic validation e) Preparation for operator assisted validation f) Data output and erasure g) Logging h) Loop test 2.2.5.2.2.1 Data Input The Message Block is transferred ┆
0x2e300…2e400 (46, 0, 3) Sector 2e04ff00348941 ┆. 4 Afrom the Line Termination module to the Buffer Memory of the MPP under control of the Input Interface. Simultaneously, the Message Block is stored in the memory of both the Mog Tape Interface and the Terminal Interface. The transfer employs the fo┆
0x2e400…2e500 (46, 0, 4) Sector 2e05ff00348941 ┆. 4 Allowing issues o Data, eight input lines o Buffer Ready, input o Data Strobe, output The transfer starts upon an active level on the Buffer Ready line, indicating that the first-byte of a message is available on the input. The subsequent-bytes┆
0x2e500…2e600 (46, 0, 5) Sector 2e067500348941 ┆. u 4 A are recalled by pulling the Data Strobe. The transfer is terminated when the Buffer Ready line goes passive. of bytes (the block length) in the received Message Block is written to the Output Interface when the Message Block has been completed. T┆
0x2e600…2e700 (46, 0, 6) Sector 2e07ff00348941 ┆. 4 A 1 2.2.5.2.2.2 Type Identification The Microprocessor reads the header information in order to check the status and to determine the message type. The status must be nominal and th┆
0x2e700…2e800 (46, 0, 7) Sector 2d08ff00348941 ┆- 4 Ae message type must be known, otherwise the message is rejected and logged. The type identification may give the result that the message shall be subject to either automatic validation or operator assisted validation. 2.2.5.2.2.3 Control and Mo┆
0x2e800…2e900 (46, 0, 8) Sector 2e09ff00348941 ┆. 4 Atransfer at data from the Buffer Memory to the Multi Purpose Processor (input) or from the Gate Keeper to the Buffer Memory (output). The interface comprises the necessary address counter, byte counter and memory read/write control circuit to retr┆
0x2e900…2ea00 (46, 0, 9) Sector 2e0aff00348941 ┆. 4 Aieve or store data from/to the Buffer Memory. As a specific security provision, the memory read function (input) includes erasure of the memory contents, i.e. writing a fixed bit pattern into all memory locations of the used buffer. Similarly, the┆
0x2ea00…2eb00 (46, 0, 10) Sector 2e0ba500348941 ┆. % 4 A memory write function (output) is preceeded by an erasure of the buffer area as soon as the previous message has been transmitted and acknowledged properly. dy signal changes to the passive state when the last byte of the Message Block has been ma┆
0x2eb00…2ec00 (46, 0, 11) Sector 2e0cff00348941 ┆. 4 A 1 2.2.5.1.3.6 Opto Isolator The Opto Isolator provides the required isolation between data on the Output Bus and the Line Terminators which are not selected for the current transfer┆
0x2ec00…2ed00 (46, 0, 12) Sector 2e0dff00348941 ┆. 4 A. 2.2.5.1.4 Summary of characteristics General o Message size: max. 8000 bytes o Throughput rate: equal to serial input rate o Storage capacity: Two Message Blocks of maximum 8 Kbytes each o Cyclic Redundancy gen┆
0x2ed00…2ee00 (46, 0, 13) Sector 2e0eff00348941 ┆. 4 Aeration and verification for data integrity check Serial Input o Communication protocol: CCITT rec. X.25 o Electrical Interface: MIL-STD-188C o Data rate: nominal 2400 Band, extendable to 9.600 Band Input and Output Interface o S┆
0x2ee00…2ef00 (46, 0, 14) Sector 2e0fbe00348941 ┆. > 4 Atandardized Message Block format o Byte-serial DMA transfer with handshake o Destruction readout o Optical isolation of output interface 2.2.5.2 Multi Purpose Processor (MPP) pulsed. The Channel Select is set to a passive state when the l┆
0x2ef00…2f000 (46, 0, 15) Sector 2e00ff00348941 ┆. 4 A 1 2.2.5.2.1 General The MPP performs the preparation of the message for validation, the logging onto a recorder in case of rejection and implements the alert function. The preparati┆
0x2f000…2f100 (47, 0, 0) Sector 2f01ff00348941 ┆/ 4 Aquired o Adaptation between the electrical levels on the line and the internal logic levels o Waveshaping and filtering as required The interface is in accordance with MIL-STD-188C in order to facilitate COMSEC certification on compromising em┆
0x2f100…2f200 (47, 0, 1) Sector 2f02ff00348941 ┆/ 4 Aanuation. 2.2.5.1.3.2 Serial Interface Controller The Serial Interface Controller performs all the basic transport functions on bit and byte level in the support of a full duplex X.25 channel. This covers for the input o Bit synchronisation┆
0x2f200…2f300 (47, 0, 2) Sector 2f03b300348941 ┆/ 3 4 A o format synchronisation o Integrity check (FCS) o Serial to parallel conversion and for the output o Parallel to serial conversion o Formatting o FCS generation fies the link access procedure for data interchange across the link between ┆
0x2f300…2f400 (47, 0, 3) Sector 2f04ff00348941 ┆/ 4 A 1 2.2.5.1.3.3 Microprocessor The miniprocessor performs the higher level functions of the level 1 and all level 2 functions, supported by the serial interface controller. In additio┆
0x2f400…2f500 (47, 0, 4) Sector 2f05ff00348941 ┆/ 4 An the following functions are performed o Message Block generation o Message Block verification o Set up of parallel input and output The microprocessor has on-chip program storage and scratch pad memory. It is, both by hardware and software, ┆
0x2f500…2f600 (47, 0, 5) Sector 2f06ff00348941 ┆/ 4 Arestricted to a write-only function on the Buffer Memory (input) or a Read-only function (output). The number of bytes (the block length) in the received Message Block is written to the Output Interface when the Message Block has been completed. T┆
0x2f600…2f700 (47, 0, 6) Sector 2f07ff00348941 ┆/ 4 Ahe number of bytes in the Message Block to be transmitted is read from the Input Interface and compared to the corresponding number in the header. 2.2.5.1.3.4 Buffer Memory The Buffer Memory is physically organized in two distinct memory banks,┆
0x2f700…2f800 (47, 0, 7) Sector 2e08ff00348941 ┆. 4 A each corresponding to two message buffers. The input buffers hold data received from the line. The output buffers hold data while being transmitted. 2.2.5.1.3.5 Input and Output Interface The Interface performs all control functions for the ┆
0x2f800…2f900 (47, 0, 8) Sector 2f09ff00348941 ┆/ 4 Aine Terminator. The transfer employs the following lines: o Channel Select, input o Data, eight three-state output lines o Buffer Ready, output o Data Strobe, input The transfer is initiated by an active level on the Channel Select Line, in┆
0x2f900…2fa00 (47, 0, 9) Sector 2f0aff00348941 ┆/ 4 Adicating that the Multi Purpose Processor is ready for a new message. The module indicates the availability of a new Message Block by activating the Buffer Ready line. The transfer can start upon an active Buffer Ready and the first byte of the ┆
0x2fa00…2fb00 (47, 0, 10) Sector 2f0bff00348941 ┆/ 4 AMessage Block will be available on the eight data lines. Subsequent bytes are made available each time a pulse is received on the Data Strobe. The Buffer Ready signal changes to the passive state when the last byte of the Message Block has been ma┆
0x2fb00…2fc00 (47, 0, 11) Sector 2f0cff00348941 ┆/ 4 Ade available. The Multipurpose Processor responds by changing the Channel Select to a passive state. 2.2.5.1.2.6 Parallel Input The Line Terminator receives the Message Block in a byte-serial input sequence and stores the data in the Buffer Mem┆
0x2fc00…2fd00 (47, 0, 12) Sector 2f0d9a00348941 ┆/ 4 Aory. The transfer employs the following lines: o Channel Select, input o Data, eight input lines o Buffer Ready, output o Data Strobe, input indicate the presence of the first byte of data on the Data lines. 2.2.5 Module Specification T┆
0x2fd00…2fe00 (47, 0, 13) Sector 2f0eff00348941 ┆/ 4 A 1 The transfer is initiated by an active level on the Channel Select line, indicating that the Multi Purpose Processor wants to transfer a message. The module indicates the availab┆
0x2fe00…2ff00 (47, 0, 14) Sector 2f0fff00348941 ┆/ 4 Aility of a free buffer by activating the Buffer Ready line. The transfer can start upon an active Buffer Ready, and the message is received byte by byte each time the Data Strobe is pulsed. The Channel Select is set to a passive state when the l┆
0x2ff00…30000 (47, 0, 15) Sector 2f00ff00348941 ┆/ 4 Aast byte has been transferred. 2.2.5.1.3 Design Details 2.2.5.1.3.1 Electrical Protection The electrical protection circuit provides for the following: o Protection against permanent damage from transients on the communication line as re┆
0x30000…30100 (48, 0, 0) Sector 3001d200348941 ┆0 R 4 Avided into the following groups a) Serial Interface b) Message Block generation (ILT) c) Message Block verification (OLT) d) Buffer handling e) Parallel Output (ILT) f) Parallel Input (OLT) the Filter. ls are multiplexed by offerin┆
0x30100…30200 (48, 0, 1) Sector 3002ff00348941 ┆0 4 A 1 2.2.5.1.2.1 Serial Interface The Serial Interface is specified by the CCITT recommendation X.25 levels 1 and 2, except for the electrical characteristics. Level 1 specifies the ┆
0x30200…30300 (48, 0, 2) Sector 3003ff00348941 ┆0 4 Aphysical, electrical, functionel and procedural characteristics to establish, maintain and disconnect the physical link between the communi- cating devices. Level 2 specifies the link access procedure for data interchange across the link between ┆
0x30300…30400 (48, 0, 3) Sector 3004ff00348941 ┆0 4 Athe communicating devices. 2.2.5.1.2.2 Message Block Generation The Message Block is generated from the received information as specified in section 2.2.3, Message Block Specification. The message is stored byte-wise in the Buffer Memory in t┆
0x30400…30500 (48, 0, 4) Sector 3005ff00348941 ┆0 4 Ahe order it is received, and the header is supplied in front of the message as specified. 2.2.5.1.2.3 Message Block Verification The Message Block Verification is made prior to the serial transmission of a validated message. The following ver┆
0x30500…30600 (48, 0, 5) Sector 3006ff00348941 ┆0 4 Aifications shall be successfully completed before the transmission can take place. o Check that Output device number is correct o Perform Cyclic Redundancy Check 2.2.5.1.2.4 Buffer handling Two pairs of buffers are available for storage of┆
0x30600…30700 (48, 0, 6) Sector 30077000348941 ┆0 p 4 A messages, one pair for input and one pair for output. The two buffers of a pair are used alternately. ion As described in section .2.2 with the remark that the Channel Select line is permanently connected to an active level. 2.2.4.3.3 Elect┆
0x30700…30800 (48, 0, 7) Sector 2f08ff00348941 ┆/ 4 A 1 2.2.5.1.2.5 Parallel Output The Line Terminator implements a byte-serial output sequence of the full message block, i.e. all retrieval from the buffer memory is performed by the L┆
0x30800…30900 (48, 0, 8) Sector 3009ff00348941 ┆0 4 Ases the Channel Request input from the two Gate Keepers in idle periods. When one of the Gate Keepers are requesting service, the corresponding Channel Number lines are to select the proper Line Terminator by an active level on the corresponding Cha┆
0x30900…30a00 (48, 0, 9) Sector 300aff00348941 ┆0 4 Annel Select Line and an active level is issued on the corresponding Bus Grant Line. The communication path has now been set up. 2.2.4.4.1.2 Initiation The selected Line Terminator issues an active level on the Buffer Ready line when selected wh┆
0x30a00…30b00 (48, 0, 10) Sector 300bff00348941 ┆0 4 Aile one of the two buffers are free. Otherwise, the active level is delayed until one of the buffers has been released. The Line Terminator will present the Channel address and the Channel Status on the data lines while selected and until an ac┆
0x30b00…30c00 (48, 0, 11) Sector 300c3200348941 ┆0 2 4 Ative level appears on the Data Strobe line. 2.2.4.2.1 Protocol 2.2.4.2.1.1 Interrogation The Input Control issues an active level on one of the Channel Select lines. This signal causes the selected Line Terminator to pre┆
0x30c00…30d00 (48, 0, 12) Sector 300dff00348941 ┆0 4 A 1 2.2.4.4.1.3 Transfer The Gate Keeper issues a pulse on the Data Strobe line to indicate the presence of the first byte of data on the Data lines. 2.2.5 Module Specification T┆
0x30d00…30e00 (48, 0, 13) Sector 300eff00348941 ┆0 4 Ahe specifications given in this subsection comprise the Line Terminator, the Multi Purpose Processor, the Input Control and the Output Control. The specifications given could be considered as draft versions of part of the final specifications whic┆
0x30e00…30f00 (48, 0, 14) Sector 300fff00348941 ┆0 4 Ah is to be provided later on. It has been found necessary to work out the following specifications in order to demonstrate the feasibility of and analyse the security aspects of a Multi Channel Security Filter. 2.2.5.1 Line Terminator (LT) 2┆
0x30f00…31000 (48, 0, 15) Sector 3000ff00348941 ┆0 4 A.2.5.1.1 General The LT implements the interface between the X.25 protocol of the serial communication channel and the internal byte parallel Message Block format of the Security Filter. 2.2.5.1.2 Functional Specification The functions are di┆
0x31000…31100 (49, 0, 0) Sector 31017c00348941 ┆1 | 4 Aremains active. An active-to-inactive transition indicates that the present byte is the last in the current block. he contents of the message. The Message Block is transferred as an entity throughout the Filter. ls are multiplexed by offerin┆
0x31100…31200 (49, 0, 1) Sector 3102ff00348941 ┆1 4 A 1 2.2.4.2.1.4 Termination The transfer is terminated by issuing a pulse while the Buffer Ready line is inactive. This situation is sensed by the Input Control which responds by de-a┆
0x31200…31300 (49, 0, 2) Sector 3103ff00348941 ┆1 4 Activating the current Channel Select line and interrogate the next channel. 2.2.4.2.1.5 Premature Termination The MPP may enforce a termination (abnormal condition) by forcing a low on the Buffer Ready line and subsequently issue a phase on the┆
0x31300…31400 (49, 0, 3) Sector 3104ff00348941 ┆1 4 A Data Strobe line. 2.2.4.2.2 Logical interface specification The transfer employs the following lines: o Data, eight three-state lines, source is selected ILT o Channel Select, source is Input Control o Buffer Ready, Open Collector line, ┆
0x31400…31500 (49, 0, 4) Sector 3105ff00348941 ┆1 4 Asource is normally selected ILT, source is MPP in case of premature termination 2.2.4.2.3 Electrical interface specification TBS 2.2.4.3 Internal Interface Specification The Internal Interface Specification is applicable to the interfaces ┆
0x31500…31600 (49, 0, 5) Sector 3106cc00348941 ┆1 L 4 Abetween the MPP and the Gate Keeper. 2.2.4.3.1 Protocol The protocol is as described in section .2.1 with the remark that the Channel Select input is permanently connected to an active level. n, the message is transferred to the butler memory ┆
0x31600…31700 (49, 0, 6) Sector 3107ff00348941 ┆1 4 A 1 2.2.4.3.2 Logical Interface Specification As described in section .2.2 with the remark that the Channel Select line is permanently connected to an active level. 2.2.4.3.3 Elect┆
0x31700…31800 (49, 0, 7) Sector 3008ff00348941 ┆0 4 Arical Interface Specification TBS 2.2.4.4 Output Bus The Output Bus provides the common data path from the Gater Keeper(s) to the Line Terminators. 2.2.4.4.1 Protocol 2.2.4.4.1.1 Interrogation The output control logic alternately sen┆
0x31800…31900 (49, 0, 8) Sector 3109ff00348941 ┆1 4 Aannel number, inserted by the Input Control Circuit. 2.2.4 Interface Specification The following interface specifications describe the internal as well as the external electrical interfaces of the Multi Channel Security Filter. 2.2.4.1 Line ┆
0x31900…31a00 (49, 0, 9) Sector 310aff00348941 ┆1 4 AInterface The procedural and logical requirements are as specified in the CCITT rec. X25. 2.2.4.1.1 Electrical interface: MIL-STD-188C 2.2.4.1.2 Electrical protection: TBS 2.2.4.2 Input Bus The Input Bus provides the common data para ┆
0x31a00…31b00 (49, 0, 10) Sector 310b4a00348941 ┆1 J 4 Afrom the line Terminator (input) to the Multi Purpose Processor. 2.2.2 Data flow Messages from all input lines are received and stored independently in the Line Terminators. The Input Control interrogates the modules cyclically. The interroga┆
0x31b00…31c00 (49, 0, 11) Sector 310cff00348941 ┆1 4 A 1 2.2.4.2.1 Protocol 2.2.4.2.1.1 Interrogation The Input Control issues an active level on one of the Channel Select lines. This signal causes the selected Line Terminator to pre┆
0x31c00…31d00 (49, 0, 12) Sector 310dff00348941 ┆1 4 Asent at the data output the channel number (bus bit) and the status. The status indicates whether a buffer is ready for transfer. If a buffer is ready, the transfer is initiated, otherwise the corresponding select line is set to inactive and the┆
0x31d00…31e00 (49, 0, 13) Sector 310eff00348941 ┆1 4 A next higher channel number (module the present number of channels) is interrogated. 2.2.4.2.1.2 Initiation The selected Line Terminator which has a buffer ready for transfer will provide an active level on the Buffer Ready Line. This line is┆
0x31e00…31f00 (49, 0, 14) Sector 310fff00348941 ┆1 4 A monitored by the Multi Purpose Processor MPP which responds with a pulse on the Data Strobe line when it is ready for input which will cause the first byte of the Message Block to appear on the Input Bus data lines. 2.2.4.2.1.3 Transfer The tr┆
0x31f00…32000 (49, 0, 15) Sector 3100ff00348941 ┆1 4 Aansfer is byte sequential. The MPP requests the next byte of the Message Block to be presented on the Input Bus data lines by issuing a pulse on the Data Strobe line. The MPP continues to request the next byte for as long as the Buffer Ready line ┆
0x32000…32100 (50, 0, 0) Sector 3201e200348941 ┆2 b 4 Aed block is called the Message Block. See the figure overleaf. The header is generated in the Line Terminator from the contents of the message. The Message Block is transferred as an entity throughout the Filter. ls are multiplexed by offerin┆
0x32100…32200 (50, 0, 1) Sector 3202ff00348941 ┆2 4 A 1 2.2.3.1 The Header The Header is composed of the following elements o Channel number The channel number is provided by the Input Control Circuit. o Reception and channel s┆
0x32200…32300 (50, 0, 2) Sector 3203ff00348941 ┆2 4 Atatus The status comprises the status provided by the receiver circuit i.e. synchronisation status and FCS check result. The channel status comprises e.g. number of retransmissions before correct reception. o Block Size The number of bytes┆
0x32300…32400 (50, 0, 3) Sector 32045500348941 ┆2 U 4 A in the Message Block o Header Size The number of bytes in the Header ANNEL SECURITY FILTER 2.2.1 General Description Please refer to figure overleaf. The Multichannel Security Filter (MCSF) is a multi-input/multi-output configuration ┆
0x32400…32500 (50, 0, 4) Sector 3205ff00348941 ┆2 4 A 1 Header: Channel number Reception and Input Line Status Block size Header size CRC Check Word Message Directory Message: The received message ┆
0x32500…32600 (50, 0, 5) Sector 32063b00348941 ┆2 ; 4 A Trailer: Channel number MESSAGE BLOCK FORMAT vision of the Input control. The message is preprocessed and validated in the same way as if it were a single channel filter. After validation, the message is transferred to the butler memory ┆
0x32600…32700 (50, 0, 6) Sector 3207ff00348941 ┆2 4 A 1 o CRC check word The Cyclic Redundancy check word generated from the message. o Message Directory A list of entry points for the sets and fields of the message, generated ┆
0x32700…32800 (50, 0, 7) Sector 3108ff00348941 ┆1 4 Aby examining the received characters of the message for the set and field delimiters. 2.2.3.2 Message Body The Message Body is the received message, ordered into bytes of characters. 2.2.3.3 Trailer The Trailer is a single byte with the ch┆
0x32800…32900 (50, 0, 8) Sector 32091f00348941 ┆2 4 Ass the cell boundaries. modes and is therefore not attractive from a security point of view. 2.1.3.3 Delay The delay will in general be increased by the multi- plexing, but the amount of delay is heavily depending upon the combination of mult┆
0x32900…32a00 (50, 0, 9) Sector 320a8400348941 ┆2 4 A 1 MULTI CHANNEL SECURITY FILTER (MCSF) ile multiplexing of many channels on message level may give excessive delays. So, from a delay point of view the lowest ┆
0x32a00…32b00 (50, 0, 10) Sector 320bff00348941 ┆2 4 A 1 2.2.2 Data flow Messages from all input lines are received and stored independently in the Line Terminators. The Input Control interrogates the modules cyclically. The interroga┆
0x32b00…32c00 (50, 0, 11) Sector 320cff00348941 ┆2 4 Ation is acknowledged if a full message has been received, and the message is transferred in byte-parallel to the MPP. Message preprocessing and validation is performed exactly as for the single channel security filter with the remark that input an┆
0x32c00…32d00 (50, 0, 12) Sector 320dff00348941 ┆2 4 Ad output channel identification must be provided together with the message when logged or displayed on the operators terminal for operator assisted validation. The validated message is transferred to the Line Terminator addressed by the Output con┆
0x32d00…32e00 (50, 0, 13) Sector 320eff00348941 ┆2 4 Atrol. The entire message is transferred to the memory of the Line Terminator at speed. The Operator Assisted Validation is performed in parallel with the automated validation. The entire message is transferred to and stored in the operator's termi┆
0x32e00…32f00 (50, 0, 14) Sector 320fff00348941 ┆2 4 Anal during the partial validation. After this, the entire message is transferred to the GK for automated validation of the remaining fields. A replica of the message is retained in the Mg Tape Interface of the MPP. The butler is erased if the me┆
0x32f00…33000 (50, 0, 15) Sector 3200ff00348941 ┆2 4 Assage has been accepted. Otherwise, the message is logged onto the tape before erasure of the buffer. 2.2.3 Message Block Specification The received message is augmented with auxilliary information arranged in a header. The combined and formatt┆
0x33000…33100 (51, 0, 0) Sector 3301ff00348941 ┆3 4 At establishes the input/output path, validated according to a preprogrammed table with legal combinations. The control is backed up by an alternative (redundant) communication path verification method. o The channels are multiplexed by offerin┆
0x33100…33200 (51, 0, 1) Sector 3302ff00348941 ┆3 4 Ag service in a cyclic manner. The processing power shall be sufficient to service a worst case situation and secure methods with acceptable performance shall be used in case of an overflow situation. o The software complexity should be minimized ┆
0x33200…33300 (51, 0, 2) Sector 33033e00348941 ┆3 > 4 Af.ex. by designing separate packages for each channel. 2.1.3 The problems The potential problems in multiplexing have already been suggested in the para 2.2. They are in summary o Security o Complexing o Delay o Channel Capac┆
0x33300…33400 (51, 0, 3) Sector 3304ff00348941 ┆3 4 A 1 2.2 MULTICHANNEL SECURITY FILTER 2.2.1 General Description Please refer to figure overleaf. The Multichannel Security Filter (MCSF) is a multi-input/multi-output configuration ┆
0x33400…33500 (51, 0, 4) Sector 3305ff00348941 ┆3 4 Awhere all channels share the Multi Purpose Processor (MPP), the Gate Keepers GK and the terminal. One Line Terminator is used for each channel, each with storage capacity for two messages in each direction. The received message is transferred to t┆
0x33500…33600 (51, 0, 5) Sector 3306ff00348941 ┆3 4 Ahe MPP with high speed over the Input Bus under supervision of the Input control. The message is preprocessed and validated in the same way as if it were a single channel filter. After validation, the message is transferred to the butler memory ┆
0x33600…33700 (51, 0, 6) Sector 3307ff00348941 ┆3 4 Aof the Selected Line Terminator under supervision of the Output control. Finally, the Line Terminator performs the transmission of the message. The MCSF is a modular expansion of the single channel filter using the same basic concept, only with a ┆
0x33700…33800 (51, 0, 7) Sector 3208ff00348941 ┆2 4 Afew additional components to control the data paths. The basic security is achieved by using a Cellular Structure in several levels with both hardware and software restructions on the capabilities, in particular the communication capabilities acro┆
0x33800…33900 (51, 0, 8) Sector 3309ff00348941 ┆3 4 Avery complicated failure modes and is therefore not attractive from a security point of view. 2.1.3.3 Delay The delay will in general be increased by the multi- plexing, but the amount of delay is heavily depending upon the combination of mult┆
0x33900…33a00 (51, 0, 9) Sector 330aff00348941 ┆3 4 Aiplexing scheme and the hardware configuration. Multiplexing on bit or byte level gives only negligible additional delay, while multiplexing of many channels on message level may give excessive delays. So, from a delay point of view the lowest ┆
0x33a00…33b00 (51, 0, 10) Sector 330bff00348941 ┆3 4 Alevel is preferrred. However, considerations of security risks lead to a multiplexing on message level. Hence, the hardware configuration must be adjusted to provide an acceptably low delay. 2.1.3.4 Channel Capacity Channel capacity is another ┆
0x33b00…33c00 (51, 0, 11) Sector 330cff00348941 ┆3 4 Aexposed parameter. The reference capacity is, in this context, the capacity of a particular channel without any filter. Insertion of a multiplexed filter may reduce the capacity significant- ly unless precautions are made. 2.1.3.5 Overflow Mes┆
0x33c00…33d00 (51, 0, 12) Sector 330dea00348941 ┆3 j 4 Asage Overflow situations may occur, either as a result of failures inside or outside the filter, or perhaps even as an acceptable (rare) situation. In both cases, the system must respond to such a situation in a secure manner. a time sliced basis.┆
0x33d00…33e00 (51, 0, 13) Sector 330eff00348941 ┆3 4 A 1 2.1.4 Conclusion The previous subsection suggests the following characteristics of a viable solution. o Multiplexing is on message level. Only one message is processed at a time┆
0x33e00…33f00 (51, 0, 14) Sector 330fff00348941 ┆3 4 A and the message is processed in entity without interference from other channels or messages from the same channel. o A Line Terminator is provided for each channel to provide the necessary reception and storage capacity for avoiding a decrease i┆
0x33f00…34000 (51, 0, 15) Sector 3300ff00348941 ┆3 4 An the individual channel capacities. This also minimizes the risk of electromagnetic or galvanic cross-talk. o All information in common areas is erased before a new message is entered. o A dedicated, simple hardware/firmware control circui┆
0x34000…34100 (52, 0, 0) Sector 3401e700348941 ┆4 g 4 Asparent to the connected ADP systems except for the delay. o The channel capacity must not be (significantly) reduced. o The design shall provide reliable operation. o Behaviour in case of a failure must be acceptable. 2.2.4 Interface Spec┆
0x34100…34200 (52, 0, 1) Sector 3402a900348941 ┆4 ) 4 A 1 Multi Channel Security Filter Communication paths terface Specification ... 2.2.4.4 Output Bus ......................... ┆
0x34200…34300 (52, 0, 2) Sector 3403ff00348941 ┆4 4 A 1 2.1.3 The problems The potential problems in multiplexing have already been suggested in the para 2.2. They are in summary o Security o Complexing o Delay o Channel Capac┆
0x34300…34400 (52, 0, 3) Sector 3404ff00348941 ┆4 4 Aity o Overflow It is throughout this subsection assumed that sufficient processing power is available to perform the validation in negligible time. 2.1.3.1 Security The multiplexing inherently introduces a multitude of failure modes which m┆
0x34400…34500 (52, 0, 4) Sector 3405ff00348941 ┆4 4 Aay lead to security breack. The most obvious risks are o Illegal source/validation table/sink relationship. The mere fact that there are several channels increases the risk of passing classified information to a channel with too low channel lev┆
0x34500…34600 (52, 0, 5) Sector 3406ff00348941 ┆4 4 Ael. o Residue A residue of classified information may inadvertently be carried along with a lower classified message. o Cross-talk The presence of several inputs and/or outputs gives the risk of cross-talk, here used to describe any mecha┆
0x34600…34700 (52, 0, 6) Sector 34075d00348941 ┆4 ] 4 Anism which may inintendedly convey legible information from one channel to another. INTRODUCTION This technical note represents the output of work package no. 320, Configuration Study, within the framework of the Security Filter Study, performe┆
0x34700…34800 (52, 0, 7) Sector 3308ff00348941 ┆3 4 A 1 2.1.3.2 Complexity Multiplexing hardware/software may be more or less complex. Very high efficiency is typically achieved through high complexity. High complexity typically gives ┆
0x34800…34900 (52, 0, 8) Sector 3409ff00348941 ┆4 4 Anes through one filter - Sharing of hardware between two or more filters - Other systems configurations (installation site, security levels) - Use of common software and hardware - Use of commercially available hardware and software (multi-s┆
0x34900…34a00 (52, 0, 9) Sector 340a7000348941 ┆4 p 4 Aource) - Use of electronic switches Each point will be treated separately in the following chapters. ┆
0x34a00…34b00 (52, 0, 10) Sector 340b6b00348941 ┆4 k 4 A 1 1.2 TERMS AND ABBREVIATIONS # SECURITY FILTER SYS.DIV. =6'C*-:!<~ B%-!/=6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x34b00…34c00 (52, 0, 11) Sector 340cff00348941 ┆4 4 A 1 2 TIME DIVISION MULTIPLEXING 2.1 ANALYSIS 2.1.1 The need ADP systems often have many communication lines in and out. This raises a demand for a solution, which is more cos┆
0x34c00…34d00 (52, 0, 12) Sector 340dff00348941 ┆4 4 At efficient than a simple duplication of hardware. This demand can often be met by time division multiplexing or time slicing methods. The idea is to utilise the hardware more efficiently by letting it handle several channels on a time sliced basis.┆
0x34d00…34e00 (52, 0, 13) Sector 340eff00348941 ┆4 4 A The slice may be either at bit level, often called time division multiplex, or at a higher level (message), often called time slicing. 2.1.2 The requirements The general requirements to the multiplexing functions restricted to fixed point-to-p┆
0x34e00…34f00 (52, 0, 14) Sector 340fff00348941 ┆4 4 Aoint communication. See figure overleaf. The channel of ADP system A using line no. 1A must communicate only with the channel of ADP system C using line no. 1B. The particular characteristics which must be considered when evaluating potential ┆
0x34f00…35000 (52, 0, 15) Sector 3400ff00348941 ┆4 4 Asolutions are first of all o Security in all aspects. o The cost should be substantially reduced compared to the simple hardware duplication. o The design must accommodate certification. o Delay must be kept low. o The filter shall be tran┆
0x35000…35100 (53, 0, 0) Sector 3501ff00348941 ┆5 4 A.. 2.2.3 Message Block Specification ............ 2.2.3.1 The Header ......................... 2.2.3.2 Message Body ....................... 2.2.3.3 Trailer ............................ 2.2.4 Interface Spec┆
0x35100…35200 (53, 0, 1) Sector 3502ff00348941 ┆5 4 Aification ................ 2.2.4.1 Line Interface ..................... 2.2.4.2 Input Bus .......................... 2.2.4.3 Internal Interface Specification ... 2.2.4.4 Output Bus ......................... ┆
0x35200…35300 (53, 0, 2) Sector 3503ff00348941 ┆5 4 A 2.2.5 Module Specification ................... 2.2.5.1 Line Terminator (LT) ............... 2.2.5.2 Multi Purpose Processor (MPP) ...... 2.2.5.3 Input Control ...................... 2.2.5.4 Output Control .....┆
0x35300…35400 (53, 0, 3) Sector 3504ff00348941 ┆5 4 A................ 2.3 PERFORMANCE ................................ 2.3.1 Security ............................... 2.3.1.1 Illegal Source/Validation table/sink relationship ....................... 2.3.1.2 Resi┆
0x35400…35500 (53, 0, 4) Sector 3505ff00348941 ┆5 4 Adue ............................ 2.3.1.3 Cross-talk ......................... 2.3.2 Throughput ............................. 2.3.3 Delay .................................. 3 SHARING OF HARDWARE .....................┆
0x35500…35600 (53, 0, 5) Sector 3506ba00348941 ┆5 : 4 A...... 3.1 ANALYSIS .................................. 3.2 SECURITY ................................... 3.3 CONCLUSION ................................. y britton-lee will provide telephone/telex support and software rele ┆
0x35600…35700 (53, 0, 6) Sector 3507ff00348941 ┆5 4 A 1 1 GENERAL 1.1 INTRODUCTION This technical note represents the output of work package no. 320, Configuration Study, within the framework of the Security Filter Study, performe┆
0x35700…35800 (53, 0, 7) Sector 3408ff00348941 ┆4 4 Ad under contract no. FK 8219 between the Air Material Command of the RDAF and Christian Rovsing A/S. The Configuration Study still examine the feasibility and the performance of technical solutions to: - Multiplexing two or more communication li┆
0x35800…35900 (53, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(53,0, 9), len=0xff, h3=41348941}, f00=»3489A «, f01=»SECURITY FILTER «, f02=»pan «, f03=»PEH «, f04=»Fra 1.1 EJ SLET «, f05=06-04-83 09:40, f06=» 12 «, f07=»37 «, f08=» 44554 «, f09=11-04-83 15:40, f10=» «, f11=»01 «, f12=» 25 «, f13=11-04-83 14:59, f14=13-04-83 12:53, f15=»0210A «, f16=» 38 «, f17=» 12 «, f18=»38 «, f19=» 708 «, f20=» 44579 «, f21=» «, f22=» «, f99=100000000010052710110190aaca1505000000000000014203d100df}
0x35900…35a00 (53, 0, 9) Sector 350a2600348941 ┆5 & 4 A 5 5 5 4 4 4 4 4 3 3 2 2 2 2 2 1 1 1 0 0 0 / / . . . - - , , , + + * * * ) ) ( DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: ┆
0x35a00…35b00 (53, 0, 10) Sector 350b8e00348941 ┆5 4 A 1 PEH/830411 # SECURITY FILTER SYS.DIV. =6'C*-:!<~ B%-!/=6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x35b00…35c00 (53, 0, 11) Sector 350cff00348941 ┆5 4 A 1 TABLE OF CONTENTS Page 1 ┆
0x35c00…35d00 (53, 0, 12) Sector 350dff00348941 ┆5 4 A 1 GENERAL ....................................... 1.1 INTRODUCTION ............................... 1.2 TERMS AND ABBREVIATIONS .................... 2 TIME DIVISIO┆
0x35d00…35e00 (53, 0, 13) Sector 350eff00348941 ┆5 4 AN MULTIPLEXING .................... 2.1 ANALYSIS ................................... 2.1.1 The need ............................... 2.1.2 The requirements ....................... 2.1.3 The problems ....................┆
0x35e00…35f00 (53, 0, 14) Sector 350fff00348941 ┆5 4 A....... 2.1.3.1 Security ........................... 2.1.3.2 Complexity ......................... 2.1.3.3 Delay .............................. 2.1.3.4 Channel Capacity ................... 2.1.3.5 Overflow┆
0x35f00…36000 (53, 0, 15) Sector 3500ff00348941 ┆5 4 A ........................... 2.1.4 Conclusion ............................. 2.2 MULTICHANNEL SECURITY FILTER ............... 2.2.1 General Description .................... 2.2.2 Data flow ............................┆
0x36000…36100 (54, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(54,0, 1), len=0xff, h3=41349041}, f00=»3490A «, f01=»HAWK CCIS «, f02=»pan «, f03=»ALF «, f04=»EJ SLET «, f05=07-04-83 10:12, f06=» 1 «, f07=»33 «, f08=» 1326 «, f09=08-04-83 10:21, f10=» «, f11=»05 «, f12=» 118 «, f13=08-04-83 10:27, f14=13-04-83 12:54, f15=»0210A «, f16=» 2 «, f17=» 1 «, f18=»38 «, f19=» 28 «, f20=» 1444 «, f21=» «, f22=» «, f99=020000000010056610110130aaca15050000000000000042030a00df}
0x36100…36200 (54, 0, 1) WangDocumentBody
[…0x6…]
0x36800…36900 (54, 0, 8) Sector 3609ff00111241 ┆6 A 1 4.2.7.4 Subpackage Data The data pertinent to this subpackage are contained in the VDU table. The data used in the validation ref. sec. 4.1.4. VDU TABLE ┆
0x36900…36a00 (54, 0, 9) Sector 360aff00111241 ┆6 A VDU STATE LP STATE VDU INPUT TYPE CONTROL INPUT TYPE CHECK ID COMMAND ┆
0x36a00…36b00 (54, 0, 10) Sector 360bff00111241 ┆6 A FIELDS DATA VDU-INPUT-TYPE = FUNCTION KEY, CMD, DATA CONTROL = INIT, CLEAR, MENU, FORM-SPLIT, ILLEGAL, NO. VALID INPUT TYPE = COPSY, VDU CHECK ID = FALSE, TRUE COMMAND = FALSE, TRUE┆
0x36b00…36c00 (54, 0, 11) Sector 360c5000111241 ┆6 P A FIELDS DATA = FALSE, TRUE VDU STATE = UP, DOWN LP STATE = UP, DOWN DISPLAY-FORMAT PROCEDURE (7.1.3) CHECK-ID = TRUE? GET DATA FROM CONFIG. TABLE NO DATA? DISPLAY "ILLEGAL ID" ┆
0x36c00…36d00 (54, 0, 12) Sector 360d7a00111241 ┆6 z A 1 4.2.7.5 Interface Refer to sec. 4.1.6.3.3. Fig. 4.2.7.3-7 a volume to be mounted, the following conditions are checked: - disk status - volume name - mou┆
0x36d00…36e00 (54, 0, 13) Sector 360eff00111241 ┆6 A 1 4.2.8 Watchdog Subpackage (WDSP) 4.2.8.1 Functional Specifications The WDSP contains the functions defined in fig. 4.2.8.1-1. The WDSP receives via the V24 lines information ┆
0x36e00…36f00 (54, 0, 14) Sector 360fff00111241 ┆6 Afrom the PUs and the operator VDU. Via the control CCB the CCB driver scans the status in the different crates via digital input ports, and if a discrepancy between the expected status and the scanned status exists, a report is issued. Furthermore┆
0x36f00…37000 (54, 0, 15) Sector 3600ff00111241 ┆6 A, the WDSP checks that the PU periodically sends "keep alive", if a PU stops sending "keep alive" the WDP will take the following action if: - An active PU with a standby PU exists: switchover - A standby PU with an active PU exists: notify ac┆
0x37000…37100 (55, 0, 0) Sector 37014300111241 ┆7 C AEDURE END FORMAT END VALIDATE - FORMAT Fig. 4.2.7.3-8 SYNTAX & SEMANTIC PROCEDURE (7.1) CASE VDU-INPUT-TYPE: FUNCTION KEY? - PERFORM IDENTIFY-FUNCTION KEY PROCEDURE CMD? - PERFORM DETERM-FORM PROCEDURE ┆
0x37100…37200 (55, 0, 1) Sector 3702ff00111241 ┆7 A 1 EXECUTE - CONTROL PROCEDURE (7.1.7) SEND CONTROL RECORD TO COPSY WAIT ANSWER (TIME) TIME OUT ? - ANSWER = NOK END EXECUTE - CONTROL ┆
0x37200…37300 (55, 0, 2) Sector 37031b00111241 ┆7 A Fig. 4.2.7.3-9 NPUT-TYPE PERFORM VDU-CONTROL PROCEDURE END SYNTAX & SEMANTIC PROCEDURE Fig. 4.2.7.3-4 f Day Format (STOD) The following parameters are checked: - month, the same as in the PU - day, the same as in the PU -┆
0x37300…37400 (55, 0, 3) Sector 3704ff00111241 ┆7 A 1 LOG PROCEDURE (7.2) STORE TIME INTO BUFFER STORE COMMAND-DATA INTO BUFFER ANSWER = OK? - COMPLETED INTO BUFFER STORE "REJECTED" INTO BUFFER CONTROL = ILLE┆
0x37400…37500 (55, 0, 4) Sector 37057700111241 ┆7 w AGAL DISPLAY "COMMAND REJECTED" LP - DOWN ? SEND BUFFER TO LP END LOG Fig. 4.2.7.3-10 7.3-5 LTUX To accept the LTUX type, it has to fit with the devices (e.g. VDU, LP) connected to this LTUX (only devices "in service"). ┆
0x37500…37600 (55, 0, 5) Sector 3706ff00111241 ┆7 A 1 VDU CONTROL PROCEDURE (7.1.6) CASE CONTROL: INIT ? - PARAM = TRANSMIT, VDU-LOCK CLEAR? - PARAM? = CMD LINE,CLEAR CMO,CLEAR FORM, VDU UNLOCK ┆
0x37600…37700 (55, 0, 6) Sector 3707ff00111241 ┆7 A VDU - INPUT TYPE = FUNCTION KEY MENU? - PARAM = CMD LINE, CLEAR CMD, VDU UNLOCK VDU INPUT TYPE = FUNCTION KEY FORM-SPLIT? - PARAM = FIRST FIELD, VDU UNLOCK VDU INPUT TYPE = FUNCTION KEY ILLEGAL? - PARAM =┆
0x37700…37800 (55, 0, 7) Sector 3608e800111241 ┆6 h A CMD LINE, VDU UNLOCK VDU INPUT TYPE = FUNCTION KEY NO-VALID? - PARAM = FIELD#, VDU UNLOCK VDU INPUT TYPE = FUNCTION KEY SEND VDU PARAM END CONTROL END VDU CONTROL Fig. 4.2.7.3-11 If status is set "Off┆
0x37800…37900 (55, 0, 8) Sector 3709ff00111241 ┆7 A 1 CASE CMD CONTINUED TDXB ? FORMAT = 13 VOLU ? FORMAT = 14 STAC ? FORMAT = 15 SWCH ? FORMAT = 16 CLOSE ? FORMAT = 17 STSB ? FORMAT = 18 STOD ? FORMA┆
0x37900…37a00 (55, 0, 9) Sector 370aff00111241 ┆7 AT = 19 LMOS ? FORMAT = 20 STRM ? FORMAT = 21 PRSS ? FORMAT = 22 MODE ? FORMAT = 23 CONTROL = FORM-SPLIT CHECK ID = FALSE OTHERS? DISPLAY "ILLEGAL CMD" CMD = FALSE CONTROL = ILLEGAL END┆
0x37a00…37b00 (55, 0, 10) Sector 370b3600111241 ┆7 6 A CMD END SPECIFY - FORMAT Fig. 4.2.7.3-6b m COPSY to the CMI. CMI sends a log to the operator LP specifying the control executed. The interface to the CMI from COPSY and the WDP is shown in fig. 4.2.7.3-1. The data flow and control logic is┆
0x37b00…37c00 (55, 0, 11) Sector 370cff00111241 ┆7 A 1 DISPLAY-FORMAT PROCEDURE (7.1.3) CHECK-ID = TRUE? GET DATA FROM CONFIG. TABLE NO DATA? DISPLAY "ILLEGAL ID" ┆
0x37c00…37d00 (55, 0, 12) Sector 370d9c00111241 ┆7 A CONTROL = ILLEGAL GET FORMAT OUTPUT FORMAT CONTROL = FORMAT? - OUTPUT FIELDS END DISPLAY FORMAT Fig. 4.2.7.3-7 a volume to be mounted, the following conditions are checked: - disk status - volume name - mou┆
0x37d00…37e00 (55, 0, 13) Sector 370eff00111241 ┆7 A 1 VALIDATE - FORMAT PROCEDURE (7.1.4) CASE FORMAT: 7 ? - PERFORM LTUX LINE PROCEDURE 8 ? - PERFORM LTUX PROCEDURE 9 ? - PERFORM BSM-X PROCEDURE 10 ? - PE┆
0x37e00…37f00 (55, 0, 14) Sector 370fff00111241 ┆7 ARFORM LTU-LINE PROCEDURE 11 ? - PERFORM LTU PROCEDURE 12 ? - PERFORM DISK DRIVE PROCEDURE 13 ? - PERFORM TDX-BUS PROCEDURE 14 ? - PERFORM VOLUME PROCEDURE 15 ? - PERFORM START ACTIVE PROCEDURE 16 ? - PERFORM SWITCHOVER PROCEDURE ┆
0x37f00…38000 (55, 0, 15) Sector 3700ff00111241 ┆7 A 17 ? - PERFORM CLOSE DOWN PROCEDURE 18 ? - PERFORM START SB PROCEDURE 19 ? - PERFORM SET TIME PROCEDURE 20 ? - PERFORM LOAD MODE PROCEDURE 21 ? - PERFORM SET TRACE PROCEDURE 22 ? - PERFORM PRINT PROCEDURE 23 ? - PERFORM MODE PROC┆
0x38000…38100 (56, 0, 0) Sector 3801ff00111241 ┆8 A 1 SYNTAX & SEMANTIC PROCEDURE (7.1) CASE VDU-INPUT-TYPE: FUNCTION KEY? - PERFORM IDENTIFY-FUNCTION KEY PROCEDURE CMD? - PERFORM DETERM-FORM PROCEDURE ┆
0x38100…38200 (56, 0, 1) Sector 3802ff00111241 ┆8 A COMMAND FALSE? PERFORM SPECIFY-FORMAT PROCEDURE DATA? - PERFORM VALIDATE-FORMAT PROCEDURE FIELDS DATA OK? - PERFORM CONTROL PROCEDURE PERFORM LOG PR┆
0x38200…38300 (56, 0, 2) Sector 38038200111241 ┆8 AOCEDURE END VDU-INPUT-TYPE PERFORM VDU-CONTROL PROCEDURE END SYNTAX & SEMANTIC PROCEDURE Fig. 4.2.7.3-4 f Day Format (STOD) The following parameters are checked: - month, the same as in the PU - day, the same as in the PU -┆
0x38300…38400 (56, 0, 3) Sector 3804ff00111241 ┆8 A 1 IDENTIFY - FUNCTION KEY PROCEDURE (7.1.5) ENTER KEY? - CMD SPLIT? - VDU INPUT TYPE = CMD VDU INPUT TYPE = DATA CONTROL = INIT COMM┆
0x38400…38500 (56, 0, 4) Sector 38057d00111241 ┆8 } AAND KEY? - CONTROL = CLEAR CONTROL = NO - ACTION END IDENTIFY FUNCTION KEY Fig. 4.2.7.3-5 LTUX To accept the LTUX type, it has to fit with the devices (e.g. VDU, LP) connected to this LTUX (only devices "in service"). ┆
0x38500…38600 (56, 0, 5) Sector 3806ff00111241 ┆8 A 1 SPECIFY - FORMAT PROCEDURE (7.1.2) READ COMMAND CASE COMMAND: HIME? - FORMAT = 1 TDXS? - FORMAT = 2 IOSY? - FORMAT = 3 PUSY? - FORMAT = 4 SOFT?┆
0x38600…38700 (56, 0, 6) Sector 3807ff00111241 ┆8 A - FORMAT = 5 WDCM? - FORMAT = 6 CONTROL = MENU LXLX? - FORMAT = 7 LTUX? - FORMAT = 8 BSMX? - FORMAT = 9 LTLN? - FORMAT = 10 LTUU? - FORMAT = 11 DDRI? - FORMAT = 12 CONTROL = FORM-SPLIT┆
0x38700…38800 (56, 0, 7) Sector 37084700111241 ┆7 G A CHECK ID = TRUE CONTINUE Fig. 4.2.7.3-6a 4.2.7.1.4.3 Validation of BSM-X Format (BSMX) During validation of the data from the BSM-X format, the status is checked against the status of the TDX Bus. If status is set "Off┆
0x38800…38900 (56, 0, 8) Sector 38099c00111241 ┆8 A 1 Fig. 4.2.7.2-1 Software Structure cannot be set) are allowed if one of the TDX buses is set active. 4.2.7.1.4.5 Validation of LT┆
0x38900…38a00 (56, 0, 9) Sector 380aff00111241 ┆8 A 1 4.2.7.3 Data Flow and Control Logic The CMI transfers data from the operator VDU and when the data have been validated, they are given over to COPSY which executes the control. W┆
0x38a00…38b00 (56, 0, 10) Sector 380bff00111241 ┆8 Ahen control is executed, a reply is returned from COPSY to the CMI. CMI sends a log to the operator LP specifying the control executed. The interface to the CMI from COPSY and the WDP is shown in fig. 4.2.7.3-1. The data flow and control logic is┆
0x38b00…38c00 (56, 0, 11) Sector 380c5f00111241 ┆8 _ A shown in the HIPO chart fig. 4.2.7.3-2 and the flow charts fig. 4.2.7.3-3 to 4.2.7.3-11 offline (standby, manual) or out of service. is updated with the actual data. ends error reports to COPSY in the ERQ. Refer to section 4.1.6.2.1.9 for a ┆
0x38c00…38d00 (56, 0, 12) Sector 380d9c00111241 ┆8 A 1 Figs. 4.2.7.3-1 CMI Block Diagram a volume to be mounted, the following conditions are checked: - disk status - volume name - mou┆
0x38d00…38e00 (56, 0, 13) Sector 380e9c00111241 ┆8 A 1 Fig. 4.2.7.3-2 Command Interpreter the disk on which the volume is to be mounted has to be online. 4.2.7.1.4.8 Validation of Disk┆
0x38e00…38f00 (56, 0, 14) Sector 380fff00111241 ┆8 A 1 1 MAIN-PROGRAM-CMI (7.0) LOOP: TEST INPUT-TYPE CASE INPUT-TYPE: VDU? - PERFORM┆
0x38f00…39000 (56, 0, 15) Sector 3800aa00111241 ┆8 * A SYNTAX & SEMANTIC PROCEDURE COPSY? - PERFORM INITIALIZE PROCEDURE END INPUT-TYPE END LOOP: END MAIN-PROGRAM-CMI Fig. 4.2.7.3-3 It is checked if an ACTIVE PU already exists (by the watchdog). 4.2.7.1.4.10 Val┆
0x39000…39100 (57, 0, 0) Sector 39018e00111241 ┆9 Aidation of Switchover Format (SWCH) This format only needs syntax check of the numbers specified in the unprotected format fields. ┆
0x39100…39200 (57, 0, 1) Sector 3902ff00111241 ┆9 A 1 4.2.7.1.4.11 Validation of Close-down Format (CLOS) This format only needs syntax check of the numbers specified in the unprotected format fields. 4.2.7.1.4.12 Validation of ┆
0x39200…39300 (57, 0, 2) Sector 3903ff00111241 ┆9 AStart-up Standby Format (STSB) Syntax check of the numbers in the format fields. 4.2.7.1.4.13 Validation of Set Time of Day Format (STOD) The following parameters are checked: - month, the same as in the PU - day, the same as in the PU -┆
0x39300…39400 (57, 0, 3) Sector 3904ff00111241 ┆9 A hour, the same as in the PU - minute, see below - second, 00 - 60 valid The time of day set by the operator must not differ from the PU clock with more than 8 minutes. 4.2.7.1.4.14 PRINT Syntax only. 4.2.7.1.4.15 Set NORMAL/AT RISK Mo┆
0x39400…39500 (57, 0, 4) Sector 39051b00111241 ┆9 Ade Syntax only. uration, the following checks take place: - type of LTUX against devices connected - status of LTUX To accept the LTUX type, it has to fit with the devices (e.g. VDU, LP) connected to this LTUX (only devices "in service"). ┆
0x39500…39600 (57, 0, 5) Sector 3906ff00111241 ┆9 A 1 4.2.7.2 Software Structure The CMI functions are implemented in one process. The process is divided into a main program and a number of procedures. Ref. fig. 4.2.7.2-1. The ma┆
0x39600…39700 (57, 0, 6) Sector 3907ff00111241 ┆9 Ain program serves the input queue from COPSY and the user connection to the WDP. When input from the operator VDU is identified, control is given over to the VDU-INPUT procedure. If the status of a LP or VDU is changed COPSY informs the CMI via ┆
0x39700…39800 (57, 0, 7) Sector 38081800111241 ┆8 Athe input queue. 4.2.7.1.4.3 Validation of BSM-X Format (BSMX) During validation of the data from the BSM-X format, the status is checked against the status of the TDX Bus. If status is set "Off┆
0x39800…39900 (57, 0, 8) Sector 3909ff00111241 ┆9 Aline", an offline TDX bus has to exist. 4.2.7.1.4.4 Validation of TDX Bus Format (TDXB) For the TDX format all combinations of the status (error cannot be set) are allowed if one of the TDX buses is set active. 4.2.7.1.4.5 Validation of LT┆
0x39900…39a00 (57, 0, 9) Sector 390aff00111241 ┆9 AU Line Format (LTLN) It shall be controlled that the type of LTU line inserted (SCARS, CCIS, NICS TARE, VDU or LP) suits the LTU to which it is connected. Any type of line can be stated as long as status of the line is set disable. Error status ┆
0x39a00…39b00 (57, 0, 10) Sector 390bff00111241 ┆9 Acannot be specified by the operator. 4.2.7.4.1.6 Validation of LTU Format (LTUU) When the data for the LTU is specified, the following parameters are checked: - type - status The type has to suit the LTU line(s) connected to the LTU else ┆
0x39b00…39c00 (57, 0, 11) Sector 390c9000111241 ┆9 Athe status has to be set "out of service". The status of the LTU line can be set active, offline (standby, manual) or out of service. is updated with the actual data. ends error reports to COPSY in the ERQ. Refer to section 4.1.6.2.1.9 for a ┆
0x39c00…39d00 (57, 0, 12) Sector 390dff00111241 ┆9 A 1 4.2.7.1.4.7 Validation of Volume Format (VOLU) When the operator has specified a volume to be mounted, the following conditions are checked: - disk status - volume name - mou┆
0x39d00…39e00 (57, 0, 13) Sector 390eff00111241 ┆9 Ant/dismount It is checked (in COPSY) that the volume name specified corresponds to the volume name on the actually loaded disk pack. The status of the disk on which the volume is to be mounted has to be online. 4.2.7.1.4.8 Validation of Disk┆
0x39e00…39f00 (57, 0, 14) Sector 390fff00111241 ┆9 A Drive Format (DDRI) To accept disk drive format, the following is checked: - disk status If only one mirrored disk exists, it is not allowed to take it offline. Error status cannot be specified. 4.2.7.1.4.9 Validation of Start-up Format ┆
0x39f00…3a000 (57, 0, 15) Sector 3900ff00111241 ┆9 A(STAC) When a PU is started up as ACTIVE, the following is checked: - state of PU specified - mode to start from - type of application software to be loaded It is checked if an ACTIVE PU already exists (by the watchdog). 4.2.7.1.4.10 Val┆
0x3a000…3a100 (58, 0, 0) Sector 3a018d00111241 ┆: A 1 Fig. 4.2.7.1.1.4-1 ┆
0x3a100…3a200 (58, 0, 1) Sector 3a02ff00111241 ┆: A 1 4.2.7.1.4.1 Validation of LTUX-LINE Format (LXLN) When an LTUX line is to be inserted in the configuration, the following checks take place: - Type of device against LTUX - Sp┆
0x3a200…3a300 (58, 0, 2) Sector 3a03ff00111241 ┆: Aeed against device - Status of device To accept the type of device (e.g. VDU, MTP, PTR, OCR), it is checked that the LTUX includes the device type specified. However, any type of device is accepted if the status of the device is "out of service"┆
0x3a300…3a400 (58, 0, 3) Sector 3a04ff00111241 ┆: A. It is checked that the speed specified to the device is legal. To accept any reconfiguration, the device has to be taken "out of service" or its status has to be error. 4.2.2.1.4.2 Validation of LTUX Format (LTUX) When an LTUX has to be i┆
0x3a400…3a500 (58, 0, 4) Sector 3a05ff00111241 ┆: Anserted in the configuration, the following checks take place: - type of LTUX against devices connected - status of LTUX To accept the LTUX type, it has to fit with the devices (e.g. VDU, LP) connected to this LTUX (only devices "in service"). ┆
0x3a500…3a600 (58, 0, 5) Sector 3a06ff00111241 ┆: A If the types do not fit, the operator is notified to set the devices "out of service" or insert the right type of LTUX. The status of an LTUX can either be "in service" or "out of service". If one or more of the LTUX lines does not fit with the ┆
0x3a600…3a700 (58, 0, 6) Sector 3a07b000111241 ┆: 0 ALTUX type, the status of the LTUX has to be set out of service. To accept a reconfiguration, the LTUX has to be taken "out of service" or its status has to be error. "$<!#<6 ! <6 {M)(sC I! <6 ! "(= <q#p!"<6 !#<6 ! "$<!&<6$`i6 {M)(sM &M7 ┆
0x3a700…3a800 (58, 0, 7) Sector 3908ff00111241 ┆9 A 1 4.2.7.1.4.3 Validation of BSM-X Format (BSMX) During validation of the data from the BSM-X format, the status is checked against the status of the TDX Bus. If status is set "Off┆
0x3a800…3a900 (58, 0, 8) Sector 3a09ff00111241 ┆: A 1 4.2.7.1.1 Initialization The CMI receives a start up command via its input queue CMIQ. Having received the start up command, the coroutines in the CMI are started. The start-u┆
0x3a900…3aa00 (58, 0, 9) Sector 3a0aff00111241 ┆: Ap command specifies user connections to the: - WDP-VDU command split - WDP-VDU format split - WDP-LP to be offered by CMI. 4.2.7.1.2 Determine Format Type The commands from the command line are divided into: - request of menu formats -┆
0x3aa00…3ab00 (58, 0, 10) Sector 3a0bff00111241 ┆: A request of control formats When the commands are interpreted, the format ID is calculated. If a command is illegal, an error message is returned to the operator, and a new command has to be entered. 4.2.7.1.3 Display Format The format spec┆
0x3ab00…3ac00 (58, 0, 11) Sector 3a0cb400111241 ┆: 4 Aified by the command is via the Format handler sent to the VDU and if a control format is displayed, the unprotected fields and a PORT-ID is updated with the actual data. ends error reports to COPSY in the ERQ. Refer to section 4.1.6.2.1.9 for a ┆
0x3ac00…3ad00 (58, 0, 12) Sector 3a0dff00111241 ┆: A 1 4.2.7.1.4 Validation When the operator has updated the format then the unprotected fields are read. The fields are checked for syntax and semantic errors, before a control record ┆
0x3ad00…3ae00 (58, 0, 13) Sector 3a0eff00111241 ┆: Ais handed over to COPSY. When COPSY has executed the control specified, the VDU is unlocked and the operator can now enter new commands. If the operator has entered an illegal character in an unprotected field, a warning is sent to him and the cu┆
0x3ae00…3af00 (58, 0, 14) Sector 3a0fff00111241 ┆: Arsor is positioned in the actual field. The operator can reject his choice of command (until it is sent to COPSY) by depressing the function key CANCEL. During COPSY execution, the operator is notified in the response line, that it is not possib┆
0x3af00…3b000 (58, 0, 15) Sector 3a00b700111241 ┆: 7 Ale to cancel the current command. The following subsection describes the semantic checks to be done. The functional breakdown of validation is given in fig. 4.2.7.1.1.4-1. ┆
0x3b000…3b100 (59, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(59,0, 1), len=0xff, h3=41111241}, f00=»1112A «, f01=»CPS/SDS/004 «, f02=»sdv «, f03=»BHJ «, f04=»4.2.7 «, f05=02-07-81 10:16, f06=» 5 «, f07=»29 «, f08=» 24685 «, f09=24-07-81 10:36, f10=» 1 «, f11=»22 «, f12=» 65 «, f13=24-07-81 12:17, f14=24-07-81 15:01, f15=»0066A «, f16=» 38 «, f17=» 8 «, f18=»31 «, f19=» 388 «, f20=» 26243 «, f21=» «, f22=» 0 «, f99=730010000110066610110480aaca15050000000000000037037f00df}
0x3b100…3b200 (59, 0, 1) Sector 3b022600111241 ┆; & A ; ; ; : : : : : 9 9 9 8 8 8 8 8 8 8 8 7 7 7 7 7 7 6 6 6 6 6 5 5 5 4 4 4 4 4 3 DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: ┆
0x3b200…3b300 (59, 0, 2) Sector 3b039400111241 ┆; A 1 CPS/SDS/004 BHJ/810801 SYSTEM STATUS AND CONTROL CAMPS :!<~ B%-!/=6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x3b300…3b400 (59, 0, 3) Sector 3b04ff00111241 ┆; A 1 4.2.7 Command Interpreter (CMI) 4.2.7.1 Functional Specification The CMI serves the commands and format fields sent from the operator VDU. When a command is received and vali┆
0x3b400…3b500 (59, 0, 4) Sector 3b05ff00111241 ┆; Adated, the CMI sends the requested format and the actual data to the operator VDU. The operator will now update the format and hereafter the updated fields are returned to the CMI. When the fields are validated, they are given over to COPSY for ex┆
0x3b500…3b600 (59, 0, 5) Sector 3b06ff00111241 ┆; Aecution. The last step in the fulfillment of a reconfiguration, is to return a log to the operator LP. The log contains information of the command executed or rejected and the time of execution (DATE and TIME). The initialization of the CMI and┆
0x3b600…3b700 (59, 0, 6) Sector 3b079900111241 ┆; A the validation of the operator VDU input is given in the following subsections. The functional breakdown of the CMI is shown in fig. 4.2.7.1-1. ! "(= Z=q#p!"<6 !&<6 ! "$<!#<6 ! <6 {M)(sC I! <6 ! "(= <q#p!"<6 !#<6 ! "$<!&<6$`i6 {M)(sM &M7 ┆
0x3b700…3b800 (59, 0, 7) Sector 3a08a200111241 ┆: " A 1 Fig. 4.2.7.1-1 FUNCTIONAL DECOMPOSITION 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=!┆
0x3b800…3b900 (59, 0, 8) Sector 3b09f500111341 ┆; u A CRATE ADDRESS = PU # 1, PU # 2, TDX 1, TDX 2, CU BSM-X # 1, ... BSM-X # 10. PORT POINTER = pointer to the output port in the crate. STATUS = status to be set via the output part. 2 ┆
0x3b900…3ba00 (59, 0, 9) Sector 3b0aff00111341 ┆; A 1 4.2.8.4.3 Power Monitoring Table CRATE ADDRESS PORT POINTER MINIMUM VOLTAGE PRESENT VOLTAGE ┆
0x3ba00…3bb00 (59, 0, 10) Sector 3b0bff00111341 ┆; A CRATE-ADDRES = PU # 1, . . . . , BSM-X # 10. PORT POINTER = pointer to the A/D converter. MINIMUM VOLTAGE = digital presentation of the minimum voltage to be accepted. PRESENT VOLTAGE = digital┆
0x3bb00…3bc00 (59, 0, 11) Sector 3b0c3900111341 ┆; 9 A presentation of the monitored voltage. PU PROCEDURE PU ACTIVE? PERFORM SWITCH PROCEDURE PERFORM DISA-SB PROCEDURE SET ERROR TYPE END PU Fig. 4.2.8.3.3.3-b ? PERFORM PU┆
0x3bc00…3bd00 (59, 0, 12) Sector 3b0dff00111341 ┆; A 1 4.2.8.4.4 System Table The system table contains the information of the state of the V24 interfaces: - PU # 1 - PU # 2 - VDU - LP PU┆
0x3bd00…3be00 (59, 0, 13) Sector 3b0eff00111341 ┆; A # 1 STATE PU # 2 STATE CU # 1 - CU # 2 - TDX # 1 - LP STATE VDU STATE PU state = ACTIVE, STANDBY, OFFLINE CU state = ACTIVE, OF┆
0x3be00…3bf00 (59, 0, 14) Sector 3b0f5f00111341 ┆; _ AFLINE TDX state = ACTIVE, STANDBY, OFFLINE LP state = ON, OFF VDU state = ON, OFF CEDURE SET DISA PU STATUS SET POINTER SEND CCB WAIT ANSWER SET ENABLE-IO STATUS SET POINTER SEND CCB WAIT ANSWER SEND "GO-ACTIVE" TO SB END ┆
0x3bf00…3c000 (59, 0, 15) Sector 0200ff00111341 ┆ A 1 4.2.8.4.5 Message Format Between WDP and PUs KIND LINE # header of a message SERIAL NUMBER ┆
0x3c000…3c100 (60, 0, 0) Sector 3c01ff00111341 ┆< A 1 TDX PROCEDURE STANDBY TDX? E WARNING TO AC PU PERFORM TDX-SWITCH PROCEDURE E WARNING TO AC PU ERROR TYPE END TDX Fig. 4.2.8.3.3.3-┆
0x3c100…3c200 (60, 0, 1) Sector 3c020800111341 ┆< Af Fig. 4.2.8.3.3.1-b Hipo Diagram CEDURE VDU-UP-MES ? - PERFORM VDU-INIT-PROCEDURE CASE VDU-INPUT: FORMAT ? - SEND BUFFER TO PU 1. FUNCKEY ? - PERFORM INIT-TRANS PROCEDURE ┆
0x3c200…3c300 (60, 0, 2) Sector 3c03ff00111341 ┆< A 1 TDX-SWITCH PROCEDURE SWITCHING LOOP: BSMX N ACTIVE? SET UP POINTER SEND CCB WAIT ANSWER LAST ONE? EXIT SWITCHING N = N+1 END SWITC┆
0x3c300…3c400 (60, 0, 3) Sector 3c044600111341 ┆< F AHING LOOP: END TDX-SWITCH Fig. 4.2.8.3.3.3-g INDIRECT-CMD PROCEDURE CASE CMD: DISABLE-PU? PERFORM DISASB PROCEDURE DISABLE-IO-A? " DISA-IO-A " DISABLE-IO-B? " DISA-IO-B " ENABLE-IO-A? " EN┆
0x3c400…3c500 (60, 0, 4) Sector 3c05ff00111341 ┆< A 1 4.2.8.4 WDP Data The following tables are used by the WDP: - digital input control table - digital output control table - power monitoring table - system table. 4.2.8┆
0x3c500…3c600 (60, 0, 5) Sector 3c06ff00111341 ┆< A.4.1 Digital Input Control Table Crate Address Port Pointer Expected Status Monitored Status Crat┆
0x3c600…3c700 (60, 0, 6) Sector 3c078a00111341 ┆< Ae address = PU # 1, PU # 2, CU, TDX # 1, TDX # 2, BSM-X # 1 - #10. Port pointer = pointer to the input port in the crate. FLINE ? PU OFFLINE ? MODE = OFFLINE PERFORM ILLEGAL PROCEDURE OTHERS : SEND FUNCTION KEY TO PU VDU┆
0x3c700…3c800 (60, 0, 7) Sector 3b08ff00111341 ┆; A 1 4.2.8.4.2 Digital Output Control Table CRATE ADDRESS PORT POINTER STATUS CRATE ADDRESS ┆
0x3c800…3c900 (60, 0, 8) Sector 3c099e00111341 ┆< APERFORM CU PROCEDURE TDX? PERFORM TDX PROCEDURE END POINTER SEND ERROR REPORT END EXCEPTION PROCEDURE Fig. 4.2.8.3.3.3 LP END LP HANDLER Fig. 4.2.8.3.4-1 PU ON LINE ? ERROR = 2 ┆
0x3c900…3ca00 (60, 0, 9) Sector 3c0aff00111341 ┆< A 1 PU-SOFT PROCEDURE CASE ACTION: SWITCH? PERFORM SWITCH PROCEDURE DISA-AC? SET DISA STATUS SET POINTER SEND CCB AWAIT ANSWER DISA-SB? PE┆
0x3ca00…3cb00 (60, 0, 10) Sector 3c0b6e00111341 ┆< n ARFORM DISA-SB PROCEDURE END ACTION SET ERROR TYPE END PU-SOFT Fig. 4.2.8.3.3.3-a CASE TYPE-INPUT INDIRECT-CMD? PERFORM INDIRECT-CMD PROCEDURE EXCEPTION? PERFORM EXCEPTION PROCEDURE DIRECT-CMD? PERFORM DIRECT-┆
0x3cb00…3cc00 (60, 0, 11) Sector 3c0cf300111341 ┆< s A 1 PU PROCEDURE PU ACTIVE? PERFORM SWITCH PROCEDURE PERFORM DISA-SB PROCEDURE SET ERROR TYPE END PU Fig. 4.2.8.3.3.3-b ? PERFORM PU┆
0x3cc00…3cd00 (60, 0, 12) Sector 3c0dfb00111341 ┆< { A 1 DISA-SB PROCEDURE SET DISA-PU STATUS SET POINTER SEND CCB WAIT ANSWER SEND "SB-DOWN" TO AC-PU END DISA-SB Fig. 4.2.8.3.3.3-c ┆
0x3cd00…3ce00 (60, 0, 13) Sector 3c0eff00111341 ┆< A 1 CU PROCEDURE CASE ERROR-TYPE: ACTIVE PART? PERFORM SWITCH PROCEDURE SB PART? SEND E WARNING TO AC-PU MANUAL-SWITCH? SEND WARNING TO AC-PU END ER┆
0x3ce00…3cf00 (60, 0, 14) Sector 3c0f4e00111341 ┆< N AROR-TYPE UPDATE TABLE END CU Fig. 4.2.8.3.3.3-d SWITCH PROCEDURE SET DISA PU STATUS SET POINTER SEND CCB WAIT ANSWER SET ENABLE-IO STATUS SET POINTER SEND CCB WAIT ANSWER SEND "GO-ACTIVE" TO SB END ┆
0x3cf00…3d000 (60, 0, 15) Sector 3c00d700111341 ┆< W A 1 BSMX PROCEDURE SET ERROR TYPE SEND REPORT TO AC PU END BSMX PROCEDURE Fig. 4.2.8.3.3.3-e ┆
0x3d000…3d100 (61, 0, 0) Sector 3d01ff00111341 ┆= A 1 GCUA PROCEDURE SET ENABLE PU STATUS SET UP POINTER SEND CCB WAIT ANSWER SET ENABLE-ID-STATUS SET UP POINTER SEND CCB WAIT ANSWER END GCUA (Get CU ACCESS┆
0x3d100…3d200 (61, 0, 1) Sector 3d023500111341 ┆= 5 A) Fig. 4.2.8.3.3.1-b Hipo Diagram CEDURE VDU-UP-MES ? - PERFORM VDU-INIT-PROCEDURE CASE VDU-INPUT: FORMAT ? - SEND BUFFER TO PU 1. FUNCKEY ? - PERFORM INIT-TRANS PROCEDURE ┆
0x3d200…3d300 (61, 0, 2) Sector 3d036200111341 ┆= b A 1 Hipo Diagram READ INPUT QUEUE CASE TYPE TIMER? PERFORM TIM PROCEDURE KEEP ALIVE? RESET COUNTER TOD? U┆
0x3d300…3d400 (61, 0, 3) Sector 3d04ff00111341 ┆= A 1 INDIRECT-CMD PROCEDURE CASE CMD: DISABLE-PU? PERFORM DISASB PROCEDURE DISABLE-IO-A? " DISA-IO-A " DISABLE-IO-B? " DISA-IO-B " ENABLE-IO-A? " EN┆
0x3d400…3d500 (61, 0, 4) Sector 3d05ff00111341 ┆= AA-IO-A " ENABLE-IO-B? " ENA-IO-B " BSM-X-ACTIVE? " BSM-X-AC " BSM-X-OFF/SB? " BSM-X-SB/OFF " BSM-X-DISCON? " BSM-X-DISCON " TDX-SWITCH? " TDX SWITCHOVER? " SWITCH END CMD RETURN ACK TO COPSY END INDIRECT┆
0x3d500…3d600 (61, 0, 5) Sector 3d062300111341 ┆= # A-CMD Fig. 4.2.8.3.3.2 Fig. 4.2.8.3.2-2 CMI PROCEDURE SEND ACK TO VDU CASE CMD: SWITCH ? ACTION = 1 RESET ? ACTION = 2 MACL ? ACTION = 3 DISA ? ACTION = 4 MAIN ? ACTION = 5 ┆
0x3d600…3d700 (61, 0, 6) Sector 3d076200111341 ┆= b A 1 Hipo Diagram PU # 2 ? SET COMMUNICATE = 2 OFFLINE ? PU OFFLINE ? MODE = OFFLINE PERFORM ILLEGAL PROCEDURE OTHERS : SEND FUNCTION KEY TO PU VDU┆
0x3d700…3d800 (61, 0, 7) Sector 3c08ff00111341 ┆< A 1 EXCEPTION PROCEDURE READ TYPE SOFT-PU? PERFORM SOFT-PU PROCEDURE READ POINTER CASE POINTER: PU? PERFORM PU PROCEDURE BSMX? PERFORM BSMX PROCEDURE CU? ┆
0x3d800…3d900 (61, 0, 8) Sector 3d09ca00111341 ┆= J AORT ? REPORT TO VDU ERROR REPORT # TO LP DRIVER REPORT? SEND LP-STATE TO PU NO-PRINT END INPUT NO-PRINT? SEND BUFFER TO LP END LP HANDLER Fig. 4.2.8.3.4-1 PU ON LINE ? ERROR = 2 ┆
0x3d900…3da00 (61, 0, 9) Sector 3d0a6200111341 ┆= b A 1 Hipo Diagram PU ENABLE ? ERROR = 3 5? 2? ┆
0x3da00…3db00 (61, 0, 10) Sector 3d0bff00111341 ┆= A 1 SYS M&C READ INPUT Q CASE TYPE-INPUT INDIRECT-CMD? PERFORM INDIRECT-CMD PROCEDURE EXCEPTION? PERFORM EXCEPTION PROCEDURE DIRECT-CMD? PERFORM DIRECT-┆
0x3db00…3dc00 (61, 0, 11) Sector 3d0cb900111341 ┆= 9 ACMD PROCEDURE ERROR-REPORT? SEND REPORT TO PU (COPSY) STATUS-REQUEST? PERFORM STATUS-REQ PROCEDURE END TYPE-INPUT END SYS M&C fig. 4.2.8.3.3-1 INE # VDU-IN ? PERFORM VDU-CHECK PROCEDURE PU-IN ? PERFORM PU┆
0x3dc00…3dd00 (61, 0, 12) Sector 3d0dff00111341 ┆= A 1 DIRECT-CMD PROCEDURE CASE CMD: RESET? SET RESET-STATUS MACL? SET MACL STATUS DISA? SET DISA STATUS MAIN? SET MAIN STATUS SET UP POINTER ┆
0x3dd00…3de00 (61, 0, 13) Sector 3d0ed300111341 ┆= S A SEND CCB WAIT ANSWER GCUA? PERFORM GCUA PROCEDURE SWITCH? PERFORM SWITCH PROCEDURE END CMP READ TIME SEND TIME AND CMP-EXECUTION TO LP END DIRECT-CMP Fig. 4.2.8.3.3-2 complete status in the crate is returned ta┆
0x3de00…3df00 (61, 0, 14) Sector 3d0fff00111341 ┆= A 1 SWITCH PROCEDURE SET DISA PU STATUS SET POINTER SEND CCB WAIT ANSWER SET ENABLE-IO STATUS SET POINTER SEND CCB WAIT ANSWER SEND "GO-ACTIVE" TO SB END ┆
0x3df00…3e000 (61, 0, 15) Sector 3d003800111341 ┆= 8 ASWITCH Fig. 4.2.8.3.3.1-a PU-CHECK PROCEDURE CASE PU-TO-VDU-INFO: VDU-CONTROL? - CURSOR-TO-CMD? VDU-INPUT = 1 FUNCKEY ACK? ┆
0x3e000…3e100 (62, 0, 0) Sector 3e01a400111341 ┆> $ AFORMAT? END PU-TO-VDU-INFO SEND BUFFER TO PU END PU-CHECK Fig. 4.2.8.3.1.3 ┆
0x3e100…3e200 (62, 0, 1) Sector 3e026200111341 ┆> b A 1 Hipo Diagram CEDURE VDU-UP-MES ? - PERFORM VDU-INIT-PROCEDURE CASE VDU-INPUT: FORMAT ? - SEND BUFFER TO PU 1. FUNCKEY ? - PERFORM INIT-TRANS PROCEDURE ┆
0x3e200…3e300 (62, 0, 2) Sector 3e03ff00111341 ┆> A 1 PU HANDLER READ INPUT QUEUE CASE TYPE TIMER? PERFORM TIM PROCEDURE KEEP ALIVE? RESET COUNTER TOD? U┆
0x3e300…3e400 (62, 0, 3) Sector 3e048c00111341 ┆> APDATE TIME-OF-DAY CONTROL? SEND TO SYS M&C Q END TYPE END PU-HANDLER Fig. 4.2.8.3.2-1 INIT PARAM TO VDU WAIT LOOP: GET MESSAGE BUFFER TIME OUT? SEND "VDU DOWN" TO PU, EXIT WAIT ┆
0x3e400…3e500 (62, 0, 4) Sector 3e05ff00111341 ┆> A 1 TIM PROCEDURE DECREMENT COUNTER # COUNTER ZERO? PU ACTIVE? SB PU EXISTING? ACTION = SWITCH ACTION = DISABLE-AC ACTION = DISABLE-SB? SEND ACTION TO┆
0x3e500…3e600 (62, 0, 5) Sector 3e064100111341 ┆> A A SYS M&C END TIM Fig. 4.2.8.3.2-2 CMI PROCEDURE SEND ACK TO VDU CASE CMD: SWITCH ? ACTION = 1 RESET ? ACTION = 2 MACL ? ACTION = 3 DISA ? ACTION = 4 MAIN ? ACTION = 5 ┆
0x3e600…3e700 (62, 0, 6) Sector 3e076200111341 ┆> b A 1 Hipo Diagram PU # 2 ? SET COMMUNICATE = 2 OFFLINE ? PU OFFLINE ? MODE = OFFLINE PERFORM ILLEGAL PROCEDURE OTHERS : SEND FUNCTION KEY TO PU VDU┆
0x3e700…3e800 (62, 0, 7) Sector 3d08ff00111341 ┆= A 1 LP HANDLER READ INPUT Q OFFLINE? SAME INPUT TYPE? NO ERROR REPORT? NEXT PAGE AND HEADER TO LP CASE INPUT: CMI LOG? WD DIRECT CMD-LOG ? ERROR REP┆
0x3e800…3e900 (62, 0, 8) Sector 3e09ff00111341 ┆> A 1 SEMAN PROCEDURE CASE ACTION: 1? - OTHER PU STANDBY? ERROR = 1 PU ON LINE ? ERROR = 2 ┆
0x3e900…3ea00 (62, 0, 9) Sector 3e0aff00111341 ┆> A 4? 6? PU ENABLE ? ERROR = 3 5? 2? ┆
0x3ea00…3eb00 (62, 0, 10) Sector 3e0bff00111341 ┆> A END ACTION ERROR = 0 ? SEND ACTION TO SYS M&C WAIT ANSWER (TIME) OK? ERROR = 4 PERFORM ILLEGAL PROCEDURE VDU INPUT = 1 FUNCKEY┆
0x3eb00…3ec00 (62, 0, 11) Sector 3e0c4800111341 ┆> H A SEND VDU CONTROL END SEMAN PROCEDURE Fig. 4.2.8.3.1.2-c VDU HANDLER RECEIVE VDU-HAN-QUEUE MODE = OFFLINE ? PERFORM OFFLI-PROCEDURE READ LINE # CASE LINE # VDU-IN ? PERFORM VDU-CHECK PROCEDURE PU-IN ? PERFORM PU┆
0x3ec00…3ed00 (62, 0, 12) Sector 3e0dff00111341 ┆> A 1 ILLEGAL PROCEDURE CASE ERROR: 1? DISPLAY NO SB !! 2? DISPLAY PU ONLINE !! 3? DISPLAY PU ENABLE !! ┆
0x3ed00…3ee00 (62, 0, 13) Sector 3e0e8700111341 ┆> A 4? DISPLAY NO CONTROL !! END ERROR END ILLEGAL PROCEDURE Fig. 4.2.8.3.1.2-d ref. sec. 4.2.8.4.4.3 and converted to an ASCII character string, before the complete status in the crate is returned ta┆
0x3ee00…3ef00 (62, 0, 14) Sector 3e0f6200111341 ┆> b A 1 Hipo Diagram RE READ LINE # PU - IN ? SEND BUFFER TO VDU WAIT ACK SEND BUFFER TO LP FUNCTION KEY ? COMMAND ? SEND ACK, ENTER ONLINE SEND ACK ┆
0x3ef00…3f000 (62, 0, 15) Sector 3e00ff00111341 ┆> A 1 PU-CHECK PROCEDURE CASE PU-TO-VDU-INFO: VDU-CONTROL? - CURSOR-TO-CMD? VDU-INPUT = 1 FUNCKEY ACK? ┆
0x3f000…3f100 (63, 0, 0) Sector 3f016200111341 ┆? b A 1 Hipo Diagram ┆
0x3f100…3f200 (63, 0, 1) Sector 3f02ff00111341 ┆? A 1 VDU-CHECK PROCEDURE VDU-UP-MES ? - PERFORM VDU-INIT-PROCEDURE CASE VDU-INPUT: FORMAT ? - SEND BUFFER TO PU 1. FUNCKEY ? - PERFORM INIT-TRANS PROCEDURE ┆
0x3f200…3f300 (63, 0, 2) Sector 3f037500111341 ┆? u A COMMAND ? - PERFORM CMI-PROCEDURE END VDU-INPUT END VDU-CHECK Fig. 4.2.8.3.1.2 TATUS AND CONTROL CAMPS :!<~ B%-!/=6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x3f300…3f400 (63, 0, 3) Sector 3f04ff00111341 ┆? A 1 INIT-TRANS PROCEDURE ENTER? SEND ACK TO VDU SEND INIT PARAM TO VDU WAIT LOOP: GET MESSAGE BUFFER TIME OUT? SEND "VDU DOWN" TO PU, EXIT WAIT ┆
0x3f400…3f500 (63, 0, 4) Sector 3f05ba00111341 ┆? : A ACK ? VDU-INPUT = COMMAND, EXIT WAIT RETURN BUFFER NACK END WAIT LOOP VDU-INPUT = FORMAT SEND KEY TO PU END INIT-TRANS Fig. 4.2.8.3.1.2-a PU drivers - VDU driver - LP driver - CCB driver - KERNEL and a┆
0x3f500…3f600 (63, 0, 5) Sector 3f06ff00111341 ┆? A 1 CMI PROCEDURE SEND ACK TO VDU CASE CMD: SWITCH ? ACTION = 1 RESET ? ACTION = 2 MACL ? ACTION = 3 DISA ? ACTION = 4 MAIN ? ACTION = 5 ┆
0x3f600…3f700 (63, 0, 6) Sector 3f07ff00111341 ┆? A G CUA ? ACTION = 6 PERFORM SEMAN PROCEDURE PU # 1 ? SET COMMUNICATE = 1 PU # 2 ? SET COMMUNICATE = 2 OFFLINE ? PU OFFLINE ? MODE = OFFLINE PERFORM ILLEGAL PROCEDURE OTHERS : SEND FUNCTION KEY TO PU VDU┆
0x3f700…3f800 (63, 0, 7) Sector 3e084700111341 ┆> G A INPUT = FORMAT END CMD END CMI Fig. 4.2.8.3.1.2-b Fig. 4.2.8.2-1 Watchdog Software Structure Overview #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=!┆
0x3f800…3f900 (63, 0, 8) Sector 3f09c300111341 ┆? C A 1 4.2.8.3 Data Flow and Control Logic The data flow and control logic are shown in the Hipo diagram and the flowgrams. 4: 2i=:g=~ JV3C/4!"<6 #6 MB&! =6 !,<6 :]=2'< AMD MB&!,<6 ! ┆
0x3f900…3fa00 (63, 0, 9) Sector 3f0a5d00111341 ┆? ] A 1 Hipo Diagram ZMo Ck4 KMo 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! ┆
0x3fa00…3fb00 (63, 0, 10) Sector 3f0b5d00111341 ┆? ] A 1 Hipo Diagram q5M@1MI1:h= Rp5Cr4IMM.:^=~ B}5I:g=~ J 5IC$3I > S C_* ┆
0x3fb00…3fc00 (63, 0, 11) Sector 3f0cff00111341 ┆? A 1 VDU HANDLER RECEIVE VDU-HAN-QUEUE MODE = OFFLINE ? PERFORM OFFLI-PROCEDURE READ LINE # CASE LINE # VDU-IN ? PERFORM VDU-CHECK PROCEDURE PU-IN ? PERFORM PU┆
0x3fc00…3fd00 (63, 0, 12) Sector 3f0d5a00111341 ┆? Z A-CHECK PROCEDURE END LINE # END VDU HANDLER Fig. 4.2.8.3.1 itoring Request Monitoring requests are sent from COPSY. A request contains the PORT ID of the crate to be monitored. The SYS M&C reads the digital status from ┆
0x3fd00…3fe00 (63, 0, 13) Sector 3f0e5d00111341 ┆? ] A 1 Hipo Diagram r status is taken from the pow-scan-table ref. sec. 4.2.8.4.4.3 and converted to an ASCII character string, before the complete status in the crate is returned ta┆
0x3fe00…3ff00 (63, 0, 14) Sector 3f0fff00111341 ┆? A 1 OFFLI PROCEDURE READ LINE # PU - IN ? SEND BUFFER TO VDU WAIT ACK SEND BUFFER TO LP FUNCTION KEY ? COMMAND ? SEND ACK, ENTER ONLINE SEND ACK ┆
0x3ff00…40000 (63, 0, 15) Sector 3f007100111341 ┆? q A INIT TRANS SEND BUFFER TO PU SEND BUFFER TO LP END OFFLI Fig. 4.2.8.3.1.1 ┆
0x40000…40100 (64, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(64,0, 1), len=0xff, h3=41111341}, f00=»1113A «, f01=»CPS/SDS/004 «, f02=»tdh «, f03=»BHJ «, f04=»fra fig 4.2.8.15-1 «, f05=02-07-81 10:39, f06=» 5 «, f07=»36 «, f08=» 14583 «, f09=24-07-81 14:04, f10=» «, f11=»00 «, f12=» 14 «, f13=24-07-81 14:05, f14=24-07-81 15:02, f15=»0066A «, f16=» 45 «, f17=» 7 «, f18=»52 «, f19=» 172 «, f20=» 19725 «, f21=» «, f22=» «, f99=020010000110066610110480aaca15050000000000000037035800df}
0x40100…40200 (64, 0, 1) Sector 40022d00111341 ┆@ - A @ @ @ @ ? ? ? ? ? ? ? ? ? ? > > > > > > > > > = = = = = = = = = < < < < < < < < < ; ; ; DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatte Forfatte┆
0x40200…40300 (64, 0, 2) Sector 40039400111341 ┆@ A 1 CPS/SDS/004 BHJ/810801 SYSTEMS STATUS AND CONTROL CAMPS :!<~ B%-!/=6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x40300…40400 (64, 0, 3) Sector 40046000111341 ┆@ ` A 1 fig. 4.2.8.15-1 p.MP- Rm.> IM)-MI,:^=~ B~.> IMB'IM2& 9x2"<!Z="(=^#Vk"$<:]=2#<:^=~ J6.! <6 M8) R6.> I! <6 M8)I!h=6 ! =6 M")IM"):g=~ J /:h=2>=M?.Mj': < Zn.C / E*:=k 0wM% !;=4C┆
0x40400…40500 (64, 0, 4) Sector 4005ff00111341 ┆@ A 1 4.2.8.2 Software Structure The WDP contains a set of processes, which is divided into standard processes: - PU drivers - VDU driver - LP driver - CCB driver - KERNEL and a┆
0x40500…40600 (64, 0, 5) Sector 4006ff00111341 ┆@ Application processes: - PU handler - SYS M&C - VDU handler - LP handler. The interactive communication between the processes is done via semaphore queues. The processes, which are not waiting in a semaphore queue, are given CPU time by the KE┆
0x40600…40700 (64, 0, 6) Sector 4007a800111341 ┆@ ( ARNEL, cf CDS-MIC/003/USM/0003. Fig. 4.2.8.1-1 gives the allocation of the functions onto the processes. Fig. 4.2.8.2-1 gives a software structure overview. 6 !&<6 ! "$<!#<6 ! <6 {M)(sC I! <6 ! "(= <q#p!"<6 !#<6 ! "$<!&<6$`i6 {M)(sM &M7 ┆
0x40700…40800 (64, 0, 7) Sector 3f088400111341 ┆? A 1 Fig. 4.2.8.2-1 Watchdog Software Structure Overview #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=!┆
0x40800…40900 (64, 0, 8) Sector 4009ff00109441 ┆@ A SSC to OLP ........................ 77 3.4 FUNCTIONS MAINTAINED BY OTHER PACKAGES .... 77 3.4.1 Recovery .............................. 77 3.4.2 Error Detection and Handling .......... 78 3.4.3 Security .....................┆
0x40900…40a00 (64, 0, 9) Sector 400aff00109441 ┆@ A......... 78 4 PACKAGE DESIGN ................................ 79 4.1 PACKAGE OVERVIEW .......................... 79 4.1.1 Functional Specification .............. 79 4.1.1.1 Checkpoint Transmission ........... 79 4.1.1.┆
0x40a00…40b00 (64, 0, 10) Sector 400bff00109441 ┆@ A2 Checkpoint Reception .............. 79 4.1.1.3 On-Line Diagnostics ............... 81 4.1.1.4 LINE M&C .......................... 81 4.1.1.4.1 Execution of External Commands Monitoring of System Connection 83 ┆
0x40b00…40c00 (64, 0, 11) Sector 400cff00109441 ┆@ A 4.1.1.4.2 Technical Error Report Handling 85 4.1.1.5 Technical Error Report Handling ... 88 4.1.1.5.1 Error Reception ............... 92 4.1.1.5.2 HW Error Fix-Up ............... 92 4.1.1.5.2.1 LTU Line .........┆
0x40c00…40d00 (64, 0, 12) Sector 400dff00109441 ┆@ A......... 92 4.1.1.5.2.2 LTU ....................... 93 4.1.1.5.2.3 LTUX Line ................. 93 4.1.1.5.2.4 LTUX ...................... 93 4.1.1.5.2.5 BSM-X ..................... 93 4.1.1.5.2.6 Off-Lin┆
0x40d00…40e00 (64, 0, 13) Sector 400eff00109441 ┆@ Ae Disk Volume ...... 93 4.1.1.5.2.7 Off-Line Disk ............. 93 4.1.1.5.2.8 Floppy Disk Volume ........ 94 4.1.1.5.2.9 Floppy Disk ............... 94 4.1.1.5.2.10 WDP ....................... 94 4.1.1.5.2┆
0x40e00…40f00 (64, 0, 14) Sector 400fff00109441 ┆@ A.11 WDP-VDU ................... 94 4.1.1.5.2.12 WDP-LP .................... 94 4.1.1.5.2.13 TDX-Bus ................... 95 4.1.1.5.2.14 Mirrored Disk Volume ...... 95 4.1.1.5.2.15 Mirrored Disk ............. 96 ┆
0x40f00…41000 (64, 0, 15) Sector 2200ff00109441 ┆" A 4.1.1.5.2.16 Standby PU ................ 96 4.1.1.5.2.17 Online Pu ................. 96 4.1.1.6 Operator Commands ................. 96 4.1.1.6.1 Software Control .............. 97 4.1.1.6.1.1 Load of new SW .......┆
0x41000…41100 (65, 0, 0) Sector 4101ff00109441 ┆A Aent Capacity ................ 71 2.3.3 Flexibility ........................... 71 2.3.3.1 Hardware Configuration Changes .... 71 2.3.3.2 Operator Commands ................. 71 2.3.3.3 Loading of New Versions of Software ┆
0x41100…41200 (65, 0, 1) Sector 4102ff00109441 ┆A A 71 2.3.4 Accuracy and Validity ................. 72 2.3.4.1 Accuracy of Input Data ............ 72 2.3.4.2 Accuracy of Transmitted Data ...... 72 3 ENVIRONMENT ................................... 73 3.1 EQUIPMENT .....┆
0x41200…41300 (65, 0, 2) Sector 4103ff00109441 ┆A A............................ 73 3.2 SOFTWARE .................................. 73 3.2.1 System Software ....................... 73 3.2.2 Development Software .................. 73 3.3 INTERFACES ..............................┆
0x41300…41400 (65, 0, 3) Sector 4104ff00109441 ┆A A.. 73 3.3.1 External Interfaces ................... 73 3.3.2 Package Interfaces .................... 74 3.3.2.1 SSC to TEP ........................ 74 3.3.2.2 TEP to SSC ........................ 74 3.3.2.3 SSC to MMO┆
0x41400…41500 (65, 0, 4) Sector 4105ff00109441 ┆A AN/MMS ................... 74 3.3.2.4 MMON/MMS to SSC ................... 74 3.3.2.5 SSC to SFM ........................ 75 3.3.2.6 SSC to CSF Process ................ 75 3.3.2.7 SSC to QMON ....................... 75 ┆
0x41500…41600 (65, 0, 5) Sector 4106ff00109441 ┆A A 3.3.2.8 SSC to Timer Monitor .............. 75 3.3.2.9 SSC to TMP ........................ 75 3.3.2.10 SSC to MDP ........................ 76 3.3.2.11 SSC to LOG ........................ 76 3.3.2.12 LOG to SSC ...........┆
0x41600…41700 (65, 0, 6) Sector 4107bb00109441 ┆A ; A............. 76 3.3.2.13 SSC to THP ........................ 76 3.3.2.14 SSC to SAR ........................ 76 3.3.2.15 SSC to STP ........................ 77 ...... 46 2.2.2.1.1.2 Start-Up of Active and ┆
0x41700…41800 (65, 0, 7) Sector 4008ff00109441 ┆@ A 1 3.3.2.16 SSC to IOC ........................ 77 3.3.2.17 SSC to SSP ........................ 77 3.3.2.18┆
0x41800…41900 (65, 0, 8) Sector 4109ff00109441 ┆A A2.2.2.2 Checkpointing and Recovery ........ 58 2.2.2.2.1 Checkpointing ................. 58 2.2.2.2.2 Recovery ...................... 60 2.2.2.2.2.1 Cold ...................... 60 2.2.2.2.2.2 WARM1 ................┆
0x41900…41a00 (65, 0, 9) Sector 410aff00109441 ┆A A..... 60 2.2.2.2.2.3 WARM2 ..................... 60 2.2.2.2.2.4 WARM3 ..................... 61 2.2.2.2.2.5 SB1 ....................... 61 2.2.2.2.2.6 SB2 ....................... 61 2.2.2.3 Handling of SSC ┆
0x41a00…41b00 (65, 0, 10) Sector 410bff00109441 ┆A AInternal Detected Errors ............................ 61 2.2.2.3.1 In the AC PU .................. 63 2.2.2.3.2 In the SB PU .................. 63 2.2.2.3.3 In the WDP .................... 63 2.2.2.4 Integrit┆
0x41b00…41c00 (65, 0, 11) Sector 410cff00109441 ┆A Ay of Operation ............ 63 2.2.2.5 Data Collection ................... 66 2.2.2.5.1 LOG ........................... 66 2.2.2.5.2 Statistics .................... 66 2.2.2.5.3 Reports ....................... 68 ┆
0x41c00…41d00 (65, 0, 12) Sector 410da500109441 ┆A % A 2.2.2.6 Security .......................... 68 2.2.2.6.1 Security on DAMOS Objects ..... 68 2.2.2.6.2 Security on CAMPS Queues ...... 68 ............. 16 1.2.1 Applicable Documents .................. 16 1.2.2 Projec┆
0x41d00…41e00 (65, 0, 13) Sector 410eff00109441 ┆A A 1 2.3 CHARACTERISTICS ........................... 69 2.3.1 Timing ................................ 69 2.3.1┆
0x41e00…41f00 (65, 0, 14) Sector 410fff00109441 ┆A A.1 Switchover ........................ 69 2.3.1.2 Initialization .................... 69 2.3.1.3 Recovery/Restart .................. 69 2.3.1.4 Watchdog Line Speeds .............. 69 2.3.1.5 Response Time ...............┆
0x41f00…42000 (65, 0, 15) Sector 4100ff00109441 ┆A A...... 70 2.3.1.6 Start-Up and Close-Down Sequence .. 70 2.3.1.7 Priorities of Input ............... 70 2.3.2 Throughput ............................ 70 2.3.2.1 Increase of Software Size ......... 70 2.3.2.2 Equipm┆
0x42000…42100 (66, 0, 0) Sector 4201ff00109441 ┆B A Reports ........................... 35 2.2.1.5.1 Active PU Handling ............ 36 2.2.1.5.1.1 SW Error Reports .......... 36 2.2.1.5.1.1.1 Child Action .......... 36 2.2.1.5.1.1.2 DAMOS/CSF Action .....┆
0x42100…42200 (66, 0, 1) Sector 4202ff00109441 ┆B A. 39 2.2.1.5.1.1.3 COPSY Handling of SW Reports ............... 39 2.2.1.5.1.2 HW Error Reports .......... 40 2.2.1.5.2 Handling of Errors Reported by Other Packages to the SSC in th┆
0x42200…42300 (66, 0, 2) Sector 4203ff00109441 ┆B Ae SB PU .............. 41 2.2.1.6 Operator Commands to an On-Line PU 41 2.2.1.7 Off-Line PU Operation ............. 42 2.2.1.7.1 Commands to the Off-Line PU ... 42 2.2.1.7.2 Allocation of Resources to the ┆
0x42300…42400 (66, 0, 3) Sector 42042c00109441 ┆B , AOff-Line PU ................... 42 nktion? Til hvor? Fra hvor? Dokument: Hvilken kommando? Hvilken side: (Sletter) (S]ger) (Udf]rer) Inds`t hvilket? Slette hvilket? Flytte hvilket? Kopiere hvilket? Bytte hvilket? Bytte med? S]ge hvilket? ┆
0x42400…42500 (66, 0, 4) Sector 4205ff00109441 ┆B A 1 2.2.1.8 Watchdog Firmware Functions ....... 43 2.2.1.8.1 Watchdog Line Communication ... 43 2.2.1.8.┆
0x42500…42600 (66, 0, 5) Sector 4206ff00109441 ┆B A2 Switch Logic .................. 44 2.2.1.8.3 Switchover .................... 44 2.2.1.8.4 WDP Standard Firmware ......... 45 2.2.2 Functional Responsibilities ........... 45 2.2.2.1 Initialization, Close-Down, and ┆
0x42600…42700 (66, 0, 6) Sector 4207ff00109441 ┆B A Restart ........................... 45 2.2.2.1.1 Start-Up (Initialization and Restart) ...................... 46 2.2.2.1.1.1 Boot Load ................. 46 2.2.2.1.1.2 Start-Up of Active and ┆
0x42700…42800 (66, 0, 7) Sector 4108ff00109441 ┆A A Stand By PU ............... 49 2.2.2.1.1.3 Disk Start-Up Information . 54 2.2.2.1.2 Ordered Close-Down ............ 55 2.2.2.1.2.1 AC PU Ordered Close-Down .. 55 2.2.2.1.2.2 SB PU Ordered Close-Down .. 58 ┆
0x42800…42900 (66, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(66,0, 9), len=0xff, h3=41109441}, f00=»1094A «, f01=»CPS/SDS/004 «, f02=»vhn «, f03=»FH «, f04=»fra table of content «, f05=29-06-81 14:47, f06=» 8 «, f07=»17 «, f08=» 31364 «, f09=29-07-81 09:35, f10=» 1 «, f11=»38 «, f12=» 1638 «, f13=29-07-81 11:14, f14=29-07-81 12:32, f15=»0066A «, f16=» 75 «, f17=» 13 «, f18=»49 «, f19=» 1236 «, f20=» 41105 «, f21=» «, f22=»& «, f99=210010000110068610110480aaca15050000000000000137035e01df}
0x42900…42a00 (66, 0, 9) Sector 420a4b00109441 ┆B K A B B B A A " ! ! DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: OpOpOp┆
0x42a00…42b00 (66, 0, 10) Sector 420b9300109441 ┆B A 1 CPS/SDS/004 FH/810801 SYSTEM STATUS AND CONTROL CAMPS -:!<~ B%-!/=6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x42b00…42c00 (66, 0, 11) Sector 420cff00109441 ┆B A 1 TABLE OF CONTENTS 1 1 GENERAL ..................┆
0x42c00…42d00 (66, 0, 12) Sector 420dff00109441 ┆B A..................... 15 1.1 PURPOSE AND SCOPE ......................... 15 1.2 APPLICABLE DOCUMENTS AND PROJECT REFERENCES ................................ 16 1.2.1 Applicable Documents .................. 16 1.2.2 Projec┆
0x42d00…42e00 (66, 0, 13) Sector 420eff00109441 ┆B At References .................... 16 1.3 TERMS AND ABBREVIATIONS ................... 17 1.3.1 Terms ................................. 17 1.3.2 Abbreviations ......................... 27 2 SUMMARY OF REQUIREMENTS ..............┆
0x42e00…42f00 (66, 0, 14) Sector 420fff00109441 ┆B A......... 28 2.1 PACKAGE DESCRIPTION ....................... 28 2.1.1 Block Diagram ......................... 29 2.2 PACKAGE FUNCTIONS ......................... 31 2.2.1 Main Functions ........................ 31 2.2.1.┆
0x42f00…43000 (66, 0, 15) Sector 4200ff00109441 ┆B A1 Checkpoint Transmission ........... 33 2.2.1.2 Checkpoint Reception .............. 33 2.2.1.3 On-Line Diagnostics ............... 34 2.2.1.4 Line Monitoring and Control ....... 34 2.2.1.5 Reception of Technical Error ┆
0x43000…43100 (67, 0, 0) Sector 43016700107641 ┆C g vAg to the checkpoint record type and an acknowledgement is sent to the active PU via the TDX bus. ~ B 3: = R 3*$<MMY *%<MMY !\<6 C 3M, !\<6 : =~ B 5: = R$3C/4!e=6 !f=6 !g=6 !h=6 Ml+M;) RE3C#4: 2i=:g=~ JV3C/4!"<6 #6 MB&! =6 !,<6 :]=2'< AMD MB&!,<6 ! ┆
0x43100…43200 (67, 0, 1) Sector 4302ff00107641 ┆C vA 1 1 FCT NO. TITLE ┆
0x43200…43300 (67, 0, 2) Sector 4303ff00107641 ┆C vA DESCRIBED IN SECTION 1 Overview 2.2.1 2 Check point transm. 2.2.1.1 4.1.1.1 3 Checkpoint reception 2.2.1.2 4.1.1.2 4 Online diagnostics 2.2.1.3 4.1.1.3 5 Li┆
0x43300…43400 (67, 0, 3) Sector 4304ff00107641 ┆C vAne M&C 2.2.1.4 4.1.1.4 6 Technical error processing 2.2.1.5 4.1.1.5 7 Operator commands 2.2.1.6 4.1.1.6 8 Offline PU operation 2.2.1.7 4.1.1.7 9 WDP FW 2.2.1.8 4.1.1.8 10 Bootload 2.2.2.1.1.1 11 Start active 2.2.2.1.1.2 4.1.┆
0x43400…43500 (67, 0, 4) Sector 4305ff00107641 ┆C vA1.6.3.1 12 Common start active 4.1.1.6.3.1 13 Start standby 2.2.2.1.1.2 4.1.1.6.3.3 14 Common start standby 4.1.1.6.3.3 15 Recovery 2.2.2.2 16 Close active 2.2.2.1.2.1 4.1.1.6.3.2 17 Close standby 2.2.2.1.2.2 18 Validity checks┆
0x43500…43600 (67, 0, 5) Sector 4306ff00107641 ┆C vA 2.2.2.4 19 Data collection 2.2.2.5 20 Own error handling 2.2.2.3 21 Peripheral recon- figuration 4.1.1.5 22 Common peripheral reconfiguration 4.1.1.5 23 Common line M&C 4.1.1.4.2 24 Common SSC functions 4.1.1.9.1 ┆
0x43600…43700 (67, 0, 6) Sector 43077700107641 ┆C w vA Figure 4.1.1-1 SSC Function to Section Table 5 41 27623 24 07 81 14 45 00 2 24 07 81 14 47 24 07 81 15 00 0066A 50 9 46 456 33185 @ f *J 7 & _┆
0x43700…43800 (67, 0, 7) Sector 2a08ff00107641 ┆* vA 1 4.1.1.3 On-Line Diagnostics The functions covered by on-line diagnostic are defined in section 2.2.1.3. 4.1.1.4 Line Monitoring and Control The line M&C functions are depicte┆
0x43800…43900 (67, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(67,0, 9), len=0xff, h3=41107641}, f00=»1076A «, f01=»System Status and Control «, f02=»sdv «, f03=»FH «, f04=»SDS/004 4-4.1.3.3 «, f05=23-06-81 10:30, f06=» 5 «, f07=»41 «, f08=» 27623 «, f09=24-07-81 14:45, f10=» «, f11=»00 «, f12=» 2 «, f13=24-07-81 14:47, f14=24-07-81 15:00, f15=»0066A «, f16=» 50 «, f17=» 9 «, f18=»46 «, f19=» 456 «, f20=» 33185 «, f21=» «, f22=» @ «, f99=990010000110066610110480aaca15050000000000000037039b00df}
0x43900…43a00 (67, 0, 9) Sector 430a3200107641 ┆C 2 vA C C C C * * * * DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatte┆
0x43a00…43b00 (67, 0, 10) Sector 430b9200107641 ┆C vA 1 CPS/SDS/004 FH/810801 SYSTEM STATUS AND CONTROL CAMPS *-:!<~ B%-!/=6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x43b00…43c00 (67, 0, 11) Sector 430cff00107641 ┆C vA 1 4 PACKAGE DESIGN 4.1 Package Overview 4.1.1 Functional Specification Sections 4.1.1.1 to 4.1.1.9 describes the functions derived in section 2.2.1 and 2.2.2 to a level of d┆
0x43c00…43d00 (67, 0, 12) Sector 430dff00107641 ┆C vAetail, which enables an allocation of the functions to process or coroutine software structures. Section 4.1.1.9 describes requirements derived from the functional responsibilities defined in section 2.2.2. The sections, in which SSC functions (┆
0x43d00…43e00 (67, 0, 13) Sector 430eff00107641 ┆C vAidentified by a number) are described, are defined in figure 4.1.1-1. 4.1.1.1 Checkpoint Transmission SSC receives checkpoint records from MMS, LOG and TIMER - MON and transfers the checkpoints records to the standby PU via the TDX-bus. Havi┆
0x43e00…43f00 (67, 0, 14) Sector 430fff00107641 ┆C vAng transmitted a record, an acknowledgement from the SB PU is awaited and a reply is sent to the caller. The SSC does not await acknowledgement before transmitting a new checkpoint (CP) record. However, only a limited number of outstanding acknow┆
0x43f00…44000 (67, 0, 15) Sector 4300ff00107641 ┆C vAledgements are allowed. 4.1.1.2 Checkpoint Reception SSC receives checkpoint records from the active PU. The checkpoint records are received via the TDX bus from the active PU. Having received a checkpoint record, a table is updated accordin┆
0x44000…44100 (68, 0, 0) Sector 44018400110041 ┆D A 1 Fig. 4.1.3.5-1 Watchdog Software Structure Overview 6 C 3M, !\<6 : =~ B 5: = R$3C/4!e=6 !f=6 !g=6 !h=6 Ml+M;) RE3C#4: 2i=:g=~ JV3C/4!"<6 #6 MB&! =6 !,<6 :]=2'< AMD MB&!,<6 ! ┆
0x44100…44200 (68, 0, 1) Sector 4402ff00110041 ┆D A 1 4.1.3.5.1 Input to the WDP from a PU The PU-IN driver recognizes three types of PU input: - VDU data - LP data - WDP data and sends the data to three associated queues: - ┆
0x44200…44300 (68, 0, 2) Sector 4403ff00110041 ┆D AVDU queue - LP queue - PU queue VDU data are analyzed in the VDU-HANDLER and LP-HANDLER process respectively and printed by the corresponding VDU and LP drivers. The LP-HANDLER synchronizes LP output. The WDP data in the PUQ contain keep alive┆
0x44300…44400 (68, 0, 3) Sector 4404ff00110041 ┆D A messages and direct WDP commands. The keep alive messages are handled in the PU-HANDLER, whereas WDP commands are executed in the SYS M&C process. The non-arrival of a keep alive message is signalled to the SYS M&C process by the PU-HANDLER. 4.1┆
0x44400…44500 (68, 0, 4) Sector 4405ff00110041 ┆D A.3.5.2 Input to the WDP from a VDU VDU input is directed to the VDU queue at the VDU-HANDLER by a VDU-IN driver. Three types of VDU input are handled: - offline PU commands - direct WDP commands - online PU commands. The VDU-HANDLER sends on┆
0x44500…44600 (68, 0, 5) Sector 4406a100110041 ┆D ! Aline and offline PU data to a PU-OUT driver. Direct WDP commands are executed in the SYS M&C process. Offline commands are copied at the record WDP-LP. - non-line processes are started/closed via separate request queues and a single reply queue. ┆
0x44600…44700 (68, 0, 6) Sector 4407ff00110041 ┆D A 1 4.1.3.5.3 CCB Scanning The CCB driver periodically scans the CAMPS crates. Exceptions are reported to the SYS M&C process, which determines further actions, e.g. an active PU erro┆
0x44700…44800 (68, 0, 7) Sector 2a00ff00110041 ┆* Ar is handled by disabling the AC PU and by commanding the SB PU to become active. Peripheral device exceptions are reported to the active PU. 4.1.3.5.4 Buffer Handling The application processes communicate via queue semaphores containing buff┆
0x44800…44900 (68, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(68,0, 9), len=0xff, h3=41110041}, f00=»1100A «, f01=»CPS/SDS/004 «, f02=»tdh «, f03=»fh «, f04=»fra 4.1.3.4 «, f05=30-06-81 12:26, f06=» 1 «, f07=»11 «, f08=» 6578 «, f09=23-07-81 09:37, f10=» «, f11=»12 «, f12=» 126 «, f13=23-07-81 10:39, f14=24-07-81 15:01, f15=»0066A «, f16=» 59 «, f17=» 11 «, f18=»46 «, f19=» 504 «, f20=» 34872 «, f21=» «, f22=» P «, f99=050010000110066610110480aaca1505000000000000003703a500df}
0x44900…44a00 (68, 0, 9) Sector 440a3b00110041 ┆D ; A D D D D D D D * * * ) ) ) ) ) ) ) ) ) ) ( ( ( ( ( ' ' ' ' ' & & & & & % % % % % $ $ $ $ # # # # # # " " " DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: ┆
0x44a00…44b00 (68, 0, 10) Sector 440b9200110041 ┆D A 1 CPS/SDS/004 FH/810801 SYSTEM STATUS AND CONTROL CAMPS *-:!<~ B%-!/=6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x44b00…44c00 (68, 0, 11) Sector 440cff00110041 ┆D A 1 4.1.3.4 OLD Data Flow and Control Logic Figure 4.1.3.4-1 overleaf defines online diagnostics data flow and control logic. OLD receives operational commands from COPSY in the OLDQ.┆
0x44c00…44d00 (68, 0, 12) Sector 440d7f00110041 ┆D A Also, supervisor and periodic request are entered in the OLDQ. OLD replies to operational and supervisor requests. 2#<! <6 M)(I:g=~ J /Mj'! "(=~ R*/!/=6jM (*(=~ R;/!/=6nM (*(=~ RM/!/=6iM (*(=~ R`/!/=6WM (*(=~ Rt/!/=6lM (*(=~ R ┆
0x44d00…44e00 (68, 0, 13) Sector 440e7100110041 ┆D q A 1 Fig. 4.1.3.4-1 OLD Block Diagram <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<┆
0x44e00…44f00 (68, 0, 14) Sector 440fff00110041 ┆D A 1 4.1.3.5 WDP Data Flow and Control Logic Figure 4.1.3.5-1 overleaf illustrates the WDP data flow and control logic. The WDP standard software drivers are shown outside the box, w┆
0x44f00…45000 (68, 0, 15) Sector 4400b600110041 ┆D 6 Ahereas the four application software processes are shown within the box. The following sections handle input to the WDP from: - a PU - a VDU - the CCB scanning driver. <2> I E*#<& "< DM L<M% :#<F 2#<> I:g= Ro2M/2 Rl2> IC13!?=4~~ B|2> I:A=!┆
0x45000…45100 (69, 0, 0) Sector 00000000000000 ┆ ┆
[…0x7f…]
