top - download
⟦44c7113bb⟧ Wang Wps File
Length: 35172 (0x8964)
Types: Wang Wps File
Notes: Spelunked
Names: »~ORPHAN61.08«
Derivation
└─⟦518101e25⟧ Bits:30005806 8" Wang WCS floppy, CR 0110A
└─ ⟦this⟧ »~ORPHAN61.08«
WangText
J…00……00……00……00…=…0a……00……00…=…0b…= <…0e…<…07…;…00…:…0a…: 9…0c…9…06…8…0a…8…0f…8 8…06…7…0c…7…0d…7…0f…7…00…7…06…6…0a…6…0e…6…0f…6…06…5…0d…5 5…05…5…06…5…07…4…0d…4…0e…4…02…3…08…3…0f…3
…02…CPS/SDS/039
…02…820104…02……02…
USER VDU
DETAILED DESIGN SPECIFICATION…02……02…CAMPS
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
1 GENERAL .......................................
12
1.1 PURPOSE AND SCOPE .........................
12
1.2 APPLICABLE DOCUMENTS AND PROJECT REFERENCES
13
1.2.1 Applicable Documents .................
13
1.2.2 Reference Documents ...................
13
1.3 TERMS AND ABBREVIATIONS ...................
14
1.3.1 Terms .................................
14
1.3.2 Abbreviations .........................
14
2 SUMMAY OF REQUIREMENTS .......................
15
2.1 PACKAGE DESCRIPTION .......................
15
2.2 PACKAGE FUNCTIONS .........................
21
2.2.1 Main Functions ........................
21
2.2.1.1 Queue Status Display..............
22
2.2.1.2 Information Concerning the Trans-
action in Progress ................
25
2.2.1.3 Display of Queued Information .....
25
2.2.1.3.1 The Receive Queue .............
25
2.2.1.3.2 The Respnse Queue ............
26
2.2.1.3.3 The Release Queue .............
26
2.2.1.4 Message/Comment Preparation .......
27
2.2.1.5 Treatment of User Request .........
31
2.2.1.6 Maintenance of Message Status Files
31
2.2.1.6.1 Outgoing Message Status .......
31
2.2.1.6.2 Delivery Status ...............
31
2.2.1.6.3 Release Status ................
33
2.2.2 Functional Responsibilities ...........
33
2.2.2.1 Initialization, Close Dow and
Restart ...........................
33
2.2.2.1.1 Initialization ................
33
2.2.2.1.2 Close Down ....................
33
2.2.2.1.3 Restart .......................
34
2.2.2.2 Checkpointing and Reovery ........
34
2.2.2.3 Error Detecting and Error Handling
34
2.2.2.4 Integrity of Operation ............
35
2.2.2.5 Data Collection ...................
35
2.2.2.5.1 Log Collection ................
35…86…1 …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02…
2.2.2.5.2 Statistics Information ........
35
2.2.2.5.3 Reports .......................
35
2.2.2.6 Security ..........................
38
2.3 CHARACTERISTICS ...........................
40
2.3.1 Timing ................................
40
2.3.2 Throughput ............................
41
2.3.3 Flexibility ..........................
42
2.3.4 Accuracy ..............................
42
3 ENVIRONMENT ...................................
43
3.1 EQUIPMENT .................................
43
3.2 SOFTWARE ..................................
43
3.2. System Software .......................
43
3.2.2 Development Support Software ..........
43
3.3 INTERFACES ................................
43
3.3.1 External Interfaces ...................
43
3.3.2 Package Interfaces ...................
44
3.3.2.1 Traffic Handling (THP) I/F ........
44
3.3.2.2 Distribution (MDP) I/F ............
44
3.3.2.3 Storage and Retrieval (SAR) I/F ...
44
3.3.2.4 Log and Accountability (LOG) I/F ..
45
3.3.2.5 Statistics (STP) I/F ..............
45
3.3.2.6 SSC Software I/F ..................
45
3.3.2.7 Table Management Package (TMP) I/F
45
3.4 FUNCTIONS MAINTAINED BY OTHER PACKAGES ....
46
4 PACKAGE DESIGN ...............................
47
4.1 PACKAGE OVERVIEW ..........................
47
4.1.1 Functional Specification ..............
49
4.1.1.1 TEMCO Control Functions ...........
51
4.1.1.2 Queue Status Maintenance ..........
53
4.1.1.3 ser Transaction Control ..........
56
4.1.1.3.1 Transaction Accounting ........
56
4.1.1.3.2 Transaction Interruption ......
61
4.1.1.3.3 Command Interpretation ........
63
4.1.1.3.4 Command Execution .............
65
4.1.1.3.5 Start/Stop Transaction
Execution .....................
67
4.1.1.3.6 Preparation of Messages/
Comments ......................
69
4.1.1.3.7 Presentation of Queued Infor-
mation .......................
71…86…1 …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02…
4.1.1.3.8 Requests to CAMPS System ......
73
4.1.1.3.9 Dialogue Formatting ...........
75
4.1.1.310 Format Validation .............
77
4.1.1.4 User Message Access Monitoring ....
79
4.1.1.4.1 Preparation Database Access
Control .......................
80
4.1.1.4.2 Message/Comment Status
Maintenance...................
83
4.1.2 Software Specification ................
87
4.1.2.1 VUS Process .......................
87
4.1.2.1.1 VUS Coroutines ................
90
4.1.2.1.1.1 VDU Control Coroutine .....
90
4..2.1.1.2 User Function Control
Coroutine .................
90
4.1.2.1.1.3 VDU Dialogue Coroutine ....
91
4.1.2.1.1.4 Retrieve Coroutine ........
91
4.1.2.2 UMAM Process ......................
92
4.1.2. Software Structure ................
92
4.1.2.3.1 VCO Coroutine Software
Structure .....................
94
4.1.2.3.2 UFCO Coroutine Software
Structure .....................
100
4.1.2.3.3 VDIA CoroutineSoftware
Structure .....................
104
4.1.2.3.4 RETR Coroutine Software
Structure .....................
106
4.1.2.3.5 UMAM Software Structure .......
108
4.1.3 Data Flow and Control Logic ...........
110
4.1.3.1 Process Data Flow and Process
Synchronization ...................
110
4.1.3.2 VUS Internal Data Flow and
Coroutine Synchronization .........
112
4.1.3.3 UMAM Internal Data Flow ...........
116
41.4 Common Package Data ...................
118
4.1.5 Common Package Procedures .............
124
4.1.5.1 VUS QUEUE ERROR ...................
124
4.1.5.2 VUS INTERNAL ERROR ................
125
4.1.6 Global Data ..........................
126
4.1.7 Interfaces ............................
126
4.1.7.1 External Interfaces ...............
127…86…1 …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02…
4.1.7.2 Package Interfaces ................
127
4.1.7.2.1 Traffic Handling (THP) I/F ....
127
4.1.7..2 Distribution (MDP) I/F ........
127
4.1.7.2.3 Storage and Retrieval (SAR) I/F
127
4.1.7.2.4 LOG and Accountability (LOG)
I/F ...........................
127
4.1.7.2.5 Statistics (STP) I/F ..........
128
4.17.2.6 SSC Software I/F ..............
128
4.1.7.2.7 Table Management Package I/F ..
128
4.1.7.3 Sub-Package Interfaces ............
128
4.1.7.3.1 Process Interfaces ............
128
4.1.7.3.2 Coroutine Interfaces .........
129
4.2 SUBPACKAGE SPECIFICATIONS .................
131
4.2.1 VDU Control Subpackage ................
131
4.2.1.1 Functional Specification ..........
131
4.2.1.1.1 Initialization ................
133
4.2.1.1.2 TEMO Command Processing ......
133
4.2.1.1.3 Flash Item Control ............
134
4.2.1.1.4 Timer Event Processing ........
134
4.2.1.1.5 VDU Header Control ............
134
4.2.1.1.6 UFCO Control ..................
134
4.2.1.1.7 Error Reporting ............... 135
4.2.1.2 Software Structure ................
135
4.2.1.2.1 VCO Control ...................
135
4.2.1.2.2 TEMCO Command Processing ......
136
4.2.1.2.3 Flash Queue Monitorin ........
137
4.2.1.2.4 Timer Event Processing ........
138
4.2.1.2.5 Common Procedures .............
138
4.2.1.3 Dataflow and Control Logic
within VCO .......................
140
4.2.1.4 VCO Module Specificatio ..........
146
4.2.1.4.1 VCO CONTROL Specification .....
146
4.2.1.4.2 TEMCO CMD. PROCESSING ..........
155
4.2.1.4.3 FLASH QUEUE MONITORING .........
159
4.2.1.4.4 TIMER EVENT PROCESSING ........
164
4.2.1.5 Commn Subpackage Data .............
167
4.2.1.6 Common Subpackage Procedures .......
167
4.2.1.6.1 SIGNAL UFCO ....................
167
4.2.1.6.2 SET PRECEDENCE FIELDS ..........
170…86…1 …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02…
4.2.1.6.3 QUEUE FIELDS UPDATE ............
171
4.2.1.6.4 DISPLAY VDU HEADER .............
174
4.2.1.65 SEARCH FLASH QUEUES ............
175
4.2.1.6.6 GET FQT ........................
176
4.2.1.6.7 REQUEST TIME OUT ...............
178
4.2.1.6.8 CANCEL TIMEOUT .................
179
4.2.1.6.9 GET DATE TIME ..................
80
4.2.1.6.10 DISM QEL .......................
182
4.2.1.6.11 INVERT AND BELL ................
183
4.2.1.6.12 REMOVE FLASH ITEM ..............
185
4.2.1.6.13 GET QUEUE LENGTH ...............
186
4.2.1.6.14 EXTRACT NO OF COO MSG .........
187
4.2.1.7 Subpackage Interfaces ..............
189
4.2.1.7.1 VCO-UFCO Interfaces ............
189
4.2.1.7.2 UFCO-VCO Interfaces ............
189
4.2.2 User Function Control Subpackage .......
190
4.2.2.1 Functional Specification ...........
190
4.2.2.1.1 System Control .................
196
4.2.2.1.2 Transaction Accounting .........
197
4.2.2.1.3 Transaction Creation ...........
197
4.2.2.1.4 Format Sequence Function .......198
4.2.2.1.4.1 Start Execution ............
199
4.2.2.1.4.2 Stop Execution .............
200
4.2.2.1.4.3 Queue Request ..............
201
4.2.2.1.4.4 Request to CAMPS System ....
201
4.2.2.1.5 Error Handling ................
203
4.2.2.2 Software Structure .................
203
4.2.2.3 Data Flow and Control Logic Within
UFCO ...............................
206
4.2.2.3.1 Data Flow ......................
206
4.2.2.3.2 Control ogic ..................
206
4.2.2.4 Module Specification ...............
234
4.2.2.4.1 UFCO MAIN ......................
234
4.2.2.4.2 RESTART UFCO ...................
242
4.2.2.4.3 VUS ANSWER QUEUE PROCESSING ....
248
42.2.4.4 VUS F/C KEY PROCESSING .........
260
4.2.2.4.5 VCO CMO PROCESSING .............
269
4.2.2.4.6 VDIA CC PROCESSING .............
272
4.2.2.4.7 RETR OP PROCESSING .............
276
4.2.2.4.8 VUS IN/OUT LINE ...............
279
4.2.2.4.9 VUS CMD PENDING ................
282…86…1 …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02…
4.2.2.4.10 VUS DISPLAY RESP MSG ...........
290
4.2.2.4.11 VUS SEQUENCE ...................
294
4.2.2.5 Common Subpackage Data .............
307
4.2.2.6 Common Subpackage Procedures .......
308
4.2.2.6.1 VDU INIT .......................
308
4.2.2.6.2 RESET CURSOR ...................
311
4.2.2.6.3 RESET CURSOR ON COMMAND LINE ..
314
4.2.2.6.4 DISPLAY ERROR MESSAGE ..........
316
4.2.2.7 Subpackage Interfaces ..............
319
4.2.2.7.1 UFCO-VDIA Interfaces ...........
319
4.2.2.7.2 VCO-UFCO Interfaces ............
319
4.2.2.7.3 RETR-UFCO Inerfaces ...........
319
4.2.2.7.4 VDIA-UFCO Interfaces ...........
320
4.2.2.7.5 UFCO-VCO Interfaces ............
320
4.2.2.7.6 UFCO-UMAM Interfaces ...........
320
4.2.2.7.7 UMAM-UFCO Interfaces ...........
320
4.2.3 Dalogue Subpackage ....................
321
4.2.3.1 Functional Specification ...........
321
4.2.3.1.1 Output of Data .................
330
4.2.3.1.2 Input of Data ..................
330
4.2.3.1.3 Validate Data .................
331
4.2.3.1.3.1 Syntax Validation ..........
331
4.2.3.1.3.2 Semantic Validation ........
332
4.2.3.1.3.3 Display of Error Codes .....
332
4.2.3.2 Software Structure .................
332
4.2.3.3 Data Flow and Conrol Logic
within VDIA .......................
336
4.2.3.3.1 Data Flow ......................
336
4.2.3.3.2 Control Logic ..................
337
4.2.3.4 Module Specification ...............
342
4.2.3.4.1 VDU MAIN MOULE ................
342
4.2.3.4.2 START VDU OUTPUT FORMAT ........
353
4.2.3.4.3 START VDU OUTPUT MESSAGE .......
358
4.2.3.4.4 START APPEND ...................
365
4.2.3.4.5 VDU DATA OUTPUT ................
370
4.2.3..6 BUILD MMON RECORD ..............
374
4.2.3.4.7 BUILD FIELD AND BUFFER LIST ....
377
4.2.3.4.8 START VDU INPUT ................
380
4.2.3.4.9 VDU DATA INPUT .................
383
4.2.3.4.10 VALIDATION .....................388
4.2.3.4.11 DISPLAY ERROR CODE TABLE .......
391
4.2.3.4.12 SEMANTIC VALIDATION OF FORMAT
A AND FORMAT C ................
396…86…1 …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02…
4.2.3.4.13 SEMANTIC VALIDATION OF FORMAT G
397
4.2.3.4.14 SEMANTIC VALIDATION OF FORMAT H
398
4.2.3.5 ommon Subpackage Data ............ 399
4.2.3.6 Common Subpackage Procedures ......
407
4.2.3.6.1 MESSAGE HANDLING INSTRUCTION ..
407
4.2.3.7 Subpackage Interfaces .............
410
4.2.3.7.1 UFCO-VDIA Interfaces ..........
41
4.2.3.7.2 VDIA-UFCO Interface ...........
410
4.2.4 Retrieve Subpackage ....................
411
4.2.4.1 Functional Specification ...........
411
4.2.4.2 Software Structure .................
413
4.2.4.3 Data Flow and Control ogic Within
RETR ...............................
415
4.2.4.3.1 Data Flow ......................
415
4.2.4.3.2 Control Logic ..................
415
4.2.4.4 Module Specification ...............
421
4.2.4.4.1 RETR MAIN odule ............... 421
4.2.4.4.2 RETR QEL INVEST Module .........
426
4.2.4.5 Common Subpackage Data .............
433
4.2.4.6 Common Subpackage Procedures .......
433
4.2.4.6.1 DISMANTLE RETR QEL .............
433
4.2.4. Subpackage Interfaces ..............
436
4.2.4.7.1 RETR UMAM Interfaces ...........
436
4.2.4.7.2 RETR UFCO Interfaces ...........
436
4.2.5 User Message Access Monitoring
Subpackage .............................
436
4.2.51 Functional Specification ...........
436
4.2.5.1.1 Collect Status .................
438
4.2.5.1.2 Generate Status ................
438
4.2.5.1.2.1 User Requested Status ......
438
4.2.5.1.2.2 Periodic Generated Status ..
438
4.2.5.1.3 Message Access Control .........
439
4.2.5.2 Software Structure .................
439
4.2.5.2.1 Command Queue Items ............
442
4.2.5.2.2 Collect Queue Items ............
442
4.2.5.3 Data Flow and Control Logic Within
UMAM ...............................
443
4.2.5.3.1 DataFlow ...................... 443
4.2.5.3.2 Control Logic ..................
443
4.2.5.4 Module Specification ...............
453
4.2.5.4.1 UMAM MAIN Module ...............
453
4.2.5.4.2 EXECUTE START FUNCTION Module ..
459
42.5.4.3 SUBQ ONE ACTION Module .........
459
4.2.5.4.4 SUBQ TWO ACTION Module .........
468
4.2.5.4.5 SUBQ THREE ACTION Module .......
477
4.2.5.4.6 SUBQ FOUR ACTION Module ........
482
4.2.5.4.7 SUBQ FIVE ACTION Module ........485
4.2.5.4.8 PERIODIC STATUS Module .........
489
4.2.5.4.9 GEN REL STA Module .............
493
4.2.5.4.10 GEN DEL STA Module ...........
498
4.2.5.4.11 GEN OUT STA Module ...........
503
4.2.5.4.12 SORT RECORDS Module ......... 509
4.2.5.4.13 GEN SVC STA Module ...........
516
4.2.5.4.14 DELETE REQUEST Module ........
522
4.2.5.4.15 INCLUDE IN INTA Module .......
528
4.2.5.4.16 SORT/STORE INTA Module .......
532
4.2.5.4.17 INCLUDE IN PREP odule ....... 537
4.2.5.5 Common Subpackage Data .............
541
4.2.5.6 Common Subpackage Procedures .......
541
4.2.5.6.1 UMAM QEL DISMANTLE .............
541
4.2.5.6.2 VDU PAGE LOOKUP ................
545
4.2.5.6.3 SENDITEM ...................... 548
4.2.5.6.4 SEND RESPONSE ..................
551
4.2.5.6.5 CREATE/OPEN STATUS CIF .........
553
4.2.5.6.6 CLOSE/SEND STATUS CIF ..........
556
4.2.5.6.7 Intentionally Left Blank .......
559
4.25.6.8 STORE PREP AREA ................
560
4.2.5.6.9 INPUT COMPLETE INTA ............
562
4.2.5.6.10 STORE INT AREA ...............
565
4.2.5.6.11 UQ ERROR .....................
567
4.2.5.6.12 INPUT PREP AREA ..............
568
4.2.5.6.13 LOOKUP STATUS CIF ............ 571
4.2.5.6.14 STORE SORTED DATA ............
573
4.2.5.6.15 CONVERT STORE LTD ............
575
4.2.5.6.16 INPUT FILE DIRECTORY .........
577
4.2.5.6.17 INPUT PREP RECORDS .......... 581
4.2.5.6.18 STORE FILE DIRECTORY .........
584
4.2.5.6.19 CLOSE/SEND MIDNIGHT STATUS ...
586
4.2.5.6.20 SEND CIF TO MDCO .............
588
4.2.5.6.21 LOOKUP STATUS REC ............
591…86…1 …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02…
4.2.5.6.22 INPUT INT AREA ...............
595
4.2.5.6.23 INPUT EXPAND AREA ............
598
4.2.5.6.24 TORE EXPAND AREA ............ 600
4.2.5.6.25 THRESHOLD WARNING ............
602
4.2.5.6.26 LOOKUP EMPTY PREP REC ........
604
4.2.5.6.27 EXCLUDE FROM PREP ............
607
4.2.5.6.28 UNLOCK PASSIVE CIFS ..........
609
4.2.56.29 SEND REPORT .................. 611
4.2.5.6.30 RESERVE BUFFER ...............
614
4.2.5.6.31 UINT ERROR ...................
615
4.2.5.7 Subpackage Interfaces ..............
616
4.3 MEMORY LAYOUT ..............................
16…86…1 …02… …02… …02… …02…
1̲ ̲ ̲G̲E̲N̲E̲R̲A̲L̲
1.1 P̲U̲R̲P̲O̲S̲E̲ ̲A̲N̲D̲ ̲S̲C̲O̲P̲E̲
a) The VDU User Package Specification for the CAMPS
Project/4040 is written to fulfil the following
objectives:
1) To provide a detailed dfinition of the VDU user
package function and software architecture.
2) To provide user operational and development personnels
with details of the ongoing analysis.
3) To define in details the interfaces with other
packages and to describe thir facilities.
b) The VDU user package specification defines the
functions and software architecture of the package
to a level sufficient for a programmer to start
detailed design with a minimum of design effort
of the architecture.
The VDU usr package constitutes one of the building
stores of the TEP package.
All VDU user package internal data and interfaces
are defined within this document in detail. For a
detailed data description of data external to the
VDU user package and interaces to other packages
refer the data definition document and the relevant
interface documents.
1.2 A̲P̲P̲L̲I̲C̲A̲B̲L̲E̲ ̲D̲O̲C̲U̲M̲E̲N̲T̲S̲ ̲A̲N̲D̲ ̲P̲R̲O̲J̲E̲C̲T̲ ̲R̲E̲F̲E̲R̲E̲N̲C̲E̲S̲
1.2.1 A̲p̲p̲l̲i̲c̲a̲b̲l̲e̲ ̲D̲o̲c̲u̲m̲e̲n̲t̲s̲
CAMPS System Requirements
CPS/210/SYS/0001
User Procedures and Associated Formats
CPS/230/ICD/001
CAMPS System Design Specification
CPS/SDS/001
Database Design Document
CPS/DBD/001
CAMPS Software Interface Control Document
CPS/ICD/009
1.2.2 R̲e̲f̲e̲r̲e̲n̲c̲e̲ ̲D̲o̲c̲u̲m̲e̲n̲t̲s̲
OCUMENT NAME DOCUMENT NUMBER
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
CAMPS System Functions CPS/SDS/024
Message Management CPS/SDS/025
Table Managment CPS/SDS/026
Input/Output Control CPS/SDS/028
System Status and Control CP/SDS/029
Storage and Retrieval CPS/SDS/030
Statistics CPS/SDS/031
Logging CPS/SDS/032
Traffic Handling CPS/SDS/033
Message Distribution CPS/SDS/034
Supervisor VDU CPS/SDS/035
Supervisor Printer CPS/SDS/036
MDCO VDU CPS/SDS/037
MSO VDU CS/SDS/038
OCR CPS/SDS/040
Printer CPS/SDS/041
1.3 T̲E̲R̲M̲S̲ ̲A̲N̲D̲ ̲A̲B̲B̲R̲E̲V̲I̲A̲T̲I̲O̲N̲S̲
1.3.1 T̲e̲r̲m̲s̲
1.3.2 A̲b̲b̲r̲e̲v̲i̲a̲t̲i̲o̲n̲s̲
PDB Preparation Data Base
RETR Retrieve Coroutine
UFCO User Function Control Coroutine
UMAM User Message Acces Monitoring
VCO VDU Control Coroutine
VDIA VDU Dialogue Coroutine
VUP VDU User Package
VUS VDU User Sub-Process
HDB Historical Data Base
FQT Flash Queue Timeout
2̲ ̲ ̲S̲U̲M̲M̲A̲R̲Y̲ ̲O̲F̲ ̲R̲E̲Q̲U̲I̲R̲E̲M̲E̲N̲T̲S̲
2.1 P̲A̲C̲K̲A̲G̲E̲ ̲D̲E̲S̲C̲R̲I̲P̲T̲I̲O̲N̲
The V̲DU U̲ser P̲ackage (VUP) constitutes the only means
by which CAMPS Personnel may gain access to the services
of the CAMPSuser function.
a) The CAMPS user function is made up of three subfunctions,
Preparation, Reception, and Release. A VDU or user
may have access rights to one or more of the subfunction
services as specified by the Supervisor. In figure
2.1-1 overlaf the services of the CAMPS user function
and the sub-functions are depicted.
b) The VDU user package (VUP) implements all the services
of the CAMPS user function, which implies the following
responsibilities:
1) Interface the user to the CAMS system, i.e.
Man/Machine I/F Support and monitoring
2) Direct all user requests/commands to the relevant
package within CAMPS
3) Present to the user information sent to his
VDU
4) Supervise/allow the user preparing messages
and comments.
c) The packages to which VUP interfaces are
1) I/O Control Software
2) CAMPS systems Functions
3) Storage and File Management
4) SS&C Software
5) Traffic Handling
6) Distribution
7) Table Management
8) Storage and Retrieal
9) Log and Accountability
10) Statistics
Figure 2.1-1
In figure 2.1-2 an overview of the interfaces of VUP
is depicted.
In figure 2.1-3 the message flow between VUP and the
rest of the CAMPS system as well as the VUP internal
flow re depicted, highlighting the most important functional
interfaces.
Information flow between VUP and other CAMPS packages
is depicted in figure 2.1-4.
Figures 2.1-2 to -4
2.2 P̲A̲C̲K̲A̲G̲E̲ ̲F̲U̲N̲C̲T̲I̲O̲N̲S̲
In this section the functions to be performed by VUP
are outlined. As stated in section 2.1 the main task
of VUP is to implement the CAMPS user function. Te
CAMPS user function and the related requirement will
be treated as a whole, i.e. the three subfunctions
Preparation, Reception, and Release constituting the
CAMPS user function and to each of which access must
be granted by the supervisor will betreated together
in most sub-sections. For the limitations imposed if
a user only possesses access rights to one or two of
the subfunctions refer subsection 2.2.2.1 and 2.2.2.6.
2.2.1 M̲a̲i̲n̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲ ̲(̲N̲o̲r̲m̲a̲l̲ ̲O̲p̲e̲r̲a̲t̲i̲o̲n̲)̲
The main functions to be mplemented by VUP are:
1) Continuously display of queue status information
2) Continuously display information concerning the
transaction in progress
3) The means for display of queued information
4) The means for message/comment preparatio
5) The means for directing requests to CAMPS and deliver
responses to the user
6) Maintain and update message status files
In figure 2.2-1 an overview of all transaction, which
may be initiated by the user is shown, together with
an indicatin of whether the transaction refers to preparation/request
or display of queued information.
2.2.1.1 Q̲u̲e̲u̲e̲ ̲S̲t̲a̲t̲u̲s̲ ̲D̲i̲s̲p̲l̲a̲y̲
The upper 5 lines of the VDU screen is named the VDU
header area, refer figure 2.2-2.
The second line of the VDU header area is used for
queue stats display. For each of the three queues;
receive queue (DISP), response queue (RESP) and release
queue (RELS) the total amount of messages queued for
presentation shall be displayed.
The total amount of messages for coordination queued
in the recive queue shall be displayed in the field
marked COOR.
The distribution of messages on precedence levels for
the two precedence queues receive and release shall
be displayed in the fields marked: ZZ (FLASH), OO (IMMEDIATE),
PP (PRIORITY), RR (ROUINE).
…01…QUEUED INFORMATION
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
FORMAT TRANSACTION DATA ENTRY RECEIVE RESPONSE
RELEAS
ID REQUEST QUEUE QUEUE QUEUE
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
A New msg. prep. X
B Msg coordination X
C1 Cont. msg prep X
D Msg release
X
E1 Incom. msg. pres. X
E2 Outg. msg. present X
F Release notificat. X
G1 New comment prep. X
G2 Comment present X
G3 Cont. Comment prep X
H Retrieval X X
M Prep. predef. msg X
N Outg. msg. status X
O Append msg. X X
P1 Deletion request X
P2 Deltion notificat. X
Q Msg release status X
R Delivery Status X
FIGURE 2.2-1…01…TRANSACTION RELATED TO THE USER FUNCTION…86…1 …02… …02… …02…
…02… …02…
FIGURE 2.2-2
2.2.1.2 I̲n̲f̲o̲r̲m̲a̲t̲i̲o̲n̲ ̲C̲o̲n̲c̲e̲r̲n̲i̲n̲g̲ ̲t̲h̲e̲ ̲T̲r̲a̲n̲s̲a̲c̲t̲i̲o̲n̲ ̲i̲n̲ ̲P̲r̲o̲g̲r̲e̲s̲s̲
The first line of the VDU Header area (refer fig. 2.2-2)
shall be used to identify to the user the transaction
in progrss (TERMINAL FUNCTION) and the classification
of the information currently accessed (CLASSIFICATON).
Whenever the classification is unknown or no transaction
is in progress the maximum classification to which
the user may gain access through thisVDU shall be displayed.
2.2.1.3 D̲i̲s̲p̲l̲a̲y̲ ̲o̲f̲ ̲Q̲u̲e̲u̲e̲d̲ ̲I̲n̲f̲o̲r̲m̲a̲t̲i̲o̲n̲
An overview of transactions to be performed in the
Response Mode, Receive Mode and Release Mode of operation
together with the transaction control capabilities
in each mode of operaion is given in figure 2.2-4.
For the sake of completeness the Interactive mode of
operation is reflected as well.
2.2.1.3.1 T̲h̲e̲ ̲R̲e̲c̲e̲i̲v̲e̲ ̲Q̲u̲e̲u̲e̲
When the user enters the command RECV (precedence)
VUP shall enter the Receive Mode of operation. Th user
shall now be able to inspect the items in the receive
queue one by one, remove an inspected item from the
queue, or request a printed copy of the item. This
may be done by means of the function keys: Keep and
Present, Delete and Present, Prin, Cancel.
The first message to be presented to the user shall
be the first queued of the precedence specified by
the command parameter. If none is specified the first
item queued with highest precedence shall be displayed.
When the user activats the function key Suspend, VUP
shall exit the Receive Mode of operation.
2.2.1.3.2 T̲h̲e̲ ̲R̲e̲s̲p̲o̲n̲s̲e̲ ̲Q̲u̲e̲u̲e̲
When the user enters the command RESP, VUP shall enter
the Response Mode of operation.
The user shall now be able to inspect the items in
the respose queue one by one, remove an inspected item
from the queue or request a printed copy of the item.
This may be done by means of the function keys; Keep
and Present, Delete and Present, Print, Cancel.
The first item to be presented to the user shll be
the first queued.
When the user activates the function key suspend VUP
shal exit the response mode of operation.
2.2.1.3.3 T̲h̲e̲ ̲R̲e̲l̲e̲a̲s̲e̲ ̲Q̲u̲e̲u̲e̲
The release queue contains messages for release.
When the releaser enters the command RELS (recedence)
VUP shall enter the Release Mode of operation. The
releaser shall now be able to inspect the items in
the release queue one by one, enter his release decision
and/or request a printed copy of the item.
To each item in the release queueis attached an input
format for the entry of the release decision. After
input of the decision the releaser notifies VUP that
a release decision has been entered by means of the
function key ENTER. VUP remove the item from the queue
and executes th decision.
Inspection and print requests are issued to VUP by
means of the function keys: Keep and Present, Print.
The first message to be presented to the releaser shall
be the first queued of the precedence specified by
the command parameter.If none is specified the first
item queued with highest precedence shall be displayed.
When the releaser activates the function key Suspend
VUP shall exit the Release Mode of operation.
2.2.1.4 M̲e̲s̲s̲a̲g̲e̲/̲C̲o̲m̲m̲e̲n̲t̲ ̲P̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲
a) Message/comment preparation consists of two functions:
Preparation of New messages/comments, Editing of
existing Messages and Comments.
b Messages may be edited until they are requested
released. If the release request is rejected or
deferred the messages become available for editing
again. After release the message is not available
for editing.
c) Comments may be edited until the are requested
sent (distributed internally).
d) It is the responsibility of VUP to send retrieval
key to SAR for the first draft of a message.
e) It is the responsibility of VUP to send retrieval
keys for a comment at the time of the send requst.
f) Message/Comment preparation is achieved through
one of the transactions listed below:
1) New Message Preparation (format A)
2) Continue Message Preparation (format C1)
3) Prepare Predefined Message (format M)
4) New Comment Prepartion (format G1)
5) Continue Comment Preparation (format G3)
g) f1), f3), and f4) above requires that VUP inserts
the new item in the preparation database. Whereas
f2) and f5) above require VUP to retrieve the items
which the user wants to editfrom the preparation
database.
h) In figure 2.2-5 the different stages of a preparation
transaction (refer f) above) is shown. The user
access to control the transaction by means of function
keys is shown for each stage as well.
1) For message the request for further treatment
may be:
- APPEND
- COORDINATE
- SEND FOR RELEASE
- DEFER …86…1 …02… …02… …02… …02…
2) For comments the request for further treatment
may be:
- SEND
- DEFER
Figure 2.2-4
Figure 2.2-5
2.2.1.5 T̲r̲e̲a̲t̲m̲e̲n̲t̲ ̲o̲f̲ ̲U̲s̲e̲r̲ ̲R̲e̲q̲u̲e̲s̲t̲s̲
Besides the user requests which may be entered as part
of a transaction, the requests listed below may be
issued by the user:
- Retrieval (fomat H)
- Deletion Request (format P1)
- Outgoing Message Status (format N)
- Delivery Status (format R)
- Release Status (format Q)
In figure 2.2-6 the different stages of a request transaction
is shown, together with the user access to contrl the
transaction by means of function keys in each stage.
2.2.1.6 M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲ ̲o̲f̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲S̲t̲a̲t̲u̲s̲ ̲F̲i̲l̲e̲s̲
It is the responsibility of VUP to maintain and update
the following status files for each VDU:
- Outgoing Message Status
- Delivery Stats
- Release Status
2.2.1.6.1 O̲u̲t̲g̲o̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲S̲t̲a̲t̲u̲s̲
The Outgoing Message Status file shall contain the
status for each message prepared at a VDU.
Each day at 24.00 hour the Outgoing Message status
file shall be cleaned up. This means that ll status
information concerning items which will no longer undergo
changes shall be deleted (e.g. messages released, deleted
etc.)
2.2.1.6.2 D̲e̲l̲i̲v̲e̲r̲y̲ ̲S̲t̲a̲t̲u̲s̲
The Delivery status shall contain a list of all items
removed from the receive queue, s well as these of
the relevant type retrieved. The Delivery Status shall
be cleared each day at 24.00 hour.…86…1 …02… …02… …02…
…02…
Figure 2.2-6
2.2.1.6.3 R̲e̲l̲e̲a̲s̲e̲ ̲S̲t̲a̲t̲u̲s̲
The release status shall contain a list of all items
to which a release decision has been taken and a list
of the associated release notifications for eah VDU
with release capability.
Each day at 24.00 hour the Release Status file shall
be cleared.
2.2.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲R̲e̲s̲p̲o̲n̲s̲i̲b̲i̲l̲i̲t̲i̲e̲s̲
2.2.2.1 I̲n̲i̲t̲i̲a̲l̲i̲z̲a̲t̲i̲o̲n̲,̲ ̲C̲l̲o̲s̲e̲ ̲D̲o̲w̲n̲,̲ ̲a̲n̲d̲ ̲R̲e̲s̲t̲a̲r̲t̲
2.2.2.1.1 I̲n̲i̲t̲i̲a̲l̲i̲z̲a̲t̲i̲o̲n̲
On command from SSC VUP shall iitialize the VUP software.
The initialization refers to the functions to be performed
after load or re-load of VUP and which it is necessary
to execute before VUP can initiate its normal operation.
2.2.2.1.2 C̲l̲o̲s̲e̲ ̲D̲o̲w̲n̲
On command from SSC, VUPshall terminate its current
processing in an ordered manner and bring itself into
a state, where it can respond to a restart command.
2.2.2.1.3 R̲e̲s̲t̲a̲r̲t̲
On command from SSC VUP shall be able to execute a
restart function. Restart is commanded following close
down, switchover or total system failure. VUP shall
imlement functions necessary to restart after each
situation listed above.
2.2.2.2 C̲h̲e̲c̲k̲p̲o̲i̲n̲t̲i̲n̲g̲ ̲a̲n̲d̲ ̲R̲e̲c̲o̲v̲e̲r̲y̲
a) Checkpointing
Checkpointing is performed by calling the SAVE-function
(CSF function) at appropriate points, that is when
a messag is created, updated, and sent to queues
in the system.
b) Recovery
When VUP is restarted by SSC software following
close down, switchover, or total system failure
"recovery required" is specified by SSC.
Relevant queues will then have contnts according
to latest checkpoint and VUP shall inspect the
queues to reestablish the VUP state.
2.2.2.3 E̲r̲r̲o̲r̲ ̲D̲e̲t̲e̲c̲t̲i̲n̲g̲ ̲a̲n̲d̲ ̲E̲r̲r̲o̲r̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲
a) Error Detecting
Errors delected by TEP are of the following types:
- Internal software errors - Illegal
contents
of
received
QEL's
- Unknown CC's delivered by System Software
b) Error Handling
Errors detected by VUP shall be reported to the
SSC together with information on whether VUP was
able to handle the error itself or not. (Reer also
subsection 2.2.2.4). Detection of an error which
VUP cannot handle itself shall cause VUP to stop
its processing and transfer control to SSC for
further handling of the situation.
