C

C/370
A programming language designed for a wide range of system and commercial applications.
CA
See control area (CA).
cache structure
A coupling facility structure that stores data that can be available to all members of a Parallel Sysplex.
call
An instruction in COBOL, assembler language, C/370, or PL/I format that is used by an application program to request DL/I services.
CALL interface
A part of the external CICS interface (EXCI). The CALL interface consists of six commands that allow you to allocate and open sessions to a CICS system from non-CICS programs running under MVS/ESA; issue DPL requests on these sessions from the non-CICS programs; and close and deallocate the sessions on completion of the DPL requests. For more details, see EXCI CALL interface commands.
canned map
A technique to achieve simulated windows using BMS. See also base map.
capacity planning
(1) An analysis of processor loading and processor capacity, extending into real storage, other resources (channels, DASD, lines), and timings and response where necessary.
(2) A method of translating growth in user demands into requirements for future computing resources. It projects future workload by taking into account the increase in existing applications and the introduction of new applications, thus allowing a prediction of performance, and helping in the evaluation of future configurations.
card reader/line printer
In CICS terminal control, a pair of input and output sequential data sets that simulate a card reader and line printer. See discussion of sequential (BSAM) devices in the CICS Transaction Server System Definition Guide or the CICS/VSE System Definition and Operations Guide.
CART
See command and response token (CART).
CAS
See coordinating address space (CAS).
CA splitting
In VSAM, to double a control area dynamically and distribute its CIs evenly when the specified minimum of free space is used up by more data.
cataloged procedure
In ESA and VSE, a set of job control statements (JCL) that has been placed in a library and can be retrieved by name. In ESA, a cataloged procedure can be executed by an ESA START command or by an EXEC statement in JCL. In VSE, a cataloged procedure can be executed by an EXEC statement in JCL.
catch-up
In XRF, a process in which the active CICS system uses CAVM message services to send a stream of messages describing the current state of all its VTAM terminals, to the message data set and thence to the alternate CICS system.
category
The recommended security specifications needed for both the CICS transaction definitions and the corresponding RACF profiles.
category 1 transaction
A set of CICS transactions categorized according to the level of security checking required for them. Transactions in this category are never associated with a terminal: that is, they are for CICS internal use only and should not be invoked from a user terminal. For this reason, CICS does not perform any security checks when it initiates transactions in this category for its own use.
category 2 transaction
A set of CICS transactions categorized according to the level of security checking required for them. Transactions in this category are either initiated by the terminal user or are associated with a terminal. You should restrict authorization to initiate these transactions to userids belonging to specific RACF groups.
category 3 transaction
A set of CICS transactions categorized according to the level of security checking required for them. Transactions in this category are either invoked by the terminal user or associated with a terminal. All CICS users, whether they are signed on or not, require access to transactions in this category. For this reason, they are exempt from any security checks and CICS permits any terminal user to initiate these transactions. Examples of category 3 transactions are CESN and CESF, to sign on and off, respectively.
CAVM
See CICS availability manager (CAVM).
CAVM message data set
In XRF, a data set used by the active CICS system to transmit messages to the alternate CICS system about the current state of resources, and when the XRF control data set is unavailable, for the secondary surveillance signals of the active and alternate CICS regions.
CBIPO
See Custom-Built Installation Process Offering (CBIPO).
CCB
See connection control block (CCB).
CCSID
See coded character set identifier.
CCTL
See coordinator control subsystem (CCTL).
CDB
See conversation data block (CDB).
CD-ROM (compact disc-read-only memory)
High-capacity read-only memory in the form of an optically read compact disc.
CDSA
See CICS dynamic storage area (CDSA).
CDT
See class descriptor table (CDT).
CEB
See conditional end bracket (CEB).
CECI
See command-level interpreter (CECI CECS).
central processor complex (CPC)
In a z/OS or OS/390 environment, a physical collection of hardware (such as an ES/3090) that consists of main storage, one or more central processors, timers, and channels.
chain assembly
In CICS intercommunication, a grouping of one or more request units to satisfy a single request. Instead of an input request being satisfied by one RU at a time until the chain is complete, the whole chain is assembled and sent to the CICS application satisfying just one request. This ensures that the integrity of the whole chain is known before it is presented to the application program.
chained data areas
A series of data areas in which each area contains the means of addressing the next. Chained data areas are implemented in VS COBOL II by means of the ADDRESS special register.
chained storage area
In COBOL, areas each of which contain a pointer to the next area in the chain.
change accumulation
The process of merging log data sets and reducing the information they contain to the minimum required to perform recovery on a particular database or group of databases.
change-direction protocol
In SNA, a data flow control protocol in which the sending logical unit (LU) stop sending normal-flow requests, signals this fact to the receiving LU using the change-direction indicator (in the request header of the last request of the last chain), and prepares to receive requests.
channel
A functional unit, controlled by the processor, that handles the transfer of data between processor storage and local peripheral equipment.
checkpoint
A place in a program at which a check is made, or at which a recording of data is made to allow the program to be restarted in case of interruption. System checkpoints can be requested by the administrator, a user, or by an application.
child activity
An activity that has been defined by another activity, its parent .
CI
See control interval (CI).
CICS (Customer Information Control System)
An IBM licensed program that provides online transaction-processing services and management for business applications. In DB2 UDB for OS/390 information, this term represents CICS Transaction Server for z/OS and OS/390, CICS/ESA, and CICS/MVS.
CICS attachment facility
A facility that provides a multithread connection to DB2 to allow applications running under CICS to execute DB2 commands.
CICS availability manager (CAVM)
In XRF, the mechanism that provides integrity for a CICS system with XRF. The CAVM uses the control data sets and the message file to handle communication between the active and alternate systems. See also availability manager (AVM).
CICS business transaction services (BTS)
CICS domains that support an application programming interface (API) and services that simplify the development of business transactions.
CICS Client
A member of the family of CICS workstation products that provide a standard set of functions for client/server computing. Each CICS client is designed to run on a particular operating system. Each can attach to a range of CICS server systems, and provides access to resources owned by the servers. See also external call interface, external presentation interface (EPI).
CICS database adapter transformer
A component of the CICS-DBCTL interface in the CICS address space. Also referred to in IMS publications as the adapter or the adapter/transformer. Its main responsibility is to communicate with the database resource adapter (DRA).
CICS default userid
The userid assigned to a terminal user before the user signs on to CICS, and after the user signs off.
CICS-deployed JAR file
A deployed JAR file, produced specifically (via several intermediate stages) for the CICS EJB server, which has been stored on the hierarchical file system (HFS) used by the host operating system. This name is reserved for the original "deployed JAR file" on the HFS of a CICS system. (There are no specific names for JAR files in the various intermediate stages of deployment).
CICS-DL/I router (DFHDLI)
Forms the interface between application programs and the DL/I call processor. It accepts requests for remote, local, or DBCTL database processing.
CICS dynamic storage area (CDSA)
(1) A storage area allocated from CICS-key storage below the 16MB line. The size of the CDSA is controlled by the CDSASZE system initialization parameter.
(2) In CICS/VSE, the CICS DSA is preallocated at system initialization, and is the area of storage left within the CICS partition after the CICS nucleus has been loaded. The size of the partition is determined by the EXEC DFHSIP SIZE parameter.
CICS EJB server
One or more CICS regions that support enterprise beans. A logical CICS EJB server typically consists of multiple (cloned) CICS listener regions and multiple (cloned) CICS AORs. The listener regions and AORs may be combined into listener/AORs.
CICS Internet Gateway
A workstation application that can accept requests from Web browsers and route them into CICS. It uses a CICS client and the EPI.
CICS-key
Storage protection key in which CICS is given control (key 8) when CICS storage protection is used. This key is for CICS code and control blocks. CICS-key storage can be accessed and modified by CICS. Application programs in user-key cannot modify CICS-key storage, but they can read it. CICS-key storage is obtained in MVS key-8 storage. See also user-key.
CICS-maintained data table (CMT)
A type of CICS data table, for which CICS automatically maintains consistency between the table and its source data set. All changes to the data table are reflected in the source data set and all changes to the source data set are reflected in the data table.
CICS messages and codes data set (DFHCMACD)
A VSAM key-sequenced data set (KSDS) that is created and loaded by running the DFHCMACI job. Service changes can be applied to the DFHCMACD data set by running the DFHCMACU job. The CMAC transaction uses the DFHCMACD data set to provide online descriptions of CICS messages and codes.
CICS monitoring facility
The CICS component responsible for monitoring and producing task-related statistics information, such as task CPU usage and waits for I/O request units on an individual task basis. Reporting is divided into classes.
CICS on Open Systems
A term used to refer generically to the products: TXSeries Version 5.0 for Multiplatforms, which contains CICS for AIX, CICS for HP-UX, CICS for Sun Solaris and CICS for Windows NT; TXSeries Version 4.3 for AIX (which contains CICS for AIX); TXSeries Version 4.2 for HP-UX (which contains CICS for HP-UX); TXSeries Version 4.3 for Sun Solaris (which contains CICS for Sun Solaris); TXSeries Version 4.3 for Windows NT (which contains CICS for Windows NT).
CICS PD/MVS
See CICS Problem Determination/MVS (CICS PD/MVS).
CICSPlex SM
See CICSPlex System Manager (CICSPlex SM).
CICSPlex SM address space (CMAS)
A CICSPlex SM component that is responsible for managing CICSplexes. A CMAS provides the single-system image for a CICSplex by serving as the interface to other CICSplexes and external programs. There must be at least one CMAS in each MVS image on which you are running CICSPlex SM. A single CMAS can manage CICS systems within one or more CICSplexes.
CICSPlex SM region
A functionally similar group of CICS resources. For example, a CICSPlex SM region can be an application-owning region, a terminal-owning region, or a file-owning region.
CICSPlex SM token
Unique, 4-byte values that CICSPlex SM assigns to various elements in the API environment. Token values are used by CICSPlex SM to correlate the results of certain API operations with subsequent requests.
CICSPlex System Manager (CICSPlex SM)
A system-management tool that enables you to manage multiple CICS systems as if they were one. CICSPlex SM can manage independent, full-function CICS systems running on one or more connected central processor complexes (CPCs) just as easily as it can manage multiple, interconnected CICS systems functioning as a CICSplex, also on one or more connected CPCs.
CICS Problem Determination/MVS (CICS PD/MVS)
A set of online tools to help system programmers analyze and manage system dumps. CICS PD/MVS automates dump analysis and formats the results into interactive online panels that can be used for further diagnosis and resolution of problems.
CICS program library (DFHRPL)
A library that contains all user-written programs and CICS programs to be loaded and executed as part of the online system. DFHRPL includes the control system itself and certain user-defined system control tables essential to CICS operation. The library contains program text and, where applicable, a relocation dictionary for a program. The contents of this library are loaded asynchronously into CICS dynamic storage for online execution.
CICS region userid
The 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 segment
The portion of a RACF profile containing data for CICS.
CICS system
(1) The entire collection of hardware and software required by CICS.
(2) In CICSPlex SM topology, a definition referring to a CICS system that is to be managed by CICSPlex SM.
CICS system definition data set (CSD)
A VSAM KSDS cluster that contains a resource definition record for every record defined to CICS using resource definition online (RDO).
CICS system group
(1) A set of CICS systems within a CICSplex that can be managed as a single entity.
(2) In CICSPlex SM topology, the user-defined name, description, and content information for a CICS system group. A CICS system group can be made up of CICS systems or other CICS system groups.
(3) In CICS business transaction services (BTS), a BTS set, that is the set of CICS regions across which BTS processes and activities may execute.
CICS Transaction Affinities Utility
CICS-supplied values to certain data options on EXEC CICS commands. For more details about the utility, see the CICS Transaction Affinities Utility User's Guide.
CICS-value data area (CVDA)
A CICS value on INQUIRE and SET commands, specifically those that refer to resource status or definition. See CICS value data areas used by all commandsfor more information.
CICSVR
CICS VSAM Recovery provides forward recovery for VSAM data sets and batch backout of VSAM data sets used by CICS.
CICS Web interface
A collection of CICS resources supporting direct access to CICS transaction processing services from Web browsers.
CI splitting
In VSAM, to double control interval dynamically and distribute its records evenly when the specified minimum of free space is used up by new or lengthened records.
CKD
See count-key-data (CKD).
class
(1) In RACF, a collection of defined entities (users, groups, and resources) with similar characteristics. The class names are USER, GROUP, DATASET, and the classes that are defined in the class descriptor table.
(2) In Java programming, an encapsulated collection of data and methods to operate on the data. A class may be instantiated to produce an object that is an instance of the class.
(3) In RACF, a collection of entities (users, groups, and resources) that have similar characteristics.
class 1 terminal
In XRF (CICS Transaction Server only), a remote SNA VTAM terminal connected through a boundary network node IBM 3745/3725/3720 Communication Controller with an NCP that supports XRF. Such a terminal has a backup session to the alternate CICS system.
class 2 terminal
In XRF (CICS Transaction Server 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/VSE equivalent of this is tracked terminal .
class 3 terminal
In XRF (CICS Transaction Server only), a terminal belonging to a class mainly comprised of TCAM(DCB) terminals. These terminals lose their sessions at takeover. The CICS/VSE equivalent of this is untracked terminal.
class authority (CLAUTH)
An authority that allows a user to define RACF profiles in a class defined in the class descriptor table. A user can have class authority to one or more classes.
class descriptor
In RACF, an entry in the CDT. Each class descriptor associates a class name with one or more CICS resources. A class descriptor should exist for every class except USER, GROUP, and DATASET.
class descriptor table (CDT)
In RACF, a table containing class descriptors. The CDT contains descriptors with default class names for CICS resources. Users can modify the supplied descriptors and add new ones.
classification rule
A rule used by the workload management and subsystems to assign a service class and, optionally, a reporting class to a work request (transaction). A classification rule consists of one or more of the following work qualifiers: subsystem type; subsystem instance; userid; accounting information; transaction name; transaction class; source LU, NETID, and LU name.
class of service (COS)
A VTAM facility that allows APPC sessions to have different characteristics to provide a user with alternate routing, mixed traffic, and trunking. Based on their class of service, sessions can take different virtual routes, use different physical links, and be of high, medium, or low priority to suit the traffic carried on them.
class path
A list of directories and JAR files that contain resource files or Java classes that a program can load dynamically at run time.
CLAUTH
See class authority (CLAUTH).
clean keypoint time
CICS sets a recovery point in the ICF catalog from the keypoint directory element (KPDE) with a time earlier than, and nearest to, the minimum fuzzpoint. This time is stored in the JCT header prefix where it is known as the clean keypoint time.
client
A system or process that is dependent on another system or process (usually called the server) to provide it with access to data, services, programs, or resources. Multiple clients may share access to a common server. See also server, host.
client initialization file
A file containing configuration information used to inform the CICS Client of the CICS servers it can connect to, and the communication protocols to be used.
client program
(1) In dynamic routing the application program, running in the requesting region, that issues a remote link request.
(2) In CICS distributed program link, the application program that issues a remote link request.
(3) In the client/server model, the front-end transaction.
client/server
Pertaining to the model of interaction in distributed data processing in which a program on one computer sends a request to a program on another computer and awaits a response. The requesting program is called a client; the answering program is called a server. See also distributed application.
cloned CICS regions
CICS regions that are identical in every respect, except for their identifiers. This means that each clone has exactly the same capability. For example, all clones of an application-owning region can process the same transaction workload.
CLT
See command list table (CLT).
cluster
A data set defined to VSAM. A cluster can be a key-sequenced data set, an entry-sequenced data set, or a relative record data set.
CMAS
See CICSPlex SM address space (CMAS).
CMAS link
A communications link between one CICSPlex SM address space (CMAS) and another CMAS or a remote managed application system (remote MAS). CMAS links are defined when CICSPlex SM is configured.
CMAS monitoring application
The agent by which the CICSPlex SM receives its information on CICS regions and resources.
CMAS monitoring subsystem
The graphical interface that displays and monitors CICSPlex SM address spaces (CMASs).
CMC
See communication management configuration (CMC).
CMT
See CICS-maintained data table (CMT).
COBOL
See Common Business Oriented Language (COBOL).
code page
A particular assignment of code points to graphic characters. Within a given code page, a code point can have only one specific meaning. A code page also identifies how undefined code points are handled. In a code page, all code points are assigned. For example, in 8-bit code, the page assigns characters or meanings to 256 points; for 7-bit code, 128 code points are assigned. To cater for different languages and the character requirements of different types of applications, an interchange code (such as EBCDIC) typically defines several code pages. Each code page has a unique name or identifier.
coded character set identifier
A 16-bit number identifying a specific set of encoding scheme identifier, character set identifier(s), code page identifier(s), and additional coding-related required information, that uniquely identifies the coded graphic character representation used. Acronym: CCSID.
cold start
The standard initialization sequence performed by the CICS system initialization program. In a cold start, all resource definitions are refreshed. Any resources dynamically installed by the CEDA transaction in a previous execution are lost. See What happens when CICS is initialized or Starting CICS with the START=COLD parameter.
command and response token (CART)
An 8-byte token that is supplied with a MODIFY command issued by the console operator and that can be added to all MVS WTO macros that are issued as a result of that command. Thus, each response WTO can be associated with the command that invoked it.
command language translator
A batch program (part of CICS program preparation utilities) that prepares a source application program that includes EXEC CICS or EXEC DLI commands. The translator program translates the EXEC commands into CALL statements in the language of the application program. The translator output can be compiled or assembled in the usual way. See source program, object module, load module (LMOD), compiler, assembler, linkage editor.
command-level interface
See application programming interface (API).
command-level interpreter (CECI CECS)
A transaction that enables CICS commands to be entered, syntax-checked, and executed interactively at a 3270 screen. It provides a reference to the syntax of the whole of the CICS command-level application programming and system programming interface. See the CICS-Supplied Transactions manual for more information.
command list table (CLT)
(1) In XRF, a CICS table that contains a list of VSE commands and messages to be issued during takeover. The CLT is defined to the alternate CICS system and used during takeover. See CLT -- Command list table
(2) System initialization parameter that specifies the suffix for the command list table, if this system initialization table is used by an alternate XRF system. See The system initialization parameter descriptions for more information.
command recognition character (CRC)
In MVS, a character that denotes an operator command. DBCTL operator commands have / as their default CRC.
command security
A form of security checking that can be specified for the PERFORM, COLLECT, DISCARD, INQUIRE, and SET commands. Command security operates in addition to any transaction security or resource security specified for a transaction. For example if a terminal invokes a transaction that the user is authorized to use, and the transaction issues a command that the user is not authorized to use, the command fails with the NOTAUTH condition.
command thread
A thread which is reserved by the CICS DB2 attachment facility for commands issued to DB2 using the DSNC transaction. See also entry thread and pool thread.
COMMAREA
See communication area (COMMAREA).
commit
The second phase in a 2-phase commit. If all UOW participants acknowledge that they are prepared to commit (vote yes), the coordinator issues the commit request. If only one UOW participant is not prepared to commit (votes no), the coordinator issues a backout request to all. See also two-phase commit.
committed change
A change that is not backed out in the event of a failure. Changes made by an LUW are committed when the syncpoint at the end of the LUW is complete.
committed output message
A message that is transmitted as a result of an LUW completing a syncpoint (at which time changes to data resources made by the LUW are also committed). A committed output message is one that, in the event of a failure, needs to be transmitted and acknowledged to be sure that logical consistency with the changes to data resources is maintained. During recovery processing, if an LUW has committed its changes but an associated committed output message has not been transmitted or has not been acknowledged, CICS places the message in a message cache. The system can retransmit the message from the cache if desired.
Common Business Oriented Language (COBOL)
A high-level programming language, based on English, that is used primarily for commercial data processing.
common error bucket
An additional error status element (ESE) generated for each terminal error block (TEB), if fewer ESEs than the maximum number of error types recognized by the CICS terminal abnormal condition program are specified when the terminal error program (TEP) tables are generated.
Common Object Request Broker Architecture (CORBA)
An architecture and a specification for distributed object-oriented computing that separates client and server programs with a formal interface definition. IIOP defines the message formats and protocols used in a CORBA distributed environment.
Common Programming Interface (CPI)
In the Systems Application Architecture (SAA) solution, a set of software interfaces, conventions, languages, and protocols that provide a framework for writing applications with cross-system consistency.
Common Services
A component of CICSPlex SM that provides commonly requested services (such as GETMAIN, FREEMAIN, POST, and WAIT processing) to other CICSPlex SM components.
common system area (CSA)
(1) A major CICS storage control block that contains areas and data required for the operation of CICS. See Control Blocks for more information.
(2) In MVS, an area that contains system control programs and control blocks. The storage areas within the common area are the system queue area (SQA), the pageable link pack area (PLPA), the (optional) modified link pack area (MLPA), a pageable BLDL table, a copy of the prefixed storage area (PSA) (for multiprocessor systems only), and a common system area (CSA).
Common User Access (CUA)
A Systems Application Architecture (SAA) specification that gives a series of guidelines describing the way information should be displayed on a screen, and the interaction techniques between users and computers.
common work area (CWA)
An area within the CSA that can be used by application programs for user data that needs to be accessed by any task in the system. This area is acquired during system initialization and its size is determined by the system initialization parameter, WRKAREA. See also transaction work area (TWA).
communication area (COMMAREA)
A CICS area that is 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.
communication controller
(1) A type of communication control unit whose operations are controlled by one or more programs stored and executed in the unit. It manages the details of line control and the routing of data through a network. See also transmission control unit (TCU).
(2) A device that directs the transmission of data over the data links of a network; its operation may be controlled by a program executed in a processor to which the controller is connected or it may be controlled by a program executed within the device. (T)
communication management configuration (CMC)
A configuration in which the VTAM subsystem that owns the terminals is in a different MVS image from the active or the alternate CICS system.
communication section
Part of the task control area (TCA) that is used by CICS and by user-written application programs for communication between the application program and CICS management and service programs.
compact disc-read-only memory (CD - ROM)
See CD-ROM (compact disc-read-only memory).
compatibility mode
A workload management mode for an MVS image in a sysplex using the pre-workload management MVS performance tuning definitions from the IEAICSxx and IEAIPSxx members of the SYS1.PARMLIB library.
compensation
The act of modifying the effects of a child activity. Typically, compensation undoes the actions taken by an activity. For example, compensation for an order activity might be to cancel the order.
compensation program
A program that implements the compensation actions for an activity. It may or may not be the same program used for the activity's normal execution.
compiler
A program that translates a source program into an executable program (an object program).
completed task
During emergency restart, a task for which recovery control encountered user-journaled records that were written with the high-order bit set on in the JTYPEID operand of the EXEC CICS WRITE JOURNALNUM command. (In CICS Transaction Server only, backout processing ignores these records, but presents them to the user at the XRCINPT exit.)
component tracing
A facility provided by CICS to track transactions through CICS components and user programs.
composite event
A "high-level" event, typically formed from the combination of two or more atomic events. However, composite events can be "empty" - that is, they may contain no sub-events. See also atomic event, user-defined event
compute-bound
The property of a transaction whereby the elapsed time for its execution is governed by its computational content rather than by its need to do input/output.
concatenation bit
In distributed transaction processing, high order bit of the first byte of the header of a GDS record.
concurrent
Pertaining to the occurrence of two or more activities within a given interval of time. Concurrent processes can alternately use shared common resources.
conditional access list
In RACF, an access list within a resource profile that associates a condition with a userid or group ID and the corresponding access authority, allowing otherwise unauthorized access if the specified condition is true.
conditional end bracket (CEB)
An SNA indicator in the request header, FMH5, denoting the end of a conversation between two transactions. See also begin bracket (BB) and FMH-5.
connection
(1) A CICS resource that defines a remote system with which your CICS system communicates, using intersystem communication (ISC) or multiregion operation (MRO).
(2) In Front-End Programming Interface (FEPI), connection refers to a target-node pair in the same pool, between which a session can be established (bound), and which can then be used for communication. See also session.
connection control block (CCB)
A control block created by CICS for each IRC session. The CCB contains control information for the interregion connection and a pointer to the CSB.
connection status block (CSB)
A control block created by CICS for each IRC session. The CSB contains status information about the interregion connection.
consistency
A state of data. A transaction updates the data and checks its state. If the transaction detects any inconsistency, the change is rolled back and the data is returned to its previous consistent state. See also ACID properties.
consistent
A type of read integrity in which a program is permitted to read only committed data - data that cannot be backed out after it has been passed to the program issuing the read request. Therefore, a consistent read request can succeed only when the data is free from all locks. See also read integrity, repeatable.
console
An input/output device on a computer, reserved for communication between the computer operator or maintenance engineer and the computer.
consolidated software inventory (CSI)
A key-sequenced VSAM data set, used by SMP/E and logically divided into zones.
constraint
A place in the system where contention for a resource is affecting performance, sometimes referred to as "transaction throughput degradation" or bottleneck.
container
In J2EE, an entity that provides life-cycle management, security, deployment, and run-time services to components. (Sun) Each type of container (EJB, Web, JSP, servlet, applet, and application client) also provides component-specific services.
contention loser
On an LU-LU session, the LU that must use an SNA BID command (LU type 6.1) or an LUSTATUS command (APPC) to request permission to begin a conversation.
contention mode
In data communication, a mode of transmission in which any station may transmit whenever the line is available, This occurs when a session is between brackets. If stations transmit simultaneously, protocols determine who wins the contention.
contention winner
On an LU-LU session, the LU that is permitted to begin a conversation at any time.
context
A named part of the CICSPlex SM environment that is currently being acted upon by CICSPlex SM. For configuration tasks, the context is a CICSPlex SM address space (CMAS); for all other tasks, it is a CICSplex. See also scope.
context-switch
The activation of a process or activity either in a separate unit of work from the requestor or with the transaction attributes specified on the DEFINE PROCESS or DEFINE ACTIVITY command, rather than with those of the requesting transaction. The relationship of the process or activity to the requestor is as between separate transactions, except that data can be passed between the two units of work. A context-switch occurs when a process or activity is activated by a RUN command, but not when it is activated by a LINK command.
continuous JVM
A Java Virtual Machine (JVM) that is initialized once, and is reused many times, but it is not reset after each Java program has completed. A continuous JVM has the option REUSE=YES specified in its JVM profile.
control area (CA)
In VSAM, a group of control intervals used as a unit for formatting a data set before adding records to it. Also, in a key-sequenced data set, the set of control intervals, pointed to by a sequence-set index record, that is used by VSAM for distributing free space and for placing a sequence-set index record adjacent to its data.
control block
In CICS, a storage area used to hold dynamic data during the execution of control programs and application programs. See also control area (CA), control table.
control data set
In XRF, a data set that ensures XRF system integrity by allowing only one active CICS system to access a particular set of resources. It is used by the active and alternate CICS systems to monitor each other's status.
control flow
Transmission of control indicators over a link when there is no user data available to send. This is often necessary during complex procedures, such as establishing syncpoints.
control interval (CI)
A fixed-length area of auxiliary-storage space in which VSAM stores records and distributes free space. The unit of information transmitted to or from auxiliary storage by VSAM in a single operation, independent of physical record size.
control subpool
A CICS area that holds the dispatch control area (DCA), interval control elements (ICEs), automatic initiate descriptors (AIDs), queue element areas (QEAs), and other control information. Generally, the control subpool occupies only one page.
control table
In CICS, a storage area used to define or describe the configuration or operation of the system. See also control block.
control terminal
In CICS, the terminal at which a designated control operator is signed on.
conversation
(1) A connection between two programs over a session that allows them to communicate with each other while processing a transaction. See also session.
(2) In FEPI, a sequence of related data transmission between a FEPI application and a particular back-end system, This is analogous to a CICS APPC conversation, but it is not the same as an IMS conversation, and it is not related to CICS conversational mode.
conversational
(1) Pertaining to a program or a system that carries on a dialog with a terminal user, alternately receiving and transmitting data.
(2) Pertaining to an SNA conversation or a dialog between two programs.
conversation characteristics
In distributed transaction processing, the attributes of a conversation that determine the functions and capabilities of programs within the conversation.
conversation correlator
In LU6.2 distributed transaction processing, a field passed in the attach header when the conversation is initiated.
conversation data block (CDB)
An area used by a program to obtain information about the outcome of a DTP command on an APPC basic (GDS) conversation.
convid
In distributed transaction processing, conversation identifier passed by EXEC CICS commands.
cooperative processing
Distributed processing in which processors, typically a programmable work station and a host computer, accomplish the work of an application by means of coordinated or synchronized use of processing functions and system resources.
coordinating address space (CAS)
The function that sets up the CICSPlex SM component topology and that supports the MVS/TSO ISPF graphic user interface to CICSPlex SM. CAS is used in CMAS-to-CMAS links.
coordinator
In a multi-MVS or VSE MRO XRF configuration, a region that receives requests from master regions to initiate a takeover. It then instructs all the alternate regions to take over.
coordinator control subsystem (CCTL)
In IMS/ESA, the transaction management subsystem that communicates with the DRA, which in turn communicates with DBCTL. In a CICS-DBCTL environment, the CCTL is CICS. The term is used in a number of IMS operator commands that apply to DBCTL, and in the IMS manuals.
CORBA
See Common Object Request Broker Architecture (CORBA).
CORBA Object Services Naming Directory
A server that supports the Java Naming and Directory Interface (JNDI).
CorbaServer
The execution environment for enterprise beans and CORBA stateless objects defined by a CORBASERVER definition. A CICS EJB server can contain multiple CorbaServers. All the AORs in a logical CICS EJB server would contain identical CORBASERVER definitions.
COS
See class of service (COS).
COS Naming Directory
See CORBA Object Services Naming Directory.
count-key-data (CKD)
A disk storage device for storing data in the format: count field normally followed by a key field followed by the actual data of a record. The count field contains, in addition to other information, the address of the record in the format: CCHHR (where CC is the two-digit cylinder number, HH is the two-digit head number, and R is the record number) and the length of the data. The key field contains the record's key (search argument).
CPC
See central processor complex (CPC)
CPI
See Common Programming Interface (CPI).
CRC
See command recognition character (CRC).
cross-partition communication control
(CICS/VSE only) A facility that enables VSE subsystems and user programs to communicate with each other; for example, with VSE/POWER.
cross-systems coupling facility (XCF)
A facility of MVS/ESA SP 4.1 that provides some initial MVS services needed to support a multisystem environment while still maintaining a single system image. Systems coupled using XCF are known as a sysplex.
CSA
See common system area (CSA).
CSB
See connection status block (CSB).
CSD
See CICS system definition data set (CSD).
CSI
See consolidated software inventory (CSI).
CUA
See Common User Access (CUA).
cumulative mapping
A form of BMS output mapping in which data stream generation is delayed until a SEND PAGE command is received or a page overflow occurs.
current connect group
In RACF, during a terminal session or batch job, the group with which a user is associated for access checking purposes. On MVS, if a user does not specify the current connect group on the LOGON command or batch JOB statement, the current connect group is the user's default group. On CICS, users cannot specify a group other than their default group. If list-of-groups processing is in effect, users are associated with all the groups to which they are connected.
current list
A list name, specified with a resource definition online command, that is "remembered" until another list name is used.
current security label
(1) The security label that RACF uses in RACF authorization checking if the SECLABEL class is active.
(2) For batch jobs on MVS, the security label specified in the SECLABEL parameter of the JOB statement, or (if no security label was specified) the default security label in the user profile associated with the job.
(3) For TSO users, the security label specified when the user logged on, or (if no security label was specified) the default security label in the user's user profile.
Custom-Built Installation Process Offering (CBIPO)
A software package for creating or replacing an MVS system.
Customer Information Control System (CICS)
See CICS.
cutover
The point of change from a development CICS system to a production CICS system, or between different releases of CICS.
CVDA
See CICS-value data area (CVDA).
CWA
See common work area (CWA).
[[ Contents Previous Page | Next Page Index ]]