OctetView
0x00000…00100 (0, 0, 0) Sector 00394130303339 ┆ 9A0039A ┆
0x00100…00200 (0, 0, 1) Sector 00000000000000 ┆ ┆
0x00200…00300 (0, 0, 2) Sector ff00fcfffffff8 ┆ | x | ` ┆
0x00300…00306 (0, 0, 3) WangDocument {d00=0x05, d01=0x91, d02=0x41, ptr=(61,0, 8), d05=0x00}
0x00306…0030c WangDocument {d00=0x05, d01=0x92, d02=0x41, ptr=(61,0, 0), d05=0x00}
0x0030c…00312 WangDocument {d00=0x05, d01=0x93, d02=0x41, ptr=(63,0, 0), d05=0x00}
0x00312…00318 WangDocument {d00=0x05, d01=0x94, d02=0x41, ptr=(67,0, 8), d05=0x00}
0x00318…0031e WangDocument {d00=0x05, d01=0x96, d02=0x41, ptr=(44,0, 8), d05=0x00}
0x0031e…00324 WangDocument {d00=0x05, d01=0x97, d02=0x41, ptr=(67,0, 0), d05=0x00}
0x00324…00340 05 97 41 48 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ AH ┆
0x00340…00360 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ ┆
[…0x4…]
0x003e0…00400 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 24 ┆ $┆
0x00400…00500 (0, 0, 4) Sector 00000000000000 ┆ ┆
0x00500…00600 (0, 0, 5) Sector 00394130303339 ┆ 9A0039A ┆
0x00600…00700 (0, 0, 6) Sector 421c402600415b ┆B @& A[' X% %( PO P ; A<' C f x f V WD O 8 :z6 ] 0597A f e < {C < { ; 9 ` f IC b bD ? K 9 : 8 t wwy 0594A0597A0601A0602A0603 '!z5 q9'8 ┆
0x00700…00800 (0, 0, 7) Sector 00000000000000 ┆ ┆
0x00800…00900 (0, 0, 8) Sector aaaaaaaaaaaaaa ┆****************************************************************************************************************************************************************************************************************************************************************┆
[…0x7…]
0x01000…01100 (1, 0, 0) WangDocumentBody
[…0x5…]
0x01600…01700 (1, 0, 6) Sector 0107ff00059441 ┆ A If messages received by a CAMPS has the precedence FLASH and format line 4 of the message does not contain an inhibit receipt flag (ZGC) a service message as specified in section 3.2.1.6.4 shall be transmitted to the originating station. Format an┆
0x01700…01800 (1, 0, 7) Sector 00004700059441 ┆ G Ad content of FLASH receipt message is as specified in 3.2.1.6.4. ained in the different message types. 3.2.2.3 Message Distribution a) Processing and distribution subsequent to ACP127 analysis depend on the message type. b) Overleaf is presen┆
0x01800…01900 (1, 0, 8) WangDocumentBody
[…0x1c…]
0x03500…03600 (3, 0, 5) Sector 00005c00059241 ┆ \ A 1 figure 3.1-7 ............... REA, REB 3) Operator at TP2 .................. BBB e) Terminal Position 3 1) Terminal Designator .............. INT 2) Ass. SCD's ......┆
0x03600…03700 (3, 0, 6) Sector 03075a00059241 ┆ Z A 1 figure 3.1-6 oing external channel designator . CHO g) Incoming external channel designator . CHI h) The formats A, B, G1, G2, C1, D, E1 are used in the example. The first li┆
0x03700…03800 (3, 0, 7) Sector 00005c00059241 ┆ \ A 1 figure 3.1-7 Z AUG 0 1 2 4 where: 241811Z AUG: date time group 0 1 2 4 station serial number, which is unique The fact that the me┆
0x03800…03900 (3, 0, 8) WangDocumentBody
0x03900…03a00 (3, 0, 9) Sector 00004c00059641 ┆ L A 1 230/ICD/0001) 3.2.4.6 Engineering Functions Engineering functions are hardware and software control functions. 3.2.4.6.1 Engineering Functions Implementation a) Engineer┆
0x03a00…03b00 (3, 0, 10) Sector 030bff00059641 ┆ A 1 3.2.4.6.2 Engineering Functions Detailed Definition a) The detailed definition of single engineering functions depends on actual hardware and software, however, main functions a┆
0x03b00…03c00 (3, 0, 11) Sector 030cff00059641 ┆ As described below shall be covered and guidelines be followed. b) Supervisor engineering command control may only be used for control of on-line equipment.(Refer 3.2.4.1.1.13). c) Engineering functions shall exist to switch between hardware unit┆
0x03c00…03d00 (3, 0, 12) Sector 030dff00059641 ┆ As whenever dualization is used to obtain required availability. d) Engineering functions shall exist to control external lines as required by line interface equipment. Examples are line speed, code, start/stop bits control. e) Engineering funct┆
0x03d00…03e00 (3, 0, 13) Sector 030eff00059641 ┆ Aion shall exist to conduct online and offline tests by software or other means as needed to meet availability requirement. f) Engineering function shall exist to control load of software from online and offline media to facilitate fast restart in ┆
0x03e00…03f00 (3, 0, 14) Sector 030fff00059641 ┆ Afailure cases and load of new software transported to site as required for initialization and restart (see 3.2.8). 3.2.4.6.3 H/W Configuration Status Display As a basis for execution of engineering functions the following status information sha┆
0x03f00…04000 (3, 0, 15) Sector 0200ff00059641 ┆ All be displayed at VDUs and/or display-panels: - switching status of redundant equipment on crate-level (refer to 3.2.4.5.2.c) - status of line interface equipment with regard to parameters controllable via engineering functions (refer to 3.2.4.┆
0x04000…04100 (4, 0, 0) WangDocumentBody
[…0xed…]
0x12e00…12f00 (18, 0, 14) Sector 00006a00059341 ┆ j At table. The TO RI of format line 2 shall be the one specified in the appropriate channel table. t 24,00 hours to 001/0001 or reset only by wrap around (i.e. 001 after 999 and 0001 after 9999). The supervisor shall also be able to update security┆
0x12f00…13000 (18, 0, 15) Sector 12000d00059341 ┆ Aer. l contain all PLA's in format lines 7,8, and 9 of format ACP 127, however, PLA's reached via other channels (other routing indicators) and local HQ PLAs shall for each separate transmission be indicated by "ZEN/PLA" in format lines 7 and 8 of┆
0x13000…13100 (19, 0, 0) WangDocumentBody
[…0xa2…]
0x1d300…1d400 (29, 0, 3) Sector 1d04ff00059441 ┆ A 1 i) If the releasing officer releases the message, then it will be converted from E1 to ACP127 format and transmitted. j) The release notification will be queued to the releasing ┆
0x1d400…1d500 (29, 0, 4) Sector 1d05ff00059441 ┆ Aofficer and will not be sent to ACCIS. k) If the specified SCD is unknown, or leads to a terminal without release capability, then the message will be forwarded to the MDCO. l) The message will be deleted after presentation to the MDCO. The MDCO┆
0x1d500…1d600 (29, 0, 5) Sector 1d06ff00059441 ┆ A may print the message. 3.2.2.5.3 Comments/VDU Displays from SCARS/ACCIS a) If an incoming comment/VDU Display contains an unknown SCD or an unknown display name, then the comment/VDU Display will be sent to the MDCO, who can print the item. Th┆
0x1d600…1d700 (29, 0, 6) Sector 1d07a200059441 ┆ " Ae item will be deleted after presentation for the MDCO, who may report the event to SCARS/ACCIS by a comment. b) If the VDU Display contains a valid name,ng of Data Message Data messages are detected by a special handling designator in FL4 (ACP ┆
0x1d700…1d800 (29, 0, 7) Sector 00007600059441 ┆ v A then the Display database will be updated, and the VDU Display will be queued for the specified SCD, if any. essages will be treated as garbled if they contain non-printable characters. The non-printable characters will be displayed as the sign┆
0x1d800…1d900 (29, 0, 8) WangDocumentBody
[…0xef…]
0x2c800…2c900 (44, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(44,0, 9), len=0xff, h3=41059641}, f00=»0596A «, f01=»CPS/210/SYS/001 «, f02=»vhn «, f03=»gj «, f04=»3.2.4 ISSUE 3 «, f05=02-02-81 13:13, f06=» 1 «, f07=»36 «, f08=» 4298 «, f09=21-12-83 09:50, f10=» «, f11=»11 «, f12=» 34 «, f13=21-12-83 10:03, f14=25-07-85 13:20, f15=»0039A «, f16=» 44 «, f17=» 9 «, f18=»57 «, f19=» 656 «, f20=» 12771 «, f21=» «, f22=» 0 «, f99=930010000110052710110280aaca1505000000000000003803d100df}
0x2c900…2ca00 (44, 0, 9) WangDocumentBody
[…0x106…]
0x3d000…3d100 (61, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(61,0, 1), len=0xff, h3=41059241}, f00=»0592A «, f01=»CPS/210/SYS/0001 IS. 3 «, f02=»vhn «, f03=»gj «, f04=»Tab. of Cont. - 3.1 «, f05=02-02-81 13:06, f06=» 1 «, f07=»19 «, f08=» 2546 «, f09=03-06-83 11:11, f10=» «, f11=»04 «, f12=» 129 «, f13=02-06-83 13:17, f14=25-07-85 11:28, f15=»0039A «, f16=» 46 «, f17=» 4 «, f18=»13 «, f19=» 756 «, f20=» 4841 «, f21=» «, f22=» «, f99=100080000110056610110290aaca1505000000000000003803ed00df}
0x3d100…3d200 (61, 0, 1) WangDocumentBody
[…0x6…]
0x3d800…3d900 (61, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(61,0, 9), len=0xff, h3=41059141}, f00=»0591A «, f01=»CPS/210/SYS/0001 «, f02=»vhn «, f03=»gj «, f04=»Revision record «, f05=02-02-81 13:03, f06=» 2 «, f07=»34 «, f08=» 3858 «, f09=14-06-84 10:28, f10=» «, f11=»00 «, f12=» 18 «, f13=15-03-84 09:21, f14=09-04-85 10:57, f15=»0039A «, f16=» 18 «, f17=» 9 «, f18=»15 «, f19=» 232 «, f20=» 17884 «, f21=» «, f22=» «, f99=810000000110052710110280aaca15050000000000000038034e00df}
0x3d900…3da00 (61, 0, 9) WangDocumentBody
[…0x16…]
0x3f000…3f100 (63, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(63,0, 1), len=0xff, h3=41059341}, f00=»0593A «, f01=»CPS/210/SYS/001 «, f02=»vhn «, f03=»gj «, f04=»3.2 - 3.2.1 is. 3 «, f05=02-02-81 13:08, f06=» 1 «, f07=»51 «, f08=» 4887 «, f09=14-03-84 13:31, f10=» «, f11=»00 «, f12=» 8 «, f13=14-03-84 13:32, f14=25-07-85 11:25, f15=»0039A «, f16=» 49 «, f17=» 11 «, f18=»13 «, f19=» 684 «, f20=» 17620 «, f21=» «, f22=» «, f99=420010000110052710110280aaca1505000000000000003803de00df}
0x3f100…3f200 (63, 0, 1) WangDocumentBody
[…0x3e…]
0x43000…43100 (67, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(67,0, 1), len=0xff, h3=41059741}, f00=»0597A «, f01=»CPS/210/SYS/0001 «, f02=»vhn «, f03=»gj «, f04=»3.2.5 - 3.2.8 IS. 3 «, f05=02-02-81 13:15, f06=» 3 «, f07=»49 «, f08=» 9157 «, f09=21-12-83 10:25, f10=» «, f11=»00 «, f12=» 18 «, f13=21-12-83 10:26, f14=25-07-85 14:06, f15=»0039A «, f16=» 46 «, f17=» 11 «, f18=»10 «, f19=» 648 «, f20=» 24941 «, f21=» «, f22=» «, f99=310010000110052710110280aaca1505000000000000003803d000df}
0x43100…43200 (67, 0, 1) WangDocumentBody
[…0x6…]
0x43800…43900 (67, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(67,0, 9), len=0xff, h3=41059441}, f00=»0594A «, f01=»CPS/210/SYS/0001 «, f02=»vhn «, f03=»gj «, f04=»3.2.2 ISSUE 3 «, f05=02-02-81 13:09, f06=» «, f07=»13 «, f08=» 876 «, f09=25-05-83 10:59, f10=» «, f11=»18 «, f12=» 66 «, f13=09-05-83 15:57, f14=25-07-85 14:05, f15=»0039A «, f16=» 26 «, f17=» 4 «, f18=»56 «, f19=» 284 «, f20=» 11494 «, f21=» «, f22=» «, f99=220010000110058610110290aaca15050000000000000038036300df}
0x43900…43a00 (67, 0, 9) WangDocumentBody
[…0x6…]
0x44000…44100 (68, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(68,0, 1), len=0xff, h3=41059441}, f00=»0594A «, f01=»CPS/210/SYS/0001 «, f02=»vhn «, f03=»gj «, f04=»3.2.2 ISSUE 3 «, f05=02-02-81 13:09, f06=» «, f07=»13 «, f08=» 876 «, f09=25-05-83 10:59, f10=» «, f11=»18 «, f12=» 66 «, f13=09-05-83 15:57, f14=23-12-83 09:53, f15=»0039A «, f16=» 26 «, f17=» 4 «, f18=»56 «, f19=» 284 «, f20=» 11494 «, f21=» «, f22=» «, f99=220010000110058610110290aaca15050000000000000038036300df}
0x44100…44200 (68, 0, 1) Sector 44021a00059441 ┆D A D D C B B B B A A A @ @ @ @ @ @ @ @ @ DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG Oprettet / / : : S : S S ┆
0x44200…44300 (68, 0, 2) Sector 4403a000059441 ┆D A 1 CPS/210/SYS/0001 831219 CAMPS SYSTEM REQUIREMENTS ISSUE 3.14 CAMPS WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x44300…44400 (68, 0, 3) Sector 4404ff00059441 ┆D A 1 1 TABLE OF CONTENTS Section 3.2.2 3.2.2 Incoming Message...................... 95 3.2.2.1 Message ┆
0x44400…44500 (68, 0, 4) Sector 4405ff00059441 ┆D AReception Procedures...... 95 3.2.2.2 ACP127 Analysis................... 95 3.2.2.2.1 Format Line Detection ........ 99 3.2.2.2.2 Selection of Parameter........ 100 3.2.2.2.3 Determination of Message Type 100 3.2┆
0x44500…44600 (68, 0, 5) Sector 4406ff00059441 ┆D A.2.3 Message Distribution ............. 100 3.2.2.3.1 Automatic Distribution ....... 106 3.2.2.3.2 Distribution of Service Messages ..................... 108 3.2.2.3.3 Handling of Codress/Plaindress Encr┆
0x44600…44700 (68, 0, 6) Sector 4407ff00059441 ┆D Aypted Messages ..................... 108 3.2.2.3.4 Handling of Data Messages .... 108 3.2.2.3.5 Handling of CLEAR Messages ... 108 3.2.2.4 Procedures Related to Receipt of FLASH messages...........┆
0x44700…44800 (68, 0, 7) Sector 4308ff00059441 ┆C A......... 108 3.2.2.5 Handling of Messages from SCARS/ ACCIS ............................ 108 3.2.2.5.1 Messages from SCARS .......... 108 3.2.2.5.2 Messages from ACCIS .......... 108 3.2.2.5.3 Comments/VDU Di┆
0x44800…44900 (68, 0, 8) Sector 4409ff00059741 ┆D Assa- ges ...................... 184 3.2.5.6.1.3 Log Records Relating to Incoming SCARS II Messa- ges ...................... 184 3.2.5.6.2 Log Record┆
0x44900…44a00 (68, 0, 9) Sector 440aff00059741 ┆D As Relating to outgo- ing Messages ................. 185 3.2.5.6.2.1 NICS-TARE/TRC/Point to Point connection Messages ................. 185 3.2.5.6.2.2 L┆
0x44a00…44b00 (68, 0, 10) Sector 440bc100059741 ┆D A Aog Records Relating to Outgoing ACE CCIS Messages 185 3.2.5.6.2.3 Log Records Relating to outgoing SCARS II Messages 185 ┆
0x44b00…44c00 (68, 0, 11) Sector 440cff00059741 ┆D A 1 3.2.5.6.3 Channel Discontinuity......... 186 3.2.5.6.3.1 NICS-TARE/TRC/Point to Point connection Channel Discon┆
0x44c00…44d00 (68, 0, 12) Sector 440dff00059741 ┆D Atinuity............. 186 3.2.5.6.3.2 Log Records Relating to ACE CCIS Channels Discontinuity ............ 186 3.2.5.6.3.3 Log Records Relating to SCA┆
0x44d00…44e00 (68, 0, 13) Sector 440eff00059741 ┆D ARS II Channel Discon- tinuity .................. 186 3.2.5.6.4 Terminal Procedures........... 187 3.2.5.6.5 Message Distribution Control.. 190 3.2.5.6.6 Message Service............... 190 3.2.5┆
0x44e00…44f00 (68, 0, 14) Sector 440f3000059741 ┆D 0 A.6.7 Supervisory Commands.......... 190 gj 3.2.5 - 3.2.8 IS. 3 02 02 81 13 15 3 49 9157 19 06 81 15 59 01 14 15 06 81 09 56 19 06 81 16 02 0039A 41 5 17 600 10359 " f *J 8 A _┆
0x44f00…45000 (68, 0, 15) Sector 4400ff00059741 ┆D A 1 3.2.5 Logging The system shall maintain a log for all transactions, including those terminated before completion. 3.2.5.1 Categories of transactions to be logged A log shal┆
0x45000…45100 (69, 0, 0) Sector 4501ff00059141 ┆E AMI) 3.1.1.3.4 Editorial MOM4(1,15) 3.1.1.3.6 MOA(MMI, 3.1.2 RETR) MOA(MMI) 3.2.1.1.1a) MOM4(10) 3.2.1.1.2c) MOA(MMI) 3.2.1.2 MOM4(1,15) 3.2.1.24 MOA(MMI) 3.2.1.4.1 MOM4(12) 3.2.1.5.1 3) MOM4(1,15) 3.2.2.3.1 3.2.3 Table of Contents MOM4 ┆
0x45100…45200 (69, 0, 1) Sector 4502ff00059141 ┆E A3.2.3 MOM4(1.1,1.4) 3.2.3a) MOM4(1,15) 3.2.3.1 b) MOM4(1) 3.2.3.1c) Editorial MOM4(1.1,1.4) 3.2.3.1d) MOM4(1.5, 3.2.3.1f) 1.6,15) MOM4(1.5, 3.2.3.1g) 1.6,15) MOM4(1) 3.2.3.2 MOM4(1,15), 3.2.3.2.2 MOA(MMI) MOA(MMI) 3.2.3.3a) MOA(MMI) 3.2┆
0x45200…45300 (69, 0, 2) Sector 4503c700059141 ┆E G A.3.3b) MOA(MMI) 3.2.3.3c) MOM4(2) MOA(MMI) 3.2.3.3d) MOA(MMI) 3.2.3.3e) MOA(MMI) 3.2.3.3f) MOM4(15) 3.2.3.4 MOA(MMI) 3.2.3.4b) MOA(MMI) 3.2.3.4c) MOM4(5) 3.2.3.4d) MOA(MMI) 3.2.3.4f) ┆
0x45300…45400 (69, 0, 3) Sector 4504ff00059141 ┆E A 1 MOM4(1,15) 3.2.3.4g) MOM4(8) 3.2.3.4g2) MOM4(14) 3.2.3.4h) MOA(MMI) 3.2.3.5 MOM4(2) MOM4(2) 3.2.3.5b) MOM4(2) 3.2.3.5c) MOA(MMI) TABLES: 3.2.3.5-1 3.2.3.5-2 3.2.3.5-3 ┆
0x45400…45500 (69, 0, 4) Sector 4505ff00059141 ┆E A MOA(MMI), 3.2.3.5 Definition of Transitions MOM4(2) MOM4(5) 3.2.3.6 MOM4(1.2) 3.2.3.7 MOA(MMI) 3.2.3.7.1 MOA(MMI) 3.2.3.7.2 MOA(MMI) 3.2.3.7.3 MOM4(1.2) 3.2.3.7.4 3.2.4 Table of Contents MOA(MMI) Fig. 3.2.4-1 MOM4(4,6,7) MOM4(1.4) Fig. ┆
0x45500…45600 (69, 0, 5) Sector 4506ff00059141 ┆E A3.2.4-2 MOA(MMI) MOA(MMI) 3.2.4 MOA(MMI) 3.2.4.1 MOA(MMI) 3.2.4.1.1.1 MOM4(6) 3.2.4.1.1.2b) MOM4(7) 3.2.4.1.1.2c) MOA(MMI) 3.2.4.1.1.2d) MOM4(13) 3.2.4.1.1.3a) MOA(MMI) MOA(MMI) 3.2.4.1.1.3b) MOA(MMI) 3.2.4.1.1.4 3.2.4.1.1.4 u, v z MOM4┆
0x45600…45700 (69, 0, 6) Sector 4507cf00059141 ┆E O A(1.1, moved to section 1.4) 3.2.4.1.1.7 MOA(MMI) 3.2.4.1.1.5 MOM4(15), 3.2.4.1.1.7 MOA(MMI) MOM4(16), MOA 3.2.4.1.1.15 (RETR, MMI) MOA(MMI) 3.2.4.1.2.2 MOA(MMI) 3.2.4.2 MOA(MMI) 3.2.4.2-1 0 136 10004 f *J 8 . _┆
0x45700…45800 (69, 0, 7) Sector 2d00ff00059141 ┆- A 1 MOA(MMI) 3.2.4.2.2 MOA(MMI) 3.2.4.3.1 MOA(MMI) 3.2.4.3.2 MOM4(4) 3.2.4.4.5 MOM4(5) New 3.2.4.5 3.2.4.5.3 Editorial MOM4(5) 3.2.5.4b) MOA(MMI) 3.2.5.4c) MOA(MMI) 3.2.5.5b) ┆
0x45800…45900 (69, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(69,0, 9), len=0xff, h3=41059141}, f00=»0591A «, f01=»CPS/210/SYS/0001 «, f02=»vhn/sdv «, f03=»gj «, f04=»Revision record «, f05=02-02-81 13:03, f06=» 2 «, f07=»34 «, f08=» 3858 «, f09=13-08-81 11:41, f10=» 1 «, f11=»01 «, f12=» 135 «, f13=13-08-81 12:43, f14=17-08-81 13:02, f15=»0039A «, f16=» 10 «, f17=» 5 «, f18=»10 «, f19=» 136 «, f20=» 10004 «, f21=» «, f22=» «, f99=020020000110056610110490aaca15050000000000000038032d00df}
0x45900…45a00 (69, 0, 9) Sector 450a0a00059141 ┆E A E E E E E - - ! ! DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG Oprettet / / : : ┆
0x45a00…45b00 (69, 0, 10) Sector 450ba500059141 ┆E % A 1 CPS/210/SYS/0001 810804 CAMPS SYSTEM REQUIREMENTS ISSUE 3.3 CAMPS /=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x45b00…45c00 (69, 0, 11) Sector 450cff00059141 ┆E A 1 R E V I S I O N R E C O R D The Authorization of change record shall be used as follows: 1) MOA (Memoran┆
0x45c00…45d00 (69, 0, 12) Sector 450dff00059141 ┆E Adum of Agreement, Resulting from SHAPE and Christian Rovsing A/S Meeting held at SHAPE during the period of 19th and 20th November 1980) is used when referencing to: MOA Doc. No. CPS/ECP/001 (MMI) Doc. No. CPS/ECP/002 (RETR) Progress Minute┆
0x45d00…45e00 (69, 0, 13) Sector 450eff00059141 ┆E As of Meeting No. 4 2) MOM4 refers to Minutes of Meeting No. 4. 3) MOA(MMI) refers to the Man/Machine Interface as stated in MOA and agreed with SHAPE during the working period at Christian Rovsing A/S. 4) MOA(RETR) refers to Retrieval as state┆
0x45e00…45f00 (69, 0, 14) Sector 450fa000059141 ┆E Ad in MOA and agreed with SHAPE during the working period at CR. Pages affected refer to the sections or paragraphs in issue 2 which have been changed. Z=q#p!"<6 !&<6 ! "$<!#<6 ! <6 {M)(sC I! <6 ! "(= <q#p!"<6 !#<6 ! "$<!&<6$`i6 {M)(sM &M7 ┆
0x45f00…46000 (69, 0, 15) Sector 4500ff00059141 ┆E A 1 MOA(MMI) 2.2 MOA(MMI) 3.1c) Editorial MOM4(1) 3.1.1.1h) MOM4(1) Fig. 3.1-1 MOM4(1.2) 3.1.1.2a) MOM4(15) 3.1.1.2.b) MOA(MMI) 3.1.1.3.1 MOM4(15) MOM4(4,6,7) Fig. 3.1-4 MOA(M┆
0x46000…46100 (70, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(70,0, 1), len=0xff, h3=41059241}, f00=»0592A «, f01=»CPS/210/SYS/0001 IS. 3 «, f02=»vhn/sdv «, f03=»gj «, f04=»Tab. of Cont. - 3.1 «, f05=02-02-81 13:06, f06=» 1 «, f07=»19 «, f08=» 2546 «, f09=14-08-81 13:04, f10=» «, f11=»02 «, f12=» 57 «, f13=13-08-81 14:40, f14=17-08-81 13:02, f15=»0039A «, f16=» 46 «, f17=» 3 «, f18=»50 «, f19=» 768 «, f20=» 3943 «, f21=» «, f22=» @ «, f99=340010000110056610110480aaca1505000000000000003803ee00df}
0x46100…46200 (70, 0, 1) Sector 46022e00059241 ┆F . A F F Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG Oprettet / / : : : ┆
0x46200…46300 (70, 0, 2) Sector 46039f00059241 ┆F A 1 CPS/210/SYS/0001 810804 CAMPS SYSTEM REQUIREMENTS ISSUE 3.3 CAMPS 6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x46300…46400 (70, 0, 3) Sector 4604ff00059241 ┆F A 1 1 TABLE OF CONTENTS 1 SCOPE ........................................ 13-13 2 APPLICABLE DOCUMENTS ........┆
0x46400…46500 (70, 0, 4) Sector 4605ff00059241 ┆F A................. 14-17 2.1 APPLICABLE DOCUMENTS ..................... 14 2.2 REFERENCE DOCUMENTS ...................... 15 2.3 TERMS .................................... 15 3 REQUIREMENTS ................................. 17-┆
0x46500…46600 (70, 0, 5) Sector 4606ff00059241 ┆F A352 3.1 SYSTEM DEFINITION ........................ 20 3.1.1 General Description .................... 20 3.1.1.1 Connectivity of a CAMPS Site ....... 20 3.1.1.2 Logical Addressing Scheme .......... 26 3.1.1.3 Functional Cap┆
0x46600…46700 (70, 0, 6) Sector 4607ff00059241 ┆F Aabilities ............ 32 3.1.2 Message Flow ......................... 42 3.2 FUNCTIONAL REQUIREMENTS .................. 52 3.2.1 Outgoing Messages .................... 55 3.2.1.1 Message Types and their Flow ┆
0x46700…46800 (70, 0, 7) Sector 1d08ff00059241 ┆ A through the CAMPS System ......... 55 3.2.1.2 Operational Messages ............ 60 3.2.1.3 Service Message .................. 74 3.2.1.4 Entry of Complete Messages ....... 76 3.2.1.5 ACP 127 Conversion ............┆
0x46800…46900 (70, 0, 8) Sector 4609ff00059341 ┆F At contains control information of the message exchange between the CAMPS sites. Two types shall exist: - Service messages - Abbreviated service messages c) Data Messages. The message text differs from the other message types in the follow┆
0x46900…46a00 (70, 0, 9) Sector 460abd00059341 ┆F = Aing way: the message text comprises a datastream which may or may not include End of Line Function. Data Messages shall not be paged by CAMPS. Maximum size is 12,000 characters. ages with Plain Text .... 78 3.2.1.5.2 Conversion of Serv┆
0x46a00…46b00 (70, 0, 10) Sector 460bff00059341 ┆F A 1 3.2.1.1.3 Flow of Outgoing Messages a) The formal presentation of a message depends on the stage of processing. Messages distributed to or received from external circuits are i┆
0x46b00…46c00 (70, 0, 11) Sector 460cff00059341 ┆F An ACP 127 format. Messages inside a CAMPS system are in internal formats. b) Messages for transmission may at the originating CAMPS be entered either as complete messages, i.e. in ACP 127 format without format line 1, in OCR input format, or by m┆
0x46c00…46d00 (70, 0, 12) Sector 460dd000059341 ┆F P Aeans of interactive procedures. c) The processing of outgoing messages and how messages are being entered depends on the message type. This dependency is shown in fig. 3.2.1.1-1 and fig. 3.2.1.1-2. termina┆
0x46d00…46e00 (70, 0, 13) Sector 460e6100059341 ┆F a A 1 Fig. 3.2.1.1-1 es a) This section describes the processing of outgoing messages by CAMPS from the initial preparation through all the stages until transmission. b) The s┆
0x46e00…46f00 (70, 0, 14) Sector 460f6100059341 ┆F a A 1 Fig.3.2.1.1-2 ages which the CAMPS system shall be able to process and gives for each type an outline of their functional flow through the system. d) Section 3.2.1.2 desc┆
0x46f00…47000 (70, 0, 15) Sector 1c00ff00059341 ┆ A 1 3.2.1.2 Operational Messages a) The system shall support the functions for outgoing messages listed below: 1) Message preparation 2) Message release 3) Local distributi┆
0x47000…47100 (71, 0, 0) Sector 4701ff00059341 ┆G A by the supervisor. f) Section 3.2.1.4 describes how complete messages are entered into the system and the involved system processing. g) Section 3.2.1.5 describes for each message type the ACP127 conversion. All outgoing messages shall be conve┆
0x47100…47200 (71, 0, 1) Sector 4702ff00059341 ┆G Arted into the relevant ACP127 format before transmission. h) The processing of converted messages related to transmission is described in section 3.2.1.6. 3.2.1.1 Message Types and their Flow through the CAMPS System Messages are constituted ┆
0x47200…47300 (71, 0, 2) Sector 4703ff00059341 ┆G Aof two parts, the message header and the message text. 3.2.1.1.1 General Structure of Messages a) Message Header. The message header contains the information which is necessary for the automatic processing of the message from its origination to┆
0x47300…47400 (71, 0, 3) Sector 4704bd00059341 ┆G = A its destination(s). After creation of the message header each entry shall be validated with respect to syntax. Validation of the semantic shall be performed to a certain extent too. Header ............... 63 3.2.1.2.1.1.2 ┆
0x47400…47500 (71, 0, 4) Sector 4705ff00059341 ┆G A 1 b) Message Text. The message text (excluding introductory text as specified in ICD/0003) contains no information necessary for the automatic processing of the message by CAMPS. ┆
0x47500…47600 (71, 0, 5) Sector 4706ff00059341 ┆G A Message text is treated as though it is in free format by CAMPS. The only validation being performed (no validation for data messages and messages with encrypted text) is that text lines do not exceed 69 characters. 3.2.1.1.2 Message Types Th┆
0x47600…47700 (71, 0, 6) Sector 4707ff00059341 ┆G Ae following three message types shall be recognized by the CAMPS system: - Operational Messages - Service Messages - Data Messages a) Operational Messages. This type is the one which may be originated or received by common users of the C┆
0x47700…47800 (71, 0, 7) Sector 4608ff00059341 ┆F AAMPS. Two types shall exist: - Operational messages with plain text - Operational messages with encrypted text b) Service Messages. Service messages are generated/handled either automatically by CAMPS or by the supervisor. The message tex┆
0x47800…47900 (71, 0, 8) Sector 47095a00059341 ┆G Z A from OCR .............. 77 3.2.1.4.2 Entry from PTR .............. 77 ┆
0x47900…47a00 (71, 0, 9) Sector 470aff00059341 ┆G A 1 3.2.1.5 ACP127 Conversion ............... 77 3.2.1.5.1 Conversion of Operational Messages with Plain Text .... 78 3.2.1.5.2 Conversion of Serv┆
0x47a00…47b00 (71, 0, 10) Sector 470bff00059341 ┆G Aice Messages .................... 89 3.2.1.5.3 Conversion of Complete Messages .................... 89 3.2.1.6 Transmission .................... 90 3.2.1.6.1 Channel Selectio┆
0x47b00…47c00 (71, 0, 11) Sector 470cff00059341 ┆G An and Identification .............. 90 3.2.1.6.2 Procedures Related to Premature Termination of a Transmission ................ 92 3.2.1.6.3 Procedures Related┆
0x47c00…47d00 (71, 0, 12) Sector 470df800059341 ┆G x A to the ZEN Prosigns .................... 92 3.2.1.6.4 Procedures Related to FLASH Receipt ............... 93 1 termina┆
0x47d00…47e00 (71, 0, 13) Sector 470eff00059341 ┆G A 1 3.2.1 Outgoing Messages a) This section describes the processing of outgoing messages by CAMPS from the initial preparation through all the stages until transmission. b) The s┆
0x47e00…47f00 (71, 0, 14) Sector 470fff00059341 ┆G Aection is organized as follows: c) Section 3.2.1.1 identifies the different types of messages which the CAMPS system shall be able to process and gives for each type an outline of their functional flow through the system. d) Section 3.2.1.2 desc┆
0x47f00…48000 (71, 0, 15) Sector 4700ff00059341 ┆G Aribes how operational messages are prepared by users, procedures associated with their release and outlines the local distribution required for outgoing operational messages. e) Section 3.2.1.3 deals with service messages and how they are prepared┆
0x48000…48100 (72, 0, 0) Sector 4801aa00059341 ┆H * Ae and retrieval requirements of incoming and outgoing messages. Section 3.2.8 defines the requirements related to initialization, error detection, and recovery. =6 !g=6 !h=6 Ml+M;) RE3C#4: 2i=:g=~ JV3C/4!"<6 #6 MB&! =6 !,<6 :]=2'< AMD MB&!,<6 ! ┆
0x48100…48200 (72, 0, 1) Sector 4802ff00059341 ┆H A 1 1 TABLE OF CONTENTS Section 3.2.1 3.2.1 Outgoing Messages ................... 55 3.2.1.1 Message Types an┆
0x48200…48300 (72, 0, 2) Sector 4803ff00059341 ┆H Ad their Flow through the CAMPS System ........ 55 3.2.1.1.1 General Structure of Messages 55 3.2.1.1.2 Message Types ................ 56 3.2.1.1.3 Flow of Outgoing Messages .... 57 3.2.1.2 Operat┆
0x48300…48400 (72, 0, 3) Sector 4804ff00059341 ┆H Aional Messages ............ 60 3.2.1.2.1 Message Preparation ......... 62 3.2.1.2.1.1 New Message Preparation .. 62 3.2.1.2.1.1.1 Preparation of Message Header ............... 63 3.2.1.2.1.1.2 ┆
0x48400…48500 (72, 0, 4) Sector 4805ff00059341 ┆H A Preparation of Message Text ................. 66 3.2.1.2.1.1.3 Correction of Header and/or Text .......... 67 3.2.1.2.1.1.4 Append/Coordinate/Re- lease/Defer .......... 67 ┆
0x48500…48600 (72, 0, 5) Sector 4806ff00059341 ┆H A 3.2.1.2.1.2 Message Editing ......... 68 3.2.1.2.1.3 Append Message ........... 69 3.2.1.2.1.4 Message Coordination .... 69 3.2.1.2.2 Comments .................... 70 3.2.1.2.2.1 New Comment Preparation ┆
0x48600…48700 (72, 0, 6) Sector 4807ff00059341 ┆H A.. 70 3.2.1.2.2.2 Comment Editing ......... 71 3.2.1.2.2.3 Comment Presentation .... 72 3.2.1.2.3 Message Release ............. 72 3.2.1.2.4 Local Distribution .......... 73 3.2.1.3 Service Messages ..┆
0x48700…48800 (72, 0, 7) Sector 4708ff00059341 ┆G A.............. 74 3.2.1.3.1 Preparation ................. 74 3.2.1.3.1.1 Initial Preparation ..... 75 3.2.1.3.1.2 Editing ................. 75 3.2.1.4 Entry of Complete Messages ...... 76 3.2.1.4.1 Entry┆
0x48800…48900 (72, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(72,0, 9), len=0xff, h3=41059741}, f00=»0597A «, f01=»CPS/230/SYS/0001 «, f02=»vhn «, f03=»gj «, f04=»3.2.5 - 3.2.8 IS. 3 «, f05=02-02-81 13:15, f06=» 3 «, f07=»49 «, f08=» 9157 «, f09=19-06-81 15:59, f10=» «, f11=»01 «, f12=» 14 «, f13=15-06-81 09:56, f14=19-06-81 16:02, f15=»0039A «, f16=» 41 «, f17=» 5 «, f18=»17 «, f19=» 600 «, f20=» 10359 «, f21=» «, f22=» «, f99=220010000110056610110480aaca1505000000000000003803c100df}
0x48900…48a00 (72, 0, 9) Sector 480a2900059741 ┆H ) A H H D D D C C C B B B B A A @ @ @ @ ? ? ? ? > > > = = = = = = < < < < ; ; ; : - - # DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG Oprett┆
0x48a00…48b00 (72, 0, 10) Sector 480b9d00059741 ┆H A 1 CPS/210/SYS/0001 810323 CAMPS SYSTEM REQUIREMENTS ISSUE 3 CAMPS /=6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x48b00…48c00 (72, 0, 11) Sector 480cff00059741 ┆H A 1 1 TABLE OF CONTENTS Section 3.2.5 3.2.5 Logging .............................. 180 3.2.5.1 Categor┆
0x48c00…48d00 (72, 0, 12) Sector 480dff00059741 ┆H Aies of Transactions to be Logged ........................... 180 3.2.5.2 Logging Events ................... 180 3.2.5.3 Storage of Log Records............ 181 3.2.5.4 Print of Log Records.............. 181 ┆
0x48d00…48e00 (72, 0, 13) Sector 480eff00059741 ┆H A3.2.5.5 Tracing (Computer Analysis) of Log Information .................. 181 3.2.5.6 Definition of Specific Log Records 182 3.2.5.6.1 Log Records Relating to In- coming Messages.............┆
0x48e00…48f00 (72, 0, 14) Sector 480fff00059741 ┆H A.. 182 3.2.5.6.1.1 Log Records Related to incoming NICS-TARE/TRC/ Point to Point connec- tion Messages ............ 182 3.5.2.6.1.1.1 Valid Messages┆
0x48f00…49000 (72, 0, 15) Sector 4408ff00059741 ┆D A ....... 182 3.4.2.6.1.1.2 Invalid Messages ..... 183 3.5.2.6.1.1.3 Automatically Deleted Messages ............. 184 3.2.5.6.1.2 Log Records Relating to Incoming ACE CCIS Me┆
0x49000…49100 (73, 0, 0) Sector 4901ff00059441 ┆I Aer" shall be reset to the one received plus one. 4) If a message is received without a channel serial number the "expected channel serial number" shall be allocated to the message by the system. The expected number for the next message shall be e┆
0x49100…49200 (73, 0, 1) Sector 4902ff00059441 ┆I Aqual to the allocated number plus one. The occurence shall be signalled to the supervisor as for incorrect serial number. The message shall be presented to the MSO who can decide to have the message sent for normal distribution. On being sent for ┆
0x49200…49300 (73, 0, 2) Sector 49033100059441 ┆I 1 Adistribution, the message shall be stored. CPS/210/SYS/0001 810804 CAMPS SYSTEM REQUIREMENTS ISSUE 3.3 CAMPS 6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x49300…49400 (73, 0, 3) Sector 49045c00059441 ┆I \ A 1 figur. ? TABLE OF CONTENTS Section 3.2.2 3.2.2 Incoming Message...................... 95 3.2.2.1 Message ┆
0x49400…49500 (73, 0, 4) Sector 4905ff00059441 ┆I A 1 3.2.2.2 ACP127 Analysis a) The format tolerances of CPS/ICD/0003 shall apply to messages in ACP 127 format. b) Certain departures from the ACP 127 format are allowed. c) Una┆
0x49500…49600 (73, 0, 5) Sector 4906ff00059441 ┆I Acceptable departures such as - no start of transmission function (VZCZC) shall result in no acceptance of input. d) The following set of conditions shall lead to immediate insertion of termination sequence and queuing for message service ┆
0x49600…49700 (73, 0, 6) Sector 4907ff00059441 ┆I A1) Consecutive start of message (SOM) sequences. 2) Oversized messages. 3) Halted messages. 4) Consecutive identical characters e) In the following cases the message shall be queued for message service position. 1) Lines are too long. ┆
0x49700…49800 (73, 0, 7) Sector 1f08ff00059441 ┆ A 2) Non-standard end-of-transmission sequence. 3) If one or more of the format lines 1, 2, 3, 4, 5, 7, 8, 11, 12a, 13, 15, and 16 are garbled. 4) If a mandatory line is not present, except for format line 12b to 12d. 5) If a garble is fou┆
0x49800…49900 (73, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(73,0, 9), len=0xff, h3=41059341}, f00=»0593A «, f01=»2PS/210/SYS/001 «, f02=»vhn/sdv «, f03=»gj «, f04=»3.2 - 3.2.1 is. 3 «, f05=02-02-81 13:08, f06=» 1 «, f07=»51 «, f08=» 4887 «, f09=14-08-81 13:05, f10=» «, f11=»04 «, f12=» 54 «, f13=14-08-81 13:30, f14=17-08-81 13:02, f15=»0039A «, f16=» 45 «, f17=» 7 «, f18=»03 «, f19=» 680 «, f20=» 11670 «, f21=» «, f22=» «, f99=520010000110056610110480aaca1505000000000000003803d300df}
0x49900…49a00 (73, 0, 9) Sector 490a2d00059341 ┆I - A I I H G G G F F F F VERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG Oprettet / / / / ┆
0x49a00…49b00 (73, 0, 10) Sector 490b9f00059341 ┆I A 1 CPS/210/SYS/0001 810804 CAMPS SYSTEM REQUIREMENTS ISSUE 3.3 CAMPS 6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x49b00…49c00 (73, 0, 11) Sector 490cff00059341 ┆I A 1 3.2 FUNCTIONAL REQUIREMENTS The following section will exhaustively specify the functional requirements to CAMPS. Section 3.2.1 and 3.2.2 defines all functional capabilities rel┆
0x49c00…49d00 (73, 0, 12) Sector 490dff00059341 ┆I Aated to processing of outgoing and incoming messages respectively. The sequence in which the functional capabilities are presented are as they appear during message processing. Section 3.2.3 specifies all functional capabilities related to termina┆
0x49d00…49e00 (73, 0, 13) Sector 490eff00059341 ┆I Als and the associated equipment. The section has been structured in such a way, that it presents the functional capabilities seen from a user's point of view. Section 3.2.4 defines all required capabilities for supervisory control commands, messag┆
0x49e00…49f00 (73, 0, 14) Sector 490fff00059341 ┆I Ae service, message distribution control, system status and alarm, engineering functions and software maintenance. The Section is not presented from an operational point of view, but more in terms of functional capabilities. Section 3.2.5 specifie┆
0x49f00…4a000 (73, 0, 15) Sector 4800ff00059341 ┆H As the events for which log entries shall be made and the information associated with the log entries. Section 3.2.6 defines the required statistical reports related to channel traffic and transactions at terminals. Section 3.2.7 specifies storag┆
0x4a000…4a100 (74, 0, 0) Sector 4a01ff00059441 ┆J A 1 3.2.2 Incoming Messages a) CAMPS shall support the following major functions for incoming message handling. 1) Message Reception Procedures (Ref. section 3.2.2.1) 2) ACP 12┆
0x4a100…4a200 (74, 0, 1) Sector 4a02ff00059441 ┆J A7 Analysis (Ref. section 3.2.2.2) 3) Message Distribution (Ref. section 3.2.2.3) b) Other major functions shall act as support functions to the message handling functions. These functions are 1) Storage and Retrieval Functions. 2) Logging a┆
0x4a200…4a300 (74, 0, 2) Sector 4a03ff00059441 ┆J And Reporting Functions. 3) Terminal Handling Functions. c) Figure 3.2.2-1 presents the functional relationships for incoming message handling functions. d) Message types applicable to incoming message handling are those specified in section 3┆
0x4a300…4a400 (74, 0, 3) Sector 4a04ff00059441 ┆J A.2.1.1. 3.2.2.1 Message Reception Procedures a) Each message received shall be uniquely identified by a channel designator and a channel serial number. This information shall be contained in "Format Line 1" of ACP127 formatted messages. b) Up┆
0x4a400…4a500 (74, 0, 4) Sector 4a05ff00059441 ┆J Aon reception of a message CAMPS shall check the channel serial number in "Format Line 1" to determine whether it is in sequence. 1) In all cases, if the number is not present or not equal to the number of the latest message incremented by one a ┆
0x4a500…4a600 (74, 0, 5) Sector 4a06ff00059441 ┆J Awarning shall be printed out at the supervisors position both indicating the expected number and the received incorrect number. A log entry shall be made (refer to section 3.2.5.6.1.1.1 b) 2) If the number is less than or equal to the number of ┆
0x4a600…4a700 (74, 0, 6) Sector 4a07cb00059441 ┆J K Athe last received message, the message shall be presented to the MSO. He can decide to have the message sent for normal distribution. On being sent for distribution, the message shall be stored. 3 07 240 6939 f *J 8 R _┆
0x4a700…4a800 (74, 0, 7) Sector 4900ff00059441 ┆I A 1 3) If the number is greater than the number of the last received message incremented by one the message shall be handled as a valid message and the "expected channel serial numb┆
0x4a800…4a900 (74, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(74,0, 9), len=0xff, h3=41059441}, f00=»0594A «, f01=»CPS/210/SYS/0001 «, f02=»vhn/sdv «, f03=»gj «, f04=»3.2.2 ISSUE 3 «, f05=02-02-81 13:09, f06=» «, f07=»13 «, f08=» 876 «, f09=14-08-81 13:07, f10=» «, f11=»01 «, f12=» 15 «, f13=13-08-81 15:03, f14=17-08-81 13:03, f15=»0039A «, f16=» 20 «, f17=» 3 «, f18=»07 «, f19=» 240 «, f20=» 6939 «, f21=» «, f22=» «, f99=020010000110056610110480aaca15050000000000000038034e00df}
0x4a900…4aa00 (74, 0, 9) Sector 4a0a1400059441 ┆J A J J J J I I DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG Oprettet / / : : S : S S : ┆
0x4aa00…4ab00 (74, 0, 10) Sector 4a0b9f00059441 ┆J A 1 CPS/210/SYS/0001 810804 CAMPS SYSTEM REQUIREMENTS ISSUE 3.3 CAMPS 6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x4ab00…4ac00 (74, 0, 11) Sector 4a0cff00059441 ┆J A 1 1 TABLE OF CONTENTS Section 3.2.2 3.2.2 Incoming Message...................... 95 3.2.2.1 Message ┆
0x4ac00…4ad00 (74, 0, 12) Sector 4a0dff00059441 ┆J AReception Procedures...... 95 3.2.2.2 ACP127 Analysis................... 95 3.2.2.2.1 Format Line Detection ........ 99 3.2.2.2.2 Selection of Parameter........ 100 3.2.2.2.3 Determination of Message Type 100 3.2┆
0x4ad00…4ae00 (74, 0, 13) Sector 4a0eff00059441 ┆J A.2.3 Message Distribution ............. 100 3.2.2.3.1 Automatic Distribution ....... 106 3.2.2.3.2 Distribution of Service Messages ..................... 108 3.2.2.3.3 Handling of Codress/Plaindress Encr┆
0x4ae00…4af00 (74, 0, 14) Sector 4a0fff00059441 ┆J Aypted Messages ..................... 108 3.2.2.3.4 Handling of Data Messages .... 108 3.2.2.3.5 Handling of CLEAR Messages ... 108 3.2.2.4 Procedures Related to Receipt of FLASH messages...........┆
0x4af00…4b000 (74, 0, 15) Sector 4a001600059441 ┆J A......... 108 (! "(=~~ J*2M2/C<2:^=~ B<2:b= R<2M/,:g=~ BG2M")M2&! "(=~~ BW2I! <6 M /M?.I*:="8=IM2&MP'Mc2! m"2< [MI !?=6 : #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=!┆
0x4b000…4b100 (75, 0, 0) Sector aaaaaaaaaaaaaa ┆****************************************************************************************************************************************************************************************************************************************************************┆
[…0x1f…]
