top - download
⟦e32342c84⟧ Wang Wps File
Length: 4478 (0x117e)
Types: Wang Wps File
Notes: Spelunked
Names: »~ORPHAN61.08«
Derivation
└─⟦b3c9a9699⟧ Bits:30006142 8" Wang WCS floppy, CR 0015A
└─ ⟦this⟧ »~ORPHAN61.08«
WangText
on status)
STATUSTYPE = Logical Data Unit, 0 to 255
RESULT = error code 1 to 255
PARAMS = undefined
3.5.4.9.2.3 I̲n̲t̲e̲r̲r̲u̲p̲t̲ ̲S̲t̲a̲t̲u̲s̲ ̲R̲e̲s̲p̲o̲n̲s̲e̲
BUFFERTYPE = #7
CONTROLTYPE = #2 (interrupt)
STATUSTYPE = #0 = RX protocol connected
1 = RX protocol disconnected
#2 = TX protocol disconnected
#3 = V24 error
RESULT = not used
PARAMS = not used
3.5.4.9.2.4 C̲h̲a̲n̲n̲e̲l̲ ̲S̲t̲a̲t̲u̲s̲ ̲R̲e̲s̲p̲o̲n̲s̲e̲
BUFFERTYPE = #7
CONTROLTYPE = #3 (channel status)
STATUSTYPE = #1 REOPEN
#2 SET ̲UP ̲LINK
#3 DISC ̲LINK
#4 SET ̲UP ̲LINES
#5 DISC ̲LINES
#6 SET-V24
#11 READ ̲V24
#12 STATISTICS
RESULT = 0 OK
1 Protocol not disconnected.
2 Protocol not connected
3 Parameter error
4 Illegal command
PARAMS = Refer to sections 3.5.4.1 thru3.5.4.8
3.5.4.10 R̲E̲Q̲U̲E̲S̲T̲ ̲O̲U̲T̲P̲U̲T̲
C̲o̲m̲m̲a̲n̲d̲ ̲F̲o̲r̲m̲a̲t̲:
BUFFERTYPE = #3 (request output)
CONTROLTYPE = Logical Data Unit number 0
to 255
STATUSTYPE = data byte
SPARE = data byte
PARAMS(1..126) = data
3.5.4.10.1 T̲r̲a̲n̲s̲m̲i̲s̲s̲i̲o̲n̲ ̲S̲t̲a̲t̲u̲s̲ ̲e̲s̲p̲o̲n̲s̲e̲
BUFFERTYPE = #7
CONTROLTYPE = #0 (transmission status)
STATUSTYPE = Logical Data Unit
sequence number, 0 to 255
RESULT = #0 TX ok
PARAMS = undefined…86…1 …02… …02… …02…
…02… …02… …02… …02…
3.5.4.10.2 I̲n̲t̲e̲r̲r̲u̲p̲t̲ ̲S̲t̲a̲t̲u̲s̲ ̲R̲e̲s̲p̲o̲n̲s̲e̲
BUFFERTYPE = #7
CONTROLTYPE = #2 (Interrupt)
STATUSTYPE = #1 = RX protocol disconnected
#2 = TX protocol disconnected
#3 =V24 error
RESULT = undefined
PARAMS = undefined
3.5.4.11 C̲L̲O̲S̲E̲ ̲L̲I̲N̲K̲
The command is used when closing the link for cleaning
up buffers pending in the LTUX FW. The LTUX will return
all buffers pending in the LTUX to the CR80 thereby
enablig a system restart without masterclearing the
CR80 and the LTUX.
BUFFERTYPE = #7 (Control command)
CONTROLTYPE = #5 (Close command ID)
STATUSTYPE = undefined
RESULT = undefined
PARAMS = undefined
No answer is returned to the CR80.
3.5.4.12 E̲x̲a̲m̲p̲l̲e̲
The following buffer is sent to CLP:
BYTE VALUE INTERPRETATION
1 #3 REQUEST OUTPUT COMMAND
2 #FE LDU number (modulo 256)
3 #45 1st data byte
4 #58 2nd data byte
5 #41 3rd data byte
6 #4D .
7 #50 .
8 #4C .
9 #45 .
. undef. undefined
130 undef. undefined
The following answer is returned:
BYTE VALUE INTERPRETATION
1 #7 STATUS RESPONSE
2 #2 Interrupt CONTROLTYPE
3 #2 TX protocol disconnected
4 undef. undefined
. undef. undefied
130 undef. undefined
The response indicates that the REQUEST OUTPUT command
failed to be executed as the level 2 protocol was unable
to transmit the data. Note, that the status type responses
do not identify which command caused the errorto occur.…86…1
…02… …02… …02… …02…
3.6 F̲I̲K̲S̲ ̲S̲Y̲S̲T̲E̲M̲ ̲U̲P̲D̲A̲T̲E̲S̲
The F̲I̲K̲S̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲P̲r̲o̲c̲e̲s̲s̲ (TEP) (ref. 1.3.25 + 1.3.26,
SFS- and MES- subsystems) shall be updated as follows:
To new supervisor (assistant) procedures ae implemented:
- Open FIKS-CCIS-link
- Close FIKS-CCIS-link
They are activated when a supervisor keys in 'OPC/CLC'
as response on 'PROC ̲'
The commands shall result in despatch of the AMOS-
messages defined in sec. 3.3.2.2 to the CTERM- proces.
This will involve updating of the 'Supervision'- module
in the SFS- subsystem and update of the
- CRT-table , ref. 1.3.6, sec. 8.6
- PTT-table , ref. 1.3.6, sec. 8.6
- SYNEF-table , ref. 1.3.6, sec. 8.5
The QACCESS ̲INIT- module (ref. 1.3.18) shall be
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
updated as follows:
If the CCIS-STATUS word in the critical region CONFIG
(ref. sec. 3.1.1.4) indicates, that the FIKS-CCIS
Link exist, then the SIGNAL- module in entries in
the CCIS- terminal queues shall be changed from
PIP to CPIP.
The S̲E̲N̲D̲ ̲R̲E̲P̲O̲R̲T̲ ̲M̲O̲N̲I̲T̲O̲R̲ (ref. 1.3.22)
shall be updated so that it is capable to handle
the new N/M Alarm texts defined in sec. 3.1.1.4.
P̲s̲t̲s̲c̲r̲i̲p̲t̲:
The above-mentioned updates are regarded as ordinary
FIKS System routine updates (error corrections, monor
changes, etc.). Therefor, when detailed and other information
is needed, refer to the appropriate documents, (Product
Specifications, Release Descriptions).
