OctetView
0x00000…00100 (0, 0, 0) Sector 01514130313531 ┆ QA0151A ┆
0x00100…00200 (0, 0, 1) Sector 00000000000000 ┆ ┆
0x00200…00300 (0, 0, 2) Sector ff0080e0ffffff ┆ ` x ┆
0x00300…00306 (0, 0, 3) WangDocument {d00=0x19, d01=0x41, d02=0x41, ptr=(55,0, 0), d05=0x00}
0x00306…0030c WangDocument {d00=0x19, d01=0x61, d02=0x41, ptr=(60,0, 0), d05=0x00}
0x0030c…00312 WangDocument {d00=0x19, d01=0x97, d02=0x41, ptr=(29,0, 8), d05=0x00}
0x00312…00320 19 97 41 3e 08 00 00 00 00 00 00 00 00 00 ┆ A> ┆
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 12 ┆ ┆
0x00400…00500 (0, 0, 4) Sector 00000000000000 ┆ ┆
0x00500…00600 (0, 0, 5) Sector 01514130313531 ┆ QA0151A ┆
0x00600…00700 (0, 0, 6) Sector 421c402600415b ┆B @& A[' n X% % PO P ; A , C f x f V WW O 8 :t t c ~ 1997A f b < {C < { ; 9 ` c I bP b O ? : 8 9 t xB 1997A GOG@GAFNFO ┆
0x00700…00800 (0, 0, 7) Sector 00000000000000 ┆ ┆
[…0x8…]
0x01000…01100 (1, 0, 0) WangDocumentBody
0x01100…01200 (1, 0, 1) Sector 00000000000000 ┆ ┆
[…0x6…]
0x01800…01900 (1, 0, 8) WangDocumentBody
[…0x2…]
0x01b00…01c00 (1, 0, 11) Sector 010cff00199741 ┆ Aased upon an individual justment of each module. The calculations for data size is an extract of the specified Common Data and Subpackage Data. The following programs shall be developed: - Analysis - Conversion - Transport 4.3.1 Analysi┆
0x01c00…01d00 (1, 0, 12) Sector 010dff00199741 ┆ As Program Program area 5.700 swell statements * 2 = 11.4 Data area: Analysis-Buffer: 12.000 Guide table: 400 System Data 400 Internal Data 800 13,6 25.0 kw ┆
0x01d00…01e00 (1, 0, 13) Sector 010e0700199741 ┆ A 1 PROCEDURE READ EMF EQUIVALENCE(PARAM BASE, TRP: TRANSPORT PARAMETERS) START SAVE LINK (LINK)(PARAM BASE) OPEN VIEW (TRP. CIQ QEL REFERENCE) (CC): ERROR OK CC NE OK┆
0x01e00…01f00 (1, 0, 14) Sector 010fff00199741 ┆ A 1 4.3.2 Conversion Program Program area 4.500 swell statements * 2 = 9 kw Data area: Conversion Buffer: 12.000 System Data : 9.100/600 Internal Data : 9┆
0x01f00…02000 (1, 0, 15) Sector 01004900199741 ┆ I A00 = 22/13.5 kw Total : 31/22.5 kw The use ANALYSE ERROR (CC, O) RESTORE LINK RETURN Flowgram 4.2.6.6-7 R6 LINK (kept) Return Registers None is associated to OT OPSEM, i.┆
0x02000…02100 (2, 0, 0) WangDocumentBody
[…0x1b7…]
0x1d800…1d900 (29, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(29,0, 9), len=0xff, h3=41199741}, f00=»1997A «, f01=»CPS/SDS/033 «, f02=»rt «, f03=»KNB «, f04=»fra 4.2.6.4.6 «, f05=13-04-82 09:30, f06=» 7 «, f07=»59 «, f08=» 30730 «, f09=19-10-84 11:41, f10=» «, f11=»03 «, f12=» 19 «, f13=19-10-84 12:18, f14=25-10-84 11:00, f15=»0151A «, f16=» 45 «, f17=» 16 «, f18=»16 «, f19=» 500 «, f20=» 50714 «, f21=» «, f22=» 0 «, f99=630000000110052710110280aaca1505000000000000014203ab00df}
0x1d900…1da00 (29, 0, 9) WangDocumentBody
[…0x83…]
0x25d00…25e00 (37, 0, 13) Sector 250e9800196141 ┆% aA? ZIDASM TIMEOUT END CASE FLASH TIMEOUT ? TRS FLASH TIMEOUT (TSN) END CASE END LOOP RESTORE LINK RETURN Flowgram 4.2.4.4.16.5-3 The NT Timer Control Module contains all the procedures for handling the timer functions within a NICS┆
0x25e00…25f00 (37, 0, 14) Sector 250fff00196141 ┆% aA 1 4.2.4.4.17 SC Timer Control Module 4.2.4.4.17.1 Functional Specification The SC Timer Control Module supplies all the procedures for handling the timer functions within the SCA┆
0x25f00…26000 (37, 0, 15) Sector 2500ff00196141 ┆% aARS/CCIS Transport Control. The following functions are supplied: a) Preemption delay elapsed b) Reset Outgoing TSN. c) Update SC TIMER TABLE. d) Timeout for incoming traffic. e) Timeout for Transaction Acknowledge. f) Timeout for TSN check ┆
0x26000…26100 (38, 0, 0) WangDocumentBody
[…0x10f…]
0x37000…37100 (55, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(55,0, 1), len=0xff, h3=41194141}, f00=»1941A «, f01=»CPS/SDS/033 «, f02=»bk «, f03=»BLP «, f04=»4.2.3,Traffic Handl. «, f05=30-03-82 10:55, f06=» 29 «, f07=»05 «, f08=» 77166 «, f09=28-09-84 15:34, f10=» «, f11=»00 «, f12=» 5 «, f13=28-09-84 15:34, f14=01-10-84 09:39, f15=»0151A «, f16=» 97 «, f17=» 55 «, f18=»29 «, f19=» 1260 «, f20=»122014 «, f21=» «, f22=» «, f99=900000000100002710110280aaca15050000000000000142039901df}
0x37100…37200 (55, 0, 1) WangDocumentBody
[…0x4e…]
0x3c000…3c100 (60, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(60,0, 1), len=0xff, h3=41196141}, f00=»1961A «, f01=»CPS/SDS/033 «, f02=»BLP «, f03=»pan «, f04=»Fra kap. 4.2.4.4.5 «, f05=31-03-82 14:25, f06=» 13 «, f07=»42 «, f08=» 33845 «, f09=28-09-84 14:05, f10=» «, f11=»01 «, f12=» 24 «, f13=28-09-84 15:29, f14=01-10-84 09:40, f15=»0151A «, f16=» 89 «, f17=» 24 «, f18=»58 «, f19=» 1072 «, f20=» 65700 «, f21=» «, f22=» @ «, f99=540010000110052710110280aaca15050000000000000142036501df}
0x3c100…3c200 (60, 0, 1) WangDocumentBody
[…0x6…]
0x3c800…3c900 (60, 0, 8) Sector 3c09ff00196141 ┆< aA7.5 Module Design .............. 4.2.4.4.8 SC Internal Command Module ..... 4.2.4.4.8.1 Functional Specification ... 4.2.4.4.8.2 Module Interface ........... 4.2.4.4.8.3 Module Components .......... ┆
0x3c900…3ca00 (60, 0, 9) Sector 3c0aff00196141 ┆< aA 4.2.4.4.8.4 Data Description ........... 4.2.4.4.8.5 Module Design .............. 4.2.4.4.9 PTP Internal Command Module .... 4.2.4.4.9.1 Functional Specification ... 4.2.4.4.9.2 Module Interface .....┆
0x3ca00…3cb00 (60, 0, 10) Sector 3c0bff00196141 ┆< aA...... 4.2.4.4.9.3 Module Components .......... 4.2.4.4.9.4 Data Description ........... 4.2.4.4.9.5 Module Design .............. 4.2.4.4.10 TP EXTERNAL COMMAND MODULE ... 4.2.4.4.10.1 Functiona┆
0x3cb00…3cc00 (60, 0, 11) Sector 3c0cff00196141 ┆< aAl Specification .. 4.2.4.4.10.2 Module Interface .......... 4.2.4.4.10.3 Module Components ......... 4.2.4.4.10.4 Data Description .......... 4.2.4.4.10.5 Module Design ............. 4.2.4.4.11 ┆
0x3cc00…3cd00 (60, 0, 12) Sector 3c0dff00196141 ┆< aANT External Command Module ... 4.2.4.4.11.1 Functional Specification .. 4.2.4.4.11.2 Module Interface .......... 4.2.4.4.11.3 Module Components ......... 4.2.4.4.11.4 Data Description .......... ┆
0x3cd00…3ce00 (60, 0, 13) Sector 3c0eff00196141 ┆< aA 4.2.4.4.11.5 Module Design ............. 4.2.4.4.12 SC External Command Module ... 4.2.4.4.12.1 Functional Specification .. 4.2.4.4.12.2 Module Interface .......... 4.2.4.4.12.3 Module Components ........┆
0x3ce00…3cf00 (60, 0, 14) Sector 3c0f7600196141 ┆< v aA. 4.2.4.4.12.4 Data Description .......... 4.2.4.4.12.5 Module Design ............. .4.1.5 Module Design .............. 4.2.4.4.2 NT Traffic Status Control ...... 4.2.4.4.2.1 Functional Specification┆
0x3cf00…3d000 (60, 0, 15) Sector 3c00ff00196141 ┆< aA 1 4.2.4.4.13 PTP External Command Module .. 4.2.4.4.13.1 Functional Specifica┆
0x3d000…3d100 (61, 0, 0) Sector 3d01ff00196141 ┆= aAus Control ...... 4.2.4.4.3.1 Functional Specification ... 4.2.4.4.3.2 Module Interface ........... 4.2.4.4.3.3 Module Components .......... 4.2.4.4.3.4 Data Description ........... 4.2.4.4.3.5 ┆
0x3d100…3d200 (61, 0, 1) Sector 3d02ff00196141 ┆= aAModule Design .............. 4.2.4.4.4 PTP Traffic Status Control ..... 4.2.4.4.4.1 Functional Specification ... 4.2.4.4.4 PTP Traffic Status Control ..... 4.2.4.4.4.1 Functional Specification ... ┆
0x3d200…3d300 (61, 0, 2) Sector 3d03ff00196141 ┆= aA 4.2.4.4.4.2 Module Interface ........... 4.2.4.4.4.3 Module Components .......... 4.2.4.4.4.4 Data Descriptions .......... 4.2.4.4.4.5 Module Design .............. 4.2.4.4.5 PTR Traffic Status Control .┆
0x3d300…3d400 (61, 0, 3) Sector 3d04ff00196141 ┆= aA.... 4.2.4.4.5.1 Functional Specification ... 4.2.4.4.5.2 Module Interface ........... 4.2.4.4.5.3 Module Components .......... 4.2.4.4.5.4 Data Description ........... 4.2.4.4.5.5 Module Design┆
0x3d400…3d500 (61, 0, 4) Sector 3d051c00196141 ┆= aA .............. TRS DISCONTINUITY LOG (R0,R1,R2,R3,R4,R5,R7,R6) Register Conventions Call Registers R1 Received TSN (destr.) R2 Expected TSN (destr.) R3 Message Type (QEL Maint) (destr.) R6 LINK (destr.) Return Registers ┆
0x3d500…3d600 (61, 0, 5) Sector 3d06ff00196141 ┆= aA 1 4.2.4.4.6 TP Internal Command Module ..... 4.2.4.4.6.1 Functional Specifica┆
0x3d600…3d700 (61, 0, 6) Sector 3d07ff00196141 ┆= aAtion ... 4.2.4.4.6.2 Module Interface ........... 4.2.4.4.6.3 Module Components .......... 4.2.4.4.6.4 Data Description ........... 4.2.4.4.6.5 Module Design .............. 4.2.4.4.7 NT Internal┆
0x3d700…3d800 (61, 0, 7) Sector 3c08ff00196141 ┆< aA Command Module ..... 4.2.4.4.7.1 Functional Specification ... 4.2.4.4.7.2 Module Interface ........... 4.2.4.4.7.3 Module Components .......... 4.2.4.4.7.4 Data Description ........... 4.2.4.4.┆
0x3d800…3d900 (61, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(61,0, 9), len=0xff, h3=41196141}, f00=»1961A «, f01=»CPS/SDS/033 «, f02=»BLP «, f03=»pan «, f04=»Fra kap. 4.2.4.4.5 «, f05=31-03-82 14:25, f06=» 13 «, f07=»42 «, f08=» 33845 «, f09=28-03-84 13:28, f10=» 2 «, f11=»13 «, f12=» 1629 «, f13=28-03-84 12:37, f14=04-09-84 10:50, f15=»0151A «, f16=» 89 «, f17=» 24 «, f18=»52 «, f19=» 1156 «, f20=» 65521 «, f21=» «, f22=» «, f99=020010000110052710110380aa8a37040000000000000142036501df}
0x3d900…3da00 (61, 0, 9) Sector 3d0a5900196141 ┆= Y aA = = = < ; ; ; : : : : : 9 9 6 6 6 6 6 6 5 5 5 5 4 4 4 4 4 3 3 3 3 2 2 2 2 2 1 1 1 1 1 0 0 0 / / / / / / . . . . . - - - - , , , , + + + + * * * * * ) ) ) ) ) ( ( ( ( ' ' ' & & & % 7)7.z.:*:(. z"z&y"G, ' y%x( C ! Gx&w*w%w'v*I&I$ . : 5 7 7 7┆
0x3da00…3db00 (61, 0, 10) Sector 3d0bab00196141 ┆= + aA 1 CPS/SDS/033 831101 TRAFFIC HANDLING DETAILED DESIGN SPECIFICATION ISSUE 1 CAMPS &*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x3db00…3dc00 (61, 0, 11) Sector 3d0cff00196141 ┆= aA 1 1 4.2.4.3 Data Flow a┆
0x3dc00…3dd00 (61, 0, 12) Sector 3d0dff00196141 ┆= aAnd Control Logic ........ 4.2.4.3.1 Commands from Channel Command Queue .......................... 4.2.4.3.2 Transport Control Masks ........ 4.2.4.3.3 Start Up Procedure ............. 4.2.4.3.4 Stop┆
0x3dd00…3de00 (61, 0, 13) Sector 3d0eff00196141 ┆= aA Procedure ................. 4.2.4.4 Module Specification ............... 4.2.4.4.1 TP Traffic Status Control ...... 4.2.4.4.1.1 Functional Specification ... 4.2.4.4.1.2 Module Interface ........... ┆
0x3de00…3df00 (61, 0, 14) Sector 3d0fff00196141 ┆= aA 4.2.4.4.1.3 Module Components .......... 4.2.4.4.1.4 Data Description ........... 4.2.4.4.1.5 Module Design .............. 4.2.4.4.2 NT Traffic Status Control ...... 4.2.4.4.2.1 Functional Specification┆
0x3df00…3e000 (61, 0, 15) Sector 3d00ff00196141 ┆= aA ... 4.2.4.4.2.2 Module Interface ........... 4.2.4.4.2.3 Module Components .......... 4.2.4.4.2.4 Data Description ........... 4.2.4.4.2.5 Module Design .............. 4.2.4.4.3 SC Traffic Stat┆
0x3e000…3e100 (62, 0, 0) Sector 3e01ff00199741 ┆> A Outgoing Message Transmission ... 4.2.6.4.9.1 Functional Specification ...... 4.2.6.4.9.2 Module Interface .............. 4.2.6.4.9.3 Module Components ........... 4.2.6.4.9.4 Data Description .........┆
0x3e100…3e200 (62, 0, 1) Sector 3e02ff00199741 ┆> A..... 4.2.6.4.9.5 Module Design ................. 4.2.6.4.10 Message Line Generation Module 4.2.6.4.10.1 Functional Specification .... 4.2.6.4.10.2 Module Interface ............ 4.2.6.4.10.3 M┆
0x3e200…3e300 (62, 0, 2) Sector 3e03ff00199741 ┆> Aodule Components ........... 4.2.6.4.10.4 Data Description ............ 4.2.6.4.10.5 Module Design ............... 4.3 Memory Layout ................................. 4.3.1 Analysis Program .....................┆
0x3e300…3e400 (62, 0, 3) Sector 3e048500199741 ┆> A..... 4.3.2 Conversion Program ........................ 4.3.3 Transport Program ......................... Udf]rer) Inds`t hvilket? Slette hvilket? Flytte hvilket? Kopiere hvilket? Bytte hvilket? Bytte med? S]ge hvilket? ┆
0x3e400…3e500 (62, 0, 4) Sector 3e05ff00199741 ┆> A 1 4.2.6.4.11 ASM Generation ................ 4.2.6.4.11.1 Functional Specification .... 4.2.6.4.┆
0x3e500…3e600 (62, 0, 5) Sector 3e06ff00199741 ┆> A11.2 Module Interface ............ 4.2.6.4.11.3 Module Components ........... 4.2.6.4.11.4 Data Description ............ 4.2.6.4.11.5 Module Design ............... 4.2.6.5 OTS, Common Subpackage Data ......┆
0x3e600…3e700 (62, 0, 6) Sector 3e07f500199741 ┆> u A..... 4.2.6.6 OTS, Common Subpackage Procedures ..... 4.2.6.6.1 Functional Specification .......... 4.2.6.6.2 Module Interfaces ................. 4.2.6.7 Subpackage Interface .................. B 3 _┆
0x3e700…3e800 (62, 0, 7) Sector 3d08ff00199741 ┆= A 1 4.2.6.4.7 NICS TARE Outgoing Message Handling 4.2.6.4.7.1 Functional Specification The NT-Outgoing Message Handling supplies the procedures which take care of the basic flow of┆
0x3e800…3e900 (62, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(62,0, 9), len=0xff, h3=41199741}, f00=»1997A «, f01=»CPS/SDS/033 «, f02=»rt «, f03=»KNB «, f04=»fra 4.2.6.4.6 «, f05=13-04-82 09:30, f06=» 7 «, f07=»59 «, f08=» 30730 «, f09=19-05-82 15:17, f10=» «, f11=»15 «, f12=» 32 «, f13=19-05-82 15:36, f14=24-05-82 09:28, f15=»0151A «, f16=» 53 «, f17=» 9 «, f18=»53 «, f19=» 496 «, f20=» 33993 «, f21=» «, f22=» «, f99=010000000110052710110290aaca1505000000000000014203b100df}
0x3e900…3ea00 (62, 0, 9) Sector 3e0a3500199741 ┆> 5 A > > > > = = = = = < < < < < < ; ; ; ; ; ; : : : : 9 9 9 9 9 8 8 8 8 8 7 7 7 7 7 $ $ $ $ # # ! ! ! DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Fo┆
0x3ea00…3eb00 (62, 0, 10) Sector 3e0baa00199741 ┆> * A 1 CPS/SDS/033 KNB/820514 TRAFFIC HANDLING DETAILED DESIGN SPECIFICATION CAMPS 2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x3eb00…3ec00 (62, 0, 11) Sector 3e0cff00199741 ┆> A 1 1 4.2.6.4.6 NICS TARE Outgoing Message Handling ┆
0x3ec00…3ed00 (62, 0, 12) Sector 3e0dff00199741 ┆> A 4.2.6.4.6.1 Functional Specification ...... 4.2.6.4.6.2 Module Interface .............. 4.2.6.4.6.3 Module Components ............. 4.2.6.4.6.4 Data Description .............. 4.2.6.4.6.5 Module D┆
0x3ed00…3ee00 (62, 0, 13) Sector 3e0eff00199741 ┆> Aesign ................. 4.2.6.4.7 SCARS/CCIS Outgoing Message Handling .......................... 4.2.6.4.7.1 Functional Specification ...... 4.2.6.4.7.2 Module Interface .............. 4.2.6.4.┆
0x3ee00…3ef00 (62, 0, 14) Sector 3e0fff00199741 ┆> A7.3 Module Components ............. 4.2.6.4.7.4 Data Description .............. 4.2.6.4.7.5 Module Design ................. 4.2.6.4.8 PTP Outgoing Message Handling ..... 4.2.6.4.8.1 Functional Specificatio┆
0x3ef00…3f000 (62, 0, 15) Sector 3e00ff00199741 ┆> An ...... 4.2.6.4.8.2 Module Interface .............. 4.2.6.4.8.3 Module Components ............. 4.2.6.4.8.4 Data Description .............. 4.2.6.4.8.5 Module Design ................. 4.2.6.4.9┆
0x3f000…3f100 (63, 0, 0) Sector 3f01ff00196141 ┆? aAy test performed by AAS. If N 4 the following actions take place: - A report is transmitted to the supervisor printer - If the incoming channel is open it is closed by updating the ACP 127 CHANNEL STATUS. In this case also reports and statis┆
0x3f100…3f200 (63, 0, 1) Sector 3f02ff00196141 ┆? aAtics are generated. The QEL containing the command is dismantled from the channel command queue. Procedure FLASH ACK REC (R2 C D QEL REFERENCE R4 C D POINTER TO TSN R6) C D LINK This procedure takes care of the SEND FLASH ACK command. ┆
0x3f200…3f300 (63, 0, 2) Sector 3f03ad00196141 ┆? - aAAn operation is sent to the OTS to make it transmit an ASM with the flash acknowledge. The QEL containing the command is dismantled from the channel command queue. 4.2.4.4.6.3-1. 4.2.4.4.6.4 Data Description Data structures are defined in s┆
0x3f300…3f400 (63, 0, 3) Sector 3f04ff00196141 ┆? aA 1 Procedure OPEN OUTG TRAFFIC (R2 C D QEL REFERENCE R6) C D LINK This procedure takes care of the OPEN OUTG TRAFFIC command. If the outgoing channel is closed the following a┆
0x3f400…3f500 (63, 0, 4) Sector 3f05ff00196141 ┆? aActions take place: - The channel is opened by updating the ACP 127 CHANNEL STATUS and the CIRCUIT CONNECTIVITY TABLE - A report is send to the supervisor printer - Statistics are generated (OUTG CHN AVAIL). Each time this command is recei┆
0x3f500…3f600 (63, 0, 5) Sector 3f06ff00196141 ┆? aAved an operation is sent to OTS to make it transmit a CHANNEL TEST MESSAGE (INT ZBZ). The QEL containing the command is dismantled from the channel command queue. Procedure CLOSE OUTG TRAFFIC (R2 C D QEL REFERENCE R6) C D LINK This proced┆
0x3f600…3f700 (63, 0, 6) Sector 3f07ff00196141 ┆? aAure takes care of the CLOSE OUTG TRAFFIC command. If the outgoing channel is open the following actions place: - The channel is closed by updating the ACP 127 CHANNEL STATUS and the CIRCUIT CONNECTIVITY TABLE - A report is send to the super┆
0x3f700…3f800 (63, 0, 7) Sector 36089500196141 ┆6 aAvisor printer - Statistics are generated (OUTG CHN AVAIL). The QEL containing the command is dismantled from the channel command queue. e SELF CHECK REC (R2 C D QEL REFERENCE R3 C D FLAGS R6) C D LINK This procedure takes care of the ┆
0x3f800…3f900 (63, 0, 8) Sector 3f09ff00196141 ┆? aAactions related to the SELF CHECK RECEIVED command. The procedures checks if a SELF ADDRESSED CHANNEL CHECK has been transmitted, i.e. if a timer has been assigned to the answer. If not the ASM referenced by the command is considered as not reco┆
0x3f900…3fa00 (63, 0, 9) Sector 3f0aff00196141 ┆? aAgnized and will be sent to the supervisor printer. The QEL is dismantled from the channel command queue. Procedure INIT PREEMPTION (R2 C D QEL REFERENCE R6) C D LINK This procedure is related to the FLASH NOTIF command. A timeout equal t┆
0x3fa00…3fb00 (63, 0, 10) Sector 3f0bff00196141 ┆? aAo the preemption delay (defined within the TRC PTOP PARAMETER) is requested from the CSF timer monitor. If a timeout already has been requested no new one is requested. If the preemption delay is equal to 0 and operation is sent to the OTS to ma┆
0x3fb00…3fc00 (63, 0, 11) Sector 3f0cff00196141 ┆? aAke it initiate preemption if necessary. The QEL is dismantled from the channel command queue. Procedure TEST REPLY REC (R2 C D QEL REF R4 C D POINTER TO REPLY (N) R6) C D LINK This procedure takes care ot the TEST REPLY RECEIVED command.┆
0x3fc00…3fd00 (63, 0, 12) Sector 3f0d0800196141 ┆? aA RETURN Flowgram 4.2.4.4.5.5-1 module is also used by the OCR Process (refer section 4.2.4.4.199. 4.2.4.4.5.2 Module Interface Call Specification a) PTR TC COROUTINE b) PTR TC COROUTINE (R6) Register Conventions Call Registers R┆
0x3fd00…3fe00 (63, 0, 13) Sector 3f0eff00196141 ┆? aA 1 If the test reply info (N) is less than 4 the following actions take place: - A report is sent to the supervisor printer - If the outgoing channel is open, it will be closed by┆
0x3fe00…3ff00 (63, 0, 14) Sector 3f0fff00196141 ┆? aA updating the ACP 127 CHANNEL status and the CIRCUIT CONNECTIVITY TABLE. This case also includes report and statistics generation. The QEL containing the command is dismantled from the channel command queue. Procedure SEND TEST REPLY ASM (R2 C┆
0x3ff00…40000 (63, 0, 15) Sector 3f00ff00196141 ┆? aA D QEL REFERENCE R4 C D POINTER TO ANALYSIS RESULT (N) R6) C D LINK This procedure takes care of the actions related to the SEND TEST REPLY command. An operation is sent to the OTS to make it transmit an ASM with the result (N) of the qualit┆
0x40000…40100 (64, 0, 0) Sector 4001ff00196141 ┆@ aA INF, SUBTYPE): OK DECODE TP INTERNAL COMMAND (R0,R1,R2,R3,R4,R5,R7,R6) 1 Register Conventions Call Registers R0 Maintype (destr.) R1 Subtype (destr.) R2 Qel (dest┆
0x40100…40200 (64, 0, 1) Sector 40026500196141 ┆@ e aAr.) R3 Flags (destr.) R4 INF Pointer (destr.) R6 LINK (kept) Return Registers None he upper most control logic of the transport control within a transport subprocess for PTR. The following tasks are performed: - Init of command trans┆
0x40200…40300 (64, 0, 2) Sector 4003ff00196141 ┆@ aA 1 4.2.4.4.6.3 Module Components The components of TP Internal Command Module are depicted on figure 4.2.4.4.6.3-1. 4.2.4.4.6.4 Data Description Data structures are defined in s┆
0x40300…40400 (64, 0, 3) Sector 4004ff00196141 ┆@ aAection 4.2.3.5. 1 4.2.4.4.6.5 Module Design DECODE TP INTERNAL COMMAND : Flowgram 4.2.4.4.6.5-1 Module Entry: Export Procedure TP DECODE INTERNAL COMMAND 1 ┆
0x40400…40500 (64, 0, 4) Sector 4005ff00196141 ┆@ aA (R0 C D MAINTYPE R1 C D SUBTYPE R2 C D QEL REFERENCE R3 C D QEL FLAGS R4 C D POINTER TO QEL INF R5 D R7 R POINTER TO TRANSPORT PARAMETERS (R6) C D LINK This procedure decodes the int┆
0x40500…40600 (64, 0, 5) Sector 4006ff00196141 ┆@ aAernal commands received from the channel command queue. For each command a call is made to specific procedure taking care of the command. Module Procedures: Procedure CHECK TSN (R2 C D QEL REFERENCE R4 C D POINTER TO TSN R6) C D LINK T┆
0x40600…40700 (64, 0, 6) Sector 4007bc00196141 ┆@ < aAhe procedure is related to the TSN CHECK RECEIVED command. The TSN supplied by the command is compared with the TSN of the message transmitted before the last outgoing TSN reset. cknowledges operations received from OTS and its during a FINAL CLO┆
0x40700…40800 (64, 0, 7) Sector 3f08ff00196141 ┆? aA 1 If no match a report is transmitted to the supervisors printer. Procedure SELF CHECK REC (R2 C D QEL REFERENCE R3 C D FLAGS R6) C D LINK This procedure takes care of the ┆
0x40800…40900 (64, 0, 8) Sector 40096400196141 ┆@ d aA 1 Figure 4.2.4.4.5.3-1 4.2.4.4.8.1 Functional Specification ... 4.2.4.4.8.2 Module Interface ........... 4.2.4.4.8.3 Module Components .......... ┆
0x40900…40a00 (64, 0, 9) Sector 400aff00196141 ┆@ aA 1 PROCEDURE PTR TC COROUTINE EQUIVALENCE(PARAM BASE,TRP: TRANSPORT PARAMETERS) START LOOP "Forever" READ PARAM BASE CHECK INDICATOR(TRP.CONTROL STATE, PRIMARY COMMAN┆
0x40a00…40b00 (64, 0, 10) Sector 400bff00196141 ┆@ aAD)(CC): BOOLEAN CC EQ TRUE? RECEIVE TRS OPERATION(POOL : TRP.TRS OP POOL, OP TYPE : PRIM COM, INFO : TRP.CCQ1 QEL ATTRIBUTES, PRIORITY : 2) (OPERATION) : OK INIT COMMAND TRANSFER (QUEUE : PTR COMMAN┆
0x40b00…40c00 (64, 0, 11) Sector 400cff00196141 ┆@ aAD QUEUE.1, ATTRIBUTES : TRP.CCQ1 QEL ATTRIBUTES, OPERATION) RESET INDICATOR(TRP.CONTROL STATE, PRIMARY COMMAND) WAIT TRS OPSEM (TRP.TC OPSEM) "Main Waiting Point" (TRP.TC OPERATION) DECODE PTR TC OPERATION END LOO┆
0x40c00…40d00 (64, 0, 12) Sector 400d2a00196141 ┆@ * aAP RETURN Flowgram 4.2.4.4.5.5-1 module is also used by the OCR Process (refer section 4.2.4.4.199. 4.2.4.4.5.2 Module Interface Call Specification a) PTR TC COROUTINE b) PTR TC COROUTINE (R6) Register Conventions Call Registers R┆
0x40d00…40e00 (64, 0, 13) Sector 400eff00196141 ┆@ aA 1 4.2.4.4.6 TP Internal Command Module 4.2.4.4.6.1 Functional Specification The PT INTERNAL COMMAND module contains procedures for decoding of the THP INTERNAL commands received ┆
0x40e00…40f00 (64, 0, 14) Sector 400fff00196141 ┆@ aAfrom the Channel Command Queue (CCQ) within the TRC/POINT TO POINT transport. The THP INTERNAL commands are generated by the AAS or the ACS and includes the following subjects: a) Test Reply b) Send Test Reply c) Self Check Received d) Check ┆
0x40f00…41000 (64, 0, 15) Sector 4000ff00196141 ┆@ aATSN e) Open Outging Traffic f) Close Outgoing Traffic g) Flash Acknowledge h) Send Flash Acknowledge i) Flash Message 4.2.4.4.6.2 Module Interface Call Specification a) DECODE TP INTERNAL COMMAND (MAINTYPE, Qel, Flags, ┆
0x41000…41100 (65, 0, 0) Sector 4101ff00196141 ┆A aA Module Entry: Export Procedure PTR TC COROUTINE 1 (R6) C D LINK This procedure is coroutine running under control of the CS┆
0x41100…41200 (65, 0, 1) Sector 4102ff00196141 ┆A aAF COROUTINE MONITOR. The procedure is supplied with an endless loop. The procedure supplies the upper most control logic of the transport control within a transport subprocess for PTR. The following tasks are performed: - Init of command trans┆
0x41200…41300 (65, 0, 2) Sector 4103e200196141 ┆A b aAfere from the channel command queue (CCQ). Dependent on the state of the COMMAND CTR MASK. - Call of decode procedure each time an operation has been received from TC OPSEM (main waiting point for TRANSPORT CONTROL). omponents ......... ┆
0x41300…41400 (65, 0, 3) Sector 4104ff00196141 ┆A aA 1 Module Procedures: Procedure DECODE PTR TC OPERATION (R4 C D POINTER TO SAVE AREA R7 C D POINTER TO TRANSPORT PARAMS R6 C D LINK This procedure decodes the OP TYPE of the┆
0x41400…41500 (65, 0, 4) Sector 4105ff00196141 ┆A aA operation which has been stored into the save area (TRS SAVE OP TYPE). A call is made to a procedure taking care of the actions related to the OP TYPE. Procedure INPUT PTR COMMAND (R4 C D POINTER TO OPERATION SAVE AREA R6 C D LINK This pr┆
0x41500…41600 (65, 0, 5) Sector 4106ff00196141 ┆A aAocedure inputs a command from the channel command queue (CCQ). The command is received through the operation referred to in the specified save area. On the base of the command maintype the procedure will activate one of the following external proc┆
0x41600…41700 (65, 0, 6) Sector 4107ff00196141 ┆A aAedures: - DECODE PTR EXTERNAL COMMAND Procedure CLOSE ACKNOWLEDGE (R4 C D POINTER TO OPERATION SAVE AREA R6) C D This procedure takes care of the actions related to close acknowledges operations received from OTS and its during a FINAL CLO┆
0x41700…41800 (65, 0, 7) Sector 4008ba00196141 ┆@ : aASE DOWN or STOP procedure. When the acknowledges have been received the following actions take place: - The I/O connection is dismantled - Achknowledge are returned to SSC face .............. 4.2.4.7.1 THP Internal ...............┆
0x41800…41900 (65, 0, 8) Sector 41094500196141 ┆A E aA... 4.2.4.7.2 THP External .................. al Command Module ..... 4.2.4.4.8.1 Functional Specification ... 4.2.4.4.8.2 Module Interface ........... 4.2.4.4.8.3 Module Components .......... ┆
0x41900…41a00 (65, 0, 9) Sector 410aff00196141 ┆A aA 1 4.2.4.4.5 PTR Traffic Status Control 4.2.4.4.5.1 Functional Specification The PTR Traffic Status Control Module supplies the PTR TC COROUTINE for the PTR Transport. The follo┆
0x41a00…41b00 (65, 0, 10) Sector 410bff00196141 ┆A aAwing main tasks are performed: - Transfer of a command from the Channel Command Queue (CCQ) is initiated. - Reception of operation from the main waiting point, TC OPSEM. - Decoding of received operation and activation of action related to oper┆
0x41b00…41c00 (65, 0, 11) Sector 410cff00196141 ┆A aAation. Procedures for the following actions are included: - 140 Identical Characters detected by ITS. - Close Down Acknowledge from ITS. - Input of command from Channel Command Queue (CCQ). On the basis of this command the PTR External Comma┆
0x41c00…41d00 (65, 0, 12) Sector 410dff00196141 ┆A aAnd Module is activated. Note: This module is also used by the OCR Process (refer section 4.2.4.4.199. 4.2.4.4.5.2 Module Interface Call Specification a) PTR TC COROUTINE b) PTR TC COROUTINE (R6) Register Conventions Call Registers R┆
0x41d00…41e00 (65, 0, 13) Sector 410e0f00196141 ┆A aA6 LINK 11.5 Module Design ............. 4.2.4.4.12 SC External Command Module ... 4.2.4.4.12.1 Functional Specification .. 4.2.4.4.12.2 Module Interface .......... 4.2.4.4.12.3 Module Components ........┆
0x41e00…41f00 (65, 0, 14) Sector 410fff00196141 ┆A aA 1 Return Registers None The PTR TC COROUTINE is implemented with an endless loop. 4.2.4.4.5.3 Module Components The components of the PTR Traffic Status Control Module are de┆
0x41f00…42000 (65, 0, 15) Sector 4100ff00196141 ┆A aApicted on figure 4.2.4.4.5.3-1. 4.2.4.4.5.4 Data Description All data structures used by this module are define in section 4.2.3.5. 4.2.4.4.5.5 Module Design Procedures included in PTR Traffic Status Control are reentrant. 1 ┆
0x42000…42100 (66, 0, 0) Sector 4201ff00196141 ┆B aAtion .. 4.2.4.4.13.2 Module Interface .......... 4.2.4.4.13.3 Module Components ......... 4.2.4.4.13.4 Data Description .......... 4.2.4.4.13.5 Module Design ............. 4.2.4.4.14 PTR Externa┆
0x42100…42200 (66, 0, 1) Sector 4202ff00196141 ┆B aAl Command Module .. 4.2.4.4.14.1 Functional Specification .. 4.2.4.4.14.2 Module Interface .......... 4.2.4.4.14.3 Module Components ......... 4.2.4.4.14.4 Data Description .......... 4.2.4.4.14┆
0x42200…42300 (66, 0, 2) Sector 4203ff00196141 ┆B aA.5 Module Design ............. 4.2.4.4.15 TP Timer Control Module ...... 4.2.4.4.15.1 Functional Specification .. 4.2.4.4.15.2 Module Interface .......... 4.2.4.4.15.3 Module Components ......... ┆
0x42300…42400 (66, 0, 3) Sector 4204ff00196141 ┆B aA 4.2.4.4.15.4 Data Description .......... 4.2.4.4.15.5 Module Design ............. 4.2.4.4.16 NT Timer Control Module ...... 4.2.4.4.16.1 Functional Specification .. 4.2.4.4.16.2 Module Interface ........┆
0x42400…42500 (66, 0, 4) Sector 4205ff00196141 ┆B aA.. 4.2.4.4.16.3 Module Components ......... 4.2.4.4.16.4 Data Description .......... 4.2.4.4.16.5 Module Design ............. 4.2.4.4.17 SC Timer Control Module ...... 4.2.4.4.17.1 Functional Sp┆
0x42500…42600 (66, 0, 5) Sector 4206ff00196141 ┆B aAecification .. 4.2.4.4.17.2 Module Interface .......... 4.2.4.4.17.3 Module Components ......... 4.2.4.4.17.4 Data Description .......... 4.2.4.4.17.5 Module Design ............. 4.2.4.4.18 PTP ┆
0x42600…42700 (66, 0, 6) Sector 4207ff00196141 ┆B aATimer Control Module ..... 4.2.4.4.18.1 Functional Specification .. 4.2.4.4.18.2 Module Interface .......... 4.2.4.4.18.3 Module Components ......... 4.2.4.4.18.4 Data Description .......... 4.2┆
0x42700…42800 (66, 0, 7) Sector 4108ff00196141 ┆A aA.4.4.18.5 Module Design ............. 4.2.4.5 Common Subpackage Data ............ 4.2.4.6 Common Subpackage Procedures ...... 4.2.4.7 Subpackage Interface .............. 4.2.4.7.1 THP Internal ...............┆
0x42800…42900 (66, 0, 8) Sector 4209ff00196141 ┆B aA7.5 Module Design .............. 4.2.4.4.8 SC Internal Command Module ..... 4.2.4.4.8.1 Functional Specification ... 4.2.4.4.8.2 Module Interface ........... 4.2.4.4.8.3 Module Components .......... ┆
0x42900…42a00 (66, 0, 9) Sector 420aff00196141 ┆B aA 4.2.4.4.8.4 Data Description ........... 4.2.4.4.8.5 Module Design .............. 4.2.4.4.9 PTP Internal Command Module .... 4.2.4.4.9.1 Functional Specification ... 4.2.4.4.9.2 Module Interface .....┆
0x42a00…42b00 (66, 0, 10) Sector 420bff00196141 ┆B aA...... 4.2.4.4.9.3 Module Components .......... 4.2.4.4.9.4 Data Description ........... 4.2.4.4.9.5 Module Design .............. 4.2.4.4.10 TP EXTERNAL COMMAND MODULE ... 4.2.4.4.10.1 Functiona┆
0x42b00…42c00 (66, 0, 11) Sector 420cff00196141 ┆B aAl Specification .. 4.2.4.4.10.2 Module Interface .......... 4.2.4.4.10.3 Module Components ......... 4.2.4.4.10.4 Data Description .......... 4.2.4.4.10.5 Module Design ............. 4.2.4.4.11 ┆
0x42c00…42d00 (66, 0, 12) Sector 420dff00196141 ┆B aANT External Command Module ... 4.2.4.4.11.1 Functional Specification .. 4.2.4.4.11.2 Module Interface .......... 4.2.4.4.11.3 Module Components ......... 4.2.4.4.11.4 Data Description .......... ┆
0x42d00…42e00 (66, 0, 13) Sector 420eff00196141 ┆B aA 4.2.4.4.11.5 Module Design ............. 4.2.4.4.12 SC External Command Module ... 4.2.4.4.12.1 Functional Specification .. 4.2.4.4.12.2 Module Interface .......... 4.2.4.4.12.3 Module Components ........┆
0x42e00…42f00 (66, 0, 14) Sector 420f7600196141 ┆B v aA. 4.2.4.4.12.4 Data Description .......... 4.2.4.4.12.5 Module Design ............. .4.1.5 Module Design .............. 4.2.4.4.2 NT Traffic Status Control ...... 4.2.4.4.2.1 Functional Specification┆
0x42f00…43000 (66, 0, 15) Sector 4200ff00196141 ┆B aA 1 4.2.4.4.13 PTP External Command Module .. 4.2.4.4.13.1 Functional Specifica┆
0x43000…43100 (67, 0, 0) Sector 4301ff00196141 ┆C aAus Control ...... 4.2.4.4.3.1 Functional Specification ... 4.2.4.4.3.2 Module Interface ........... 4.2.4.4.3.3 Module Components .......... 4.2.4.4.3.4 Data Description ........... 4.2.4.4.3.5 ┆
0x43100…43200 (67, 0, 1) Sector 4302ff00196141 ┆C aAModule Design .............. 4.2.4.4.4 PTP Traffic Status Control ..... 4.2.4.4.4.1 Functional Specification ... 4.2.4.4.4 PTP Traffic Status Control ..... 4.2.4.4.4.1 Functional Specification ... ┆
0x43200…43300 (67, 0, 2) Sector 4303ff00196141 ┆C aA 4.2.4.4.4.2 Module Interface ........... 4.2.4.4.4.3 Module Components .......... 4.2.4.4.4.4 Data Descriptions .......... 4.2.4.4.4.5 Module Design .............. 4.2.4.4.5 PTR Traffic Status Control .┆
0x43300…43400 (67, 0, 3) Sector 4304ff00196141 ┆C aA.... 4.2.4.4.5.1 Functional Specification ... 4.2.4.4.5.2 Module Interface ........... 4.2.4.4.5.3 Module Components .......... 4.2.4.4.5.4 Data Description ........... 4.2.4.4.5.5 Module Design┆
0x43400…43500 (67, 0, 4) Sector 43051c00196141 ┆C aA .............. ndes ikke Flyt positions-viser Funktion annulleret Ukendt kommando JA eller ANNULLER Kun tal Kun mellemrum eller retur Under redigering nu Ukendt dokument Fundet I brug nu Allerede p> systemdiskette ┆
0x43500…43600 (67, 0, 5) Sector 4306ff00196141 ┆C aA 1 4.2.4.4.6 TP Internal Command Module ..... 4.2.4.4.6.1 Functional Specifica┆
0x43600…43700 (67, 0, 6) Sector 4307ff00196141 ┆C aAtion ... 4.2.4.4.6.2 Module Interface ........... 4.2.4.4.6.3 Module Components .......... 4.2.4.4.6.4 Data Description ........... 4.2.4.4.6.5 Module Design .............. 4.2.4.4.7 NT Internal┆
0x43700…43800 (67, 0, 7) Sector 4208ff00196141 ┆B aA Command Module ..... 4.2.4.4.7.1 Functional Specification ... 4.2.4.4.7.2 Module Interface ........... 4.2.4.4.7.3 Module Components .......... 4.2.4.4.7.4 Data Description ........... 4.2.4.4.┆
0x43800…43900 (67, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(67,0, 9), len=0xff, h3=41196141}, f00=»1961A «, f01=»CPS/SDS/033 «, f02=»BLP «, f03=»pan «, f04=»Fra kap. 4.2.4.4.5 «, f05=31-03-82 14:25, f06=» 13 «, f07=»42 «, f08=» 33845 «, f09=28-03-84 13:28, f10=» «, f11=»00 «, f12=» 14 «, f13=28-03-84 12:37, f14=28-03-84 13:48, f15=»0151A «, f16=» 88 «, f17=» 22 «, f18=»39 «, f19=» 1232 «, f20=» 63906 «, f21=» «, f22=» «, f99=020010000110052710110380aa8a37040000000000000142036301df}
0x43900…43a00 (67, 0, 9) Sector 430a5800196141 ┆C X aA C C C B A A A @ @ @ @ @ ? ? 6 6 6 6 6 5 5 5 5 4 4 4 4 4 3 3 3 3 2 2 2 2 2 1 1 1 1 1 0 0 0 / / / / / / . . . . . - - - - , , , , + + + * * * * * * ) ) ) ) ) ( ( ( ( ' ' ' & & & & 7)7.z.:*:(. z"z&y"G, ' y%x( C ! Gx&w*w%w'v*I&I$ . : 5 7 7 8 8┆
0x43a00…43b00 (67, 0, 10) Sector 430bab00196141 ┆C + aA 1 CPS/SDS/033 831101 TRAFFIC HANDLING DETAILED DESIGN SPECIFICATION ISSUE 1 CAMPS &*/=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 430cff00196141 ┆C aA 1 1 4.2.4.3 Data Flow a┆
0x43c00…43d00 (67, 0, 12) Sector 430dff00196141 ┆C aAnd Control Logic ........ 4.2.4.3.1 Commands from Channel Command Queue .......................... 4.2.4.3.2 Transport Control Masks ........ 4.2.4.3.3 Start Up Procedure ............. 4.2.4.3.4 Stop┆
0x43d00…43e00 (67, 0, 13) Sector 430eff00196141 ┆C aA Procedure ................. 4.2.4.4 Module Specification ............... 4.2.4.4.1 TP Traffic Status Control ...... 4.2.4.4.1.1 Functional Specification ... 4.2.4.4.1.2 Module Interface ........... ┆
0x43e00…43f00 (67, 0, 14) Sector 430fff00196141 ┆C aA 4.2.4.4.1.3 Module Components .......... 4.2.4.4.1.4 Data Description ........... 4.2.4.4.1.5 Module Design .............. 4.2.4.4.2 NT Traffic Status Control ...... 4.2.4.4.2.1 Functional Specification┆
0x43f00…44000 (67, 0, 15) Sector 4300ff00196141 ┆C aA ... 4.2.4.4.2.2 Module Interface ........... 4.2.4.4.2.3 Module Components .......... 4.2.4.4.2.4 Data Description ........... 4.2.4.4.2.5 Module Design .............. 4.2.4.4.3 SC Traffic Stat┆
0x44000…44100 (68, 0, 0) Sector 4401ff00194141 ┆D AAFER : ARRAY (1..MAX TP INP BUF) OF TP INP IOC BUFFER OUT IOC BUFFER : ARRAY (1..MAX TP OUT BUF) OF TP OUT IOC BUFFER PENDING ASM TABLE : ARRAY (1..MAX TP PENDING ASM) OF TRS ASM WAITING TYPE TIMER TABLE : ARRAY (TP TRS TIMER TYPE) OF TRS TIMER ┆
0x44100…44200 (68, 0, 1) Sector 4402ff00194141 ┆D AAFLASH TABLE : ARRAY (1..MAX TP FLASH) OF TRS FLASH TIMER TIMER PROFILE : TRS TIMER PROFILE SYS PARAMS : TRC PTOP PARAMETER TYPE QEL ATTRIBUTES POOL : ARRAY (1..NO OF TP QEL ATTRIBUTES) OF QEL ATTRIBUTES CHN PROFILE : CHANNEL PROFILE CHANNEL STA┆
0x44200…44300 (68, 0, 2) Sector 4403ff00194141 ┆D AATE : ACP 127 CHANNEL STATUS CIR PROFILE : CIRCUIT PROFILE OUT FIELD LIST : TRS OUT FIELD LIST TYPE INP FIELD LIST : TRS INP FIELD LIST TYPE OUT ACP PARAM : TRS OUT ACP PARAM TYPE INP ACP PARAM : TRS INP ACP PARAM TYPE TRS TMP PARAM : TRS TMP T┆
0x44300…44400 (68, 0, 3) Sector 44043200194141 ┆D 2 AAYPE END DATA RECORD FOR TRC/POINT TO POINT K POINTER TO TIMER TABLE R3 C K POINER TO FLASH TABLE R4 C K POINTER TO TIMER PROFILE R6) C D LINK The procedure will initialize the timer profile with the parameters specified in R0-R3. Data structu┆
0x44400…44500 (68, 0, 4) Sector 4405ff00194141 ┆D AA 1 4.2.3.5.3 Data Record for NICS TARE Subprocess TRS NT DATA = RECORD 1 TRP : TRANSPORT PARAMTERS; COROUTINE POOL┆
0x44500…44600 (68, 0, 5) Sector 4406ff00194141 ┆D AA : ARRAY (1..NO OF NT COROUTINES) OF TRS COROUTINE DESCRIPTION SEMAPHORE POOL : ARRAY (1..NO OF NT SEMAPHORES) OF COROUTINE SEMAPHORE OP POOL POOL : ARRAY (1..NO OF NT OP POOLS) OF TRS OP POOL TYPE OPERATION BUFFER : ARRAY (1..NO OF NT OPERATION┆
0x44600…44700 (68, 0, 6) Sector 4407ff00194141 ┆D AAS) OF TRS OPERATION INP IOC OPERATION : ARRAY (1..MAX NT INP BUF) OF TRS IOC OPERATION OUT IOC OPERATION : ARRAY (1..MAX NT OUT BUF) OF TRS IOC OPERATION INP EMF BUFFER : NT INP EMF BUFFER OUT EMF BUFFER : NT OUT EMF BUFFER INP IOC BUFFER : ARR┆
0x44700…44800 (68, 0, 7) Sector 2500ff00194141 ┆% AAAY (1..MAX NT INP BUF) OF NT INP IOC BUFFER OUT IOC BUFFER : ARRAY (1..MAX NT OUT BUF) OF NT OUT IOC BUFFER PENDING ASM TABLE : ARRAY (1..MAX NT PENDING ASM) OF TRS ASM WAITING TYPE TIMER TABLE : ARRAY (NT TRS TIMER TYPE) OF TRS TIMER FLASH TAB┆
0x44800…44900 (68, 0, 8) Sector 4409ff00194141 ┆D AAthe following data records: TRS TP DATA : (TRC/P TO P) TRS NT DATA : (NICS TARE) TRS SC DATA : (SCARS/CCIS) TRS PTP DATA : (PTP) TRS PTR DATA : (PTR) TRS OCR DATA : (OCR) All data records include the entry "TRANSPORT PARAM┆
0x44900…44a00 (68, 0, 9) Sector 440aff00194141 ┆D AAETERS". The other fields are of different type from record to record. The TRANSPORT PARAMETERS are initialized with reference to the other fields of the data record. All coroutines within a transport subprocess are reentrant and access the data ┆
0x44a00…44b00 (68, 0, 10) Sector 440bff00194141 ┆D AArecord by impressing the TRANSPORT PARAMETERS on a specific address inserted into the Coroutine Descriptions during the initialization. When a coroutine is active, the address of its Coroutine Description is stored into the external variable "RUNN┆
0x44b00…44c00 (68, 0, 11) Sector 440c5900194141 ┆D Y AAING COROUTINE" which is updated by CSF Coroutine Monitor. (ref.fig.4.2.3.7.1-1). BPROCESS ID R6) C D LINK This procedure initializes the CSF COROUTINE MONITOR and inserts the coroutines related to a PTR subprocess into the ready list. (See data┆
0x44c00…44d00 (68, 0, 12) Sector 440d8f00194141 ┆D AA 1 FIGURE 4.2.3.5.1-1 R6) C D LINK This procedure initializes the CSF COROUTINE MONITOR and inserts the coroutines related to a OCR┆
0x44d00…44e00 (68, 0, 13) Sector 440eff00194141 ┆D AA 1 4.2.3.5.2 Data Record for TRC/POINT TO POINT Subprocess TRS TP DATA = RECORD 1 TRP : TRANSPORT PARAMTERS; COROU┆
0x44e00…44f00 (68, 0, 14) Sector 440fff00194141 ┆D AATINE POOL : ARRAY (1..NO OF TP COROUTINES) OF TRS COROUTINE DESCRIPTION SEMAPHORE POOL : ARRAY (1..NO OF TP SEMAPHORES) OF COROUTINE SEMAPHORE OP POOL POOL : ARRAY (1..NO OF TP OP POOLS) OF TRS OP POOL TYPE OPERATION BUFFER : ARRAY (1..NO OF TP ┆
0x44f00…45000 (68, 0, 15) Sector 4400ff00194141 ┆D AAOPERATIONS) OF TRS OPERATION INP IOC OPERATION : ARRAY (1..MAX TP INP BUF) OF TRS IOC OPERATION OUT IOC OPERATION : ARRAY (1..MAX TP OUT BUF) OF TRS IOC OPERATION INP EMF BUFFER : TP INP EMF BUFFER OUT EMF BUFFER : TP OUT EMF BUFFER INP IOC BUF┆
0x45000…45100 (69, 0, 0) Sector 4501ff00194141 ┆E AA 1 Procedure INIT IOC POOL (R0 C D BUFFER SIZE (WORDS) R1 C D NO. OF BUFFERS (OPERATIONS) R2 C D POINTER TO BUFFER POOL R4 C D POINTER TO XXX IOC POOL R5 C D POINTER TO IOC OPER┆
0x45100…45200 (69, 0, 1) Sector 4502ff00194141 ┆E AAATION POOL R6) C D LINK The procedure is used for inserting a number of TRS IOC OPERATIONS into the INP IOC POOL and the OUT IOC POOL during the initialization of a transport process. Before inserting of the TRS IOC OPERATION this is supplied w┆
0x45200…45300 (69, 0, 2) Sector 4503ff00194141 ┆E AAith a pointer to a buffer used for the communication with the IOS system. From now on this buffer is always related to the operation. Data structure defiend in section 4.2.3.5.7.6 and 4.2.3.5.7.2. Procedure INIT TRS TIMER PROFILE (R0 C K NO. OF ┆
0x45300…45400 (69, 0, 3) Sector 4504ff00194141 ┆E AATRS TIMERS R1 C K NO. OF FLASH TIMERS R2 C K POINTER TO TIMER TABLE R3 C K POINER TO FLASH TABLE R4 C K POINTER TO TIMER PROFILE R6) C D LINK The procedure will initialize the timer profile with the parameters specified in R0-R3. Data structu┆
0x45400…45500 (69, 0, 4) Sector 4505dd00194141 ┆E ] AAre defined in section 4.2.3.5.7.7. Procedure RESET DATA RECORD (R1 C D NUMBER OF WORDS TO BE RESET R4 C D POINTER TO RECORD START R6) C D LINK This procedure will reset all the words of a specified record. OCR subprocess by inserting pointe┆
0x45500…45600 (69, 0, 5) Sector 4506ff00194141 ┆E AA 1 4.2.3.5 Transport Process Data 1 4.2.3.5.1 Introduction The data area for a Transport Process may be divided int┆
0x45600…45700 (69, 0, 6) Sector 4507ff00194141 ┆E AAo two mainparts (see figure 4.2.3.5.1-1). a) Common Process Data Contains variables, constants and strings declared within the program modules for a transport process. This area is common to all subprocesses within the process and has the same ┆
0x45700…45800 (69, 0, 7) Sector 4408ff00194141 ┆D AAstructure for all types of transport. b) Array of subprocess data records defined for the type of transport which are to be controlled by the process. XX PROC DATA ARRAY (1..MAX XX PR PROCESS) OF TRS XX DATA with TRS XX DATA equal to one of ┆
0x45800…45900 (69, 0, 8) Sector 4509ff00194141 ┆E AA.1). Procedure INIT SC COROUTINES (R0 C K POINTER TO POOL OF COROUTINE RECORDS R2 C K SUBPROCESS ID R6) C D LINK This procedure initializes the CSF COROUTINE MONITOR and inserts the coroutines related to a SCARS/CCIS subprocess into the read┆
0x45900…45a00 (69, 0, 9) Sector 450aaf00194141 ┆E / AAy list. (See data structure in section 4.2.3.5.7.1). Procedure INIT PTP COROUTINES (R0 C K POINTER TO POOL OF COROUTINE RECORDS R2 C K SUBPROCESS ID R6) C D LINK process with as many subproceses as indicated in SUBPROCESS CNT stored in TRS IN┆
0x45a00…45b00 (69, 0, 10) Sector 450bff00194141 ┆E AA 1 This procedure initializes the CSF COROUTINE MONITOR and inserts the coroutines related to a PTP subprocess into the ready list. (See data structure in section 4.2.3.5.7.1). Proc┆
0x45b00…45c00 (69, 0, 11) Sector 450cff00194141 ┆E AAedure INIT PTR COROUTINES (R0 C K POINTER TO POOL OF COROUTINE RECORDS R2 C K SUBPROCESS ID R6) C D LINK This procedure initializes the CSF COROUTINE MONITOR and inserts the coroutines related to a PTR subprocess into the ready list. (See data┆
0x45c00…45d00 (69, 0, 12) Sector 450dff00194141 ┆E AA structure in section 4.2.3.5.7.1). Procedure INIT OCR COROUTINES (R0 C K POINTER TO POOL OF COROUTINE RECORDS R2 C K SUBPROCESS ID R6) C D LINK This procedure initializes the CSF COROUTINE MONITOR and inserts the coroutines related to a OCR┆
0x45d00…45e00 (69, 0, 13) Sector 450eff00194141 ┆E AA subprocess into the ready list. (See data structure in section 4.2.3.5.7.1). Procedure INIT TRS SEMAPHORES (R1 C D NO. OF SEMAPHORES R4 C D POINTER TO SEMAPHORE POOL R6) C D LINK The procedure will initialize a specified number of semaphore┆
0x45e00…45f00 (69, 0, 14) Sector 450fff00194141 ┆E AAs collected in a pool. Procedure INIT TRS OP POOL (R1 C D NO. OF OPERATIONS R4 C D POINTER TO TRS OP POOL R5 C D POINTER TO OPERATION POOL R6 C D LINK This procedure will insert a specified number of operations into the TRS OP POOL. Data st┆
0x45f00…46000 (69, 0, 15) Sector 45003f00194141 ┆E ? AAructure defined in section 4.2.3.5.7.6 and 4.2.3.5.7.2. s data record (i.e. TRS NT DATA). See datastructures defined in sect. 4.2.3.5.3 and 4.2.3.5.7.10. Procedure INIT SC DATA (R5 C K POINTER TO SUBPROCESS DATA RECORD R6) C D LINK This proc┆
0x46000…46100 (70, 0, 0) Sector 4601ff00194141 ┆F AAedure will initialize the TRANSPORT PARAMETERS for a SCARS/CCIS subprocess by inserting pointers (references) to the other fields of the subprocess data record (i.e. TRS SC DATA). See datastructures defined in sect. 4.2.3.5.4 and 4.2.3.5.7.10. Pro┆
0x46100…46200 (70, 0, 1) Sector 4602ff00194141 ┆F AAcedure INIT PTP DATA (R5 C K POINTER TO SUBPROCESS DATA RECORD R6) C D LINK This procedure will initialize the TRANSPORT PARAMETERS for a PTP subprocess by inserting pointers (references) to the other fields of the subprocess data record (i.e. ┆
0x46200…46300 (70, 0, 2) Sector 4603ff00194141 ┆F AATRS SC DATA). See datastructures defined in sect. 4.2.3.5.5 and 4.2.3.5.7.10. Procedure INIT PTR DATA (R5 C K POINTER TO SUBPROCESS DATA RECORD R6) C D LINK This procedure will initialize the TRANSPORT PARAMETERS for a PTR subprocess by inser┆
0x46300…46400 (70, 0, 3) Sector 4604a800194141 ┆F ( AAting pointers (references) to the other fields of the subprocess data record (i.e. TRS SC DATA). See datastructures defined in sect. 4.2.3.5.6 and 4.2.3.5.7.10. TP TC COROUTINE END CASE END TRANSPORT START FLOWGRAM 4.2.3.4.1.5-1 e initi┆
0x46400…46500 (70, 0, 4) Sector 4605ff00194141 ┆F AA 1 Procedure INIT OCR DATA (R5 C K POINTER TO SUBPROCESS DATA RECORD R6) C D LINK This procedure will initialize the TRANSPORT PARAMETERS for a OCR subprocess by inserting pointe┆
0x46500…46600 (70, 0, 5) Sector 4606ff00194141 ┆F AArs (references) to the other fields of the subprocess data record (i.e. TRS SC DATA). See datastructures defined in sect. 4.2.3.5.6a and 4.2.3.5.7.10. Procedure INIT TP COROUTINES (R0 C K POINTER TO POOL OF COROUTINE RECORDS R2 C K SUBPROCESS I┆
0x46600…46700 (70, 0, 6) Sector 4607ff00194141 ┆F AAD R6) C D LINK This procedure initializes the CSF COROUTINE MONITOR and inserts the coroutines related to a TRC/POINT TO POINT subprocess into the ready list. (See data structure in section 4.2.3.5.7.1). Procedure INIT NT COROUTINES (R0 C K P┆
0x46700…46800 (70, 0, 7) Sector 4508ff00194141 ┆E AAOINTER TO POOL OF COROUTINE RECORDS R2 C K SUBPROCESS ID R6) C D LINK This procedure initializes the CSF COROUTINE MONITOR and inserts the coroutines related to a NICS TARE subprocess into the ready list. (See data structure in section 4.2.3.5.7┆
0x46800…46900 (70, 0, 8) Sector 46099f00194141 ┆F AALINK This procedure will initialize a NICS TARE Transport process with as many subprocesses as indicated in SUBPROCESS CNT stored in TRS INIT PARAMS. rd for each type of transport is defined in sec. 4.2.3.5. b) Presenting a coroutine descriptio┆
0x46900…46a00 (70, 0, 9) Sector 460aff00194141 ┆F AA 1 Procedure INIT SC TRANSPORT (R6) C D LINK This procedure will initialize a SCARS/CCIS transport process with as many subproceses as indicated in SUBPROCESS CNT stored in TRS IN┆
0x46a00…46b00 (70, 0, 10) Sector 460bff00194141 ┆F AAIT PARAMS. Procedure INIT PTP TRANSPORT (R6) C D LINK This procedure will initialize a PTP transport process with as many subprocesses as indicated in SUBPROCESS CNT stored in TRS INIT PARAMS. Procedure INIT PTR TRANSPORT (R6) C D LINK T┆
0x46b00…46c00 (70, 0, 11) Sector 460cff00194141 ┆F AAhis procedure will initialize a PTR transport process with as many subprocesses as indicated in SUBPROCESS CNT stored in TRS INIT PARAMS. Procedure INIT OCR TRANSPORT (R6) C D LINK This procedure will initialize a OCR transport process with as┆
0x46c00…46d00 (70, 0, 12) Sector 460dff00194141 ┆F AA many subprocesses as indicated in SUBPROCESS CNT stored in TRS INIT PARAMS. Procedure INIT TP DATA (R5 C K POINTER TO SUBPROCESS DATA RECORD R6) C D LINK This procedure will initialize the TRANSPORT PARAMETERS for a TRC/POINT TO POINT subpro┆
0x46d00…46e00 (70, 0, 13) Sector 460eb500194141 ┆F 5 AAcess by inserting pointers (references) to the other fields of the Subprocess data record (i.e. TRS TP DATA). See datastructures defined in sect. 4.2.3.5.2 and 4.2.3.5.7.10. nents of the Transport Init Module are shown on figure 4.2.3.4.1.3-1. No┆
0x46e00…46f00 (70, 0, 14) Sector 460fff00194141 ┆F AA 1 Procedure INIT NT DATA (R5 C K POINTER TO SUBPROCESS DATA RECORD R6) C D LINK This procedure will initialize the TRANSPORT PARAMETERS for a NICS TARE subprocess by inserting p┆
0x46f00…47000 (70, 0, 15) Sector 4600ff00194141 ┆F AAointers (references) to the other fields of the subprocess data record (i.e. TRS NT DATA). See datastructures defined in sect. 4.2.3.5.3 and 4.2.3.5.7.10. Procedure INIT SC DATA (R5 C K POINTER TO SUBPROCESS DATA RECORD R6) C D LINK This proc┆
0x47000…47100 (71, 0, 0) Sector 47019900194141 ┆G AA 4.2.3.4.1.4 Module Design The procedures within the Transport Init Module are implemented with a design as given by the flowgram 4.2.3.4.1.5-1 ication takes place. The TRS OP POOL semaphore contains those of the operations which at a certain m┆
0x47100…47200 (71, 0, 1) Sector 4702ff00194141 ┆G AA 1 MAINMODULE TRANSPORT START TRANSPORT START (PROCESS TYPE, FIRST SUBPROCESS NO, NO OF SUBPROCESSES) END TRANSPORT PROCEDURE TRANSPORT START (PROCESS TYPE, FIRST ┆
0x47200…47300 (71, 0, 2) Sector 4703ff00194141 ┆G AASUBPROCESS NO, NO OF SUBPROCESSES) START PRE INITIALIZATION INIT TRANSPORT PROCESS (PROCESS TYPE, FIRST SUBPROCESS NO, NO OF SUBPROCESSES) CASE PROCESS TYPE 1 OC┆
0x47300…47400 (71, 0, 3) Sector 4704f800194141 ┆G x AAR S ? OCR TC COROUTINE PTR S ? PTR TC COROUTINE PTP S ? PTP TC COROUTINE NICS TARE S ? NT TC COROUTINE SCARS CCIS S ? SC TC COROUTINE TRC PTOP S ? TP TC COROUTINE END CASE END TRANSPORT START FLOWGRAM 4.2.3.4.1.5-1 e initi┆
0x47400…47500 (71, 0, 4) Sector 4705ff00194141 ┆G AA 1 Module Procedures: Procedure TRANSPORT START (R0 D R1 C D SUBPROCESS TYPE R2 C D FIRST SUBPROCESS NO R3 C D NO OF SUBPROCESSES R4 D R7 D INF FOR PREINITIALIZATION R6)┆
0x47500…47600 (71, 0, 5) Sector 4706ff00194141 ┆G AA C D LINK This procedure is called from the TRANSPORT MAIN MODULE and activates initialization of the specified transprot process. After initialization the procedure jumps to the first Coroutine inserted into the READY LIST of the CSF COROUTINE ┆
0x47600…47700 (71, 0, 6) Sector 4707ff00194141 ┆G AAMONITOR. Procedure INIT TRANSPORT PROCESS (R0 C D BOOLEAN "TYPE OF INIT" R1 C D SUBPROCESS TYPE R2 C D FIRST SUBPROCESS NO R3 C D NO OF SUBPROCESSES R6) C D LINK This procedure branch to the type of initialization related to the subprocess┆
0x47700…47800 (71, 0, 7) Sector 4608ff00194141 ┆F AA type. Procedure INIT TP TRANSPORT (R6) C D LINK This procedure will initialize a TRC/POINT TO POINT transport process with as many subproceses as indicated in SUBPROCESS CNT stored in TRS INIT PARAMS. Procedure INIT NT TRANSPORT (R6) C D ┆
0x47800…47900 (71, 0, 8) Sector 4709ff00194141 ┆G AAwing main tasks are included: a) Setting up a data record for each subprocess within the process. (See figure 4.2.3.5.1-1). The subprocess data record for each type of transport is defined in sec. 4.2.3.5. b) Presenting a coroutine descriptio┆
0x47900…47a00 (71, 0, 9) Sector 470aff00194141 ┆G AAn to CSF Coroutine Monitor for each coroutine within a subprocess. c) Handing over the running of coroutines to the Coroutine Monitor. 4.2.3.4.1.2 Module Interface Register Convention for Mainmodule Before the mainmodule "TRANSPORT" is ente┆
0x47a00…47b00 (71, 0, 10) Sector 470bff00194141 ┆G AAred the "Parent Process" shall specify the Transport Process by means of the following register conventions: R0: START UP ACTIVE TYPE "Global Type" R1: PROCESS TYPE "Global Type" R2: FIRST-SUBPROCESS NO ┆
0x47b00…47c00 (71, 0, 11) Sector 470c8700194141 ┆G AA"Global Constant" R3: NO OF SUBPROCESSES The mainmodule only contains one statement which calls the "Transport Init Module". to OT OPSEM indicating that a message is ready for transmission. The OT COROUTINE will pack the message lines into a b┆
0x47c00…47d00 (71, 0, 12) Sector 470dff00194141 ┆G AA 1 Call Specification a) TRANSPORT START (PROCESS TYPE, FIRST SUBPROCESS NO, NO OF SUBPROCESSES) b) TRANSPORT START (R0, R1, R2, R3, R4, R7, R6) Register Convention for TRANSPOR┆
0x47d00…47e00 (71, 0, 13) Sector 470eff00194141 ┆G AAT START Call Registers As for mainmodule (see above). Return Registers Undefined. (No return is made from TRANSPORT START. 4.2.3.4.1.3 Module Components The components of the Transport Init Module are shown on figure 4.2.3.4.1.3-1. No┆
0x47e00…47f00 (71, 0, 14) Sector 470fff00194141 ┆G AAte that the procedure PRE INITIALIZATION is an external procedure required by COPSY. 4.2.3.4.1.4 Data Description The Transport Init Module makes use of the following data type for the purpose of initialization: 1 ┆
0x47f00…48000 (71, 0, 15) Sector 4700ff00194141 ┆G AA TRS INIT PARAMS = RECORD TRANSPORT TYPE :INTEGER SUBPROCESS TYPE :INTEGER SUBPROCESS DATA PNT :INTEGER SUBPROCESS CNT :INTEGER SUBPROCESS ID :INTEGER INIT TRS COMON :BOOLEAN INTI TYPE :BOOLEAN END┆
0x48000…48100 (72, 0, 0) Sector 4801ff00194141 ┆H AAnsport Subprocess Operation Pools A transport subprocess is supplied with a specified maximum of operations by means of which the internal communication takes place. The TRS OP POOL semaphore contains those of the operations which at a certain m┆
0x48100…48200 (72, 0, 1) Sector 4802d900194141 ┆H Y AAoment are not being used in the internal communication, i.e. the idle operations. A coroutine takes out (receives) an idle operation from the TRS OP POOL each time a message is to be sent to another coroutine have been introduced with the followin┆
0x48200…48300 (72, 0, 2) Sector 4803ff00194141 ┆H AA 1 An operation received from another coroutine is returned to the TRS OP POOL when the information has been saved or decoded. Operations used for communication with IOS are stored ┆
0x48300…48400 (72, 0, 3) Sector 4804ff00194141 ┆H AAin IOC OUT POOL and IOC INP POOL. These operations are connected to a specific buffer structure required for transmitting/receiving a message through IOS. The pools simplify the reservation of buffer structures. The pools mentioned above are initi┆
0x48400…48500 (72, 0, 4) Sector 48053b00194141 ┆H ; AAalized with operations by the Transport Init Module. Send and receive functions related to semaphores are performed by means of procedures defined within the CSF Coroutine Monitor. A detailed description of semaphore operations for┆
0x48500…48600 (72, 0, 5) Sector 48068200194141 ┆H AA 1 Internal communication Figure 4.2.3.3-1 til 6. PSEM The main waiting point for the Transport Control Coroutine (TC COROUTINE) is the TC OPSEM semaphore. From here the ┆
0x48600…48700 (72, 0, 6) Sector 4807ff00194141 ┆H AA 1 4.2.3.4 Module Specification 4.2.3.4.1 Transport Init Module 4.2.3.4.1.1 Functional Specification The Transport Init Module is called from the mainmodule "TRANSPORT" which c┆
0x48700…48800 (72, 0, 7) Sector 4708ff00194141 ┆G AAontains the first statement to be executed when a Transport Process has been created. The Transport Init Module will initialize a Transport Process with the type of transport(s) which are specified by the "Parent Process" (i.e. COPSY). The follo┆
0x48800…48900 (72, 0, 8) Sector 4809ff00194141 ┆H AA2 Outgoing Transport Operation Semaphore, OT OPSEM The main waiting point for the Outgoing Transport Coroutine (OT COROUTINE) is the OT OPSEM semaphore. From here the OT COROUTINE may receive operations from the Transport Control Coroutine (TC ┆
0x48900…48a00 (72, 0, 9) Sector 480aff00194141 ┆H AACOROUTINE). This makes it possible for the TC COROUTINE to interfere with the outgoing transport. The outgoing messages to be transmitted on the external channel are received from the circuit Queue (CIQ) through the OT OPSEM. In this case the OT C┆
0x48a00…48b00 (72, 0, 10) Sector 480b6d00194141 ┆H m AAOROUTINE first initiates a System Call (RECEIVE FIRST QEL) and then associates the answer to OT OPSEM. The Subprocess Data Record defines all data structures necessary to support the coroutines within a subprocess. The Transport Subprocess Data Mo┆
0x48b00…48c00 (72, 0, 11) Sector 480cff00194141 ┆H AA 1 When a message is available in the CIQ an operation is sent to OT OPSEM indicating that a message is ready for transmission. The OT COROUTINE will pack the message lines into a b┆
0x48c00…48d00 (72, 0, 12) Sector 480dff00194141 ┆H AAuffer which is sent to the IOS for outgoing transmission. This is done by initiating a System Call (APPEND BYTES) and associating the answer to OT OPSEM. When the IOS has emptied the buffer an operation is sent to OT OPSEM telling the OT COROUTINE┆
0x48d00…48e00 (72, 0, 13) Sector 480eff00194141 ┆H AA that the buffer is idle. 4.2.3.3.2.3 Incoming Transport Operation Semaphore, IT OPSEM The main waiting point for the Incoming Transport Coroutine (IT COROUTINE) is the IT OPSEM semaphore. From here the IT COROUTINE may receive commands from t┆
0x48e00…48f00 (72, 0, 14) Sector 480fff00194141 ┆H AAhe Transport Control Coroutine (TC COROUTINE). This makes it possible for the TC COROUTINE to interfere with the incoming transport. The incoming messages from the IOS are also received through IT OPSEM. In this case the IT COROUTINE initiates a S┆
0x48f00…49000 (72, 0, 15) Sector 4800ff00194141 ┆H AAystem Call (READ BYTES) and associates the answer to IT OPSEM. When the IOS has filled out a buffer with characters from the external line, an operation will be sent to IT OPSEM, telling the IT COROUTINE that the buffer is ready. 4.2.3.3.2.4 Tra┆
0x49000…49100 (73, 0, 0) Sector 4901ff00194141 ┆I AAdy List of the Coroutine Monitor. The coroutines within a subprocess exchange information to synchronize the transport (ref. 4.2.3.3.2). Note however that the subprocesses within a transport process is independent of each other. 4.2.3.3.2 Inter┆
0x49100…49200 (73, 0, 1) Sector 4902ff00194141 ┆I AAnal Communication The communication logic within a Transport Subprocess is realized by means of semaphores through which the coroutines exchange operations. To create a Transport Subprocess three semaphores have been introduced with the followin┆
0x49200…49300 (73, 0, 2) Sector 4903ff00194141 ┆I AAg type definitions: Type TC OPSEM: COROUTINE SEMAPHORE OT OPSEM: COROUTINE SEMAPHORE IT OPSEM: COROUTINE SEMAPHORE The configurations of semaphores and coroutines are shown on figure 4.2.3.3.-1 ro 4.2.3.3.-5 for each type of Transport Subp┆
0x49300…49400 (73, 0, 3) Sector 49040f00194141 ┆I AArocess. es specific for the type of process to let them run under control of the Coroutine Monitor. c) Starting up the Coroutine Monitor. ng independently of the others. The Transport Control has its own subpackage "Transport Control Subpackage┆
0x49400…49500 (73, 0, 4) Sector 4905ff00194141 ┆I AA 1 Send and receive functions related to semaphores are performed by means of procedures defined within the CSF Coroutine Monitor. A detailed description of semaphore operations for┆
0x49500…49600 (73, 0, 5) Sector 4906ff00194141 ┆I AA all types of Transport Subprocesses is given in section 4.2.3.7. 4.2.3.3.2.1 Transport Control Operation Semaphore, TC OPSEM The main waiting point for the Transport Control Coroutine (TC COROUTINE) is the TC OPSEM semaphore. From here the ┆
0x49600…49700 (73, 0, 6) Sector 4907ff00194141 ┆I AATC COROUTINE may receive operations from the Outgoing Transport Coroutine (OT COROUTINE) or the Incoming Transport Coroutine (IT COROUTINE). Commands from the Channel Command Queue (CCQ) are also received through the TC OPSEM. In this case the TC ┆
0x49700…49800 (73, 0, 7) Sector 4808ff00194141 ┆H AACOROUTINE first initiates a System Call (RECEIVE FIRST QEL) and then associates the answer to the TC OPSEM. When a command is available in the CCQ an operation is sent to the TC OPSEM telling the TC-COROUTINE that a command is ready. 4.2.3.3.2.┆
0x49800…49900 (73, 0, 8) Sector 4909ff00194141 ┆I AA5). 4.2.3.2.5 Incoming Transport Coroutine The Incoming Transport Coroutine is responsible for all functions related to the incoming transport of a single Transport Subprocess. A specific Incoming Transport Coroutine is supplied for each type o┆
0x49900…49a00 (73, 0, 9) Sector 490a8b00194141 ┆I AAf transport except for the PTP. Each of these coroutines is described in the Incoming Transport Subpackage (see section 4.2.6). ine/device. The Outgoing Transport appends a number of lines such as: start of message, text separators, end of me┆
0x49a00…49b00 (73, 0, 10) Sector 490bff00194141 ┆I AA 1 4.2.3.2.6 Subprocess Data Record The Subprocess Data Record defines all data structures necessary to support the coroutines within a subprocess. The Transport Subprocess Data Mo┆
0x49b00…49c00 (73, 0, 11) Sector 490cc600194141 ┆I F AAdule includes definition of a specific data record for each type of Transport (see section 4.2.3.5). All Data Records within a Transport Process is initialized by the Transport Init module. pplies the functions which are necessary to initialize a ┆
0x49c00…49d00 (73, 0, 12) Sector 490d6700194141 ┆I g AA 1 Figure 4.2.3.2-1 til -6 TRANSPORT PROCESS Figure 4.2.3.1.2-1 the Transport Subpackage also serves the purpose of giving an overview of a Transport Process concern┆
0x49d00…49e00 (73, 0, 13) Sector 490eff00194141 ┆I AA 1 4.2.3.3 Data Flow and Control Logic 4.2.3.3.1 Dynamical Program Structure When a transport process is created it will first execute the procedures supplied by the Transport Ini┆
0x49e00…49f00 (73, 0, 14) Sector 490fff00194141 ┆I AAt module. Hereby the process is divided into a number of subprocesses corresponding the number of channels/devices, which are to be controlled by the process. For each subprocess a specific number of coroutines are presented to the Coroutine Mon┆
0x49f00…4a000 (73, 0, 15) Sector 4900ff00194141 ┆I AAitor (i.e. inserted in the Ready List). When the Transport Init procedures are all executed the program control is handed over to the Coroutine Monitor. From now on all coroutines within the process are executed in the order they appear in the Rea┆
0x4a000…4a100 (74, 0, 0) Sector 4a01ff00194141 ┆J AAc set of coroutines for each type of Transport Process. During the initialization of a Transport Process only the set of coroutines related to the actual type of Transport is presented to the Coroutine Monitor. Each coroutine is constructed as a r┆
0x4a100…4a200 (74, 0, 1) Sector 4a02ff00194141 ┆J AAeentrant procedure. This makes it possible for all subprocess within a Transport Process to share the same code minimizing the resources of memory. 4.2.3.2.1 Transport Init The purpose of the Transport Init module is to initialize a Transport P┆
0x4a200…4a300 (74, 0, 2) Sector 4a03ff00194141 ┆J AArocess with the number of subprocesses prescribed by the creating process, i.e. the "Parent Process". The initializing includes the following maintasks: a) Init. of the data structure for each subprocess. b) Setting up each subprocess with the┆
0x4a300…4a400 (74, 0, 3) Sector 4a049300194141 ┆J AA coroutines specific for the type of process to let them run under control of the Coroutine Monitor. c) Starting up the Coroutine Monitor. ng independently of the others. The Transport Control has its own subpackage "Transport Control Subpackage┆
0x4a400…4a500 (74, 0, 4) Sector 4a05ff00194141 ┆J AA 1 4.2.3.2.2 Transport Auxiliary Functions The Transport Auxiliary Functions include a number of procedures which are common to the Transport Control, Outgoing Transport and Incoming┆
0x4a500…4a600 (74, 0, 5) Sector 4a06ff00194141 ┆J AA Transport. 4.2.3.2.3 Transport Control Coroutine. The Transport Control Coroutine is responsible for all functions related to the Transport Control of a single Transport Subprocess. A specific Transport Control Coroutine is supplied for each t┆
0x4a600…4a700 (74, 0, 6) Sector 4a07ff00194141 ┆J AAype of Transport. Each of these coroutines is described in the Transport Control Subpackage (see section 4.2.4). 4.2.3.2.4 Outgoing Transport Coroutine The Outgoing Transport Coroutine is responsible for all functions related to the outgoing ┆
0x4a700…4a800 (74, 0, 7) Sector 4908ff00194141 ┆I AAtransport of a single Transport Subprocess. A specific Outgoing Transport Coroutine is supplied for each type of transport except for the PTR and the OCR. Each of these coroutines is described in the Outgoing Transport Subpackage (see section 4.2.┆
0x4a800…4a900 (74, 0, 8) Sector 4a09ff00194141 ┆J AArt Subpackage" (sec. 4.2.5) which gives a detailed description of the functions for each type of Transport. 4.2.3.1.6 Outgoing Transport The Outgoing Transport includes the functions which are closely related to the outgoing traffic. Outgoing┆
0x4a900…4aa00 (74, 0, 9) Sector 4a0aff00194141 ┆J AA messages are received from the circuit queue related to the subprocess and transferred to the IOS for transmission to the external line/device. The Outgoing Transport appends a number of lines such as: start of message, text separators, end of me┆
0x4aa00…4ab00 (74, 0, 10) Sector 4a0bff00194141 ┆J AAssage, page identification etc. (ref. sec. 4.2.6). The OTS may also generate and transmit Abbreviated Service Messages (ASM) specified by the Transport Control. The Outgoing Transport has its own subpackage "Outgoing Transport Subpackage" (sec.4┆
0x4ab00…4ac00 (74, 0, 11) Sector 4a0c3c00194141 ┆J < AA.2.6) which gives a detailed functional description. 4.2.3 TRANSPORT SUBPACKAGE 4.2.3.1 Functional Specification 4.2.3.1.1 Introduction The transport subpackage (TRS) supplies the functions which are necessary to initialize a ┆
0x4ac00…4ad00 (74, 0, 12) Sector 4a0d9900194141 ┆J AA 1 TRANSPORT PROCESS Figure 4.2.3.1.2-1 the Transport Subpackage also serves the purpose of giving an overview of a Transport Process concern┆
0x4ad00…4ae00 (74, 0, 13) Sector 4a0eff00194141 ┆J AA 1 4.2.3.2 Software Structure The basic unit in a Transport Process is a subprocess taking care of all functions related to an external channel or a stand alone devices (PTP/PTR/OCR)┆
0x4ae00…4af00 (74, 0, 14) Sector 4a0fff00194141 ┆J AA. When a Transport Process has been created it will start up a subprocess for each channel/device which is to be controlled by the process. This section describes the principle software structure related to a Transport Process. The basic compone┆
0x4af00…4b000 (74, 0, 15) Sector 4a00ff00194141 ┆J AAnts of the software structure are shown on figure 4.2.3.2-1 to 4.2.3.2-6. All functions within a Transport Subprocess are realized by means of coroutines running under control of the CSF Coroutine Monitor. The software is supplied with a specifi┆
0x4b000…4b100 (75, 0, 0) Sector 4b01ff00194141 ┆K AA 1 4.2.3.1.3 Transport Initialization When a Transport Process is created, the type of transport and the number of channels/devices to be controlled must be specified to the process.┆
0x4b100…4b200 (75, 0, 1) Sector 4b02ff00194141 ┆K AA The Transport Initialization includes all functions which are necessary to initialize Transport Control, Outgoing Transport and Incoming Transport in such a way that they support the specified type of transport. 4.2.3.1.4 Transport Control T┆
0x4b200…4b300 (75, 0, 2) Sector 4b03ff00194141 ┆K AAhe Transport Control takes care of the superior control functions concerning the outgoing and incoming transport. (START UP, CLOSE DOWN, Timer Functions etc.) The functions performed by Transport Control are initiated by commands received from ext┆
0x4b300…4b400 (75, 0, 3) Sector 4b04ff00194141 ┆K AAernal subpackages through a Channel Command Queue (CCQ). Each channel/device within a Transport Process has its own Transport Control working independently of the others. The Transport Control has its own subpackage "Transport Control Subpackage┆
0x4b400…4b500 (75, 0, 4) Sector 4b05ff00194141 ┆K AA" (Ref. 4.2.4), which supplies a detailed functional description 4.2.3.1.5 Incoming Transport The Incoming Transport includes the functions which transfer the messages from IOS to the Analysis Processes. A number of message lines are detected┆
0x4b500…4b600 (75, 0, 5) Sector 4b06ff00194141 ┆K AA in order to separate the message into the field groups which constitute the External Message Format of a CIF. Furthermore a number of error checks are performed. Parameters describing the message are collected and transferred to the Analysis to┆
0x4b600…4b700 (75, 0, 6) Sector 4b073200194141 ┆K 2 AAgether with the result of the error check. BLP 4.2.3,Traffic Handl. 30 03 82 10 55 29 05 77166 27 03 84 12 37 11 40 26498 30 03 84 08 27 30 03 84 10 29 0151A 102 51 04 1672 120019 ) ' * 7 B _┆
0x4b700…4b800 (75, 0, 7) Sector 4a08ff00194141 ┆J AA 1 Each channel/device within a Transport Process has its own Incoming Transport working independently of the others. The Incoming Transport has its own subpackage "Incoming Transpo┆
0x4b800…4b900 (75, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(75,0, 9), len=0xff, h3=41194141}, f00=»1941A «, f01=»CPS/SDS/033 «, f02=»bk «, f03=»BLP «, f04=»4.2.3,Traffic Handl. «, f05=30-03-82 10:55, f06=» 29 «, f07=»05 «, f08=» 77166 «, f09=27-03-84 12:37, f10=» 11 «, f11=»40 «, f12=» 26498 «, f13=30-03-84 08:27, f14=30-03-84 10:29, f15=»0151A «, f16=»102 «, f17=» 51 «, f18=»04 «, f19=» 1672 «, f20=»120019 «, f21=» «, f22=» «, f99=290000000100002710110380aa8a3704000000000000014203c201df}
0x4b900…4ba00 (75, 0, 9) Sector 4b0a6600194141 ┆K f AA/ K K K K J J J I I I I H H H H G G G F F F E E E D D D % # # " " " " " ! ! ┆
0x4ba00…4bb00 (75, 0, 10) Sector 4b0bab00194141 ┆K + AA 1 CPS/SDS/033 831101 TRAFFIC HANDLING DETAILED DESIGN SPECIFICATION ISSUE 1 CAMPS &*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x4bb00…4bc00 (75, 0, 11) Sector 4b0cff00194141 ┆K AA 1 4.2.3 TRANSPORT SUBPACKAGE 4.2.3.1 Functional Specification 4.2.3.1.1 Introduction The transport subpackage (TRS) supplies the functions which are necessary to initialize a ┆
0x4bc00…4bd00 (75, 0, 12) Sector 4b0dff00194141 ┆K AAspecified Transport Process. Furthermore it includes a number of auxiliary functions common to different parts of the Process. The description of the Transport Subpackage also serves the purpose of giving an overview of a Transport Process concern┆
0x4bd00…4be00 (75, 0, 13) Sector 4b0eff00194141 ┆K AAing Software Structure, Internal Communication and Data Structure. 4.2.3.1.2 Transport Process This section introduces the functions which support a Transport Process within CAMPS. Six types of Transport Processes are realized: - TRC/POINT ┆
0x4be00…4bf00 (75, 0, 14) Sector 4b0fff00194141 ┆K AATO POINT - NICS/TARE - SCARS/CCIS - PTR - PTP - OCR The functional breakdown for each type of process is depicted on figure 4.2.3.1.2-1. Four maingroups of functions have been identified: - Transport Initialization - Transport Control -┆
0x4bf00…4c000 (75, 0, 15) Sector 4b003300194141 ┆K 3 AA Outgoing Transport - Incoming Transport = 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=!┆
0x4c000…4c100 (76, 0, 0) Sector 00000000000000 ┆ ┆
[…0xf…]
