OctetView
0x00000…00100 (0, 0, 0) Sector 00914130303931 ┆ A0091A ┆
0x00100…00200 (0, 0, 1) Sector 00000000000000 ┆ ┆
0x00200…00300 (0, 0, 2) Sector ff00f0fffcfeff ┆ p |~ xx x p ┆
0x00300…00306 (0, 0, 3) WangDocument {d00=0x13, d01=0x68, d02=0x41, ptr=(58,0, 0), d05=0x00}
0x00306…0030c WangDocument {d00=0x13, d01=0x76, d02=0x41, ptr=(17,0, 8), d05=0x00}
0x0030c…00312 WangDocument {d00=0x13, d01=0x77, d02=0x41, ptr=(18,0, 8), d05=0x00}
0x00312…00318 WangDocument {d00=0x13, d01=0x78, d02=0x41, ptr=(26,0, 8), d05=0x00}
0x00318…0031e WangDocument {d00=0x13, d01=0x79, d02=0x41, ptr=(31,0, 8), d05=0x00}
0x0031e…00324 WangDocument {d00=0x13, d01=0x80, d02=0x41, ptr=(37,0, 8), d05=0x00}
0x00324…0032a WangDocument {d00=0x13, d01=0x81, d02=0x41, ptr=(45,0, 8), d05=0x00}
0x0032a…00340 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ ┆
0x00340…00360 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ ┆
[…0x4…]
0x003e0…00400 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2a ┆ *┆
0x00400…00500 (0, 0, 4) Sector 00000000000000 ┆ ┆
0x00500…00600 (0, 0, 5) Sector 00914130303931 ┆ A0091A ┆
0x00600…00700 (0, 0, 6) Sector 421c402600415b ┆B @& A[' . T% %( PO P ; yAt C f x f V W! O 7 :S X9 s 1379A f T < {C < { ; 5 ` i x b bD K : 8 9 t xky 0 1378A1379A Y7j ] u I=v I4 ┆
0x00700…00800 (0, 0, 7) Sector 00000000000000 ┆ ┆
[…0x8…]
0x01000…01100 (1, 0, 0) WangDocumentBody
[…0x3…]
0x01400…01500 (1, 0, 4) Sector 0105ce00137641 ┆ N vAses to a DAMOS object High level security checks are performed by the queue monitor based on: - queue profiles and subprocess profiles - access capabilities for a subprocess to queue elements ing of mount/dismount on the off-line disk d) E┆
0x01500…01600 (1, 0, 5) Sector 00000600137641 ┆ vArror reports, when the WDP LP is out of service. 3.3.2.2 TEP to SSC a) Execution of supervisor control of VDU, SAD instances b) Release security interrogation c) Perform system integrity check 3.3.2.3 SSC to MMON/MMS a) Start-up b) H┆
0x01600…01700 (1, 0, 6) Sector 00000000000000 ┆ ┆
[…0x1…]
0x01800…01900 (1, 0, 8) WangDocumentBody
[…0xd…]
0x02600…02700 (2, 0, 6) Sector 00008400137741 ┆ wA.4 Functions Maintained by Other Packages TMP is supported by Coroutine Monitor and System Call Monitor in the CSF package. check pointing. All data except global number series will be copied to disk each time they are updated so they will alwa┆
0x02700…02800 (2, 0, 7) Sector 0108ff00137641 ┆ vA 1 3.3.2.5 SSC to MMS Via MMON as specified in 3.3.2.3. 3.3.2.6 SSC to CSF Process a) Start-up b) Close-down 3.3.2.7 SSC to QMON a) Start-up b) Close-down c) Initiali┆
0x02800…02900 (2, 0, 8) WangDocumentBody
[…0x6…]
0x02f00…03000 (2, 0, 15) Sector 02004a00137741 ┆ J wAe in two incarnations. The throughput will increase about 50%. ivered. 5.12.2.2.1.2 Update Of Table One record is changed, inserted in a table or removed from a table. 5.12.2.2.1.3 Reorganization Of Tables A table is reorganized so un┆
0x03000…03100 (3, 0, 0) WangDocumentBody
[…0xe7…]
0x11800…11900 (17, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(17,0, 9), len=0xff, h3=41137641}, f00=»1376A «, f01=»CPS/SDS/001 «, f02=»vhn «, f03=»FH «, f04=»kapitel 5.11 «, f05=12-10-81 10:42, f06=» 1 «, f07=»11 «, f08=» 3573 «, f09=03-11-81 13:05, f10=» «, f11=»12 «, f12=» 401 «, f13=03-11-81 13:17, f14=03-11-81 16:01, f15=»0091A «, f16=» 58 «, f17=» 1 «, f18=»27 «, f19=» 672 «, f20=» 4217 «, f21=» «, f22=» «, f99=400010000110066610110480aaca1505000000000000013703e400df}
0x11900…11a00 (17, 0, 9) WangDocumentBody
[…0xe…]
0x12800…12900 (18, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(18,0, 9), len=0xff, h3=41137741}, f00=»1377A «, f01=»CPS/SDS/001 «, f02=»vhn «, f03=»BMN «, f04=»Kapitel 5.12 «, f05=12-10-81 10:47, f06=» «, f07=»46 «, f08=» 2079 «, f09=03-11-81 13:27, f10=» «, f11=»01 «, f12=» 8 «, f13=03-11-81 13:28, f14=03-11-81 16:01, f15=»0091A «, f16=» 12 «, f17=» «, f18=»53 «, f19=» 136 «, f20=» 2360 «, f21=» «, f22=» «, f99=200010000110066610110480aaca15050000000000000137032f00df}
0x12900…12a00 (18, 0, 9) WangDocumentBody
[…0x13…]
0x13d00…13e00 (19, 0, 13) Sector 130eff00137641 ┆ vA Data Elements ................ 151 4.1.5.1 QMON Buffers ...................... 151 4.1.5.2 Checkpoint Area in Active PU ...... 152 4.1.5.3 Checkpoint Area in Standby ........ 153 4.1.5.4 System Parameters ................. ┆
0x13e00…13f00 (19, 0, 14) Sector 130fff00137641 ┆ vA154 4.1.6 Interfaces ............................ 154 4.1.6.1 External Interfaces ............... 155 4.1.6.2 Package Interfaces ................ 155 4.1.6.2.1 SSC to TEP .................... 155 4.1.6.2.1.1 SSC to TE┆
0x13f00…14000 (19, 0, 15) Sector 1300ff00137641 ┆ vAP VDU Subprocess . 156 4.1.6.2.1.2 SSC to TEP SAD Subprocess . 158 4.1.6.2.1.3 Error Reports ............. 158 4.1.6.2.1.4 SSC to TEP (Off-line disk) 159 4.1.6.2.1.5 SSC to TEP Non-Line Process .........┆
0x14000…14100 (20, 0, 0) WangDocumentBody
[…0x4…]
0x14500…14600 (20, 0, 5) Sector 1406ff00137641 ┆ vAware ............. 114 4.1.1.9 Common SSC Functions .............. 115 4.1.2 SW Structure .......................... 117 4.1.3 Data Flow and Control Logic ........... 123 4.1.3.1 COPSY Coroutines Data Flow and Contr┆
0x14600…14700 (20, 0, 6) Sector 1407ff00137641 ┆ vAol Logic ..................... 123 4.1.3.1.1 CMO Coroutine Data Flow and Control Logic ................. 125 4.1.3.1.2 SEH Coroutine Data Flow and Control Logic ................. 125 4.1.3.1.3 M-C Coroutine┆
0x14700…14800 (20, 0, 7) Sector 1308ff00137641 ┆ vA Data Flow and Control Logic ................. 126 4.1.3.1.3.1 Reception of Commands in Operational Semaphores .... 126 4.1.3.1.3.2 Operational Commands to a Subprocess, CPT, CMI ...... 126 ┆
0x14800…14900 (20, 0, 8) WangDocumentBody
[…0x5f…]
0x1a800…1a900 (26, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(26,0, 9), len=0xff, h3=41137841}, f00=»1378A «, f01=»CPS/SDS/001 «, f02=»vhn «, f03=»KNB «, f04=»Kapitel 5.13 «, f05=12-10-81 10:56, f06=» «, f07=»35 «, f08=» 2494 «, f09=03-11-81 13:25, f10=» «, f11=»04 «, f12=» 145 «, f13=03-11-81 13:32, f14=24-05-83 17:45, f15=»0091A «, f16=» 26 «, f17=» «, f18=»45 «, f19=» 360 «, f20=» 2849 «, f21=» «, f22=» «, f99=200010000110066610110480aaca15050000000000000037037600df}
0x1a900…1aa00 (26, 0, 9) WangDocumentBody
[…0x4e…]
0x1f800…1f900 (31, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(31,0, 9), len=0xff, h3=41137941}, f00=»1379A «, f01=»CPS/SDS/001 «, f02=»vhn «, f03=»NJ «, f04=»Kapitel 5.14 «, f05=12-10-81 11:00, f06=» «, f07=»28 «, f08=» 2008 «, f09=03-11-81 13:34, f10=» «, f11=»15 «, f12=» 177 «, f13=03-11-81 13:50, f14=24-05-83 17:45, f15=»0091A «, f16=» 19 «, f17=» «, f18=»49 «, f19=» 256 «, f20=» 2435 «, f21=» «, f22=» «, f99=200010000110066610110480aaca15050000000000000137035500df}
0x1f900…1fa00 (31, 0, 9) WangDocumentBody
[…0x5e…]
0x25800…25900 (37, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(37,0, 9), len=0xff, h3=41138041}, f00=»1380A «, f01=»CPS/SDS/001 «, f02=»vhn «, f03=»BBC «, f04=»Kapitel 5.15 «, f05=12-10-81 11:10, f06=» «, f07=»18 «, f08=» 1583 «, f09=03-11-81 13:50, f10=» «, f11=»06 «, f12=» 102 «, f13=03-11-81 14:04, f14=03-11-81 16:02, f15=»0091A «, f16=» 26 «, f17=» «, f18=»26 «, f19=» 292 «, f20=» 1911 «, f21=» «, f22=» «, f99=100010000110066610110480aaca15050000000000000137036500df}
0x25900…25a00 (37, 0, 9) WangDocumentBody
[…0xb…]
0x26500…26600 (38, 0, 5) Sector 2606ff00138041 ┆& A 1 5.15.1.3.2 Abbreviations 1 DIDIA Delivery Dialogue Coroutine DIFCO Delivery Function Control Coroutine DIRT D┆
0x26600…26700 (38, 0, 6) Sector 2607ff00138041 ┆& Aelivery Retrieval Coroutine DIVCO Delivery VDU Control Coroutine DELCO Delivery Control Coroutine MDO VDU MDCO Package MDOS VDU MDCO Subprocess MSO VDU Message Service Package MSOS VDU Message Service Subprocess OCCO OCR Control Coro┆
0x26700…26800 (38, 0, 7) Sector 2508ff00138041 ┆% Autine OCIP OCR Input Coroutine OCP OCR Package ORF Outstanding Reports File PAC Preparation Data Base Access Control Coroutine PPF Print Format File PRI Printer Package PRIS User Printer Process PROP Printer Output Coroutine R┆
0x26800…26900 (38, 0, 8) WangDocumentBody
[…0x6f…]
0x2d800…2d900 (45, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(45,0, 9), len=0xff, h3=41138141}, f00=»1381A «, f01=»CPS/SDS/001 «, f02=»vhn «, f03=»RIM «, f04=»Kapitel 5.16 «, f05=12-10-81 11:15, f06=» «, f07=»31 «, f08=» 2053 «, f09=07-04-82 14:28, f10=» «, f11=»01 «, f12=» 22 «, f13=07-04-82 14:29, f14=15-04-82 10:43, f15=»0091A «, f16=» 27 «, f17=» 1 «, f18=»07 «, f19=» 384 «, f20=» 2454 «, f21=» «, f22=» «, f99=910010000110066610110480aaca15050000000000000137037d00df}
0x2d900…2da00 (45, 0, 9) WangDocumentBody
[…0xa…]
0x2e400…2e500 (46, 0, 4) Sector 2e05ff00138141 ┆. Aeast 30 days on offline disk volumes (long term storage). SAR supports retrieval of CIFS from the intermediate storage within a specified time limit. Retrieving off-line is possible within a time limit to be specified measured from when off-line┆
0x2e500…2e600 (46, 0, 5) Sector 2e06ff00138141 ┆. A volume is mounted. The functions carried out by SAR are then: - Retrieve on-line - Store on-line - Store off-line - Retrieve off-line 5.16.2.1.1.1 On-Line Storage The on-line CIFs handled by SAR are on-line resident for at least 24 hours.┆
0x2e600…2e700 (46, 0, 6) Sector 2e07ba00138141 ┆. : A On-line storage is characterized by the fact that no mounting of physical media is required to retrieve the CIF. Actual time span for on-line storage is in the order of days. ut .................... 28 5.16.2.3.1.4 Traffic Load .......┆
0x2e700…2e800 (46, 0, 7) Sector 2d08ff00138141 ┆- A 1 5.16.2.1.1.2 Off-Line Storage An off-line storage process is carried out by dumping CIF to an off-line volume, when they have been on-line resident for at least 24 hours. Off-lin┆
0x2e800…2e900 (46, 0, 8) WangDocumentBody
[…0xb7…]
0x3a000…3a100 (58, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(58,0, 1), len=0xff, h3=41136841}, f00=»1368A «, f01=»CPS/SDS/001 «, f02=»vhn «, f03=»SRA «, f04=»Kapitel 5.3 «, f05=12-10-81 08:49, f06=» «, f07=»12 «, f08=» 786 «, f09=07-06-82 12:17, f10=» «, f11=»10 «, f12=» 387 «, f13=09-06-82 15:21, f14=09-06-82 20:32, f15=»0091A «, f16=» 47 «, f17=» 7 «, f18=»31 «, f19=» 588 «, f20=» 21649 «, f21=» «, f22=» 0 «, f99=430010000110066610110480aaca1505000000000000013703c400df}
0x3a100…3a200 (58, 0, 1) WangDocumentBody
[…0x6…]
0x3a800…3a900 (58, 0, 8) Sector 3a09ff00136841 ┆: hAontains distribution equipment and a line terminating unit. Two types of line terminating units exist - Line terminating unit of the LTU type (I/O BUS I/F) - Line terminating units of the LTUX type (TDX BUS I/F) Common to all DECs is the ele┆
0x3a900…3aa00 (58, 0, 9) Sector 3a0aff00136841 ┆: hActrical interface specification between a line terminating unit and its associated distribution equipment. This I/F conforms to the CCITT V24/V28 recommendations. To adapt this internal standard interface to the various interface requirements of the┆
0x3aa00…3ab00 (58, 0, 10) Sector 3a0bff00136841 ┆: hA terminals and external circuits, collocated or remote, three main types of distribution equipment are involved: - Optical link distribution - Low level V24/V28 distribution - Statistical mux/demux distribution 5 categories of DECs are imple┆
0x3ab00…3ac00 (58, 0, 11) Sector 3a0cff00136841 ┆: hAmented to satisfy interface and security requirements when connecting terminals and external circuits to CAMPS. These are as shown in fig. 5.3.2-1. The line termination modules are placed within CAMPS in either a TDX Unit shown in fig. 5.3.2-2 or ┆
0x3ac00…3ad00 (58, 0, 12) Sector 3a0d2d00136841 ┆: - hAa CHANNEL UNIT shown in fig. 5.3.2-3. .................. 201 5.3.2 Distribution & Monitoring Equipment/ Facilities ........................... 201 5.3.2.1 DEC - Category 1 ................. 209 5.3.2.2 DEC - Category 2 .....┆
0x3ad00…3ae00 (58, 0, 13) Sector 3a0ec500136841 ┆: E hA 1 Some of the Distribution Equipment modules are also placed in either a TDX Unit or an Adapter Crate (ref. sec. 5.3.3.3). nal Adaption ...................... 5.3.3.1 The ┆
0x3ae00…3af00 (58, 0, 14) Sector 3a0fa100136841 ┆: ! hA 1 FIGURE 5.3.1-1 CAMPS H/W CONFIGURATION st of Distribution Equipment ....... 217 5.3.5 Appendix A ........................... 21┆
0x3af00…3b000 (58, 0, 15) Sector 3a00a500136841 ┆: % hA 1 FIGURE 5.3.2-1 DATA EXHANGE CHANNEL MATRIX :8=F 28=I!#<:"<>R<2> I E*#<& "< DM L<M% :#<F 2#<> I:g= Ro2M/2 Rl2> IC13!?=4~~ B|2> I:A=!┆
0x3b000…3b100 (59, 0, 0) Sector 3b01ff00136841 ┆; hA 1 5.3 DISTRIBUTION, MONITORING & TEST (DM&T) DESIGN 5.3.1 General The aim of this section is to explain the design of the DM&T equipment/facilities as implemented in the present ┆
0x3b100…3b200 (59, 0, 1) Sector 3b02ff00136841 ┆; hACAMPS H/W configuration shown in fig. 5.3.1-1. 5.3.2 Distribution & Monitoring Equipment/Facilities The present CAMPS system interfaces to terminals and external circuits, both in a collocated and a remote configuration. The main difference b┆
0x3b200…3b300 (59, 0, 2) Sector 3b03ff00136841 ┆; hAetween a collocated and a remote configuration is that data exchange in the remote configuration involves VF-Modem links carrying encrypted data (crypto/modem link). The types of terminals in collocated configurations are: 1 ┆
0x3b300…3b400 (59, 0, 3) Sector 3b04ff00136841 ┆; hA - Visual Display Unit (VDU) - Medium Speed Teleprinter (MSP) - Low Speed Channel Device (i.e TTY) (LSC) - Optical Character Reader (OCR) - Paper Tape Puncher (PTP) - Paper Tape Reader (PTR) The re┆
0x3b400…3b500 (59, 0, 4) Sector 3b05ff00136841 ┆; hAmote terminal configuration is only applicable to a subset of these namely: - VDU - MSP Furthermore, the remote terminal concept involves a statistical multiplexing/demultiplexing system minimizing the number of crypto/modem links. The types ┆
0x3b500…3b600 (59, 0, 5) Sector 3b063e00136841 ┆; > hAof external circuits in collocated configurations are: ┆
0x3b600…3b700 (59, 0, 6) Sector 3b07ff00136841 ┆; hA 1 - NICS/TARE - SCARS - CCIS The remote external circuits configuration is only applicable to NICS TARE. Terminals and external circuits, collocated or remote, are connected to┆
0x3b700…3b800 (59, 0, 7) Sector 3a08ff00136841 ┆: hA CAMPS via the Distribution Equipment. The path for data exchange between CAMPS and one collocated/remote terminal type or one collocated/remote external circuit type will in the following be referenced to as a Data Exchange Channel (DEC). A DEC c┆
0x3b800…3b900 (59, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(59,0, 9), len=0xff, h3=41136841}, f00=»1368A «, f01=»CPS/SDS/001 «, f02=»vhn «, f03=»SRA «, f04=»Kapitel 5.3 «, f05=12-10-81 08:49, f06=» «, f07=»12 «, f08=» 786 «, f09=14-04-82 17:18, f10=» «, f11=»14 «, f12=» 243 «, f13=14-04-82 17:40, f14=15-04-82 10:45, f15=»0091A «, f16=» 47 «, f17=» 7 «, f18=»17 «, f19=» 692 «, f20=» 21048 «, f21=» «, f22=» «, f99=420010000110066610110480aaca1505000000000000013703c300df}
0x3b900…3ba00 (59, 0, 9) Sector 3b0a2f00136841 ┆; / hA ; ; ; ; : : : : : : : 9 9 9 9 8 8 8 8 7 7 6 6 6 6 5 5 5 5 4 4 3 3 3 2 2 2 2 2 2 1 1 1 1 1 0 0 / : Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG OprettSLAG OprettttSLAG Opretttt┆
0x3ba00…3bb00 (59, 0, 10) Sector 3b0ba500136841 ┆; % hA 1 CPS/SDS/001 SRA/820402 CAMPS SYSTEM DESIGN SPECIFICATION ISSUE 1.2 CAMPS /=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x3bb00…3bc00 (59, 0, 11) Sector 3b0cff00136841 ┆; hA 1 1 TABLE OF CONTENTS 5.3 DISTRIBUTION, MONITORING & TEST (DM&T) DESIGN ................................┆
0x3bc00…3bd00 (59, 0, 12) Sector 3b0dff00136841 ┆; hA... 201 5.3.1 General .............................. 201 5.3.2 Distribution & Monitoring Equipment/ Facilities ........................... 201 5.3.2.1 DEC - Category 1 ................. 209 5.3.2.2 DEC - Category 2 .....┆
0x3bd00…3be00 (59, 0, 13) Sector 3b0eff00136841 ┆; hA............ 211 5.3.2.3 DEC - Category 3 ................. 213 5.3.2.4 DEC - Category 4 ................. 215 5.3.2.5 DEC - Category 5 ................. 217 5.3.3 Signal Adaption ...................... 5.3.3.1 The ┆
0x3be00…3bf00 (59, 0, 14) Sector 3b0fff00136841 ┆; hAV24/V28 (L/L) Adapters........ 5.3.3.2 The OPTO TRANSCEIVERS ............ 5.3.3.3 The Adapter Crate ................ 5.3.4 Test of Distribution Equipment ....... 217 5.3.5 Appendix A ........................... 21┆
0x3bf00…3c000 (59, 0, 15) Sector 3b000900136841 ┆; hA7 {! ;6 ! <6 MM(! "(=~~ J*2M2/C<2:^=~ B<2:b= R<2M/,:g=~ BG2M")M2&! "(=~~ BW2I! <6 M /M?.I*:="8=IM2&MP'Mc2! m"2< [MI !?=6 : #wI>K!8=>R 2!8=6 #4 E*8=k L<M% :8=F 28=I!#<:"<>R<2> I E*#<& "< DM L<M% :#<F 2#<> I:g= Ro2M/2 Rl2> IC13!?=4~~ B|2> I:A=!┆
0x3c000…3c100 (60, 0, 0) Sector 3c01ff00138141 ┆< A 1 Further the filling rate of intermediate storage is set by the MMS command SET INTERMEDIATE STORAGE THRESHOLD. 2.2.2.1.2 Close-Down Close-down of SAR is performed this way. SA┆
0x3c100…3c200 (60, 0, 1) Sector 3c02ff00138141 ┆< AR will operate normally until close-down command from SSC is received. Detailed close-down action is described in 4.2.5.1.9. 2.2.2.1.3 Restart Start-up command from SSC causes SAR to take the following actions. Checkpointed ISQ is re-establishe┆
0x3c200…3c300 (60, 0, 2) Sector 3c03ff00138141 ┆< Ad so all pending storage requests are queued again. Main memory control area is initialized as described under initialization. Semaphore and status information is set to the values as contained in the initialization section. 2.2.2.2 Checkpointing┆
0x3c300…3c400 (60, 0, 3) Sector 3c04ff00138141 ┆< A and Recovery 2.2.2.2.1 Checkpointing Storage requests for SAR are checkpointed i.e. ISQ QELs are checkpointed at their arrival to queue and released when storage procedure has terminated. 2.2.2.2.2 Recovery Recovery of SAR is requested by┆
0x3c400…3c500 (60, 0, 4) Sector 3c059400138141 ┆< A SSC. SSC specifies which kind of recovery to be performed. Recovery actions performed are described in CPS/SDS/001 figure 5.10.1.2.1.3-1. e is mounted or cannot intermediately be mounted. When mounted MMS is asked to open the off-line volumes┆
0x3c500…3c600 (60, 0, 5) Sector 3c06ff00138141 ┆< A 1 2.2.2.3 Error Detection and Error Handling 2.2.2.3.1 Error Detection Errors detected by SAR are of the following types: - Errors in storage keys during storage of messages an┆
0x3c600…3c700 (60, 0, 6) Sector 3c07ff00138141 ┆< Ad transactions - Error code received during CSF section dump - QMON delivery error - Software errors 2.2.2.3.2 Error Handling The previous mentioned detected errors (refer 2.2.2.3.1) are handled in the following way, described in the same┆
0x3c700…3c800 (60, 0, 7) Sector 3b08ff00138141 ┆; A order as they are detected. - Storage request and retrieval keys are delivered to SSC error queue. - Error handling, caused by failure in volume name in CSF section dump command is to complete dump as normal with a report to supervisors report ┆
0x3c800…3c900 (60, 0, 8) Sector 3c09a600138141 ┆< & Apletion codes. c) Off-Line Catalogue Display As for on-line retrieval the catalogue entries corresponding to the retrieval search keys are returned (2g). consulted to determine which CIFs to dump (3a) (3b) according to the TOC field in each C┆
0x3c900…3ca00 (60, 0, 9) Sector 3c0a6100138141 ┆< a A 1 Figure 2.2.1.3-1 ctions: - Dump CIF command for MMS (3c) - Dump CIF completion code for SAR (3d) - Update off-line catalogue (3e) - Update on-line catalogue (3f) - Clear┆
0x3ca00…3cb00 (60, 0, 10) Sector 3c0bff00138141 ┆< A 1 2.2.2 Functional Responsibilities Functional responsibilities included in the storage and retrieval package are specified in the next paragraphs. 2.2.2.1 Initialization, Close ┆
0x3cb00…3cc00 (60, 0, 11) Sector 3c0cff00138141 ┆< ADown, and Restart 2.2.2.1.1 Initialization Initialization procedure performs the initiation of main memory collect area catalogue files, semaphores and status information. Main memory is initiated by loading the control area with initial valu┆
0x3cc00…3cd00 (60, 0, 12) Sector 3c0dff00138141 ┆< Aes. The three locations shall be loaded: 1 PRI AREA: pri area start address DTG AREA: dtg area start address no of-PRI ENT 0 On-line catalogue files are created during initial┆
0x3cd00…3ce00 (60, 0, 13) Sector 3c0eff00138141 ┆< Aization. The TOC FILE ON locations in information area are all set to 0, except for TOC start time which is set upon first storage. Off-Line catalogue files are created and initiated when dump is incarnated. Volume table is initialized as an empty┆
0x3ce00…3cf00 (60, 0, 14) Sector 3c0fff00138141 ┆< A table with no entries. The following semaphores are initiated: - lock cat to neutral stage - off-line disk lock to neutral stage - lock table to neutral stage - off-line retrieval susp to neutral stage Status information is initiated as fo┆
0x3cf00…3d000 (60, 0, 15) Sector 3c005c00138141 ┆< \ Allows: - off-line retrieval on/off is reset to the value on - off-line count to 0 elivered to MMS (1c). MMS returns a view ref. referencing the generated temporary CIF (1d) which is handled further on by SAR to requestor after security and acce┆
0x3d000…3d100 (61, 0, 0) Sector 3d01ff00138141 ┆= Ass check (1e). b) Retrieval Completion Codes Improper completion of a retrieval procedure can be caused by: - Not found referenced CIF - Retrieval intermediately impossible Completion code is returned through step 1e. c) Catalogue Di┆
0x3d100…3d200 (61, 0, 1) Sector 3d02b300138141 ┆= 3 Asplay In case that a catalogue display is required the on-line catalogue is consulted. The entries fulfilling the retrieval key parameters are returned through step 1e. First Draft Storage after completion of new message preparation format A┆
0x3d200…3d300 (61, 0, 2) Sector 3d03ff00138141 ┆= A 1 2.2.1.3.2 Off-Line Retrieval According to the TOC retrieval parameter an off-line retrieval process is initiated. This is serviced at a lower priority level than on-line retrieval┆
0x3d300…3d400 (61, 0, 3) Sector 3d04ff00138141 ┆= A and will result in three different actions. a) Ordinary Off-Line Retrieval Ordinary off-line retrieval is carried out by requesting the supervisor to mount a specified volume (2a). Determination of volume is done by consulting a table contain┆
0x3d400…3d500 (61, 0, 4) Sector 3d05ff00138141 ┆= Aing information about time intervals on off-line volumes. As for off-line storage a completion code is returned (2b) telling whether the volume is mounted or cannot intermediately be mounted. When mounted MMS is asked to open the off-line volumes┆
0x3d500…3d600 (61, 0, 5) Sector 3d06ff00138141 ┆= A directory and CIF area by the command GET MMS CATALOGUE (2c). SAR consults the directory for determination of view-ref of wanted CIF (2d). A RETRIEVE CIF command is handed by SAR to MMS (2e), which returns the previously mentioned view ref. (2f).┆
0x3d600…3d700 (61, 0, 6) Sector 3d07ff00138141 ┆= A This again is passed to the calling application via its delivery queue (2g) by SAR. b) Off-Line Retrieval Completion Codes If the off-line volume cannot intermediately be mounted, the application is acknowledged by a completion code in its de┆
0x3d700…3d800 (61, 0, 7) Sector 3c08ff00138141 ┆< Alivery queue (2h). This completion code can as well tell that referenced CIF not found or off-line retrieval intermediately impossible. The need for a reduction in time interval, because interval covers 2 volumes, is also acknowledge back via com┆
0x3d800…3d900 (61, 0, 8) Sector 3d09ff00138141 ┆= Arator (2). MMS sends an intermediate storage warning to SAR. Supervisor (TEP) sends a perform dump command until time specified to SAR. The on-line catalogue is consulted to determine which CIFs to dump (3a) (3b) according to the TOC field in each C┆
0x3d900…3da00 (61, 0, 9) Sector 3d0aff00138141 ┆= AIF entry. Dumping the CIFs are carried out sectionwise through the following sequence of actions: - Dump CIF command for MMS (3c) - Dump CIF completion code for SAR (3d) - Update off-line catalogue (3e) - Update on-line catalogue (3f) - Clear┆
0x3da00…3db00 (61, 0, 10) Sector 3d0b8400138141 ┆= A item command for MMS (3g) Total completion of the dump process is acknowledged to TEP (supervisor) report printer (3h). .1.1.5 Retrieval Retrieval of stored CIF using a combination of the previous mentioned key can be achieved from both on-l┆
0x3db00…3dc00 (61, 0, 11) Sector 3d0c6300138141 ┆= c A 1 figure 2.2.1.2-1 ss Office Delay: Time from the creation of a message to the departure from the site or time of reception on the site until presentation on terminal positio┆
0x3dc00…3dd00 (61, 0, 12) Sector 3d0dff00138141 ┆= A 1 2.2.1.3 Retrieval Refer figure 2.2.1.3-1. Retrieval of the previously stored information takes place from either on-line volume or off-line by placing a retrieve command in the ┆
0x3dd00…3de00 (61, 0, 13) Sector 3d0eff00138141 ┆= Aretrieve request queue (RRQ) of SAR, which then returns one out of three things to the requesting application. a) A view ref. referencing the retrieved CIF b) Completion code telling the reason for improper completion c) Catalogue information ┆
0x3de00…3df00 (61, 0, 14) Sector 3d0fff00138141 ┆= Afor display 2.2.1.3.1 On-Line Retrieval a) Returning a View Ref. After reception and detection of an on-line retrieval command (1a), the on-line catalogue is consulted to determine the CIF-id and view-id corresponding to the retrieval key pa┆
0x3df00…3e000 (61, 0, 15) Sector 3d00ff00138141 ┆= Arameters (1b). A RETRIEVE CIF command with CIF-id and view-id as input parameter is delivered to MMS (1c). MMS returns a view ref. referencing the generated temporary CIF (1d) which is handled further on by SAR to requestor after security and acce┆
0x3e000…3e100 (62, 0, 0) Sector 3e01ad00138141 ┆> - Age are stored according to the events listed below: Incoming Messages. Storage after succesful passing analysis including possible correction by message service. .................. 144 A.1 SPECIFIC STORAGE AND RETRIEVAL KEYS ....... 144 ┆
0x3e100…3e200 (62, 0, 1) Sector 3e02ff00138141 ┆> A 1 Released Messages Storage when the positive release decision has been given by the releasing officer. First Draft Storage after completion of new message preparation format A┆
0x3e200…3e300 (62, 0, 2) Sector 3e03ff00138141 ┆> A. Comments Storage after completion of new comment preparation format G1. Release Notifications Storage after completion of the release decision Log CIFs Storage after completion of a log CIF, i.e. every 10 minutes The packages respons┆
0x3e300…3e400 (62, 0, 3) Sector 3e04ff00138141 ┆> Aible for the above mentioned actions initiate a storage process as described next. During step 1a-d, the application modules request SAR to initiate a storage process by queuing a request in the incoming storage queue (ISQ). The on-line catalogue┆
0x3e400…3e500 (62, 0, 4) Sector 3e05ff00138141 ┆> A is updated for each storage process with a new entry (2) and upon this completion, SAR requests MMS to store the respective item by issuing a STORE ITEM command (3) with input parameter View Reference. Application is acknowledged of storage complet┆
0x3e500…3e600 (62, 0, 5) Sector 3e065600138141 ┆> V Aion (4). The on-line storage process is depicted overleaf in figure 2.2.1.1-1. retrieve the CIF. Actual time span for on-line storage is in the order of days. 3) To define in detail the interfaces with other packages and to describe their facil┆
0x3e600…3e700 (62, 0, 6) Sector 3e078800138141 ┆> A 1 Fig. 2.2.1.1-1 ied out by dumping CIF to an off-line volume, when they have been on-line resident for at least 24 hours. Off-line sto┆
0x3e700…3e800 (62, 0, 7) Sector 3d08ff00138141 ┆= A 1 2.2.1.2 Off-Line Storage (Dump) The communication during an off-line dump is carried out as shown on figure 2.2.1.2-1. Incarnation is achieved by either MMS (1a) or Supervisor ope┆
0x3e800…3e900 (62, 0, 8) Sector 3e09ff00138141 ┆> A any encrypted message. Further data messages are stored only for reruns. The CIFs for on-line storage are as follows: First draft, Released messages, Incoming analysed + possible corrected messages, Release notifications and Comment submitted.┆
0x3e900…3ea00 (62, 0, 9) Sector 3e0aff00138141 ┆> A 2.1.1.4 Storage and Retrieval Keys The CIFs for storage are catalogued under a combination of the keys: TOC (time of occurrence), TOC window, DTG (release), ORIG. HQ., ITEM REF ID, CHANNEL ID, CHANNEL SERIAL NUMBER, STATION ID, STATION SERIAL ┆
0x3ea00…3eb00 (62, 0, 10) Sector 3e0bff00138141 ┆> ANUMBER, FILE TIME, SICs. Retrieval of the CIFs is achieved by combining the search keys depending on the category of CIF. 2.1.1.5 Retrieval Retrieval of stored CIF using a combination of the previous mentioned key can be achieved from both on-l┆
0x3eb00…3ec00 (62, 0, 11) Sector 3e0c2800138141 ┆> ( Aine or off-line storage media. essages and transactions stored and retrieved by SAR. Cross Office Delay: Time from the creation of a message to the departure from the site or time of reception on the site until presentation on terminal positio┆
0x3ec00…3ed00 (62, 0, 12) Sector 3e0dff00138141 ┆> A 1 2.1.1.5.1 On-Line Retrieval The on-line disk contains the on-line CIFs which can be retrieved to a terminal position which has already gained knowledge of the CIF by either having┆
0x3ed00…3ee00 (62, 0, 13) Sector 3e0eff00138141 ┆> A prepared it or previously received. Exception is that the supervisor can retrieve all stored information. 2.1.1.5.2 Off-Line Retrieval The off-line CIFs reside on a number of off-line volumes which are mounted when an off-line retrieval proces┆
0x3ee00…3ef00 (62, 0, 14) Sector 3e0fff00138141 ┆> As is in progress. 2.2 PACKAGE FUNCTIONS The next two sub-sections 2.2.1 and 2.2.2 contain a functional description under normal operations and special circumstances respectively. 2.2.1 Main Functions Main functions included in SAR are: -┆
0x3ef00…3f000 (62, 0, 15) Sector 3e00ff00138141 ┆> A on-line storage - on-line retrieval - off-line retrieval - off-line storage (dump) 2.2.1.1 On-Line Storage Storage on-line means storage on intermediate storage of CIFs which have completed processing. The five categories of items for stora┆
0x3f000…3f100 (63, 0, 0) Sector 3f010f00138141 ┆? Aorage APPENDIX A ....................................... 144 A.1 SPECIFIC STORAGE AND RETRIEVAL KEYS ....... 144 ┆
0x3f100…3f200 (63, 0, 1) Sector 3f02ff00138141 ┆? A 1 2 SUMMARY OF REQUIREMENTS This chapter includes the requirements pertinent to SAR at package level. 2.1 PACKAGE DESCRIPTION 2.1.1 General Concept SAR provides function┆
0x3f200…3f300 (63, 0, 2) Sector 3f03ff00138141 ┆? Aal capabilities for on-line storage of all incoming and outgoing messages in an intermediate storage (up to a few days depending on traffic and assigned disk space and allowed fill rate). After that, the CIFs are kept for a period of at least 30 day┆
0x3f300…3f400 (63, 0, 3) Sector 3f04ff00138141 ┆? As on offline disk volumes (long term storage). SAR supports retrieval of CIFS from the intermediate storage within a specified time limit. Retrieving off-line is possible within a time limit to be specified measured from when off-line volume is ┆
0x3f400…3f500 (63, 0, 4) Sector 3f05ff00138141 ┆? Amounted. The functions carried out by SAR are then: - Retrieve on-line - Store on-line - Store off-line - Retrieve off-line 2.1.1.1 On-Line Storage The on-line CIFs handled by SAR are on-line resident for at least 24 hours. On-line storag┆
0x3f500…3f600 (63, 0, 5) Sector 3f06aa00138141 ┆? * Ae is characterized by the fact that no mounting of physical media is required to retrieve the CIF. Actual time span for on-line storage is in the order of days. 3) To define in detail the interfaces with other packages and to describe their facil┆
0x3f600…3f700 (63, 0, 6) Sector 3f07ff00138141 ┆? A 1 2.1.1.2 Off-Line Storage An off-line storage process is carried out by dumping CIF to an off-line volume, when they have been on-line resident for at least 24 hours. Off-line sto┆
0x3f700…3f800 (63, 0, 7) Sector 3e08ff00138141 ┆> Arage may require, that a media must be loaded prior to retrieval. 2.1.1.3 Subject to Storage Data for storage and retrieval are operational and service messages except for the categories: security classification CTS, special handling ATOMAL and┆
0x3f800…3f900 (63, 0, 8) Sector 3f09af00138141 ┆? / Ahe following documents represent a baseline for this specification: - CPS/210/SYS/0001 CAMPS System Requirements - CPS/SDS/001 CAMPS System Design Specification e Entry .... 122 4.2.5.1.6 Request Volume Table Contents . 123 4.2.┆
0x3f900…3fa00 (63, 0, 9) Sector 3f0aff00138141 ┆? A 1 1.2.2 Project References Reference documents are as follows: - CPS/230/ICD/0001 User Procedures and Associated Formats - CPS/230/ICD/002 Supervisor Commands and Procedures┆
0x3fa00…3fb00 (63, 0, 10) Sector 3f0bff00138141 ┆? A 1.3 TERMS AND ABBREVIATIONS 1.3.1 Terms 1 Dump: Transferring messages and transactions from on-line disk to off-line disk. Off-Line Disk: Disk volume used for storage of me┆
0x3fb00…3fc00 (63, 0, 11) Sector 3f0cff00138141 ┆? Assages and transactions. Item: Messages and transactions stored and retrieved by SAR. Cross Office Delay: Time from the creation of a message to the departure from the site or time of reception on the site until presentation on terminal positio┆
0x3fc00…3fd00 (63, 0, 12) Sector 3f0d9e00138141 ┆? An. Interleaving: Interruption at ordinary SAR functions i.e. on-line storage, on-line retrieval, off-line retrieval, dump and supervisor commands. 4.2.5.3.2.7 Start-Up Command Control Logic ..................... 129 4.2.5.┆
0x3fd00…3fe00 (63, 0, 13) Sector 3f0eff00138141 ┆? A 1 1.3.2 Abbreviations ISQ Incoming Storage Queue RRQ Retrieval request Queue FIFO First In First Out SFM Storage and File Management Package QEL Queue Element OROF Off-Line Ret┆
0x3fe00…3ff00 (63, 0, 14) Sector 3f0fff00138141 ┆? Arieval Off ORON Off-Line Retrieval On ORSU Off-Line Retrieval Suspended VOCL Volume Control List VOIL Volume Identification List VONM Volume Naming VODL Volume Deletion SCQ Supervisor Command Queue MAQ Mount Acknowledge Queue DCQ Dump Comma┆
0x3ff00…40000 (63, 0, 15) Sector 3f00ff00138141 ┆? And Queue CIF CAMPS Information Field ISTOQ Incoming Storage Time-Out Queue APP Application TD Terminal Designator RC5 Return Code 5 PD Preliminary Design SP.PD Sub-Package Preliminary Design MMS Message Management System IS Intermediate St┆
0x40000…40100 (64, 0, 0) Sector 4001ff00138141 ┆@ A 1 APPENDIX A ....................................... 144 A.1 SPECIFIC STORAGE AND RETRIEVAL KEYS ....... 144 ┆
0x40100…40200 (64, 0, 1) Sector 4002ff00138141 ┆@ A A.1.1 Incoming Message After Analysis ....... 144 A.1.2 Incoming Message After Selection of Nominal Distribution List .......... 144 A.1.3 First Draft ........................... 145 A.1.4 Comments ..........................┆
0x40200…40300 (64, 0, 2) Sector 4003ff00138141 ┆@ A.... 145 A.1.5 Release Notification .................. 145 A.1.6 Released Messages ..................... 145 A.1.7 Released Messages after Assignment of Transaction Keys ...................... 146 A.1.8 Log Items ........┆
0x40300…40400 (64, 0, 3) Sector 40042100138141 ┆@ ! A..................... 146 uests ......... 107 4.2.4.1.2 Check Mounted Volume .......... 107 4.2.4.1.3 Volume Mount Procedure ........ 107 4.2.4.1.4 Dump Procedure ................ 108 4.2.4.2 Software Structure .........┆
0x40400…40500 (64, 0, 4) Sector 4005ff00138141 ┆@ A 1 1 GENERAL 1.1 PURPOSE AND SCOPE The Package Specification for Storage and Retrieval Package (SAR) CPS/SDS/007 is written to fulfil the following objectives: 1) To provide d┆
0x40500…40600 (64, 0, 5) Sector 4006ff00138141 ┆@ Aetailed definition of the package function and software architecture. 2) To provide user operational and development personnel details of the ongoing analysis. 3) To define in detail the interfaces with other packages and to describe their facil┆
0x40600…40700 (64, 0, 6) Sector 4007ff00138141 ┆@ Aities. The specification contains a description of the package to a level of a few software statements as lowest detail. Higher level design specification can be found in the document system design listed in the next section, applicable document┆
0x40700…40800 (64, 0, 7) Sector 3f08ff00138141 ┆? As. All interfaces and data are described in this specification and contained in the software Interface Control Document and Database Design Document respectively. 1.2 APPLICABLE DOCUMENTS AND PROJECT REFERENCES 1.2.1 Applicable Documents T┆
0x40800…40900 (64, 0, 8) Sector 4009ff00138141 ┆@ A 1 4.2.5.1.5 Request Volume Table Entry .... 122 4.2.5.1.6 Request Volume Table Contents . 123 4.2.┆
0x40900…40a00 (64, 0, 9) Sector 400aff00138141 ┆@ A5.1.7 Delete Volume Table Entry ..... 123 4.2.5.1.8 Start-Up Command .............. 123 4.2.5.1.9 Close Down Command ............ 123 4.2.5.2 Software Structure ................ 124 4.2.5.3 Data Flow and Control Logic ...┆
0x40a00…40b00 (64, 0, 10) Sector 400bff00138141 ┆@ A.... 126 4.2.5.3.1 Main Module Control Logic ..... 126 4.2.5.3.2 Command Control Logic ......... 128 4.2.5.3.2.1 Off-Line Retrieval Off Control Logic ............. 128 4.2.5.3.2.2 Off-Line Retrieval On ┆
0x40b00…40c00 (64, 0, 11) Sector 400cff00138141 ┆@ A Control Logic ............. 128 4.2.5.3.2.3 Off-Line Retrieval Susp. Control Logic ............. 128 4.2.5.3.2.4 Volume Table Entry Control Logic ..................... 128 4.2.5.3.2.5 Volume┆
0x40c00…40d00 (64, 0, 12) Sector 400dff00138141 ┆@ A Table Contents Control Logic ............. 128 4.2.5.3.2.6 Delete Volume Entry Control Logic ............. 128 4.2.5.3.2.7 Start-Up Command Control Logic ..................... 129 4.2.5.┆
0x40d00…40e00 (64, 0, 13) Sector 400eff00138141 ┆@ A3.2.8 Close-Down Command Control Logic ..................... 129 4.2.5.4 Sub-Package Data .................. 138 4.2.5.5 Sub-Package Interfaces ............ 138 4.2.5.5.1 Lock-Table Interface .......... 139 4.┆
0x40e00…40f00 (64, 0, 14) Sector 400fff00138141 ┆@ A2.5.5.2 Off-Line-Retrieval-Susp. Control Logic ................. 139 4.2.5.5.3 Off-Line-Retrieval-On/Off Control Logic ................. 139 4.3 MEMORY LAYOUT ............................. 139 4.3.1 Program Ar┆
0x40f00…41000 (64, 0, 15) Sector 4000d000138141 ┆@ P Aea .......................... 139 4.3.2 Main Memory Data Area ................. 140 4.3.3 On-Line Disk Data Area ................ 140 4.3.4 Off-Line Disk Data Area ............... 140 3 CIF Not Found ............. 99 4.2.3┆
0x41000…41100 (65, 0, 0) Sector 4101ff00138141 ┆A A.1.8.4 CIF Found ................. 99 4.2.3.2 Software Structure ................ 99 4.2.3.3 Data Flow and Control Logic ....... 101 4.2.3.3.1 Control Elements .............. 101 4.2.3.3.2 Control Logic ................┆
0x41100…41200 (65, 0, 1) Sector 4102ff00138141 ┆A A. 101 4.2.3.4 Sub-Package Data .................. 104 4.2.3.5 Sub-Package Interfaces ............ 104 4.2.3.5.1 Off-Line-Count ................ 104 4.2.3.5.2 Off-Line-Disk-Lock ............ 104 4.2.3.5.3 Lock-Table ┆
0x41200…41300 (65, 0, 2) Sector 4103ff00138141 ┆A A.................... 104 4.2.3.5.4 Off-Line-Retrieval-Susp. ...... 105 4.2.3.6 Sub-Package Initialization ........ 105 4.2.4 Dump Specifications ................... 105 4.2.4.1 Functional Specification .......... 105 ┆
0x41300…41400 (65, 0, 3) Sector 4104ff00138141 ┆A A4.2.4.1.1 Receive Dump Requests ......... 107 4.2.4.1.2 Check Mounted Volume .......... 107 4.2.4.1.3 Volume Mount Procedure ........ 107 4.2.4.1.4 Dump Procedure ................ 108 4.2.4.2 Software Structure .........┆
0x41400…41500 (65, 0, 4) Sector 4105ff00138141 ┆A A....... 108 4.2.4.3 Data Flow and Control Logic ....... 110 4.2.4.3.1 MMS Main Control .............. 110 4.2.4.3.2 TEP Main Control .............. 110 4.2.4.3.3 Dump Control................... 110 4.2.4.3.3.1 Perf┆
0x41500…41600 (65, 0, 5) Sector 4106ff00138141 ┆A Aorm Dump on Usual Volume Control ............ 113 4.2.4.3.3.2 Perform Dump on New Volume Control ............ 117 4.2.4.4 Sub-Package Data .................. 118 4.2.4.5 Sub-Package Interfaces ...┆
0x41600…41700 (65, 0, 6) Sector 4107ff00138141 ┆A A......... 118 4.2.4.5.1 Off-Line-Disk-Lock ............ 118 4.2.4.5.2 Lock-Table .................... 118 4.2.4.5.3 Lock-Cat ...................... 118 4.2.5 Supervisor Command Specifications ..... 118 4.2.5.1 Functi┆
0x41700…41800 (65, 0, 7) Sector 4008fd00138141 ┆@ } Aonal Specification .......... 118 4.2.5.1.1 Receive and Detect Command .... 122 4.2.5.1.2 Off-Line Retrieval Off ........ 122 4.2.5.1.3 Off-Line Retrieval On ......... 122 4.2.5.1.4 Off-Line Retrieval Suspended .. 122 Ar┆
0x41800…41900 (65, 0, 8) Sector 4109ff00138141 ┆A Aea ..................... 79 4.2.1.5 Sub-Package Interfaces ............ 81 4.2.1.6 Sub-Package Initialization ........ 81 4.2.2 On-Line Retrieval Specifications ...... 81 4.2.2.1 Functional Specificaion ........... 81 ┆
0x41900…41a00 (65, 0, 9) Sector 410aff00138141 ┆A A 4.2.2.1.1 Receive Retrieval Requests .... 83 4.2.2.1.2 On-Line/Off-Line Retrieval Separation .................... 83 4.2.2.1.3 On-Line/Catalogue Consult ..... 84 4.2.2.1.4 Access Check .................. 86┆
0x41a00…41b00 (65, 0, 10) Sector 410bff00138141 ┆A A 4.2.2.1.5 Retrieval of CIF .............. 86 4.2.2.1.6 Delivery of Retrieval Result .. 87 4.2.2.2 On-Line Retrieval Software Structure ......................... 87 4.2.2.3 Data Flow and Control Logic ....... ┆
0x41b00…41c00 (65, 0, 11) Sector 410cff00138141 ┆A A89 4.2.2.4 Sub-Package Data .................. 92 4.2.2.5 Sub-Package Interfaces ............ 93 4.2.2.6 On-Line Retrieval Initialization .. 93 4.2.3 Off-Line Retrieval Specifications ..... 94 4.2.3.1 Functional Spec┆
0x41c00…41d00 (65, 0, 12) Sector 410dff00138141 ┆A Aification .......... 94 4.2.3.1.1 Activate Off-Line Retrieval ... 96 4.2.3.1.2 Off-Line Volume Determination . 96 4.2.3.1.3 Test of Mounted Volume ........ 96 4.2.3.1.4 Volume Mount .................. 97 4.2.3.┆
0x41d00…41e00 (65, 0, 13) Sector 410eff00138141 ┆A A1.5 Off-Line Catalogue Consult .... 97 4.2.3.1.6 Access Check .................. 97 4.2.3.1.7 Retrieve CIF .................. 97 4.2.3.1.8 Delivery of Retrieval Result .. 98 4.2.3.1.8.1 Volume Mount Refusal ...... ┆
0x41e00…41f00 (65, 0, 14) Sector 410f0a00138141 ┆A A 98 .1 Package Control Data Elements ..... 42 4.1.3.2 Data Flow Logic ................... 46 4.1.4 Common Data Elements (Internal) ....... 48 4.1.4.1 On-Line Catalogue ................. 48 4.1.4.2 Off-Line Catalogue ....┆
0x41f00…42000 (65, 0, 15) Sector 4100ff00138141 ┆A A 1 4.2.3.1.8.2 Access Check Failure ...... 98 4.2.3.1.8.3 CIF Not Found ............. 99 4.2.3┆
0x42000…42100 (66, 0, 0) Sector 4201ff00138141 ┆B AReturn Data After a Retrieval ..... 56 4.1.5.3.1 Return Code ................... 57 4.1.5.3.2 Catalogue Information ......... 57 4.1.5.4 Supervisor Command Data ........... 57 4.1.5.4.1 Volume File Entry .............┆
0x42100…42200 (66, 0, 1) Sector 4202ff00138141 ┆B A 57 4.1.5.4.2 Volume File Entry ............. 57 4.1.5.5 Printer Data Elements ............. 57 4.1.6 Interfaces ............................ 57 4.1.6.1 External Interfaces ............... 57 4.1.6.2 Package Inte┆
0x42200…42300 (66, 0, 2) Sector 4203ff00138141 ┆B Arfaces ................ 58 4.1.6.2.1 SAR/TEP Interface ............. 58 4.1.6.2.2 SAR/MDP Interface ............. 59 4.1.6.2.3 SAR/THP Interface ............. 59 4.1.6.2.4 SAR/LOG Interface ............. 59 4.1┆
0x42300…42400 (66, 0, 3) Sector 4204ff00138141 ┆B A.6.3 Sub-Package Interfaces ............ 60 4.1.6.3.1 Storage Sub-Package Interfaces 60 4.1.6.3.2 On-Line Retrieval Sub-Package Interfaces .................... 60 4.1.6.3.3 Off-Line Retrieval Sub-Package ┆
0x42400…42500 (66, 0, 4) Sector 4205c200138141 ┆B B A Interfaces .................... 60 4.1.6.3.4 Dump Sub-Package Interfaces ... 61 4.1.6.3.5 Supervisor Command Sub-Package Interfaces .................... 61 .2.2.6 Security .......................... 26 2.3 CHAR┆
0x42500…42600 (66, 0, 5) Sector 4206ff00138141 ┆B A 1 4.2.1 On-Line Storage Specification.......... 67 4.2.1.1 Functional Specification .......... 67 4┆
0x42600…42700 (66, 0, 6) Sector 4207ff00138141 ┆B A.2.1.1.1 Reception of Storage Requests . 69 4.2.1.1.2 Retrieval Key Pick-Up ......... 69 4.2.1.1.3 Emptying Collect Area ......... 69 4.2.1.1.4 Update On-Line Catalogue ...... 70 4.2.1.1.5 Complete Storage ..........┆
0x42700…42800 (66, 0, 7) Sector 4108ff00138141 ┆A A.... 70 4.2.1.2 Sub-Package Software Structure .... 70 4.2.1.3 Data Flow and Control Logic ....... 73 4.2.1.4 Sub-Package Data .................. 79 4.2.1.4.1 Control Area .................. 79 4.2.1.4.2 Data Ar┆
0x42800…42900 (66, 0, 8) Sector 4209ff00138141 ┆B A......... 31 3.2.2 Development Software .................. 31 3.3 INTERFACES ................................ 32 3.3.1 External Interfaces ................... 32 3.3.2 Package Interfaces .................... 32 3.3.2.1 ┆
0x42900…42a00 (66, 0, 9) Sector 420aff00138141 ┆B A Storage Interface ................. 32 3.3.2.2 On-Line Retrieval Interface ....... 32 3.3.2.3 Off-Line Retrieval Interface ...... 33 3.3.2.4 Dump Retrieval Interface .......... 33 3.3.2.5 Supervisor Command Interface ...┆
0x42a00…42b00 (66, 0, 10) Sector 420bff00138141 ┆B A... 33 3.4 FUNCTIONS MAINTAINED BY OTHER PACKAGES .... 35 4 PACKAGE DESIGN ................................ 36 4.1 PACKAGE OVERVIEW .......................... 36 4.1.1 Functional Specifications ............. 36 4.1.1.1 ┆
0x42b00…42c00 (66, 0, 11) Sector 420cff00138141 ┆B AStorage of Messages ............... 38 4.1.1.2 On-Line Retrieval ................. 38 4.1.1.3 Off-Line Retrieval ................ 38 4.1.1.4 Dump .............................. 39 4.1.1.5 Perform Supervisor Commands .....┆
0x42c00…42d00 (66, 0, 12) Sector 420d0f00138141 ┆B A.. 39 ferences .................... 11 1.3 TERMS AND ABBREVIATIONS ................... 11 1.3.1 Terms ................................. 11 1.3.2 Abbreviations ......................... 12 2 SUMMARY OF REQUIREMENTS .........┆
0x42d00…42e00 (66, 0, 13) Sector 420eff00138141 ┆B A 1 4.1.2 Software Structure .................... 40 4.1.3 Data Flow and Control Logic ........... 42 4┆
0x42e00…42f00 (66, 0, 14) Sector 420fff00138141 ┆B A.1.3.1 Package Control Data Elements ..... 42 4.1.3.2 Data Flow Logic ................... 46 4.1.4 Common Data Elements (Internal) ....... 48 4.1.4.1 On-Line Catalogue ................. 48 4.1.4.2 Off-Line Catalogue ....┆
0x42f00…43000 (66, 0, 15) Sector 4200ff00138141 ┆B A............ 51 4.1.4.3 Volume Table ...................... 53 4.1.5 External Data Elements ................ 56 4.1.5.1 Storage Keys During Storage ....... 56 4.1.5.2 Retrieval keys During Retrieval ... 56 4.1.5.3 ┆
0x43000…43100 (67, 0, 0) Sector 4301ff00138141 ┆C Aval ......................... 20 2.2.1.3.1 Online Retrieval .............. 20 2.2.1.3.2 Offline Retrieval ............. 21 2.2.2 Functional Responsibilities ........... 23 2.2.2.1 Initialization, Close Down and ┆
0x43100…43200 (67, 0, 1) Sector 4302ff00138141 ┆C A Restart ........................... 23 2.2.2.1.1 Initialization ................ 23 2.2.2.1.2 Close Down .................... 24 2.2.2.1.3 Restart ....................... 24 2.2.2.2 Checkpointing and Recovery ......┆
0x43200…43300 (67, 0, 2) Sector 43037800138141 ┆C x A.. 24 2.2.2.2.1 Checkpointing ................. 24 2.2.2.2.2 Recovery ...................... 24 B}5I:g=~ J 5IC$3I > S C_* ┆
0x43300…43400 (67, 0, 3) Sector 4304ff00138141 ┆C A 1 2.2.2.3 Error Detection and Error Handling .................... 25 2.2.2.3.1 Error Detection┆
0x43400…43500 (67, 0, 4) Sector 4305ff00138141 ┆C A ............... 25 2.2.2.3.2 Error Handling ................ 25 2.2.2.4 Integrity of Operation ............ 26 2.2.2.5 Data Collection ................... 26 2.2.2.6 Security .......................... 26 2.3 CHAR┆
0x43500…43600 (67, 0, 5) Sector 4306ff00138141 ┆C AACTERISTICS .......................... 26 2.3.1 Timing ................................ 26 2.3.1.1 Response Time to Queries .......... 27 2.3.1.2 Response Time to Dump ............. 28 2.3.1.3 Priorities Related to Input ┆
0x43600…43700 (67, 0, 6) Sector 4307ff00138141 ┆C A....... 28 2.3.1.4 Traffic Load ...................... 29 2.3.1.5 Interleaving STP .................. 30 2.3.2 Throughput ............................ 30 2.3.3 Flexibility ........................... 30 2.3.4 Accurac┆
0x43700…43800 (67, 0, 7) Sector 4208ff00138141 ┆B Ay of Input Data ................ 30 3 ENVIRONMENT ................................... 31 3.1 EQUIPMENT ENVIRONMENT ..................... 31 3.2 SOFTWARE ENVIRONEMT ....................... 31 3.2.1 System Software ..............┆
0x43800…43900 (67, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(67,0, 9), len=0xff, h3=41138141}, f00=»1381A «, f01=»CPS/SDS/001 «, f02=»vhn «, f03=»KR «, f04=»Kapitel 5.16 «, f05=12-10-81 11:15, f06=» «, f07=»00 «, f08=» 13 «, f09= - - : , f10=» «, f11=» «, f12=» «, f13= - - : , f14=12-10-81 11:17, f15=»0091A «, f16=» 33 «, f17=» «, f18=»00 «, f19=» 548 «, f20=» 13 «, f21=» «, f22=» «, f99=020010000110066610a10a80aaca1505000000000000013703ac00df}
0x43900…43a00 (67, 0, 9) Sector 430a2100138141 ┆C ! A C C B B A @ @ @ ? ? ? ? > > > > = = = < < < < ; ; ; : : : : 9 9 9 DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG Oprettet / / : : S┆
0x43a00…43b00 (67, 0, 10) Sector 430bff00138141 ┆C A 1 TABLE OF CONTENTS 1 1 GENERAL .............┆
0x43b00…43c00 (67, 0, 11) Sector 430cff00138141 ┆C A.......................... 10 1.1 PURPOSE ................................... 10 1.2 APPLICABLE DOCUMENTS AND PROJECT REFERENCES ................................ 10 1.2.1 Applicable Documents .................. 10 1.2.2 P┆
0x43c00…43d00 (67, 0, 12) Sector 430dff00138141 ┆C Aroject References .................... 11 1.3 TERMS AND ABBREVIATIONS ................... 11 1.3.1 Terms ................................. 11 1.3.2 Abbreviations ......................... 12 2 SUMMARY OF REQUIREMENTS .........┆
0x43d00…43e00 (67, 0, 13) Sector 430eff00138141 ┆C A.............. 13 2.1 PACKAGE DESCRIPTION ....................... 13 2.1.1 General Concept ....................... 13 2.1.1.1 Online Storage .................... 13 2.1.1.2 Offline Storage ................... 14 2.1.1┆
0x43e00…43f00 (67, 0, 14) Sector 430fff00138141 ┆C A.3 Subject to Storage ................ 14 2.1.1.4 Storage and Retrieval Keys ........ 14 2.1.1.5 Retrieval ......................... 14 2.1.1.5.1 Online Retrieval .............. 15 2.1.1.5.2 Offline Retrieval .........┆
0x43f00…44000 (67, 0, 15) Sector 4300ff00138141 ┆C A.... 15 2.2 PACKAGE FUNCTIONS ......................... 15 2.2.1 Main Functions ........................ 15 2.2.1.1 Online Storage .................... 15 2.2.1.2 Offline Storage (Dump) ............ 18 2.2.1.3 Retrie┆
0x44000…44100 (68, 0, 0) Sector 00000000000000 ┆ ┆
[…0x8f…]
