top - download
⟦473a869fa⟧ Wang Wps File
Length: 31579 (0x7b5b)
Types: Wang Wps File
Notes: CMS/USM/001
Names: »4568A «
Derivation
└─⟦2e54efd14⟧ Bits:30006189 8" Wang WCS floppy, CR 0430A
└─ ⟦this⟧ »4568A «
WangText
.…0a….…0c….…0d….…0f….…02….…06….…07…-…08…-…0d…-…01…- …86…1
…02…
…02…
…02…
…02…CMS/USM/001
…02…840206…02……02…#
TDP USER
MANUAL
…02……02…CAMPS
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
1 INTRODUCTION ...................................
4
2 DOCUMENTS ......................................
5
3 TDP ............................................
6
3.1 TDP Runtime Requirements ...................
6
3.1.1 Equipment ..............................
6
3.1.1.1 General ............................
6
3.1.1.2 LTUX-requirement (runtime) .........
6
3.1.1.3 Backpanels/Cables ..................
8
3.1.1.4 TDP-TMS-HANDLER-LTUX Requirements ..
8
3.1.2 Scripts - input to TDP .................
11
3.1.2.1 Script - formats ...................
11
3.1.2.1.1 Generel Format .................
12
3.1.2.1.2 Detailed Formats with Examples .
14
3.1.2.2 Example of Complete Script Setup ...
26
3.1.2.3 Offline Script-generation Run ......
27
3.1.3 Logfile ................................
28
3.1.4 Run and Startup of TDP .................
29
3.1.4.1 Startup of Level 1: TDP-STI ........
29
3.1.4.1.1 Error Messages .................
29
3.1.4.2 Startup of Level 2: TDP-LTUX .......
30
3.1.4.2.1 Error Messages .................
30
3.1.4.3 Startup of Level 3: TDP-VDU ........
31
3.1.4.3.1 Startup errors .................
32
3.1.4.3.2 Fatal Errors ...................
33
3.1.4.3.3 Warnings and Messages ..........
36
3.1.5 TDP Requirements for CAMPS Startup ....
38
4 TDP MAINTENANCE ................................
39
1̲ ̲ ̲I̲N̲T̲R̲O̲D̲U̲C̲T̲I̲O̲N̲
This manual gives all information necessary to operate
TDP-VDU-Simulation, to recognize errors and to setup
a script for the simulation.
Never the less it requires an understanding of normal
CR80 and CAMPS operation.
Actually it is three separate parts:
Run of TDP,
Scripts and
TDP maintenance guide.
2̲ ̲ ̲D̲O̲C̲U̲M̲E̲N̲T̲S̲
TDS System Design (LN)
Test Drive System (CR)
TDP Detailed Design (CR)
CAMPS user procedures CPS/230/ICD/0001
3̲ ̲ ̲T̲D̲P̲
3.1 T̲D̲P̲ ̲R̲u̲n̲t̲i̲m̲e̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲
3.1.1 E̲q̲u̲i̲p̲m̲e̲n̲t̲
3.1.1.1 G̲e̲n̲e̲r̲a̲l̲
TDP should run on a CR80 Damos machine with at least
0.5 Mwords, 1 disk and a number of LTUX-S's.
3.1.1.2 L̲T̲U̲X̲-̲r̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲ ̲(̲r̲u̲n̲t̲i̲m̲e̲)̲
1̲ Standard LTUX-S sys.fw. Pt. 2298-03
2̲ Special TDS-LTUX-S appl.fw. Pt. 0101-43
3̲ Application switches (4), one for each channel.
OPEN - TDS side
CLOSED - CAMPS side
4̲ Address switches:
BSMX ̲NO CHANNEL (LTUX-NO)
On TDS-side use addresses as described below:
First LTUX: BSMX-no. 1, LTUX-no. 1
Second LTUX: BSMX-no. 1, LTUX-no. 2
Third LTUX: BSMX-no. 2, LTUX-no. 1
Fourth LTUX: BSMX-no. 2, LTUX-no. 2
Fifth LTUX: BSMX-no. 3, LTUX-no. 1
etc.
D̲e̲v̲i̲c̲e̲ ̲h̲i̲e̲r̲a̲r̲c̲h̲y̲ ̲i̲n̲ ̲T̲D̲S̲-̲s̲y̲s̲t̲e̲m̲:
Level 1, assign of STI/TIA is performed by TDP ̲STI.O.
Level 2, create of LTUX is performed by TDP ̲LTUX.O.
A process for each LTUX required.
Level 3, create of VDU and the simulation itself is
performed by TDP ̲VDU.O. A process for each VDU-simulation
required.
3.1.1.3 B̲a̲c̲k̲p̲a̲n̲e̲l̲s̲/̲C̲a̲b̲l̲e̲s̲
TDS LTUX's connected to backpanel-2 and CAMPS LTUX's
connected to backpanel-8 or vice versa.
Cables: Now we use a common 10-lead schreened RS-232
cable-only four leads used.
3.1.1.4 T̲D̲P̲-̲T̲M̲S̲-̲H̲A̲N̲D̲L̲E̲R̲-̲L̲T̲U̲X̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲
TDP requires on TDS side a special VDU-handler protocol,
the TP-LINK protocol.
This protocol is mentioned in system generation as
TMS-protocol no. 6. The protocol-id has to be 99.
On both sides, TDS and CAMPS, TDP requires a special
LTUX-S application firmware. Refer to the chapter LTUX-requirement
(runtime).
Next page shows the logical hierarchy TDP-TMS-TP-LINK-LTUX.
I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲ ̲-̲ ̲C̲A̲M̲P̲S̲ ̲a̲n̲d̲ ̲T̲D̲S̲
L̲o̲g̲i̲c̲a̲l̲ ̲C̲A̲M̲P̲S̲/̲T̲D̲S̲ ̲i̲n̲t̲e̲r̲f̲a̲c̲e̲
3.1.2 S̲c̲r̲i̲p̲t̲s̲ ̲-̲ ̲i̲n̲p̲u̲t̲ ̲t̲o̲ ̲T̲D̲P̲
3.1.2.1 S̲c̲r̲i̲p̲t̲ ̲-̲ ̲f̲o̲r̲m̲a̲t̲s̲
In this release (II) of TDP, following commands are
allowed:
FK,
COMMAND,
DATA,
LABEL,
END,
PASSWORD,
VERIFY,
REPEAT,
DELAY,
DELAY FACTOR,
TIME,
QUEUES,
RELEASE,
MESSAGE,
STOP,
TERMINATE.
They are all described further below.
First the general format is described, then the specific
syntax and semantics are described for each script-command
and last an example of setup for a whole script-session
is shown.
All data-entries are done via DAMOS text-editor, making
a text-editor-script file as input to the SCRIPT-GENERATOR
program.
Setup of scripts, requires knowledge off CAMPS VDU-operation
(see CPS/230/ICD/0001 user formats) since TDP is very
much connected/dependent to/of the way it (CAMPS VDU)
operates, and the character of these formats.
In the scripts all split, line and column numbers should
be identical to the position of fields defined in ICD/0001
formats.
3.1.2.1.1 G̲e̲n̲e̲r̲e̲l̲ ̲F̲o̲r̲m̲a̲t̲
%̲ (script ̲command) :̲ (space)(parameters) ̲ n̲l̲
Characters with underscores are r̲e̲q̲u̲i̲r̲e̲d̲ as shown.
(script ̲command) ::= FK/COMMAND/DATA/LABEL/END/PASSWORD/VERIFY/REPEAT/DELAY/DELAYFACTOR/TIME/MESSAGE/STOP/TERMINATE/QUEUES/RELEASE
(space) ::= one or several spaces
(parameters) ::= (set of param) !̲ n̲l̲ (set of param)
(set of param) ::= (p1) ;̲ (p2) ;̲ (p3) ;̲ (p4)
p1-p4 depends on script ̲commandtype
as shown below
n̲l̲ - means new ̲line (carriage return)
Comments are allowed - started by "̲ ,and rest of the
line is then treated as comments.
and are overall used to symbolize zero, one or
several occurences of the content between the brackets
S̲h̲o̲r̲t̲ ̲S̲c̲r̲i̲p̲t̲ ̲c̲o̲m̲m̲a̲n̲d̲ ̲o̲v̲e̲r̲v̲i̲e̲w̲:
%FK: ENTER/CANCEL/DELETE AND PRESENT MESSAGE
%DATA: (split);(line);(column);(txt) !
(split);(line);(column);(txt)
%COMMAND: SION/SIOF/PRNM/PRNC/RELS/RECV
%LABEL: (four letter label)
%END (four letter label)
%REPEAT: (four letter label);(no of repeats)
%PASSWORD: (id, password)
%VERIFY: (split);(line);(column);(txt) !
(split);(line);(column);(txt)
%DELAYFACTOR: (integerfactor)
%DELAY: (delay in seconds)
%TIME: (hour);(minute);(seconds)
%QUEUES: RECV/RESP ; O/E
%MESSAGE: (txt)
%STOP: (txt)
%TERMINATE: (txt)
%RELEASE: (scd); O/E
3.1.2.1.2 S̲p̲e̲c̲i̲f̲i̲c̲ ̲S̲y̲n̲t̲a̲x̲ ̲a̲n̲d̲ ̲S̲e̲m̲a̲n̲t̲i̲c̲s̲
%̲F̲K̲:̲ (sp)(function key) ̲ ̲ (n̲l̲)
(sp) ::= one or several spaces
(function key) ::= ENTER/CANCEL/DELETE AND
PRESENT MESSAGE
When interpreting %FK, TDP sends the code, corresponding
to the specified key to CAMPS.
Can be used after %DATA to transmit data, format etc.
to CAMPS.
Ex: %DATA: 2; 4; 41; SEN
%FK: ENTER
Above example shows a valid input to format A-3 (last
of prepare-new-message). First the text "SEN" will
be placed in split 2, line 4, position 41 (selecting
a s̲e̲n̲d̲) and thereafter an ENTER-key will be sent just
if an operator hits the ENTER-key.
Only to be used at times where ENTER are allowed according
to formats in ICD/0001.
%̲D̲A̲T̲A̲:̲ (sp)(split);̲(line);̲(column);̲(txt) !̲
(split);̲(line);̲(column);̲(txt) ̲
(split) ::= 0/1/2, split no.
(line) ::= numeric line no between 1 and 285.
(column) ::= numeric column no between 1 and 80.
(txt) ::= valid field content according to format.
only characters 0-9 , A-Z , . , /
sp
allowed.
Max 60 characters and only the number
of characters left at line from specified
column no up to and including col.80.
%DATA is used to "type" data in a format at specified
positions.
Ex: %DATA: 2; 2; 12; THIS IS A COMMENT TEXT!
2; 3; 12; LAST TEXT LINE USED
%FK: ENTER
%DATA: 2; 4; 41; SEN
%FK: ENTER
Example shows a short but valid script setup for "prepare
new comment" format G-2 & G-3.
When "typing" data in repeatable lines (first line
marked "R"), it is important to add "the inserted no.
of lines" to rest of line specifications in the format,
since TDP automatically will take care of insertion
off the lines needed. An example will clarify this:
In format A-1 (prepare new message) the "TO" fields
are repeatable, with 4 predefined entry lines before
insertion are required (line 22-25). The next group
"INFO" begins in line 27 if no lines are inserted in
connection to "TO" group.
%DATA: 2; 22; 17; PLA NO ONE! "TO - line one
2; 23; 17; PLA NO TWO! "TO - line two
2; 24; 17; PLA NO THREE! "TO - line three
2; 25; 17; PLA NO FOUR! "TO - line four
2; 26; 17; PLA NO FIVE! "TO - line five
2; 27; 17; PLA NO SIX! "TO - line six
2; 30; 17; INFO NO.ONE)) "INFO -line one
Since "TO" has room for four lines, line five and six
are automatically inserted, with the consequences,
that first entry to the INFO-group should be in line
30 (instead of line 28). Refer to ICD/0001 for specification
of the line-numbers.
NB! I̲t̲ ̲i̲s̲ ̲v̲e̲r̲y̲ ̲i̲m̲p̲o̲r̲t̲a̲n̲t̲ ̲w̲h̲e̲n̲ ̲i̲n̲s̲e̲r̲t̲i̲n̲g̲ ̲t̲e̲x̲t̲ ̲i̲n̲ ̲r̲e̲p̲e̲a̲t̲a̲b̲l̲e̲
̲l̲i̲n̲e̲s̲,̲ ̲t̲o̲ ̲u̲s̲e̲ ̲e̲a̲c̲h̲ ̲l̲i̲n̲e̲ ̲c̲o̲n̲s̲e̲q̲u̲t̲i̲v̲e̲l̲y̲.
%̲C̲O̲M̲M̲A̲N̲D̲S̲:̲ (sp)(four letter mnemonic) ̲
(four letter mnemonic) ::= SION/SIOF/PRNM/PRNC/RELS/RECV
TDP interprets a COMMAND by sending a command-key,
followed by an enter-key with the four letter command.
EX: %PASSWORD: LAA,LAALAALA
%COMMAND: SION
%COMMAND: PRNM
data to format A-1 etc.
%̲ ̲L̲A̲B̲E̲L̲:̲ (sp)(name) ̲
%̲E̲N̲D̲:̲ (sp)(name) ̲
(name) ::= four letter identification.
A label-end pair with the same (name) is used for identification
of a group of script-commands, making it possible to
reoeat these command, later in the script.
Label-end are only required if repetition is used.
Label-end's can be nested to a level of ten.
Ex: (See %REPEAT)
%LABEL: ABCD
%COMMAND:PRNC
A
%FK:ENTER
%LABEL:BBCC
B
%END: BBCC
%REPEAT: BBCC; 2
%END: ABCD
%LABEL:AAAA
%REPEAT: BBCC; 4
%REPEAT: ABCD; 2
%END: AAAA
%REPEAT: AAAA; 100
%̲R̲E̲P̲E̲A̲T̲:̲ (sp)(name);̲(no. of times) ̲
(name) ::= four letter label-end identification
(no. of times) ::= integer between 1 and 3600 (incl.),
specifying no. of times to repeat
the group (label-end-group).
Refer to example specified in connection with %LABEL/%END.
This example will result in execution as stated below:
A
B
ABCD first time
%REPEAT:BBCC;2 B
B
B
B
%REPEAT:BBCC;4 B
B
A AAAA first time
B
B
B
%REPEAT:ABCD;2
A
B
B
B
B
B
B
B
A
%REPEAT:AAAA; 100 B first repetition of AAAA
B
B
A
B
B
B
%̲P̲A̲S̲S̲W̲O̲R̲D̲:̲ (id, password) ̲
(id, password) ::= 12 character ident, password as
required in SION.
A password should be specified as one of the first
commands in script-file before %COMMAND: SION .
The password is saved and used automatically at subsequent
(SIOF) SION's in the script.
In future releases it might be used automatically for
all security interrogation.
Ex: %PASSWORD: ISB, ISBISBIS
%̲V̲E̲R̲I̲F̲Y̲:̲(sp)(split);̲(line);̲(column);̲(txt) !̲ n̲l̲
(split);̲(line);̲(column);̲(txt) ̲
(split) ::= 0/1/2
(line) ::= numeric line no. between 1 and 285
(column)::= numeric column between 1 and 80.
(txt) ::= contents to verify (max. 40 chars.)
only characters 0-9 , A-Z , . , /
sp
Ex: %VERIFY: 2; 2; 24; USER MENU))
The contents of VDU split in required positions are
compared with the contents specified in the verify-command.
An error message will be displayed if not identical
at runtime.
%̲D̲E̲L̲A̲Y̲:̲ (sp)(period) ̲
%̲D̲E̲L̲A̲Y̲F̲A̲C̲T̲O̲R̲:̲ (sp)(factor) ̲
%̲T̲I̲M̲E̲:̲ (sp)(hour);̲(minute);̲(second) ̲
(period) ::= delay period in seconds, 1-3600
(factor) ::= multiplicator, making it possible to
repeat a group, giving varied delays.
The delay period in seconds is multiplied
by factor giving the used delay.
Integer. period * factor should
be less than 3600 (1 hour).
(hour) ::= 0-23
(minute) ::= 0-59 Process is delayed until time
(second) ::= 0-59 = (hour):(minute):(seconds)
%TIME makes it possible to start a testsequence at
a specified time.
Ex: %TIME: 12; 0; 0 "test will continue at noon"
%LABEL: ABCD
.
.
.
%DELAY: 10
%END: ABCD
%DELAYFACTTOR: 20
%REPEAT: ABCD; 2
NB! Use delay and time commands b̲e̲t̲w̲e̲e̲n̲ sessions, preparations
etc. only. Never in a preparation.
%̲Q̲U̲E̲U̲E̲S̲:̲ (sp)(queuetype);̲(action) ̲
(queuetype) ::= RESP/RECV, Response or receive queue
(action) ::= O/E, remove One element (first)or
E̲mpty the queue (remove all
in descending priority).
Items are removed from receive or response-queue by
using DELETE ̲AND ̲PRESENT ̲NEXT. Select between one item
or all items in queue.
A message will be displayed, if the queue is already
empty, but the simulation will continue.
Ex: %QUEUES: RECV;O
%̲R̲E̲L̲E̲A̲S̲E̲:̲ (sp)(scd);̲(action) ̲
(scd) ::= releaser orginators scd - 3 letters;
(action)::= O/E , O - release o̲ne message
E - release all messages in
queue (E̲mpty queue).
Ex: %RELEASE: ISD; E
%LABEL: AAAA
%RELEASE: ISD; E
%DELAY: 600
%END: AAAA
%REPEAT: AAAA; 50
%̲M̲E̲S̲S̲A̲G̲E̲:̲ (sp)(txt) ̲
(txt) ::= contains a runtime message, which will
be displayed on the operator-VDU.
Max. 30 characters - 0-9 , A-Z , , . /
sp
A message is displayed, making it possible to see how
far the simulation has come.
Ex: %MESSAGE: PREP. OF MSG A1247 STARTED))
%̲S̲T̲O̲P̲:̲ (sp)(txt) ̲
%̲T̲E̲R̲M̲I̲N̲A̲T̲E̲:̲ (sp)(txt) ̲
(txt) ::= message to be displayed on operator VDU.
Max. 30 characters - 0-9 . A-Z , , . /
sp
A message is displayed on operator VDU, just as for
%MESSAGE.
%TERMINATE will thereafter terminate the simulation.
%STOP will ask for an operator-entry, either
C̲O̲N̲T̲I̲N̲U̲E̲ - the simulation is continued; or
T̲E̲R̲M̲I̲N̲A̲T̲E̲ - the simulation is terminated.
%STOP will thereby give a possibility to check simulationresults,
delaying the process the required amount of time, before
continuing.
%STOP: END OF SESSION ONE))
.
.
.
%TERMINATE: VDU 2 SIMULATION ENDED))
3.1.2.2
3.1.2.3 O̲f̲f̲l̲i̲n̲e̲ ̲S̲c̲r̲i̲p̲t̲-̲g̲e̲n̲e̲r̲a̲t̲i̲o̲n̲ ̲R̲u̲n̲
Scripts are setup and edited via Damos text-editor,
giving a text-edit-script file.
This file is compiled and validated by an offline generator
program named OFF ̲GEN.O
% *TDSVOL*USERS.D*TDS.D*TDP.D*OFF.D*OFF ̲GEN.O.
Execution of OFF ̲GEN.O requires setup as shown below:
OFF ̲GEN.O IE:text-edit-file OC:commandfile OD:datafile
A:append
text ̲edit ̲file = file name of text ̲editor ̲script
̲file, input to the offline-generator.
commandfile = filename of Simulation commandfile,
output.
datafile = file name of simulation datafile,
output.
append = Y/N
if "Y" the scripts from editor
file are appended to the contents
of command and datafile.
if "N" or if the parameter is excluded,
then command ̲and ̲data ̲files are
emptied before use.
A compilation without errors will appear on VDU as
follows:
OFFLINE COMMAND-/DATAFILE GENERATOR REL.001 IS STARTED
END OF EDITING FILE
OFFLINE COMMAND-/DATAFILE GENERATOR HAS TERMINATED
followed by register dumps (from MON(TERMINATE)).
When errors are detected, error messages (if possible
containing line number) are displayed on VDU. When
detecting an error, correct the fault and run again.
When using a̲p̲p̲e̲n̲d̲ ̲y̲e̲s̲, realize that part of the editor
file has been appended properly.
Error texts:
"SYNTAX ERROR",
"ILLEGAL FUNCTION KEY",
"ILLEGAL COMMAND FUNCTION",
"TOO MANY FIELDS SPECIFIED", (MAX. 280)
"TOO MANY LABELS SPECIFIED", (MAX. 50)
"NO LABELS SPECIFIED",
"LABEL/END MISMATCH",
"TOO MANY REPEATS SPECIFIED", (nested max. 10)
"TOO MANY CHARACTERS",
"TOO LARGE DIGIT",
"ILLEGAL COMMAND",
"EDITING FILE EMPTY",
"LINE NOT READ",
"RECORD NOT READ",
"FILE ENTRY SYNTAX", file/IO errors,
"COMMAND RECORD NOT OUTPUT", IO-completioncode
"POSITION NOT FOUND", shown in addition
to
"POSITION NOT SET", the text.
"FILE NOT RESET",
"OUTTEXT ERROR",
"OUTLINE ERROR",
3.1.3 L̲o̲g̲f̲i̲l̲e̲
During run of the simulation (TDP ̲VDU) all transactions
concerning input and output from/to CAMPS or LTUX are
logged in the format they are received or sent, that
is normal ldu-format, except that every ldu before
log is timetagged.
Precise format is:
record,
hour,
second,
millisecond,
sequence no.,
input-output: integers;
ldu : array ((1 .. 128)) of chars;
end
3.1.4 R̲u̲n̲ ̲a̲n̲d̲ ̲S̲t̲a̲r̲t̲u̲p̲ ̲o̲f̲ ̲T̲D̲P̲
To run a VDU simulation all three levels according
to LTUX-description has to be started under TDSSTARTUP.D.
3.1.4.1 L̲e̲v̲e̲l̲ ̲1̲:̲ Assign of STI and Create of Subdevice TIA
TDP ̲STI.O 01: FILES.D*LTUX1 02: FILES.D*LTUX2 etc.
This version can handle up to 10 files - 10 LTUX's
3.1.4.1.1 Errors possible in TDP STI are all errors connected
to TMS/IO/PCF
"ASSIGN ERROR",
"CREATE TIA ERROR",
"ENTER ERROR" - impos. to enter TIA ̲NAME/handle
in directory
"PROTECT ERROR" - protection error, while protecting
entry in dir.
"INIT ̲AWAIT ERR", - sync. el errors
"DUMMY ̲AWAIT ERR",
"NO SYNC EL",
"NO DUMMY SYNC EL",
"SYNCAT IP", - error while catalogging or
"CAPABILITIES IP" while updating capabilities.
Furthermore file errors concerning one of the outputfiles
are possible:
"ERROR FILETYPE ID",
"FILE ID SYNTAX",
"OUTREC ERROR".
When displaying errors the completioncode is displayed
too, where possible.
A correct run of TDP ̲STI will result in the following
display on VDU:
STI ASSIGNED
SUBDEV TIA CREATED
STI ̲TIA OK
It will continue to run (until killed) to prevent TOS
from releasing resources.
3.1.4.2 L̲e̲v̲e̲l̲ ̲2̲:̲ ̲C̲r̲e̲a̲t̲i̲o̲n̲ ̲o̲f̲ ̲S̲u̲b̲d̲e̲v̲i̲c̲e̲ ̲L̲T̲U̲X̲
One process for each LTUX required, has to be started
with an outputfile for each VDU used on the LTUX.
TDP ̲LTUX.O I1: FILES.D*LTUX1 01: FILES.D*VDU12 ...
............. 04: FILES.D*VDU15
Use 01 to 04 for outputfiles.
TDP ̲LTUX will just as TDP ̲STI continue to run and has
to be killed manually when test is over.
VDU display for correct run will appear as follows:
START TDP ̲ LTUX
SUBDEV LTUX CREATED
NO CH ̲3 ̲VDU
NO CH ̲4 ̲VDU Only if files (02, 03 and
NO CH ̲5 ̲VDU 04 are excluded)
TDP ̲LTUX OK
3.1.4.2.1 Errors will result in an error message and in termination
of the run.
Possible errors are:
File errors:
"ERROR FILETYPE"
"FILE 02 SYNTAX"
"RESET ERROR", followed by fileident.
"INREC ERR"
"INPUTFILE MISSING"
"FILEERROR"
Other errors:
"CREATE LTUX ERROR"
"SYNC ̲EL NOT FOUND"
"GET ROOT FAILED"
"ENTER LTUX FAILED"
"PROTECT LTUX FAILED"
"NO DUMMY SYNC ̲EL"
"DUMMY AWAIT ERR"
3.1.4.3 L̲e̲v̲e̲l̲ ̲3̲:̲ Creation of subdevice VDU and simulation of
the VDU
When the STI is assigned and the LTUX is created then
you have to wait for CAMPS to get ready before starting
the VDU simulation.
CAMPS opens the line by raising DTR(DSR). On CAMPS
OC, the lines shown below will appear at that time:
"STIMULATOR REL ..."
"PLEASE SPECIFY ..."
"DEFAULT: OUTFILE STI ̲LOG
"COMMAND:"
From that point CAMPS will timeout on the line after
= 5 minutes, if the simulation is not started within
this timeframe. You can start the simulation up to
four minutes before CAMPS is ready (the TDS ̲LTUX ̲S
times out after four minutes, if the line is not coming
up).
Start simulation by executing.
TDP ̲VDU.O IC: commandfile ID: datafile
OL: logfile VI: VDU ident. file
All files are mandatory:
Command and datafiles are both output from script generation.
Logfile is used to log all incoming and outgoing traffic.
VDU ident. file is output from level-2 execution and
identifies the VDU channel to use in simulation. As
an example refer to level-2 description it could be
"FILES.D*VDU12".
An example with start-up of all three levels is shown
below:
Example:
I: TDP ̲STI.O 01:LTUX3 02:LTUX4
II: TDP ̲LTUX.0 I1:LTUX3 01:VDU31 02:VDU32
TDP ̲VDU.O IC:ICMD31 ID:IDATA31 OL:LOG31 VI:VDU31
III
TDP ̲VDU.O IC:ICMD32 ID:IDATA32 OL:LOG32 VI:VDU32
II TDP ̲LTUX.O I1:LTUX4 01:VDU41
III TDP ̲VDU.O IC:ICMD41 ID:IDATA41 OL:LOG41 VI:VDU41
A normal startup of VDU simulation (level 3) will result
in the following display on TOS ̲CMI ̲VDU:
TDP ... VDU SIMULATOR REL.001 IS STARTED
SUBDEV ̲VDU CREATED
CHANNEL OPEN
PROT.ENABLED
PROTOCOL OPEN
Display on this VDU before the message "PROTOCOL OPEN"
of errors are described under START ̲UP errors. Errors
displayed after the message "PROTOCOL OPEN" are called
runtime errors.
Description of possible errors during execution of
the simulation (level 3).
3.1.4.3.1 E̲r̲r̲o̲r̲s̲ ̲D̲u̲r̲i̲n̲g̲ ̲S̲i̲m̲u̲l̲a̲t̲i̲o̲n̲ ̲R̲u̲n̲
Startup errors:
"INREC ERR"
"VDU ̲INFO ̲FILE MISSING"
"FILEERROR"
"FILETYPE SYNTAX"
"SYNC ̲EL NOT FOUND"
"GET LTUX ̲IX FAILED"
"TIME ̲SYNC ERR"
"CREATE SUBDEV ̲VDU ERROR"
"OPEN CHANNEL ERROR"
"ENABLE ̲INITREAD ERROR"
"ENABLE ̲APPEND ERROR"
"ENABLE WAIT ERROR"
"ENABLE CONTENTS ERROR"
"OPEN ̲PROTOC INITREAD ERROR"
"OPEN ̲PROTOC APPEND ERROR"
"OP.PROT, WAITERR"
"OPEN ̲PROTOC CONTENTS ERROR"
Display on VDU (TOS) after "PROTOCOL OPEN" will be
a combination of scriptmessages, irregularities and
runtime errors.
Irregularities are unexpected situations such as VERIFY's
that fails, message in response-line from CAMPS or
error codes in margin area (sent by VUP). The VDU simulator
is trying to survive these conditions by skipping until
next COMMAND, STOP, TIME, DELAY, DELAYFACTOR or TERMINATE.
When an error is detected in responseline or in margin
area the line will be displayed on VDU.
Runtime errors are divided in fatal and non-fatal errors.
The simulator will try to survive a non-fatal error,
but a fatal error will always result in termination
of the simulation for this CAMPS "VDU".
All errors and warnings in level-3 runtime are prefixed
by three letters and a number;
- tmmxx - t̲ can be F for Fatal error
or W for Warning
- m̲m̲ is a module identification
- x̲x̲ is a consecutive number within the
module.
Ex: FSI01 - fatal error in SIM ̲CONTROL.
Fatal system errors are prefixed by completioncode.
Moduleidentifications:
CE - CONTR ̲ENTRYINT
CW - COMM ̲WAIT
LO - LOG
SC - SCR ̲COMMAND
SI - SIM ̲CONTR
VH - VDU ̲HANDLER (INPUT ̲DATA/OUTOUT ̲DATA)
VU - VDU ̲SPLIT
3.1.4.3.2 F̲a̲t̲a̲l̲ ̲E̲r̲r̲o̲r̲s̲
FCE05 - Reception ERROR XXX, invalid receptionstatus
XXX identifies VDU.
FCE09 - TRANSMISSION STATUS, normally followed
by DEVICE ERROR XXX or
END OF LDU MISSING XXX or XXX identifies
TIME OUT XXX VDU
FCE10 - INTERRUPT ERROR REPORT, followed by INTERRUPT
CODE = XXX ERROR CODE = YYY
where XXX shows interrupt code and YYY
error code, in decimal.
FCE11 - OPEN PROT. ERROR
FCE12 - OP. PROT. WAITERR attempt to reopen
protocol failed
FCE13 - PROT. ERROR
FCW01 - AWAIT SINGLE ERROR, IOS error completion
code shown in front of error message.
FCW02 - OP.ID ERROR, illegal operation id used.
FLO01 - LOG ERROR, completion code in front of
error message will identify cause.
FSC01 - FILE ENTRY SYNTAX, missing file(s)
FSC02 - INIT READ ERROR reading from VDU failed
FSC03 - INREC ERROR
FSC07 - INREC ERROR, read error on command file
FSC08 - ILLEGAL COMMAND, unknown script ̲command
FSC09 - POSITION NOT FOUND IOS GETPOSITION
or SETPOSITION
failed
FSC10 - POSITION NOT SET
FSC11 - END OF DATA FILE
FSC12 - LINE NOT READ
FSC13 - ERROR ON FILE
FSC14 - DATA-FILE INCONSISTENT Datafile inconsistences
FSC15 - NO DATA RECORD FOUND
FSC16 - SETPOS FAILED
FSC17 - GETPOS FAILED
FSC18 - DATAFILE READER
FSC19 - NON WRITABLE FIELD, attempt from SCRIPT
to put data in unformattet splitline. Error
in scriptline , VDU-format-error or syncronization
error.
FSI01 - SCRIPT COMMAND ERROR, unidentified command,
program error.
FSI02 - COMMAND DISBALED
FSI03 - INSERT DISABLED Attempt to send a
functionkey, which is
FSI04 - SYSTEM DISABLED disabled for the moment.
Probably a syncronization
FSI05 - ENTER DISBALED ERROR; TDP ̲CAMPS.
FSI06 - CANCEL DISABLED
FSI07 - DEL ̲AND ̲PRES DISABLED
FSI08 - RET ̲TO ̲CUR DISABLED
FSI09 - UNKNOWN FUNCTION, program error?
FSI10 - UNKNOWN COMMAND, program error?
FSI15 - MAX LINES EXCEEDED, script error, attempt
to insert above size of split ̲memory,
FSI16 - TIME: READ ̲ERR
FSI17 - TIME: CONV ̲TO ̲INT ERR
FSI18 - TIME: CONV ̲FROM ̲INT ̲ERR RTC ̲error, refer
to
completion-code.
FSI19 - TIME: INIT ̲AWAIT ERR
FSI20 - TIME: SCHEDULE ERR
FSI21 - TIME ERROR
FSI22 - CONV ̲IX OUT OF RANGE, syncronization error
or change in CAMPS VDU-queueline, in headersplit.
FVH01 - LDU LENGTH/STATE ERROR, error in LDU or
transmission error (time-out).
FVH02 - INIT RB ERROR IOS error in
INPUT ̲DATA refer
to
FVH03 - APPEND BYTES ERROR completion-code.
FVH04 - WAITOPERATION ERROR
FVH05 - APPEND BYTES ERROR, IOS error in OUTPUT
̲DATA
FVU08 - ILLEGAL FIRST LINE, error in arm ̲command
FVU10 - ILLEGAL FIELD LGTH
FVU11 - EXCESSIVE CURSOR
inconsistent
field definitions
FVU13 - OVERLAPPING FIELD DEFINITIONS
FVU15 - MAX LINE EXCEEDED, split memory overflow
in TDS. Change "MAX ̲LINES" if required
and recompile.
FVU16 - ATTEMPT TO DEFINE TOO MANY FIELDS, change
const. "MAX ̲NO ̲OF ̲FILEDS" if required and
recompile.
3.1.4.3.3 W̲a̲r̲n̲i̲n̲g̲s̲ ̲a̲n̲d̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
WCE01 - BAD FORMAT, a control ̲LDU ̲type not according
to formats implemented, is received.
WCE02 - DEVICE ERROR XXX
WCE03 - TIME OUT ON LTUX XXX response to
input-request.
XXX
WCE04 - END OF LDU MISSING XXX identifies VDU.
WSC04 - NO COMMAND ENTERED type CONTINUE
or TERMINATE
WSC05 - ERROR IN COMMAND
WSC06 - END OF COMMAND FILE, command file without
a "%TERMINATE".
WSI11 - INVALID REPLY, %STOP ̲command, type CONTINUE
or TERMINATE.
WSI12 - COMMAND: RELS, QUEUE EMPTY
WSI13 - COMMAND: RECV, QUEUE EMPTY no action queue
initially empty
WSI14 - COMMAND: RESP, QUEUE EMPTY
WSI23 - RESP QUEUE UNEXP
unexpected answer
on
WSI24 - RECV QUEUE UNEXP RECV, RESP or
RELS.
Queue probably
empty
WSI25 - RELEASE STATE UNEXP Response line
in
headersplit
can be
WSI26 - RELEASE UNEXP displayed too.
WVU01 - BAD RECORD, LDU not starting with IOC ̲REC
or ARM ̲COMMAND. Skipped.
WVU02 - WRONG IOC TYPE, record skipped.
WVU03 - BAD ARM, arm command unknown
WVU04 - ARM FUNCTIONS NOT IMPL, skipped.
WVU05 - ILLEGAL CHARACTER, a character, not identified
as a function or part of a text, is received.
Skipped to next function. The character
is displayed in front of message (hex).
WVU06 - ATTEMPT TO BACKSPACE TO COL. 0, skipped.
WVU07 - CONTROL FUNC. NOT IMPLEMENTED, skipped
to next function.
WVU09 - WRITE ̲TO ̲FIELD NOT IMPL., skipped to next
function.
WVU14 - LINK SPLIT NOT IMPL, skipped to next function.
WVU17 - FELETE N CHARACTERS NOT POSSIBLE, no of
characters errorprone. Skipped.
WVU18 - ILLEGAL SEND ̲FIELDS, field-number or number
of fields errorprone. Skipped.
XXX ... XXX YY ... YY, a verify command failed.
XX ... XX shows actual
contents. YY ... YY shows
expected contents. Simulation
continues.
3.1.5 T̲D̲P̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲ ̲f̲o̲r̲ ̲C̲A̲M̲P̲S̲ ̲S̲t̲a̲r̲t̲u̲p̲
Timing in enable format for user VDU have to be changed
in Copsy device data on CAMPS:
TIME ̲OUT ̲106 change to #50
TIME ̲OUT ̲107 change to #50
Use Diag PTCH to change during startup.
TDP requires that security interrogations and security
warnings are discarded. Switch off in Supervisor function
"SECC".
4̲ ̲ ̲T̲D̲P̲ ̲M̲A̲I̲N̲T̲E̲N̲A̲N̲C̲E̲
TDP consists of 4 programs (processes):
OFF ̲GEN.O - offline generator of scriptfiles
TDP ̲STI.O - TDP-STI-assignment
TDP ̲LTUX.O - TDP-LTUX-Creation of subdevice
TDP ̲VDU.O - TDP-VDU-Simulation.
OFF ̲GEN.O is only used offline for scriptfilegeneration.
All programs, files etc. are placed on TDSVOL under
%*TDSVOL*USERS.D*TDS.D*TDP.D
using a hierarchy of subdirectories (under TDP.D).
OFF ̲GEN.O under OFF.D,
TDP ̲STI.O,
under TDSSTARTUP.D
TDP ̲LTUX.O and
TDP ̲VDU.O.
TDP ̲VDU consists of a number of modules, each placed
on subdirectories (depending of subpackage connection):
TDP ̲VDU (under TDSSTARTUP.D),
SIM ̲CONTR, CONTRENTRYINT, COMM ̲WAIT,
SIM ̲TERM (under SIM.D),
VDU ̲SPLIT 1, VDU ̲SPLIT2 (under VDU.D),
SCR (under SCC.D)
LOG (under LOG.D),
READPARAMFILE (under TDP.D).
Attached a printout of directories on TDSVOL. Source,
object, link, linkfiles, control strings etc. are placed
according to CPS standard.
Linkfiles, postfixed - . JL,
compilestrings, postfixed - . JC,
linkprint , postfixed - . PL,
compileprint, postfixed - . PC.
Linkfile to runtime version of TDP ̲VDU is TDP ̲VDU.JL,
directly under TDPSTARTUP.D.
