AOR—see Application-owning region
Application-owning region (AOR)
A CICS system region that owns the transaction.
asynchronous processing
Asynchronous processing within CICS is an intercommunication function that lets a transaction executing on one CICS system start a transaction on another system. The two transactions execute independently of each other. Compare with distributed transaction processing.
ATI—see Automatic Transaction Initiation
Automatic transaction initiation (ATI)
The automatic act of initiating a CICS transaction by an internally generated request. For example, issuing an EXEC CICS START command or the reaching of a transient data trigger level. A transaction can be initiated immediately, at a specified time, after a specified time interval, or, if a terminal is required, as soon as that terminal is free.
auxiliary storage
Data storage other than main storage; for example, storage on magnetic tape or direct access devices.
auxiliary trace
An optional CICS function that causes trace entries to be recorded to the auxiliary trace data set. The auxiliary trace data set is a sequential data set on disk or tape.
CICS Complex (CICSplex)
(1) A set of interconnected CICS regions acting as Resource Managers, and are combined to provide a set of coherent services for a customer's business needs. In its simplest form, a CICSplex operates within a single MVS image. Within a Parallel Sysplex environment, a CICSplex can be configured across all the MVS images in the sysplex. The CICS regions in the CICSplex are generally linked through the CICS inter-region communication (IRC) facility, using either the XM or IRC access method (between regions in the same MVS image), or the XCF/MRO access method (between regions in different MVS images). (2) The largest set of CICS regions or systems to be manipulated by a single CICSPlex SM entity.
CICSplex—see CICS Complex
CICSPlex SM—see CICSPlex System Manager
CICSPlex System Manager (CICSPlex SM)
A system-management product that provides a single-system image and a single point of control for one or more CICSplexes.
CICS region userid
A userid assigned to a CICS region at CICS initialization. It is specified either in the RACF started procedures table when CICS is started as a started task, or on the USER parameter of the JOB statement when CICS is started as a job.
CICS-attachment facility
Part of the CICS product that provides a multithread connection to DB2 to let applications running under CICS execute DB2 commands.
CKTI
An MQSeries supplied CICS transaction that monitors an MQSeries initiator queue. CKTI starts a CICS transaction when an MQ event occurs on that queue.
COMMAREA—see Communication Area
Communication area (COMMAREA)
A CICS storage area used to pass data between tasks that communicate with a given terminal. The area can also be used to pass data between programs within a task.
connection
Defines a remote system with which your CICS system communicates using either intersystem communication or multi-region operation (MRO).
DOR—see Data-Owning Region
Data-Owning Region (DOR)
A CICS system region that owns the data files or databases. DORs are similar to file-owning region.
Distributed Program Link (DPL)
A programming mechanism that lets a CICS client program call a server program running in a remote CICS region, and pass and receive data using a COMMAREA.
Distributed Transaction Processing
A type of intercommunication in CICS, in which the processing is distributed between transactions that communicate synchronously with one another over intersystem or inter-region links.
DPL—see Distributed Program Link
DTP—see Distributed Transaction Processing
EDF—see Execution Diagnostic Facility
EIB—see EXEC Interface Block
EXEC
A keyword used in CICS command language. All CICS commands begin with the keywords EXEC CICS.
EXEC Interface block (EIB)
A control block associated with each task in a CICS command-level environment. The EIB contains information that is useful during the execution of an application program (such as the transaction identifiers) and information that is helpful when a dump is being used to debug a program.
Execution Diagnostic Facility
A CICS facility used for testing application programs interactively online, without making modifications to the source program or to the program preparation procedure. The facility intercepts execution of the program at various points and displays information about the program at these points. Also displayed are any screens sent by the user program, so that the programmer can converse with the application program during testing just as a user would do on the production system. There are two CICS-supplied transactions used to invoke this facility depending on application type: (1) CEDF is used for applications executing at a terminal, (2) CEDX is used for non-terminal tasks.
ECI—see External Call Interface
External Call Interface (ECI)
An API that lets a non-CICS program running on a CICS client call a CICS program located on a CICS server, and pass and retrieve data from it.
function shipping
A process, transparent to the application program, by which CICS accesses resources when those resources are actually held on another CICS system.
FOR—see File-Owning Region
File-owning region (FOR)
A CICS address space whose primary purpose is to manage files and databases. FOR is similar to data-owning region (DOR).
intercommunication facilities
A generic CICS term covering inter-system communication and multi-region operation.
Inter-Region Communication (IRC)
The method by which CICS implements multi-region operation.
Inter-System Communication (ISC)
A term that describes communication between separate systems using SNA networking facilities or using the application-to-application facilities of VTAM.
interval control
The CICS processing activity that provides time-dependent facilities.
IRC—see Inter-Region Communication
ISC—see Inter-System Communication
link
(1) A logical connection between two systems or applications. (2) A link is a programmatic request within one program to invoke another program. Upon completion of the invoked program, control returns to the invoking program at the point at which the link was executed.
mirror task
A task required to service incoming requests that specify one of the CICS mirror transactions (CSMI, CSM1, CSM2, CSM3, CSM5, CPMI, CVMI).
mirror transaction
A transaction initiated in CICS in response to a "function shipping" request from another CICS system. The mirror transaction recreates the original request and the request is issued. The mirror transaction returns the acquired data to the originating CICS system.
MRO—see Multi-Region Operation
MSGUSER
One of the DDNAMEs by CICS as a destination for log data.
multiprogramming
The concurrent execution of application programs across partitions.
Multi-Region Operation (MRO)
A way to communicate between CICS systems without the use of SNA networking facilities. The systems must be in the same operating system; or, if the XCF access method is used, in the same MVS sysplex.
Parallel Sysplex
An MVS Sysplex where all the MVS images are linked through a coupling facility.
principal facility
To a transaction, the principal facility is the session that activates it.
pseudoconversational
A type of CICS transaction that is designed to appear to the operator as a continuous conversation occurring as part of a single transaction.
quasi-reentrant
A characteristic of a CICS application that applies to programs that are serially reusable between entry and exit points because it does not modify itself or store data within itself between calls on CICS facilities.
queue
A collection of items formed by items in a system waiting for service; for example, tasks to be performed or messages to be transmitted in a message-switching system.
resource
Any facility of the computing system or operating system required by a job or task, and including main storage, input/output devices, the processing unit, data sets, and control or processing programs.
SDT—see Shared Data Table
Shared Data Table (SDT)
A copy of a data set that CICS loads into a MVS data space and is accessed by data table services like cross-memory instead of VSAM services.
start code
A 2-byte indicator showing how the transaction issuing the request was started. It can have a number of values, as described in the following table:
|
D |
A distributed program link (DPL) request that did not specify the SYNCONRETURN option. The task cannot issue I/O requests against its principal facility, nor can it issue any syncpoint requests. |
|
DS |
A distributed program link (DPL) request that did specify the SYNCONRETURN option. The task can issue syncpoint requests. |
|
S |
START command without data. |
|
SD |
START command with data. |
|
TD |
Terminal input or permanent transid. |
SIT—see System Initialization Table
System initialization table (SIT)
A CICS table of user-specified data that controls how CICS is initialized.
session
A logical link between two CICS systems that communicate using intersystem communication or MRO. In CICS intersystem communication, a session makes use of an SNA LU-LU session.
taskid
An identifier (number) given by CICS to a task.
task
The dispatching unit of execution in CICS corresponding to an invocation of a transaction for a particular user.
TCT—see Terminal Control Table
TCTTE—see Terminal Control Table Terminal Entry.
Temporary Storage (TS)
A CICS facility use to temporarily save data in the form of a sequential queue. A TS queue is held in main storage or on a VSAM data set on DASD. All queues not in main storage are in a single VSAM data set. A task can create a TS queue with a name selected by the task. The queue exists until deleted by a task (usually, but not necessarily, the task that created it).
Temporary Storage Queue (TSQ)
A storage are for data that is managed by CICS.
Temporary Storage Queue Owning Region (TSQOR)
A CICS region that owns and manages access to temporary storage queues. See TSQ.
Temporary Storage Table (TST)
An in storage table describing temporary-storage queues and queue prefixes for which CICS is to provide recovery.
terminal
In CICS, a device equipped with a keyboard and some kind of display, capable of sending and receiving information over a communication channel.
Terminal Control Table (TCT)
A table describing a configuration of terminals, logical units, or other CICS systems in a CICS network with which the CICS system can communicate.
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 auto installed. 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-owning region (TOR)
The CICS system region that owns the terminals.
TOR - see Terminal-Owning Region
transaction
A unit of processing (consisting of one or more programs) initiated by a single request, often from a terminal. A transaction can require the initiation of one or more tasks for its execution.
transaction routing
A type of CICS intercommunication in which users of a CICS system can execute transactions that exits in a CICS system other than the one in the user's terminal is connected.
transaction backout
The system activity that occurs because of a transaction failure. Updates to resources associated with the transaction are backed out.
transaction identifier
A synonym for transaction name or transaction code. For example, a transaction identifier is a one to four character code entered by an operator when selecting a transaction.
TS—see Temporary Storage
TST—see Temporary Storage Table
Two-Phase Commit
When a transaction is operating as part of a distributed Unit-of-Work (UOW), two-phase commit is the protocol used to coordinate and execute a syncpoint. At syncpoint, all updates to recoverable resources must either be 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. This can be summarized as follows:
Coordinator invokes each UOW participant, asking each one if it is prepared to commit.
If all UOW participants acknowledge that they are prepared to commit (vote yes), the coordinator issues the commit request.
If any UOW participant is not prepared to commit (votes no), the coordinator issues a backout request to all.
trace
A facility for recording CICS activity. There are three destinations for trace entries: internal trace, auxiliary trace, and externally to the Generalized Trace Facility (GTF).
Transaction Work Area (TWA)
An option specified on the ADDRESS command. The TWA is an in memory storage area used to pass information between application programs, but only if they are in the same task. The pointer reference is set to the address of the TWA. If a TWA does not exist, the pointer reference is set to X'FF000000'.
TSQ—see Temporary Storage Queue
TSQOR—see Temporary Storage Queue Owning Region
A CICS region that owns temporary storage queues.
TWA—see Transaction work area
User-Maintained Shared Data Table
An MVS data table whose records are not automatically reflected in the source data set.
Unit of Work (UOW)
The processing activities associated with a sequence of processing actions (database changes, for example) that must be completed before any of the individual actions performed by a transaction can be regarded as committed. After changes are committed (by successful completion of the UOW and recording of the syncpoint on the system log) they become durable, and are not backed out in the event of a subsequent failure of the task or system.
The beginning and end of the sequence can be marked by the following activities:
Thus a UOW is completed when a transaction takes a syncpoint, which occurs either when a transaction issues an explicit syncpoint request, or when CICS takes an implicit syncpoint at the end of the transaction. In the absence of user syncpoints explicitly taken within the transaction, the entire transaction is one UOW.
Unit of Work Identifier (UOW ID)
A unique identifier as known within the originating system. On MVS, a UOW ID can be assigned explicitly using an API call or is automatically assigned by the target system (CICS, WebSphere, and so on). It is a binary value derived from the originating system clock or a character value (hhmmss).
UOW—see Unit Of Work
UOW id—see Unit Of Work Identifier
user authentication
The process by which a service accurately establishes the authenticity of a user making a request.
user identification
The process by which the identity of a user is established. Typically, the term user ID is used to denote the user's identity. In Java terminology the term principal is used.
|
Copyright © 2014 CA.
All rights reserved.
|
|