top - download
⟦6db57a27a⟧ Wang Wps File
Length: 3335 (0xd07)
Types: Wang Wps File
Notes: Spelunked
Names: »~ORPHAN41.12«
Derivation
└─⟦b3c9a9699⟧ Bits:30006142 8" Wang WCS floppy, CR 0015A
└─ ⟦this⟧ »~ORPHAN41.12«
WangText
1.3.6, sec. 8.1.4.6. The 'Open Agreement' - timeout timer is dismantled, ref. 3.3.3.1.
+ 3.3.3.5. An AMOS signal shall be sent to CPIP (to start outgoing narrative message
processing). Finally ACK upon the control message is returned to CCIS.
- Oen Link Rejection
The FIKS Supervisor is notified by the use of 'SEND REPORT' with the text 'CCIS
OPEN NOT OK'. 'Open Agreement'- timer is dismantled and ACK is returned just as
in the preceding section.
- Close Link
The CCIS ̲STATUS in 'CONFI' is set to 'CCIS CLOSED'. This change in CCIS ̲STATUS is
reported by use of 'SEND ̲REPORT' with text 'CCIS CLOSE OK' and checkpointed in the
same way as at 'Open Link Agreement'. ACK is returned to CCIS.
- All other received control messages will e ignored.…86…1 …02… …02… …02… …02… …02…
FIGURE 3.3.3-2
PROCESS CONTROL MESSAGE FLOW
3.3.3.4 P̲r̲o̲c̲e̲s̲s̲i̲n̲g̲ ̲o̲f̲ ̲N̲a̲r̲r̲a̲t̲i̲v̲e̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
ref. fig. 3.3.3-3
The narrative messages coming in from CCIS is checked
to fulfil the FIKS-SMF message layout as stated in
ref. 1.3.6, sc. 10.1 (or at least for errors in the
layout, that could cause a "catastrophie" in the FIKS-
Network).
The checking involves:
- Total length of the message must be less than 9000
bytes. This is performed both by checking 'Message
Length' in th binary header (ref. 1.3.6, sec. 10.1.1,8)
and the length of the PDB-files, that contains
the message. (MON(IO,GETFILEINFORMATION), ref.
1.3.11).
- Action and Info precedence must be correct. I.e.
the corresponding items in the binary header mustbe
less than 7 and greater than 0.
- The classification of the message must not be greater
than, that of the CCIS-terminal, defined in the
terminal control block (TCB), ref. sec. 3.1.1.4
+ ref. 1.3.6, sec. 7.2. The message classification
is obtaied from the binary header.
- Address List Offset, Signal Header Length, MSG-ID
reference and SIC- reference in the binary header
must be probable, i.e. less than total message
length.
- The message must not be of special handling type.
I.e. theSpecat. code in the binary header shall
be 0.
If one of these checks fails, a NACK is returned to
CCIS and the resources concerning the message is released
(further processing stopped). The FIKS system is notified
of the event via a 'LOCAL ̲FIX ̲UP-error report with
error code equal #2222, ref. sec. 3.3.4.
If checking is ok, then the message is released to
the FIKS Network. I.e.:
- The MTCB - referring to the message is filled out
just as if the message was going to be released
after an rdinary message preparation performed
at a FIKS MEDE. ref. 1.3.6, sec. 7.1.1.1, case
2.
- Checkpoint of the becoming enqueing to the MDS-process
is performed. ref. 1.3.6, 8.1.4.1
- The event of receiveing a message from CCIS is
logged by using the Message Journal Log monitor
(ref. 1.3.21) with event code 'MESSAGE RELEASED'.
- As the CCIS in the FIKS Systm is regarded as a
FIKS Terminal, then also statistics concerning
'messages released' has to be updated to maintain
consistency in the system. In the critical region
'STATIC' the items: NO ̲OF ̲MESSAGES, NO ̲OF ̲ANOS,
NO ̲OF ̲CHARACTERS for the proper pr
