top - download
⟦6820dfe81⟧ Wang Wps File
Length: 17776 (0x4570)
Types: Wang Wps File
Notes: PC/TRP/005
Names: »6521A «
Derivation
└─⟦3a6539bee⟧ Bits:30006236 8" Wang WCS floppy, CR 0703A
└─ ⟦this⟧ »6521A «
WangText
…00……00……00……00……00…>…02……00……00…>
…02…PC/TRP/005
…02…860428…02……02…#
PROTOCOL CONVERTER ICD VALIDATION REPORT
…02……02…PC
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
1 SCOPE ........................................
2
1.1 GENERAL ..................................
2
1.2 REFERENCED DOCUMENTS .....................
2
1.2.1 Baseline Documentation ...............
2
1.2.2 Informational Documentation ..........
2
1.3 APPLICABLE DOCUMENTS .....................
2
1.4 ABBREVIATION .............................
3
2 VALIDATION AVTIVITIES ........................
4
2.1 PLANNED VALIDATION ACTIVITY ..............
4
2.2 VALIDATION ACTIVITY CARRIED OUT ..........
6
3 EVALUATION OF RESULTS ........................
9
3.1 RESUME ON VALIDATION ACTIVITY ............
9
3.1.1 Wednesday 860129 .....................
9
3.1.2 Friday 860131 .....................
9
3.1.3 Saturday 860102 .....................
10
3.1.4 Sunday 860202 .....................
10
3.1.5 Monday 860203 .....................
10
3.1.6 Tuesday 860204 .....................
10
3.1.7 Wednesday 860205 .....................
11
3.1.8 Thursday 860206 .....................
11
3.1.9 Friday 860207 .....................
11
3.1.10 Saturday 860208 .....................
11
3.1.11 Sunday 860209 .....................
11
3.1.12 Saturday 860315 .....................
12
3.1.13 Sunday 860316 .....................
12
3.1.14 Saturday 860323 .....................
12
3.1.15 Sunday 860323 .....................
13
3.2 LIST OF PROBLEMS .........................
13
3.3 DETAILED VALIDATION EVALUATION ...........
14
4 CHANGE PAGES TO PC/ICD/001 ...................
17
APPENDIX A
APPENDIX B
1̲ ̲ ̲S̲C̲O̲P̲E̲
The scope of the document is both to present the evaluated
results and to serve as documentation for the performed
validation activities. The purpose of the performed
evaluation is to provide updates to the PC/ICD/001.
1.1 G̲E̲N̲E̲R̲A̲L̲
This document describes the validation activities performed
at SHAPE in the periodes 860129 - 860210 and 860315
- 860323. Chapter 2 provides the overview over the
validation activities, and in chapter 3 evaluation
of the test results is described. In chapter 4 a list
of recomended actions for PC/ICD/001 improvements is
provided. The test log is provided in Appendix A.
1.2 R̲E̲F̲E̲R̲E̲N̲C̲E̲D̲ ̲D̲O̲C̲U̲M̲E̲N̲T̲S̲
1.2.1 B̲a̲s̲e̲l̲i̲n̲e̲ ̲D̲o̲c̲u̲m̲e̲n̲t̲a̲t̲i̲o̲n̲
1. Protocol Converter Interface Control Document
PC/ICD/001, dated 851221, preliminary issue.
2. Protocol Converter Validation Procedure
PC/TRP/007, dated 851230, issue 1.
1.2.2 I̲n̲f̲o̲r̲m̲a̲t̲i̲o̲n̲a̲l̲ ̲D̲o̲c̲u̲m̲e̲n̲t̲a̲t̲i̲o̲n̲
-
1.3 A̲P̲P̲L̲I̲C̲A̲B̲L̲E̲ ̲D̲O̲C̲U̲M̲E̲N̲T̲S̲
1. PC-CCIS Interface Study
Contract SHNMO 85-9532/INF.
1.4 A̲B̲B̲R̲E̲V̲I̲A̲T̲I̲O̲N̲
The following abbreviations are used:
ACCIS Automated Command and Control Information System
ACK Acknowledgement
ADP Automated Data Processing
CCIS Command and Control Information System
DCE Data Circuit Terminating Equipment
DTE Data Terminal Equipment
DINDAC Autodin-WWMCCS Direct Access Communications Module
DN/355 Honeywell Front-end Processor
EOM End of Message
GRTS General Remote Terminal Supervisor of DN/553
I/F Interface
ICD Interface Control Document
NAK Negative Acknowledgement
PC Protocol Converter
RCI Remote Computer Interface
SCARS Status and Control Alerting and Reporting System
SCI Station Channel Identifier
SHAPE Supreme Headquarters Allied Powers Europe
TSN Transmission Serial Number
VDU Visual Display Unit
WWMCCS World Wide Military Command and Control System
2̲ ̲ ̲V̲A̲L̲I̲D̲A̲T̲I̲O̲N̲ ̲A̲C̲T̲I̲V̲I̲T̲I̲E̲S̲
The validation provedure PC/TRP/007 describes the different
test cases and the testsetup needed. In section 2.1
the test case description is repeated and a test reference
is made. The testsetup and detailed test case description
are given in PC/TPR/007.
2.1 P̲L̲A̲N̲N̲E̲D̲ ̲V̲A̲L̲I̲D̲A̲T̲I̲O̲N̲ ̲A̲C̲T̲I̲V̲I̲T̲Y̲
The test is divided into two groups: The first group
covers the Physical Link Level and the second the other
three levels. In order to minimize the support needed,
the same test is used for the different test messages,
if applicable. The different test cases are:
Test Group A: Physical Link Level.
Test Case A01: Normal Transmission Control
Signal Handling.
Test Case A02: Disconnection of Data Signal.
Test Case A03: Disconnection of Control Signal
CTS.
Test Case A04: Disconnection of Control Signal
DCD.
Test Case A05: Disconnection of Control Signal
DSR.
Test Group B: Message Traffic Handling (Level 2 to
4).
Test Case B01: Log On Sequence.
Test Case B02: Log Off Sequence.
Test Case B03: Normal Transmission CCIS to
PC.
Test Case B04: Normal Transmission PC to CCIS.
Test Case B05: Normal Transmission PC to CCIS.
Test Case B05A: Two messages from CCIS and one
from PC.
Test Case B05B: Two messages from PC and one
from CCIS.
Test Case B05C: Ten messages from PC and ten
from CCIS.
Test Case B06: SUPERNAK Handling CCIS to PC.
Test Case B07: SUPERNAK Handling PC to CCIS.
Test Case B08: Timeout Handling CCIS to PC.
Test Case B09: Timeout Handling PC to CCIS.
Test Case B10: Wait message handling CCIS to
PC.
Test Case B10A: Wait message handling without
final timeout.
Test Case B10B: Wait message handling with final
timeout.
Test Case B11: Wait message handling PC to
CCIS.
Test Case B11A: Wait message handling without
final timeout.
Test Case B11B: Wait message handling with final
timeout.
Test Case B12: Preemption of messages CCIS
to PC.
Test Case B13: Preemption of messages PC to
CCIS.
Test Case B14: Burst of messages CCIS to PC.
Test Case B15: Burst of message PC to CCIS.
Test Case B16: Compression handling CCIS to
PC.
Test Case B16A: Compression within a subsegment.
Test Case B16B: Compression within a segment.
Test Case B16C: Compression within a message.
Test Case B16D: Compression several times within
a segment.
Test Case B17: Compression handling PC to CCIS.
Test Case B17A: Compression within a subsegment.
Test Case B17B: Compression within a segment.
Test Case B17C: Compression within a message.
Test Case B17D: Compression several times within
a segment.
2.2 V̲A̲L̲I̲D̲A̲T̲I̲O̲N̲ ̲A̲C̲T̲I̲V̲I̲T̲Y̲ ̲C̲A̲R̲R̲I̲E̲D̲ ̲O̲U̲T̲
Testgroup A:
Testgroup B:
N̲o̲t̲e̲ ̲1̲:
Test case changed due to timing problems. 10 messages
queued at both ends but the scope of the test case
is the same.
N̲o̲t̲e̲ ̲2̲:
Note done either due to SW/HW errors or lack of time.
N̲o̲t̲e̲ ̲3̲:
Test case changed due to format limitations (line length).
N̲o̲t̲e̲ ̲4̲:
Done but with test case modifications (same scope).
3̲ ̲ ̲E̲V̲A̲L̲U̲A̲T̲I̲O̲N̲ ̲O̲F̲ ̲R̲E̲S̲U̲L̲T̲S̲
3.1 R̲E̲S̲U̲M̲E̲ ̲O̲N̲ ̲V̲A̲L̲I̲D̲A̲T̲I̲O̲N̲ ̲A̲C̲T̲I̲V̲I̲T̲Y̲
This resume is based on the description given in the
test log in Appendix A. The resume is separated in
sections, one for each testday.
3.1.1 W̲e̲d̲n̲e̲s̲d̲a̲y̲ ̲8̲6̲0̲1̲2̲9̲
The startup of the CCIS system gave some problems with
the line configuration. The datanet was configured
in a 4 wire mode and not in the 2 wire mode that is
necessary for control of half duplex communication.
The problems identified were:
1. CCIS datanet configuration.
2. CCIS termination messages.
3. PC logon frame error.
4. V24 line handling.
5. Sequence code (SC) alternating.
3.1.2 F̲r̲i̲d̲a̲y̲ ̲8̲6̲0̲1̲3̲1̲
A new version of the PC test software used. The software
eliminated problems 3 and 4, and bypassed problem 5
by disabling the SC check in the PC. New problems identified
were:
6. Problems with the physical line between PC - CAMPS.
7. No messages from CAMPS came through the PC:
8. Improper LOGOFF sequence by the PC test software.
9. Break message handling gives problems.
3.1.3 S̲a̲t̲u̲r̲d̲a̲y̲ ̲8̲6̲0̲1̲0̲2̲
No tests with the CCIS - PC interface due to problems
with the PC - CAMPS interface. Problem 6, solved, broke
control lead no. 20. Prbblem 7, a wrong length of the
Transaction Serial Number (TSN) sent from the CAMPS
system. The CAMPS system has a selectable length of
TSN, 3 and 4 digits. The PC will only accept a 3 digit
TSN.
3.1.4 S̲u̲n̲d̲a̲y̲ ̲8̲6̲0̲2̲0̲2̲
Simulation of the PC - CAMPS link with the HP Protocol
Analyzer against the CCIS interface to test the TSN
reaction. The PC - CAMPS link gave some problems due
to special test software on the CAMPS system. A new
problem was identified:
10. The PC handling of TSN.
3.1.5 M̲o̲n̲d̲a̲y̲ ̲8̲6̲0̲2̲0̲3̲
New version of the PC test software used, with changed
disconnect routine. Hardware problems with the cable
between PC and CCIS, broken leads 2 and 3.
The application software running in the CCIS gave some
problems. Testing of signal and control leads as listed
in paragraph 2.2. New probelms identified were:
11. The CCIS application software not running properly.
12. No time out by CCIS or PC on sub-segments.
3.1.6 T̲u̲e̲s̲d̲a̲y̲ ̲8̲6̲0̲2̲0̲4̲
Continued testing of short and long break of control
leads to the OC - CCIS interface. A wrong message type
from CCIS gave problems. A new problem was identified:
13. V24 interface handling of control leads by the
PC test software is not correct.
3.1.7 W̲e̲d̲n̲e̲s̲d̲a̲y̲ ̲8̲6̲0̲2̲0̲5̲
The test were not successful. There were problems with
the application software in the CCIS and the E1 message
format from the CCIS:
3.1.8 T̲h̲u̲r̲s̲d̲a̲y̲ ̲8̲6̲0̲2̲0̲6̲
Simulation tests with HP Protocol Analyzer against
the CCIS interface to simulate the Break message was
not successful. The CCIS application software gave
some problems.
3.1.9 F̲r̲i̲d̲a̲y̲ ̲8̲6̲0̲2̲0̲7̲
Testing with enqueued messages in CCIS and CAMPS gave
some problems which were resulting in in overwritten
messages in the CCIS due to buffer wrap around. Problem
14 was solved by changed buffer size.
A new problem was identified:
14. The CCIS message buffer size.
3.1.10 S̲a̲t̲u̲r̲d̲a̲y̲ ̲8̲6̲0̲2̲0̲8̲
Testing with different numbers of messages enqueued
in CCIS and CAMPS. A Break message handling by the
PC test software gave some problems which were:
15. The BUST message text from the PC test software.
16. LOGON timeout in the PC.
3.1.11 S̲u̲n̲d̲a̲y̲ ̲8̲6̲0̲2̲0̲9̲
The testing gave a SUPERNAK reason 3 and the CAMPS
system preempted correctly. The Break message reaction
was not solved and this will give some problems.
A restart of DINDAC without initialize showed that
the PC did not recognize the ' * RSTRT' sequence from
DINDAC.
Compression of data messages was tested but there were
some problems with the PC software. HP-P.A. simulation
of compression gave some results. Simulation test of
Break message was tried but it failed.
The new problems identified were:
17. ' * RSTRT' message from DINDAC not recognized by
the PC.
18. Compression/expansion not implemented in the PC
software.
3.1.12 S̲a̲t̲u̲r̲d̲a̲y̲ ̲8̲6̲0̲3̲1̲5̲
The second round of testing at SHAPE was starting with
a new version of the PC software, but some problems
showed up with the new software. The LOGON timeout
in the PC test software is still too short, the SC
problem, and correct Break sequence not solved.
3.1.13 S̲u̲n̲d̲a̲y̲ ̲8̲6̲0̲3̲1̲6̲
The startup of CCIS gave some start problems. The LOGON
timeout by the PC has been increased to 2 minutes.
A hardware problem in the PC, a defect LTU module in
the PC-CAMPS interface gave some problems.
New problems identified were:
19. The PC termination sequence not correct.
20. The BUST messate handling not correct in the PC.
3.1.14 S̲a̲t̲u̲r̲d̲a̲y̲ ̲8̲6̲0̲3̲2̲3̲
The handling of SUPERNAK tested. The PC running with
modified test software for Break handling and TSN handling.
There were temporary hardware problems in the PC test
system. No new problems were identified.
3.1.15 S̲u̲n̲d̲a̲y̲ ̲8̲6̲0̲3̲2̲3̲
A test of SUPERNAK handling, preemption, and compression.
The PC test software had only partially implemented
compression handling.
3.2 L̲I̲S̲T̲ ̲O̲F̲ ̲P̲R̲O̲B̲L̲E̲M̲S̲
The following list of problems were identified during
the Validation Test:
1. CCIS datanet configuration.
2. CCIS termination messages.
3. PC logon frame error.
4. V24 line handling.
5. Sequence code (SC) alternating.
6. Problems with the physical line between PC - CAMPS.
7. No messages from CAMPS came through the PC:
8. Improper LOGOFF sequence by the PC test software.
9. Break message handling gives problems.
10. The PC handling of TSN.
11. The CCIS application software not running properly.
12. No time out by CCIS or PC on sub-segments.
13. V24 interface handling of control leads by the
PC test software is not correct.
14. The CCIS message buffer size.
15. The BUST message text from the PC test software.
16. LOGON timeout in the PC.
17. ' * RSTRT' message from DINDAC not recognized by
the PC.
18. Compression/expansion not implemented in the PC
software.
19. The PC termination sequence not correct.
20. The BUST messate handling not correct in the PC.
3.3 D̲E̲T̲A̲I̲L̲E̲D̲ ̲V̲A̲L̲I̲D̲A̲T̲I̲O̲N̲ ̲E̲V̲A̲L̲U̲A̲T̲I̲O̲N̲
The problems listed in paragraph 3.2 give an overview
of encountered problems during the testactivities.
The listed problems will be treat one by one.
1. CCIS datanet configuration.
The CCIS system network interface, the DATANET,
is configured in two versions: A 2 wire and a 4
wire configuration. The interface will run with
the 2 wire version.
2. CCIS termination messages.
Some of the termination messages from the CCIS
system were not known to the PC, which lead to
a correction in the PC/ICD.
3. PC logon frame error.
The LOGON frame error by the PC was a minor misunderstanding
of bracket types, a '( )' instead of ' '.
4. V24 line handling.
The RTS signal goes down before the last character
is finished.
5. Sequence code (SC) alternating.
The PC does allways alternate the SC byt the tests
showed that in some cases the CCIS does not alternate
the SC. Clarification in PC/ICD.
6. Problems with the physical line between PC - CAMPS.
The signal cables between the PC-CAMPS and PC-CCIS
are of a single core leads. DUe to the stiffness
of the wires, the leads break easily if the connector
housing is loose and can turn on the cable.
7. No messages from CAMPS came through the PC:
The TSN in the CAMPS system is selectable in length
of 3 and 4 digits. The PC will only accept 3 digit
TSN.
8. Improper LOGOFF sequence by the PC test software.
The LOGOFF sequence in the PC software is wrong.
9. Break message handling gives problems.
The Break message handling based on the validation
tests and documentation listed in the PC-ICD, will
be defined in the PC-ICD.
10. The PC handling of TSN.
The PC software does not allways reset the TSN
correctly.
11. The CCIS application software not running properly.
The CCIS application software is not running properly.
12. No time out by CCIS or PC on sub-segments.
The test showed that a timeout is needed for too
long ack/nak answer delay of sub-segments.
13. V24 interface handling of control leads by the
PC test software is not correct
The PC test software lack some facilities for handling
V24 interface control signals.
14. The CCIS message buffer size.
The CCIS message buffer size is a software selectable
parameter.
15. The BUST message text from the PC test software.
AN error in the BUST message text from the PC,
and the rules for BUST message handling to be clarified
in the PC-ICD:
16. LOGON timeout in the PC.
The answer time from the CCIS system is sometimes
too long for the PC during LOGON. The PC timeout
to be increased to 2 minutes during LOGON.
17. ' * RSTRT' message from DINDAC not recognized by
the PC.
The ' * RSTRT' message compare string in the PC
software not correct.
18. Compression/expansion not implemented in the PC
software.
The compression is only partially implemented in
the PC test software but the expansion is not implemented.
19. The PC termination sequence not correct.
An error in the PC handling of a line termination
message.
20. The BUST message handling not correct in the PC.
The rules for BUST message handling to be clarified
in the PC-ICD.
4̲ ̲ ̲C̲H̲A̲N̲G̲E̲ ̲P̲A̲G̲E̲S̲ ̲T̲O̲ ̲P̲C̲/̲I̲C̲D̲/̲0̲0̲1̲
The change pages to the PC/ICD/001 are included in
Appendix B.
The change pages are based on findings of discrepancies
or clarifications from the validation tests at SHAPE.
The page numbering has been changed from the preliminary
issue to issue 1 so the change pages cannot directly
replace the previous pages.
