
G&R
Two-way-simultaneous sessions do not have a ‘turn’ concept, but the DSA
session records indicate the enclosure level specified by the sender. Thus data
blocks may be delivered with enclosure ‘end of group’ indicating ‘turn’.
GCOS8 DACQ applications using interactive dialog will generally indicate
‘turn’ at the end of their output even if they are configured as two-way
simultaneous. GCOS6 command mode does not indicate 'turn'. Forcing two
way alternate (-CM TWAA) is sometimes the only way to make some
applications function correctly, and the Host Links products which have
problems with ‘turn’ will do this by default.
The handler by default asks for an ASCII session when connecting to GCOS6
and GCOS8, and an EBCDIC session for GCOS7 and IBM hosts. When an
ASCII product like Qsim uses an EBCDIC session to GCOS7 the code set is
transliterated in the line handler. The transliteration can be modified to map
ÆØÅ æøå ‘correctly’ for Scandinavian users (-SX). When G3270, G5250,
the 3270 CPI-C API or the 5250 CPI-C API use an EBCDIC session
they do their own transliteration
.
Service messages
The line handler accepts service messages for connect $*$CN, disconnect
$*$DIS, break $*$BRK (attention, and possibly purge undelivered data,
depending on configuration of the mainframe, and/or application), the two
attention signals $*$A1 (attention type 1), $*$A2 (attention type 2) and
identification query $*$ID from the communications product using the
handler. You can type them and transmit when using an emulator or
concentrator. Unknown service messages (messages beginning with $*$ but
where the 2-3 following characters are not recognized) will cause an error
message.
Interpretation of service messages within the message text can be disabled
(-DSD OFF as an emulation parameter) so that they are transmitted as data to
the mainframe. The emulators all have command keys for issuing service
messages that may be used instead of typing $*$ if interpretation is disabled.
User applications using one of our communications APIs from the GlAPI
library must send service messages themselves when the Gline API is used,
but they will be sent automatically by CMALLC, CMDEAL and CMSERR
when one of our CPI-C APIs is used.
Gline Line Handlers and Configuration
27
Commentaires sur ces manuels