- table builder services message (TBSM)
- A message issued by a table
builder module.
- TACLE
- See terminal abnormal condition line entry (TACLE).
- takeover time
- In XRF, the elapsed time between the occurrence of a failure, the completion
of switching all terminals to the alternate CICS system, and the running of
the first user transaction.
- tape volume table of contents
(TVTOC)
- Information about a tape data set that RACF stores in
the TAPEVOL profile for the volume on which the data set resides. The TVTOC
includes the data set name, data set sequence number, creation date, and an
indicator as to whether a discrete tape data set profile exists.
- target
region
- In BTS, the CICS region on which a routed process or activity
executes. See also requesting region, routing region.
- target zone
- SMP/E term for the structure and contents of a set
of target system libraries that are created during system generation and from
which CICS is run.
- task
- (1) A basic unit of work to be accomplished by
a device or a person.
- (2) In CICS, a single instance of the execution
of a transaction. See also transaction.
- task control
area (TCA)
- An area of main storage acquired by CICS when a task
is first dispatched. It is used to control the processing of the task. Once
acquired, the TCA exists until the task is terminated. It contains the current
status of the task, its relative dispatching priority, and parameters and
information being passed between CICS and the application program. During
execution of the task, the user can change the priority through task control
services; further processing of the task is scheduled accordingly.
- task control block (TCB)
- (1) A z/OS control block used to communicate
information about tasks within an address space that are connected to a z/OS
subsystem such as WebSphere MQ for z/OS or CICS.
- (2) In CICS/VSE,
a VSE control block. A TCB is created for each VSE task.
- tasking
- See multitasking.
- task-related user exit (TRUE)
- A user exit program that is associated with specified events in a particular
task, rather than with every occurrence of a particular event in CICS processing
(as is the case with global user exits). See also global user exit, resource manager interface (RMI).
- task switching
- The overlapping of I/O
operations and processing between several tasks. In WebSphere MQ for z/OS,
the task switcher optimizes performance by allowing some MQI calls to be executed
under subtasks rather than under the main CICS TCB.
- TBSM
- See table builder services message (TBSM).
- TCA
- See task control area (TCA).
- TCAM
- See Telecommunications Access Method (TCAM)
- TCB
- See task control block (TCB).
- TCP
- See Transmission Control Protocol.
- TCP/IP
- See Transmission Control Protocol/Internet Protocol (TCP/IP).
- TCT
- See terninal control table (TCT).
- TCTE
- See terminal control table terminal entry (TCTTE TCTE).
- TCTLE
- See terminal control table line entry (TCTLE).
- TCTSE
- See terminal control table system entry (TCTSE).
- TCTTE
- See terminal control table terminal entry (TCTTE TCTE).
- TCU
- See transmission control unit (TCU).
- TD
- See transient data (TD).
- TDT
- See transaction dump table (TDT).
- TEB
- See terminal error block (TEB).
- Telecommunications Access Method (TCAM)
- An access method used
to transfer data between main storage and remote or local storage.
- Teleprocessing Network Simulator (TPNS)
- A program used to test
new functions before they encounter production volumes.
- teletypewriter exchange service (TWX)
- Teletypewriter service in
which suitably arranged teletypewriter stations are provided with lines to
a central office for access to other such stations throughout the U.S. and
Canada. Both baudot-and ASCII-coded machines are used. Business machines may
also be used with certain restrictions.
- temporary storage (TS)
- The CICS facility that allows application programs to store data
in a temporary storage queue for later retrieval.
- temporary storage group identification (TSGID)
- A control block
containing entries addressing each element of a temporary storage queue. Each
temporary storage queue has at least one TSGID. Extra TSGID entries are allocated
as required. See the CICS Transaction Server System Definition Guide or the
CICS/VSE System Definition and Operations Guide for more information.
- temporary storage table (TST)
- A table describing temporary storage
queues and queue prefixes for which CICS is to provide recovery or security
or that are located on a remote CICS system.
- temporary
storage unit table (TSUT)
- A table that contains an entry for each
temporary storage identifier. Each entry addresses either a temporary storage
record in main or in auxiliary storage, or, in the case of a temporary storage
queue, the TSGID.
- TEP
- See terminal error program (TEP).
- terminal
- (1) In a system or communications network, a point at which data can either enter
or leave.
- (2) In data communication, a device, usually equipped with
a keyboard and display device, capable of sending and receiving information.
- terminal abnormal condition line entry (TACLE)
- An area containing
CICS error information and a copy of the data event control block (DECB) at
the time an error occurred on a non-VTAM terminal or line. When an abnormal
condition occurs on a non-VTAM terminal or line, terminal control places the
terminal out of service and dynamically creates a TACLE, which is chained
off the terminal control table line entry (TCTLE) for the terminal or line
on which the error occurred.
- terminal control interface
- An interface that allows an application program to send or receive
a device-dependent terminal data stream.
- terminal control
table (TCT)
- CICS control table retained to define non-VTAM terminal
networks.
- terminal control table line entry (TCTLE)
- A control block in the
TCT for all non-VTAM terminals on the same line. The TCTLE contains all parameters
necessary for processing requests for terminals on the line. For example,
there are TCTLLEs for BSAM terminals and for TCAM terminals on CICS Transaction
Server. The equivalent information for VTAM terminals is in the VTAM request
parameter list (RPL).
- terminal control table
system entry (TCTSE)
- In the TCT, an entry that is generated for
each system known to the local CICS system. Using resource definition macro
(RDM), the DFHTCT TYPE=SYSTEM macro defining a TCTSE must specify the applid
of the remote system in the NETNAME or the SYSIDNT option. Using resource
definition online (RDO), the CEDA DEFINE CONNECTION transaction defining a
remote system generates a TCTSE, and must specify the applid of the remote
system in the NETNAME option.
- terminal control table terminal entry (TCTTE TCTE)
- In the TCT,
an entry for each terminal known to CICS. TCTTEs are generated either during
system initialization (for terminals predefined by resource definition) or
when a terminal is autoinstalled. The TCTTE describes the terminal and addresses
the corresponding TCTLE (RPL for VTAM terminals), the active TCA, and TIOAs;
it also contains control information relating to terminal control requests
issued by the CICS application program.
- terminal emulation
- The capability of a microcomputer or personal computer to operate as
if it were a particular type of terminal linked to a processing unit, and
to access data.
- terminal error block (TEB)
- Control block that maintains error information associated with terminals,
for use by the CICS terminal error program.
- terminal error
program (TEP)
- A user-replaceable CICS program used to handle error
conditions that can occur when TCAM devices (in CICS Transaction Server) or
BTAM terminals (in CICS/VSE) or sequential devices are used. (Node error programs
must be used for VTAM-supported devices.) The terminal error program analyzes
the cause of the terminal or line error that has been detected by the terminal
control program. For programming information, see the Recovery and Restart
Guide.
- terminal-initiated transaction routing
- Transaction routing that
is initiated by a request to start a remote transaction arriving from a terminal.
On the basis of an installed resource definition for the transaction and possibly
on decisions made in a user-written dynamic transaction routing program, the
request is routed to the appropriate remote system. The transaction runs as
if the terminal were attached to the transaction-owning system.
- terminal input/output area (TIOA)
- Area that is set up by storage
control and chained to the terminal control table terminal entry (TCTTE) as
needed for terminal input/output operations.
- terminal list table
(TLT)
- CICS control table that allows terminal, or operator identifications,
or both, to be grouped logically. See supervisory terminal functions.
- terminal operator
- The user of an Emulator High-Level Language Application Programming
Interface (EHLLAPI) application program.
- terminal-owning
region (TOR)
- A CICS region which owns most or all of the terminals
defined locally. See also application-owning region (AOR), data-owning region (DOR).
- terminal paging
- A set of commands for retrieving pages of an oversize
output message in any order.
- termination phase
- The
XRF phase in which the XRF complex returns to two separate and independent
environments and all XRF activity in the alternate system stops.
- thread
- (1) In CICS
Transaction Server, a link between a CICS application and DBCTL. To DBCTL,
a thread represents the CICS transaction that has issued a DL/I request. The
system initialization parameter DLTHRED specifies the number of threads provided
through the CICS local DL/I interface.
- (2) A connection between a
CICS transaction and DB2.
- threading
- The process whereby various transactions
undergo concurrent execution.
- throughput rate
- The data
processing work successfully completed per unit of time.
- tie-up record
(TUR)
- In the CICS backup while open (BWO) facility, a record in
the forward recovery journal that associates a file name with a data set name.
- tight loop
- A loop in a single program, in which the same instructions
are executed repeatedly, with the result that control is never returned to
CICS.
- time-of-day clock (TOD clock)
- A z/Series hardware facility that
provides a high-resolution measure of real time suitable for the indication
of date and time of day.
- timer
- A BTS object that expires
when the system time becomes greater than a specified time, or after a specified
period has elapsed. When you define a timer, a timer event is automatically
associated with it. When the timer expires, its associated event fires.
- timer domain
- Major component of CICS that provides interval timing
and alarm clock services for CICS domains. These are processes that cause
an action to occur at some predetermined future time. This service can be
performed after a specific interval, at periodic intervals, at a specified
time of day, or at a specific time of day every day. It also provides date
and time provision and conversion facilities.
- timer event
- An atomic
event that fires when its associated timer expires. See also user-defined event.
- Time Sharing Option (TSO)
- An option of the MVS operating system
that provides interactive time sharing from remote terminals.
- TIOA
- See terminal input/output area (TIOA).
- TLT
- See terminal list table (TLT).
- TOD clock
- See time-of-day clock (TOD clock).
- token
- A value passed as a parameter for the purpose
of uniquely identifying objects.
- topology
- An inventory of CICS
and CICSPlex SM resources, and a map of their relationships. CICSPlex SM supports
the definition of resource and system topology.
- topology definition
- A named subset of CICS and CICSPlex SM resources. Topology definitions
are user-created and can include CICSplexes, CICS systems, and CICS system
groups.
- Topology Services
- A component of CICSPlex SM that is responsible
for maintaining topology information about CICSplexes and resources, and making
it available to other CICSPlex SM components.
- TOR
- See terminal-owning region (TOR).
- TPNS
- See Teleprocessing Network Simulator (TPNS).
- TP record
- See transaction program record (TP record).
- trace
- Facility for recording CICS activity. In CICS Transaction
Server, there are three destinations for trace entries: internal trace, auxiliary
trace, and the generalized trace facility (GTF). In CICS/VSE, there are two
destinations for trace entries: internal trace and auxiliary trace.
- trace domain
- Major component of CICS used by CICS system code
and user applications to record and manage trace information on CICS internal,
auxiliary, and GTF trace services.
- trace level
- A level
associated with each trace point. The level of a trace point depends on where
the trace point is and on what sort of detail it can provide on a trace call.
Most trace points are trace level 1 or 2.
- trace point
- One of several
defined places in the CICS code from which trace entries can be written to
any currently selected trace destination.
- trace utility
program (DFHTUP TUP)
- An offline trace utility program that formats
and prints the output from trace control.
- tracked terminal
- In XRF (CICS/VSE only), a terminal belonging to a class mainly comprised of
VTAM terminals that are not eligible for class 1. For these terminals, the
alternate system tracks the session, and attempts reestablishment after takeover.
The CICS Transaction Server equivalent of this is class 2 terminal.
- tracking
- In XRF, the process by which the alternate CICS system
mirrors the starting and stopping of terminal sessions in the active CICS
system so that it is prepared to take over the active system should the need
arise.
- transaction
- A unit of processing consisting of one or more application
programs, affecting one or more objects, that is initiated by a single request,
often from a terminal. See also task.
- transaction
abend code
- A four-character code, defined by CICS or the user,
that is used when abnormally terminating a transaction. CICS-defined transaction
abend codes begin with the letter 'A'. A transaction abend code is used to
indicate the cause of an error that may have occurred in CICS code or in a
user program. CICS Transaction Abend Codescontains
descriptions of the transaction abend codes defined by CICS. A transaction
abend code may be placed into a transaction dump to identify it. See transaction dump code.
- transaction backout
- The cancellation,
as a result of a transaction failure, of all updates performed by a task.
- transaction backout program
- A program (part of the emergency restart
function) that is invoked during emergency restart, and that reads backout
information (written to the restart data set by the recovery utility program)
for task, message, DL/I, and file tables.
- transaction backout
table
- In the restart data set, a summary table that contains an
entry for each task for which system log records have been copied to the restart
data set. Each entry indicates whether the task is in-flight, active, or completed.
Data in this table is available to user-written exit programs.
- transaction
deadlock
- A condition in which two or more transactions cannot
continue processing because each is waiting on a resource held by the other.
- transaction dump
- In CICS, a formatted dump for the program active
at the time the dump was requested. A transaction dump indicates where the
error occurred within the program.
- transaction dump code
- A name of up to four characters by which a transaction dump will
be known. When a transaction abend causes CICS to create a transaction dump,
the associated transaction abend code is used as the transaction dump code.
The Messages and Codes manual contains descriptions of the CICS transaction
abend codes. A transaction dump code can be defined by CICS or the user and
specifies a set of system actions held in the form of an entry in the transaction
dump table. See the Problem Determination Guide. See also dump code, transaction abend code.
- transaction dump table (TDT)
- A CICS table which may contain an entry for each transaction dump code.
See dump table.
- transaction ID
- See transaction identifier.
- transaction identifier (transaction ID)
- A unique name that is
assigned to a transaction and is used to identify the actions associated with
that transaction.
- transaction isolation
- A CICS
facility that offers storage protection between transactions, ensuring that
a program of one transaction does not accidentally overwrite the storage of
another transaction. See also storage protection. For more details, see
the Recovery and Restart Guide and the Performance Guide.
- transaction list table (XLT)
- CICS control table containing a list of transaction identifications.
Depending on a system initialization specification that can be changed during
system termination, the transactions in a particular XLT can be initiated
from terminals during the first quiesce stage of system termination. During
CICS execution the suffix of an XLT can be entered at the master terminal
- the transactions in that XLT can then be enabled or disabled as a group.
- transaction manager (XM)
- The CICS program that controls all CICS
tasks.
- transaction manager domain
- A CICS domain that provides transaction-related
services to create, terminate, purge, and inquire on tasks; and manage transaction
definitions and transaction classes. The transaction manager domain is designed
to provide greater reliability and improved function; it has minimal impact
on end users.
- transaction program record (TP record)
- TP records are part of
the user data that follows the attach FMH header in an APPC basic conversation.
These records indicate the function the signon transaction program is to perform;
for example, sign on or sign on and change password.
- transaction rate
- The number of units of processing successfully completed per
unit of time.
- transaction restart program
- In CICS/VSE, a user-replaceable CICS
program (DFHRTY) used to modify the conditions under which a transaction is
restarted by CICS after dynamic transaction backout. In CICS Transaction Server,
a user-replaceable program (DFHREST) that enables you to participate in the
decision as to whether a transaction should be restarted or not. The default
program requests restart under certain conditions; for example, in the event
of a program isolation deadlock (that is, when two tasks each wait for the
other to release a particular DL/I database segment), one of the tasks is
backed out and automatically restarted, and the other is allowed to complete
its update.
- transaction routing
- An intercommunication
facility that allows terminals or logical units connected to one CICS region
to initiate and to communicate with transactions in another CICS region within
the same processor system or in another CICS system connected by an APPC link.
- transaction security
- A call to RACF (CICS Transaction Server)
or to the CICS security program (DFHXSP) (CICS/VSE) each time a transaction
identifier is entered at a terminal to verify that the terminal user or userid
associated with that terminal is permitted to run the transaction.
- transaction-system affinity
- An affinity between a transaction
and a particular CICS region, where the transaction interrogates or changes
the properties of that CICS region. Transactions with affinity to a particular
system, rather than another transaction, are not eligible for dynamic transaction
routing. In general, they are transactions that use INQUIRE and SET commands,
or have some dependency on global user exit programs, which also have an affinity
with a particular CICS region. For more details, see Transaction Affinities Utility MVS/ESA User's Guide. See also inter-transaction affinity.
- transaction work area (TWA)
- An optional extension of the TCA,
used as a work area for a given task. The TWA can be used for the accumulation
of data and intermediate results during the execution of the task. When the
amount of working storage for a task is relatively static, the TWA may be
used if data is accessed by different programs during task processing. This
approach cannot be used for multiple transactions; the TWA is released automatically
at task termination.
- transient data (TD)
- A CICS facility that provides the ability to read and write data in
sequential queues.
- transient data control program
- The CICS program that controls sequential data files and intrapartition
transient data.
- Transmission Control Protocol (TCP)
- A communications protocol used in the Internet and in any network
that follows the Internet Engineering Task Force (IETF) standards for internetwork
protocol. TCP provides a reliable host-to-host protocol between hosts in packet-switched
communications networks and in interconnected systems of such networks. It
uses the Internet Protocol (IP) as the underlying protocol.
- Transmission Control Protocol/Internet Protocol (TCP/IP)
- A set
of communications protocols that provide peer-to-peer connectivity functions
for both local and wide area networks.
- transmission
control unit (TCU)
- A communication control unit whose operations
are controlled solely by programmed instructions from the computing system
to which the unit is attached. No program is stored or executed in the unit.
Examples are the IBM 2702 and 2703 Transmission Controls. See also communication controller.
- transparency
- Terminal attribute whereby data is not translated
between terminal and main storage representation on read or write requests.
This allows the transmission of all 256 possible byte values.
- trigger field
- In BMS, a field that is transmitted to the host processor as soon as
the terminal operator has modified the field and then tries to move the cursor
out of it. You can use display trigger fields to initiate input to an application
program. The trigger attribute is ignored if the operator has not modified
the trigger field.
- trigger level
- The number of records written
to an intrapartition transient data destination or queue that will cause CICS
to automatically initiate a task to process that queue. See also automatic transaction initiation (ATI).
- TRUE
- See task-related user exit (TRUE).
- trunking
- A function of
the VTAM class of service facility. Trunking enables explicit routes to use
parallel links between specific nodes.
- trusted middleware
class path
- The class path used in a JVM for middleware classes,
which are trusted by the JVM to manage their own state across a JVM-reset.
In CICS, it is specified by the CICS_DIRECTORY, TMPREFIX and TMSUFFIX options
in the JVM profile.
- TS
- See temporary storage (TS).
- TSGID
- See temporary storage group identification (TSGID).
- TSO
- See Time Sharing Option (TSO).
- TST
- See temporary storage table (TST).
- TSUT
- See temporary storage unit table (TSUT).
- tuning
- The
process of adjusting system control variables to make the system divide its
resources most efficiently for the workload.
- TUP
- See trace utility program (DFHTUP TUP).
- TUR
- See tie-up record (TUR).
- turnaround time
- (1) The elapsed time between entry of the first character of the first input into
the input interface and the passage of the last character of the last output
through the output interface.
- (2) The total time consumed from the
start to the completion of a specific unit of work measured at specific interfaces.
When multiple inputs and/or multiple outputs are parts of one unit of work,
intermediate turnaround time specifications may be needed.
- TVTOC
- See tape volume table of contents (TVTOC).
- TWA
- See transaction work area (TWA).
- two-phase commit
- In CICS, the protocol observed when taking a syncpoint in a distributed
UOW. At syncpoint, all updates to recoverable resources must be either committed
or backed out. At this point, the coordinating recovery manager gives each
subordinate participating in the UOW an opportunity to vote on whether its
part of the UOW is in a consistent state and can be committed. If all participants
vote "yes", the distributed UOW is committed. If any vote no, all changes
to the distributed UOW's resources are backed out. This is called the two-phase
commit protocol, because there is first a "voting" phase (the prepare phase),
which is followed by the actual commit phase. See also prepare and commit.
See also commit, in-doubt, subordinate.
- TWX
- See teletypewriter exchange service (TWX).
[[ Contents Previous Page | Next Page Index ]]