top - download
⟦682b3fb78⟧ Wang Wps File
Length: 10246 (0x2806)
Types: Wang Wps File
Notes: Spelunked
Names: »~ORPHAN44.12«
Derivation
└─⟦b3c9a9699⟧ Bits:30006142 8" Wang WCS floppy, CR 0015A
└─ ⟦this⟧ »~ORPHAN44.12«
WangText
3.2.3.5 E̲r̲r̲o̲r̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲
In the following is listed the most likely error cases
that may arise in the CNSS -processing and the actions
taken.
T̲i̲m̲e̲o̲u̲t̲ ̲f̲r̲o̲m̲ ̲t̲h̲e̲ ̲T̲D̲X̲-̲s̲y̲s̲t̲e̲m̲
APPED of packets to the TDX-system may result in a
#0607 error code (ref. 1.3.6, sec. 4.2.2.2). This error
is of 'LOCAL FIX UP'-type. The error will indicate
a severe malfunction in the CCISLTUX-TDX-system. Recovery
from the error is performed by reiniializing of the
CCISLTUX concerning both the TDX-system and the X25-protocol.
Ref. sec. 3.2.3.2.
L̲i̲n̲k̲ ̲E̲v̲e̲n̲t̲s̲
If the CNSS gets an EVENT from the X25-protocol (ref.
1.3.14, sec. 3.1.2.5.4) indicating a failure in the
link, this is reported to theFIKS system as an LOCAL
̲FIX ̲UP error report with error code equal #2222. If
the error indicates disconnection, then the X25-protocol
is (attempted) reinitialized as described in 3.2.3.2.
L̲i̲n̲k̲ ̲F̲a̲i̲l̲u̲r̲e̲
In case a 'FODCCIS FAILURE' is discovered bythe CPIP-process
(ref. sec. 3.4.3.6) an AMOS-signal is sent to CNSS.
The CNSS will then perform reinitialization of the
X25-protocol as described in sec. 3.2.3.2.
U̲n̲e̲x̲p̲e̲c̲t̲e̲d̲ ̲D̲a̲t̲a̲
If some kind of unexpected (corrupted) data are received
by the CSS, this is reported by use of 'LOCAL ̲FIX ̲UP'-error
report with error code equal #2222 (ref. sec. 3.2.4).
No other actions are performed.
M̲i̲s̲s̲i̲n̲g̲ ̲P̲a̲c̲k̲e̲t̲s̲
The CNSS keeps constantly track of the packets passing
to/from the CCISLTUX by use of the DU NUMBER in the
data packets. Ref. 1.3.14, sec. 3.1.2.5.(5 + 6). If
a LDU-number is missing, either in the incoming or
the outgoing sequence this is reported as a 'LOCAL
̲FIX ̲UP'-error report with error code equal #B03. No
other actions are taken.
3.2.4 C̲N̲S̲S̲ ̲E̲r̲r̲o̲r̲ ̲L̲o̲c̲a̲t̲i̲o̲n̲s̲
3.2.5 C̲N̲S̲S̲ ̲N̲o̲t̲e̲s̲
S̲t̲o̲r̲a̲g̲e̲ ̲A̲l̲l̲o̲c̲a̲t̲i̲o̲n̲:
The CNSS-process has the following memory claim (approximately)
in words:
Program: 585 (max. overlay)
Process: 1230
The FIKS Overlay Moitor, ref. 1.3.3.3, has been used
at the implementation of the CNSS to reduce the program
memory claim. The CCIS-LTUX initializing processing
has been extracted from the CNSS Main Flow and placed
in a separate overlay.
P̲e̲r̲f̲o̲r̲m̲a̲n̲c̲e̲ ̲C̲h̲a̲r̲a̲c̲t̲e̲r̲i̲s̲t̲i̲c̲s̲
The way, the CNSS-process is performing IO-operation,
imply that the CNSS must never exist as 'Background
Process' in the FIKS system.
Ref. 1.3.28, sec. 3.3.15.
P̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲ ̲f̲o̲r̲ ̲D̲e̲l̲i̲v̲e̲r̲y̲:
Do as stated in the file 'INFORMATION' in the last
deivery of CNSS to FIXLIB. (ref. 1.3.34).
M̲o̲d̲u̲l̲e̲ ̲G̲e̲n̲e̲r̲a̲t̲i̲o̲n̲:
The CNSS-module is compiled and linked by means of
the AMOS SWELL Compiler and Linker. Refer to 1.3.35/36/37/38.
3.3 C̲C̲I̲S̲ ̲T̲E̲R̲M̲I̲N̲A̲L̲ ̲P̲R̲O̲C̲E̲S̲S̲ ̲(̲C̲T̲E̲R̲M̲)̲
3.3.1 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The CTERM-Process has the following tasks:
- Receive all messages sent from CCIS to FIKS
- Separate Control and Narrative Messages from each
other.
- Process Control Message as follows:
1) Message ACK-
forward it to the CPIP-Process.
2) Message NAK-
forward it to the CPIP-Process.
3) Open Link Agreement -
Mark CCIS-FIKS link as OPEN. 4) Open
Link
Rejection
-
Mark CCIS-FIKS Links as CLOSED.
5) Close Link -
Mark CCIS-FIKS link as CLOSED.
6) Other Control Messages -
ignore
- The CTERM is monitoring 'time-out' upon 'Open Link
Agreement'.
- Narrative Messages are hecked to be valid FIKS-SMF-Messages
by doing the following checks:
1) total length is less than 9000 bytes and does
correspond to the length of the PDB-file in
which it is placed.
2) action and info. precedence is valid
(range 1-6)
3) clssification code is in the valid range for
the CCIS-terminal.
4) address list offset, signal header length,
MSG ̲ID ̲reference, SIC-reference does not exceed
the total length.
5) The message is not of special handling type.
If the checkingfails, then CTERM sees to it that
a NACK on the message is returned to CCIS. If the
checking answers OK then an ACK is returned, and
the message is released to the FIKS-Network. I.e.
enqueued to the MDS-Process (ref. 1.3.20) and checkpointed
(ref. .3.19). LOG ̲JOURNAL (message released) is
performed. ref. 1.3.21.
- Receive and process CCIS Supervisor Commands:
1) Open Link Request -
Initiate despatch of an 'Open Link Request'
control message and start a timeout test on
return of the orresponding 'Open Link Agreement/Open
Link Rejection' Control Message.
2) Close Link Command -
Initiate despatch of a 'Close Link' Control
Message and immediately set FIKS-CCIS Link
Status to 'CLOSED'.
- The CTERM-process reports to the FIK supervisor
by using the SEND REPORT-Procedure (ref. 1.3.22)
about changes in the FIKS-CCIS-Link Status.
- The CTERM maintains the MEDE-Statistics (ref. 1.3.6,
sec. 10.2.2.10) concerning the CCIS-terminal in
the critical region 'STATIC'.
3.3.2 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
3.3.2.1 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲O̲v̲e̲r̲v̲i̲e̲w̲
FIKS Interface refer to 1.3.6
Refer to fig. 3.3.2.1-1.
S̲y̲s̲t̲e̲m̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲
1. FMS-System via the IO-system
2. Kernel, se of AMOS-Message Functions and Critical
Region Procedures.
F̲I̲K̲S̲ ̲A̲p̲p̲l̲i̲c̲a̲t̲i̲o̲n̲s̲
1. FIKS Monitors -
QACCESS, MTCB, LOG-JOURNAL, SEND REPORT.
2. FIKS Critical Regions -
CONFIG (CCIS-STATUS)/STATIC (Statistics)
3. FIKS-Queues -
The MDS - ,M,P,O,Y,Z - queues, Supervisor Al-queue,
4. FIKS-Modules -
The TERMXX-process when the FIKS Supervisor issue
of commands concerning CCIS.
5. CHECKP-process -
At checkpointing.
C̲C̲I̲S̲-̲A̲p̲p̲l̲i̲c̲a̲t̲i̲o̲n̲s̲
1. CNSS-Process (Reception of Messages)
. CPIP-Process (Despatch Control Message Commands)
F̲i̲l̲e̲s̲
1. PDB- files…86…1 …02… …02… …02… …02…
FIGURE 3.3.2.1-1
CTERM INTERFACE OVERVIEW…86…1 …02… …02… …02… …02… …02…
3.3.2.2 F̲o̲r̲m̲a̲t̲ ̲o̲f̲ ̲A̲M̲O̲S̲ ̲M̲e̲s̲s̲a̲g̲e̲/̲A̲n̲s̲w̲e̲r̲ ̲t̲o̲/̲f̲r̲o̲m̲ ̲C̲T̲E̲R̲M̲
Messages from CNSS about reception of message from
CCIS.
Message Answer
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲
^̲ ̲Type = 0 ̲^̲ Word 0 ^̲ ̲ Type = 0 ̲^̲
^̲ ̲MTCB index ̲^̲ 1 ^̲ ̲ MTCB index ̲^̲
^̲ ̲(of MTCB ̲^̲ 2 ^̲ ̲ ̲^̲
^̲ ̲refrring to ̲^̲ 3 ^̲ ̲ ̲^̲
^̲ ̲m̲e̲s̲s̲a̲g̲e̲)̲ ̲ ̲ ̲ ̲ ̲^̲ 4 ^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲
The use and layout of the MTCB's is as for CNSS-interfaces.
(ref. sec. 3.2.2.2).
Messages from TERMXX-process (Supervisor commands)
(XX = atual supervisor terminal no.), concerning FIKS-CCIS
Link Open/Close request.
Message Answer
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲
^̲ ̲Type = 1 ̲^̲ Word 0 ^̲ ̲Type = 1 ̲^̲
^̲ ̲Command Code ̲^̲ 1 ^̲ ̲Command Code ̲^̲
^̲ ̲ ̲^̲ 2 ^̲ ̲ ̲^̲
^̲ ̲ ̲^̲ 3 ^̲ ̲ ̲^̲
^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲ 4 ^̲ ̲C̲o̲m̲p̲l̲e̲t̲i̲o̲n̲ ̲ ̲ ̲^̲
C̲o̲m̲m̲a̲n̲d̲ ̲C̲o̲d̲e̲s̲: C̲o̲m̲p̲l̲e̲t̲i̲o̲n̲s̲
0 : Open Link Request 0
:
OK
(Command
Accepted)
1 : Close Link Command 1
:
Unexpected
Command
Returned
immediately
after
reception
3.3.3 C̲T̲E̲R̲M̲ ̲P̲r̲o̲c̲e̲s̲s̲i̲n̲g̲
3.3.3.1 C̲T̲E̲R̲M̲ ̲M̲a̲i̲n̲ ̲F̲l̲o̲w̲ (ref. fig. 3.3.3-1)
The CTERM passes through an initializing phase. After
this, events to initiate some kind of processing is
awited. They may be:
1) Reception of a message from CCIS.
The event is noted as an AMOS message sent to CTERM
from CNSS with layout as stated in sec. 3.3.2.2.
The message may be both a narrative and a control
message. The type depends upon the MTCB-type (PSEUDO/REAL)
ref. sec. 3.2.2.2. Of all messages the control
messages has the highest priority, and of those
ACK/NACK's has the highest priority. To ensure
that this priority scheme is kept, the CTERM-AMOS
message queue (ref. 1.3.27) is sanned by use of
'MON(INSPECTEVENTS), MON(SAVEEVENT), 'MON(RECOVEREVENTS)'
each time an AMOS-message is received. The first
one with the highest priority is processed.
2) Reception of a supervisor command. This event is
realized as an AMOS messagesent from one of the
supervisor terminal processes with layout as stated
in sec. 3.3.2.2.
3) Timeout upon 'Open Agreement' - request.
The timeout test is started at reception of the
request (ref. 2). To control this timing the AMOS
SET-CYCLE/ZEOPHASE - event is used.
(ref. 1.3.27 + 1.3.28). This timer is the only
one to be handled by CTERM. Therefore CYCLE can
be used directly as timeout time. Dismantling (i.e.
cancel of timeout test) of the timer is simply
performed by setting CYCLE t zero.
FIGURE 3.3.3-1
CTERM MAIN FLOW
3.3.3.2 C̲T̲E̲R̲M̲ ̲I̲n̲i̲t̲i̲a̲l̲i̲z̲i̲n̲g̲
As the FIKS MTCB/QACCESS - Monitors are used, MTCB
̲INIT shall be performed. ref (1.3.29 + 1.3.30).
CTERM is responsible for reopening of the FIKS CCI
Link after a 'SWITCHOVER' at the FIKS Node/MEDE. The
status of the link as it was before SWITCHOVER has
been checkpointed. This CCIS ̲STATUS is retrieved by
use of the Checkpoint procedure, ref. 3.1.1.4 + ref.
1.3.6, sec. 8.1.4. If the status is 'CIS ̲OPEN' then
a 'Open Link Request'- control message is despatched
to CCIS in the same way as if it was initiated by a
supervisor command. ref. 3.3.3.5.
3.3.3.3 P̲r̲o̲c̲e̲s̲s̲i̲n̲g̲ ̲o̲f̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
(ref. fig. 3.3.3-2)
The control messages coming in from CCIS must be one
of the following mentioned. They are processed as follows:
- Mesage ACK/NACK
The information about the event is forwarded to
CPIP by sending an AMOS message to CPIP with the
layout as stated in sec. 3.4.2.2.
- Open Link Agreement
The CCIS ̲STATUS in the critical region 'CONFIG'
is set to 'CCIS ̲OPEN', ref.
