OctetView
0x00000…00100 (0, 0, 0) Sector 05144130353134 ┆ A0514A ┆
0x00100…00200 (0, 0, 1) Sector 00000000000000 ┆ ┆
0x00200…00300 (0, 0, 2) Sector ff00f0ffffe0ff ┆ p ` | ` x x p ┆
0x00300…00306 (0, 0, 3) WangDocument {d00=0x51, d01=0x97, d02=0x41, ptr=(69,0, 0), d05=0x00}
0x00306…0030c WangDocument {d00=0x51, d01=0x98, d02=0x41, ptr=(19,0, 8), d05=0x00}
0x0030c…00312 WangDocument {d00=0x51, d01=0x99, d02=0x41, ptr=(38,0, 8), d05=0x00}
0x00312…00318 WangDocument {d00=0x52, d01=0x00, d02=0x41, ptr=(45,0, 0), d05=0x00}
0x00318…0031e WangDocument {d00=0x52, d01=0x01, d02=0x41, ptr=(58,0, 0), d05=0x00}
0x0031e…00324 WangDocument {d00=0x52, d01=0x02, d02=0x41, ptr=(61,0, 8), d05=0x00}
0x00324…0032a WangDocument {d00=0x52, d01=0x03, d02=0x41, ptr=(65,0, 0), d05=0x00}
0x0032a…00330 WangDocument {d00=0x52, d01=0x84, d02=0x41, ptr=(68,0, 0), d05=0x00}
0x00330…00340 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ ┆
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 30 ┆ 0┆
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 ; R A C g x g V W O : 5203A g < {C < { ; 3 ;g ┆
0x00700…00800 (0, 0, 7) Sector 00000000000000 ┆ ┆
[…0x8…]
0x01000…01100 (1, 0, 0) WangDocumentBody
[…0x3…]
0x01400…01500 (1, 0, 4) Sector 00000000000000 ┆ ┆
[…0x3…]
0x01800…01900 (1, 0, 8) WangDocumentBody
[…0x12…]
0x02b00…02c00 (2, 0, 11) Sector 020c8900519941 ┆ Q A 1 HIPO Overview use of tables (read from RIA and RDF). The detailed conversion rules are described in ref. 1, section 3.1.1.3.2.4.┆
0x02c00…02d00 (2, 0, 12) Sector 020d8900519941 ┆ Q A 1 HIPO Overview The message is of type: specat. - The message is highly classified. - The Nato ANO or the Nato plain text addres┆
0x02d00…02e00 (2, 0, 13) Sector 020e7600519941 ┆ v Q A 1 HIPO Overview his type of message means that ACP127 message is enclosed in a SMF envelope. The addresses in the "SMF" formatted message is hereby Routi┆
0x02e00…02f00 (2, 0, 14) Sector 00008900519941 ┆ Q A 1 HIPO Overview classification in the "SMF" message is extracted from the ACP127 format line 2 and 4. Errors. such as illegal addr┆
0x02f00…03000 (2, 0, 15) Sector 0200ff00519941 ┆ Q Ac. 4.2.4.3.2 Files The message service subsystem uses the following files: - IMF Inbound Message File. Contains messages received from collocated NODE/MEDE. - AMF ACP127 Message File. Contains messages to/from NICS-TARE. - RIA Address ┆
0x03000…03100 (3, 0, 0) WangDocumentBody
[…0x1d…]
0x04e00…04f00 (4, 0, 14) Sector 0000a500519841 ┆ % Q Ar filled with the Ckeckpoint File. The MTCB-Monitor is initialized. The Coroutine Monitor is initialized. Finally the Starting Module is stopped. SCC, from the local MEDE, and from the neighbour NSS. The messages from the SCC are: -┆
0x04f00…05000 (4, 0, 15) Sector 00000000000000 ┆ ┆
0x05000…05100 (5, 0, 0) WangDocumentBody
[…0xe7…]
0x13800…13900 (19, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(19,0, 9), len=0xff, h3=41519841}, f00=»5198A «, f01=»FIX/1000/PSP/038 «, f02=»aml «, f03=»JL «, f04=»Sec. 4.1.2 «, f05=25-07-84 10:23, f06=» 4 «, f07=»01 «, f08=» 13424 «, f09=10-07-85 09:41, f10=» «, f11=»00 «, f12=» 2 «, f13=07-08-84 12:59, f14=10-07-85 10:43, f15=»0514A «, f16=» 53 «, f17=» 5 «, f18=»24 «, f19=» 824 «, f20=» 14062 «, f21=» «, f22=» «, f99=020010000110052710110080aaca1505000000000000013803f600df}
0x13900…13a00 (19, 0, 9) WangDocumentBody
[…0x12e…]
0x26800…26900 (38, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(38,0, 9), len=0xff, h3=41519941}, f00=»5199A «, f01=»FIX/1000/PSP/038 sec 4.2 «, f02=»bna «, f03=»MLA «, f04=»System Spec. 4.2 «, f05=25-07-84 10:23, f06=» 11 «, f07=»40 «, f08=» 64689 «, f09=05-07-85 10:25, f10=» «, f11=»08 «, f12=» 182 «, f13=05-07-85 10:33, f14=10-07-85 10:44, f15=»0514A «, f16=» 98 «, f17=» 13 «, f18=»14 «, f19=» 980 «, f20=» 67294 «, f21=» «, f22=» 0 «, f99=630010000110052710110180aaca15050000000000000138034b01df}
0x26900…26a00 (38, 0, 9) WangDocumentBody
[…0x66…]
0x2d000…2d100 (45, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(45,0, 1), len=0xff, h3=41520041}, f00=»5200A «, f01=»FIX/1000/PSP/038 4.2.5 «, f02=»bna «, f03=»MLA «, f04=»System Spec. 4.2.5. «, f05=25-07-84 10:23, f06=» 4 «, f07=»01 «, f08=» 23429 «, f09=26-06-85 15:23, f10=» «, f11=»04 «, f12=» 131 «, f13=27-06-85 09:18, f14=10-07-85 10:45, f15=»0514A «, f16=» 45 «, f17=» 4 «, f18=»30 «, f19=» 336 «, f20=» 23858 «, f21=» «, f22=» «, f99=020010000110052710110280aaca15050000000000000138037c00df}
0x2d100…2d200 (45, 0, 1) WangDocumentBody
[…0x9…]
0x2db00…2dc00 (45, 0, 11) Sector 2d0cff00520041 ┆- R Aen the FIKS network and the NICS-TARE network. The point to point connection between FIKS and NICS-TARE is a 600 baud synchronous full duplex channel. The link control protocol employed by this channel is the LITSYNC Error Detection and Connection┆
0x2dc00…2dd00 (45, 0, 12) Sector 2d0dff00520041 ┆- R A Protocol 1) (EDC), which ensures an error-free transmission across the link. Messages for transmission to the NICS-TARE network are enqueued in the NICS-TARE Transmission Queue (NT) by the MSS subsystem. Upon transmission, the message is dequeu┆
0x2dd00…2de00 (45, 0, 13) Sector 2d0eff00520041 ┆- R Aed from NT and an acknowledgement (ACK), which confirms a successfully transmission of this specific message, is returned to the MSS. Inbound messages received from the NICS-TARE network are enqueued in the ACP/SMF conversion queue (CQ1) by the NTS ┆
0x2de00…2df00 (45, 0, 14) Sector 2d0fff00520041 ┆- R Asubsystem for onward processing by the MSS. Control and supervision of the NTS is performed by the NSC subsystem. Unrecoverable errors (line loss) are reported to the NSC for display on the Supervisor Positions VDU. Channel control, i.e. setup, o┆
0x2df00…2e000 (45, 0, 15) Sector 2d00a300520041 ┆- # R Apen and close, are a subset of the supervisors interactive functions that monitor the NTS subsystem. 1) Ref. Doc. FIX/1163/SPC/0005, Issue 1, 800313. ┆
0x2e000…2e100 (46, 0, 0) WangDocumentBody
[…0xc…]
0x2ed00…2ee00 (46, 0, 13) Sector 2e0eff00520041 ┆. R A Outbound Message Processing 4.2.5.3.1.2 Inbound Message Processing 4.2.5.3.1.3 Channel Control .......... 4.2.5.3.2 EDC Submodule ................ 4.2.5.3.2.1 EDC Output Channel ....... 4.2.5.3.┆
0x2ee00…2ef00 (46, 0, 14) Sector 2e0fff00520041 ┆. R A2.2 EDC Input Channel ........ 4.2.5.3.3 LTU-Driver Submodule (DLTU) .. 4.2.5.3.3.1 DLTU Output Channel ...... 4.2.5.3.3.2 DLTU Input Channel ....... 4.2.5.3.4 Queues ....................... 4.2.┆
0x2ef00…2f000 (46, 0, 15) Sector 2e00ff00520041 ┆. R A5.3.5 Files ........................ 4.2.5.5 Subsystem Overview HIPO Diagram .. 4.2.6 Inter SCC Handshaking Subsystem (ISH) 4.2.6.1 Function ......................... 4.2.6.3 Design Overview .................. ┆
0x2f000…2f100 (47, 0, 0) WangDocumentBody
[…0x14…]
0x30500…30600 (48, 0, 5) Sector 3006ff00519741 ┆0 Q A 1 4.1.5.4 Visual Table of Contents Figure 4.1.5-4 gives an overview of the main modules which constitutes the MES. Other interactive terminal functions that are not related to mes┆
0x30600…30700 (48, 0, 6) Sector 3007fb00519741 ┆0 { Q Asage entry, such as log on/log off, are provided by the ITM. 4.1.5.5 Subsystem overview HIPO Diagram Figure 4.1.5-5 provides an overview of the functions that occur in support of the basic message entry processes. Although the functions a is ┆
0x30700…30800 (48, 0, 7) Sector 00006a00519741 ┆ j Q Are listed sequentially, their execution for unrelated terminals is designed to occur concurrently. rding to the message precedence, and is a reference to the related MTCB. - SRS input queue The queue is accessed for insertion when retrieval re┆
0x30800…30900 (48, 0, 8) WangDocumentBody
[…0x88…]
0x39100…39200 (57, 0, 1) Sector 39022e00519741 ┆9 . Q A 9 9 9 8 8 8 8 7 7 7 6 6 6 6 5 5 5 5 5 4 4 4 4 4 4 3 3 3 3 3 2 2 2 1 1 1 0 0 0 0 / / / / / / / DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer:┆
0x39200…39300 (57, 0, 2) Sector 3903ac00519741 ┆9 , Q A 1 5197A/bna FIX/1000/PSP/0038 MLA/840726 FIKS SYSTEM SPECIFICATION FK 7809 */=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x39300…39400 (57, 0, 3) Sector 3904ff00519741 ┆9 Q A 1 TABLE OF CONTENTS 1 4.1.5 Message Entry Subsys┆
0x39400…39500 (57, 0, 4) Sector 3905ff00519741 ┆9 Q Atem Overview ..... 4.1.5.1 Functions ........................ 4.1.5.2 Subsystem Block Diagram .......... 4.1.5.3 Design Overview .................. 4.1.5.3.1 Queues Accessed .............. 4.1.5.3.2 Dis┆
0x39500…39600 (57, 0, 5) Sector 39069000519741 ┆9 Q Ak File Access ............. 4.1.5.4 Visual Table of Contents ......... 4.1.5.5 Subsystem overview HIPO Diagram .. 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<┆
0x39600…39700 (57, 0, 6) Sector 3907ff00519741 ┆9 Q A 1 4.1.5 Message Entry Subsystem Overview 4.1.5.1 Functions The objective of the MES is to provide the interactive terminal user the service of common message facilities. Comm┆
0x39700…39800 (57, 0, 7) Sector 3808ff00519741 ┆8 Q Aon MES functions are: a. The preparation function supports the creation of a message and its storage on the Preparation Data Base (PDB). b. The coordination function supports the (logical) transmission of a message between the message preparer's┆
0x39800…39900 (57, 0, 8) WangDocumentBody
[…0x7…]
0x3a000…3a100 (58, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(58,0, 1), len=0xff, h3=41520141}, f00=»5201A «, f01=»FIX/1000/PSP/038 «, f02=»bna «, f03=»JL «, f04=»System Spec. 4.1.1.2 «, f05=25-07-84 10:23, f06=» 4 «, f07=»03 «, f08=» 17811 «, f09=27-08-84 10:57, f10=» «, f11=»05 «, f12=» 7 «, f13=27-08-84 10:44, f14=28-06-85 09:21, f15=»0514A «, f16=» 3 «, f17=» 4 «, f18=»11 «, f19=» 76 «, f20=» 17849 «, f21=» «, f22=» «, f99=300010000110052710110180aaca15050000000000000038031500df}
0x3a100…3a200 (58, 0, 1) WangDocumentBody
[…0x36…]
0x3d800…3d900 (61, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(61,0, 9), len=0xff, h3=41520241}, f00=»5202A «, f01=»FIX/1000/PSP/038 «, f02=»bna «, f03=»MLA «, f04=»System Spec. 4.1.1.3 «, f05=25-07-84 10:23, f06=» «, f07=»21 «, f08=» 147 «, f09=27-06-85 12:07, f10=» «, f11=»01 «, f12=» 19 «, f13=04-07-85 15:23, f14=04-07-85 15:26, f15=»0514A «, f16=» 7 «, f17=» «, f18=»59 «, f19=» 192 «, f20=» 1151 «, f21=» «, f22=» «, f99=600010000110052710110180aaca15050000000000000038033900df}
0x3d900…3da00 (61, 0, 9) WangDocumentBody
[…0x12…]
0x3ec00…3ed00 (62, 0, 12) Sector 00000000000000 ┆ ┆
[…0x3…]
0x3f000…3f100 (63, 0, 0) WangDocumentBody
[…0x1f…]
0x41000…41100 (65, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(65,0, 1), len=0xff, h3=41520341}, f00=»5203A «, f01=»FIX/1000/PSP/038 «, f02=»bna «, f03=»MLA «, f04=»SYSTEM SPEC. 4.3.3 «, f05=25-07-84 10:23, f06=» 2 «, f07=»42 «, f08=» 14541 «, f09=27-06-85 11:40, f10=» «, f11=»00 «, f12=» 8 «, f13=27-06-85 11:42, f14=10-07-85 10:50, f15=»0514A «, f16=» 23 «, f17=» 2 «, f18=»49 «, f19=» 212 «, f20=» 14598 «, f21=» «, f22=» «, f99=020010000110052710110180aaca15050000000000000138034b00df}
0x41100…41200 (65, 0, 1) WangDocumentBody
[…0x6…]
0x41800…41900 (65, 0, 8) Sector 4109bd00520341 ┆A = R A) Return to TCM Errors 5e, 15e, 25e Abnormal situations 55f, 65f, 75f 6e, 16e, 26e Issue error code 56f, 66f, 76f 8e, 18e, 28e Analyse result 58f, 68f, 78f extual data for storage on message preparation, edit and remarks f┆
0x41900…41a00 (65, 0, 9) Sector 410aaa00520341 ┆A * R A 1 Figure 4.3.3.2-1 ITM Subsystem, Block Diagram processes that were in execution at the time of a system malfunction. The services ┆
0x41a00…41b00 (65, 0, 10) Sector 410bff00520341 ┆A R A 1 4.3.3.3 Design Overview The ITM Subsystem executes with one process for the Process Start Module (PSM) and one interactive terminal process for each interactive terminal logged on┆
0x41b00…41c00 (65, 0, 11) Sector 410cff00520341 ┆A R A. (VDU and TP). An interactive terminal process executes the program containing the entire modules of Message Entry Subsystem (MES) and the Supervisor Function Subsystem (SFS) together with all the ITM modules except for the Process Start Module (┆
0x41c00…41d00 (65, 0, 12) Sector 410dff00520341 ┆A R Aillustrated in figure 4.3.3.3-1). The Message Entry Subsystem and the Supervisory Function Subsystem is implemented as procedures called by the Terminal Command Module. Terminal data shared between terminal processes and other processes (e.g. PS┆
0x41d00…41e00 (65, 0, 13) Sector 410ea600520341 ┆A & R AM, PIP) are placed in Terminal Control Blocks (TCB). The TCBs are located in Critical Region. See Figure 4.3.3.3-1 and 4.3.3.3-2 ITM software configuration. s the function: - Transfer data and control codes to the VDU terminals. ity claasifi ┆
0x41e00…41f00 (65, 0, 14) Sector 410fac00520341 ┆A , R A 1 Figure 4.3.3.3-1 ITM Subsystem, Design Overview s in the terminal process, when interactive procedures goes on. When a number wit┆
0x41f00…42000 (65, 0, 15) Sector 4100ac00520341 ┆A , R A 1 Figure 4.3.3.3-2 ITM Subsystem, Design Overview PSM Process Start Module TCM Terminal Command Module EM Error Module TIOM ┆
0x42000…42100 (66, 0, 0) Sector 42015900520341 ┆B Y R ATerminal I/O Module MES Message Entry Subsystem PIP Print Interface Process ┆
0x42100…42200 (66, 0, 1) Sector 4202ff00520341 ┆B R A 1 Block Diagram Description The first terminal logged-on could be one of the supervisor/supervisor assistants terminals (S/SA terminals) 1 - 4 Log-on sequence on S/SA terminal┆
0x42200…42300 (66, 0, 2) Sector 4203ff00520341 ┆B R A 5 PSM is informed 6 - 7 PIP is informed 8 - 9 Queue status line is displayed 10 Return to TCM When the message preparation operator (MPO) logs-on his terminal and calls an operational procedure. 51 - 51 Log-on sequence on MPO┆
0x42300…42400 (66, 0, 3) Sector 4204ff00520341 ┆B R A terminal 55 PSM is informed 56 - 57 PIP is informed 58 - 59 Queue stastus line is displayed (only if the terminal is a VDU) 60 Return to TCM 61 - 64 TCM receives the operator command 65 The appropriate MES/SFS procedure is cal┆
0x42400…42500 (66, 0, 4) Sector 4205c700520341 ┆B G R Aled 66 - 69 MES/SFS carries out the procedure 70 Return to TCM At any time the S/SA are allowed to block or unblock a terminal. In the following the block terminal command is chosen. cess Start Module (PSM) ... 4.3.3.3.2 Terminal┆
0x42500…42600 (66, 0, 5) Sector 4206ff00520341 ┆B R A 1 11 - 14 TCM receives the S/SA command "block terminal" 15 The appropriate SFS procedure is called 16 - 19 SFS is starting the procedure 17b PSM is informed 18b - 19b ┆
0x42600…42700 (66, 0, 6) Sector 4207ff00520341 ┆B R APIP is informed 20b - 22b The terminal process is ordered to terminate the current procedure. 23b - 24b Return to SFS 16 - 19 SFS is finishing the procedure 20 Return to TCM If not blocked by the S/SA, the MPO can log-off his terminal ┆
0x42700…42800 (66, 0, 7) Sector 4108ff00520341 ┆A R Aas follows (the S/SA log-off in the same way). 1 71 - 74 (21-24) TCM carries out the log-off procedure. 75 (25) PSM is informed 76 - 77 (26-27) PIP is informed 78 - (28┆
0x42800…42900 (66, 0, 8) Sector 4209ff00520341 ┆B R Aegardless of the specific application. These include procedures for the user log on and log off sequences; the entering of commands that initiate terminal processes; the entering of textual data for storage on message preparation, edit and remarks f┆
0x42900…42a00 (66, 0, 9) Sector 420aff00520341 ┆B R Ailes; the cancelling of any transaction procedure inexecution fdor a given terminal; and the recovery of input to message preparation files and restart of terminal processes that were in execution at the time of a system malfunction. The services ┆
0x42a00…42b00 (66, 0, 10) Sector 420bff00520341 ┆B R Aare provided by the following modules: - Process Start Module (PSM) which supports the functions: - Subsystem initialization - Terminal handling Blocking and unblocking of terminals Queue status line updating Interface betw┆
0x42b00…42c00 (66, 0, 11) Sector 420cf100520341 ┆B q R Aeen terminal processes and the Printer Interface Process (PIP). - Terminal Command Module (TCM) which supports the functions: - Get (and interprete) terminal command - Execute interactive procedures Log-on Log-off ssage Retrieva┆
0x42c00…42d00 (66, 0, 12) Sector 420dff00520341 ┆B R A 1 - Terminal I/O Module (TIOM) which supports the functions: - Create/dismantle channels - Transfer data - Control screen (VDU) - Wait operations - Send AMOS messag┆
0x42d00…42e00 (66, 0, 13) Sector 420ef200520341 ┆B r R Ae - Error Module (EM) which supports the functions: - Interactive error handling - Reporting of errors to SFS - VDU handler (VDUH) which supports the function: - Transfer data and control codes to the VDU terminals. ity claasifi ┆
0x42e00…42f00 (66, 0, 14) Sector 420fff00520341 ┆B R A 1 4.3.3.2 Subsystem Block Diagram Figure 4.3.3.2-1 illustrates the co-operation between the modules in the terminal process, when interactive procedures goes on. When a number wit┆
0x42f00…43000 (66, 0, 15) Sector 4200ff00520341 ┆B R Ah small letters (e.g. (1a)) it indicates that an exception may happen. Abbreviations: S/SA Supersivor/Supervisor Assistants MPO Message Preparation Operator PSM Process Start Module TCM Terminal Command Module EM Error Module TIOM ┆
0x43000…43100 (67, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(67,0, 1), len=0xff, h3=41520341}, f00=»5203A «, f01=»FIX/1000/PSP/038 «, f02=»bna «, f03=»MLA «, f04=»SYSTEM SPEC. 4.3.3 «, f05=25-07-84 10:23, f06=» 2 «, f07=»42 «, f08=» 14541 «, f09=27-06-85 11:40, f10=» «, f11=»00 «, f12=» 8 «, f13=27-06-85 11:42, f14=28-06-85 09:26, f15=»0514A «, f16=» 24 «, f17=» 2 «, f18=»49 «, f19=» 212 «, f20=» 14598 «, f21=» «, f22=» «, f99=020010000110052710110180aaca15050000000000000138034f00df}
0x43100…43200 (67, 0, 1) Sector 43021800520341 ┆C R A C C C B B B B A A A A A A @ @ @ @ ? ? ? > > > > > DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TI┆
0x43200…43300 (67, 0, 2) Sector 4303a500520341 ┆C % R A 1 5203A/bna FIX/1000/PSP/0038 MLA/850529 FIKS SYSTEM SPECIFICATION FK7809 /=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x43300…43400 (67, 0, 3) Sector 4304ff00520341 ┆C R A 1 TABLE OF CONTENTS 1 4.3.3 The Interactive Terminal ┆
0x43400…43500 (67, 0, 4) Sector 4305ff00520341 ┆C R AMonitor ..... 4.3.3.1 Function ......................... 4.3.3.2 Subsystem Block Diagram .......... 4.3.3.3 Design Overview .................. 4.3.3.3.1 Process Start Module (PSM) ... 4.3.3.3.2 Terminal┆
0x43500…43600 (67, 0, 5) Sector 4306ff00520341 ┆C R A Command Module (TCM) 4.3.3.3.3 Terminal I/O Module .......... 4.3.3.3.4 Error Module (EM) ............ 4.3.3.3.5 VDU Handler Module (VDUH) .... 4.3.3.3.6 Interactive Terminals ........ 4.3.3.3.7 Te┆
0x43600…43700 (67, 0, 6) Sector 43079100520341 ┆C R Arminal Operators ........... 4.3.3.4 Visual Table of Contents ......... 4.3.3.5 Subsystem Overview HIPO Diagrams . s! 9"c=! "(= Z=q#p!"<6 !&<6 ! "$<!#<6 ! <6 {M)(sC I! <6 ! "(= <q#p!"<6 !#<6 ! "$<!&<6$`i6 {M)(sM &M7 ┆
0x43700…43800 (67, 0, 7) Sector 4208ff00520341 ┆B R A 1 4.3.3 The Interactive Terminal Monitor 4.3.3.1 Function The ITM provides to terminal-oriented application processes a set of services that are common to interactive terminals r┆
0x43800…43900 (67, 0, 8) WangDocumentBody
[…0x7…]
0x44000…44100 (68, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(68,0, 1), len=0xff, h3=41528441}, f00=»5284A «, f01=»FIX/1000/PSP/0038,SYST.SP «, f02=»bna «, f03=»JL «, f04=»4.1.1.3.11.- 12. «, f05=27-08-84 10:51, f06=» «, f07=»35 «, f08=» 3995 «, f09=26-06-85 15:47, f10=» «, f11=»02 «, f12=» 22 «, f13=26-06-85 16:02, f14=28-06-85 09:26, f15=»0514A «, f16=» 3 «, f17=» «, f18=»37 «, f19=» 60 «, f20=» 4017 «, f21=» «, f22=» «, f99=020010000110052710110180aaca15050000000000000038031400df}
0x44100…44200 (68, 0, 1) WangDocumentBody
[…0x6…]
0x44800…44900 (68, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(68,0, 9), len=0xff, h3=41519941}, f00=»5199A «, f01=»FIX/1000/PSP/038 sec 4.2 «, f02=»bna «, f03=»MLA «, f04=»System Spec. 4.2 «, f05=25-07-84 10:23, f06=» 11 «, f07=»40 «, f08=» 64689 «, f09=04-07-85 15:37, f10=» «, f11=»16 «, f12=» 1186 «, f13=04-07-85 15:55, f14=04-07-85 15:58, f15=»0514A «, f16=»100 «, f17=» 12 «, f18=»54 «, f19=» 980 «, f20=» 66879 «, f21=» «, f22=» 0 «, f99=630010000110052710110180aaca15050000000000000138035a01df}
0x44900…44a00 (68, 0, 9) Sector 440a6400519941 ┆D d Q A D D / / / / ' & & & & & % % % % % % $ $ $ $ # # # # # # # " " " ! ! ! ! ! ! DOKUMENTOVERSIGT Dokument ┆
0x44a00…44b00 (68, 0, 10) Sector 440ba700519941 ┆D ' Q A 1 5199A/bna FIX/1000/PSP/0038 MLA/850529 FIKS SYSTEM SPECIFICATION FK 7809 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 440cff00519941 ┆D Q A 1 TABLE OF CONTENTS 1 4.2 SYSTEM CONTROL CENTE┆
0x44c00…44d00 (68, 0, 12) Sector 440dff00519941 ┆D Q AR (SCC) .............. 4.2.1 SCC System Overview (on-line SCC) .... 4.2.1.1 SCC Hardware Overview ............ 4.2.1.2 SCC Software Overview ............ 4.2.1.3 SCC External Interfaces .......... 4.2.1.3┆
0x44d00…44e00 (68, 0, 13) Sector 440eff00519941 ┆D Q A.1 SCC - Collocated N/M Interface 4.2.1.3.1.1 Hardware I/F ............. 4.2.1.3.1.2 Software I/F ............. 4.2.1.3.2 SCC - NICS-TARE Interface .... 4.2.1.4 Geographical Back-up ............. ┆
0x44e00…44f00 (68, 0, 14) Sector 440fff00519941 ┆D Q A4.2.1.4.1 Active SCC Functions ......... 4.2.1.4.2 Stand-by SCC Functions ....... 4.2.1.4.3 Controlled Switchover ........ 4.2.1.4.4 Emergency Switchover ......... 4.2.1.4.5 Start-up ..................... ┆
0x44f00…45000 (68, 0, 15) Sector 2f08ff00519941 ┆/ Q A 4.2.1.4.6 Narrative Message Service Control ...................... 4.2.1.5 Control Message Characteristics .. 4.2.1.5.1 Format ....................... 4.2.1.5.2 Precedence ................... ┆
0x45000…45100 (69, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(69,0, 1), len=0xff, h3=41519741}, f00=»5197A «, f01=»FIX/1000/PSP/0038, 4.1.5 «, f02=»bna «, f03=»MLA «, f04=»SYSTEM DESIGN SPEC. «, f05=25-07-84 10:23, f06=» 5 «, f07=»57 «, f08=» 32911 «, f09=27-06-85 09:59, f10=» «, f11=»00 «, f12=» 8 «, f13=27-06-85 10:00, f14=10-07-85 10:43, f15=»0514A «, f16=» 33 «, f17=» 6 «, f18=»28 «, f19=» 464 «, f20=» 33536 «, f21=» «, f22=» «, f99=020010000110052710110180aaca15050000000000000138039500df}
0x45100…45200 (69, 0, 1) WangDocumentBody
[…0x6…]
0x45800…45900 (69, 0, 8) Sector 00000000000000 ┆ ┆
[…0x77…]
