OctetView
0x00000…00100 (0, 0, 0) Sector 02824130323832 ┆ A0282A ┆
0x00100…00200 (0, 0, 1) Sector 00000000000000 ┆ ┆
0x00200…00300 (0, 0, 2) Sector ff000000ffe0ff ┆ ` p | ┆
0x00300…00306 (0, 0, 3) WangDocument {d00=0x30, d01=0x98, d02=0x41, ptr=(75,0, 0), d05=0x00}
0x00306…0030c WangDocument {d00=0x31, d01=0x41, d02=0x41, ptr=(73,0, 0), d05=0x00}
0x0030c…00312 WangDocument {d00=0x31, d01=0x43, d02=0x41, ptr=(71,0, 0), d05=0x00}
0x00312…00318 WangDocument {d00=0x31, d01=0x71, d02=0x41, ptr=(75,0, 8), d05=0x00}
0x00318…0031e WangDocument {d00=0x31, d01=0x76, d02=0x41, ptr=(13,0, 0), d05=0x00}
0x0031e…00324 WangDocument {d00=0x31, d01=0x95, d02=0x41, ptr=(42,0, 8), d05=0x00}
0x00324…00340 31 95 41 2a 08 00 31 95 41 2a 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆1 A* 1 A* ┆
0x00340…00360 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ ┆
[…0x4…]
0x003e0…00400 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 24 ┆ $┆
0x00400…00500 (0, 0, 4) Sector 00000000000000 ┆ ┆
0x00500…00600 (0, 0, 5) Sector 86312020202020 ┆ 1 8 7 Q? > 7 f= \ . . d N ~<) 0uH &4'>( 1c5 & & ┆
0x00600…00700 (0, 0, 6) Sector 421c402600415b ┆B @& A[' 6 X% % PO P ; 1 A} C f x f V Ww O 8 :} [,4 > 3182A f J < {C < { ; 4 ' k TuL Tux V 0 9 : 8 4 t xyyx yy ~ q-q.q/q n9q!q"q#q$X- ┆
0x00700…00800 (0, 0, 7) Sector 00000000000000 ┆ ┆
[…0x8…]
0x01000…01100 (1, 0, 0) Sector 0101c600318241 ┆ F 1 A 1 4 Quality Assurance 4.1 Qualification Tests Ref. (S10, test report) 4.2 Other Quality Assurance Provisions N/A ectory. Besides the Process area the SRS also access th┆
0x01100…01200 (1, 0, 1) Sector 0102ff00318241 ┆ 1 A 1 5 Preparations for Delivery Command files used in generation of the object code (SRS.CR0,SRS.CR1,SRS.CP,SRS.L0,SRS.L1) can be found in FIXLIB source directory for SRS (ref.VI) G┆
0x01200…01300 (1, 0, 2) Sector 0103ff00318241 ┆ 1 Aeneration of object code file: . Copy the source directory of the actual SRS version into a work directory. . Activate the command file SRS.CR0 . - - - - SRS.CP . - - - - SRS.L0 The object code ready for┆
0x01300…01400 (1, 0, 3) Sector 0104a000318241 ┆ 1 A installation will then be found in the file SRS.C Listings By activating the command file SRS.PP all source code and link output file is printed. When the buffer is full it is copied to MRF file and MRF IND, which is a pointer to next free r┆
0x01400…01500 (1, 0, 4) Sector 00006d00318241 ┆ m 1 A 1 6 Notes N/A 7 Appendices N/A MDS and an answer from MDS (which have been waiting since it placed the element in the SRS1-queue) is awaited.g the MRF record no. of the first m┆
0x01500…01600 (1, 0, 5) Sector 00000000000000 ┆ ┆
[…0x2…]
0x01800…01900 (1, 0, 8) Sector 01094a00318241 ┆ J 1 A 1 3.3.16 DECODE AIG M (PROCESS MESS utility procedure) Registers: R6: LINK Function: The AIG bitmap (in BUFFER 1) is decoded an┆
0x01900…01a00 (1, 0, 9) Sector 010a4a00318241 ┆ J 1 A 1 SK3.11 READ DTGF ENT Registers: R4: in: Ref (DTG) out: MRF record no. R6: LINK Function: The offset of the specified DTG is found either in DTG┆
0x01a00…01b00 (1, 0, 10) Sector 010b4a00318241 ┆ J 1 A 1 is delivered. critical region SRS CR) is updated with the MRF record number of the message being processed. Whenever the incore DTGF buffer is full or its size equals the space f┆
0x01b00…01c00 (1, 0, 11) Sector 010cff00318241 ┆ 1 A 1 3.5. Storage Allocation Program Size: 2107 words, Page 0 Process Size: 1322 words, Page 1 or 2 3.6 Performance Characteristics N/A 3.7 Limitations The storage ca┆
0x01c00…01d00 (1, 0, 12) Sector 010d6a00318241 ┆ j 1 Apacity is 30 days of average message traffic. 3.8 Error Codes/Error Locations see attached listOCESS MESS utility procedure) Registers: R0: in: terminal number out: - - ┆
0x01d00…01e00 (1, 0, 13) Sector 010e4a00318241 ┆ J 1 A 1 uested terminal number is set.is necessary or not beofre storage. To avoid a deletion. 3 criterias must be fulfilled: 1. at least 256 entries (words) must be free on DTGF file ┆
0x01e00…01f00 (1, 0, 14) Sector 010f4a00318241 ┆ J 1 A 1 t least the number of sectors required to store the current message must be free on MTF If all criterias are fulfilled the flag F SPACE is set to true.n c. a search is started unt┆
0x01f00…02000 (1, 0, 15) Sector 01007300318241 ┆ s 1 A 1 3.9 Listing References Ref. chap. 5 .S contains declarations of all variables buffers and arrays which define the data area (Process) of the STORAGE subsystem. The file HDB CO┆
0x02000…02100 (2, 0, 0) WangDocumentBody
[…0xa…]
0x02b00…02c00 (2, 0, 11) Sector 020c5f00317141 ┆ _ 1qA W Inds`t EDB-tekst record of the retrieved message (ref.3.3.11). If no errors occured at MTCB creation the procedure is exited and returned in LINK + 1. In case of errors the ex┆
0x02c00…02d00 (2, 0, 12) Sector 020d5f00317141 ┆ _ 1qA W Inds`t EDB-tekst RECORDS and MRF-REC are updated: MRF-REC:= 1 (1.record) RECORDS:= REC2-REC1 (no. of records) The process is exited by loading the overlay which l┆
0x02d00…02e00 (2, 0, 13) Sector 020eff00317141 ┆ 1qA W 3.5 STORAGE ALLOCATION Program size: 448 words = size of biggest overlay Process size: 1234 words, page 1 or 2 Disk storage: The overlay SRR INIT.C is loaded by ESP ┆
0x02e00…02f00 (2, 0, 14) Sector 020fff00317141 ┆ 1qA at initialization and is therefore placed in directory MD*FIX CONFIG.D*SRR OVL.xxxx.D (xxxx= version number). The name of this overlay is defined at complilation time and a change of this name or overlay┆
0x02f00…03000 (2, 0, 15) Sector 0200ff00317141 ┆ 1qA names will cause errors. 3.6 Performance caracteristics The SRR submodule is considered as a non time critical module and it is loaded as a background process. Considerable response time must be expected in some retrieval cases, i.e. a retriev┆
0x03000…03100 (3, 0, 0) WangDocumentBody
[…0x9f…]
0x0d000…0d100 (13, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(13,0, 1), len=0xff, h3=41317641}, f00=»3176A «, f01=»FIX/1200/PSP/0104 «, f02=»ja «, f03=»MLA «, f04=»T26 SUBSYSTEM PSP «, f05=17-12-82 16:06, f06=» «, f07=»42 «, f08=» 4638 «, f09=27-01-83 10:31, f10=» «, f11=»00 «, f12=» 5 «, f13=27-01-83 10:31, f14=27-01-83 14:35, f15=»0282A «, f16=» 25 «, f17=» 1 «, f18=»46 «, f19=» 96 «, f20=» 7672 «, f21=» «, f22=» «, f99=700050000110052710110180aaca15050000000000000042033000df}
0x0d100…0d200 (13, 0, 1) WangDocumentBody
[…0x6…]
0x0d800…0d900 (13, 0, 8) Sector 0d09ff00318241 ┆ 1 ANST.S contains all constants used in the STORAGE subsystem. The same file defines the constants of the RETRIEVAL subsystem and it is therefore placed in the directory FIX PREFIX.D in main directory. Besides the Process area the SRS also access th┆
0x0d900…0da00 (13, 0, 9) Sector 0d0aff00318241 ┆ 1 Ae critical region SRS CR. (This region is a common data area used by SRS, SRR and ESP. The region is read and updated by SRS and inspected by SRR and ESP) The SRS CR consists of a DTGF buffer (incore part of DTGF file), MRF buffer (incore part of ┆
0x0da00…0db00 (13, 0, 10) Sector 0d0bff00318241 ┆ 1 AMRF file) and a parameter list. (see fig. 3.4-1) Each word in the DTGF buffer belongs to a specific DTG (which can be calculated from the DTG pointers) and it contains a MRF record number. When the buffer is full it is copied to DTGF file and DTG┆
0x0db00…0dc00 (13, 0, 11) Sector 0d0cff00318241 ┆ 1 A IND, which is a pointer to the next free word in the buffer, is preset. The MRF buffer contains up to 16 MRF records each of 8 words (see fig. 3.4-2). When the buffer is full it is copied to MRF file and MRF IND, which is a pointer to next free r┆
0x0dc00…0dd00 (13, 0, 12) Sector 0d0d2500318241 ┆ % 1 Aecord in the buffer, is preset. the storage is completed is sent to MDS and an answer from MDS (which have been waiting since it placed the element in the SRS1-queue) is awaited.g the MRF record no. of the first m┆
0x0dd00…0de00 (13, 0, 13) Sector 0d0e4a00318241 ┆ J 1 A 1 3.3.15 DECODE SICS (PROCESS MESS utility procedure) Registers: R6: LINK Function: The SIC area of the message has been copied t┆
0x0de00…0df00 (13, 0, 14) Sector 0d0f4a00318241 ┆ J 1 A 1 nd copy them to the MRF record of the message.s R4: in: MRF record no out:Ref. (DTG) R5: in: None out: Ref. (MTF sector no.) R6: LINK Function: To e┆
0x0df00…0e000 (13, 0, 15) Sector 01084a00318241 ┆ J 1 A 1 he record is in the incore part of MRF the information is read from SRS CR, else it is read from MRF file. record and the MTF space free is again calculated. This iteration contin┆
0x0e000…0e100 (14, 0, 0) Sector 0e01ff00318241 ┆ 1 A 1 3.3.16 DECODE AIG M (PROCESS MESS utility procedure) Registers: R6: LINK Function: The AIG bitmap (in BUFFER 1) is decoded an┆
0x0e100…0e200 (14, 0, 1) Sector 0e024c00318241 ┆ L 1 Ad bits indicating local terminals are detected and invoked in BIT MASK3.11 READ DTGF ENT Registers: R4: in: Ref (DTG) out: MRF record no. R6: LINK Function: The offset of the specified DTG is found either in DTG┆
0x0e200…0e300 (14, 0, 2) Sector 0e034a00318241 ┆ J 1 A 1 is delivered. critical region SRS CR) is updated with the MRF record number of the message being processed. Whenever the incore DTGF buffer is full or its size equals the space f┆
0x0e300…0e400 (14, 0, 3) Sector 0e04ff00318241 ┆ 1 A 1 3.3.17 GET MEDE NO (PROCESS MESS utility procedure) Registers: R2: in: Mede id out: Mask number in AIG Mask R6: L┆
0x0e400…0e500 (14, 0, 4) Sector 0e05ff00318241 ┆ 1 AINK Function: The mede id is converted to an AIG mask pointer (1-8) 3.3.18 UPD TERM BIT M (PROCESS MESS utility procedure) Registers: R0: in: terminal number out: - - ┆
0x0e500…0e600 (14, 0, 5) Sector 0e066800318241 ┆ h 1 A R6: LINK Function: The bit in BIT MASK representing the requested terminal number is set.is necessary or not beofre storage. To avoid a deletion. 3 criterias must be fulfilled: 1. at least 256 entries (words) must be free on DTGF file ┆
0x0e600…0e700 (14, 0, 6) Sector 0e074a00318241 ┆ J 1 A 1 t least the number of sectors required to store the current message must be free on MTF If all criterias are fulfilled the flag F SPACE is set to true.n c. a search is started unt┆
0x0e700…0e800 (14, 0, 7) Sector 0d08ff00318241 ┆ 1 A 1 3.4 DATA ORGANIZATION The file SRS1 EXP.S contains declarations of all variables buffers and arrays which define the data area (Process) of the STORAGE subsystem. The file HDB CO┆
0x0e800…0e900 (14, 0, 8) Sector 0e093100318241 ┆ 1 1 Arst sector of oldest message is calculated. d (and parts of it is present in the incore buffer MTF BUF) retrieval relevant information i.e. message id and SIC s) is extracted and the MRF record is generated. Additional infor┆
0x0e900…0ea00 (14, 0, 9) Sector 0e0a4a00318241 ┆ J 1 A 1 3.3.8 UPD PARAM Registers: R6: LINK Function: File pointers and pointers to incore buffers are updated and copied to critical region SRS CRy changing the values o┆
0x0ea00…0eb00 (14, 0, 10) Sector 0e0bff00318241 ┆ 1 A 1 3.3.14 DECODE BIN H (PROCESS MESS utility procedure) Registers: R6: LINK Function: From binary header (which now is present in┆
0x0eb00…0ec00 (14, 0, 11) Sector 0e0cc500318241 ┆ E 1 A MTF BUF) the address list offset and SIC is extracted. A SIC offset = 0 indicates that no 316 s exists. As the SIC-offset is not the actual offset of the first SIC, a correction is added.ctor address and the HDB indicator flag. The file is rel┆
0x0ec00…0ed00 (14, 0, 12) Sector 0e0d4a00318241 ┆ J 1 A 1 the storage is completed is sent to MDS and an answer from MDS (which have been waiting since it placed the element in the SRS1-queue) is awaited.g the MRF record no. of the first m┆
0x0ed00…0ee00 (14, 0, 13) Sector 0e0eff00318241 ┆ 1 A 1 3.3.15 DECODE SICS (PROCESS MESS utility procedure) Registers: R6: LINK Function: The SIC area of the message has been copied t┆
0x0ee00…0ef00 (14, 0, 14) Sector 0e0f7800318241 ┆ x 1 Ao SIC BUF by PROCESS MESS. DECODE SICS extract the delimiters (/) and copy them to the MRF record of the message.s R4: in: MRF record no out:Ref. (DTG) R5: in: None out: Ref. (MTF sector no.) R6: LINK Function: To e┆
0x0ef00…0f000 (14, 0, 15) Sector 0e004a00318241 ┆ J 1 A 1 he record is in the incore part of MRF the information is read from SRS CR, else it is read from MRF file. record and the MTF space free is again calculated. This iteration contin┆
0x0f000…0f100 (15, 0, 0) Sector 0f014a00318241 ┆ J 1 A 1 3.3.7 U MRF DTGF Registers: R6: LINK Function: The MRF record generated in PROCESS MESS is stored in the incore part of MRF file (the upper part of critical regi┆
0x0f100…0f200 (15, 0, 1) Sector 0f02ff00318241 ┆ 1 A 1 3.3.11 READ DTGF ENT Registers: R4: in: Ref (DTG) out: MRF record no. R6: LINK Function: The offset of the specified DTG is found either in DTG┆
0x0f200…0f300 (15, 0, 2) Sector 0f035800318241 ┆ X 1 AF income file (SRS CR) or DTGF file and its entry (a MRF record no.) is delivered. critical region SRS CR) is updated with the MRF record number of the message being processed. Whenever the incore DTGF buffer is full or its size equals the space f┆
0x0f300…0f400 (15, 0, 3) Sector 0f044a00318241 ┆ J 1 A 1 3.3.4 TEST SPACE Registers: RG: LINK Function: The DTG extracted from the MTCB (which was time stamped by MDS subsystem) is converted from seconds to minutes. As the message┆
0x0f400…0f500 (15, 0, 4) Sector 0f05ff00318241 ┆ 1 A 1 3.3.12 CALC RECS FRGE ON MRF (Delete utility Procedure) Registers: R0: in: NONE out: Records free Function: No ┆
0x0f500…0f600 (15, 0, 5) Sector 0f065000318241 ┆ P 1 Aof records between oldest and newest MRF record on MRF file is calculated.mine whether a deletion is necessary or not beofre storage. To avoid a deletion. 3 criterias must be fulfilled: 1. at least 256 entries (words) must be free on DTGF file ┆
0x0f600…0f700 (15, 0, 6) Sector 0f074a00318241 ┆ J 1 A 1 t least the number of sectors required to store the current message must be free on MTF If all criterias are fulfilled the flag F SPACE is set to true.n c. a search is started unt┆
0x0f700…0f800 (15, 0, 7) Sector 0e08ff00318241 ┆ 1 A 1 3.3.13 CALCULATE MTF SPACE (DELET utility procedure) Registers: R6: LINK Function: Number of sectors between MTF SECTOR and fi┆
0x0f800…0f900 (15, 0, 8) Sector 0f094a00318241 ┆ J 1 A 1 d (and parts of it is present in the incore buffer MTF BUF) retrieval relevant information i.e. message id and SIC s) is extracted and the MRF record is generated. Additional infor┆
0x0f900…0fa00 (15, 0, 9) Sector 0f0ae800318241 ┆ h 1 A 1 3.3.8 UPD PARAM Registers: R6: LINK Function: File pointers and pointers to incore buffers are updated and copied to critical region SRS CRy changing the values o┆
0x0fa00…0fb00 (15, 0, 10) Sector 0f0b4a00318241 ┆ J 1 A 1 GF and MTF are done until 3 criterias are fulfilled: 1. at least 300 records free on MRF 2. at least 576 entries free on DTGF 3. at least 568 sectors free on MTF If the spa┆
0x0fb00…0fc00 (15, 0, 11) Sector 0f0cff00318241 ┆ 1 A 1 3.3.9 DEL Q ELEM Registers: R6: LINK Function: The MTCB representing the message is updated with MTF sector address and the HDB indicator flag. The file is rel┆
0x0fc00…0fd00 (15, 0, 12) Sector 0f0ddc00318241 ┆ \ 1 Aeased and the queue element is deleted. A message indicating that the storage is completed is sent to MDS and an answer from MDS (which have been waiting since it placed the element in the SRS1-queue) is awaited.g the MRF record no. of the first m┆
0x0fd00…0fe00 (15, 0, 13) Sector 0f0e4a00318241 ┆ J 1 A 1 he 2 pointers DTGS and MRF REC (which are the new pointers of oldest MRF rec and oldest DTG with criterion 1 fulfilled). If the new DTG does not fulfill criterion 2 a new DTG is c┆
0x0fe00…0ff00 (15, 0, 14) Sector 0f0fff00318241 ┆ 1 A 1 3.3.10 READ MRE REC Registers R4: in: MRF record no out:Ref. (DTG) R5: in: None out: Ref. (MTF sector no.) R6: LINK Function: To e┆
0x0ff00…10000 (15, 0, 15) Sector 0f00b500318241 ┆ 5 1 Axtract the DTG and MTF address from the specified MRF record. If the record is in the incore part of MRF the information is read from SRS CR, else it is read from MRF file. record and the MTF space free is again calculated. This iteration contin┆
0x10000…10100 (16, 0, 0) WangDocumentBody
0x10100…10200 (16, 0, 1) Sector 00000000000000 ┆ ┆
[…0x6…]
0x10800…10900 (16, 0, 8) WangDocumentBody
[…0xf…]
0x11800…11900 (17, 0, 8) Sector 1109ff00318241 ┆ 1 A 1 3.3.7 U MRF DTGF Registers: R6: LINK Function: The MRF record generated in PROCESS MESS is stored in the incore part of MRF file (the upper part of critical regi┆
0x11900…11a00 (17, 0, 9) Sector 110aff00318241 ┆ 1 Aon SRS CR). If the incore MRF buffer (which can contrin 16 records) is full, or the space free on MRF file is equal to the present size of MRFincore part, it is copied to MRF file. The number of minutes since last stored message is calculateed a┆
0x11a00…11b00 (17, 0, 10) Sector 110bff00318241 ┆ 1 And each corresponding entry in the incore part of the DTGF file (the lower part of critical region SRS CR) is updated with the MRF record number of the message being processed. Whenever the incore DTGF buffer is full or its size equals the space f┆
0x11b00…11c00 (17, 0, 11) Sector 110c3a00318241 ┆ : 1 Aree on disc file, the buffer is copied to DTGF file. 3.3.4 TEST SPACE Registers: RG: LINK Function: The DTG extracted from the MTCB (which was time stamped by MDS subsystem) is converted from seconds to minutes. As the message┆
0x11c00…11d00 (17, 0, 12) Sector 110d4a00318241 ┆ J 1 A 1 d if the DTG of the current message is older than the DTG of the previous stored message, if not, the message cannot be handled by SRS and MON ERROR is called, requesting a switchov┆
0x11d00…11e00 (17, 0, 13) Sector 110e4a00318241 ┆ J 1 A 1 determine whether a deletion is necessary or not beofre storage. To avoid a deletion. 3 criterias must be fulfilled: 1. at least 256 entries (words) must be free on DTGF file ┆
0x11e00…11f00 (17, 0, 14) Sector 110f4a00318241 ┆ J 1 A 1 t least the number of sectors required to store the current message must be free on MTF If all criterias are fulfilled the flag F SPACE is set to true.n c. a search is started unt┆
0x11f00…12000 (17, 0, 15) Sector 0f084a00318241 ┆ J 1 A 1 3.3.6 PROCESS MESS REGISTERS: R6: LINK Function: The message being processed is copied from its temporary media (PDB or IMF file) into a SRS buffer and from th┆
0x12000…12100 (18, 0, 0) Sector 1201ff00318241 ┆ 1 Aere into the next free area on MTF file. While the message is copied (and parts of it is present in the incore buffer MTF BUF) retrieval relevant information i.e. message id and SIC s) is extracted and the MRF record is generated. Additional infor┆
0x12100…12200 (18, 0, 1) Sector 1202ba00318241 ┆ : 1 Amation is extracted from MTCB and placed in the MRF record. A bitmap representing the terminals which were addressed is generated from the address list and placed in MRF record. flag F SPACE as false. The deletion is done by changing the values o┆
0x12200…12300 (18, 0, 2) Sector 12034a00318241 ┆ J 1 A 1 GF and MTF are done until 3 criterias are fulfilled: 1. at least 300 records free on MRF 2. at least 576 entries free on DTGF 3. at least 568 sectors free on MTF If the spa┆
0x12300…12400 (18, 0, 3) Sector 12044a00318241 ┆ J 1 A 1 est record no", MRF REC is calculated. The DTG corresponding to this record no. is found by extracting the DTG of the found MRF record. As it is shown in fig. 3.1-2 several MRF re┆
0x12400…12500 (18, 0, 4) Sector 12054a00318241 ┆ J 1 A 1 ame minute). Therefore to get the correct relationship between the new "OLDEST DTG" and the new "oldest record no" the entry of the DTG (containing the MRF record no. of the first m┆
0x12500…12600 (18, 0, 5) Sector 12064a00318241 ┆ J 1 A 1 he 2 pointers DTGS and MRF REC (which are the new pointers of oldest MRF rec and oldest DTG with criterion 1 fulfilled). If the new DTG does not fulfill criterion 2 a new DTG is c┆
0x12600…12700 (18, 0, 6) Sector 12074a00318241 ┆ J 1 A 1 The MTF sector no. which fulfills criterion 3 is found by iteration: The MRT REC record is read and MTF address is extracted and stored in MTF SECTOR (which now is a quess of "┆
0x12700…12800 (18, 0, 7) Sector 11084a00318241 ┆ J 1 A 1 han required in criterion 3, a new MRF record is calculated. The MTF address is extracted from the new MTF record and the MTF space free is again calculated. This iteration contin┆
0x12800…12900 (18, 0, 8) Sector 12092b00318241 ┆ + 1 Aues until criterion 3 is fulfilled. 3.3.3 GET QUEUE ELEM REGISTERS: R6: LINK FUNCTION: The SRS1-queue is served by call of MON QACCESS. If the queue is empty the process waits in 10 sec or until a signal┆
0x12900…12a00 (18, 0, 9) Sector 120aff00318241 ┆ 1 A 1 The new pointers to oldest entries on DTGF, MRF and MTF are updated and copied to critical region SRS CR. The same pointers are copied to the control records on the files MRF, DJ┆
0x12a00…12b00 (18, 0, 10) Sector 120b7200318241 ┆ r 1 AGF and MTF. Deletion is now done and the processing of the message which caused the deletion can continue.E ELEM, HIPO Chart., Fig. 3.3.3 via RDF monitor (read) MTF,MRF,DTGF,SRS CHECK P: Via IOS (read, write) MTCB MONITOR PSP IV┆
0x12b00…12c00 (18, 0, 11) Sector 120c4a00318241 ┆ J 1 A 1 3.3.4 TEST SPACE Registers: RG: LINK Function: The DTG extracted from the MTCB (which was time stamped by MDS subsystem) is converted from seconds to minutes. As the message┆
0x12c00…12d00 (18, 0, 12) Sector 120d4a00318241 ┆ J 1 A 1 d if the DTG of the current message is older than the DTG of the previous stored message, if not, the message cannot be handled by SRS and MON ERROR is called, requesting a switchov┆
0x12d00…12e00 (18, 0, 13) Sector 120e4a00318241 ┆ J 1 A 1 determine whether a deletion is necessary or not beofre storage. To avoid a deletion. 3 criterias must be fulfilled: 1. at least 256 entries (words) must be free on DTGF file ┆
0x12e00…12f00 (18, 0, 14) Sector 120f4a00318241 ┆ J 1 A 1 t least the number of sectors required to store the current message must be free on MTF If all criterias are fulfilled the flag F SPACE is set to true.n c. a search is started unt┆
0x12f00…13000 (18, 0, 15) Sector 1200ff00318241 ┆ 1 A 1 3.3.6 PROCESS MESS REGISTERS: R6: LINK Function: The message being processed is copied from its temporary media (PDB or IMF file) into a SRS buffer and from th┆
0x13000…13100 (19, 0, 0) Sector 13014a00318241 ┆ J 1 A 1 the critical region SRS CR (which is also accessed by the Retrieval submodule (SRR), and the entire region (containing DTGF incore part, MRF incore part and pointers) is stored on ┆
0x13100…13200 (19, 0, 1) Sector 1302ff00318241 ┆ 1 A 1 3.3.5 Deletion Registers R6: LINK Function: DELETE is called if the TEST SPACE procedure returns with the flag F SPACE as false. The deletion is done by changing the values o┆
0x13200…13300 (19, 0, 2) Sector 1303ff00318241 ┆ 1 Af the filepointers (pointers to oldest entries) Deletion on MRF, DTGF and MTF are done until 3 criterias are fulfilled: 1. at least 300 records free on MRF 2. at least 576 entries free on DTGF 3. at least 568 sectors free on MTF If the spa┆
0x13300…13400 (19, 0, 3) Sector 1304ff00318241 ┆ 1 Ace left on MRF file is less than specified in criteria 1, a new "oldest record no", MRF REC is calculated. The DTG corresponding to this record no. is found by extracting the DTG of the found MRF record. As it is shown in fig. 3.1-2 several MRF re┆
0x13400…13500 (19, 0, 4) Sector 1305ff00318241 ┆ 1 Acords can contain identical DTG s (i.e. messages stores within the same minute). Therefore to get the correct relationship between the new "OLDEST DTG" and the new "oldest record no" the entry of the DTG (containing the MRF record no. of the first m┆
0x13500…13600 (19, 0, 5) Sector 1306ff00318241 ┆ 1 Aessage of this DTG) is read from DTGF file. The result of this is the 2 pointers DTGS and MRF REC (which are the new pointers of oldest MRF rec and oldest DTG with criterion 1 fulfilled). If the new DTG does not fulfill criterion 2 a new DTG is c┆
0x13600…13700 (19, 0, 6) Sector 1307ff00318241 ┆ 1 Aalculated and its corresponding MRF record no. is read in DTGF file. The MTF sector no. which fulfills criterion 3 is found by iteration: The MRT REC record is read and MTF address is extracted and stored in MTF SECTOR (which now is a quess of "┆
0x13700…13800 (19, 0, 7) Sector 1208ff00318241 ┆ 1 Aoldest MTF sector"). The free MTF space is calculated and if less than required in criterion 3, a new MRF record is calculated. The MTF address is extracted from the new MTF record and the MTF space free is again calculated. This iteration contin┆
0x13800…13900 (19, 0, 8) Sector 1309ff00318241 ┆ 1 A W 3.3.3 GET QUEUE ELEM REGISTERS: R6: LINK FUNCTION: The SRS1-queue is served by call of MON QACCESS. If the queue is empty the process waits in 10 sec or until a signal┆
0x13900…13a00 (19, 0, 9) Sector 130a9100318241 ┆ 1 A is received and then it tries again. If a queue element is found, the corresponding MTCB is read and placed in the buffer MTCBWKSP. message is completed an AMOS message is sent to MDS. MDS-SRS: An answer is returned to MDS. Critical r┆
0x13a00…13b00 (19, 0, 10) Sector 130b9300318241 ┆ 1 A W SET QUEUE ELEM, HIPO Chart., Fig. 3.3.3 via RDF monitor (read) MTF,MRF,DTGF,SRS CHECK P: Via IOS (read, write) MTCB MONITOR PSP IV┆
0x13b00…13c00 (19, 0, 11) Sector 130cff00318241 ┆ 1 A W 3.3.4 TEST SPACE Registers: RG: LINK Function: The DTG extracted from the MTCB (which was time stamped by MDS subsystem) is converted from seconds to minutes. As the message┆
0x13c00…13d00 (19, 0, 12) Sector 130dff00318241 ┆ 1 As must arrive to the SRS1-queue in a cronological order, it is tested if the DTG of the current message is older than the DTG of the previous stored message, if not, the message cannot be handled by SRS and MON ERROR is called, requesting a switchov┆
0x13d00…13e00 (19, 0, 13) Sector 130eff00318241 ┆ 1 Aer. TEST SPACE is always called before processing of a message to determine whether a deletion is necessary or not beofre storage. To avoid a deletion. 3 criterias must be fulfilled: 1. at least 256 entries (words) must be free on DTGF file ┆
0x13e00…13f00 (19, 0, 14) Sector 130fe300318241 ┆ c 1 A2. at least 16 records (8 words each) must be free on MRF file 3. at least the number of sectors required to store the current message must be free on MTF If all criterias are fulfilled the flag F SPACE is set to true.n c. a search is started unt┆
0x13f00…14000 (19, 0, 15) Sector 13004a00318241 ┆ J 1 A 1 3.3.1 STORAGE (Main module). FUNCTION: After call of INIT STORAGE an endless loop is entered. The loop is only excited in case of a fatal error or a removal of the process. ┆
0x14000…14100 (20, 0, 0) Sector 1401ff00318241 ┆ 1 A After processing of a message all update pointers are copied to the critical region SRS CR (which is also accessed by the Retrieval submodule (SRR), and the entire region (containing DTGF incore part, MRF incore part and pointers) is stored on ┆
0x14100…14200 (20, 0, 1) Sector 14021d00318241 ┆ 1 Adisc file SRS CHECKP. s calculated. If condition c. is not fulfilled the search is repeated. To get the correct relationship between MRF number and DTG entry the retrieval DTG in the calculated 'oldest MRF record' is extracted and defined as ol┆
0x14200…14300 (20, 0, 2) Sector 14039900318241 ┆ 1 A W STORAGE Mainmodule, HIPO Chart , Fig. 3.3.1-1 record is read and the MTF address is extracted and the value defined as first sector of oldest messag┆
0x14300…14400 (20, 0, 3) Sector 14049800318241 ┆ 1 A W STORAGE Mainmodule, HIPO chart, Fig 3.3.1.-1 Deletion completed. SRS RECOVERY After each storage of a message the critical region SRS CR (┆
0x14400…14500 (20, 0, 4) Sector 1405ff00318241 ┆ 1 A W 3.3.2 INIT STORAGE REGISTERS: R6: LINK FUNCTION: File discriptions are found for directories MOVEHEAD and FIXHEAD and files, MRF, DTGF, MTF, RDF and SRS CHECKP. ┆
0x14500…14600 (20, 0, 5) Sector 1406ef00318241 ┆ o 1 A The MTCB monitor is initiated and the local mede id found. SRS CHECKP file is copied into critical region SRS CR and pointers and variables are recovered. The procedure is called once after start/restart and is then never used. ls QACCESS to ge┆
0x14600…14700 (20, 0, 6) Sector 14079400318241 ┆ 1 A W INIT STORAGE, HIPO Chart, Fig. 3.3.3.2-1 T HDB has to be run. The generator presets variables and pointers in SRS-CHECKUP to indicate an empty HDB.┆
0x14700…14800 (20, 0, 7) Sector 13089200318241 ┆ 1 A W INIT STORAGE, HIPO Chart, Fig, 3.3.2-2 outlined above. Deletion is performed so that: a. A given timespan is available for message storage. T┆
0x14800…14900 (20, 0, 8) Sector 1409ff00318241 ┆ 1 A W 3.2 Interface Description Interface data: ref. I, chap. 7.1.1.1. Input queues: SRS1-queue (first in, first out) Output queues: None Interface to ot┆
0x14900…14a00 (20, 0, 9) Sector 140aff00318241 ┆ 1 Aher subsystems: SRS MDS: MDS requests storage of a message by enqueueing a MTCB index in SRS1-queue. SRS MDS: When a storage of a message is completed an AMOS message is sent to MDS. MDS-SRS: An answer is returned to MDS. Critical r┆
0x14a00…14b00 (20, 0, 10) Sector 140beb00318241 ┆ k 1 Aegion access: SRS Read and updates critical region SRS CR File access: IMF, PDB: via MTCB monitor (read) RDF: via RDF monitor (read) MTF,MRF,DTGF,SRS CHECK P: Via IOS (read, write) MTCB MONITOR PSP IV┆
0x14b00…14c00 (20, 0, 11) Sector 140cff00318241 ┆ 1 A W 3.3 Processing This chapter contains a detailed 'as build' description of the subsystem SRS. Each procedure is presented by a brief description and a HIPO chart. Pointers, variabl┆
0x14c00…14d00 (20, 0, 12) Sector 140dff00318241 ┆ 1 Aes, buffers and constants are described in chapter 3.4. Figure 3.3-1 shows an overview block diagram of the subsystem. The STORAGE box represents the main module, from which the procedures are called. The procedures again call a number of util┆
0x14d00…14e00 (20, 0, 13) Sector 140ec500318241 ┆ E 1 Aity procedures (the smallest boxes) and monitors (boxes with double sides). A detailed description the data referenced in the input/output blocks of the HIPO charts is found in chap. 3.4. is read: The DTGF entry gives the MRF record number. This ┆
0x14e00…14f00 (20, 0, 14) Sector 140f9300318241 ┆ 1 A W Fig. 3.3-1, Module block diagram of SRS nt of free space is calculated. If the calculated space does not fulfil condition c. a search is started unt┆
0x14f00…15000 (20, 0, 15) Sector 1400ff00318241 ┆ 1 A W 3.3.1 STORAGE (Main module). FUNCTION: After call of INIT STORAGE an endless loop is entered. The loop is only excited in case of a fatal error or a removal of the process. ┆
0x15000…15100 (21, 0, 0) Sector 1501ff00318241 ┆ 1 A W The number of messages is added to the present value 'oldest MRF record number '. The MRF record is read and the MTF address is extracted. With this value of 'oldest MTF sector' ┆
0x15100…15200 (21, 0, 1) Sector 1502ff00318241 ┆ 1 Athe space free on MTF is calculated. If condition c. is not fulfilled the search is repeated. To get the correct relationship between MRF number and DTG entry the retrieval DTG in the calculated 'oldest MRF record' is extracted and defined as ol┆
0x15200…15300 (21, 0, 2) Sector 1503ff00318241 ┆ 1 Adest DTG after deletion. The DTG entry is read from DTSF file and the entry is defined as the MRF record of oldest message after deletion. The MRF record is read and the MTF address is extracted and the value defined as first sector of oldest messag┆
0x15300…15400 (21, 0, 3) Sector 1504ff00318241 ┆ 1 Ae on HDB after deletion. 4. The first sector of DTGF, MRF and MTF (the control sectors) are updated to reflect deletion. Deletion completed. SRS RECOVERY After each storage of a message the critical region SRS CR (┆
0x15400…15500 (21, 0, 4) Sector 1505ff00318241 ┆ 1 Awhich contains all necessary pointers for a restart) Is copied to the checkpoint file SRS CHECKP. When the SRS process is loaded and started (at cold start or recovery) the SRS CHECKP. file is copied to SRS CR and pointers and variables in SRS pr┆
0x15500…15600 (21, 0, 5) Sector 15064e00318241 ┆ N 1 Aocess is reconstructed. The SRS i now ready to serve its input queue. the message. When SRS has received a system answer from MDS the critical region SRS CR is copied to the checkpoint file SRS CHECKP on FIXHEAD. The SRS now calls QACCESS to ge┆
0x15600…15700 (21, 0, 6) Sector 1507ff00318241 ┆ 1 A W At disc initialization time (or at corruption of HDB) the generator PRESET HDB has to be run. The generator presets variables and pointers in SRS-CHECKUP to indicate an empty HDB.┆
0x15700…15800 (21, 0, 7) Sector 14084d00318241 ┆ M 1 A A detailed product description of PRESET HDB is found in, ref. VII. letion of oldest messages is intitiated whenever no room available as outlined above. Deletion is performed so that: a. A given timespan is available for message storage. T┆
0x15800…15900 (21, 0, 8) Sector 1509ff00318241 ┆ 1 Ahis means, that messages shall be deleted to get a new value for the DTG of the oldest message. The entries from DTG (oldest) to DTG (newest) are the occupied entries. Number of free entries = Total number if entries - (entries from ┆
0x15900…15a00 (21, 0, 9) Sector 150aff00318241 ┆ 1 ADTG (oldest) to DTG (newest). The number of free entries shall be superior to the number of entries required to cover the given timespan. b. A given number of records free on MRF for storage of new messages. Messages shall be deleted so t┆
0x15a00…15b00 (21, 0, 10) Sector 150bd500318241 ┆ U 1 Ahat the required number of records are free on the MRF. c. A given amount of space on the message text file. Messages shall be deleted so that the given amount of text space is available on the MTF. e fig. 3.1-3. MTCB MONITOR PSP IV┆
0x15b00…15c00 (21, 0, 11) Sector 150cff00318241 ┆ 1 A W Deletion is performed as follows: 1. Calculate the MRF record number to fulfil condition b. The determined record may correspond to a message which is not the first for a given ┆
0x15c00…15d00 (21, 0, 12) Sector 150dff00318241 ┆ 1 ADTG. To obtain this the MRF record is read to obtain the retrieval DTG of the message. This value + one minute is defined as the new value for the DTG of the oldest message. 2. A test is performed to see if condition a. is fulfilled. If not the D┆
0x15d00…15e00 (21, 0, 13) Sector 150eff00318241 ┆ 1 ATG of the oldest message is incremented to fulfil condition a. 3. With the present value for the DTG of the oldest message the offset in the DTGF is calculated and the corresponding entry is read: The DTGF entry gives the MRF record number. This ┆
0x15e00…15f00 (21, 0, 14) Sector 150fff00318241 ┆ 1 AMRF record is read. From the MTF address of the oldest message as defined here and the MTF address of the first free part in the MTF the amount of free space is calculated. If the calculated space does not fulfil condition c. a search is started unt┆
0x15f00…16000 (21, 0, 15) Sector 1500d100318241 ┆ Q 1 Ail condition c. is fulfilled. The search starts by calculating the remaining number of messages to be deleted to fullfil condition c. (Remaining messages = (space required - space free)/18 sectors). MRF is performed. (The storage process await ┆
0x16000…16100 (22, 0, 0) Sector 16012200318241 ┆ " 1 Atermination). (fig. 3.1-3). is the MRF record number of the first message in this DTG. If no message has re- trieval time equal to this DTG the DTGF entry is the MRF record number of the first message after this DTG. The MRF consists of 44800 r┆
0x16100…16200 (22, 0, 1) Sector 1602ff00318241 ┆ 1 A W If the retrieval DTG of the message (obtained from the MTCB) is superior to the retrieval time of the last stored message, update of the in-memory subset of the DTGF (which resid┆
0x16200…16300 (22, 0, 2) Sector 1603ff00318241 ┆ 1 Aes in the critical region SRS CR)takes place. This means an update of all entries corresponding to DTG's since the DTG of the last stored message. All these entries get updated with the MRF record number of the present message. Whenever in this proc┆
0x16300…16400 (22, 0, 3) Sector 1604ff00318241 ┆ 1 Aess the in-memory subset of the DTGF gets full transfer is made to the DTGF (fig. 3.1-3). The MTCB of the message is updated with o MTF address o Indicator that the message is on HDB by call to the MTCB monitor. The queue element (and the MT┆
0x16400…16500 (22, 0, 4) Sector 1605ff00318241 ┆ 1 ACB) is released via call to QACCESS. If the storage process was the last referencing the input file the MTCB monitor will delete the file. A system message is sent to the subsystem MDS. The message tells that the narrative message it had queued┆
0x16500…16600 (22, 0, 5) Sector 1606ff00318241 ┆ 1 A to SRS now is stored on HDB and that MDS can continue its processing of the message. When SRS has received a system answer from MDS the critical region SRS CR is copied to the checkpoint file SRS CHECKP on FIXHEAD. The SRS now calls QACCESS to ge┆
0x16600…16700 (22, 0, 6) Sector 1607da00318241 ┆ Z 1 At the next element in the storage queue for processing as described above. If no queue element was found the storage process goes into a wait for signal that a queue element has been entered in an empty queue. he storage process calls QACCESS and ┆
0x16700…16800 (22, 0, 7) Sector 1508ff00318241 ┆ 1 A W Deletion of oldest messages is intitiated whenever no room available as outlined above. Deletion is performed so that: a. A given timespan is available for message storage. T┆
0x16800…16900 (22, 0, 8) Sector 1609ff00318241 ┆ 1 A W At least the length of the message free on MTF One record free on MRF If the DTG of the message to be stored is superior to the DTG of the last message stored on the HDB, the ┆
0x16900…16a00 (22, 0, 9) Sector 160aff00318241 ┆ 1 Astorage process tests if space is available on the DTGF for DTG entries from the DTG of the last message to DTG of current message. If one or more of the three tests shows, that space is not available deletion is performed (see below). When┆
0x16a00…16b00 (22, 0, 10) Sector 160be400318241 ┆ d 1 Aever space is available the storage processing continues as follows: The message file (the message as referenced by the MTCB) is copied to the MTF starting in the begin- ning of the first free sector. See fig. 3.1-3. MTCB MONITOR PSP IV┆
0x16b00…16c00 (22, 0, 11) Sector 160c8600318241 ┆ 1 A W Fig 3.1-3, MESSAGE STORAGE l DTG Text address (sector no. on MTF file) Message length Message id. 3 SIC's Message classificatio┆
0x16c00…16d00 (22, 0, 12) Sector 160dff00318241 ┆ 1 A W In the copy processing eventually all of the message is in memory (not all at one instant). While in memory all information for the MRF is extracted. This means: Copy MSG ID ┆
0x16d00…16e00 (22, 0, 13) Sector 160eff00318241 ┆ 1 A Security class SIC's from the message Read address numbers (ANO's) and AIG's together with originator ID and generate the bit mask in- dicating terminals with retrieval right: originator ANO and TO and INFO ANO's are scanned. Those r┆
0x16e00…16f00 (22, 0, 14) Sector 160fff00318241 ┆ 1 Aeferring a local terminal give the retrieval right to this terminal. The MRF record for the message is formed of the ex- tracted information together with the MTF address of the firs sector of the message, the retrieval time and the message┆
0x16f00…17000 (22, 0, 15) Sector 1600ff00318241 ┆ 1 A length from the MTCB The in-memory subset of the MRF(which is a part of the critical region SRS CR) is updated with the record. If the in-memory subset of the MRF hereby gets full, a transfer to the MRF is performed. (The storage process await ┆
0x17000…17100 (23, 0, 0) Sector 1701ff00318241 ┆ 1 Ais one word long. This word is the MRF record number of the first message in this DTG. If no message has re- trieval time equal to this DTG the DTGF entry is the MRF record number of the first message after this DTG. The MRF consists of 44800 r┆
0x17100…17200 (23, 0, 1) Sector 1702ff00318241 ┆ 1 Aecords correspon- ding to 44800 messages. One record contains: MSG - ID Retrieval DTG Message security class Bit mask with one bit per terminal The bit is true if the corre- sponding terminal has the right to retrieve the message. ┆
0x17200…17300 (23, 0, 2) Sector 17030f00318241 ┆ 1 A3 SIC's dule verifies that space is available for the next message in the Historical Data Base, if space is not available a prescribed amount of space is obtained by deletion of oldest messages on the HDB (Retention, 3.). When space is available th┆
0x17300…17400 (23, 0, 3) Sector 1704ff00318241 ┆ 1 A W Message address on MTF. It is an offset in sectors from the beginning of the MTF. Message length. Action and info precedence The MTF file consists of 110309 contiguou┆
0x17400…17500 (23, 0, 4) Sector 1705ff00318241 ┆ 1 As sectors (+ 1 sector reserved for control information). The messages are stored on the MTF starting on a sector boundary. This gives a wanted space of 25% in average (the space at end of one message until next sector boundary). The capacity is then┆
0x17500…17600 (23, 0, 5) Sector 1706ff00318241 ┆ 1 A 44795 messages of average length (ref. I, chap. 11.2). A detailed description of the files MTF, MRF and DTGF is found in ref. I, chap. 11.2. Message Storage and Deletion Message Storage is initiated by placing an entry in the SRS storage queu┆
0x17600…17700 (23, 0, 6) Sector 1707ff00318241 ┆ 1 Ae that points to a Message Transition Control Block. Each MTCB is time stamped by the MDS subsystem with the retrieval time (DTGF entry) and they must be entered sequentially. The processing is as follows: The storage process calls QACCESS and ┆
0x17700…17800 (23, 0, 7) Sector 1608a300318241 ┆ # 1 Athe MTCB monitor to get the first element in the storage queue. The storage process tests if space is available for the message on the HDB. This means r in the DTGF is calculated from the value of the DTG, the DTG corresponding to the oldest e┆
0x17800…17900 (23, 0, 8) Sector 1709ff00318241 ┆ 1 Antry in the file, entry number of oldest entry and number of entries in the file: Word offset on DTGF of DTG: RM -DTG-BASE-DTG + word length No. of entries on DTGF of control block (DTG of oldest message on HDB ┆
0x17900…17a00 (23, 0, 9) Sector 170aff00318241 ┆ 1 A DTG DTG of last stored message). The entry of this offset is the record number of the first message stored in the interval DTG to DTG + 1 minute. If no messages were stored in this interval the entry contains the MRF number of the next stored┆
0x17a00…17b00 (23, 0, 10) Sector 170b1f00318241 ┆ 1 A message. (fig. 3.1-2). 2 APPLICABLE DOCUMENTS I FIX/0100/MAN/0004 FIKS DATA I/F REFERENCE II FIX/1256/PSP/0078 QACCESS MONITOR PSP III FIX/1256/PSP/0066 MTCB MONITOR PSP IV┆
0x17b00…17c00 (23, 0, 11) Sector 170cff00318241 ┆ 1 A W The MRF file contains fixed length records of Retrieval DTG Text address (sector no. on MTF file) Message length Message id. 3 SIC's Message classificatio┆
0x17c00…17d00 (23, 0, 12) Sector 170d3e00318241 ┆ > 1 An Action and info precedence Terminal bit mask 3010 ............... 1 1.1 Introduction .............................. 1 1.2 ABBREVIATIONS .............................. 1 2 APPLICABLE DOCUMENTS ........................... ┆
0x17d00…17e00 (23, 0, 13) Sector 170e8d00318241 ┆ 1 A W Fig. 3.1-2, HDB Logical Structure he interface to the HDB. It supports storage on the HDB, deletion of messages on the HDB and retrieval of messages┆
0x17e00…17f00 (23, 0, 14) Sector 170fff00318241 ┆ 1 A W HDB layout The HDB is laid out with each of the three files as contiguous files. Updates of DTGF and MRF are performed as updates in an in memory subset of these files. Wheneve┆
0x17f00…18000 (23, 0, 15) Sector 1700ff00318241 ┆ 1 Ar the in memory subset is full a transfer is made to the disc file. The DTGF consists of 43776 entries corresponding to 30 days storage. One entry exists for each minute independent of whether a messagae was stored or not. One entry in the DTGF ┆
0x18000…18100 (24, 0, 0) Sector 1801ff00318241 ┆ 1 A W Subsystem Block Diagram In figure 3.1-1 the SRS subsystem block diagram is found. Main events are marked with numbers 1. Processing of storage requests 2. Eventual updates of┆
0x18100…18200 (24, 0, 1) Sector 1802ff00318241 ┆ 1 A retrieval files 3. Retention (deletion of messages) The subsystem has one input queue: SRS1-queue The queue is handled in a First in First out manner. When an element, representing a message to be stored is entered in the SRS1 queue. The S┆
0x18200…18300 (24, 0, 2) Sector 1803ff00318241 ┆ 1 Atorage Module verifies that space is available for the next message in the Historical Data Base, if space is not available a prescribed amount of space is obtained by deletion of oldest messages on the HDB (Retention, 3.). When space is available th┆
0x18300…18400 (24, 0, 3) Sector 1804ff00318241 ┆ 1 Ae in memory subset of the message retrieval files (DTGF and MRF) are updated with retrieval relevant information and a transfer of the message text is performed from the Input file to the Message Text File (1). The MTCB for the message is updated w┆
0x18400…18500 (24, 0, 4) Sector 18059700318241 ┆ 1 Aith the MTF address and a HDB indicator flag. Whenever the in-memory subsets of the DTGF and/or MRF are full, a transfer to disc is made (2). 3.4 DATA ORGANIZATION .......................... 72 3.5 Storage Allocation ......................┆
0x18500…18600 (24, 0, 5) Sector 18069f00318241 ┆ 1 A W Fig. 3.1-1, STORAGE MODULE, INTERFACE BLOCK DIAGRAM s ................ 80 3.9 Listing References ......................... 83 4 Quality Assu┆
0x18600…18700 (24, 0, 6) Sector 1807ff00318241 ┆ 1 A W HDB structure (fig. 3.1-2) Message retrieval is performed by reference to two message access files. The DTGF file is the primary access reference. Each entry in the DTGF file co┆
0x18700…18800 (24, 0, 7) Sector 1708ff00318241 ┆ 1 Antains the number of records offset from the beginning of the MRF file where the first message in or after the specified DTG is referenced. The entry number in the DTGF is calculated from the value of the DTG, the DTG corresponding to the oldest e┆
0x18800…18900 (24, 0, 8) Sector 1809ff00318241 ┆ 1 A W 1 Scope This document contains a detailed product specification of the storage module SRS. 1.1 Introduction The SRS performs long time storage of narrative messages on the Hi┆
0x18900…18a00 (24, 0, 9) Sector 180abe00318241 ┆ > 1 Astorical Data Base, HDB. Further it maintains the retrieval catalog files DTSF and MRF, which are used by the retrieval system SRR. 1.2 ABBREVIATIONS Ref DATA I/F MANUAL (ref I). ┆
0x18a00…18b00 (24, 0, 10) Sector 180bff00318241 ┆ 1 A W 2 APPLICABLE DOCUMENTS I FIX/0100/MAN/0004 FIKS DATA I/F REFERENCE II FIX/1256/PSP/0078 QACCESS MONITOR PSP III FIX/1256/PSP/0066 MTCB MONITOR PSP IV┆
0x18b00…18c00 (24, 0, 11) Sector 180cff00318241 ┆ 1 A FIX/1256/PSP/0057 LOG JOUR MONITOR PSP V FIX/1153/PSP/0097 SRS SUBMODULE PSP VI FIX/1000/EWP/0080 FIKS S/W CONFIGURATION CONTROL LIB.DESCR.DOC. VII FIX/1200/PSP/0042 FIKS FILE GENERATORS┆
0x18c00…18d00 (24, 0, 12) Sector 180d4400318241 ┆ D 1 A PSP VIII FIX/0000/TRP/0085 SYSTEM TEST REPORT 3010 ............... 1 1.1 Introduction .............................. 1 1.2 ABBREVIATIONS .............................. 1 2 APPLICABLE DOCUMENTS ........................... ┆
0x18d00…18e00 (24, 0, 13) Sector 180eff00318241 ┆ 1 A W 3 MODULE SPECIFICATION 3.1 Functional capabilities The SRS is the interface to the HDB. It supports storage on the HDB, deletion of messages on the HDB and retrieval of messages┆
0x18e00…18f00 (24, 0, 14) Sector 180fff00318241 ┆ 1 A from the HDB. Storage All message categories (non control messages) are stored except for Special Handling Category messages. Deletion The SRS maintains the HDB by deletion of oldest messages. Deletion is performed when there is not space┆
0x18f00…19000 (24, 0, 15) Sector 1800d400318241 ┆ T 1 A available for storage of next message. At this event messages are deleted to insure 1) A preset amount of time for storage 2) A preset number of messages 39 A preset amount of space for message text. .......... 54 3.3.10 READ MRF REC ....┆
0x19000…19100 (25, 0, 0) Sector 1901ff00318241 ┆ 1 A..................... 56 3.3.11 READ DTGF ENT ........................ 58 3.3.12 CALC REC FRGE ON MRF (Delete utility Procedure) ........................... 60 3.3.13 CALCULATE MTF SPACE (DELET utility procedu┆
0x19100…19200 (25, 0, 1) Sector 1902ff00318241 ┆ 1 Are) ........................... 62 3.3.14 DECODE BIN H (PROCESS MESS utility procedure) ........................... 64 3.3.15 DECODE SICS (PROCESS Mess utility procedure) ........................... 66 ┆
0x19200…19300 (25, 0, 2) Sector 1903ff00318241 ┆ 1 A 3.3.16 DECODE AIG M (PROCESS MESS utility procedure) ........................... 68 3.3.17 GET MEDE NO (PROCESS MESS utility procedure) ........................... 70 3.3.18 UPD TERM BNIT M (PROCESS MESS u┆
0x19300…19400 (25, 0, 3) Sector 19044600318241 ┆ F 1 Atility procedure) ........................... 70 " " " " " " " " A32 CIA-A 4.04202-01 ┆
0x19400…19500 (25, 0, 4) Sector 1905ff00318241 ┆ 1 A W 3.4 DATA ORGANIZATION .......................... 72 3.5 Storage Allocation ......................┆
0x19500…19600 (25, 0, 5) Sector 1906ff00318241 ┆ 1 A... 80 3.6 Performance Characteristics ................ 80 3.7 Limitations ................................ 80 3.8 Error Codes/Error Locations ................ 80 3.9 Listing References ......................... 83 4 Quality Assu┆
0x19600…19700 (25, 0, 6) Sector 1907ff00318241 ┆ 1 Arance .............................. 84 4.1 Qualification Tests ........................ 84 4.2 Other Quality Assurance Provisions ......... 84 5 Preparations for Delivery ...................... 85 6 Notes ..........................┆
0x19700…19800 (25, 0, 7) Sector 18085600318241 ┆ V 1 A................ 86 7 Appendices ..................................... 86 ┆
0x19800…19900 (25, 0, 8) Sector 1909ff41318241 ┆ A1 A3182A FIX/1153/PSP/0097 lbe OK SRS Subsystem PSP 20 12 82 10 41 5 12 17160 17 02 83 09 10 07 372 17 02 83 13 16 22 02 83 09 13 0282A 87 6 34 408 20137 @ ' *J B = _┆
0x19900…19a00 (25, 0, 9) Sector 190a5700318241 ┆ W 1 A at]r: Forfatter: Kommentarer: STATISTIK AKAKAKAKAKAKAK┆
0x19a00…19b00 (25, 0, 10) Sector 190ba400318241 ┆ $ 1 A 1 FIX/1153/PSP/0097 OK/830216 SRS Subsystem PSP OK/821216 FK 7809 !/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x19b00…19c00 (25, 0, 11) Sector 190cff00318241 ┆ 1 A 1 TABLE OF CONTENTS Page W ┆
0x19c00…19d00 (25, 0, 12) Sector 190dff00318241 ┆ 1 A 1 Scope .......................................... 1 1.1 Introduction .............................. 1 1.2 ABBREVIATIONS .............................. 1 2 APPLICABLE DOCUMENTS ........................... ┆
0x19d00…19e00 (25, 0, 13) Sector 190eff00318241 ┆ 1 A2 3 MODULE SPECIFICATION ........................... 3 3.1 Functional capabilities .................... 3 3.2 Interface Description ...................... 19 3.3 Processing ................................. 20 3.3.1 STORAGE (Mai┆
0x19e00…19f00 (25, 0, 14) Sector 190fff00318241 ┆ 1 An module). ................. 22 3.3.2 INIT STORAGE ........................... 25 3.3.3 GET QUEUE ELEM ......................... 28 3.3.4 TEST SPACE ............................. 30 3.3.5 DELETION ............................... ┆
0x19f00…1a000 (25, 0, 15) Sector 1900ff00318241 ┆ 1 A33 3.3.6 PROCESS MESS ........................... 39 3.3.7 U MRF DTGF ............................. 46 3.3.8 UPD PARAM .............................. 52 3.3.9 DEL Q ELEM ............................. 54 3.3.10 READ MRF REC ....┆
0x1a000…1a100 (26, 0, 0) WangDocumentBody
[…0x3…]
0x1a400…1a500 (26, 0, 4) Sector 1a05ff00318241 ┆ 1 Aeferring a local terminal give the retrieval right to this terminal. The MRF record for the message is formed of the ex- tracted information together with the MTF address of the firs sector of the message, the retrieval time and the message┆
0x1a500…1a600 (26, 0, 5) Sector 1a06ff00318241 ┆ 1 A length from the MTCB The in-memory subset of the MRF(which is a part of the critical region SRS CR) is updated with the record. If the in-memory subset of the MRF hereby gets full, a transfer to the MRF is performed. (The storage process await ┆
0x1a600…1a700 (26, 0, 6) Sector 1a072200318241 ┆ " 1 Atermination). (fig. 3.1-3). is the MRF record number of the first message in this DTG. If no message has re- trieval time equal to this DTG the DTGF entry is the MRF record number of the first message after this DTG. The MRF consists of 44800 r┆
0x1a700…1a800 (26, 0, 7) Sector 1908ff00318241 ┆ 1 A W If the retrieval DTG of the message (obtained from the MTCB) is superior to the retrieval time of the last stored message, update of the in-memory subset of the DTGF (which resid┆
0x1a800…1a900 (26, 0, 8) WangDocumentBody
[…0xff…]
0x2a800…2a900 (42, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(42,0, 9), len=0xff, h3=41319541}, f00=»3195A «, f01=»FIX/3232/PSP/0033 «, f02=»ja «, f03=»CAH «, f04=»Fra Kptl. 11 «, f05=22-12-82 10:54, f06=» 1 «, f07=»37 «, f08=» 3120 «, f09=04-01-83 14:35, f10=» «, f11=»10 «, f12=» 293 «, f13=22-12-82 14:28, f14=18-01-83 13:32, f15=»0282A «, f16=»105 «, f17=» 1 «, f18=»48 «, f19=» 516 «, f20=» 3488 «, f21=» «, f22=» «, f99=020010000110056610110190aaca1505000000000000014203e900df}
0x2a900…2aa00 (42, 0, 9) WangDocumentBody
[…0x14…]
0x2be00…2bf00 (43, 0, 14) Sector 00000000000000 ┆ ┆
[…0x1…]
0x2c000…2c100 (44, 0, 0) WangDocumentBody
[…0x1af…]
0x47000…47100 (71, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(71,0, 1), len=0xff, h3=41314341}, f00=»3143A «, f01=»FIX/1154/PSP/0107 «, f02=»io «, f03=»JL «, f04=»Fra Kptl. 3.3.4.3.2 «, f05=10-12-82 11:34, f06=» 3 «, f07=»30 «, f08=» 16931 «, f09=15-08-84 09:58, f10=» «, f11=»00 «, f12=» 2 «, f13=01-07-83 13:59, f14=04-12-84 09:42, f15=»0282A «, f16=» 78 «, f17=» 8 «, f18=»21 «, f19=» 464 «, f20=» 23221 «, f21=» «, f22=» 0 «, f99=430000000110052710110180aaca1505000000000000004203c400df}
0x47100…47200 (71, 0, 1) WangDocumentBody
[…0x1e…]
0x49000…49100 (73, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(73,0, 1), len=0xff, h3=41314141}, f00=»3141A «, f01=»FIX/1154/PSP/0107 «, f02=»ut «, f03=»JL «, f04=»NSS «, f05=10-12-82 11:31, f06=» 14 «, f07=»35 «, f08=» 70527 «, f09=20-07-83 11:09, f10=» «, f11=»00 «, f12=» 2 «, f13=05-07-83 14:17, f14=25-07-84 13:20, f15=»0282A «, f16=» 84 «, f17=» 23 «, f18=»59 «, f19=» 904 «, f20=» 93607 «, f21=» «, f22=» «, f99=300000000110252710110290aaca15050000000000000042033801df}
0x49100…49200 (73, 0, 1) WangDocumentBody
[…0x1e…]
0x4b000…4b100 (75, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(75,0, 1), len=0xff, h3=41309841}, f00=»3098A «, f01=»FIKS s/w Configuration «, f02=»lbe (vikar) «, f03=»HFJ «, f04=»FIX/1000/EWP/0080 «, f05=01-12-82 10:45, f06=» 1 «, f07=»07 «, f08=» 3093 «, f09=24-01-83 09:54, f10=» «, f11=»12 «, f12=» 797 «, f13=24-01-83 14:34, f14=27-01-83 14:34, f15=»0282A «, f16=» 7 «, f17=» 1 «, f18=»20 «, f19=» 64 «, f20=» 3897 «, f21=» «, f22=» «, f99=020010000110052710110280aaca15050000000000000142031600df}
0x4b100…4b200 (75, 0, 1) WangDocumentBody
[…0x6…]
0x4b800…4b900 (75, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(75,0, 9), len=0xff, h3=41317141}, f00=»3171A «, f01=»FIX/1153/PSP/0096 «, f02=»lbe «, f03=»ok «, f04=»SRR Subsyst.PSP «, f05=16-12-82 15:32, f06=» 11 «, f07=»43 «, f08=» 27715 «, f09=21-09-88 14:45, f10=» «, f11=»01 «, f12=» 20 «, f13=19-09-88 15:35, f14=19-12-88 12:31, f15=»0282A «, f16=» 64 «, f17=» 16 «, f18=»42 «, f19=» 464 «, f20=» 31838 «, f21=» «, f22=» «, f99=410001000200052710110480aaca1704000000000000014203b300df}
0x4b900…4ba00 (75, 0, 9) WangDocumentBody
[…0x6…]
0x4c000…4c100 (76, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(76,0, 1), len=0xff, h3=41317141}, f00=»3171A «, f01=»FIX/1153/PSP/0096 «, f02=»lbe «, f03=»ok «, f04=»SRR Subsyst.PSP «, f05=16-12-82 15:32, f06=» 11 «, f07=»43 «, f08=» 27715 «, f09=27-01-83 11:07, f10=» «, f11=»07 «, f12=» 115 «, f13=27-01-83 11:31, f14=27-01-83 14:34, f15=»0282A «, f16=» 62 «, f17=» 12 «, f18=»56 «, f19=» 444 «, f20=» 29848 «, f21=» «, f22=» P «, f99=350000000110052710110180aaca15050000000000000142039900df}
0x4c100…4c200 (76, 0, 1) Sector 4c023e00317141 ┆L > 1qA L L K K + + DOKUMENTOVERSIGT Dokument nr: Dokumentnavn┆
0x4c200…4c300 (76, 0, 2) Sector 4c039a00317141 ┆L 1qA 1 FIX/1153/PSP/0096 OK/821216 SRR Subsystem PSP FK 7809 %-!/=6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x4c300…4c400 (76, 0, 3) Sector 4c04ff00317141 ┆L 1qA W LIST OF CONTENTS W ┆
0x4c400…4c500 (76, 0, 4) Sector 4c05ff00317141 ┆L 1qA Page 1 SCOPE .......................................... 1 1.1 Introduction ............................... 1 1.2 Abbreviations .............................. 1 2 APPLICABLE DOCUMENTS ........................... ┆
0x4c500…4c600 (76, 0, 5) Sector 4c06ff00317141 ┆L 1qA1 3 MODULE SPECIFICATION ........................... 2 3.1 Functional Capabilities .................... 2 3.2 INTERFACE DESCRIPTION ...................... 10 3.3 PROCESSING.................................. 12 3.3.1 SRR INIT ..┆
0x4c600…4c700 (76, 0, 6) Sector 4c07ff00317141 ┆L 1qA............................. 16 3.3.2 RMAIN: ................................. 18 3.3.3 GET RTR Q ELEM ......................... 20 3.3.4 R MID .................................. 22 3.3.5 RDTGR ..................................┆
0x4c700…4c800 (76, 0, 7) Sector 4b08ff00317141 ┆K 1qA 24 3.3.6 RDTDS .................................. 26 3.3.7 RMLOG .................................. 28 3.3.8 QUEUE MTCBS ............................ 30 3.3.9 DEL RTR Q ELEM ......................... 32 3.3.10 RRDTG .......┆
0x4c800…4c900 (76, 0, 8) Sector 00000000000000 ┆ ┆
[…0x7…]
