top - download
⟦10e1a24ad⟧ Wang Wps File
Length: 71972 (0x11924)
Types: Wang Wps File
Notes: CPS/SDS/048
Names: »4663A «
Derivation
└─⟦249f842e7⟧ Bits:30006192 8" Wang WCS floppy, CR 0445A
└─ ⟦this⟧ »4663A «
WangText
Y…00……00……00……00…<…02……00……00…<
;…0e…:…08…:
…14……06……13……00……12……0b……12……06……11……0b……11……00……11… …10……0b……10……00……10……07……0f……0b……0f……0c……0f……0d……0f……00……0f……01……0f…
…0f… …0f……06……0f……07……0e……09……0e……0f……0e……00……0e……01……0e……02……0d……08……0d……0e……0d……05……0c……0c……0c…
…0b……08……0b……0e……0b……02……0a……08……0a……0b……0a……0e……0a……01……86…1 …02… …02… …02…
…02…CPS/SDS/048
…02…JBS/840301…02……02…
MESSAGE SERVICE VDU
…02……02…CAMPS
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
1 GENERAL .......................................
001
1.1 PURPOSE AND SCOPE .........................
002
1.2 APPLICABLE DOCUMENTS AND PROJECT REFERENCES
002
1.2.1 Applicable Documents ..................
002
1.2.2 Reference Documents ...................
002
1.3 TERMS AND ABBREVIATIONS ...................
003
1.3.1 Terms .................................
003
1.3.2 Abbreviations .........................
003
2 SUMMARY OF REQUIREMENTS .......................
005
2.1 PACKAGE DESCRIPTION .......................
005
2.2 PACKAGE FUNCTIONS .........................
017
2.2.1 Main Functions (Normal Operation) .....
021
2.2.1.1 Queue Status Display ..............
021
2.2.1.2 Information Concerning the Trans-
actions in Progress ...............
022
2.2.1.3 Menu Guidance .....................
022
2.2.1.4 Display of Queued Information .....
022
2.2.1.4.1 The Incoming Message Queue .....
023
2.2.1.4.2 The Outgoing Message Queue .....
023
2.2.1.4.3 The Message Distribution Queue .
024
2.2.1.4.4 The Response Queue .............
024
2.2.1.4.6 The Receive Queue ..............
024
2.2.1.5 Service Message Preparation .......
025
2.2.1.6 Maintenance and Update of Message
Status Files ......................
025
2.2.1.7 Requests/Commands to CAMSP System .
025
2.2.1.7.1 Supervisor Control Commands ....
025
2.2.1.7.2 Requests (Supervisor Procedure
Commands) ......................
026
2.2.2 Functional Responsibilities ...........
026
2.2.2.1 Initialization, Close-Down and
Restart ...........................
026
2.2.2.2 Checkpointing and Recovery ........
027
2.2.2.3 Error Detection and Error Handling
027
2.2.2.4 Integrity of Operation ............
027
2.2.2.5 Data Collection (Log, Statistics
and Reports) ......................
028
2.2.2.6 Security ..........................
028
2.3 CHARACTERISTICS ...........................
029
2.3.1 Timing ................................
029
2.3.2 Throughput ............................
029
2.3.3 Flexibility ...........................
030
2.3.4 Accuracy ..............................
030
3 ENVIRONMENT ...................................
031
3.1 EQUIPMENT .................................
031
3.2 SOFTWARE ..................................
031
3.2.1 System Software .......................
031
3.2.2 Development Support Software ..........
031
3.3 INTERFACES ................................
031
3.3.1 External Interfaces ...................
031
3.3.2 Package Interfaces ....................
032
3.3.2.1 SSC I/F ...........................
032
3.3.2.2 TMP I/F ...........................
032
3.3.2.3 LOG I/F ...........................
032
3.3.2.4 SAR I/F ...........................
032
3.3.2.5 THP I/F ...........................
032
3.3.2.6 MDP I/F ...........................
032
3.3.2.7 PRIS I/F ..........................
032
3.3.3.8 SVUP I/F ..........................
033
3.3.3.9 OCP I/F ...........................
033
3.3.2.10 UMAM I/F ..........................
033
3.3.2.11 VUS I/F ...........................
033
3.4 FUNCTIONS MAINTAINED BY OTHER PACKAGES ....
033
4 PACKAGE DESIGN ................................
034
4.1 PACKAGE OVERVIEW ..........................
034
4.1.1 Functional Specification ..............
038
4.1.1.1 TEMCO Control Functions ...........
040
4.1.1.2 Queue Status Maintenance ..........
042
4.1.1.3 Transaction Accounting ............
045
4.1.1.4 Transaction Interruption ..........
047
4.1.1.5 Command Interpretation ............
049
4.1.1.6 Command Execution .................
051
4.1.1.7 Start/Stop Transaction Execution ..
053
4.1.1.8 Preparation of Service Message ....
055
4.1.1.9 Presentation of Retrieved Message .
057
4.1.1.10 Requests to CAMPS System ..........
059
4.1.1.11 Dialogue Formatting ...............
061
4.1.1.12 Format Validation .................
063
4.1.1.13 Preparation Database Maintenance ..
065
4.1.2 Software Specification ................
067
4.1.2.1 MAVCO Coroutine Software Structure
069
4.1.2.2 MAFCO Coroutine Software Structure
074
4.1.2.3 VDIA Coroutine Software Structure ...
078
4.1.2.4 MART Coroutine Software Structure ...
080
4.1.2.5 Subpackage Identification ...........
082
4.1.3 Dataflow and Control Logic ...............
083
4.1.4 Common Package Data ......................
087
4.1.5 Common Package Procedure .................
089
4.1.5.1 TEP Queue Error .....................
089
4.1.5.2 TEP Internal Error ..................
089
4.1.5.3 TEP Dismantle .......................
089
4.1.5.4 Display Header Queue ................
089
4.1.5.5 Set Header Text .....................
089
4.1.5.6 Set Header Classification ...........
090
4.1.5.7 Internal Representation to ASCII
Conversion ..........................
090
4.1.5.8 ASCII to Internal Representation
Conversion ..........................
090
4.1.5.9 Move Words ..........................
090
4.1.5.10 Display Header Information ..........
090
4.1.6 Global Data Elements .....................
090
4.1.7 Interfaces ...............................
090
4.1.7.1 External Interfaces .................
090
4.1.7.2 Package Interfaces ..................
091
4.1.7.2.1 SSC I/F .........................
091
4.1.7.2.2 TMP I/F .........................
091
4.1.7.2.3 LOG I/F .........................
091
4.1.7.2.4 SAR I/F .........................
091
4.1.7.2.5 THP I/F .........................
091
4.1.7.2.6 MDP I/F .........................
091
4.1.7.3 Subpackage I/F ......................
092
4.1.7.3.1 Process Interfaces ..............
092
4.1.7.3.2 Coroutine Interfaces ............
092
4.1.7.3.3 Other I/F .......................
093
4.2 SUBPACKAGE SPECIFICATION .....................
094
4.2.1 Message Assistance VDU Control
Subpackage (MAVCO) .......................
094
4.2.1.1 Functional Specification ............
094
4.2.1.1.1 Initialization (1.0) ............
096
4.2.1.1.2 TEMCO Command Processing (2.0) ..
096
4.2.1.1.3 VDU Header Control (3.0) ........
096
4.2.1.1.4 Error Reporting (4.0) ...........
097
4.2.1.2 Software Structure ..................
097
4.2.1.2.1 MAVCO Control (1.0) .............
097
4.2.1.2.2 Start User (2.0) ................
099
4.2.1.2.3 Stop User/Close Down (3.0) ......
099
4.2.1.2.4 Timer Event Processing (4.0) ....
099
4.2.1.2.5 Flash Action (5.0) ..............
099
4.2.1.2.6 Queue Fields Update (6.0) .......
099
4.2.1.2.7 Common Procedures ...............
100
4.2.1.3 Dataflow and Control Logic Within
MAVCO ...............................
100
4.2.1.3.1 Data Flow .......................
100
4.2.1.3.2 Control Logic ...................
100
4.2.1.4 MVCO Module Specification .........
110
4.2.1.4.1 MVCO Control ....................
110
4.2.1.4.2 Start User ......................
114
4.2.1.4.3 Stop User .......................
115
4.2.1.4.4 Timer Event Processing ..........
116
4.2.1.4.5 Flash Action ....................
118
4.2.1.4.6 Queue Fields Update .............
119
4.2.1.5 Common Subpackage Data ..............
121
4.2.1.6 Common Subpackage Procedures ........
122
4.2.1.6.1 Request Periodic Timeout ........
122
4.2.1.6.2 Send MART Command ...............
123
4.2.1.6.3 Send MAFCO Command ..............
124
4.2.1.6.4 Clear Header Split ..............
125
4.2.1.6.5 Send Reply to SSC ...............
126
4.2.1.6.6 Get Date Time ...................
127
4.2.1.6.7 Cancel Periodic Timeout .........
128
4.2.1.6.8 Remove User Connection ..........
129
4.2.1.6.9 Check VDU Attributes ............
130
4.2.2 Message Service Function Control
Subpackage (MAFCO) .......................
132
4.2.2.1 Functional Specification ............
132
4.2.2.1.1 MAFCO Software Error Functions ..
135
4.2.2.1.2 F/C Key Command Functions .......
135
4.2.2.1.3 MAVCO Control Functions .........
135
4.2.2.1.4 MSA Command Execution Functions
. 136
4.2.2.1.5 Transaction Execution Functions
. 137
4.2.2.1.6 Transaction Accounting ..........
137
4.2.2.2 Software Structure ..................
138
4.2.2.2.1 SFCO Main (1.0) .................
138
4.2.2.2.2 F/C Key Command Execution (2.0)
. 138
4.2.2.2.3 Validate Command (3.0) ..........
145
4.2.2.2.4 Full Parameter Check (4.0) ......
145
4.2.2.2.5 MSA Command Validation (5.0) ....
145
4.2.2.2.6 Execute Transaction (6.0) .......
145
4.2.2.2.7 System Sequence Control (7.0) ...
145
4.2.2.2.8 Execute System Sequence (8.0) ...
145
4.2.2.2.9 Transaction Control (9.0) .......
145
4.2.2.2.10 SVUP Exception (10.0) ...........
146
4.2.2.2.11 Command Confirmation (11.0) .....
146
4.2.2.2.12 Execute MSA Function (12.0) .....
146
4.2.2.2.13 Send Action (13.0) ..............
146
4.2.2.2.14 MASS Answer Queue Processing
(14.0) ..........................
146
4.2.2.2.15 SVC Handling (15.0) .............
147
4.2.2.2.16 Create New View (16.0) ..........
147
4.2.2.2.17 UMAM Request (17.0) .............
147
4.2.2.2.18 Create New C/F Version (18.0) ...
147
4.2.2.2.19 Create New C/F (19.0) ...........
147
4.2.2.2.20 Retrieval Request (20.0) ........
147
4.2.2.2.21 Get First (21.0) ................
148
4.2.2.2.22 Get Next (22.0) .................
148
4.2.2.2.23 Receive First (23.0) ............
148
4.2.2.2.24 Receive Next (24.0) .............
148
4.2.2.2.25 Calculate MASS Format (25.0) ....
148
4.2.2.3 Data Flow and Control Logic Within
MAFCO ...............................
148
4.2.2.4 MAFO Module Specification ...........
169
4.2.2.4.1 SFCO Main .......................
169
4.2.2.4.2 F/C Key Command Execution .......
169
4.2.2.4.3 Validate Command ................
169
4.2.2.4.4 Execute Transaction .............
169
4.2.2.4.5 Full Parameter Check ............
169
4.2.2.4.6 System Control Sequence .........
169
4.2.2.4.7 Execute System Sequence .........
169
4.2.2.4.8 Transaction Control .............
169
4.2.2.4.9 Command Confirmation ............
170
4.2.2.4.10 SVUP Exception ..................
170
4.2.2.4.11 Answer Queue Processing .........
170
4.2.2.4.12 Calculate MASS Format ...........
171
4.2.2.4.13 Send Action .....................
173
4.2.2.4.14 Execute MSA Function ............
178
4.2.2.4.15 Get First .......................
180
4.2.2.4.16 Get Next ........................
182
4.2.2.4.17 Recv First ......................
183
4.2.2.4.18 Recv Next .......................
184
4.2.2.4.19 Create CIF ......................
186
4.2.2.4.20 Create New CIF Version ..........
187
4.2.2.4.21 Create New View .................
188
4.2.2.4.22 MSA Command Validation ..........
190
4.2.2.4.23 Retrieval Request ...............
191
4.2.2.4.24 UMAM Request ....................
193
4.2.2.4.25 SVC Handling ....................
195
4.2.2.5 Common Subpackage Data ..............
198
4.2.2.6 Common Subpackage Procedures ........
198
4.2.2.6.1 Request FC-Key Input ............
198
4.2.2.6.2 Delete FC-Key Input Request .....
198
4.2.2.6.3 Set Cursor ......................
198
4.2.2.6.4 Display Header Field ............
198
4.2.2.6.5 Read Command Line ...............
199
4.2.2.6.6 Display Response Message ........
199
4.2.2.6.7 Execute DERM Command ............
199
4.2.2.6.8 Fetch and Validate Key ..........
199
4.2.2.6.9 Set Header Feet .................
199
4.2.2.6.10 Free SFCO Operation .............
199
4.2.2.4.11 Fetch SFCO Operation ............
199
4.2.2.4.12 Send SVCO Answer ................
199
4.2.2.6.13 Send SVDIA Command ..............
199
4.2.2.6.14 Send SCREP Command ..............
200
4.2.2.6.15 Wait SFCO Event .................
200
4.2.2.6.16 Exception VDU ...................
200
4.2.2.6.17 Fetch Sequence Record ...........
200
4.2.2.6.18 Simple Parameter Check ..........
200
4.2.2.6.19 Compute Error Number ............
200
4.2.2.6.20 FC-Key Parameter Validation .....
200
4.2.2.6.21 Lookup Parameters ...............
200
4.2.2.6.22 Extract Parameter ...............
200
4.2.2.6.23 Log Reporting ...................
201
4.2.2.6.24 Accounting ......................
202
4.2.2.6.25 Set Cursor Position .............
203
4.2.2.6.26 Set Format Name .................
204
4.2.2.6.27 Calculate Menu ..................
206
4.2.2.6.28 Calculate Message Handling Menu
. 207
4.2.2.6.29 Request Answer Queue Input ......
208
4.2.2.6.30 Transaction Accounting (Initial)
209
4.2.2.6.31 Empty Action ....................
210
4.2.2.6.32 OK Action .......................
211
4.2.2.6.33 Calculate Receive Queue Format ..
212
4.2.2.6.34 Calculate Preparation Header
Format ..........................
213
4.2.2.6.35 Copy Request ....................
214
4.2.2.6.36 Display Response From SAR .......
215
4.2.2.6.37 Calculate Retrieval Key Format ..
216
4.2.2.6.38 Send Request to SAR .............
217
4.2.2.6.39 Send to THP .....................
219
4.2.2.6.40 Send to MDP .....................
220
4.2.2.6.41 Send to OCR .....................
221
4.2.2.6.42 Send Flash Notification .........
222
4.2.2.6.43 Send for Print ..................
223
4.2.2.6.44 Return CIF to Queue .............
225
4.2.2.6.45 Send Special ....................
226
4.2.2.6.46 Reserve Buffer ..................
227
4.2.2.6.47 Send Deletion Notification ......
228
4.2.2.6.48 Send Retrieval Request ..........
229
4.2.2.6.49 Request Open CIF ................
230
4.2.2.6.50 Wait Open SIF ...................
232
4.2.2.6.51 Return View .....................
233
4.2.2.6.52 Save View .......................
234
4.2.2.6.53 Change Profile ..................
235
4.2.2.6.54 Read View Attributes ............
236
4.2.2.6.55 Make CIF Permanent ..............
237
4.2.2.6.56 Collect Atomal Log Data .........
239
4.2.2.6.57 Ring The Bell ...................
240
4.2.2.6.58 Change VDU Field Attributes .....
241
4.2.2.6.59 Perform Invert Bell Command .....
242
4.2.2.6.60 Enable F/C Keys .................
243
4.2.2.6.61 Calculate Retrieval Display
Format ..........................
244
4.2.3 VDU Dialogue Subpackage (VDIA) ...........
245
4.2.4 Retrieve Subpackage ......................
246
4.2.4.1 Functional Specification ............
246
4.2.4.1.1 Initialization (1.0) ............
248
4.2.4.1.2 MAVCO Command Processing (2.0) ..
248
4.2.4.1.3 Retrieval Processing (3.0) ......
248
4.2.4.1.4 Error Handling (4.0) ............
249
4.2.4.2 Software Structure ..................
249
4.2.4.3 Data Flow and Control Logic within
MART ................................
249
4.2.4.3.1 Data Flow .......................
249
4.2.4.3.2 Control Logic ...................
249
4.2.4.4 MART Module Specification ...........
254
4.2.4.4.1 MART Main .......................
254
4.2.4.5 Common Subpackage Data ..............
256
4.2.5 Message Assistance Procedure Subpackage ..
256
4.2.5.1 Functional Specification ............
256
4.2.5.1.1 Display Procedure ...............
257
4.2.5.1.2 Syntax Procedure ................
257
4.2.5.1.3 Semantic Procedures .............
257
4.2.5.2 Software Structure ..................
257
4.2.5.3 Data Flow ...........................
257
4.2.5.4 MAPR Module Specification ...........
258
4.2.5.4.1 MSA Syntax Specification ........
258
4.2.5.4.2 Seman Val Specification .........
268
4.2.5.4.3 Display Field Specification .....
268
4.3 MEMORY LAYOUT ................................
269
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 Message Assistance VDU Package Specification
for the CAMPS project/4040 is written to fulfil
the following objectives:
1) To provide a detailed definition of the Message
Assistance VDU Package function and Software
architecture.
2) To provide user operational and development
personnel with details of the ongoing analysis.
3) To define in detail the interfaces with other
packages and to describe their facilities.
b) The Message Assistance VDU Package Specification
defines the functions and software architecture
of the package to a level sufficient for a programmer
to start coding with a minimum of design effort.
The Message Assistance VDU Package constitutes
one of the building blocks of the TEP package.
All Message Assistance VDU Package internal data
and interfaces are defined within this document
in detail. For a detailed data description of data
external to the Supervisor VDU package and interfaces
to other packages refer the Database Design 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̲
a) CAMPS System Requirement Specification
CPS/210/SYS/0001
b) Supervisor Commands and Procedures
CPS/230/ICD/0002
c) CAMPS System Design Specification
CPS/SDS/001
d) Database Design Document
CPS/DBD/001
e) 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̲
DOCUMENT NAME DOCUMENT NUMBER
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
f) CAMPS System Functions CPS/SDS/024
g) Message Management CPS/SDS/025
h) System Status and Control CPS/SDS/029
i) Table Managment CPS/SDS/026
j) Input/Output Control CPS/SDS/028
k) Storage and Retrieval CPS/SDS/030
l) Statistics CPS/SDS/031
m) Logging CPS/SDS/032
n) Traffic Handling CPS/SDS/033
o) Message Distribution CPS/SDS/034
p) Supervisor VDU CPS/SDS/035
q) Supervisor Printer CPS/SDS/036
r) User VDU CPS/SDS/039
s) OCR CPS/SDS/040
t) 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̲
CAMPS function: The CAMPS function includes:
- The CAMPS
Supervisor
Function
- The CAMPS
Message
Distribution
Control Function
- The CAMPS
Message Service
Control Function
- The CAMPS User
Function, i.e
Preparation,
Reception and
Release.
Preparation - Common term
Database (PDB) for the messages
under preparation
for which access
is controlled
by UMAM (ref.s)
1.3.2 A̲b̲b̲r̲e̲v̲i̲a̲t̲i̲o̲n̲s̲
SFCO Supervisor Function Control Coroutine
SUP Supervisor VDU Package
SVCO Supervisor VDU Control Coroutine
VDIA VDU Dialogue Coroutine
SVUP Supervisor VDU Process
SPRI Supervisor Print Process
VUS VDU User Subprocess
UMAM User Message Access Monitoring Process
PEC Permissive Entry Code
IOC I/O Control Software
CSF CAMPS System Functions
SSC System Status and Control
THP Traffic Handling Package
MDP Message Distribution Package
TMP Table Management Package
SAR Storage and Retrieval
STP Statistics Package
LOG Log and Accountability Package
TEP Terminal Package
MAS Message Assistance Subprocess
MSA Message Service Assistance
MAVCO Message Assistance VDU Control
MAFCO Message Assistance Functional Control
MART Message Assistance Retrieval
MAPR Message Assistance Procedures
TEMCO Terminal Monitoring and Control
SCREP Supervisor Completion Report Control
PDB Preparation Database
C̲o̲m̲m̲a̲n̲d̲ ̲a̲b̲b̲r̲e̲v̲i̲a̲t̲i̲o̲n̲s̲: (refer CPS/230/ICD/0002)
MSGH Message Handling
SMPR Service Message Preparation
REDE Retrieval for Deletion
RELU Retrieval For Local Use
READ Retrieval For Readdressal
RERN Retrieval For Rerun
REDS Retrieval For Redistribution
RESP Response Message
PRPF Prepare New Plaindress Message
PRAP Prepare New Abbreviated Plaindress Message
PRAS Prepare New Abbreviated Service Message
CPFP Continue Plaindress Preparation
CAPP Continue Abbreviated Plaindress Preparation
CASP Continue Abbreviated Service Message Preparation
DESM Delete Service Message
OSMS Outgoing Service Message Status
MDAS Message Distribution Assistance
OMAS Outgoing Message Service Assistance
IMAS Incoming Message Service Assistance
SION Sign-On
SIOF Sign-Off
PRNC Prepare New Comment
CTCP Continue Comment Preparation
RECV Receive Comment
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̲ ̲S̲P̲E̲C̲I̲F̲I̲C̲A̲T̲I̲O̲N̲
a) The M̲essage S̲ervice A̲ssistance VDU P̲ackage (MSA)
constitutes the only means by which CAMPS personnel
may gain access to the services of the CAMPS MSO
and MDCO function.
b) MSA implements all the services of the CAMPS MSO
and MDCO Function which imply the following responsibilities:
1) Interface the MSO and MDCO to the CAMPS system,
i.e. Man/Machine I/F support and monitoring.
2) Allow the MSO to service outgoing/incoming
Messages (i.e. garble correction, RI-assignment).
3) Allow the MDCO to service outgoing/incoming
messages (i.e. alternative distribution, incoming
distribution assistance).
4) Direct all MSO/MDCO requests/commands to the
relevant Package within CAMPS.
5) Supervise/allow the MSO/MDCO to prepare Service
Messages.
6) Present to the supervisor retrieved items on
his VDU.
c) The CAMPS MSO/MDCO Function consists of functions
which may be grouped into two main categories:
- System Control
- Message Handling
d) The System Control Functions are the functions
for:
Garble Correction
Relay Assistance
Outgoing Routing Indicator Assignment
Incoming Message Distribution
Alternative Message Distribution
as defined in CPS/230/ICD/0002
These functions allow the MSO/MDCO to correct messages
until they can be normally processed by the system.
e) The Message Handling Functions are the functions
for:
e1) S̲e̲r̲v̲i̲c̲e̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲P̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲
Prepare New Plaindress Service Message
Prepare New Abbreviated Plaindress Service Message
Prepare New Abbreviated Service Message
Prepare New Comment
Continue Plaindress Preparation
Continue Abbreviated Plaindress Preparation
Continue Abbreviated Service Message Preparation
Continue Comment Preparation
Delete Service Message
Outgoing Service Message Status
Receive Comment
e2) R̲e̲t̲r̲i̲e̲v̲a̲l̲
Retrieval for Readdressal
Retrieval for Rerun
Retrieval for Redistribution
Retrieval for Local use
Retrieval for Deletion
as defined in CPS/230/ICD/0002.
These functions allow the MSO/MDCO to prepare and
edit Service Messages, to send Service messages,
to delete Service Messages and to obtain status
regarding Service Messages under preparation or
sent for transmission. The retrieval functions
allow the supervisor to retrieve any message in
a suitable format and dependent of this format
(ACP127, E1, E2) to specify readdressal, rerun,
redistribution or local use.
f) The packages to which SUP interfaces are:
1) I/O Control Software
2) Storage and File Management
3) CAMPS System Functions
4) System Status and Control Software
5) Traffic Handling
6) Message Distribution
7) Table Management
8) Storage and Retrieval
9) Log and Accountability
10) Statistics
11) Terminal Package
In figure 2.1-1 an overview of the MSA interfaces
is depicted.
g) The MAS interface to the Terminal Package (TEP)
consists of the interfaces between the Message
Assistance VDU Process and the following other
TEP processes:
1) Supervisor Print Process (SPRI)
2) Printer Subprocess (PRIS)
3) User Message Access Monitoring Process (UMAM)
4) User VDU Process (VUP)
5) OCR Analysis Process (OAS)
6) Supervisor VDU Process (SVUP)
The information flow between MSA and the rest of the
CAMPS System packages/processes is depicted in fig.
2.1-2 through 2.1-5.
Fig. 2.1-1 MSA INTERFACE OVERVIEW
Fig. 2.1-2
Message Service
Message/Data Flow
Legend figure 2.1-2
1. Messages returned from garble correction and inspection.
2. Incoming messages sent for garble correction and
inspection.
3. Messages returned from RI-assignment.
4. Outgoing messages sent for RI-assignment or relay
assistance.
5. Log of MSO transactions.
6. Printout of item currently worked upon.
7. Messages returned from OCR garble correction.
8. Messages from the OCR sent for garble correction.
FIGURE 2.1-3
Message Distribution
Message/Data Flow
Legend for figure 2.1-3.
1. Incoming messages sent for incoming distribution
assistance.
2. Messages sent for alternative distribution (e.g.
flash queue timeout).
3. Messages returned from incoming distribution assistance
or alternative distribution assistance.
4. Printout of item currently worked upon.
5. Log of MDCO transactions.
FIGURE 2.1-4
Message Handling
Message/Data Flow
Legend for figure 2.1-4.
1. Retrieval request or deletion request.
2. Retrieved item or retrieval error notification.
3. Deletion notification to message drafter.
4. Command completion report for message deletion.
5. Retrieved messages sent for redistribution.
6. Retrieved messages sent for readdressal or rerun.
7. Log of message handling transactions.
8. Printout of retrieved item.
FIGURE 2.1-5
Message Preparation
Message/Data Flow
Legend for figure 2.1-5
1. Status delivery and edit request.
2. Messages under preparation and error responses.
3. Service messages sent for transmission.
4. Transmission acknowledge.
5. Comments sent for local distribution.
6. Storage of first draft of messages and comments.
7. Log of message preparation transactions.
8. Printout of message under preparation.
2.2 P̲A̲C̲K̲A̲G̲E̲ ̲F̲U̲N̲C̲T̲I̲O̲N̲S̲
a) In this section, the functions to be performed
by MSA are outlined. As stated in section 2.1,
the main task of MSA is to implement the CAMPS
MSO/MDCO Function.
b) As a short introduction to the description of the
MSA main functions and functional responsibilities,
an overview of the capabilities of the CAMPS MSO/MDCO
Function is depicted in fig. 2.2-1 through 2.2-2
and the environment as it may be emphasized by
the supervisor is depicted in fig. 2.2-3.
The MSO may access the preparation database where all
messages under preparation are kept. The user may insert/delete/edit
item in the database.
The MSO may access the incoming and outgoing queues
which are queues of the precedence type into which
CAMPS inserts all messages/comments destined to the
MSO terminals. The MSO may inspect/edit/remove/get
a printed copy of the queued elements.
The user may access the response queue which is a queue
of the non-precedence type into which CAMPS inserts
responses to user issued requests with long or unpredictable
response times e.g. retrieval for rerun and readdressal.
The MSO may edit/inspect/remove/get a printed copy
of the queued elements.
The MSO may issue requests/commands to the system,
e.g. retrieve a message, delete a service message.
FIGURE 2.2-1
MDCO Command Overview
FIGURE 2.2-2
MSO Command Overview
FIGURE 2.2-3
Functional MSO Interface
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 implemented by MAS are:
1. Continuous display of queue status information
2. Continuous display of information concerning the
transaction in progress
3. The means for Menu Guidance
4. The means for display of queued information
5. The means for Service Message preparation
6. Maintain and Update Message Status Files
7. The means for directing requests/Commands to CAMPS
and deliver responses.
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 VDU Header
Area.
The second line of the VDU Header Area is used for
Queue Status Display and updated regularly (every minute).
The queues in question are:
1. Receive Queue: this contains the total number of
comments queued for the MSO/MDCO Subprocess.
2. Response Queue: this contains the total number
of offline retrieved items queued for MSA in the
Response Queue.
3. Incoming Queue: this contains the total number
of incoming messages requiring incoming message
service assistance.
4. Outgoing Queue: this contains the total number
of outgoing messages requiring outgoing message
service assistance.
5. Message Distribution Queue: this contains the total
number of incoming and outgoing messages requiring
message distribution assistance.
Together with update of the Queue Status Display the
date/time field on the first line is updated.
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 is used to identify
the Transaction in progress (i.e. the MSO/MDCO Function
called upon) and the classification of the information
currently accessed.
Whenever the classification is unknown or no transaction
is in progress the maximum classification to which
the MSO/MDCO may gain access through this VDU is displayed.
2.2.1.3 M̲e̲n̲u̲ ̲G̲u̲i̲d̲a̲n̲c̲e̲
a) MSO/MDCO Transactions which reflect identical functional
areas are logically grouped, each group represented
by a Menu listing all the related transactions.
b) Stepping from a leaf (Menu) towards the roots (Main
Menu) of the Menu tree may be accomplished by use
of the F/C Key Return to current Menu.
c) Display of the Main Menu is accomplished by use
of the F/C Key SYSTEM ̲BREAK.
d) All other Menus are displayed when the Menu-Name
is entered as a Command.
e) Transactions may be called either directly or via
the appropriate menus.
2.2.1.4 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̲
Five queues are known by MSA. They are:
- Incoming Message Queue
- Outgoing Message Queue
- Message Distribution Queue
- Response Queue
- Receive Queue
2.2.1.4.1 T̲h̲e̲ ̲I̲n̲c̲o̲m̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲Q̲u̲e̲u̲e̲
When the MSO enters the command IMAS, he will be able
to inspect the items in the IMQ queue one by one, make
service on the messages in accordance with the contents
of Terminal Function field, (i.e. Garble Correction,
Message Inspection), 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 Next, Delete and Present Next, Print, and Cancel.
The first message to be presented to the MSO will be
the item with the highest precedence level. If two
or more have the same precedence the oldest item will
be displayed first.
When the MSO activates the F/C key Return to current
menu it will cause the system to send to the VDU the
MSO menu and return the item currently displayed on
the VDU to the queue.
2.2.1.4.2 T̲h̲e̲ ̲O̲u̲t̲g̲o̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲Q̲u̲e̲u̲e̲
When the MSO enters the command OMAS he will be able
to inspect the item in the OMQ queue one by one, make
service on the messges in accordance with the content
of Terminal Function filed, (i.e. Outgoing Routing
Indicator Assignment), 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 Next, Delete and Present Next, Print, and Cancel.
The first message to be presented to the MSO will be
the item with the highest precedence level and if two
or more have the same precedence then the oldest will
be displayed.
When the MSO activates the F/C key Return to current
Menu it will cause the system to send to the VDU the
MSO menu and the item currently displayed on the VDU
in returned to the queue.
2.2.1.4.3 T̲h̲e̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲Q̲u̲e̲u̲e̲
When the MDCO enters the command MDAS he will be able
to inspect the items in the MDQ queue one by one. He
can make service on the message in accordance with
the contents of Terminal Function field (i.e. Alternative
Assistance, Incoming Assistance), remove an inspected
item from the queue, or request a printed copy of the
item.
The first message to be presented to the MDCO will
be the item with the highest precedence level. If two
or more have the same precedence the oldest item will
be displayed first.
2.2.1.4.4 T̲h̲e̲ ̲R̲e̲s̲p̲o̲n̲s̲e̲ ̲Q̲u̲e̲u̲e̲
When the MSO/MDCO enters the command RESP, he will
be able to inspect the items in the RESP queue one
by one, make service on the messages in accordance
with the content of Terminal Function field (i.e. Retrieval
for Rerun, Retrieval for Readdressal), remove an inspected
item from the queue, or request a printed copy of the
item.
The first message to be presented will be the first
in the queue.
When the MSO/MDCO activates the function key Return
to Current Menu. It will have the effect that the item
is returned to the queue and causes the system to send
the menu to the VDU.
2.2.1.4.5 T̲h̲e̲ ̲R̲e̲c̲e̲i̲v̲e̲ ̲Q̲u̲e̲u̲e̲
When the MSO/MDCO enters the command RECV he will receive
the first comment in the receive queue. He can remove
the comment from the queue or request a printed copy
of the comment.
The first comment to be presented will be the one with
the highest precedence level.
2.2.1.5 S̲e̲r̲v̲i̲c̲e̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲P̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲
The Service Message Preparation functions support creation
of Service messages and storage in the Preparation
Database, recall and editing of Service Messages and
Deletion from the Preparation Database.
The preparation is performed in 5 phases:
1. Display of empty format for entry of Service Message
Header.
2. Input and validation of header.
3. Display of header with error codes or when error
free header is entered display of empty format
for entry of text.
4. Input of text and validation.
5. Display of text with error codes or format for
entry of message treatment decision (defer or send).
2.2.1.6 M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲ ̲a̲n̲d̲ ̲U̲p̲d̲a̲t̲e̲ ̲o̲f̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲S̲t̲a̲t̲u̲s̲ ̲F̲i̲l̲e̲s̲
These functions maintain the Outgoing Service Message
Status for Service Messages under preparation.
The display of Outgoing Service Message status is available
via the OSMS-command (ref. CPS/230/ICD/0002).
At 24.00 hours the Outgoing Message Status is queued
for print at the Supervisor Printer and the Message
Status File is cleared.
2.2.1.7 R̲e̲q̲u̲e̲s̲t̲s̲/̲C̲o̲m̲m̲a̲n̲d̲s̲ ̲t̲o̲ ̲C̲A̲M̲P̲S̲ ̲S̲y̲s̲t̲e̲m̲
2.2.1.7.1 S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲C̲o̲m̲m̲a̲n̲d̲s̲
a) It is the responsibility of MSA to request input
of the confirmation code (COCO) before issuing
the entered command to the system or executing
it.
b) Further MSA is responsible for collecting the system
replies to MSO/MDCO Commands and generate and queue
corresponding Command Completion Reports to the
Report printer.
2.2.1.7.2 R̲e̲q̲u̲e̲s̲t̲s̲ ̲t̲o̲ ̲C̲A̲M̲P̲S̲ ̲S̲y̲s̲t̲e̲m̲
It is the responsibility of MSA to direct requests
to the relevant part of the CAMPS System and display
the received information.
The MSO/MDCO may issue requests to CAMPS system by
means of either a command or by use of F/C keys.
The MSO/MDCO may request:
1. Ourgoing service message status.
2. Message retrieval.
3. Message treatment.
4. Message print.
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̲
MSA performs Initialization, Close Down and Restart
on command from SSC (TEMCO)
a) I̲n̲i̲t̲i̲a̲l̲i̲z̲a̲t̲i̲o̲n̲
Initialization of the MSA process making the controlling
units (coroutines) ready to run. This includes
initial call of the Coroutine Monitor of the CSF
Software and of the Format Handler of the IOC software.
b) C̲l̲o̲s̲e̲ ̲D̲o̲w̲n̲
Termination of the current processing in an ordered
manner setting MSA into a state ready for restart.
c) R̲e̲s̲t̲a̲r̲t̲
Restart shall always be performed after Close Down,
Switchover and Total System Failure and contains
the elements described for Initialization with
the addition of processing queue elements marked
as "recovered".
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̲
Checkpointing shall be performed by calling the SAVE-function
(CSF-function) at appropriate points, that is when
a message is created, updated, and sent to queues in
the system.
Recovery shall be performed during restart and is processing
of queue elements returned by CSF and marked "recovered".
(E.g messages marked "recovered" found in the Answer
Queue shall be sent to the UMAM process).
2.2.2.3 E̲r̲r̲o̲r̲ ̲D̲e̲t̲e̲c̲t̲i̲o̲n̲ ̲a̲n̲d̲ ̲E̲r̲r̲o̲r̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲
Errors detected by MAS shall be reported to SSC for
decision on what type of action shall be taken. (e.g.
Ignore, Terminate, Process, etc.).
2.2.2.4 I̲n̲t̲e̲g̲r̲i̲t̲y̲ ̲o̲f̲ ̲O̲p̲e̲r̲a̲t̲i̲o̲n̲
MAS shall contain credibility checks to contain the
effects of corrupt or inaccurate data to the extent
this does not introduce redundant processing which
will decrease the system throughput.
It shall be a design aim that wherever possible the
consequence of a single software fault incident will
not affect more than one transaction. The detection
of an inconsistency indicating a fault shall initiate
a report and the re-processing from a validated checkpoint
in an attempt to recover with a minimum of discontinuity.
Only after further failures should major recovery or
operator intervention action be invoked.
2.2.2.5 D̲a̲t̲a̲ ̲C̲o̲l̲l̲e̲c̲t̲i̲o̲n̲ ̲(̲L̲O̲G̲,̲ ̲S̲T̲A̲T̲I̲S̲T̲I̲C̲S̲,̲ ̲a̲n̲d̲ ̲R̲e̲p̲o̲r̲t̲s̲)̲
1. L̲o̲g̲ ̲C̲o̲l̲l̲e̲c̲t̲i̲o̲n̲
Log information on MSO/MDCO Transactions shall
be collected by MSA and reported to the Log Package.
Log information shall be reported at the time
of completion of a transaction and have the contents
as specified below.
L̲o̲g̲ ̲r̲e̲c̲o̲r̲d̲ ̲d̲a̲t̲a̲:
Terminal Designator
Transaction Serial Number
Format Identification
Log time
Item Reference ID
Exit Code
Start Time of Transaction
Month and Day
2 S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲
N/A.
3 R̲e̲p̲o̲r̲t̲s̲
The following reports shall be generated and queued
to the Supervisor Print Package:
a) Command Completion Reports
2.2.2.6 S̲e̲c̲u̲r̲i̲t̲y̲
MSA shall maintain a list of all MSO/MDCO commands
together with their (possibly) Restrictive Warning
Text.
This list shall be used during validation of any MSO/MDCO
command issued to the system from the message service
VDUs.
2.3 C̲H̲A̲R̲A̲C̲T̲E̲R̲I̲S̲T̲I̲C̲S̲
2.3.1 T̲i̲m̲i̲n̲g̲
The following requirements extracted from CPS/210/SYS/0001
shall be fulfilled by MSA.
S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲y̲ ̲C̲o̲m̲m̲a̲n̲d̲ ̲R̲e̲s̲p̲o̲n̲s̲e̲ ̲(̲3̲.̲4̲.̲1̲.̲6̲.̲5̲)̲
Response time shall be measured as of 3.4.1.6.3 c.
The response time is time to acceptance of command
parameters (i.e. request for new input).
Response time for commands entered via the command
line or via a format display shall be less than 5 seconds
for 99% of all commands.
The above time shall never exceed 10 seconds.
U̲s̲e̲r̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲I̲n̲t̲e̲r̲a̲c̲t̲i̲o̲n̲ ̲(̲3̲.̲4̲.̲1̲.̲6̲.̲3̲)̲
c) During interactive transactions at VDUs the response
time shall be measured as the time delay from transmission
of the last character of the input to the system
and the start of display of response/next format/menu.
1) Response times for entry in the command line
shall not exceed 1 second in 90% of all cases.
2) Response times for validation of a request
(e.g. retrieval, status) shall not exceed 5
seconds in 90% of all cases.
3) Response times for validation of information
(e.g. message, edited message) shall not exceed
10 seconds per VDU page in 90% of all cases.
2.3.2 T̲h̲r̲o̲u̲g̲h̲p̲u̲t̲
The following characteristics extracted from CPS/210/SYS/0001
apply to MSA:
M̲e̲s̲s̲a̲g̲e̲ ̲T̲r̲a̲f̲f̲i̲c̲ ̲C̲h̲a̲r̲a̲c̲t̲e̲r̲i̲s̲t̲i̲c̲s̲ ̲(̲3̲.̲4̲.̲1̲.̲1̲)̲
M̲e̲s̲s̲a̲g̲e̲ ̲C̲h̲a̲r̲a̲c̲t̲e̲r̲i̲s̲t̲i̲c̲s̲ ̲(̲3̲.̲4̲.̲1̲.̲1̲.̲1̲)̲
d) Service Messages have an average length of 400
characters.
e) Service Messages have a maximum length of 12000
characters.
f) Maximum 5% of Service Messages exceed 1000 characters
in length.
2.3.3 F̲l̲e̲x̲i̲b̲i̲l̲i̲t̲y̲
The design shall ensure that changes to formats and
format tolerances can be implemented with ease to facilitate
improvement of the MMI useability.
2.3.4 A̲c̲c̲u̲r̲a̲c̲y̲
Time shall be accurate within +/- 500 ms.
All other data be that input or output shall be exact.
3̲ ̲ ̲E̲N̲V̲I̲R̲O̲N̲M̲E̲N̲T̲
3.1 E̲Q̲U̲I̲P̲M̲E̲N̲T̲
The equipment environment of this package is the CR80D
Computer.
3.2 S̲O̲F̲T̲W̲A̲R̲E̲
3.2.1 S̲y̲s̲t̲e̲m̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲
MAS's system software environment consists of the following
components:
- DAMOS
- CAMPS System Function
- Message Management System
- Storage and File Management
- I/O Control Software
- SSC Software
3.2.2 D̲e̲v̲e̲l̲o̲p̲m̲e̲n̲t̲ ̲S̲u̲p̲p̲o̲r̲t̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲
Development software is standard DAMOS and TOS (Terminal
Operating System) resident in a single CR8OD configuration.
3.3 I̲N̲T̲E̲R̲F̲A̲C̲E̲S̲
3.3.1 E̲x̲t̲e̲r̲n̲a̲l̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
Ref. Supervisor Procedures (CPS/230/ICD/0002)
3.3.2 P̲a̲c̲k̲a̲g̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
3.3.2.1 S̲S̲C̲ ̲I̲/̲F̲
Start-user
Stop-user
Initialize
Restart
Close Down
Block Terminal
3.3.2.2 T̲M̲P̲ ̲I̲/̲F̲
VALIDATION FUNCTIONS
3.3.2.3 L̲O̲G̲ ̲I̲/̲F̲
SEND LOG RECORD
3.3.2.4 S̲A̲R̲ ̲I̲/̲F̲
STORE
RETRIEVE
DELETE MESSAGE
3.3.2.5 T̲H̲P̲ ̲I̲/̲F̲
READDRESSAL
RERUN
SERVICE MESSAGES
RI ASSIGNMENT
GARBLE CORRECTION
3.3.2.6 M̲D̲P̲ ̲I̲/̲F̲
REDISTRIBUTION
SEND/RECEIVE COMMENT
ALTERNATIVE DISTRIBUTION
INCOMING DISTRIBUTION
3.3.2.7 P̲R̲I̲S̲ ̲I̲/̲F̲
PRINTOUT OF MESSAGES
3.3.2.8 S̲V̲U̲P̲ ̲I̲/̲F̲
GENERATE COMMAND COMPLETION REPORT
3.3.2.9 O̲C̲P̲ ̲I̲/̲F̲
OCR GARBLE CORRECTION
3.3.2.10 U̲M̲A̲M̲ ̲I̲/̲F̲
SERVICE MESSAGES UNDER PREPARATION
OUTGOING SERVICE MESSAGE STATUS
DELETE MESSAGE
3.3.2.11 V̲U̲S̲ ̲I̲/̲F̲
DELETION NOTIFICATIONS
3.4 F̲U̲N̲C̲T̲I̲O̲N̲S̲ ̲M̲A̲I̲N̲T̲A̲I̲N̲E̲D̲ ̲B̲Y̲ ̲O̲T̲H̲E̲R̲ ̲P̲A̲C̲K̲A̲G̲E̲S̲
The following security related functions are performed
by TEMCO (SSC):
Sign-on Procedure
Select MSO/MDCO capability
Security Interrogation
Security Warning
Sign-off procedure
4̲ ̲ ̲P̲A̲C̲K̲A̲G̲E̲ ̲D̲E̲S̲I̲G̲N̲
4.1 P̲A̲C̲K̲A̲G̲E̲ ̲O̲V̲E̲R̲V̲I̲E̲W̲
The Message Assistance VDU-Package consists of 2 processes.
One process containing the software required to support
the VDU handling and one containing software to control
the Preparation Database.
An overview of the M̲essage A̲ssistance VDU S̲ubprocess
(MAS) is shown on fig. 4.1-1. It consists of 4 sub-packages
(or coroutines) as specified in sec. 4.1.2:
a) MAVCO (M̲essage A̲ssistance V̲DU C̲o̲ntrol) which reacts
upon commands from TEMCO and controls the other
coroutines as well as it maintains the VDU Header
Status Area.
b) MAFCO (M̲essage A̲ssistance F̲unction C̲o̲ntrol) which
reacts upon commands from MACO, F/C Keys (Function
Keys) from Keyboard and processes input from the
Answer Queue and Response Queue. It also receives
input from the Retrieve Coroutine (MART) and controls
the Dialogue Coroutine (VDIA).
It contains all the functions for c̲o̲n̲t̲r̲o̲l̲ of the
M̲an M̲achine I̲nterface (MMI), for command execution
and for interfacing to other packages.
c) VDIA (V̲DU D̲i̲a̲loque) which performs input and output
to and from the VDU format area and validation
of input data on command from MAFCO.
d) MART (M̲essage A̲ssistance R̲et̲rieval) which receives
answers (messages or error-codes) from SAR on requests
sent to SAR from MAFCO. It communicates on-line
retrieval results to MAFCO and off-line retrieval
results to the Response Queue.
Communication with other packages (apart from CSF)
is done via queues. The MAS has 8 input queues:
Command Queue: Commands from TEMCO and timer
events from Timer Monitor
Answer Queue: Answers to requests to other packages.
Response Queue: Off-line Retrieval Results (placed
in the queue by MART).
Retrieve Queue: Retrieval results (off-line and
on-line) from SAR.
Receive Queue: Comments distributed locally by
MDP
Common Incoming
Message Service
Queue: Messages queued for incoming message
service by THP. The queue is shared
between up to four MSOs.
Common Outgoing
Message Service
Queue: Messages queued for outgoing message
service by THP. The queue is shared
between up to four MSO's.
Common Message
Distribution
Queue: Messages queued for message distribution
assistance by MDP or VUP. The
queue is shared between up to
four MDCOs.
For an overview of the User Message Access Monitoring
Process (UMAM) controlling the Preparation Database
refer CPS/SDS/039.
The analysis performed leading to the breakdown
of MAS into the four subpackages described above
is based on the analysis performed for VUP and
thus not presented within this document.
FIGURE 4.1-1
MAS Overview
Legend for fig. 4.1-1
1. Commands from SSC (e.g. start, stop) and timer
events.
2. Timer initiated update of VDU header (queues, time)
3. Control information from MAVCO to MAFCO
4. Control information from MAVCO to MART.
5. Commands/parameters and function keys
6. Transaction ID, classification and error messages
7. Messages and system update requests
8. Validated/unvalidated messages and system information
9. Retrieved messages
10. Off-line retrieval results are sent to the Response
queue.
11. Retrieve finished signal to MAFCO and on-line retrieval
results.
12. Answers to requests, retrieved messages and comments
distributed locally.
13. Messages queued for MSO/MDCO assistance.
The MAP Coroutines shall be assigned mutual priorities
as specified below:
highest priority MAVCO
MAFCO
VDIA
lowest priority MART
4.1.1 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
This section contains an analysis of the main functions
to be performed by MAS.
The analysis is carried out to a level where self-contained
sub-functions can be identified.
The first level break-down of the MAS-functions is
shown on figure 4.1.1-1. The following main functions
are identified and broken down in this section.
TEMCO CONTROL FUNCTIONS:
These implement the TEMCO Commands (Init, start, stop,
close-down, etc.).
QUEUE STATUS MAINTENANCE:
These maintain the VDU Header Status Area.
MSO/MDCO TRANSACTION CONTROL:
These are the bulk of the package functions controlling
the MMI and performing the Supervisory transactions.
SERVICE MESSAGE DATABASE MAINTENANCE:
These functions perform access control and Status Maintenance
for Service Messages under preparation.
FIGURE 4.1.1-1
MAS Main Functions
4.1.1.1 T̲E̲M̲C̲O̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
Functional breakdown of these functions is shown in
figure 4.1.1.1-1.
INITIALIZATION is performed on command from TEMCO during
start of the CAMPS System.
RESTART process is performed on command from TEMCO
during recovery from a system failure (switchover or
total system failure).
CLOSE-DOWN is performed on command from TEMCO during
ordered System Close Down.
START USER is performed on command from TEMCO following
a successful SIGN-ON procedure.
STOP USER is performed on command from TEMCO following
a SIGN-OFF procedure.
FIGURE 4.1.1.1-1
TEMCO Control Functions
4.1.1.2 Q̲u̲e̲u̲e̲ ̲S̲t̲a̲t̲u̲s̲ ̲M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲
The headline Queue Status Maintenance covers the requirements
listed below:
- The periodic update of the VDU header queue status
line with a periodicity of one minute.
- The immediate update of FLASH (and superflash)
precedence queues each time an item is placed in
such a queue.
Functional breakdown of these functions is shown in
figure 4.1.1.2-1.
UPDATE DTG FIELD:
The date-time-group is updated to reflect current time.
U̲P̲D̲A̲T̲E̲ ̲P̲R̲E̲C̲E̲D̲E̲N̲C̲E̲ ̲F̲I̲E̲L̲D̲S̲
These fields contain the total number of elements queued
in each precedence queue for the queue currently worked
upon.
U̲P̲D̲A̲T̲E̲ ̲M̲A̲I̲N̲ ̲Q̲U̲E̲U̲E̲ ̲F̲I̲E̲L̲D̲S̲
These fields contain the total number of elements queued
in IMQ, OMQ, MOQ, RESPQ and RECVQ depending on current
mode.
I̲N̲V̲E̲R̲T̲ ̲F̲I̲E̲L̲D̲
The fields containing flash messages are displayed
in inverse video.
U̲P̲D̲A̲T̲E̲ ̲F̲L̲A̲S̲H̲ ̲Q̲U̲E̲U̲E̲ ̲L̲E̲N̲G̲T̲H̲
The flash precedence queue length and the corresponding
main queue length is updated to reflect current state
of the queue.
O̲U̲T̲P̲U̲T̲ ̲A̲U̲D̲I̲B̲L̲E̲ ̲A̲L̲A̲R̲M̲
Rings the bell to inform the MSO/MDCO operator that
a flash message has been sent to one of his associated
queues.
DISPLAY QUEUE STATUS INFORMATION:
This function performs the actual display of the VDU
Header Queue Status Line.
FIGURE 4.1.1.2-1
Queue Status Maintenance.
4.1.1.3 T̲r̲a̲n̲s̲a̲c̲t̲i̲o̲n̲ ̲A̲c̲c̲o̲u̲n̲t̲i̲n̲g̲
Functional break-down of these functions is shown in
figure 4.1.1.3-1.
ASSIGN TRANSACTION DESIGNATOR:
This function assigns a Transaction Designator to the
transaction started.
COLLECT LOG DATA:
This function collects initial and final log information.
FINAL LOG REPORTING:
This function sends log information to the LOG-package
upon completion of the current transaction.
FIGURE 4.1.1.3-1
Transaction Accounting
4.1.1.4 T̲r̲a̲n̲s̲a̲c̲t̲i̲o̲n̲ ̲I̲n̲t̲e̲r̲r̲u̲p̲t̲i̲o̲n̲
Functional breakdown of these functions is shown in
figure 4.1.1.4-1. The functions are performed when
an F/C Key Interrupt occurs.
FETCH FUNCTION KEY:
This function analyses the F/C Key Interrupt to identify
the F/C Key.
CHECK RECEIVED F/C KEY ALLOWED:
This function checks that the F/C key is valid in the
current context (at this stage in the transaction).
DISPLAY ERROR MESSAGE:
This function performs display of the appropriate error
message in the case where the F/C key is invalid.
EXECUTE F/C KEY FUNCTIONS:
This function performs the function corresponding to
the F/C Key.
FIGURE 4.1.1.4-1
Transaction Interruption
4.1.1.5 C̲o̲m̲m̲a̲n̲d̲ ̲I̲n̲t̲e̲r̲p̲r̲e̲t̲a̲t̲i̲o̲n̲
Functional breakdown of these functions is shown in
figure 4.1.1.5-1. The functions are performed when
a command is entered on the Command line of the VDU
header.
COMMAND VALIDATION is performed to check that the command
is a valid MSO/MDCO Command and acceptable in the current
context.
COMMAND PARAMETER VALIDATION is performed on parameters
entered with the command (if any).
DISPLAY ERROR MESSAGE is performed if command, para-
meter or PEC is not acceptable.
FIGURE 4.1.1.5-1
Command Interpretation
4.1.1.6 C̲o̲m̲m̲a̲n̲d̲ ̲E̲x̲e̲c̲u̲t̲i̲o̲n̲
Functional breakdown for these functions is shown in
figure 4.1.1.6-1.
CREATE NEW CIF is done via call to Message Monitor
when preparation of a Service Message shall be performed.
FETCH REFERENCED CIF is done via request to UMAM when
editing of a Service Message shall be performed.
DISPLAY ERROR MESSAGE is performed when referenced
CIF cannot be accessed.
OPEN FOR QUEUE ACCESS is performed when a presentation
CMD (RESP) is received.
REQUEST COMMAND EXECUTION initiates the REQUEST to
CAMPS SYSTEM - functions.
OUTPUT REQUESTED NO OF LINES is performed when an INSERT
LINES CMD is entered.
DELETE REQUESTED NO OF LINES is performed when a DELETE
LINES CMD is entered.
RETURN CURSOR returns the cursor to the position where
it was when the CMD-key was activated (prior to INSERT/DELETE
LINES CMDs).
DEFINE VALID COMMANDS defines the commands valid in
the context of the current transaction.
FIGURE 4.1.1.6-1
Command Execution
4.1.1.7 S̲t̲a̲r̲t̲/̲S̲t̲o̲p̲ ̲T̲r̲a̲n̲s̲a̲c̲t̲i̲o̲n̲ ̲E̲x̲e̲c̲u̲t̲i̲o̲n̲
Functional break-down of these functions is shown in
figure 4.1.1.7-1.
CREATE NEW CIF VERSION is performed when an editing
transaction is started.
GET NEXT QUEUED CIF is performed when a message (or
service message) from the Response Queue is requested.
RETURN CIF TO PDB (Preparation Database (PDB)) is performed
when a Service Message Preparation Transaction is terminated
with a DEFER request.
REQUEST UPDATE OF OUTGOING MESSAGE STATUS is performed
when a Service Message Preparation Transaction is terminated
with a SEND-request.
DELETE CIF VERSION is performed when a Service Message
Preparation Transaction is terminated by F/C Key CANCEL.
REMOVE CIF FROM QUEUE is performed when a Presentation
Transaction is terminated by F/C Key DELETE AND PRESENT.
RETURN CIF TO QUEUE is performed when a Presentation
Transaction is terminated by F/C Key KEEP AND PRESENT.
REQUEST ACCESS TO CIF is performed via request to UMAM
when a Preparation Transaction shall start.
GIVE UP ACCESS TO CIF is performed via request to UMAM
when a Preparation Transaction shall stop.
CLEAR USED WORK SPACE is performed when a Preparation
or Presentation Transaction has stopped.
FIGURE 4.1.1.7-1
Start/Step Transaction Execution
4.1.1.8 P̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲ ̲o̲f̲ ̲S̲e̲r̲v̲i̲c̲e̲ ̲M̲e̲s̲s̲a̲g̲e̲
Functional breakdown of these functions is shown on
figure 4.1.1.8-1.
OUTPUT TRANSACTION INFORMATION IN HEADERLINE is performed
when a Preparation Transaction is started.
DEFINE ALLOWED F/C KEY INTERRUPTS defines the F/C Keys
allowed in the context of the current transaction.
OUTPUT MESSAGES HEADER initiates display of the Header
Format with empty fields for preparation of a new Service
Message and with field contents for editing of a Service
Message.
INPUT MESSAGE HEADER initiates input of the header
part of the message when the ENTER F/C Key is activated.
OUTPUT MESSAGES TEXT initiates display of the Text
Format with or without contents when the previously
entered header is accepted.
INPUT MESSAGES TEXT initiates input of the text part
of the message when the ENTER F/C Key is activated.
OUTPUT MESSAGE TREATMENT FORMAT initiates display of
the format for entry of SEND or DEFER decision.
Figure 4.1.1.8-1
Preparation of Service Messages.
4.1.1.9 P̲r̲e̲s̲e̲n̲t̲a̲t̲i̲o̲n̲ ̲o̲f̲ ̲R̲e̲t̲r̲i̲e̲v̲e̲d̲ ̲M̲e̲s̲s̲a̲g̲e̲
Functional breakdown of these functions is shown in
figure 4.1.1.9-1.
OUTPUT TRANSACTION INFORMATION IN HEADER LINE is performed
when a Presentation Transaction is started.
DEFINE ALLOWED F/C KEY INTERRUPTS defines the F/C Keys
allowed in the context of the current transaction.
DISPLAY OF MESSAGE initiates display of the item requested
from the response or the receive queue.
FETCH SAR ERROR CODES is performed if the off-line
Retrieval request was unsuccessful.
FETCH THP/MDP ERROR CODES is performed if the message
is queued for message assistance by THP or MDP
INPUT MESSAGE is performed in order to take the appropriate
action on the displayed item.
ERROR CODE DISPLAY is performed to give details of
reason for failure.
FIGURE 4.1.1.9-1
Presentation of Queued Information
4.1.1.10 R̲e̲q̲u̲e̲s̲t̲s̲ ̲t̲o̲ ̲C̲A̲M̲P̲S̲ ̲S̲y̲s̲t̲e̲m̲
Functional breakdown of these functions is shown in
figure 4.1.1.10-1.
RETRIEVAL REQUESTS are the requests made available
via the RELU Menu (ref CPS/230/ICD/0002).
MESSAGE TREATMENT REQUESTS are the operations that
can be performed upon a prepared Service Message and
on retrieved items (except deletion which is considered
a command).
OUTGOING MESSAGE STATUS REQUEST is the requests made
available via the OSMS command.
PRINT REQUESTS are the requests for print of messages/service
messages signalled by activation of the PRINT F/C Key.
FIGURE 4.1.1.10-1
Requests to CAMPS System
4.1.1.11 D̲i̲a̲l̲o̲g̲u̲e̲ ̲F̲o̲r̲m̲a̲t̲t̲i̲n̲g̲
Functional breakdown of these functions is shown in
figure 4.1.1.11-1. The functions are all calls on the
Monitor Procedures of the FORMAT HANDLER in the IOC
Package. Via these procedures the actual communication
with the VDU Format Area is performed.
FIGURE 4.1.1.11-1
Dialogue Formatting
4.1.1.12 F̲o̲r̲m̲a̲t̲ ̲V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
Functional breakdown of these functions is shown in
figure 4.1.1.12-1.
HEADER FORMAT VALIDATION is performed after entry of
message header during Service Message Preparation.
TEXT FORMAT VALIDATION is performed after entry of
message text during Service Message Preparation.
REQUEST FORMAT VALIDATION is performed after entry
of a request.
DISPLAY ERROR CODE FORMAT is performed when errors
are found during validation.
FIGURE 4.1.1.12-1
Format Validation
4.1.1.13 P̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲ ̲D̲a̲t̲a̲b̲a̲s̲e̲ ̲M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲
Functional breakdown of these functions is shown on
figure 4.1.1.13-1.
The functions shown are a subset of the functions for
Preparation Database Maintenance. A full description
is contained in ref. s) (UMAM).
FIGURE 4.1.1.13-1
Database Maintenance
4.1.2 S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
This section describes the mapping of the functions
specified in section 4.1.1 onto software components.
Figure 4.1.2-1 shows the mapping of functions onto
processes and coroutines. As can be seen MAS consists
of the two processes mentioned in section 4.1.
MAS contains the coroutines:
MAVCO M̲essage A̲ssistance V̲DU C̲o̲ntrol
MAFCO M̲essage A̲ssistance F̲unction C̲o̲ntrol
VDIA V̲DU D̲i̲a̲logue
MART M̲essage A̲ssistance R̲et̲rieval
The detailed analysis leading to the software structure
of MAS is very similar to the one described for VUP
with respect to the coroutines MAVCO, MAFCO, VDIA and
MART. UMAM (Preparation Database Maintenance) serves
both MAS and VUS and is described in CPS/SDS/039 and
therefore not further treated in this document.
The rest of this section describes the functions allocated
to the sub-packages (coroutines). The functions can
be divided into two types:
1) Functions mapped from functional breakdown
2) Functions related to communication between software
components (coroutines and processes).
As the former functions are described in section 4.1.1
only the latter functions will be described in this
section. (The functions mapped from functional breakdown
are presented in highlighted boxes in this section).
FIGURE 4.1.2-1
Functional Mapping on Software Components.
4.1.2.1 M̲A̲V̲C̲O̲ ̲C̲o̲r̲o̲u̲t̲i̲n̲e̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲
This coroutine is the controlling coroutines within
the process. It accepts commands from TEMCO and controls
MAFCO via commands and processes completion reports
from MAFCO corresponding to the commands.
It also maintains the VDU Queue Status Line every minute
activated by a timer event. Figures 4.1.2.1-1 to 4.1.2.1-4
show the software structure.
FIGURE 4.1.2.1-1
MAVCO Structure
FIGURE 4.1.2.1-2
MAVCO Structure - TEMCO Command Processing
FIGURE 4.1.2.1-3
MAVCO Structure - Update of Queue Status Line
FIGURE 4.1.2.1-4
MAVCO Structure - Process Command Completion from MAFCO
4.1.2.2 M̲A̲F̲C̲O̲ ̲C̲o̲r̲o̲u̲t̲i̲n̲e̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲
This coroutine controls input/output to and from the
VDU and the communication with other packages.
It accepts commands from MAVCO and controls VDIA via
commands and processes completion acknowledges from
VDIA corresponding to the commands.
It communicates with MAVCO by sending completion reports
corresponding to commands received from MAVCO.
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.
Figures 4.1.2.2-1 through 4.1.2.2-3 show the software
structure.
FIGURE 4.1.2.2-1
MAFCO Structure
FIGURE 4.1.2.2-2
MAFCO Structure - Process Invalid F/C Key Interrupt
FIGURE 4.1.2.2-3
MAFCO Structure - Execute F/C Key Function
4.1.2.3 V̲D̲I̲A̲ ̲C̲o̲r̲o̲u̲t̲i̲n̲e̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲
This coroutine performs input/output to and from the
format area of the VDU and validation and storing of
input.
It accepts commands from MAFCO and sends completion
reports 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.
Figure 4.1.2.3-1 shows the software structure.
FIGURE 4.1.2.3-1
VDIA Structure.
4.1.2.4 M̲A̲R̲T̲ ̲C̲o̲r̲o̲u̲t̲i̲n̲e̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲
This coroutine receives input from SAR via the Retrieve
Queue and communicates with MAFCO.
This communication is done by MART sending On-line
Retrieval Results directly to MAFCO and Off-line Retrieval
Results indirectly via the Response Queue.
Figure 4.1.2.4-1 shows the Software Structure.
FIGURE 4.1.2.4-1
MART Structure
4.1.2.5 S̲u̲b̲p̲a̲c̲k̲a̲g̲e̲ ̲I̲d̲e̲n̲t̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
Each of the coroutines in section 4.1.2.1 through 4.1.2.4
are identified as subpackages.
The task of initializing the MAS process and upstart
of the MAS coroutines is described in the MAS initialization
subpackage.
The following subpackages are thus described in section
4.2:
- MAVCO subpackage
- MAFCO Subpackage
- VDIA Subpackage
- MART Subpackage
- MAS Initialization Subpackage
4.1.3 D̲a̲t̲a̲ ̲F̲l̲o̲w̲ ̲a̲n̲d̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲L̲o̲g̲i̲c̲
In this section, the data flow between the MAS coroutines
will be described together with the control logic used
to synchronize their execution of the MAS functions
allocated to them.
For a description of MAS processes Data Flow and Process
Synchronization between the processes MAS and UMAM
refer CPS/SDS/039.
The data flow internal to MAS is depicted in fig. 4.1.3-1.
In fig. 4.1.3-2 an overview of the MAS coroutines and
the primitives (S1, S2, S3, S4) used for synchronization
is depicted.
MAVCO receives its input from S1. MAVCO is the coroutine
which controls the activities of all the others through
its control of MAFCO. MAVCO starts and stops MAFCO
by executing a send operation on S2 with the proper
command. When MAFCO has executed a command sent by
MAVCO, MAFCO notifies MAVCO by performing a send operation
on S1 with the relevant Command Completion code.
MAFCO receives its input from S2. MAFCO controls the
activities of VDIA through S3. The control logic is
analog to that described above for MAVCO control of
MAFCO.
MART receives its input from S4. MAVCO controls the
activities of MART through S4. The control logic is
analog to that described above for MAVCO control of
MAFCO. When started by MAVCO, MART will receive input
from the Retrieve Queue through S4. Thus the control
structure will be to await input in S4 and process
the occurred events.
FIGURE 4.1.3-1
Data Flow Between Coroutines
L̲e̲g̲e̲n̲d̲ ̲f̲o̲r̲ ̲F̲i̲g̲.̲ ̲4̲.̲1̲.̲3̲-̲1̲
1. Commands from SSC (e.g. start, stop) and timer
events.
2. Timer initiated update of VDU header (queues, time).
3. Control information from MAVCO to MAFCO.
4. Control information from MAVCO to MART.
5. Commands/parameters and function keys.
6. Transaction ID, classification and error messages.
7. Messages and system update requests.
8. Validated/unvalidated messages and system information.
9. Retrieved messages.
10. Off-line retrieval results are sent to the Response
queue.
11. Retrieve finished signal to MAFCO and on-line retrieval
results.
12. Answers to requests, retrieved messages, and comments
distributed locally.
13. Messages queued for MSO/MDCO assistance.
FIGURE 4.1.3-2
MAS Coroutine Synchronization Overview
VDIA receives its input from S3. As the main work
load of the MAS process due to I/O transfers and validation
of messages/commands and requests is actually performed
by VDIA, a way to interrupt VDIA function execution
within a reasonable time has to be considered. This
means that VDIA shall return to its waiting point frequently
enough to fulfil the requirements for being controllable
by MAFCO.
4.1.4 C̲o̲m̲m̲o̲n̲ ̲P̲a̲c̲k̲a̲g̲e̲ ̲D̲a̲t̲a̲
a) Data References
The following CPS Prefixes are used:
- GENERAL
- DAMOS ̲GENERAL
- CPS ̲CONF
- CPS ̲GENERAL
- CSF ̲GENERAL
- UTILITY ̲FUNC
- QUEUE ̲MON
- TIMER ̲MON
- MESSAGE ̲MON
- COROUTINE ̲MON
- SYS ̲CALL ̲MON
- SERVICE ̲SYS
- CPS ̲ERROR ̲HAND
- HAND ̲GENERAL
- FH ̲GENERAL
- FMS ̲GENERAL
- IOS ̲PARAMS
- TMP ̲GENERAL
- GNS ̲MON
- OTHER ̲TABLES
- MSOS ̲CAP
- SVUP ̲CAP
- QUEUE ̲GENERAL
- CPS ̲APP ̲GENERAL
- CPS ̲IMF
- CPS ̲EMF
- CPS ̲IIF
- CPS ̲LOG ̲PREF
- CPS ̲SAR ̲PREF
- RESPONSE ̲TEXT
- EXIT ̲CAUSE
- TRACE
- TEP
b) External Data
The following CPS Data modules are used:
- CPS ̲DATA
- SITE ̲DATA
c) Local Data
The following MSA Prefixes are used:
- GEN ̲PREFIX
- IO ̲PREFIX
- COROU ̲PREFIX
- QUEUE ̲PREFIX
- TRACE ̲PREFIX
- MSA ̲Q ̲PREFIX
The following MSA Data mnodules are used:
- GEN ̲DATA
- IO ̲DATA
- COROU ̲DATA
- QUEUE ̲DATA
