DataMuseum.dk

Presents historical artifacts from the history of:

CR80 Wang WCS documentation floppies

This is an automatic "excavation" of a thematic subset of
artifacts from Datamuseum.dk's BitArchive.

See our Wiki for more about CR80 Wang WCS documentation floppies

Excavated with: AutoArchaeologist - Free & Open Source Software.


top - download

⟦53f1db3b5⟧ Wang Wps File

    Length: 8320 (0x2080)
    Types: Wang Wps File
    Notes: Spelunked
    Names: »~ORPHAN67.08«

Derivation

└─⟦21670ed14⟧ Bits:30006224 8" Wang WCS floppy, CR 0211A
    └─ ⟦this⟧ »~ORPHAN67.08« 

WangText



9…08…9…0e…9                                                       8…09……86…1
                                                           
                                                           
                                                           
                                                           
                                                           
                                                           
                                                           
                                                           
                                                           
                                                           
                                                           
                                                           
                                                           
                                                           
                                                           
                                                           
                                                           
                                                           
                                                           
                                                           
                                                           
                                                           
                                                          …02… 
                                                           
                                                           
                                                           
                                                           
                                                           …02…
                                                           
                                                          …02… 
                                                           
                                                           
                                                           
                                                          

…02…CPS/SDS/010

…02…KNB/810801…02……02…
TRAFFIC HANDLING
…02……02…CAMPS







4.2.2.4  S̲u̲b̲-̲P̲a̲c̲k̲a̲g̲e̲ ̲D̲a̲t̲a̲

         This section defines the major dataitems used during
         routing and conversion.



4.2.2.4.1    R̲o̲u̲t̲i̲n̲g̲ ̲L̲i̲s̲t̲s̲

         a)  L̲a̲y̲-̲o̲u̲t̲ ̲R̲I̲-̲L̲I̲S̲T̲

              ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲

             RI CODE      RI     NETWORK TYPE    CIRCUIT
              ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲

             Length: 14 Bytes
             Size:   Max. 250 Records
             Total:  3500 Bytes

             R̲I̲-̲C̲o̲d̲e̲ ̲(̲I̲n̲t̲e̲g̲e̲r̲)̲

             0 = Select ok
             1 = No channels open this circit
             2 = Classification mismatch RI
             3 = Too low circuit classification
             4 = Too many destinations (routes)
             5 = X-PLA

             R̲I̲ ̲(̲9̲ ̲C̲h̲a̲r̲a̲c̲t̲e̲r̲s̲)̲

             The Routing Indicator selected under selective
             Routing Procedures, assigned under preparation
             (e.g. AS) or assigned by Message Service.

             N̲e̲t̲w̲o̲r̲k̲ ̲T̲y̲p̲e̲ ̲(̲C̲h̲a̲r̲a̲c̲t̲e̲r̲)̲

             A = CCIS
             C = CAMPS Local
             S = SCARS
             T = TRC/Point-to-Point
             N = NICS TARE

             C̲i̲r̲c̲u̲i̲t̲ ̲(̲I̲n̲t̲e̲g̲e̲r̲)̲

             A code indicating the circuit-ID to which the RI
             is assigned.


         b)  L̲a̲y̲-̲O̲u̲t̲ ̲S̲e̲l̲e̲c̲t̲i̲v̲e̲ ̲R̲I̲-̲L̲i̲s̲t̲:̲

                  ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲

             4 * CLASSIFICATION  RI  NETWORK       CIRCUIT
                  ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲

             Lengh:  52 Bytes
             Size:   1 record
             Total:  52 Bytes

             C̲l̲a̲s̲s̲i̲f̲i̲c̲a̲t̲i̲o̲n̲ ̲(̲C̲h̲a̲r̲a̲c̲t̲e̲r̲)̲

             A character indicating the highest classification
             associated to the following route (RI)

             R̲I̲ ̲(̲9̲ ̲C̲h̲a̲r̲a̲c̲t̲e̲r̲s̲)̲

             The Routing Indicator available for select.

             N̲e̲t̲w̲o̲r̲k̲ ̲n̲d̲ ̲C̲i̲r̲c̲u̲i̲t̲

             As for the RI-list.

             The up to 4 RIs available for select in accordance
             with classification, will be arranged with the
             lowest first, in order to establish the logical
             sequence of processing:

             The RI selected from the selective RI-ist will
             be assigned the RI-list.

         c)  L̲a̲y̲-̲O̲u̲t̲ ̲O̲r̲i̲g̲i̲n̲a̲t̲o̲r̲ ̲R̲I̲-̲L̲i̲s̲t̲

              ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲

             RI…0e…1…0f…       RI…0e…2…0f…       RI…0e…3…0f…       RI…0e…4…0f…
              ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲

             Length: 36 Bytes

             R̲I̲…8e…1̲…8f… ̲-̲ ̲R̲I̲…8e…4̲…8f…

             The for RIs associated to the originators HQ.

             The purpose of these RIs is to select one of them
             to be used when formatting FL3.


             RI…0e…1…0f… =   NICS TARE
             RI…0e…2…0f… =   TRC/Point-to-Point
             RI…0e…3…0f… =   ?
             RI…0e…4…0f… =   ?



4.2.2.4.2    C̲o̲n̲v̲e̲r̲s̲i̲o̲n̲ ̲B̲u̲f̲f̲e̲r̲s̲

         Size:   1024 Bytes
         Buffer-1:   Message parts for conversion
         Buffer-2:   Formatted variable text
         TOTAL:      2048 Bytes

         The size of these buffers might be redefined during
         detailed design in accordance with available resources
         and performance.

         At this stagethe buffers are estimated to contain 1
         sector of data each.



4.2.2.4.3    C̲o̲n̲v̲e̲r̲s̲i̲o̲n̲ ̲L̲i̲s̲t̲s̲

         a)  L̲a̲y̲-̲O̲u̲t̲ ̲V̲I̲E̲W̲-̲L̲I̲S̲T̲

              ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲

              VIEW-REF
              ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲

             Length: 2 bytes
             Size:   15
             Total:  30 bytes

             V̲I̲E̲W̲-̲R̲E̲F̲ ̲(̲I̲n̲t̲e̲g̲e̲r̲)̲

             View Identifictions of formatted and section separated
             message views for multiple transmissions.


         b)  L̲a̲y̲-̲O̲u̲t̲ ̲C̲i̲r̲c̲u̲i̲t̲-̲L̲i̲s̲t̲

              ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲

             CIRCUIT ID   NETWORK CODE      COPIES
              ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲

             Length: 4 Bytes
             Sie:    33 records
             Total:  132 Bytes

             C̲i̲r̲c̲u̲i̲t̲ ̲I̲D̲ ̲(̲I̲n̲t̲e̲g̲e̲r̲)̲

             A number representing the queue to which the message
             shall be directed after conversion.

             -   NICS TARE circuit queue
             -   TRC/Point-to-point circuit queues
             -   SCARS circuit queue
             -   CCIScircuit queue
             -   Message Distribution queue
             -   PTP queue

             N̲e̲t̲w̲o̲r̲k̲ ̲C̲o̲d̲e̲ ̲(̲B̲y̲t̲e̲)̲

             A code indicating the network type, depending on
             which the message shall be formatted:

             A = CCIS
             C = CAMPS Local
             S = SCARS
             T = TRC/Point-to-Point
             N = NIC TARE

             C̲O̲P̲Y̲ ̲(̲H̲a̲l̲f̲ ̲I̲n̲t̲e̲g̲e̲r̲)̲

             The number of transmissions needed to include all
             RIs of FL2 using the associated View-Ref as basis.

         c)  C̲o̲n̲v̲e̲r̲s̲i̲o̲n̲ ̲C̲o̲u̲n̲t̲e̲r̲s̲

             Integers:   Number of Sections
                         Number of Routes
                         Number of Networks




4.2.2.5  I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲

         The environment of this sub-package is as depicted
         in figure 4.2.2.5-1. This figure illustrates the other
         sub-packages of THP and packages that this sub-packag
         interfaces to. The interfaces to system-oriented packages
         are described in section 3.4



4.2.2.5.1    A̲p̲p̲l̲i̲c̲a̲t̲i̲o̲n̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲

         The application sub-packages and packages that the
         ACP127-conversion sub-package interface to are:

         -   Message Distributio Package (MDP)
         -   Terminal Package (TEP)
         -   Transport Sub-package (TRS)
         -   ACP127 Analysis Sub-Package (AAS)
         -   Log Package (LOG)

















































FIGURE 4.2.2.5-1…01…INTERFACES ACP127 CONVERSION SUB-PACKAGE…86…1         …02…   …02…   …02…   …02…   …02…              
                         
4.2.2.5.1.1 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲M̲D̲P̲

         A̲C̲S̲ ̲t̲o̲ ̲M̲D̲P̲:̲

         a)  Plaindress or data messages for incoming message
             distribution (Local PLA - Format E1).



4.2.2.5.1.2 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲T̲E̲P̲

         A̲C̲S̲ ̲t̲o̲ ̲T̲E̲P̲:̲

         a)  essage service for RI-assignment.

         b)  Security and warning Reports for printout at the
             supervisor position.

         T̲E̲P̲ ̲t̲o̲ ̲A̲C̲S̲:̲

         a)  User prepared plaindress and data messages for
             RI-assignment and conversion.

         b)  Supervisor prepared ASM and service mesages for
             RI-validation and conversion. (Return Completion-code).

         c)  User prepared comments and VDU-pages in complete
             SCARS/CCIS E1-format that shall be forwarded to
             these systems. (Return status-code originator).

         d)  Re-entering from outgoing mssage service after
             RI-assignment with a notation indicating whether
             the following subfunctions have been performed:

             -   Relay assignment
             -   Punch
             -   Clear.

             (Return Completion Code)

         e)  Supervisor initiated readdressal and rerun.

             (Return ompletion Code)




4.2.2.5.1.3 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲T̲R̲S̲

         A̲C̲S̲ ̲t̲o̲ ̲T̲R̲S̲:̲

         a)  Messages for transmission to:

             -   NICS TARE
             -   TRC/Point-to-point
             -   SCARS
             -   CCIS

             The messages will be forwarded to the correspnding
             circuit-queue.

         b)  Re-routed messages for transmission and retransmission.
             The messages for retransmission shall be supplied
             with a suspected duplicate pilot (ACP127 or E1
             in accordance with format-type).

         c)  Messages to be punched at the ddicated PTP for
             off-line decryption.

         d)  A command indicating that a message of precedence
             flash has been forwarded to a circuit or PTP-queue
             will be sent to the transmission control queue
             in order to initiate preemption (not NICS TARE).

         T̲R̲S̲ ̲t̲o̲ ̲C̲S̲:̲

         a)  Messages for re-routing (any case of channel close).
             It shall be indicated whether the message had been
             partly transmitted or not (if possible).



4.2.2.5.1.4 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲A̲A̲S̲

         A̲A̲S̲ ̲t̲o̲ ̲A̲C̲S̲:̲

         a)  Complete outgoing messages for Routing and autmatic
             release before transmission.

         b)  Plaindress released messages from SCARS/CCIS for
             RI-assignment and conversion.




4.2.3    I̲n̲c̲o̲m̲i̲n̲g̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲ ̲S̲u̲b̲-̲P̲a̲c̲k̲a̲g̲e̲



4.2.3.1  F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲

         The incoming transport receives message lines from
         incoming channels via IOC, checks for reception errors
         extracts message characteristics, divides and stores
         message lines into several fields depending on the
         message type and condition (garbled characters). The
         incoming transport finally forwards the recieved message
         to the Analysis Queue. 

         There ae four types of external channels which the
         incoming transport will serve.  They are as follows:

         -   TRC, Point-to-Point
         -   NICS TARE
         -   SCARS/CCIS
         -   PTR

         For the external channel types listed above, the incoming
         transport is described in detail n the following and
         the functions which will be performed are depicted
         in figures 4.3.2-1 to 4.2.3-5. For further details
         see HIPO diagrams section 4.2.3.3.



4.2.3.1.1    I̲n̲c̲o̲m̲i̲n̲g̲ ̲T̲r̲a̲n̲s̲p̲o̲r̲t̲ ̲T̲R̲C̲,̲ ̲P̲o̲i̲n̲t̲-̲t̲o̲-̲P̲o̲i̲n̲t̲

         The main functional components contaied within the
         incoming transport, related to TRC, Point-to-Point
         connections are as follows:

         -   Initial transport
         -   Error control
         -   Message characteristics
         -   Message division

         The functions listed above are depicted in figure 4.2.3-2
         and descrbed in detail in the following.