OctetView
0x00000…00100 (0, 0, 0) Sector 01494130313439 ┆ IA0149A ┆
0x00100…00200 (0, 0, 1) Sector 00000000000000 ┆ ┆
0x00200…00300 (0, 0, 2) Sector ff00f880ffffff ┆ x x ~ ┆
0x00300…00306 (0, 0, 3) WangDocument {d00=0x18, d01=0x83, d02=0x41, ptr=(32,0, 0), d05=0x00}
0x00306…0030c WangDocument {d00=0x18, d01=0x99, d02=0x41, ptr=(47,0, 8), d05=0x00}
0x0030c…00312 WangDocument {d00=0x19, d01=0x18, d02=0x41, ptr=(38,0, 8), d05=0x00}
0x00312…00318 WangDocument {d00=0x19, d01=0x19, d02=0x41, ptr=(62,0, 8), d05=0x00}
0x00318…0031e WangDocument {d00=0x19, d01=0x30, d02=0x41, ptr=(58,0, 0), d05=0x00}
0x0031e…00324 WangDocument {d00=0x19, d01=0x51, d02=0x41, ptr=(65,0, 8), d05=0x00}
0x00324…00340 19 51 41 41 08 00 19 51 41 48 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ QAA QAH ┆
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 01494130313439 ┆ IA0149A ┆
0x00600…00700 (0, 0, 6) Sector 421c402600415b ┆B @& A[' X% % PO P ; QAN C f x f V Wj O 7 :W W 1951A f o < {C < { ; 9 ;s! A sH s 9 8 : B t x 1951A0603A V W W 3CcC ┆
0x00700…00800 (0, 0, 7) Sector 00000000000000 ┆ ┆
[…0x8…]
0x01000…01100 (1, 0, 0) WangDocumentBody
[…0x4…]
0x01500…01600 (1, 0, 5) Sector 00000000000000 ┆ ┆
[…0x2…]
0x01800…01900 (1, 0, 8) WangDocumentBody
0x01900…01a00 (1, 0, 9) Sector 0000ba00189941 ┆ : A 1 APPENDIX B Sequence Tables: Mask 1 is at the moment left blank. Column not filled in is null. erface Call Specification a) OUTGROUP (READ ITEM PT INTEGER ┆
0x01a00…01b00 (1, 0, 10) Sector 010bff00189941 ┆ AMS,CC):ERROR OK ERROR? CASE ANALYSE ERROR(CC,1,BLOCKED QUEUE):(L1) L1? END CASE OK? END CASE DISM(SETR QEL)(4.1.5.3) SETR OP.CMD=RETRIEVAL ERROR SIGNAL OPSEM(MSOS S2,SETR OP):OK DISM(SETR QEL)(4.1.5.3) END SE┆
0x01b00…01c00 (1, 0, 11) Sector 010c3f00189941 ┆ ? ATR QEL3 INSPECT Figure 4.2.4.4.1.5-15 OFFLINE SYSCAT HANDLING MOVE DATA TO MSOS SEND PARAMS CASE SEND(MSOS SEND PARAMS,SETR QEL,RESPQ) (MSOS SEND PARAMS,CC):ERROR OK ERROR? CASE ANALYSE ERROR(CC,1,BLOCKED Q┆
0x01c00…01d00 (1, 0, 12) Sector 010dff00189941 ┆ A 1 4.2.4.5 Common Subpackage Data N/A. 4.2.4.6 Common Subpackage Procedures N/A. 4.2.4.7 Subpackage Interfaces 4.2.4.7.1 SETR UMAM Interfaces Refer CPS/ICD/009 4.2.4.7┆
0x01d00…01e00 (1, 0, 13) Sector 010e5f00189941 ┆ _ A.2 SETR UFCO Interfaces The following notifications are sent from SETR to SEFCO via opeNG SETR QEL ATTR.HEADER.INFO.TRANSACTION SER.NO NE TRANSACTION ID.SERIAL NO? OFFLINE SYSCAT HANDLING (4.2.4.4.1.5-10) USER ACTIVE F┆
0x01e00…01f00 (1, 0, 14) Sector 00008c00189941 ┆ Aration semaphore MSOS S2: ONLINE NOTIFICATION OFFLINE NOTIFICATION RERUN NOTIFICATION READDRESS NOTIFICATION RETRIEVAL ERROR. SEFCO SETR ATTR=SETR QEL ATTR SETR QEL ATTR.HEADER.INFO.RETR FLAG.BIT 2 EQ BIT 2? SETR OP.CMD=RERUN NOTI┆
0x01f00…02000 (1, 0, 15) Sector 00000000000000 ┆ ┆
0x02000…02100 (2, 0, 0) WangDocumentBody
[…0x1bf…]
0x1e000…1e100 (30, 0, 0) Sector 1e01ff00195141 ┆ QADISP PROC ................ 4.2.3.7 Subpackage Interface ............... 4.2.3.7.1 SEFCO SEDIA Interfaces ......... 4.2.3.7.2 SEDIA SEFCO Interfaces ......... 4.2.4 Retrieve Subpackage ................... 4.2.4.1 Function┆
0x1e100…1e200 (30, 0, 1) Sector 1e02ff00195141 ┆ QAal Specification ........... 4.2.4.2 Software Structure ................. 4.2.4.3 Data Flow and Control Logic......... 4.2.4.3.1 Data Flow ...................... 4.2.4.3.2 Control Logic .................. 4.2.4.4 Module ┆
0x1e200…1e300 (30, 0, 2) Sector 1e03ff00195141 ┆ QASpecification .............. 4.2.4.4.1 SETR MAIN Module ............... 4.2.4.5 Common Subpackage Data ............. 4.2.4.6 Common Subpackage Procedures ....... 4.2.4.7 Subpackage Interfaces .............. 4.2.4.7.1 SETR┆
0x1e300…1e400 (30, 0, 3) Sector 1e045600195141 ┆ V QA DIFCO Interfaces .......... 4.2.4.7.2 SETR SEFCO Interfaces .......... .2.6.25 COPY CIF FIELD .............. 4.2.2.6.26 TEP CLOSE VIEW .............. 4.2.2.7 Subpackage Interfaces ........... 4.2.2.7.l SEFCO SED┆
0x1e400…1e500 (30, 0, 4) Sector 00007300195141 ┆ s QA APPENDIX A ....................................... APPENDIX B ....................................... 4.2.1.6.6 Set Receive CCMD QEL ........ 4.2.1.6.7 Send Notify ................. 4.2.1.6.8 Remove ...................... ┆
0x1e500…1e600 (30, 0, 5) Sector 1e06ff00191841 ┆ A PT INTEGER ITEM LENGTH INTEGER WHITE ITEM PT INTEGER) (ITEM LENGTH INTEGER):ERROR OK b) PUNCH REQ (R0,R1,R2,R6):ERROR OK Call Registers R0-R1 Pointer to Item to be converted R2 Length of Item to be converted R3-R┆
0x1e600…1e700 (30, 0, 6) Sector 1e07ff00191841 ┆ A4 Pointer to where item is to be stored R6 LINK Return Registers R0-R1 Destroyed R2 Length of converted item R3-R7 Destroyed Module Components N/A Data Description PUNCH FLAG: ref.4.3.2.5 Module Design The PUNCH area is compared┆
0x1e700…1e800 (30, 0, 7) Sector 00006700191841 ┆ g A with a Y and if it corresponds PUNCH FLAG is set to true. Otherwise PUNCH FLAG is set to false. s 4.2.3.7.1 SEFCO SEDIA Interfaces SEFCO commands: CLOSE CANCEL I O CLEAR VDU INPUT DATA OUTPUT DATA OUTPUT FORMAT L INSERT L DELE┆
0x1e800…1e900 (30, 0, 8) WangDocumentBody
[…0x4…]
0x1ed00…1ee00 (30, 0, 13) Sector 1e0efe00191841 ┆ ~ Aeception of error notification The functional breakdown is shown in figure 4.2.4.1-1. Retrieved items and off-line/on-line notifications are received from SAR in the retrieve queue. After analysis, the received item is sent to the destination. T┆
0x1ee00…1ef00 (30, 0, 14) Sector 1e0f6500191841 ┆ e A 1 Figure 4.2.4.1-1 on a) Data References MSOS OP Refer 4.1.4 b) External Data N/A c) Local Data N/A 4.2.3.6.23.4 Procedure Design Refer figure 4.2.3.6.2┆
0x1ef00…1f000 (30, 0, 15) Sector 00004a00191841 ┆ J A 1 4.2.3.6.21.3 Data Description a) Data References VAL ERR Ref. 4.2.3.5 b) External Data N/A c) Local Data N/A 4.2.3.6.21.4 Procedure Design Refer figure┆
0x1f000…1f100 (31, 0, 0) WangDocumentBody
[…0xf…]
0x20000…20100 (32, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(32,0, 1), len=0xff, h3=41188341}, f00=»1883A «, f01=»CPS/SDS/038 «, f02=»vhn «, f03=»JHH «, f04=»4.2.3 «, f05=22-03-82 16:19, f06=» 4 «, f07=»30 «, f08=» 8860 «, f09=03-06-82 10:08, f10=» «, f11=»14 «, f12=» 328 «, f13=03-06-82 13:15, f14=11-06-82 11:31, f15=»0149A «, f16=»114 «, f17=» 5 «, f18=»48 «, f19=» 1068 «, f20=» 10434 «, f21=» «, f22=» P «, f99=950010000110062710110490aaca15050000000000000137037d01df}
0x20100…20200 (32, 0, 1) WangDocumentBody
[…0x66…]
0x26800…26900 (38, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(38,0, 9), len=0xff, h3=41191841}, f00=»1918A «, f01=»CPS/SDS/038 «, f02=»vhn «, f03=»JHH «, f04=»4.2.3.6.13 «, f05=26-03-82 12:25, f06=» 2 «, f07=»32 «, f08=» 7844 «, f09=07-06-82 11:01, f10=» «, f11=»02 «, f12=» 140 «, f13=07-06-82 13:54, f14=11-06-82 11:30, f15=»0149A «, f16=» 36 «, f17=» 4 «, f18=»27 «, f19=» 264 «, f20=» 13448 «, f21=» «, f22=» 0 «, f99=630010000110062710110490aaca15050000000000000137036800df}
0x26900…26a00 (38, 0, 9) WangDocumentBody
[…0x8e…]
0x2f800…2f900 (47, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(47,0, 9), len=0xff, h3=41189941}, f00=»1899A «, f01=»CPS/SDS/038 «, f02=»bk «, f03=»JHH «, f04=»4.2.4.2 «, f05=24-03-82 08:50, f06=» 4 «, f07=»14 «, f08=» 9832 «, f09=04-06-82 14:54, f10=» «, f11=»02 «, f12=» 8 «, f13=04-06-82 15:48, f14=11-06-82 11:31, f15=»0149A «, f16=» 35 «, f17=» 9 «, f18=»01 «, f19=» 272 «, f20=» 21613 «, f21=» «, f22=» «, f99=320010000110062710110490aaca15050000000000000137036900df}
0x2f900…2fa00 (47, 0, 9) WangDocumentBody
[…0xe…]
0x30800…30900 (48, 0, 8) Sector 3009ff00193041 ┆0 0Aiate the analysis corresponding to the type (incoming, complete or PTR analysis) - set up analysis guide table - determine message type. b) Error Handling - errors during transport - unknown message type c) Format line detection and co┆
0x30900…30a00 (48, 0, 9) Sector 300aff00193041 ┆0 0Antrol of incoming messages received into SCARS/CCIS E1 format. - Garble and E1-pilot detect - Handling of Comments, VDU pages, messages for coordination, messages for release and released messages. d) Format line detection and control of mess┆
0x30a00…30b00 (48, 0, 10) Sector 300bff00193041 ┆0 0Aages in ACP127 format plus messages in SCARS/CCIS E1 format from FL5. - Garble, Pilot, readdressal and relay detect. - Relaying and handling of incoming ASM's. e) Flash acknowledge procedures for incoming messages. f) Internal format conve┆
0x30b00…30c00 (48, 0, 11) Sector 300cc600193041 ┆0 F 0Arsion, e.g. conversion to E1-format for incoming messages. g) Log, statistics and retrieval keys for incoming messages. h) Determine to where the message shall be directed after analysis. utput Control (IOC) - Access to external channels and ┆
0x30c00…30d00 (48, 0, 12) Sector 300daf00193041 ┆0 / 0A 1 FIGURE 4.1.1.1-1 FUNCTIONAL BREAK-DOWN ACP127-ANALYSIS = ====== ction of Retrieval keys - Collection of Log information - Reports ┆
0x30d00…30e00 (48, 0, 13) Sector 300e4a00193041 ┆0 J 0A 1 4 PACKAGE DESIGN 4.1 PACKAGE OVERVIEW In overview the Traffic Handling Package consists of 3 main areas with completely different functional capabilities: - ACP127 analysis┆
0x30e00…30f00 (48, 0, 14) Sector 00000600193041 ┆ 0A - ACP127 conversion - Transport The transport functions consist of 3 subjunctions: - Outgoing Transport - Transport Control - Incoming Transport As shown in figure 4.1-1 the Traffic Handling Package has been separated into the following s┆
0x30f00…31000 (48, 0, 15) Sector 00000000000000 ┆ ┆
0x31000…31100 (49, 0, 0) WangDocumentBody
[…0x3…]
0x31400…31500 (49, 0, 4) Sector 5f554e52454144 ┆_UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD_┆
0x31500…31600 (49, 0, 5) Sector 3106ff00193041 ┆1 0Aa NICS TARE, TRC/Point-to-point or SCARS/CCIS. 2) Complete outgoing messages via low speed teleprinters (operating as PTR's) 3) Complete outgoing or incoming messages entered via the dedicated PTR. The above described types received for analys┆
0x31600…31700 (49, 0, 6) Sector 31075000193041 ┆1 P 0Ais, forms 3 analysis types with individual and common functions as well. format respectively after conversion to external format. 3.3.2.4 Interface LOG - Incoming message logs - Outgoing message logs - Channel Discontinuity log 3.3.2.5 I┆
0x31700…31800 (49, 0, 7) Sector 3008ff00193041 ┆0 0A 1 A separate description of individual and common functions between the analysis-types will be specified in section 4.2.1. In general the function of ACP127 analysis are: a) Init┆
0x31800…31900 (49, 0, 8) WangDocumentBody
[…0x87…]
0x3a000…3a100 (58, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(58,0, 1), len=0xff, h3=41193041}, f00=»1930A «, f01=»CPS/SDS/033 «, f02=»UW «, f03=» «, f04=»1 «, f05=29-03-82 13:03, f06=» 3 «, f07=»04 «, f08=» 8715 «, f09= - - : , f10=» «, f11=» «, f12=» «, f13= - - : , f14=30-03-82 08:53, f15=»0149A «, f16=» 40 «, f17=» 3 «, f18=»04 «, f19=» 500 «, f20=» 8715 «, f21=» «, f22=» «, f99=020010000110066610a10a80aaca15050000000000000137039f00df}
0x3a100…3a200 (58, 0, 1) WangDocumentBody
[…0x46…]
0x3e800…3e900 (62, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(62,0, 9), len=0xff, h3=41191941}, f00=»1919A «, f01=»CPS/SDS/038 «, f02=»rt/uw «, f03=»JHH «, f04=»fra 4.2.2.4.4 «, f05=26-03-82 13:16, f06=» 8 «, f07=»48 «, f08=» 20719 «, f09=07-06-82 09:10, f10=» «, f11=»03 «, f12=» 45 «, f13=07-06-82 09:15, f14=11-06-82 11:30, f15=»0149A «, f16=» 56 «, f17=» 22 «, f18=»37 «, f19=» 560 «, f20=» 44436 «, f21=» «, f22=» @ «, f99=640000000110062710110490aaca1505000000000000003703c500df}
0x3e900…3ea00 (62, 0, 9) WangDocumentBody
[…0x2e…]
0x41800…41900 (65, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(65,0, 9), len=0xff, h3=41195141}, f00=»1951A «, f01=»CPS/SDS/038 «, f02=»vhn «, f03=»JHH «, f04=»TABLE OF CONTENTS «, f05=31-03-82 08:07, f06=» 1 «, f07=»25 «, f08=» 1818 «, f09=16-06-82 13:55, f10=» «, f11=»00 «, f12=» 2 «, f13=16-06-82 08:35, f14=16-06-82 15:56, f15=»0149A «, f16=» 7 «, f17=» 2 «, f18=»27 «, f19=» 276 «, f20=» 4064 «, f21=» «, f22=» «, f99=500010000110052710110290aaca15050000000000000142034800df}
0x41900…41a00 (65, 0, 9) WangDocumentBody
[…0x6…]
0x42000…42100 (66, 0, 0) Sector 4201ff00191941 ┆B AINF (m) refer 4.1.4 OUTPUT FLAG refer 4.2.2.5 SPLIT DIGIT (m) refer 4.2.2.5 CURSOR RECORD 1(m) refer 4.1.4 OUT LINE FLAG (m) refer 4.2.2.5 RESPONSE TEXT FLAG (m) refer 4.2.2.5 CMD FLAG (m) refer 4.2.2.5 SEQUENCE CODE NO (m) refer 4.2.2┆
0x42100…42200 (66, 0, 1) Sector 4202ff00191941 ┆B A.5 FC KEY OP (m) refer 4.1.4 HEADER IFCB refer 4.1.4 IN LINE FLAG (m) refer 4.2.2.5 FORMAT IFCB refer 4.1.4 c) Local Data CONST COUNT = 69 CONST CMD = 1 CONST NUME = 1 CONST CMD LINE = 3 VAR NOT IN FIELD: BOOLEAN VAR LIST: BUFFE┆
0x42200…42300 (66, 0, 2) Sector 42038000191941 ┆B AR LIST ELEMENT TYPE INIT NOT IN FIELD = FALSE VAR MSO FC KEY: MSO FC KEY TYPE VAR MASK 1, MASK 2: FC KEY MASK TYPE J 5IC$3I > S C_* ┆
0x42300…42400 (66, 0, 3) Sector 4204ff00191941 ┆B A 1 4.2.2.4.4.5 Module Design This module investigates the FC key inputs, invest if it shall enter MSOS SEQUENCE (4.2.2.4.11) and in cases where flags are set other modules are called┆
0x42400…42500 (66, 0, 4) Sector 4205c900191941 ┆B I A. On the other hand, if no flags are set and the FC key requests one, it is set and ENTER FC key input are expected. The cursor position on the command line, and ENTER FC key input are awaited. llerede p> systemdiskette ┆
0x42500…42600 (66, 0, 5) Sector 4206ff00191941 ┆B A 1 MSOS F/C KEY PROCESSING CASE WAIT SYSTEM CALL(FC KEY OP)(SPLIT DIGIT, MSO FC KEY, CC): ERROR OK ERROR? CASE ANALYSE ERROR(CC,2 PRIORITY OVERRIDE, VDU SP┆
0x42600…42700 (66, 0, 6) Sector 4207ce00191941 ┆B N ALIT FAI- LED):(ULB1, ULB2) ULB1? ULB2? SET VDU SPLIT FLAG = TRUE END CASE OK? FC KEY VALIDATION(4.2.2.4.4-2) END CASE FIGURE 4.2.2.4.4-1 16 636 44159 ' *J 7 Y _┆
0x42700…42800 (66, 0, 7) Sector 3f00ff00191941 ┆? A 1 FC KEY VALIDATION MSO FC KEY EQ ENTER? SPLIT DIGIT EQ FORMAT IFCB? SET MSO FC KEY = RETURN MSO FC KEY NOT IN MASK 1? DISPLAY ERROR MSG(ERROR NO)(4.2.2.6.4) O┆
0x42800…42900 (66, 0, 8) Sector 4209ff41191941 ┆B A A1919A CPS/SDS/038 rt/uw JHH fra 4.2.2.4.4 26 03 82 13 16 8 48 20719 03 06 82 10 04 2 46 2037 03 06 82 13 32 03 06 82 13 46 0149A 56 22 16 636 44159 ' *J 7 E _┆
0x42900…42a00 (66, 0, 9) Sector 420a3800191941 ┆B 8 A B B B B B B ? > > > > > = = = = < < < < ; ; ; ; ; 0 0 . . - - - - , , , , , + + + + + * * * * ) ) ) ) ) ) ( ( ( ( ent nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLSLSLSLSLSLSLSL┆
0x42a00…42b00 (66, 0, 10) Sector 420b9f00191941 ┆B A 1 CPS/SDS/038 JHH/820514 MSO VDU DETAILED DESIGN SPECIFICATION CAMPS 6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x42b00…42c00 (66, 0, 11) Sector 420cff00191941 ┆B A 1 4.2.2.4.4 MSOS F/C KEY PROCESSING 4.2.2.4.4.1 Functional Specification The purpose of this module is to analyse the FC KEY input, and, depending on the FC key identity to call ┆
0x42c00…42d00 (66, 0, 12) Sector 420dff00191941 ┆B Aother modules and procedures. Further it takes care of blanking the command and the response-line and placing the cursor on the command line. 4.2.2.4.4.2 Module Interface Call Specification a) MSOS FC KEY PROCESSING b) MSOS FC KEY PROCESSIN┆
0x42d00…42e00 (66, 0, 13) Sector 420e9900191941 ┆B AG (R6) Register Convention Call Register R6 LINK (DEST) Return Register None R0 - R7 (DEST) 4.2.2.4.4.3 Module Components None CR0Mc&!.=6 ! <6 M1' R40C.1! <6 M1' RC0C.1! <6 M1' RR0C.1!$<5CQ0!$<6 !&<6 Mc&! "(=6 E '<M% ! "2<┆
0x42e00…42f00 (66, 0, 14) Sector 420fff00191941 ┆B A 1 4.2.2.4.4.4 Data Description a) Data References MSOS CO OP TYPE refer 4.1.4 IOC FIELD DESCRIPTOR TYPE refer 4.1.4 MSO FC KEY TYPE refer 4.2.2.5 SEQUENCE CODE NO TYPE refe┆
0x42f00…43000 (66, 0, 15) Sector 4200ff00191941 ┆B Ar 4.2.2.5 BUFFER LIST ELEMENT TYPE refer CPS/DBD/001 ERROR NO TYPE refer 4.2.2.5 INTERNAL ERROR TYPE refer 4.1.4 FC KEY MASK TYPE refer 4.2.2.5 b) External Data FIELD DESCRIP (m) refer 4.1.4 VDU SPLIT FLAG (m) refer 4.1.4 INT ERROR ┆
0x43000…43100 (67, 0, 0) Sector 4301ff00191941 ┆C AUTPUT FLAG EQ TRUE? DISPLAY VDU FIELD(RESP LINE,SPACES) (4.2.2.6.5) SET OUTPUT FLAG = FALSE MSO FC KEY IN MASK 2? SET SEQUENCE CODE (4.2.2.4.4-6) MSOS SEQUENCE (4.2.2.4.11) MSO FC KEY EQ RETURN? INPUT CMD LINE (4.┆
0x43100…43200 (67, 0, 1) Sector 4302ff00191941 ┆C A2.2.4.4-4) VDU SPLIT FALG EQ TRUE? BYTE TRANSFERRED EQ 0? -SET CURSOR(RETURN) (4.2.2.6.2) SET IN FLAG = FALSE SET OUT FLAG = FALSE SET CMD FLAG = FALSE IN FLAG EQ TRUE? SET RES┆
0x43200…43300 (67, 0, 2) Sector 4303ff00191941 ┆C APONSE TEXT FLAG = FALSE OUT FLAG EQ TRUE? MSOS IN/OUT LINE (4.2.2.4.8) RESPONSE TEXT FLAG EQ TRUE? MSOS DISP RESP MSG(4.2.2.4.l0) CMD FLAG EQ TRUE? MSOS CMD PENDING(4.2.2.4.┆
0x43300…43400 (67, 0, 3) Sector 43046400191941 ┆C d A9) MSOS INTERBAL ERROR(GIVE UP)(4.l.5.2) INSPECT (4.2.2.4.4.-3) fig.4.2.2.4.4-2 CESSING 4.2.2.4.4.1 Functional Specification The purpose of this module is to analyse the FC KEY input, and, depending on the FC key identity to call ┆
0x43400…43500 (67, 0, 4) Sector 4305ff00191941 ┆C A 1 INSPECT GET CURSOR POSITION (4.2.2.4.4-5) VDU SPLIT FLAG EQ TRUE? MSO FC KEY EQ INSERT LINE? NOT IN FIELD EQ TRUE? DISPLAY ERROR MSG(ERROR NO)(4.2.2.6.4) ┆
0x43500…43600 (67, 0, 5) Sector 4306ff00191941 ┆C A SET IN FLAG = TRUE SET CURSOR(HEADER)(4.2.2.6.2) DISPLAY VDU FIELD(SMD.LINE.SPACES)(4.2.2.6.5) MSO FC KEY EQ DELETE LINE? NOT IN FIELD EQ TRUE? DISPLAY ERROR MSG(ERROR NO)(4.2.2.6.4) SET OUT ┆
0x43600…43700 (67, 0, 6) Sector 4307ff00191941 ┆C AFLAG = TRUE SET CURSOR(HEADER)(4.2.2.6.2) DISPLAY VDU FIELD(CMD LINE,SPACES)(4.2.2.6.5) MSO FC KEY EQ RESPONSE TEXT? SET RESPONSE TEXT FLAG = TRUE SET CURSOR(HEADER)(4.2.2.6.2) DISPLAY VDU FIELD(┆
0x43700…43800 (67, 0, 7) Sector 4208ff00191941 ┆B ACMD LINE, SPACES)(4.2.2.6.5) MSO FC KEY EQ COMMAND? SET CMD FLAG = TRUE SET CURSOR(HEADER)(4.2.2.6.2) DISPLAY VDU FIELD(CMD.LINE.SPACES) (4.2.2.6.5) MSOS INTERNAL ERROR(GIVE UP)┆
0x43800…43900 (67, 0, 8) Sector 4309ff00191941 ┆C A(m) refer 4.2.2.5 OUTPUT FLAG refer 4.2.2.5 SPLIT DIGIT (m) refer 4.2.2.5 CURSOR RECORD 1(m) refer 4.1.4 OUT LINE FLAG (m) refer 4.2.2.5 RESPONSE TEXT FLAG (m) refer 4.2.2.5 CMD FLAG (m) refer 4.2.2.5 SEQUENCE CODE NO (m) refer 4.2.2.5┆
0x43900…43a00 (67, 0, 9) Sector 430aff00191941 ┆C A FC KEY OP (m) refer STET HEADER IFCB refer 4.1.4 IN LINE FLAG (m) refer 4.2.2.5 c) Local Data CONST CMD = 1 CONST NUME = 1 CONST CMD LINE = 3 VAR NOT IN FIELD: BOOLEAN VAR LIST: BUFFER LIST ELEMENT TYPE VAR NOT IN FIELD: INTEGER┆
0x43a00…43b00 (67, 0, 10) Sector 430b2600191941 ┆C & A INIT NOT IN FIELD = FALSE Cq5M[2 R45Cq5M 2M[- RA5Cq5:^=~ BL5C`5M{) RV5Cq5M . R`5Cq5M@1MI1:h= Rp5Cr4IMM.:^=~ B}5I:g=~ J 5IC$3I > S C_* ┆
0x43b00…43c00 (67, 0, 11) Sector 430cff00191941 ┆C A 1 4.2.2.4.4.5 Module Design This module checks the FC key inputs, invest if it shall enter MSOS SEQUENCE (4.2.2.4.11) and in cases where flags are set other modules are called. On t┆
0x43c00…43d00 (67, 0, 12) Sector 430dc300191941 ┆C C Ahe other hand, if no flags are set and the FC key requests one, it is set and ENTER FC key input are expected. The cursor position on the command line, and ENTER FC key input are awaited. SOS SEQUENCE(4.2.2.4.ll) LOG ACK? CASE ANQ ATTR.HEADER.FL┆
0x43d00…43e00 (67, 0, 13) Sector 430eff00191941 ┆C A 1 MSOS F/C KEY PROCESSING CASE WAIT SYSTEM CALL(FC KEY OP)(SPLIT DIGIT, MSO FC KEY, CC): ERROR OK ERROR? CASE ANALYSE ERROR(CC,2 PRIORITY OVERRIDE, VDU SP┆
0x43e00…43f00 (67, 0, 14) Sector 430ffe00191941 ┆C ~ ALIT FAI- LED):(ULB1, ULB2) ULB1? ULB2? SET VDU SPLIT FLAG = TRUE SEQUENCE CODE NO = SEQ FAILURE MSOS SEQUENCE(4.2.2.4.11) END CASE OK? FC KEY VALIDATION(4.2.2.4.4-2) END CASE FIGURE 4.2.2.4.4-1 _┆
0x43f00…44000 (67, 0, 15) Sector 4300ff00191941 ┆C A 1 FC KEY VALIDATION MSO FC KEY EQ ENTER? SPLIT DIGIT EQ FORMAT IFCB SET MSO FC KEY = RETURN MSO FC KEY NOT IN MASK 1? DISPLAY ERROR MSG(ERROR NO)(4.2.2.6.4) O┆
0x44000…44100 (68, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(68,0, 1), len=0xff, h3=41191941}, f00=»1919A «, f01=»CPS/SDS/038 «, f02=»rt/uw «, f03=»JHH «, f04=»fra 4.2.2.4.4 «, f05=26-03-82 13:16, f06=» 8 «, f07=»48 «, f08=» 20719 «, f09=31-03-82 09:27, f10=» «, f11=»00 «, f12=» 2 «, f13=31-03-82 09:24, f14=01-04-82 09:12, f15=»0149A «, f16=» 43 «, f17=» 10 «, f18=»20 «, f19=» 476 «, f20=» 22064 «, f21=» «, f22=» @ «, f99=240000000110062710110480aaca15050000000000000037039100df}
0x44100…44200 (68, 0, 1) Sector 44022b00191941 ┆D + A D D D C C C C B B B B B B A A A A @ @ @ @ ? ? ? ? ? > > > > > = = = = < < < < < < ; ; ; ent nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLSLSLAKTIVITET DATO TID ANV.TID ANSLSLSL┆
0x44200…44300 (68, 0, 2) Sector 44039f00191941 ┆D A 1 CPS/SDS/038 JHH/820305 MSO VDU DETAILED DESIGN SPECIFICATION CAMPS 6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x44300…44400 (68, 0, 3) Sector 4404ff00191941 ┆D A 1 4.2.2.4.4 MSOS F/C KEY PROCESSING 4.2.2.4.4.1 Functional Specification The purpose of this module is to analyse the FC KEY input, and, depending on the FC key identity to call ┆
0x44400…44500 (68, 0, 4) Sector 4405ff00191941 ┆D Aother modules and procedures. Further it takes care of blanking the command and the response-line and placing the cursor on the command line. 4.2.2.4.4.2 Module Interface Call Specification a) MSOS FC KEY PROCESSING b) MSOS FC KEY PROCESSIN┆
0x44500…44600 (68, 0, 5) Sector 44069500191941 ┆D AG (R6) Register Convention Call Register R6 LINK (DEST) Return Register None R0 - R7 (DEST) 4.2.2.4.4.3 Module Components Z 0CR0Mc&!.=6 ! <6 M1' R40C.1! <6 M1' RC0C.1! <6 M1' RR0C.1!$<5CQ0!$<6 !&<6 Mc&! "(=6 E '<M% ! "2<┆
0x44600…44700 (68, 0, 6) Sector 4407ff00191941 ┆D A 1 4.2.2.4.4.4 Data Description a) Data References MSOS CO OP TYPE refer 4.1.4 IOC FIELD DESCRIPTOR TYPE refer 4.1.4 FC KEY TYPE refer CPS/DBD/001 SEQUENCE CODE NO TYPE refe┆
0x44700…44800 (68, 0, 7) Sector 4308ff00191941 ┆C Ar 4.2.2.5 BUFFER LIST ELEMENT TYPE refer CPS/DBD/001 ERROR NO TYPE refer 4.2.2.5 INTERNAL ERROR TYPE refer 4.1.4 b) External Data FIELD DESCRIP (m) refer 4.1.4 VDU SPLIT FLAG (m) refer 4.1.4 INT ERROR INF (m) refer 4.1.4 MSO FC KEY ┆
0x44800…44900 (68, 0, 8) Sector 4409ff00195141 ┆D QA....... 4.2.3.2 Software Structure ................. 4.2.3.3 Data Flow and Control Structure .... 4.2.3.5 DIDIA Module Specifications ........ 4.2.3.4.1 DIALOGUE CONTROL Specification . 4.2.3.4.2 VDU DATA OUTPUT Speci┆
0x44900…44a00 (68, 0, 9) Sector 440aff00195141 ┆D QAfication .. 4.2.3.4.3 VDU DATA INPUT Specification ... 4.2.3.4.4 VDU FORMAT OUTPUT .............. 4.2.3.4.5 SYNTAX VALIDATION .............. 4.2.3.4.6 SEMANTIC VALIDATION ............ 4.2.3.4.7 DISPLAY ERROR CODES ┆
0x44a00…44b00 (68, 0, 10) Sector 440bff00195141 ┆D QA............ 4.2.3.5 Common Subpackage Data ............. 4.2.3.6 Common Subpackage Procedures ....... 4.2.3.6.1 STOP INPUT OUTPUT .............. 4.2.3.6.2 CLEAN UP ....................... 4.2.3.6.3 LINE INSERT ....┆
0x44b00…44c00 (68, 0, 11) Sector 440cff00195141 ┆D QA................ 4.2.3.6.4 LINE DELETE .................... 4.2.3.6.5 CLEAR .......................... 4.2.3.6.6 SET BUFFER STRUCTURE ........... 4.2.3.6.7 SET MMI VDU ADDRESSES .......... 4.2.3.6.8 SET IOC REC ADD┆
0x44c00…44d00 (68, 0, 12) Sector 440dff00195141 ┆D QARESSES .......... 4.2.3.6.9 SET FIELD LIST ADDRESSES ....... 4.2.3.6.10 SET MEMORY ADDRESSES .......... 4.2.3.6.11 SET ERROR LIST ADDRESSES ...... 4.2.3.6.12 WRITE CIF BUF ................. 4.2.3.6.13 READ MMI CTRL┆
0x44d00…44e00 (68, 0, 13) Sector 440eff00195141 ┆D QA TABLE ........... 4.2.3.6.14 CLEAR SPLIT ................... 4.2.3.6.15 CREATE DISP REC ............... 4.2.3.6.16 FIELD REPEAT .................. 4.2.3.6.17 FIELD GROUP REPEAT ............ 4.2.3.6.18 DISPLAY LINE NOS ┆
0x44e00…44f00 (68, 0, 14) Sector 440f1600195141 ┆D QA.............. FUNCTION ............ 4.2.2.5 COMMON SUBPACKAGE DATA .......... 4.2.2.6 Common Subpackage Procedures .... 4.2.2.6.l VDU INIT .................... 4.2.2.6.2 SET CURSOR .................. 4.2.2┆
0x44f00…45000 (68, 0, 15) Sector 3a08ff00195141 ┆: QA 1 4.2.3.6.20 CHECK FINAL CALL .............. 4.2.3.6.21 EXEC VAL PROC ................. 4.2.3.6.22 EXEC ┆
0x45000…45100 (69, 0, 0) Sector 4501ff00195141 ┆E QA TEP CREATE CIF .............. 4.2.2.6.9 TEP CREATE NEW CIF .......... 4.2.2.6.l0 TEP NEW VIEW ................ 4.2.2.6.ll TEP TRSERNO ................. 4.2.2.6.l2 TEP RETURN VIEW ............. 4.2.2.6.l3 TE┆
0x45100…45200 (69, 0, 1) Sector 4502ff00195141 ┆E QAP SAVE VIEW ............... 4.2.2.6.l4 TEP READ BUFFER ............. 4.2.2.6.l5 TEP WRITE BUFFER ............ 4.2.2.6.l6 TEP RESERVE BUFFER .......... 4.2.2.6.l7 COPY TEXT FIELDS ............ 4.2.2.6 l8 UPDATE┆
0x45200…45300 (69, 0, 2) Sector 4503ff00195141 ┆E QA VDU HEADER ........... 4.2.2.6.19 SEND TO SERVICED MSG TO THP . 4.2.2.6.20 SEND REQUEST TO UMAM ........ 4.2.2.6.21 SEND REQUEST TO SAR ......... 4.2.2.6.22 SEND TO ASS PRINTER ........ 4.2.2.6.23 TEP OPEN V┆
0x45300…45400 (69, 0, 3) Sector 4504ff00195141 ┆E QAIEW ............... 4.2.2.6.24 SEND TO PRINTER PRINT ....... 4.2.2.6.25 COPY CIF FIELD .............. 4.2.2.6.26 TEP CLOSE VIEW .............. 4.2.2.7 Subpackage Interfaces ........... 4.2.2.7.l SEFCO SED┆
0x45400…45500 (69, 0, 4) Sector 45054f00195141 ┆E O QAIA Interfaces ...... 4.2.2.7.2 SEVCO SEFCO Interfaces ...... t Receive CMD QEL ......... 4.2.1.6.6 Set Receive CCMD QEL ........ 4.2.1.6.7 Send Notify ................. 4.2.1.6.8 Remove ...................... ┆
0x45500…45600 (69, 0, 5) Sector 4506ff00195141 ┆E QA 1 4.2.2.7.3 SETR SEFCO Interfaces ....... 4.2.2.7.4 SEDIA SEFCO Interfaces ...┆
0x45600…45700 (69, 0, 6) Sector 4507ff00195141 ┆E QA... 4.2.2.7.5 SEFCO SEVCO Interfaces ...... 4.2.2.7.6 SEFCO UMAM Interfaces ....... 4.2.2.7.7 UMAM SEFCO Interfaces ....... 4.2.3 Dialogue Subpackage .................... 4.2.3.1 Functional Specification .....┆
0x45700…45800 (69, 0, 7) Sector 4408ff00195141 ┆D QA...... 4.2.3.1.1 Output of Data ................. 4.2.3.1.2 Input of Data .................. 4.2.3.1.3 Validation ..................... 4.2.3.1.4 Display of Error Codes ......... 4.2.3.1.5 Error Handling ..........┆
0x45800…45900 (69, 0, 8) Sector 4509ff00195141 ┆E QA (4.0) ....................... 4.2.2.1.4.1 Start Execution (4.1) ... 4.2.2.1.4.2 Stop Execution (4.2) .... 4.2.2.1.4.3 Queue Requests (4.3) .... 4.2.2.1.4.4 Requests to CAMPS System (4.4) ......┆
0x45900…45a00 (69, 0, 9) Sector 450aff00195141 ┆E QA...... 4.2.2.1.5 Error Handling .............. 4.2.2.2 Software Structure .............. 4.2.2.3 Data Flow and Control Logic ..... 4.2.2.3.1 Data Flow ................... 4.2.2.3.2 Control Logic ..........┆
0x45a00…45b00 (69, 0, 10) Sector 450b1000195141 ┆E QA..... ................... 4.1.7.1 External Interfaces ............. 4.1.7.2 Package Interfaces .............. 4.1.7.2.1 Traffic Handling (THP) I/F... 4.1.7.2.2 Storage and Retrieval (SAR) ┆
0x45b00…45c00 (69, 0, 11) Sector 450cff00195141 ┆E QA 1 4.2.2.4 Module Specification ............ 4.2.2.4.1 SEFCO MAIN ..............┆
0x45c00…45d00 (69, 0, 12) Sector 450dff00195141 ┆E QA.... 4.2.2.4.2 RESTART SEFCO ............... 4.2.2.4.3 MSOS ANSWER Q PROCESSESING .. 4.2.2.4.4 MSOS F/C KEY PROCESSING .... 4.2.2.4.5 SEVCO CMD PROCESSING ........ 4.2.2.4.6 SEDIA CC PROCESSING ......... ┆
0x45d00…45e00 (69, 0, 13) Sector 450eff00195141 ┆E QA 4.2.2.4.7 SETR OP PROCESSING .......... 4.2.2.4.8 MSOS IN/OUT LINE ............ 4.2.2.4.9 MSOS CMD PENDING ............ 4.2.2.4.l0 MSOS DISPLAY RESP MSG ...... 4.2.2.4.ll MSOS SEQUENCE ............... 4.2┆
0x45e00…45f00 (69, 0, 14) Sector 450fff00195141 ┆E QA.2.4.l2 EXECUTE FUNCTION ............ 4.2.2.5 COMMON SUBPACKAGE DATA .......... 4.2.2.6 Common Subpackage Procedures .... 4.2.2.6.l VDU INIT .................... 4.2.2.6.2 SET CURSOR .................. 4.2.2┆
0x45f00…46000 (69, 0, 15) Sector 4500ff00195141 ┆E QA.6.3 MSO RECV FIRST .............. 4.2.2.6.4 DISPLAY ERROR MSG ........... 4.2.2.6.5 DISPLAY VDU FIELD ........... 4.2.2.6.6 MSO RECV NEXT ............... 4.2.2.6.7 CALCULATE FORMAT ............ 4.2.2.6.8┆
0x46000…46100 (70, 0, 0) Sector 4601f600195141 ┆F v QA. 4.2.1.2.7 Internal Antiflash .......... 4.2.1.2.8 Common Procedures ........... 4.2.1.3 Dataflow and Control Logic within SEVCO .................... 4.2.1.4 SEVCO Module Specification ...... 4 PACKA┆
0x46100…46200 (70, 0, 1) Sector 4602ff00195141 ┆F QA 1 4.2.1.4.1 SEVCO Control ............... 4.2.1.4.2 TEMCO CMD Processing .....┆
0x46200…46300 (70, 0, 2) Sector 4603ff00195141 ┆F QA... 4.2.1.4.3 Flash Queue Monitoring ...... 4.2.1.4.4 Timer Event Processing ...... 4.2.1.4.5 SEFCO Response Processing ... 4.2.1.4.6 Internal Flash .............. 4.2.1.4.7 Internal Antiflash .......┆
0x46300…46400 (70, 0, 3) Sector 4604ff00195141 ┆F QA... 4.2.1.5 Common Subpackage Data .......... 4.2.1.6 Common Subpackage Procedures .... 4.2.1.6.1 Signal SEFCO ................ 4.2.1.6.2 Flash Queue Fields Update ... 4.2.1.6.3 Queue Fields Update .......┆
0x46400…46500 (70, 0, 4) Sector 4605ff00195141 ┆F QA.. 4.2.1.6.4 Display VDU Header .......... 4.2.1.6.5 Set Receive CMD QEL ......... 4.2.1.6.6 Set Receive CCMD QEL ........ 4.2.1.6.7 Send Notify ................. 4.2.1.6.8 Remove ...................... ┆
0x46500…46600 (70, 0, 5) Sector 4606ff00195141 ┆F QA 4.2.1.6.9 Set Date Time ............... 4.2.1.6.10 Invert And Bell ............. 4.2.1.6.11 Get Queue Length ............ 4.2.1.6.12 Get Total Free .............. 4.2.1.6.13 Set Prec Length ............. ┆
0x46600…46700 (70, 0, 6) Sector 4607ff00195141 ┆F QA 4.2.1.6.14 Get USERQ Length ............ 4.2.1.7 Subpackage Interfaces ........... 4.2.1.7.1 SEVCO-SEFCO Interfaces ...... 4.2.1.7.2 SEFCO-SEVCO Interfaces ...... 4.2.2 MSO Function Control Subpackage .... ┆
0x46700…46800 (70, 0, 7) Sector 4508ff00195141 ┆E QA 4.2.2.1 Functional Specification ........ 4.2.2.1.1 System Control (1.0) ........ 4.2.2.1.2 Transaction Accounting (2.0) . 4.2.2.1.3 Transaction Creation (3.0) .. 4.2.2.1.4 Format Sequence Function ┆
0x46800…46900 (70, 0, 8) Sector 4609ff00195141 ┆F QA 1 4.1.4 Common Package Data ................. 4.1.5 Common Package Procedures .┆
0x46900…46a00 (70, 0, 9) Sector 460aff00195141 ┆F QA.......... 4.1.5.1 MSOS Queue Error ................ 4.1.5.2 MSOS Internal Error ............. 4.1.5.3 Dism ............................ 4.1.6 Global Data ......................... 4.1.7 Interfac┆
0x46a00…46b00 (70, 0, 10) Sector 460bff00195141 ┆F QAes .......................... 4.1.7.1 External Interfaces ............. 4.1.7.2 Package Interfaces .............. 4.1.7.2.1 Traffic Handling (THP) I/F... 4.1.7.2.2 Storage and Retrieval (SAR) ┆
0x46b00…46c00 (70, 0, 11) Sector 460cff00195141 ┆F QAI/F ................... 4.1.7.2.3 Log and Accountability (LOG) I/F ................... 4.1.7.2.4 SSC Software I/F ............ 4.1.7.2.5 Table Management Package (TMP) I/F ........... ┆
0x46c00…46d00 (70, 0, 12) Sector 460dff00195141 ┆F QA 4.1.7.3 Subpackage Interfaces ........... 4.1.7.3.1 Process Interfaces .......... 4.1.7.3.2 Coroutine Interfaces ........ 4.2 Subpackage Specification ................ 4.2.1 Message Service Control Sub ┆
0x46d00…46e00 (70, 0, 13) Sector 460eff00195141 ┆F QApackage . 4.2.1.1 Functional Specification ........ 4.2.1.1.1 Initialization .............. 4.2.1.1.2 TEMCO Command Processing .... 4.2.1.1.3 Flash Item Control .......... 4.2.1.1.4 Timer Event Processing ┆
0x46e00…46f00 (70, 0, 14) Sector 460fff00195141 ┆F QA...... 4.2.1.1.5 VDU Header Control .......... 4.2.1.1.6 SEFCO Control ............... 4.2.1.1.7 Error Reporting ............. 4.2.1.2 Software Structure .............. 4.2.1.2.1 SEVCO Control ...........┆
0x46f00…47000 (70, 0, 15) Sector 4600ff00195141 ┆F QA.... 4.2.1.2.2 TEMCO CMD Processing ........ 4.2.1.2.3 Flash Queue Monitoring ...... 4.2.1.2.4 Timer Event Processing ...... 4.2.1.2.5 SEFCO Response Processing ... 4.2.1.2.6 Internal Flash .............┆
0x47000…47100 (71, 0, 0) Sector 4701ff00195141 ┆G QA.............. 3.3.2.4 THP I/F ........................... 3.3.2.5 UMAM I/F .......................... 3.3.2.6 VUS I/F ........................... 3.4 FUNCTIONS MAINTAINED BY OTHER PACKAGES .... 4 PACKA┆
0x47100…47200 (71, 0, 1) Sector 4702ff00195141 ┆G QAGE DESIGN ................................ 4.1 PACKAGE OVERVIEW .......................... 4.1.1 Functional Specification .............. 4.1.1.1 TEMCO Control Function ............ 4.1.1.2 Queue Status Function .┆
0x47200…47300 (71, 0, 2) Sector 4703ff00195141 ┆G QA............ 4.1.1.3 Transaction Accounting ............ 4.1.1.4 Transaction Interruption .......... 4.1.1.5 Command Interpretation ............ 4.1.1.6 Command Execution ................. 4.1.1.7 St┆
0x47300…47400 (71, 0, 3) Sector 4704ff00195141 ┆G QAart/Stop Transaction Execution .. 4.1.1.8 Preparation of Service Messages ... 4.1.1.9 Presentation of Queued Information 4.1.1.10 Requests to CAMPS System .......... 4.1.1.11 Dialogue Formatting ...............┆
0x47400…47500 (71, 0, 4) Sector 4705ff00195141 ┆G QA 4.1.1.12 Format Validation ................. 4.1.1.13 Service Message Database Maintenance ....................... 4.1.2 Software Specification ................ 4.1.2.1 SEVCO Sub-Package ..............┆
0x47500…47600 (71, 0, 5) Sector 4706ff00195141 ┆G QA... 4.1.2.2 SEFCO Sub-Package ................. 4.1.2.3 SEDIA Sub-Package ................. 4.1.2.4 SETR Sub-Package .................. 4.1.3 Data Flow and Control Logic ........... 4.1.3.1 Process D┆
0x47600…47700 (71, 0, 6) Sector 4707ff00195141 ┆G QAata Flow and Process Syn- chronization....................... 4.1.3.2 MSOP Internal Data Flow and Corou- ting Synchronization .............. 4.1.3.2.1 Normal Functional Flow (Major transaction) ....┆
0x47700…47800 (71, 0, 7) Sector 46081b00195141 ┆F QA.............. ans- action in Progress ................ 2.2.1.3 Display of Queued Information ..... 2.2.1.3.1 The Incoming Message Queue .... 2.2.1.3.2 The Outgoing Message Queue .... 2.2.1.3┆
0x47800…47900 (71, 0, 8) Sector 4709ff00195141 ┆G QA.3 The Response Queue ............ 2.2.1.3.4 The User Queue ................ 2.2.1.4 Requests to CAMPS System .......... 2.2.1.5 Service Message Preparation ....... 2.2.1.6 Maintenance and Update of Message┆
0x47900…47a00 (71, 0, 9) Sector 470aff00195141 ┆G QA Status Files ...................... 2.2.2 Functional Responsibilities ........... 2.2.2.1 Initializaton, Close Down, and Restart ........................... 2.2.2.2 Checkpointing and Recovery ........┆
0x47a00…47b00 (71, 0, 10) Sector 470bff00195141 ┆G QA 2.2.2.3 Error Detection and Error Handling 2.2.2.4 Integrity of Operation ............ 2.2.2.5 Data Collection ................... 2.2.2.6 Security .......................... 2.3 CHARACTERISTICS ...┆
0x47b00…47c00 (71, 0, 11) Sector 470cff00195141 ┆G QA........................ 2.3.1 Timing ................................ 2.3.2 Throughput ............................ 2.3.3 Flexibility ........................... 2.3.4 Accuracy .............................. ┆
0x47c00…47d00 (71, 0, 12) Sector 470d0900195141 ┆G QA ta CONST MAX ERROR NO = 99 4.2.2.4.10.5 Module Design The number read from the command line is converted to integer and if the convertion result is beyond a max range or illegal, an error message is displayed. Other- wise the common proc┆
0x47d00…47e00 (71, 0, 13) Sector 470eff00195141 ┆G QA 1 3 ENVIRONMENT ................................... 3.1 EQUIPMENT ................┆
0x47e00…47f00 (71, 0, 14) Sector 470fff00195141 ┆G QA................. 3.2 SOFTWARE .................................. 3.2.1 System Software ....................... 3.2.2 Development Support Software .......... 3.3 INTERFACE ................................. ┆
0x47f00…48000 (71, 0, 15) Sector 4700ff00195141 ┆G QA3.3.1 External Interfaces ................... 3.3.2 Package Interfaces .................... 3.3.2.1 SSC I/F ........................... 3.3.2.2 LOG I/F ........................... 3.3.2.3 SAR I/F .............┆
0x48000…48100 (72, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(72,0, 1), len=0xff, h3=41195141}, f00=»1951A «, f01=»CPS/SDS/038 «, f02=»vhn «, f03=»JHH «, f04=»TABLE OF CONTENTS «, f05=31-03-82 08:07, f06=» 1 «, f07=»25 «, f08=» 1818 «, f09= - - : , f10=» «, f11=» «, f12=» «, f13=31-03-82 09:37, f14=01-04-82 09:13, f15=»0149A «, f16=» 7 «, f17=» 1 «, f18=»25 «, f19=» 256 «, f20=» 1818 «, f21=» «, f22=» «, f99=020010000110056610110480aaca15050000000000000142034500df}
0x48100…48200 (72, 0, 1) Sector 48020700195141 ┆H QA H H G F F E E D DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG Oprettet / / : : S S: S┆
0x48200…48300 (72, 0, 2) Sector 48039f00195141 ┆H QA 1 CPS/SDS/038 JHH/820305 MSO VDU DETAILED DESIGN SPECIFICATION CAMPS 6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x48300…48400 (72, 0, 3) Sector 4804ff00195141 ┆H QA 1 TABLE OF CONTENTS 1 ┆
0x48400…48500 (72, 0, 4) Sector 4805ff00195141 ┆H QA1 GENERAL ....................................... 1.1 PURPOSE AND SCOPE ......................... 1.2 APPLICABLE DOCUMENTS AND PROJECT REFERENCES 1.2.1 Applicable Documents .................. 1.2.2 Reference Docum┆
0x48500…48600 (72, 0, 5) Sector 4806ff00195141 ┆H QAents ................... 1.3 TERMS AND ABBREVIATIONS ................... 1.3.1 Terms ................................. 1.3.2 Abbreviations ......................... 2 SUMMARY OF REQUIREMENTS .......................┆
0x48600…48700 (72, 0, 6) Sector 4807ff00195141 ┆H QA 2.1 PACKAGE DESCRIPTION ....................... 2.2 PACKAGE FUNCTIONS ......................... 2.2.1 Main Functions ........................ 2.2.1.1 Queue Status Display .............. 2.2.1.2 Informat┆
0x48700…48800 (72, 0, 7) Sector 4708ff00195141 ┆G QAion Concerning the Trans- action in Progress ................ 2.2.1.3 Display of Queued Information ..... 2.2.1.3.1 The Incoming Message Queue .... 2.2.1.3.2 The Outgoing Message Queue .... 2.2.1.3┆
0x48800…48900 (72, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(72,0, 9), len=0xff, h3=41188341}, f00=»1883A «, f01=»CPS/SDS/038 «, f02=»vhn «, f03=»JHH «, f04=»4.2.3 «, f05=22-03-82 16:19, f06=» 4 «, f07=»30 «, f08=» 8860 «, f09=25-05-82 13:57, f10=» 1 «, f11=»04 «, f12=» 1246 «, f13=26-05-82 09:56, f14=27-05-82 13:24, f15=»0149A «, f16=»114 «, f17=» 5 «, f18=»34 «, f19=» 1136 «, f20=» 10106 «, f21=» «, f22=» «, f99=020010000110062710110290aaca15050000000000000137037d01df}
0x48900…48a00 (72, 0, 9) Sector 480a7200188341 ┆H r A H H ┆
0x48a00…48b00 (72, 0, 10) Sector 480b9f00188341 ┆H A 1 CPS/SDS/038 JHH/820514 MSO VDU DETAILED DESIGN SPECIFICATION CAMPS 6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x48b00…48c00 (72, 0, 11) Sector 480cff00188341 ┆H A 1 1 4.2.3 Dialogue Subp┆
0x48c00…48d00 (72, 0, 12) Sector 480dff00188341 ┆H Aackage .................... 4.2.3.1 Functional Specification ........... 4.2.3.1.1 Output of Data ................. 4.2.3.1.2 Input of Data .................. 4.2.3.1.3 Validation ..................... ┆
0x48d00…48e00 (72, 0, 13) Sector 480eff00188341 ┆H A 4.2.3.1.4 Display of Error Codes ......... 4.2.3.2 Software Structure ................. 4.2.3.3 Data Flow and Control Structure .... 4.2.3.5 SEDIA Module Specifications ......... 4.2.3.4.1 DIALOGUE CONTROL Spe┆
0x48e00…48f00 (72, 0, 14) Sector 480fff00188341 ┆H Acification . 4.2.3.4.1.1 Functional Specification ... 4.2.3.4.1.2 Module Interface ........... 4.2.3.4.1.3 Module Components .......... 4.2.3.4.1.4 Data Description ........... 4.2.3.4.1.5 Modul┆
0x48f00…49000 (72, 0, 15) Sector 2000ff00188341 ┆ Ae Design .............. 4.2.3.4.2 VDU DATA OUTPUT Specification .. 4.2.3.4.2.1 Functional Specification ... 4.2.3.4.2.2 Module Interface ........... 4.2.3.4.2.3 Module Components .......... 4.2┆
0x49000…49100 (73, 0, 0) Sector 49015900189941 ┆I Y A 1 Tre hippoer ┆
0x49100…49200 (73, 0, 1) Sector 4902ff00189941 ┆I A 1 1 4.2.4.4 Module Specification 4.2.4.4.1 SETR MAIN Module 4.2.4.4.1.1 Functional Specification The purpos┆
0x49200…49300 (73, 0, 2) Sector 4903ff00189941 ┆I Ae of this module is to receive input from the retrieve queue (MSOS ARR, subqueue 3) and to analyse the received QEL-attributes (maintype,subtype) 4.2.4.4.1.2 Module Interface Call Specification a) SETR MAIN b) SETR MAIN (R6) Register Conve┆
0x49300…49400 (73, 0, 3) Sector 4904ff00189941 ┆I Antion Call Register R6 Link (dest) Return Register None R0-R7 Destroyed The procedure is a submodule which is only called by the Coroutine Monitor. 4.2.4.4.1.3 Module Components 4.2.4.4.1.3.1 OFFLINE SETR HANDLING ┆
0x49400…49500 (73, 0, 4) Sector 49053f00189941 ┆I ? A sends off-line retrieved messages to response queue. Control Logic ........ 4.2.4.3.1 Data Flow ..................... 4.2.4.3.2 Control Logic .................. 4.2.4.7 Subpackage Interfaces .............. ┆
0x49500…49600 (73, 0, 5) Sector 4906ff00189941 ┆I A 1 4.2.4.4.1.3.2 OFFLINE SYSCAT HANDLING sends off-line retrieved system catalogues to response queue. 4.2.4.4.1.3.3 OFFLINE TRANSCAT HANDLING sends off-line retrived transmi┆
0x49600…49700 (73, 0, 6) Sector 49072c00189941 ┆I , Assion catalogues to response queue. 4.2.4 Retrieve Subpackage The Message Service Retrieve Subpackage (RETR) is responsible for reception and treatment of retrieval answer from SAR. 4.2.4.1 Functional Specificatio┆
0x49700…49800 (73, 0, 7) Sector 1d08ff00189941 ┆ A 1 4.2.4.4.1.4 Data Description a) Data References QELEMENT MAIN TYPE ref. CPS/DBD/001 ACK SUBTYPE ref. CPS/DBD/001 TRANS CAT SUBTYPE ref. CPS/DBD/001 MESSAGE SUBTYPE ref. C┆
0x49800…49900 (73, 0, 8) Sector 49099b00189941 ┆I A items and off-line/on-line notifications are received from SAR in the retrieve queue. After analysis, the received item is sent to the destination = R$3C/4!e=6 !f=6 !g=6 !h=6 Ml+M;) RE3C#4: 2i=:g=~ JV3C/4!"<6 #6 MB&! =6 !,<6 :]=2'< AMD MB&!,<6 ! ┆
0x49900…49a00 (73, 0, 9) Sector 490aff00189941 ┆I A 1 4.2.4.2 Software Structure The retrieve subpackage consists of one coroutine. The software structure of SETR is shown in figure 4.2.4.2-1. SETR will wait on reception of a QEL┆
0x49a00…49b00 (73, 0, 10) Sector 490bff00189941 ┆I A in the Retrieve Queue. The QEL will identify one of the following events: - on-line/off-line notification - on-line retrieval - off-line retrieval Each of the events will constitute a main function. A brief description of each function is give┆
0x49b00…49c00 (73, 0, 11) Sector 490cff00189941 ┆I An below: a) On-line/off-line notification. The received item is sent to SEFCO. b) On-line Retrieval: The received item is sent to SEFCO. c) Off-line Retrieval: The received item is sent to the Response Queue. d) Retrieval Error Not┆
0x49c00…49d00 (73, 0, 12) Sector 490d3900189941 ┆I 9 Aification. The received item is sent to SEFCO DEX) = BOCB (INDEX) END Figure 4.2.3.6.12-1 MMI CTRL REC.ITEM COUNT PT) EQUIVALENCE (MMI CTRL TABLE(MMI PT), DISP PROC: MMI CTRL REC.DISPLAY PROCEDURE) EQUIVALENCE┆
0x49d00…49e00 (73, 0, 13) Sector 490e5f00189941 ┆I _ A 1 figure 4.2.4.2-1 (MMI CTRL TABLE(MMI PT), ERR: MMI CTRL REC. ERROR CODE) EQUIVALENCE ((BOCB(I PT BASE)+DATA PT)%, ITEM: ARRAY (1..I SIZE) OF BYTES) EQUIVALENCE ((BOC┆
0x49e00…49f00 (73, 0, 14) Sector 490fff00189941 ┆I A 1 4.2.4.3 Data Flow and Control Logic 4.2.4.3.1 Data Flow The HIPO diagram overleaf show the data flow of SETR. Refer fig. 4.2.4.3-1 to 3 4.2.4.3.2 Control Logic The control ┆
0x49f00…4a000 (73, 0, 15) Sector 49003000189941 ┆I 0 Alogic of SETR is contained in one module. ┆
0x4a000…4a100 (74, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(74,0, 1), len=0xff, h3=41189941}, f00=»1899A «, f01=»CPS/SDS/038 «, f02=»bk «, f03=»JHH «, f04=»4.2.4.2 «, f05=24-03-82 08:50, f06=» 4 «, f07=»14 «, f08=» 9832 «, f09=26-05-82 10:12, f10=» 2 «, f11=»38 «, f12=» 10138 «, f13=26-05-82 13:38, f14=27-05-82 13:25, f15=»0149A «, f16=» 35 «, f17=» 8 «, f18=»20 «, f19=» 292 «, f20=» 20953 «, f21=» «, f22=»& «, f99=020010000110062710110490aaca15050000000000000137036a00df}
0x4a100…4a200 (74, 0, 1) Sector 4a022300189941 ┆J # A J J J I I I I I I I Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID rer: STATISTIK AKTIVITET DATO TID STIK AKTIVI┆
0x4a200…4a300 (74, 0, 2) Sector 4a039f00189941 ┆J A 1 CPS/SDS/038 JHH/820514 MSO VDU DETAILED DESIGN SPECIFICATION CAMPS 6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x4a300…4a400 (74, 0, 3) Sector 4a04ff00189941 ┆J A 1 1 4.2.4.2 Software S┆
0x4a400…4a500 (74, 0, 4) Sector 4a05ff00189941 ┆J Atructure ................. 4.2.4.3 Data Flow and Control Logic ........ 4.2.4.3.1 Data Flow ..................... 4.2.4.3.2 Control Logic .................. 4.2.4.7 Subpackage Interfaces .............. ┆
0x4a500…4a600 (74, 0, 5) Sector 4a066d00189941 ┆J m A 4.2.4.7.1 RETR UMAM Interfaces ........... 4.2.4.7.2 RETR UFCO Interfaces ........... %0! <6 M1' R 0C 0! <6 M1' R 0C 0! <6 M1' Z 0CR0Mc&!.=6 ! <6 M1' R40C.1! <6 M1' RC0C.1! <6 M1' RR0C.1!$<5CQ0!$<6 !&<6 Mc&! "(=6 E '<M% ! "2<┆
0x4a600…4a700 (74, 0, 6) Sector 4a07ff00189941 ┆J A 1 4.2.4 Retrieve Subpackage The Message Service Retrieve Subpackage (RETR) is responsible for reception and treatment of retrieval answer from SAR. 4.2.4.1 Functional Specificatio┆
0x4a700…4a800 (74, 0, 7) Sector 4908ff00189941 ┆I An The functions included in this subpackage are the following: - reception of off-line/on-line notification - reception of retrieved items - reception of error notification The functional breakdown is shown in figure 4.2.4.1-1. Retrieved┆
0x4a800…4a900 (74, 0, 8) Sector 00000000000000 ┆ ┆
[…0x27…]
