LU 6.2 API Application Programmer's Reference Guide (30294-90008)

216
conversation with confirm: A
conversation established in such
a way that confirmation requests
and responses can be sent and
received.
conversation without
confirm: A conversation
established in such a way that
confirmation requests and
responses cannot be sent or
received.
Customer Information
Control System (CICS): An
IBM application subsystem that
provides file handling and data
communications services for
application programs.
D
Deallocate state: The
conversation state from which a
TP can deallocate the mapped
conversation locally.
dependent LU: An LU capable
of conducting only one LU-LU
session at a time. A dependent
LU always functions as a
secondary LU and cannot send a
BIND to initiate an LU-LU
session; to request a session, it
must send an INIT_SELF to the
host and wait for the host to send
the BIND. See independent
LU.
E
end user: The ultimate
destination of data in a
communicationsnetwork. Anend
user can be a human user, a
peripheral device (like a printer
or a terminal), or an application
program.
G
Generalized Data Stream
(GDS): The name of the LU 6.2
data stream. LU 6.2 data packets
must include GDS headers (see
GDS header).
GDS header A portion of an LU
6.2 data packet that contains
information about the kind of
data being sent or received.
I
independent LU: An LU
capable of conducting multiple,
simultaneous (parallel) APPC
sessions with another
independent LU on a remote
system. An independent LU can
function as either a primary or
secondary LU. See dependent
LU.
intrinsic: A subprogram
provided by Hewlett-Packard to
perform common functions such
as opening files, opening
communicationslines,performing
subsystem-defined functions, or
transmitting data over a
communications line.
L
local TP: The TP running on the
local processor.