OctetView
0x00000…00100 (0, 0, 0) Sector 01124130313132 ┆ A0112A ┆
0x00100…00200 (0, 0, 1) Sector 00000000000000 ┆ ┆
0x00200…00300 (0, 0, 2) Sector ff00c0fff0fff0 ┆ @ p p x ┆
0x00300…00306 (0, 0, 3) WangDocument {d00=0x14, d01=0x63, d02=0x41, ptr=(46,0, 0), d05=0x00}
0x00306…0030c WangDocument {d00=0x15, d01=0x26, d02=0x41, ptr=(22,0, 8), d05=0x00}
0x0030c…00312 WangDocument {d00=0x15, d01=0x49, d02=0x41, ptr=(29,0, 0), d05=0x00}
0x00312…00318 WangDocument {d00=0x15, d01=0x52, d02=0x41, ptr=( 3,0, 0), d05=0x00}
0x00318…00320 00 00 00 00 00 00 00 00 ┆ ┆
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 01124130313132 ┆ A0112A ┆
0x00600…00700 (0, 0, 6) Sector 421c402600415b ┆B @& A[' k X% % PO P ; cA & C f x f V W O 7 : 8 ;p - 1463A f i < {C < { ; 2 ` l j< jA O 9 8 : p t xI 1463A1461A I Lc2g;#> ┆
0x00700…00800 (0, 0, 7) Sector 00000000000000 ┆ ┆
[…0x8…]
0x01000…01100 (1, 0, 0) WangDocumentBody
[…0x1…]
0x01200…01300 (1, 0, 2) Sector 0103ff00154941 ┆ IAus administration field. 4.2.5.6.15.2 Interface Definition Call Convertion a) CONVERT STORE LTD (LTD: INTEGER) b) CONVERT STORE LTD (R0, R6) Register Convention R0 LTD (Kept) R6 LINK (D┆
0x01300…01400 (1, 0, 3) Sector 0104ff00154941 ┆ IAest.) Return Registers None R1-R7 (Dest.) 4.2.5.6.15.3 Data Definition a) Data References TABLE TYPE CPS/DBD/001 DEVICE PROFILE TYPE CPS/DBD/001 TERMINAL PROFILE TYPE ┆
0x01400…01500 (1, 0, 4) Sector 0105a900154941 ┆ ) IA CPS/DBD/001 NO OF VDUS CPS/DBD/001 b) External Data UMAM TABLE REC 4.2.5.5 4.2.5.6.15.4 Procedure Design odule is to change the state of a CIF from passive to active. 4.2.5.6.13.2 Interfac┆
0x01500…01600 (1, 0, 5) Sector 0106ff00154941 ┆ IA 1 CONVERT/STORE LTD LTD GT NO OF VDUS? SET LDD = LTD-NO OF VDUS CASE TMP SEARCH(TERMINAL PROFILE, LTD) (LTD(ASCII), CC): ERROR OK ERROR┆
0x01600…01700 (1, 0, 6) Sector 0107ff00154941 ┆ IA? ANALYZE ERROR(CC, 0) OK? END CASE MOVE LTD(ASCII)TO STA ADM.LTD CASE TMP SEARCH(DEVICE PROFILE,LDD) (LDD(ASCII),CC):ERROR OK ERROR? ANALYZE ERROR┆
0x01700…01800 (1, 0, 7) Sector 0000a100154941 ┆ ! IA: OK? END CASE MOVE LDD(ASCII) TO STA ADM.LDD Fig. 4.2.5.6.15 N/A 4.2.5.6.13.4 Procedure Design . 4.2.5.6.11.2 Interface Definition Call Specifica┆
0x01800…01900 (1, 0, 8) WangDocumentBody
[…0xb…]
0x02400…02500 (2, 0, 4) Sector 0000e700152641 ┆ g &As used then the status records are read and sorted. The Intermediate File and the Preparation File are read and the status records are sorted. Upon completion the generated status is sent either to a VDU or to a printer. ECORDS(4.2.5.4.1.2) SE┆
0x02500…02600 (2, 0, 5) Sector 0206ff00155241 ┆ RA 1 4.2.5.6.31 UINT ERROR 4.2.5.6.31.1 Functional Specification TBD 4.2.5.6.31.2 Interface Definition Call Specification TBD Register Convention Call Registers TBD ┆
0x02600…02700 (2, 0, 6) Sector 02079f00155241 ┆ RA Return Registers TBD 4.2.5.6.31.3\Data Description a) Data References TBD b) External Data TBD 4.2.5.6.31.4 Procedure Design TBD CIFS (4.2.5.6.28) UMAM QEL DISMANTLE (4.2.5.6.1) CLEAR STATUS RECORD PREP EQ TRUE ? - ┆
0x02700…02800 (2, 0, 7) Sector 00009a00155241 ┆ RA 1 4.2.5.7 Subpackage Interfaces Refer CPS/ICD/009 4.3 Memory Layout TBD UMAM FILE ADDR.BYTE COUNT = INTA LENGTH UMAM BLE.ADDRESS = BIG BUFFER (PREP AREA SIZE +1) UMAM┆
0x02800…02900 (2, 0, 8) WangDocumentBody
[…0x7…]
0x03000…03100 (3, 0, 0) WangDocumentHead {hdr=WangSectHead {next=( 3,0, 1), len=0xff, h3=41155241}, f00=»1552A «, f01=»USER VDU «, f02=»bbh «, f03=»BBC «, f04=»CPS/039 4.2.5.6.16 «, f05=23-12-81 09:12, f06=» 9 «, f07=»18 «, f08=» 20835 «, f09=24-03-82 10:36, f10=» «, f11=»01 «, f12=» 8 «, f13=07-01-82 12:18, f14=19-05-82 14:43, f15=»0112A «, f16=» 1 «, f17=» 10 «, f18=»16 «, f19=» 248 «, f20=» 22370 «, f21=» «, f22=» @ «, f99=040010000110062710110480aaca15050000000000000037030400df}
0x03100…03200 (3, 0, 1) WangDocumentBody
[…0x2…]
0x03400…03500 (3, 0, 4) Sector 0305aa00155241 ┆ * RA TBD Return Registers TBD 4.2.5.6.30.3 Data Description a) Data REferences TBD b) External Data TBD 4.2.5.6.30.4 Procedure Design TBD (R1, R6) Register Convention Call Register R1 pointer to PREP REC (DEST) ┆
0x03500…03600 (3, 0, 5) Sector 0306ff00155241 ┆ RA 1 4.2.5.6.31 UINT ERROR 4.2.5.6.31.1 Functional Specification TBD 4.2.5.6.31.2 Interface Definition Call Specification TBD Register Convention Call Registers TBD ┆
0x03600…03700 (3, 0, 6) Sector 03079f00155241 ┆ RA Return Registers TBD 4.2.5.6.31.3\Data Description a) Data References TBD b) External Data TBD 4.2.5.6.31.4 Procedure Design TBD CIFS (4.2.5.6.28) UMAM QEL DISMANTLE (4.2.5.6.1) CLEAR STATUS RECORD PREP EQ TRUE ? - ┆
0x03700…03800 (3, 0, 7) Sector 00009a00155241 ┆ RA 1 4.2.5.7 Subpackage Interfaces Refer CPS/ICD/009 4.3 Memory Layout TBD UMAM FILE ADDR.BYTE COUNT = INTA LENGTH UMAM BLE.ADDRESS = BIG BUFFER (PREP AREA SIZE +1) UMAM┆
0x03800…03900 (3, 0, 8) WangDocumentBody
[…0x12f…]
0x16800…16900 (22, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(22,0, 9), len=0xff, h3=41152641}, f00=»1526A «, f01=»CPS/SDS/039 «, f02=»bbh «, f03=»JBS «, f04=»fra 4.2.4 «, f05=15-12-81 09:23, f06=» 30 «, f07=»25 «, f08=» 58201 «, f09=13-05-82 09:58, f10=» «, f11=»08 «, f12=» 143 «, f13=07-01-82 12:14, f14=14-05-82 15:31, f15=»0112A «, f16=»108 «, f17=» 35 «, f18=»15 «, f19=» 824 «, f20=» 64054 «, f21=» «, f22=» «, f99=700010000110062710110480aaca15050000000000000037033c01df}
0x16900…16a00 (22, 0, 9) WangDocumentBody
[…0x66…]
0x1d000…1d100 (29, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(29,0, 1), len=0xff, h3=41154941}, f00=»1549A «, f01=»USER VDU «, f02=»sdv «, f03=»BBC «, f04=»SDS/039,4.2.5.4.13-1 «, f05=23-12-81 08:36, f06=» 14 «, f07=»05 «, f08=» 40928 «, f09=04-12-82 09:55, f10=» 2 «, f11=»09 «, f12=» 2414 «, f13=07-01-82 12:16, f14=19-05-82 14:43, f15=»0112A «, f16=» 37 «, f17=» 16 «, f18=»14 «, f19=» 332 «, f20=» 43342 «, f21=» «, f22=» «, f99=520010000110062710110480aaca15050000000000000037037a00df}
0x1d100…1d200 (29, 0, 1) WangDocumentBody
[…0xb…]
0x1dd00…1de00 (29, 0, 13) Sector 1d0ee500154941 ┆ e IAIZE CASE MODIFYBYTES(FILE NAME,UMAM FILE ADDR,UMAM BLE) (UMAM FILE ADDR,CC): ERROR OK ERROR? ANALYZE ERROR(CC,0) OK? END CASE ADD SORT COUNT TO FILE DIRECTORY(LTD).COUNT Fig. 4.2.5.4.16-3 d are an LTD and a status ┆
0x1de00…1df00 (29, 0, 14) Sector 1d0fff00154941 ┆ IA 1 4.2.5.4.17 INCLUDE IN PREP Module 1 4.2.5.4.17.1 Functional Specification The purpose of this module is to ins┆
0x1df00…1e000 (29, 0, 15) Sector 1d00ff00154941 ┆ IAert status records in the Preparation File. If no empty record can be found in the Preparation File, then the Expand File is inspected. If the Expand File is full or nearly full, a threshold warning will be sent to the Supervisor Printer. When t┆
0x1e000…1e100 (30, 0, 0) WangDocumentBody
[…0xff…]
0x2e000…2e100 (46, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(46,0, 1), len=0xff, h3=41146341}, f00=»1463A «, f01=»CPS/SDS/024 «, f02=»dhh «, f03=»JSC «, f04=»fra 4.2 «, f05=24-11-81 10:28, f06=» 4 «, f07=»17 «, f08=» 7512 «, f09=21-01-86 10:17, f10=» «, f11=»18 «, f12=» 47 «, f13=28-08-85 08:43, f14=27-01-86 12:32, f15=»0112A «, f16=» 82 «, f17=» 31 «, f18=»05 «, f19=» 740 «, f20=» 78207 «, f21=» «, f22=» «, f99=020000000110062710110280aaca15050000000000000037030d01df}
0x2e100…2e200 (46, 0, 1) WangDocumentBody
[…0x6…]
0x2e800…2e900 (46, 0, 8) Sector 2e095a00155341 ┆. Z SAT: INTEGER 4.2.1.4.1.5 Module Design The module performs the following tasks: rted and activates initialization or restart accordingly. It initializes the VUS dataareas, sends a command to UFCO, signals UFCO and initiates reception from the VU┆
0x2e900…2ea00 (46, 0, 9) Sector 2e0aff00155341 ┆. SA 1 - Interprets the START UP ACTIVE TYPE and sends a INIT UFCO cmd or RESTART UFCO cmd accordingly. - Initializes VUS data- and VCO dataareas. - Sets up RECEIVE FIRST QEL call ┆
0x2ea00…2eb00 (46, 0, 10) Sector 2e0bff00155341 ┆. SAto VUS CMDQ, associates the call to VUS S1, signals UFCO and waits for VUS S1. - Analyses input to VUS CMDQ and calls the modules: TEMCO CMD PROCESSING FLASH QUEUE MONITORING TIMER EVENT PROCESSING accordingly. - Analyses UFCO responses ┆
0x2eb00…2ec00 (46, 0, 11) Sector 2e0c4b00155341 ┆. K SAand updates and displays VDU header. - Sends acknowledge to TEMCO. e displayed (if not it will be sent to MDCO immediately), determines whether the current precedence is flash or above (in which case timeout request is not required), checks if a t┆
0x2ec00…2ed00 (46, 0, 12) Sector 2e0dff00155341 ┆. SA 1 VCO CONTROL CASE START UP OF DEAD1? RESTART: = FALSE DEAD2? RESTART: = FALSE COLD ? RESTART: = FALSE WARM1? RESTART: = TRUE WARM2? RESTART: = TRUE OTHERWI┆
0x2ed00…2ee00 (46, 0, 13) Sector 2e0eff00155341 ┆. SASE? VUS QUEUE ERROR(CONTINUE) (4.1.5.1) END CASE STARTUP VUS INIT(4.2.1.4.1.3.1) RESTART? VCO OP.CMD: = RESTART UFCO CMD VCO OP.CMD: = INIT UFCO CMD SIGNAL UFCO(4.2.1.6.1) SET RECEIVE CMD QEL(4.2.1.4.1.3.2) LOOP FOREVER WAIT OPSEM(V┆
0x2ee00…2ef00 (46, 0, 14) Sector 2e0fff00155341 ┆. SAUS S1)(VUS OP): OK CASE VUS OP.IDENT OF CMD IDENT? VUS CMD QEL PROCESSING(-2) UFCO IDENT? UFCO RESPONSE PROCESSING(-3) OTHERWISE? VUS INTERNAL ERROR(GIVE UP)(4.1.5.2) END CASE IDENT END FOREVER LOOP END FIGU┆
0x2ef00…2f000 (46, 0, 15) Sector 2e001800155341 ┆. SARE 4.2.1.4.1.5-1 Responds to completion of UFCO cmd and sends acknowledge of BLOCK TERMINAL cmd to TEMCO. module interprets the timeout to determine whether it is a periodic- or flash timeout request. For periodic timeouts the date/time fiel┆
0x2f000…2f100 (47, 0, 0) Sector 2f01ff00155341 ┆/ SA 1 4.2.1.4.1.3.8 CLOSE DOWN UFCO CC PROCESSING Responds to completion of UFCO cmd, clears VDU Header Split, closes Format Handler interface and sends acknowledge of CLOSE DOWN cmd to┆
0x2f100…2f200 (47, 0, 1) Sector 2f021000155341 ┆/ SA TEMCO. eues are searched for further flash items (if such items are found renewed timeout is requested), the VDU queue length fields are updated and displayed. If unexpected queue elements are found this is reported to SSC. 4.2.1.2.5 Common Pr┆
0x2f200…2f300 (47, 0, 2) Sector 2f03ff00155341 ┆/ SA 1 SET RECEIVE CMD QEL CASE INIT RECEIVE FIRST QEL(WAIT, VUS CMDQ, VUS CMDQ ATTR, CMD OP)(CC): ERROR OK ERROR? ANALYSE ERROR(CC,0) OK? ASSOCIATE(VUS S1, CMD OP): OK ┆
0x2f300…2f400 (47, 0, 3) Sector 2f044100155341 ┆/ A SA END CASE INIT END FIGURE 4.2.1.4.1.3.2-1 FIGURE 4.2.1.2-1 1.2) Initiates a receive function for the VUS CMDQ and associates the event to the VUS S1 semaphore. c) Init UFCO cc Processing (1.3) Reacts upon comp┆
0x2f400…2f500 (47, 0, 4) Sector 2f05ff00155341 ┆/ SA 1 4.2.1.4.1.4 Data Description a) Data References VCO OP refer 4.1.4 VUS S1 refer 4.1.4 INIT UFCO CMD refer 4.1.4 RESTART UFCO CMD refer 4.1.4 START UFCO CMD refer 4.1.4 ┆
0x2f500…2f600 (47, 0, 5) Sector 2f06ff00155341 ┆/ SA STOP UFCO CMD refer 4.1.4 BLOCK UFCO CMD refer 4.1.4 CLOSE DOWN UFCO CMD refer 4.1.4 INIT UFCO CC refer 4.1.4 RESTART UFCO CC refer 4.1.4 START UFCO CC refer 4.1.4 STOP UFCO CC refer 4.1.4 BLOCK UFCO CC refer 4.1.4 CLOSE DOWN UFCO ┆
0x2f600…2f700 (47, 0, 6) Sector 2f07ff00155341 ┆/ SACC refer 4.1.4 USER MODE CHANGE refer 4.1.4 PRECEDENCE CHANGE refer 4.1.4 QERROR INF refer 4.1.4 INTERNAL ERROR INF refer 4.1.4 CMD QEL refer 4.2.1.5 CMD QEL MAINTYPE refer 4.2.1.5 CMD QEL SUBTYPE refer 4.2.1.5 CMD QEL FLAGS refer 4.┆
0x2f700…2f800 (47, 0, 7) Sector 2e08ff00155341 ┆. SA2.1.5 ACK PARAMS refer 4.2.1.5 CURRENT MODE QUEUE refer 4.2.1.5 FLASH ITEM FOUND refer 4.2.1.5 b) External Data START UP: START UP ACTIVE TYPE c) Local Data RESTART: BOOLEAN UFCO CC RECEIVED: BOOLEAN OP POINTER: INTEGER OP IDEN┆
0x2f800…2f900 (47, 0, 8) Sector 2f09ff00155341 ┆/ SAerprets the startup parameters delivered in the registers when the subprocess is started and activates initialization or restart accordingly. It initializes the VUS dataareas, sends a command to UFCO, signals UFCO and initiates reception from the VU┆
0x2f900…2fa00 (47, 0, 9) Sector 2f0aff00155341 ┆/ SAS CMDQ. It associates the reception from this queue with the semaphore VUS S1 and waits for this semaphore. It analyses the input to the semaphore (when signalled) to identify: - SSC commands - Flash Notifications - Timeouts - UFCO Responses ┆
0x2fa00…2fb00 (47, 0, 10) Sector 2f0bff00155341 ┆/ SAand calls appropriate modules. 4.2.1.4.1.2 Module Interface Call Specification a) VCO CONTROL b) VCO CONTROL (R6) Register Convention Call Registers R6 LINK DESTROYED Return Registers RO-R7 DEST┆
0x2fb00…2fc00 (47, 0, 11) Sector 2f0c2200155341 ┆/ " SAROYED Fatal Errors None r the classification allows the item to be displayed (if not it will be sent to MDCO immediately), determines whether the current precedence is flash or above (in which case timeout request is not required), checks if a t┆
0x2fc00…2fd00 (47, 0, 12) Sector 2f0dff00155341 ┆/ SA 1 4.2.1.4.1.3 Module Components 4.2.1.4.1.3.1 VUS INIT Initializes the VUS-data areas and VCO-dataareas. 4.2.1.4.1.3.2 SET RECEIVE CMD QEL Initiates reception from VUS CMDQ ┆
0x2fd00…2fe00 (47, 0, 13) Sector 2f0eff00155341 ┆/ SAand associates to VUS S1. Refer figure 4.2.1.4.1.3.2-1. 4.2.1.4.1.3.3 INIT UFCO CC PROCESSING Responds to completion of UFCO cmd. 4.2.1.4.1.3.4 RESTART UFCO CC PROCESSING Responds to completion of UFCO cmd. 4.2.1.4.1.3.5 START UFCO CC┆
0x2fe00…2ff00 (47, 0, 14) Sector 2f0fff00155341 ┆/ SA PROCESSING Responds to completion of UFCO cmd and sends acknowledge of START USER cmd to TEMCO. 4.2.1.4.1.3.6 STOP UFCO CC PROCESSING Responds to completion of UFCO cmd and sends acknowledge of STOP USER cmd to TEMCO. 4.2.1.4.1.3.7 BLOCK ┆
0x2ff00…30000 (47, 0, 15) Sector 2f007700155341 ┆/ w SAUFCO CC PROCESSING Responds to completion of UFCO cmd and sends acknowledge of BLOCK TERMINAL cmd to TEMCO. module interprets the timeout to determine whether it is a periodic- or flash timeout request. For periodic timeouts the date/time fiel┆
0x30000…30100 (48, 0, 0) Sector 3001ff00155341 ┆0 SAd and queue length fields in the VDU header are updated and the VDU header displayed. For a flash timeout it is checked if current precedence is flash or above (in which case no action is taken), otherwise the flash item timed out is sent. MDCO, th┆
0x30100…30200 (48, 0, 1) Sector 3002ff00155341 ┆0 SAe flash queues are searched for further flash items (if such items are found renewed timeout is requested), the VDU queue length fields are updated and displayed. If unexpected queue elements are found this is reported to SSC. 4.2.1.2.5 Common Pr┆
0x30200…30300 (48, 0, 2) Sector 30035500155341 ┆0 U SAocedures For description of the 14 common procedures refer section 4.2.1.6. ata and VCO data. ) a) Initialize VUS Data (1.1) Performs initialization of common data for the subpackages within VUS. b) Initialize VCO Data (1.2) Performs init┆
0x30300…30400 (48, 0, 3) Sector 30046300155341 ┆0 c SA 1 FIGURE 4.2.1.2-1 1.2) Initiates a receive function for the VUS CMDQ and associates the event to the VUS S1 semaphore. c) Init UFCO cc Processing (1.3) Reacts upon comp┆
0x30400…30500 (48, 0, 4) Sector 3005ff00155341 ┆0 SA 1 4.2.1.3 Dataflow and Control Logic within VCO An overview of the dataflow through VCO is shown on diagrams 4.2.1.3-1 to 4. The call structure within VCO is shown on figure 4.2.1┆
0x30500…30600 (48, 0, 5) Sector 30064900155341 ┆0 I SA.3-5 identifying all calls between modules and common procedures. 7) Reacts upon completion of the BLOCK UFCO CMD. h) Close Down UFCO cc Processing (1.8) Reacts upon completion of the CLOSE DOWN UFCO CMD. 4.2.1.2.2 TEMCO CMD Processing (2.┆
0x30600…30700 (48, 0, 6) Sector 30077500155341 ┆0 u SA 1 FIGURE 4.2.1.3-1 - FIGURE 4.2.1.3-5 nd reports reception of unexpected queue elements to SSC. The following component procedures are contained in this module: a) Get Term┆
0x30700…30800 (48, 0, 7) Sector 2f08ff00155341 ┆/ SA 1 4.2.1.4 VCO Module Specifications 4.2.1.4.1 VCO CONTROL Specification 4.2.1.4.1.1 Functional Specifcation This module is the controlling module within the subpackage. It int┆
0x30800…30900 (48, 0, 8) Sector 30094500155341 ┆0 E SAEMCO together with START USER CMD) to VUS common data areas. 4.2.1.1.3 Flash Item Control (3.0) a) Interpret flash notification (3.1) Analyses the flash notification to determine the precedence (superflash or flash) and which queue the fl┆
0x30900…30a00 (48, 0, 9) Sector 300aff00155341 ┆0 SA 1 d) Init Header Split (2.4) Initializes the contents of the fields to be displayed as VDU header and displays the fields. e) Request Periodic Timeout (2.5) Requests the period┆
0x30a00…30b00 (48, 0, 10) Sector 300bff00155341 ┆0 SAic timeout (every minute) for the duration of this session. 4.2.1.2.3 Flash Queue Monitoring (3.0) This module interprets the flash notification to determine which queue the flash item has arrived at and the precedence of the item (superflash a┆
0x30b00…30c00 (48, 0, 11) Sector 300cff00155341 ┆0 SAnd flash), determines whether the classification allows the item to be displayed (if not it will be sent to MDCO immediately), determines whether the current precedence is flash or above (in which case timeout request is not required), checks if a t┆
0x30c00…30d00 (48, 0, 12) Sector 300dff00155341 ┆0 SAimeout is already outstanding (in which case timeout request is not required), reads the system parameter FQT (Flash Queue Timeout), checks if it is changed since last used, requests/cancels timeout accordingly, updates VDU header queue fields, inve┆
0x30d00…30e00 (48, 0, 13) Sector 300eff00155341 ┆0 SArts appropriate flash queue fields, rings the bell displays the VDU header and reports reception of unexpected queue element in the VUS CMDQ. The following component procedure is contained in the module: a) Get Flash QEL Attributes (3.1) Obtai┆
0x30e00…30f00 (48, 0, 14) Sector 300f5400155341 ┆0 T SAns flash queue element attributes by call upon the Queue Monitor function. ess Precedence Change (6.4) Reacts upon information from UFCO that the current precedence has changed. 4.2.1.1.7 Error Reporting (7.0) a) Queue Error Reporting (7.┆
0x30f00…31000 (48, 0, 15) Sector 3000ff00155341 ┆0 SA 1 4.2.1.2.4 Timer Event Processing (4.0) This module interprets the timeout to determine whether it is a periodic- or flash timeout request. For periodic timeouts the date/time fiel┆
0x31000…31100 (49, 0, 0) Sector 3101ff00155341 ┆1 SAe software structure is shown on figure 4.2.1.2-1. VCO consists of one coroutine containing 4 modules and 14 common procedures. 4.2.1.2.1 VCO Control (1.0) This is the module containing the mainloop of VCO. The module contains the VUS initializ┆
0x31100…31200 (49, 0, 1) Sector 3102ff00155341 ┆1 SAation functions, receives and processes items arriving in the VUS CMDQ, receives and reacts upon UFCO responses, sends acknowledge of TEMCO commands to TEMCO and reports queue errors and internal errors to SSC. The following component procedures a┆
0x31200…31300 (49, 0, 2) Sector 31036700155341 ┆1 g SAre contained in this module: a) VUS Init (1.1) Initializes the VUS common data and VCO data. ) a) Initialize VUS Data (1.1) Performs initialization of common data for the subpackages within VUS. b) Initialize VCO Data (1.2) Performs init┆
0x31300…31400 (49, 0, 3) Sector 3104ff00155341 ┆1 SA 1 b) Set Receive CMD QEL (1.2) Initiates a receive function for the VUS CMDQ and associates the event to the VUS S1 semaphore. c) Init UFCO cc Processing (1.3) Reacts upon comp┆
0x31400…31500 (49, 0, 4) Sector 3105ff00155341 ┆1 SAletion of the INIT UFCO CMD. d) Restart UFCO cc Processing (1.4) Reacts upon completion of the RESTART UFCO CMD. e) Start UFCO cc Processing (1.5) Reacts upon completion of the START UFCO CMD. f) Stop UFCO cc Processing (1.6) Reacts upon┆
0x31500…31600 (49, 0, 5) Sector 3106ff00155341 ┆1 SA completion of the STOP UFCO CMD. g) Block UFCO cc Processing (1.7) Reacts upon completion of the BLOCK UFCO CMD. h) Close Down UFCO cc Processing (1.8) Reacts upon completion of the CLOSE DOWN UFCO CMD. 4.2.1.2.2 TEMCO CMD Processing (2.┆
0x31600…31700 (49, 0, 6) Sector 3107ff00155341 ┆1 SA0) This module analyses TEMCO commands, performs start user actions (after sign on), sends commands to UFCO and reports reception of unexpected queue elements to SSC. The following component procedures are contained in this module: a) Get Term┆
0x31700…31800 (49, 0, 7) Sector 3008ff00155341 ┆0 SAinal Profile (2.1) Reads the terminal profile by call upon TMP. b) Set Session Attributes (2.2) Transfers data from the terminal profile to VUS Common data areas. c) Set User Connection (2.3) Transfers the user connection (received from T┆
0x31800…31900 (49, 0, 8) Sector 3109ff00155341 ┆1 SA 1 4.2.1.1.3 Flash Item Control (3.0) a) Interpret flash notification (3.1) Analyses the flash notification to determine the precedence (superflash or flash) and which queue the fl┆
0x31900…31a00 (49, 0, 9) Sector 310aff00155341 ┆1 SAash item is in (Release - or Receive queue). b) Request/Cancel Timeout (3.2) Calls upon the timer monitor functions. c) Search Flash Queues (3.3) Searches for flash items in the flashqueues. d) Send Flash Items to MDCO (3.4) Sends old fl┆
0x31a00…31b00 (49, 0, 10) Sector 310bff00155341 ┆1 SAash items to MDCO. 4.2.1.1.4 Timers Event Processing (4.0) a) Interpret Timeout (4.1) Analyses timeout to determine whether it is a flash timeout request or a periodic timeout. b) Request Timeout (4.2) Requests a flash timeout. 4.2.1.1┆
0x31b00…31c00 (49, 0, 11) Sector 310cff00155341 ┆1 SA.5 VDU Header Control (5.0) a) Update Date/Time Field (5.1) Maintains the Date/Time Field in the VDU-header when a periodic timeout occurs. b) Update Q-Status Fields (5.2) Maintains the queue length filds in the VDU-header. c) Display VDU-┆
0x31c00…31d00 (49, 0, 12) Sector 310d9700155341 ┆1 SAHeader (5.3) Updates the VDU-header display. 4.2.1.1.6 UFCO Control (6.0) a) Send CMD to UFCO (6.1) Controls UFCO by sending commands. 4. Close Down CC 5. Validation Result. 6. Output format CC 7. Input format CC 5. From UFCO to R┆
0x31d00…31e00 (49, 0, 13) Sector 310eff00155341 ┆1 SA 1 b) Process Command Completion from UFCO (6.2) Interprets and reacts upon acknowledge from UFCO. c) Process User Mode Change (6.3) Reacts upon information from UFCO that the c┆
0x31e00…31f00 (49, 0, 14) Sector 310fff00155341 ┆1 SAurrent user mode (i.e. release, preparation, reception) has changed. d) Process Precedence Change (6.4) Reacts upon information from UFCO that the current precedence has changed. 4.2.1.1.7 Error Reporting (7.0) a) Queue Error Reporting (7.┆
0x31f00…32000 (49, 0, 15) Sector 3100ff00155341 ┆1 SA1) Reports to SSC that an unexpected Queue element has been received. b) Internal Error Handling (7.2) Reports to SSC that an unexpected response has been received from UFCO or from monitor procedures called. 4.2.1.2 Software Structure Th┆
0x32000…32100 (50, 0, 0) Sector 32015000155341 ┆2 P SA - Error Reporting Figure 4.2.1.1-1 presents the functional breakdown. Interfaces NT = ANQ IDENT INIT F/C KEY OP. IDENT = F/C KEY IDENT INIT VDU OP. IDENT = VDU IDENT VAR VUS S1, VUS S2, VUS S3: COROUTINE SEMAPHORE TYPE VAR FORMAT I┆
0x32100…32200 (50, 0, 1) Sector 32026300155341 ┆2 c SA 1 FIGURE 4.2.1.1-1 es User Procedures ref. doc. no. CPS/230/ICD/0001. All VUP subpackages interfaces, this document. 4.1.7.2 Package Interfaces 4.1.7.2.1 Traffic Han┆
0x32200…32300 (50, 0, 2) Sector 3203ff00155341 ┆2 SA 1 4.2.1.1.1 Initialization (1.0) a) Initialize VUS Data (1.1) Performs initialization of common data for the subpackages within VUS. b) Initialize VCO Data (1.2) Performs init┆
0x32300…32400 (50, 0, 3) Sector 3204ff00155341 ┆2 SAialization of common data for the modules within the VCO subpackage. 4.2.1.1.2 TEMCO Command Processing a) Process START USER CMD (2.1) This command is received after a successful SIGN ON procedure has taken place and VCO takes action and sta┆
0x32400…32500 (50, 0, 4) Sector 3205ff00155341 ┆2 SArts UFCO. b) Process STOP USER CMD (2.2) This command is received after SIGN OFF and VCO takes action and stops UFCO. c) Process BLOCK TERMINAL CMD (2.3) This command is received when the terminal has been blocked (by supervisor or as a resu┆
0x32500…32600 (50, 0, 5) Sector 3206ff00155341 ┆2 SAlt of a failed SIGN ON procedure or security interrogation) and VCO informs UFCO. d) Process CLOSE DOWN CMD (2.4) This command informs VUS that a system close down procedure is to take place and VCO informs UFCO. e) Send Response to TEMCO (2.5┆
0x32600…32700 (50, 0, 6) Sector 3207ff00155341 ┆2 SA) For each TEMCO command a corresponding command to UFCO exists and to each UFCO command a corresponding completion response exists. When VCO has received the expected completion response from UFCO an acknowledge to the TEMCO command is sent to TE┆
0x32700…32800 (50, 0, 7) Sector 31080e00155341 ┆1 SAMCO. ) and VDIA (table access). For details refer CPS/ICD/009. 4.1.7.3 Subpackage Interfaces 4.1.7.3.1 Process Interfaces These are the interfaces between UMAM and VUS: From VUS to UMAM: 1. Status Requests 2. Edit Requests 3. Del┆
0x32800…32900 (50, 0, 8) Sector 32097200155341 ┆2 r SAete Requests 4. Access State Changes 5. VDU-PAGE Retrieval 6. Status Records. 7. Storage of VDU-PAGES DEST R6 LINK DEST Return Registers None R0-R7 DEST DELETED CC, ┆
0x32900…32a00 (50, 0, 9) Sector 320aff00155341 ┆2 SA 1 From UMAM to VUS: 1. Access Key to CIF (QEL ref) 2. Append Notification 3. Message Release Status 4. Outgoing Message Status 5. Delivery Status. 4.1.7.3.2 Coroutine Interf┆
0x32a00…32b00 (50, 0, 10) Sector 320bff00155341 ┆2 SAaces 1. From VCO to UFCO 1. Initialize Command 2. Restart UFCO Command 3. Start UFCO Command 4. Stop UFCO Command 5. Close Down Command. 2. From UFCO to VCO 1. Initalize CC 2. Restart UFCO CC 3. Start UFCO CC 4. Stop UFCO CC 5. ┆
0x32b00…32c00 (50, 0, 11) Sector 320ce700155341 ┆2 g SAClose Down CC 3. From UFCO to VDIA 1. Initialize CMD 2. Start VDIA CMD 3. Display Format CMD 4. Input Format CMD 5. Output Message CMD 6. Insert Lines CMD 7. Delete Lines CMD 8. Clean Up CMD 9. Close Down CMD. a) VUS INTERNAL┆
0x32c00…32d00 (50, 0, 12) Sector 320dff00155341 ┆2 SA 1 4. From VDIA to UFCO 1. Initialize CC 2. Start VDIA CC 3. Clean Up CC 4. Close Down CC 5. Validation Result. 6. Output format CC 7. Input format CC 5. From UFCO to R┆
0x32d00…32e00 (50, 0, 13) Sector 320eb500155341 ┆2 5 SAETR None. 6. From RETR to UFCO 1. SAR on-line retrieval notification 2. SAR off-line retrieval notification 3. On-line retrieval result 4. On-line append result DEST Return Registers None R0-R7 ┆
0x32e00…32f00 (50, 0, 14) Sector 320fff00155341 ┆2 SA 1 4.2 Subpackage Specifications 4.2.1 VDU Control Subpackage (VCO) This subpackage is the controlling subpackage within the package. The control is exercised by issue of commands┆
0x32f00…33000 (50, 0, 15) Sector 3200ff00155341 ┆2 SA and reception of responses. 4.2.1.1 Functional Specification The subpackage contains the following functions: - Initialization - TEMCO Command Processing - Flash Item Control - Timer Event Processing - VDU Header Control - UFCO Control ┆
0x33000…33100 (51, 0, 0) Sector 33015f00155341 ┆3 _ SA by calling the SEND GARBLE-procedure. 4.1.6 Global Data TBD 4.1.7 Interfaces NT = ANQ IDENT INIT F/C KEY OP. IDENT = F/C KEY IDENT INIT VDU OP. IDENT = VDU IDENT VAR VUS S1, VUS S2, VUS S3: COROUTINE SEMAPHORE TYPE VAR FORMAT I┆
0x33100…33200 (51, 0, 1) Sector 3302ff00155341 ┆3 SA 1 4.1.7.1 External Interfaces User Procedures ref. doc. no. CPS/230/ICD/0001. All VUP subpackages interfaces, this document. 4.1.7.2 Package Interfaces 4.1.7.2.1 Traffic Han┆
0x33200…33300 (51, 0, 2) Sector 3303ff00155341 ┆3 SAdling (THP) I/F This interface is implemented by the VUS coroutine UFCO. For details refer CPS/ICD/009. 4.1.7.2.2 Distribution (MDP) I/F This interface is implemented by the VUS coroutine UFCO. For details refer CPS/ICD/009. 4.1.7.2.3 ┆
0x33300…33400 (51, 0, 3) Sector 3304ff00155341 ┆3 SAStorage and Retrieval (SAR) I/F This interface is implemented by the VUS coroutines UFCO (requests queued to SAR) and RETR (reception of SAR responses). For details refer CPS/ICD/009. 4.1.7.2.4 Log and Accountability (LOG) I/F This interfac┆
0x33400…33500 (51, 0, 4) Sector 33055700155341 ┆3 W SAe is implemented by the VUS coroutine UFCO. For details refer CPS/ICD/009. TYPE VAR VUS QERROR: QERROR INF TYPE VAR VUS INT ERROR = RECORD USER CC: INTEGER USER INF: ARRAY(1..4) of INTEGER END; VAR ERROR TEXT ┆
0x33500…33600 (51, 0, 5) Sector 3306ff00155341 ┆3 SA 1 4.1.7.2.5 Statistics (STP) I/F This interface is implemented by the VUS coroutine UFCO. For details refer CPS/ICD/009. 4.1.7.2.6 SSC Software I/F This interface is impleme┆
0x33600…33700 (51, 0, 6) Sector 3307ff00155341 ┆3 SAnted by the VUS coroutines VCO (start / stop function ) and UFCO (security interrogation request). For details refer CPS/ICD/009. 4.1.7.2.7 Table Management Package (TMP) I/F This interface is implemented by the VUS coroutines UFCO (Global no┆
0x33700…33800 (51, 0, 7) Sector 3208ff00155341 ┆2 SA. series) and VDIA (table access). For details refer CPS/ICD/009. 4.1.7.3 Subpackage Interfaces 4.1.7.3.1 Process Interfaces These are the interfaces between UMAM and VUS: From VUS to UMAM: 1. Status Requests 2. Edit Requests 3. Del┆
0x33800…33900 (51, 0, 8) Sector 3309ef00155341 ┆3 o SA DEST R3 QEL DEST R4 pointer to VUS QERROR DEST R6 LINK DEST Return Registers None R0-R7 DEST DELETED CC, ┆
0x33900…33a00 (51, 0, 9) Sector 330aff00155341 ┆3 SA 1 4.1.5.1.3 Data Description a) Data References USER ACTION TYPE refer CPS/DBD/001 GAQ INFO TYPE refer CPS/DBD/001 QEL REFERENCE refer CPS┆
0x33a00…33b00 (51, 0, 10) Sector 330bff00155341 ┆3 SA/DBD/001 b) External Data VUS QERROR refer 4.1.4 c) Local Data None 4.1.5.1.4 Procedure Design This procedure reports queue errors to the SSC by calling the SEND GARBLE-procedure. 4.1.5.2 VUS INTERNAL ERROR 4.1.5┆
0x33b00…33c00 (51, 0, 11) Sector 330cff00155341 ┆3 SA.2.1 Functional Specification The purpose of this procedure is to report internal errors to the SSC. 4.1.5.2.2 Interface Definition Call Specification 1 a) VUS INTERNAL┆
0x33c00…33d00 (51, 0, 12) Sector 330d9f00155341 ┆3 SA ERROR (USER ACTION USER ACTION TYPE, VUS INT ERROR: INTERNAL ERROR INF) b) VUS INTERNAL ERROR (R1, R4, R6) Register Convention , SEQ VAL ERROR CC, SEQ SUSPEND CC, SEQ APPEND VALID CC, SEQ DEFER VALID CC, SEQ RELEASE V┆
0x33d00…33e00 (51, 0, 13) Sector 330eff00155341 ┆3 SA 1 Call Registers R1 USER ACTION DEST R4 pointer to VUS INT ERROR DEST R6 LINK DEST Return Registers None R0-R7 ┆
0x33e00…33f00 (51, 0, 14) Sector 330fff00155341 ┆3 SA DEST 4.1.5.2.3 Data Description a) Data References USER ACTION TYPE refer CPS/DBD/001 GAQ INFO TYPE refer CPS/DBD/001 QEL REFERENCE refer CPS/DBD/001 INTERNAL ERROR INF ┆
0x33f00…34000 (51, 0, 15) Sector 3300ff00155341 ┆3 SATYPE refer CPS/DBD/001 b) External Data VUS INTE ERROR refer 4.1.4 c) Local Data TYPE VUS INTERNAL ERROR: INTERNAL ERROR INF TYPE 4.1.5.2.4 Procedure Design This procedure reports internal errors to the SSC┆
0x34000…34100 (52, 0, 0) Sector 3401ff00155341 ┆4 SAT INIT RETR OP. IDENT = RETR IDENT INIT CMD OP. IDENT = CMDQ IDENT INIT ANQ OP. IDENT = ANQ IDENT INIT F/C KEY OP. IDENT = F/C KEY IDENT INIT VDU OP. IDENT = VDU IDENT VAR VUS S1, VUS S2, VUS S3: COROUTINE SEMAPHORE TYPE VAR FORMAT I┆
0x34100…34200 (52, 0, 1) Sector 3402ff00155341 ┆4 SAFCB, HEADER IFCB: IFCB INDEX TYPE VAR FIRST FIELD RECORD: FIELD DESCRIPTOR TYPE VAR CURSOR RECORD 1, CURSOR TO CMD RECORD, CURSOR RECORD = RECORD SPLIT DIGIT : INTEGER FIELD : FIELD DESCRIPTOR TYPE L┆
0x34200…34300 (52, 0, 2) Sector 3403cc00155341 ┆4 L SAINES ABOVE : INTEGER END; VAR TRANSACTION ID = RECORD TERMINAL DESIGNATOR: DESIGNATOR TYPE SERIAL NO : INTEGER TIME : TIME TYPE END; gned to a separate coroutine, due to the fact that ┆
0x34300…34400 (52, 0, 3) Sector 3404ff00155341 ┆4 SA 1 VAR CIF REF QEL, APPEND QEL: QEL REFERENCE TYPE VAR CURRENT CLASSIFIC: CLASSIFICATION TYPE VAR CURRENT PRECEDENCE: PRECEDENCE TYPE VAR CAB : USER CAPABILITY TYPE C┆
0x34400…34500 (52, 0, 4) Sector 3405ff00155341 ┆4 SAONST LOG BUFFER SIZE = CONST STATUS BUFFER SIZE = VAR TMP RECORD: TMP PARAM TYPE VAR VUS QERROR: QERROR INF TYPE VAR VUS INT ERROR = RECORD USER CC: INTEGER USER INF: ARRAY(1..4) of INTEGER END; VAR ERROR TEXT ┆
0x34500…34600 (52, 0, 5) Sector 34064b00155341 ┆4 K SA : ARRAY(1..36) OF CHAR VAR VUS SEND PARAMS : SEND PARAMS TYPE VDU CMD TYPE END CASE TYPE VCO CMD = (INIT UFCO CMD, RESTART UFCO CMD, START UFCO CMD, STOP UFCO CMD, BLOCK UFCO CMD, CLOSE DOWN UFCO CMD) TYPE UFCO CC = (INIT U┆
0x34600…34700 (52, 0, 6) Sector 3407ff00155341 ┆4 SA 1 4.1.5 Common Package Procedures 4.1.5.1 VUS QUEUE ERROR 4.1.5.1.1 Functional Specification The purpose of this procedure is to report queue errors to the SSC. 4.1.5.1.2 I┆
0x34700…34800 (52, 0, 7) Sector 3308ff00155341 ┆3 SAnterface Definition Call Specification a) VUS QUEUE ERROR(USER ACTION: USER ACTION TYPE, QEL: QEL REFERENCE, VUS QERROR: QERROR INF) b) VUS QUEUE ERROR(R1, R3, R6) Register Convention Call Registers R1 USER ACTION ┆
0x34800…34900 (52, 0, 8) Sector 3409ff00155341 ┆4 SAPUT MSG, VDIA APPEND, VDIA INSERT, VDIA DELETE) TYPE VDIA UFCO CC = (SPLIT FAILED CC, VDIA CLOSE DOWN CC, VDIA CANCEL CC, VDIA CLEAR VDU CC, INSERT NOT ALLOWED CC, LINES INSERTED CC, DELETE NOT ALLOWED CC, LINES DELETED CC, ┆
0x34900…34a00 (52, 0, 9) Sector 340aff00155341 ┆4 SA OUTPUT MSG CC, OUTPUT FORMAT CC, INPUT REQ CC, INPUT MSG CC, EXCEEDED CC, VAL ERROR CC, VDIA SUSPEND CC, APPEND VALID CC, DEFER VALID, RELEASE VALID, COORDINATION VALID) TYPE RETR NOT = (ONLINE NOTIFICATION, OFFLINE NOT┆
0x34a00…34b00 (52, 0, 10) Sector 340bb000155341 ┆4 0 SAIFICATION, RETRIEVAL NOTIFICATION, APPEND NOTIFICATION) TYPE VDU CMD = (FORMAT TO VDU, FIELDS TO VDU, FIELDS FROM VDU, LINES INSERTED, LINES DELETED) control logic for UFCO can be constructed in the same way as done for VCO. V┆
0x34b00…34c00 (52, 0, 11) Sector 340cff00155341 ┆4 SA 1 TYPE SEQUENCE CODE = (SEQ ENTER, SEQ FK1, SEQ FK2, SEQ FK3...SEQ FK36, SEQ START, SEQ CLOSE DOWN, SEQ STOP USER, SEQ BLOCK TERMINAL, SEQ FAILURE, SEQ CLOSE DOWN CC, ┆
0x34c00…34d00 (52, 0, 12) Sector 340dff00155341 ┆4 SA SEQ CANCEL CC, SEQ CLEAR VDU CC, SEQ OUTPUT MSG CC, SEQ OUTPUT FORMAT CC, SEQ INPUT REQ CC, SEQ INPUT MSG CC, SEQ INPUT FORMAT CC, SEQ EXCEEDED CC, SEQ VAL ERROR CC, SEQ SUSPEND CC, SEQ APPEND VALID CC, SEQ DEFER VALID CC, SEQ RELEASE V┆
0x34d00…34e00 (52, 0, 13) Sector 340eff00155341 ┆4 SAALID CC, SEQ COORDINATION VALID CC, SEQ CONT, SEQ DISP, CONT DISP, SUS/DEF DISP, UMAM ERROR RESP, CONT COMMENT, SUS/DEF COMMENT, DISP COOR, ACK THP, SEQ DELI, SEQ OUTG, SEQ RELS, REL OK, REL NOT, SEQ OFF NOT) 1 ┆
0x34e00…34f00 (52, 0, 14) Sector 340f4600155341 ┆4 F SA c) VUS COMMON DATA s without coroutines, then no internal synchronization is required. ion 4.1.1 has as far as possible been used in the software structure charts, with the purpose of highlighting th┆
0x34f00…35000 (52, 0, 15) Sector 3400ff00155341 ┆4 SA 1 VAR VCO OP, UFCO OP, VDIA CC OP, RETR OP, CMD OP, ANQ OP, F/C KEY OP, VDU OP: VUS COROUTINE OP TYPE INIT UFCO OP. IDENT = UFCO VDIA IDENT INIT VDIA CC OP. IDENT = VDIA IDEN┆
0x35000…35100 (53, 0, 0) Sector 3501ff00155341 ┆5 SA 1 4.1.4 Common Package Data a) DATA REFERENCES COROUTINE SEMAPHORE TYPE refer CPS/DBD/001 COROUTINE OPERATION TYPE refer CPS/DBD/001 IFCB INDEX TYPE refer CPS/DBD/001 FI┆
0x35100…35200 (53, 0, 1) Sector 3502ff00155341 ┆5 SAELD DESCRIPTOR TYPE refer CPS/DBD/001 DESIGNATOR TYPE refer CPS/DBD/001 TIME TYPE refer CPS/DBD/001 QEL REFERENCE TYPE refer CPS/DBD/001 CLASSIFICATION TYPE refer CPS/DBD/001 PRECEDENCE TYPE refer CPS/DBD/001 USER CAPABILITY TYPE r┆
0x35200…35300 (53, 0, 2) Sector 35037600155341 ┆5 v SAefer CPS/DBD/001 QERROR INF TYPE refer CPS/DBD/001 TMP PARAM TYPE refer CPS/DBD/001 b) VUS COMMON TYPES synchronization is depicted. swers from SAR. The functions of RETR have been assigned to a separate coroutine, due to the fact that ┆
0x35300…35400 (53, 0, 3) Sector 3504ff00155341 ┆5 SA 1 TYPE VUS COROUTINE OP = RECORD COROUTINE OP: COROUTINE OP TYPE IDENT: IDENT TYPE CMD: CO CMD's TYPE PARA: INTEGER END TYPE IDENT = (VCO ID┆
0x35400…35500 (53, 0, 4) Sector 3505ff00155341 ┆5 SAENT, UFCO IDENT, UFCO VDIA IDENT,VDIA IDENT, RETR IDENT, CMDQ IDENT,F/C KEY IDENT, ANQ IDENT, VDU IDENT) TYPE CO-CMD = CASE IDENT OF VCO IDENT: VCO CMD TYPE UFCO IDENT: UFCO CC TYPE UFCO VDIA IDENT: UFCO VDIA CMD TYPE VDIA ┆
0x35500…35600 (53, 0, 5) Sector 3506ff00155341 ┆5 SAIDENT: VDIA UFCO CC TYPE RETR IDENT: RETR NOT TYPE VDU IDENT: VDU CMD TYPE END CASE TYPE VCO CMD = (INIT UFCO CMD, RESTART UFCO CMD, START UFCO CMD, STOP UFCO CMD, BLOCK UFCO CMD, CLOSE DOWN UFCO CMD) TYPE UFCO CC = (INIT U┆
0x35600…35700 (53, 0, 6) Sector 35079200155341 ┆5 SAFCO CC, RESTART UFCO CC) START UFCO CC, STOP UFCO CC, BLOCK UFCO CC, CLOSE DOWN UFCO CC, USER MODE CHANGE, PRECEDENCE CHANGE) 1. Answers to requests and retrieved messages. Figure 4.1.2.3-11 shows the software structure. s simple an┆
0x35700…35800 (53, 0, 7) Sector 3408ff00155341 ┆4 SA 1 TYPE UFCO VDIA CMD= (VDIA CLOSE DOWN, VDIA CANCEL, VDIA CLEAR VDU, VDIA SUSPEND, VDIA INPUT FORMAT, VDIA INPUT MSG, VDIA INPUT REQ, VDIA OUTPUT FORMAT, VDIA OUT┆
0x35800…35900 (53, 0, 8) Sector 3509ff00155341 ┆5 SA 1 VCO receives its input from S1. VCO is the coroutine which controls the activities of all the others through its control of UFCO. VCO starts and stops UFCO by executing a send oper┆
0x35900…35a00 (53, 0, 9) Sector 350aff00155341 ┆5 SAation on S2 with the proper command. When UFCO has executed a command sent by VCO, UFCO notifies VCO by performing a send operation on S1 with the relevant Command Completion code. UFCO receives its input from S2. UFCO controls the activities of V┆
0x35a00…35b00 (53, 0, 10) Sector 350bff00155341 ┆5 SADIA through S3. The control logic is analogous to that described above for VCO control of UFCO. On the basis of the UFCO Software Structure (ref. section 4.1.2.3.2) the control logic for UFCO can be constructed in the same way as done for VCO. V┆
0x35b00…35c00 (53, 0, 11) Sector 350cff00155341 ┆5 SADIA receives its input from S3. As the main work load due to I/O transfers and validation of messages / comments of the VUS process is actually performed by VDIA, a way to interrupt VDIA function execution within a reasonable time has to be consider┆
0x35c00…35d00 (53, 0, 12) Sector 350dff00155341 ┆5 SAed. This means that VDIA shall return to its waiting point frequently enough to fulfil the requirements for being controlable by UFCO. RETR receives input from the retrieve queue only, thus its control structure will be to await items to be insert┆
0x35d00…35e00 (53, 0, 13) Sector 350eff00155341 ┆5 SAed and process the occurred events. 4.1.3.3 UMAM Internal Data Flow UMAM receives input in the Command and Collect queues, thus the control structure will be to await item to be inserted and process the occured events. In figure 4.1.3.3-1 an┆
0x35e00…35f00 (53, 0, 14) Sector 350f8f00155341 ┆5 SA overview of the UMAM process is depicted. As UMAM is a process without coroutines, then no internal synchronization is required. ion 4.1.1 has as far as possible been used in the software structure charts, with the purpose of highlighting th┆
0x35f00…36000 (53, 0, 15) Sector 35006000155341 ┆5 ` SA 1 FIGURE 4.1.3.3-1 tions of VUS do not communicate with each other in a way requiring synchronization of their operations. However, they do exchange information directly (i.e. me┆
0x36000…36100 (54, 0, 0) Sector 3601ff00155341 ┆6 SAssages for release and release notifications). In the following subsections, the data flow and control logic internal to UMAM and VUS, i.e. between their coroutines, are described. 4.1.3.2 VUS Internal Data Flow and Coroutine Synchronization ┆
0x36100…36200 (54, 0, 1) Sector 3602ff00155341 ┆6 SA The data flow internal to VUS is depicted in fig. 4.1.3.2-2. The command parameters listed with the arrows 3 and 6 are identical, but those associated with arrow 3 are unformatted while those associated with arrow 6 are input via a format, refer se┆
0x36200…36300 (54, 0, 2) Sector 36039500155341 ┆6 SAction 4.1.1.3.4. In fig. 4.1.3.2-2, an overview of the VUS coroutines and the primitives (S1, S2, S3) used for synchronization is depicted. swers from SAR. The functions of RETR have been assigned to a separate coroutine, due to the fact that ┆
0x36300…36400 (54, 0, 3) Sector 36047d00155341 ┆6 } SA 1 Fig. 4.1.3-2 Dataflow between VUS Coroutines coroutine receives input from SAR via the Retrieve Queue and communicates with UFCO. This communication is done either by RETR s┆
0x36400…36500 (54, 0, 4) Sector 3605ff00155341 ┆6 SA 1 Legend for fig. 4.1.3.2-1 on Previous Page 1. Commands from SSC (e.g. start, stop) and time events. 2. Timer initiated update of VDU header (queues, time). 3. Control informa┆
0x36500…36600 (54, 0, 5) Sector 3606ff00155341 ┆6 SAtion from UVCO to UFCO. 4. Commands / parameters and function keys. 5. Transaction ID, classification, error messages. 6. Messages and system update requests. 7. Validated / unvalidated messages and system information. 8. Retrieved message┆
0x36600…36700 (54, 0, 6) Sector 3607c400155341 ┆6 D SAs. 9. Off-line retrieval results are sent to the response queue. 10. Retrieve finished signal to UFCO and on-line retrieval results. 11. Answers to requests and retrieved messages. Figure 4.1.2.3-11 shows the software structure. s simple an┆
0x36700…36800 (54, 0, 7) Sector 35088600155341 ┆5 SA 1 Fig. 4.1.3.2-2 VUS Coroutine Synchronization Overview For those commands representing the key commands with respect to the execution of the VUP main functions, the software s┆
0x36800…36900 (54, 0, 8) Sector 3609ff00155341 ┆6 SA 1 4.1.3 Data Flow and Control Logic In this section, the data flow between the VUS processes and coroutines will be described together with the control logic used to synchronize the┆
0x36900…36a00 (54, 0, 9) Sector 360aff00155341 ┆6 SAir execution of the VUP functions allocated to them. 4.1.3.1 Process Data Flow and Process Synchronization The data flow and process synchronization of the UMAM process and the VUS incarnations will be described for the UMAM process and one VUS┆
0x36a00…36b00 (54, 0, 10) Sector 360bff00155341 ┆6 SA process, as the flow and synchronization for all VUS incarnations are identical. In fig. 4.1.3.1-1 the data flow between UMAM and VUS is depicted. The flow is shown for the VUS process possessing full access rights to the CAMPS USER FUNCTIONS. H┆
0x36b00…36c00 (54, 0, 11) Sector 360cff00155341 ┆6 SAowever, the dataflow for a VUS process possessing access right to a subset of the CAMPS USER FUNCTIONS only (i.e. one or more of the subfunctions PREPARATION, RECEPTION or RELEASE) is indicated as well by means of the capital letters enclosed in par┆
0x36c00…36d00 (54, 0, 12) Sector 360dff00155341 ┆6 SAentheses, which denote the subfunction to which the flow is associated. VUS acts as the master(controlling) process and UMAM is the slave process, i.e. UMAM does not execute any function before requested by VUS, and while UMAM executes the request┆
0x36d00…36e00 (54, 0, 13) Sector 360e7400155341 ┆6 t SAed function, VUS stops its own processing and awaits the result to be delivered by UMAM in its answer queue. ss Invalid F/C Key Interrupt ned in the following subsections. The description of the software structure will mainly be in the form of so┆
0x36e00…36f00 (54, 0, 14) Sector 360f5f00155341 ┆6 _ SA 1 Figure 4.1.3-1 CO Structure - Execute F/C Key Function n section 4.1.1 has as far as possible been used in the software structure charts, with the purpose of highlighting th┆
0x36f00…37000 (54, 0, 15) Sector 3600ff00155341 ┆6 SA 1 The different incarnations of VUS do not communicate with each other in a way requiring synchronization of their operations. However, they do exchange information directly (i.e. me┆
0x37000…37100 (55, 0, 0) Sector 3701ff00155341 ┆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┆
0x37100…37200 (55, 0, 1) Sector 37023500155341 ┆7 5 SAig. 4.1.2.3-9 shows the software structure. ection 4.1.3. igher priority than VDIA. 4.1.2.1.1.3 VDU Dialogue Coroutines The VDU dialogue (VDIA) coroutine is responsible for the VDU format transfromation of input and output and for validat┆
0x37200…37300 (55, 0, 2) Sector 37037400155341 ┆7 t SA 1 FIGURE 4.1.2.3-9 VDIA Structure Structure tment of retrieval answers from SAR. The functions of RETR have been assigned to a separate coroutine, due to the fact that ┆
0x37300…37400 (55, 0, 3) Sector 3704ff00155341 ┆7 SA 1 4.1.2.3.4 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┆
0x37400…37500 (55, 0, 4) Sector 3705a800155341 ┆7 ( SAending Online Retrieval Results direct to UFCO or Off-line Retrieval Results indirectly via the Response Queue. Fig. 4.1.2.3-10 shows the software structure. within VUS. of functions onto processes and coroutines will be explained, based on┆
0x37500…37600 (55, 0, 5) Sector 37066f00155341 ┆7 o SA 1 fig. 4.1.2.3-10 RETR Structure ash Queue Monitoring to the preparation database and maintains the Outgoing Message Status, the Release Status, the Delivery Status and the Se┆
0x37600…37700 (55, 0, 6) Sector 3707f400155341 ┆7 t SA 1 4.1.2.3.5 UMAM Software Structure This processs receives input from other packages in the Collect and Command Queues. Figure 4.1.2.3-11 shows the software structure. s simple an┆
0x37700…37800 (55, 0, 7) Sector 36087700155341 ┆6 w SA 1 Fig. 4.1.2.3-11 UMAM Software Structure ng is depicted. For those commands representing the key commands with respect to the execution of the VUP main functions, the software s┆
0x37800…37900 (55, 0, 8) Sector 3709ff00155341 ┆7 SAtructure is slightly more detailed than for the others, as this is the most important to grasp when getting to understand the general structure. 4.1.2.3.2 UFCO Coroutine Software Structure This coroutine controls input / output to and from the ┆
0x37900…37a00 (55, 0, 9) Sector 370aff00155341 ┆7 SAVDU and the communication with other packages. It accepts commands from VCO and control VDIA via commands and process completion reports from VDIA corresponding to the commands. It communicates with VCO by sending completion report corresponding┆
0x37a00…37b00 (55, 0, 10) Sector 370bff00155341 ┆7 SA to commands received by VCO. The control of the MMI is exercised via function 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-6 to fig. 4.1.2.3-8 sh┆
0x37b00…37c00 (55, 0, 11) Sector 370c2400155341 ┆7 $ SAow the software structure. 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┆
0x37c00…37d00 (55, 0, 12) Sector 370d6e00155341 ┆7 n SA 1 Fig. 4.1.2.3-6 UFCO Structure ctions were to be executed with higher priority than User Transaction Control Functions. Thus these two functions have been allocated their own c┆
0x37d00…37e00 (55, 0, 13) Sector 370e9300155341 ┆7 SA 1 Fig. 4.1.2.3-7 UFCO Structure - Process Invalid F/C Key Interrupt ned in the following subsections. The description of the software structure will mainly be in the form of so┆
0x37e00…37f00 (55, 0, 14) Sector 370f8900155341 ┆7 SA 1 Fig. 4.1.2.3-8 UFCO Structure - Execute F/C Key Function n section 4.1.1 has as far as possible been used in the software structure charts, with the purpose of highlighting th┆
0x37f00…38000 (55, 0, 15) Sector 3700ff00155341 ┆7 SA 1 4.1.2.3.3 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┆
0x38000…38100 (56, 0, 0) Sector 3801ff00155341 ┆8 SAined in the structure charts in fig. 4.1.2.3-1 through fig. 4.1.2.3-5 and is related to fig. 4.1-7 and fig. 4.1-8 of the functional specifications. In fig. 4.1.2.3-1, the box PROCESS TEMCO COMMAND EXECUTION reflects that VCO controls the activitie┆
0x38100…38200 (56, 0, 1) Sector 38024600155341 ┆8 F SAs of UFCO. Control logic will be described in section 4.1.3. igher priority than VDIA. 4.1.2.1.1.3 VDU Dialogue Coroutines The VDU dialogue (VDIA) coroutine is responsible for the VDU format transfromation of input and output and for validat┆
0x38200…38300 (56, 0, 2) Sector 38038000155341 ┆8 SA 1 Fig. 4.1.2.3-1 VCO Coroutine Software Structure tment of retrieval answers from SAR. The functions of RETR have been assigned to a separate coroutine, due to the fact that ┆
0x38300…38400 (56, 0, 3) Sector 38048200155341 ┆8 SA 1 Fig. 4.1.2.3-2 VCO Structure TEMCO CMD Processing n of the RETR may be considered as low priority tasks, having in mind that during on-line retrieval all the other coroutines ┆
0x38400…38500 (56, 0, 4) Sector 38058d00155341 ┆8 SA 1 Fig. 4.1.2.3-3 UVCO Structure Update of Queue Status Line signed the lowest priority within VUS. of functions onto processes and coroutines will be explained, based on┆
0x38500…38600 (56, 0, 5) Sector 38068600155341 ┆8 SA 1 Fig. 4.1.2.3-4 VCO Structure - Flash Queue Monitoring to the preparation database and maintains the Outgoing Message Status, the Release Status, the Delivery Status and the Se┆
0x38600…38700 (56, 0, 6) Sector 38079a00155341 ┆8 SA 1 Fig. 4.1.2.3-5 VCO Structure - Process CMD Completion Report from UFCO. ocated their own process for the following reasons: a) To keep security access control as simple an┆
0x38700…38800 (56, 0, 7) Sector 3708ff00155341 ┆7 SA 1 In fig. 4.1.2.3-2 the Temco Command Processing is depicted. For those commands representing the key commands with respect to the execution of the VUP main functions, the software s┆
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 disigner 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 and references should be made to the functional specification given in section 4.1.1. The denotation used in section 4.1.1 has as far as possible been used in the software structure charts, with the purpose of highlighting th┆
0x38f00…39000 (56, 0, 15) Sector 3800ff00155341 ┆8 SAe close relationship. Thus the identification of programme tasks is given in narrative English and not as programme or procedure names. 4.1.2.3.1 VCO Coroutine Software Structure The software structure of the VDU Control Coroutine (VCO) is outl┆
0x39000…39100 (57, 0, 0) Sector 3901ff00155341 ┆9 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 ┆
0x39100…39200 (57, 0, 1) Sector 3902ff00155341 ┆9 SAinitiation / awaiting is performed by VDIA. UFCO is assigned a higher priority than VDIA. 4.1.2.1.1.3 VDU Dialogue Coroutines The VDU dialogue (VDIA) coroutine is responsible for the VDU format transfromation of input and output and for validat┆
0x39200…39300 (57, 0, 2) Sector 3903ff00155341 ┆9 SAion 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 ┆
0x39300…39400 (57, 0, 3) Sector 3904ff00155341 ┆9 SAthe 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 ┆
0x39400…39500 (57, 0, 4) Sector 3905b800155341 ┆9 8 SAassociated 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. of functions onto processes and coroutines will be explained, based on┆
0x39500…39600 (57, 0, 5) Sector 3906ff00155341 ┆9 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┆
0x39600…39700 (57, 0, 6) Sector 3907ff00155341 ┆9 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┆
0x39700…39800 (57, 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┆
0x39800…39900 (57, 0, 8) Sector 39097100155341 ┆9 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 ! ┆
0x39900…39a00 (57, 0, 9) Sector 390aff00155341 ┆9 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┆
0x39a00…39b00 (57, 0, 10) Sector 390bff00155341 ┆9 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┆
0x39b00…39c00 (57, 0, 11) Sector 390cff00155341 ┆9 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┆
0x39c00…39d00 (57, 0, 12) Sector 390dff00155341 ┆9 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┆
0x39d00…39e00 (57, 0, 13) Sector 390eff00155341 ┆9 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┆
0x39e00…39f00 (57, 0, 14) Sector 390f9100155341 ┆9 SA.2 User Function Control Coroutine The User Function Control (UFCO) Coroutine performs the direct control of the VDU Dialogue Coroutine. 03 196 07 01 82 11 49 26 03 82 13 44 0112A 100 16 47 816 49018 0 f *J 7 2 _┆
0x39f00…3a000 (57, 0, 15) Sector 3900ff00155341 ┆9 SA 1 UFCO performs the user transaction control, which consists of: - user transaction execution - user requested transaction interruption - user transaction accounting. The fu┆
0x3a000…3a100 (58, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(58,0, 1), len=0xff, h3=41155341}, f00=»1553A «, f01=»CPS/SDS/039 «, f02=»pn «, f03=»JBS «, f04=»4.1.2 «, f05=23-12-81 10:06, f06=» 11 «, f07=»36 «, f08=» 39119 «, f09=04-02-82 12:35, f10=» «, f11=»03 «, f12=» 196 «, f13=07-01-82 11:49, f14=26-03-82 13:44, f15=»0112A «, f16=»100 «, f17=» 16 «, f18=»47 «, f19=» 816 «, f20=» 49018 «, f21=» «, f22=» 0 «, f99=830010000110066610110480aaca15050000000000000037033201df}
0x3a100…3a200 (58, 0, 1) Sector 3a026400155341 ┆: d SA : : : : 9 9 9 9 8 8 8 8 8 8 8 8 7 7 7 7 7 7 7 7 7 6 6 6 6 6 6 5 5 5 5 5 4 4 4 4 3 3 3 3 2 2 2 2 2 1 1 1 0 0 0 0 0 0 / / / / . . . . - - - - - , , , , + + + + + * * * * * * ) ) ) ) ) ) ( ( ( # # # " " " RSIGT Dokument nr: Dokumentnavn: ┆
0x3a200…3a300 (58, 0, 2) Sector 3a039c00155341 ┆: SA 1 CPS/SDS/039 820104 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┆
0x3a300…3a400 (58, 0, 3) Sector 3a045f00155341 ┆: _ 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┆
0x3a400…3a500 (58, 0, 4) Sector 3a05ff00155341 ┆: 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┆
0x3a500…3a600 (58, 0, 5) Sector 3a06ff00155341 ┆: 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┆
0x3a600…3a700 (58, 0, 6) Sector 3a07ec00155341 ┆: 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 ┆
0x3a700…3a800 (58, 0, 7) Sector 39085e00155341 ┆9 ^ 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=!┆
0x3a800…3a900 (58, 0, 8) Sector 3a09ff00155241 ┆: RA 1 REQIRED STA EQ NORMAL? DIR AREA EQ NORMAL? INPUT DIRECTORY (4.2.5.6.16-2) SET DIR AREA = NORMAL DIR AREA EQ MIDNIGHT? INPUT DIRECTORY (4.2.5.6.16-2) SET DIR ARE┆
0x3a900…3aa00 (58, 0, 9) Sector 3a0a4c00155241 ┆: L RAA = MIDNIGHT Figure 4.2.5.6.16-1 =~ BV4C75:g=~ Bf4 ZMo Ck4 KMo Mj ~ B 4:g=~ J 4Cq5M")IMy,M1' R 4 'M, CV4:g=~ Bg4M73~ B)4Cq5! ="(=*(=N#FMC 2.=M ':>=V V u:A=!>= AH1 R^4 ]M, C 4:>=2A=Ms!:g=~ Jr4Mj2:g=~ B}4C75! ┆
0x3aa00…3ab00 (58, 0, 10) Sector 3a0bff00155241 ┆: RA 1 STORE FILE DIRECTORY (4.2.5.6.18) UMAM FILE ADDR. FIRST BYTE = O UMAM FILE ADDR.BYTE COUNT = SIZE (FILE DIR) UMAM BLE. ADDRESS = FILE DIR UMAM BLE.BYTE SIZE = SIZE (FILE DI┆
0x3ab00…3ac00 (58, 0, 11) Sector 3a0cff00155241 ┆: RAR) DIR AREA EQ MIDNIGHT? - SET DIR FILE ID = OLD DIR FILE SET DIR FILE ID = CURRENT DIR FILE CASE READBYTES (DIR FILE ID, UMAM FILE ADDR, UMAM BLE) (UMAM FILE ADDR, CC): ERROR OK ERROR? ANALYZE ERROR (CC, 0) OK? END CASE ┆
0x3ac00…3ad00 (58, 0, 12) Sector 3a0d2d00155241 ┆: - RA Figure 4.2.5.6.16-2 CPS/DBD/001 b) External Data UMAM TABLE REC 4.2.5.5 4.2.5.6.15.4 Procedure Design odule is to change the state of a CIF from passive to active. 4.2.5.6.13.2 Interfac┆
0x3ad00…3ae00 (58, 0, 13) Sector 3a0eff00155241 ┆: RA 1 4.2.5.6.17 INPUT PREP RECORDS 4.2.5.6.17.1 Functional Specification The purpose of this module is to read all prep records concerning a specified terminal. 4.2.5.6.17.3 Inte┆
0x3ae00…3af00 (58, 0, 14) Sector 3a0fff00155241 ┆: RArface Definition Call Specification a) INPUT PREP RECORDS (LTD : DESIGNATOR TYPE) (START: PREP REC TYPE STOP : PREP REC TYPE) b) INPUT PREP RECORDS (R1, R2, R3, R6) Register Convention) Call Register R1 L┆
0x3af00…3b000 (58, 0, 15) Sector 2800ff00155241 ┆( RATD (KEPT) R6 LINK (DEST) Return Register R2 points to first PREP REC R3 points to lad PREP REC R0 (DEST) R4 - R7 (DEST) 4.2.5.6.17.3 Data Description a) Data References EXPAND AREA TYPE refer 4.2.5.5 PREP REC TYPE refer 4.┆
0x3b000…3b100 (59, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(59,0, 1), len=0xff, h3=41155241}, f00=»1552A «, f01=»USER VDU «, f02=»bbh «, f03=»BBC «, f04=»CPS/039 4.2.5.6.16 «, f05=23-12-81 09:12, f06=» 9 «, f07=»18 «, f08=» 20835 «, f09=24-03-82 10:36, f10=» «, f11=»00 «, f12=» 2 «, f13=07-01-82 12:18, f14=04-05-82 13:06, f15=»0112A «, f16=» 40 «, f17=» 10 «, f18=»15 «, f19=» 248 «, f20=» 22364 «, f21=» «, f22=» @ «, f99=040010000110062710110480aaca15050000000000000037036800df}
0x3b100…3b200 (59, 0, 1) Sector 3b022800155241 ┆; ( RA ; ; ; : : : ( ( ( ' ' ' ' ' & & & & & & & & % % % % % $ $ $ $ $ $ # # # DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: ┆
0x3b200…3b300 (59, 0, 2) Sector 3b03a000155241 ┆; RA 1 CPS/SDS/039 BBC/820104 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┆
0x3b300…3b400 (59, 0, 3) Sector 3b04ff00155241 ┆; RA 1 4.2.5.6.16 INPUT FILE DIRECTORY 4.2.5.6.16.1 Functional Specification Depending on the status type the File Directory is updated with the Current or Old Directory. 4.2.5.6.1┆
0x3b400…3b500 (59, 0, 4) Sector 3b05ff00155241 ┆; RA6.2 Interface Definition Call Specification a) INPUT FILE DIRECTORY (REQ STA: REQ DIR TYPE) b) INPUT FILE DIRECTORY (R1, R6) Register Convention Call Register R1 REQ STA (DEST) R6 LINK (DEST) Return Register None R0 - R7 (┆
0x3b500…3b600 (59, 0, 5) Sector 3b06ff00155241 ┆; RADEST) 4.2.5.6.16.3 Data Definition a) Data References REQ DIR TYPE ref. 4.2.5.5 b) External Data REQUIRED STA ref. 4.2.5.5 OLD DIR FILE ref. 4.2.5.5 CURRENT DIR FILE ref. 4.2.5.5 UMAM BLE (m) ref. 4.2.5.5 UMAM FILE ADDR ref. 4.┆
0x3b600…3b700 (59, 0, 6) Sector 3b072500155241 ┆; % RA2.5.5 DIR AREA ref. 4.2.5.5 => w#6 I! "(=6 *(=#"(=6 IM2&! w"2< hMI sM & E 0= u M% :^=~ Bl1{M40sI:^=~ J 1!"<6;!#<6 !&<6 ! "$<! <6 {M;(s! 9"c=! "(= Z=q#p!"<6 !&<6 ! "$<!#<6 ! <6 {M)(sC I! <6 ! "(= <q#p!"<6 !#<6 ! "$<!&<6$`i6 {M)(sM &M7 ┆
0x3b700…3b800 (59, 0, 7) Sector 3a088300155241 ┆: RA 1 c) Local Data None 4.2.5.6.16.4 Procedure Design #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=!┆
0x3b800…3b900 (59, 0, 8) Sector 3b09ff00155341 ┆; 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┆
0x3b900…3ba00 (59, 0, 9) Sector 3b0aff00155341 ┆; 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 disigner the freedom to optimize disk-accesses and to utili┆
0x3ba00…3bb00 (59, 0, 10) Sector 3b0bff00155341 ┆; 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┆
0x3bb00…3bc00 (59, 0, 11) Sector 3b0cb800155341 ┆; 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┆
0x3bc00…3bd00 (59, 0, 12) Sector 3b0d6400155341 ┆; 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┆
0x3bd00…3be00 (59, 0, 13) Sector 3b0eff00155341 ┆; 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┆
0x3be00…3bf00 (59, 0, 14) Sector 3b0fff00155341 ┆; SAftware structure charts and references should be made to the functional specification given in section 4.1.1. The denotation used in section 4.1.1 has as far as possible been used in the software structure charts, with the purpose of highlighting th┆
0x3bf00…3c000 (59, 0, 15) Sector 3b00ff00155341 ┆; SAe close relationship. Thus the identification of programme tasks is given in narrative English and not as programme or procedure names. 4.1.2.3.1 VCO Coroutine Software Structure The software structure of the VDU Control Coroutine (VCO) is outl┆
0x3c000…3c100 (60, 0, 0) Sector 3c01ff00155341 ┆< 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 ┆
0x3c100…3c200 (60, 0, 1) Sector 3c02ff00155341 ┆< SAinitiation / awaiting is performed by VDIA. UFCO is assigned a higher priority than VDIA. 4.1.2.1.1.3 VDU Dialogue Coroutines The VDU dialogue (VDIA) coroutine is responsible for the VDU format transfromation of input and output and for validat┆
0x3c200…3c300 (60, 0, 2) Sector 3c03ff00155341 ┆< SAion 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 ┆
0x3c300…3c400 (60, 0, 3) Sector 3c04ff00155341 ┆< SAthe 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 ┆
0x3c400…3c500 (60, 0, 4) Sector 3c05b800155341 ┆< 8 SAassociated 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. of functions onto processes and coroutines will be explained, based on┆
0x3c500…3c600 (60, 0, 5) Sector 3c06ff00155341 ┆< 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┆
0x3c600…3c700 (60, 0, 6) Sector 3c07ff00155341 ┆< 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┆
0x3c700…3c800 (60, 0, 7) Sector 3b08ff00155341 ┆; 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┆
0x3c800…3c900 (60, 0, 8) Sector 3c097100155341 ┆< 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 ! ┆
0x3c900…3ca00 (60, 0, 9) Sector 3c0aff00155341 ┆< 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┆
0x3ca00…3cb00 (60, 0, 10) Sector 3c0bff00155341 ┆< 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┆
0x3cb00…3cc00 (60, 0, 11) Sector 3c0cff00155341 ┆< 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┆
0x3cc00…3cd00 (60, 0, 12) Sector 3c0dff00155341 ┆< 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┆
0x3cd00…3ce00 (60, 0, 13) Sector 3c0eff00155341 ┆< 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┆
0x3ce00…3cf00 (60, 0, 14) Sector 3c0f9100155341 ┆< SA.2 User Function Control Coroutine The User Function Control (UFCO) Coroutine performs the direct control of the VDU Dialogue Coroutine. 11 187 07 01 82 11 49 07 01 82 15 45 0112A 100 16 44 996 48822 0 f *J 7 _ _┆
0x3cf00…3d000 (60, 0, 15) Sector 3c00ff00155341 ┆< SA 1 UFCO performs the user transaction control, which consists of: - user transaction execution - user requested transaction interruption - user transaction accounting. The fu┆
0x3d000…3d100 (61, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(61,0, 1), len=0xff, h3=41155341}, f00=»1553A «, f01=»CPS/SDS/039 «, f02=»pn «, f03=»JBS «, f04=»4.1.2 «, f05=23-12-81 10:06, f06=» 11 «, f07=»36 «, f08=» 39119 «, f09=07-01-82 10:12, f10=» «, f11=»11 «, f12=» 187 «, f13=07-01-82 11:49, f14=07-01-82 15:45, f15=»0112A «, f16=»100 «, f17=» 16 «, f18=»44 «, f19=» 996 «, f20=» 48822 «, f21=» «, f22=» 0 «, f99=830010000110066610110480aaca15050000000000000037033201df}
0x3d100…3d200 (61, 0, 1) Sector 3d026400155341 ┆= d SA = = = = < < < < ; ; ; ; ; ; ; ; : : : : : : : : : 9 9 9 9 9 9 8 8 8 8 8 7 7 7 7 6 6 6 6 5 5 5 5 5 4 4 4 3 3 3 3 3 3 2 2 2 2 1 1 1 1 0 0 0 0 0 / / / / . . . . . - - - - - - , , , , , , + + + + + + * * * RSIGT Dokument nr: Dokumentnavn: ┆
0x3d200…3d300 (61, 0, 2) Sector 3d039c00155341 ┆= SA 1 CPS/SDS/039 820104 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┆
0x3d300…3d400 (61, 0, 3) Sector 3d045f00155341 ┆= _ 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┆
0x3d400…3d500 (61, 0, 4) Sector 3d05ff00155341 ┆= 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┆
0x3d500…3d600 (61, 0, 5) Sector 3d06ff00155341 ┆= 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┆
0x3d600…3d700 (61, 0, 6) Sector 3d07ec00155341 ┆= 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 ┆
0x3d700…3d800 (61, 0, 7) Sector 3c085e00155341 ┆< ^ 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=!┆
0x3d800…3d900 (61, 0, 8) Sector 00000000000000 ┆ ┆
[…0xf7…]
