top - download
⟦6535e5a4b⟧ Wang Wps File
Length: 11590 (0x2d46)
Types: Wang Wps File
Notes: CPS/SDS/006
Names: »1078A «
Derivation
└─⟦53e9d9273⟧ Bits:30006039 8" Wang WCS floppy, CR 0063A
└─ ⟦this⟧ »1078A «
WangText
9…05…9…06…9…07…8…08…8…09…8…0a…8…0b…8…0c…8…0e…8…86…1
…02…
…02…
…02…
…02…CPS/SDS/006
…02…HKI/810801…02……02…
I/O
CONTROL
…02……02…CAMPS
4.2.2.3.3 L̲o̲w̲ ̲S̲p̲e̲e̲d̲ ̲L̲i̲n̲e̲ ̲H̲a̲n̲d̲l̲e̲r̲ ̲F̲l̲o̲w̲
The Low Speed Line Handler transfers data from/to the
application to/from the LTUX.
The environment for the Low Speed Line Handler is shown
in figure 4.2.2.3.3-1 and the data transfer mechanism
in figure 4.2.2.3.3-2.
For low speed lines the data transfer is of a different
nature from VDU and OCR. The input or output data streams
are to be seen on a contiguous string of records.
Output streams may be interrupted when no output request
is pending.
Input streams are interrupted by the LTUX on 4 conditions.
1) Control character sequence other than CR, CR, LF,
or CR, LF appears.
2) Printable characters appear after (1).
3) A time interval of more than N seconds between
two characters received.
4) Error condition, i.e. parity error or V24 status
line change occurred.
The Low Speed Line Handler may be configured for input/output
or for output only. In the latter case the input buffer
is not available (length zero).
In the following the abbreviation LSL is used for low
speed line.
Figure 4.2.2.3.3-1 to -2
LSL HANDLER REQUEST ENTRY (3.1)
CHANNEL COMMAND
S̲U̲B̲D̲E̲V̲I̲C̲E̲ ̲C̲O̲M̲M̲A̲N̲D̲ ̲(̲3̲.̲1̲.̲1̲)̲ C̲H̲A̲N̲N̲E̲L̲ ̲C̲O̲M̲M̲A̲N̲D̲ ̲(̲3̲.̲1̲.̲2̲)̲
P̲E̲N̲D̲I̲N̲G̲ ̲R̲E̲Q̲U̲E̲S̲T̲ ̲H̲A̲N̲D̲L̲I̲N̲G̲ ̲(̲3̲.̲3̲)̲
SUBDEVICE COMMAND (3.1.1)
SUBDEVICE NOT CREATED PUT ERROR
DELETE D̲E̲L̲E̲T̲E̲ ̲S̲U̲B̲D̲E̲V̲I̲C̲E̲ ̲(̲3̲.̲1̲.̲1̲.̲1̲)̲
CONTROL C̲O̲N̲T̲R̲O̲L̲ ̲S̲U̲B̲D̲E̲V̲I̲C̲E̲ ̲(̲3̲.̲1̲.̲1̲.̲2̲)̲
INPUT R̲E̲Q̲U̲E̲S̲T̲ ̲I̲N̲P̲U̲T̲ ̲(̲3̲.̲1̲.̲1̲.̲3̲)̲
ACK INPUT A̲C̲K̲ ̲I̲N̲P̲U̲T̲ ̲(̲3̲.̲1̲.̲1̲.̲4̲)̲
OUTPUT R̲E̲Q̲U̲E̲S̲T̲ ̲O̲U̲T̲P̲U̲T̲ ̲(̲3̲.̲1̲.̲1̲.̲5̲)̲
INIT OUTPUT I̲N̲I̲T̲ ̲O̲U̲T̲P̲U̲T̲ ̲(̲3̲.̲1̲.̲1̲.̲6̲)̲
CANCEL C̲A̲N̲C̲E̲L̲ ̲(̲3̲.̲1̲.̲1̲.̲7̲)̲
OTHER PUT ERROR
DELETE SUBDEVICE (3.1.1.1)
SET SUBDEVICE NOT CREATED
ANSWER PENDING REQUESTS
MARK ONGOING REQUESTS DUMMY
CONTROL SUBDEVICE (3.1.1.2)
REQUEST INPUT (3.1.1.3)
2 PENDING REQUESTS PUT "TOO MANY REQUESTS"
ONE PENDING REQUEST PUT PENDING AND "REQUEST
QUEUED"
PUT PENDING
DATA NOT AVAILABLE
I̲N̲P̲U̲T̲ ̲E̲N̲D̲ ̲(̲3̲.̲4̲)̲
ACK INPUT (3.1.1.4)
ISSUE TDX READ
REQUEST OUTPUT (3.1.1.5)
2 REQUESTS PENDING PUT "TOO MANY REQUESTS"
ONE REQUEST PENDING PUT PENDING AND "QUEUED"
RETURN BUFFER
INIT OUTPUT (3.1.1.6)
INIT TDX WRITE
CANCEL (3.1.1.7)
OPERATION NOT PENDING RETURN ERROR
OPERATION NOT ACTIVE RETURN CC
OUTPUT OPERATION
PUT DUMMY ISSUE CANCEL
TO LTUX
CHANNEL COMMAND (3.1.2)
INITIALIZE I̲N̲I̲T̲I̲A̲L̲I̲Z̲E̲ ̲(̲3̲.̲1̲.̲2̲.̲1̲)̲
CREATE SUBDEVICE C̲R̲E̲A̲T̲E̲ ̲S̲U̲B̲D̲E̲V̲I̲C̲E̲ ̲(̲3̲.̲1̲.̲2̲.̲2̲)̲
OPEN O̲P̲E̲N̲ ̲(̲3̲.̲1̲.̲2̲.̲3̲)̲
REQ. CONTROL R̲E̲Q̲.̲ ̲C̲O̲N̲T̲R̲O̲L̲ ̲(̲3̲.̲1̲.̲2̲.̲4̲)̲
INIT CONTROL I̲N̲I̲T̲ ̲C̲O̲N̲T̲R̲O̲L̲ ̲(̲3̲.̲1̲.̲2̲.̲5̲)̲
GET CONTROL RESPONSE C̲O̲N̲T̲R̲O̲L̲ ̲R̲E̲S̲P̲O̲N̲S̲E̲ ̲(̲3̲.̲1̲.̲2̲.̲6̲)̲
ACK CONTROL A̲C̲K̲ ̲C̲O̲N̲T̲R̲O̲L̲ ̲(̲3̲.̲1̲.̲2̲.̲7̲)̲
CLOSE C̲L̲O̲S̲E̲ ̲(̲3̲.̲1̲.̲2̲.̲8̲)̲
INITIALIZE (3.1.2.1)
BUILD MEMORY FOR ONE SUBDEVICE AND
WITH SPECIFIED INPUT BUFFER CAPACITY
CREATE SUBDEVICE (3.1.2.2)
ALREADY CREATED PUT ERROR
SET CREATED
OPEN (3.1.2.3)
ISSUE OPEN TO LTUX
INIT READ TDX CONTROL
INIT READ TDX DATA
PUT PENDING
REQ. CONTROL (3.1.2.4)
CONTROL ALREADY PENDING RETURN ERROR
RETURN BUFFER
INIT CONTROL (3.1.2.5)
NOT LTUX CONTROL RETURN ERROR
ISSUE COMMAND OUTPUT
CONTROL RESPONSE (3.1.2.6)
COMMAND ANSWER RECEIVED
RETURN BUFFER
PUT RESPONSE PENDING
ACK CONTROL (3.1.2.7)
SET NOT PENDING
CLOSE (3.1.2.8)
RETURN PENDING TRANSFERS
ISSUE CLOSE TO LTUX
TDX RESPONSE RECEIVED ENTRY (3.2)
CONTROL IN C̲O̲N̲T̲R̲O̲L̲ ̲R̲E̲S̲P̲O̲N̲S̲E̲ ̲I̲N̲ ̲(̲3̲.̲2̲.̲1̲)̲
CONTROL OUT C̲O̲N̲T̲R̲O̲L̲ ̲R̲E̲S̲P̲O̲N̲S̲E̲ ̲O̲U̲T̲
̲(̲3̲.̲2̲.̲2̲)̲
DATA IN D̲A̲T̲A̲ ̲R̲E̲S̲P̲O̲N̲S̲E̲ ̲I̲N̲ ̲(̲3̲.̲2̲.̲3̲)̲
DATA OUT D̲A̲T̲A̲ ̲R̲E̲S̲P̲O̲N̲S̲E̲ ̲O̲U̲T̲ ̲(̲3̲.̲2̲.̲4̲)̲
CONTROL RESPONSE IN (3.2.1)
COMMAND ANSWER C̲O̲M̲M̲A̲N̲D̲ ̲A̲N̲S̲W̲E̲R̲ ̲(̲3̲.̲2̲.̲1̲.̲1̲)̲
(ASYNCHRONOUS REPORT)
R̲E̲P̲O̲R̲T̲ ̲R̲E̲S̲P̲O̲N̲S̲E̲ ̲(̲3̲.̲2̲.̲1̲.̲2̲)̲
REISSUE CONTROL READ
COMMAND ANSWER (3.2.1.1)
OPEN? SET OPEN GENERATE RESPONSE
LTUX COMMAND STATISTICS? GENERATE RESPONSE
CLOSE? RETURN ANSWER
REPORT RESPONSE (3.2.1.2)
LTUX ERROR OR V24 ERROR
CLOSE
PARITY
(KEY ON/OFF MSTP)
SEND ASYNCHRONEOUS REPORT
CONTROL RESPONSE OUT (3.2.2)
DATA RESPONSE IN (3.2.3)
NO PENDING INPUT
I̲N̲P̲U̲T̲ ̲E̲N̲D̲ ̲(̲3̲.̲4̲)̲
DATA RESPONSE OUT (3.2.4)
PUT NOT PENDING
LAST TRANSFER FOR THIS
APPL. REQUEST
RETURN COMPLETION
PENDING REQUEST HANDLING (3.3)
ONGOING OUTPUT
PENDING OUTPUT INITIATE
ONGOING INPUT?
PENDING INPUT? INITIATE
INPUT END (3.4)
APPLICATION BUFFER
NOT FILLED
SELECT SET OF COMPLETE TEST FOR END
RECORDS AND SET COMPLETION OF SEQUENCE
TERMINATION
SET
TERM CODE
INPUT REQUEST
RETURN BUFFER RETURN BUFFER
ASYNCHRONOUSLY
4.2.2.4 S̲u̲b̲-̲P̲a̲c̲k̲a̲g̲e̲ ̲D̲a̲t̲a̲
4.2.2.4.1 V̲D̲U̲ ̲H̲a̲n̲d̲l̲e̲r̲ ̲D̲a̲t̲a̲
The VDU Handler data consist of one pending transfer
control block (PTCB) per possible queued transfer plus
a buffer for data transfer and a buffer for control
input.
Terminal 0,2,.....2N has PTCB for INPUT.
Terminal 1,3.......2N+1 has PTCB for OUPUT and INPUT/OUTPUT.
The buffer for data transfer consists of two parts.
The first part is used for output only where it is
located with split selection sequences. The second
part is used for input and output.
The buffer for control input is used to receive asynchronous
reports and command responses. Figure 4.2.2.4.1-1 and
-2 show the data area.
Figure 4.2.2.4.1-1 - 2
4.2.2.4.2 O̲C̲R̲ ̲H̲a̲n̲d̲l̲e̲r̲ ̲D̲a̲t̲a̲
The OCR Handler data consist of 2 pending transfer
control blocks (PTCB for input requests).
1 PTCB for Channel Control
One buffer for data input.
One buffer for control output/input
Figure 4.2.2.4.2-1 presents the OCR Handler Data.
Figure 4.2.2.4.2-1
4.2.2.4.3 L̲S̲L̲ ̲H̲a̲n̲d̲l̲e̲r̲ ̲D̲a̲t̲a̲
The LSL Handler data consist of 4 pending transfer
control blocks (PTCBs) 2 for output and 2 for input.
1 PTCB for Channel Control.
One buffer for data output.
One buffer for data input (may be omitted)
One buffer for control output
One buffer for control input
Figure 4.2.2.4.3-1 presents the LSL Handler data.
Figure 4.2.2.4.3-1
4.2.2.5 S̲u̲b̲-̲P̲a̲c̲k̲a̲g̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
4.2.2.5.1 V̲D̲U̲ ̲H̲a̲n̲d̲l̲e̲r̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
The VDU Handler interfaces to the FORMAT HANDLER, The
Creator, and to the LTUX FUNCTIONS Sub-Package.
The FORMAT HANDLER interface for one VDU split is shown
in figure 4.2.2.5.1-1.
The records transferred are of type (refer section
4.1.6.2.2).
0,1 and 4 for data type terminal
4 for control type terminal.
The Creator interface is described in section 4.1.6.2.1.
The LTUX interface for one LTUX channel is shown in
figure 4.2.2.5.1-2.
The data transferred from the VDU Handler to the LTUX
have the format shown in figure 4.2.2.5.1-3.
The record type definitions are as of section 4.1.6.2.2
with two additions:
Record type "Start of Sequence" (8) specifies to the
LTUX that a transfer starts and record type "End of
Sequence" (9) specifies end of a transfer.
For each transfer the LTUX returns an acknowledge with
the sequence number.
The data transferred from the LTUX to the VDU handler
is shown in figure 4.2.2.5.1-4.
The "End of Sequence" record contains a completion
code giving the reason for termination.
- Normal Termination (ETX from VDU)
- Checksum error
- Interruption due to V24 status change
- Parity error
The commands and responses to/from the LTUX are:
1) OPEN
Defines the VDU including baud rate
Set-up V24.
2) CLOSE
Remove V24
3) CANCEL
Dummy command for VDU
4) REQUEST STATISTICS
Number or incoming characters
Number of outgoing characters
both since last request
5) In addition the following asynchronous reports:
Parity error
Checksum error
V24 status change
LTUX error
Key on/off
Function key.
Figure 4.2.2.5.1-1 to -4
4.2.2.5.2 O̲C̲R̲ ̲H̲a̲n̲d̲l̲e̲r̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
The OCR Handler interface to the application and to
the creator is presented in section 4.1.6.2.
The LTUX data interface for one LTUX channel is shown
in figure 4.2.2.5.2-1.
The data transferred is depicted in figure 4.2.2.5.2-2.
Commands to the LTUX are (with response)
1) OPEN
Define OCR including baudrate set up V24.
2) CLOSE
Remove V24
3) CANCEL
Dummy for OCR LTUX
4) REQUEST STATISTICS
Number of incoming characters
Number of outgoing characters
5) Following async. reports
Parity error
V24 status error
LTUX error
Figure 4.2.2.5.2-1 to -2
4.2.2.5.3 L̲S̲L̲ ̲H̲a̲n̲d̲l̲e̲r̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
The Low Speed Line Handler interfaces to the application
and the creator. The interfaces are presented in section
4.1.6.2.
The LTUX data interface for one LTUX channel is shown
in figure 4.2.2.5.3-1.
Commands with responses
OPEN
CLOSE
CANCEL
REQUEST STATISTICS
Async. Reports
Parity error
V24 status change
LTUX error
MSTP or PTP/PTR key on/off
Figure 4.2.2.5.3-1 to -2
