OctetView
0x00000…00100 (0, 0, 0) Sector 01704130313730 ┆ pA0170A ┆
0x00100…00200 (0, 0, 1) Sector 00000000000000 ┆ ┆
0x00200…00300 (0, 0, 2) Sector ff00f0f8e0ffff ┆ px` ┆
0x00300…00306 (0, 0, 3) WangDocument {d00=0x15, d01=0x53, d02=0x41, ptr=(21,0, 8), d05=0x00}
0x00306…0030c WangDocument {d00=0x21, d01=0x28, d02=0x41, ptr=(26,0, 8), d05=0x00}
0x0030c…00312 WangDocument {d00=0x21, d01=0x33, d02=0x41, ptr=(35,0, 8), d05=0x00}
0x00312…00318 WangDocument {d00=0x21, d01=0x41, d02=0x41, ptr=(42,0, 8), d05=0x00}
0x00318…00320 21 41 41 4a 08 00 00 00 ┆!AAJ ┆
0x00320…00340 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ ┆
[…0x5…]
0x003e0…00400 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 18 ┆ ┆
0x00400…00500 (0, 0, 4) Sector 00000000000000 ┆ ┆
0x00500…00600 (0, 0, 5) Sector 01704130313730 ┆ pA0170A ┆
0x00600…00700 (0, 0, 6) Sector 421c402600415b ┆B @& A[' I X% % PO P ; !AAh0 C f x f V W O 8 :h0 h3 ) 2141A f e < {C < { ; 3 ` o IC b bJ P Q 9 8 : 1553A2141A h2h3g3g4g0 ┆
0x00700…00800 (0, 0, 7) Sector 00000000000000 ┆ ┆
[…0x8…]
0x01000…01100 (1, 0, 0) WangDocumentBody
[…0x3…]
0x01400…01500 (1, 0, 4) Sector 00000000000000 ┆ ┆
[…0x3…]
0x01800…01900 (1, 0, 8) WangDocumentBody
[…0x4…]
0x01d00…01e00 (1, 0, 13) Sector 010eff00212841 ┆ !(AUTINE 11 Modules x 0,175 K 1,925 33 Procedures 0,050 K 1,65 3,575 VDIA COROUTINE 7 Modules x 0,175 K 1,225 24 Procedures 0,050K 1,2 2,425 RERT COROUTINE 1 Module x 0,30 OK 0,300 0,3 TOTAL ┆
0x01e00…01f00 (1, 0, 14) Sector 010fef00212841 ┆ o !(A7,575 statements Thus 1 Source statement equal 2 words and Data Area is estimated to 3 K Words the Memdory turns to be: 7,575 K Words x 2 + 3 K Words = 18,15 Words UMAM PROCESS 18 Modules x 0,150 2,700 30 Procedures x 0,0nents N/A ┆
0x01f00…02000 (1, 0, 15) Sector 00004500212841 ┆ E !(A30 0,900 3,600 statements UMAM data are = 6,0 KW 4.2.6.4.4.4 Data Description a) Data References MSO SUBP ID Refer 4.2.6.5 b) External Data SEVCO REC Refer CPS/SDS/038 4.1.4 SEVCO PRIO Refer CPS/SDS/038 4.1.4 SEFCO R┆
0x02000…02100 (2, 0, 0) WangDocumentBody
[…0x2…]
0x02300…02400 (2, 0, 3) Sector 0204ff00155341 ┆ SAe = true by the next call of VCO Q NEXT or VCO Q TERM. Export procedure VCO Q TERM (R4 C K % VCO Q DESCR R6) C K LINK Procedure RETURN Q EL (R4 C D % VCO Q DESCR R6) C K LINK R7 R Set to VCO STACK.CUR PTR Other reg's Destroyed !!! ┆
0x02400…02500 (2, 0, 4) Sector 0205ff00155341 ┆ SA 1 Returns or dismantles the queue element references by VCO Q DESCR according to VCO Q DESCR.STATE as follows: QU EMPTY: Nothing is done QU RETURN: Queue element is RETURN'ed to ┆
0x02500…02600 (2, 0, 5) Sector 0206ff00155341 ┆ SAQUEUE QU DISMANTLE: Queue is TEP DISMANTLE's with CHECKPOINT = FALSE Qu SAVE: Queue is TEP DISMANTLE'd with CHECKPOINT = TRUE Afterwards STATE IN VCO Q DESCR is set to QU EMPTY. 4.2.1.7 Subpackage Interfaces 4.2.1.7.1 VCO UFCO Interfaces ┆
0x02600…02700 (2, 0, 6) Sector 02077c00155341 ┆ | SA The following commands are sent from VCO to UFCO via operation semaphore VUS S2: START UFCO STOP UFCO BLOCK UFCO Gets the actual value of FLASH QUEUE TIMEOUT by calling the TMP REQUEST TMP GET SYSTEM PARAM, FLASH QUEUE TIMEOUT. Procedure┆
0x02700…02800 (2, 0, 7) Sector 0000f900155341 ┆ y SA CLOSE UFCO 4.2.1.7.2 UFCO VCO Interfaces Completion codes are sent from UFCO to VCO for the following commands: START UFCO STOP UFCO BLOCK UFCO CLOSE UFCO The following completion codes exist: OK CC ERROR CC SPLIT FAILED CC PM TIM┆
0x02800…02900 (2, 0, 8) WangDocumentBody
[…0x12f…]
0x15800…15900 (21, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(21,0, 9), len=0xff, h3=41155341}, f00=»1553A «, f01=»CPS/SDS/039 «, f02=»pn «, f03=»JBS «, f04=»4.1.1.4-2 «, f05=23-12-81 10:06, f06=» 11 «, f07=»36 «, f08=» 39119 «, f09=26-07-85 13:04, f10=» «, f11=»00 «, f12=» 6 «, f13=24-07-85 11:27, f14=01-08-85 09:34, f15=»0170A «, f16=» 72 «, f17=» 48 «, f18=»24 «, f19=» 684 «, f20=»116652 «, f21=» «, f22=» ` «, f99=020000000110062710110080aaca1505000000000000003703f500df}
0x15900…15a00 (21, 0, 9) WangDocumentBody
[…0x7…]
0x16100…16200 (22, 0, 1) Sector 00004600214141 ┆ F !AA OTHERWISE? INTERNAL ERROR (GIVE UP) FIGURE 4.2.2.4.7-1 Call Register R5 pointer to VDIA OP (DEST) R6 LINK (DEST) Return Register R0 - R7 (DEST) 4.2.2.4.6.3 Module Component None dule Components 4.2.2.4.4.3.1 RESP ACT┆
0x16200…16300 (22, 0, 2) Sector 1603a400155341 ┆ $ SA 1 # CPS/SDS/039 841101 USER VDU DETAILED DESIGN SPECIFICATION ISSUE 1 CAMPS !/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x16300…16400 (22, 0, 3) Sector 16045f00155341 ┆ _ SA 1 Fig. 4.1.1.4-2 Bp.MP- Rm.> IM)-MI,:^=~ B~.> IMB'IM2& 9x2"<!Z="(=^#Vk"$<:]=2#<:^=~ J6.! <6 M8) R6.> I! <6 M8)I!h=6 ! =6 M")IM"):g=~ J /:h=2>=M?.Mj': < Zn.C / E*:=k 0wM% !;=4C┆
0x16400…16500 (22, 0, 4) Sector 1605ff00155341 ┆ SA 1 4.1.2 Software Specification In this section the software structure of VUP will be described. The allocation of functions onto processes and coroutines will be explained, based on┆
0x16500…16600 (22, 0, 5) Sector 1606ff00155341 ┆ SA the analysis performed in section 4.1.1. Figure 4.1.2-1 shows the mapping of functions onto processes and coroutines 4.1.2.1. VUS Process The VDU USER PROCESS controls the interaction with the user VDU, under supervision of TEMCO (SSC softwa┆
0x16600…16700 (22, 0, 6) Sector 1607ec00155341 ┆ l SAre). It thus has the following responsibilities: - TEMCO command execution - Control and execution of user transactions - User transaction accounting - Maintaining the VDU Header queue status - Monitoring of FLASH queues. 6$`i6 {M)(sM &M7 ┆
0x16700…16800 (22, 0, 7) Sector 15085e00155341 ┆ ^ SA 1 Fig. 4.1.2-1 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=!┆
0x16800…16900 (22, 0, 8) WangDocumentBody
[…0x3f…]
0x1a800…1a900 (26, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(26,0, 9), len=0xff, h3=41212841}, f00=»2128A «, f01=»CPS/SDS/039 «, f02=»ja «, f03=»JBS «, f04=»4.2.6. «, f05=03-05-82 18:29, f06=» 4 «, f07=»02 «, f08=» 15677 «, f09=13-02-85 08:33, f10=» «, f11=»01 «, f12=» 2 «, f13=13-02-85 13:45, f14=20-06-85 13:25, f15=»0170A «, f16=» 34 «, f17=» 14 «, f18=»29 «, f19=» 444 «, f20=» 36287 «, f21=» «, f22=» «, f99=020010000110052710110380aa8a37040000000000000142039300df}
0x1a900…1aa00 (26, 0, 9) WangDocumentBody
[…0x8e…]
0x23800…23900 (35, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(35,0, 9), len=0xff, h3=41213341}, f00=»2133A «, f01=»CPS/SDS/039 «, f02=»bk «, f03=»JBS «, f04=»4.2.1.5 «, f05=05-05-82 09:22, f06=» 3 «, f07=»56 «, f08=» 6704 «, f09=17-05-82 15:39, f10=» «, f11=»02 «, f12=» 37 «, f13=18-05-82 08:21, f14=03-08-83 09:20, f15=»0170A «, f16=» 34 «, f17=» 4 «, f18=»49 «, f19=» 240 «, f20=» 8288 «, f21=» «, f22=» «, f99=100010000110052710110290aaca15050000000000000042035400df}
0x23900…23a00 (35, 0, 9) WangDocumentBody
[…0x6e…]
0x2a800…2a900 (42, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(42,0, 9), len=0xff, h3=41214141}, f00=»2141A «, f01=»CPS/SDS/039 «, f02=»vhn «, f03=»JBS «, f04=»4.2.2 «, f05=10-05-82 14:33, f06=» 12 «, f07=»55 «, f08=» 44047 «, f09=26-07-85 13:05, f10=» «, f11=»01 «, f12=» 13 «, f13=24-07-85 10:13, f14=01-08-85 09:35, f15=»0170A «, f16=» 53 «, f17=» 30 «, f18=»44 «, f19=» 504 «, f20=» 70028 «, f21=» «, f22=» «, f99=020050000510052710110080aaca1505000000000000014203b100df}
0x2a900…2aa00 (42, 0, 9) WangDocumentBody
[…0x6…]
0x2b000…2b100 (43, 0, 0) Sector 2b01ff41214141 ┆+ A!AA2141A CPS/SDS/039 vhn JBS 4.2.2 10 05 82 14 33 12 55 44047 17 04 84 09 58 1 52 3243 31 01 84 14 50 08 11 84 15 02 0170A 53 27 05 548 68473 % ' *J B 2 _┆
0x2b100…2b200 (43, 0, 1) Sector 2b023500214141 ┆+ 5 !AA + + * * * * ) ) ) ( ( ( ( ' ' ' ' ' ' & & & & & & & % % % % % $ $ $ $ DOKUMENTOVERSIGT Dokument nr: DoDoDo DoDoDo Dokument nr: DoDoDo DoDo DoDoDoDoDoDoDoDo┆
0x2b200…2b300 (43, 0, 2) Sector 2b03a600214141 ┆+ & !AA 1 # CPS/SDS/039 841101 USER VDU DETAILED DESIGN SPECIFICATION ISSUE 1 CAMPS =6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x2b300…2b400 (43, 0, 3) Sector 2b04ff00214141 ┆+ !AA 1 1 4.2.2.4.1.1 Fun┆
0x2b400…2b500 (43, 0, 4) Sector 2b05ff00214141 ┆+ !AActional Specification ... 4.2.2.4.1.3.1 CANCEL ANQ IN-PUT...... 4.2.2.4.1.3.2 REQUEST ANQIN-PUT........ 4.2.2.4.1.3.3 REQUEST FC KEY IN-PUT.. 4.2.2.4.1.3.4 CANCEL FC KEY IN-PUT.. 4.2.2.4.┆
0x2b500…2b600 (43, 0, 5) Sector 2b06ff00214141 ┆+ !AA1.4. Data Description.......... 4.2.2.4.1.5 Module Design .............. 4.2.2.4.2 VUS ANSER Q PROCESSING ......... 4.2.2.4.2.1 Functional Specification .. 4.2.2.4.2.2 Module Interface ........... ┆
0x2b600…2b700 (43, 0, 6) Sector 2b07ff00214141 ┆+ !AA 4.2.2.4.2.3 Module Component ........... 4.2.2.4.2.3.1 Delete Append CIF ...... 4.2.2.4.2.4 Data Description ........... 4.2.2.4.2.5 Module Design .............. 4.2.2.4.3 Append Investigation .....┆
0x2b700…2b800 (43, 0, 7) Sector 2a08ff00214141 ┆* !AA..... 4.2.2.4.3.1 Functional Description .... 4.2.2.4.3.2 Module Interface .......... 4.2.2.4.3.3 Module Components ......... 4.2.2.4.3.4 Data Description .......... 4.2.2.4.3.5 Module Desi┆
0x2b800…2b900 (43, 0, 8) Sector 2b09ef00214141 ┆+ o !AAR, the answer queue or the VDU. Each command will constitute a main function and is, as well as major function, implemented as a module. Furthermore some common procedures and module components exist. Refer figure 4.2.2.2.1-2. ne the format wh┆
0x2b900…2ba00 (43, 0, 9) Sector 2b0a6200214141 ┆+ b !AA 1 Figs. 4.2.2.2-1/2 nctions are those which must be performed when a user gives up access to a CIF. a) Dismantle CIF / Buffer (4.2.1) These functions are those used to inte┆
0x2ba00…2bb00 (43, 0, 10) Sector 2b0bff00214141 ┆+ !AA 1 4.2.2.3 Data Flow and Control Logic 4.2.2.3.1 Data Flow The HIPO diagrams overleaf show the data flow of UFCO. 4.2.2.3.2 Control Logic The control logic of UFCO is shown i┆
0x2bb00…2bc00 (43, 0, 11) Sector 2b0c2f00214141 ┆+ / !AAn the module-tree in figure 4.2.2.2-1/2. nctions update the VDU header fields, classification and terminal function. e transaction creation group includes all the functions to be performed before a transaction may be started. a) Receive and Valid┆
0x2bc00…2bd00 (43, 0, 12) Sector 2b0d6600214141 ┆+ f !AA 1 Diag. ID: 4.2.2.3/24 4.3) The queue request functions are those concerning the reception of messages. a) Receive (4.3.1) The first CIF to which the requestor has acces┆
0x2bd00…2be00 (43, 0, 13) Sector 2b0e5f00214141 ┆+ _ !AA 1 Fig. 4.2.2.3-1 a queue. c) Keep (4.3.3) This function returns a CIF to a queue. d) Keep and Present next (4.3.4) This function returns a CIF to the queue from which┆
0x2be00…2bf00 (43, 0, 14) Sector 2b0fff00214141 ┆+ !AA 1 4.2.2.4 Module Specification UFCO MAIN (4.2.2.4.1) VUS ANSWER Q PROCESSING (4.2.2.4.2) APPEND INVESTIGATION (4.2.2.4.3) VUS F/C KEY PROCESSING (4.2.2.4.4) VCO CMD PROCESSING ┆
0x2bf00…2c000 (43, 0, 15) Sector 2b00ff00214141 ┆+ !AA(4.2.2.4.5) VDIA CC PROCESSING (4.2.2.4.6) RETR OP PROCESSING (4.2.2.4.7) VUS IN/OUT LINE (4.2.2.4.8) VUS CMD PENDING (4.2.2.4.9) VUS SEQUENCE (4.2.2.4.10) EAXECUTE FUNCTION (4.2.2.4.11) 4.2.2.4.1 UFCO MAIN 4.2.2.4.1.1 Functional Specific┆
0x2c000…2c100 (44, 0, 0) Sector 2c018100214141 ┆, !AAion created by MDP is displayed. b) Send for Release (4.4.2) The message is sent to the associated release terminal. ine. f) Execute Function Key The functions associated with the received function key are performed and the format sequenc┆
0x2c100…2c200 (44, 0, 1) Sector 2c02ff00214141 ┆, !AA 1 c) Release (4.4.3) The message is sent for local distribution and transmission. A release notification is returned to the drafter. d) Retrieve / Append (4.4.4) A retrieve r┆
0x2c200…2c300 (44, 0, 2) Sector 2c03ff00214141 ┆, !AAequest is sent to SAR and the retrieved CIF and/or a response message is displayed. e) Print (4.4.5) The CIF currently displayed on the VDU is sent to the associated printer, or the atomal printer. f) Defer (4.4.6) The preparation is termi┆
0x2c300…2c400 (44, 0, 3) Sector 2c04ff00214141 ┆, !AAnated and the CIF is sent to the preparation database. g) Status Request (4.4.7) A status request is sent to UMAM and the received CIF is displayed. h) Send for Distribution (4.4.8) A comment is sent for local distribution. i) Edit / Del┆
0x2c400…2c500 (44, 0, 4) Sector 2c057600214141 ┆, v !AAete Requests (4.4.9) A request is sent to UMAM and the referenced CIF or a response message is displayed. cution (4.1) The start execution functions are those which must be performed before a format is presented for a user. a) Create CIF /┆
0x2c500…2c600 (44, 0, 5) Sector 2c06ff00214141 ┆, !AA 1 4.2.2.1.5 Error Handling The error handling function is separated into two parts: a) Q ERROR (5.1) This function handles error due to failure in communication between UFCO an┆
0x2c600…2c700 (44, 0, 6) Sector 2c07ff00214141 ┆, !AAd its queues and decides whether or not the processing may continue. b) Internal (5.2) This function handles errors due to failure in communication between b1) the subpackages communicating with UFCO b2) the modules within UFCO, and decides whe┆
0x2c700…2c800 (44, 0, 7) Sector 2b08ff00214141 ┆+ !AAther or not the processing may continue. 4.2.2.2 Software Structure The UFCO subpackage consists of one coroutine with operation semaphore S2 as the main waiting point. The input to UFCO will be a command which is received from VCO, VDIA, RET┆
0x2c800…2c900 (44, 0, 8) Sector 2c09ff00214141 ┆, !AA 1 e) Display Error Code (4.1.5) These functions display a response message in the VDU response line. f) Determine Message Type (4.1.6) These functions determine the format wh┆
0x2c900…2ca00 (44, 0, 9) Sector 2c0aff00214141 ┆, !AAich shall be used for a message. 4.2.2.1.4.2 Stop Execution (4.2) The stop execution functions are those which must be performed when a user gives up access to a CIF. a) Dismantle CIF / Buffer (4.2.1) These functions are those used to inte┆
0x2ca00…2cb00 (44, 0, 10) Sector 2c0bff00214141 ┆, !AArface to the message management system. b) Update Status (4.2.2) The outgoing message status, release message status and the delivery message status are updated. The message / comment under preparation is returned to the preparation database. ┆
0x2cb00…2cc00 (44, 0, 11) Sector 2c0c7c00214141 ┆, | !AA c) Update VDU Header (4.2.3) These functions update the VDU header fields, classification and terminal function. e transaction creation group includes all the functions to be performed before a transaction may be started. a) Receive and Valid┆
0x2cc00…2cd00 (44, 0, 12) Sector 2c0dff00214141 ┆, !AA 1 4.2.2.1.4.3 Queue Requests (4.3) The queue request functions are those concerning the reception of messages. a) Receive (4.3.1) The first CIF to which the requestor has acces┆
0x2cd00…2ce00 (44, 0, 13) Sector 2c0eff00214141 ┆, !AAs is received from a given queue. b) Delete (4.3.2) This function removes a CIF from a queue. c) Keep (4.3.3) This function returns a CIF to a queue. d) Keep and Present next (4.3.4) This function returns a CIF to the queue from which┆
0x2ce00…2cf00 (44, 0, 14) Sector 2c0fff00214141 ┆, !AA it was received. The next CIF to which the requestor has access is returned. e) Delete and Present next (4.3.5) This function removes a CIF from the queue from which it was received. The next CIF to which the requestor has access is returned. ┆
0x2cf00…2d000 (44, 0, 15) Sector 2c00ff00214141 ┆, !AA 4.2.2.1.4.4 Requests to CAMPS System (4.4) The request functions are those concerning the treatment of messages (CIFs) and requests (buffers). a) Send for Coordination (4.4.1) The message is sent for coordination and the delivery notificat┆
0x2d000…2d100 (45, 0, 0) Sector 2d01ff00214141 ┆- !AA the correct range. e) Display Response Message (3.5) These functions display a response message in the VDU response line. f) Execute Function Key The functions associated with the received function key are performed and the format sequenc┆
0x2d100…2d200 (45, 0, 1) Sector 2d02ff00214141 ┆- !AAe is changed. g) Execute Command (3.7) The sequence table key is looked up in the command validation table and the format sequence is started. h) Assign Transaction Number (3.8) Allocates next transaction no. for this terminal. 4.2.2.1.4┆
0x2d200…2d300 (45, 0, 2) Sector 2d03e100214141 ┆- a !AA Format Sequence Function (4.0) The format sequence functions are those functions which are called from the format sequence table. This table makes it possible to drive the MMI in an automatic and flexible manner. .!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x2d300…2d400 (45, 0, 3) Sector 2d04ff00214141 ┆- !AA 1 It defines for each screen format: - Allowed commands and function keys - Functions to be called corresponding to commands/F/C Keys - LOG, STATISTICS, SAR reporting required ┆
0x2d400…2d500 (45, 0, 4) Sector 2d05ff00214141 ┆- !AA - Cursor position - Command to VDIA - Subsequently sequence record to be executed 4.2.2.1.4.1 Start Execution (4.1) The start execution functions are those which must be performed before a format is presented for a user. a) Create CIF /┆
0x2d500…2d600 (45, 0, 5) Sector 2d06ff00214141 ┆- !AABuffer (4.1.1) These functions are those used to interface to the message management system. b) Request CIF (4.1.2) If a continue preparation command is received, then the referenced CIF is fetched from the preparation database. If a rece┆
0x2d600…2d700 (45, 0, 6) Sector 2d07ff00214141 ┆- !AAive command is received, then the first CIF in the corresponding queue is fetched. c) Update VDU Header (4.1.3) These functions update the VDU header fields, classification and terminal function. d) Complete Append (4.1.4) These functions ┆
0x2d700…2d800 (45, 0, 7) Sector 2c08a100214141 ┆, ! !AAadd a section of another message to a message under preparation. It shall be noticed that an off-line append can result in two security interrogations. ...... 4.2.2.4.3.4 Data Description .......... 4.2.2.4.3.5 Module Desi┆
0x2d800…2d900 (45, 0, 8) Sector 2d09ff00214141 ┆- !AA 1 4.2.2.1.2 Transaction Accounting (2.0) The transaction accounting functions are those concerning log and statistics. a) Collect Data (2.1) The data which are used for log, st┆
0x2d900…2da00 (45, 0, 9) Sector 2d0aff00214141 ┆- !AAatistics and other purposes are collected in sequence table. There exists no special collecting procedures but all data which are pertinent for UFCO will be placed in this area. b) Log Reporting (2.2) The log reporting functions are those requi┆
0x2da00…2db00 (45, 0, 10) Sector 2d0bff00214141 ┆- !AAred to report final log records. The data which are required in a log record are extracted from the sequence table. c) Statistics Reporting (2.3) The statistics reporting functions are those required to report statistics. The data which are ┆
0x2db00…2dc00 (45, 0, 11) Sector 2d0cff00214141 ┆- !AArequired in the statistics are monthly extracted from the sequence table. 4.2.2.1.3 Transaction Creation (3.0) The transaction creation group includes all the functions to be performed before a transaction may be started. a) Receive and Valid┆
0x2dc00…2dd00 (45, 0, 12) Sector 2d0dff00214141 ┆- !AAate (3.1) Function keys entered by a user are received from the VDU. The received function key is validated against a function key bit mask. There are two bit masks. Bit mask (1) reflects the function keys which are allowed at the moment. ┆
0x2dd00…2de00 (45, 0, 13) Sector 2d0e5800214141 ┆- X !AA Bit mask (2) reflects the function keys which will change the format sequence. 4.2.2.4.7 RETR OP PROCESSING ............ 4.2.2.4.7.1 Functional Specifica┆
0x2de00…2df00 (45, 0, 14) Sector 2d0fff00214141 ┆- !AA 1 b) Define Next Function Key (3.2) If a function key must be followed by another, this is defined (i.e. RETURN shall follow COMMAND). c) Receive Command Line (3.3) The conte┆
0x2df00…2e000 (45, 0, 15) Sector 2d00ff00214141 ┆- !AAnts of the VDU command line are received via the format handler. d) Validate Command Line (3.4) The contents of the command line are validated. A command is validated against the command validation table. Parameters are checked to be within┆
0x2e000…2e100 (46, 0, 0) Sector 2e01ff00214141 ┆. !AA the VDU dialogue. 4.2.2.1 Functional Specification The following functions are included in this subpackage: - System control - Transaction accounting - Transaction creation - Format sequence functions - Error Handling Fig. 4.2.2.1-┆
0x2e100…2e200 (46, 0, 1) Sector 2e022b00214141 ┆. + !AA1 presents the functional breakdown. ┆
0x2e200…2e300 (46, 0, 2) Sector 2e036000214141 ┆. ` !AA 1 Figs. 4.2.2.1-1/5 40601 USER VDU DETAILED DESIGN SPECIFICATION ISSUE 1 CAMPS /=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x2e300…2e400 (46, 0, 3) Sector 2e04ff00214141 ┆. !AA 1 4.2.2.1.1 System Control (1.0) The system control functions are those which indirectly involve the SSC package. The commands are received from VCO. a) Initialization (1.1) Ex┆
0x2e400…2e500 (46, 0, 4) Sector 2e05ff00214141 ┆. !AAecutes the function to be performed after load of software and which must be executed before normal operation can be initiated. Depending on the type of initialization, different actions are taken. An initialization command is sent to VDIA. b) ┆
0x2e500…2e600 (46, 0, 5) Sector 2e06ff00214141 ┆. !AAStart-Up (1.2) Executes the function to be performed after sign-on. The command validation table reflecting the user capability is defined. c) Termination (1.3) This function provides the UFCO with the capability of performing the following ┆
0x2e600…2e700 (46, 0, 6) Sector 2e07ff00214141 ┆. !AAfunctions: - Sign-off - Block terminal - Ordered close-down. d) Security Interrogation (1.4) Requests a security interrogation to be performed in case of release. Executes the functions to be performed after a security interrogation (┆
0x2e700…2e800 (46, 0, 7) Sector 2d082400214141 ┆- $ !AAe.g. receive function keys). Functional Description .... 4.2.2.4.3.2 Module Interface .......... 4.2.2.4.3.3 Module Components ......... 4.2.2.4.3.4 Data Description .......... 4.2.2.4.3.5 Module Desi┆
0x2e800…2e900 (46, 0, 8) Sector 2e09ff00214141 ┆. !AAgn ............. 4.2.2.4.4 VUS F/C KEY PROCESSING ......... 4.2.2.4.4.1 Functional Specification .. 4.2.2.4.4.2 Module Interface ........... 4.2.2.4.4.3 Module Components ......... 4.2.2.4.4.4┆
0x2e900…2ea00 (46, 0, 9) Sector 2e0aff00214141 ┆. !AA Data Description .......... 4.2.2.4.4.5 Module Design ............. 4.2.2.4.5 VCO CMD PROCESSING ............ 4.2.2.4.5.1 Functional Specification .. 4.2.2.4.5.2 Module Interface .......... ┆
0x2ea00…2eb00 (46, 0, 10) Sector 2e0bff00214141 ┆. !AA 4.2.2.4.5.3 Module Component .......... 4.2.2.4.5.3.1 STOP ACTION ........... 4.2.2.4.5.4 Data Description ........ 4.2.2.4.5.5 Module Design ........... 4.2.2.4.6 VDIA CC PROCESSING ...........┆
0x2eb00…2ec00 (46, 0, 11) Sector 2e0cff00214141 ┆. !AA. 4.2.2.4.6.1 Functional Specification .. 4.2.2.4.6.2 Module Interface .......... 4.2.2.4.6.3 Module Component ......... 4.2.2.4.6.4 Data Description .......... 4.2.2.4.6.5 Module Design .┆
0x2ec00…2ed00 (46, 0, 12) Sector 2e0d1800214141 ┆. !AA............ r Findes ikke Flyt positions-viser Funktion annulleret Ukendt kommando JA eller ANNULLER Kun tal Kun mellemrum eller retur Under redigering nu Ukendt dokument Fundet I brug nu Allerede p> systemdiskette ┆
0x2ed00…2ee00 (46, 0, 13) Sector 2e0eff00214141 ┆. !AA 1 4.2.2.4.7 RETR OP PROCESSING ............ 4.2.2.4.7.1 Functional Specifica┆
0x2ee00…2ef00 (46, 0, 14) Sector 2e0fe400214141 ┆. d !AAtion ... 4.2.2.4.7.2 Module Interface ........... 4.2.2.4.7.3 Module Component ........... 4.2.2.4.7.4 Data Description ........... 4.2.2.4.7.5 Module Design .............. ' * 7 B 3 _┆
0x2ef00…2f000 (46, 0, 15) Sector 2e00ff00214141 ┆. !AA 1 4.2.2 User Function Control Subpackage The User Function Control (UFCO) subpackage performs the control of all user transactions. Furthermore, UFCO performs the direct control of┆
0x2f000…2f100 (47, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(47,0, 1), len=0xff, h3=41214141}, f00=»2141A «, f01=»CPS/SDS/039 «, f02=»vhn «, f03=»JBS «, f04=»4.2.2 «, f05=10-05-82 14:33, f06=» 12 «, f07=»55 «, f08=» 44047 «, f09=17-04-84 09:58, f10=» «, f11=»06 «, f12=» 94 «, f13=11-04-84 11:30, f14=17-04-84 10:11, f15=»0170A «, f16=» 54 «, f17=» 25 «, f18=»19 «, f19=» 492 «, f20=» 65324 «, f21=» «, f22=» «, f99=020010000110052710110380aa8a3704000000000000014203b300df}
0x2f100…2f200 (47, 0, 1) Sector 2f023600214141 ┆/ 6 !AA / / . . . . - - - , , , , + + + + + + * * * * * * * ) ) ) ) ) ( ( ( ( ' ' ' ' & & & & & & & % % % % % % $ $ $ DOKUMENTOVERSIGT Dokument nr: DoDoDo DoDoDo Dokument nr: DoDoDo DoDo DoDoDoDoDoDoDo┆
0x2f200…2f300 (47, 0, 2) Sector 2f03a500214141 ┆/ % !AA 1 CPS/SDS/039 840601 USER VDU DETAILED DESIGN SPECIFICATION ISSUE 1 CAMPS /=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x2f300…2f400 (47, 0, 3) Sector 2f04ff00214141 ┆/ !AA 1 1 4.2.2.4.1.1 Fun┆
0x2f400…2f500 (47, 0, 4) Sector 2f05ff00214141 ┆/ !AActional Specification ... 4.2.2.4.1.3.1 CANCEL ANQ IN-PUT...... 4.2.2.4.1.3.2 REQUEST ANQIN-PUT........ 4.2.2.4.1.3.3 REQUEST FC KEY IN-PUT.. 4.2.2.4.1.3.4 CANCEL FC KEY IN-PUT.. 4.2.2.4.┆
0x2f500…2f600 (47, 0, 5) Sector 2f06ff00214141 ┆/ !AA1.4. Data Description.......... 4.2.2.4.1.5 Module Design .............. 4.2.2.4.2 VUS ANSER Q PROCESSING ......... 4.2.2.4.2.1 Functional Specification .. 4.2.2.4.2.2 Module Interface ........... ┆
0x2f600…2f700 (47, 0, 6) Sector 2f07ff00214141 ┆/ !AA 4.2.2.4.2.3 Module Component ........... 4.2.2.4.2.3.1 Delete Append CIF ...... 4.2.2.4.2.4 Data Description ........... 4.2.2.4.2.5 Module Design .............. 4.2.2.4.3 Append Investigation .....┆
0x2f700…2f800 (47, 0, 7) Sector 2e08ff00214141 ┆. !AA..... 4.2.2.4.3.1 Functional Description .... 4.2.2.4.3.2 Module Interface .......... 4.2.2.4.3.3 Module Components ......... 4.2.2.4.3.4 Data Description .......... 4.2.2.4.3.5 Module Desi┆
0x2f800…2f900 (47, 0, 8) Sector 2f09a100212841 ┆/ ! !(ALINK Calls UPDATE ERROR LIST using information from field bundle, found from address in stack (WORK.REG 1). Updates stacked result code (WORK.REG 0). dation procedure for each possible field of the user formats. The function of each procedure w┆
0x2f900…2fa00 (47, 0, 9) Sector 2f0aff00212841 ┆/ !(A 1 4.2.7.4.1.4 Software Design VAL CLASS FILE: SYNTAX VAL2.S PROCEDURE: CLASS VALIDATION: Classification, 2 chars without IOC STORAGE 0: bin value 2 bytes STORAGE 1: - VUP S┆
0x2fa00…2fb00 (47, 0, 10) Sector 2f0bff00212841 ┆/ !(AEMAN REC.UC.CLASS bin values USPR TABLES:TAB CLASS SHORT TMP: - COMMENTS: - VAL SPH FILE: SYNTAX VAL2.S PROCEDURE: SPH VALIDATION: Special Handling bundle max. 2 fields without IOC STORAGE 0: bitmask, national name 6 bytes STORAGE 1: n┆
0x2fb00…2fc00 (47, 0, 11) Sector 2f0cff00212841 ┆/ !(Aumber of sphs 2 bytes VUP SEMAN REC.VC.SPH bitmask USPR TABLES:- TMP: SPECIAL HANDLING TABLE COMMENTS: - VAL MHI DECISION FILE: SYNTAX VAL2.S PROCEDURE: MHI DECISION VALIDATION: Message Handling decision "Y" or " " STORAGE 0: - STORAG┆
0x2fc00…2fd00 (47, 0, 12) Sector 2f0dff00212841 ┆/ !(AE 1: - VUP SEMAN REC - USPR TABLES - TMP: - COMMENTS: - VAL PREC ACTION FILE SYNTAX VAL2.S PROCEDURE PREC ACTION VALIDATION Action precedence - mandatory 2 chars. without IOC STORAGE 0 bin value 2 bytes STORAGE 1 - VUP SEMAN REC.UC.A┆
0x2fd00…2fe00 (47, 0, 13) Sector 2f0e4c00212841 ┆/ L !(ACTION PREC bin value USPR TABLES TAB PREC SHORT TMP - COMMENTS - ODE R6) C LINK s are used to convert data from internal representation to strings which can be displayed on the VDU. During input syntax and semantic procedures are used to ┆
0x2fe00…2ff00 (47, 0, 14) Sector 2f0fff00212841 ┆/ !(A 1 VAL PREC INFO FILE SYNTAX VAL2.S PROCEDURE PREC INFO VALIDATION Info precedence - optional 2 chars without IOC STORAGE 0 bin value 2 bytes STORAGE 1 - VUP SEMAN REC.INFO ┆
0x2ff00…30000 (47, 0, 15) Sector 0700ff00212841 ┆ !(APRECEDENCE bin value USPR TABLES TAB PREC SHORT TMP - COMMENTS - VAL SCDS FILE SYNTAX VAL2.S PROCEDURE SCDS VALIDATION SCD - optional bundle max. 16 fields without IOC STORAGE 0 non blank SCDs 4 characters STORAGE 1 - VUP SEMAN REC.CO┆
0x30000…30100 (48, 0, 0) Sector 3001ff00212841 ┆0 !(AISION CODE = VUP SEMAN REC.UC.DECISION CHAR NOT COUND - ERROR CODE V RR INVALID Procedure returns directly to caller of VUP SYNTAX. Subactions should look as follows: PROCEDURE ... LABEL TABLE BEGIN LOCATION (TABLE) = R0 DECISION┆
0x30100…30200 (48, 0, 1) Sector 3002ff00212841 ┆0 !(A (R0, R1, R5, R7, R6) TABLE (CHAR) (DECISION CODE) ... ... 0 END OF TABLE END 1 Procedure CALL TMP (VAL REF: INTEGER VALIDATIO┆
0x30200…30300 (48, 0, 2) Sector 3003ff00212841 ┆0 !(AN PROC REC - USED FOR FATAL ERROR REPORTING TABLE ID: TABLE ID TYPE FUNCTION: TMP FUNCTION MASK1: BITMASK MASK2: BITMASK R0 C K TMP PARAM.ENTRY R1 C K TMP PARAM.BUFFER1 R2 C K TMP PARAM.COUNT R3 C K TMP PARAM.BUFFER2 R4 C K % TMP┆
0x30300…30400 (48, 0, 3) Sector 30043e00212841 ┆0 > !(A PARAM R5 C K TMP PARAM.BUFFER2 LENGTH R6) C LINK 4.2.7.1.3 Semantic Procedures The semantic procedures are a set of procedures which are able to validate the context between different fields in format. I.e. is it in message head┆
0x30400…30500 (48, 0, 4) Sector 3005ff00212841 ┆0 !(A 1 Performs a TMP call using the call parameters in constant parameter record and in registers. The register R4 should point to a TMP param record allocated for the TMP call. Proced┆
0x30500…30600 (48, 0, 5) Sector 3006ff00212841 ┆0 !(Aure MANDATORY (R0 - K R1 C K %FIELD BUNDLE R2 - D UNDEFINED AT RETURN R3 - D UNDEFINED AT RETURN R4 - K R5 - K R7 C K P STACK INTEGER - SYNTAX WORK STACK R6) C - LINK Checks that the first field in bundle in non-blank. If field is ┆
0x30600…30700 (48, 0, 6) Sector 3007ff00212841 ┆0 !(Ablank, the procedure issues a validation error and returns directly to caller of VUP SYNTAX. If filed is not blank, the procedure returns to LINK. A field is considered blank if: - It is without IOC header and first char is space - It is with I┆
0x30700…30800 (48, 0, 7) Sector 2f08ff00212841 ┆/ !(AOC header and IOC count is = 0 Procedure VAL ERROR (R2 C K FIELD NO IN BUNDLE (1, 2, ...) R3 C K ERROR CODE R7 C K =P STACK INTEGER, must point to main stack record stacked by VUF SYNTAX main entry i.e. record in stack of type WORK R6) C ┆
0x30800…30900 (48, 0, 8) Sector 3009ff00212841 ┆0 !(A 1 4.2.7.4.1.1 Functional Specification The function of this module is to contain a validation procedure for each possible field of the user formats. The function of each procedure w┆
0x30900…30a00 (48, 0, 9) Sector 300aff00212841 ┆0 !(Aill be shown in a schematic form. This scheme (ref. 4.2.7.4.1.4) will describe the main functions of a procedure. If further details are necessary please refer to the source list. 4.2.7.4.1.2 Module Interface All syntax procedures have the same┆
0x30a00…30b00 (48, 0, 10) Sector 300bff00212841 ┆0 !(A interface, thus they will be described as one. SYNTAX PROC (R6) Register conventions: R0: Syntax procedure reference (case label) R1: Pointer to field bundle R4: Pointer to memory record 1 (UFCO VAL) R5: Pointer to memory record 3 (SEMAN V┆
0x30b00…30c00 (48, 0, 11) Sector 300cff00212841 ┆0 !(AAL) R7: P STACK % INTEGER painting to stack of type WORM containing: BUF, WRU1, PROC NO: Working location for subaction R0: Result value OK/NOT OK R1-R6: Call registers. The subaction should return directly to caller of VUP SYNTAX b┆
0x30c00…30d00 (48, 0, 12) Sector 300dff00212841 ┆0 !(Ay use of the stacked link (r6). The record WORK should be unstacked prior to return. 4.2.7.4.1.3 Module Components 1 Procedure SEARCH TERM SCD (R0 C K SCD: CHARS 1 AND 2 R1 C┆
0x30d00…30e00 (48, 0, 13) Sector 300e5f00212841 ┆0 _ !(A SCD: CHAR 3 R SCD CHAR 3 AND SPACE R3 R RESULT: OK OR ERROR CODE R6) C LINK s are used to convert data from internal representation to strings which can be displayed on the VDU. During input syntax and semantic procedures are used to ┆
0x30e00…30f00 (48, 0, 14) Sector 300fff00212841 ┆0 !(A 1 A trailing space is added to the 3 char SCD. The SCD is searched in the terminal profile for the terminal (found via init area in M.O). Procedure DECISION (R0 C LOCATION OF DE┆
0x30f00…31000 (48, 0, 15) Sector 3000ff00212841 ┆0 !(ACISION CODE TABLE R1 C % FIELD BUNDLE R5 C % M.3 (VUP SEMAN RECORD) R7 C P STACK INTEGER - WORK RECORD R6) C DUMMY LINK Searches the first char in input from field bundle field 1 in the in-code table addressed by R0: CHAR FOUND - DEC┆
0x31000…31100 (49, 0, 0) Sector 3101ff00212841 ┆1 !(Ahe display procedures are a set of procedures, which are able to convert data in internal representation to displayable string. Data in internal representation can be numbers (byte, interger or long) or ASCII strings, while external representation i┆
0x31100…31200 (49, 0, 1) Sector 3102ff00212841 ┆1 !(As IOC records. I.e. a long of time type can be converted to an ASCII string. 4.2.7.1.2 Syntax Procedures The syntax procedures are a set of procedures which are able to validate and convert data from external format to internal representation. ┆
0x31200…31300 (49, 0, 2) Sector 3103bd00212841 ┆1 = !(AI.e. a SCD is validated against the SCD table and stored as an ASCII string, and a PLA is validated against the PLA table and stored as a PLA-ref (integer) and as an ASCII string. on fig. 4.2.6.2-1. The initialisation subpackage contains 2 module┆
0x31300…31400 (49, 0, 3) Sector 3104ff00212841 ┆1 !(A 1 4.2.7.1.3 Semantic Procedures The semantic procedures are a set of procedures which are able to validate the context between different fields in format. I.e. is it in message head┆
0x31400…31500 (49, 0, 4) Sector 3105ff00212841 ┆1 !(Aer validated that info precedence is not higher than action precedence. 4.2.7.2 Software Structure The structure of the three kinds of user procedures are alike as they all are built as big cases, switching to the wanted action. If needed a new┆
0x31500…31600 (49, 0, 5) Sector 3106ff00212841 ┆1 !(A procedure easily can be added by adding a new case label and coding a new procedure with the call convensions for the module. This procedure can now be activated from the Format Control Program simply by using its reference (case label) while readi┆
0x31600…31700 (49, 0, 6) Sector 3107ff00212841 ┆1 !(Ang or writing on the VDU. 4.2.7.3 Data Flow The user procedures have no data of their own because they get a pointer to the memory where it can fetch data and where to put them when they are converted. If, however, the procedures need a dataa┆
0x31700…31800 (49, 0, 7) Sector 3008ef00212841 ┆0 o !(Area for calculation, they can use the memory management for allocating working space, though it is important that the memory used is released before exit. 4.2.7.4 USPR Module Specification 4.2.7.4.1 VUP SYNTAX Specification Module Specific┆
0x31800…31900 (49, 0, 8) Sector 3109ff00212841 ┆1 !(A 1 4.3 MEMORY LAYOUT As a basis for calculation the following figures are used: DIVCO COROUTINE 8 Modules x 0,125 K 1,0 11 Procedures x 0,025 K 0,275 1,275 UFCO CORO┆
0x31900…31a00 (49, 0, 9) Sector 310aff00212841 ┆1 !(AUTINE 11 Modules x 0,175 K 1,925 33 Procedures 0,050 K 1,65 3,575 VDIA COROUTINE 7 Modules x 0,175 K 1,225 24 Procedures 0,050K 1,2 2,425 RERT COROUTINE 1 Module x 0,30 OK 0,300 0,3 TOTAL ┆
0x31a00…31b00 (49, 0, 10) Sector 310bff00212841 ┆1 !(A7,575 statements Thus 1 Source statement equal 2 words and Data Area is estimated to 3 K Words the Memdory turns to be: 7,575 K Words x 2 + 3 K Words = 18,15 Words UMAM PROCESS 18 Modules x 0,150 2,700 30 Procedures x 0,030 0,900 ┆
0x31b00…31c00 (49, 0, 11) Sector 310c3600212841 ┆1 6 !(A 3,600 statements UMAM data are = 6,0 KW PROCESS START CASE RO OF STARTUP ACTIVE TYPE: DEAD1? -START UP: =START DEAD2? -START UP: =START COLD? -START UP: =START WARM1? -START UP: =RESTART WARM2? -START UP┆
0x31c00…31d00 (49, 0, 12) Sector 310dff00212841 ┆1 !(A 1 4.2.7 User Procedures Subpackage 4.2.7.1 Functional Specification The USPR subpackage contains all validation and conversion procedures needed to validate, store and display th┆
0x31d00…31e00 (49, 0, 13) Sector 310eff00212841 ┆1 !(Ae data in the users formats. During output of data to the formats the display procedures are used to convert data from internal representation to strings which can be displayed on the VDU. During input syntax and semantic procedures are used to ┆
0x31e00…31f00 (49, 0, 14) Sector 310fff00212841 ┆1 !(Avalidate the contents of the fileds which are read from the VDU. If an error is detected, an error will be generated and the filed containing the error will be inverted, else the filed will be converted to internal representation and stored in a CIF┆
0x31f00…32000 (49, 0, 15) Sector 3100ff00212841 ┆1 !(A or a memory record. The action performed is selected by interpreting the Format Control Program which contains a reference (case label) of the procedure, which is able to validate or display the specific field. 4.2.7.1.1 Display Procedures T┆
0x32000…32100 (50, 0, 0) Sector 3201ff00212841 ┆2 !(A 1 4.2.6.4.2 VUP SUBPROCESS INIT Specification 4.2.6.4.2.1 Functional Specification This module interprets the start up parameters, initialises the user coroutines, semaphores and┆
0x32100…32200 (50, 0, 1) Sector 3202ff00212841 ┆2 !(A operations, and starts VCO. 4.2.6.4.2.2 Module Interface Call Specification a) USER SUBPROCESS INIT b) VUP COPSY INI R0: START MODE R1: SUBPROCESS ID R2: SUBPROCESS NO R6: LINK Register Convention Call Registers R0 ST┆
0x32200…32300 (50, 0, 2) Sector 3203b000212841 ┆2 0 !(AART TYPE R1 SUBPROCESS ID R6 LINK DESTROYED R2 SUBPROCESS NO Return Registers R0 - R7 DESTROYED Fatal Errors NONE 4.2.6.4.2.3 Module Components N/A ure is shown on fig. 4.2.6.2-1. The initialisation subpackage contains 2 module┆
0x32300…32400 (50, 0, 3) Sector 3204ff00212841 ┆2 !(A 1 4.2.6.4.2.4 Data Description a)Data References Refer source listings. b) External Data Refer source listings. c) Local Data N/A 4.2.6.4.2.5 Module Design This mo┆
0x32400…32500 (50, 0, 4) Sector 3205ff00212841 ┆2 !(Adule interpret the start up type and initialises the coroutines: -UFCO -VDIA -RETR by call to Coroutine Monitor, initialises the semaphores: -VUS S1 -VUS S2 -VUS S3 -RETR SEM -SPLIT SEM by call to Coroutine Monitor and initialises the┆
0x32500…32600 (50, 0, 5) Sector 32067700212841 ┆2 w !(A operations: -RETR OP -NOT OP -ANQ OP -FC KEY OP -VDU OP -SEM OP (1..4) by call to Coroutine Monitor n of the operations. d) Starts VCO 4.2.6.5 Common Subpackage Data ............. 4.2.6.6 Common Subpackage Procedu┆
0x32600…32700 (50, 0, 6) Sector 3207ff00212841 ┆2 !(A 1 4.2.6.5 Common Subpackage Data None. 4.2.6.6 Common Subpackage Procedures N/A 4.2.6.7 Subpackage Interfaces The initialisation subpackage call VCO direct (by procedure┆
0x32700…32800 (50, 0, 7) Sector 31087e00212841 ┆1 ~ !(A call). All other coroutines are called via Coroutine Monitor and will all end up waiting in their waiting points. lisation Subpackage The mainmodule Process Start calls upon module VUP COPSY INI. 4.2.6.4 VUS Initialisation Module Specific┆
0x32800…32900 (50, 0, 8) Sector 3209ff00212841 ┆2 !(Aation 4.2.6.4.1 PROCESS START Specification 4.2.6.4.1.1 Functional Specification This module acts only as a mainmodule and makes the call to the actual INITMODULE after preinitialization. This file is intended for COPSY environment. To be ┆
0x32900…32a00 (50, 0, 9) Sector 320ae600212841 ┆2 f !(Alinked with file VUP COP INI.L. 4.2.6.4.1.2 Module Interface N/A 4.2.6.4.1.3 Module Components N/A 4.2.6.4.1.4 Data Description a) Data References N/A b) External Data N/A c) Local Data N/A 4.2.7.4.3 DISPLA┆
0x32a00…32b00 (50, 0, 10) Sector 320bc100212841 ┆2 A !(A 1 4.2.6.4.1.5 Module Design Two calls are performed. One upon PRE INITIALIZATION and one upon VUP SUBPROCESS INIT. *$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x32b00…32c00 (50, 0, 11) Sector 320cff00212841 ┆2 !(A 1 PROCESS START CASE RO OF STARTUP ACTIVE TYPE: DEAD1? -START UP: =START DEAD2? -START UP: =START COLD? -START UP: =START WARM1? -START UP: =RESTART WARM2? -START UP┆
0x32c00…32d00 (50, 0, 12) Sector 320dff00212841 ┆2 !(A: =RESTART OTHERWISE? VUS INTERNAL ERROR(GIVE UP)(4.1.5.2) END CASE USER SUBP ID =R2 MDCO SUBP ID =R3 MSO SUBP ID =R4 INIT COMMON (VCO REC,VCO PRIO,USER SUBP ID,VCO ID):OK USER MDCO MSO SW INIT (4.2.6.4.1-2) VCO(4.2.1.4.1) END MO┆
0x32d00…32e00 (50, 0, 13) Sector 320e2c00212841 ┆2 , !(ADULE Fig. 4.2.6.4.15-1 MSO VDU Software Initialisation. (4.0) .......................... 4.2.6.2 Software Structure ................. 4.2.6.2.1 Process Start (1.0) ............ 4.2.6.2.2 US┆
0x32e00…32f00 (50, 0, 14) Sector 320fff00212841 ┆2 !(A 1 USER MDCO MSO SW INIT USER SUBP ID EQ 0? USER SUBPROCESS INIT (4.2.6.4.2) MDCO SUBP ID EQ 0? MDCO SUBPROCESS INIT (4.2.6.4.3) MSO SUBP ID EQ 0? MSO SUBPROCESS INIT (4.┆
0x32f00…33000 (50, 0, 15) Sector 32004100212841 ┆2 A !(A2.6.4.4) END Fig. 4.2.6.4.1-2 4.2.6.1.1 VUS Initialization (1.0) - Executes pre-initialization. 4.2.6.1.2 USER VDU Software Initialisation(2.0) a) Coroutine Monitor Initialisation (2.1) Performs initialis┆
0x33000…33100 (51, 0, 0) Sector 3301ff00212841 ┆3 !(Aation of the Coroutine Monitor Data Structure by a call to Coroutine Monitor.(VCO is also initialised by this call) b) User Coroutine Initialisation (2.2) Performs initialisation of the 3 remaining VUS coroutines by call to Coroutine Monitor. ┆
0x33100…33200 (51, 0, 1) Sector 3302ff00212841 ┆3 !(A c) User Semaphore Initialisation (2.3) Performs initialisation of the 5 VUS semaphores by call to Coroutine Monitor. d) User Operation Initialisation (2.4) Performs initialisation of the 9 VUS operations by call to Coroutine Monitor. e) St┆
0x33200…33300 (51, 0, 2) Sector 3303ff00212841 ┆3 !(Aart VCO (2.5) Performs start of VCO (VCO is initialised when Coroutine Monitor is initialised but it is not started) 4.2.6.2 Software Structure The Software Structure is shown on fig. 4.2.6.2-1. The initialisation subpackage contains 2 module┆
0x33300…33400 (51, 0, 3) Sector 33048500212841 ┆3 !(As. 4.2.6.2.1 Process Start (1.0) This Module is a mainmdule and calls upon PRE INITIALISATION and VUP SUBPROCESS INIT. 4.2.6.4.4.1\Functional Specification ... 4.2.6.4.4.2 Module Interface ........... 4.2.6.4.4┆
0x33400…33500 (51, 0, 4) Sector 3305ff00212841 ┆3 !(A 1 4.2.6.2.2 VUP Subprocess Init (2.0) This Module containes the functions: a) USER Coroutine Init (2.1) that performs initialisation of the 4 coroutines. b) USER Semaphore Init ┆
0x33500…33600 (51, 0, 5) Sector 33069e00212841 ┆3 !(A(2.2) that performs initialisation of the Semaphores. c) USER Operations Init (2.3) that performs initialisation of the operations. d) Starts VCO 4.2.6.5 Common Subpackage Data ............. 4.2.6.6 Common Subpackage Procedu┆
0x33600…33700 (51, 0, 6) Sector 33079e00212841 ┆3 !(A 1 FIGURE 4.2.6.2-2 SOFTWARE STRUCTURE ecification ........... 4.2.7.1.1 Display Procedures ............. 4.2.7.1.2 ┆
0x33700…33800 (51, 0, 7) Sector 3208ff00212841 ┆2 !(A 1 4.2.6.3 Dataflow and Control Logic within VUS Initialisation Subpackage The mainmodule Process Start calls upon module VUP COPSY INI. 4.2.6.4 VUS Initialisation Module Specific┆
0x33800…33900 (51, 0, 8) Sector 3309ff00212841 ┆3 !(A 4.2.7.4.1 VUP SYNTAX Specification ....... 4.2.7.4.1.1 Functional Specification ... 4.2.7.4.1.2 Module Interface ........... 4.2.7.4.1.3 Module Components .......... 4.2.7.4.1.4 Software Design .┆
0x33900…33a00 (51, 0, 9) Sector 330aff00212841 ┆3 !(A........... 4.2.7.4.2 SEMAN VAL Specification ........ 4.2.7.4.2.1 Functional Specification ... 4.2.7.4.2.2 Module Interface ........... 4.2.7.4.2.3 Module Components .......... 4.2.7.4.3 DISPLA┆
0x33a00…33b00 (51, 0, 10) Sector 330bc200212841 ┆3 B !(AY FIELD Specification ... 4.2.7.4.3.1 Functional Specification ... 4.2.7.4.3.2 Module Interface ........... 4.2.7.4.3.3 Module Components .......... *$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x33b00…33c00 (51, 0, 11) Sector 330cff00212841 ┆3 !(A 1 4.2.6 VUS Initialisation Subpackage This subpackage performs interpretation of start up information delivered by SSC in the registers when the process is started. The coroutines ┆
0x33c00…33d00 (51, 0, 12) Sector 330dff00212841 ┆3 !(Aconstituting the VDU User Software are initialised. 4.2.6.1 Functional Specification The subpackage contains the following functions: - Interpretation of start up information - Initialisation of VUS Coroutines Fig. 4.2.6.1-1 presents the f┆
0x33d00…33e00 (51, 0, 13) Sector 330e1b00212841 ┆3 !(Aunctional breakdown. 4.2.6.1.4 MSO VDU Software Initialisation. (4.0) .......................... 4.2.6.2 Software Structure ................. 4.2.6.2.1 Process Start (1.0) ............ 4.2.6.2.2 US┆
0x33e00…33f00 (51, 0, 14) Sector 330f8600212841 ┆3 !(A 1 Fig. 4.2.6.1-1 within. VUS Initialisation Subpackage..... 4.2.6.4 VUS Initialisation Module Specifi cat┆
0x33f00…34000 (51, 0, 15) Sector 3300ff00212841 ┆3 !(A 1 4.2.6.1.1 VUS Initialization (1.0) - Executes pre-initialization. 4.2.6.1.2 USER VDU Software Initialisation(2.0) a) Coroutine Monitor Initialisation (2.1) Performs initialis┆
0x34000…34100 (52, 0, 0) Sector 3401ff00212841 ┆4 !(A 4.2.6.4.1.4 Data Description ........... 4.2.6.4.1.5 Module Design .............. 4.2.6.4.2 USER SUBPROCESS INIT Specifica.. tion............................ 4.2.6.4.2.1 Functional Specification .┆
0x34100…34200 (52, 0, 1) Sector 3402ff00212841 ┆4 !(A.. 4.2.6.4.2.2 Module Interface ........... 4.2.6.4.2.3 Module Components .......... 4.2.6.4.2.4 Data Description ........... 4.2.6.4.2.5 Module Design .............. 4.2.6.4.3 MDCO SUBPROCESS I┆
0x34200…34300 (52, 0, 2) Sector 3403ff00212841 ┆4 !(ANIT Specifica- tion........................... 4.2.6.4.3.1 Functional Specification ... 4.2.6.4.3.2 Module Interface ........... 4.2.6.4.3.3 Module Components .......... 4.2.6.4.3.5 Module┆
0x34300…34400 (52, 0, 3) Sector 3404ff00212841 ┆4 !(A Design .............. 4.2.6.4.4 MSO SUBPROCESS INIT Specifica- tion............................ 4.2.6.4.4.1\Functional Specification ... 4.2.6.4.4.2 Module Interface ........... 4.2.6.4.4┆
0x34400…34500 (52, 0, 4) Sector 34059400212841 ┆4 !(A.3 Module Components .......... 4.2.6.4.4.4 Data Description ........... 4.2.6.4.4.5 Module Design .............. nder redigering nu Ukendt dokument Fundet I brug nu Allerede p> systemdiskette ┆
0x34500…34600 (52, 0, 5) Sector 3406ff00212841 ┆4 !(A 1 4.2.6.5 Common Subpackage Data ............. 4.2.6.6 Common Subpackage Procedu┆
0x34600…34700 (52, 0, 6) Sector 3407ff00212841 ┆4 !(Ares ....... 4.2.6.7 Subpackage Interfaces .............. 4.2.7 User Procedures Subpackage ............. 4.2.7.1 Functional Specification ........... 4.2.7.1.1 Display Procedures ............. 4.2.7.1.2 ┆
0x34700…34800 (52, 0, 7) Sector 3308ff00212841 ┆3 !(ASyntax Procedures .............. 4.2.7.1.3 Semantic Procedures ............ 4.2.7.2 Software Structure ................. 4.2.7.3 Data Flow .......................... 4.2.7.4 USPR Module Specification .......... ┆
0x34800…34900 (52, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(52,0, 9), len=0xff, h3=41212841}, f00=»2128A «, f01=»CPS/SDS/039 «, f02=»ja «, f03=»JBS «, f04=»4.2.6. «, f05=03-05-82 18:29, f06=» 4 «, f07=»02 «, f08=» 15677 «, f09=27-05-82 15:22, f10=» 8 «, f11=»24 «, f12=» 17171 «, f13=25-04-84 11:30, f14=26-04-84 16:54, f15=»0170A «, f16=» 37 «, f17=» 13 «, f18=»48 «, f19=» 564 «, f20=» 35641 «, f21=» «, f22=» «, f99=020000000110052710110380aa8a37040000000000000142039b00df}
0x34900…34a00 (52, 0, 9) Sector 340a2500212841 ┆4 % !(A 4 4 4 3 3 3 3 3 3 2 2 2 2 2 2 1 1 1 0 0 0 / / DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarererererere┆
0x34a00…34b00 (52, 0, 10) Sector 340ba300212841 ┆4 # !(A 1 CPS/SDS/039 840601 USER VDU DETAILED DESIGN SPECIFICATION ISSUE 1 CAMPS -!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x34b00…34c00 (52, 0, 11) Sector 340cff00212841 ┆4 !(A 1 1 4.2.6 VUS Initialis┆
0x34c00…34d00 (52, 0, 12) Sector 340dff00212841 ┆4 !(Aation Subpackage........... 4.2.6.1 Functional Specification ........... 4.2.6.1.1 Start up Information Interpretation ................ 4.2.6.1.3 MDCO VDU Software Initialisation (3.0)..........┆
0x34d00…34e00 (52, 0, 13) Sector 340eff00212841 ┆4 !(A................. 4.2.6.1.4 MSO VDU Software Initialisation. (4.0) .......................... 4.2.6.2 Software Structure ................. 4.2.6.2.1 Process Start (1.0) ............ 4.2.6.2.2 US┆
0x34e00…34f00 (52, 0, 14) Sector 340fff00212841 ┆4 !(AER Subprocess Init (2.0) ..... 4.2.6.2.3 MSO Subprocess Init (4.0) ...... 4.2.6.3 Dataflow and Control Logic within. VUS Initialisation Subpackage..... 4.2.6.4 VUS Initialisation Module Specifi cat┆
0x34f00…35000 (52, 0, 15) Sector 3400ff00212841 ┆4 !(Aions............................. 4.2.6.4.1 PROCESS START Specification .... 4.2.6.4.1.1 Functional Specification ... 4.2.6.4.1.2 Module Interface ........... 4.2.6.4.1.3 Module Components ......... ┆
0x35000…35100 (53, 0, 0) Sector 35018600213341 ┆5 !3A REMOVE USER CONNECTION(4.2.1.6.2) VCO CONTROL(VDU FAILURE)(4.2.1.4.1) Figure 4.2.1.6.4-1 gure 4.2.1.6.2-1 ┆
0x35100…35200 (53, 0, 1) Sector 3502ff00213341 ┆5 !3A 1 4.2.1.6.5 SEARCH FLASH QUEUES 4.2.1.6.5.1 Functional Specification This procedure reads the length of the Super Flash Subqueues and Flash Subqueues of the RELEASE QUEUE and REC┆
0x35200…35300 (53, 0, 2) Sector 3503cb00213341 ┆5 K !3AEIVE QUEUE and returns to the ITEM label if any flash item is found. 4.2.1.6.5.2 Interface Definition Call Specification a) SEARCH FLASH QUEUES ( ): EMPTY ITEM b) SEARCH FLASH QUEUES (R6) 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x35300…35400 (53, 0, 3) Sector 3504b900213341 ┆5 9 !3A 1 Register Convention Call Registers R6 LINK DEST Return Registers R0 - R7 DEST Fatal Errors Noneear the header split of the VDU. 4.2.1.6.3.2 Interface Definition ┆
0x35400…35500 (53, 0, 4) Sector 3505ff00213341 ┆5 !3A 1 4.2.1.6.5.3 Data Description a) Data References PRECEDENCE TYPE refer CPS/DBD/001 EMPTY ITEM refer 4.2.1.5 External Data VUS RECVQ refer 4.1.4 VUS RELSQ refer 4.1.4 ┆
0x35500…35600 (53, 0, 5) Sector 35065c00213341 ┆5 \ !3A c) Local Data None 4.2.1.6.5.4 Procedure Design Refer figure 4.2.1.6.5-1 ta Description a) Data References SEND CONTROL COMMAND refer CPS/DBD/001 b) External Data HEADER IFCB refer 4.1.4 c) Local Data None 4.2.1.6.3.4 ┆
0x35600…35700 (53, 0, 6) Sector 3507ff00213341 ┆5 !3A 1 SEARCH FLASH QUEUE GET QLENGTH (VUS RECVQ, FLASH)(LENGTH)(4.2.1.6.10) LENGTH NE 0 ? GET QLENGTH (VUS RELSQ, FLASH)(LENGTH)(4.2.1.6.10) LENGTH NE 0 ? GET QLENGTH (VUS RECVQ, SUP┆
0x35700…35800 (53, 0, 7) Sector 3408d700213341 ┆4 W !3AERFLASH)(LENGTH)(4.2.1.6.10) LENGTH NE 0 ? GET QLENGTH (VUS RELSQ, SUPERFLASH)(LENGTH)(4.2.1.6.10) LENGTH NE 0 ? RETURN (EMPTY) RETURN (ITEM) Figure 4.2.1.6.5-1 AILED): (LA1) ┆
0x35800…35900 (53, 0, 8) Sector 35095000213341 ┆5 P !3A LA1? END CASE OK? END CASE Figure 4.2.1.6.3-1 a) Data References IDENT ID TYPE refer 4.1.4 VCO CMD refer 4.1.4 QELEMENT MAIN TYPE refer CPS/DBD/001 ACK SUBTYPE refer CPS/DBD/001 SSC REPLY TYPE refer 4.2.1.5 ! ┆
0x35900…35a00 (53, 0, 9) Sector 350aff00213341 ┆5 !3A 1 4.2.1.6.4 SPLIT FAILURE 4.2.1.6.4.1 Functional Description This procedure is called when a VDU SPLIT FAILED completion code is returned from the Format Handler. The fol┆
0x35a00…35b00 (53, 0, 10) Sector 350bbe00213341 ┆5 > !3Alowing actions are taken: - Periodic timeouts are cancelled - A reply is sent to SSC if required and the QEL is dismantled if DISM is true - The VCO CONTROL module is called ┆
0x35b00…35c00 (53, 0, 11) Sector 350cff00213341 ┆5 !3A 1 4.2.1.6.4.2 Interface Definition Call Specification a) SPLIT FAILURE(CALLER: FAIL CALLER/DISM: BOOLEAN) b) SPLIT FAILURE(R4, R5, R6) Register Convention Call Regi┆
0x35c00…35d00 (53, 0, 12) Sector 350d6a00213341 ┆5 j !3Asters R4 DISM DEST R5 CALLER DEST R6 LINK DEST Return Registers None R0-R7 DESTSE OTHERWISE? - VUS INTERNAL ERROR(GIVE UP)(4.1.5.2) END CASE VUS SEND PARAMS.FLAG = VUS OP.PARA1 VUS SEND PARAMS.SUBTYPE = TEP ACK VUS ┆
0x35d00…35e00 (53, 0, 13) Sector 350eff00213341 ┆5 !3A 1 4.2.1.6.4.3 Data Description a) Data References VUS TIMER ENENTS refer 4.2.1.5 FAIL CALLER refer 4.2.1.5 SVCO CALLER refer 4.1.4 b) External Data CMD QEL(m) ┆
0x35e00…35f00 (53, 0, 14) Sector 350f8500213341 ┆5 !3Arefer 4.2.1.5 VUS QEL ATTR refer 4.1.4 c) Local Data None 4.2.1.6.4.4 Procedure Design Refer figure 4.2.1.6.4-1al Description This procedure closes the interface to the terminal. 4.2.1.6.2.2 Interface Definition Call Specific┆
0x35f00…36000 (53, 0, 15) Sector 3500ff00213341 ┆5 !3A 1 SPLIT FAILURE CALLER EQ SSC START? SSC REPLY(OP FAIL, NIL)(4.2.1.6.1) DISM EQ TRUE? VUS DISMANTLE(CMD QEL)(4.1.5.3) CANCEL PENDING TIMEOUT(S PERIODIC)(4.2.1.6.3) ┆
0x36000…36100 (54, 0, 0) Sector 36019600213341 ┆6 !3Aata HEADER IFCB refer 4.1.4 FORMAT IFCB refer 4.1.4 c) Local Data None 4.2.1.6.2.4 Procedure Design Refer figure 4.2.1.6.2-1 ┆
0x36100…36200 (54, 0, 1) Sector 3602ff00213341 ┆6 !3A 1 REMOVE USER CONNECTION CASE REMOVE TERMINAL(FORMAT IFCB)(CC): ERROR OK ERROR? ANALYZE ERROR(CC,0) OK? END CASE CASE REMOVE TERMINAL(HEADER IFCB)(CC): ERROR OK ER┆
0x36200…36300 (54, 0, 2) Sector 36035e00213341 ┆6 ^ !3AROR? ANALYZE ERROR(CC,0) OK? END CASE Figure 4.2.1.6.2-1 JBS/820505 USER VDU DETAILED DESIGN SPECIFICATION CAMPS WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x36300…36400 (54, 0, 3) Sector 3604ff00213341 ┆6 !3A 1 4.2.1.6.3 CLEAR HEADER SPLIT 4.2.1.6.3.1 Functional Description The purpose of this procedure is to clear the header split of the VDU. 4.2.1.6.3.2 Interface Definition ┆
0x36400…36500 (54, 0, 4) Sector 3605a900213341 ┆6 ) !3A Call Specification a) CLEAR HD SPLIT b) CLEAR HD SPLIT(R6) Register Convention Call Registers R6 LINK DEST Return Registers None R0-R7 DEST RELS INVERT, RECV INVERT, TIME OUT OUTSTANDING: BOOLEAN; S REQUEST TIME: REQUE┆
0x36500…36600 (54, 0, 5) Sector 3606ff00213341 ┆6 !3A 1 4.2.1.6.3.3 Data Description a) Data References SEND CONTROL COMMAND refer CPS/DBD/001 b) External Data HEADER IFCB refer 4.1.4 c) Local Data None 4.2.1.6.3.4 ┆
0x36600…36700 (54, 0, 6) Sector 36073100213341 ┆6 1 !3AProcedure Design Refer figure 4.2.1.6.3-1 4.2.1.6 Common Subpackage Procedure 4.2.1.6.1 SSC REPLY 4.2.1.6.1.1 Functional Description An acknowledge telling the result of a SSC-command is returned to the SSC. 4.2.┆
0x36700…36800 (54, 0, 7) Sector 3508ff00213341 ┆5 !3A 1 CLEAR HD SPLIT CASE SEND CONTROL(HEADER IFCB, CLEAR THE SPLIT) (CC): ERROR OK ERROR? CASE ANALYZE ERROR(CC, 1, VDU SPLIT FAILED): (LA1) ┆
0x36800…36900 (54, 0, 8) Sector 3609fd00213341 ┆6 } !3A Return Registers None R0-R7 DEST 4.2.1.6.1.3 Data Description a) Data References IDENT ID TYPE refer 4.1.4 VCO CMD refer 4.1.4 QELEMENT MAIN TYPE refer CPS/DBD/001 ACK SUBTYPE refer CPS/DBD/001 SSC REPLY TYPE refer 4.2.1.5 ! ┆
0x36900…36a00 (54, 0, 9) Sector 360aff00213341 ┆6 !3A 1 b) External Data VUS SEND PARAMS (m) refer 4.1.4 CMD QEL refer 4.2.1.5 VUS OP refer 4.1.4 c) Local Data CONST EXE NOK = 1; 4.2.1.6.1.4 Procedure Design Refer┆
0x36a00…36b00 (54, 0, 10) Sector 360b1b00213341 ┆6 !3A figure 4.2.1.6.1-1 5Cq5MB' R*5Cq5M[2 R45Cq5M 2M[- RA5Cq5:^=~ BL5C`5M{) RV5Cq5M . R`5Cq5M@1MI1:h= Rp5Cr4IMM.:^=~ B}5I:g=~ J 5IC$3I > S C_* ┆
0x36b00…36c00 (54, 0, 11) Sector 360cff00213341 ┆6 !3A 1 SSC REPLY OP FAILURE EQ OP FAIL? VUS SEND PARAMS.FLAG = EXE NOK CASE VUS OP.ID OF IDENT ID TYPE UFCO ID? CASE VUS OP.CMD OF VCO CMD START UFCO, CLOSE UFC┆
0x36c00…36d00 (54, 0, 12) Sector 360dff00213341 ┆6 !3AO, STOP UFCO, BLOCK UFCO? OTHERWISE?VUS INTERNAL ERROR(GIVE UP)(4.1.5.2) END CASE OTHERWISE? - VUS INTERNAL ERROR(GIVE UP)(4.1.5.2) END CASE VUS SEND PARAMS.FLAG = VUS OP.PARA1 VUS SEND PARAMS.SUBTYPE = TEP ACK VUS ┆
0x36d00…36e00 (54, 0, 13) Sector 360ec800213341 ┆6 H !3ASEND PARAMS.MAINTYPE = ACK CASE SEND REPLY(VUS SEND PARAMS, NIL, CMD QEL) (VUS SEND PARAMS, CC): ERROR OK ERROR? ANALYZE ERROR(CC, 0) OK? END CASE Figure 4.2.1.6.1-1 es, semaphores and operations. 4.2.6.4.4.2 Module I┆
0x36e00…36f00 (54, 0, 14) Sector 360fff00213341 ┆6 !3A 1 4.2.1.6.2 REMOVE USER CONNECTION 4.2.1.6.2.1 Functional Description This procedure closes the interface to the terminal. 4.2.1.6.2.2 Interface Definition Call Specific┆
0x36f00…37000 (54, 0, 15) Sector 3600ff00213341 ┆6 !3Aation a) REMOVE USER CONNECTION b) REMOVE USER CONNECTION (R6) Register Conventions Call Registers R6 LINK DEST Return Registers None R0-R7 DEST 4.2.1.6.2.3 Data Description a) Data References None b) External D┆
0x37000…37100 (55, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(55,0, 1), len=0xff, h3=41213341}, f00=»2133A «, f01=»CPS/SDS/039 «, f02=»bk «, f03=»JBS «, f04=»4.2.1.5 «, f05=05-05-82 09:22, f06=» 3 «, f07=»56 «, f08=» 6704 «, f09=17-05-82 15:39, f10=» «, f11=»02 «, f12=» 37 «, f13=18-05-82 08:21, f14=18-05-82 08:48, f15=»0170A «, f16=» 34 «, f17=» 4 «, f18=»49 «, f19=» 240 «, f20=» 8288 «, f21=» «, f22=» «, f99=100010000110052710110290aaca15050000000000000042035400df}
0x37100…37200 (55, 0, 1) Sector 37022200213341 ┆7 " !3A 7 7 7 6 6 6 6 6 6 6 5 5 5 5 5 5 5 5 4 4 4 4 4 4 4 3 3 3 3 3 3 2 2 2 2 DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG Oprettet / / : : S┆
0x37200…37300 (55, 0, 2) Sector 3703a000213341 ┆7 !3A 1 CPS/SDS/039 JBS/820505 USER VDU DETAILED DESIGN SPECIFICATION CAMPS WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x37300…37400 (55, 0, 3) Sector 3704ff00213341 ┆7 !3A 1 4.2.1.5 Common Subpackage Data a) Data References QELEMENT REFERENCE refer CPS/DBD/001 REQUEST TIME RELATIV refer CPS/DBD/001 b) Common Types SSC REPLY TYPE = (NO FAIL,OP┆
0x37400…37500 (55, 0, 4) Sector 3705ff00213341 ┆7 !3A FAIL); VUS TIMER ENENTS = (S PERIODIC, S FLASH); EMPTY ITEM = (EMPTY,ITEM); FAIL CALLER = (SSC START, c) Common Constants None d) Common Variables RELS INVERT, RECV INVERT, TIME OUT OUTSTANDING: BOOLEAN; S REQUEST TIME: REQUE┆
0x37500…37600 (55, 0, 5) Sector 37064500213341 ┆7 E !3AST TIME RELATIV CMD QEL: QEL REFERENCE; CUR FQT: INTEGER;<6 +6L!&<6 :$<~ JY0*.;:i=>Jf0C.1:.= Rp0C%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<┆
0x37600…37700 (55, 0, 6) Sector 3707ff00213341 ┆7 !3A 1 4.2.1.6 Common Subpackage Procedure 4.2.1.6.1 SSC REPLY 4.2.1.6.1.1 Functional Description An acknowledge telling the result of a SSC-command is returned to the SSC. 4.2.┆
0x37700…37800 (55, 0, 7) Sector 3608ff00213341 ┆6 !3A1.6.1.2 Interface Definition Call Specification a) SSC REPLY(VUS OP: VUS CO OP; OP FAILURE: SSC REPLY TYPE) b) SSC REPLY(R4, R5, R6) Register Convention Call Register R4 OP FAILURE DEST R5 pointer to VUS OP DEST R6 LINK DEST ┆
0x37800…37900 (55, 0, 8) Sector 3709ff00155341 ┆7 SA 1 4.1.2.3.4 VDIA Coroutine Software Structure This coroutine performs input / output to and from the format area of the VDU and validation and storage of input. It accepts comman┆
0x37900…37a00 (55, 0, 9) Sector 370aff00155341 ┆7 SAds from UFCO and sends completion report corresponding to these commands. It communicates with the VDU via the Format Handler of the IOC Package and accesses data in the Internal Message Format (IMF) via the Message Monitor of the CSF Package. F┆
0x37a00…37b00 (55, 0, 10) Sector 370b3500155341 ┆7 5 SAig. 4.1.2.3-5 shows the software structure. status types exist. e) The centralization of status maintenance and PDB access control for all VDU processes in one process, increases the flexibility of the system. 4.1.2.3 Software Structure I┆
0x37b00…37c00 (55, 0, 11) Sector 370c8900155341 ┆7 SA 1 FIGURE 4.1.2.3-5 VDIA COROUTINE - SOFTWARE STRUCTURE rmed by these software components identified. age is kept longer in a Flash precedence queue than allowed by the supe┆
0x37c00…37d00 (55, 0, 12) Sector 370dff00155341 ┆7 SA 1 4.1.2.3.5 RETR Coroutine Software Structure This coroutine receives input from SAR via the Retrieve Queue and communicates with UFCO. This communication is done either by RETR s┆
0x37d00…37e00 (55, 0, 13) Sector 370ea700155341 ┆7 ' SAending Online Retrieval Results direct to UFCO or Off-line Retrieval Results indirectly via the Response Queue. Fig. 4.1.2.3-6 shows the software structure. subsections. The description of the software structure will mainly be in the form of so┆
0x37e00…37f00 (55, 0, 14) Sector 370f8400155341 ┆7 SA 1 Fig. 4.1.2.3-6 RETR COROUTINE - SOFTWARE STRUCTURE re Structure This subpackage contains the software which initializes the coroutines and semaphores of the VUS, MSOS and M┆
0x37f00…38000 (55, 0, 15) Sector 2d00f300155341 ┆- s SA 1 4.1.2.3.6 UMAM Software Structure This processs receives input from other packages in the Collect and Command Queues. Figure 4.1.2.3-7 shows the software structure. f the VDU-he┆
0x38000…38100 (56, 0, 0) Sector 38019300155341 ┆8 SAader is performed by VCO. The software structure of the VDU Control Coroutine (VCO) is outlined in the structure chart in fig. 4.1.2.3-3. gress, UFCO software shall only take care of transaction interruption while all formatting and I/O transfer ┆
0x38100…38200 (56, 0, 1) Sector 38028400155341 ┆8 SA 1 Fig. 4.1.2.3-1 Software Structure Process Overview. e The VDU dialogue (VDIA) coroutine is responsible for the VDU format transformation of input and output and for validati┆
0x38200…38300 (56, 0, 2) Sector 38038500155341 ┆8 SA 1 Fig. 4.1.2.3-2 VUS INITIALIZATION - SOFTWARE STRUCTURE of retrieval answers from SAR. The functions of RETR have been assigned to a separate coroutine, due to the fact that t┆
0x38300…38400 (56, 0, 3) Sector 38048400155341 ┆8 SA 1 Fig. 4.1.2.3-3 VCO COROUTINE - SOFTWARE STRUCTURE f the RETR may be considered as low priority tasks, having in mind that during on-line retrieval all the other coroutines a┆
0x38400…38500 (56, 0, 4) Sector 3805ff00155341 ┆8 SA 1 4.1.2.3.3 UFCO Coroutine Software Structure This coroutine controls input / output to and from the VDU and the communication with other packages. It accepts commands from VCO an┆
0x38500…38600 (56, 0, 5) Sector 3806ff00155341 ┆8 SAd control VDIA via commands and process completion reports from VDIA corresponding to the commands. It communicates with VCO by sending completion report corresponding to commands received by VCO. The control of the MMI is exercised via function┆
0x38600…38700 (56, 0, 6) Sector 3807bd00155341 ┆8 = SA key interrupts received from the VDU, via execution of commands entered from the VDU and via input / output commands sent to VDIA. Fig. 4.1.2.3-4 shows the software structure. llowing reasons: a) To keep security access control as simple an┆
0x38700…38800 (56, 0, 7) Sector 37087e00155341 ┆7 ~ SA 1 Fig. 4.1.2.3-4 UFCO COROUTINE - SOFTWARE STRUCTURE .1 this means that the solution where the releaser process queues a request for removing or changing items is not chosen. Note th┆
0x38800…38900 (56, 0, 8) Sector 3809ff00155341 ┆8 SAat due to security, it is our aim that a user process should not be trusted, meaning that access rights possessed by an unassigned user process (no user has signed on) shall be kept at a minimum. c) The close relationship between Preparation Datab┆
0x38900…38a00 (56, 0, 9) Sector 380aff00155341 ┆8 SAase Access Control and Message / Comment Status Maintenance has caused both functions to be allocated to the same process. d) The allocation of one process to Status Maintenance gives the designer the freedom to optimize disk-accesses and to utili┆
0x38a00…38b00 (56, 0, 10) Sector 380bff00155341 ┆8 SAze the fact that identical entries in different status types exist. e) The centralization of status maintenance and PDB access control for all VDU processes in one process, increases the flexibility of the system. 4.1.2.3 Software Structure I┆
0x38b00…38c00 (56, 0, 11) Sector 380cb800155341 ┆8 8 SAn the preceding subsections of section 4.1.2, the processes and coroutines of VUP have been isolated, and the functions to be performed by these software components identified. age is kept longer in a Flash precedence queue than allowed by the supe┆
0x38c00…38d00 (56, 0, 12) Sector 380d6400155341 ┆8 d SA 1 FIGURE 4.1.2.1-2enance functions were to be executed with higher priority than User Transaction Control Functions. Thus these two functions have been allocated their own c┆
0x38d00…38e00 (56, 0, 13) Sector 380eff00155341 ┆8 SA 1 The software structure for each component (i.e. coroutine) will be outlined in the following subsections. The description of the software structure will mainly be in the form of so┆
0x38e00…38f00 (56, 0, 14) Sector 380fff00155341 ┆8 SAftware structure charts. In figure 4.1.2.3-1 an overview of the VUP processes is shown. 4.1.2.3.1 VUS INITIALIZATION Software Structure This subpackage contains the software which initializes the coroutines and semaphores of the VUS, MSOS and M┆
0x38f00…39000 (56, 0, 15) Sector 3800ff00155341 ┆8 SADOS subprocesses. The software structure is shown in figure 4.1.2.3-2. 4.1.2.3.2 VCO Coroutine Software Structure This coroutine receives commands from TEMCO and starts/stops UFCO accordingly. Furthermore the periodic updating of the VDU-he┆
0x39000…39100 (57, 0, 0) Sector 3901d600214141 ┆9 V !AA 1 OPEN APPEND CIF CASE OPEN VIEW(APPEND CIF)(CC) : ERROR OK ERROR? - CASE ANALYZE ERROR(CC, 1, OPEN NOT ACCEPTED): (LA1) LA1? routine, display notification and enter┆
0x39100…39200 (57, 0, 1) Sector 0000e700214141 ┆ g !AA SEC FAILED = TRUE VUS DISMANTLE(APPEND CIF)(4.1.5.3) END CASE OK? - SEQ FORMAT = SEQ A2 SEQ CODE = SEQ START APPEND VUS SEQUENCE (4.2.2.4.10) END CASE FIG. 4.2.2.4.7-3 R5 pointer to VUS O┆
0x39200…39300 (57, 0, 2) Sector 00000000000000 ┆ ┆
[…0x5…]
0x39800…39900 (57, 0, 8) Sector 3909ff00214141 ┆9 !AARETRIEVAL ERROR? - DISPLAY ERROR MSG(VUS OP.PARA1) (4.2.2.6.4) SPLIT FAILED EQ TRUE? SEQ FORMAT = SEQ REC. NEW FORMAT SEQ CODE = SEQ SAR ERROR VUS SEQUENCE (4.2.2.4.10) QUEUE┆
0x39900…39a00 (57, 0, 9) Sector 390aff00214141 ┆9 !AA ERROR? DISPLAY ERROR MSG( )(4.2.2.6.4) SPLIT FAILED EQ TRUE? SEQ FORMAT = SEQ REC. NEW FORMAT SEQ CODE = SEQ QER VUS SEQUENCE (4.2.2.4.10) OTHERWISE? VUS INTERNAL ERROR(GIVE UP)(4.1.5.2) END C┆
0x39a00…39b00 (57, 0, 10) Sector 390b1d00214141 ┆9 !AAASE FIG. 4.2.2.4.7-1 3) ERROR CC? - CASE VUS OP.PARA 2 OF EXCEED? - SEQ CODE = SEQ EXCEED VAL ERROR? - SEQ CODE = SEQ INPUT ERROR END CASE OTHERWISE? - VUS INTERNAL ERROR┆
0x39b00…39c00 (57, 0, 11) Sector 390cff00214141 ┆9 !AA 1 CALCULATE SEQUENCE KEYS CASE VUS RECV ATTR.MAINTYPE OF MESSAGE MAIN TYPE SC PLAINDRESS? - SEQ FORMAT = E1 ABB PLAINDRESS? - CASE UFCO RETR PARAM.FLAG VALUE OF ┆
0x39c00…39d00 (57, 0, 12) Sector 390dff00214141 ┆9 !AAREADDRESSED? - SEQ FORMAT = E1 RE NON READDRESSED? - SEQ FORMAT = E1 END CASE PLAINDRESS? - CASE UPCO RETR FLAG VALUE OF CAMPS ORIG? -SEQ FORMAT = E2 NON CAMPS? - SEQ FORMAT = E1 CAMPS ORIG READ? - SEQ FORM┆
0x39d00…39e00 (57, 0, 13) Sector 390eff00214141 ┆9 !AAAT = E2 RE NON CAMPS READ? - SEQ FORMAT = E1 RE END CASE SC COMMENT? - SEQ FORMAT = SC G2 COMMENT? - SEQ FORMAT = G2 SYSTEM CATALOGUE DISPLAY? - SEQ FORMAT = SYS CAT RELEASE NOTIFICATION? - SEQ FORMAT = F OTHERWISE? - VUS I┆
0x39e00…39f00 (57, 0, 14) Sector 390fff00214141 ┆9 !AANTERNAL ERROR(GIVE UP)(4.1.5.2) END CASE CASE OPEN VIEW(INPUT CIF)(CC): ERROR OK ERROR? - CASE ANALYZE ERROR(CC, 1,OPEN NOT ACCEPTED):(LA1) LA1? SEC FAILED = TRUE VUS DISMANTLE(INPUT CIF)(4.1.5.3) END CASE OK? - SEQ CODE ┆
0x39f00…3a000 (57, 0, 15) Sector 39004b00214141 ┆9 K !AA= SEQ DISP VUS SEQUENCE(4.2.2.4.10) END CASE FIG. 4.2.2.4.7-2 nvention Call Register R5 pointer to VUS OP (DEST) R6 LINK (DEST) Return Register R0 - R7 (DEST) 4.2.2.4.6.3 Module Component None IN TYPE ┆
0x3a000…3a100 (58, 0, 0) Sector 3a01ff00214141 ┆: !AA 1 4.2.2.4.7 RETR OP PROCESSING 4.2.2.4.7.1 Functional Specification The purpose of this module is to analyse input from RETR Co- routine, display notification and enter┆
0x3a100…3a200 (58, 0, 1) Sector 3a02ff00214141 ┆: !AAing the VUS SEQUENCE module (4.2.2.4.10). 4.2.2.4.7.2 Module Interface Call Specification a) RETR OP PROCESSING (VUS OP: VUS CO OP TYPE) b) RETR OP PROCESSING (R5, R6) Register Convention Call Register R5 pointer to VUS O┆
0x3a200…3a300 (58, 0, 2) Sector 3a038600214141 ┆: !AAP (DEST) R6 LINK (DEST) Return Register None R0 - R7 (DEST) 4.2.2.4.7.3 Module Component None None 4.2.2.4.6.5 Module Design This module analyses completion code from VDIA, and in those cases where VDIA C┆
0x3a300…3a400 (58, 0, 3) Sector 3a04ff00214141 ┆: !AA 1 4.2.2.4.7.4 Data Description a) Data References MESSAGE MAIN TYPE refer CPS/DBD/001 VUS CO OP TYPE refer 4.1.4 VUS RESP MSG TYPE refer 4.1.4 RETR CMD re┆
0x3a400…3a500 (58, 0, 4) Sector 3a05ff00214141 ┆: !AAfer 4.1.4 SEQ CODE TYPE refer 4.2.2.5 SEQ FORMAT TYPE refer 4.2.2.5 b) External Data INPUT CIF (m) refer 4.1.4 SPLIT FAILED refer 4.2.2.5 SEC FAILED (m) refer 4.2.2.5 SEQ CODE (m) refer 4.2.2.5 SEQ FORMAT (┆
0x3a500…3a600 (58, 0, 5) Sector 3a06be00214141 ┆: > !AAm) refer 4.2.2.5 c) Local Data None 4.2.2.4.7.5 Module Design This module calls either DISPLAY ERROR MSG (4.2.2.6.4) and VUS SEQUENCE (4.2.2.4.10) or the latter only. DISPLAY ERROR MSG( )(4.2.2.6.4) OTHERWISE? - VUS INTERNAL┆
0x3a600…3a700 (58, 0, 6) Sector 3a07ff00214141 ┆: !AA 1 RETR OP PROCESSING CASE VUS OP. CMD OF RETR CMD ONLINE NOTIFICATION? - DISPLAY ERROR MSG( )(4.2.2.6.4) OFFLINE NOTIFICATION? - DISPLAY ERROR MSG( )(4.2.2.6.4) ┆
0x3a700…3a800 (58, 0, 7) Sector 3908ff00214141 ┆9 !AA SPLIT FAILED EQ TRUE? SEQ CODE = SEQ OFF NEW SEQ FORMAT = SEQ REC.NEW FORMAT VUS SEQUENCE (4.2.2.4.10) RETRIEVAL NOTIFICATION? - CALCULATE SEQUENCE KEYS ( -2) APPEND NOTIFICATION? - OPEN APPEND CIF (-3) ┆
0x3a800…3a900 (58, 0, 8) Sector 3a09ff00214141 ┆: !AA 1 CONTINUE VIDA CC PROCESSING CASE VUS OP. CMD OF UFCO CMD SUSP, CANCEL I O, CLOSE? CASE VUS OP. PARA1 OF CO CMD CC OK CC? VUS OP.CMD EQ CANCEL? - SEQ CODE = SEQ C┆
0x3a900…3aa00 (58, 0, 9) Sector 3a0aff00214141 ┆: !AAANCEL CC SEQ CODE = SEQ CLOSE CC SEQ FORMAT = SEQ REC. NEW FORMAT VUS SEQUENCE (4.2.2.4.10) OTHERWISE? - VUS INTERNAL ERROR(GIVE UP)(4.1.5.2) END CASE INPUT DATA? - CASE VUS OP. PARA1 OF CO CMD CC OK┆
0x3aa00…3ab00 (58, 0, 10) Sector 3a0bff00214141 ┆: !AA CC? - SET SET CODE ( -3) ERROR CC? - CASE VUS OP.PARA 2 OF EXCEED? - SEQ CODE = SEQ EXCEED VAL ERROR? - SEQ CODE = SEQ INPUT ERROR END CASE OTHERWISE? - VUS INTERNAL ERROR┆
0x3ab00…3ac00 (58, 0, 11) Sector 3a0cff00214141 ┆: !AA(GIVE UP) (4.1.5.2) END CASE ENABLE FC KEYS (4.2.2.6.33) SEQ FORMAT = SEQ REC. NEW FORMAT VUS SEQUENCE (4.2.2.4.10) OTHERWISE? - VUS INTERNAL ERROR (GIVE UP)(4.1.5.2) END CASE FIG. 4.2.2.┆
0x3ac00…3ad00 (58, 0, 12) Sector 3a0d0c00214141 ┆: !AA4.6-2 CMD CC = E USER FIG. 4.2.2.4.5.3-1 ecification a) VCO CMD PROCESSING (VUS OP: VUS CO OP TYPE):EXIT LAB b) VCO CMD PROCESSING (R5, R6) Register Convention Call Register R5 pointer to VUS OP (┆
0x3ad00…3ae00 (58, 0, 13) Sector 3a0eff00214141 ┆: !AA 1 SET SEQ CODE CASE VUS OP.PARA2 OF VDIA CC V DUMMY? - SEQ CODE = SEQ INPUT OK RETR APPEND? - SEQ CODE = SEQ RETR REQ DEFER? - SEQ CODE = SEQ DEFER RELEASE? ┆
0x3ae00…3af00 (58, 0, 14) Sector 3a0fff00214141 ┆: !AA SEQ CODE = SEQ RELEASE COORDINATE? SEQ CODE = SEQ COOR ECHO BACK? SEQ CODE = SEQ ECHO MHI REQ? SEQ CODE = SEQ MHI OTHERWISE? - VUS INTERNAL ERROR(GIVE UP) (4.1.5.2) END CASE SEQ FORMAT = SEQ REC.NEW FORMAT VUS SEQUENCE (4.2.2┆
0x3af00…3b000 (58, 0, 15) Sector 3a003000214141 ┆: 0 !AA.4.10 FIG. 4.2.2.4.6-3 NG (R5, R6) Register Convention Call Register R5 pointer to VUS OP (DEST) R6 LINK (DEST) Return Register R0 - R7 (DEST) 4.2.2.4.6.3 Module Component None IN TYPE ┆
0x3b000…3b100 (59, 0, 0) Sector 3b01ff00214141 ┆; !AA 1 4.2.2.4.6.4 Data Description a) Data References VUS CO OP TYPE refer 4.1.4 VDIA CC refer 4.1.4 IDENT TYPE refer 4.1.4 USER ACTION TYPE refer CPS/D┆
0x3b100…3b200 (59, 0, 1) Sector 3b02ff00214141 ┆; !AABD/001 UFCO CMD refer 4.1.4 VUS RESP MSG TYPE refer 4.1.4 CO CMD CC refer 4.1.4 SEQUENCE CODE TYPE refer 4.2.2.5 b) External Data UFCO OP (m) refer 4.1.4 EXP VDIA CMD (m) refer 4.2.2.5 SPLIT FAILED (m) ref┆
0x3b200…3b300 (59, 0, 2) Sector 3b03ff00214141 ┆; !AAer 4.2.2.5 SEQ REC refer 4.2.2.5 SEQ FORMAT (m) refer 4.2.2.5 SEQ CODE (m) refer 4.2.2.5 c) Local Data None 4.2.2.4.6.5 Module Design This module analyses completion code from VDIA, and in those cases where VDIA C┆
0x3b300…3b400 (59, 0, 3) Sector 3b046b00214141 ┆; k !AAC is to command issued by VCO, a completion code is sent to VCO before entering VUS SEQUENCE module. PARA1 NE P VDUP ACK OR P SC COM ACK? WAIT PENDING OP (-2) CASE VUS OP.CMD OF VCO CMD STOP UFCO? - STOP ACTION(SEQ STOP)(CMD CC)(4.2.2.4.5.3.┆
0x3b400…3b500 (59, 0, 4) Sector 3b05ff00214141 ┆; !AA 1 VIDA CC PROCESSISNG FREE SFCO OP(VUS OP)(4.2.2.6.32) VUS OP.CMD NE EXP VDIA CMD? VUS OP. PARA1 EQ SPLIT FAILED CC? - SPLIT FAILED = TRUE CASE VUS OP.CMD OF UFCO CMD ┆
0x3b500…3b600 (59, 0, 5) Sector 3b06ff00214141 ┆; !AAINSERT SET, DELETE SET, INSERT SEGMENT, DELETE SEGMENT, INSERT GROUP, DELETE GROUP, L INSERT, L DELETE? - CASE VUS OP.PARA1 OF CO CMD CC OK CC? ERROR CC? - DISPLAY ERROR MSG( )(4.2.2.6.4) OTHERWISE? - VUS INTERNAL┆
0x3b600…3b700 (59, 0, 6) Sector 3b07ff00214141 ┆; !AA ERROR(GIVE UP) (4.1.5.2) END CASE APPEND, CLEAR VDU, OUTPUT FORMAT, DISPLAY MENU, OUTPUT DATA? - CASE VUS OP. PARA1 OF CO CMD CC OK CC? - FCK SET = SEQ REC.MASK2 ENABLE FC KEYS (4.2.┆
0x3b700…3b800 (59, 0, 7) Sector 3a08fd00214141 ┆: } !AA2.6.33) SET CURSOR(SEQ REC.CURSOR)(4.2.2.6.2 OTHERWISE? - VUS INTERNAL ERROR (GIVE UP) (4.1.5.2) END CASE OTHERWISE? - CONTINUE VDIA CC PROCESSING ( - 2) END CASE FIG. 4.2.2.4.6-1 ┆
0x3b800…3b900 (59, 0, 8) Sector 3b09ff00214141 ┆; !AAERROR? ANALYZE ERROR(CC, O) OK? CASE VUS QEL ATTR. MAINTYPE OF QELEMENT MAIN TYPE ACK? - CASE VUS QEL ATTR.SUBTYPE OF ACK SUBTYPE THP ACK? OTHERWISE? VUS QUEUE ERROR (CONT)(4.1.5.1) END CA┆
0x3b900…3ba00 (59, 0, 9) Sector 3b0aff00214141 ┆; !AASE SC VDU PAGE, SC COMMENT? - CASE VUS QEL ATTR.SUBTYPE OF MESSAGE SUBTYPE SUSPENDED/DEFERRED? SEND UMAM(4.2.8.4.5.3.1) OTHERWISE? VUSQUEUE ERROR ┆
0x3ba00…3bb00 (59, 0, 10) Sector 3b0bad00214141 ┆; - !AA (CONT)(4.1.5.1) END CASE OTHERWISE? VUS QUEUE ERROR(CONT)(4.1.5.1) END CASE END CASE ANQ OP.PARA1 = NO PENDING FIG. 4.2.2.4.5-2 EG, FK INSERT, FK DELETE? - INSERT DELETE LINES(PENDING FC)(4.2.2.4.8) ┆
0x3bb00…3bc00 (59, 0, 11) Sector 3b0cff00214141 ┆; !AA 1 STOP ACTION SEQ FORMAT = SEQ REC. NEW FORMAT SEQ CODE = STOP CODE VUS SEQUENCE (4.2.2.4.10) VUS OP.ID = UFCO ID VUS OP. PARA 1 = OK CC SIGNAL OPSEM(VUS S1, VUS OP) ┆
0x3bc00…3bd00 (59, 0, 12) Sector 3b0d4f00214141 ┆; O !AA: OK CMD CC = E USER FIG. 4.2.2.4.5.3-1 ecification a) VCO CMD PROCESSING (VUS OP: VUS CO OP TYPE):EXIT LAB b) VCO CMD PROCESSING (R5, R6) Register Convention Call Register R5 pointer to VUS OP (┆
0x3bd00…3be00 (59, 0, 13) Sector 3b0eff00214141 ┆; !AA 1 4.2.2.4.6 VDIA CC PROCESSING 4.2.2.4.6.1 Functional Specification The purpose of this module is to analyze the inputs that UFCO gets from VDIA. Depending on input a com┆
0x3be00…3bf00 (59, 0, 14) Sector 3b0fff00214141 ┆; !AApletion code is signalled to VDO and thereafter VUS SEQUENCE (4.2.2.4.11) is entered, or on behalf of other inputs VUS SEQUENCE (4.2.2.4.11) is entered directly. 4.2.2.4.6.2 Module Interface Call Specification a) VDIA CC PROCESSING (VUS ┆
0x3bf00…3c000 (59, 0, 15) Sector 3b00f700214141 ┆; w !AAOP:VUS CO OP TYPE) b) VDIA CC PROCESSING (R5, R6) Register Convention Call Register R5 pointer to VUS OP (DEST) R6 LINK (DEST) Return Register R0 - R7 (DEST) 4.2.2.4.6.3 Module Component None IN TYPE ┆
0x3c000…3c100 (60, 0, 0) Sector 3c01ff00214141 ┆< !AArefer CPS/SDS/001 MESSAGE SUBTYPE refer CPS/SDS/001 ACK SUBTYPE refer CPS/SDS/001 EXIT LAB refer 4.2.2.5 b) External Data VCO OP (m) refer 4.1.4) UFCO OP (m) refer 4.1.4 VUS S1 refer 4.1.4 VUS S2 refer┆
0x3c100…3c200 (60, 0, 1) Sector 3c02ff00214141 ┆< !AA 4.1.4 VUS QNAME (m) refer 4.1.4 VUS QEL ATTR (m) refer 4.1.4 ANQ QEL (m) refer 4.1.4 SEQ REC refer 4.2.2.5 4.2.2.4.5.5 Module Design This module inspects VCO commands, enters VUS SEQUENCE (4.2.2.4.11) and signals ackno┆
0x3c200…3c300 (60, 0, 2) Sector 3c031600214141 ┆< !AAwledges to VCO. FCO OP.ID = UFCO ID SIGNAL OPSEM(VUS S3, UFCO OP): OK END CASE FIG. 4.2.2.4.4-4 EY is converted and it is checked whether the received key is allowed or not. If the F/C key shall be followed by a new F/C key entry,┆
0x3c300…3c400 (60, 0, 3) Sector 3c04ff00214141 ┆< !AA 1 VCO CMD PROCESSING ANQ OP.PARA1 NE P VDUP ACK OR P SC COM ACK? WAIT PENDING OP (-2) CASE VUS OP.CMD OF VCO CMD STOP UFCO? - STOP ACTION(SEQ STOP)(CMD CC)(4.2.2.4.5.3.┆
0x3c400…3c500 (60, 0, 4) Sector 3c05ff00214141 ┆< !AA2) BLOCK UFCO? - STOP ACTION(SEQ CLOSE)(CMD CC)(4.2.2.4.5.3.2) CLOSE UFCO? - SEQ FORMAT = SEQ REC.NEW FORMAT SEQ CODE = SEQ CLOSE VUS SEQUENCE (4.2.2.4.10) LOOP WAIT OPSEM(VUS S2)(VDIA PTR) : OK CASE VDIA PTR. I┆
0x3c500…3c600 (60, 0, 5) Sector 3c06ff00214141 ┆< !AAD OF IDENT TYPE VDIA ID? FREE SFCO OP(VDIA PTR)(4.2.2.6.32) CMD EQ EXP VDIA CMD EXIT LOOP OTHERWISE? - VUS INTERNAL ERROR(GIVE UP) (4.1.5.2) END CASE END LOOP SIGNAL OP┆
0x3c600…3c700 (60, 0, 6) Sector 3c078d00214141 ┆< !AASEM(VUS S1, VUS OP) : OK CMD CC = E START OTHERWISE? - VUS INTERNAL ERROR (GIVE UP)(4.1.5.2) END CASE FIG. 4.2.2.4.5-1 DU FIELD(CMD LINE, SPACES)(4.2.2.6.3) STORED MASK = FCK SET FCK SET = ENTER MASK END CASE FIG. 4.2.2┆
0x3c700…3c800 (60, 0, 7) Sector 3b08ff00214141 ┆; !AA 1 WAIT PENDING OP VUS QNAME.MAINQUEUE = VUS ARRQ VUS QNAME.SUBQUEUE = ANS SUBQ CASE RECEIVE FIRST QEL (WAIT, VUS QNAME) (VUS QEL ATTR, ANQ QEL, QUEUE, CC) : ERROR OK ┆
0x3c800…3c900 (60, 0, 8) Sector 3c09ff00214141 ┆< !AA 1 VUS DISP RESP MSG EQUIVALENCE(CMD PARAM TABLE(1), CUR PARAM: CMD PARAM) LOOKUP PARAMS(BTRANS)(NO OF PARAMS)(4.2.2.6.1) NO OF PARAMS GT PARAMS 1? CUR PARAM.TYPE NE NUM? ┆
0x3c900…3ca00 (60, 0, 9) Sector 3c0aff00214141 ┆< !AA CUR PARAM.NO OF CHAR GT RESP CODE LENGTH? DISPLAY ERROR MSG( )(4.2.2.6.4) CONVERT TO INTEGER(HEADER LINE(CUR PARAM.POS), CUR PARAM.NO OF CHAR) (ERROR NO) ERROR NO GT MAX USER ERROR NO? - DISPLAY ERROR M┆
0x3ca00…3cb00 (60, 0, 10) Sector 3c0b6b00214141 ┆< k !AASG( )(4.2.2.6.4) DISPLAY ERROR MSG(ERROR NO)(4.2.2.6.4) FIG. 4.2.2.4.4.-6 PENDING FC OF PENDING FC TYPE FK INSERT SEG, FK DELETE SEG, FK INSERT, FK DELETE? - INSERT DELETE LINES(PENDING FC)(4.2.2.4.8) ┆
0x3cb00…3cc00 (60, 0, 11) Sector 3c0cff00214141 ┆< !AA 1 4.2.2.4.5 VCO CMD PROCESSING 4.2.2.4.5.1 Functional Specification The purpose of this module is to analyse commands from VCO and, in accordance with the commands, to ent┆
0x3cc00…3cd00 (60, 0, 12) Sector 3c0dff00214141 ┆< !AAer VUS SEQUENCE (4.2.2.4.11). 4.2.2.4.5.2 Module Interface Call Specification a) VCO CMD PROCESSING (VUS OP: VUS CO OP TYPE):EXIT LAB b) VCO CMD PROCESSING (R5, R6) Register Convention Call Register R5 pointer to VUS OP (┆
0x3cd00…3ce00 (60, 0, 13) Sector 3c0e7a00214141 ┆< z !AADEST) R6 LINK (DEST) Return Register None R0 - R7 (DEST) 4.2.2.4.5.3 Module Component ESENT? - CURRENT PREC EQ SUPERFLASH OR FLASH? DISPLAY ERROR MSG( )(4.2.2.6.4) SEQ CODE = NULL SEQ CODE = S┆
0x3ce00…3cf00 (60, 0, 14) Sector 3c0fff00214141 ┆< !AA 1 4.2.2.4.5.3.1 STOP ACTION Sets up sequence codes and signals completion code to VCO. Refer figure 4.2.2.4.5.3-1. 4.2.2.4.5.4 Data Description a) Data References ┆
0x3cf00…3d000 (60, 0, 15) Sector 3c00ff00214141 ┆< !AA USER ACTION TYPE refer CPS/DBD/001 QUEUE REFERENCE refer CPS/DBD/001 VCO CMD refer 4.1.4 IDENT TYPE refer 4.1.4 SEQ FORMAT TYPE refer 4.1.4 SEQ CODE TYPE refer 4.1.4 ANQ PENDING refer 4.1.4 QELEMENT MAIN TYPE ┆
0x3d000…3d100 (61, 0, 0) Sector 3d01ff00214141 ┆= !AANOT IN GROUP, VDU SPLIT FAILED)(L1, L2) L1? - DISPLAY ERROR MSG( )(4.2.2.6.4) L2? - SPLIT FAILED = TRUE END CASE OK? - FETCH UFCO OP (UFCO OP)(4.2.2.6.31) CASE VUS FC KEY OF VUS FC TYPE FC IN┆
0x3d100…3d200 (61, 0, 1) Sector 3d02ff00214141 ┆= !AASERT SET? - UFCO OP.CMD = INSERT SET FC DELETE SET? - UFCO OP.CMD = DELETE SET FC INSERT FIELD GROUP? - UFCO OP.CMD = INSERT GROUP FC DELETE FIELD GROUP? - UFCO OP.CMD = DELETE GROUP ┆
0x3d200…3d300 (61, 0, 2) Sector 3d037900214141 ┆= y !AA END CASE UFCO OP.ID = UFCO ID SIGNAL OPSEM(VUS S3, UFCO OP): OK END CASE FIG. 4.2.2.4.4-4 EY is converted and it is checked whether the received key is allowed or not. If the F/C key shall be followed by a new F/C key entry,┆
0x3d300…3d400 (61, 0, 3) Sector 3d04ff00214141 ┆= !AA 1 GET CURSOR POSITION CASE GET CURSOR POSITION(SPLIT DIGIT) (CURSOR RECORD.FIELD, CURSOR RECORD.LINES ABOVE, CC): ERROR OK ERROR? - CASE AN┆
0x3d400…3d500 (61, 0, 4) Sector 3d05ff00214141 ┆= !AAALYZE ERROR(CC,3, CURSOR NOT IN FORMATTED LINE, CURSOR NOT IN FIELD,VDU SPLIT FAILED)(L1,L2,L3) L1? L2? DISPLAY ERROR MSG( )(4.2.2.6.4) L3? SPLIT FAILED = TRUE END CASE OK? - CASE VUS FC KEY OF VUS FC TYPE FC C┆
0x3d500…3d600 (61, 0, 5) Sector 3d06ff00214141 ┆= !AAOMMAND? - PENDING FC = FK COMMAND FC DISPLAY RESPONSE MSG? - PENDING FC = FK RESP TXT FC INSERT LINE? - PENDING FC = FK INSERT FC DELETE LINE? - PENDING FC = FK DELETE FC INSERT SEGMENT? - PENDING FC = FK INSERT SEG FC ┆
0x3d600…3d700 (61, 0, 6) Sector 3d07ff00214141 ┆= !AADELETE SEGMENT? - PENDING FC = FK INSERT SEG END CASE SET CURSOR(HEADER)(4.2.2.6.2) SPLIT FAILED EQ TRUE? DISPLAY VDU FIELD(CMD LINE, SPACES)(4.2.2.6.3) STORED MASK = FCK SET FCK SET = ENTER MASK END CASE FIG. 4.2.2┆
0x3d700…3d800 (61, 0, 7) Sector 3c080d00214141 ┆< !AA.4.4-5 ITION ( - 4) FC COMMAND, FC DISPLAY RESPONSE MSG, FC INSERT LINE, FC DELETE LINE, FC INSERT SEGMENT, FC DELETE SEGMENT? GET CURSOR POSITION ( - 5) END CASE FIG. 4.2.2.4.4-1 S FC KEY PROCESSING (FC KEY: FUNCTION KEY) ┆
0x3d800…3d900 (61, 0, 8) Sector 3d09ff00214141 ┆= !AA 1 RETURN FC KEY ACTION VDU HEADER BLE.ADDRESS = ADDRESS(HEADER LINE) VDU HEADER BLE.BYTE SIZE = SIZE (HEADER LINE) HEADER ADDRESS.LINE = CMD LINE HEADER ADDRESS. INCARNAT┆
0x3d900…3da00 (61, 0, 9) Sector 3d0aff00214141 ┆= !AAION = HD INCARNATION HEADER ADDRESS. FIELD = CMD FIELD NO CASE FIELDS INPUT(HEADER IFCB, VDU HEADER BLE, HEADER ADDRESS, 1) (B TRANS, HEADER ADDRESS, CC): ERROR OK ERROR? - CASE ANALYZE ERROR(CC, 1, VDU SPLIT FAILED): (LA1) LA1? ┆
0x3da00…3db00 (61, 0, 10) Sector 3d0bff00214141 ┆= !AA- SPLIT FAILED = TRUE END CASE OK? - B TRANS EQ O? - SET CURSOR(C RETURN)(4.2.2.6.2) CASE PENDING FC OF PENDING FC TYPE FK INSERT SEG, FK DELETE SEG, FK INSERT, FK DELETE? - INSERT DELETE LINES(PENDING FC)(4.2.2.4.8) ┆
0x3db00…3dc00 (61, 0, 11) Sector 3d0caa00214141 ┆= * !AA FK COMMAND? - VUS CMD PENDING (4.2.2.4.9) FK RESP TXT? -VUS DISP RESP MSG (-6) END CASE FCK SET = STORED MASK END CASE FIG. 4.2.2.4.4-2 4 FC KEEP AND PRESENT FK 5 FC INSERT LINE FK 7 FC DISPLAY RESPONSE MSG FK 8┆
0x3dc00…3dd00 (61, 0, 12) Sector 3d0dff00214141 ┆= !AA 1 SET SEQUENCE CODE CASE VUS FC KEY OF VUS FC TYPE FC PRINT? - SEQ CODE = SEQ PRINT FC SUSPEND? - CURRENT PREC EQ SUPERFLASH OR FLASH? DISPLAY ERROR MSG( )(4.2.2┆
0x3dd00…3de00 (61, 0, 13) Sector 3d0eff00214141 ┆= !AA.6.4) SEQ CODE = NULL SEQ CODE = SEQ SUSPEND FC CANCEL? - SEQ CODE = SEQ CANCEL FC KEEP AND PRESENT? - CURRENT PREC EQ SUPERFLASH OR FLASH? DISPLAY ERROR MSG( )(4.2.2.6.4) SEQ CODE = NULL SEQ CODE = S┆
0x3de00…3df00 (61, 0, 14) Sector 3d0fbd00214141 ┆= = !AAEQ KEEP FC DELETE AND PRESENT? - SEQ CODE = SEQ DELETE FC ENTER? - SEQ CODE = SEQ ENTER END CASE SEQ CODE EQ NULL? VUS SEQUENCE (4.2.2.4.10) FIG. 4.2.2.4.4-3 FCO CMD refer 4.1.4 CO CMD CC -"- VUS FC TYPE refer 4.2.2┆
0x3df00…3e000 (61, 0, 15) Sector 3d00ff00214141 ┆= !AA 1 GET SEGMENT POSITION CASE GET CURSOR GROUP POSITION(FORMAT IFCB)(GROUP NO GROUP INC, CC): ERROR OK ERROR? - CASE ANALYZE ERROR(CC, 2, CURSOR ┆
0x3e000…3e100 (62, 0, 0) Sector 3e01ff00214141 ┆> !AA -"- HEADER IFCB -"- FORMAT IFCB -"- VUS S3 -"- VDU HD BLE (m) -"- FCK SET (m) refer 4.2.2.5 OUTPUT FLAG (m) -"- SPLIT FAILED (m) -"- VUS FC KEY (m) -"- PENDING FC (m) -"- HEADER ADDRESS ┆
0x3e100…3e200 (62, 0, 1) Sector 3e02bf00214141 ┆> ? !AA(m) -"- BTRANS (m) refer 4.2..2.5 CURRENT PREC -"- SEQ CODE (m) -"- c) Local Data VAR STORED MASK: LONG GROUP NO, GROUP INC: COUNTER ENTER MASK: LONG ERROR? - CASE ANALYZE ERROR(CC,1,OPEN NOT ACCEPTED)(LA1) ┆
0x3e200…3e300 (62, 0, 2) Sector 3e03ff00214141 ┆> !AA 1 4.2.2.4.4.5 Module Design The received F/C-KEY is converted and it is checked whether the received key is allowed or not. If the F/C key shall be followed by a new F/C key entry,┆
0x3e300…3e400 (62, 0, 3) Sector 3e048f00214141 ┆> !AA then the variable PENDING FC is updated. Insert/delete line commands is signalled to VDIA. For other F/C-KEYS VUS SEQUENCE is entered. CE (4.2.2.4.10) FIG. 4.2.2.4.3-2 OTHERWISE? - CC = A QER END CASE OTHERWISE? - CC = A QER ┆
0x3e400…3e500 (62, 0, 4) Sector 3e05ff00214141 ┆> !AA 1 1 FC KEY VALIDATION CONVERT FC KEY (FC KEY)(VUS FC KEY)(4.2.2.4.4.3.1) VUS FC KEY EQ FC DUMMY? VUS FC K┆
0x3e500…3e600 (62, 0, 5) Sector 3e06ff00214141 ┆> !AAEY NOT IN FCK SET? DISPLAY ERROR MSG (4.2.2.6.4) OUTPUT FLAG EQ TRUE? - DISPLAY VDU FIELD (RESP LINE SPACES) (4.2.2.6.3) OUTPUT FLAG = FALSE SPLIT FAILED EQ TRUE? CASE VUS FC KEY OF VUS FC TYPE FC RETURN? - RE┆
0x3e600…3e700 (62, 0, 6) Sector 3e07ff00214141 ┆> !AATURN FC KEY ACTION ( -2) FC PRINT, FC SUSPEND, FC CANCEL, FC KEEP AND PRESENT, FC DELETE AND PRESENT, FC ENTER? SET SEQUENCE CODE ( - 3) FC INSERT SET, FC DELETE SET, FC INSERT FIELD GROUP, FC DELETE FIELD GROUP? - GET SEGM┆
0x3e700…3e800 (62, 0, 7) Sector 3d08d200214141 ┆= R !AAENT POSITION ( - 4) FC COMMAND, FC DISPLAY RESPONSE MSG, FC INSERT LINE, FC DELETE LINE, FC INSERT SEGMENT, FC DELETE SEGMENT? GET CURSOR POSITION ( - 5) END CASE FIG. 4.2.2.4.4-1 S FC KEY PROCESSING (FC KEY: FUNCTION KEY) ┆
0x3e800…3e900 (62, 0, 8) Sector 3e09ff00214141 ┆> !AAb) VUS FC KEY PROCESSING (R6) Register Convention Call Register R5 FC KEY (DEST) R6 LINK (DEST) Return Register R0 - R7 (DEST) 4.2.2.4.4.3 Module Components 4.2.2.4.4.3.1 CONVERT FC KEY The procedure converts the Function ke┆
0x3e900…3ea00 (62, 0, 9) Sector 3e0a8100214141 ┆> !AAy type received from the Format Handler to a logical function key in accordance with the table shown in table 4.2.2.4.4-1. .4.3.4 Data Description a) Data References SEQ FORMAT TYPE refer 4.1.4 SEQ CODE TYPE refer 4.1.4 STATUS TYPE refer 4┆
0x3ea00…3eb00 (62, 0, 10) Sector 3e0bff00214141 ┆> !AA 1 1 FC KEY IDENTIFICATION LOGICAL FC KEY DELIVERED BY IDENTIFICAT┆
0x3eb00…3ec00 (62, 0, 11) Sector 3e0cff00214141 ┆> !AAION FORMAT HANDLER ASSIGNED BY VUS ENTER 1 FC RETURN FC ENTER FK 1 FC COMMAND FK 2 FC SUSPEND FK 4 FC KEEP AND PRESENT FK 5 FC INSERT LINE FK 7 FC DISPLAY RESPONSE MSG FK 8┆
0x3ec00…3ed00 (62, 0, 12) Sector 3e0dff00214141 ┆> !AA FC CANCEL FK 9 FC PRINT FK10 FC DELETE AND PRESENT FK11 FC DELETE LINE FK25 FC INSERT SEGMENT FK26 FC DELETE SEGMENT FK28 FC INSERT SET FK29 FC DELETE SET FK31 FC INSERT FIELD GROUP FK32 FC DELETE FIND GROUP ┆
0x3ed00…3ee00 (62, 0, 13) Sector 3e0edb00214141 ┆> [ !AA FK 3 FK 6 FK12 - FK24 FC DUMMY FK27 FK30 FK33 - FK30 F/C KEY CONVERSION TABLE TABLE 4.2.2.4.4-1 NCED CIF (4.2.2.4.3.3) FOUN┆
0x3ee00…3ef00 (62, 0, 14) Sector 3e0fff00214141 ┆> !AA 1 4.2.2.4.4.4. Data Description a) Data References FUNCTION KEY refer CPS/DBD/001 PRECEDENCE TYPE -"- UFCO CMD refer 4.1.4 CO CMD CC -"- VUS FC TYPE refer 4.2.2┆
0x3ef00…3f000 (62, 0, 15) Sector 3e00ff00214141 ┆> !AA.5 PENDING FC TYPE -"- CURSOR SPLIT TYPE -"- SEQ CODE TYPE -"- PARAMS TYPE -"- CMD PARAM -"- VUS RESP MSG TYPE -"- b) External Data UFCO OP (m) refer 4.1.4 CURSOR RECORD (m) -"- SPLIT DIGIT ┆
0x3f000…3f100 (63, 0, 0) Sector 3f010c00214141 ┆? !AA4.3-1 C = A ACK ANQ ER NO = NULL SEQ CODE = SEQ COOR DISP OTHERWISE? - CC = A QER END CASE OTHERWISE? - CC = A QER END CASE FIG. 4.2.2.4.2-15 S E NOT ┆
0x3f100…3f200 (63, 0, 1) Sector 3f02ff00214141 ┆? !AA 1 APPEND COMPLETE LOOKUP REFERENCED CIF (4.2.2.4.3.3) FOUND? - CASE OPEN VIEW(APPEND CIF)(CC): ERROR OK ERROR? - CASE ANALYZE ERROR(CC,1,OPEN NOT ACCEPTED)(LA1) ┆
0x3f200…3f300 (63, 0, 2) Sector 3f03ff00214141 ┆? !AA LA1? - TEP RETURN(APPEND CIF)( ) VUS DISMANTLE(ANQ QEL CLOSE(4.1.5.3) END CASE OK? - APPEND = COMPLETE SEQ PARAM.FORMAT = C1 SEQ PARAM.CODE = CTMP CONT VUS SEQUENCE (4.2.2.4.10) E┆
0x3f300…3f400 (63, 0, 3) Sector 3f04bb00214141 ┆? ; !AAND CASE VUS QUEUE ERROR (CONTINUE)(4.1.5.1) APPEND = ERROR COMPLETE SEQ PARAM.FORMAT = C1 SEQ PARAM.CODE = CTMP CONT VUS SEQUENCE (4.2.2.4.10) FIG. 4.2.2.4.3-2 OTHERWISE? - CC = A QER END CASE OTHERWISE? - CC = A QER ┆
0x3f400…3f500 (63, 0, 4) Sector 3f05ff00214141 ┆? !AA 1 APPEND ABNORMAL LOOKUP REFERENCED CIF (4.2.2.4.3.3) FOUND? - APPEND = ERROR COMPLETE VUS LOG. ITEM REF = TRSERNO VUS DISMANTLE(APPEND CIF)(4.1.5.3) VUS QUEU┆
0x3f500…3f600 (63, 0, 5) Sector 3f06b700214141 ┆? 7 !AAE ERROR(CONTINUE)(4.1.5.1) APPEND = ERROR COMPLETE SEQ PARAM.FORMAT = C1 SEQ PARAM.CODE = CTMP CONT VUS SEQUENCE(4.2.2.4.10) FIG. 4.2.2.4.3-3 oked up in the Response Queue. 4.2.2.4.3.2 Module Interface Call S┆
0x3f600…3f700 (63, 0, 6) Sector 3f07ff00214141 ┆? !AA 1 4.2.2.4.4 VUS F/C KEY PROCESSING 4.2.2.4.4.1 Functional Specification The purpose of this module is to analyse the F/C KEY input, and, depending on the F/C KEY identity to cal┆
0x3f700…3f800 (63, 0, 7) Sector 3e08ff00214141 ┆> !AAl other modules and procedures. Further it takes care of blanking the command and the response-line and placing the cursor or the command line. 4.2.2.4.4.2 Module Interface Call Specification a) VUS FC KEY PROCESSING (FC KEY: FUNCTION KEY) ┆
0x3f800…3f900 (63, 0, 8) Sector 3f09ff00214141 ┆? !AA 1 4.2.2.4.3.3 Module Components a) LOOKUP REFERENCED CIF This procedure receives QEL's from the Response Queue and compares the item ref. ID found in the QEL-attributes with the┆
0x3f900…3fa00 (63, 0, 9) Sector 3f0aff00214141 ┆? !AA item ref. ID of the CIF received in the Answer Queue. The procedure will return with a completion code and a QEL. 4.2.2.4.3.4 Data Description a) Data References SEQ FORMAT TYPE refer 4.1.4 SEQ CODE TYPE refer 4.1.4 STATUS TYPE refer 4┆
0x3fa00…3fb00 (63, 0, 10) Sector 3f0bff00214141 ┆? !AA.1.4 QEL REFERENCE refer CPS/DBD/001 QEL ATTRIBUTES refer CPS/DBD/001 USER ACTION TYPE refer CPS/DBD/001 b) External Data APPEND CIF refer 4.2.2.5 SEQ PARAM refer 4.2.2.5 APPEND refer 4.2.2.5 VUS LOG refer 4.2.2.5 c) Local Dat┆
0x3fb00…3fc00 (63, 0, 11) Sector 3f0c4900214141 ┆? I !AAa None 4.2.2.4.3.5 Module Design Refer figure 4.2.2.4.3-1 DELETE RESPONSE CASE VUS QEL ATTR.MAINTYPE OF QELEMENT MAIN TYPE TEP INTERNAL? CASE VUS QEL ATTR. SUBTYPE OF TEP INTERNAL SUBTYPE UMAM RESPONSE? CASE VUS Q┆
0x3fc00…3fd00 (63, 0, 12) Sector 3f0dff00214141 ┆? !AA 1 1 CASE OPEN VIEW(ANQ QEL)(CC): ERROR OK ERROR? - CASE ANALYZE ERROR(CC, 2) STOPPED, OPEN NOT ACCEPTED)(L┆
0x3fd00…3fe00 (63, 0, 13) Sector 3f0eff00214141 ┆? !AAA1, LA2) LA1? - DISPLAY ERROR MSG (4.2.2.6.4) VUS DISMANTLE (ANQ QEL)(4.1.5.3) STATUS NE APPEND COMPLETE OR APPEND AB- NORMAL? LOOKUP REFERENCED CIF (4.2.2.4.3.3) FOUN┆
0x3fe00…3ff00 (63, 0, 14) Sector 3f0fff00214141 ┆? !AAD? - VUS DISMANTLE (APPEND CIF) (4.1.5.3) VUS QUEUE ERROR (CONTINUE)(4.1.5.1) SEQ PARAM.CODE = SEQ UMAM ERROR VUS SEQUENCE (4.2.2.4.10) LA2? - VUS DISMANTLE(ANQ QEL)(4.1.5.3) END CASE OK? ┆
0x3ff00…40000 (63, 0, 15) Sector 3f00ff00214141 ┆? !AA- STATUS EQ APPEND COMPLETE? - APPEND COMPLETE (-2) STATUS EQ APPEND ABNORMAL? - APPEND ABNORMAL (-3) SEQ PARAM.FORMAT = C1 SEQ PARAM.CODE = CTMP CONT INPUT CIF = ANQ QEL VUS SEQUENCE(4.2.2.4.10) END CASE FIG. 4.2.2.┆
0x40000…40100 (64, 0, 0) Sector 4001ef00214141 ┆@ o !AAY? - CC = A ACK ANQ ER NO = NULL SEQ CODE = SEQ COOR DISP OTHERWISE? - CC = A QER END CASE OTHERWISE? - CC = A QER END CASE FIG. 4.2.2.4.2-15 S E NOT ┆
0x40100…40200 (64, 0, 1) Sector 4002ff00214141 ┆@ !AA 1 SSC ACK CASE VUS QEL ATTR.MAINTYPE OF QELEMENT MAIN TYPE ACK? - CASE VUS QEL ATTR.SUBTYPE OF ACK SUBTYPE SSC ACK? - CASE VUS QEL ATTR OF SEC ANS SEC OK? -┆
0x40200…40300 (64, 0, 2) Sector 4003ff00214141 ┆@ !AA CC = A ACK SEQ CODE = SEQ SEC OK SEC NOK? - CC = A ACK SEQ CODE = SEQ SEC NOK OTHERWISE? - CC = A QER END CASE ANQ ER NO = NULL OTHERWISE? = CC = A QER END CASE OTHERWISE? -┆
0x40300…40400 (64, 0, 3) Sector 40044000214141 ┆@ @ !AA CC = A QER END CASE FIG. 4.2.2.4.2-16 CC = A RESP OTHERWISE? - CC = A QER END CASE OTHERWISE? - CC = A QER END CASE OTHERWISE? - CC = A QER END CASE OTHERWISE? - CC = A QER ┆
0x40400…40500 (64, 0, 4) Sector 4005ff00214141 ┆@ !AA 1 4.2.2.4.3 Append Investigation 4.2.2.4.3.1 Functional Description The purpose of this module is to inspect items for continued preparation which are received in the answer qu┆
0x40500…40600 (64, 0, 5) Sector 4006ff00214141 ┆@ !AAeue. The received CIF will be opened and it is checked whether the status type is identical to append complete or not. If append is required then the referenced CIF will be looked up in the Response Queue. 4.2.2.4.3.2 Module Interface Call S┆
0x40600…40700 (64, 0, 6) Sector 4007ff00214141 ┆@ !AApecification a) APPEND INVESTIGATION(ANQ QEL: QEL REFERENCE ANQ QEL ATTR: QEL ATTRIBUTES) b) APPEND INVESTIGATION (R1, R2, R6) Register Convention Call Registers R1 pointer to ANQ QEL ATTR (DEST) R2 ANQ QEL ┆
0x40700…40800 (64, 0, 7) Sector 3f085100214141 ┆? Q !AA (DEST) R6 LINK (DEST) Return Registers None R0 - R7 (DEST) ELEASE STATUS CASE VUS QEL ATTR.MAINTYPE OF QELEMENT MAIN TYPE STATUS? - CASE VUS QEL ATTR.SUBTYPE OF STATUS SUBTYPE RELEASE MESSAGE STATUS? - CC = A CIF OT┆
0x40800…40900 (64, 0, 8) Sector 40098300214141 ┆@ !AAHERWISE? - CC = A QER END CASE OTHERWISE? - CC = A QER END CASE FIG. 4.2.2.4.2-12 ROR RESP? CASE VUS QEL ATTR.FLAG OF UMAM RESPONSE EDIT RESP? CASE VUS QEL ATTR.INF OF EDIT ANS ┆
0x40900…40a00 (64, 0, 9) Sector 400aff00214141 ┆@ !AA 1 DELIVERY STATUS CASE VUS QEL ATTR.MAINTYPE OF QELEMENT MAIN TYPE STATUS? - CASE VUS QEL ATTR.SUBTYPE OF STATUS SUBTYPE DELIVERY STATUS? - CC = A CIF OTHERWIS┆
0x40a00…40b00 (64, 0, 10) Sector 400b7d00214141 ┆@ } !AAE? - CC = A QER END CASE OTHERWISE? - CC = A QER END CASE FIG. 4.2.2.4.2-13 6) OTHERWISE? - VUS INTERNAL ERROR(GIVE UP)(4.1.5.2) END CASE ANQ OP.PARA1 = NO PENDING FIG. 4.2.2.4.2-3 AR ANQ ┆
0x40b00…40c00 (64, 0, 11) Sector 400cff00214141 ┆@ !AA 1 DELETE RESPONSE CASE VUS QEL ATTR.MAINTYPE OF QELEMENT MAIN TYPE TEP INTERNAL? CASE VUS QEL ATTR. SUBTYPE OF TEP INTERNAL SUBTYPE UMAM RESPONSE? CASE VUS Q┆
0x40c00…40d00 (64, 0, 12) Sector 400dff00214141 ┆@ !AAEL ATTR.FLAG OF UMAM RESPONSE DELETE RESP? CASE VUS QEL ATTR.INF OF DELETE ANS D NOT FOUND, D DELETED, D AWAITING RELEASE, D AWAITING APPEND? - ANQ ER NO = CC = A RESP D APPEN┆
0x40d00…40e00 (64, 0, 13) Sector 400eff00214141 ┆@ !AAD COMP? - ANQ ER NO = CC = A RESP DELETE APPEND CIF OTHERWISE? - CC = A QER END CASE OTHERWISE? - CC = A QER END CASE OTHERWISE? - CC = A QER END CASE OTHERWISE? - CC = A QER EN┆
0x40e00…40f00 (64, 0, 14) Sector 400f2200214141 ┆@ " !AAD CASE FIG. 4.2.2.4.2-14 SC COMMENT ACK CASE VUS QEL ATTR.MAINTYPE OF QELEMENT MAIN TYPE SC COMMENT? CASE VUS QEL ATTR.SUBTYPE OF MESSAGE SUBTYPE SUSPENDED/DEFERRED? - ANQ ER NO = ┆
0x40f00…41000 (64, 0, 15) Sector 4000ff00214141 ┆@ !AA 1 COORDINATION NOT CASE VUS QEL ATTR.MAINTYPE OF QELEMENT MAIN TYPE COORDINATION NOTIFICATION? - CASE VUS QEL ATTR.SUBTYPE OF COOR SUBTYPE FOR DISPLA┆
0x41000…41100 (65, 0, 0) Sector 41014f00214141 ┆A O !AAE OTHERWISE? - CC = A QER END CASE FIG. 4.2.2.4.2-9 BTYPE OF TEP INTERNAL SUBTYPE UMAM ERROR RESP? CASE VUS QEL ATTR.FLAG OF UMAM RESPONSE EDIT RESP? CASE VUS QEL ATTR.INF OF EDIT ANS E NOT ┆
0x41100…41200 (65, 0, 1) Sector 4102ff00214141 ┆A !AA 1 VDU PAGE RETR CASE VUS QEL ATTR.MAINTYPE OF QELEMENT MAIN TYPE SC VDU PAGE? - CASE VUS QEL ATTR.SUBTYPE OF MESSAGE SUBTYPE FOR DISPLAY ? - CC = A CIF OTHE┆
0x41200…41300 (65, 0, 2) Sector 4103ff00214141 ┆A !AARWISE? - CC = A QER END CASE TEP INTERNAL? CASE VUS QEL ATTR.SUBTYPE OF TEP INTERNAL SUBTYPE UMAM ERROR RESP? CASE VUS QEL ATTR.FLAG OF UMAM RESPONSE VDU RETR RESP? CASE VUS QEL ATTR.INF OF RETR ANS R┆
0x41300…41400 (65, 0, 3) Sector 4104ff00214141 ┆A !AA NOT FOUND, R SEC PROFILE? - ANQ ER NO = CC = A RESP OTHERWISE? - CC = A QER END CASE OTHERWISE? - CC = A QER END CASE OTHERWISE? - CC = A QER END CASE OTHERWISE? - CC = A QER ┆
0x41400…41500 (65, 0, 4) Sector 41052500214141 ┆A % !AA END CASE FIG. 4.2.2.4.2-10 END CASE TEP INTERNAL? CASE VUS QEL ATTR.SUBTYPE OF TEP INTERNAL SUBTYPE UMAM ERROR RESP? CASE VUS QEL ATTR.FLAG OF UMAM RESPONSE EDIT RESP? CASE VUS QEL ATTR.INF OF EDIT ANS ┆
0x41500…41600 (65, 0, 5) Sector 4106ff00214141 ┆A !AA 1 OUTGOING STATUS CASE VUS QEL ATTR.MAINTYPE OF QELEMENT MAIN TYPE STATUS? - CASE VUS QEL ATTR.SUBTYPE OF STATUS SUBTYPE OUTGOING MESSAGE STATUS? - CC = A CIF ┆
0x41600…41700 (65, 0, 6) Sector 41078500214141 ┆A !AAOTHERWISE? - CC = A QER END CASE OTHERWISE? - CC = A QER END CASE FIG. 4.2.2.4.2-11 END CASE VUS DISMANTLE (ANQ QEL)(4.1.5.3) OK? - SEQ FORMAT = SEQ REC. NEW FORMAT SEQ CODE = SEQ ANQ CONT ┆
0x41700…41800 (65, 0, 7) Sector 4008ff00214141 ┆@ !AA 1 RELEASE STATUS CASE VUS QEL ATTR.MAINTYPE OF QELEMENT MAIN TYPE STATUS? - CASE VUS QEL ATTR.SUBTYPE OF STATUS SUBTYPE RELEASE MESSAGE STATUS? - CC = A CIF OT┆
0x41800…41900 (65, 0, 8) Sector 4109ff00214141 ┆A !AA OTHERWISE? - CC = A QER END CASE TEP INTERNAL? CASE VUS QEL ATTR.SUBTYPE OF TEP INTERNAL SUBTYPE UMAM ERROR RESP? CASE VUS QEL ATTR.FLAG OF UMAM RESPONSE EDIT RESP? CASE VUS QEL ATTR.INF OF EDIT ANS ┆
0x41900…41a00 (65, 0, 9) Sector 410aff00214141 ┆A !AA E NOT FOUND, E SEC PROFILE? - ANQ ER NO = CC = A RESP OTHERWISE? - CC = A QER END CASE OTHERWISE? - CC = A QER END CASE OTHERWISE? - CC = A QER END CASE OTHERWISE? - CC = A QER┆
0x41a00…41b00 (65, 0, 10) Sector 410b2600214141 ┆A & !AA END CASE FIG. 4.2.2.4.2-7 DELETE RESP (-14) P COOR ACK? - COORDINATION NOT (-15) P SSC ACK? - SSC ACK (-16) OTHERWISE? - VUS INTERNAL ERROR(GIVE UP)(4.1.5.2) END CASE ANQ OP.PARA1 = NO PENDING FIG. 4.2.2.4.2-3 AR ANQ ┆
0x41b00…41c00 (65, 0, 11) Sector 410cff00214141 ┆A !AA 1 VDU PAGE ACK CASE VUS QEL ATTR.MAINTYPE OF QELEMENT MAIN TYPE SC VDU PAGE? - CASE VUS QEL ATTR.SUBTYPE OF MESSAGE SUBTYPE SUSPENDED/DEFERRED? - ANQ ER NO = ┆
0x41c00…41d00 (65, 0, 12) Sector 410dff00214141 ┆A !AA SEQ CODE = SEQ THP NACK CC = A ACK OTHERWISE? - CC = A QER END CASE ACK? - CASE VUS QEL ATTR. SUBTYPE OF ACK SUBTYPE THP ACK? - ANQ ER NO = CC = A RESP OTHERWISE? - CC = A QER END CA┆
0x41d00…41e00 (65, 0, 13) Sector 410e5000214141 ┆A P !AASE OTHERWISE? - CC = A QER END CASE FIG. 4.2.2.4.2-8 E NOT AVAIB, E APPEND NOT COMP, E SEC PROFILE? - ANQ ER NO = CC = A RESP OTHERWISE? CC = A QER END┆
0x41e00…41f00 (65, 0, 14) Sector 410fff00214141 ┆A !AA 1 SC COMMENT ACK CASE VUS QEL ATTR.MAINTYPE OF QELEMENT MAIN TYPE SC COMMENT? CASE VUS QEL ATTR.SUBTYPE OF MESSAGE SUBTYPE SUSPENDED/DEFERRED? - ANQ ER NO = ┆
0x41f00…42000 (65, 0, 15) Sector 4100ff00214141 ┆A !AA SEQ CODE = SEQ THP NACK CC = A ACK OTHERWISE? - CC = A QER END CASE ACK? - CASE VUS QEL ATTR. SUBTYPE OF ACK SUBTYPE THP ACK? - ANQ ER NO = CC = A RESP OTHERWISE? - CC = A QER END CAS┆
0x42000…42100 (66, 0, 0) Sector 4201ff00214141 ┆B !AASE? CC = A QER END CASE TEP INTERNAL? CASE VUS QEL ATTR.SUBTYPE OF TEP INTERNAL SUBTYPE UMAM ERROR RESP? CASE VUS QEL ATTR.FLAG OF UMAM RESPONSE EDIT RESP? CASE VUS QEL ATTR.INF OF EDIT ANS E NOT ┆
0x42100…42200 (66, 0, 1) Sector 4202ff00214141 ┆B !AAFOUND, E SEC PROFILE? - ANQ ER NO = CC = A RESP OTHERWISE? - CC = A QER END CASE OTHERWISE? - CC = A QER END CASE OTHERWISE? - CC = A QER END CASE OTHERWISE? - CC = A QER ┆
0x42200…42300 (66, 0, 2) Sector 42032400214141 ┆B $ !AA END CASE FIG. 4.2.2.4.2-5 ? CASE DISPLAY RESP MSG(ANQ ER NO): EXC DONE (4.2.2.6.4) EXC? - RETURN CC = EXC DONE? - SEQ CODE = SEQ ANQ RESP SEQ FORMAT = SEQ REC. NEW FORMAT VUS SEQUENCE (4.2.2.4.10) RETURN C┆
0x42300…42400 (66, 0, 3) Sector 4204ff00214141 ┆B !AA 1 VDU PAGE EDIT CASE VUS QEL ATTR.MAINTYPE OF QELEMENT MAIN TYPE SC VDU PAGE? - CASE VUS QEL ATTR.SUBTYPE OF MESSAGE SUBTYPE FOR CONTINUED PREP? - CC = A CIF ┆
0x42400…42500 (66, 0, 4) Sector 4205ff00214141 ┆B !AA OTHERWISE? - CC = A QER END CASE TEP INTERNAL? CASE VUS QEL ATTR.SUBTYPE OF TEP INTERNAL SUBTYPE UMAM ERROR RESP? CASE VUS QEL ATTR.FLAG OF UMAM RESPONSE EDIT RESP? CASE VUS QEL ATTR.INF OF EDIT ANS ┆
0x42500…42600 (66, 0, 5) Sector 4206ff00214141 ┆B !AA E NOT FOUND, E SEC PROFILE? - ANQ ER NO = CC = A RESP OTHERWISE? - CC = A QER END CASE OTHERWISE? - CC = A QER END CASE OTHERWISE? - CC = A QER END CASE OTHERWISE? - CC = A QER┆
0x42600…42700 (66, 0, 6) Sector 42072600214141 ┆B & !AA END CASE FIG. 4.2.2.4.2-6 RETURN CC = DONE END CASE SEC FAILED = TRUE L2? - RETURN CC = EXC END CASE VUS DISMANTLE (ANQ QEL)(4.1.5.3) OK? - SEQ FORMAT = SEQ REC. NEW FORMAT SEQ CODE = SEQ ANQ CONT ┆
0x42700…42800 (66, 0, 7) Sector 4108ff00214141 ┆A !AA 1 SC COMMENT EDIT CASE VUS QEL ATTR.MAINTYPE OF QELEMENT MAIN TYPE SC COMMENT? CASE VUS QEL ATTR.SUBTYPE OF MESSAGE SUBTYPE FOR CONTINUED PREP? - CC = A CIF ┆
0x42800…42900 (66, 0, 8) Sector 4209ff00214141 ┆B !AA 1 VALIDATE ANQ INPUT CASE ANQ OP. PARA1 OF ANQ PENDING P MSG EDIT? - MESSAGE EDIT (-4) P COM EDIT? - COMMENT EDIT (-5) P VDUP EDIT? - VDU PAGE EDIT (-6) P SC CO┆
0x42900…42a00 (66, 0, 9) Sector 420aff00214141 ┆B !AAM EDIT? - SC COMMENT EDIT (-7) P VDUP ACK? - VDU PAGE ACK (-8) P SC COM ACK? - SC COMMENT ACK (-9) P VDUP RETR? - VDU PAGE RETR (-10) P OUTG STA? - OUTGOING STATUS (-11) P RELS STA? - RELEASE STATUS (-12) P DEL STA? - DELIVERY ┆
0x42a00…42b00 (66, 0, 10) Sector 420bf800214141 ┆B x !AASTATUS (-13) P DELETE ACK? - DELETE RESP (-14) P COOR ACK? - COORDINATION NOT (-15) P SSC ACK? - SSC ACK (-16) OTHERWISE? - VUS INTERNAL ERROR(GIVE UP)(4.1.5.2) END CASE ANQ OP.PARA1 = NO PENDING FIG. 4.2.2.4.2-3 AR ANQ ┆
0x42b00…42c00 (66, 0, 11) Sector 420cff00214141 ┆B !AA 1 MESSAGE EDIT CASE VUS QEL ATTR.MAINTYPE OF QELEMENT MAIN TYPE PLAINDRESS, PLAINDRESS DATA? - CASE VUS QEL ATTR.SUBTYPE OF MESSAGE SUBTYPE FOR CONTINUED PRE┆
0x42c00…42d00 (66, 0, 12) Sector 420dff00214141 ┆B !AAP? - CC = A MSG OTHERWISE? - CC = A QER END CASE TEP INTERNAL? - CASE VUS QEL ATTR.SUBTYPE OF TEP INTERNAL SUBTYPE UMAM ERROR RESP? CASE VUS QEL ATTR.FLAG OF UMAM RESPONSE EDIT RESP? ┆
0x42d00…42e00 (66, 0, 13) Sector 420eff00214141 ┆B !AACASE VUS QEL ATTR.INF OR EDIT ANS E NOT FOUND, E NOT AVAIB, E APPEND NOT COMP, E SEC PROFILE? - ANQ ER NO = CC = A RESP OTHERWISE? CC = A QER END┆
0x42e00…42f00 (66, 0, 14) Sector 420fa800214141 ┆B ( !AA CASE OTHERWISE? - CC = A QER END CASE OTHERWISE? CC = A QER END CASE OTHERWISE? - CC = A QER END CASE FIG. 4.2.2.4.2-4 MD refer 4.1.4 IDENT TYPE refer 4.1.4 EXC DONE refer 4.1.4 EXIT LAB refer 4.2.2.5┆
0x42f00…43000 (66, 0, 15) Sector 4200ff00214141 ┆B !AA 1 COMMENT EDIT CASE VUS QEL ATTR.MAINTYPE OF QELEMENT MAIN TYPE COMMENT? - CASE VUS QEL ATTR.SUBTYPE OF MESSAGE SUBTYPE FOR CONTINUED PREP? - CC = A CIF OTHERWI┆
0x43000…43100 (67, 0, 0) Sector 4301ff00214141 ┆C !AAONT)(4.1.5.2) CASE DISPLAY RESP MSG ( ):EXC DONE(4.2.2.6.4) EXC? RETURN CC = EXC DONE? SEQ FORMAT = SEQ REC.NEW FORMAT SEQ CODE = SEQ QER RETURN CC = DONE VUS SEQUENCE(4.2.2.4.10) END CASE ┆
0x43100…43200 (67, 0, 1) Sector 4302ff00214141 ┆C !AAA MSG? APPEND INVEST (4.2.2.4.3) RETURN CC = DONE A ACK? CASE DISPLAY RESP MSG(ANQ ER NO)(4.2.2.6.4):EXC DONE EXC? - RETURN CC = EXC DONE? - SEQ FORMAT = SEQ REC. NEW FORMAT VUS SEQUENCE (4.2.2.4.10) RETURN CC =┆
0x43200…43300 (67, 0, 2) Sector 4303ff00214141 ┆C !AA DONE END CASE A RESP? CASE DISPLAY RESP MSG(ANQ ER NO): EXC DONE (4.2.2.6.4) EXC? - RETURN CC = EXC DONE? - SEQ CODE = SEQ ANQ RESP SEQ FORMAT = SEQ REC. NEW FORMAT VUS SEQUENCE (4.2.2.4.10) RETURN C┆
0x43300…43400 (67, 0, 3) Sector 43046f00214141 ┆C o !AAC = DONE END CASE A CIF? OPEN RECEIVED CIF ( 2) END CASE RETURN(RETURN CC) fig. 4.2.2.4.2-1 AIT OPSEM(VUS S2)(VCO-PTR):OK CASE VCO PTR.ID OF IDENT TYPE VCO ID? CASE VCO CMD PROCESSING (VCO PTR):EXIT LAB(4.2.2.4.5) ┆
0x43400…43500 (67, 0, 4) Sector 4305ff00214141 ┆C !AA 1 1 OPEN RECEIVED CIF CASE OPEN VIEW(ANQ QEL)(CC): ERROR OK ERROR? - CASE ANALYZE ERROR(CC, 2, STOP┆
0x43500…43600 (67, 0, 5) Sector 4306ff00214141 ┆C !AAPED, OPEN NOT ACCEPTED) (L1,L2) L1? - CASE DISPLAY RESP MSG( ):EXC DONE (4.2.2.6.4) EXC? - RETURN CC = EXC DONE? - SEQ FORMAT = SEQ REC. NEW FORMAT SEQ CODE = SEQ QER ┆
0x43600…43700 (67, 0, 6) Sector 4307ff00214141 ┆C !AA VUS SEQUENCE (4.2.2.4.10) RETURN CC = DONE END CASE SEC FAILED = TRUE L2? - RETURN CC = EXC END CASE VUS DISMANTLE (ANQ QEL)(4.1.5.3) OK? - SEQ FORMAT = SEQ REC. NEW FORMAT SEQ CODE = SEQ ANQ CONT ┆
0x43700…43800 (67, 0, 7) Sector 42085f00214141 ┆B _ !AA VUS SEQUENCE (4.2.2.4.10) RETURN CC = DONE END CASE FIG. 4.2.2.4.2-2 ription a) Data References VUS CO OP TYPE refer 4.1.4 QEL ATTRIBUTES refer CPS/DBD/001 QEL REFERENCE refer CPS/DBD/001 SEQ CODE TYPE refer 4.1.4 QU┆
0x43800…43900 (67, 0, 8) Sector 4309ff00214141 ┆C !AAEUE REFERENCE refer CPS/DBD/001 QELEMENT MAIN TYPE refer CPS/DBD/001 MESSAGE SUBTYPE refer CPS/DBD/001 TEP INTERNAL SUBTYPE refer CPS/DBD/001 ACK SUBTYPE refer CPS/DBD/001 STATUS SUBTYPE refer CPS/DBD/001 COORDINATIONNNOT SUBTYPE refer C┆
0x43900…43a00 (67, 0, 9) Sector 430aff00214141 ┆C !AAPS/DBD/001 USER ACTION TYPE refer CPS/DBD/001 UMAM RESPONSE refer 4.1.4 EDIT ANS refer 4.1.4 DELETE ANS refer 4.1.4 RETR ANS refer 4.1.4 VUS RESP MSG TYPE refer 4.1.4 SEC ANS refer 4.2.2.5 ANQ CC refer 4.2.2.5 ANQ PENDING refer 4┆
0x43a00…43b00 (67, 0, 10) Sector 430bff00214141 ┆C !AA.2.2.5 SEQ CODE TYPE refer 4.2.2.5 SEQ FORMAT TYPE refer 4.2.2.5 b) External Data VUS QEL ATTR refer 4.1.4 ANQ QEL refer 4.1.4 ANQ OP(M) refer 4.1.4 SEQ FORMAT(M) refer 4.2.2.5 SEQ CODE(M) refer 4.2.2.5 c) Local Data VAR ANQ ┆
0x43b00…43c00 (67, 0, 11) Sector 430c2300214141 ┆C # !AAER NO: VUS RESP MSG TYPE; Q OP.PARA1 NE P VDUP ACK OR P SC COM ACK? VUS DISMANTLE (ANQ QEL)(4.1.5.3) CASE RETURN (ANQ.QEL (CC):ERROR OK ERROR? ANALYZE ERROR(CC,0) OK? END CASE END CASE Fig.┆
0x43c00…43d00 (67, 0, 12) Sector 430dff00214141 ┆C !AA 1 4.2.2.4.2.5 Module Design The input in the Answer Queue is validated. If no input is expected then a queue error is reported, otherwise the input is validated. For each pending o┆
0x43d00…43e00 (67, 0, 13) Sector 430eff00214141 ┆C !AAperation it is validated whether the main type and sub-type is within the allowed range. If an invalid entry is found then a response message and the current menu will be displayed. If an acknowledge is received then a response message is display┆
0x43e00…43f00 (67, 0, 14) Sector 430f6f00214141 ┆C o !AAed and VUS SEQUENCE is entered. If a CIF is received then it is opened and VUS SEQUENCE is entered. FERENCE refer CPS/DBD/001 VCO CMD refer 4.1.4 UFCO CMD refer 4.1.4 IDENT TYPE refer 4.1.4 EXC DONE refer 4.1.4 EXIT LAB refer 4.2.2.5┆
0x43f00…44000 (67, 0, 15) Sector 4300ff00214141 ┆C !AA 1 ANQ PROC ANQ OP.PARA 1 EQ NO PENDING? VUS QUEUE ERROR (CONT)(4.1.5.2) VALIDATE ANQ INPUT(-3) RETURN CC = DONE CASE CC OF ANQ CC A QER? VUS QUEUE ERROR(C┆
0x44000…44100 (68, 0, 0) Sector 44013800214141 ┆D 8 !AA Fig. 4.2.2.4.1.3-3 KEYS (4.2.2.6.33) USER ON LOOP (-5) Fig. 4.2.2.4.1-4 ETR OP refer 4.1.4 ANQ OP(M) refer 4.1.4 FC KEY OP(M) refer 4.1.4 VCO OP(M) refer 4.1.4 UFCO OP(M) refer┆
0x44100…44200 (68, 0, 1) Sector 44024a00214141 ┆D J !AA 1 USER ON LOOP WAIT OPSEM(VUS S2)(VUS OP): OK CASE VUS OP. ID OF IDENT TYPE VCO ID? CANCEL ANQ INPUT(4.2.2.4.1.3.1) CANCEL FC KEY IN-PUT(4.2.2.4.1.3.4) C┆
0x44200…44300 (68, 0, 2) Sector 4403ff00214141 ┆D !AA 1 CANCEL FC KEY INPUT CANCEL SYSCALL (FC KEY OP):OK CASE WAIT SYSTEM CALL (FC KEY OP)(FC KEY,CC):ERROR OK ERROR? CASE ANALYZE ERROR (CC,2,CANCELLED,VDU SPLIT FAILED)┆
0x44300…44400 (68, 0, 3) Sector 44046e00214141 ┆D n !AA:(L1,L2) L1? L2? END CASE OK? END CASE Fig. 4.2.2.4.1.3-4 WAIT OPSEM(VUS S2)(VCO-PTR):OK CASE VCO PTR.ID OF IDENT TYPE VCO ID? CASE VCO CMD PROCESSING (VCO PTR):EXIT LAB(4.2.2.4.5) ┆
0x44400…44500 (68, 0, 4) Sector 4405ff00214141 ┆D !AA 1 4.2.2.4.2 VUS ANSWER Q PROCESSING 4.2.2.4.3.1 Functional Specification The purpose of this module is to receive items placed in the Answer Queue, analyse the in-put and call V┆
0x44500…44600 (68, 0, 5) Sector 4406ff00214141 ┆D !AAUS SEQUENCE(4.2.2.4.10) 4.2.2.4.2.2 Module Interface Call Specification a) ANQ PROC():EXC DONE b) ANQ PROC (R6) Register Convention Call Registers R6 LINK (DEST) Return Registers R0 - R7 (DEST) 4.2.2.4.2.3 Module Component ┆
0x44600…44700 (68, 0, 6) Sector 44077100214141 ┆D q !AA 4.2.2.4.2.3.1 Delete Append CIF The referenced CIF is looked up in the Response queue and dismantled OF IDENT TYPE VDIA ID? VDIA CC PROCESSING (VUS OP)(4.2.2.4.6) RETR ID? RETR OF PROCESSING (VUS OP)(4.2.2.4.7) ANG ID? CASE WAI┆
0x44700…44800 (68, 0, 7) Sector 4308ff00214141 ┆C !AA 1 4.2.2.4.2.4 Data Description a) Data References VUS CO OP TYPE refer 4.1.4 QEL ATTRIBUTES refer CPS/DBD/001 QEL REFERENCE refer CPS/DBD/001 SEQ CODE TYPE refer 4.1.4 QU┆
0x44800…44900 (68, 0, 8) Sector 4409ff00214141 ┆D !AA KEY ID? CASE WAIT SYSTEM CALL(FC KEY OP) (FC KEY, CC):ERROR OK ERROR? CASE ANALYZE ERROR(CC,1,SPLIT FAILED):(LA1) LA1? SPLIT FAILED=TRUE END CASE OK? FC KEY VALIDATION (FC KEY)(4.2.2.4.4) SEC FAILED EQ TRUE? ┆
0x44900…44a00 (68, 0, 9) Sector 440aad00214141 ┆D - !AA SPLIT FAILED EQ TRUE? REQUEST FC KEY INPUT (4.2.2.4.1.3.3) END CASE OTHERWISE? VUS INTERNAL ERROR(GIVE UP) (4.1.5.2) END CASE Fig. 4.2.2.4.1-6 EQ REL MENU RECV PREP? SEQ FORMAT= SEQ PREP MENU OTHERWISE? SEQ FORMAT= ┆
0x44a00…44b00 (68, 0, 10) Sector 440bff00214141 ┆D !AA 1 CANCEL ANQ INPUT CANCEL SYS CALL (ANQ OP):OK CASE WAIT SYSTEM CALL(ANQ OP) (VUS QEL.ATTR,ANQ QEL,QUEUE,CC):ERROR OK ERROR? CASE ANALYZE ERROR(CC,1, CANCELLED)(LA1) ┆
0x44b00…44c00 (68, 0, 11) Sector 440cff00214141 ┆D !AALA1? END CASE OK? ANQ OP.PARA1 NE P VDUP ACK OR P SC COM ACK? VUS DISMANTLE (ANQ QEL)(4.1.5.3) CASE RETURN (ANQ.QEL (CC):ERROR OK ERROR? ANALYZE ERROR(CC,0) OK? END CASE END CASE Fig.┆
0x44c00…44d00 (68, 0, 12) Sector 440d1600214141 ┆D !AA 4.2.2.4.1.3-1 REMOVE ANQ ITEMS VUS QNAME.MAIN = VUS ARRQ VUS QNAME.SUB = ANS SUBQ REMOVE LOOP CASE RECEIVE FIRST QEL(NO WAIT,VUS QNAME) (VUS RECV ATTR,RECV QEL,QUEUE,CC):ERROR OK ┆
0x44d00…44e00 (68, 0, 13) Sector 440eff00214141 ┆D !AA 1 REQUEST ANQ INPUT VUS QNAME.MAIN = VUS ARRQ VUS QNAME.SUB = ANS SUBSQ CASE INIT RECEIVE FIRST QEL(WAIT,VUS QNAME,ANQ OP) (CC):ERROR OK ERROR? ANALYZE ERROR(CC,0) ┆
0x44e00…44f00 (68, 0, 14) Sector 440f6b00214141 ┆D k !AA OK? ASSOCIATE (VUS-S2,ANQ OP):OK END CASE Fig. 4.2.2.4.1.3-2 E REFERENCE refer CPS/DBD/001 VCO CMD refer 4.1.4 UFCO CMD refer 4.1.4 IDENT TYPE refer 4.1.4 EXC DONE refer 4.1.4 EXIT LAB refer 4.2.2.5┆
0x44f00…45000 (68, 0, 15) Sector 4400ff00214141 ┆D !AA 1 REQUEST FC KEY INPUT CASE INIT RECEIVE CONTROL(SPLIT DIGIT,FC KEY OP) (CC):ERROR OK ERROR? ANALYZE ERROR(CC,0) OK? ASSOCIATE (VUS S2,FC KEY OP):OK END CASE ┆
0x45000…45100 (69, 0, 0) Sector 45018e00214141 ┆E !AA REQUEST FC KEY INPUT(4.2.2.4.1.3.3) ENABLE FC KEYS (4.2.2.6.33) USER ON LOOP (-5) Fig. 4.2.2.4.1-4 ETR OP refer 4.1.4 ANQ OP(M) refer 4.1.4 FC KEY OP(M) refer 4.1.4 VCO OP(M) refer 4.1.4 UFCO OP(M) refer┆
0x45100…45200 (69, 0, 1) Sector 4502ff00214141 ┆E !AA 1 USER ON LOOP WAIT OPSEM(VUS S2)(VUS OP): OK CASE VUS OP. ID OF IDENT TYPE VCO ID? CANCEL ANQ INPUT(4.2.2.4.1.3.1) CANCEL FC KEY IN-PUT(4.2.2.4.1.3.4) C┆
0x45200…45300 (69, 0, 2) Sector 4503ff00214141 ┆E !AAASE VCO CMD PROCESSING (VUS OP) :EXIT LAB(4.2.2.4.5) E USER? EXIT USER ON LOOP E START? EXIT START LOOP END CASE OTHERWISE? ANALYSE SEMAPHORE INPUT (-6) END CASE SEC FAILED EQ FALSE? VDU FAILED EQ FALS┆
0x45300…45400 (69, 0, 3) Sector 4504ff00214141 ┆E !AAE? CANCEL ANQ INPUT (4.2.2.4.1.3.1) CANCEL FC KEY INPUT(4.2.2.4.1.3.4) FAIL LOOP WAIT OPSEM(VUS S2)(VCO-PTR):OK CASE VCO PTR.ID OF IDENT TYPE VCO ID? CASE VCO CMD PROCESSING (VCO PTR):EXIT LAB(4.2.2.4.5) ┆
0x45400…45500 (69, 0, 4) Sector 4505ff00214141 ┆E !AA E USER? EXIT USER ON LOOP E START? EXIT START LOOP END CASE VDIA ID? FREE SFCO OP(VDO PTR)(4.2.2.6.32) OTHERWISE? VUS INTERNAL ERROR (GIVE UP)(4.1.5.2) END CASE END FAIL LOOP END USER ON LOOP F┆
0x45500…45600 (69, 0, 5) Sector 45061600214141 ┆E !AAig. 4.2.2.4.1-5 ich are taken over for further treatment. Ststem errors will be treated by the Error Reporting Procedure, which is common `to all modules within VUP. nd Present next (4.3.4) This function returns a CIF to the queue from which┆
0x45600…45700 (69, 0, 6) Sector 4507ff00214141 ┆E !AA 1 ANALYSE SEMAPHORE INPUT CASE VUS OP.ID OF IDENT TYPE VDIA ID? VDIA CC PROCESSING (VUS OP)(4.2.2.4.6) RETR ID? RETR OF PROCESSING (VUS OP)(4.2.2.4.7) ANG ID? CASE WAI┆
0x45700…45800 (69, 0, 7) Sector 4408ff00214141 ┆D !AAT SYSTEM CALL(ANQ OP) (VUS QEL ATTR,ANQ QEL,QUEUE,CC):ERROR OK ERROR? ANALYZE ERROR(CC,0) OK? CASE ANQ PROC(): EXC DONE(4.2.2.4.2) EXP? DONE? REQUEST ANQ INPUT(4.2.2.4.1.3.2) END CASE END CASE FC┆
0x45800…45900 (69, 0, 8) Sector 45098800214141 ┆E !AA.2) END CASE END START LOOP CLOSE LOOP WAIT OPSEM(VUS S2)(VUS OP):OK END CLOSE LOOP Fig. 4.2.2.4.1-1 start command is received. The module receives commands and completions codes from the other coroutines and validate┆
0x45900…45a00 (69, 0, 9) Sector 450aff00214141 ┆E !AA 1 START ACTIONS REMOVE ANQ ITEMS (-3) CASE INIT AREA.CURRENT USER CAP RELS ONLY? SEQ FORMAT= SEQ REL MENU RECV PREP? SEQ FORMAT= SEQ PREP MENU OTHERWISE? SEQ FORMAT= ┆
0x45a00…45b00 (69, 0, 10) Sector 450bff00214141 ┆E !AASEQ USER MENU END CASE SEQ CODE=SEQ START VUS SEQUENCE(4.2.2.4.10) WAIT OPSEM(VUS S2)(VDIA PTR):OK CASE VDIA PTR.ID OF IDENT TYPE VDIA ID? FREE SFCO OP(4.2.1.1.6.32) VDIA PTR.CMD EQ EXP VDIA CMD? START COMP(-4) VUS INTERNAL ERROR (┆
0x45b00…45c00 (69, 0, 11) Sector 450c7b00214141 ┆E { !AAGIVE UP) (4.1.5.2) OTHERWISE? VUS INTERNAL ERROR (GIVE UP) (4.1.5.2) END CASE Fig. 4.2.2.4.1-2 ANCEL ANQ INPUT An outstanding INIT RECEIVE is cancelled. If the operation is in semaphore and a SCARS/CCIS acknowledge is pendin┆
0x45c00…45d00 (69, 0, 12) Sector 450dff00214141 ┆E !AA 1 REMOVE ANQ ITEMS VUS QNAME.MAIN = VUS ARRQ VUS QNAME.SUB = ANS SUBQ REMOVE LOOP CASE RECEIVE FIRST QEL(NO WAIT,VUS QNAME) (VUS RECV ATTR,RECV QEL,QUEUE,CC):ERROR OK ┆
0x45d00…45e00 (69, 0, 13) Sector 450eff00214141 ┆E !AA ERROR? CASE ANALYZE ERROR(CC,2,QEL PROFILE CHECK, QUEUE EMPTY):(LA1,LA1) LA1? VUS DISMANTLE(RECV QEL)(4.1.5.3) LA2? EXIT REMOVE LOOP END CASE OK? VUS DISMANTLE(RECV QEL)(4.1.5.3) END CASE END REMO┆
0x45e00…45f00 (69, 0, 14) Sector 450f3400214141 ┆E 4 !AAVE LOOP Fig. 4.2.2.4.1-3 001 USER FCT CAPABILITY TYPE refer CPS/DBD/001 QUEUE REFERENCE refer CPS/DBD/001 VCO CMD refer 4.1.4 UFCO CMD refer 4.1.4 IDENT TYPE refer 4.1.4 EXC DONE refer 4.1.4 EXIT LAB refer 4.2.2.5┆
0x45f00…46000 (69, 0, 15) Sector 4500ff00214141 ┆E !AA 1 START COMP VCO PTR.ID = UFCO ID VCO PTR.PARA 1 =VDIA PTR.PARA 1 SIGNAL OPSEM(VUS S1,VCO PTR):OK VCO PTR.PARA 1 EQ ERROR CC OR SPLIT FAILED CC? REQUEST ANQ INPUT( 4.2.2.4.1.3.2)┆
0x46000…46100 (70, 0, 0) Sector 4601ff00214141 ┆F !AA 1 b) External Data VUS S1 refer 4.1.4 VUS-S2 refer 4.1.4 RETR OP refer 4.1.4 ANQ OP(M) refer 4.1.4 FC KEY OP(M) refer 4.1.4 VCO OP(M) refer 4.1.4 UFCO OP(M) refer┆
0x46100…46200 (70, 0, 1) Sector 4602ff00214141 ┆F !AA 4.1.4 INIT AREA refer 4.1.4 ANQ QEL(M) refer.4.1.4 RECV QEL(M) refer 4.1.4 VUS QNAME (M) refer 4.1.4 VUS QEL ATTR(M) refer 4.1.4 VUS ARRQ(M) refer 4.1.4 ANQ SUBQ refer 4.1.4 SPLIT FAILED refer 4.2.2.5 SEC FAILED refer 4.2.2.5 SP┆
0x46200…46300 (70, 0, 2) Sector 4603a700214141 ┆F ' !AALIT DIGIT refer 4.2.2.5 FC KEY refer 4.2.2.5 EXP VDIA CMD refer 4.2.2.5 SEQ FORMAT(M) refer 4.2.2.5 SEQ CODE(M) refer 4.2.2.5 c)Local Data None the data flow of UFCO. 4.2.2.3.2 Control Logic The control logic of UFCO is shown i┆
0x46300…46400 (70, 0, 3) Sector 4604ff00214141 ┆F !AA 1 4.2.2.4.1.5 Module Design Commands received from VCO or VDIA are analysed. The following actions are taken: If a CLOSE DOWN is received before a user has signed on then the CLO┆
0x46400…46500 (70, 0, 4) Sector 4605ff00214141 ┆F !AASE LOOP is entered. Two system call is performed in order to open for in-p`ut from Answer Queue and F/C key. Unknown QEL from Answer Q is sent to SSC. A loop is entered in order to distribute in-put from Answer Queue, F/C keys, VCO,VDIA and RE┆
0x46500…46600 (70, 0, 5) Sector 4606b100214141 ┆F 1 !AATR to modules which are taken over for further treatment. Ststem errors will be treated by the Error Reporting Procedure, which is common `to all modules within VUP. nd Present next (4.3.4) This function returns a CIF to the queue from which┆
0x46600…46700 (70, 0, 6) Sector 4607ff00214141 ┆F !AA 1 UFCO START START LOOP WAIT OPSEM (VUS S2)(VCO PTR):OK CASE VCO PTR.ID OF IDENT TYPE VCO ID? CASE VDO PTR.CMD OF VCO CMD CLOSE UFCO? VCO.PTR.ID=UFCO ID VCO PT┆
0x46700…46800 (70, 0, 7) Sector 4508ff00214141 ┆E !AAR.PARA1 = OK CC SIGNAL OPSEM(VUS S1,VCO PTR),:OK EXIT START LOOP START UFCO? START ACTIONS (-2) OTHERWISE? VUS INTERNAL ERROR(GIVEUP)(4.1.5.2) END CASE OTHERWISE? VUS INTERNAL ERROR(GIVE UP)(4.1.5┆
0x46800…46900 (70, 0, 8) Sector 4609ff00214141 ┆F !AAation This module is the main module within UFCO. If awaits commands from VCO in semaphore S1 and enters the USER ON loop when a start command is received. The module receives commands and completions codes from the other coroutines and validate┆
0x46900…46a00 (70, 0, 9) Sector 460aff00214141 ┆F !AAs the input. Furthermore F/C-key interrupts and Answer Queue input is treated by this module. 4.2.2.4.1.2 Module Interface Call Specification a) UFCO MAIN b) UFCO MAIN (R6) Register Convention Call Register R6 LINK (DEST) Return┆
0x46a00…46b00 (70, 0, 10) Sector 460b2500214141 ┆F % !AA Register R0 - R7 (DEST) etrieved CIF and/or a response message is displayed. e) Print (4.4.5) The CIF currently displayed on the VDU is sent to the associated printer, or the atomal printer. f) Defer (4.4.6) The preparation is termi┆
0x46b00…46c00 (70, 0, 11) Sector 460cff00214141 ┆F !AA 1 4.2.2.4.1.3 Module Components 4.2.2.4.1.3.1 CANCEL ANQ INPUT An outstanding INIT RECEIVE is cancelled. If the operation is in semaphore and a SCARS/CCIS acknowledge is pendin┆
0x46c00…46d00 (70, 0, 12) Sector 460dff00214141 ┆F !AAg, then the QEL will be returned to the queue. Refer figure. 4.2.2.4.1.3-1 4.2.2.4.1.3.2 REQUEST ANQ INPUT Sets up an INIT RECEIVE on the Answer queue. Refer figure 4.2.2.4.1.3-2 4.2.2.4.1.3.3 REQUEST FC KEY INPUT Sets upon INIT RECEIVE ┆
0x46d00…46e00 (70, 0, 13) Sector 460eff00214141 ┆F !AACONTROL on the current VDU-split Refer figure 4.2.2.4.1.3-3 4.2.2.4.1.3.4 CANCEL FC KEY INPUT Cancels a previous set-up INIT RECEIVE CONTROL Refer figure. 4.2.2.4.1.3-4 4.2.2.4.1.4 Data Description a) Data References QEL ATTRIBUTES re┆
0x46e00…46f00 (70, 0, 14) Sector 460fff00214141 ┆F !AAfer CPS/DBD/001 QEL REFERENCE refer CPS/DBD/001 USER FCT CAPABILITY TYPE refer CPS/DBD/001 QUEUE REFERENCE refer CPS/DBD/001 VCO CMD refer 4.1.4 UFCO CMD refer 4.1.4 IDENT TYPE refer 4.1.4 EXC DONE refer 4.1.4 EXIT LAB refer 4.2.2.5┆
0x46f00…47000 (70, 0, 15) Sector 46006100214141 ┆F a !AA ANQ PENDING refer 4.2.2.5 SEQ FORMAT TYPE refer 4.2.2.5 SEQ CODE TYPE refer 4.2.2.5 operation semaphore S2 as the main waiting point. The input to UFCO will be a command which is received from VCO, VDIA, RETR, the answer queue or the VDU. ┆
0x47000…47100 (71, 0, 0) Sector 4701cf00214141 ┆G O !AA Each command will constitute a main function and is, as well as major function, implemented as a module. Furthermore some common procedures and module components exist. Refer figure 4.2.2.2.1-2. .1.6) These functions determine the format wh┆
0x47100…47200 (71, 0, 1) Sector 47026200214141 ┆G b !AA 1 Figs. 4.2.2.2-1/2 nctions are those which must be performed when a user gives up access to a CIF. a) Dismantle CIF / Buffer (4.2.1) These functions are those used to inte┆
0x47200…47300 (71, 0, 2) Sector 4703ff00214141 ┆G !AA 1 4.2.2.3 Data Flow and Control Logic 4.2.2.3.1 Data Flow The HIPO diagrams overleaf show the data flow of UFCO. 4.2.2.3.2 Control Logic The control logic of UFCO is shown i┆
0x47300…47400 (71, 0, 3) Sector 47042d00214141 ┆G - !AAn the module-tree in figure 4.2.2.3-1. functions update the VDU header fields, classification and terminal function. ction creation group includes all the functions to be performed before a transaction may be started. a) Receive and Validate (3.1┆
0x47400…47500 (71, 0, 4) Sector 47056600214141 ┆G f !AA 1 Diag. ID: 4.2.2.3/24 4.3) The queue request functions are those concerning the reception of messages. a) Receive (4.3.1) The first CIF to which the requestor has acces┆
0x47500…47600 (71, 0, 5) Sector 47065f00214141 ┆G _ !AA 1 Fig. 4.2.2.3-1 a queue. c) Keep (4.3.3) This function returns a CIF to a queue. d) Keep and Present next (4.3.4) This function returns a CIF to the queue from which┆
0x47600…47700 (71, 0, 6) Sector 4707ff00214141 ┆G !AA 1 4.2.2.4 Module Specification UFCO MAIN (4.2.2.4.1) VUS ANSWER Q PROCESSING (4.2.2.4.2) APPEND INVESTIGATION (4.2.2.4.3) VUS F/C KEY PROCESSING (4.2.2.4.4) VCO CMD PROCESSING ┆
0x47700…47800 (71, 0, 7) Sector 4608ff00214141 ┆F !AA(4.2.2.4.5) VDIA CC PROCESSING (4.2.2.4.6) RETR OP PROCESSING (4.2.2.4.7) VUS IN/OUT LINE (4.2.2.4.8) VUS CMD PENDING (4.2.2.4.9) VUS SEQUENCE (4.2.2.4.10) EAXECUTE FUNCTION (4.2.2.4.11) 4.2.2.4.1 UFCO MAIN 4.2.2.4.1.1 Functional Specific┆
0x47800…47900 (71, 0, 8) Sector 47098100214141 ┆G !AAion created by MDP is displayed. b) Send for Release (4.4.2) The message is sent to the associated release terminal. ine. f) Execute Function Key The functions associated with the received function key are performed and the format sequenc┆
0x47900…47a00 (71, 0, 9) Sector 470aff00214141 ┆G !AA 1 c) Release (4.4.3) The message is sent for local distribution and transmission. A release notification is returned to the drafter. d) Retrieve / Append (4.4.4) A retrieve r┆
0x47a00…47b00 (71, 0, 10) Sector 470bff00214141 ┆G !AAequest is sent to SAR and the retrieved CIF and/or a response message is displayed. e) Print (4.4.5) The CIF currently displayed on the VDU is sent to the associated printer, or the atomal printer. f) Defer (4.4.6) The preparation is termi┆
0x47b00…47c00 (71, 0, 11) Sector 470cff00214141 ┆G !AAnated and the CIF is sent to the preparation database. g) Status Request (4.4.7) A status request is sent to UMAM and the received CIF is displayed. h) Send for Distribution (4.4.8) A comment is sent for local distribution. i) Edit / Del┆
0x47c00…47d00 (71, 0, 12) Sector 470d7600214141 ┆G v !AAete Requests (4.4.9) A request is sent to UMAM and the referenced CIF or a response message is displayed. cution (4.1) The start execution functions are those which must be performed before a format is presented for a user. a) Create CIF /┆
0x47d00…47e00 (71, 0, 13) Sector 470eff00214141 ┆G !AA 1 4.2.2.1.5 Error Handling The error handling function is separated into two parts: a) Q ERROR (5.1) This function handles error due to failure in communication between UFCO an┆
0x47e00…47f00 (71, 0, 14) Sector 470fff00214141 ┆G !AAd its queues and decides whether or not the processing may continue. b) Internal (5.2) This function handles errors due to failure in communication between the subpackages communicating with UFCO, and decides whether or not the processing may c┆
0x47f00…48000 (71, 0, 15) Sector 4700ff00214141 ┆G !AAontinue. 4.2.2.2 Software Structure The UFCO subpackage consists of one coroutine with operation semaphore S2 as the main waiting point. The input to UFCO will be a command which is received from VCO, VDIA, RETR, the answer queue or the VDU. ┆
0x48000…48100 (72, 0, 0) Sector 4801ff00214141 ┆H !AA 1 e) Display Error Code (4.1.5) These functions display a response message in the VDU response line. f) Determine Message Type (4.1.6) These functions determine the format wh┆
0x48100…48200 (72, 0, 1) Sector 4802ff00214141 ┆H !AAich shall be used for a message. 4.2.2.1.4.2 Stop Execution (4.2) The stop execution functions are those which must be performed when a user gives up access to a CIF. a) Dismantle CIF / Buffer (4.2.1) These functions are those used to inte┆
0x48200…48300 (72, 0, 2) Sector 4803ff00214141 ┆H !AArface to the message management system. b) Update Status (4.2.2) The outgoing message status, release message status and the delivery message status are updated. The message / comment under preparation is returned to the preparation database. ┆
0x48300…48400 (72, 0, 3) Sector 48047c00214141 ┆H | !AA c) Update VDU Header (4.2.3) These functions update the VDU header fields, classification and terminal function. ction creation group includes all the functions to be performed before a transaction may be started. a) Receive and Validate (3.1┆
0x48400…48500 (72, 0, 4) Sector 4805ff00214141 ┆H !AA 1 4.2.2.1.4.3 Queue Requests (4.3) The queue request functions are those concerning the reception of messages. a) Receive (4.3.1) The first CIF to which the requestor has acces┆
0x48500…48600 (72, 0, 5) Sector 4806ff00214141 ┆H !AAs is received from a given queue. b) Delete (4.3.2) This function removes a CIF from a queue. c) Keep (4.3.3) This function returns a CIF to a queue. d) Keep and Present next (4.3.4) This function returns a CIF to the queue from which┆
0x48600…48700 (72, 0, 6) Sector 4807ff00214141 ┆H !AA it was received. The next CIF to which the requestor has access is returned. e) Delete and Present next (4.3.5) This function removes a CIF from the queue from which it was received. The next CIF to which the requestor has access is returned. ┆
0x48700…48800 (72, 0, 7) Sector 4708ff00214141 ┆G !AA 4.2.2.1.4.4 Requests to CAMPS System (4.4) The request functions are those concerning the treatment of messages (CIFs) and requests (buffers). a) Send for Coordination (4.4.1) The message is sent for coordination and the delivery notificat┆
0x48800…48900 (72, 0, 8) Sector 4809ff00214141 ┆H !AA the correct range. e) Display Response Message (3.5) These functions display a response message in the VDU response line. f) Execute Function Key The functions associated with the received function key are performed and the format sequenc┆
0x48900…48a00 (72, 0, 9) Sector 480aff00214141 ┆H !AAe is changed. g) Execute Command (3.7) The sequence table key is looked up in the command validation table and the format sequence is started. h) Assign Transaction Number (3.8) Allocates next transaction no. for this terminal. 4.2.2.1.4┆
0x48a00…48b00 (72, 0, 10) Sector 480be100214141 ┆H a !AA Format Sequence Function (4.0) The format sequence functions are those functions which are called from the format sequence table. This table makes it possible to drive the MMI in an automatic and flexible manner. .!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x48b00…48c00 (72, 0, 11) Sector 480cff00214141 ┆H !AA 1 It defines for each screen format: - Allowed commands and function keys - Functions to be called corresponding to commands/F/C Keys - LOG, STATISTICS, SAR reporting required ┆
0x48c00…48d00 (72, 0, 12) Sector 480dff00214141 ┆H !AA - Cursor position - Command to VDIA - Subsequently sequence record to be executed 4.2.2.1.4.1 Start Execution (4.1) The start execution functions are those which must be performed before a format is presented for a user. a) Create CIF /┆
0x48d00…48e00 (72, 0, 13) Sector 480eff00214141 ┆H !AABuffer (4.1.1) These functions are those used to interface to the message management system. b) Request CIF (4.1.2) If a continue preparation command is received, then the referenced CIF is fetched from the preparation database. If a rece┆
0x48e00…48f00 (72, 0, 14) Sector 480fff00214141 ┆H !AAive command is received, then the first CIF in the corresponding queue is fetched. c) Update VDU Header (4.1.3) These functions update the VDU header fields, classification and terminal function. d) Complete Append (4.1.4) These functions ┆
0x48f00…49000 (72, 0, 15) Sector 4800a100214141 ┆H ! !AAadd a section of another message to a message under preparation. It shall be noticed that an off-line append can result in two security interrogations. ...... 4.2.2.4.3.4 Data Description .......... 4.2.2.4.3.5 Module Desi┆
0x49000…49100 (73, 0, 0) Sector 4901ff00214141 ┆I !AA 1 4.2.2.1.2 Transaction Accounting (2.0) The transaction accounting functions are those concerning log and statistics. a) Collect Data (2.1) The data which are used for log, st┆
0x49100…49200 (73, 0, 1) Sector 4902ff00214141 ┆I !AAatistics and other purposes are collected in sequence table. There exists no special collecting procedures but all data which are pertinent for UFCO will be placed in this area. b) Log Reporting (2.2) The log reporting functions are those requi┆
0x49200…49300 (73, 0, 2) Sector 4903ff00214141 ┆I !AAred to report final log records. The data which are required in a log record are extracted from the sequence table. c) Statistics Reporting (2.3) The statistics reporting functions are those required to report statistics. The data which are ┆
0x49300…49400 (73, 0, 3) Sector 4904ff00214141 ┆I !AArequired in the statistics are extracted from the sequence table. 4.2.2.1.3 Transaction Creation (3.0) The transaction creation group includes all the functions to be performed before a transaction may be started. a) Receive and Validate (3.1┆
0x49400…49500 (73, 0, 4) Sector 4905ff00214141 ┆I !AA) Function keys entered by a user are received from the VDU. The received function key is validated against a function key bit mask. There are two bit masks. Bit mask (1) reflects the function keys which are allowed at the moment. Bit ma┆
0x49500…49600 (73, 0, 5) Sector 49065000214141 ┆I P !AAsk (2) reflects the function keys which will change the format sequence. 4.2.2.4.7 RETR OP PROCESSING ............ 4.2.2.4.7.1 Functional Specifica┆
0x49600…49700 (73, 0, 6) Sector 4907ff00214141 ┆I !AA 1 b) Define Next Function Key (3.2) If a function key must be followed by another, this is defined (i.e. RETURN shall follow COMMAND). c) Receive Command Line (3.3) The conte┆
0x49700…49800 (73, 0, 7) Sector 4808ff00214141 ┆H !AAnts of the VDU command line are received via the format handler. d) Validate Command Line (3.4) The contents of the command line are validated. A command is validated against the command validation table. Parameters are checked to be within┆
0x49800…49900 (73, 0, 8) Sector 4909ff00214141 ┆I !AA the VDU dialogue. 4.2.2.1 Functional Specification The following functions are included in this subpackage: - System control - Transaction accounting - Transaction creation - Format sequence functions - Error Handling Fig. 4.2.2.1-┆
0x49900…49a00 (73, 0, 9) Sector 490a2b00214141 ┆I + !AA1 presents the functional breakdown. ┆
0x49a00…49b00 (73, 0, 10) Sector 490b6000214141 ┆I ` !AA 1 Figs. 4.2.2.1-1/5 20505 USER 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┆
0x49b00…49c00 (73, 0, 11) Sector 490cff00214141 ┆I !AA 1 4.2.2.1.1 System Control (1.0) The system control functions are those which indirectly involve the SSC package. The commands are received from VCO. a) Initialization (1.1) Ex┆
0x49c00…49d00 (73, 0, 12) Sector 490dff00214141 ┆I !AAecutes the function to be performed after load of software and which must be executed before normal operation can be initiated. Depending on the type of initialization, different actions are taken. An initialization command is sent to VDIA. b) ┆
0x49d00…49e00 (73, 0, 13) Sector 490eff00214141 ┆I !AAStart-Up (1.2) Executes the function to be performed after sign-on. The command validation table reflecting the user capability is defined. c) Close-Down (1.3) This function provides the UFCO with the capability of performing the following f┆
0x49e00…49f00 (73, 0, 14) Sector 490fff00214141 ┆I !AAunctions: - Sign-off - Block terminal - Order close-down. d) Security Interrogation (1.4) Requests a security interrogation to be performed in case of release. Executes the functions to be performed after a security interrogation (e.g┆
0x49f00…4a000 (73, 0, 15) Sector 49002100214141 ┆I ! !AA. receive function keys). 1 Functional Description .... 4.2.2.4.3.2 Module Interface .......... 4.2.2.4.3.3 Module Components ......... 4.2.2.4.3.4 Data Description .......... 4.2.2.4.3.5 Module Desi┆
0x4a000…4a100 (74, 0, 0) Sector 4a01ff00214141 ┆J !AAgn ............. 4.2.2.4.4 VUS F/C KEY PROCESSING ......... 4.2.2.4.4.1 Functional Specification .. 4.2.2.4.4.2 Module Interface ........... 4.2.2.4.4.3 Module Components ......... 4.2.2.4.4.4┆
0x4a100…4a200 (74, 0, 1) Sector 4a02ff00214141 ┆J !AA Data Description .......... 4.2.2.4.4.5 Module Design ............. 4.2.2.4.5 VCO CMD PROCESSING ............ 4.2.2.4.5.1 Functional Specification .. 4.2.2.4.5.2 Module Interface .......... ┆
0x4a200…4a300 (74, 0, 2) Sector 4a03ff00214141 ┆J !AA 4.2.2.4.5.3 Module Component .......... 4.2.2.4.5.3.1 STOP ACTION ........... 4.2.2.4.5.4 Data Description ........ 4.2.2.4.5.5 Module Design ........... 4.2.2.4.6 VDIA CC PROCESSING ...........┆
0x4a300…4a400 (74, 0, 3) Sector 4a04ff00214141 ┆J !AA. 4.2.2.4.6.1 Functional Specification .. 4.2.2.4.6.2 Module Interface .......... 4.2.2.4.6.3 Module Component ......... 4.2.2.4.6.4 Data Description .......... 4.2.2.4.6.5 Module Design .┆
0x4a400…4a500 (74, 0, 4) Sector 4a051800214141 ┆J !AA............ INVERT AND BELL HEADER ADDRESS.LINE = QUEUE LINE NO HEADER ADDRESS.INCARNATION = HEADER.INCARNATION NO CASE VUS QEL ATTR. FLAG VALUE OF FLASH QUEUE TYPE RECVQ? - HEADER ADD┆
0x4a500…4a600 (74, 0, 5) Sector 4a06ff00214141 ┆J !AA 1 4.2.2.4.7 RETR OP PROCESSING ............ 4.2.2.4.7.1 Functional Specifica┆
0x4a600…4a700 (74, 0, 6) Sector 4a07e400214141 ┆J d !AAtion ... 4.2.2.4.7.2 Module Interface ........... 4.2.2.4.7.3 Module Component ........... 4.2.2.4.7.4 Data Description ........... 4.2.2.4.7.5 Module Design .............. ' *J B 9 _┆
0x4a700…4a800 (74, 0, 7) Sector 4908ff00214141 ┆I !AA 1 4.2.2 User Function Control Subpackage The User Function Control (UFCO) subpackage performs the control of all user transactions. Furthermore, UFCO performs the direct control of┆
0x4a800…4a900 (74, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(74,0, 9), len=0xff, h3=41214141}, f00=»2141A «, f01=»CPS/SDS/039 «, f02=»ja/vhn/rt «, f03=»JBS «, f04=»4.2.2 «, f05=10-05-82 14:33, f06=» 12 «, f07=»55 «, f08=» 44047 «, f09=17-05-82 15:41, f10=» «, f11=»10 «, f12=» 66 «, f13=18-05-82 08:22, f14=18-05-82 08:48, f15=»0170A «, f16=» 80 «, f17=» 16 «, f18=»40 «, f19=» 924 «, f20=» 46840 «, f21=» «, f22=» 0 «, f99=530010000110052710110280aaca15050000000000000142031a01df}
0x4a900…4aa00 (74, 0, 9) Sector 4a0a5000214141 ┆J P !AA J J J J I I I I H H H G G G G G G G F F F F E E E E E D D D D D D D C C C B B B B B A A A A A @ @ @ @ @ ? ? ? ? ? > > > > = = = = < < < < < ; ; ; ; : : : : : 9 9 DOKUMENTOVERSIGT Dokument nr: DoDoDo┆
0x4aa00…4ab00 (74, 0, 10) Sector 4a0b9e00214141 ┆J !AA 1 CPS/SDS/039 820505 USER 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┆
0x4ab00…4ac00 (74, 0, 11) Sector 4a0cff00214141 ┆J !AA 1 1 4.2.2.4.1.1 Fun┆
0x4ac00…4ad00 (74, 0, 12) Sector 4a0dff00214141 ┆J !AActional Specification ... 4.2.2.4.1.3.1 CANCEL ANQ IN-PUT...... 4.2.2.4.1.3.2 REQUEST ANQIN-PUT........ 4.2.2.4.1.3.3 REQUEST FC KEY IN-PUT.. 4.2.2.4.1.3.4 CANCEL FC KEY IN-PUT.. 4.2.2.4.┆
0x4ad00…4ae00 (74, 0, 13) Sector 4a0eff00214141 ┆J !AA1.4. Data Description.......... 4.2.2.4.1.5 Module Design .............. 4.2.2.4.2 VUS ANSER Q PROCESSING ......... 4.2.2.4.2.1 Functional Specification .. 4.2.2.4.2.2 Module Interface ........... ┆
0x4ae00…4af00 (74, 0, 14) Sector 4a0fff00214141 ┆J !AA 4.2.2.4.2.3 Module Component ........... 4.2.2.4.2.3.1 Delete Append CIF ...... 4.2.2.4.2.4 Data Description ........... 4.2.2.4.2.5 Module Design .............. 4.2.2.4.3 Append Investigation .....┆
0x4af00…4b000 (74, 0, 15) Sector 4a00ff00214141 ┆J !AA..... 4.2.2.4.3.1 Functional Description .... 4.2.2.4.3.2 Module Interface .......... 4.2.2.4.3.3 Module Components ......... 4.2.2.4.3.4 Data Description .......... 4.2.2.4.3.5 Module Desi┆
0x4b000…4b100 (75, 0, 0) Sector 4b01ff00155341 ┆K SAnctions of UFCO and VDIA have been assigned separate coroutines to decrease the complexity of the software. When a user transaction is in progress, UFCO software shall only take care of transaction interruption while all formatting and I/O transfer ┆
0x4b100…4b200 (75, 0, 1) Sector 4b02ff00155341 ┆K SAinitiation / awaiting is performed by VDIA. UFCO is assigned a higher priority than VDIA. 4.1.2.1.1.3 VDU Dialogue Coroutine The VDU dialogue (VDIA) coroutine is responsible for the VDU format transformation of input and output and for validati┆
0x4b200…4b300 (75, 0, 2) Sector 4b03ff00155341 ┆K SAon of user input. 4.1.2.1.1.4 Retrieve Coroutine The Retrieve (RETR) Coroutine is responsible for reception and treatment of retrieval answers from SAR. The functions of RETR have been assigned to a separate coroutine, due to the fact that t┆
0x4b300…4b400 (75, 0, 3) Sector 4b04ff00155341 ┆K SAhe function may be performed even when the other coroutines have been stopped after user sign-off. Furthermore, the function of the RETR may be considered as low priority tasks, having in mind that during on-line retrieval all the other coroutines a┆
0x4b400…4b500 (75, 0, 4) Sector 4b05b700155341 ┆K 7 SAssociated with user transaction processing (UFCO, VDIA) will await input from RETR, thereby allowing RETR to be processing. RETR is assigned the lowest priority within VUS. n of functions onto processes and coroutines will be explained, based on┆
0x4b500…4b600 (75, 0, 5) Sector 4b06ff00155341 ┆K SA 1 4.1.2.2 UMAM Process The UMAM process controls the access to the preparation database and maintains the Outgoing Message Status, the Release Status, the Delivery Status and the Se┆
0x4b600…4b700 (75, 0, 6) Sector 4b07ff00155341 ┆K SArvice Message Status for each VDU and printer. In figure 4.1.2.1-2 an overview of the UMAM process is shown. The functions of UMAM have been allocated their own process for the following reasons: a) To keep security access control as simple an┆
0x4b700…4b800 (75, 0, 7) Sector 3808ff00155341 ┆8 SAd tight as possible. b) To minimize the damage caused by system malfunction. With reference to the analysis in 4.1.1.4.1 this means that the solution where the releaser process queues a request for removing or changing items is not chosen. Note th┆
0x4b800…4b900 (75, 0, 8) Sector 4b097100155341 ┆K q SA 1 Fig. 4.1.2.1-1 VUS Structure 3*$<MMY *%<MMY !\<6 C 3M, !\<6 : =~ B 5: = 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 ! ┆
0x4b900…4ba00 (75, 0, 9) Sector 4b0aff00155341 ┆K SA 1 4.1.2.1.1 VUS Coroutines The VDU USER PROCESS consists of four coroutines: - the VDU Control Coroutine - the User Function Control Coroutine - the VDU Dialogue Coroutine - t┆
0x4ba00…4bb00 (75, 0, 10) Sector 4b0bff00155341 ┆K SAhe Retrieve Coroutine. In figure 4.1.2.1-1 an overview of VUS is depicted. 4.1.2.1.1.1 VDU Control Coroutine The VDU Control (VCO) Coroutine is the controlling coroutine, controlling the start / stop of the processing of all the other corout┆
0x4bb00…4bc00 (75, 0, 11) Sector 4b0cff00155341 ┆K SAines. VCO is responsible for the execution of commands received from TEMCO, e.g initialize, close down, restart, start/stop, for VDU Header queue status update and that no message is kept longer in a Flash precedence queue than allowed by the supe┆
0x4bc00…4bd00 (75, 0, 12) Sector 4b0dff00155341 ┆K SArvisor. During the analysis it was found that TEMCO Control Functions and Queue Status Maintenance functions were to be executed with higher priority than User Transaction Control Functions. Thus these two functions have been allocated their own c┆
0x4bd00…4be00 (75, 0, 13) Sector 4b0eff00155341 ┆K SAoroutine named VDU CONTROL COROUTINE (VCO). The VCO coroutine shall be asssigned the highest priority among the coroutines of VUS, meaning that whenever VCO and other VUS coroutines are ready to run, VCO shall be allowed to run first. 4.1.2.1.1┆
0x4be00…4bf00 (75, 0, 14) Sector 4b0f9100155341 ┆K SA.2 User Function Control Coroutine The User Function Control (UFCO) Coroutine performs the direct control of the VDU Dialogue Coroutine. 02 59 25 05 82 14 10 26 05 82 14 14 0170A 113 39 41 1096 90316 0 # ' *J 7 _┆
0x4bf00…4c000 (75, 0, 15) Sector 4b00ff00155341 ┆K SA 1 UFCO performs the user transaction control, which consists of: - user transaction execution - user requested transaction interruption - user transaction accounting. The fu┆
0x4c000…4c100 (76, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(76,0, 1), len=0xff, h3=41155341}, f00=»1553A «, f01=»CPS/SDS/039 «, f02=»pn «, f03=»JBS «, f04=»4.1.1.4-2 «, f05=23-12-81 10:06, f06=» 11 «, f07=»36 «, f08=» 39119 «, f09=25-05-82 14:08, f10=» «, f11=»02 «, f12=» 59 «, f13=25-05-82 14:10, f14=26-05-82 14:14, f15=»0170A «, f16=»113 «, f17=» 39 «, f18=»41 «, f19=» 1096 «, f20=» 90316 «, f21=» «, f22=» 0 «, f99=230010000110062710110490aaca15050000000000000037037801df}
0x4c100…4c200 (76, 0, 1) Sector 4c027100155341 ┆L q SA L L L L K K K K 8 8 8 8 8 8 8 7 7 7 7 7 - - - , , , , , + + + + * * * ) ) ) ( ( ( ( ( ( ' ' ' ' & & & & & % % % % % $ $ $ $ $ # # # " " " " " ! ! ! ! g f f f e e e ┆
0x4c200…4c300 (76, 0, 2) Sector 4c039c00155341 ┆L SA 1 CPS/SDS/039 820505 USER 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┆
0x4c300…4c400 (76, 0, 3) Sector 4c045f00155341 ┆L _ SA 1 Fig. 4.1.1.4-2 Bp.MP- Rm.> IM)-MI,:^=~ B~.> IMB'IM2& 9x2"<!Z="(=^#Vk"$<:]=2#<:^=~ J6.! <6 M8) R6.> I! <6 M8)I!h=6 ! =6 M")IM"):g=~ J /:h=2>=M?.Mj': < Zn.C / E*:=k 0wM% !;=4C┆
0x4c400…4c500 (76, 0, 4) Sector 4c05ff00155341 ┆L SA 1 4.1.2 Software Specification In this section the software structure of VUP will be described. The allocation of functions onto processes and coroutines will be explained, based on┆
0x4c500…4c600 (76, 0, 5) Sector 4c06ff00155341 ┆L SA the analysis performed in section 4.1.1. Figure 4.1.2-1 shows the mapping of functions onto processes and coroutines 4.1.2.1. VUS Process The VDU USER PROCESS controls the interaction with the user VDU, under supervision of TEMCO (SSC softwa┆
0x4c600…4c700 (76, 0, 6) Sector 4c07ec00155341 ┆L l SAre). It thus has the following responsibilities: - TEMCO command execution - Control and execution of user transactions - User transaction accounting - Maintaining the VDU Header queue status - Monitoring of FLASH queues. 6$`i6 {M)(sM &M7 ┆
0x4c700…4c800 (76, 0, 7) Sector 4b085e00155341 ┆K ^ SA 1 Fig. 4.1.2-1 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=!┆
0x4c800…4c900 (76, 0, 8) Sector 00000000000000 ┆ ┆
[…0x7…]
