top - download
⟦aba9b6e54⟧ Wang Wps File
Length: 43447 (0xa9b7)
Types: Wang Wps File
Notes: CPS/USM/002
Names: »3831A «
Derivation
└─⟦739d3b0df⟧ Bits:30006175 8" Wang WCS floppy, CR 0316A
└─ ⟦this⟧ »3831A «
WangText
'…07…&…0c…&…0f……86…1
…02… …02… …02…
…02…CPS/USM/002
…02…FNJ/830629…02……02…
STIMULATOR USER'S MANUAL
…02……02… CAMPS
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
1 GENERAL ........................................
1
2 ENVIRONMENT ....................................
2
3 FUNCTIONAL DESCRIPTION .........................
5
4 STIMULATOR COMMANDS ............................
6
4.1 TEST COMMANDS ..............................
7
4.1.1 SEND ...................................
7
4.1.2 VERIFY .................................
7
4.1.3 CREATE .................................
7
4.1.4 DISMANTLE ..............................
7
4.1.5 RECEIVE ................................
8
4.1.6 PRINT ..................................
8
4.1.7 SENDSE .................................
8
4.1.8 AWAITSE ................................
8
4.1.9 SENDREQ ................................
9
4.1.10 SENDREPLY ............................
9
4.1.11 RESERVE ..............................
9
4.1.12 DUMP .................................
9
4.1.13 SAVE .................................
10
4.1.14 WAIT .................................
10
4.1.15 GETATTR ..............................
10
4.1.16 PASS .................................
10
4.2 UTILITY COMMANDS ...........................
11
4.2.1 CMDFILE ................................
11
4.2.2 CONTINUE ...............................
11
4.2.3 RETURN .................................
11
4.2.4 STOP ...................................
11
4.2.5 EXIT ...................................
11
4.2.6 BEGIN ..................................
11
4.2.7 END ....................................
12
4.2.8 MACRO ..................................
12
4.2.9 DATAFILE ...............................
12
4.2.10 VERIFYFILE ...........................
12
4.2.11 OUTFILE ..............................
12
5 STIMULATOR LOG .................................
13
6 TEST SETUP .....................................
14
7 HOW TO RUN THE STIMULATOR ......................
16
7.1 SIMULATED ENVIRONMENTS .....................
16
7.2 REAL ENVIRONMENTS ..........................
19
8 COMMAND FILE ...................................
21
8.1 LAYOUT .....................................
22
8.2 SYNTAX .....................................
23
8.3 COMMAND PARAMETERS .........................
26
8.3.1 SEND ...................................
26
8.3.2 VERIFY .................................
26
8.3.3 CREATE .................................
26
8.3.4 DISMANTLE ..............................
27
8.3.5 RECEIVE ................................
27
8.3.6 PRINT ..................................
27
8.3.7 SENDSE .................................
27
8.3.8 AWAITSE ................................
28
8.3.9 SENDREQ ................................
28
8.3.10 SENDREPLY ............................
28
8.3.11 RESERVE ..............................
28
8.3.12 DUMP .................................
29
8.3.13 SAVE .................................
29
8.3.14 WAIT .................................
29
8.3.15 GETATTR ..............................
29
8.3.16 PASS .................................
29
8.3.17 CMDFILE ..............................
30
8.3.18 DATAFILE .............................
30
8.3.19 VERIFYFILE ...........................
30
8.3.20 OUTFILE ..............................
30
8.3.21 MACRO ................................
31
9 DATA/VERIFY FILE ...............................
31
9.1 LAYOUT .....................................
32
9.2 SYNTAX .....................................
33
10 CONSTRAINTS ..................................
34
10.1 CREATE CIF ...............................
34
10.2 RECEIVE QEL ..............................
35
10.3 PRINT ....................................
35
10.4 LOGICAL NAME FOR QEL REFERENCE ...........
35
ANNEX A ..........................................
36
ANNEX B ..........................................
56
ANNEX C ..........................................
72
ANNEX D ..........................................
83
ANNEX E ..........................................
104
1̲ ̲ ̲G̲E̲N̲E̲R̲A̲L̲
This manual describes the use of the Stimulator.
The Stimulator is a specific CAMPS test tool, intended
to be used when performing package/system test and
integration. The purpose of the Stimulator is to test
interfaces between processes and verify that the interface
definitions are adhered to the Software Interface Control
Document and the Data Base Document. The interfaces
can be of two types:
- queue interfaces
- sync. element interfaces
Further the Stimulator has facilities for error isolating
and finding, i.e. acting as a debugging tool.
2̲ ̲ ̲E̲N̲V̲I̲R̲O̲N̲M̲E̲N̲T̲S̲
The Stimulator is to be executed on a CR80M computer
running the DAMOS (extended)/TOS operating system or
COPSY operating system.
The DAMOS (extended) is an operating system, where
DAMOS, CSF and MMS are integrated.
The Stimulator exist in two versions, one to be running
in real environments and one to be running in simulated
environments. (See diagram A, B and C)
It is possible to use the DAMOS Debugger and start
the Stimulator and the P̲ackage U̲nder T̲est (PUT) under
the Debugger. The TMP process shall also be started
when performing test of a package.
S̲i̲m̲u̲l̲a̲t̲e̲d̲ ̲E̲n̲v̲i̲r̲o̲n̲m̲e̲n̲t̲ ̲S̲e̲t̲u̲p̲
TOS
Q SETUP STI PUT TMP
Diagram A. Process Configuration without Debugger
TOS
Q SETUP STI DEBUG
PUT TMP
Diagram B. Process Configuration with Debugger
R̲e̲a̲l̲ ̲E̲n̲v̲i̲r̲o̲n̲m̲e̲n̲t̲ ̲S̲e̲t̲u̲p̲
ROOT…01……01……01……01…COPSY…01……01……01……01…
System and Application Processes…01……01……01……01……01……01…Diagram C. Process Configuration in real environment.
3̲ ̲ ̲F̲U̲N̲C̲T̲I̲O̲N̲A̲L̲ ̲D̲E̲S̲C̲R̲I̲P̲T̲I̲O̲N̲
The Stimulator is a test tool which facilitates testing
and verification of interfaces between packages (processes).
The type of interfaces, which can be tested is:
- queue interfaces
- sync. element interfaces
The Stimulator contains facilities for creation of
queue elements and contents of CIFs and Buffers. The
created data can be sent to one or more queues. Further
it contains facilities for receiving, verifying, dumping
and printing of queue elements as well as queue elements
can be dismantled. These facilities apply to the three
types of queue elements: Single, View and Buffer.
Also facilities for sending and awaiting sync. elements
as well as a Wait function are implemented in the Stimulator.
Debugging facilities as "listening" to a queue interface
and get queue status are also implemented.
To utilize a convenient operator interface a set of
utility commands are implemented. These are:
- dynamic command file execution
- dynamic file allocation
- execution control from the operator VDU
- switch between entry of commands from VDU (on-line)
or file (off-line)
- stop the stimulator process
4̲ ̲ ̲S̲T̲I̲M̲U̲L̲A̲T̲O̲R̲ ̲C̲O̲M̲M̲A̲N̲D̲S̲
The following commands are implemented in the Stimulator:
- Test commands
o SEND (VDU/File)
o VERIFY (VDU/File)
o CREATE (VDU/File)
o DISMANTLE (VDU/File)
o RECEIVE (VDU/File)
o PRINT (VDU/File)
o SENDSE (VDU/File)
o AWAITSE (VDU/File)
o SENDREQ (VDU/File)
o SENDREPLY (VDU/File)
o RESERVE (VDU/File)
o DUMP (VDU/File)
o SAVE (VDU/File)
o WAIT (VDU/File)
o GETATTR (VDU/File)
o PASS (VDU/File)
- Utility commands
o CMDFILE (VDU/File)
o DATAFILE (VDU/File)
o VERIFY FILE (VDU/File)
o OUTFILE (VDU/File)
o CONTINUE (VDU)
o RETURN (FILE)
o STOP (VDU/File)
o EXIT (VDU/File)
o BEGIN (FILE)
o END (FILE)
o MACRO (FILE)
Generally commands can be executed both from the VDU
(on-line) and from a File (off-line). Some commands
may only be executed from one media.
4.1 T̲E̲S̲T̲ ̲C̲O̲M̲M̲A̲N̲D̲S̲
4.1.1 S̲E̲N̲D̲
A QEL is sent to specified Queue destination. The QEL
may be of type: Single, View or Buffer. Data for parameter
setup is read from the datafile.
CSF call activated: SEND ̲QEL
4.1.2 V̲E̲R̲I̲F̲Y̲
The last received QEL is verified against the referenced
data in the verify file. QEL must be of type "single"
or "Buffer".
CSF call activated: READ ̲BUFFER
4.1.3 C̲R̲E̲A̲T̲E̲
A CIF is created. Data for parameter setup is read
from the date file.
CSF call activated:
CREATE ̲CIF, OPEN ̲VIEW
WRITE ̲VIEW, CLOSE ̲VIEW
4.1.4 D̲I̲S̲M̲A̲N̲T̲L̲E̲
If the parameter is NIL:
The last received QEL is dismantled. The QEL can be
of type: Single, View or Buffer.
If the parameter refers to a QEL:
The referenced QEL and View or QEL and Buffer is dismantled.
CSF call activated:
DISMANTLE, or DISMANTLE ̲VIEW or,
DISMANTLE ̲BUFFER
4.1.5 R̲E̲C̲E̲I̲V̲E̲
A QEL is received from specified Queue destination.
WAIT or NO WAIT can be specified. Optionally a name
(logical QEL Reference) can be specified to which the
QEL Reference is saved.
CSF call activated:
RECEIVE ̲FIRST
4.1.6 P̲R̲I̲N̲T̲
A view or a buffer specified by a logical QEL Reference
is printed. If no logical QEL Reference is specified,
then the last received QEL is printed.
CSF call activated:
GET ̲VIEW ̲ATTRIBUTES
OPEN ̲VIEW
READ ̲VIEW
CLOSE ̲VIEW
READ ̲BUFFER.
4.1.7 S̲E̲N̲D̲S̲E̲
A Sync.Element is sent.
DAMOS call activated:
DISMANTLE ̲OBJECT
SEARCH ̲OBJECT
SEND
4.1.8 A̲W̲A̲I̲T̲S̲E̲
A Sync Element is awaited.
DAMOS call activated:
DISMANTLE ̲OBJECT
SEARCH ̲OBJECT
AWAIT
4.1.9 S̲E̲N̲D̲R̲E̲Q̲
A QEL is sent to specified Queue destination. An answer
is expected to be received in the specified answer
queue. Same data as for 'SEND' (see sec. 4.1.1).
CSF call activated:
SEND ̲REQUEST.
4.1.10 S̲E̲N̲D̲R̲E̲P̲L̲Y̲
A QEL is sent to a queue destination specified by a
logical QEL reference belonging to a specified QEL,
which was sent by a SEND ̲REQUEST. Same data as for
'SEND' (see sec. 4.1.1).
CSF call activated:
SEND ̲REPLY.
4.1.11 R̲E̲S̲E̲R̲V̲E̲
A buffer is reserved. Data for parameter setup is read
from the data file.
CSF call activated:
RESERVE ̲BUFFER
WRITE ̲BUFFER
4.1.12 D̲U̲M̲P̲
A view specified by a logical QEL Reference is dumped
in hexadecimal form. If no logical QEL Reference is
specified, then the last received QEL is dumped. QEL
must be of type 'view'.
CSF call activated:
GET ̲VIEW ̲ATTRIBUTES
OPEN ̲VIEW
READ VIEW
CLOSE ̲VIEW
4.1.13 S̲A̲V̲E̲
A view is checkpointed.
CSF call activated: SAVE ̲VIEW.
4.1.14 W̲A̲I̲T̲
The STIMULATOR stops execution for a specified time
period.
CSF call activated:
REQUEST ̲TIMEOUT
RECEIVE ̲FIRST ̲QEL
DISMANTLE
DISMANTLE ̲BUFFER
DISMANTLE ̲VIEW.
4.1.15 G̲E̲T̲A̲T̲T̲R̲
Get Queue attributes for specified queue. The Queue
information (profile, status, length) is displayed
both on VDU and on file.
CSF call activated:
GET ̲QUEUE ̲ATTRIBUTES.
4.1.16 P̲A̲S̲S̲
Snap a QEL from a specified queue, print it and pass
it to the queue again. The stimulator instruction activated
by this command is transparent to the two processes
communicating via the queue.
CSF call activated:
QMON ̲SET ̲CAPABILITY, REQUEST ̲TIMEOUT
RECEIVE ̲FIRST ̲QEL, CANCEL ̲TIMEOUT
PASS ̲QEL, QMON ̲DISMANTLE
GET ̲VIEW ̲ATTRIBUTES, OPEN ̲VIEW
READ ̲VIEW, CLOSE ̲VIEW
READ ̲BUFFER.
4.2 U̲T̲I̲L̲I̲T̲Y̲ ̲C̲O̲M̲M̲A̲N̲D̲S̲
4.2.1 C̲M̲D̲F̲I̲L̲E̲
Enter of command file for input of commands. If a current
command file already is connected, this file is dismantled.
4.2.2 C̲O̲N̲T̲I̲N̲U̲E̲
Leave VDU mode for further input of commands from current
command file. Continuation point in the command file
is just after the RETURN command which caused VDU mode
to be entered.
4.2.3 R̲E̲T̲U̲R̲N̲
Leave current command file for entry of commands from
the VDU.
4.2.4 S̲T̲O̲P̲
The STIMULATOR process is terminated.
4.2.5 E̲X̲I̲T̲
The current command file is leaved, the file is dismantled
and VDU mode is entered for further commands.
4.2.6 B̲E̲G̲I̲N̲
BEGIN indicates the start point of a command sequence
(main-or subsequence) on a command file.
4.2.7 E̲N̲D̲
END indicates the end of a subsequence. Reading of
commands is continued just after the command MACRO,
which caused the subsequence to be entered.
4.2.8 M̲A̲C̲R̲O̲
Reading from current input file is continued at the
specified subsequence.
4.2.9 D̲A̲T̲A̲F̲I̲L̲E̲
Charge to new data file during execution of the STIMULATOR.
The file shall exist.
4.2.10 V̲E̲R̲I̲F̲Y̲F̲I̲L̲E̲
Change to new verify file during execution of the STIMULATOR.
The file shall exist.
4.2.11 O̲U̲T̲F̲I̲L̲E̲
Change to new log file during execution of the STIMULATOR.
If the file does not exist, then the file is created.
Default name of the log file at start-up is 'STI ̲LOG'.
5̲ ̲ ̲S̲T̲I̲M̲U̲L̲A̲T̲O̲R̲ ̲L̲O̲G̲
One of the facilities implemented in the STIMULATOR
is that all processing performed by the STIMULATOR
is logged on a file. All commands read either from
the command file or the VDU is logged. And all data
read either from the data file or the verify file are
logged in the same layout as they were read from the
files. Both the commands and the data are logged before
processing of the read information. Error warning and
error messages are logged too.
The log file can be changed during execution. Default
name at start-up is 'STI ̲LOG'.
6 T̲E̲S̲T̲ ̲S̲E̲T̲U̲P̲
The setup for run of the STIMULATOR is shown in the
following figure:
F I G U R
The following steps shall be performed before start
of the STIMULATOR:
S̲T̲E̲P̲ ̲1̲
A boot module containing DAMOS, CSF and MMS shall be
available.
S̲T̲E̲P̲ ̲2̲
In case of real environments a COPSY load module shall
be available. In case of simulated environments a QSETUP
process shall be part of the Boot module.
S̲T̲E̲P̲ ̲3̲
A STIMULATOR load module of TOS version (simulated
environment) or of COPSY version (real environment).
S̲T̲E̲P̲ ̲4̲
A load module for the TMP process and a load module(s)
for the PUT process(es) shall be available. These modules
are not necessary, when performing test with the STIMULATOR
alone.
S̲T̲E̲P̲ ̲5̲
Create a datafile which shall have the layout as described
in section 9. Use of the pre-defined skeletons (see
Annex B) will be a help, when preparing the data file
by use of the TOS Editor. The pre-defined skeletons
are stored in the file 'SKELETONS'.
S̲T̲E̲P̲ ̲6̲
Creation of a verify file. Further actions are similar
to step 5.
S̲T̲E̲P̲ ̲7̲
Creation of a log file named 'STI ̲LOG'. If the log
file is not created at startup of the STIMULATOR, then
it is created automatically.
S̲T̲E̲P̲ ̲8̲
Creation of command file(s). The name is selectable.
These files are not necessary for run of the STIMULATOR,
but will be helpfull when entering command sequences
to the STIMULATOR. The command file(s) shall have the
layout described in section 8.
7̲ ̲ ̲H̲O̲W̲ ̲T̲O̲ ̲R̲U̲N̲ ̲T̲H̲E̲ ̲S̲T̲I̲M̲U̲L̲A̲T̲O̲R̲
Two cases exist: simulated environments and real environments.
7.1 S̲I̲M̲U̲L̲A̲T̲E̲D̲ ̲E̲N̲V̲I̲R̲O̲N̲M̲E̲N̲T̲S̲
The following steps shall be performed for each run
with the STIMULATOR:
S̲T̲E̲P̲ ̲1̲
Boot the system and perform a configuration setup of
the system from the OC-terminal.
S̲T̲E̲P̲ ̲2̲
Log ̲in on user-terminal.
S̲T̲E̲P̲ ̲3̲
Start the STIMULATOR process.
S̲T̲E̲P̲ ̲4̲
Start the CSF process.
S̲T̲E̲P̲ ̲5̲
Start the PUT process. (Not necessary for run with
the STIMULATOR alone).
Now the STIMULATOR will be ready for entry of commands.
Below you will find an example of commands executed
during a run with the STIMULATOR.
All data in the rectangular boxes are to be entered
by the operator. All other data in the example are
printed by the system.
O̲C̲-̲T̲e̲r̲m̲i̲n̲a̲l̲
STEP 1.
EDB TEXT.…86…1 …02… …02… …02… …02…
STEP 2.
LOGIN STI1
STEP 3
STI.O
STEP 4
CSFPROC CDIR: CSFPROC.D
STIMULATOR REL 03 VER 02 DATE 830415 TOS VER PLEASE
SPECIFY DATAFILE, VERIFYFILE AND OUTFILE
DEFAULT: OUTFILE STI ̲LOG
COMMAND: CMDFILE CMD ̲EXAMPLE
7.2 R̲E̲A̲L̲ ̲E̲N̲V̲I̲R̲O̲N̲M̲E̲N̲T̲S̲
The following steps shall be performed for start up
of the CAMPS System. COPSY will start the STIMULATOR
process. (The steps will be changed in the final version
of the CAMPS system).
S̲T̲E̲P̲ ̲1̲
Boot the system from the OC-terminal.
S̲T̲E̲P̲ ̲2̲
Log in as 'SSC' on the OC-terminal.
S̲T̲E̲P̲ ̲3̲
Perform a 'COPSY' resource setup.
S̲T̲E̲P̲ ̲4̲
Start the COPSY process.
S̲T̲E̲P̲ ̲5̲
Perform a 'TOS' resource setup.
Now the STIMULATOR will be ready for entry of commands
from the OC-terminal.
Below you will find an example of the startup sequence.
S̲T̲E̲P̲ ̲1̲
07 MAP/BIT:OK
DAMOS Boot Loader 820429
CPU 0
BO 172
DAMOS Root vs. 0501, 830121
Time (yyyy:mm:dd hh:mm:ss) = 1983 05 27 13 45 0
TMS ̲PROC version: 202 started
FMS version: 204 started
QSETUP version: 0 started
TOS Version: 2 Started
from: TOS
TOS 0202
S̲T̲E̲P̲ ̲2̲
#OPEN SSC
System open
from: SSC
Welcome to TOS
USE SSC.D
S̲T̲E̲P̲ ̲3̲
:DO COPRES
:RESOURCES FMS ̲MOVING UCBS:25 CONNECS:150 KIND:SYSTEM
OPERATIONS:20
:RESOURCES TMS UCBS:15 CONNECS:150 KIND:SYSTEM
OPERATIONS:150 SUBDEV:50
:LOGOUT
S̲T̲E̲P̲ ̲4̲
:COPSY.O203
S̲T̲E̲P̲ ̲5̲
:DO TOSRES
:RESOURCES FMS ̲MOVING UCBS:0 CONNEC:50 KIND:
ORDINARY SUBDEV:0 OPERAT:0
:RESOURCES TMS UCBS:0 CONNEC:15 KIND:ORDINARY
SUBDEV:0 OPERAT:12
:LOGOUT
from: TMS ̲USER ̲020
STIMULATOR REL 03 VER 02 DATE 830415 COPSY VERSION
PLEASE SPECIFY DATAFILE,VERIFYFILE AND OUTFILE AS
COMMANDS
DEFAULT: OUTFILE STI ̲LOG
COMMAND:
GETATTR #91 #0
QUEUE ̲ATTRIBUTES:
PROFILE :#00250025
LENGTH : 0
THRESHOLD : 0
STATUS :BLOCKED
COMMAND: PASS #F #7 #91
8̲ ̲ ̲C̲O̲M̲M̲A̲N̲D̲ ̲F̲I̲L̲E̲
a) The command file consists of a list of commands
arranged in a main sequence and perhaps in several
subsequences. The Main command sequence shall exist.
It consists of, as a minimum:
BEGIN "MAIN"
:
EXIT
b) Sub-sequences, if present, can only be involved
from the main sequence.
c) The command 'BEGIN' is used to indicate a start
point of a command sequence. 'BEGIN' is not allowed
to be used within a sequence.
d) There is no check for duplicate sequence names.
e) The command 'END' indicates termination of a sub-sequence
and must not be used in the main sequence.
f) The commands 'MACRO' and 'RETURN'...'CONTINUE'
will cause reading of the file to be continued
just after the position of the line with the command
'MACRO' or 'RETURN'.
g) The commands 'CMDFILE', 'EXIT' and 'STOP' will
cause the reading of the file to be stopped and
it will not be possible to continue reading at
a position just after one of these commands.
h) A comment line is ignored.
i) Leading spaces in front of a line are ignored.
j) Superfluous 'spaces' between commands and parameters
and between two parameters are ignored.
k) Each command has a fixed number of parameters (refer
to para. 8.2).
l) 'NIL' shall be used if dummy parameter is applicable.
m) Too many parameters will not cause an error message,
but the superfluous parameter(s) will be ignored.
8.1 L̲A̲Y̲O̲U̲T̲
BEGIN "MAIN" File Name: any (dynamics)
;TEST CASE TTT1
CREATE CIF ̲REF #1 #1
RETURN
MACRO SUB ̲N Main Sequence
SEND QEL ̲1 NIL #3 #1
:
:
EXIT
BEGIN "SUB ̲1"
:
Subsequence 1
:
END
-
-
-
-
BEGIN "SUB ̲N"
:
: Subsequence N (max 29)
END
8.2 S̲Y̲N̲T̲A̲X̲
Syntax for input to the Command Interpreter:
COMMAND FILE ::= LINE
COMMAND SEQUENCE MAIN
COMMAND SEQUENCE
COMMAND SEQUENCE MAIN ::= BEGIN SP "MAIN" NL
LINE
COMMAND SEQUENCES ::= BEGIN SP STRING NL
LINE
STRING ::= " IDENT "
LINE ::= COMMENT LINE NL
COMMAND LINE NL
COMMAND LINE COMMENT LINE NL
COMMENT LINE ::= ; characters
COMMAND LINE ::= COMMAND D PARAMETER D
COMMAND PARAMETERS ::=
SEND IDENT IDENT HEX HEX
VERIFY IDENT
CREATE IDENT HEX HEX
DISMANTLE IDENT
RECEIVE HEX HEX
PRINT
SENDSE IDENT IDENT HEX
AWAITSE IDENT HEX
CMDFILE IDENT
CONTINUE
RETURN
STOP
EXIT
BEGIN
END
MACRO IDENT
DATAFILE IDENT
VERIFYFILE IDENT
OUTFILE IDENT
SENDREQ IDENT IDENT HEX HEX HEX HEX
SENDREPLY IDENT IDENT IDENT
RESERVE IDENT HEX HEX
DUMP IDENT
SAVE IDENT
WAIT HEX
GEATTR HEX HEX
PASS HEX HEX HEX
IDENT ::= CHARACTER SPECIAL CHAR
HEX ::= # HEX SIGN
HEX SIGN ::= 0/1/2/3/4/5/6/7/8/9/A/B/C/D/E/F
SPECIAL CHAR ::= ̲/#
D ::= SP /
SP ::= (:20:)
NL ::= (:10:)
8.3 C̲O̲M̲M̲A̲N̲D̲ ̲P̲A̲R̲A̲M̲E̲T̲E̲R̲S̲
8.3.1 S̲E̲N̲D̲
COMMAND: SEND QEL ̲NAME OBJ ̲NAME MAIN ̲Q SUB ̲Q
QEL ̲NAME: Name of 'QEL' data group in the data file.
The reference data group shall be of type:
-'SINGLE', if OBJ ̲NAME = NIL
-'VIEW', if OBJ ̲NAME refer a CIF
-'BUFFER', if OBJ ̲NAME refer a BUFFER
OBJ ̲NAME: - Equal to NIL, indicating a dumme reference
- A name of a created CIF
- A name of a reserved BUFFER
MAIN ̲Q: Main Queue reference number
SUB ̲Q: Sub Queue reference number.
8.3.2 V̲E̲R̲I̲F̲Y̲
COMMAND: VERIFY VERI ̲NAME QEL ̲REF
VERI ̲NAME: Name of a data group in the Verify file.
The directive of the data group shall be:
'QEL' or 'BUFFER'.
QEL ̲REF: Optional. Logical name referring to a received
QEL. If not present or equal to 'NIL' then
the actual QEL reference will be the last
received.
8.3.3 C̲R̲E̲A̲T̲E̲
COMMAND: CREATE CIF ̲NAME MAIN ̲Q SUB ̲Q
CIF ̲NAME: Name of a data group is the data file.
The directive of the data group shall be
'CIF'.
MAIN ̲Q: Main Queue reference number.
SUB ̲Q: Sub Queue reference number.
8.3.4 D̲I̲S̲M̲A̲N̲T̲L̲E̲
COMMAND: DISMANTLE QEL ̲REF
QEL ̲REF: Optional. Logical name referring to a received
QEL. If not present or equal to 'NIL' then
the actual reference will be the last received.
8.3.5 R̲E̲C̲E̲I̲V̲E̲
COMMAND: RECEIVE N/Y MAIN ̲Q SUB ̲Q QEL ̲REF
N/Y: - N means no wait
- Y means wait
MAIN ̲Q: Main Queue reference number
SUB ̲Q: Sub Queue reference number
QEL ̲REF: Optional. Logical name to which
the received QEL reference is saved.
8.3.6 P̲R̲I̲N̲T̲
COMMAND: PRINT QEL ̲REF
QEL ̲REF: Optional. Logical name referring to a received
QEL. If not present or equal to 'NIL',
then the actual QEL reference will be the
last received. The type of the QEL must
be: 'VIEW' or 'BUFFER'.
8.3.7 S̲E̲N̲D̲S̲E̲
COMMAND: SENDSE SYNC ̲NAME SYNC ̲ID NUMBER
SYNC ̲NAME: Name of a data group in the datafile. The
directive of the data group shall be 'SYNC'.
SYNC ̲ID: Name of a created SYNC ̲ELEMENT
NUMBER: Number of words in the SYNC ̲ELEM buffer.
8.3.8 A̲W̲A̲I̲T̲S̲E̲
COMMAND: AWAITSE SYNC ̲ID NUMBER
SYNC ̲ID: Name of a created SYNC ̲ELEMENT
NUMBER: Number of words in the SYNC ̲ELEM. buffer.
8.3.9 S̲E̲N̲D̲R̲E̲Q̲
COMMAND: SENDREQ QEL ̲NAME OBJ ̲NAME MAIN ̲Q SUB ̲Q ANS
̲M ̲Q ANS ̲S ̲Q
For QEL ̲NAME, OBJ ̲NAME, MAIN ̲Q and SUB ̲Q see sec. 8.3.1.
ANS ̲M ̲Q: Main Queue reference number for answer queue.
ANS ̲S ̲Q: Sub Queue reference number for answer queue.
8.3.10 S̲E̲N̲D̲R̲E̲P̲L̲Y̲
COMMAND: SENDREPLY QEL ̲NAME OBJ ̲NAME QEL ̲REF
For QEL ̲NAME and OBJ ̲NAME see sec. 8.3.1
QEL ̲REF: Logical name referring to a received QEL
which is sent by SEND ̲REQUEST.
8.3.11 R̲E̲S̲E̲R̲V̲E̲
COMMAND: RESERVE BUF ̲NAME MAIN ̲Q SUB ̲Q
BUF ̲NAME: Name of a data group in the datafile. The
data group shall be 'BUFFER'
MAIN ̲Q: Main Queue reference number
SUB ̲Q: Sub Queue reference number.
8.3.12 D̲U̲M̲P̲
COMMAND: DUMP QEL ̲REF
QEL ̲REF: Optional. Logical name referring to a received
QEL. If not present or equal to 'NIL',
then the actual QEL reference will be the
last received. The type of the QEL must
be: 'VIEW'.
8.3.13 S̲A̲V̲E̲
COMMAND: SAVE CIF ̲NAME
CIF ̲NAME: Name of a created CIF.
8.3.14 W̲A̲I̲T̲
COMMAND: WAIT NUMBER
NUMBER: Hexadecimal number in seconds.
8.3.15 G̲E̲T̲A̲T̲T̲R̲
COMMAND: GETATTR MAIN ̲Q SUB ̲Q
MAIN ̲Q: Main Queue reference number
SUB ̲Q: Sub Queue reference number.
8.3.16 P̲A̲S̲S̲
COMMAND: PASS SUBPROC CAP ̲INDX MAIN ̲Q
SUBPROC: Subprocess number for the sender process
CAP ̲INDX: Capability index for the sender process.
Can either be Single capability or Group
capability.
If Single: # single cap.no.
If Group : #XXYY, where
XX= group cap.no
YY= ref.queue no. within group
MAIN ̲Q: Main Queue reference number for the actual
queue for which the QEL shall be passed
on to.
If CAP ̲INDX is of type:
S̲i̲n̲g̲l̲e̲: The STIMULATOR will check that
the specified Main Queue ref. no. is the
same as the one already associated the
specified subprocess no. and capability
index. The pass ̲function will not be performed,
if the check fails.
G̲r̲o̲u̲p̲: No check is performed.
NOTE: If nothing is received in the actual Queue
within 100 seconds, then the PASS command is
timed out.
8.3.17 C̲M̲D̲F̲I̲L̲E̲
COMMAND: CMDFILE FILE ̲NAME
FILE ̲NAME: Name of a created file.
8.3.18 D̲A̲T̲A̲F̲I̲L̲E̲
COMMAND: DATAFILE FILE ̲NAME
FILE ̲NAME: Name of a created file.
8.3.19 V̲E̲R̲I̲F̲Y̲F̲I̲L̲E̲
COMMAND: VERIFYFILE FILE ̲NAME
FILE ̲NAME: Name of a created file.
8.3.20 O̲U̲T̲F̲I̲L̲E̲
COMMAND: OUTFILE FILE ̲NAME
FILE ̲NAME: Name of a file. If the file does not exist
then the file is created.
8.3.21 M̲A̲C̲R̲O̲
COMMAND: MACRO SEQ ̲NAME
SEQ ̲NAME: Name of a sub sequence in the current command
file.
9̲ ̲ ̲D̲A̲T̲A̲/̲V̲E̲R̲I̲F̲Y̲ ̲F̲I̲L̲E̲
To help the user with data setup a set of skeletons
is defined (refer to Annex B).
The data file may contain skeletons of type:
- Long QEL
- CIF
- SYNC ̲ELEM
- BUFFER
Verify file may contain skeletons of type:
- Verify QEL
- BUFFER
Use of duplicate data group names in the input files
is not checked.
The characters = and " are significant characters and
must not be used for other purposes than:
= indicate start of data entry
" indicate start of data group name.
Only one data entry on a line.
All characters on a "data line" (refer para 9.1) preceeding
the char = are ignored by the STIMULATOR.
All characters after the data entry (terminated by
a space) are ignored by the STIMULATOR.
All characters on a "data group name line" (refer para.
9.1) preceeding and succeeding the "data group name
string" are ignored by the STIMULATOR.
All "comment lines" are ignored.
Specific limits of data entry are not checked. (Strings
are truncated to max. length).
Scalar values from CPS ̲PREFIX can be used for: MAINTYPE,
SUBTYPE, CLASSIFICATION, PRECEDENCE and SPECIAL HANDLING
DESIGNATOR.
9.1 L̲A̲Y̲O̲U̲T̲
Text line(s) Filename: any(dynamic)
"NAME ̲ID"
prompt = 'XXX'
prompt = #dd
prompt = dd
= B101 Data Group
prompt = FALSE
prompt = ;Don't care
prompt = Ldddd
= *
-
-
-
"NAME ̲ID"
prompt = B011 COMMENT Data Group
prompt =
= .
prompt = % ACK
prompt =
Prompt = % CONFIDENTIAL Legend:
= * . Field end mark
* GROUP end mark
"END" No more data group mark
9.2 S̲Y̲N̲T̲A̲X̲
Syntax for input to the Data Interpreter.
VERIFY FILE ::= DATA FILE
DATA FILE ::= COMMENT LINE
DATA GROUP
"END"
COMMENT LINE ::= ASCII CHAR. NL, a max 130
ASCII CHAR. ::= All printable ASCII characters
except = and "
DATA GROUP ::= GROUP IDENT
LINE
GROUP END
GROUP IDENT ::= " GROUP NAME "
GROUP NAME ::= ACSII value 48 , i.e.
(o..9/A..Z/a..z/ - /other spec.char.)
LINE ::= COMMENT LINE
DATA LINE COMMENT LINE
DATA LINE ::= PROMPT = SP
DATA SP
PROMPT ::= ASCII CHAR
X+Length (DATA)+Y+Z+a max 130
DATA ::= STRING
DECIMAL
HEX
BINARY
LONG DEC.
BOOLEAN
NO ENTRY
FIELD END
SCALAR VALUES
STRING ::= ' ACSII value 32
DECIMAL ::= 0..9 ,max 32767
HEX ::= # 0..9/A/B/C/D/E/F
BINARY ::= B 0/1
LONG DEC. ::= L 0..9/A/B/C/D/E/F
BOOLEAN ::= TRUE/FALSE....T/F
NO ENTRY ::= NL/;
FIELD END ::= .
SCALAR VALUES ::= % MAINTYPE/SUBTYPE/OTHER
GROUP END ::= PROMPT SP * SP COMMENT LINE
NL ::= (:10:)
SP ::= (:20:)
NOTE:
Data Groups are created on basis of pre-defined skeletons.
Five types of skeletons exist: Long QEL; Verify QEL,
CIF, BUFFER and SYNC.ELEMENT.
1̲0̲ ̲ ̲C̲O̲N̲S̲T̲R̲A̲I̲N̲T̲S̲
The flexibility of the STIMULATOR is limited by some
design constraints. These constraints are grouped into
the related command.
10.1 C̲R̲E̲A̲T̲E̲ ̲C̲I̲F̲
a) The maximum field size of a field in a CIF is 1960
words.
b) It is not possible to specify data to the CTS ̲ATOMAL
̲DELETION ̲LOG. (Default initiated with zero).
c) Only o̲n̲e̲ Exercise line (69 char)
Only o̲n̲e̲ Internal Handling Instruction line(69
char)
Only o̲n̲e̲ Subject line (69 char)
d) The maximum number of errors in the error list
(field 9) is 10.
10.2 R̲E̲C̲E̲I̲V̲E̲ ̲Q̲E̲L̲
a) Receive with parameter "yes" for wait may cause
problems due to the cataloging of the Sync.Element
connected to wait function.
10.3 P̲R̲I̲N̲T̲
a) Fields with error in the IOC Header will be hexadecimal
dumped instead of printed in an annotated form.
b) Some fields (field 7 and 8) may have different
layouts (purposes). The STIMULATOR will use the
same annotated layout for both "purposes" and will
not differentiate between the layouts.
10.4 L̲O̲G̲I̲C̲A̲L̲ ̲N̲A̲M̲E̲ ̲F̲O̲R̲ ̲Q̲E̲L̲ ̲R̲E̲F̲E̲R̲E̲N̲C̲E̲
a) The maximum number of logical names which can be
associated to QEL References is 100. The STIMULATOR
does not check for duplicate names. The commands:
CREATE CIF, RESERVE BUFFER and RECEIVE FIRST QEL
(only if parameter four is specified (# NIL)) will
create a new entry in the QEL Reference table and
will increase the number of used logical names.
A̲N̲N̲E̲X̲ ̲A̲
A1. General
A2. Command File
A3 Data File
A4. Verify File
A̲1̲.̲ ̲G̲e̲n̲e̲r̲a̲l̲
This example shows the general use of the STIMULATOR.
It contains at least one example of:
- each command
- each type of data group (skeleton)
- each data type
- the layout of a Command-, Data- and Verify File.
The test run is executed on an M-machine with operating
system DAMOS+CSF+MMS.
…02…The job is executed under TOS in simulated environments.
The names of the files used in this test example were:
- CMD ̲EXAMPLE
- DATA ̲EXAMPLE
- VERIFY ̲EXAMPLE
- LOG ̲EXAMPLE
The contents of the files (3 input files and 1 output
file) are shown on the following pages.
The commands to be executed when running this example
are:
LOGIN STI1(or 2)
CSFPROC CDIR: CSFPROC.D
STI.O (stimulator load module)
CMDFILE CMD ̲EXAMPLE
CONTINUE Stimulator commands
:
:
CONTINUE
STOP
A̲2̲ ̲C̲O̲M̲M̲A̲N̲D̲ ̲F̲I̲L̲E̲…86…1 …02… …02… …02… …02… …02…
COMMAND FILE…86…1 …02… …02… …02… …02… …02…
COMMAND FILE…86…1 …02… …02… …02… …02… …02…
A̲3̲ ̲D̲A̲T̲A̲ ̲F̲I̲L̲E̲…86…1 …02… …02… …02… …02… …02…
DATA FILE…86…1 …02… …02… …02… …02… …02…
DATA FILE…86…1 …02… …02… …02… …02… …02…
DATA FILE…01……86…1 …02… …02… …02… …02… …02…
DATA FILE…86…1 …02… …02… …02… …02… …02…
DATA FILE…86…1 …02… …02… …02… …02… …02…
DATA FILE…86…1 …02… …02… …02… …02… …02…
DATA FILE…86…1 …02… …02… …02… …02… …02…
DATA FILE…86…1 …02… …02… …02… …02… …02…
DATA FILE…86…1 …02… …02… …02… …02… …02…
DATA FILE…86…1 …02… …02… …02… …02… …02…
DATA FILE…86…1 …02… …02… …02… …02… …02…
DATA FILE…86…1 …02… …02… …02… …02… …02…
DATA FILE…86…1 …02… …02… …02… …02… …02…
A̲4̲ ̲V̲E̲R̲I̲F̲Y̲ ̲F̲I̲L̲E̲…86…1 …02… …02… …02… …02… …02…
A̲N̲N̲E̲X̲ ̲B̲
S̲ ̲K̲ ̲E̲ ̲L̲ ̲E̲ ̲T̲ ̲O̲ ̲N̲ ̲S̲
B1 Long QEL
B2 Verify QEL
B3 CIF
B4 Buffer
B5 Sync. Element
B̲1̲ ̲L̲O̲N̲G̲ ̲Q̲E̲L̲…86…1 …02… …02… …02… …02… …02…
B̲2̲ ̲V̲E̲R̲I̲F̲Y̲ ̲Q̲E̲L̲…86…1 …02… …02… …02… …02… …02…
B̲3̲ ̲C̲I̲F̲…86…1 …02… …02… …02… …02… …02…
B3 CIF…86…1 …02… …02… …02… …02… …02…
B3 CIF…86…1 …02… …02… …02… …02… …02…
B3 CIF
B3 CIF
B3 CIF
B3 CIF
B3 CIF
B3 CIF
B3 CIF
B3 CIF
B̲4̲ ̲B̲U̲F̲F̲E̲R̲
B̲5̲ ̲S̲Y̲N̲C̲.̲ ̲E̲L̲E̲M̲E̲N̲T̲
A̲N̲N̲E̲X̲ ̲C̲
H̲o̲w̲ ̲t̲o̲ ̲f̲i̲l̲l̲ ̲o̲u̲t̲ ̲s̲k̲e̲l̲e̲t̲o̲n̲s̲
C1 Data Setup for QEL
C2 Data Setup for Verify QEL
C3 Data Setup for Create CIF
C4 Data Setup for Reserve Buffer
C5 Data Setup for Sync. Element
C̲1̲ ̲D̲a̲t̲a̲ ̲S̲e̲t̲u̲p̲ ̲f̲o̲r̲ ̲Q̲E̲L̲
Entry PROMPT VALUE COMMENT
-------------------------------------------------------------------
1 Directive 'QEL'
2 Type 'SINGLE' if nothing is referenced
'VIEW' if a view is referenced
'BUFFER' if a buffer is referenced
3 Inform.type 'TRUE' if long QEL (INFORMATION(1..3))
'FALSE' if short QEL
4 Checkp.status 'TRUE' checkpoint stored
'FALSE' no checkpoint stored
5 Profile B001 Message for delivery (E1,
E2)
B010 Message for coordination
B100 Message for release
6 Main type 1..127 see Annex D
7 Subtype 1..31 see Annex D
8 Flags B0001 CAMPS originated
B0010 Readdressed
B0100 Pilot
B1000 Relay instruction
9 INF integer any code
10-12 Information 3 integers applicable
if
Information
Type
=
TRUE
C̲2̲ ̲D̲a̲t̲a̲ ̲S̲e̲t̲u̲p̲ ̲f̲o̲r̲ ̲V̲e̲r̲i̲f̲y̲ ̲Q̲E̲L̲
Entry PROMPT VALUE COMMENT
-------------------------------------------------------------------
1 Directive 'QEL'
2 Maintype 1..127 see Annex D
3 Subtype 1..31 see Annex D
4 Flags BXXXX see Annex C1
5 INF integer see Annex C1
6-8 Information 3 integers see Annex C1
NOTE:
If no value is specified for an entry, then this entry
is not validated.
C̲3̲ ̲D̲a̲t̲a̲ ̲S̲e̲t̲u̲p̲ ̲f̲o̲r̲ ̲C̲I̲F̲
D̲A̲T̲A̲ ̲f̲o̲r̲ ̲C̲R̲E̲A̲T̲I̲O̲N̲ ̲o̲f̲ ̲a̲ ̲C̲I̲F̲
1. entry, Directive, shall contain 'CIF'
2. entry, Access Profile, shall be a long integer.
The encoding for the 32 bit is as follows:
0- 2 Security Classification
The following values are used:
1: Unclassified
2: Restricted
3: Confidential
4: Secret
5: Cosmic Top Secret
3 Encryption Indicator
Bit 3 is set for an encrypted item.
4-23 Special Handling Designators
One bit for each of the possible 20 special
handling designators. A bit set means that
the item has the corresponding designator set.
The following bits have been assigned:
4: ATOMAL Designator
5: Data Message Designator
6: Crypto Security Designator
7: Exclusive Designator
Bits 8-23 are variable for future assignements.
24 Exercise Indication
The values are:
0: Exercise
1: Non-exercise
The exercise indication of a message shall
be derived from the header. For all other kinds
of items, the exercise indication is set to
zero.
25-27 Item Type
There is one bit allocated to each of the following
groups of types:
25: Message Maintype : PLAINDRESS..ABB ̲SERVICE
26: Comment Maintype : SC ̲VDU ̲PAGE..COMMENT
27: Release Notification, Retrieved Item
28 Spare
29-31 Application Fields
This part of the profile can be specified as
a parameter in Send.
29: Message for delivery (E1, E2)
30: Message for coordination
31: Message for release
On the next pages is given a description of the data
to be specified for each field to be created in the
CIF. This information is collected to a Field List:
P̲R̲O̲F̲I̲L̲E̲:̲
Contains the profile of the CIF. The application part
of the profile is always zero.
I̲n̲p̲u̲t̲ ̲t̲o̲
- CREATE ̲CIF
O̲u̲t̲p̲u̲t̲ ̲f̲r̲o̲m̲
- All
R̲E̲F̲E̲R̲E̲N̲C̲E̲D̲:̲
Indicates if the field is referenced or not.
I̲n̲p̲u̲t̲ ̲t̲o̲
- CREATE ̲CIF
The field groups must be specified without "holes",
i.e. when the first not referenced field is met,
the rest is skipped.
- CREATE ̲VIEW
The new view can only reference a subset of the
field groups referenced by predecessor
- CREATE ̲FIELDS
O̲u̲t̲p̲u̲t̲ ̲f̲r̲o̲m̲:̲
All
P̲E̲R̲M̲A̲N̲E̲N̲T̲:̲
Indicates if the field is permanent or not.
I̲n̲p̲u̲t̲ ̲t̲o̲:̲
- CREATE ̲CIF
O̲u̲t̲p̲u̲t̲ ̲f̲r̲o̲m̲:̲
All
A̲L̲L̲O̲C̲A̲T̲E̲D̲ ̲L̲E̲N̲G̲T̲H̲:̲
Specifies the number of bytes allocated for the field.
I̲n̲p̲u̲t̲ ̲t̲o̲:̲
- CREATE ̲CIF
̲ CREATE ̲NEW ̲CIF ̲VERSION
In these two commands a specified non-zero value
will be used to allocate initial disk space for
the field.
- CREATE ̲VIEW
̲ CREATE ̲FIELDS
If specified in these commands that a new field
shall be added to the field group, ALLOCATED ̲LENGTH
may specify that space shall be allocated for the
field.
O̲u̲t̲p̲u̲t̲ ̲f̲r̲o̲m̲:̲
All
F̲I̲E̲L̲D̲ ̲S̲T̲A̲T̲U̲S̲:̲
Specify the states as follows:
0: Not existing
1: Field included from predecessor view
2: New field created
I̲n̲p̲u̲t̲ ̲t̲o̲:̲
CREATE ̲CIF
CREATE ̲NEW ̲CIF ̲VERSION
CREATE ̲VIEW
CREATE ̲FIELDS
In CREATE ̲CIF AND CREATE ̲NEW ̲CIF ̲VERSION, FIELD
̲STATUS specifies if a field has already been created
for the view. If specified, subsequent calls of
CREATE ̲FIELDS may be avoided.
In CREATE ̲FIELDS, FIELD ̲STATUS specifies whether
the field shall be included from predecessor view
or a new field shall be added to the field group.
O̲u̲t̲p̲u̲t̲ ̲f̲r̲o̲m̲:̲
All
An overview of ATTRIBUTES used as input parameter is
given in figure 4.1.7.2.4-6.
NOTE:
The field list containing information of each field
to be created in the CIF must not contain notes, i.e.
information for each field shall be given even though
the field does not exist.
However, it is not necessary to specify information
for fields succeeding a field where the entry 'REFERENCED'
is equal to 'FALSE', because when the first not referenced
field is met, the rest is skipped.
D̲A̲T̲A̲ ̲t̲o̲ ̲b̲e̲ ̲s̲t̲o̲r̲e̲d̲ ̲i̲n̲ ̲t̲h̲e̲ ̲C̲I̲F̲
Actual data for entries of type: SCD, PLA, RI, ID.,
Names, SIC, Designators, MHI and text is to be found
somewhere else.
F̲o̲r̲m̲a̲t̲ ̲f̲o̲r̲ ̲T̲i̲m̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
A long integer specifying the time in seconds since
a defined date.
E̲n̲c̲o̲d̲e̲d̲ ̲E̲n̲t̲r̲i̲e̲s̲
Maintype,
Flags : see Annex C1
Classification,
Spec.Hand.Inst.: see page
Precedence: 0 - DUMMY
1 - PREC1
2 - FLASH
3 - IMMEDIATE
4 - PREC2
5 - PRIORITY
6 - ROUTINE
Coor. check mark: X : coordination OK
space : coordination not OK
SCD: Each SCD shall consist of 4 characters (3 letters
terminated with 1 space).
NOTE:
Data to be stored in separate fields are identified
by a field number and terminated by the 'field end
mask' '.'
The sequence of data for each field shall be in increasing
order. The sequence may contain holes.
C̲4̲ ̲D̲a̲t̲a̲ ̲S̲e̲t̲u̲p̲ ̲f̲o̲r̲ ̲B̲u̲f̲f̲e̲r̲
Entry PROMPT VALUE COMMENT
-------------------------------------------------------------------
1 DIRECTIVE 'BUFFER'
2 DATA Integer Information to be sent
: :
: :
N Integer N is max. 27
C̲5̲ ̲D̲a̲t̲a̲ ̲S̲e̲t̲u̲p̲ ̲f̲o̲r̲ ̲S̲y̲n̲c̲.̲E̲l̲e̲m̲e̲n̲t̲
Entry PROMPT VALUE COMMENT
-------------------------------------------------------------------
1 Directive 'SYNC'
2 Data Integer Information to be sent to
a Sync.Element
: :
: :
N Integer N is max. 25.
