top - download
⟦4a7f8f57c⟧ Wang Wps File
Length: 24362 (0x5f2a)
Types: Wang Wps File
Notes: CPS/TRP/023
Names: »4789A «
Derivation
└─⟦060f447e1⟧ Bits:30006194 8" Wang WCS floppy, CR 0460A
└─ ⟦this⟧ »4789A «
WangText
…00……00……00……00……00……18……0a……18……0b……18……0c……18……01……18……06……17……0c……86…1 …02… …02… …02…
…02…CPS/TRP/023
…02…840402…02……02…#
CAMPS SYSTEM INTEGRATION TEST REPORT
…02……02…CAMPS
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
1 GENERAL ........................................
4
1.1 PURPOSE ....................................
4
1.2 APPLICABLE DOCUMENTS .......................
4
1.3 TERMS AND ABBREVIATIONS ....................
4
2 TEST ANALYSIS ..................................
5
2.1 TEST/FUNCTION RELATIONSHIP .................
5
2.2 TEST PERFORMANCE ...........................
6
2.2.1 Test Execution .........................
6
2.2.2 Error Detection ........................
6
2.2.3 Error Analysis .........................
7
2.2.4 Error Correction .......................
7
2.2.5 Regression Testing .....................
9
2.2.6 Error Frequency ........................
9
3 SUMMARY AND CONCLUSION .........................
13
APPENDIX A .......................................
14
1̲ ̲ ̲G̲E̲N̲E̲R̲A̲L̲
1.1 P̲U̲R̲P̲O̲S̲E̲
The purpose of this Test Report is to summarize the
observations and results obtained during CAMPS System
Integration and Test.
1.2 A̲P̲P̲L̲I̲C̲A̲B̲L̲E̲ ̲D̲O̲C̲U̲M̲E̲N̲T̲S̲
a) System Integration and Test Plan, CPS/TSP/005
b) System Integration and Test Specification and Procedures,
CPS/TPR/011
1.3 T̲E̲R̲M̲S̲ ̲A̲N̲D̲ ̲A̲B̲B̲R̲E̲V̲I̲A̲T̲I̲O̲N̲S̲
CCB Configuration Control Board
CM Configuration Management
CSF CAMPS System Functions
ICD Interface Control Document
IOC Input/Output Control
LOG Log Package
LTUX Line Termination Unit
MDP Message Distribution Package
MSA Message Assistance Package
MMS Message Management System
PR Problem Report
PRT Printer Package
SAR Storage and Retrieval
SSC System Status and Control
STP Statistics Package
SUP Supervisor Package
THP Traffic Handling Package
TMP Table Management Package
VUP VDU User Package
RD Release Description
SRS System Requirement Specification
2̲ ̲ ̲T̲E̲S̲T̲ ̲A̲N̲A̲L̲Y̲S̲I̲S̲
System integration testing has been performed in an
incremental fashion with increments based on individual
process releases. A total of 65 increments were performed
to complete system integration.
Each package release submitted for system integration
was documented by means of a release description. The
release description contained a functional specifications,
which formed the basis for selection of the appropriate
test cases to be executed.
All system integration testcases (CPS/TPR/011) were
planned and specified based on functional requirements
contained in the SRS and ICD's. In this way the test
procedures contained little or no constraints related
to the integration sequence. The test procedures have
been used as a library from which relevant test cases
have been selected prior to execution of each integration
increment.
In certain areas additional testcases have been specified
and executed throughout the integration process.
2.1 T̲E̲S̲T̲/̲F̲U̲N̲C̲T̲I̲O̲N̲ ̲R̲E̲L̲A̲T̲I̲O̲N̲S̲H̲I̲P̲
For the purpose of test visibility and management all
system functions specified in the SRS and ICD's have
been divided into 4 groups where each group relates
to:
- user functions
- operator functions
- supervisory functions
- traffic functions
In order to facilitate test identification the test
related to each function has been numbered as indicated
in appendix A.
2.2 T̲E̲S̲T̲ ̲P̲E̲R̲F̲O̲R̲M̲A̲N̲C̲E̲
2.2.1 T̲e̲s̲t̲ ̲E̲x̲e̲c̲u̲t̲i̲o̲n̲
System integration was completed after successful execution
of approximately 1125 testcases contained in CPS/TPR/011,
issue 1 plus an additional approx. 315 testcases specified
in the course of the integration process. ( These testcases
will be documented in CPS/TPR/011, issue 2)
Test execution was performed over a timespan of 14
months and required manpower resources of approximately
5 manyears.
Testequipment consisting of 4 CAMPS hardware configurations
was used for system integration and a total of approximately
8500 hours of testexecution has been accumulated.
2.2.2 E̲r̲r̲o̲r̲ ̲D̲e̲t̲e̲c̲t̲i̲o̲n̲
Any test outcome deviating from the expected result
has been reported on a Problem Report (PR). During
system integration approximately 1200 PR's were issued.
The issued PR's were distributed over the various software
packages/areas as follows:
SOFTWARE NUMBER OF ISSUED
P̲A̲C̲K̲A̲G̲E̲/̲A̲R̲E̲A̲ P̲R̲O̲B̲L̲E̲M̲ ̲R̲E̲P̲O̲R̲T̲S̲
CSF 58
MMS 39
IOC 80
TMP 87
SSC 201
SAR 111
STP 13
LOG 15
THP 68
MDP 23
SUP 70
SPR 15
VUP 249
PRT 91
MSA 65
LTUX FW ̲ ̲2̲5̲
Total 1210
2.2.3 E̲r̲r̲o̲r̲ ̲A̲n̲a̲l̲y̲s̲i̲s̲
All issued PRs have been submitted for Configuration
Management (CM). At a daily Configuration Control Board
(CCB) meeting all issued PRs have been reviewed for:
a) Screening of duplicates.
b) Validation of requirement interpretation.
c) Identification of actionee and due date for correction.
d) Evaluation, coordination, and decision on proposed
changes or corrections.
Subsequent to the CCB review the PRs have been logged
by CM and distributed to the actionees.
Analysis of the PR's issued during system integration
testing lead to the following observations:
a) 5% of the issued PR's have been rejected for various
reasons.
b) 10% of the issued PR's related to errors previously
reported but not corrected yet.
c) 10% of the issued PR's related to errors in another
package/area than originally identified in the
PR.
d) Error categories were determined to have the following
approximate distribution:
Cat. 1: 0.1%
Cat. 2: 10%
Cat. 3: 80%
Cosmetics: 10%
Categorisation was made using the same definition
as those to be used during 240 hour test.
2.2.4 E̲r̲r̲o̲r̲ ̲C̲o̲r̲r̲e̲c̲t̲i̲o̲n̲
Error correction has been performed by the software
development team.
After error identification the correction has been
implemented and verified by means of suitable regression
testing at module - and package level. Successful completion
of this regression testing has lead to formal issue
of a new version of the package release which is submitted
for CM.
A Release Description (RD) has beeen enclosed to each
new version of a package release. The RD contains a
log of errors corrected with appropriate PR references.
After logging by CM the new version was submitted to
the system I & T team. Based on the RD appropriate
testcases were selected and regression testing executed.
Based on the 1200 PR's issued corrections have been
made which have lead to issue of a total of approximately
700 new versions. The new versions were distributed
per package as follows:
SOFTWARE NUMBER OF ISSUED
P̲A̲C̲K̲A̲G̲E̲/̲A̲R̲E̲A̲ V̲E̲R̲S̲I̲O̲N̲S̲
CSF 22
MMS 35
IOC 37
TMP 83
SSC 58
SAR 47
STP 12
LOG 20
THP 82
MDP 20
SUP 41
VUP 135
PRT 67
MSA 31
LTUX FW ̲ ̲1̲0̲
Total 700
Scheduling of error correction has been determined
by the CCB based on the severity of the error. Therefore,
the observed mean time to correct errors during the
system integration period gives no indication of the
actual time required for error correction.
2.2.5 R̲e̲g̲r̲e̲s̲s̲i̲o̲n̲ ̲T̲e̲s̲t̲i̲n̲g̲
When a new version of a package release has been issued
an appropriate set of testcases was selected and executed
for verification of the corrected errors.
Depending on the type of error and the complexity of
the corresponding correction the appropriate regression
testing will require execution of anywhere from one
to 200 testcases.
Approximately 4200 testcases have been executed in
regression testing which amounts to an average of 6
testcases per new version implemented.
2.2.6 E̲r̲r̲o̲r̲ ̲F̲r̲e̲q̲u̲e̲n̲c̲y̲
An exact registration of the experienced error frequency
has not been performed.
However, by using the Problem Report log and the total
executed test time, month by month, an average test
execution time per issued PR can be calculated.
On figure 1 is shown:
a) Number of PR's issued per month versus calender
time.
b) Hours of test execution per month versus calender
time.
On figure 2 is shown:
Hours of test execution time per issued PR versus calender
time.
FIGURE 1
FIGURE 2
From figure 1 it can be seen that the error frequency
has a peak after completion of about 80% (11 months)
of the integration period. Up to this point in time
the test activity had been steadily increased, which
together with the ongoing integration of new functions
resulted in an increase in the error frequency.
During completion of the remaining 20% of the integration
period the error frequency has been ever decreasing,
indicating a stabilization of the system.
From figure 2 it can be seen that the trend in test
execution time between error detection is clearly indicating
a system stabilization towards the end of the system
integration period. A final monthly average error rate
of one problem per 16 executed test hours was experienced.
3̲ ̲ ̲S̲U̲M̲M̲A̲R̲Y̲ ̲A̲N̲D̲ ̲C̲O̲N̲C̲L̲U̲S̲I̲O̲N̲
System integration testing was performed and completed
over a timeperiod of approximately 14 months.
A total of 1440 testcases have been successfully executed
with the purpose of verifying that all functional requirements
have been implemented correctly.
During system integration testing a total of 1200 Problem
Reports were issued and the corresponding error corrections
resulted in release of 700 new versions of software
configuration items.
Implementations of the performed correction has required
regression testing amounting to execution of more than
4000 testcases.
The trend of the observed error frequency gives a clear
indication of an increase in the software reliability
towards the end of the system integration test period.
A P P E N D I X A…01…***************************…01……01……01……01…TEST/FUNCTION RELATIONSHIP
TESTGROUP 1: USER FUNCTIONS
1.1 VDU Characteristics
1.2 User Transactions Using VDU
1.2.1 Sign On/User Menu/Release Menu-1/Release
Menu-2/Sign off
1.2.2 New Message Preparation
1.2.3 New Comment Preparation/Comment Presentation
1.2.4 Continue Message Preparation
1.2.5 Continue Comment Preparation
1.2.6 Message for Coordination
1.2.7 Message Release/Notification of Release
1.2.8 Local Distribution of an Outgoing Message
1.2.9 Incoming Message Presentation
1.2.10 Security Warning
1.2.11 Security Interrogation
1.2.12 Retrieval of Final Draft
1.2.13 Retrieval of Locally Distributed Outgoing
Messages
1.2.14 Retrieval of Incoming Message
1.2.15 Retrieval of Released Outgoing Messages
without
Local Distribution
1.2.16 Retrieval of Comments
1.2.17 Retrieval of Release Notification
1.2.18 Append Message/Notification of Append
1.2.19 Prepare Predefined Message
1.2.20 Message Deletion/Notification of Deletion
1.2.21 Comment Deletion
1.2.22 Outgoing Message/Comment Status
1.2.23 Delivery Status
1.2.24 Message Release Status
1.2.25 Precedence and Queuing
1.2.26 Message to SCARS and ACCIS
1.2.27 Preparation, Continue Prep. and Transmission
of
Terminal-to-Terminal Comment to SCARS and
ACCIS
1.2.28 Preparation, Continue Prep. and Transmission
of
VDU Display to SCARS and ACCIS
1.2.29 Presentation of Comment/VDU Display from
SCARS
and ACCIS
1.2.30 Retrieval of VDU Display
1.2.31 Responsibility Take-Over
1.3 Transaction Using a Low Speed Teleprinter
1.3.1 Message Transmission
1.3.2 Message Print Out
1.4 Transaction Using OCR
1.4.1 Complete Message entry
1.5 Transaction Using a High Speed PTP/PTR
1.5.1 Output to Punch
1.5.2 Complete Message entry from PTR
1.6 Transaction Using a MSP
1.6.1 Functional Capabilities of Terminal
Procedures - Transaction Print
1.6.2 Routing to Stand Alone Device - MSP
1.7 Logging
1.7.1 Log of User Transactions
1.7.2 Log of Security Procedures
1.7.3 Log of Automatically Deleted
Comment and Notification
1.7.4 Log of OCR Transactions
1.7.5 Log of Printer Transactions
1.8 Statistic
TESTGROUP 2: OPERATOR FUNCTIONS
2.1 High Level Menu
2.1.1 PU Control Menu
2.1.2 CU Control Menu
2.1.3 TDX Control Menu
2.1.4 Software Control Menu
2.1.5 Watchdog Command Menu
2.1.1 PU Control Menu
2.1.1.1 Boot, Start UP
2.1.1.2 Switchover
2.1.1.3 Close Down
2.1.1.4 Delete CIF
2.1.1.5 Terminate Operator Only Mode
2.1.2 CU Control Menu
2.1.2.1 LTU Line Control
2.1.2.2 LTU Control
2.1.2.3 Disk Drive Assignment
2.1.2.4 Volume Handling
2.1.3 TDX Control Menu
2.1.3.1 LTUX Line Control
2.1.3.2 LTUX Control
2.1.3.3 BSM-X
2.1.4 Software Control Menu
2.1.4.1 Ajust Time
2.1.4.2 Load Modified Software
2.1.4.3 Set Trace Mask
2.1.4.4 Print Software Version
2.1.4.5 Print Configuration
2.1.5 Watchdog Command Menu
2.1.5.1 Set PU in Maintenance Mode
2.1.5.2 Reset PU
2.1.5.3 Master Clear PU
2.1.5.4 Enable PU
2.1.5.5 Disable PU
2.1.5.6 Communication to PU #1
2.1.5.7 Communication to PU #2
2.1.5.8 Offline Communication
2.1.5.9 Direct Switchover via WDP
2.1.5.10 Set PU in Normal Mode
2.1.6 Start Up and Error Handling
2.1.6.1 Recovery/Restart from total System Error
2.1.6.2 Recovery after Switch-Over
T̲E̲S̲T̲G̲R̲O̲U̲P̲ ̲3̲:̲ ̲ ̲S̲U̲P̲E̲R̲V̲I̲S̲O̲R̲Y̲ ̲F̲U̲N̲C̲T̲I̲O̲N̲S̲
3.1 General Functions
3.1.1 Sign on/off
3.1.2 High Level Menu
3.2 Supervisor Menu
3.2.1 System Control
3.2.2 Message Handling
3.2.3 Supervisor Engineering Functions
3.2.1 System Control Menu
3.2.1.1 Device Control Menu
3.2.1.1.1 Terminal Control
3.2.1.1.2 PT/OCR/SATP Control
3.2.1.1.3 Channel Control
3.2.1.2 Addressing Scheme Control Menu
3.2.1.2.1 SIC Table Update
3.2.1.2.2 SDL Table Update
3.2.1.2.3 AIG Table Update
3.2.1.2.4 Global PLA Table Update
3.2.1.2.5 RI Table Update
3.2.1.2.6 Circuit Table Update
3.2.1.2.7 SCARS/CCIS Display Table Update
3.2.1.2.8 Operating Signal Table Update
3.2.1.2.9 Local PLA Table Update
3.2.1.2.10 Local RI Table Update
3.2.1.2.11 SCD Table Update
3.2.1.2.12 Reorganize All Tables
3.2.1.2.13 Abandon Reorganization
3.2.1.3 User Profile Update
3.2.1.4 Queue Control Functions Menu
3.2.1.4.1 Block Circuit Queue
3.2.1.4.2 Unblock Circuit Queue
3.2.1.4.3 Block Terminal Queue
3.2.1.4.4 Unblock Terminal Queue
3.2.1.4.5 Block Device Queue
3.2.1.4.6 Unblock Device Queue
3.2.1.4.7 Cancel Circuit Queue
3.2.1.4.8 Cancel Terminal Queue
3.2.1.4.9 Cancel Device Queue
3.2.1.5 Supervisor Print Control
3.2.1.6 Disk Control Functions Menu
3.2.1.6.1 Off Load Data
3.2.1.6.2 Abandon Off Load
3.2.1.6.3 copy System Param File
3.2.1.6.4 Off Line Retrieval Off
3.2.1.6.5 Off Line Retrieval On
3.2.1.6.6 Off Line Retrieval Suspend
3.2.1.6.7 currently Used Volume List
3.2.1.6.8 Refuse Mount
3.2.1.6.9 Volume Mount
3.2.1.6.10 System Volume Mount
3.2.1.6.11 Volume Dismount
3.2.1.6.12 Volume Name
3.2.1.6.13 Volume Delete
3.2.1.7 Command Control
3.2.1.8 Security Control
3.2.1.9 Global No. Series Control Functions Menu
3.2.1.9.1 System No. Series Control
3.2.1.9.2 Channel No. Series Control
3.2.1.9.3 Transaction No. Series Reset
3.2.1.10 System Param Control Functions Menu
3.2.1.10.1 Print/Punch Param Control
3.2.1.10.2 Channel Param Control
3.2.1.10.3 ACP 127 Param Control
3.2.1.10.4 Message Distr. Param Control
3.2.1.10.5 Special Distr. Param Control
3.2.1.10.6 Crisis Indicator On
3.2.1.10.7 Crisis Indicator Off
3.2.1.10.8 Set Quiet Hours
3.2.1.10.9 Stop Quiet Hours
3.2.1.10.10 Flash Queue Time Out
3.2.1.10.11 Close Log CIF
3.2.1.10.12 CAMPS DE RI Control
3.2.1.11 System Information Extract Functions
Menu
3.2.1.11.1 Log Trace
3.2.1.11.2 Password List
3.2.1.11.3 Queue State Print
3.2.1.11.4 User Profile Print
3.2.1.11.5 Terminal Profile Print
3.2.1.11.6 Device Profile Print
3.2.1.11.7 Channel Profile Print
3.2.1.11.8 Command Print
3.2.1.11.9 System Param Print
3.2.1.11.10 Storage Occupancy Request
3.2.1.12 Table Print Functions
3.2.1.12.1 Local PLA-Table Print
3.2.1.12.2 Local RI Table Print
3.2.1.12.3 SIC Table Print
3.2.1.12.4 SDL Table Print
3.2.1.12.5 SCD Table Print
3.2.1.12.6 AIG Table Print
3.2.1.12.7 Global PLA Table Print
3.2.1.12.8 RI Table Print
3.2.1.12.9 Circuit Table Print
3.2.1.12.10 SCARS/ACCIS Display Table Print
3.2.1.12.11 Operating Signal Table Print
3.2.1.12.12 Table Status Print
3.2.2 Message Handling Functions Menu
3.2.2.1 Service Message Preparations Menu
3.2.2.1.1 Prep. New Plaindress Msg.
3.2.2.1.2 Prep. New Abbrev. Plaindress Msg.
3.2.2.1.3 Prep. New Abbrev. Service Msg.
3.2.2.1.4 Continue Plaindress Prep.
3.2.2.1.5 Continue Abbrev. Plaindress Prep.
3.2.2.1.6 Continue Abbrev. Service Prep.
3.2.2.1.7 Delete Service Message
3.2.2.1.8 Outgoing Service Message
3.2.2.2 Retrieval For Local Use Menu
3.2.2.3 Retrieval for Readdressal Menu
3.2.2.4 Retrieval for Rerun
3.2.2.5 Retrieval for Redistribution
3.2.2.6 Retrieval for Deletion
3.2.2.7 Response Message Display
3.2.3 Supervisor Engineering Functions
3.2.3.1 Supervisor Engineering Functions Menu
3.2.3.1.1 Perform Integrity Check
3.2.3.1.2 Perform Message Flow Trace Anal.
3.2.3.1.3 Set Disk Fill Rate Threshold
3.2.3.2 Supervisor Restart Functions Menu
3.2.3.2.1 System Queue Cancellation
3.2.3.2.2 Cancel All Circuit Queues
3.2.3.2.3 Cancel All Terminal Queues
3.2.3.2.4 Cancel All Device Queues
3.2.3.2.5 Circuit Queue Cancellation
3.2.3.2.6 Terminal Queue Cancellation
3.2.3.2.7 Device Queue Cancellation
3.2.3.2.8 CAMPS GO
3.2.3.2.9 Queue Status Print
3.2.3.2.10 Storage Occupancy Print
3.2.4 Log of Supervisor Transaction
3.3 MDCO Menu
3.3.1 Service Message Preparation Menu (as
3.2.2.1)
3.3.2 Retrieval for Redistribution (as
3.2.2.5)
3.3.3 Message Distribution Assistance
3.3.3.1 Incoming Message Distr. Assist.
3.3.3.2 Alternative Distr. Assist.
3.3.3.3 Objects queued for the MDCO
3.3.4 Response Message Display (as
3.2.2.7)
3.3.5 Retrieval for Local Use Menu (as
3.2.2.2)
3.3.6 Retrieval for Readdressal Menu (as
3.2.2.3)
3.3.7 Retrieval for Rerun
3.3.8 Log of MDCO Transactions
3.4 MSO Menu
3.4.1 Service Message Preparation Menu (as
3.2.2.1)
3.4.2 Retrieval for Readdressal Menu (as
3.2.2.3)
3.4.3 Retrieval for Rerun (as
3.2.2.4)
3.4.4 Outgoing Message Service Assistance
3.4.5 Incoming Message Service Assistance
3.4.6 Response Message Display (as
3.2.2.7)
3.4.7 Retrieval for Local Use Menu (as
3.2.2.2)
3.4.8 Retrieval for Redistribution (as
3.2.2.5)
3.4.9 Log of MSO Transactions
T̲E̲S̲T̲G̲R̲O̲U̲P̲ ̲4̲:̲ ̲ ̲T̲R̲A̲F̲F̲I̲C̲ ̲F̲U̲N̲C̲T̲I̲O̲N̲S̲
4.1 Outgoing Messages
4.1.1 ACP 127 Conversion
4.1.1.1 Operational Msgs. with Plain Text
4.1.1.2 Service Messages
4.1.1.3 Complete Messages
4.1.2 Transmission
4.1.2.1 Channel Selection and Identification
4.1.2.2 Premature Termination of Transmission
4.1.2.3 ZEN Prosigns
4.1.2.4 CRYPTO SECURITY
4.2 Incoming Messages
4.2.1 Message Reception Procedures
4.2.2 ACP 127 Analysis
4.2.2.1 Format Line Detection
4.2.2.2 Selection of Parameter
4.2.2.3 Determination of Message Type
4.2.2.4 Format Line 1 Analysis
4.2.2.5 Format Line 2 Analysis
4.2.2.6 Format Line 3 Analysis
4.2.2.7 Format Line 4 Analysis
4.2.2.8 Format Line 5 Analysis
4.2.2.9 Format Line 6 Analysis
4.2.2.10 Format Line 7 Analysis
4.2.2.11 Format Line 8 Analysis
4.2.2.12 Format Line 9 Analysis
4.2.2.13 Format Line 10 Analysis
4.2.2.14 Format Line 11 Analysis
4.2.2.15 Format Line 12a Analysis
4.2.2.16 Format Line 12b Analysis
4.2.2.17 Format Line 12c Analysis
4.2.2.18 Format Line 12d Analysis
4.2.2.19 Format Line 13 Analysis
4.2.2.20 Format Line 15 Analysis
4.2.2.21 Format Line 16 Analysis
4.3 Message Distribution
4.3.1 Automatic Distribution
4.3.2 Distribution of Service Msgs.
4.3.3 Codress/Plaindress Encrypted Msgs.
4.3.4 Data Msgs.
4.3.5 CLEAR Msgs.
4.4 Automatic Message Traffic Control
4.4.1 TRC, Point-to-Point Connections
4.4.1.1 Concesutive Identical Character
4.4.1.2 FLASH Receipt
4.4.1.3 Selfaddressed Channel Check
4.4.1.4 Channel no reset
4.4.1.5 Channel Open/Close
4.4.2 NICS TARE Connections
4.4.2.1 FLASH Receipt
4.4.2.2 Channel Check
4.4.2.3 Channel Number Reset
4.4.2.4 Channel Open/Close
4.4.3 SCARS, ACCIS Connections
4.4.3.1 Transaction Acknowledge
4.4.3.2 Channel Check
4.4.3.3 Channel Number Reset
4.4.3.4 Channel Open/Close
4.5 Handling of Msg. from SCARS
4.5.1 Inc. Msgs. with CAMPS RI in FL2
4.5.2 Inc. Msgs. with Non-CAMPS RI in FL2
4.6 Handling of Msgs. from CCIS
4.6.1 CAMPS PLA in Addr. List
4.6.2 CAMPS Coord., Release and Transmission
4.6.3 Inc. Comment with unknown SCD
4.7 Log of Incoming Messages
4.7.1 Log Records related to NICS TARE, TRC, P-t-P
and PTR messages
4.7.1.1 Valid Messages
4.7.1.2 Invalid Messages
4.7.1.3 Automatically Deleted Messages
4.7.2 Log Records related to ACCIS
4.7.3 Log Records related to SCARS
4.8 Log of Outgoing Messages
4.8.1 Log Records related to NICS TARE, TRC and
P-t-P
4.8.2 Log Records related to ACCIS
4.8.3 Log Records related to SCARS
4.9 Log of Channel Discontinuity
4.9.1 NICS TARE, TRC and P-t-P
4.9.2 ACCIS
4.9.3 SCARS
4.10 Statistical Data
4.10.1 Incoming Messages
4.10.2 Outgoing Messages
4.10.3 Rejected Messages
4.10.4 Channel Availability and Occupancy
4.10.5 Message Distribution
