|
DataMuseum.dkPresents historical artifacts from the history of: RegneCentralen RC850 |
This is an automatic "excavation" of a thematic subset of
See our Wiki for more about RegneCentralen RC850 Excavated with: AutoArchaeologist - Free & Open Source Software. |
top - metrics - download
Length: 24832 (0x6100)
Types: TextFile
Names: »D163«
└─⟦4b76feb82⟧ Bits:30008865 Diskette med tekster der formodes at være 31-D-163…174
└─⟦this⟧ »D163«
\f
i
T_A_B_L_E_ _O_F_ _C_O_N_T_E_N_T_S_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _P_A_G_E_
1. INTRODUCTION .......................................... 1
2. GENERAL INFORMATION ................................... 2
3. HOW TO USE THE X.21 DRIVER FUNCTIONS .................. 3
4. CONTROL MESSAGES ...................................... 4
4.1 CLEAR-connection ................................. 4
4.2 TERMINATE Outstanding WAIT-CALL .................. 4
5. TRANSPUT MESSAGES ..................................... 5
5.1 The Databuffer ................................... 5
5.2 Format of Line Identifications ................... 7
5.3 CALL ............................................. 8
5.4 WAIT-CALL ........................................ 9
\f
ii
\f
1_._ _ _ _ _ _ _ _ _I_N_T_R_O_D_U_C_T_I_O_N_ 1.
This paper is an addendum to the General Synchronous
Communications Driver description, chapter 22 in RC3600 Drivers
Reference Manual (RCSL No 44-RT1522).
The X.21 interface is only supported by the SMX0 to SMX7 drivers.
\f
F_ 2_._ _ _ _ _ _ _ _ _G_E_N_E_R_A_L_ _I_N_F_O_R_M_A_T_I_O_N_ 2.
The driver can run in both V.24 and X.21 mode.
When running V.24 the driver is compatible with the previous
version except for
1) conversion control message does not affect the V.24 modem
signal dataterminal ready. This signal is turned ON at the
first transput-message
2) for transput-messages bit 8-11 are not used.
bit 12 = 1 means speciel X.21-message. This means that the
RING field is only bit 13, and not bit 8-13.
When running X.21 two new transput-messages have been
implemented:
1) CALL, which is able to make an X.21-Call
2) WAIT-CALL, which is able to wait for an incomming call.
and two control-messages have been changed:
1) DISCONNECT, which clears the X.21-connection
2) TERMINATE, which is used to get an outstanding WAIT-CALL
returned without clearing if an incomming CALL had just
arrived.
When an X.21-connection is established the driver is running as
if it was V.24 except that status bit 1 and 2 (V.24-modem
signals) can not appear and bit 0 means that the X.21-connection
has been cleared.
\f
F_ 3_._ _ _ _ _ _ _ _ _H_O_W_ _T_O_ _U_S_E_ _T_H_E_ _X_._2_1_ _D_R_I_V_E_R_ _F_U_N_C_T_I_O_N_S_ 3.
If the application should be able to handle incomming calls there
should always be a wait-call message at the driver when no
X.21-connection is established. When the application wants to
make an X.21-call it sends a CALL-message to the driver, which
has one of the following results:
1) If no incomming call has arrived the WAIT-CALL message is
returned with status not processed and the driver tries to
establish the X.21-connection specified in the CALL-message
2) If an incmonning call has arrived the WAIT-CALL message is
returned with OK (connection established) and the CALL-message
is returned with status illegal.
A CALL-message and a WAIT-CALL-message can always be interrupted
with a DISCONNECT-message. The CALL/WAIT-CALL message will be
returned with OK/not processed depending on whether the
connection had just been established or not. A possible
connection will be cleared, the DISCONNECT message will be
returned with status OK.
Once a X.21-connection has been established it can always be
cleared by a DISCONNECT-message.
To get a outstanding WAIT-CALL message returned, without clearing
if a connection has just been established, use a TERMINATE
message. The WAIT-CALL is then returned with status not processed
if no connection was established otherwise status OK. The
TERMINATE message is always returned with status OK.
\f
F_ 4_._ _ _ _ _ _ _ _ _C_O_N_T_R_O_L_ _M_E_S_S_A_G_E_S_ 4.
4_._1_ _ _ _ _ _ _ _C_L_E_A_R_-_c_o_n_n_e_c_t_i_o_n_ 4.1
mess 0 control message with DISCONNECT (bit 9)
mess 1 unused
mess 2 unused
mess 3 unused
Always returned with status OK
(answ 0 = 0).
4_._2_ _ _ _ _ _ _ _T_E_R_M_I_N_A_T_E_ _O_u_t_s_t_a_n_d_i_n_g_ _W_A_I_T_-_C_A_L_L_ 4.2
mess 0 TERMINATION (bit 11)
mess 1 unused
mess 2 unused
mess 3 unused
Always returned with status OK
(answ 0 = 0).
\f
F_ 5_._ _ _ _ _ _ _ _ _T_R_A_N_S_P_U_T_ _M_E_S_S_A_G_E_S_ 5.
5_._1_ _ _ _ _ _ _ _T_h_e_ _D_a_t_a_b_u_f_f_e_r_ 5.1
The databuffer used in the WAIT-CALL/CALL message has the
following format:
Databuffer=
record
timer: string(1) from 1;
nooffac: string(1) from 2;
cpcode: string(1) from 3;
dummy: string(1) from 4;
offset: string(128) from 5;
userdata: string(128) from 133;
end;
The databuffer must start at an even byteaddress.
timer CALL-message:
Call-parameter containing time in seconds to wait in
the que if the called number is busy
WAIT-CALL-message:
Call-parameter containing time in seconds to wait
for an incomming call to arrive
255 means infinite.
noffac CALL-message:
Call-parameter containing number of facility-codes
(see also the description of userdata)
WAIT-CALL-message:
Unused
\f
cpcode CALL-message:
Return-parameter containing the received
call-progress code. 255 means no call-progress code
received. For a detailed description of
call-progress codes see the X.21 recommendation, and
documentation of the relevant network
implementation.
WAIT-CALL-message:
Unused
dummy Unused byte with the purpose to make offset and
userdata start at an even byteaddress.
offset Workarea reserved for the driver.
userdata CALL-message:
Both call- and return parameter.
Call: nooffac x 2 bytes containing facility codes
followd by the address-code.
Each facility-code consists of two characters
in ISO (IA5)
All possible codes (00-99) can be send by the
driver but at present only
61 charge information
62 called line identification
63 redirection of call
are defined
The address-code is the identification in ISO
(IA5) of the terminal to be called either
1) Abbreviated address (.00-.99)
2) Full address (see 5.2)
In both cases terminated by binary zeroes.
\f
Return: If bit 3 is set in the status the first 16
bytes contains called line identification
(B-ident) filled with binary zeroes, (see
5.2). If bit 3 is not set userdata is
undefined at return.
WAIT-CALL-message:
Returnparameter.
If bit 3 is set in the status: the first 16 bytes
contains calling line identification (A-ident) filled
with binary zeroes, (see 5.2).
If bit 4 is set in the status, byte 16 - binary zero
contains DCE provided information in the format:
/n/xxxxxxx<0>
where n defines what kind of information xxxxx is.
The driver is able to receive all kinds, but at
present only 1, 2 and 3 are defined (charging
information in three different ways).
For a detailed description of DCE-provided
information see the X.21 recommendation and
documentation of the relevant network
implementation.
5_._2_ _ _ _ _ _ _ _F_o_r_m_a_t_ _o_f_ _L_i_n_e_ _I_d_e_n_t_i_f_i_c_a_t_i_o_n_s_ 5.2
The address of the terminal to be called given in a CALL-message
and called/calling line identification returned from
CALL/WAIT-CALL message has two formats: with or without DNIC
(Data Network Identification Code) depending on whether the call
is from one country to another or inside the same country.
1) 00xxxyzzzzzzzzzz
DNIC
2) zzzzzzzzzz
\f
00 two zeroes to get out of the country
xxx country code
y network digit
zzz...zz terminal number (6-10 characters)
When receiving called calling line-identification from the
network, the ident is headed by one * if no DNIC, and two *'s if
DNIC. Those *'s are removed by the driver. If two *'s were
received, two zeroes are inserted, so the format of received
IDENTS seen from the application is the same as the IDENT which
the application gives the driver when making a CALL.
For a more detailed description of Line Identifications see the
X.21 recommendation and documentation of the relevant
network-implementation.
5_._3_ _ _ _ _ _ _ _C_A_L_L_ 5.3
mess 0 11
mess 1 bytecount
mess 2 buffer addr (even byteaddr)
mess 3 unused
Status Bits:
Bit
0 Error during CALL-sequence
(see CPCODE)
3 Called Line Identification (B-ident) is in userdata.
5 The Called Line Identification (B-ident) is not equal
to the one we have called. The connection is
established and the application must decide whether the
connection should be cleared or not.
\f
Bit
6 Illegal: Incomming Call has arrived first.
Reserved.
The driver is running V.24.
Mess 2 is not an even address.
8 Size offset/userdata too small.
Should not appear.
14 Timeout (the CALL has been waiting timer seconds in
que).
15 Not processed (the CALL message has been interrupted by
a CLEAR message).
If any status bit except 3 and 5 occurs no connection is
established otherwise the connection is established.
5_._4_ _ _ _ _ _ _ _W_A_I_T_-_C_A_L_L_ 5.4
mess 0 9
mess 1 bytecount
mess 2 buffer addr (even byteaddr)
mess 3 unused
Status Bits:
Bit
0 Error during CALL-sequence or DCE not ready after timer
seconds.
3 Calling Line Identification (A-ident) is in userdata
4 DCE provided Information is in userdata
\f
Bit
6 Illegal: Reserved.
The driver is running V.24.
Mess 2 is not an even address.
8 Size offset/userdata too small.
Should not appear.
14 Timeout. No incomming call within timer seconds.
15 Not processed (the WAIT-CALL message has been
interrupted by a CALL, TERMINATE or CELAR message).
If any status bit except 3 and 4 occurs no connection is
established otherwise an incomming call has arrived and a
connection is established.
\f
i
F_O_R_O_R_D_
Første udgave: RCSL Nr. 31-D644.
Denne manual beskriver release 3.3 af systemet. Den indeholder
både brugervejledning for betjening af skærme, installationsvej-
ledning, betjeningsvejledning, referencedokumentation og program-
dokumentation.
Carl Henrik Dreyer
A/S REGNECENTRALEN af 1979, maj 1981
Anden udgave: RCSL Nr. 31-D667.
Denne manual er en brugervejledning for betjening af tilsluttede
skærme og erstatter således første udgave på dette punkt. Den
dækker release 4.2, hvori de væsenligste nye faciliteter er:
- logon-message på skærmene
- bedre operatør-udskrifter
- statistik-opsamling
Carl Henrik Dreyer
A/S REGNECENTRALEN af 1979, november 1981
\f
ii
\f
iii
I_N_D_H_O_L_D_S_F_O_R_T_E_G_N_E_L_S_E_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _S_I_D_E_
1. INTRODUKTION ........................................... 1
2. KONTROLTASTER .......................................... 2
3. BEHANDLING AF SKÆRMBILLEDE ............................. 3
4. LOGON (OG AFBRYDELSE) .................................. 4
B_I_L_A_G_:
A. REFERENCER ............................................. 5
\f
iv
\f
1_._ _ _ _ _ _ _ _ _I_N_T_R_O_D_U_K_T_I_O_N_ 1.
Din terminal kan være tilsluttet RC8000 med forskellige front-end
systemer.
- Enten skrives ved første SEND efter at den er tændt:
V Æ L G S Y S T E M
01. ----
02. ----
03. ----
og der skal nu vælges ved at taste 01, 02 eller 03.
- Eller der skrives intet, og du er koblet direkte på "System 1".
Du kan så med en PA-tast (som regel PA2) vælge ved at der skri-
ves:
LINK1:
LINK2:
SELECT LINK:
Her vælges altså "LINK", men egentlig sker der det samme i de to
tilfælde. I et (eller flere) af de systemer/links, der kan vælges
(installations-afhængigt), vil skærmen blive tilsluttet RC8000
gennem TTY-emulator.
Formålet med dette er at få betjeningen og behandlingen af skær-
men til at ligne det, der sker på en TTY kompatibel skærm.
Det gør den også, idet f.eks. de forskellige taster (SEND - CLEAR
- PA1 osv.) får tillagt en funktion som findes på en TTY-skærm.
Der er dog n væsentlig forskel. En format-skærm kan ikke rulle
som en TTY-skærm. I stedet for at rulle vil billedet nu blive
overskrevet fra toppen, når sidste linie er brugt.
Mange applikations-systemer sørger dog selv for at "skrive for-
fra" på skærmen, og så vil billedet aldrig komme til at "rulle",
fordi sidste linie ikke fyldes.
\f
F_ 2_._ _ _ _ _ _ _ _ _K_O_N_T_R_O_L_T_A_S_T_E_R_ 2.
SEND benyttes når der er indtastet noget, som er input
(TTY: RETURN) til systemet. Hvis systemet ikke er klar til in-
put, er SEND uden funktion (og bør undgås).
PA-Tast bevirker, at a_t_t_e_n_t_i_o_n_ _d_i_a_l_o_g_ startes. Der skrives
(TTY: ESC) att på skærmen, og herefter skal der tastes et
navn på den proces der skal have en attention. Der
ventes 1 minut, og hvis intet er tastet, bruges
det navn der sidst var i brug (ved att, input,
output).
PF-Tast Skal ikke bruges. Men virker iøvrigt ligesom SEND.
CLEAR Hvis systemet er klar til input, vil der blive af-
leveret et FF tegn (til applikationen, ISO 12).
Hvis systemet ikke er klar til input, bevirker
CLEAR kun at skærmen blankes.
\f
F_ 3_._ _ _ _ _ _ _ _ _B_E_H_A_N_D_L_I_N_G_ _A_F_ _S_K_Æ_R_M_B_I_L_L_E_D_E_ 3.
Rulning En format-skærm kan ikke rulle billedet. Hvis bil-
ledet skrives fuld (ud over sidste linie), vil sy-
stemet fortsætte på øverste linie, uden at fjerne
skærmens indhold i øvrigt.
Indtastning Når systemet er k_l_a_r_ _t_i_l_ _i_n_p_u_t_, bliver der det på-
gældende sted på skærmen åbnet for input i høj
lysstyrke (der kan nu tastes på resten af linien).
Indtil der trykkes SEND, kan det tastede rettes
frit. Men når SEND trykkes, vil systemet (ofte)
forvente, at CURSEREN står lige efter det indtas-
tede, og "der regnes" kun med den text der står
til venstre for curseren.
Hvis systemet i_k_k_e_ er klar til input, kan man al-
tid trykke på PA , CLEAR som nævnt overfor.
Tryk på SEND (som da er uden funktion) bør und-
gås, da det kun giver unødig belastning af syste-
met.
\f
F_ 4_._ _ _ _ _ _ _ _ _L_O_G_O_N_ _(_O_G_ _A_F_B_R_Y_D_E_L_S_E_)_ 4.
LOGON Første gang (efter, at tty emulatoren er startet)
der fra skærmen trykkes på en kontroltast (eller,
hvis der er et menu-billede: første gang der væl-
ges det system, tty-emulatoren betjener), udskri-
ves:
kl.tt mm ss logon rc8000 terminal. velkommen
att
på skærmen og attention dialogen startes (se oven-
for). Herefter er skærmen "kendt", og selv om der
udføres LOGOFF, og man (via menu-billedet) vælger
et andet system senere, vil logon-udskriften ikke
blive gentaget (se dog nedenfor) når dette system
vælges igen.
Teksten der skrives på terminalen kan ændres af
RC8000-operatøren.
Afbrydelse Når systemet er klar til input, afventes dette i
et vist antal minutter (bestemmes af RC8000-opera-
tøren, som også har mulighed for helt at undgå
denne automatiske afbrydelse). Herefter betragtes
forbindelsen som afbrudt, og den pågældende appli-
kation "meddeles" dette. Der vil i dette tilfælde
i_k_k_e_ blive skrevet noget på skærmen, for ikke at
forstyrre en evt. dialog med et andet system. Men
når der vælges tilbage til dette system, kommer
logon-udskriften igen.
\f
F_ A_._ _ _ _ _ _ _ _ _R_E_F_E_R_E_N_C_E_R_ A.
1 RCSL No 31-D644:
RC8000 TTY Emulator til 3270 skærme
Carl Henrik Dreyer, maj 1981
2 RCSL No 31-D668:
RC8000 TTY emulator til IBM3270 kompatible skærme,
Installations- og betjeningsvejledning
Carl Henrik Dreyer, november 1981
\f
F_
\f
«eof»