
	Software �>�Globalization�>�Terminology�>�

IBM Terminology

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z #

Please send any feedback about the terms and definitions on this site to terms@ca.ibm.com

�

�C++: An enhancement of the C language that adds features supporting object-oriented programming.
�C2: A level of security defined in the Trusted Computer System Evaluation Criteria (TCSEC) published by the United States Government. To meet C2 requirements, a system must perform discretionary access control, authentication and verification, object reuse protection, and auditing of security-relevant events.
�C2A: See Click-to-Action.
�C/370: A programming language designed for a wide range of system and commercial applications.
�C/370 common anchor area (C-CAA): A common anchor area (CAA), specific to the C/370, in the runtime environment.
�CA: (1) See channel adapter.; (2) See control area.; (3) See change accumulation.; (4) See certificate authority.
�CAA: See common anchor area.
�cable path: A series of cables connected in sequence.
�cable segment: A section of cable between components or devices on a network. A segment may consist of a single patch cable, multiple patch cables that are connected to one another, or a combination of building cable and patch cables that are connected to one another.
�cable-through: Pertaining to a function or feature of a display station that allows multiple work stations to be attached to one cable path.
�CA certificate: See certificate authority certificate.
�cache: (1) A special-purpose buffer storage, smaller and faster than main storage, used to hold a copy of instructions and data obtained from main storage and likely to be needed next by the processor.; (2) A buffer that contains frequently accessed instructions and data; it is used to reduce access time.; (3) Memory used to improve access times to instructions, data, or both. Data that resides in cache memory is normally a copy of data that resides elsewhere in slower, less expensive storage, such as on a disk or on another network node.; (4) To place, hide, or store frequently used information locally for quick retrieval.
�cache fast write: A storage control capability in which data is written directly to cache without using nonvolatile storage. Cache fast write is useful for temporary data or data that is readily re-created. See also DASD fast write.
�cache hit: An event that satisfies a read operation by retrieving data from cache instead of retrieving it from the intended storage or a lower level of cache. See also cache miss.
�cache instance resource: A location where any Java Platform, Enterprise Edition (Java EE) application can store, distribute, and share data.
�cache line: A record that contains relevant information about the user data that is currently in the subsystem cache memory. Examples of this information include the current state of the data and the intended location of the data on one or more disks.
�cache miss: An event that satisfies a read operation by retrieving data from the intended storage or a lower level of cache because the requested data is not available in the only level or a higher level of cache. See also cache hit.
�cache replication: The sharing of cache IDs, cache entries, and cache invalidations with other servers in the same replication domain.
�cache set: A storage-class parameter, defined in the base configuration information, that maps a logical name to cache structure names in a coupling facility (CF).
�cache structure: A coupling facility structure that stores data that can be available to all members of a Sysplex. A DB2 data sharing group uses cache structures as group buffer pools. See also group buffer pool.
�cache table: In a federated system, a logical table object that is used to cache data from a data source table. A cache table comprises a nickname that identifies the data source table, one or more materialized query tables, and a schedule for replicating the data in each materialized query table.
�cache timeout: The length of time that is allowed to pass before the cache is updated.
�caching: The process of storing frequently used results from a request to memory for quick retrieval, until it is time to refresh the information. The DB2 database manager provides many forms of caching, such as directory caching, package caching, file system caching, and LDAP caching.
�caching proxy server: A proxy server that stores the documents that it retrieves from other servers in a local cache. The caching proxy server can then respond to subsequent requests for these documents without retrieving them from the other servers. This can improve response time.
�cadence: The modulated and rhythmic recurrence of an audio signal. For example, a series of beeps or a series of rings.
�CAF: See call attachment facility.
�CA key: See command attention key.
�calculation code: A code associated with order items, catalog entries, or catalog groups to specify how discounts, shipping charges, sales or use taxes, and shipping taxes should be calculated.
�calculation framework: A flexible, generic framework provided by the WebSphere Commerce order subsystem, used to implement calculations and apply them to the applicable business objects.
�calculation method: A reference task command that implement parts of calculation framework.
�calculation rule: A rule that defines how a calculation will be done.
�calculation scale: A set of ranges that can be used by a calculation rule. For example, for shipping charges, there can be a set of weight ranges that each correspond to a particular cost. That is, a product that weighs between 0 to 5 kg might cost $10.00 to ship, while a product weighing 5 to 10 kg might cost $15.00 to ship.
�calculation specification: In RPG, a specification on which the programmer describes the processing to be done by the program.
�calculation usage: A type of calculation that the calculation framework performs.
�calendar: A view in the Notes mail database that can be used to manage time and schedule meetings. Users can add appointments, meetings, reminders, events, and anniversaries to the Calendar view.
�calendar exception: A partial or full day during which a resource does not work on a project
�calendaring and scheduling: A feature available for clients using Notes that allows the user whose mail is enabled with Sametime to schedule an online meeting in Notes and send e-mail invitations to prospective participants.
�calibration: In capacity planning, the process of refining a model so that it represents the system the user is modeling. The predicted and measured values should match as closely as possible, with no more than a 10% difference for resource utilization, and no more than a 20% difference for response times.
�call: (1) To start a program or procedure, usually by specifying the entry conditions and transferring control to an entry point.; (2) A physical or logical connection between one or more parties in a telephone call.; (3) A single runtime instance of a voice application.; (4) An instruction in COBOL, assembler language, C/370, or PL/I format that is used by an application program to request DL/I services.; (5) In Sametime, an audible message sent using a traditional phone call (POTS, PSTN). It may be IP based, or a hybrid using both IP and traditional phone.; (6) An action state that invokes an operation on a classifier.
�callable interface (CI): (1) The name of the interface program, the definition of the arguments passed to the interface program, and the definition of the data structures passed to the interface program.; (2) In query management, the Common Programming Interface (CPI) that includes the definitions of the control blocks and constants used for the interface. See also command interface.
�callable service: (1) A program service provided through a programming interface. See also action service.; (2) A set of documented interfaces between the z/OS operating system and higher level applications that want to access functions specified in the Single UNIX Specification and earlier standards.; (3) Services that are provided by IMS for use by IMS exit routines. These services provide clearly defined interfaces that allow exit routines to request various functions, such as acquiring storage or finding an IMS control block.
�call-accepted packet: A call supervision packet that a called data terminal equipment (DTE) transmits to indicate to the data circuit-terminating equipment (DCE) that it accepts the incoming call. See also call request packet, call connected packet.
�call attachment facility (CAF): A DB2 for z/OS attachment facility for application programs that run in TSO or z/OS batch. The CAF is an alternative to the DSN command processor and provides greater control over the execution environment. See also Recovery Resource Services attachment facility.
�callback: A way for one thread to notify another application thread that an event has happened.
�callback function: See implementation function.
�callback handler: A mechanism that uses a Java Authentication and Authorization Service (JAAS) interface to pass a security token to the Web service security runtime for propagation in the Web service security header.
�callback registration: The identification and registration of a callback routine.
�call center: (1) A central point at which all inbound calls are handled by a group of individuals on a controlled sequential basis. Call centers are usually a front end to a business such as airline ticketing or mail order.; (2) A place staffed by users in the customer service representative access group, who can perform some functions on behalf of a customer. For example, they can update customer information, including the password; they can also update orders or place a new order.
�call center dashboard: A user interface that provides information on how the telesales service representative, shift, or call center is performing.
�call chain: A trace of all active routines and subroutines, such as the names of routines and the locations of save areas, that can be constructed from information included in a system dump.
�call connected packet: In X.25 communications, a call supervision packet transmitted by a DCE to inform the calling DTE of the complete establishment of the call. See also call-accepted packet, call request packet.
�call control: That set of telephony functions that includes call establishment, call transfer, and call disconnection (the program control of a telephone call).
�call detail record (CDR): In telephony, a unit of information containing data about a completed call, such as the time the call began, its duration and date, the originating extension, and the number called.
�called number: See dialed number identification service.
�called party: Any person, device, or system that receives a telephone call. See also caller.
�called program: A program that is the object of a CALL statement combined at run time with the calling program to produce a run unit.
�called routine: A program or sequence of instructions that is invoked by another program.
�caller: (1) The requester of a service.; (2) Any person, device, or system that makes a telephone call. See also called party.; (3) A function that calls another function.
�call forwarding: The process of sending incoming calls to a different number.
�call home: A communication link established between a product and a service provider. The product can use this link to place a call to IBM or to another service provider when it requires service. With access to the machine, service personnel can perform service tasks, such as viewing error and problem logs or initiating trace and dump retrievals. See also heartbeat.
�calling: In X.25 communications, pertaining to the location or user that makes a call.
�calling command ID: A numeric identifier for a command that calls an API function.
�calling line identification presentation (CLIP): An ISDN supplementary service that advises the called party of the caller's number: for example, by displaying it on a telephone display panel.
�calling program: A program that calls another program.
�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.x
�call level: The position of an entry (program or procedure) in the call stack. The first entry has a call level of 1. Any entry called by a level 1 entry has a call level of 2, and so on.
�Call Level Interface (CLI): An API for database access that provides a standard set of functions to process SQL statements, XQuery expressions, and related services at run time. See also embedded SQL.
�call level number: A unique number assigned by the system to each call stack entry.
�call message queue: A message queue that exists for each call stack entry within a job.
�call-not-accepted signal: A call control signal sent by the called data terminal equipment to indicate that it does not accept the incoming call.
�callout: The action of bringing a computer program, a routine, or a subroutine into effect.
�callout node: The connection point in a mediation request flow from which a service message is sent to a target. There must be one callout node for each target operation.
�callout response node: The starting point for a mediation response flow. There must be one callout response node for each target.
�CallPath: Software that provides basic computer-telephony integration (CTI) enablement and comprehensive CTI functionality. This includes access to, and management of, inbound and outbound telecommunications.
�call profile: In telephony, a set of characteristics that may be used when establishing or manipulating a program-controlled telephone call.
�call progress signal: A call control signal transmitted from the data circuit-terminating equipment (DCE) to the calling data terminal equipment (DTE) to indicate the progress of the establishment of a call, the reason why the connection could not be established, or any other network condition.
�call request packet: A call supervision packet that a data terminal equipment (DTE) transmits to ask that a connection for a call be established throughout the network. See also call-accepted packet, call connected packet.
�call session: The sequence of events that occurs from the time a call is initiated to the time all activities related to answering and processing the call are completed.
�call stack: (1) The ordered list of all programs or procedures currently started for a job. The programs and procedures can be started explicitly with the CALL instruction, or implicitly from some other event.; (2) A list of data elements that is constructed and maintained by the Java virtual machine (JVM) for a program to successfully call and return from a method.
�call stack entry: A program or procedure in the call stack.
�call supervision packet: A packet used to establish or clear a call at the interface between the data terminal equipment (DTE) and the data circuit-terminating equipment (DCE).
�call thread: In the Distributed Computing Environment (DCE), a thread created by a remote procedure call (RPC) server's run time to execute remote procedures. When engaged by an RPC, a call thread temporarily forms part of the RPC thread of the call.
�call transfer: A series of actions that directs a call to another telephone number.
�call-triggered flow: A data flow triggered by a direct call that the collaboration receives through the Server Access Interface. An access client initiates a call-triggered flow.
�call user data (CUD): User-specified data that can be placed in an X.25 call request packet to be sent to the adjacent node.
�campaign: A planned series of operations including advertisements and suggestive selling techniques, that are pursued to achieve a defined set of business objectives. In the WebSphere Commerce Accelerator, campaigns are used to coordinate and aggregate groups of campaign initiatives.
�cancel: To end a task before it is completed.
�cancelability point: A specific point within the current thread that is enabled to solicit cancel requests.
�cancellation cleanup handler: A function that you can specify to perform an action, such as releasing resources, that occurs after the thread returns from the start routine and calls pthread_exit() or after a cancellation request is performed on the thread.
�cancellation point: A function that causes a pending cancellation request to be delivered if the cancellation state is enabled and the cancellation type is deferred.
�cancellation state: One of two values, which are either enabled or disabled, that describe whether cancellation requests in the current thread are acted on or held in a pending state. If the value is enabled, the cancellation request is acted on immediately and is based on the current cancellation type. If the value is disabled, the cancellation request is held in a pending state until it is enabled.
�cancellation type: One of two values (deferred or asynchronous) that describe how cancellation requests in the current thread are acted on when the cancellation state is enabled. If the value is deferred, the cancellation request is held pending. If the value is asynchronous, the cancel request is acted on immediately, thus ending the thread with a status of PTHREAD_CANCELED.
�candidate endpoint: A known service endpoint that implements an interface for a particular request. The set of candidates is then filtered by the dynamic assembler to select the best endpoint out of all the candidates.
�canned map: A technique to achieve simulated windows using BMS. See also base map, overlay map.
�canonical: (1) In computer science, pertaining to an expression that conforms to a specific set of rules.; (2) Pertaining to the practice of conforming to known rules or procedures.
�canonical address: In LANs, the IEEE 802.1 format for the transmission of medium access control (MAC) addresses for token-ring and Ethernet adapters. In canonical format, the least significant (rightmost) bit of each address byte is transmitted first. See also noncanonical address.
�canonical format: A format for storing hierarchical names that displays the hierarchical attribute of each component of the name. For example, the canonical format for the name Reuben D. Smith/Ottawa/Acme/CA is: CN=Reuben D. Smith/OU=Ottawa/O=Acme/C=CA where: CN is the common name, OU is the organizational unit, O is the organization, and C is the region or country code.
�canonical mode: See line mode.
�capability: (1) A set of access rights to a group of target instances.; (2) In Eclipse, a group of functions that can be hidden or revealed in order to simplify the user interface. Capabilities are enabled or disabled by changing preference settings.; (3) An abstract definition of functional software characteristics (function, interface, property, event, and so forth) or nonfunctional software characteristics (scalability, portability, performance, and so forth). See also feature.; (4) Specific features or characteristics of a piece of software, such as the database version.
�capability data: In OSI, a confirmed data transfer service provided by the session layer to transfer a limited amount of data outside of an activity. Capability data can be used by two peers to exchange information about their capability to start an activity.
�capability list: A list of associated resources and their corresponding privileges per user.
�capability matrix: A data structure that represents the linguistic capabilities available within multiple language dictionaries, and allows searching for appropriate dictionaries.
�capability type: A capability category, such as "database" or "hardware".
�capacitor: An electronic part that permits storage of electricity.
�capacity on demand (CoD): The ability of a computing system to increase or decrease its performance capacity as needed to meet fluctuations in demand.
�capacity planner: A function that uses information about the system, such as a description of the system's workload, performance objectives, and configuration, to determine how the data processing needs of the system can best be met. The capacity planner then recommends, through the use of printed reports and graphs, ways to enhance performance, such as hardware upgrades, performance tuning, or system configuration changes.
�capacity planning: (1) The process of determining the hardware and software configuration required to accommodate the anticipated workload on a system.; (2) The process of scheduling the resources required to perform project work.
�capped partition: A logical partition in a shared processor pool whose processor use never exceeds its assigned processing capacity.
�capsule: A design pattern that represents an encapsulated thread of control. It is a stereotyped class with a set of required and restricted associations and properties.
�capsule role: A specification of the type of capsule that can occupy a particular position in a capsule's collaboration or structure. Capsule roles are strongly owned by the container capsule and cannot exist independently of it.
�caption: A National Language Support-enabled text string in a policy expression that describes the policy.
�capture: (1) In SQL replication, event publishing, and Q replication, to gather changes from a source database. These changes can come from the DB2 log or journal or from source transactions in a non-DB2 relational database.; (2) The process by which an acquirer receives payment from the customer's financial institution and remits the payment. A "capture" is the guarantee that the funds are available and that the transfer will take place.
�Capture control server: In SQL replication, a database or subsystem that contains the Capture control tables, which store information about registered replication source tables. The Capture program runs on the Capture control server.
�captured UCB: A virtual window into the actual unit control block (UCB). Captured UCB resides in private storage below 16 MB. All the virtual windows on the actual UCB view the same data at the same time. Only actual UCBs above 16 MB are captured. See also actual UCB, unit control block.
�Capture latency: In SQL replication, an approximate difference between the time that source data was changed and the time that the Capture program made the data available to the Apply program by committing the data to a CD table. This is a subset of the end-to-end latency in a replication configuration. See also latency, Apply latency, Q Apply latency, Q Capture latency, end-to-end latency.
�Capture program: In SQL replication, a program that reads database log or journal records to capture changes that are made to DB2 database source tables and store them in staging tables. See also Apply program, Capture trigger, Q Capture program.
�Capture schema: In SQL replication, a name that identifies the control tables that are used by a particular instance of the Capture program.
�Capture trigger: In SQL replication, a mechanism that captures delete, update, or insert operations that are performed on non-DB2 source tables. See also Apply program, Capture program.
�card: (1) An electronic circuit board that is plugged into a slot in a system to give it added capabilities.; (2) WML document that provides user-interface and navigational settings to display content on mobile devices. See also deck.
�card enclosure: The area in the system that contains the logic cards.
�card image: A one-to-one representation of the hole patterns of a punched card; for example, a card image might be a matrix in which a one represents a punch and a zero represents the absence of a punch.
�cardinality: (1) The number of rows in a database table or the number of elements in an array.; (2) The number of elements in a set. See also multiplicity.; (3) A measure of the number of unique values in a column.
�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.
�card type: A 4-digit identifier printed on the logic card.
�carriage control character: A character that is used to specify a write, space, or skip operation. See also control character.
�carriage return (CR): (1) A keystroke generally indicating the end of a command line.; (2) The movement of the printing position or display position to the first position on the same line.
�carriage return character: A character that in the output stream indicates that printing should start at the beginning of the same physical line in which the carriage-return character occurred.
�carrier: A continuous frequency (a pulse train, or an electric or electromagnetic wave) that may be varied by a signal bearing information to be transmitted over a communication system.
�carrier management system: A network management product that a communication common carrier provides to a customer; this product monitors and manages the telecommunication equipment that the communication common carrier provides for the customer's network.
�carrier sense: In a local area network, an ongoing activity of a data station to detect whether another station is transmitting.
�Carrier Sense Multiple Access with Collision Detection (CSMA/CD): (1) A media access method that monitors another station's transmissions. If the data station detects another signal during transmission, it stops transmitting, sends a jam signal, then waits for a variable time before trying again.; (2) A class of medium access procedures that allows multiple stations to access the medium at will, without explicit prior coordination, and avoids contention by way of carrier sense and deference. Contention is resolved by way of collision detection and transmission.
�CART: See command and response token.
�cartridge eject: For an IBM TotalStorage Enterprise Automated Tape Library 3494, IBM 3495 Tape Library Dataserver, or a manual tape library, the act of physically removing a tape cartridge, usually under robot control, by placing it in an output station. The software logically removes the cartridge by deleting or updating the tape volume record in the tape configuration database (TCDB). For a manual tape library, cartridge eject is the logical removal of a tape cartridge from the manual tape library by deleting or updating the tape volume record in the TCDB.
�cartridge entry: For an IBM TotalStorage Enterprise Automated Tape Library 3494, IBM 3495 Tape Library Dataserver, or a manual tape library, the process of logically adding a tape cartridge to the library by creating or updating the tape volume record in the tape configuration database (TCDB). The cartridge entry process includes the assignment of the cartridge to the scratch or private category in the library.
�cartridge loader: A feature that allows a user to place tape cartridges in a loading rack for automatic loading. Manual loading of single tape cartridges is also possible.
�Cartridge System Tape: The base tape-cartridge medium used with the IBM 3480 Magnetic Tape Subsystem and IBM 3490 Magnetic Tape Subsystem.
�CAS: (1) See coordinating address space.; (2) See channel associated signaling.; (3) See Common Analysis Structure.
�cascade: To connect in a series or in a succession of stages so that each stage derives from or acts upon the product of the preceding stage. For instance, network controllers might be cascaded in a succession of levels in order to concentrate many more lines than a single level permits.
�cascade delete: A process by which the DB2 database manager enforces referential constraints by deleting all descendent rows of a deleted parent row.
�cascaded initiator: An intermediate node in a transaction program network that uses the two-phase commit protocol.
�cascaded menu: A menu that appears from, and contains choices related to, a cascading choice in another menu.
�cascaded transaction: A transaction that spans nodes and is coordinated by Resource Recovery Services (RRS). cascaded multisystem transaction. A transaction that spans systems in a sysplex and is coordinated by Resource Recovery Services (RRS).
�cascaded UR family: A collection of nodes consisting of a unit of recovery (UR) and its descendants.
�cascading choice: A choice on a menu that, when selected, presents another menu with additional related choices.
�cascading replication: A replication topology in which there are multiple tiers of servers. A peer/master server replicates to a small set of read-only servers which in turn replicate to other servers. Such a topology off-loads replication work from the master servers.
�cascading resource: A resource that can be taken over by more than one node. A takeover priority is assigned to each configured cluster resource group on a per-node basis. In the event of a takeover, the node with the highest priority acquires the resource group. If that node is unavailable, the node with the next-highest priority acquires the resource group, and so on.
�cascading style sheet (CSS): A file that defines a hierarchical set of style rules for controlling the rendering of HTML or XML files in browsers, viewers, or in print.
�cascading style sheet positioning (CSS-P): Use of a cascading style sheet to position Web page elements using pixel locations or locations relative to other elements.
�cascading switches: Switches that are interconnected to build large fabrics.
�CASE: See Computer Assisted Software Engineering.
�case clause: In a C or C++ switch statement, a CASE label followed by any number of statements.
�CASE expression: An expression that is selected based on the evaluation of one or more conditions.
�case label: The word case followed by a constant expression and a colon. When the selector is evaluated to the value of the constant expression, the statements following the case label are processed.
�case-sensitive: Pertaining to the ability to distinguish between uppercase and lowercase letters.
�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.
�cassette: (1) In cut-sheet printers, a removable container for a supply of paper.; (2) A software component which supports a particular payment protocol.
�cast: In programming languages, an expression that converts the value of its operand to a specified type.
�cast expression: An expression that converts or reinterprets its operand.
�cast function: A function that is used to convert instances of a source data type into instances of a different target data type. In general, a cast function has the name of the target data type and has one single argument whose type is the source data type. Its return type is the target data type. See also built-in function.
�CAS tone: See Customer Premise Equipment Alerting Signal tone.
�cast operator: An operator that is used for explicit type conversions.
�castout: The DB2 process of writing changed pages from a group buffer pool to disk.
�castout owner: The DB2 member that is responsible for casting out a particular page set or partition.
�casual connection: In an APPN network, a connection between an end node and a network node with different network identifiers.
�catalog: (1) A collection of tables and views that contains descriptions of objects such as tables, views, and indexes.; (2) A directory of files and libraries, with reference to their locations.; (3) A data set that contains information about other data sets.; (4) A container that, depending on the container type, holds processes, data, resources, organizations, or reports in the project tree.; (5) To enter information about a data set or a library into a catalog.
�catalog asset store: A collection of catalog artifacts that creates a virtual catalog. See also asset store, storefront asset store.
�catalog cleanup: A process that deletes entries for which volumes are no longer available; catalog cleanup also allows deletion of a catalog even though it is not empty.
�catalog connector: A catalog entry, either a user catalog entry or a catalog connector entry, in the master catalog that points to a user catalog's volume (that is, it contains the volume serial number of the direct access volume that contains the user catalog).
�cataloged data set: A data set that is represented in an index or hierarchy of indexes that provide the means for locating it.
�cataloged procedure: A set of job control language (JCL) statements that has been placed in a library and that is retrievable by name.
�catalog entry: An object in an online catalog. An entry has a name, description, list price, and other details. The entry can be as simple as a SKU; it may also be a product that is automatically broken down into its component items such as a bundle or package.
�catalog group: A collection of one or more catalog entries or catalog groups which create a navigational hierarchy for an online catalog.
�catalog node: See catalog partition.
�catalog partition: In a partitioned database environment, the database partition where the catalog tables for the database are stored. Each database in a partitioned database environment can have its catalog partition on a different database partition server. The catalog partition for a database is automatically created on the database partition server where the CREATE DATABASE command is run.
�catalog recovery area (CRA): An entry-sequenced data set (ESDS) that exists on each volume owned by a recoverable catalog, including the volume on which the catalog resides. The CRA contains copies of the catalog's records and can be used to recover a damaged catalog.
�Catalog Search Interface: In z/OS, a particular application programming interface (API) that allows programs written in assembler or a high-level language to read information from a catalog.
�catalog table: (1) A table that is automatically created in the DB2 database catalog when a database is created. Catalog tables contain information about a database and its objects. See also catalog view.; (2) Any table in the DB2 catalog.
�catalog view: (1) In DB2 Database for Linux, UNIX, and Windows, a SYSCAT or SYSSTAT view on the catalog table.; (2) One of a set of views automatically created when a database is created. Catalog views contain information about the database and the objects in that database. Examples of information about the database are definitions of database objects and information about the authority that users have on these objects. See also catalog table.
�catch block: A block associated with a try block that receives control when an exception matching its argument is thrown. See also try block.
�catcher: A server that service personnel use to collect and retain status data that other machines, such as the TotalStorage Enterprise Storage Server (ESS), send to it. See also catcher telephone number.
�catcher telephone number: The telephone number that connects the ESS to the support-catcher server and enables the ESS to receive a trace or dump package. See also Remote Technical Assistance and Information Network, catcher.
�catch-up: (1) In a remote journal network, the process of replicating journal entries that existed in the journal receivers of the source journal before the remote journal was activated.; (2) 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.
�catch-up processing: In an RSR environment, the process by which tracked log data is used to make all recoverable resources (for example, shadow databases) current with those resources on the active IMS.
�catchup state: In high availability disaster recovery, a state in which the standby database might not have applied all logged operations that occurred on the primary database. In this state, the standby database retrieves and applies previously generated log data to synchronize with the primary database. There are two types of catchup states: local and remote.
�category: (1) A logical subset of volumes in a tape library. A category can be assigned by the library manager (for example, the insert category) or by the software (such as, the private or scratch categories).; (2) A word, phrase, or number used to group documents in a view.; (3) The recommended security specifications needed for both the CICS transaction definitions and the corresponding RACF profiles.; (4) An optional grouping of entities that are related in some way, such as messages or assets that relate to a particular application. See also message.; (5) A container used in a structure diagram to group elements based on a shared attribute or quality.
�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.
�category bean: A bean that logs information about content categories.
�category manager: A defined role in WebSphere Commerce that manages the category hierarchy by creating, modifying, and deleting categories. The category hierarchy organizes products or services offered by the store. The category manager also manages products, expected inventory records, vendor information, inventory, and return reasons.
�category page: A Web page in an online store that displays product categories. Category pages connect customers to child category pages or to products that belong to the selected category. See also child category.
�category tree: A hierarchy of categories. See also taxonomy.
�CAVM: See CICS availability manager.
�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.
�CBC: See cipher block chaining.
�CBD: See component-based development.
�CELL/B.E.: See Cell Broadband Engine.
�CBIC: See control blocks in common.
�CBJ: See Class Broker for Java.
�CBPDO: See Custom-built Product Delivery Option.
�CBR: See content based routing.
�CBS: See composite business service.
�CBX: See computerized branch exchange.
�CC: (1) See clearing channel.; (2) See change control.
�CCA: See Common Cryptographic Architecture.
�C-CAA: See C/370 common anchor area.
�CCB: (1) See command control block.; (2) See connection control block.; (3) See change control board.; (4) See conversation control block.
�CC-compatible SnapShot: See concurrent copy-compatible SnapShot.
�CCD (CCD table): See consistent-change-data table.
�CCD table (CCD): See consistent-change-data table.
�CCF: (1) See Common Connector Framework.; (2) See channel control function.
�CCH: See Comite de Coordination de l'Harmonisation.
�CCI: See Common Console Interface.
�CCITT: See Comit� consultatif international t�l�graphique et t�l�phonique.
�CCL: See common communication layer.
�CCMS: See Configuration Change Management System.
�CCP: See Communication Control Program.
�CCR: See channel command retry.
�CCS: (1) See coded character set.; (2) See Common Communications Support.; (3) See console communication service.; (4) See common channel signaling.
�CCSID: See coded character set identifier.
�CCSID 65534: See coded character set identifier 65534.
�CCSID 65535: See coded character set identifier 65535.
�CCTL: (1) See coordinator control subsystem.; (2) See coordinator controller.
�CCW: See channel command word.
�CD: See compact disc.
�CDB: (1) See communications database.; (2) See conversation data block.
�CDD: (1) See common data set descriptor record.; (2) See customization definition document.
�CDF: See channel definition file.
�CDK: See connector development kit.
�CDMA: See code division multiple access.
�CDNM session: See cross-domain network manager session.
�CDP: See Customization Definition Program.
�CDPD: See cellular digital packet data.
�CDR: (1) See call detail record.; (2) See critical design review.
�CD-R: See compact disc - recordable.
�CDRA: See Character Data Representation Architecture.
�CDRM: See cross-domain resource manager.
�CD-ROM: See compact-disc read-only memory.
�CDRSC: See cross-domain resource.
�CDS: (1) See Cell Directory Service.; (2) See class definition statement.; (3) See couple data set.; (4) See control data set.
�CDSA: See CICS dynamic storage area.
�CDS clerk: The software that provides an interface between client applications and Cell Directory Service (CDS) servers.
�CDS control program (CDSCP): In the Distributed Computing Environment (DCE), a program that Cell Directory Service (CDS) administrators use to control CDS servers and clerks.
�CDSCP: See CDS control program.
�CDSQ serialization: A technique that serializes DFSMShsm control data sets (CDSs) with a global enqueue product, such as global resource serialization (GRS).
�CDSR serialization: A technique that serializes DFSMShsm control data sets (CDSs) with volume reserves.
�CDT: See class descriptor table.
�CD table: See change-data table.
�CEB: See conditional end bracket.
�CEC: See central electrical complex.
�CECP: See country extended code page.
�CEEDUMP: A dump of the run-time environment for Language Environment and the member language libraries. Sections of the dump are selectively included, depending on options specified on the dump invocation. This is not a dump of the full address space, but a dump of storage and control blocks that Language Environment and its members control.
�CEI: See Common Event Infrastructure.
�CEI event: An event generated over the Common Event Infrastructure (CEI) and logged in a CEI data store.
�cell: (1) In a multidimensional clustering table, a unique combination of dimension values. Physically, a cell is made up of blocks of pages whose records all share the same values for each dimension column.; (2) A group of managed processes that are federated to the same deployment manager and can include high-availability core groups.; (3) In asynchronous transfer mode (ATM), a medium access control (MAC) protocol data unit (PDU) of fixed size.; (4) A logical grouping of users, computers, data, and other resources that share either a common purpose or a common level of trust.; (5) A single cartridge location within an Automated Tape Library Dataserver (ATLDS). See also rack number, slot.; (6) One or more processes that each host runtime components. Each has one or more named core groups.
�Cell Broadband Engine (CELL/B.E.): A breakthrough microprocessor with unique capabilities for applications requiring video, 3D graphics, or high-performance computation for imaging, security, visualization, health care, surveillance, and more. Based on the Power Architecture, a choreographed high-bandwidth memory architecture, and multicore technology, the Cell Broadband Engine has been shown to accelerate some algorithms to many times the speed of a traditional microprocessor.
�Cell Broadband Engine processor: A single-chip multiprocessor consisting of one or more PowerPC Processor Elements (PPEs) and one or more (typically eight) Synergistic Processor Elements (SPEs). It is used for distributed processing and media-rich applications. See also PowerPC Processor Element, Synergistic Processor Element.
�Cell Directory Service (CDS): A Distributed Computing Environment (DCE) component that manages a database of information about the resources within a cell. See also Global Directory Service.
�cell-relative name: See local name.
�cell-scoped binding: A binding scope where the binding is not specific to, and not associated with any node or server. This type of name binding is created under the persistent root context of a cell.
�cellular digital packet data (CDPD): A standard for transmitting data over a cellular network that places the data in digital electronic envelopes and sends it at high speed through underused radio channels or during pauses in cellular phone conversations.
�Cellular Telecommunications Industry Association (CTIA): A trade group that represents cellular, PCS, and enhanced specialized mobile radio carriers.
�Celsius: Pertaining to a thermometric scale at which water boils at 100 degrees and freezes at 0 degrees in standard atmospheric pressure.
�central data warehouse: The component of Tivoli Enterprise Data Warehouse that contains the cleansed historical data. Data in the central data warehouse is derived from operational data, although operational data is not stored directly in the central data warehouse.
�central data warehouse ETL: In Tivoli Enterprise Data Warehouse, the extract, transform, and load (ETL) process that reads the data from the operational data stores of the application that collects it (for example, a log file, a Tivoli Inventory repository, or a Tivoli Enterprise Console database), verifies the data, makes the data conform to the Tivoli Enterprise Data Warehouse schema, and places the data into the central data warehouse. See also data mart ETL.
�central directory architecture: Directory architecture in a Domino domain in which some servers store configuration directories and use primary Domino Directories on remote servers for lookups.
�central electrical complex (CEC): See central processor complex.
�central institution: An organization that performs clearing, netting, or settlement for a financial community. Typically, but not necessarily, a national or central bank.
�centralized control: A type of control in which in which all the primary station functions of the data link are centralized in one data station. See also independent control.
�centralized directory service: In OSI, a method of organizing directory services so that one node provides directory service for other nodes. OSI Communications Subsystem supports only centralized directory service.
�centralized processing: In CICS, processing in which the application is processed on a central processor, which users access using a terminal.
�centralized script management: The process of managing scripts centrally in the OS/390 library and sending them to the fault-tolerant agents to be run.
�central office (CO): A telephone switching system that connects customer-premise business and subscriber lines to other customer lines or trunks, both locally or remotely. A central office is located on the edge of the telephone service provider's network, rather than on a customer's premises.
�central processing unit (CPU): The part of a computer that includes the circuits that control the interpretation and running of instructions.
�central processor (CP): The part of the computer that contains the sequencing and processing facilities for instruction execution, initial program load, and other machine operations.
�central processor complex (CPC): A physical collection of hardware that consists of main storage, one or more central processors, timers, and channels.
�central registry: A component of the License Use Management network topology. A server's database which logs requests for licenses, upgrades for licenses, and journals all license activity in a tamper-proof auditable file.
�central resource registration: A process in which an APPN network node sends information about itself and its client end nodes to a central directory server.
�central service: In MERVA, a service that uses resources that either require serialization of access, or are only available in the MERVA nucleus.
�central site: In a network of systems, the system licensed to receive program temporary fixes (PTFs) and distribution media from IBM. This system is also used to provide problem handling support to other systems in a network. In a distributed data processing network, the central site is usually defined as the focal point in a communications network for alerts, application design, and remote system management tasks such as problem management.
�central storage: Storage that is an integral part of the processor unit. Central storage includes both main storage and the hardware system area. UNIX-experienced users refer to central storage as memory.
�central system: A single system that handles all of the communications to an endpoint system.
�CEPT: See Conference Europeenne des Administrations des Postes et Telecommunications.
�CERN: See Conseil Europ�en pour la Recherche Nucl�aire.
�certificate: In computer security, a digital document that binds a public key to the identity of the certificate owner, thereby enabling the certificate owner to be authenticated. A certificate is issued by a certificate authority and is digitally signed by that authority.
�certificate authority (CA): A trusted third-party organization or company that issues the digital certificates used to create digital signatures and public-private key pairs. The certificate authority verifies the identity of the individuals who are granted the unique certificate.
�certificate authority certificate (CA certificate): In computer security, a digital document that identifies an organization that issues certificates.
�certificate revocation list (CRL): A list of certificates that have been revoked before their scheduled expiration date. Certificate revocation lists are maintained by the certificate authority and used, during a Secure Sockets Layer (SSL) handshake to ensure that the certificates involved have not been revoked.
�certificate set: A set of primary and secondary certificates that can be associated to a participant connection.
�certificate store: The Windows name for a key repository.
�certification: A process that creates special signed messages called certificates, which state that a particular public key is associated with a particular user or server name.
�certifier ID: A file that generates an electronic "stamp" that indicates a trust relationship. It is analogous to the device used to stamp passports--it verifies that a person is trusted by that stamping authority.
�CES: See connection event sequence.
�CF cache structure: See coupling facility cache structure.
�CFIOP: See combined function IOP.
�CF key: See command function key.
�CF lock structure: See coupling facility lock structure.
�CFM: See Configuration File Manager.
�CF message: Confirmed message. When a sending MERVA Link system is informed of the successful delivery of a message to the receiving application, it routes the delivered application messages as CF messages, that is, messages of class CF, to an ACK wait queue or to a complete message queue.
�CFRM: See Coupling Facility Resource Manager.
�CFRM policy: See Coupling Facility Resource Management policy.
�CFS: See continuous-forms stacker.
�CFStruct: A WebSphere MQ object used to describe the queue manager's use of a Coupling Facility list structure
�CGI: See Common Gateway Interface.
�CGI program: See CGI script.
�CGI script: A computer program that runs on a Web server and uses the Common Gateway Interface (CGI) to perform tasks that are not usually done by a Web server (for example, database access and form processing).
�CGU: See character generator utility.
�chain: (1) In DFU, a way to change from one display format to another after the user signals that the first display format was completed.; (2) In RPG, an operation code that reads input records identified by specified relative record numbers or keys.; (3) A group of logically linked records that are transferred over a communications line.; (4) A group of request units delimited by begin-chain and end-chain. Responses are always single-unit chains.; (5) The name of a channel framework connection that contains an endpoint definition.
�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.
�chaining: (1) A method of storing records in which each record belongs to a list or group of records and has a linking field for tracing the chain.; (2) In the Distributed Computing Environment (DCE), a mode of interaction optionally used by a directory system agent (DSA) that cannot perform an operation by itself. The DSA chains by invoking the operation in another DSA and then relaying the outcome to the original requester.
�Challenge Handshake Authentication Protocol (CHAP): An authentication protocol that protects against eavesdropping by encrypting the user name and password. See also Password Authentication Protocol.
�challenge-response authentication: An authentication method that requires users to respond to a prompt by providing information to verify their identity when they log in to the system. For example, when users forget their password, they are prompted (challenged) with a question to which they must provide an answer (response) in order to either receive a new password or receive a hint for specifying the correct password.
�chameleon schema: A schema that inherits a target namespace from a schema that includes the chameleon schema.
�change accumulation (CA): (1) The process of creating a compacted version of one or more IMS log data sets by eliminating records not related to recovery, and by merging multiple changes to a single segment into a single change.; (2) 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 aggregate table: In SQL replication, a type of replication target table that contains data aggregations that are based on the contents of a CD table. See also base aggregate table.
�change authority: An object authority that allows a user to perform all operations on the object except those limited to the owner or controlled by object existence authority, object management authority, object alter authority, and object reference authority. The user can add, change, and delete entries in an object, or read the contents of an entry in the object. Change authority combines object operational authority and all the data authorities.
�change bar: A character used in the left margin to indicate that a document line is changed.
�change-capture replication: The process of capturing changes that are made to a replication source table and applying them to a replication target table. See also full refresh.
�change control (CC): The use of change management commands for the installation or removal of software or data.
�change control administrator: A person responsible for software distribution and change control activities.
�change control board (CCB): A group of individuals on a project team that ensures that every change request is properly considered and that any work required is authorized and coordinated.
�change control client: A workstation that (a) receives software and data files from its change control server and (b) installs and removes software and data files as instructed by its change control server.
�change control domain: A change control server and its change control clients.
�change control server: A system that controls and tracks the distribution of software and data files to other workstations.
�change-data table (CD table): In SQL replication, a replication table on the Capture control server that contains changed data for a replication source table. See also synchpoint.
�change-direction protocol: In SNA, a data flow control protocol in which the sending logical unit (LU) stops 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.
�changed subfile record: A subfile record into which the work station user has entered data, or a subfile record for which a write or change operation was issued with the DDS keyword SFLNXTCHG or DSPATR(MDT) in effect.
�change history: The list of audit entries recorded for a resource.
�change log: (1) For directory shadowing, a record of changes made to directory entries, departments, and locations for the purpose of sending only the updates and not the entire directory to collecting systems.; (2) The area of the checkpoint data set that contains the specific control blocks changed by the last member of the multi-access spool configuration to own the checkpoint data set.
�change-managed relationship: A relationship between two artifacts. A change to either artifact affects the relationship. See also suspect relationship state.
�change management: (1) The process of planning (for example, scheduling) and controlling (for example, distributing, installing, and tracking) software changes over a network.; (2) The process of controlling and tracking modifications to artifacts. See also scope management.; (3) The process of planning for and executing changes to configuration items in the information technology environment.
�change manager: The deployment management component that decomposes aggregated installable unit (IUs) and coordinates the change management operations across the hosting environments. See also aggregated installable unit, hosting environment.
�change number of sessions (CNOS): An internal transaction program that regulates the number of parallel sessions between the partner LUs with specific characteristics.
�change record: The identification of a difference to a data center device made outside of Tivoli Provisioning Manager. For example, if the IP address of a server is manually changed at the server, the change is identified during discovery and a record is created.
�change request (CR, CRQ): (1) In System Manager, an instance of a change request description that has been submitted to run or is running. A change request is uniquely identified by the change request name and a sequence number.; (2) A request from a stakeholder to change an artifact or process. See also defect, enhancement request.; (3) A request to change some aspect of the project, project plan, activity definition or document.
�change request description (CRQD): An i5/OS object that describes a change to be made to the computing environment. The object, which is maintained only at the central site system or systems, consists of a list of activities that describe the steps needed to make the change.
�change set: A list of versions of elements that are associated with a Unified Change Management (UCM) activity.
�change unit: A block of information that is created when a task is created that will affect one or more configuration items. The Forward Schedule of Change displays information about the change window, the impact of the change on services in the environment, and other information that is included in a change unit.
�channel: (1) A link along which signals can be sent, such as the channel that handles the transfer of data between processor storage and local peripheral equipment. See also trunk.; (2) A specialized Web application within a portal to which a user can subscribe.; (3) An entry point to the Web services gateway that carries requests and responses between Web services and the gateway.; (4) The means of distribution of a company's products. Examples are e-commerce and physical stores.; (5) In mainframe computing, the part of a channel subsystem that manages a single I/O interface between a channel subsystem and a set of control units.; (6) A mode by which a business service is consumed by a subscriber.; (7) A communication path through a chain to an endpoint.
�channel action: A business function that can be issued on a channel. Channel actions are role specific and an authorization policy makes it possible to control which role can perform which action in a channel.
�channel adapter (CA): A communication controller hardware unit that is used to attach the communication controller to a host channel.
�channel associated signaling (CAS): A method of communicating telephony supervisory or line signaling (on-hook and off-hook) and address signaling on T1 and E1 digital links. See also common channel signaling.
�channel-attached: (1) Pertaining to the attachment of devices directly by input/output channels to a host processor.; (2) Pertaining to devices attached to a controlling unit by cables, rather than by telecommunication lines. See also link-attached.
�channel bank: A device that converts an analog line signal to a digital trunk signal.
�channel code: A number from 1 to 12 that identifies a position in a forms-control buffer or a page definition.
�channel command retry (CCR): In mainframe computing, the protocol used between a channel and a control unit that enables the control unit to request that the channel reissue the current command.
�channel command word (CCW): In zSeries systems, an 8-byte command issued to the channel subsystem by a central processor and operating asynchronously with the issuing processor.
�channel control function (CCF): A program to move messages from a transmission queue to a communication link, and from a communication link to a local queue, together with an operator panel interface to allow the setup and control of channels.
�channel counter: A counting device that identifies how many pages have been successfully received.
�channel definition file (CDF): A file containing communication channel definitions that associate transmission queues with communication links.
�channel event: An event reporting conditions detected during channel operations, such as when a channel instance is started or stopped. Channel events are generated on the queue managers at both ends of the channel.
�channel exit program: A user-written program that is called from one of a defined number of places in the processing sequence of a message channel agent (MCA).
�channel framework: A common model for connection management, thread usage, channel management, and message access within WebSphere Application Server.
�channel group: A group of channels defined for a particular MERVA Liquidity Manager installation. The channels in a group need not all use the same currency.
�channel initiator: A component of WebSphere MQ distributed queuing that monitors the initiation queue to see when triggering criteria have been met and then starts the sender channel.
�channel interface: The circuitry in a storage control that attaches storage paths to a host channel.
�channel link: A System/390 I/O channel-to-control-unit interface that has an SNA network address. A channel link can be a subarea link, a peripheral link, a LEN link, or an APPN link.
�channel listener: A component of WebSphere MQ distributed queuing that monitors the network for a startup request and then starts the receiving channel.
�channel manager: A defined role in WebSphere Commerce that manages the channel hub, as well as the distributors and resellers associated with that hub, including creating and importing distributor and reseller contracts.
�channel number: The identifying number assigned to a licensed channel on the T1 or E1 trunk that connects DirectTalk to the switch, channel bank, or channel service unit.
�channel path: In mainframe computing, the interconnection between a channel and its associated control units.
�channel process (CHP): (1) The AIX process that executes the logic of the state table; each active caller session has one active channel process.; (2) In WebSphere Voice Server, the system process that manages call flow.
�channel program: A sequence of one or more channel command words (CCWs) issued to one device.
�channel service unit (CSU): (1) An American Telephone and Telegraph (AT&T) unit that is part of the AT&T nonswitched digital data system.; (2) A device used to connect a digital phone line to a multiplexer, a channel bank, or directly to another device producing a digital signal. A CSU performs certain line-conditioning and equalization functions, and responds to loopback commands sent from the central office (CO).
�channel station: In certain printers, a page-counting device that counts the number of pages queued for printing.
�channel status word (CSW): An area in storage used to indicate the status of a device and channel involved in an I/O operation.
�channel subsystem (CSS): A collection of subchannels that directs the flow of information between I/O devices and main storage, relieves the processor of communication tasks, and performs path management functions.
�channel-subsystem image: In mainframe computing, the logical functions that a system requires to perform the function of a channel subsystem. With ESCON multiple image facility (EMIF), one channel-subsystem image exists in the channel subsystem for each logical partition (LPAR). Each image appears to be an independent channel-subsystem program, but all images share a common set of hardware facilities.
�channel switch: The rerouting of an outgoing and not yet scheduled message to another clearing channel.
�channel-to-channel (CTC): Pertaining to the physical connection or the interaction of two devices.
�channel-to-channel adapter (CTC adapter): A device for connecting two channels on the same processor or on different processors.
�CHAP: See Challenge Handshake Authentication Protocol.
�CHAPS: See Clearing House Automated Payment System.
�CHAPS-Euro: The Euro-denominated RTGS payment system operated by the CHAPS Clearing Company Ltd. and comprising a network, central message handling software, elements of members' interfaces to the network, and the Bank of England's central interface.
�character: (1) Any symbol that can be entered on a keyboard, printed, or displayed. For example, letters, numbers, and punctuation marks are all characters.; (2) In a computer system, a member of a set of elements that is used for the representation, organization, or control of data. See also glyph.; (3) A sequence of one or more bytes representing a single graphic symbol or control code.
�character array: A named list or table of character data.
�character box: The area that completely contains the character pattern.
�character cell: In the GDDM function, the imaginary box whose boundaries govern the size, orientation, and spacing of individual characters to be displayed on a work station.
�character class: A named set of characters sharing an attribute associated with the name of the class. The classes and the characters that they contain are dependent on the value of the LC_CTYPE category in the current locale.
�character code: In System i Access, an ASCII or EBCDIC value assigned to the symbols or functions that are used by a computer.
�character-coded: See unformatted.
�character constant: (1) The actual character value (a symbol, quantity, or constant) in a source program that is itself data, instead of reference to a field that contains the data. See also numeric constant.; (2) In the C language, a character or an escape sequence enclosed in quotation marks.; (3) A constant value whose data attribute is character.
�character conversion: The process of changing data from one character coding representation to another.
�character conversion table: A table that converts one or more characters to alternative characters using hexadecimal encoding for the character sets. The character sets are defined in code pages.
�character data: (1) Data in the form of letters and special characters, such as punctuation marks.; (2) Data that has an associated coding representation that defines how to interpret each specific pattern of bits that are grouped into one or more bytes.
�Character Data Representation Architecture (CDRA): An IBM architecture that defines a set of identifiers, resources, services, and conventions to achieve consistent representation, processing, and interchange of graphic character data in heterogeneous environments.
�character data representation identifier: A tag that is used to achieve data integrity. The Character Data Representation Architecture specifies that you should tag all character data as it flows through the system. You can tag using a short-form or a long-form identifier. A coded character set identifier (CCSID) is an example of a character data representation identifier.
�character encoding: The mapping from a character (a letter of the alphabet) to a numeric value in a character code set. For example, the ASCII character code set encodes the letter "A" as 65, while the EBCIDIC character set encodes this letter as 43. The character code set contains encodings for all characters in one or more language alphabets.
�character entity reference: A character string of the form &#xdddd or &#dddd, where dddd is the hexadecimal or decimal equivalent of a character's Unicode code point. For example, &#x003E and &#0062 are both character entity references to the > (greater-than) sign.
�character expression: A character constant, a simple character variable, an element of a character array, a character-valued function reference, a substring reference, or a sequence of the above separated by the concatenation operator and parentheses.
�character field: An area that is reserved for information that can contain any of the characters in the character set. See also numeric field.
�character format: In REXX, a format that is used in the REXX conversion functions to indicate that data is in a textual form as opposed to machine-readable form.
�character generator utility (CGU): A function of the Application Development ToolSet feature that is used to define and maintain user-defined double-byte characters and related sort information.
�character grid: In Business Graphics Utility, an invisible network of uniformly spaced horizontal and vertical lines covering the chart area. Used by the Business Graphics Utility to determine the physical dimensions of the chart and the placement of the data on it.
�character grid unit: In Business Graphics Utility, the distance between two adjacent horizontal or vertical lines on a character grid.
�character group: Any number of character graphics and character properties.
�character ID: See character identifier.
�character identifier (character ID): (1) The standard identifier for a character, regardless of its style. For example, all uppercase A's have the same character identifier.; (2) On a system, a 4-byte binary value. The value is a concatenation of the graphic character set global identifier followed by the code page global identifier. For example, the character identifier for German (feature 2929) is 00697 00273.
�character increment: The distance from the character reference point to the character escapement point. Character increment is the sum of the A-space, B-space, and C-space. Usually the distance between the current print position and the next print position.
�character key: A keyboard key that allows the user to type into the system the character shown on the key.
�character large object (CLOB): (1) A data type that contains a sequence of characters (single-byte, multibyte, or both) that can range in size from 0 bytes to 2 gigabytes less 1 byte. In general, CLOB values are used whenever a character string might exceed the limits of the VARCHAR type. See also large object.; (2) A character string that contains single-byte characters with an associated code page.
�character normalization: A process in which the variant forms of a character, such as capitalization and diacritical marks, are reduced to a common form.
�character operator: A symbol representing an operation to be performed on character data, such as concatenation (joining the data or fields) in the control language (CL).
�character printer: A device that prints a single character at a time. See also line printer.
�character rotation: The alignment of a character with respect to its character baseline, measured in degrees in a clockwise direction. See also orientation.

�character set: (1) A defined set of characters with no coded representation assumed that can be recognized by a configured hardware or software system. A character set may be defined by alphabet, language, script, or any combination of these items.; (2) A set of binary codes that represent specific text characters.
�character set identifier 65534: The character set identifier (CCSID) that is used to show that a CCSID value for data at this level of processing is not relevant. When CCSID 65534 ( FFFE ) is associated with data, a CCSID value for the data should be obtained from the tagged fields of elements that are at a lower level in the defined hierarchy. For example, a file has CCSIDs tagged for each individual field it contains. If the file is tagged with CCSID 65534, processing is based on the CCSIDs assigned to each individual field instead of the CCSID assigned to the file.
�character set identifier 65535: The character set identifier (CCSID) that is used to show that data associated with the CCSID should not be processed as coded-graphic-character data.
�character special file: A special interface file that provides access to an input or output device, which uses character I/0 instead of block I/0. See also block special file.
�characters per inch (cpi): The number of characters printed horizontally within an inch across a page.
�character string: (1) A sequence of consecutive characters that are treated as a unit.; (2) A sequence of bytes that represents bit data, single-byte characters, or a mixture of single-byte and multibyte characters.; (3) A contiguous sequence of characters terminated by and including the first null byte.
�character string delimiter: A character that is used to identify the beginning and the end of a character string.
�character type: A data type that consists of alphanumeric characters.
�character variable: (1) Character data whose value is assigned or changed while the program is running.; (2) In the C language, a data object whose value can be changed while a program is running and whose data type is a signed or unsigned character.
�charge-back account: An account used for tracking computing resource usage by business departments or projects. Examples of charge-back accounts are "Marketing Department" or "Summer catalog project."
�charge code: An accounting code that is used to register and categorize costs against project budgets.
�chart: A picture defined in terms of graphics primitives and graphics attributes.
�chart area: In the GDDM function, the part of the picture space in which a business chart is to be drawn.
�chart format: In Business Graphics Utility, an object containing chart characteristics, such as the chart type, chart heading, legend position, and so on. The chart format does not include the data values to be plotted. The system-recognized identifier for the object type is *CHTFMT.
�chart layout: In Business Graphics Utility, the arrangement of the various parts in the chart area and surrounding margins.
�chart series: A selection of a category of data that will be represented by a chart in a report. A chart can have multiple chart series to represent multiple types of data.
�CHASE: In SNA, a command used by the host system to determine when the secondary logical unit has finished processing all previously sent response units.
�chassis: The metal frame in which various electronic components are mounted.
�chassis detect-and-deploy profile: A profile that IBM Director automatically applies to all new BladeCenter chassis when they are discovered. The profile settings include management module name, network protocols, and static IP addresses. If Remote Deployment Manager (RDM) is installed on the management server, the chassis detect-and-deploy profile also can include deployment policies.
�chat: (1) The sending of typed messages between online meeting participants.; (2) In LearningSpace - Virtual Classroom session, the sending of typed messages between session participants. There are two types of chat: session chat, which allows a user to send messages to everyone in the session and private chat, which allows a user to send a message to an individual participant.
�chat transcript: A record of the typed messages between participants in a chat meeting.
�cheat sheet: An interface that guides users through the wizards and steps required to perform a complex task, and that links to relevant sections of the online help.
�check: The process of determining whether a component is appropriate or meets the necessary requirements. For example, an environment check verifies that the target systems contain the appropriate operating systems and software for an operation.
�check box: A square box with associated text that represents a choice. When a user selects the choice, the check box is filled to indicate that the choice is selected. The user can clear the check box by selecting the choice again, thereby deselecting the choice.
�CHECK clause: In SQL, an extension to the SQL CREATE TABLE and SQL ALTER TABLE statements that specifies a table check constraint.
�check condition: A restricted form of search condition used in check constraints.
�check constraint: A user-defined constraint that specifies the values that specific columns of a base table can contain. See also constraint.
�check digit: The far right number of a self-check field used to verify the accuracy of the field.
�checked-out version: A copy of a file that corresponds to a version of an element. See also version.
�check in: (1) In certain software configuration management (SCM) systems, to copy files back into the repository after changing them.; (2) To replace an inactive document, project WBS element, scope element, requirement or resource record (with its modifications) to its repository directory so that others can view it or modify it.
�checkin: The action that creates a new version of an element on any branch of its version tree.
�checkin screen: The screen identifying the host screen that should be active for a connection to be considered ready to be returned to the connection pool. If the application is not on the screen specified by the checkin screen, the connection will be discarded or recycled in attempt to return the connection to the host screen specified by the checkin screen. The checkin screen is only meaningful if connection pooling is specified for a connection.
�check integrity: The condition that exists when each row in a table conforms to the check constraints that are defined on that table.
�check out: (1) In certain software configuration management (SCM) systems, to copy the latest revision of a file from the repository so that it can be modified.; (2) To remove an active document, project WBS element, scope element, requirement or resource record from its repository directory in order to modify it. Only one individual may check out the same element at a time.
�check pending: (1) In DB2 for z/OS, a state into which a table can be put where only limited activity is allowed on the table and constraints are not checked when the table is updated.; (2) A state that occurs when data for a constraint cannot be verified as valid. A constraint could be either a referential constraint or a check constraint.; (3) A state of a table space or partition that prevents its use by some utilities and by some SQL statements because of rows that violate referential constraints, check constraints, or both.
�checkpoint: (1) 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.; (2) A point at which the database manager records internal status information on the log; the recovery process uses this information if the subsystem abnormally terminates.
�checkpoint data set: A local data set that contains Common Queue Server (CQS) system checkpoint information about a group of shared queues.
�checkpointing: The periodic copying of processing information to the checkpoint data set. Checkpointing ensures that information about in-storage job and output queues is not lost in the event of a hardware or software error.
�checkpoint reconfiguration: A process that allows a user to dynamically redefine checkpoint data-set specification for the JES multi-access spool (MAS) configuration.
�checkpoint reconfiguration dialog: An interactive form of a JES2 checkpoint reconfiguration that directs the reconfiguration process with replies to a series of WTOR messages.
�checkpoint restart: The process of resuming a job at a checkpoint within the job step that caused abnormal termination. The restart can be automatic or deferred. A deferred restart requires that the job be resubmitted. See also automatic restart, deferred restart, step restart.
�checkpoint/restart facility: A facility for restarting execution of a program at some point other than at the beginning, after the program was terminated due to a program or system failure. A restart can begin at a checkpoint or from the beginning of a job step, and uses checkpoint records to reinitialize the system.
�checkpoint size: In OSI X.400, the maximum amount of data (in units of 1024 bytes) that can be sent between two minor synchronization points. The checkpoint size is used by the X.400 reliable transfer server.
�checkpoint write: Any write to the checkpoint data set. A checkpoint write is a primary, intermediate, or final write that updates a checkpoint data set.
�checksum: (1) The sum of a group of data that is associated with a group of data and that is used for error detection.; (2) On a diskette, data written in a section for error detection purposes.
�checksum protection: (1) A function that protects data stored in an auxiliary storage pool from being lost because of the failure of a single disk. When checksum protection is in effect and a disk failure occurs, the system automatically reconstructs the data when the system program is loaded after the device is repaired. See also device parity protection, mirrored protection.; (2) In TCP/IP, the sum of a group of data associated with the group and used for error checking purposes.
�checksum set: Units of auxiliary storage defined in groups to provide a way for the system to recover data if a disk failure occurs when checksum protection is in effect.
�child: (1) In a generalization relationship, the specialization of another element, the parent.; (2) A node that is subordinate to another node in a tree structure. Only the root node is not a child.
�child activity: An activity that is launched during the processing of another activity, which becomes the parent activity. See also parent activity.
�child business object: A business object that is contained or referenced by another business object. When the full child business object is part of its parent's hierarchy, the child is contained by the parent. See also array attribute, foreign key attribute, single-cardinality attribute.
�child category: A category that is subordinate to another category in a hierarchy. See also category page, parent category.
�child class: A class that inherits instance methods, attributes, and instance variables directly from the parent class (also known as the base class or superclass), or indirectly from an ancestor class.
�child component: Optional second or lower level of a hierarchical item type. Each child component is directly associated with the level above it.
�child document: A document that inherits its values from another document (the parent document).
�child enclave: The nested enclave created as a result of certain commands being issued from a parent enclave. See also nested enclave, parent enclave.
�child lock: In explicit hierarchical locking, a lock that is held on a table, a page, a row, or a large object. Each child lock has a parent lock. See also parent lock.
�child node: A node within the scope of another node.
�child organizational entity: One or more further levels of organizational entities that exist beneath the parent organizational entity.
�child process: A process that is created by a parent process and that shares the resources of the parent process to carry out a request.
�child resource: A secured resource, either a file or library, that uses the user list of a parent resource. A child resource can have only one parent resource.
�child segment: In a database, any segment that is dependent on another segment above it (its parent) in the hierarchy.
�child UR: A unit of recovery (UR) cascaded from a parent UR in a cascaded transaction.
�child window: A window that appears within the border of its parent window (either a primary window or another child window). When the parent window is resized, moved, or destroyed, the child window also is resized, moved, or destroyed. However, the child window can be moved or resized independently from the parent window, within the boundaries of the parent window.
�choice: An option in a pop-up window or menu used to influence the operation of the system.
�CHP: See channel process.
�cHTML: See Compact Hypertext Markup Language.
�CI: (1) See control interval.; (2) See callable interface.; (3) See configuration item.
�CIB: See condition information block.
�CIC: (1) See Concurrent Image Copy.; (2) See circuit identification code.
�CICS: An IBM licensed program that provides online transaction-processing services and management for business applications.
�CICS attachment facility: A facility that provides a multithread connection to a DB2 database to allow applications that run in the CICS environment 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.
�CICS BTS: See business transaction services.
�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.
�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-DL/I router: 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 group: An i5/OS library containing the CICS resource definition for CICS tables.
�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 storage.
�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: CICS for HP-UX, CICS for Sun Solaris, TXSeries for AIX, TXSeries for HP-UX, and TXSeries for Solaris.
�CICS on System/390: A term used to refer generically to the products: CICS Transaction Server for z/OS, CICS for MVS/ESA, CICS Transaction Server for VSE/ESA, and CICS/VSE.
�CICS PD/MVS: See CICS Problem Determination/MVS.
�CICSplex: (1) A collection of related and connected CICS regions, which helps to address the inefficiencies in having multiple, full-function CICS systems processing a single OLTP workload. See also multiregion operation.; (2) The largest set of CICS regions, or systems, to be manipulated by CICSPlex SM as a single entity. CICS systems in a CICSplex being managed by CICSPlex SM do not need to be connected to each other.
�CICSPlex SM: See CICSPlex System Manager.
�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 user ID: The user IDassigned 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 run unit: A set of statically bound, dynamically bound, or both, modules that can be loaded by a CICS loader.
�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: A utility designed to detect potential causes of inter-transaction affinity and transaction-system affinity for those users planning to use dynamic transaction routing.
�CICS-value data area (CVDA): CICS-supplied values to certain data options on EXEC CICS commands.
�CICS VSAM Recovery: An IBM product that recovers lost or damaged Virtual Storage Access Method (VSAM) data.
�CICS Web interface: A collection of CICS resources supporting direct access to CICS transaction processing services from Web browsers.
�CID: (1) See communication identifier.; (2) See configuration, installation, and distribution.
�CIDF: See control interval definition field.
�CID methodology: An IBM-specified way to install and configure products on, or remove products from, remote workstations and hosts. Response files and redirected installation and configuration may be used by a CID-enabled product to eliminate or reduce user interaction with the CID-enabled product.
�CIDR: See Classless Inter-Domain Routing.
�CIF: (1) See common interchange file.; (2) See Customization Input File.
�CIFS: See Common Internet File System.
�CIM: See Common Information Model.
�CIM implementation: See Common Information Model implementation.
�CIM instrumentation: See Common Information Model instrumentation.
�CIM object manager (CIMOM): The common conceptual framework for data management that receives, validates, and authenticates the Common Information Model (CIM) requests from the client application. It then directs the requests to the appropriate component or service provider.
�CIMOM: See CIM object manager.
�CIM provider: See Common Information Model provider.
�CIM schema: See Common Information Model schema.
�CIM server: See Common Information Model server.
�CINET: See Common INET.
�CINIT: See control initiate.
�C interface: The interface that is defined at a level that depends on the variant of C standardized by ANSI.
�CIP: See commit in progress.
�cipher: A cryptographic algorithm used to encrypt data that is unreadable until converted into plain data with a predefined key.
�cipher block chaining (CBC): A method of reducing repetitive patterns in ciphertext by performing an exclusive-OR operation on each 8-byte block of data with the previously encrypted 8-byte block before it is encrypted.
�CipherSpec: The combination of encryption algorithm and hash function applied to an SSL message after authentication completes.
�cipher suite: (1) The combination of authentication, key exchange algorithm, and CipherSpec used by SSL for secure exchange of data.; (2) A set of ciphers.
�ciphertext: Data that has been encrypted. Ciphertext is unreadable until it has been converted into plaintext (decrypted) with a key.
�circuit: In fibre-channel technology, an established communication path between two ports, which consists of two virtual circuits capable of transmitting in opposite directions. See also link.
�circuit breaker: A switch that automatically interrupts an electric circuit because of an abnormal condition.
�circuit identification code (CIC): A 12-bit number that identifies a trunk and channel on which a call is carried.
�circuit-level gateway: In a firewall, a proxy server that redirects a client's request through the firewall to the intended server. See also application-level gateway.
�circuit switching: A process that, on demand, connects two or more data terminal equipment (DTEs) and permits the exclusive use of a data circuit between them until the connection is released.
�circular file: A type of file that appends data until full; subsequent incoming data overwrites the data starting at the beginning of the file.
�circular log: A database log in which records are overwritten if they are no longer needed by an active database. See also archive log.
�circular logging: In WebSphere MQ on UNIX systems and WebSphere MQ for Windows, the process of keeping all restart data in a ring of log files. See also linear logging.
�circular reference: A series of objects where the last object refers to the first object, which can cause the series of references to be unusable.
�circular traceability relationship: A relationship between a requirement and itself, or an indirect relationship that leads back to a previously traced-from node. Traceability relationships cannot have circular references.
�CISC: See complex instruction set computer.
�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.
�CIU: (1) See common interchange unit.; (2) See Customer Initiated Upgrade.; (3) See container installable unit.
�CKD: (1) See count-key-data device.; (2) See count key data.
�CL: (1) See control language.; (2) See Command Language.
�claim: A notification to DB2 for z/OS that an object is being accessed. A claim prevents a drain from occurring until the claim is released, which usually occurs at a commit point. See also drain, logical claim.
�claim class: A specific type of object access that can be one of the following types: cursor stability (CS), repeatable read (RR), or write.
�C language: A language used to develop application programs in compact, efficient code that can be run on different types of computers with minimal change.
�C++ language: An object-oriented high-level language that evolved from the C language. C++ takes advantage of the benefits of object-oriented technology such as code modularity, portability, and reuse.
�class: (1) An object that contains specifications, such as priority, maximum processing time, and maximum storage, to control the run-time environment of a job. The system-recognized identifier for the object type is *CLS.; (2) In the Distributed Computing Environment (DCE), a category into which objects are placed based on their purpose and internal structure.; (3) In object-oriented design or programming, a model or template that can be used to create objects with a common definition and common properties, operations, and behavior. An object is an instance of a class.; (4) In C++, a user-defined data type. A class data type can contain both data representations (data members) and functions (member functions).; (5) In RACF, a collection of defined entities (users, groups, and resources) with similar characteristics.; (6) An attribute that is related to a transaction code and a message region that is used to determine scheduling. See also message class, region class.; (7) A description of a set of objects that share the same attributes, operations, methods, relationships, and semantics. A class may use a set of interfaces to specify collections of operations that it provides to its environment. See also interface, object.; (8) The definition of an object within a specific hierarchy. A class can have properties and methods and can serve as the target of an association.; (9) A section of a module. A class can represent program text, that is, the instructions and data that are loaded into virtual storage during execution. Other classes, such as an external symbol dictionary (ESD) and a relocation dictionary (RLD), are required for binding and loading the program.; (10) In the AIX operating system, pertaining to the I/O characteristics of a device.
�class 0: See transport class 0.
�class 1: Service that provides a dedicated connection between two ports (also called connection-oriented service), with notification of delivery or nondelivery.
�class 1 terminal: (1) 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.; (2) A terminal for which the alternate IMS pre-opens backup sessions for the primary sessions that the active IMS opens; VTAM/NCP switches sessions from primary to backup at takeover.
�class 2: (1) Connectionless service between ports with notification of delivery or nondelivery.; (2) See transport class 2.
�class 2 terminal: (1) 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 .; (2) A terminal for which IMS in the alternate reestablishes service at takeover.
�class 3: In fibre-channel technology, connectionless service between ports without notification of delivery. Other than notification, the transmission and routing of class 3 frames is identical to that of class 2 frames.
�class 3 terminal: (1) 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.; (2) A terminal that communicate with XRF IMS but whose sessions are not automatically reestablished at takeover.
�class 4: See transport class 4.
�class A network: In Internet communications, a network in which the high-order (most significant) bit of the IP address is set to 0 and the host ID occupies the three low-order octets.
�class attribute: A value in a class object that controls the processing of routing steps in a job. These values include the run priority, time slice, eligibility for purge, default wait time, maximum processing unit time, and maximum temporary storage parameters.
�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 binding signature: A hexadecimal value that contains the class signature (obtained from the signature bank) and the inheritance level. The class binding signature is added to the Interface Definition Language (IDL) source file by the signature emitter.
�class B network: In Internet communications, a network in which the two high-order (most significant and next-to-most significant) bits of the IP address are set to 1 and 0, respectively, and the host ID occupies the two low-order octets.
�Class Broker for Java (CBJ): A Java tool that allows Java applications to run on a host system that does not have a graphical user interface (GUI). Because the IBM Developer Kit for Java Remote Abstract Window Toolkit is not recommended for complex graphics or highly interactive operations, CBJ for high-performance GUI services can be used.
�class C network: In Internet communications, a network in which the two high-order (most significant and next-to-most significant) bits of the IP address are both set to 1 and the next high-order bit is set to 0. The host ID occupies the low-order octet.
�class condition: In COBOL, a condition that specifies the character content of a data item as all alphabetic or all numeric.
�class definition statement (CDS): A statement that specifies (a) the mapping of incoming events to classes and (b) the values assigned to event attributes.
�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.
�class diagram: A diagram that shows a collection of declarative (static) model elements, such as classes, types, and their contents and relationships. See also object diagram.
�class F: Connectionless service for inter-switch control traffic, which provides notification of delivery or nondelivery between two expansion ports (E_ports).
�class file: A compiled Java source file.
�class hierarchy: The relationships between classes that share a single inheritance.
�classic command: A supported non-IMSplex command. A classic command generally requires a leading slash, for example, /DBRECOVERY.
�classification: In the Reusable Asset Specification (RAS), a major section of an asset providing classification schemas and descriptors that classify an asset for searching.
�classification rule: A rule used by the workload manager component of z/OS to assign a service class.
�classifier: (1) In QoS, a control function that selects packets according to the content within the packet headers.; (2) A mechanism that describes behavioral and structural features. Classifiers include interfaces, classes, data types, and components.; (3) A specialized attribute used for grouping and color-coding process elements.
�class key: One of the C++ keywords: class, struct, and union.
�Classless Inter-Domain Routing (CIDR): A method for adding class C Internet Protocol (IP) addresses. The addresses are given to Internet Service Providers (ISPs) for use by their customers. CIDR addresses reduce the size of routing tables and make more IP addresses available within organizations.
�class library: In object-oriented programming, a collection of prewritten classes or coded templates, any of which can be specified and used by a programmer when developing an application.
�class loader: Part of the Java virtual machine (JVM) that is responsible for finding and loading class files. A class loader affects the packaging of applications and the runtime behavior of packaged applications deployed on application servers.
�class mask: A network mask that is derived solely on the basis of the network class of an Internet Protocol (IP) address.
�class method: (1) A method that creates class instances.; (2) In Java, a method that is called without referring to a particular object. Class methods affect the class as a whole, not a particular instance of the class. See also instance method.
�class-name: In COBOL, a user-defined word defined in the SPECIAL-NAMES paragraph of the Environment Division that assigns a name to the proposition, for which a truth value can be defined, to verify that the content of a data item consists exclusively of those characters listed in the definition of the class-name.
�class name: A unique identifier of a class type that becomes a reserved word within its scope.
�class object: An object that identifies the run attributes of a job. The system-recognized identifier for the object type is *CLS.
�class of service (COS): (1) A VTAM term for a list of routes through a network, arranged in an order of preference for their use.; (2) A set of link and node characteristics, associated with a session or a set of sessions, that determine the route that is selected for the sessions through an APPN network.; (3) A set of characteristics (such as route security, transmission priority, and bandwidth) used to construct a route between session partners. The class of service is derived from a mode name specified by the initiator of a session.; (4) In fibre-channel technology, a specified set of delivery characteristics and attributes for frame delivery.
�class-of-service description: A system object created for Advanced Peer-to-Peer Networking (APPN) support that provides the information required to assign relative priority to the transmission groups and intermediate routing nodes for an APPN session. The system-recognized identifier for the object type is *COSD.
�CLASSPATH: In the execution environment, a variable that specifies the directories in which to look for class and resource files. See also class path.
�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. See also CLASSPATH.
�class-responsibility collaborators: A technique in object-oriented development to define what objects should do in the system (their responsibilities), and identify other objects (the collaborators) that are involved in fulfilling these responsibilities.
�class scope: The scope of C++ class members. See also namespace scope.
�class signature: A hexadecimal value obtained from a server and placed in a signature bank on the workstation. The signature bank uniquely identifies an Interface Definition Language (IDL) interface. Class signatures are added to the IDL source file by the signature emitter.
�class statistics: Statistical information that includes information such as the number of instances of the class in the application, the CPU time spent in that class, the number of calls made to the class, and so on.
�class template: A blueprint describing how a set of related C++ classes can be constructed.
�class template declaration: A class template declaration introduces the name of a class template and specifies its template parameter list. A class template declaration may optionally include a class template definition.
�class template definition: A definition that describes various characteristics of the class types that are its specializations. These characteristics include the names and types of data members of specializations, the signatures and definitions of member functions, accessibility of members, and base classes. See also base class.
�class transition: A change in an object's management class or storage class when an event occurs that brings about a change in an object's service level or management criteria. Class transition occurs during a storage management cycle.
�clause: (1) A set of consecutive character strings that specify a characteristic of an entry. There are three types of clauses: data, environment, and file.; (2) The fundamental grouping of REXX syntax. A clause is composed of zero or more blanks, a sequence of tokens, zero or more blanks, and the semicolon delimiter.; (3) In SQL, a distinct part of a statement in the language structure, such as a SELECT clause or a WHERE clause.
�CLAUTH: See class authority.
�CLAW: See Common Link Access to Workstation.
�CLB: See Communication Line Block.
�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.
�cleanse: (1) To transform the data extracted from operational systems to make it usable by a data warehouse.; (2) To ensure that all values in a data set are consistent and correctly recorded.
�cleanup: In SNA products, a network services request, sent by a system services control point (SSCP) to a logical unit (LU), that causes a particular LU-LU session with that LU to be ended immediately without requiring the participation of either the other LU or its SSCP.
�cleanup interval: The length of time to wait before removing obsolete data.
�ClearCase administrators group: A Windows domain group whose members have superuser access to ClearCase objects.
�ClearCase registry: A network service that allows programs to access versioned object bases (VOBs) and views by name instead of network path.
�clear-confirmation packet: In X.25 communications, a packet transmitted by the DTE to inform the DCE that a call has been cleared.
�clear indication packet: In X.25 communications, a call supervision packet that a data circuit-terminating equipment (DCE) transmits to inform a data terminal equipment (DTE) that a call has been cleared.
�clearing channel (CC): A payment system in a settlement bank that originates, schedules, disperses, and accounts for payments. Examples are CHAPS-Euro, Euro1, and RTGSplus. Each clearing channel has a corresponding S.W.I.F.T. service code.
�clearinghouse: In the Distributed Computing Environment (DCE), a collection of directory replicas on one Cell Directory Service (CDS) server. A clearinghouse takes the form of a database file. See also control access.
�Clearing House Automated Payment System (CHAPS): A same-day, guaranteed value payment system operated by the CHAPS Clearing Company Ltd.
�clearing system: See clearing channel.
�clear key encryption: Any type of encryption key not protected by encryption under another key.
�clear message: A message displayed by DirectTalk to tell the operator that a red or yellow error message has been cleared.
�clear request packet: A call supervision packet transmitted by a data terminal equipment (DTE) to ask that a call be cleared.
�cleartext
�cleartool: The primary command-line interface to ClearCase and ClearCase LT version-control and configuration management software.
�clerk: (1) In the DCE Distributed Time Service (DTS), a software component that synchronizes the clock for its client system by requesting time values from servers, computing a new time from the values, and supplying the computed time to client applications.; (2) In the DCE Cell Directory Service (CDS), a software component that receives CDS requests from a client application, ascertains an appropriate CDS server to process the requests, and returns the results of the requests to the client application.
�CLI: (1) See Call Level Interface.; (2) See command-line interface.
�C library: A system library that contains common C language subroutines for file access, string operations, character operations, memory allocation, and other functions.
�C++ library: A system library that contains common C++ language subroutines for file access, memory allocation, and other functions.
�CLI bundle: In Tivoli Kernel Services, a software object that implements the behavior of commands for a given component.
�click: To press and release a mouse button without moving the pointer off the choice.
�clickstream: In Web advertising, the sequence of clicks or pages requested as a visitor explores a Web site.
�Clickstream Engine: The Macromedia LikeMinds Personalization Server component that accesses transaction information and generates recommendations based on users' shopping behavior as they navigate a Web site. WebSphere Commerce generates events based on shopping behavior, including viewing a product detail page and adding items to a shopping cart or wish list. These events are forwarded to the Clickstream Engine.
�clickthrough rate: In Web advertising, the number of clicks on an ad on an HTML page as a percentage of the number of times that the ad was downloaded with a page. See also impression.
�Click-to-Action (C2A): A method for implementing cooperative portlets, whereby users can click an icon on a source portlet to transfer data to one or more target portlets. See also cooperative portlets, wire.
�CLI client: In Tivoli Kernel Services, the code that interprets a command line request and invokes the appropriate CLI bundle in the appropriate ORB. The CLI client in Tivoli Kernel Services is the wcmd command.
�client: (1) A software program or computer that requests services from a server. See also server, host.; (2) A runtime component that provides access to queuing services on a server for local user applications. The queues used by the applications reside on the server. See also WebSphere MQ client.; (3) A classifier that requests a service from another classifier. See also association.
�Client Access: See System i Access for Windows.
�client API: The interface used by client applications to invoke services in CICS using the facilities of the Client daemon. See also external call interface, external security interface.
�client application: (1) An application written with the Content Manager APIs to customize a user interface.; (2) An application written with object-oriented or Internet APIs to access content servers from Information Integrator for Content.; (3) An application, running on a workstation and linked to a client, that gives the application access to queuing services on a server.; (4) A user application, written in a supported programming language other than Java, that communicates directly with the Client daemon.; (5) A storage management program that initiates Common Information Model (CIM) requests to the CIM agent for the device.
�Client Application for Windows: A complete object management system provided with Content Manager and written with Content Manager APIs. It supports document and folder creation, storage, and presentation, processing, and access control.
�client application thread: In DCE remote procedure call (RPC), a thread executing client application code that makes one or more RPCs.
�client certificate: See certificate.
�client connection channel type: The type of MQI channel definition associated with a WebSphere MQ client. See also server connection channel type.
�client context: In the Distributed Computing Environment (DCE), the state within a Remote Procedure Call (RPC) server generated by a set of remote procedures and maintained across a series of calls for a particular client.
�Client daemon: A daemon that manages network connections to CICS servers. It processes ECI, EPI, and ESI requests, sending and receiving the appropriate flows from the CICS server to satisfy the application requests. The Client daemon (process cclclnt) exists only on distributed platforms.
�client domain: The set of drives, file systems, or volumes that the user selects to back up or archive using the backup-archive client.
�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 logical partition: A logical partition that uses the I/O resources of another logical partition, for example, a logical partition that uses the resources of a Virtual I/O Server logical partition or an i5/OS logical partition.
�client message: A message from a client application that is to be sent via a network to its destination, or a message that is routed to a client application to acknowledge the receipt of a client message by a network.
�client migration: In storage management, the process of copying a file from a client node to server storage and replacing the file with a stub file on the client node. The space management attributes in the management class control this migration.
�client node: In a single system image (SSI), a WebSphere Voice Response system that handles interactions with callers. A client node must have a telephony connection. It does not store application or voice data; it gets data from the server node of the SSI.
�client process: A process that requests services from a server process. See also server process.
�client profile: A profile that is used to configure clients using the Import function in the Configuration Assistant. The client profile can contain database connection information, client settings, and CLI or ODBC common parameters.
�client program: (1) A program that uses a C++ class.; (2) In dynamic routing the application program, running in the requesting region, that issues a remote link request.; (3) In the client/server model, the front-end transaction.
�client proxy: An object on the client side of a network connection that provides a remote procedure call interface to a service on the server side.
�client reroute: A method that allows a client application, upon the loss of communication with a database server and the predefinition of an alternative server, to continue working with the original database server or the alternative server with only minimal interruption of the work.
�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.
�client state manager (CSM): (1) A component of the client kernel that provides protocol support for the client.; (2) A station that consists of a control unit (a cluster controller) and the terminals attached to it.
�client stub: In the Distributed Computing Environment (DCE), the surrogate code for a remote procedure call (RPC) interface that is linked with and called by the client application code. In addition to general operations such as marshaling data, a client stub calls the RPC runtime library to perform remote procedure calls and, optionally, to manage bindings.
�client type detection: A process in which a servlet determines the markup language type required by a client and calls the appropriate JavaServer Pages file.
�CLIP: See calling line identification presentation.
�clipboard: An area of computer memory, or storage, that temporarily holds data. Data in the clipboard is available to other applications.
�clipping: (1) In the GDDM function, the process of cutting off the image at the border of the display but allowing the coordinates of the lines to extend beyond.; (2) In computer graphics, removing those parts of display elements that lie outside of a given boundary.
�CLIST: See command list.
�clitic: A word that syntactically functions separately but is phonetically connected to another word. A clitic can be written as connected or separate from the word it is bound to. Common examples of clitics include the last part of a contraction in English 'wouldn't' or 'you're'.
�cliticization: The process by which a complex word or expression is formed by attaching a clitic to another word. A common example of cliticization includes attaching a clitic to a verb, for example: "je t'aime" in French.
�CL module: See control language module.
�CLNP: (1) See connectionless-mode network protocol.; (2) See Connectionless Network Protocol.
�CLNS: See connectionless-mode network service.
�CLNS path: In OSI, a path used when the connectionless-mode network service is used. Each CLNS path names data terminal equipment (DTE) to be used for outbound communication.
�CLNS path maintenance: In OSI, an option of whether or not to maintain a CLNS path to an adjacent node permanently (until OSI Communications Subsystem is restarted), or release the path when no active CLNS connection uses it. These connections include both network management and directory service connections and connections between customer programs.
�CLNS path set: In OSI, a path set used when the connectionless-mode network service is used.
�CLOB: See character large object.
�clocking: (1) In communications, a method of controlling the number of data bits sent on a communications line in a specified time.; (2) In binary synchronous communication, the use of clock pulses to control synchronization of data and control characters.
�clock time: The elapsed time in real time. Clock time differs from CPU time as thread switches and process context switches introduce uncertainty in performance calculation; clock time does not account for this execution behavior.
�clone: To prepare a reference computer and create a system profile ready for deployment.
�cloned CICS region: 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.
�cloned IMSplex: A group of IMSs in a sysplex that share databases, queues, or both, and have identical resource definitions.
�clone object: An object that is associated with a clone table, including the clone table itself and check constraints, indexes, and BEFORE triggers on the clone table.
�clone table: A table that is structurally identical to a base table. The base and clone table each have separate underlying VSAM data sets, which are identified by their data set instance numbers. See also base table.
�cloning: A copying technique that preserves the characteristics of the original but personalizes instance-specific data. The result of a cloning operation is new instance of an entity (for example, of a virtual disk, a virtual computer system, or an operating system) rather than a backup of the original.
�close: (1) To end an activity and remove that window from the display. See also open.; (2) To end processing by ending the connection between the file and a program.
�closed application: An application that requires exclusive use of certain statements on certain DB2 objects, so that the objects are managed solely through the external interface of that application.
�closed registration: A registration process in which only an administrator can register workstations as client nodes with the server. See also open registration.
�closed system: A system whose characteristics comply with proprietary standards and that therefore cannot readily be connected to other systems.
�closed user group (CUG): In data communication, a group of users who can communicate with other users in the group, but not with users outside the group. A data terminal equipment (DTE) may belong to more than one closed user group.
�closure line: In the GDDM function, a line added by the system to enclose an area being filled with a pattern, in instances when the routines that precede the GSENDA routine fail to form an enclosed area.
�Cloudscape: An embeddable, all Java, object-relational database management system (ORDBMS).
�CLP: (1) See communication line processor.; (2) See current line pointer.; (3) See command line processor.
�CLPA: See create link pack area.
�CL procedure: See control language procedure.
�CL program: See control language program.
�CLR: See common language runtime.
�CLS: See Continuous Linked Settlement.
�CLT: See command list table.
�CLU: See control logical unit.
�CLUSRCVR: See cluster-receiver channel.
�CLUSSDR: See cluster-sender channel.
�cluster: (1) A collection of complete systems that work together to provide a single, unified computing capability.; (2) In SNA, a group of stations that consist of a controller (cluster controller) and the workstations attached to it.; (3) In high-availability cluster multiprocessing (HACMP), a set of independent systems (called nodes) that are organized into a network for the purpose of sharing resources and communicating with each other.; (4) In WebSphere MQ, a group of two or more queue managers on one or more computers, providing automatic interconnection, and allowing queues to be shared amongst them for load balancing and redundancy.; (5) In Microsoft Cluster Server, a group of computers, connected together and configured in such a way that, if one fails, MSCS performs a failover, transferring the state data of applications from the failing computer to another computer in the cluster and reinitiating their operation there.; (6) 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.; (7) A group of application servers that collaborates for the purposes of workload balancing and failover.; (8) A group of two or more Domino servers that provides users with constant access to data, balances the workload among servers, improves server performance, and maintains performance when the size of an enterprise increases.; (9) A loosely coupled collection of independent systems (or nodes) organized into a network for the purpose of sharing resources and communicating with each other. See also GPFS cluster.
�cluster configuration: User definition of all cluster components. Component information is stored in the ODM. Components include cluster name and ID, and information about member nodes, adapters, and network modules.
�cluster configuration data: The configuration data that is stored on the cluster configuration servers.
�cluster controller: A device that can control the input/output operations of more than one device connected to it.
�cluster domain: A virtual collection of physical elements such as computer systems and logical elements such as software instances that can provide services to a client as a single unit. See also cluster domain node.
�cluster domain node: A physical element such as a computer system or a logical element such as a software instance in a cluster domain. See also cluster domain, management server domain, peer domain.
�clustered index: An index whose sequence of key values closely corresponds to the sequence of rows stored in a table. The degree of correspondence is measured by statistics that are used by the optimizer.
�cluster entry: A catalog entry that contains the following information about a key-sequenced or entry-sequenced Virtual Storage Access Method (VSAM) cluster: ownership, cluster attributes, and the cluster's passwords and protection attributes. A key-sequenced cluster entry points to both a data entry and an index entry; an entry-sequenced cluster entry points to a data entry only. See also alternate-index entry.
�Cluster feature: A feature that provides four cable connections and allows up to four work stations to be attached to a 5251 Model 12 Display Station.
�clustering: The ability to group independent systems to work together as a single system.
�clustering block index: See dimension block index.
�clustering index: An index that determines how rows are physically ordered (clustered) in a table space. If a clustering index on a partitioned table is not a partitioning index, the rows are ordered in cluster sequence within each data partition instead of spanning the partitions.
�cluster joining: The process whereby additional nodes join an existing cluster when they can communicate with another active clustered node and can validate the node name and version compatibility.
�cluster log: A log that maintains a history of routine activities and error conditions that are generated by all metadata servers in the cluster.
�cluster manager: The node that monitors node status using disk leases, detects failures, drives recovery, and selects file system managers. The cluster manager is the node with the lowest node number among the quorum nodes that are operating at a particular time.
�cluster member: An identically configured copy of an object, such as an application server. Cluster members can be used for workload management purposes, for example, to support horizontal scaling and vertical scaling.
�cluster membership list: A set of cluster nodes that have been configured for a cluster.
�cluster node: A system that is a member of a cluster. See also system.
�cluster processor complex (CPC): The unit within a cluster that provides the management function for the ESS. It consists of cluster processors, cluster memory, and related logic.
�ClusterProven: An IBM designation that defines certain high-availability requirements that are applied to a software product either by itself or in combination with other software products. A solution that satisfies the technical criteria of these requirements can be validated with IBM and licensed to be marketed with IBM's ClusterProven trademark.
�cluster queue: A queue that is hosted by a cluster queue manager and made available to other queue managers in the cluster.
�cluster queue manager: A queue manager that is a member of a cluster. A queue manager can be a member of more than one cluster.
�cluster-receiver channel (CLUSRCVR): A channel on which a cluster queue manager can receive messages from other queue managers in the cluster, and cluster information from the repository queue managers.
�cluster resource: Any part of the system that is available across multiple cluster nodes. The two types of system resources that can be resilient are the following: Objects that are kept up to date by using replication. A resilient application and its associated IP address, which can be switched.
�cluster resource group (CRG): A collection of related cluster resources that defines actions to be taken during a switchover or failover operation of the access point of resilient resources. The group describes a recovery domain and supplies the name of the cluster resource group exit program that manages the movement of an access point.
�cluster resource group manager (CRGM): A highly available client application that uses the integrated cluster resource services to configure, define, monitor, and administer a cluster of systems.
�cluster resource service: An i5/OS system service function that supports cluster implementations.
�cluster-root container: A special container that is the root of the global file system.
�cluster-sender channel (CLUSSDR): A channel on which a cluster queue manager can send messages to other queue managers in the cluster, and cluster information to the repository queue managers.
�cluster service: A Windows (TM) service that manages the cluster specific activities and is installed on each node of the cluster. The components of the Cluster service provide high availability, easy management and enhanced scalability for Windows.
�cluster transmission queue: A transmission queue that holds all messages from a queue manager destined for another queue manager that is in the same cluster. The queue is called SYSTEM.CLUSTER.TRANSMIT.QUEUE.
�cluster VLAN: The virtual LAN that connects nodes to each other and to the management server through an Ethernet connection. Installation and administration tasks are done on the cluster VLAN.
�CLUT: See color lookup table.
�CL variable: See control language variable.
�CM: See configuration management.
�CMAS: See CICSPlex SM address space.
�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: (1) See Common Messaging Call.; (2) See communication management configuration.
�CMDB: See configuration management database.
�cmf: See compiled message flow.
�CMI: See control message interface.
�CMIP: See Common Management Information Protocol.
�CMIP services: The VTAM implementation of the Common Management Information Protocol (CMIP), which provides a common set of program services for application programmers to use in writing CMIP application programs. These services include controlling associations, converting basic encoding rules (BER) syntax, and validating protocols.
�CMIS: See common management information service.
�CMM: See common management model.
�CMOS: See complementary metal-oxide semiconductor.
�CMOT: See Common Management Information Protocol over TCP/IP.
�CMP: See container-managed persistence.
�CMPI: See Common Manageability Programming Interface.
�CMRA: See SPX Component Model Reference Architecture.
�CMRO task: See cross memory resource-owning task.
�CMRS: See Commercial Mobile Radio Services spectrum.
�CMS: See Conversational Monitor System.
�CMS extended parameter list: A type of parameter list available in the CMS environment consisting of a string composed exactly as the user typed it at the terminal. There is no tokenization performed on the string.
�CMS tokenized parameter list: A type of parameter list available in the CMS environment consisting of 8-byte tokens, which are folded to uppercase and end with a double word of FF.
�CMT: See CICS-maintained data table.
�CNN: See composite network node.
�CNOS: See change number of sessions.
�CNT: See Communication Name Table.
�CO: (1) See central office.; (2) See configuration object.
�COA: Confirm on arrival.
�coalescing: The process of combining the configuration data from the preference node trees of an ORB and all ORB sets to which the ORB belongs into a single preference node tree. See also inheriting.
�COA report: See confirm-on-arrival report.
�coarse-grained: Pertaining to viewing a group of objects from an abstract or high level. See also fine-grained.
�coaxial cable: A cable consisting of one conductor, usually a small copper wire, within and insulated from another conductor of larger diameter, usually copper tubing or copper braid.
�COBOL: See Common Business Oriented Language.
�COBOL character: Any of the 51 characters of the COBOL character set.
�COBOL reserved-word file: In EGL, a user-defined text file that contains reserved words other than EGL reserved words. If an EGL variable name matches a reserved word, EGL aliases the variable name at generation time, as reflected in the generated output.
�COBOL run unit: A COBOL-specific term that defines the scope of language semantics. A COBOL run unit is equivalent to a Language Environment enclave.
�COBOL word: In COBOL, a character string of not more than 30 characters that forms a user-defined word, a system-name, or a reserved word.
�COBPACK: A collection of individual modules that are packaged into a single load module in order to reduce the time that would otherwise be needed to load the individual load modules.
�COD: See confirm on delivery.
�CoD: See capacity on demand.
�code: A number that uniquely identifies a catalog entry in the WebSphere Commerce system. A product code is used as the prefix for creating individual SKU codes.
�code assist: See content assist.
�codebase: Works together with the code attribute in the APPLET tag to give a complete specification of where to find the main applet class file: code specifies the name of the file, and codebase specifies the URL of the directory containing the file.(Sun)
�codec: (1) A technology that compresses and decompresses data for the purpose of reducing the bandwidth required to send streaming data.; (2) Pertaining to adapters that compress and decompress video files.
�coded character set (CCS): A set of unambiguous rules that establishes a character set and the one-to-one relationships between the characters of the set and their coded representations. See also invariant character set.
�coded character set identifier (CCSID): A 16-bit number that includes a specific set of encoding scheme identifiers, character set identifiers, code page identifiers, and other information that uniquely identifies the coded graphic-character representation. See also binary string.
�coded character set identifier 65534 (CCSID 65534): The coded character set identifier (CCSID) that is used to show that a CCSID value for data at this level of processing is not relevant. When CCSID 65534 (X'FFFE') is associated with data, a CCSID value for the data should be obtained from the tagged fields of elements that are at a lower level in the defined hierarchy. For example, a file has CCSIDs that are tagged for each individual field it contains. If the field is tagged with CCSID 65534, processing is based on the CCSIDs assigned to each individual field instead of the CCSID assigned to the file.
�coded character set identifier 65535 (CCSID 65535): An identifier that is used to show that the associated data should not be processed as coded-graphic-character data. CCSID 65535 ( FFFF ) cannot be represented in long form. Data that is associated with CCSID 65535 should be interpreted as actual representation is unknown as defined in Character Data Representation Architecture-Level 2, IBM Registry. You cannot convert data that is associated with CCSID 65535 from one CCSID to another. The coded character set identifier (CCSID) that is used to show that data associated with the CCSID should not be processed as coded-graphic-character data.
�coded font: In AFP support, a font file that associates a code page and a font character set. For double-byte fonts, a coded font associates multiple pairs of code pages and font character sets.
�coded font local identifier: A 1-byte identifier that the Map Coded Font structured field assigns to each coded font it selects. The identifier is then specified in the text-control sequence that precedes the string of text to be printed with the particular font. See also local identifier.
�coded font section: A font character set and code page pair. A single-byte coded font consists of only one coded font section; a double-byte coded font can consist of more than one.
�coded graphic character-set ID: A 10-digit identifier (two 5-digit identifiers separated by a space) that is the combination of a graphic character-set ID and a code-page ID. See also code-page ID.
�code division multiple access (CDMA): A form of multiplexing where the transmitter encodes the signal using a pseudo-random sequence, which the receiver also knows and can use to decode the received signal. Each different random sequence corresponds to a different communication channel.
�coded overlay: An overlay loaded in a printer in a coded format, rather than as a raster pattern. See also raster overlay.
�code element: A code construct in source or binary code. This term is often used as the antipode of model element.
�code element set: The result of applying rules that map a numeric code value to each element of a character set. An element of a character set may be related to more than one numeric code value but the reverse is not true. However, for state-dependent encodings the relationship between numeric code values to elements of a character set may be further controlled by state information. The character set may contain fewer elements than the total number of possible numeric code values; that is, some code values may be unassigned. X/Open.
�code fragment: In Process Designer, the specification of an action through WebSphere business integration API methods or other Java code. A developer can add or customize default code fragments. Process Designer embeds each code fragment in the code it generates to produce a whole program. See also action, action node.
�code generation: The process of initally generating code from model information or subsequently updating code with model changes. Code changes might be overwritten by changes in the model. See also round-trip engineering.
�code generation cycle: The set of supported or expected actions that are performed in response to a single code generation (forward engineering) invocation gesture.
�code generator: The part of the compiler that physically generates the object code.
�code group: In a computer security code system, an apparently meaningless sequence of letters, digits, or both, that represents a plaintext element, which may be a word, phrase, or sentence.
�code list: A table, supplied by Data Interchange Services or defined by the user, that contains all acceptable values for a single data field.
�code load: In System Manager, the type of product load that contains all of the product code that does not require translation to other languages, such as the code for displays, menus, and messages. However, if a product is never going to be translated, the code may contain all the product code.
�code model: Any specifically designated model that is bound to a domain other than analysis.
�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. See also code point.
�code page global identifier (CPGID): A 5-digit decimal or 2-byte binary identifier that is assigned to a code page. The range of values is 00001 to 65534 (X'0001' to X'FFFE').
�code-page ID: A 5-digit registered identifier used to specify a particular assignment of code points to graphic characters. The code-page ID is the second part of the QCHRID system value or the CHRID parameter value. See also coded graphic character-set ID.
�code point: (1) A unique bit pattern that represents a character in a code page. See also code page.; (2) For SNA alerts, a 1-or 2-byte hexadecimal code that designates a particular piece of text to be displayed at the focal point.; (3) An identifier in an alert description that represents a short unit of text. The code point is replaced with the text by an alert display program.; (4) In QoS, pertaining to a specific value in the Differentiated Services field of a data packet that signals to a network the behavior that is assigned to that packet.
�code project: A project in a Visual Studio solution. One or more projects are contained in one solution. Most projects represent the collection of files that are used to build a component. A specific programming language is often used to code all project items throughout a project. It is possible to have multiple-language projects in VS.NET. Note that, you cannot use multiple languages within one project item. See also solution.
�code set: See code page.
�code synchronization: A feature that enables merging of model and code changes. See also round-trip engineering.
�code template: A textual definition of the operation body code that is used when generating source code for a model element. This allows the source code to be reused and shared throughout a project or across projects. A code template consists of source code and embedded script logic, very much like an HTML page.
�code unit: The fundamental binary width in a computer architecture that is used for representing character data, such as 7 bits, 8 bits, 16 bits, or 32 bits. Depending on the character encoding form that is used, each code point in a coded character set can be represented by one or more code units.
�COD report: See confirm-on-delivery report.
�coexistence: (1) The ability of two or more entities to function in the same system or network.; (2) During migration, the state during which two releases exist in the same data sharing group.
�coherency check: Verification that the current state of an object satisfies the programmer-defined invariant properties of its class.
�coherent: Pertaining to an object in which all data values satisfy the invariant properties. If any invariant property is not satisfied, the object is not coherent.

�cohesion: The union of components of the same kind that depend on one another. See also coupling.
�cold project: A project that contains only a work breakdown structure and schedule that are imported from another project-scheduling tool.
�cold queue: A CQS private queue type that contains in doubt data objects for a client that cold started or a CQS that cold started.
�cold start: (1) A method of starting CICS where all local resources are refreshed, but information relating to remote systems and resource managers is preserved.; (2) The process of starting a system or program using an initial program load procedure.; (3) A process in which the system is initialized. All jobs that were active or in the job queue at the time of the cold start are removed from the system. See also warm start.; (4) A process by which DB2 restarts without processing any log records. See also warm start.; (5) The starting of IMS when it is initialized for the first time or when some error condition prevents a warm or emergency restart. See also emergency restart, normal restart.
�collaboration: (1) A WebSphere business integration system component that contains business logic describing a distributed business process. Collaborations are used to coordinate and extend the business processes of disparate enterprise software products and to facilitate meaningful data exchange between them. Collaborations use business objects to exchange and manipulate data. See also business logic.; (2) A conceptual collection or grouping of model elements, classifiers, or primitive types that are unified in accomplishing some objective within the context of the collaboration.; (3) The ability to connect customers, employees, or business partners to the people and processes in a business or organization, in order to facilitate improved decision-making. Collaboration involves two or more individuals with complementary skills interacting together to resolve a business problem.
�collaboration diagram: See communication diagram.
�collaboration meeting: One of the pre-defined Sametime meetings that can be selected when scheduling a meeting. A collaboration meeting is a small, very interactive meeting in which all participants have data permission. If computer audio is being used, anyone can talk at any time.
�collaboration object: An object created from a collaboration template that is executable after it is configured and bound. Each collaboration object is configured for a specific business environment to integrate specific applications or software products. See also collaboration template.
�collaboration-object group: An executable set of collaboration objects bound together to represent a combined business process. See also event isolation.
�collaboration property: A configuration option that, with the full set of such options, enables an administrator to customize the business processing behavior of a specific collaboration object. Collaboration properties are set in System Manager. See also property.
�collaboration template: The logic and framework of a collaboration that provides the definition of its actions. A collaboration template consists of Java code, which Process Designer generates and the developer can customize. The template consists of scenarios, which specify sets of actions. A collaboration template is not executable; it is a Java class used to instantiate executable collaboration objects. See also action, collaboration object.
�Collaborative Components: UI-neutral API methods and tag libraries that allow developers who are writing portlets for WebSphere portals to add Lotus Software collaborative functionality to their portlets.
�collaborative filtering: Personalization technology that calculates the similarity between users based on the behaviors of a number of other people and uses that information to make recommendations for the current user.
�collaborative portal: A highly personalized desktop-to-Web tool designed for specific audiences and communities of users that organizes information, applications, and services for effective community building at the corporate level and for personal use by individuals.
�collaborative unit: The configuration of the part of a deployment environment that delivers required behavior to an application module. For example, a messaging collaborative unit includes the host of the messaging engine and deployment targets of the application module, and provides messaging support to the application module.
�collate: To combine and arrange in order.
�collating element: The smallest entity used to determine the logical ordering of strings. A collating element consists of either a single character, or two or more characters collating as a single entity. The value of the LC_COLLATE category in the current locale determines the current set of collating elements. See also collating sequence.
�collating sequence: (1) The sequence in which the characters are ordered for the purpose of sorting, merging, comparing, and processing indexed data sequentially.; (2) An ordering assigned to a set of items, such that any two sets in that assigned order can be collated.; (3) A specified arrangement used in sequencing. See also collating element.; (4) The relative ordering of collating elements as determined by the setting of the LC_COLLATE category in the current locale. The character order, as defined for the LC_COLLATE category in the current locale, defines the relative order of all collating elements, such that each element occupies a unique position in the order.
�collation: The logical ordering of characters and strings according to defined rules.
�collator: A device that combines and arranges pages in order.
�collection: (1) Data obtained by a collector that represents the system status at a given point in time. Collections are timestamped and stored in a management collection object. See also schema.; (2) In a Tivoli environment, a container that provides a single view of related resources.; (3) The process of monitoring and storing application performance data, aggregating it to a time interval, and saving it into data files on the endpoint.; (4) A group of objects with a similar set of management rules.; (5) An abstract class without any ordering, element properties, or key properties.; (6) A group of objects that typically have similar performance, availability, backup, retention, and class transition characteristics. A collection is used to catalog a large number of objects which, if cataloged separately, could require an extremely large catalog.; (7) A set of data sources and options for crawling, parsing, indexing, and searching those data sources.; (8) A group of packages that have the same qualifier.
�collection certificate store: A collection of intermediate certificates or certificate revocation lists (CRL) that are used by a certificate path to build up a certificate chain for validation.
�Collection Class Library: A complete set of abstract data structure such as trees, stacks, queues, and linked lists.
�collection page: A type of page in the administrative console that displays a collection list of administrative objects. From this type of page, you can typically select objects to act on or to display other pages for.
�collection point block (CPB): In the NetView Performance Monitor (NPM), a control block used to coordinate the collection of network and session data.
�Collection Services: A System i Navigator tool that collects performance data independent of the system monitors in System i Navigator. This function is intended for subsequent analysis by performance personnel either by writing queries against the collected data or by reviewing reports produced by the Performance Tools for i5/OS licensed program.
�collective: A set of brokers that are fully interconnected and that form part of a multi-broker network for publish/subscribe applications.
�collector: (1) A generic name for a program that at regular intervals collects data about the status of the system.; (2) In a Tivoli environment, either (a) a repeater site on which Scalable Collection Service (SCS) is installed or (b) an SCS daemon on a managed node or gateway that stores and then forwards data to other collectors or to the inventory receive or inventory data handler.
�collector system: For directory shadowing, a system that receives initial or changed Enterprise Address Book (EAB) data from a supplier system in a network. See also supplier system.
�Collector Tool: A tool that gathers information about a WebSphere Application Server installation and packages this data in a Java archive (JAR) file to assist in problem determination and analysis. This information includes logs, property files, configuration files, operating system data, Java data, and prerequisite software presence and levels.
�collision: An unwanted condition that results from concurrent transmissions on a channel, causing the transmissions to be unintelligible.
�collision avoidance: In carrier sense multiple access with collision avoidance (CSMA/CA), the process of sending a jam signal and waiting for a variable time before transmitting data. The process is designed to avoid two or more simultaneous transmissions.
�collision detect: In Performance Tools, a counter that counts the total number of times the terminal equipment (TE) detected that the frames it transmitted were damaged by another TE trying to use the same bus.
�collocated join: The result of two tables being joined under one of two conditions. The first condition is where the tables reside in a single-partition database partition group in the same database partition. The second condition is where the tables are in the same database partition group, the number of partitioning columns is the same, the columns are partition compatible, both tables use the same partitioning function, and pairs of the corresponding partitioning key columns participate in the equijoin predicates. See also partition-compatible join.
�collocation: The process of keeping all data belonging to a single client node or a single client file space on the minimal number of sequential access media volumes within a storage pool, reducing the number of volumes that must be accessed when a large amount of data must be restored.
�collocation frequency: A statistic that indicates the likelihood of certain words occurring together in text.
�colony address space: An address space in which a physical file system (PFS) can be initialized. The address space can be viewed as a logical extension to the kernel address space.
�color: In computer systems, a color is usually represented by a triplet called RGB (red, green, and blue) signals. Most computer monitors require RGB signals to drive the 3-colored phosphors of a color monitor.
�color lookup table (CLUT): See color map.
�color map: (1) A set of color cells. A pixel value indexes the color map to produce RGB-intensities. A color map consists of a set of entries defining color values that, when associated with a window, is used to display the contents of the window.; (2) A lookup table in which each index is associated with a red, green, and blue value.
�color mapping file: File CICSCOL.INI used by the CICS Transaction Gateway to customize the 3270 screen color attributes on client workstations.
�color mapping table: An architected MO:DCA object that is used to map color values specified in a source color space to color values specified in a target color space. This object is loaded into printers that support the color mapping table.
�color palette: (1) In Business Graphics Utility, the range of colors defined by hue, lightness, and saturation to be used when a chart is displayed on a graphics-capable display.; (2) A set of colors that can be displayed on the display at one time. This can be standard set used for all images or a set that can be customized for each image.
�color selection: The ability to specify a color other than black to print data in more than one color. Some printers support selection of several colors, depending upon the color of ribbon installed in the printer. Other printers support the selection of black or "color of media," which can cause white lettering on a background that has been shaded black, for example.
�color table: See color map.
�column: (1) In a relational database, a field defined for a given record or row.; (2) The vertical component of a database table. A column has a name and a particular data type (for example, character, decimal, or integer).; (3) A character position within a print line or on a display. The positions are numbered consecutively from 1, starting at the leftmost character position and extending to the rightmost position.; (4) A vertical arrangement of characters or other expressions. Columns are positioned side by side on a page or display. See also row.; (5) A subdivision of a band, such as baseline or actual.
�column analysis: A data quality process that describes the condition of data at the field level. You perform column analysis by defining and running a column analysis job and then examining the results.
�column data: The data in a column of a relational database table or view. The type of the data can be any data type supported by the database manager.
�column function: See aggregate function.
�column option: In a federated system, a parameter of the CREATE NICKNAME and ALTER NICKNAME statements that describes the values in certain columns of the data source object that a nickname references. This information is added to the global catalog and used by the query optimizer to develop better access plans. Column options provide a way to tell the data source wrapper to handle a column in a different way than it normally would.
�column position: A unit of horizontal measure related to characters in a line. It is assumed that each character in a character set has an intrinsic column width independent of any output device. Each printable character in the portable character set has a column width of one. The standard utilities, when used as described in this document set, assume that all characters have integral column widths. The column width of a character is not necessarily related to the internal representation of the character (numbers of bits or bytes). The column position of a character in a line is defined as one plus the sum of the column widths of the preceding characters in the line. Column positions are numbered starting from 1. X/Open.
�column separator: A symbol on each side of a position of a field on a display. This symbol does not occupy a position on the display.
�column wrapping: Formatting values in a report so that they occupy several lines within a column. Often used when a column contains values whose length exceeds the column width.
�COM: See computer output microfilm.
�comb: In a magnetic disk unit, an assembly of access arms that moves as a unit.
�combination box: A control that combines the capabilities of an entry field and a list box. The list box contains choices that a user can select from to complete the entry field.
�combined alert: In the NetView program, an alert that includes both a nongeneric alert and a generic alert in one network management vector transport.
�combined condition: In COBOL, a condition that is the result of connecting two or more conditions with the AND or the OR logical operator.
�combined file: In RPG, a data file that is used as both an input file and an output file. The fields are not necessarily the same in the input and output records.
�combined function IOP (CFIOP): A type of IOP that can connect to a variety of different input/output adapters to support disk units, a console, and communications hardware. It contains some multifunction IOP (MFIOP) capabilities as well as Ethernet and token-ring controllers. This processor does not contain server processor functions. See also multifunction IOP.
�combined search: A query that combines one or more of the following types of searches: parametric, text, or image.
�combined station: In high-level data link control (HDLC), the part of a data station that supports the combined control functions of the data link, generates commands and responses for transmission, and interprets received commands and responses.
�combo box: See combination box.
�COM device: See microfilm device.
�come from checking: An SNA LU 6.2 security option that defines a list of authorization identifiers that are allowed to connect to DB2 for z/OS from a partner LU.
�Comitato Elettrotechnico Italiano: The Italian standards organization responsible for signaling protocols.
�Comit� consultatif international t�l�graphique et t�l�phonique (CCITT): See International Telecommunication Union Telecommunication Standardization Sector.
�Comite de Coordination de l'Harmonisation (CCH): The CEPT committee responsible for standards.
�comma: (1) In REXX, a token that represents the continuation character, a separator of arguments in an argument list, or a separator in a parsing template.; (2) A unique pattern (either binary 1100000 or binary 0011111) used in 8B/10B encoding to specify character alignment within a data stream. See also K28.5.
�comma delimited file: A file whose records contain fields that are separated by a comma.
�comma expression: An expression that contains two operands separated by a comma. Although the compiler evaluates both operands, the value of the right operand is the value of the expression. If the left operand produces a value, the compiler discards this value.
�command: (1) A statement used to initiate an action or start a service. A command consists of the command name abbreviation, and its parameters and flags if applicable.; (2) In SDLC, a frame transmitted by a primary station. Asynchronous balanced mode stations send both commands and responses. See also response.; (3) In SNA, any field set in the transmission header (TH), request header (RH), or request unit (RU) that states an action or that starts a protocol.; (4) A request from a terminal or automated operator for the performance of an operation or service, or for the execution of a particular program.; (5) A request to perform an operation or run a program. When parameters, arguments, flags, or other operands are associated with a command, the resulting character string is a single command.
�command alias: An abbreviation of a long command line or a new name for a command. [OSF]
�command and response token (CART): An 8-byte token that is added to write-to-operator (WTO) commands; it enables the response WTO to be associated with the command that invoked it.
�command area: An area of a display screen in which the user enters commands.
�command attention key (CA key): In DDS, a keyboard key that can be specified with the CA keyword to request the function specified by the keyword. Data is not returned to the system. See also command function key.
�command authorization table: A set of entries that define an operator's authorization for accessing commands and, depending on the level of granularity that an enterprise chooses, command keywords and keyword values.
�command bag: In the MQAI, a type of bag that is created for administering WebSphere MQ objects, but cannot change the order of data items or create lists within a message.
�command bean: (1) A bean that contains the programming logic to handle a particular request.; (2) A proxy that can invoke a single operation using an execute() method.
�command button: See push button.
�Command Center: A component of the Control Center for IMS that is used to issue IMSplex commands from both a workstation or multiple IMS systems.
�command code: The portion of the segment search argument that enables an application program to access a database segment based on some variation in either the call function, the segment qualification, or the setting of parentage.
�command control block (CCB): In the IBM Token-Ring Network, a specifically formatted block of information provided from the application program to the adapter support software to request an operation.
�command definition: An object that contains the definition of a command (including the command name, parameter descriptions, and validity-checking information) and identifies the program that performs the function requested by the command. The system-recognized identifier for the object type is *CMD.
�command definition statement: A source statement that defines keywords and parameter values, qualified names, elements in a list, parameter requirements and interrelationships, and prompt text for a command. Command definition statements are used to create a CL command.
�command entry field: In Common User Access (CUA) architecture, an entry field in which a user types commands.
�command file: (1) In PC operating systems, a file with a file name extension of .CMD that functions like a batch file in DOS.; (2) In RJE, a remote job input stream that can contain host system commands and job control language (JCL), data, and RJE control statements (READFILE or EOF). See also data file.
�command function key (CF key): In DDS, a keyboard key that can be specified with the CF keyword to request the function specified by the keyword. Data is returned to the system. See also command attention key.
�command history: An automatic listing of previously issued commands.
�command interface: An interface for running QMF commands. The QMF commands can only be issued from within an active QMF session. See also callable interface.
�command interpreter: See command language interpreter.
�command key indicator: In RPG, an indicator defined to correspond with the function keys to tell the program when one of the function keys is pressed.
�Command Language (CL): In WebSphere MQ for iSeries, a language that can be used to issue commands, either at the command line or by writing a CL program.
�command language interpreter: A program that reads commands and changes them into computer instructions.
�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.
�command length: In query management, one of the arguments passed to the language-specific interface programs that specifies the length of the query command to be run.
�command-level: Pertaining to an operation that is performed for a specific command in a program. For example, a Monitor Message (MONMSG) command that immediately follows a specific command in a CL program is a command-level MONMSG command. See also program level.
�command-level interface: See application programming interface.
�command-level interpreter: 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.
�command line: The blank line on a display where commands, option numbers, or selections can be entered.
�command-line argument: A part of a command line, delimited by white space. Arguments are used to specify detailed behavior to a program. They are usually either command line options selecting variations in program operation, or path names of files to be processed.
�command-line interface (CLI): A type of computer interface in which the input command is a string of text characters. See also Copy Services command-line interface.
�command line processor (CLP): A text-based interface for entering SQL and XQuery statements and database manager commands.
�command list (CLIST): (1) A language for performing TSO tasks.; (2) A list of commands and statements designed to perform a specific function for the user.
�command list language: An interpretive language that is used to write command lists that contain sequences of commands to be executed when the name of the command list is entered. Tivoli NetView for z/OS supports command lists that are written in two command list languages: REXX and its own unique language, the NetView command list language.
�command list table (CLT): 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.
�command master: In an IMSplex, the IMS that OM designates to process a command when a command is issued through the OM API. Commands are routed to all IMS systems that are registered for the command and, if the command requires only one IMS to process it, the command master processes the command.
�command mode: A state of a system or device in which the user can enter commands.
�command name: The first term in a command, a verb, which specifies the action to be performed and is usually followed by operands.
�command prefix (CPF): (1) A 1- to 8-character command identifier. The command prefix distinguishes the command as belonging to an application or subsystem rather than to z/OS.; (2) In WebSphere MQ for z/OS, a character string that identifies the queue manager to which WebSphere MQ for z/OS commands are directed, and from which WebSphere MQ for z/OS operator messages are received.
�command procedure: A command list, a command processor that is written in a high-level language, or a Tivoli NetView pipeline.
�command processing client: An entity that can process commands or do other work as directed by an OM. In an IMSplex, an IMS control region is a command processing client.
�command processing program (CPP): A program that processes a command. This program performs some validity checking and processes the command so that the requested function is performed.
�command processor: A module designed to perform a specific function for the user. Users can write command processors in assembler language or in a high-level language. Command processors are invoked as commands.
�command processor parameter list (CPPL): A list that contains addresses required by the command processor.
�command prompt: A displayed character (or string of characters) that indicates that a user may enter a command to be processed.
�command recognition character (CRC): (1) A character that permits a z/OS console operator or an IMS subsystem user to route DB2 commands to specific DB2 for z/OS subsystems.; (2) In MVS, a character that denotes an operator command.
�command scope: The breadth of the impact of a command in a data sharing group. In a data sharing environment, a command can have a group scope or a member scope.
�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 server: The WebSphere MQ component that reads commands from the system-command input queue, verifies them, and passes valid commands to the command processor.
�command significant status: The command status that is associated with a resource. For example, the status of STOP, TRACE, and MFSTEST commands. If a resource structure is defined, the recovery of command significant status is always maintained globally by the RM in the resource structure. See also end-user significant status.
�command string: In query management, a character string that contains a query command.
�command substitution: In UNIX-based operating systems, a shell feature that makes it possible to use the output from one command as an argument to another command.
�command synonym: The verb or verb/object part of a site-defined command. Users enter this for the command, followed by other information that is needed.
�command synonym table: A table each of whose rows describes a site-defined command. Each user can be assigned one of these tables.
�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, pool thread.
�COMMAREA: See communication area.
�COMMDS: See communications data set.
�comment: (1) Explanatory text in a program or file that is not translated by the compiler.; (2) An annotation attached to an element or a collection of elements. See also constraint.
�comment-entry: In COBOL, an entry in the Identification Division of the source program that may be any combination of characters from the character set of the computer. The comment-entry is written in area B on one or more lines. Comment-entries serve only as documentation and are not translated by the compiler.
�comment line: In COBOL, a source program line represented by an asterisk (*) in the indicator area of the line and any characters from the computer's character set in area A and area B of that line. The comment line serves only for documentation in a program.
�Commercial Mobile Radio Services spectrum (CMRS): An organization that provides cellular, PCs, mobile radio, paging, and other wireless services.
�commercial processing workload (CPW): An application that is run on System i models and processors to determine processor performance. The CPW workload is representative of commercial applications, particularly those that do significant database processing in conjunction with journaling and commitment control.
�commit: (1) To end a unit of work by releasing locks so that the database changes made by that unit of work can be perceived by other processes. This operation makes the data changes permanent. See also atomic, recoverable data set.; (2) To make changes permanent for a resource in order to establish a new consistent state.; (3) To move managed assets from a task group in a workspace to the production-ready data on the authoring server. See also authoring server, workspace, task group, production-ready data, workspace task group approver, quick publish.; (4) An operation that applies all the changes made during the current unit of recovery (UR) or unit of work. After the operation is complete, a new UR or unit of work begins. See also backout.
�commit coordinator: See sync point manager.
�commit cycle: The sequence of changes made between commitment boundaries.
�commit cycle identifier: The journal sequence number associated with the start commitment operation that is used to identify the journal entries in a particular commit cycle.
�commit identifier: The information that associates the commit operation with a specific set of committable resource changes. The commit ID is placed in the notify object if a system or routing step failure occurs, or if uncommitted changes exist when a routing step ends normally. The commit ID contains information (supplied on the commit statement) about the last successful transaction (group of changes that appear as a single change); for example, the transfer of funds from savings to a checking account.
�commit in progress (CIP): The commit in progress logical unit of work (LUW) state indicates that all the resources associated with this logical unit of work have been prepared after a unanimous vote to commit. The protected resource managers are in the process of committing.
�commitment boundary: (1) In a commitment controlled environment, any time there are no outstanding changes for a committable resource existing within a job.; (2) A point at which there are no changes to a database file pending within a job. See also roll back.
�commitment control: (1) A means of grouping committable resource operations to allow either the processing of a group of committable resource changes as a single unit through the Commit command, or the removing of a group of committable resource changes as a single unit through the Rollback command.; (2) A way of grouping file operations that allows the processing of a group of database changes as a unit or the removal of a group of database changes as a unit. See also roll back.
�commitment definition: Information used by the system to maintain the commitment control environment throughout a routing step and, in the case of a system failure, throughout an IPL (initial program load). This information is obtained from the Start Commitment Control (STRCMTCTL) command, which establishes the commitment control environment, and the file open information in a routing step. The commitment definition has a scope either to the job or to a particular activation group within the job.
�commit operation: A change management operation that causes all the updates prepared in the preparation phase to take effect. See also transactional mode.
�commit phase: (1) In software distribution, the phase in which previously prepared actions are committed, causing all of the updates to take effect. See also transactional mode.; (2) The second phase in a XA process. If all participants acknowledge that they are prepared to commit, the transaction manager issues the commit request. If any participant is not prepared to commit, the transaction manager issues a back-out request to all participants.
�commit point: (1) A point in time when data is considered to be consistent. See also synchronization point.; (2) The point at which an application program commits that a section of work is done and that the data it has modified or created is consistent and complete. The application program's output, which has been held up to that time, is sent to its destinations, its input is removed from the message queues, and its database updates are confirmed and made available to other applications. A commit point occurs when a program terminates normally or when it issues a checkpoint call or command. If a program processes messages, a commit point may also occur when it retrieves a new message.
�commit processing: The processing that IMS performs at a commit point.
�committable resource: A local or remote i5/OS object that can be placed under commitment control.
�committable update: An operation that results in a change to an object such that the object is under commitment control.
�committed change: A change that is not backed out in the event of a failure. Changes made by a logical unit of work (LUW) are committed when the sync point at the end of the LUW is complete.
�committed copy counter: A counting device that identifies the number of copies of a page that have been committed to printing but have not been counted by the committed page counter.
�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.
�committed page counter: A counting device that identifies the number of pages that have been committed to printing and have been removed from the page buffer.
�common agent: An agent that provides shared infrastructure for management applications. The common agent is self monitoring and self-starting, and provides remote deployment capability, shared machine resources, secure connectivity, and a single entry point. See also agent, subagent.
�Common Analysis Structure (CAS): A structure that stores the content and metadata of a document, and all analysis results that are produced by a text analysis engine. All data exchange during document analysis is handled by using the common analysis structure. See also text analysis engine, annotation.
�common analysis structure consumer: A consumer that does the final processing on the analysis results that are stored in the common analysis structure. For example, a consumer indexes the contents of the common analysis structure in a search engine or it populates a relational database with specific analysis results.
�common anchor area (CAA): Dynamically acquired storage that represents a z/OS thread. This area acts as a central communications area for the program, holding control blocks and addresses of various storage and error-handling routines, and control blocks.
�common area: (1) A control section used to reserve a virtual storage area to which other modules can refer.; (2) In a Web page that is based on a page template, the fixed region of the page.
�Common Base Event: A specification based on XML that defines a mechanism for managing events, such as logging, tracing, management, and business events, in business enterprise applications. See also situation.
�common block: In FORTRAN, a storage area that can be referred to by a calling program and one or more subprograms.
�Common Business Oriented Language (COBOL): A high-level programming language that is used primarily for commercial data processing.
�common carrier: In data communications, any government-regulated company that provides communications services to the general public. Examples are: the government-regulated telephone and telegraph companies in the United States, the General Post Office in the United Kingdom, the Bundespost in Germany, and Nippon Telephone and Telegraph Public Corporation in Japan.
�common channel signaling (CCS): A method of communicating telephony information and line signaling events (for example, call setup and call clearing) on a dedicated signaling channel. See also channel associated signaling.
�common communication layer (CCL): The communication infrastructure that unites the various components, such as controller, parser, crawler, and index server, of WebSphere Information Integrator OmniFind Edition.
�Common Communications Support (CCS): The Systems Application Architecture (SAA) component that defines architectures and protocols that interconnect systems and devices in an SAA environment and allow data to be interchanged among them.
�common component: A combination of related software, information, data, and other artifacts that forms the smallest logical unit of software packaging and sharing and has a managed development and maintenance life cycle. A common component is a serviceable software asset. See also feature, assembly, offering, serviceable software asset, component.
�Common Connector Framework (CCF): A product offering interface and class definitions that provide a consistent means of interacting with enterprise resources (for example, CICS and Encina transactions) from any Java execution environment.
�Common Console Interface (CCI): The interface definition that enables console components to run either in a previously installed console or in a Web console, such as the Integrated Solutions Console (ISC).
�Common Criteria: A framework for independent assessment, analysis, and testing of IT products to a set of security requirements.
�Common Cryptographic Architecture (CCA): IBM software that enables a consistent approach to cryptography on major IBM computing platforms. It supports application software that is written in a variety of programming languages. Application software can call on CCA services to perform a broad range of cryptographic functions, including DES and RSA encryption.
�common data set descriptor record (CDD): The record that precedes a user's data set on a DFSMShsm-owned volume and that is used to return the data set to the user's format.
�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 Event Infrastructure (CEI): The implementation of a set of APIs and infrastructure for the creation, transmission, persistence, and distribution of business, system, and network Common Base Events. See also event server, event emitter.
�common filter service: A subcomponent of DFSMSdfp common services that compares data items with filter keys, and then indicates which data items match the keys and how many matches have been found.
�Common Gateway Interface (CGI): An Internet standard for defining scripts that pass information from a Web server to an application program, through an HTTP request, and vice versa.
�Common INET (CINET): A physical file system layer for the address families AF_INET and AF_INET6 that multiplexes sockets across several other physical file systems or transports.
�Common Information Model (CIM): An implementation-neutral, object-oriented schema for describing network management information. The Distributed Management Task Force (DMTF) develops and maintains CIM specifications. See also common management model.
�Common Information Model implementation (CIM implementation): The particular technology used to implement the CIM standard. Examples for CIM implementations are CIM servers (implementing the Web Based Enterprise Management (WBEM) standards).
�Common Information Model instrumentation (CIM instrumentation): The CIM server and CIM providers that are installed on a system.
�Common Information Model provider (CIM provider): Software that enables the CIM server to access and manage the resources. A CIM provider implements a particular portion of a Web Based Enterprise Management (WBEM) profile.
�Common Information Model schema (CIM schema): A collection of class definitions that describe managed objects in a particular environment. A CIM schema is often defined at only a high level, while Web Based Enterprise Management (WBEM) profiles define the specific behavior being implemented.
�Common Information Model server (CIM server): Software, such as OpenPegasus, that allows use of the CIM standard on a system.
�common interchange file (CIF): A file that contains one ImagePlus Interchange Architecture (IPIA) data stream.
�common interchange unit (CIU): The independent unit of transfer for a common interchange file (CIF). It is the part of the CIF that identifies the relationship to the receiving database. A CIF can contain multiple CIUs.
�Common Internet File System (CIFS): A protocol that enables collaboration on the Internet by defining a remote file-access protocol that is compatible with the way applications already share data on local disks and network file servers.
�common key: In COBOL, the key fields that are common to all record formats in the file starting with the first key field (the most significant) and ending with the last key field (the least significant).
�common language runtime (CLR): The runtime interpreter for all .NET Framework applications. See also .NET Framework.
�Common Link Access to Workstation (CLAW): A continuously executing program designed to minimize host interrupts while maximizing channel utilization.
�Common Manageability Programming Interface (CMPI): A common C-based interface that is between the CIM server and provider. The provider that is implemented with CMPI can run with the CIM server.
�Common Management Information Protocol (CMIP): In OSI, the management protocol (ISO 9596-2) that supports the common management information service.
�Common Management Information Protocol over TCP/IP (CMOT): An Internet Engineering Task Force (IETF) specification for the use of CMIP over a TCP/IP protocol stack.
�common management information service (CMIS): In OSI, the set of services defined by ISO 9595. The common management information service is used by agent processes and managing processes to communicate.
�common management model (CMM): A model that describes how to represent IT entities as managed resources and services. See also Common Information Model.
�common message log: A log that contains messages from several Infoprint Server components, including Print Interface, NetSpool, and IP PrintWay extended mode. Infoprint Central and the aoplogu command can display messages in the common message log.
�Common Messaging Call (CMC): An application programming interface (API) defined by the X.400 API Association.
�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. See also Internet Inter-ORB Protocol, Bonobo.
�common operations services (COS): The portion of SNA management services that pertains to the major vectors for limited remote operations control.
�Common Platform Storage Subsystems: A strategy and family of storage products based on common hardware parts.
�common program: In COBOL, a program that, despite being directly contained within another program, can be called from any program directly or indirectly contained in that other program.
�Common Programming Interface (CPI): In Systems Application Architecture (SAA), a set of software interfaces, conventions, languages, and protocols that provide a framework for writing applications with cross-system consistency.
�Common Programming Interface for Communications (CPI-C): A call-level interface that provides a consistent application programming interface (API) for applications that use program-to-program communications. CPI-C uses LU 6.2 architecture to create a set of interprogram services that can establish and end a conversation, send and receive data, exchange control information, and notify a partner program of errors.
�Common Queue Server (CQS): The address space that manages the shared queues (data objects that are stored in a coupling-facility list structure) for its clients (IMS).
�common section: See common area.
�Common Secure Interoperability Version 2: An authentication protocol developed by the Object Management Group (OMG) that supports interoperability, authentication delegation and privileges.
�common service area (CSA): In z/OS, a part of the common area that contains data areas that can be addressed by all address spaces but is protected during its use by the key of the requester.
�Common Service Layer (CSL): A collection of IMS manager address spaces that provide the infrastructure that is needed for systems management tasks. The CSL address spaces include RM, OM, and SCI. The CSL is built on the Base Primitive Environment (BPE) layer.
�Common Service Layer client (CSL client): A z/OS address space that uses the services that are provided by the Common Service Layer (CSL). The IMS control region is an example of a CSL client.
�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 storage area (CSA): A shared region of memory.
�Common System Administration: A core capability of the IBM Autonomic Computing Initiative that addresses the need to reduce the complexity of computer operations.
�common system area (CSA): (1) A major CICS storage control block that contains areas and data required for the operation of CICS.; (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 table expression: An expression that defines a result table with a name (a qualified SQL identifier). The expression can be specified as a table name in any FROM clause in the fullselect that follows the WITH clause.
�common transport semantics (CTS): The layer of the Networking Blueprint above the transport layer that makes the services of transport providers available to the transport user.
�common-use form: A paper size commonly used throughout the world.
�Common User Access (CUA): The Systems Application Architecture (SAA) specification for a user interface.
�common user ID: See common user identification.
�common user identification (common user ID): In System i Access, the user identification of a System i Access user that is used by the router when establishing a communications connection with a host system if a user ID is not specified in either the CONFIG.PCS file or in an alternative configuration file. The router uses this common user ID when connecting the personal computer to each additional host system. See also user identification.
�common work area (CWA): (1) A work area that can be accessed by any transaction in the CICS system.; (2) 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. See also transaction work area.
�communicates-association: An association between an actor class and a use case class, indicating that their instances interact. The direction of the association indicates the initiator of the communication (Unified Process convention).
�communication: The process of sending or receiving data between two points of a network.
�communication adapter: (1) An optional hardware feature, available on certain processors, that permits communications facilities to be attached to the processors.; (2) A device which allows network communication.
�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 attached: In PSF, pertaining to a device that is SNA-attached and that uses a communication controller. See also attached processor, local attached.
�communication call: A conversation statement that transaction programs can issue to communicate through the LU 6.2 protocol boundary. The specific calls that a transaction program can issue are determined by the program's current conversation state.
�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.; (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 Control Program (CCP): A portion of the network control program communication interrupt control program (CICP) that initiates and ends I/O line operations, handles first-level line error recovery and recording, and administers commands issued by background programs.
�communication control unit: A communication device that controls transmission of data over lines in a network.
�communication diagram: In UML, an interaction diagram that shows the structure of interactions and messages that pass between lifelines, which can be used to explore the dynamic behavior of a system. See also sequence diagram, object diagram.
�communication identifier (CID): (1) In VTAM, a key for locating the control blocks that represent a session. The key is created during session establishment and deleted when the session ends.; (2) The VTAM/NCP communication ID. This value is given to IMS and is used by VTAM and IMS to identify a session between IMS and a VTAM logical unit.
�Communication Line Block (CLB): An IMS control block that represents a VTAM node or a BTAM line. Each VTAM node or BTAM line has a single CLB. For VTAM, the block is one of several blocks that are part of the VTCB control block. The CLB represents the TM task in the IMS system for the node or line, and also contains many other fields that pertain to the node or line.
�communication line processor (CLP): In a communication controller, the processor that manages telecommunication lines.
�communication management configuration (CMC): (1) In VTAM, a technique for configuring a network that allows for the consolidation of many network management functions for the entire network in a single host processor.; (2) 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 Name Table (CNT): An IMS control block that represents a logical terminal.
�communication path: In UML modeling, a type of association that occurs between nodes in deployment diagrams to show how the nodes communicate.
�communication port: (1) An access point for data entry or exit to or from a communication device such as a workstation.; (2) On a personal computer, a serial port to which a stand-alone modem can be attached.
�communication resource manager: A resource manager that coordinates a two-phase commit across multiple nodes in a distributed transaction. These nodes may be on the same system or multiple systems.
�communications area: In query management, a control block used to communicate between the system code supporting the Common Programming Interface (CPI) and the application program using the CPI.
�communications configuration: The physical placement of communications controllers, the attachment of communications lines, and so forth; and the configuration descriptions that describe the physical configuration to the system and describe how the configuration will be used by the system.
�communications controller: The I/O processor card in the card enclosure.
�communications database (CDB): A set of tables in the DB2 for z/OS catalog that is used to establish conversations with remote database management systems.
�communications data format: In RJE, the output data received from the host system is left the same as it was received (either compressed, or data cut off at the end, or both).
�communications data set (COMMDS): The primary means of communication among systems governed by a single storage management subsystem (SMS) configuration. The COMMDS is a linear data set (LDS) that contains the name of the active control data set (ACDS) and current usage statistics for each system-managed volume, which helps balance space among systems running SMS. See also active control data set, control data set, source control data set.
�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.
�communications infrastructure: In the AIX operating system, a framework of communication that consists of a postmaster, an object registration service, a startup file, communication protocols, and application programming interfaces.
�communications job: A batch job that is started by a program start request from a remote system.
�communications line: The physical link (such as a wire or a telephone circuit) that connects one or more work stations to a communications controller, or connects one controller to another. See also data link protocol.
�communications manager: A function that manages the use of the system's communication facilities.
�communications security: A system option that requires the identity of a remote location to be verified before that location can run programs on your system.
�Communications Server: IBM SecureWay Software that supports (a) the development and use of application programs across two or more connected systems or workstations, (b) multiple concurrent connections that use a wide range of protocols, and (c) several application programming interfaces (APIs) that may be called concurrently and that are designed for client/server and distributed application programs.
�communications side information: In CPI Communications, an object that contains initialization parameters, such as the name of the partner program with which a program can establish a conversation and the name of the logical unit (LU) at the partner program's node, which CPI Communications requires to establish a conversation. The system-recognized identifier for the object type is *CSI.
�communications storage manager (CSM): In VTAM, a buffer management technology that reduces performance overhead resulting from the movement of large amounts of data. CSM enables authorized host application programs to put data in buffers that can be addressed and accessed by other authorized host application programs without any need to copy the data.
�communications type: A method for application programs to communicate on a local system, or between a local system and a remote system using the intersystem communications function (ICF). Examples of these communications methods include (a) asynchronous communications, (b) binary synchronous communications (BSC), (c) intrasystem communications, or (d) Systems Network Architecture (SNA), such as advanced program-to-program communications (APPC) and SNA upline facility (SNUF).
�Communications Utilities: The IBM licensed program that contains the VM/MVS bridge and the remote job entry function. Communications Utilities provides a method of exchanging mail or files and submitting or receiving jobs between connected systems.
�community: (1) The relationship between a Simple Network Management Protocol (SNMP) agent and one or more SNMP managers. The community describes which SNMP manager requests the SNMP agent should honor.; (2) In the Simple Network Management Protocol (SNMP), an administrative relationship between entities.; (3) A repository area where an assigned group of users can work together.
�community administrator: A person who manages users in and across communities.
�Community Console: A Web-based tool that is used to configure WebSphere Partner Gateway and to manage the flow of business documents between trading partners.
�community manager: See internal partner.
�community name: The part of an SNMP message that represents a password-like name and that is used to authenticate the SNMP message.
�community operator: The service provider who has a restricted set of typical day-to-day administrative responsibilities for the hub.
�community participant
�community services: In Sametime, services provided for awareness and text-based conversation. Pertains primarily to the server, as in community services on the Sametime server.
�commutative: Combining mathematical elements or having elements that combine in a way that the result is independent of the order in which they are processed. For example, such that a + b = b + a and a x b = b x a.
�compact: (1) To replace repetitive bits in a file or folder with control bits so that the file or folder takes up less space when saved.; (2) To compress a database, in order to reclaim space freed by the deletion of documents and attachments.
�compact disc (CD): An optical disc that stores digital data.
�compact-disc read-only memory (CD-ROM): High-capacity read-only memory in the form of an optically read compact disc.
�compact disc - recordable (CD-R): A device that can write data to compact disc recordable (CD-R) discs. A CD-R then can be read like CD-ROM media.
�Compact Hypertext Markup Language (cHTML): A format for publishing hypertext information on wireless devices.
�compaction: See compression.
�compaction table: In SNA networking, a table used by sending an LU-to-LU (logical unit-to-logical unit) half-session to transform data so that fewer bytes are sent to the receiving half-session. The receiving LU-to-LU half-session uses the same table to reverse the process, thereby restoring the data to its original form. See also compression.
�compare session: In version control software, the forum in which differences between contributors are displayed.
�comparison operator: (1) In SQL, a symbol used in comparison expressions to specify a relationship between two values. Comparison operators are = (equal to), <> (not equal to), < (less than), > (greater than), <= (less than or equal to), and >= (greater than or equal to).; (2) In REXX, an operator that compares two terms and returns the value 1 if the result of the comparison is true, or 0 if it is not true.
�comparison predicate: See basic predicate.
�comparison predicate subquery: See subquery in a basic predicate.
�compatibility: The ability of a device or system to work with another device or system without modification.
�compatibility font: An AFP font designed to emulate the uniformly spaced and fixed-pitch fonts used with line printers.
�compatibility mode: (1) A mode of operation in which a device can simulate the function of another device or model. The device will function like a different device of the same type, ignoring some or all of the additional features that the device might possess. Compatibility mode permits a migration between devices with minimal impact on programs that have device dependencies. See also page mode, 32-name mode.; (2) A mode of processing in which the IEAIPSxx and IEAICSxx parmlib members determine system resource management.; (3) A programming model that uses existing Tivoli Distributed Monitoring monitors to gather data that is used to create the dynamic model of a new resource model. This mode is used when migrating from previous versions of Tivoli Monitoring to ensure the compatibility of the new monitoring engine with the existing monitor collection.; (4) The first mode of operation in version-to-version migration process, during which DB2 runs the executable code for the new version with preliminary changes to the DB2 catalog. In a DB2 data sharing group, members that operate in compatibility mode can coexist with members that operate at the prior version level. Compatibility mode supports fallback to the prior version of DB2. When operating in compatibility mode, the DB2 subsystem cannot use any new functions of the new version. See also enabling-new-function mode, enabling-new-function mode*, compatibility mode*.
�compatibility mode*: A mode of operation in the version-to-version migration process during which DB2 runs the executable code for the new version, but with additional DB2 catalog changes relative to compatibility mode. Compatibility mode* applies only to a DB2 subsystem or data sharing group that was in enabling-new-function mode (ENFM) or new-function mode (NFM) at one time. Compatibility mode* does not support fallback to a prior version of DB2. When operating in compatibility mode*, a DB2 data sharing group cannot coexist with members that operate at the prior version level. See also enabling-new-function mode, enabling-new-function mode*, compatibility mode.
�compatible: Pertaining to the ability of a device or program to work with another device or program.
�compatible offerings: Offerings that have identical sets of base offering components (resource type and measurement source). The corresponding offering components in each compatible offering can have different sets of metrics.
�compatible schedule: A schedule that has the same set of defined schedule states (for example, peak, off-peak, and critical) as an existing schedule, the one that it is likely to replace.
�compatible schedules: Schedules that have the states needed by the breach values in the offering components for an offering.
�compatible server: In the Distributed Computing Environment (DCE), a server that offers the requested Remote Procedure Call (RPC) interface and RPC object and that is accessible over a valid combination of network and transport protocols.
�compensation: (1) On a federated database, a means of processing a query fragment if the data source cannot process the fragment or if the federated database can process the fragment faster than the data source can. See also push-down processing, query optimizer.; (2) The means by which operations in a process that have successfully completed can be undone if an error occurs, to return the system to a consistent state.; (3) The action that a collaboration takes during rollback of a transaction to undo a previously executed service call. Such an action semantically negates the action taken by a corresponding step in the service call, which has already been executed. For example, the compensation step for a Create action might involve deleting the object just created. See also isolation checking, minimum transaction level, transactional collaboration.
�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.
�compensation service: The operation that is performed to compensate for a successful operation when a process generates a fault (which is not handled within the process).
�competency: A work related role or field used to identify resources, for example, manager, programmer, network technician.
�competitive trade-up: A license for a program that replaces a qualifying non-IBM program that is obtained for a reduced charge. See also IBM trade-up.
�compilation: Translation of a source program (such as RPG or COBOL specifications) into a program in machine language. In Integrated Language Environment (ILE) languages, compilation translates source statements into modules, which then can be bound into programs or service programs.
�compilation host: In a cross-compilation environment, the machine on which compilation takes place. See also execution host.
�compilation unit: A portion of a computer program sufficiently complete to be compiled correctly.
�compile: (1) In Integrated Language Environment (ILE) languages, to translate source statements into modules that then can be bound into programs or service programs.; (2) To translate all or part of a program expressed in a high-level language into a computer program expressed in an intermediate language, an assembly language, or a machine language.
�compiled grammar file: A grammar in binary format, built by the WebSphere Voice Server grammar development tools.
�compiled message flow (cmf): A message flow that has been compiled to prepare it for transmission to the broker. A cmf is sent to the broker within a bar file.
�compiled program: In the original program model (OPM), the set of machine-language instructions that is the output from the compilation of a source program. The actual processing of data is done by the machine-language program. The system-recognized identifier for the object type is *PGM.
�compiler: A program that translates a source program into an executable program (an object program).
�compiler-directing statement: (1) A statement that controls what the compiler does rather than what the compiled program does.; (2) In COBOL, a statement, beginning with a compiler-directing verb, that causes the compiler to take a specific action during compilation. The compiler-directing statements are the COPY, ENTER, REPLACE, and USE statements.; (3) In RPG, an instruction that controls a compilation listing or causes records to be inserted. The four compiler directives are /TITLE, /EJECT, /SPACE, and /COPY.
�compiler listing: A printout that is produced by compiling a program or creating a file and that optionally includes, for example, a line-by-line list of the high-level language source, a cross-reference list, diagnostic information; and for programs, the description of the externally described files.
�compiler option: A keyword that can be specified to control certain aspects of compilation. Compiler options can control the nature of the load module generated by the compiler, the types of printed output to be produced, the efficient use of the compiler, and the destination of error messages.
�compile time: The time period during which a computer program is being compiled into an executable program.
�compile-time array: In RPG, an array that is compiled with the source program and becomes a permanent part of the program. See also preruntime array, runtime array.
�compile-time option: A keyword that can be specified to control certain aspects of compilation. Compiler options can control the nature of the load module generated by the compiler, the types of printed output to be produced, the efficient use of the compiler, the destination of error messages, and other things.
�compile-time table: In RPG, a table that is built into the source program and that becomes a permanent part of the compiled program. See also runtime table.
�complement: (1) In Cryptographic Support, a binary value that, in an exclusive-OR operation with a given binary value of the same length, produces a binary value of all ones.; (2) The value that can be added to the number to equal a given value.
�complementary metal-oxide semiconductor (CMOS): A technology that combines the electrical properties of n-type semiconductors and p-type semiconductors.
�complete: A table attribute that indicates that the table contains a row for every primary key value of interest. As a result, a complete source table can be used to perform a refresh of a target table.
�complete CCD table: In SQL replication, a CCD table that initially contains all of the rows from the replication source table or view and any predicates from the source table or view. See also noncomplete CCD table.
�complete class name: The complete qualification of a nested C++ class name including all enclosing class names and namespaces.
�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.)
�complete recovery: The CICS VSAM Recovery (CICSVR) function that consists of forward recovery followed by backout, if needed. In complete recovery, CICSVR restores a DFSMShsm or DFSMSdss backup.
�completion code: (1) An indicator that reflects the status of a task set at the time of its completion.; (2) A return code indicating how a message queue interface (MQI) call has ended.
�completion message: A message that tells the operator when work is successfully ended.
�complex: The maximum set of hardware and software resources that support one or more images of a single operating system.
�Complex Analysis: A core capability of the IBM Autonomic Computing Initiative that addresses the need for complex algorithms that implement intelligent, autonomic behavior.
�complex condition: In COBOL, a condition in which one or more logical operators (AND, OR or NOT) act on one or more conditions. Complex conditions include negated simple conditions, combined conditions, and negated combined conditions. See also simple condition.
�complex element: A named structure that contains simple elements within the message. Complex elements can contain other complex elements, and can also contain groups. The content of a complex element is defined by a complex type.
�complex instruction set computer (CISC): A computer that uses the traditional processor architecture to process instructions. See also reduced instruction set computer.
�Complex Mathematics Library: A C++ class library that provides the facilities to manipulate complex numbers and perform standard mathematical operations on them.
�complex number: A number consisting of an ordered pair of real numbers, expressible in the form a+bi, where a and b are real numbers and i squared equals minus one.
�complex type: (1) In XML, a type that allows elements in its content and may carry attributes. See also simple type.; (2) A structure within a message. A complex type contains elements, attributes, and groups organized into a hierarchy.
�complex word: A word formed by combining a root word with affixes, for example: the prefix 'un-' and the suffix '-ful' attach to the root word 'faith', which creates the complex word 'unfaithful'.
�complex word processing: In lexical analysis, the process in which algorithmic processing is used to determine the boundaries of words. In the case of Indo-European languages, the LanguageWare algorithm uses constraints in order to determine optimal boundaries. For Chinese, LanguageWare uses statistical processing - word frequencies and collocation frequencies. For Japanese LanguageWare uses a combination of statistical and grammatical processing.
�compliance: A state of being in accordance with established software and security specification on target machines, or the process of becoming so.
�compliance check: (1) In privacy management, the process of determining whether an access attempt to personally identifiable information (PII) complies with all governing privacy policies. See also ruling, conformance check, default ruling.; (2) A group of settings used to determine whether a computer or group of computers is compliant or not. There are two types of compliance checks: software and security.
�compliance report: A report that shows the number of available systems that specified installation activities can be performed on, and the percentages of the states of the installation activities.
�compliance type: In i5/OS licensed management, the value that determines the action the product must take when the authorized usage limit is reached or exceeded. The warning compliance type indicates users are never denied access to a product. The operation action compliance type means that new users are denied access to the product once the usage limit is reached, but users that are currently using the product still have access.
�compliant state: The state of conforming to the defined rules of compliance.
�component: (1) In VisualAge RPG, a functional grouping of classes and related files within a product.; (2) A part of a structured type or value, such as an array element or a record field.; (3) A reusable object or program that performs a specific function and is designed to work with other components and applications.; (4) In Eclipse, one or more plug-ins that work together to deliver a discrete set of functions.; (5) A visual element of a host screen, such as a command line, function key, or selection list. HATS applications transform host components into widgets.; (6) A ClearCase object that is used to group a set of related directory and file elements within a Unified Change Management (UCM) project. Typically, the elements that make up a component are developed, integrated, and released together. A project must contain at least one component, and it can contain multiple components. Projects can share components.; (7) A set of modules that performs a major function within a system.; (8) An entity about which measurements are collected for reporting purposes. Sample components include a specific network storage device; the Web address http://www.ibm.com; and a person with whom you have a customer relationship. Each component type in the data model has a set of metrics and attributes that apply to all components of that type.; (9) A common component or an assembly. See also common component, assembly.; (10) A named, cataloged collection of stored records, such as the data component or index component of a key-sequenced file or alternate index. A component, the lowest member of the hierarchy of data structures that can be cataloged, contains no named subsets.; (11) In UML modeling, a model element that represents an autonomous, replaceable part of a system.
�component association: In the IBM Director Rack Manager task, a function that can make a managed system or device rack-mountable when the inventory collection feature of IBM Director does not recognize the managed system or device. The function associates the system or device with a predefined component.
�component-based development (CBD): The creation and deployment of software-intensive systems assembled from components as well as the development and harvesting of such components.
�component depot: In Tivoli Kernel Services, a component that accesses files and other components from the installation depot and pushes them to Tivoli Kernel Services servers. See also installation depot.
�component diagram: In UML modeling, a diagram that shows the physical structure of a system.
�component directory: In z/OS, the root directory of the component's runtime environment.
�component element: An entity in a component where a breakpoint can be set, such as an activity or Java snippet in a business process, or a mediation primitive or node in a mediation flow.
�component framework: In the Reusable Asset Specification (RAS), a collaboration in which all the components are specified with type models; some of them may come with their own implementations. To use the framework, plug in components that fulfill the specifications.
�component instance: (1) A running component that can be running in parallel with other instances of the same component.; (2) A UML model element that represents an actual entity in a system.
�componentization: A re-engineering and transformation of the SWG development model. This transformation is a key part of the IBM On Demand strategy. Its fundamental goals are to make our software business more responsive to customer demands, and to improve development efficiency and effectiveness. Specifically, software componentization is the movement of IBM software development from a monolithic, product-oriented development model to one based on the concept of software offerings composed from the sharing of reusable software components. See also consumability.
�componentization facet: A characteristic of software componentization that impacts the various aspects of IBM's software business. The SPX reference architecture takes an inherently evolutionary, iterative, and incremental approach to defining software component characteristics, with each reference architecture release focusing on one or more componentization facets.
�componentize: To re-engineer a product into reusable software components.
�Component Manager: In Tivoli Kernel Services, the component (in every ORB) that sets up the execution environment for other components. The Component Manager maintains each component over its lifetime, applying all upgrades.
�component model: (1) A software development model that provides for consistent packaging of software components; the ability to upgrade part of a system as it is executing; the ability to control, monitor, and deploy software across global networks; and the ability to locate and implement services on a global scale. When developed according to the component model, components have interfaces that are rigorously implemented, are packaged into JAR files, and have dynamic execution environments.; (2) An architecture and an API that allows developers to define reusable segments of code that can be combined to create a program.
�component name: The external name of a component. It is used, for example, in the workbench and in commands. Each component requires a name.
�component object model: A software architecture from DEC and Microsoft, allowing interoperation between ObjectBroker and OLE (Object Linking and Embedding). Microsoft later evolved COM into DCOM.
�component PDSE: In a z/OS environment, a PDSE that contains jobs to define resources to DB2, WebSphere MQ, and the WebSphere Business Integration Message Broker started task. See also partitioned data set.
�component store archive: A starter store archive for a component of a composite store archive. Component store archives are available for each business model. See also composite store archive.
�component system: A pattern that contains other reusable solutions. A component system has extension points and parameters to fill and complete.
�component test: An automated test of one or more components of an enterprise application, which may include Java classes, EJB beans, or Web services. See also abstract test, test pattern.
�component tracing: A facility provided by CICS to track transactions through CICS components and user programs.
�compose: In the XML Extender, to generate XML documents from relational data in an XML collection.
�composed text: Text that has been formatted and that contains text-control information to direct the presentation of the text.
�composed-text data: Data that has been composed into pages. Text formatting programs such as DCF can produce composed text data, which consists entirely of AFP structured fields.
�composed-text page: A page of data composed entirely of AFP structured fields. This type of page is usually the output of a text formatting program such as DCF.
�composed-text print data set: A print data set consisting entirely of structured fields.
�composer: In Java, a class used to map a single complex bean field to multiple database columns. Composition is needed for complex fields that are themselves objects with fields and behavior.
�composite: A class that is related to one or more classes by a composition relationship.
�composite aggregation: See also aggregation relationship.
�composite application: An application representing an open architecture in which components of the applications can be developed by IBM or by independent software vendors.
�composite bar chart: In the GDDM function, a bar chart in which multiple vertical axis values for the same horizontal axis value are stacked one on top of another. See also floating bar chart, multiple bar chart.
�composite bar graph: In Performance Tools, a bar graph in which multiple vertical axis values for the same horizontal axis value are stacked one on top of another. See also floating bar graph.
�composite bean: A bean that is composed of other beans. A composite bean can contain visual beans, nonvisual beans, or both.
�composite block index: An index that contains only dimension key columns and is used to maintain the clustering of data during insert and update activity in a multidimensional clustering (MDC) table. See also clustering block index.
�composite business policy: A runtime aggregation of business policies based on context, content and contract of a service request.
�composite business service (CBS): A collection of business services that work together, along with a client's existing applications, to provide a specific business solution.
�composite catalog entry: A collection of catalog entries that breaks down to its separate components when ordered. See also dynamic kit.
�composite difference: In a compare or merge session, an aggregate of several individual but related changes.
�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.
�composite identity relationship: An identity relationship that relates two business objects through a composite key. The composite key consists of a unique key from a parent business object and a key, which is not unique, from a child business object.
�composite key: (1) An ordered set of key columns of the same table.; (2) A key for a file or record format that is composed of more than one key field.
�composite LEN node: A type 5 node and its subordinate type 4 nodes that support LEN protocols and appear to an attached APPN or LEN node as a single LEN node.
�composite library: The host's virtual view of the Peer-to-Peer Virtual Tape Server (PtP VTS) subsystem. In general, host communication with a library will occur at the composite level with the virtual volumes and drives being defined to the composite library.
�composite model: A large model that contains several smaller models.
�composite network: In MPTN architecture, a single-protocol transport network made up of multiple individual networks running the same transport protocol, each with its own unique net ID.
�composite network node (CNN): A type 5 node and its subordinate type 4 nodes that support APPN network node protocols and appear to an attached APPN or LEN node as a single network node.
�composite part: In VisualAge RPG, a collection of controls selected by the user on the GUI designer tool suite and then placed in the parts palette.
�composite project: A container holding projects or composite projects, or both. Composite projects are used to organize the projects associated with the software application.
�composite service: In service-oriented architecture, a unit of work accomplished by an interaction between computing devices.
�composite state: (1) A state that consists of either concurrent substates or sequential substates. See also disjoint substate.; (2) In a business state machine, an aggregate of one or more states that is used to decompose a complex state machine diagram into a simple hierarchy of state machines.

�composite store archive: A compressed file that contains the organization structure, predefined user roles, and necessary access control policies to create the appropriate store environment, plus a working starter store or site. Each of the parts that make up the composite store archive are also available as separate store archives. See also store archive, component store archive.
�composition relationship: In UML modeling, an aggregation relationship that specifies that the lifetime of the part classifier depends on the lifetime of the whole classifier. See also aggregation relationship.
�Composition Services: The component of the WebSphere Commerce messaging system that provides a formatted output for messages using JSP templates.
�compound condition: In COBOL, a statement that tests two or more relational expressions. The result can be true or false.
�compound element: An item in the source or target document that contains child items, such as EDI Segments and EDI composite data elements, ROD records and ROD structures in record oriented data, and XML elements.
�compound key: In a relational database, a key that consists of two or more attributes in a relation.
�compound license: In License Use Management, a type of license that allows a system administrator to generate license passwords for a given number of licenses. Such a license is valuable when an administrator needs a certain number of licenses, but does not yet know what machines or who will use them.
�compound rule: A rule that specifies a causal relationship between two event classes. See also simple rule.
�compound SQL statement: A block of SQL statements that is executed in a single call to the application server.
�compound symbol: In REXX, a symbol that permits the substitution of variables within its name, when referred to. A compound symbol contains at least one period and at least two other characters. It cannot start with a digit or a period, and if there is only one period in the compound symbol, it cannot be the last character. The compound symbol begins with a stem (that part of the symbol up to and including the first period). The stem is followed by the tail (the parts of the name, delimited by periods, that are constant symbols, simple symbols, or null). Compound symbols allow the construction of arrays, associative tables, lists, and so on.
�compound variable: In REXX, a symbol that contains at least one period, one character before the period, and one character after the period. A compound variable cannot start with a digit or period.
�compound word: A morphologically complex word constructed out of two or more word formation elements, such as 'snowboard' and 'post office'. See also multiword expression, solid compound.
�comprehensive command authority: In DFSMShsm, the level of permission that lets a user issue the ABACKUP command for all aggregate groups.
�compress: To reduce the size of a set of data, such as a file, in order to save space or transmission time. See also compressed format.
�compressed audio: A method of digitally encoding and decoding several seconds of voice quality audio per single videodisc frame. This increases the storage capability to several hours of audio per videodisc. Sometimes referred to as still frame audio or sound over still.
�compressed format: A type of extended-format data set. In the Virtual Storage Access Method (VSAM), individual records are put in a compressed-format data set; in the sequential access method (SAM), individual records or blocks are put in a compressed-format data set. See also extended format.
�compressed-format data set: A type of extended-format data set created in a data format that supports record-level or block-level compression.
�compressed listing: In CoOperative Development Environment/400, a graphical representation of the listing of the program currently being debugged. See also compressed source.
�compressed-pattern storage (CPS): In certain printers, storage that holds the extended (double-byte) fonts.
�compressed source: In CoOperative Development Environment/400, a graphical representation of the source of the program currently being debugged. See also compressed listing.
�compressed video: Video resulting from the process of digitally encoding and decoding a video image or segment using a variety of computer techniques to reduce the amount of data required to represent the content accurately.
�compression: A function that removes repetitive characters, spaces, or strings of characters from the data being processed and replaces the repetitive characters with control characters. Compression reduces the amount of storage space required for the data.
�compression dictionary: The dictionary that controls the process of compression and decompression. In DB2 for z/OS, this dictionary is created from the data in a table space or table space partition. In DB2 Database for Linux, UNIX, and Windows, the dictionary is created from the data in each table partition or each table in a database partition. A compression dictionary is specific to the table space, table space partition, or table from which it was created. See also automatic dictionary creation.
�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.
�computed constructor: A constructor that creates element, attribute, document, text, processing-instruction, or comment nodes in which the content of the node is based on enclosed expressions. See also constructor, direct constructor.
�computed field: On a form, a field whose value is determined by a formula that the application designer writes.
�computed time: In the Distributed Computing Environment (DCE), the resulting time after a Distributed Time Service (DTS) clock synchronization. Computed time is the value that the clerk or server process computes according to the values it receives from several servers.
�compute node: A Blue Gene core node on which user applications run.
�computer: A functional unit that can perform substantial computations, including numerous arithmetic operations and logic operations. In information processing, the term computer usually describes a digital computer. A computer can consist of a stand-alone unit or can consist of several interconnected units.
�Computer Assisted Software Engineering (CASE): A set of tools or programs to help develop complex applications.
�computer graphics: The use of a computer to produce visual representations of data, such as charts and multi-dimensional drawings by means of dots, lines, and curves.
�computer group: A group of related computers. An administrator can create computer groups to organize systems into meaningful categories, and to facilitate deployment of patches to multiple computers.
�computer instruction: An instruction that can be recognized by the processing unit of the computer for which it is designed. See also machine language.
�computerized branch exchange (CBX): (1) An exchange in which a central node acts as a high-speed switch to establish direct connections between pairs of attached nodes.; (2) A computer-driven, digital communications controller providing telephone communication between internal stations and external networks.
�computer language: A language that can be used directly by a computer without intermediate processing. See also computer instruction.
�computer-name: In COBOL, a system-name that identifies the computer on which the program is to be compiled or run.
�computer output microfilm (COM): The hardware controller that manages the microfilm print engine and processes the functions unique to COM.
�Computer Science Network (CSNET): A large computer network, mostly in the United States but with international connections. CSNET sites include universities, research labs, and some commercial companies. CSNET has merged with the Because It's Time Network (BITNET) to form the Consortium for Research and Education Network (CREN).
�computer-telephony integration (CTI): The use of a general-purpose computer to issue commands to a telephone switch to transfer calls and provide other services. Typically, CTI is used in call centers.
�computer template: A template that defines the compliant state for installed software and software configuration on the system.
�computer word: A contiguous sequence of 32 bits (four bytes) or characters that can be addressed as a unit. See also halfword.
�computing system catalog: In DFSMShsm, the master catalog and any associated user catalogs used as sources during the audit process.
�computing system RPQ: A customer request for a price quotation on alterations or additions to the functional capabilities of a computing system, hardware product, or device. The RPQ can be used in conjunction with programming RPQs to solve unique data processing problems. See also programming request for price quotation.
�COM setup data: Data that enables the PSF user to designate unique microfilm printing functions for AFP print jobs. The parameter values, structure, syntax, and semantics are defined by the COM manufacturer, not by IBM-controlled architectures.
�concatenate: (1) To link together.; (2) To join two character strings.
�concatenated data set: A group of logically connected data sets that are treated as one data set for the duration of a job step.
�concatenated field: Two or more fields that are combined to make one field in a logical file.
�concatenated key: The key that is constructed to access a particular segment. A concatenated key consists of the key fields, including that of the root segment and successive children, down to the accessed segment.
�concatenation: Joining two characters or strings to form one string.
�concatenation bit: In distributed transaction processing, high order bit of the first byte of the header of a GDS record.
�concatenation operator: (1) The symbol used to join two character data items. In CL, for example, the concatenation operator is two vertical bars (||).; (2) In REXX, an operator used to combine two strings into one by adding the second string to the right end of the first string. The concatenation operators for REXX are a double vertical bar (which concatenates without a blank) and the blank (which concatenates with a blank).
�concentrator: (1) In data transmission, a functional unit that permits a common transmission medium to serve more data sources than there are channels currently available within the transmission medium.; (2) Any device that combines incoming messages into a single message (concentration) or extracts individual messages from the data sent in a single transmission sequence (deconcentration).
�concept extraction: A text analysis function that identifies significant vocabulary items, such as people, places, or products, in text documents and produces a list of those items. See also theme extraction.
�conceptual architecture: The most abstract form of specialization of an architecture, favoring coverage over precision, and specifying a finite set of types for components and for relationships in the system.
�concrete class: (1) A class that can be directly instantiated. See also abstract class.; (2) A class that is not abstract.; (3) A class defining objects that can be created.
�concrete portlet: A logical representation of a portlet object distinguished by a unique configuration parameter (PortletSettings).
�concurrency: The shared use of resources by multiple interactive users or application processes at the same time.
�concurrency control: The management of contention for data resources.
�concurrent: (1) Pertaining to the shared use of resources by multiple interactive users or application programs at the same time.; (2) Pertaining to the occurrence of two or more activities within a given interval of time. Concurrent processes can alternately use shared common resources.
�concurrent connection limit: In OSI, the maximum number of concurrent connections allowed for a given OSI Communications Subsystem node.
�concurrent copy: A function that increases the accessibility of data by creating a consistent copy of the data concurrent with regular processing.
�concurrent copy-compatible SnapShot (CC-compatible SnapShot): See virtual concurrent copy.
�Concurrent Image Copy (CIC): A batch utility program that is used to make a copy of OSAM data sets and VSAM entry-sequenced DBDSs, whether or not IMS is running and the database is online.
�concurrent installation of licensed internal code: The process of installing Licensed Internal Code in a device while the device is in use.
�concurrent maintenance: Service that is performed on a hardware unit while it is operational.
�concurrent media maintenance: Service performed on a disk drive module (DDM) without losing access to the data.
�concurrent server: A server that can handle many connections at the same time. It can accept new connection requests while still processing the transactions started by previous requests. See also iterative server.
�Concurrent Versions System (CVS): An open-source, network-transparent version control system.
�condensed: In SQL replication, a table attribute that indicates that the table contains current data rather than a history of changes to the data. A condensed table includes no more than one row for each primary key value in the table. As a result, a condensed table can be used to supply current information for a refresh.
�condensed CCD table: In SQL replication, a CCD table that contains only the most current value for a row and has only one row for each key value. See also consistent-change-data table, noncondensed CCD table.
�condensed directory catalog: A directory catalog optimized for small size and used primarily on Notes clients.
�condition: (1) An expression that can be evaluated to either true or false. It can be expressed in natural language text, in mathematically formal notation, or in a machine-readable language.; (2) In the Integrated Language Environment (ILE) model, a system-independent representation of an error condition within a high-level language (HLL). For an i5/OS program, each ILE condition has a corresponding exception message.; (3) In REXX, a specific event, or state, that can be trapped by the REXX CALL ON or SIGNAL ON instruction.; (4) An exception that has been enabled, or recognized, by the Language Environment and thus is eligible to activate user and language condition handlers. Conditions can be detected by the hardware/operating system and result in an interrupt. They can also be detected by language-specific generated code or language library code.; (5) The component of a policy expression that specifies the states for which a policy is relevant.; (6) The circumstances or state information of a managed resource that are examined during policy evaluation.; (7) In a business state machine, an expression that guards the transition and only allows the transition to the next state when and if the incoming operation evaluates to 'True'. Otherwise, the current state is maintained.; (8) A test of a situation or state that must be in place in order for a specific action to occur.
�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): (1) In SNA, the value (binary 1) of the conditional end bracket indicator in the request header (RH) of the last request of the last chain of a bracket; the value denotes the end of the bracket. See also end bracket.; (2) An SNA indicator in the request header, FMH5, denoting the end of a conversation between two transactions. See also begin bracket.
�conditional expression: (1) A statement that compares the relationship (such as greater than or equal) of two items.; (2) In COBOL, a simple condition or a complex condition specified in an IF, a PERFORM, or a SEARCH statement.; (3) A compound expression that contains a condition (the first expression), an expression to be evaluated if the condition has a nonzero value (the second expression), and an expression to be evaluated if the condition has the value zero (the third expression).
�conditional external reference: An external reference that causes automatic linking to be performed.
�conditional force: A function that replaces the specified control field character before the record is sorted only if the control field in the input record contains a particular entry.
�conditional loop: In REXX, a loop that allows a set of instructions to be repeated either WHILE or UNTIL a specified condition is met.
�conditional phrase: (1) In COBOL, a phrase that specifies the action to be taken on the determination of the truth value of a condition resulting from the running of a conditional statement.; (2) In REXX, a phrase in a DO instruction, introduced by the subkeyword WHILE or UNTIL, that is used to change the iteration of a repetitive DO loop.
�conditional processing: A page-definition function that allows input data records to partially control their own formatting.
�conditional prompting: A type of prompting that is provided by the system depending on the values selected by the user for other parameters. See also selective prompting.
�conditional restart: A DB2 restart that is directed by a user-defined conditional restart control record (CRCR).
�conditional restart control record (CRCR): A queue of records in the bootstrap data set (BSDS) that is associated with a conditional restart of DB2 for z/OS. Each element in the queue indicates the choices that were made when the record was created and the progress of the restart operation it controls.
�conditional statement: In COBOL, a statement that controls program flow based on the result of the evaluation of a condition.
�conditional variable: In COBOL, a data item, one or more values of which has a condition-name assigned to it.
�condition code: (1) See flag.; (2) A code that reflects the result of a previous input/output, arithmetic, or logical operation.
�conditioned installable unit (conditioned IU): Any installable unit that can be defined within a root installable unit.
�conditioned IU: See conditioned installable unit.
�condition handler: A user-written routine or language-specific routine (such as a PL/ION-unit or C signal() function call) invoked by the Language Environment condition manager to respond to conditions.
�condition handling: The diagnosis, reporting, or tolerating of errors that occur while a routine is running.
�condition information block (CIB): The platform-specific data block used by the Language Environment condition manager as a repository for data about conditions raised in the Language Environment run-time environment.
�conditioning: The use of indicators in a program to control when calculations or output operations are done, or in a file, the use of indicators or condition names to control when certain functions or operations are done.
�conditioning indicator: In RPG, an indicator used to specify when to do calculations or which characteristics apply to a record format or field.
�condition manager: The condition manager is the part of the common execution environment that manages conditions by invoking various user-written and language-specific condition handlers.
�condition name: (1) For display files, a name used to control the selection of DDS keywords and display locations based on the model of the display station.; (2) The name assigned to a status of a user-defined switch.; (3) In COBOL, a name assigned to a specific value, set of values, or range of values within the complete set of values that a conditional variable can have.
�condition-name condition: In COBOL, a statement that the value of a conditional variable is one of a set (or range) of values assigned to a condition name associated with the conditional variable.
�condition rule: In a privacy management environment, a Boolean condition that is applied to a group or purpose in a usage statement to further restrict access to the PII defined in the statement. For example, a condition rule could be applied to a usage statement that restricts access to the PII unless the monitored system contains a recording of the PII owner's explicit agreement to the use of the PII. See also evaluation rule, privacy policy statement.
�condition step: The step of the Language Environment condition handling model that follows the enablement step. In the condition step, user-written condition handlers, C signal handlers, and PL/I ON-units are first given a chance to handle a condition. See also enablement step, termination imminent step.
�condition token: (1) A 12-byte data structure, which is consistent across multiple Systems Application Architecture (SAA) participating systems, that allows the application programmer to associate the condition with the underlying exception message.; (2) In Language Environment, a data type consisting of 96 bits (12 bytes). The condition token contains structured fields that indicate various aspects of a condition including the severity, the associated message number, and information that is specific to a given instance of the condition.
�condition trap: In REXX, the method by which the explicit flow of processing in a REXX program can be changed. Condition traps are enabled or disabled using the ON or OFF subkeywords of the CALL and SIGNAL instructions.
�condition variable: An object that allows a thread to suspend execution when it finds an untrue condition, and to resume execution when another thread makes the condition true.
�conduit: A pipe for protecting electric wires or cables.
�Conference Europeenne des Administrations des Postes et Telecommunications (CEPT): European Conference of Postal and Telecommunications Administration.
�confidence factor: A number between 0 and 100 indicating the level of accuracy of the trended value. The number 0 indicates no confidence. The number 100 indicates a perfectly approximated function.
�confidentiality: (1) In computer security, assurance that sensitive information is not visible to an eavesdropper.; (2) The security service that protects sensitive information from unauthorized disclosure. Encryption is a common mechanism for implementing this service.
�configuration: (1) The manner in which the hardware and software of a system, subsystem, or network are organized and interconnected.; (2) See topology.; (3) The machines, devices, and programs that make up a system, subsystem, or network.; (4) The process of describing to a system the devices, optional features, and program products that have been installed so that these features can be used. See also customization.; (5) In a broker domain, the brokers, execution groups, deployed message sets, and deployed message flows, and the defined topics and access control lists.; (6) The requirements, design, and implementation that define a particular version of a system or system component. See also configuration management.; (7) A type of decision, for both solicited and unsolicited interactions, that controls the properties of a managed resource.; (8) The operating system parameters of a system profile.
�configuration administration: The administration of the configuration object types (CTs), configuration objects (COs), and configuration object sets (COSs) that comprise the configuration data of organizational units (OUs). This is carried out after the product has been installed and customized. See also security administration.
�configuration audit: A physical check on the infrastructure to determine whether the Configuration Management database (CMDB) and the physical configuration items correspond.
�Configuration Change Management System (CCMS): In a Tivoli environment, a data store of profiles that contain configuration data that is used by system management applications to make configuration changes on groups of systems.
�configuration database: The Data Interchange Services client database that stores parameters necessary for running Data Interchange Services client, including database definitions, messages, queries, and preferences.
�configuration directory: A directory in a central directory architecture that contains only documents related to Domino configuration.
�configuration entity: WebSphere BI for FN entities used to model an organization, and to specify how messages are processed. These entities include configuration object types (CTs), organizational units (OUs), configuration object sets (COSs), configuration objects (COs).
�configuration event: Notifications about the attributes of an object. The notifications are generated when the object is created, changed, or deleted and also by explicit requests.
�configuration file: (1) A file that specifies the characteristics of a program, system device, system, or network.; (2) In performance, a file that contains information about a collection as well as certain system attributes.; (3) A file that contains the values that are specified for configuration parameters. There are two types of configuration files: the database manager configuration file for each DB2 instance and the database configuration file for each individual database.; (4) See parameter file.; (5) A Struts file that contains information about data sources, form beans, global forwards, and action mappings.; (6) In WebSphere MQ on UNIX systems and WebSphere MQ for iSeries, a file that contains configuration information for logs, communications, or installable services.
�Configuration File Manager (CFM): A file repository that synchronizes and maintains file consistency across nodes in a cluster.
�configuration, installation, and distribution (CID): An IBM architecture that provides for the remote, unattended installation and configuration of applications.
�configuration item (CI): (1) An entity in a configuration that satisfies an end-use function and can be uniquely identified at a given reference point.; (2) Any component of an information technology infrastructure that is under the control of configuration management.
�configuration list: A list of local or remote locations, network addresses, or pass-through device descriptions used by some types of communications descriptions. The system-recognized identifier for the object type is *CFGL.
�configuration management (CM): (1) The control of information necessary to identify both physical and logical information systems and their relationship to one another.; (2) A supporting process whose purpose is to identify, define, and baseline items; control modifications and releases of these items; report and record status of the items and modification requests; ensure completeness, consistency and correctness of the items; and control storage, handling and delivery of the items. See also configuration.; (3) The process of planning for, identifying, controlling, and verifying the configuration items within a service, recording and reporting their status and, in support of change management, assessing the potential impact of changing those items.
�configuration management database (CMDB): A database that contains details about the attributes and history of each configuration item and the details about the relationships between configuration items.
�Configuration Manager: The component that provides an interface between the workbench, the configuration repository, and a set of runtime brokers. It provides brokers with their initial configuration, and updates them with any subsequent changes. It maintains the broker domain configuration.
�configuration node: A node that acts as the focal point for configuration commands and manages the data that describes the cluster configuration.
�configuration object (CO): An instance of a configuration object type (CT) that represents an object in an organizational unit (OU). Which attributes can be added to a CO is determined by the definition of the CT on which the CO is based.
�configuration object set (COS): A set of configuration objects, used to limit the scope of configuration data provided to message flows.
�configuration object type (CT): A description of the class of configuration objects, including the attributes that each member of this class can have.
�configuration parameter: (1) A parameter whose value limits or defines the resources that can be used by the database manager or a database. Some configuration parameters are informational and define characteristics about the environment that cannot be changed. See also database configuration parameter.; (2) A variable that controls the behavior of the system or the behavior of all applications running on the system.
�configuration program: In Tivoli Software Distribution, Version 3, the feature that enables a Tivoli administrator to perform operations (a) before or after file package distributions, (b) before or after file package removal, (c) during a file package commit operation, or (d) after an error stops a distribution or removal operation.
�configuration report server (CRS): A function that resides on each ring in an environment of multiple token-ring networks in which configuration is being monitored. This function receives notifications about inserting and removing stations and notifications about active monitor failures.
�configuration repository: (1) A RIM repository that contains information stored by inventory scans and software distributions.; (2) The persistent storage for broker configuration and topology definition. It is a DB2 database managed by the Configuration Manager.; (3) A storage area of configuration data that is typically located in a subdirectory of the product installation root directory.
�Configuration Section: In COBOL, a section of the Environment Division of a program, which describes the overall specifications of the source and object computers.
�configuration service: Service activating, deactivating, and maintaining the status of physical units, links, and link stations.
�configuration specification (config spec): A set of rules that specify which versions of VOB elements a view selects. The config spec for a snapshot view also specifies which elements to load into the view.
�configuration unit: The file or set of files that comprise the atomic unit of configuration.
�configurator: Software that provides a dynamic rules-based kit (bundling) capability to determine a group of items that may be sold together. The configurator may also supply a price for the configuration. This grouping is based on pre-defined rules in addition to user interaction with the configurator. See also dynamic kit.
�configure: (1) To describe the interconnected arrangement of the devices, programs, communications, and optional features installed on a system.; (2) To describe setting up auxiliary storage pools and checksum protection.; (3) In storage, to define the logical and physical configuration of the I/O subsystem through the user interface that the storage facility provides for this function.
�configured name binding: Persistent storage of an object in the name space that is created using either the administrative console or the wsadmin program.
�configured test case: A test case that is used to run a test script for a specific test configuration.
�confirm: In OSI, a service primitive issued by a service provider to complete the procedures associated with a confirmed service.
�confirmation of delivery: The automatic notification to the sender of a message, note, or document as to when action is taken on the message, note, or document. Confirmation of delivery must be requested by the sender.
�confirmation panel: In DFSMSrmm, a panel that signals DFSMSrmm whether to continue or stop a delete or release action. Confirmation of delete or release requests is specified in the dialog user options.
�confirmed service: In OSI, a service that indicates to the sender whether or not data or control information was properly received. A confirmed service involves a request, indication, response, and confirm service primitive. See also unconfirmed service.
�confirm-on-arrival report (COA report): A WebSphere MQ report message type created when a message is placed on that queue. It is created by the queue manager that owns the destination queue.
�confirm on delivery (COD): A feature of WebSphere MQ that allows a notification to be sent to a source application whenever a target application receives a message from the source application.
�confirm-on-delivery report (COD report): A WebSphere MQ report message type created when an application retrieves a message from the queue in a way that causes the message to be deleted from the queue. It is created by the queue manager.
�conflict: (1) In a compare or merge session, the result when two contributors have changes that cannot both be accepted.; (2) A result that occurs when two simultaneous edit submissions are processed for the same object and where the intended outcome of the edit is unclear.
�conflict detection: The process of determining whether a replicated change (an insert, an update, or a delete) is incompatible with some characteristic of a target. An incompatibility exists, for example, if changes were made to both a source and a target before replication occurred. See also replica table, master table.
�conflict group: In a compare or merge session, a collection of conflicts that are associated with one or more changes in a composite difference.
�conflicting reference: An external reference from a Fortran or assembler language routine to a Fortran library routine with a name that is the same as the name of a C/C++ library routine. The reference is considered to be a conflicting reference only when the intended resolution is to the Fortran library routine rather than to the corresponding C/C++library routine.
�conformance: In privacy management, the process of determining whether a request for personally identifiable information (PII) matches the rules defined in a single governing privacy policy. See also conformance check.
�conformance check: In privacy management, the process of determining whether an access attempt to personally identifiable information (PII) conforms to a single governing privacy policy. See also ruling, compliance check, conformance, default ruling.
�conformance document: A document provided by an implementer (such as IBM) that contains implementation details as described in the current POSIX.1 standard.
�conformant array: In DCE Remote Procedure Call (RPC), an array whose size is determined at runtime. A structure containing a conformant array as a field is a conformant structure.
�confounder: A bit string that is used to initialize the encryption-block chaining value so that the encrypted result is different each time a data value is encrypted.
�conjunction: The Boolean operation whose result has the Boolean value 1 if and only if each operand has the Boolean value 1.
�connect: In a LAN, to physically join a cable from a station to an access unit or network connection point.
�connect data set to line: In SNA, an option that determines how the data terminal ready (DTR) signal to the modem operates. It is used if a DTR indicates an unconditional command from the data terminal equipment (DTE) to the attached data circuit-terminating equipment (DCE) to connect to or remove itself from the network.
�connected: In a remote copy relationship, pertaining to the condition that occurs when two clusters can communicate.
�connection: (1) In data communication, an association established between entities for conveying information. See also SQL connection.; (2) A combination of two endpoints that the virtual private network (VPN) protects and a security policy. Such a connection can exist between any combination of a host and a gateway.; (3) In Open Systems Interconnection architecture, an association established by a given layer between two or more entities of the next higher layer for the purpose of data transfer.; (4) A set of parameters used by HATS to connect to a host application, stored in an .hco file. See also background connection, default connection.; (5) A link between two process elements. Connections can be used to specify the chronological sequence of activities in a process.
�connection concentrator: An approach that allows applications to stay connected without any resources being consumed on the DB2 host server. Thousands of connections can be active while only a few agents are active on the DB2 host server.
�connection context: In SQLJ, a Java object that represents a connection to a data source.
�connection control block (CCB): A control block created by CICS for each IRC session. The CCB contains control information for the inter-region connection and a pointer to the CSB.
�connection declaration clause: In SQLJ, a statement that declares a connection to a data source.
�connection document: A document that enables communication between two servers and specifies how and when the information exchange occurs.
�connection event sequence (CES): This value is copied to full name (NCC) records and used by the path manager to determine the most current record pertinent to the tracking of full name (NKJE) connections.
�connection factory: A set of configuration values that produces connections that enable a Java EE component to access a resource. Connection factories provide on-demand connections from an application to an enterprise information system (EIS) and allow an application server to enrol the EIS in a distributed transaction.
�connection handle: (1) The data object containing information that is associated with a connection that is managed by DB2 ODBC. This information includes general status information, transaction status information, and diagnostic information. See also statement handle.; (2) The identifier or token by which a program accesses the queue manager to which it is connected.; (3) A representation of a physical connection.
�connection ID: See connection identifier.
�connection identifier (connection ID): A DB2 for z/OS identifier that is supplied by the attachment facility and that is associated with a specific address space connection.
�connectionless mode: A mode of transfer in which data is passed from one user to another in self-contained units with no logical relationship required among the units.
�connectionless-mode network protocol (CLNP): The OSI protocol defined by ISO 8473. This protocol is used to provide the connectionless-mode network service (CLNS).
�connectionless-mode network service (CLNS): In OSI, an unacknowledged network service that enables an entity to send a unit of data from a source service access point to one or more destination service access points without establishing a connection. The OSI protocol that provides this service in the Network Layer is defined by ISO 8473 (internet protocol, or IP).
�Connectionless Network Protocol (CLNP): An OSI protocol for the delivery of data. CLNP uses datagrams (packets) that include address information for routing network messages. CLNP is used in local area networks (LANs) rather than wide area networks (WANs).
�connectionless protocol: In the Distributed Computing Environment (DCE), a remote procedure call (RPC) transport protocol, such as User Datagram Protocol (UDP), that does not require a connection to be established prior to data transfer. See also connection-oriented protocol.
�connectionless service: (1) See unacknowledged service.; (2) A network service that treats each packet or datagram as a separate entity that contains the source address and destination address and for which no acknowledgment is returned to the originating source. Connectionless services are on a best-effort basis and do not guarantee reliable or in-sequence delivery. See also connection-oriented network service.
�connection list: A communications object for ISDN that provides a list of information used to determine when to accept incoming calls and what information to send with outgoing calls. The system-recognized identifier for the object type is *CNNL.
�connection manager: A Content Manager component that helps maintain connections to the library server, rather than starting a new connection for each query. The connection manager has an application programming interface.
�connection modem: In Operations Console, a driver (cwbopaoc.inf file) that allows a console to connect to the server.
�connection-mode network service: In OSI, an acknowledged network service that enables an entity to send a unit of data from a source service access point to a destination service access point by establishing, maintaining, and disconnecting a connection. The OSI protocol that provides this service in the network layer is defined by the X.25 Packet-Level Protocol defined by CCITT 1980 and 1984.
�connection network: A switched network (such as a local area network, X.25, or public-switched dial network) that allows a local node to establish APPN connections to more than one undefined adjacent node.
�connection-oriented network service (CONS): A type of networked data communication in which a dedicated connection between two peer entities is established before data is transferred. A connection-oriented service consists of three phases: establishment, data transfer, and release. The two networks exchange address information only while the connection is being established. See also connectionless service.
�connection-oriented protocol: In the Distributed Computing Environment (DCE), a Remote Procedure Call (RPC) protocol that runs over a connection-based transport protocol. It is a reliable, virtual-circuit transport protocol, such as TCP. See also connectionless protocol.
�connection point manager: In SNA, a component of the transmission control layer that performs session-level pacing of normal-flow requests, (b) checks sequence numbers of received request units, (c) verifies that request units do not exceed the maximum permissible size, (d) routes incoming request units to their destinations in the half-session, and enciphers and deciphers FMD request units when cryptography is selected.
�connection pool: A group of host connections that are maintained in an initialized state, ready to be used without having to create and initialize them.
�connection pooling: (1) A process in which an application server or any product that interacts with a database on behalf of applications establishes a finite set of connections to the database and maps requests from the applications to this set of connections. Using these connections reduces the overall connection time for these applications and removes the cost of establishing a database connection from the host.; (2) A technique used for establishing a pool of resource connections that applications can share on an application server.
�connection profile: A set of data that is used to establish a connection.
�connection script: Data, such as sign-on and password information, that is exchanged between the host and remote systems when a connection is established.
�connection status block (CSB): A control block created by CICS for each IRC session. The CSB contains status information about the inter-region connection.
�connective: In COBOL, a word or a punctuation character that associates a data name, paragraph name, condition name, or text name with its qualifier; links two or more values in a series; or forms a conditional expression.
�connectivity: (1) The capability of a system or device to be attached to other systems or devices without modification.; (2) The degree to which storage controls are joined to a direct access storage device (DASD) and processors to achieve adequate data paths (and alternative data paths) to meet data availability needs.
�connector: (1) In a query management command, the TO word in the EXPORT command, the FROM word in the IMPORT command, or the AS word in the SAVE DATA command.; (2) In Java EE, a standard extension mechanism for containers to provide connectivity to enterprise information systems (EISs). A connector consists of a resource adapter and application development tools (Sun). See also container.; (3) A servlet that provides a portlet access to external sources of content, for example, a news feed from a Web site of a local television station.; (4) The component of an adapter that uses business objects to send information about an event to an integration broker (inbound) or receive information about a request from the integration broker (outbound). A connector consists of the Websphere Adapter Foundation Classes and the connector's application-specific component.; (5) A plug-in that is used to access and update data sources. A connector accesses the data and separates out the details of data manipulations and relationships.
�connector agent: The subcomponent of a connector that interacts with a defined interface of an application or URL.
�connector class: (1) An object class that is used for objects that connect different parts of the network and route or switch traffic between these parts. This class includes gateways, repeaters (including multiport repeaters), and bridges. See also network class.; (2) Object-oriented programming class that provides standard access to APIs that are native to specific content servers.
�connector configuration property: A configuration setting used by the connector. Connectors use standard and connector-specific configuration properties, which can be set using System Manager. After the values are set, they are saved in the repository. See also connector-specific configuration property, standard connector configuration properties.
�connector controller: The subcomponent of a connector that interacts with collaborations. A connector controller runs within InterChange Server and initiates mapping between application-specific and generic business objects, and manages collaboration subscriptions to business object definitions.
�connector development kit (CDK): C++ class libraries used when developing a C++ connector. These libraries contain predefined classes that are used to derive connector classes and libraries. Also, they provide methods for implementing services such as tracing and logging.
�connector-specific configuration property: A configuration setting whose value determine how the connector interacts with the application and processes business objects. These properties are specific to each connector. See also connector configuration property, standard connector configuration properties.
�connect phase: An optional phase of link activation during which initial communication is established. It includes dialing and answering on switched links and can include modem equalization. The connect phase is followed by the optional prenegotiation phase or by the contact phase.
�CONS: See connection-oriented network service.
�consecutive processing: A method of processing in which the records in the file are read, written to, or deleted in the order in which they exist in a file. See also random processing, sequential processing.
�Conseil Europ�en pour la Recherche Nucl�aire (CERN): (European Laboratory for Particle Physics) Located in Geneva, Switzerland, CERN initiated the World Wide Web and was the first organization to create a Web server. The CERN Web server is the basis for many commercially available servers.
�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 property.
�consistency group: A group of copy relationships between virtual volumes or data sets that are maintained with the same time reference so that all copies are consistent in time.
�consistency token: A unique identifier that is generated during precompilation, stored in the application source, and sent to the database when the package is bound. The consistency token is used to ensure the integrity of the shared application information that is stored in the database as a package.
�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.
�consistent-change-data table (CCD table): In SQL replication, a type of replication target table that is used for storing history, auditing data, or staging data. A CCD table can also be a replication source. See also condensed CCD table, external CCD table, internal CCD table, noncondensed CCD table, staging table.
�consistent copy: (1) A copy of a data entity (a logical volume {LVOL}), for example) that contains the contents of the entire data entity at an instant in time.; (2) In a remote copy relationship, a copy of a secondary virtual disk (VDisk) that is identical to the primary VDisk from the viewpoint of a host system, even if a power failure occurred while I/O activity was in progress.
�consistent read: An integrity option that Virtual Storage Access Method record-level sharing (VSAM RLS) obtains for a share lock on a record. Consistent read ensures that the reader does not see an uncommitted change made by another transaction.
�consistent read explicit: An integrity option that Virtual Storage Access Method record-level sharing (VSAM RLS) obtains for a share lock on a record; VSAM RLS then keeps the share lock on the record until the end of transaction. This option is available only to Customer Information Control System (CICS) transactions because VSAM does not recognize the end of transaction for non-CICS usage. This capability is also referred to as repeatable read.
�console: (1) A display station from which an operator can control and observe the system operation.; (2) In COBOL, a function name associated with the operator's display station.; (3) A user interface for one or more administrative tasks. For example, the IBM Integrated Solutions Console integrates the administrative tasks for multiple products and solutions into a single console.; (4) A user interface to a server, such as can be provided by a personal computer.
�console authority level: A numeric value from 0 - 15 assigned to remote job processing (RJP) consoles, which governs the set of commands that can be issued from the console.
�console communication service (CCS): The SNA facility that acts as an interface between the control program and the VSCS component of VTAM for VM.
�console destination class: One of a set of named classes used to direct messages to certain consoles. Console destination classes also are used in specifying the messages to be received at a remote job processing (RJP) console.
�console event: An event sent by a monitor to a console.
�console module deployment descriptor: An XML file that describes the following elements that need to be known when a console module is included in the IBM Integrated Solutions Console framework: navigation tree contributions, page layout definitions, access control information, prerequisite portlet or console modules, and extension points.
�console server: The hardware device through which the management server opens a remote console session for a node.
�console service: A dynamic support program (DSP) that performs traffic management for consoles.
�consolidated software inventory (CSI): A key-sequenced VSAM data set, used by SMP/E and logically divided into zones.
�CONS path: In OSI, a path that indicates both quality-of-service values through a network QOS mode and values to indicate how splitting and multiplexing is to be accomplished. A CONS path can optionally be reserved for outbound communications to a specific DTE at an adjacent node.
�CONS path set: In OSI, a path set used when the connection-mode network service is used.
�constant: (1) A language element that specifies an unchanging value. Constants are classified as string constants or numeric constants.; (2) Data that has an unchanging, predefined value to be used in processing.
�constant expression: An expression that has a value that can be determined during compilation and that does not change during the running of the program.
�constant field: (1) In an externally described display or printer file, an unnamed field that contains actual data that is passed to the display or printer but is unknown to the program passing it.; (2) A field defined by a display format to contain a value that does not change.
�constant propagation: An optimization technique where constants used in an expression are combined and new ones are generated. Mode conversions are done to allow some intrinsic functions to be evaluated at compile time.
�constant symbol: In REXX, a symbol that starts with a digit (0-9) or a period. The value of a constant symbol cannot be changed.
�constraint: (1) A rule that limits the values that can be inserted, deleted, or updated in a table. See also check constraint, primary key, referential constraint, unique constraint, unique key, foreign key, informational constraint.; (2) A place in the system where contention for a resource is affecting performance.; (3) See threshold.; (4) A semantic condition or restriction. Certain constraints are predefined in the UML, others may be user defined. Constraints are one of three extensibility mechanisms in UML. See also tagged value, comment.; (5) A limit to set controls on the start and finish dates on task elements of the project, such as start-no-earlier-than or finish-no-later-than.; (6) In lexical analysis, a morphotactics rule that accurately processes compound words using dictionaries of word formation elements.
�constraint cycle: A sequence of constraint relationships in which a descendent of a parent file becomes the parent to the original parent file.
�construct: One of the following collective concepts: data class, storage class, management class, storage group, aggregate group, and base configuration.
�constructed reentrancy: The attribute of applications that contain external data and require additional processing to make them reentrant. See also natural reentrancy.
�construction: The phase of the software development life cycle in which the product is coded and tested.
�constructor: (1) In object-oriented programming, a special method used to initialize an object.; (2) A special C++ class member function that has the same name as the class and is used to create an object of that class.; (3) An XQuery expression that creates XML structures within a query. See also computed constructor, constructor function, direct constructor.
�constructor function: In XQuery, a constructor where the expression is a function invocation that creates a typed atomic value. See also constructor.
�constructor method: In programming languages, a method that has the same name as a class and is used to create and initialize objects of that class.
�consumability: The ease with which our customers can evaluate, buy, attain, install, and deal simply and effectively with product maintenance throughout the offering lifecycle.
�consumer: See client.
�consumer application: An application that uses the data in the central data warehouse for a specific business need. Consumer applications use reporting and third-party online analytical processing (OLAP) tools as well as planning, trend-tracking, analysis, accounting, and data mining tools. See also source application.
�consumer direct: The consumer direct business model supports commerce transactions involving products, services, or information between businesses and consumers. Consumers typically purchase goods or services directly from a business in a consumer direct scenario. The FashionFlow starter store is an example of a consumer direct business. See also direct sales business model, B2B direct business model.
�consumer server: A server which receives changes through replication from a supplier server.
�consumption: The usage of a resource. See also saturation.
�contact: A person whose ID is configured to receive e-mail or pager notifications of DB2 administration messages that are written to the administration notification log. The definition for each contact contains the name and the e-mail or pager address of the person to receive notifications and is stored in the contact list of the system that is specified by the CONTACT_HOST configuration parameter of the DB2 administration server. See also administration notification message, administration notification log, orphaned contact.
�contact list: A directory database that is stored on a Notes client and contains the names and addresses of users and groups added by Notes users.
�contact phase: A phase of link activation during which negotiation-proceeding XID3s are exchanged between the connected link stations to establish the primary and secondary roles of the link stations, the TG number to be used, and other characteristics of the link, and during which the mode-setting command is sent and acknowledged after the primary and the secondary roles are established. Link activation may consist only of the contact phase, or it may also have either a connect phase or a prenegotiation phase or both preceding the contact phase.
�contained CIU: See contained container installable unit.
�contained container installable unit (contained CIU): A dedicated container installable unit (CIU) of an aggregated installable unit (aggregated IU). A contained CIU is intended to be deployed to a single hosting environment. For each instance of a contained CIU, a new, dedicated, installable unit (IU) instance is created (unless the installable unit is an update or fix) and a has component relationship is registered.
�contained installable unit (contained IU): A dedicated installable unit of an aggregation. A contained installable unit is intended to be deployed to one or more hosting environments. For each instance of a contained installable unit, a new dedicated installable unit instance is created (unless the installable unit is an update or fix) and a HasComponent relationship is registered.
�contained IU: See contained installable unit.
�container: (1) In CoOperative Development Environment/400, a system object that contains and organizes source files. An i5/OS library or an MVS-partitioned data set are examples of a container.; (2) A software object that holds or organizes other software objects or entities.; (3) A data storage location: for example, a file, directory, or device. See also table space.; (4) An entity that provides life-cycle management, security, deployment, and runtime services to components. (Sun) See also resource adapter, connector.; (5) A column or row that is used to arrange the layout of a portlet or other container on a page.; (6) An instance that exists to contain other instances, and that provides operations to access or iterate its contents; for example, arrays, lists, or sets.; (7) In a virtual tape server (VTS), a receptacle in which one or more exported logical volumes (LVOLs) can be stored. A stacked volume containing one or more LVOLs and residing outside a VTS library is considered to be the container for those volumes. See also stacked volume.; (8) A group of stages and links in a job design.
�container class: In Backup, Recovery, and Media Services, an object that defines the types of physical containers that are used to store and transport removable media. Container classes are distinguished by attributes such as capacity and media class.
�container installable unit (CIU): An aggregated installable unit that is intended to be deployed on a single hosting environment. See also smallest installable unit.
�container-managed persistence (CMP): The mechanism whereby data transfer between an entity bean's variables and a resource manager is managed by the entity bean's container. (Sun) See also bean-managed persistence.
�container-managed transaction: (1) A transaction whose boundaries are defined by an EJB container. An entity bean must use container-managed transactions. (Sun); (2) A transaction where the EJB container is responsible for administration of tasks such as committal or rollback. See also bean-managed transaction.
�container management: In Backup, Recovery, and Media Services, a function that assigns container classes and tracks containers by storage location for retention, reuse, and recovery.
�container object: A structural designation that organizes the object space into distinct functional regions.
�container transaction: See container-managed transaction.
�container window: A window that lists the names of all existing objects of the same type.
�containment hierarchy: A namespace hierarchy consisting of model elements, and the containment relationships that exist between them. A containment hierarchy forms an acyclic graph.
�containment relationship: A relationship between two objects where one object is contained within the other. The destination is nested within the source.
�content: (1) Any launchable asset; the physical files that make up a course offering.; (2) In the Reusable Asset Specification (RAS), a section of an asset that contains a collection of artifacts providing a solution to a problem.; (3) The data semantics of a message that is received by the dynamic assembler.
�content aggregation: See course structure.
�content area: In a Web page that is based on a page template, the editable region of the page.
�content assist: A feature of some source editors that prompts the user with a list of valid alternatives for completing the current line of code or input field.
�content-based filter: In publish/subscribe, an expression that is included as part of a subscription to determine whether a publication message is received based on its content. The expression can include wildcards.
�content based routing (CBR): An optional feature of the caching proxy that provides intelligent routing to back-end application servers. This routing is based on HTTP session affinity and a weighted round-robin algorithm.
�content class: (1) See MIME type.; (2) A collection of subjects that users need to complete a universal task. Examples include planning, installing, administering and problem determination.
�content contributor: A role in the pre-defined workflow process shipped with WebSphere Portal content publishing. Users assigned to the role of content contributor can create and edit content.
�content delivery server: A server that delivers course content to the client and provides content tracking and navigation features. See also LMS server.
�contention: (1) A situation in which a transaction attempts to lock a row or table that is already locked.; (2) A condition on a session when two programs try to start a conversation at the same time.
�contention loser: On an LU-LU session, the LU that must use an SNA BID command (LUTYPE6.1) or an LUSTATUS command (APPC) to request permission to begin a conversation.
�contention-loser session: To a network accessible unit (NAU), a contention-loser session is a session for which it was defined during session initiation to be the contention loser. See also contention-winner session.
�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 state: In data communications, a type of half-duplex line or data link control in which either user may transmit any time the line or link is available. If both users attempt to transmit at the same time, the protocols or the hardware determines who goes first.
�contention winner: On an LU-LU session, the LU that is permitted to begin a conversation at any time.
�contention-winner session: To a network accessible unit (NAU), a session for which it was defined during session initiation to be the contention winner. See also bidder session.
�content management: (1) Software designed to help businesses manage and distribute content from diverse sources.; (2) The process of managing, organizing, storing, tracking ownership of, and distributing information that was created for a common purpose.
�content model: The representation of any data that may be contained inside an XML element. There are four kinds of content models: element content, mixed content, EMPTY content and ANY content.
�content partner: See IBM content partner.
�content provider: A source for content that can be incorporated into a portal page as a portlet.
�content publisher: A role in the pre-defined workflow process shipped with WebSphere Portal content publishing. Users assigned to the role of Content Publisher have authority to publish content to production servers.
�content resource: Java classes (.class), Java archive (.jar), and resource (.hrf, or XML) files that reference user data or Web content (such as text, a graphic, an applet, or JavaScript) contained in an external data store.
�content server: A software system that stores multimedia and business data and the related metadata required for users to work with that data. Content Manager and Content Manager ImagePlus for OS/390 are examples of content servers.
�content spot: A class file that is added to a JSP file to designate display of personalized data or content. Each content spot has a name and will accept a specific type of data from a rule.
�contents view: A view of an object that shows the contents of the object in list form. Container views are provided for containers, and for any object that has container behavior, for example, a device object such as a printer. Icons view and details view are examples of contents views.
�content type: A specification type for the autonomic computing architecture that defines the enumerated set of instance values for a data segment.
�context: (1) One or more units of recovery, with the associated application programs, resource managers, and protected resources. A context represents a work request in an application, and the life of a context consists of a series of units of recovery.; (2) A set of one or more grammars that are enabled and used during a recognition action.; (3) 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.; (4) A view of a set of related modeling elements for a particular purpose, such as specifying an operation.; (5) The address space for a process, hardware registers, and related kernel data structures.; (6) In ODBC, an application's logical connection to the data source and associated DB2 ODBC connection information that allows the application to direct its operations to a data source. A DB2 ODBC context represents a DB2 thread.; (7) An object created for a service request in the business service model. The object contains one or more of the following details of information captured from the metadata: a business process, organization, role, channel, and domain specific information. See also context propagation.
�context handle: In the Distributed Computing Environment (DCE) Remote Procedure Call (RPC), a reference to a client context maintained across remote RPCs by a server on behalf of a client.
�context interest token: A token provided to the resource manager expressing interest in a context.
�context item: The item in a sequence that is currently being processed in an XQuery expression. See also context position, context node.
�context name: The name given to a context in a context profile used for WebSphere Voice Server.
�context node: A context item that is a node. See also context item.
�context parameter: A definition of the server view of the Web application within which the servlet is running and supports servlet access to available resources.
�context position: The position of the context item within the sequence of items. See also context item.
�context profile: Describes to the WebSphere Voice Server process which contexts should be loaded into an engine. A DirectTalk for Windows application specifies which context profiles to load into the engine it has reserved.
�context propagation: In a multiple service transaction, the information about the details of a service request that passes from one invocation to another via the message header. See also context.
�context root: (1) The Web application root, which is the top-level directory of an application when it is deployed to a Web server.; (2) A relative name in the Web namespace that identifies a Web application.
�context security: On z/OS, the authority checks that are performed when an application opens a queue and specifies that it will set the context in messages that it puts on the queue, or pass the context from messages that it has received to messages that it puts on the queue.
�context services: The z/OS system component that provides services used to track a work request and allow a resource manager to express interest in the work request.
�context size: The number of items in the sequence of items that is currently being processed. See also focus.
�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.
�context token: A token that represents a work request's context.
�context type: Indicates to the recognition engine how to interpret the grammar file. Possible types are: VOCAB_FILE, GRAMMAR_FILE, TEXT, MNR_FILE, MNR, PERSONAL_FILE, PERSONAL_WDS, BASEFORM_FILE.
�contiguous item: In COBOL, an elementary or group item that is adjacent to another elementary or group item in the Data Division, contained in the same data hierarchy.
�contiguous space: An unbroken consecutive series of storage locations.
�contingent allegiance: In mainframe computing, a relationship that is created in a control unit between a device and a channel when the channel accepts unit-check status. Contingent allegiance causes the control unit to guarantee access; that is, the control unit does not present the busy status to the device. It also enables the channel to retrieve sense data that is associated with the unit-check status on the channel path associated with the allegiance. See also reserved allegiance, implicit allegiance.
�contingent resource: Monies or time placed in reserve to accommodate assessed project risks.
�continuation character: (1) A character represented by a plus sign (+) that lets a command be extended to more than one line.; (2) In REXX, a character represented by a comma that lets a clause be extended to more than one line. This character is functionally replaced by a blank and cannot be used in the middle of a string or comment.
�continuation handle: A value, which is passed between a high-level language program and a list application programming interface (API), used to mark the last value put in the user space.
�continuation line: (1) A line of a source statement where characters are entered when the source statement cannot be contained on the previous line or lines.; (2) An additional line (or lines) required to continue the coding of a CL command or a DDS keyword and its value.; (3) In RLU, a report line or sample line that is part of a record format or a group of sample lines excluding the first line in the record format or group of sample lines.; (4) In RPG, additional lines specified on the file description specifications to provide more information about the file being defined.
�continuation mode: In VTAM, the state of a conversation or session, which is either continue-any mode or continue-specific mode.
�continued-entry field: In DDS, a panel element that contains a field that contains a set of associated entry fields.
�continuous forms: A series of connected forms that feed continuously through a printing device. The connection between the forms is perforated so that the user can tear them apart. Before printing, the forms are folded in a stack, with the folds along the perforations. See also cut-sheet paper.
�continuous-forms stacker (CFS): In continuous-forms printers, an output assembly that refolds and stacks continuous forms after printing.
�Continuous Linked Settlement (CLS): The method of settling payments arising from foreign exchange trades that effects settlement by simultaneously debiting and crediting counterparty accounts in all relevant currencies across the CLS bank.
�continuously powered main storage (CPM): The function of supplying power only to main storage (cards) for a varied amount of time (for example, one day) when utility power is lost on systems that have a system power control network (SPCN).
�continuous speech recognition: Recognition of words spoken in a continuous stream. Unlike isolated or discrete word recognition, users do not have to pause between words. See also discrete word recognition.
�contouring: The process of mapping scheduled work over time. For example, work on a task might be scheduled for 4 hours per day, every second day for 2 weeks.
�contract: (1) In WebSphere Commerce, an agreement representing the terms and conditions that apply to a transaction.; (2) The set of business policy assertions that have to be met by service provider at runtime based on the context and content.
�contracting conversion: A process that occurs when the length of a converted string is smaller than that of the source string. See also expanding conversion.
�contraction: A form of compounding that can occur either by cliticization or by phonological contraction. For example, 'ain't' is a contraction of 'is not'.
�control: (1) In WebSphere MQ and VisualAge RPG, the result of selecting a part from the parts palette and placing it on the design window. An example of a control is an entry field.; (2) See widget.
�control access: In the Distributed Computing Environment (DCE) Cell Directory Service (CDS), an access right that grants users the ability to change the access control on a name and to perform other management tasks, such as replicate a directory or move a clearinghouse. See also clearinghouse.
�control analysis: A type of analysis that displays variations in values of the business measures over a specific period of time. This type of analysis reduces data variation, and is often used for quality control. Allowable variation is three times the standard deviation of the data.
�control area (CA): (1) See control block.; (2) In the Virtual Storage Access Method (VSAM), a group of control intervals used as a unit for formatting a data set before adding records to it. In a key-sequenced data set (KSDS), each CA is pointed to by a sequence-set index record, and used by VSAM for distributing free space and for placing a sequence-set index record adjacent to its data. See also control block.
�control block: (1) A storage area used by a program to hold control information.; (2) In CICS, a storage area used to hold dynamic data during the execution of control programs and application programs. See also control area, control table.
�control blocks in common (CBIC): A facility with which a user can open a Virtual Storage Access Method (VSAM) data set so that the VSAM control blocks are placed in the common service area (CSA) of the MVS operating system. CBIC provides the capability for multiple memory accesses to a single, VSAM, control structure for the same VSAM data set.
�control boundary: A call stack entry used as the point to which control is transferred when an unmonitored error occurs or a high-level language termination verb is used. A control boundary can be either of the following: a) any Integrated Language Environment (ILE) call stack entry for which the immediately preceding call stack entry is in a different activation group, or b) any ILE call stack entry for which the immediately preceding call stack entry is an original program model (OPM) program.
�control break: In RPG, a change in the contents of a control field that indicates all records from a particular control group were read and a new control group is starting.
�Control Center: The graphical interface that lets a user administer DB2 databases and perform a variety of tasks including creating objects and monitoring performance. The Control Center shows database objects (such as databases and tables) and their relationships to each other.
�control character: A character whose occurrence in a particular context initiates, modifies, or stops a control function. See also carriage control character.
�control class: A class that is used to model behavior that is specific to one or more use cases.
�control command: In WebSphere MQ on UNIX systems and WebSphere MQ for Windows, a command that can be entered interactively from the operating system command line. Such a command requires only that the WebSphere MQ product be installed; it does not require a special utility or program to run it.
�control database: In Tivoli Enterprise Data Warehouse, the component that contains the metadata that describes the data in the warehouse, including the source of the data, how the data was transformed before being placed in the warehouse, when the data was collected, and the formats used to publish the data (for example, the star schemas used to create Tivoli Enterprise Data Warehouse data marts).
�control data set (CDS): (1) 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.; (2) A data set containing configurational, operational, and communication information. The z/OS storage management subsystem (SMS), DFSMSrmm, and DFSMShsm use control data sets. See also active control data set, backup control data set, communications data set, source control data set, migration control data set, offline control data set.
�control data set ID: In DFSMSrmm, a 1 - 8 character identifier for the DFSMSrmm control data set (CDS) used to ensure that, in a multi-system, multi-complex environment, the correct management functions are performed.
�control data structures: Data structures needed to manage file data and metadata cached in memory. Control data structures include hash tables and link pointers for finding cached data; lock states and tokens to implement distributed locking; and various flags and sequence numbers to monitor updates to the cached data.
�control field: (1) In RPG, one or more fields that are compared from record to record to determine when the information in the fields changes. When the information changes, the control level indicator (L1 through L9) assigned to a control field is set on.; (2) In AFP Utilities, an input field on the screen view that is used to move the image area up, down, left, or right.; (3) In Application Development ToolSet, one or more specified fields that are compared to determine the record sequence in the output file.; (4) In data communications, a field within a frame that contains the commands, responses, sequence numbers, and poll or final bit for data link control.; (5) In MERVA Link, a field that is part of a MERVA message on the queue data set and of the message in the TOF. A control field is written to the TOF at nesting identifier 0. Messages in SWIFT format do not contain a control field.
�control file: In DFSMShsm aggregate backup and recovery processing, one of three aggregate files generated by the aggregate backup process. It contains the catalog, allocation, volume, and related information necessary to perform aggregate recovery.
�control flow: (1) 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.; (2) The sequence that dictates the order in which steps of a business process are executed. The sequence can include branching based on decisions, iterating over a set of steps until a certain condition is reached, and so on. In a collaboration, control flow refers to the path that a scenario takes, which depends on the order of action nodes in an activity diagram. When an action node has multiple transition links, the path reflects the state of those links. This path is illustrated in a top-to-bottom direction. See also transition link.; (3) In DB2 data warehousing, a graphical model that sequences data flows and mining flows, integrates external commands, programs, and stored procedures, and provides conditional processing logic for a data warehouse application.
�control function: In TELNET, the standard representation for interconnection functions. The i5/OS implementation of these functions includes IP, AO, AYT, and SYNCH.
�control group: In Backup, Recovery, and Media Services, a group of libraries, special values, special operations, and lists that share common characteristics and are processed together due to their similar process cycles. The control groups used are backup control groups and archive control groups.
�control initiate (CINIT): A network services request sent from a system services control point (SSCP) to a logical unit (LU) asking that LU to establish a session with another LU and to act as the primary end of the session.
�control interval (CI): (1) A fixed-length area of direct access storage in which VSAM stores records and creates distributed free space. The control interval is the unit of information that VSAM transmits to or from direct access storage. A control interval always includes an integral number of physical records.; (2) In a key-sequenced data set or file, the set of records that an entry in the sequence-set index record points to.
�control interval definition field (CIDF): In VSAM, a field located in the 4 bytes at the end of each control interval; it describes the free space, if any, in the control interval. See also record definition field.
�control interval update sequence number (CUSN): An indicator used in a data-sharing environment to determine which sharing partner last read a CI. IMS compares the value of the CUSN for each CI to determine whether a CI should be updated during area restart or recovery.
�control language (CL): The set of all commands with which a user requests system functions.
�control language module (CL module): A module object (*MODULE) that results from compiling a CL source program using the Integrated Language Environment (ILE) CL compiler.
�control language procedure (CL procedure): The single Integrated Language Environment (ILE) procedure that is contained within a CL module. A CL procedure can be called by other ILE procedures when the CL module is bound with other ILE modules to create a program object (*PGM) or service program object (*SRVPGM).
�control language program (CL program): A program that is created from source statements consisting entirely of control language commands.
�control language source program: A set of control language (CL) source statements that can be compiled into either an original program model (OPM) program or an Integrated Language Environment (ILE) module.
�control language variable (CL variable): A program variable that is declared in a control language program and is available only to the CL program.
�controlled load service: In QoS, a level of service that supports the class of applications that are highly sensitive to overloaded networks. This service emulates a lightly loaded network in congested environments. For example, audio and videoconferencing would work well using controlled load service.
�controlled program: A RACF function with which an installation can control who can run RACF-controlled programs. See also dirty address space.
�controlled repetitive loop: In REXX, a repetitive DO loop in which the repetitive phrase specifies a control variable. The variable is given an initial value before the first run of the instruction list and is then stepped (by adding the result of an optional expression) before the second and subsequent times that the instruction list is run.
�controlled shutdown: See quiesced shutdown.
�controller: (1) A device that coordinates and controls the operation of one or more input/output devices (such as workstations) and synchronizes the operation of such devices with the operation of the system as a whole.; (2) Software that administrators use to perform remote control, file transfer, or chat functions.; (3) The functional component responsible for resource management (load balancing and admission control). The controller communicates with one or more data pumps to initiate and terminate connections to clients.
�controller card: A generic term for any of the I/O controller logic cards, such as storage device controller, work station controller, or communications controller.
�controller command: A command that interacts with a Web controller directly. On completion, a controller command returns the name of a view task to be executed. The Web controller determines the correct implementation class of the view command and then invokes it. See also task command.
�controller configuration: The process of creating configuration descriptions for the local (device configuration) and remote (communications configuration) controllers that make up a data processing system.
�controller description (CTLD): An object that contains a description of the characteristics of a controller that is either directly attached to the system or attached to a communications line. The system-recognized identifier for the object type is *CTLD.
�controller proxy: The remote control proxy that connects to the target as if it was the controller.

�control-level indicator: In RPG, an indicator (L1 through L9) used to specify certain fields as control fields and to control the operations that are performed at total and detail time in the RPG program cycle.
�controlling process: A session leader that has control of a terminal.
�controlling subsystem: The interactive subsystem that is automatically started first when the system is started and through which the system operator controls the system.
�controlling terminal: The active workstation from which the process group for that process was started. Each session may have at most one controlling terminal associated with it, and a controlling terminal is associated with exactly one session.
�control link: An object in a process that links nodes and determines the order in which they run.
�control logical unit (CLU): A logical unit that resides in a Transaction Processing Facility (TPF) type 2.1 node and that is used to pass private protocol request units between this TPF type 2.1 node and the logon manager (a VTAM application program). The communication flow between the control logical unit and the logon manager enables a logical unit controlled by VTAM to establish a session with TPF.
�control menu: See system menu.
�control message: (1) In Internet communications, a message that governs the aspects of a tunnel and sessions within a tunnel.; (2) An incoming message received from a clearing channel or the S.W.I.F.T. network that indicates the status of the payment.; (3) In Q replication, a message from a Q Apply program or a user application that asks a Q Capture program to activate or deactivate a Q subscription or an XML publication, invalidate a send queue, or confirm that a target table is loaded.
�control message interface (CMI): A set of control signals that are used to pass hardware-level messages between ports.
�control number: A number that is used to identify an interchange, group, or EDI document.
�control operator: (1) A token that performs a control function such as the symbols ().; (2) For logical unit (LU) 6.2, a service transaction program that describes and controls the availability of certain resources. For example, it describes network resources accessed by the local LU, and it controls session limits between the LU and its partners.
�control panel: A panel that contains lights and switches that are used to observe status and to operate or service the system.
�control point: In APPN, a component of a node that manages resources of that node and optionally provides services to other nodes in the network. Examples are a system services control point (SSCP) in a type 5 node, a physical unit control point (PUCP) in a type 4 node, a network node control point (NNCP) in a type 2.1 (T2.1) network node, and an end node control point (ENCP) in a T2.1 end node. See also physical unit.
�control point management services (CPMS): A component of a control point, consisting of management services function sets, that provides facilities to assist in performing problem management, performance and accounting management, change management, and configuration management.
�control point management services unit (CP-MSU): The message unit that contains management services data and flows between management services function sets. This message unit is in general data stream (GDS) format. See also network management vector transport.
�control point name: A network-qualified name of a control point that consists of a qualifier that identifies the network to which the control point node belongs.
�control point server (CP-SVR): The pair of conversations that are used to transmit encapsulated SNA.
�CONTROL privilege: The authority to completely control an object, which includes the authority to access, drop, or alter an object and the authority to extend privileges on the object to other users or to revoke their privileges on the object.
�control program (CP): A routine, usually part of an operating system, that aids in controlling the operations and managing the resources of a computer system.
�control region: (1) A virtual storage area that provides the control, scheduling, and work management mechanisms necessary to coordinate shared resources.; (2) The MVS main storage region that contains the IMS control program.
�control region adjunct: A servant that interfaces with service integration busses to provide messaging services.
�control section (CSECT): The part of a program specified by the programmer to be a relocatable unit, all elements of which are to be loaded into adjoining main storage locations.
�control server: (1) In SQL replication, a database server that contains replication control tables for the Capture program, Apply program, or Replication Alert Monitor. See also Apply control server, Apply server, Monitor control server, Q Capture server.; (2) The system where the control database component of Tivoli Enterprise Data Warehouse is installed.; (3) In database replication, the database location of the applicable subscription definitions and Apply program control tables.
�control specification: In RPG, a specification that provides information about program generation.
�control statement: (1) In programming languages, a statement that is used to interrupt the continuous sequential processing of programming statements. Conditional statements such as IF, PAUSE, and STOP are examples of control statements.; (2) In RPG, an entry on a control specification.; (3) A statement placed into an input stream to identify special processing options for jobs
�control station: The controlling or primary computer on a multipoint line. The control station controls the sending and receiving of data.
�control string: One of several compiled objects, which consist primarily of map control strings and document definition control strings.
�control structure: The beginning and ending segments (header and trailer) of EDI-enveloped documents.
�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.
�control unit (CU): A device that coordinates and controls the operation of one or more input/output devices, and synchronizes the operation of such devices with the operation of the system as a whole.
�control unit address: The high order bits of the storage control address, which are used to identify the storage control to the host system.
�control-unit image: In mainframe computing, a logical subsystem that is accessed through an ESCON or FICON I/O interface. One or more control-unit images exist in each control unit. Each image appears as an independent control unit, but all control-unit images share a common set of hardware facilities.
�control-unit initiated reconfiguration (CUIR): (1) A software mechanism that the ESS uses to request that an operating system of a zSeries or S/390 host verify that one or more subsystem resources can be taken offline for service. The ESS can use this process to automatically vary channel paths offline and online to facilitate bay service or concurrent code installation. Depending on the operating system, support for this process might be model-dependent, might depend on the IBM TotalStorage Enterprise Storage Server Subsystem Device Driver, or might not exist.; (2) An automation of the process used by service representatives to vary off and vary on subsystem resources for maintenance.
�control unit terminal (CUT): An IBM protocol used for communications an interface unit. In this protocol, a program in the workstation emulates a terminal for a user at a virtual terminal, and the interface unit is responsible for enforcing the protocol.
�control vector: One of a general class of RU substructures that has variable length, is carried within some enclosing structure, and has a one-byte key used as an identifier.
�convenience input: The process of adding a small number of cartridges to an Automated Tape Library Dataserver (ATLDS) without interrupting automated operations. The cartridges are added by inserting them directly into cells in a convenience input station.
�convenience input/output station: A transfer station with combined tape-cartridge input and output functions in the IBM TotalStorage Enterprise Automated Tape Library 3494 only.
�convenience input station: A transfer station, accessible from outside the enclosure, that is used by the operator to add tape cartridges to an Automated Tape Library Dataserver (ATLDS).
�convenience output: The process of removing a small number of cartridges from the Automated Tape Library Dataserver (ATLDS) without interrupting automated operation.
�convenience output station: A transfer station, accessible from outside the enclosure area, which is used by the operator to remove tape cartridges from the Automated Tape Library Dataserver (ATLDS).
�convenience station: The part of the tape library that is used to load and unload small numbers of cartridges into the tape library.
�conventional memory: Personal computer memory that is addressed by DOS from 0 KB to 640 KB. See also expanded memory.
�converged service processor: A common card in both System i and RS/6000 systems. The primary function of a converged service processor is to start the system and diagnose hardware failures.
�convergence: In the Distributed Computing Environment (DCE), the degree to which the Cell Directory Service (CDS) attempts to keep all replicas of a directory consistent.
�conversation: (1) A connection between two programs over a session that allows them to communicate with each other while processing a transaction. See also SQL processing conversation, transaction, session.; (2) See speech recognition session.; (3) 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.; (4) The communication between a CICS Transaction Gateway and a CICS server.; (5) A dialog between a terminal and a message processing program using IMS conversational processing facilities. Also, a dialog between an LU 6.2 program and an IMS application program. A conversation between a terminal and a message processing program is significant status that is kept in RM, if RM is used. Status for a held conversation is not kept in RM. The IMS conversation is represented by a CCB. See also conversational processing.
�conversational: (1) Pertaining to a program or a system that conducts a dialog with a terminal user, alternately receiving and transmitting data. See also transaction-oriented programming.; (2) Pertaining to an SNA conversation or a dialog between two programs.; (3) Pertaining to a communication model where two distributed applications exchange information in a dialog.
�Conversational Monitor System (CMS): A virtual-machine operating system that provides general interactive time sharing, problem solving, and program development capabilities.
�conversational processing: (1) An optional facility that allows an application program to accumulate information acquired through multiple interchanges with a terminal, even though the program terminates between interchanges. Conversation information for the active and held conversations is significant status that can optionally be kept in the RM if a status recovery mode of GLOBAL is selected. See also conversation.; (2) An optional IMS facility that allows a user's application program to accumulate information acquired through multiple interchanges with a terminal, even though the program terminates between interchanges. In the context of IMS Connector for Java, the interchanges are between a Java client program and a user's application program. See also IMS conversation.
�conversational transaction: In APPC, two or more programs communicating using the services of logical units (LUs).
�conversation characteristic: In distributed transaction processing, one of the attributes of a conversation that determine the functions and capabilities of programs within the conversation.
�conversation control block (CCB): An IMS control block that represents a conversation between a terminal and an application program.
�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.
�conversation identifier: A value used to identify the conversation.
�conversation key: See session key.
�conversation-level security: See end-user verification.
�conversation security: In APPC, a process that allows validation of a user identifier or group identifier and password before establishing a connection.
�conversation state: The condition of a conversation, such as send or receive state. The conversation state reflects the actions that have been taken pertinent to that conversation and determines what the next set of actions may be.
�conversion: (1) The process of changing from one method of data processing to another or from one data processing system to another. Changing a code point that is assigned to a character in one code page to its corresponding code point in another code page is an example of conversion.; (2) In programming languages, the transformation between values that represent the same data item but belong to different data types. Information may be lost because of conversion since accuracy of data representation varies among different data types.; (3) The process of changing from one form of representation to another. Changing a code point that is assigned to a character in one code page to its corresponding code point in another code page is an example of conversion.; (4) In DFSMSrmm, the process of moving removable-media-library inventory from another media management system to DFSMSrmm. DFSMSrmm manages the inventory and policies after conversion.
�conversion function: A C++ member function that specifies a conversion from its class type to another type.
�conversion table: (1) An object that contains a set of hexadecimal characters used to convert one or more characters of data. The table can be used for the conversion of data being moved between the system and a device. For example, data stored in one coded character set may need to be displayed or entered on display devices that support a different coded character set. The table can also be used to specify an alternative collating sequence or field conversion functions. The system-recognized identifier for the object type is *TBL.; (2) A table that contains a set of characters that can be replaced with alternative characters.
�conversion template table: A CICS table containing entries that identify how data is to be converted when transported to or from a remote system.
�converted journal entry: The version of a journal entry that can be displayed, printed, or written to a database output file.
�converter: In Enterprise JavaBeans (EJB) programming, a class that translates a database representation to an object type and back.
�converter/interpreter processing: The system function that converts and interprets job control language (JCL) for z/OS.
�convert in place: See in-place conversion.
�cookie: Information that a server stores on a client machine and accesses during subsequent sessions. Cookies allow servers to retrieve specific information about clients.
�cooperative application: In the Systems Application Architecture (SAA) environment, a type of distributed application in which the user interface portion of the application runs on a programmable work station while some or all of the remaining code runs on one or more linked systems.
�CoOperative Development Environment/400: A feature of the WebSphere Development Studio Client licensed program that provides System i application development and maintenance tools for editing, compiling, and debugging third-generation programming languages.
�cooperative portlets: Two or more portlets on the same Web page that interact by sharing information. See also Click-to-Action, wire, property broker.
�cooperative processing: Distributed processing in which processors, typically a programmable workstation and a host computer, accomplish the work of an application by means of coordinated or synchronized use of processing functions and system resources.
�coordinate: (1) To bring into a common action, movement, or condition.; (2) A member of an ordered set of N numbers that identifies a position in N-dimensional space. For example, in a two-dimensional map of the Earth, a position can be referenced by two coordinates. The first coordinate identifies the latitude value of the position, and the second coordinate identifies the longitude value of the position.
�coordinated online change: See global online change.
�Coordinated Universal Time (UTC): The international standard of time that is kept by atomic clocks around the world.
�coordinate system: A reference framework that is used to define the positions of points in space in two or three dimensions.
�coordinating address space (CAS): (1) 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.; (2)
�coordinating agent: The agent that is directly responsible for processing requests from and responding to an application. If the connection concentrator is not used, the agent remains associated with the application during the life of the application and initiates subagents that work for the application. See also subagent.
�coordinator: (1) The system component that coordinates the commit or rollback of a unit of work that includes work that is done on one or more other systems.; (2) 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. See also master, subordinate.
�coordinator agent: The agent responsible for accepting and processing application requests on a database connection or an instance attachment.
�coordinator controller (CCTL): A z/OS subsystem that consists of the database resource adapter (DRA) and a transaction management subsystem, such as CICS.
�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.
�coordinator node: See coordinator partition.
�coordinator partition: The database partition server to which the application originally connected and on which the coordinating agent resides.
�coordinator subsection: The subsection of an application that starts other subsections (if any) and returns results to the application.
�copied: In a FlashCopy relationship, the indication that the copy process is complete and that the target disk has no further dependence on the source disk.
�copper chip technology: A technology in which chips exploit the capabilities of copper circuitry, which passes electrical currents more easily than aluminum. Aluminum has been the traditional material used in the wires that connect the "switches," or transistors, in silicon chips. Copper chip technology produces smaller, faster chips that have enormous capacity for holding and transmitting information.
�copy: To read data from a source, leaving the source data unchanged, and to write the same data elsewhere.
�copy constructor: A C++ constructor used to make a copy of a class object from another class object of the same class type.
�copy group: (1) One or more copies of a sheet of paper or form. Each copy can have modifications, such as text suppression, page position, forms flash, overlays, paper-source, and duplex printing.; (2) A policy object whose attributes control how backup copies or archive copies are generated, where they are located, and when they expire. A copy group belongs to a management class, which specifies how the server manages the backup copy or archive group.; (3) An internal object in a form definition or a print data set that controls such items as modifications to a form, page placement, and overlays.
�copy helper: An access bean that contains a local copy of attributes from a remote entity bean. Unlike bean wrappers, copy helpers are optimized for use with a single instance of an entity bean.
�copying: A status condition that describes the state of a pair of virtual disks (VDisks) that have a copy relationship. The copy process has been started but the two virtual disks are not yet synchronized.
�copy modification: The process of adding, deleting, or replacing data on selected copies of either a presentation space or certain pages of a print job.
�copy pool: A collection of names of storage groups that are processed collectively for fast replication operations.
�copy proposed to plan: In Rational Portfolio Manager, the act of moving a project from a planning stage into a scheduled, executable state.
�copy separation: The method or printer mechanism for distinguishing consecutive copies of a single data set or print file. In the continuous-forms stacker, the method consists of the alternation between one, two, or three vertical bars placed on the left carrier strip between forms. In the burster-trimmer-stacker or for cut-sheet paper, the mechanism consists of offset stacking.
�Copy Services CLI: See Copy Services command-line interface.
�Copy Services client: Software that runs on each ESS cluster (or, optionally, in an external cluster) in the Copy Services server group and that performs the following functions: communicates configuration, status, and connectivity information to the Copy Services server; and performs data-copy functions on behalf of the Copy Services server. See also backup Copy Services server, primary Copy Services server.
�Copy Services command-line interface (Copy Services CLI): Software that invokes ESS Copy Services functions from the command-line interface (CLI) of hosts that are attached to the ESS. See also command-line interface.
�Copy Services domain: See Copy Services server group.
�Copy Services server: An ESS cluster (or, optionally, in an external cluster) designated by the copy services administrator to perform the ESS Copy Services functions. See also backup Copy Services server, primary Copy Services server.
�Copy Services server group: A collection of user-designated ESS clusters participating in Copy Services functions managed by a designated, active, Copy Services server. See also backup Copy Services server, primary Copy Services server.
�copy set: The set of source volumes or target volumes involved in a FlashCopy operation.
�copy target: A named set of SMS storage groups that are to be used as containers for copy pool volume copies. A copy target is an SMS construct that lets you define which storage groups are to be used as containers for volumes that are copied by using FlashCopy functions.
�copy version: A point-in-time FlashCopy copy that is managed by HSM. Each copy pool has a version parameter that specifies the number of copy versions to be maintained on disk.
�CORBA: See Common Object Request Broker Architecture.
�CORBA Object Services Naming Directory (COS Naming Directory): A server that supports the Java Naming and Directory Interface (JNDI).
�CorbaServer: The execution environment defined by a CORBASERVER definition. A CICS EJB server can contain multiple CorbaServers.
�core group: A group of processes that is directly accessible to each other and is connected using a local area network (LAN).
�core group access point: A definition of a set of servers that provides access to the core group.
�core group bridge: The means by which core groups communicate.
�core group member: A server included in the cluster of a core group.
�core interchange font: A uniformly spaced typographic font with specialized characters for different languages.
�corequisite: A component or service that is needed in parallel with a component. In other words, the components, resources, or services listed as corequisites of a component must be installed and configured in conjunction with the component. See also requisite.
�corequisite dependency: A condition in which a configuration change is performed only if other required changes are also performed as part of the specified change sequence.
�corequisite fix: A temporary solution to or a bypass of a problem that is necessary to provide a complete solution to correct a problem. The system requires that you apply the corequisite fix with the PTF that needs it. See also distribution requisite fix, prerequisite fix.
�Corrective Service Diskette: A diskette provided by IBM to registered service coordinators for resolving user-identified problems with previously installed software. This diskette includes program updates designed to resolve problems.
�correlated column: In SQL, a relationship between the value of one column and the value of another column.
�correlated reference: A reference to a column of a table or view that is outside a subquery. See also correlated subquery.
�correlated subquery: A subquery that contains a correlated reference. See also correlated reference.
�correlation: (1) The process of analyzing event data to identify patterns, common causes, and root causes. Correlation analyzes the incoming events for known states, using rules and relationships.; (2) In transaction monitoring, the process of tracking hierarchical relationships among transactions and associating transactions with their nested subtransactions.; (3) A record used with business processes and state machines to allow two partners to initialize a transaction, temporarily suspend an activity, and then recognize each other again when that activity resumes.; (4) A mechanism that bridges a point in a process flow between two or more process instances.; (5) The relationship, captured in a correlation expression, that describes how an incoming event is matched with one or more monitoring context instances to which it will be delivered.
�correlation ID: See correlation identifier.
�correlation identifier (correlation ID): (1) An application-defined identifier assigned to distributions for the user's information.; (2) A field in a message that provides a means of identifying related messages. Correlation identifiers are used, for example, to match request messages with their corresponding reply message.; (3) In DB2 for z/OS, an identifier that is associated with a specific thread. In TSO, the correlation ID is either an authorization identifier or the job name.
�correlation name: An identifier specified and used within a single SQL statement as the exposed name for objects such as a table, view, table function reference, nested table expression, or data change table reference. Correlation names are useful in an SQL statement to allow two distinct references to the same base table and to allow an alternative name to be used to represent an object.
�correlation property: Data in an event that the runtime server uses to determine which instance of a task, process, or business state machine should receive the input at run time.
�correlation rule: See compound rule.
�correlation table: In OSI X.400, a table that records details of distributions sent and received across a gateway (such as VM/MVS bridge or X.400). A correlation table is used by a gateway to forward acknowledgments, as appropriate, after they are received.
�correlator: Information that identifies a relation among things. An example is a variable field of a response that identifies the corresponding request.
�correspondent: An institution to which your institution sends and from which it receives messages.
�correspondent identifier: The 11-character identifier of the receiver of a telex message. Used as a key to retrieve information from the Telex correspondents file.
�COS: (1) See common operations services.; (2) See class of service.; (3) See configuration object set.
�COS Naming Directory: See CORBA Object Services Naming Directory.
�cost: (1) The estimated total resource usage that is necessary to run the access plan for a statement (or the elements of a statement). Cost is derived from a combination of processor cost (in number of instructions) and I/O cost (in numbers of seeks and page transfers).; (2) A number that is used as a weighting mechanism to differentiate one resource from another where a smaller value is always preferred.
�cost category: A category into which DB2 for z/OS places cost estimates for SQL statements at the time the statement is bound. The cost category is externalized in the COST_CATEGORY column of the DSN_STATEMNT_TABLE when a statement is explained.
�cost performance index (CPI): The ratio of cost efficiency or value earned per unit actual cost. A number less than one indicates that the project is spending more money than budgeted.
�cost variance (CV): The difference between the estimated cost of an activity and the actual cost of that activity.
�cost variance at completion (CVAC): See variance at completion.
�counter: (1) A data item used for storing numbers or number representations in a manner that permits these numbers to be increased or decreased by the value of another number or to be set to an arbitrary value.; (2) A register or storage location used to accumulate the number of occurrences of an event.; (3) A representation of information that is cumulative up until the sample is taken. The counter counts values that increase, such as the number of deadlocks. Counters are reset when an instance or a database is stopped and restarted. See also gauge.; (4) A binary string that is used by some block cipher modes in an exclusive-OR (XOR) operation. It is incremented and then applied in the encryption or decryption of each block of data. For a given key, a counter should never be repeated.; (5) A specialized metric used to keep track of the number of occurrences of a specific situation or event. For example, you can use a counter to track the number of times that a task is started within a process, where that task is contained in a loop.
�counterpart SAN: A non-redundant portion of a redundant storage area network (SAN). A counterpart SAN provides all the connectivity of the redundant SAN but without the redundancy. Each counterpart SAN provides an alternate path for each SAN-attached device. See also redundant SAN.
�counter value: A displayed monetary amount converted from the shopping currency into a different currency.
�count field: The first field of a count-key-data (CKD) record. This field contains eight bytes: the first four bytes identify the track address, which includes the cylinder and head that are associated with the track; the fifth byte identifies the record on the track; the sixth byte identifies the length of the record's key field; the last two bytes identify the length of the record's data field.
�count key data (CKD): (1) In mainframe computing, a data-record format employing self-defining record formats in which each record is represented by up to three fields: a count field identifying the record and specifying its format, an optional key field that can be used to identify the data area contents, and an optional data field that typically contains the user data. See also data record.; (2) An ESA/390 architecture for a direct access storage device (DASD) logical device that specifies the format of and access mechanisms for the logical data units on the device. The logical data unit is a track that can contain one or more records, each consisting of a count field, an optional key field, and an optional data field. See also custom volume.
�count-key-data device (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).
�count-key-data storage: See S/390 storage.
�country code: In X.25 communications, the 3-digit number that precedes the national terminal number in the network user address for public networks.
�country extended code page (CECP): An EBCDIC code page that is extended by the addition of code points for characters needed in the language used by a specific country. Using country extended code page (CECP) support, a German panel, for example, can be displayed on a French CECP terminal with all common characters displayed correctly
�country ID: See country identifier.
�country identifier (country ID): The 2-character representation for the country associated with an object. For example, documents and user profiles can have a country associated with them.
�country/region code: See territory code.
�couple data set (CDS): A data set that contains information related to a sysplex, its systems, cross-system coupling facility (XCF) groups, and their members. See also sysplex couple data set.
�coupled extended remote copy (CXRC): In z/OS or S/390 environments, a technique that supports synchronous copy operations in large environments that have an expanded number of primary-storage controls and direct access storage device (DASD) volumes; this number is in excess of those supported by a single data-mover configuration. Installations can have configurations consisting of thousands of volumes in multiple extended remote copy (XRC) sessions; coordination among the sessions ensures that all volumes will be recovered to a consistent time. CXRC greatly expands upon the ability of XRC to provide remote disaster-recovery protection across a sysplex.
�coupler: A device that connects a modem to a telephone network.
�coupling: The dependency that components have on one another. See also cohesion.
�coupling facility: A special logical partition that provides high-speed caching, list processing, and locking functions in a sysplex.
�coupling facility cache structure (CF cache structure): The hardware that provides a data cache.
�coupling facility channel: A high-bandwidth fiber-optic channel that provides the high-speed connectivity required for data sharing between a coupling facility and the central processor complexes (CPCs) directly attached to it.
�coupling facility lock structure (CF lock structure): The hardware that supports sysplex-wide locking.
�Coupling Facility Resource Management policy (CFRM policy): The allocation rules for a coupling facility structure that are declared by a z/OS administrator.
�Coupling Facility Resource Manager (CFRM): A component of z/OS that provides the services to manage coupling facility resources in a Parallel Sysplex. This management includes the enforcement of CFRM policies to ensure that the coupling facility and structure requirements are satisfied.
�coupling service: A function of the cross-system coupling facility (XCF) that transfers data and status information among the members of a group that reside in one or more of the MVS systems in a sysplex.
�courier server: In the DCE Distributed Time Service, a local server that requests a time value from a randomly selected global server. The time value returned is used to synchronize a local access network (LAN) with all other parts of the network.
�course: (1) The body of content that is taught, including general information such as the course description for the course catalog, an outline of materials covered, a schedule of sessions, and, optionally, assessments such as tests or evaluations. More than one person can be listed as an instructor for each course.; (2) A set of learning activities designed to meet one or more specific objectives. A course is stored in the LMS as a master. from which multiple offerings can be created.
�course catalog: A list of courses available; also, the module where administrators manage course masters and offerings.
�course master: The structure and metadata information that is extracted from a course package and stored in the Lotus Learning Management System so that course offerings can be created from it.
�course offering: A specific instance of a course, based on a course master and offered at a particular date and time.
�course package: A compressed package interchange file (PIF) containing course structure and metadata, and possibly course content. This is the form in which courses are imported into the Lotus Learning Management System.
�course profile: The label assigned to a course, which can locate the course when used as a search criterion in the course catalog.
�course structure: The navigational map, typically presented as a tree, used to combine learning resources into a cohesive unit of instruction.
�covered database: A database or area in an RSR environment that is tracked by a tracking subsystem. Recovery information is not maintained by the tracking subsystem for databases or areas that are not covered.
�CP: (1) See control program.; (2) See central processor.
�CPB: See collection point block.
�CPC: (1) See central processor complex.; (2) See current processor capacity.; (3) See cluster processor complex.
�CP capabilities: The level of network services provided by the control point (CP) in an APPN end node or network node. CP capabilities information is exchanged during the activation of CP-CP sessions between two nodes. A node's CP capabilities are encoded in the CP capabilities (X'12C1') GDS variable.
�CP-CP session: In SNA, one of the parallel sessions between two control points, using LU 6.2 protocols and a mode name of CPSVCMG, on which network services requests and replies are exchanged. Each CP of a given pair has one contention-winner session and one contention-loser session with the other.
�CP-CP session-capable connection: A link over which a node permits CP-CP sessions to be established.
�CPE: See customer premises equipment.
�CPF: See command prefix.
�CPGID: See code page global identifier.
�cpi: See characters per inch.
�CPI: (1) See Common Programming Interface.; (2) See cost performance index.
�CPI-C: See Common Programming Interface for Communications.
�CPI-C driven application program: An application program that uses CPI for Communications calls to receive an incoming message and to send a reply.
�CPM: See continuously powered main storage.
�CPMS: See control point management services.
�CP-MSU: See control point management services unit.
�CPP: (1) See command processing program.; (2) See also spool.
�CPPL: See command processor parameter list.
�CPS: See compressed-pattern storage.
�CP-SVR: See control point server.
�CP-SVR pipe: A pair of LU 6.2 sessions, between the control points in dependent-LU-requester (DLUR) and dependent-LU-server (DLUS) nodes, that carry the flows of SSCP services, which are encapsulated in APPN formats.
�CPU: See central processing unit.
�CPW: See commercial processing workload.
�CQS: See Common Queue Server.
�CQS restart: The process by which CQS starts: either a cold start or a warm start. During a CQS warm start, the CQS environment is restored to its state when CQS terminated. During a CQS cold start, the CQS environment is not restored to its previous state; it is reinitialized.
�CR: (1) See carriage return.; (2) See change request.
�CRA: See catalog recovery area.
�cracker: Someone, usually with malicious intent, who tries to circumvent or subvert system protection mechanisms. See also hacker.
�cradle: The part of a telephone that holds the handset or receiver.
�crash recovery: The process of bringing a database back to a consistent and usable state after a failure. See also version recovery, roll-forward recovery.
�crawl: To search for information across various web pages across the Internet or an intranet.
�crawler: A software program that retrieves documents from data sources and gathers information that can be used to create search indexes.
�crawl space: A set of sources that match specified patterns, such as database names, file system paths, domain names, IP addresses, and Uniform Resource Locators (URLs), that a crawler reads from to retrieve items for indexing.
�CRC: (1) See command recognition character.; (2) See cyclic redundancy check.
�CRCR: See conditional restart control record.
�create access list: A list that restricts a form, so that only specified users can create documents using the form.
�create data: The data necessary to convert code to machine instructions.
�create date: (1) In DFSMSrmm, the date that a data set is written to tape.; (2) The date that a data set was read if it was created before DFSMSrmm was in use. The create date is updated each time a data set is replaced and not extended.; (3) The date that volumes and other resources are defined to DFSMSrmm or the date specified on the command as the create date.
�created global variable: A global variable whose definition exists in the system catalog. See also global variable.
�created temporary table: A persistent table that holds temporary data and is defined with the SQL statement CREATE GLOBAL TEMPORARY TABLE. Information about created temporary tables is stored in the DB2 catalog and can be shared across application processes See also temporary table, declared temporary table.
�create link pack area (CLPA): An option that is used during initial program load to initialize the link pack pageable area.
�create method: In enterprise beans, a method defined in the home interface and invoked by a client to create an enterprise bean. (Sun)
�creation date: The system date when an object is created.
�creation time: The total time that an asset owner takes to create an asset, measured in hours, days, months, or years.
�creation time stamp (CTS): In the Distributed Computing Environment (DCE), an attribute of all Cell Directory Service clearinghouses, directories, soft links, child pointers, and object entries that contains a unique value reflecting the date and time the name was created.
�credential: (1) In the Java Authentication and Authorization Service (JAAS) framework, a subject class that owns security-related attributes. These attributes can contain information used to authenticate the subject to new services.; (2) Detailed information, acquired during authentication, that describes the user, any group associations, and other security-related identity attributes. Credentials can be used to perform a multitude of services, such as authorization, auditing, and delegation. For example, the sign-on information (user ID and password) for a user are credentials that allow the user to access an account.
�credential mapper: The component of Web Express Logon that handles requests for host credentials, which have been previously authenticated by a network security layer. See also network security layer.
�credit: In fibre-channel technology, the number of receive buffers allocated to a transmitting node port (N_port), node loop port (NL_port), or fabric port (F_port). The credit is the maximum number of outstanding frames that can be transmitted by that N_port, NL_port, or F_port without causing a buffer overrun condition at the receiver.
�credit cap: A limit for credit payments. MERVA Liquidity Manager issues a warning when it is reached.
�credit payment: A payment that credits the bank's account. It can be received as an incoming message from another bank, as an in-house message, or as a credit confirmation.
�CRG: See cluster resource group.
�CRGM: See cluster resource group manager.
�critical design review (CDR): In the waterfall life cycle, the major review held when the detailed design is completed.
�critical path: (1) The processing path that takes the longest time to complete of all parallel paths in a process instance, where each path considered begins at a start node or an input to the process and ends at a stop node.; (2) The sequence of activities that determines the earliest date at which a project can be completed. The length of this path changes as activities or tasks are completed earlier or later than the original schedule.
�critical path method: A technique used to identify and predict project duration by analyzing which sequence of activities has the least amount of scheduling flexibility.
�critical ratio: The relationship of the time scheduled to complete a task to the time available to perform it. This ratio is used to measure how closely a task is adhering to its schedule.
�CRL: See certificate revocation list.
�cron table: A table that is used to schedule application programs and processes.
�crop: In image processing and in multimedia applications, to cut off or trim.
�cross-certificate: A certificate in the Personal Address Book or Domino Directory that indicates trust in an Internet certificate or trust in a certificate from a foreign Domino domain.
�cross-compiler: A compiler that produces executable files that run on a platform other than the one on which the compiler is installed.
�cross-cutting concern: A software concern (synchronization, logging, memory allocation, and so forth) that is external and orthogonal to the problem that a software component is designed to address. See also aspect.
�cross-domain: Pertaining to control or resources involving more than one domain.
�cross-domain analysis: A type of analysis that identifies the overlap of data values between two columns of data.
�cross-domain key: In Cryptographic Support, a type of key-encrypting key used to encrypt a data-encrypting key that is being sent across a data line or being stored in a file.
�cross-domain key table: In Cryptographic Support, a table in the system-supplied physical file QACRKTBL in library QUSRSYS used to store all key-encrypting keys other than the host master key and its variants. Each record of the file contains the name of the key, its use, and its value. The three types of uses are sending, receiving, and personal identification numbers (PINs).
�cross-domain link: (1) A subarea link connecting two subareas that are in different domains.; (2) A link physically connecting two domains.
�cross-domain network manager session (CDNM session): A session between two network managers in separate domains.
�cross-domain resource (CDRSC): A representation for a logical unit that is owned by another domain and is referenced by a symbolic name, which can be qualified by a network identifier.
�cross-domain resource manager (CDRM): In VTAM, the function in the system services control point (SSCP) that controls initiation and termination of cross-domain sessions.
�cross-functional: Features, changes, or other characteristics that affect more than one DFSMS element.
�cross-memory linkage: In a z/OS environment, a method for invoking a program in a different address space. The invocation is synchronous with respect to the caller.
�cross-memory mode: A synchronous method of communication between address spaces.
�cross memory resource-owning task (CMRO task): A job step in an address space that owns the cross-memory resources. The CMRO task is the top, or first, job step task in the address space.
�cross-network session: An LU-LU or SSCP-SSCP session whose path traverses more than one SNA network.
�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-project: Pertaining to project dependencies from one project to another.
�cross-project traceability: A feature that establishes traceability relationships between requirements that reside in different projects. See also external project, external traceability.
�cross-reference: A pointer to a preferred term (see reference) or to additional information (see also reference).
�cross-reference listing: The part of the compiler listing that tells where files, fields, and indicators are defined, referred to, and changed in a program.
�cross-sell: A product recommendation that is related or complementary to the currently displayed or selected product. See also up-sell, accessory.
�cross-server migration: The migration of Tivoli Intelligent Orchestrator or Tivoli Provisioning Manager where you install the new version of Tivoli Intelligent Orchestrator on a new server, and then migrate your data to the new server.
�cross-site mirroring (XSM): A function of i5/OS High Available Switchable Resources, Option 41, that provides geographic mirroring and the services to switch over or automatically cause a failover to a secondary copy, potentially at another location, in the event of an outage at the primary location.
�cross-system coupling facility (XCF): A component that provides functions to support cooperation between authorized programs running within a sysplex.
�cross-system extended services (XES): A set of services with which multiple instances of an application or subsystem, running on different systems in a sysplex environment, can implement high-performance, high-availability data sharing by using a coupling facility.
�cross-system restart: A process during which automatic restart management restarts elements on another eligible system in the sysplex when a system fails.
�cross-table analysis: A type of anaysis that combines foreign key analysis and cross-domain analysis.
�cross-volume consistency: A consistency group property that guarantees consistency between virtual disks (VDisks) when an application issues dependent write operations that span multiple VDisks.
�CRQ: See change request.
�CRQD: See change request description.
�CRS: See configuration report server.
�CRU: See customer-replaceable unit.
�cryptanalyst: In Cryptographic Support, a specialist in solving cryptographic problems.
�cryptographic: Pertaining to transformation of data to conceal meaning.
�cryptographic adapter: An expansion board that provides a comprehensive set of cryptographic functions for the network security processor and the workstation in the TSS family of products.
�cryptographic algorithm: A set of rules that specify the mathematical steps required to encrypt and decrypt data.
�cryptographic key: A parameter that determines cryptographic transformations between plaintext and ciphertext.
�Cryptographic Service Provider (CSP): A feature of the i5/OS operating system that provides APIs. The CCA Cryptographic Service Provider enables a user to run functions on the 4758 Coprocessor.
�Cryptographic Support: The IBM licensed program that provides support for the encryption and decryption of data, according to the Data Encryption Algorithm, and for the management of cryptographic keys and personal identification numbers (PINs).
�cryptographic token: A logical view of a hardware device that performs cryptographic functions and stores cryptographic keys, certificates, and user data.
�cryptography: (1) The transformation of data to conceal its information content and to prevent its unauthorized use or undetected modification.; (2) Protecting information by transforming it (encrypting it) into an unreadable format, called ciphertext. Only those who possess a secret key can decipher (or decrypt) the message into plaintext.
�CS: See cursor stability.
�CSA: (1) See common service area.; (2) See common storage area.; (3) See common system area.
�CSB: See connection status block.
�CSD: See CICS system definition data set.
�CSECT: See control section.
�C shell: A command line processor for UNIX that provides interactive features such as job control and command history.
�CSI: See consolidated software inventory.
�CSL: See Common Service Layer.
�CSL client: See Common Service Layer client.
�CSL component: An IMSplex member type that is part of the CSL: OM, RM, or SCI.
�CSM: (1) See communications storage manager.; (2) See client state manager.
�CSMA/CD: See Carrier Sense Multiple Access with Collision Detection.
�CSM database: A repository of cluster, node, and node group information that is created and used by Cluster Systems Management (CSM).
�CSM-only installation: The process of installing only Cluster Systems Management (CSM) on the nodes, as opposed to a full installation, which involves installing both CSM and the operating system on the nodes.
�CSNET: See Computer Science Network.
�CSP: See Cryptographic Service Provider.
�CSR: See customer service representative.
�CSS: (1) See cascading style sheet.; (2) See channel subsystem.
�CSS-P: See cascading style sheet positioning.
�CSU: See channel service unit.
�CSV file: A comma-separated value text file, commonly used to exchange files between database systems that use different formats. Sometimes called comma-delimited files, CSV files can be imported into RequisitePro.
�CSW: See channel status word.
�CT: (1) See configuration object type.; (2) See cursor table.
�CTC: See channel-to-channel.
�CTC adapter: See channel-to-channel adapter.
�CTI: See computer-telephony integration.
�CTIA: See Cellular Telecommunications Industry Association.
�CTLD: See controller description.
�CTS: (1) See creation time stamp.; (2) See common transport semantics.
�CU: See control unit.
�CUA: See Common User Access.
�cube: A multidimensional representation of data needed for online analytical processing and multidimensional reporting.
�cube server: A high-performance, scalable cubing engine that is designed to support queries from many users against many different OLAP cubes.
�CUD: See call user data.
�CUG: See closed user group.
�CUIR: See control-unit initiated reconfiguration.
�cumulative backup: The process of copying only data sets that have changed since the last backup of any type. See also full backup, incremental backup.
�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.
�cumulative PTF package: Media containing the program temporary fixes (PTFs) for i5/OS that have been accumulated from the start of the current release. PTFs requiring special handling are not included in a cumulative PTF package.
�cumulative service tape: A tape that is sent with a new function order and that contains all current PTFs for that function.
�cumulative time: The time that a method spends on the execution stack, including both time spent in the method itself and in other methods that it calls.
�currency advice: An advice that is not assigned to a particular channel.
�currency code file: A file containing the currency codes, together with the name, fraction length, country code, and country names.
�currency credit advice: A credit advice that is not assigned to a particular channel.
�currency debit advice: A debit advice that is not assigned to a particular channel.
�currency sign: In COBOL, the character $.
�currency symbol: (1) A character such as the dollar sign ($) used to identify monetary values.; (2) In COBOL, the character defined by the CURRENCY SIGN clause in the SPECIAL-NAMES paragraph. If no CURRENCY SIGN clause is present in a COBOL source program, the currency symbol is identical to the currency sign.
�current backup version: In DFSMShsm, a backup copy of the data set that was created on a date after the data set was last updated.
�current charge: In an advanced order, the set of charges a customer incurs for order items that can be shipped at once. See also total charge.
�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 customization definition: A customization definition that describes an instance for which the corresponding resources have already been deployed and are running.
�current data: Data within a host structure that is current with (identical to) the data within the base table.
�current directory: See working directory.
�current file: The file being edited. If multiple windows are in use, the current file is the file containing the cursor.
�current files library: The files library to search for database files to be used by the System/36 environment for the current job.
�current form: In query management, the form being applied against the data to produce the report being displayed or printed.
�current interrupted job: When a job is interrupted by pressing the Attn key, another job can be started from a command line. This job can also be interrupted by pressing the Attn key again. The current interrupted job is the most recently interrupted. The job name for the current interrupted job is displayed at the top of the Inquiry Options menu.
�current library: The library that is specified to be the first user library searched for objects requested by a user. The name for the current library can be specified on the Sign-On display or in a user profile. When you specify an object name (such as the name of a file or program) on a command, but do not specify a library name, the system searches the libraries in the system part of the library list, then searches the current library before searching the user part of the library list. The current library is also the library that the system uses when you create a new object, if you do not specify a library name.
�current line: The line on which the cursor is located.
�current line pointer (CLP): In systems with time sharing, a pointer that indicates the display line on which operations are being performed.
�current list: A list name, specified with a resource definition online command, that is "remembered" until another list name is used.
�current mode: In the GDDM function, the characteristics of the controlling session. For example, when a color is defined, everything the program draws uses that color until the color is changed.
�current path: An ordered list of schema names that is used in the resolution of unqualified references to functions and data types. In dynamic SQL, the current function path is found in the CURRENT PATH special register. In static SQL, it is defined in the FUNCPATH option for PREP and BIND commands.
�current position: (1) In computer graphics, the position, in user coordinates, that becomes the starting point for the next graphics routine, if that routine does not explicitly specify a starting point.; (2) In an IMS database, the place immediately preceding the segment occurrence that IMS retrieves if you immediately issue an unqualified retrieval call.
�current print position: The picture element that defines the character reference point or the upper-left corner of an image.
�current processor capacity (CPC): The amount of processor capacity (in units of 1/100 of a physical processor) that is assigned to a logical partition.
�current record: (1) In COBOL, the record that is available in the record area associated with the file.; (2) The record pointed to by the current line pointer.
�current record pointer: In COBOL, a method of identifying a record that is used in the sequential processing of the next record.
�current release: The latest available release of the system that replaced the Licensed Internal Code, operating system, or both.
�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.
�current SQL ID: In DB2 for z/OS, an identifier that, at a single point in time, holds the privileges that are exercised when certain dynamic SQL statements run. The current SQL ID can be a primary authorization ID or a secondary authorization ID.
�current state: In DB2 for i5/OS, the state of a connection when it is the one used for SQL statements that are executed. See also dormant state.
�current status rebuild: The second phase of restart processing during which the status of the subsystem is reconstructed from information on the log.
�current volume pointer: In COBOL, a conceptual entity that points to the current volume of a sequential file.
�current working directory: See working directory.
�curriculum: A series of courses that together satisfy a specific set of learning objectives. A student can enroll in a curriculum rather than each of the individual courses it contains, and progress can be tracked over the curriculum as a whole.
�cursor: (1) A named control structure used by an application program to point to and select a row of data from a set. See also insensitive cursor, sensitive cursor, cursor sensitivity, dynamic cursor, static cursor, asensitive cursor.; (2) A movable symbol on a display, often a blinking or solid block of light, that identifies a choice to select, indicates where user interaction with the keyboard will appear, or indicates a position of interest on the display surface.; (3) A reference to an element at a specific position in a data structure.; (4) A displayed symbol that acts as a marker to help the user locate a point in text, in a system command, or in storage. Cursors mark file position and access information in distributed data management (DDM) architecture.; (5) During a HALDB online reorganization, a marker in a database partition that separates the copied database records from the records that have not been copied. The cursor indicates the progress of the reorganization through the HALDB partition.
�cursor-active status: For HALDB online reorganization, the status in the RECON data set that tells DBRC that an online reorganization has started.
�cursor blocking: See blocking.
�cursor movement key: A key that a user presses to move the cursor on the screen.
�cursor sensitivity: The degree to which database updates made by the same application process or another application process are incorporated in the data returned by subsequent FETCH statements for a cursor. See also cursor, insensitive cursor, sensitive cursor, asensitive cursor.
�cursor stability (CS): An isolation level that for cursors, after fetching and while positioned on a row, prevents the row from being changed by other applications until the cursor position is moved from the row. CS also prevents any row that is changed by other applications from being read until the change is committed. See also read stability, repeatable read, uncommitted read, isolation level.
�cursor table (CT): The internal representation of a cursor.
�curve fitting: See smoothness of curve.
�CUSN: See control interval update sequence number.
�custom action: (1) In JSP programming, an action described in a portable manner by a tag library descriptor and a collection of Java classes and imported into a JSP page by a taglib directive. (Sun); (2) A Java or non-Java process definition that you can define as a part of a health policy action plan.
�custom attribute: User-defined characteristics of an asset, for example: support contact and confidential.
�Custom-built Product Delivery Option (CBPDO): A software delivery package consisting of uninstalled products and unintegrated service. Installation requires the use of SMP/E. CBPDO is one of the two entitled methods for installing z/OS; the other method is ServerPac.
�custom data binding: A data binding that is written through a standard interface. See also data binding.
�customer: (1) A user of an online store.; (2) A person or organization, internal or external to the producing organization, who takes financial responsibility for the system. In a large system this may not be the end user. The customer is the ultimate recipient of the developed product and its artifacts. See also stakeholder.; (3) A group or organization that is associated with one or more applications. A customer can be an external organization that accesses a data center or an internal department within a company.
�Customer Console: A user interface to a server.
�customer-facing store: An online site where users may obtain information regarding products and conduct business transactions regarding these products. WebSphere Commerce supports the following customer-facing stores: hub store, direct sales store, and extended site store.
�customer group: A type of member group consisting of a collection of customers who have been grouped by a site administrator because they share similar shopping patterns or characteristics. See also site administrator.
�Customer Initiated Upgrade (CIU): A Web-based application that enables users to configure, order, and download microcode to upgrade processors and memory
�Customer Premise Equipment Alerting Signal tone (CAS tone): In ADSI, this tone is sent to the ADSI telephone to switch the phone to data mode.
�customer premises equipment (CPE): Telephony equipment which is on the premises of a business or domestic customer of the telephone company. An example is a private branch exchange (PBX).
�customer profile: See customer segment.
�customer-replaceable unit (CRU): An assembly or part that a customer can replace. See also field-replaceable unit.
�customer segment: All information about the customer that is held by the seller. This can include basic demographics, order history, or operational data such as the user ID and shipping address. Customer segments are dynamic; marketing managers define the criteria for including a customer in a customer segment. Customer segments can be the targets of campaigns.
�customer service representative (CSR): A defined role in WebSphere Commerce that manages customer inquiries. The customer service representative also processes customer registration, orders, and returns. See also customer service supervisor, order.
�customer service supervisor: A defined role in WebSphere Commerce that has access to all customer service tasks. The customer service supervisor manages customer inquiries (such as customer registration, orders, returns, and auctions) and has authority to complete tasks that cannot be accessed by a customer service representative, such as approving system-denied returns records, and contacting customers regarding payment exceptions (such as credit card authorization failures). See also customer service representative.
�customer session data: Information gathered from customers during the time they visit an online store.
�custom finder: See finder method.
�customization: (1) The ability to change how objects on a personal computer look and work. For example, a user can tailor what objects are in a work area by creating, moving, or copying objects to the work area.; (2) The process of describing optional changes to defaults of a software program that is already installed on the system and configured so that it can be used. See also configuration.; (3) The process of designing a data processing installation or network to meet the requirements of particular users. Activities can include installing additional products, taking advantage of new software features and functions, and enabling or disabling optional features.; (4) The modification of a portal page or portlet by a user. WebSphere Portal enables a user to customize a portal page by modifying the page layout and by selecting which portlets will display per device. See also personalization.
�customization definition document (CDD): An XML document that describes the layout of an instance (that is, its organizational units (OUs) and servers, and which service bundles are assigned to each server-OU combination). The Customization Definition Program (CDP) uses a CDD to determine which deployment data to produce for an instance.
�Customization Definition Program (CDP): A program used to generate deployment data based on information contained in a customization definition document (CDD). It also generates reports that describe the resulting instance.
�customization definition report: A report, generated by the Customization Definition Program (CDP), that describes the servers, organizational units (OUs), and services of an instance, and how they are distributed within the instance.
�customization deployment: Using the deployment data created during customization definition to create the resources required by your runtime systems.
�Customization Input File (CIF): In a z/OS environment, the file that contains configuration data that is required to customize a component.
�customization set: A collection of settings that match users to a custom user interface.
�customization time data: See build time data.
�customizer: A Java class (implementing the java.beans.Customizer interface) that is associated with a bean to provide a richer user interface for that bean's properties.
�custom profile: A profile that describes an empty node, which becomes operational, as a managed node, when federated into a network deployment cell.
�custom relationship: An association between two or more data entities as provided by the user.
�custom scan: The execution of script or binary provided by an application or product that uses Common Inventory Technology.
�custom screen record: A run-time view of the screen that allows access to available screen fields.
�custom server: A C language or C++ language program that provides data manipulation and local or remote data stream, database, or other services beyond those provided by the state table interface. Custom servers provide an interface between DirectTalk and business applications, functions, or other processes to give callers access to business information and voice processing functions such as speech recognition. See also 3270 server.
�custom service: A configurable service that plugs in to a WebSphere Application Server and defines a hook point that runs when the server starts and shuts down when the server stops.
�custom tag: An extension to the JavaServer Pages (JSP) language that performs a specialized task. Custom tags are usually distributed in the form of a tag library, which also contains the Java classes that implement the tags.
�custom text analysis engine: A text analysis engine that is created using the Unstructured Information Management Architecture (UIMA) SDK and can be added to the set of standard enterprise search text analysis engines. See also enterprise search base annotator.
�custom user registry: A customer-implemented user registry that implements the UserRegistry Java interface. This registry type can support virtually any kind of accounts repository from a relational database and can provide flexibility in adapting product security to various environments.
�custom volume: A volume in count-key-data (CKD) format that is not a standard volume, which means that it does not necessarily present the same number of cylinders and capacity to its assigned logical control unit as provided by one of the standard S/390 volume types. See also count key data, standard volume, interleave.
�Custom Wire Format (CWF): The physical representation of a message in the MRM domain that is composed of a number of fixed format data structures or elements, that are not separated by delimiters.
�cut: An action that identifies a page, object, or picture that is to be deleted or moved to another place in the same or different document or file
�CUT: See control unit terminal.
�cut and paste: A type of dictionary gloss used to restore the lemma form the surface form by cutting and pasting new characters.
�cut-off time: The time the clearing channel is cut off, that is, the time after which it no longer settles payments.
�cutover: The point of change from a development CICS system to a production CICS system, or between different releases of CICS.
�cut-sheet paper: Paper that is cut into uniform-size sheets before being loaded into the printer. See also continuous forms.
�cut-through: In fibre-channel technology, a switching technique that allows a routing decision to be made and acted upon as soon as the destination address of a frame is received. See also route.
�cut-through channel: A channel of voice data which has been passed through echo cancellation algorithms. The channel provides echo-cancelled voice data which can then be used by the engine in a recognition attempt.
�CV: See cost variance.
�CVAC: See cost variance at completion.
�CVDA: See CICS-value data area.
�CVS: See Concurrent Versions System.
�CVS file: A text file containing comma separated values, that is, tabular values delimited by commas.
�CWA: See common work area.
�CWALL: An NCP threshold of buffer availability, below which the NCP will accept only high-priority path information units (PIUs).
�CWF: See Custom Wire Format.
�CXRC: See coupled extended remote copy.
�cycle: (1) A set of tables that can be ordered so that each table is a descendent of the one before it, and the first table is a descendent of the last table. A self-referencing table is a cycle with a single member. See also referential cycle.; (2) To end a management collection object that is currently in use and to open a new object for storing future collections. This process prevents collection objects from becoming too large.
�cycle start date: In DFSMShsm, the date a backup cycle, dump cycle, or migration cleanup cycle is started.
�cycle time: The time required for a process instance in a process simulation run to finish processing its inputs. Cycle time includes idle time when an activity in the process is waiting for a resource to become available.
�cyclic redundancy check (CRC): A redundancy check in which the check key is generated by a cyclic algorithm
�cylinder: (1) On a magnetic disk or in an assembly of disks, the set of all tracks that can be accessed by all the magnetic heads of a comb in a given position, without repositioning the access mechanism.; (2) A unit of storage on a count-key-data (CKD) device with a fixed number of tracks.

Back to top�

�

�DA: See device adapter.
�DAA: See designated approving authority.
�DAD: See document access definition.
�DAD script: A file that is used by the DB2 XML Extender, either to compose XML documents from existing DB2 data or to decompose XML documents into DB2 data.
�DADSM: See direct access device space management.
�DADSM interrupt recording facility (DIRF): A provision that ensures that an error is recorded if a system fails or a permanent I/O error occurs during allocation of space or during performance of a routine that updates the volume table of contents (VTOC). The DIRF turns on a bit in the VTOC upon entry to a direct access device space management (DADSM) function and, if no errors occur during processing, turns off that bit upon exiting from that function.
�DADX: See document access definition extension.
�DADX group: A folder that contains database connection (JDBC and JNDI) and other information that is shared between DADX files within the group.
�DADX runtime: In a DADX Web service, the period of time during which SOAP requests are sent to the new Web service. The DADX runtime environment provides information to the DADX Web service, including the HTTP GET and POST bindings, the test page, WSDL generation, and the translation of DTD data into XML schema data.
�DAE: See dump analysis and elimination.
�daemon: A program that runs unattended to perform continuous or periodic functions, such as network control.
�daemon configuration file: In the Distributed Computing Environment (DCE), a file containing information about which daemons are configured on the host, including which environment variables are set, the parameters to pass to the process, the minimum restart interval, and the timeout period.
�DAF: See destination address field.
�DAG: See directed acyclic graph.
�daisy chain: (1) In CICS intercommunication, the chain of sessions that results when a system requests a resource in a remote system, but the remote system discovers that the resource is in a third system and has itself to make a remote request.; (2) See serial connection.
�damaged logical unit of work: The effect on protected resources caused by part of the resources committing and part rolling back.
�DAP: See directory access protocol.
�DARPA: See Defense Advanced Research Projects Agency.
�DAS: See dual-attachment station.
�DASD: See direct access storage device.
�DASD fast write (DFW): A function in which data is written concurrently to cache and nonvolatile storage, and automatically scheduled for destaging to DASD. Both copies are retained in the storage control until the data is completely written to the DASD, providing data integrity equivalent to writing directly to the DASD. Use of DASD fast write for system-managed data sets is controlled by storage class attributes to improve performance. See also cache fast write, dynamic cache management.
�DASD sharing: An option that lets independent computer systems use common data on shared disk devices.
�DASD volume: A direct access storage device (DASD) space identified by a common label and accessed by a set of related addresses. See also primary storage.
�dashboard: (1) A summary view of the status of multiple service level agreements (SLAs). Users can click on links in the displayed Web page to obtain more detailed information on the SLAs as necessary.; (2) A Web page that can contain one or more viewers that graphically represent business data.; (3) An interface that integrates data from a variety of sources and provides a unified display of relevant and in-context information.
�data: A representation of facts or instructions in a form suitable for communication, interpretation, or processing by human or automatic means. Data includes constants, variables, arrays, and character strings.
�data abstraction: A data type with a private representation and a public set of operations (functions or operators) which restrict access to that data type to that set of operations. The C++ language uses the concept of classes to implement data abstraction.
�data access bean: A class library that provides a rich set of features and functions, while hiding the complexity associated with accessing relational databases.
�data acquisition engine: A component of Tivoli Provisioning Manager that gathers and preprocesses metrics from each managed application.
�data aggregate: (1) A logical collection of data elements that can be referred to either collectively or individually.; (2) In PL/I, an arry or a structure.
�data analyst: A technical expert who creates, runs, and reviews data analysis processe
�data area: (1) A memory area that is used by a program to hold information.; (2) A system object used to communicate data, such as CL variable values between the programs within a job and between jobs. The system-recognized identifier for the data area is *DTAARA.; (3) An area of a predefined length and format on a panel in which data can be entered or displayed. A field can consist of one or more data areas.
�data authority: A specific authority to read, add, update, or delete data, to run a program, or to search a library or directory.
�data availability: (1) An IMS enhancement available with DBCTL. It allows PSB scheduling to complete successfully even if some of the full-function databases it requires are not available.; (2) The degree to which data is available when needed, typically measured as a percentage of time that the system would be capable of responding to any data request (for example, 99.999% available).
�data bag: A container of object properties that the MQAI uses in administering queue managers. There are three types of data bag: user (for user data), administration (for administration with assumed options), and command (for administration with no options assumed).
�database (DB): A collection of interrelated or independent data items that are stored together to serve one or more applications.
�database access thread (DBAT): A thread that accesses data on a local subsystem on behalf of a remote subsystem.
�database activity: See activity.
�database administrator (DBA): A person who is responsible for the design, development, operation, security, maintenance, and use of a database.
�database agent: A representation of the physical process or thread that will do the actual work inside the database engine.
�database alias: The name of the target server if it is different from the location name. The database alias is used to provide the name of the database server as it is known to the network.
�database authority: An authority that authorizes the possessor to perform database-level tasks, such as connecting to the database or creating packages in the database. See also authority level, authorization.
�database backup series: One full backup of the database, plus up to 32 incremental backups that were made after that full backup. Each full backup that is run starts a new database backup series. A number identifies each backup series. See also database snapshot.
�database cache: A section of memory on a Domino server where databases are stored for quick access. Administrators can display cache statistics, change the number of databases that a server can hold in its cache, close all databases in the cache, and disable the cache.
�database catalog: A database containing information about databases stored on a single Domino server, a group of servers, or all the servers in a domain. Database catalogs are commonly used to let users add the databases in them to the user's desktop.
�database client: A workstation used to access a database that is on a database server.
�database configuration parameter: A parameter whose value limits the system resources that a database can use. See also configuration parameter.
�Database Connection Services directory (DCS directory): A directory that contains entries for remote host databases and the corresponding application requester used to access them.
�Database Control (DBCTL): (1) An environment that allows full-function databases and DEDBs to be accessed from one or more transaction management subsystems.; (2) An interface between CICS Transaction Server and IMS/ESA that allows access to IMS DL/I full-function databases and to data entry databases (DEDBs) from one or more CICS systems without the need for data sharing. It also provides release independence, virtual storage constraint relief, operational flexibility, and failure isolation.
�database control environment (DBDTL environment): The IMS DB/DC environment without the message handling and queue management capabilities.
�database/data communication (DB/DC): IBM DB/DC program products provide a method to separate the designer and programmer from the physical aspects and constraints of data storage and the physical characteristics of the terminal network, so maximum effort can be placed on the applications.
�database data set (DBDS): A data set that contains some or all of the database records that are stored in a full-function database. Other types of data sets that are used in IMS databases include Fast Path area data sets, HALDB indirect list data sets, and HALDB primary index data sets.
�database definition: A Data Interchange Services definition that contains information used by Data Interchange Services Client to connect to a database.
�database description (DBD): The collection of macro parameter statements that define the characteristics of a database, such as the database's organization and access method, the segments and fields in a database record, and the relationship between types of segments.
�database description generation (DBDGEN): The process by which a DBD is created.
�database descriptor (DBD): An internal representation of a DB2 for z/OS database definition, which reflects the data definition that is in the DB2 for z/OS catalog. The objects that are defined in a database descriptor are table spaces, tables, indexes, index spaces, relationships, check constraints, and triggers. A DBD also contains information about accessing tables in the database.
�database directory: A directory that contains database access information for all databases to which a client can connect.
�database engine: The part of the database manager that provides the base functions and configuration files that are needed to use the database.
�database exception status: In a data sharing environment, an indication that something is wrong with a database.
�database file: (1) One of several types of the system object type *FILE kept in the system that contains descriptions of how input data is to be presented to a program from internal storage and how output data is to be presented to internal storage from a program.; (2) In Lotus Notes, a file with the extension NSF that contains the data for an application. Its structure is composed of forms, fields, folders, views, and other presentation features, such as a navigator and a database icon.
�database header: An internal structure that stores database-wide information such as a time stamp that indicates when a database was first created or when the Fixup task last ran on it.
�database ID: See database identifier.
�database identifier (DBID, database ID): (1) The time stamp that is located in the Notes database header and that indicates when a Notes database was first created or when the Fixup task last ran on it.; (2) An internal identifier of the database.
�database instance ID (DBIID): A value that is located in the Notes database header and that associates the database with specific entries in the transaction log.
�database integrity: The protection of data items in a database while they are available to any application program. This protection includes the isolation of effects of concurrent updates to a database by two or more application programs.
�database-level sharing: A kind of data sharing that enables application programs in one IMS to read data while another program in another IMS reads from the same database or updates it. See also block-level sharing, data sharing.
�database-level tracking: In an RSR environment, a tracking subsystem that tracks the active subsystem's databases or areas.
�database library: A database that lists database links and uses replication ID numbers to locate databases on various servers. For example, a corporate database library might contain databases that deal with corporate policies and procedures.
�database log: A set of primary and secondary log files consisting of log records that record all changes to a database. The database log is used to roll back changes for units of work that are not committed and to recover a database to a consistent state.
�database-managed space table space (DMS table space): A table space whose storage space is managed by the database manager. See also system-managed space table space.
�database management batch (DBB): One of two batch regions (the other being a DL/I batch region). DBB is an execution parameter. DBB batch jobs contain JCL DD statements for the ACB library.
�database management system (DBMS): (1) See database manager.; (2) A software system that controls the creation, organization, and modification of a database and the access to the data that is stored within it.
�database manager: (1) A person with Manager access to a Notes database, whose responsibilities include setting up and maintaining access to the database and monitoring database replication, usage, and size.; (2) A program that manages data by providing centralized control, data independence, and complex physical structures for efficient access, integrity, recovery, concurrency control, privacy, and security. See also data server.; (3) A program used to create and maintain a database and to communicate with programs requiring access to the database.
�database manager configuration parameter: A configuration parameter whose value is set when an instance is created. Most database manager configuration parameters affect the amount of system resources that is allocated to a single instance of the database manager, or they configure the setup of the database manager and the different communications subsystems based on environmental considerations.
�database manager instance: A logical database manager environment that consists of configuration files, directories, and a set of authorized users.
�database monitor (DB monitor): See IMS monitor.
�database name: An identifier that designates a database. A database name must be unique within the location in which it is cataloged. See also server name.
�database node: See database partition.
�database object: An object that exists in an installation of a database system, such as an instance, a database, a database partition group, a buffer pool, a table, or an index. See also object.
�database organization: The physical arrangement of related data on a storage device. DL/I database organizations are hierarchical direct (HD) and hierarchical sequential (HS).
�database partition: A portion of a database that consists of its own user data, indexes, configuration file, and transaction logs. Database partitions exist on a database partition server and can be logical or physical. See also database partition group.
�database partition group: A named subset of database partitions that is grouped together with a common distribution map. All table spaces that are created under the same database partition group have data on the same set of database partitions. See also database partition.
�database partitioning: A data organization scheme in which table data is divided across multiple database partitions based on the hash values in one or more distribution key columns of the table and based on the use of a distribution map of the database partitions. Data from a given table is distributed based on the specifications that are provided in the DISTRIBUTE BY clause of the CREATE TABLE statement. See also massively parallel processing, data partition, table partitioning.
�Database Partitioning Feature (DPF): A feature that can be used to improve the management of a large database by dividing it into multiple database partitions that are physically placed on one or more servers. See also massively parallel processing.
�database position: A program's place in the database after a DL/I call. IMS keeps track of the program's position in the database in order to process DL/I calls.
�database program communication block (DB PCB): The PCB that describes an application program's interface to a database. One DB PCB is required for each database view that is used by the application program.
�database record: In an IMS database, a collection of segments that contains one occurrence of the root segment type and all of its dependents arranged in a hierarchic sequence. A database record can be a physical database record or a logical database record. See also logical database record, physical database record.
�database recovery: (1) The process of restoring a physically or logically damaged DBDS by merging an image copy and logs or change accumulation data sets.; (2) The function of restoring the user data sets, starting with a backup copy and applying all changes made to each data set after the backup was taken.
�Database Recovery Control (DBRC): A feature of the IMS Database Manager that facilitates easier recovery of IMS databases. DBRC maintains information that is required for database recoveries, generates recovery control statements, verifies recovery input, maintains a separate change log for database data sets, and supports sharing of IMS databases and areas by multiple IMS subsystems.
�database recovery log: See database log.
�database reference field: In the Data Description Specifications Design Utility (DSU), a field in a data description specifications (DDS) source file that is created by referring to the description of an existing field in a database file.
�database reorganization: The process of unloading and reloading a database to optimize physical segment adjacency or to modify the DBD.
�database replica: A special copy of a Notes database that, because it shares a replica ID with the original database, can exchange information with it through replication.
�database request module (DBRM): A data set member that is created by the DB2 for z/OS precompiler and that contains information about SQL statements. DBRMs are used in the bind process.
�database resource adapter (DRA): (1) Component of the CICS-DBCTL interface in the CICS address space. Its functions include requesting connection and disconnection from DBCTL, telling CICS when a shutdown of DBCTL has been requested or if DBCTL has failed, managing threads, establishing contact with the DBCTL address space, and loading the DRA startup parameter table.; (2) An interface to IMS DB full-function databases and DEDBs. The DRA can be used by a coordinator controller (CCTL) or a z/OS application program that uses the ODBA interface.
�database response file: A text file that specifies parameters for configuring the database.
�database schema: A collection of database objects such as tables, views, indexes, or triggers that define a database. A database schema provides a logical classification of database objects.
�database segment: The unit of access; the smallest amount of data that can be transferred by one IMS operation.
�database server: (1) A software program that uses a database manager to provide database services to other software programs or computers.; (2) The server on which the database application and database are installed.; (3) A computer that is dedicated to running a database manager to provide database services to other software programs or computers. See also data server.
�database server node: In a single system image (SSI), a DirectTalk system that contains the DirectTalk DB2 database. This is usually the same node as the voice server node.
�database set: One or more user databases and the schema repository that stores the schema they all use.
�database snapshot: A complete backup of the entire database to media that can be taken offsite. When a database snapshot is created, the current database backup series is not interrupted. A database snapshot cannot have incremental backups associated with it. See also database backup series, full backup.
�database system monitor: A collection of APIs that gathers information regarding the state of the database system at the instance, database, and application levels. This information is stored in data elements, which can be examined by taking point-in-time snapshots or by using the event monitor to log system activity over a period of time.
�data bean: A type of bean that is placed in a JSP file. Data beans can have associated commands that are invoked when the JSP file instantiates the data bean at run time.
�data bean command: A command associated with a data bean, and called by a JSP file. This command retrieves data for the data bean from a persistent object, such as an entity bean.
�data bean manager: A module that invokes a data bean command to fetch data from corresponding entity beans.
�data binding: (1) A process that allows the user to represent some form of data as an Object in memory.; (2) A Java class that converts a stream of native data to a business object during inbound processing, and converts a business object to a stream of native data during outbound processing. See also custom data binding.
�data bus: A computer facility used to transfer data among processing units, storage, or peripheral devices.
�Data Cache Manager: A component of CICSPlex SM that manages logical cache storage for use by other CICSPlex SM components.
�data cache unit (DCU): A high-speed buffer storage that contains frequently accessed instructions and data to reduce access time.
�data carrier detect: A signal defined in the EIA-232 standard that indicates to the data terminal equipment (DTE) that it is receiving a signal from the remote data circuit-terminating equipment (DCE).
�data catalog: A collection of models representing objects, such as business items and notifications, to be used as inputs and outputs in process modeling.
�data center: A centralized repository of data and information relating to a particular field of knowledge.
�data center asset: A logical or physical resource in a data center. Examples include servers, switches, load balancers, software, VLANs, security policies, and service level agreements.
�data center device: See data center asset.
�data center fragment (DCF): A list of data center model objects required to support an application deployment template. It is a subset of the data center model.
�data center model (DCM): A centralized repository, containing physical and logical assets, that Tivoli Intelligent Orchestrator manages, and their relationships. The data center model tracks data center devices, their configuration, and associated allocations to applications.
�data center object: An abstract representation of a data center asset. Data center objects are used to create a data center model.
�data chaining (DC): The process of using information from one data source or location to access another data source or location.
�data character set: See character set.
�data check: (1) An operation used to verify data quality or data integrity.; (2) A synchronous or asynchronous indication of a condition caused by invalid data or incorrect positioning of data. Some data checks can be suppressed.
�data circuit: A pair of associated transmit and receive channels that provide a means of two-way data communication.
�data circuit-terminating equipment (DCE): The equipment that provides signal conversion and coding between the data terminal equipment (DTE) and the line. The DCE provides all the functions required to establish, maintain, and end a connection.
�data class: (1) An access bean that provides data storage and access methods for caching enterprise bean properties. Unlike copy helpers, data class access beans work with enterprise beans that have local client views as well as remote client views.; (2) A named list of allocation and space attributes that the system uses when creating a data set. The storage administrator uses the Interactive Storage Management Facility (ISMF) to define data classes, but the affected data sets are not required to be managed by the storage management subsystem (SMS). See also storage construct.; (3) A classification that designates the logical type of data in of a data field. For example, the classification INDICATOR represents a binary value such as TRUE/FALSE or YES/NO.
�data clause: In COBOL, a clause in a data description entry in the Data Division that describes a particular characteristic of a data item.
�data cleansing: The process of preparing data for integration by using data matching, standardization, enrichment, and survivorship operations to simplify the process of integrating similar data from multiple sources.
�data code page: In Network File System (NFS), a list of the data name components of the files that are exported to and mounted on the specified NFS client or netgroup.
�data collection: The process of obtaining performance and availability monitoring data and providing that data to a metric evaluator. Examples of data collectors include DNS probes, Web page analyzers, or database analyzers. See also metric evaluation.
�data collection application: An Interactive Storage Management Facility (ISMF) application that allows the storage administrator interactively to submit IDCAMS DCOLLECT background jobs or to save job control language (JCL) for later use.
�data column: A vertical arrangement of identical data items that is used on list panels to display an attribute, characteristic, or value of one or more objects.
�data communication: Transfer of data among functional units by means of data transmission protocols.
�data communication equipment (DCE): A device that establishes, maintains and terminates a session on a network. It may also convert signals for transmission. It is typically the modem.
�data communication program communication block (DC-PCB): See telecommunication program PCB.
�Data Communications Control (DCCTL): A subsystem that allows IMS TM to act as a stand-alone, full-function transaction manager that can connect to DB2 or other external subsystems.
�data component: The part of a Virtual Storage Access Method (VSAM) data set, alternate index, or catalog that contains the object's data records.
�data compression: (1) The reduction of data volume on the media when performing save operations.; (2) The process of eliminating gaps, empty fields, redundancies, and unnecessary data to shorten the length of records or blocks.
�data confidentiality: A function of the system that prevents unauthorized disclosure of data.
�data connection resource (DCR): A design element that is used to define a connection between a Notes form and an enterprise database for exchanging data.
�data consolidation: Replication of data from more than one source database to a single target database.
�data container: A named area of storage, maintained by BTS, and used to pass data between activities, or between different invocations of the same activity. Each data container is associated with an activity; it is identified by its name and by the activity for which it is a container. An activity can have any number of containers, as long as they all have different names.
�data control block (DCB): A control block used by access method routines in storing and retrieving data.
�data conversion: (1) The process of changing data from one form of representation to another.; (2) The process of changing from one coded character set identifier (CCSID) to another. A system does data conversion when exchanging data with another system that is using a different CCSID.
�data-conversion interface (DCI): The WebSphere MQ interface to which customer- or vendor-written programs that convert application data between different machine encodings and CCSIDs must conform. A part of the WebSphere MQ Framework.
�data-conversion service: A service that converts application data to the character set and encoding that are required by applications on other platforms.
�data country code (DCC): A 3-digit code, unique to each country or region, that specifies the X.21 call format used by a network in its International Data Number to call another station. See also data network identification code.
�data currency: The state in which data that is retrieved into a host variable in a program is a copy of data in the base table.
�data decompression: Reconstruction of data from a compressed format when performing a restore operation.
�data definition (DD): (1) In IDDU, information that describes the contents and characteristics of a field, record, or file.; (2) A program statement that describes the features of, specifies relationships of, or establishes the context of data. A data definition reserves storage and can provide an initial value.; (3) A data object that defines a database or table.
�Data Definition Language (DDL): A language for describing data and its relationships in a database. See also Data Manipulation Language.
�data definition name (ddname): The name of a data definition (DD) statement that corresponds to a data control block that contains the same name.
�data definition statement (DD statement): A job control statement that is used to define a data set for use by a batch job step, started task or job, or an online user.
�data description entry: In COBOL, an entry in the Data Division that describes the characteristics of a data item.
�Data Description Language: See Data Definition Language.
�data description specifications (DDS): A fixed format for describing and creating i5/OS databases or device files.
�Data Description Specifications Design Utility (DSU): A feature of the CoOperative Development Environment/400 licensed program that helps users develop and create display files, printer files, and database files.
�data dictionary: (1) In IDDU, an object for storing field, record format, and file definitions. The system-recognized identifier for the object type is *DTADCT.; (2) A repository of information about an organization's application programs, databases, logical data models, users, and authorizations.; (3) A grouping of logically related components of a particular syntax type, such as ROD dictionaries, EDI dictionaries, and XML dictionaries.
�data directory: A directory that contains local Notes databases, local database templates, country language services (CLS) files, and configuration files.
�data distribution: A means of dividing table data across multiple database partitions based on the hash values in one or more distribution key columns of the table and based on the use of a distribution map of the database partitions.
�data division: One of the four main parts of a COBOL program. The data division describes the files to be used in the program and the records contained within the files. It also describes any internal working storage records that are needed.
�data dump: In COBOL, the contents of the data areas used by a program that has failed.
�data element: (1) A unit of data that, in certain context, is considered indivisible. An example is the data element "age of a person" with values consisting of all three-decimal digit combinations.; (2) The smallest unit of data that can be referred to.; (3) See monitor element.; (4) A unit of storage in a coupling facility list structure that makes up a data entry.; (5) In server jobs, a specification that describes the type of data in a column and how the data is converted.
�data element delimiter: A character, such as an asterisk (*), that follows the EDI segment identifier and separates each EDI data element in an EDI segment. See also segment ID separator.
�data element separation: A delimiter sequence that defines how a TDS message is to be parsed. The following separation types are supported: data pattern separation, delimited separation, fixed length separation, and tagged separation.
�data-encrypting key: A key that is used to encipher, decipher, or authenticate data. See also key-encrypting key.
�Data Encryption Algorithm (DEA): (1) In Cryptographic Support, the equivalent to the Data Encryption Standard.; (2) In computer security, a 64-bit block cipher that uses a 64-bit key, of which 56 bits are used to control the cryptographic process and 8 bits are used for parity checking to ensure that the key is transmitted properly.
�Data Encryption Standard (DES): A cryptographic algorithm designed to encrypt and decrypt data using a private key.
�data entry: (1) A catalog entry that describes the data component of a cluster, alternate index, page spaces, or catalog. A data entry contains the data component's attributes, allocation and extent information, and statistics. A data entry for a cluster's or catalog's data component can also contain the data component's passwords and protection attributes.; (2) Part of a coupling facility list structure list entry that is used to hold user-specified data.
�data entry database (DEDB): A direct-access database that consists of one or more areas, with each area containing both root segments and dependent segments. DEDBs use a data structure that allows them to be used for both hierarchic processing and journaling. The database is accessed by using the VSAM Media Manager. See also Fast Path, sequential dependent segment.
�data entry panel: An interface with which the user communicates with the system by completing one or more fields.
�data event control block: A control supplied by an application program to represent a read or write request for the basic direct access method (BDAM), basic partitioned access method (BPAM), or basic sequential access method (BSAM).
�Data Exchange SPI architecture (DESPI): The interface by which resource adapters and runtime components exchange business object data. It is based on the concept of cursors and accessors, abstracting the data type so that an adapter can be written once and work on runtimes supporting different data types, such as data objects and JavaBeans.
�Data Facility Hierarchical Storage Management System (DFHSM): A DASD management tool for automatically managing low-activity and inactive data in DFSMS and non-DFSMS environments.
�Data Facility Sort (DFSORT): An IBM licensed program that is a high-speed data-processing utility. DFSORT provides an efficient and flexible method for sorting, merging, and copying operations, as well as providing versatile data manipulation at the record, field, and bit level.
�Data Facility Storage Management Subsystem: See DFSMS.
�data field: (1) The optional third field of a count-key-data (CKD) record. The data field contains data that the program writes. The count field specifies the length of the data field.; (2) A column or field that contains a specific set of data values that are common to all records in a file or table.
�data file: (1) A group of related data records organized in a specific order. A data file can be created by the specification of FILETYPE(*DATA) on the create commands. See also command file, source file.; (2) In RJE, a remote job input stream that can contain host system commands and job control language as well as data.
�data file utility (DFU): The part of the Application Development ToolSet feature that is used to enter, maintain, and display records in a database file.
�data flow: A graphical model that defines activities that extract data from flat files or relational tables, transform the data, and load it into a data warehouse, data mart, or staging table.
�data flow control (DFC): In SNA, a request/response unit (RU) category used for requests and responses exchanged between the data flow control layer in one half-session and the data flow control layer in the session partner.
�data flow control layer (DFC layer): In SNA, the layer within a half-session that (a) controls whether the half-session can send or receive, or both send and receive request units (RUs) at the same time, (b) combines related RUs into RU chains, (c) defines the limits of transactions by using the bracket protocol, (d) controls the connection of requests and responses in accordance with control modes specified when the session is started, (e) creates sequence numbers, and (f) associates requests with responses.
�data format: A description of the application data for a particular transaction. An application data format is composed of data structures and fields.
�datagram: (1) A self-contained packet, independent of other packets, that carries information sufficient for routing from the originating data terminal equipment (DTE) to the destination DTE without relying on earlier exchanges between the DTEs and the network.; (2) A form of asynchronous messaging in which an application sends a message, but does not require a response.
�Datagram Delivery Protocol (DDP): In AppleTalk networks, a protocol that provides network connectivity by means of connectionless socket-to-socket delivery service on the internet layer.
�datagram protocol: In Distributed Computing Environment (DCE) Remote Procedure Call (RPC), a datagram-based transport protocol, such as User Datagram Protocol (UDP), that provides a connectionless transport layer.
�data graph: A set of Service Data Objects (SDO) interconnected with relationships.
�data group: (1) In Business Graphics Utility, a collection of values that identify the comparisons in a chart. For example, the relative size of the slices in a pie chart or the relative height of the bars in a bar chart. See also data value.; (2) In the GDDM function, a collection of data values displayed, for example, as a pie chart or as the plotted points on a line of a line chart. More than one data group may be displayed on a chart.
�data handler: A Java class or library of classes that a process uses to transform data into and from specific formats. In the WebSphere business integration environment, data handlers transform text data of specified formats into business objects, and transform business objects into text data of specified formats.
�data hierarchy: In COBOL, the relationship between a group item or record and the group data items and elementary data items that make it up.
�data independence: (1) The concept of separating the definitions of logical and physical data such that application programs do not depend on where or how physical units of data are stored; the reduction of application program modification in data storage structure and access strategy.; (2) In CICS, the ability to request data by a high-level data-management method without concern as to how the data is stored or retrieved.
�data integrity: (1) The condition that exists as long as accidental or intentional destruction, alteration, or loss of data does not occur.; (2) The security service that detects whether there has been unauthorized modification of data, or tampering. The service detects only whether data has been modified; it does not restore data to its original state if it has been modified.
�data interchange: (1) The use of data by systems of different manufacture.; (2) The sharing of data between applications.
�data interchange block (DIB): A block created by the CICS data interchange program (DIP) to control input and output to SNA batch devices. The DIB is chained to the appropriate TCTTE for the batch device, and is released at the termination of the transaction.
�data interchange format (DIF): In System i Access, a format that presents data in rows and columns.
�data interchange program (DIP): A CICS program that communicates with batch data interchange terminals, such as the 3790, for bulk transfer of dumps, data sets, and so on.
�Data Interchange Services (DIS): A feature of WebSphere Partner Gateway that provides support for exchanging EDI documents; it consists of a set of tools for describing document metadata and mapping documents to one another along with the associated runtime components for executing document transformations. Data Interchange Services is also compatible with WebSphere Data Interchange.
�Data Interchange Services client (DIS client): The Data Interchange Services tool used to document metadata and map documents to one another.
�Data Interchange Services database: The database that contains all Data Interchange Services objects.
�Data Interchange Services translator: The Data Interchange Services component responsible for transforming a document from one format to another.
�Data Interfile Transfer, Testing and Operations utility (DITTO utility): An IBM licensed program that provides file-to-file services for card I/O, tape, and disk devices.
�data in transit: The update data on application, system, direct access storage device (DASD) volumes that is being sent to the recovery system to be written to DASD volumes on the recovery system.
�data item: (1) A unit of information to be processed.; (2) In COBOL, a character or a set of consecutive characters (excluding literals in either case) defined as a unit of data by the COBOL program.; (3) In EGL, an area of memory that is not in a structure and is based either on a data item part or on an explicit primitive-type description such as CHAR(3).; (4) In the MQAI, an item contained within a data bag. This can be an integer item or a character-string item, and a user item or a system item.
�data label: In Business Graphics Utility and the GDDM function, a text string that describes a set of data values. Data labels are used with bar charts, pie charts, and Venn diagrams.
�Data Language/I (DL/I): The IMS data manipulation language, which is a common high-level interface between a user application and IMS. DL/I calls are invoked from application programs that are written in languages such as Java, PL/I, COBOL, VS Pascal, C, and Ada. DL/I can also be invoked from assembler language application programs by subroutine calls. IMS lets the user define data structures, relate structures to the application, load structures, and reorganize structures.
�data line: (1) In Business Graphics Utility, a straight line drawn from either axis that shows the exact data values on the chart.; (2) In the GDDM function, a line drawn parallel to a chart axis, through a specified value along the other axis.
�datalink: A field in a database file that contains a link to an object. The link is in the form of a uniform resource locator (URL).
�data link: The physical connection (communications lines, modems, controller, work stations, other communications equipment), and the rules (protocols) for sending and receiving data between two or more locations in a data network.
�data link connection identifier (DLCI): (1) The field in a Q.922 frame that is used for frame relay routing. Each DLCI identifies a frame relay virtual circuit.; (2) The numeric identifier of a frame-relay subport or PVC segment in a frame-relay network. Each subport in a single frame-relay port has a unique DLCI.
�data link control (DLC): A set of rules used by nodes on a data link (such as an SDLC link or a token ring) to accomplish an orderly exchange of information.
�data link control layer (DLC layer): In communications, the layer that consists of the link stations that schedule data transfer over a link between two nodes and perform error control for the link. Examples of data link control are SDLC and HDLC. See also data flow control layer.
�data link control protocol (DLC): The protocol layer used by nodes on a data link to accomplish an orderly exchange of information.
�data link escape character (DLE, DLE character): In binary synchronous communication (BSC), a transmission control character used to indicate that the next character is a control character, not a data character.
�DataLink File Manager: A system function that maintains the status of objects that are linked to a database file through a datalink.
�data link layer: In the Open Systems Interconnection reference model, the layer that provides services to transfer data between entities in the network layer over a communication link. The data link layer detects and possibly corrects errors that may occur in the physical layer.
�data link level: In the hierarchical structure of a data station, the conceptual level of control or processing logic between high level logic and the data link that maintains control of the data link. The data link level performs such functions as inserting transmit bits and deleting receive bits; interpreting address and control fields; generating, transmitting, and interpreting commands and responses; and computing and interpreting frame check sequences.
�data link protocol: (1) The rules that govern control of the physical connection for sending and receiving data between two or more locations in a network. Examples of data link protocols include (a) asynchronous, (b) binary synchronous communications (BSC), (c) Ethernet, (d) synchronous data link control (SDLC), (e) token-ring network, and (f) X.25. See also communications line.; (2) In SNA, a set of rules for data communication over a data link in terms of a transmission code, a transmission mode, and control and recovery procedures.
�data management: (1) The part of the operating system that controls the storing and accessing of data to or from an application program. The data can be on internal storage (for example, database), on external media (diskette, tape, or printer), or on another system.; (2) The task of systematically identifying, organizing, storing, and cataloging data in an operating system.
�data management application program interface (DMAPI): The interfaces defined by the Open Group's Data Storage management (XDSM) specification. These interfaces support the monitoring of events on files and the management and maintenance of the data in a file.
�data management block (DMB): An IMS control block in main storage that describes and controls a physical database. A DMB is constructed from information that is obtained from the ACB library or the DBD library.
�Data Management Services: The DB2 component that controls creating, removing, maintaining, and accessing the tables and table data in a database.
�Data Manipulation Language (DML): A subset of SQL statements that is used to manipulate data. Most applications primarily use DML SQL statements, which are supported by the DB2 Connect program. SELECT, INSERT, UPDATE, and DELETE statements are similar across the IBM relational database products. See also Data Definition Language, Structured Query Language.
�data map: An internal object in a page definition that specifies fonts, page segments, fixed text, page size, and the placement and orientation of text.
�data mapping: The process of changing characters from one form of representation to another, such as from zoned decimal to packed decimal.
�data map transmission subcase: An internal object that specifies the control information for printing line data. One data map transmission subcase must appear in each data map of a page definition.
�data mart: A subset of a data warehouse that contains data that is tailored and optimized for the specific reporting needs of a department or team. A data mart can be a subset of a warehouse for an entire organization, such as data that is contained in online analytical processing (OLAP) tools.
�data mart ETL: In Tivoli Enterprise Data Warehouse, the extract, transform, and load (ETL) process that extracts a subset of data from the central data warehouse, transforms it, and loads it into one or more star schemas. These schemas then can be included in data marts to answer specific business questions. See also central data warehouse ETL.
�data mart server: A machine that hosts one or more data marts. Multiple data mart servers can draw data from the same central data warehouse.
�data member: The smallest possible piece of complete data. Elements are composed of data members.
�data message: In Q replication and event publishing, a message that contains all or part of a committed transaction that involves source tables, a committed operation on a single row in a source table (event publishing only), or all or part of a large object (LOB) value from a row operation within a transaction.
�data migration: (1) The movement of data when the software is upgraded or the data is transferred to a different hardware server or model.; (2) The movement of data from one physical location to another without disruption of application I/O operations.
�data mining: The process of collecting critical business information from a data warehouse, correlating the information and uncovering associations, patterns, and trends.
�data mode: In data communications, a time during which BSC is sending or receiving characters on the communications line.
�data model: (1) A logical view of the organization of data in a database.; (2) A description of the organization of data in a manner that reflects the information structure of an enterprise.; (3) A model defining the structure of business artifacts that are operated upon by business operations.
�data modeling: A structured set of techniques for defining and recording business information requirements. It is a depiction of the user's view of the data needs of the organization in a consistent and rigorous fashion. The data model eventually serves as the basis for translation to computer system databases.
�data movement operation: An operation that physically moves a row from one location to another location in a table. Examples of data movement operations are updating database partitioning keys and reorganizing tables.
�data mover: (1) A device that moves data on behalf of the server. A network-attached storage (NAS) file server is a data mover.; (2) The program that copies data when a backup of the control data sets is being made.
�data multiplexer: See multiplexed device.
�data name: In COBOL, a user-defined word that names a data item. When used in the general formats, data name represents a word that cannot be subscripted, indexed, or qualified unless specifically permitted by the rules of that format. See also identifier.
�data network: An arrangement of data circuits and switching facilities for establishing connections between data terminal equipment.
�data network identification code (DNIC): A 4-digit code that specifies the X.21 call format used by a network in its International Data Number to call another station. The first three numbers are the data country or region code, and the last number is the country or region network identifier. See also data country code.
�data note: A document in a Notes database.
�data object: (1) A program variable that provides operational and possibly representational characteristics to byte strings in spaces.; (2) An object that conveys information, such as text, graphics, audio, or video. See also machine object.; (3) A piece of client data that is placed on the coupling facility by CQS as a result of a CQSPUT request or a CQSUPD request. From an IMS shared queues point of view, a data object contains one part or all of an IMS message or an entire EMH message. From an IMS Resource Manager point of view, a data object contains information about an IMS resource such as a transaction or a user.; (4) Any object (such as tables, views, indexes, functions, triggers, and packages) that can be created or manipulated using SQL statements. See also business object.; (5) An object that is either specified within a page or overlay or is identified as a resource using the Map Data Resource (MDR) structured field and later included in a page or overlay. Examples include: PDF single-page objects, encapsulated PostScript objects, and IOCA images.; (6) An element of data structure such as a file, an array, or an operand that is needed for the execution of an application.
�data object filter: A control that allows the exclusion of data objects (such as tables and schemas) from the tree view of the database.
�data object resource: An object container resource or IOCA image resource that is either printer resident or downloaded. Data object resources can be used to prepare for the presentation of a data object, such as with a resident color profile resource object, included in a page or overlay through the Include Object (IOB) structured field; for example, PDF single-page objects, encapsulated PostScript objects, and IOCA images, or invoked from within a data object; for example, PDF resource objects.
�data origin authentication: The confirmation that data comes from the apparent originator.
�data-owning region (DOR): A CICS address space whose primary purpose is to manage files and databases. See also terminal-owning region, application-owning region.
�data packet: In X.25 communications, a packet used for the transmission of user data on a virtual circuit at the DTE/DCE interface.
�data part: An EGL definition that specifies a data structure. The types of data parts are dataItem, dataTable, and record parts.
�data partition: (1) A VSAM data set that is contained within a partitioned table space.; (2) A set of table rows that is stored separately from other sets of rows. A data partition is grouped by the specifications that are provided in the PARTITION BY clause of the CREATE TABLE statement. See also database partitioning, table partitioning.
�data-partitioned secondary index (DPSI): A secondary index that is partitioned according to the underlying data. See also nonpartitioned secondary index.
�Dataphone digital service (DDS): The AT&T line service that allows the customer to transmit data on the line in a digital format.
�data pipelining: The process of pulling records from the source system and moving them through the sequence of processing functions that are defined in the data flow.
�data pointer: A pointer that provides addressability and scalar representational attributes to a byte string in a space.
�data policy: The collection of protocols that governs Phase II negotiations.
�data pump: The combination of the disks that hold the data and the networking hardware and software required to deliver assets to clients.
�data queue: An object that is used to communicate and store data used by several programs in a job or between jobs. The system-recognized identifier is *DTAQ.
�Dataradio Multiplex Protocol (DMP): The protocol that is used in a Dataradio network.
�data rate: The rate at which data is transmitted or received from a device. Interactive applications tend to require a high data rate, while batch applications can usually tolerate lower data rates.
�data record: The basic unit of S/390 and zSeries storage on an ESS, also known as a count-key-data (CKD) record. See also index record, count key data, fixed-block architecture, track.
�data reference line: In the GDDM function, a data line that also acts as a shading boundary for the first data group of a surface chart, histogram, or composite bar chart, or for all the data groups of a multiple bar chart. If no data reference line is present, such data groups are shaded from the horizontal axis.
�data resource manager: A program that allows applications to read and change data. Changes are coordinated using a sync point manager.
�data security: The protection of data against unauthorized disclosure, transfer, modification, or destruction, whether accidental or intentional.
�data segment: A specification type of the autonomic computing architecture that defines a commonly used arrangement of data, as described by the World Wide Web Consortium (W3C).
�data server: (1) A device on a local area network (LAN) that provides services, data, or facilities for other devices on the network.; (2) A server that provides services for the secure and efficient management of information. See also database management system, database server.
�Data Server Client: See IBM Data Server Client.
�data server client: See IBM data server client.
�data server driver copy: See IBM data server driver copy.
�Data Server Provider for .NET: See IBM Data Server Provider for .NET.
�data service unit (DSU): A device that provides a digital data service interface directly to the data terminal equipment. The DSU provides loop equalization, remote and local testing capabilities, and a standard EIA/CCITT interface.
�data service unit/channel service unit (DSU/CSU): A device used to connect a system to a digital communications line.
�data set: (1) See file.; (2) The major unit of data storage and retrieval, consisting of a collection of data in one of several prescribed arrangements and described by control information to which the system has access. See also file.
�data set change indicator: A bit in the data set label that the system sets when the data set is opened for processing other than input.
�data set collection: A group of data sets that are intended to be allocated on the same tape volume or set of tape volumes as a result of data set stacking.
�data set concatenation: The allocation of two or more data sets such that the access method retrieves them as a single data set. The two types of data set concatenation are sequential and partitioned. See also partitioned concatenation, sequential concatenation.
�data set control block (DSCB): A control block in the volume table of contents (VTOC) that describes data sets.
�data set deletion: (1) Removing a data set control block (DSCB) and releasing its space. A tape data set generally is considered to be deleted when its volume or volumes are made available for reuse or destruction. For both disk and tape, deletion generally also includes removing the data set's entry from the catalog DSCB.; (2) In DFSMShsm, the space management technique of deleting data sets, not managed by the storage management subsystem (SMS), that have not been used for a specified number of days and do not have expiration date protection.
�data set forwarding: The dynamic replacement of the specifications of the checkpoint data set with new specifications.
�data set group: An operating system data set that contains a subset of a database with one or more unique segment types. A database always consists of at least one data set group. See also primary data set group, secondary data set group.
�data set header: A page in printed output that separates multiple data sets or multiple copies of a data set within a print job. See also job header.
�data set instance number: A number that indicates the data set that contains the data for an object.
�data set label: Record that is used to identify data sets and contain information about those data sets.
�data set name (dsname): An identifier assigned to a data set.
�data set name block (DSNAME block, DSNB): An area, addressed by a FCT entry, that represents a physical VSAM or BDAM (DAM in CICS/VSE) data set that is being accessed through one or more CICS files. A DSNAME block (DSNB) is created, if it does not already exist, when a file is opened or, in CICS Transaction Server only, when a SET FILE DSNAME command is executed.
�data set name sharing: An MVS or VSE option that allows one set of control blocks to be used for the base and the path in a VSAM alternate index.
�data set organization (DSORG): The type of arrangement of data in a data set, such as sequential organization or partitioned organization.
�data set pool: One or more volumes managed by DFSMShsm to which data sets that have migrated can be recalled, depending on the set of initial characters of the data set name.
�data set profile: A profile that provides RACF protection for one or more data sets. The information in the profile can include data such as the profile owner, universal access authority, and access list. See also discrete profile, generic profile.
�data set ready (DSR): In the EIA 232 standard, a signal that indicates to the data terminal equipment (DTE) that the local data circuit-terminating equipment (DCE) is connected to the communication channel and is ready to send data.
�data set retirement: In DFSMShsm, the space management technique of deleting data sets, not managed by the storage management subsystem (SMS), that have not been referred to for a specified number of days and have a backup version. See also delete-if-backed-up.
�data set separator page: A page of printed output that delimits data sets.
�data set sequence number (DSSN): A number, maintained by DBRC in the RECON data set, that counts when an application opens a database for update.
�data set stacking: A function that places several data sets on the same tape volume or set of tape volumes. Data set stacking increases the efficiency of tape media usage and reduces the overall number of tape volumes needed by allocation. It also allows an installation to group related data sets on a minimum number of tape volumes, which is useful when sending data off-site.
�data sharing: (1) A function of DB2 for z/OS that enables applications on different DB2 subsystems to read from and write to the same data concurrently.; (2) The ability of multiple host systems to concurrently use data that they store on one or more storage devices. The storage facility enables configured storage to be accessible to any, or all, attached host systems. To use this capability, the host program must be designed to support data that it is sharing.; (3) The ability of concurrent subsystems (such as DB2 or IMS DB) or application programs to directly access and change the same data while maintaining data integrity.; (4) The concurrent access of databases by two or more IMSs. The IMSs can be in one operating system image or in separate operating system images. They can share data at two levels: the database level and the block level. See also block-level sharing, database-level sharing.
�data-sharing component: The shared whiteboard or screen in an online meeting.
�data sharing group: (1) A collection of one or more DB2 for z/OS subsystems that directly access and change the same data while maintaining data integrity.; (2) In IMS, the components involved in sysplex data sharing. Among the components are the sharing IMS subsystems, the IRLMs they use, the IRLM, OSAM, and VSAM structures in the coupling facility, and a single set of DBRC RECONs.
�data sharing member: (1) A local or remote relational or nonrelational data manager that is capable of supporting data access using an ODBC driver that supports the ODBC APIs.; (2) In a federated system, typically a relational database management system (RDBMS) instance and one or more databases that are supported by that instance. A federated system can include other types of data sources, such as flat-file databases and table-structured files.; (3) A DB2 subsystem that is assigned by XCF services to a data sharing group.
�data skew: The uneven distribution of data values across logical or physical data storage media.
�data source: (1) A repository of data to which a federated server can connect and then retrieve data by using wrappers. A data source can contain relational databases, XML files, search algorithms, table-structured files, or other objects. In a federated system, data sources appear as a single collective database. See also foreign server.; (2) In JDBC, an interface that provides a logical representation of a pool of connections to a physical data source. Data source objects provide application portability by making it unnecessary to supply information specific to a particular database driver.; (3) The means by which an application accesses data from a database.
�data source object: In a federated system, an object at the data source on which operations can be performed. Examples include a database table, a database view, and a spreadsheet list. See also nickname.
�data source type: A grouping of data sources according to the protocol that is used to access the data.
�data space: A separate area of addressable storage that contains only data. A data space can hold up to 2 gigabytes of data. See also address space.
�data store: (1) A place (such as a database system, file, or directory) where data is stored.; (2) A data structure where documents are kept in their parsed form.
�data store profile: An object that defines properties used by the default data store plug-in, which is used to persistently store events received by the event server.
�data stream: The commands, control codes, data, or structured fields that are transmitted between an application program and a device such as printer or nonprogrammable display station.
�data striping: Storage process in which information is split into blocks (a fixed amount of data) and the blocks are written to (or read from) a series of disks in parallel.
�data structure: (1) An area of storage that defines the layout of the fields, called subfields, within the area. A data structure is program described.; (2) In Open Source Initiative (OSI), the syntactic structure of symbolic expressions and their storage allocation characteristics.
�data subclass: A user-defined data class that is used to designate more specifically the type of data. For example, in the Quantity class category, the subclass 01 might stand for a data field that holds information about currency. The 01 subclass category might mean 1 dollar in this context.
�data synchronization: The process by which a system ensures that data previously given to the system by an access method is written to some form of nonvolatile storage.
�data table: A file whose records are held in main storage.
�DataTAC: A technology for radio packet-data networks that was developed by Motorola.
�data terminal equipment (DTE): (1) In OSI, a physical node on a network.; (2) A device on a data link that sends and receives data, and provides data communications control functions according to protocols.; (3) A communications device that is the source or destination of signals on a network. It is typically a terminal or computer.
�data terminal ready: A signal to the modem used with the EIA 232 protocol.
�data token: In OSI, the token that controls which peer entity has permission to send on a half-duplex connection.
�data tower: In AFP Utilities, a set of Intelligent Printer Data Stream commands that represent a data type, such as text, image, graphics, and bar code.
�data traffic: In data communications, the quantity of data transmitted past a particular point in a path.
�data transfer rate: The average number of bits, characters, or blocks per unit time passing between corresponding equipment in a data transmission system. The rate is expressed in bits, characters, or blocks per second, minute, or hour. Corresponding equipment should be indicated; for example, modems, intermediate equipment, or source and sink.
�Data Transformation Framework (DTF): An infrastructure that includes data bindings and function selectors, which enables an adapter to convert native data formats to business objects and to convert business objects back to native data formats, such as XML.
�data transformation map: A set of mapping instructions that describes how to translate data from a source document into a target document. Both the source and target documents can be one of several supported document types. A data transformation map is one of three supported map types.
�data transparency: An attribute of a input message that causes ISC edit to route the message to its destination without examination or modification.
�data type: (1) In SQL, an attribute of columns, literals, host variables, special registers, parameters, and the results of functions and expressions.; (2) An attribute used for defining data as either numeric or character.; (3) In programming languages, a descriptor of a set of values together with a set of permitted operations. A data type determines the kind of value that a variable can assume or that a function can return.; (4) A category that identifies the mathematical qualities and internal representation of data and functions. See also type.; (5) In OSI, a category of data clearly defined using a data declaration method, such as ASN.1 or Pascal.
�data type mapping: The mapping of a data type to another data type across products or languages. For example, the Oracle type FLOAT maps to the DB2 type DOUBLE. See also forward data type mapping.
�Data Universal Numbering System (DUNS): A system in which internationally recognized nine-digit numbers are assigned and maintained by Dun & Bradstreet to uniquely identify worldwide businesses.
�data value: In Business Graphics Utility, a single, numeric data item entered as a value for a horizontal line or vertical line. See also data group.
�data warehouse: (1) A subject-oriented collection of data that is used to support strategic decision making. The warehouse is the central point of data integration for business intelligence. It is the source of data for data marts within an enterprise and delivers a common view of enterprise data.; (2) A central repository for all or significant parts of the data that an organization's business systems collect.
�Data Warehouse Center: The component of DB2 Universal Database that provides the graphical interface and the software behind it that enables you to work with the components of the warehouse. You can use the Data Warehouse Center to define and manage the warehouse data and the processes that create the data in the warehouse.
�data warehousing: A set of hardware and software components that can be used to analyze large amounts of data for making effective business decisions. For example, data warehousing can be used to analyze daily sales information, customer orders, products, inventory, and schedules.
�Data Window Services (DWS): Services provided as part of the Callable Services Library that allow manipulation of data objects such as VSAM linear data sets and temporary data objects known as TEMPSPACE.
�data word: In fibre-channel technology, a type of transmission word that occurs within frames. The frame header, data field, and cyclic redundancy check (CRC) all consist of data words. See also transmission word, frame, ordered set.
�date: A three-part value that designates a day, month, and year: for example, YYYY-MM-DD.
�date duration: A DECIMAL(8,0) value that represents a number of years, months, and days in the format yyyymmdd.
�datetime value: A value of the data type DATE, TIME, or TIMESTAMP.
�DAU: See direct access unmovable.
�DB: See database.
�dB: See decibel.
�DB2: A family of IBM licensed programs for relational database management.
�DB2 administration server: A control point that is used to assist with administration tasks on DB2 servers and to perform remote tasks on the server and the host system on behalf of a client request.
�DB2 Call Level Interface: See Call Level Interface.
�DB2 client: See IBM data server client.
�DB2 command: An instruction to the operating system to access and maintain the database manager. For example, DB2 commands allow a user to start or stop a database and to display information on current users and the status of databases.
�DB2 control server: A DB2 database system that contains the satellite control database, SATCTLDB. See also satellite.
�DB2 copy: One or more installations of DB2 database products in a particular location on a system. Multiple DB2 copies can be installed and run on the same system.
�DB2 copy name: The name that refers to a single instance of an installation of a DB2 database product, which is specified when the product is installed.
�DB2 Embedded Application Server: The application server middleware component that is provided with DB2 database products and licensed for use with Web applications that are supplied with DB2 database products. See also application server.
�DB2 for i5/OS: The integrated relational database manager on the system. It provides access to and protection for data. It also provides advanced functions such as referential integrity and parallel database processing.
�DB2 Geodetic Extender: A DB2 component that stores and manipulates spatial data using the round-Earth model that is a continuous, closed globe (unlike DB2 Spatial Extender, which treats the Earth as a flat map).
�DB2I: See DB2 Interactive.
�DB2 Interactive (DB2I): An interactive service within DB2 for z/OS that facilitates the execution of SQL statements, DB2 (operator) commands, and programmer commands and the invocation of utilities.
�DB2 Net Search Extender: A program that provides full-text retrieval through a DB2 procedure.
�DB2 notify log: See administration notification log.
�DB2 Query Manager (Query Manager): Part of the DB2 Query Manager and SQL Development Kit for i5/OS licensed program that is a collection of tools used to obtain information from the DB2 for i5/OS database. DB2 Query Manager can also be used to create query definitions, to run new or existing query definitions, or to format query information.
�DB2 Query Manager and SQL Development Kit for i5/OS: The IBM licensed program that is one of the DB2 family of products. Query Manager allows users to develop SQL queries and reports. The SQL Development Kit allows programmers to develop SQL applications.
�DB2 Spatial Extender: A DB2 component that stores and manipulates spatial data. DB2 Spatial Extender is used to generate and analyze spatial information about geographic features. See also geographic information system.
�DB2 Text Search: A component that can be optionally installed with DB2 Database for Linux, UNIX, and Windows that provides text search capabilities. DB2 Text Search works with SQL, XML, and XQuery.
�DB2 thread: The database manager structure that describes an application's connection, traces its progress, processes resource functions, and delimits its accessibility to the database manager resources and services. Most DB2 for z/OS functions execute under a thread structure.
�DB2 XML Extender: A program that is used to store and manage XML documents in DB2 tables. Well-formed and validated XML documents can be generated from existing relational data, stored as column data, and the content of XML elements and attributes can be stored in DB2 tables.
�DBA: See database administrator.
�DBAT: See database access thread.
�DBB: See database management batch.
�DBCLOB: See double-byte character large object.
�DBCS: See double-byte character set.
�DBCS code: The hexadecimal code, 2 bytes in length, that identifies a double-byte character.
�DBCS conversion: A function of the operating system that allows a display station user to enter alphanumeric data and request that the alphanumeric data be converted to double-byte data.
�DBCS conversion dictionary: A table used by the conversion function to map alphanumeric entries to double-byte entries. The system-recognized identifier for the object type is *IGCDCT.
�DBCS data: In DB2 for i5/OS, data that is associated with a double-byte character set.
�DBCS/EBCDIC mixed field: A field that contains both DBCS and EBCDIC data. The DBCS portions should always be enclosed with SO/SI control characters in both inbound and outbound data. In the case of inbound data, the control characters are automatically created by the terminal.
�DBCS-either: Pertaining to a character string that is either SBCS or bracketed DBCS, but not both. See also DBCS-graphic, DBCS-open, DBCS-only.
�DBCS font file: A system-supplied file that holds the 24x24 character images of one of the following groups of commonly used characters: 1) Japanese non-Kanji and basic-Kanji, 2) Korean non-Hangeul/non-Hanja, Hangeul, and a subset of Hanja, 3) Traditional Chinese non-Chinese and a subset of primary Chinese characters, or 4) all IBM-defined Simplified Chinese characters.
�DBCS font table: A system-supplied table that holds either 24x24 or 32x32 pel character images of a double-byte character set. A Japanese 24x24 DBCS font table holds Japanese extended Kanji and user-defined characters. A Korean 24x24 DBCS font table holds a subset of Hanja and user-defined characters. A Traditional Chinese 24x24 DBCS font table holds a subset of primary Traditional Chinese, all secondary Chinese, and user-defined characters. A Simplified Chinese 24x24 DBCS font table holds IBM-supplied Simplified Chinese characters as well as user-defined characters. A 32x32 DBCS font table holds 32x32 pel character images of a double-byte character set, including its user-defined characters. The system-recognized identifier for the object type is *IGCTBL.
�DBCS-graphic: Pertaining to a character string in which each character is represented by 2 bytes. Used only with the EBCDIC encoding scheme. The character string does not contain shift-out (SO) and shift-in (SI) characters. See also DBCS-either, DBCS-open, DBCS-only.
�DBCS number: The decimal value, 5 digits in length, that identifies a double-byte character.
�DBCS-only: Pertaining to a character string that is only bracketed DBCS. See also DBCS-either, DBCS-graphic, DBCS-open, graphic data type.
�DBCS-open: Pertaining to a character string that can be a mixture of SBCS and bracketed DBCS. See also DBCS-either, DBCS-graphic, DBCS-only.
�DBCS sort table: A system-supplied object that contains sequencing information to sort double-byte characters. The system-recognized identifier for the object type is *IGCSRT.

�DBCTL: See Database Control.
�DBD: (1) See database descriptor.; (2) See database description.
�DB/DC: See database/data communication.
�DBDGEN: See database description generation.
�DBDS: See database data set.
�DBDTL environment: See database control environment.
�DBID: See database identifier.
�DBIID: See database instance ID.
�D-bit: See delivery-confirmation bit.
�DB monitor: See database monitor.
�DBMS: See database management system.
�DBO: See DL/I backout table.
�DB PCB: See database program communication block.
�DBRC: See Database Recovery Control.
�DBRC group: In IMS Version 10, one or more DBRC instances that share a single RECON data set in an IMSplex environment. Each DBRC group has a group identifier (GROUP ID), which is unique for that group. DBRC groups are used by DBRC, whether or not parallel RECON access is enabled.
�DBRC request: An action (command process, query, and update) that is asked of DBRC by IMS, DBRC application programs, and jobs.
�DBRM: See database request module.
�DBT: IMS System Utilities/Database Tools
�DBU: See delete-if-backed-up.
�DC: See data chaining.
�DCA: See Document Content Architecture.
�DCB: See data control block.
�DCBU: See D-channel backup.
�DCC: See data country code.
�DCCTL: See Data Communications Control.
�DCDB: See domain control database.
�DCE: (1) See Distributed Computing Environment.; (2) See data communication equipment.; (3) See data circuit-terminating equipment.
�DCEM: See Distributed Command Execution Manager.
�DCE principal: A user ID that uses the distributed computing environment.
�DCF: (1) See Document Composition Facility.; (2) See data center fragment.
�D-channel: See delta channel.
�D-channel backup (DCBU): An ISDN NFAS configuration where two of the T1 facilities have a D-channel, one of which is used for signaling, and the other as a backup in case the other fails. See also non-facility-associated signaling.
�DCI: See data-conversion interface.
�DCLCB: See declare control block.
�DCLGEN: See declarations generator.
�DCM: (1) See Digital Certificate Manager.; (2) See dynamic cache management.; (3) See data center model.
�DCOM: See distributed component object model.
�DC-PCB: See data communication program communication block.
�DCR: See data connection resource.
�DCS directory: See Database Connection Services directory.
�DCSS: See discontiguous shared segment.
�DCT: (1) See destination control table.; (2) See device characteristics table.; (3) See Digital Cordless Telephone.
�DCU: See data cache unit.
�DD: (1) See data definition.; (2) See device driver.
�DDE: See dynamic data exchange.
�DDE client: The computer, or an application running on it, that provides the function of receiving dynamic data exchange (DDE) data from another DDE-enabled application.
�DDE server: The computer, or an application running on it, that provides dynamic data exchange (DDE) data to another DDE-enabled application. In VisualAge RPG, all components provide DDE server functions.
�DDF: See distributed data facility.
�DDI: (1) See distributed data interface.; (2) See direct dial in.
�DDIR: See DL/I database directory.
�DDL: See Data Definition Language.
�DDM: (1) See distributed data management.; (2) See disk drive module.
�DDM Architecture: See Distributed Data Management Architecture.
�DDM file: A system object with type *FILE, created by a user on the local (source) system, that identifies a data file that is kept on a remote (target) system. The DDM file provides the information needed for a local system to locate a remote system and to access the data in the remote data file.
�DDMMYYYY: Day-day-month-month-year-year format of a date (for example, 14022001 for 14 February 2001). This is the default format for the DATFORM system initialization parameter.
�DDN: See Defense Data Network.
�ddname: See data definition name.
�DDO: See dynamic data object.
�DDP: See Datagram Delivery Protocol.
�DDR: See dynamic device reconfiguration.
�DDS: (1) See data description specifications.; (2) See Dataphone digital service.
�DDS1: See Digital Subscriber signaling System Number 1.
�DDSA: See digital data service adapter.
�DD statement: See data definition statement.
�DEA: See Data Encryption Algorithm.
�deactivate: To take a resource of a node out of service, rendering it inoperable, or to place it in a state in which it cannot perform the functions for which it was designed. Contrast with activate
�dead code: Code that is never referenced, or that is always branched over.
�dead key: See nonescaping key.
�dead-letter queue: A queue to which a queue manager or application sends messages that cannot be delivered to their correct destination.
�dead-letter queue handler: A WebSphere MQ-supplied utility that monitors a dead-letter queue (DLQ) and processes messages on the queue in accordance with a user-written rules table.
�deadline scheduling: A method of scheduling jobs by time of day, or by week, month, or year.
�deadlock: (1) A condition under which a transaction cannot proceed because it is dependent on exclusive resources that are locked by another transaction, which in turn is dependent on exclusive resources in use by the original transaction.; (2) Unresolved contention for the use of resources.; (3) A condition in which two independent threads of control are blocked, each waiting for the other to take some action. Deadlock often arises from adding synchronization mechanisms to avoid race conditions.
�deadlock detector: A process within the database manager that monitors the states of the locks to determine whether a deadlock condition exists. When a deadlock condition is detected, the detector stops one of the transactions involved in the deadlock. This transaction is rolled back, and the other transaction can proceed.
�deadman switch timer: A kernel timer that works on a node that has lost its disk lease and has outstanding I/O requests. By causing the kernel to panic, this timer ensures that the affected node cannot complete the outstanding I/O requests. If the node were able to complete outstanding I/O requests without a disk lease, file system corruption could result.
�dead store: A store into a memory location that will later be overwritten by another store without any intervening loads. In this case, the earlier store can be deleted.
�deallocate: To release a resource that is assigned to a specific task.
�debit cap: A limit for debit payments. MERVA Liquidity Manager holds all debit payments until there is sufficient liquidity available to cover them.
�debit payment: A payment that debits the bank's account. It can be sent as an outgoing message to another bank, received as an in-house message, or received as a debit confirmation.
�deblocking: The process of removing each logical record from a block. See also blocking.
�debug: To detect, diagnose, and eliminate errors in programs.
�debug engine: The server component of the debugger, whose client/server design enables both local and remote debugging. The debug engine runs on the same system as the program being debugged.
�debugger: A tool used to detect and trace errors in computer programs.
�debugging line: (1) A COBOL statement run only when the WITH DEBUGGING MODE clause is specified. Debugging lines can help determine the cause of an error.; (2) In COBOL, any line with a D in the indicator area of the line.
�debugging section: In COBOL, a declaratives section that receives control when an identifier, file name, or procedure name is encountered in the Procedure Division.
�debugging session: The debugging activities that occur between the time that a developer starts a debugger and the time that the developer exits from it.
�debug mode: (1) A mode in which a program provides detailed output about its activities to aid a user in detecting and correcting errors in the program itself or in the configuration of the program or system.; (2) An environment in which programs can be tested.; (3) In DFSMShsm, the method of operation that projects the changes that would occur in normal operation but in which no user data is moved.
�decapsulation: In communication, a technique used by layered protocols in which a protocol receives a protocol data unit and removes its header to recover its control information. The protocol uses control information in the header to enable it to deliver the data in the protocol data unit (PDU) to the appropriate upper-layer protocol. See also encapsulation.
�decibel (dB): A unit of signal strength or loudness, such as the signal on a data communications channel.
�decimal: Pertaining to a system of numbers to the base 10. The decimal digits range from 0 through 9.
�decimal constant: A numerical data type used in standard arithmetic operations. Decimal constants can contain any digits 0 through 9. See also integer constant.
�decimal floating-point number: A 64-bit or 128-bit representation of a number with a precision of 16 or 34 decimal digits and an exponent. Decimal floating-point numbers include normal numbers, subnormal numbers, and the special values of infinity, NaN, and sNaN. In IBM SQL, decimal floating-point numbers are not considered to be floating-point numbers. See also not-a-number, infinity, signaling NaN, subnormal number, normal number, floating-point number.
�decimalization table: In Cryptographic Support, a table of 16 decimal characters that is used to convert a hexadecimal value to a decimal value. Each hexadecimal digit is used as an offset in the (decimalization) table and is replaced with the value found there.
�decimal notation: In an EDI Standard, the character that represents a decimal point.
�decimal overflow: A condition that occurs when one or more nonzero digits are lost because the destination field in a decimal operation is too short to contain the results.
�decimal position: (1) The location of the decimal point in a series of numbers.; (2) Numbers to the right of the decimal point. For example, 4.009 has three decimal positions.
�decipher: To convert enciphered data in order to restore the original data.
�decision: (1) A specific location on an activity diagram or state chart diagram where the workflow may branch based upon guard conditions. See also business value.; (2) A process element that routes an input to one of several alternative outgoing paths, depending on its condition. A decision is like a question that determines the exact set of activities during the execution of a process. Questions might include: What type of order? Or How will the order be shipped?; (3) The component of a policy expression that indicates the specific behavior or property that the policy affects. Types of decisions include actions, goals, results, and configurations. See also decision name.
�decision federator (DF): See policy editor storage.
�decision input: In a policy-enabled system, a data value (along with its name and type) or sensor value that the managed resource provides to the autonomic manager and that the autonomic manager uses when making a decision.
�decision name: An attribute that identifies a specific decision of a result-based policy or a configuration-profile-based policy that is used for solicited decision requests. All policies in a policy set have the same decision name and use the same collection of names and types of result values, which are returned by the autonomic manager during policy evaluation. See also decision, policy set.
�decision output: In Policy Management for Autonomic Computing, the data value (along with its name and type) in a result-based policy or a configuration-profile-based policy that is used for solicited decision requests. A decision output is the data value that is returned by the autonomic manager that represents the decision in the policy.
�decision point: A part of a program in a policy-enabled system that requests and accepts solicited decisions from an autonomic manager. A managed resource contains one or more decision points, which provide policy support for the managed resource. See also autonomic control loop.
�decision point pattern: A set of interfaces that are linked and that provide developers with a framework for implementing policy-based management in their applications. Each decision point pattern identifies where decision points are needed in the application to implement the operational flow. Policy Management for Autonomic Computing provides three decision point patters: an auditor pattern, which checks compliance with a specific set of policies; a planner pattern, which uses policies to design or configure a new system; and a virtualization pattern, which provides a virtualized interface to a physical system.
�decision table: A form of business rule that captures multi-conditional decision-making business logic in a table where the rows and columns intersect to determine the appropriate action. Unlike a rule set, a decision table uses more than one condition to determine the action. See also rule set.
�deck: An XML document that contains a collection of WML cards. See also card.
�declaration: (1) In the C and C++ languages, a description that makes an external object or function available to a function or a block statement.; (2) A statement that establishes the names and characteristics of data objects and functions used in a program.; (3) In Java programming, a statement that establishes an identifier and associates attributes with it, without necessarily reserving its storage or providing the implementation. (Sun)
�declarations generator (DCLGEN): A subcomponent of DB2 for z/OS that generates SQL table declarations and COBOL, C, or PL/I data structure declarations that conform to the table. The declarations are generated from DB2 system catalog information.
�declaratives: In COBOL, a set of one or more special-purpose sections, at the beginning of the Procedure Division that can be used for error checking or debugging.
�declarative security: The security configuration of an application during assembly stage that is defined in the deployment descriptors and enforced by the security run time.
�declarative sentence: In COBOL, a compiler-directing statement that specifies when a debugging section or an exception/error procedure is to be run.
�declarator: An identifier and optional symbols that declare a single function, object or data type within a declaration. See also function declarator.
�declare control block (DCLCB): A control block containing file information.
�declared temporary table: A table that holds temporary data and is defined with the SQL statement DECLARE GLOBAL TEMPORARY TABLE. Information about declared temporary tables is not stored in the DB2 catalog, so this kind of table is not persistent and can only be used by the application process that issued the DECLARE statement. See also base table, temporary table, created temporary table.
�DECnet: A network architecture that defines the operation of a family of software modules, databases, and hardware components typically used to tie Digital Equipment Corporation systems together for resource sharing, distributed computation, or remote system configuration. DECnet network implementations follow the Digital Network Architecture (DNA) model.
�decode: To convert data by reversing the effect of some previous encoding.
�decomposition: (1) The process of breaking up an XML document for storage in database tables.; (2) The separation of a compound word into its constituents (or formation elements). Internally this consists of three distinct steps: segmentation, normalization, and annotation.
�decompound: To decompose a word or a multiword unit into its constituent parts.
�decompression: (1) A function that exchanges control characters for actual data.; (2) A function that expands data to the length that precedes data compression.; (3) Process of restoring compressed data to its original state, so that it can be used again.
�decoration: In graphical user interfaces (GUIs), a glyph that annotates a resource with status information, for example to indicate that a file has changed since it was last saved or checked out of a repository.
�decrypt: (1) In Cryptographic Support, to convert ciphertext into plaintext. See also encrypt.; (2) To decipher data.
�decryption: (1) In computer security, the process of transforming encoded text or ciphertext into plaintext.; (2) The process of decoding data that has been encrypted into a secret format. Decryption requires a secret key or password.
�DECT: See Digital European Cordless Telecommunications.
�DEDB: See data entry database.
�dedicated: Pertaining to the assignment of a system resource (such as a device, a program, or an entire system) to an application or purpose.
�dedicated line: A connection not requiring dialing to establish communication.
�dedicated save operation: An operation that the user runs to save objects when no other jobs are running. See also save-while-active operation.
�Dedicated Server for Domino (DSD): A System i server that is specially designed to run Lotus Domino servers and applications.
�dedicated service tools (DST): (1) The part of the service function used to service the system when the operating system is not running.; (2) Service functions that are available only from the console and can run when the operating system is not available, as well as when the operating system is available.
�dedicated storage: Storage within a storage facility that is configured such that a single host system has exclusive access to the storage.
�dedicated system: A system intentionally reserved for a single job or task.
�de-editing: In COBOL, the logical removal of all editing characters from a numeric edited data item to determine the unedited numeric value of the item.
�de-envelope: To extract a document from an EDI envelope.
�deep computing: Ultrafast computing that is combined with sophisticated analytical software to enable organizations to analyze, find patterns in, and take action on the data that they have gathered.
�default: Pertaining to an attribute, value, or option that is assumed when none is explicitly specified.
�default access control list (default ACL): A template used to generate access control lists (ACLs) for the files within a directory. A default ACL is not used to verify permissions.
�default ACL: See default access control list.
�default agent site: An agent site that is located on the same system as the control server. A remote agent site does not require the installation of IBM DB2 Warehouse Manager Standard Edition. See also agent site, remote agent site.
�default argument: An argument that is declared with default values in a C++ function prototype or declaration. If a call to the function omits this argument, a default value is used. An arguments with a default value must be the trailing argument in a function prototype argument list.
�default class: A class with preprogrammed definitions that can be used for simple implementations.
�default clause: In the C or C++ languages, within a switch statement, the keyword default followed by a colon, and one or more statements. When the conditions of the specified case labels in the switch statement do not hold, the default clause is chosen.
�default configuration: In OSI, the set of default configuration and initialization values supplied with OSI Communications Subsystem. The user can change the default configuration, which is provided by initial records supplied in the subsystem information base shipped with OSI Communications Subsystem.
�default connection: The connection on which HATS transforms and presents host application screens to the user. See also background connection, connection.
�default constructor: A C++ constructor that takes no arguments, or if it takes any arguments, all its arguments have default values.
�default contract: In WebSphere Commerce, an agreement representing the terms and conditions that apply to all transactions. A default contract is required for all stores.
�default database client interface copy: See default IBM database client interface copy.
�default DB2 copy: The DB2 copy that is used by applications that access DB2 database products through the default interface. Multiple DB2 copies can be installed and run on the same system.
�default delivery: The method of delivering messages to a message queue without interrupting the job, and sending the system-assigned reply for any messages requiring a reply. Messages are placed on the message queue only if the message queue is QSYSOPR; otherwise, the messages are discarded by the system. For messages requiring a reply, replies are sent before the messages are discarded.
�default device geometry: A part of the storage management subsystem (SMS) base configuration that identifies the number of bytes per track and the number of tracks per cylinder for the purpose of converting space requests made in tracks or cylinders into bytes. Default device geometry is used when no unit name has been specified.
�default directory: The directory name supplied by the operating system if none is specified.
�default entry point: An entry point in a user's program that receives control from the operating system when a user runs an application.
�default error handler: The part of the RPG logic cycle that handles program or file exceptions/errors when program or file exceptions/errors are not controlled by the programmer.
�default focal point: (1) In SNA, a network node that receives alerts from nodes that do not have defined focal points. See also primary focal point.; (2) A focal point that provides management services support for those nodes that have not been assigned a focal point. The set of nodes in the sphere of control (SOC) of a default focal point is not defined at either the focal point itself or the SOC nodes. A default focal point exchanges management services capabilities with all network nodes known to it; only those nodes that have not established a relationship with another focal point accept the request.
�default form: (1) A temporary object that contains the description of the format of a printed or displayed report, which was built without explicitly specifying a form to be applied against it.; (2) A form that is created when a query is run. The default form is not created if a saved form is run with the query.
�default group: In RACF, the group specified in a user profile that is the default current connect group.
�default IBM database client interface copy (default database client interface copy): The copy that applications requiring the use of the IBM Data Server Driver for ODBC and CLI and the IBM Data Server Provider for .NET use by default.
�default initialization: The initial value assigned to a data object by the compiler if no initial value is specified by the programmer. In C language, external and static variables receive a default initialization of zero, while the default initialization for auto and register variables is undefined.
�default interface: An interface with a well-known name that applications specify when using DB2 databases.
�default literal: In MFS, a literal field that MFS inserts into an input message when no data for the field is received from the terminal. See also explicit literal, literal field, system literal.
�default management class: A part of the storage management subsystem (SMS) base configuration that identifies the management class for system-managed data sets that do not have a management class assigned.
�default namespace: The namespace that is applied if an XML element, type, or function has no namespace prefix. If the URI reference in a default namespace declaration is empty, unprefixed elements in the scope of the declaration are not considered to be in any namespace.
�default network message queue: A message queue to which messages related to network activity are sent when either the user profile does not have a message queue specified or the message queue named in the user profile cannot be used.
�default network output queue: An output queue to which spooled files are sent when either the user does not have an output queue specified or the output queue name in the user profile cannot be used.
�default object: A definition of an object (for example, a queue) with all attributes defined. If a user defines an object but does not specify all possible attributes for that object, the queue manager uses default attributes in place of any that were not specified.
�default organization: The organizational entity that is used when a user registers and does not identify an organizational entity. In addition, guest users are created under the default organization.
�default password: A password that is the same as the service tools user ID. For example, the IBM-supplied QSECOFR service tools user ID is shipped with a default password of QSECOFR.
�default policy: In a Tivoli environment, a set of resource property values that are assigned to a resource when the resource is created. See also validation policy.
�default portal page: The page that displays to a user at initial portal deployment and before the user completes enrollment. Sometimes used as a synonym for home page.
�default printer: A printer that is assigned to a system or user and accepts all the printed output from that system or user, if no other printer is specified.
�default profile: The profile that is assigned ownership of an object if the original owning profile is deleted or damaged.
�default program: A user-specified program that is assumed when no other program is specifically named on a debug command, or a user-defined program for handling error messages.
�default public place: A place whose membership automatically includes all portal users and which appears in the Places selector for every user. A user is always a member of this place.
�default record: A record that consists entirely of default values (numeric fields are filled with zeros; character fields are filled with blanks; and fields of either data type (numeric or character) can be filled with a value specified by the user with the DFT keyword in DDS).
�default rendering: The method used by HATS to render parts of the host screen for which no specific transformation is specified.
�default reply: A system-assigned reply to an inquiry or notify message, which is used when the message queue at which the message arrives is in default delivery mode.
�default routing entry: In SNADS, the routing table entry specifying the route to be used when the table contains no explicit routing entry.
�default ruling: For a failed conformance check, a setting that defines the default course of action. The default ruling is set to either "deny," which causes the conformance check to fail regardless of the conformance check results of other governing privacy policies, or to "defer," which indicates that the conformance check failed, but the final result of the compliance check depends on the classification of each governing privacy policy and on the result of the conformance check against each governing privacy policy. See also ruling, compliance check, conformance check.
�default subsystem name (DSN): The name of the DB2 subsystem that can connect to the control server (the default subsystem name is DSN).
�default system control area (DSCA): In MFS, part of the device output format (DOF) that causes specific terminal functions to be performed if the destination terminal has the required features. See also system control area.
�default terminal security: The basic system security that prohibits the entry of certain commands from any terminal other than the master terminal.
�default unit: A part of the storage management subsystem (SMS) base configuration that identifies an esoteric (such as SYSDA) or generic (such as 3390) device name. If a user omits the UNIT parameter in the job control language (JCL) or the dynamic allocation equivalent, SMS applies the default unit if the data set has a disposition of MOD or NEW and is not system-managed.
�default user: The user whose security attributes are used to protect CICS resources in the absence of other, more specific, user identification. For example, except in the case of terminals defined with preset security, the security attributes of the default user are assigned to terminal users who do not sign on.
�default user ID: The user identifier (user ID) of the default user. The default user ID is specified with the DFLTUSER system initialization parameter.
�default user name: A system-provided name for a user identification for a computer system that does not want to require separate user identifications.
�default user pool: A storage pool that stores file data that SAN File System has not assigned (using the active policy set) to a user pool. There is only one default user pool; however, you can assign any user storage pool as the default pool. See also user pool.
�default value: (1) A predetermined value, attribute, or option that is assumed when no other value is specified. A default value can be defined for column data in DB2 tables by specifying the DEFAULT keyword in an SQL statement that changes data (such as INSERT, UPDATE, and MERGE).; (2) A value that is automatically assigned.
�default value formula: The formula that lets users set an initial value for an editable field.
�default view: (1) In XML Extender, a representation of data in which an XML table and all of its related side tables are joined.; (2) The view displayed the first time a user opens a Notes database.
�defect: A type of change request that identifies an anomaly or flaw in a work product. See also change request.
�Defense Advanced Research Projects Agency (DARPA): The United States Department of Defense agency responsible for creating ARPANET, a large TCP/IP network.
�Defense Data Network (DDN): The MILNET, ARPANET, and TCP/IP networks and protocols.
�deferred connection: A pending event that is activated when a CICS subsystem tries to connect to WebSphere MQ for z/OS before it has started.
�deferred embedded SQL: In DB2 for z/OS, SQL statements that are neither fully static nor fully dynamic. Like static statements, they are embedded within an application, but like dynamic statements, they are prepared during the execution of an application. See also dynamic SQL, static SQL, incremental bind statement.
�deferred flow: A flow whose recovery was deferred
�deferred index cleanup rollout: A rollout in which index cleanup is performed after the deletion of the portion of the MDC table is complete. Deferred index cleanup rollout is significantly faster than immediate index cleanup rollout, but rolled-out blocks are not available for immediate reuse. See also rollout.
�deferred maintenance: The process of waiting until the system can be powered down to repair or replace a failed disk-related hardware component.
�deferred printing mode: A printing mode that spools output through JES to a data set instead of printing it immediately. Output is controlled using job control language (JCL) statements. See also direct printing mode.
�deferred restart: A restart performed by the system when a user resubmits a job. The operator submits the restart deck to the system through a system input reader. See also automatic restart, checkpoint restart.
�deferred update: A Fast Path capability that keeps updates to databases in main storage buffers until a synchronization point is reached. Synchronization point processing schedules the VSAM writes and response messages to terminals after physically logging the changed data.
�deferred work element (DWE): (1) The catalyst used to call event-driven services controlled within CICS. A DWE causes a unit of work to be scheduled later, normally at the end of the task or just before or after syncpoint.; (2) A work element created and placed on a chain (the DWE chain) to save information about an event that must be completed before task termination but that is not completed at the present time. DWEs are also used to save information about work to be backed out in case of an abend.
�deferred write: The process of asynchronously writing changed data pages to disk.
�defined address: A named set of a) Internet Protocol (IP) addresses, or b) interface names and point-to-point profiles. This set is classified as trusted, untrusted, or border.
�defined user ID: See defined user identifier.
�defined user identifier (defined user ID): A user identifier (user ID) named on a DEFINE PROCESS or DEFINE ACTIVITY command. It specifies the user ID under whose authority the process or activity will be run, if it is activated by a RUN command.
�defined zone configuration: The complete set of all zone objects that are defined in the fabric. The defined zone configuration can include multiple zone configurations. See also enabled zone configuration, zone configuration.
�define the file (DTF): The DTF is a DAM control block that identifies to DAM the file associated with this DAM request. It is passed to DAM by DFHFCD to initiate a DAM request, and lasts for the lifetime of the CICS run. The DTF is included in the associated FCT entry, and is generated at FCT assembly time by the DTFDA macro. There is one DTF per DAM FCT entry.
�defining attribute: A property of an item in an online store such as its color or size. Defining attributes are used for SKU resolution. See also attribute value, item, descriptive attribute.
�defining model: The model on which a repository is based. Any number of repositories can have the same defining model.
�definite response (DR): In SNA, a value in the response-requested field of the request header that directs the receiver of the request to return a response unconditionally, whether positive or negative, to that request. See also exception response, no response.
�definite response 1 indicator (DR1I): A single bit in an SNA frame that signals whether a definite response 1 is requested.
�definite response 2 indicator (DR2I): A single bit in an SNA frame that signals whether a definite response 2 is requested.
�definition: A declaration that reserves storage and can provide an initial value for a data object or define a function.
�definition file: Defines the content that is displayed within the navigation and workarea frames.
�definitions file: In EGL, a file that is in EGL source format and that contains any number of function and data parts. The file may import other definitions files. The file name extension is .egldef.
�definition specification: In RPG, a specification used for data definitions. This specification includes defining the following: data structures, data-structure subfields, named constants, arrays, and stand-alone fields.
�definitive software library (DSL): A location where all quality controlled versions of all software configuration items (CIs) are held in their definitive form, together with any associated CIs such as license and other documentation.
�defragmentation: The process of running a software utility to rewrite fragmented data to contiguous sectors of a computer storage medium to improve access and retrieval time. See also fragmentation.
�degraded: Pertaining to a mode of operation that has suffered a failure, but continues to function.
�degree: The number of children of a node.
�degree of parallelism: The number of concurrently executed operations that are initiated to process a query.
�delay characteristic: The average amount of time required for an operation (such as call setup, call clearing, data transfer, and so forth) to be performed on a packet-switching network.
�delay compensation: In CCP, a responding arrangement by which the IBM 3710 Network Controller answers for a receiving station.
�delayed maintenance: A method of logging changes to an access path for database files and applying the changes the next time the file is opened instead of rebuilding the access path completely or maintaining it immediately. See also immediate maintenance, rebuild maintenance.
�delay start: A procedure used with some channel associated signaling protocols to indicate when a switch or PABX is ready to accept address signaling. After seizure, the switch sends off-hook until it's ready to accept address signaling, at which time it sends on-hook. See also immediate start, wink start.
�delegate: A user who is authorized to work for another user.
�delegation: (1) The act of giving other users or groups the authority to perform operations.; (2) The process of propagating a security identity from a caller to a called object. According to the Java Platform, Enterprise Edition (Java EE) specification, a servlet and an enterprise bean can propagate either the client identity when invoking enterprise beans, or can use another specified identity as indicated in the corresponding deployment descriptor.
�delete authority: A data authority that allows the user to remove entries from an object; for example, delete messages from a message queue or delete records from a file. See also add authority.
�delete-by-age: In DFSMShsm, the space management technique of deleting data sets, not managed by the storage management subsystem (SMS), that have not been opened for a specified number of days.
�delete-connected: In SQL, a property of a table that is a dependent of table P or a dependent of a table to which delete operations from table P cascade.
�delete hole: A row in the result of a SELECT statement of a cursor that no longer has a corresponding row in the base table because that row was deleted. The row for the SELECT statement is no longer accessible though the cursor. See also update hole, update hole.
�delete-if-backed-up (DBU): In DFSMShsm, the space management technique of deleting data sets, not managed by the storage management subsystem (SMS), that have not been opened for a specified number of days and that have a current backup version. See also data set retirement.
�delete lock: Lock acquired by CICS file control whenever a DELETE, WRITE, or WRITE MASSINSERT operation is being performed for a recoverable VSAM KSDS or a recoverable path over a KSDS.
�delete rule: A rule associated with a referential constraint that either restricts the deletion of a parent row or specifies the effect of such a deletion on the dependent rows.
�delete trigger: A trigger that is activated by a delete operation on the table or view that is specified in the trigger definition. See also insert trigger, trigger, instead of trigger, update trigger.
�deletion stub: A truncated document that is left in a Notes database in place of the original document to indicate to the Replication task that the document should, in fact, be deleted from all other replicas.
�delimited identifier: A sequence of one or more characters enclosed by quotation marks (").
�delimited scope statement: In COBOL, any statement that includes its explicit scope terminator.
�delimited text: A simple file format that consists of text separated into meaningful chunks by specific characters. The chunks of text are usually individual fields. The specific character is called a delimiter, and can be any character that is not found in the text. Comma and tab are common delimiters. If the delimiter is used as a character in the text, it must be enclosed by a pair of text qualifiers, usually double quotation marks.
�delimiter: (1) A flag that is formed by a character or a sequence of characters to group or separate items of data by marking the beginning and end of a unit of data. The delimiter is not a part of the flagged unit of data.; (2) A character, such as comma or tab, used to group or separate units of text by marking the boundary between them.
�delimiter token: A string constant, a delimited identifier, an operator symbol, or any of the special characters shown in syntax diagrams.
�deliverable: An output from a process that has a value, material or otherwise, to a customer or other stakeholder.
�delivery-confirmation bit (D-bit): In X.25 communications, the bit in a data packet or call-request packet that is set to 1 if end-to-end acknowledgment (delivery confirmation) is required from the recipient.
�delivery operation: A ClearCase operation in which developers merge the work from their own development streams to the project's integration stream or to a feature-specific development stream. If required, the deliver operation invokes the Merge Manager to merge versions.
�delta backup: A copy of all database data that has changed since the last successful backup (full, incremental, or delta) of the table space in question. A delta backup is also known as a differential, or noncumulative, backup image. The predecessor of a delta backup image is the most recent successful backup that contains a copy of each of the table spaces in the delta backup image.
�delta business object: A business object used in an update operation. Such a business object contains only key values and the values to be changed. See also after-image.
�delta channel (D-channel): In ISDN, a common channel used for signaling and management of the network. In a basic rate interface, the D-channel operates at 16 kilobits per second. In a primary rate interface, the D-channel operates at 64 kilobits per second. See also bearer channel.
�delta deployment: Deployment of only that data that is required to transform a current runtime environment into a target runtime environment.
�delta index build: In an enterprise search system, the process of adding new information to an existing index. See also main index build.
�delta install: The process of creating the software package that contains only the delta between the base software package and the software package to be installed. See also byte-level differencing.
�demand-activated logical link: A logical link that can be activated by APPN configuration services when needed without requiring operator intervention.
�demand chain: A demand chain is a value chain that supports both direct sales channels and indirect sales channels. The Commerce Plaza sample site is an example of an indirect sales channel demand chain. See also supply chain, value chain business model.
�demand poll: A polling operation initiated by the user.
�demand select job: A job created by MVS and passed to JES3 for processing.
�demangling: The conversion of mangled C++ names back to their original source code names to make program debugging easier. See also mangling.
�demarshal: To deconstruct an object so that it can be written as a stream of bytes.
�demilitarized zone (DMZ): A configuration including multiple firewalls to add layers of protection between a corporate intranet and a public network, like the Internet.
�demodulate: To return the frequency of a signal to its original level.
�demonstration certificate: A digital certificate issued exclusively for demonstration and test purposes. The private key for a demonstration certificate is commonly available.
�demote: To remove a logical data unit from cache memory. A storage server demotes a data unit to create space for other logical data units in the cache or because the logical data unit is not valid. The ESS must destage logical data units with active write units before they can be demoted.
�demotion: The process of one host losing level functions to another. Both original and promoted hosts can be demoted. See also promotion, level function.
�denial-of-service attack: In computer security, an assault on a network that brings down one or more hosts on a network such that the host is unable to perform its functions properly. Network service is interrupted for some period.
�denormalization: The intentional duplication of columns in multiple tables to increase data redundancy. Denormalization is sometimes used to improve performance. See also normalization.
�dense wavelength division multiplexing (DWDM): A technology that places many optical signals onto one single-mode fiber using slightly different optical frequencies. DWDM enables many data streams to be transferred in parallel.
�dependency: (1) A requirement that one managed resource has on another managed resource in order to operate correctly.; (2) A link between projects, tasks, deliverables or requirements. Items with these links depend on start and finish dates of at least one other element and therefore cannot be completed without taking the other into consideration.
�dependency checker: The deployment management component that validates whether or not dependencies are met before installing artifacts in a hosting environment.
�dependency criticality: The manner in which a dependency is satisfied, based on the availability of the resources or services that a component depends upon.
�dependency management: The management discipline that defines standard formats for describing potential capabilities and dependencies.
�dependency relationship: In UML modeling, a relationship in which changes to one model element (the supplier) impact another model element (the client). See also realizes relationship, abstraction relationship, binding relationship, substitution relationship, usage relationship.
�dependent: In SQL, an object (row, table, or table space) that has at least one parent. See also parent table space.
�dependent default: Attribute value for RDO that differs depending on the values for the other attributes that have already been specified on the command line.
�dependent file: The file in a constraint relationship that contains the foreign key. See also parent file.
�dependent foreign key table: A foreign key table that is a dependent in at least one referential constraint. See also parent table, descendent foreign key table.
�dependent immediate materialized query table: A table whose definition is based on the result of a query and whose data is in the form of precomputed results. These results come from the tables or nicknames that are used in the definition of the materialized query table.
�dependent job control (DJC): A method of handling multiple jobs that must be run in a specific order because of job dependencies. DJC manages jobs that are dependent upon one another.
�dependent job control network (DJC network): A set of jobs that JES3 must run in a predetermined order. Success or failure of one job can result in execution, holding, or cancellation of other jobs.
�dependent logical unit (DLU): A logical unit that requires assistance from a system services control point (SSCP) to instantiate an LU-to-LU session. See also independent logical unit.
�dependent logical unit requester (DLUR): An advanced program-to-program communications (APPC) application that allows dependent secondary logical units (LU 0, 1, 2, and 3) an entry point into the Advanced Peer-to-Peer Networking (APPN) network. DLUR support gives the appearance of having an adjacent connection to VTAM, but allows traversing the APPN network through intermediate nodes.
�dependent logical unit server (DLUS): An APPN network node that provides SSCP services for dependent logical units (DLUs) owned by dependent LU requesters (DLURs) located elsewhere in an APPN network.
�dependent materialized query table: A materialized query table that is dependent on a given table.
�dependent region: (1) An address space, managed by the IMS control region, where IMS application programs run. Dependent region types are MPP, BMP, IFP, JMP, and JBP.; (2) In a multi-MVS or VSE MRO XRF configuration, a region that receives commands from a master or coordinator region at takeover time. It cannot initiate a takeover.
�dependent row: A row that contains a foreign key that matches the value of a parent key in the parent row. The foreign key value represents a reference from the dependent row to the parent row. See also parent row.
�dependent segment: In a database, a segment that relies on a higher-level segment for its full hierarchic meaning. A child is a dependent segment of its parent. See also root segment.
�dependent service element (DSE): An element of the active IMS system that has a counterpart in the alternate IMS system, but cannot trigger a takeover on its own. z/OS, VTAM, IRLM, and the CPC are DSEs. A DSE depends on IMS to recognize a failure in its processing and request that the alternate take over its operation.
�dependent staging table: The staging table for a dependent materialized query table of a given table.
�dependent table: A table that is a dependent of an object. For example, a table with a foreign key is a dependent of the table containing the corresponding primary key. See also descendent table, parent table.
�dependent write: An application write that depends upon the completion of a previous application I/O operation.
�dependent write operation: A write operations that must be applied in the correct order to maintain cross-volume consistency.
�depletable resource: A resource that can be reduced in number and quantity; that is, materials such as pencils, paper, and chalk. See also resource, finite resource.
�deploy: (1) To place files or install software into an operational environment. In Java Platform, Enterprise Edition (Java EE), this involves creating a deployment descriptor suitable to the type of application that is being deployed.; (2) To make operational the configuration and topology of the broker domain.; (3) To make a HATS application ready for use on the server, using functions in WebSphere Application Server, after transfer has taken place. See also transfer.; (4) To place files or install software into an operational environment. For example, in a policy-enabled system, policies are deployed to the autonomic managers that are registered to receive those policies, putting those policies into effect in that operational environment. See also undeploy.
�deployed security role: A security role that is qualified with the display name specified in an enterprise bean's deployment descriptor, and the prefix specified in the EJBROLEPRFX system initialization parameter.
�deployment: (1) The act of packaging enterprise beans into a JAR file for distribution to a container on an enterprise bean server.; (2) The process of making WebSphere Commerce application code available for use. This process includes packaging customized commands, data beans, and enterprise beans into JAR files. The JAR files must then be installed and configured within a container.; (3) A discipline in the software-engineering process, whose purpose is to ensure a successful transition of the developed system to its users. Included are artifacts such as training materials and installation procedures.; (4) In WebSphere InterChange Server, the process of taking generated components and making them available for use. This process includes the user choosing the components to deploy, repos copy or System Manager taking the user's choices and sending the data to the server, the server taking the data and the instructions and integrating them into the system.; (5) The process of reconfiguring and reallocating resources in the managed environment. Deployment occurs in response to deployment requests, created manually by administrators or automatically by the system.; (6) The process to install an operating system, and possibly other applications and files, on a client computer. During a deployment, data previously stored on the hard drives of the client are deleted.
�deployment code: Additional code that enables bean implementation code written by an application developer to work in a particular EJB runtime environment. Deployment code can be generated by tools that the application server vendor supplies.
�deployment data: The resource files, generated during customization, that are used to create the resources for an instance.
�deployment data set: A data set containing the resource files generated during customization.
�deployment descriptor: An XML file that describes how to deploy a module or application by specifying configuration and container options. For example, an EJB deployment descriptor passes information to an EJB container about how to manage and control an enterprise bean.
�deployment diagram: A UML diagram that models the physical architecture of a system by showing the relationships between the software and hardware components in the system and the physical distribution of the processing.
�deployment directory: The directory where the published server configuration and Web application are located on the machine where the application server is installed.
�deployment engine: A component of Tivoli Provisioning Manager that runs workflows.
�deployment environment: (1) A specific instance of a configuration of hardware and software established for the purpose of installing and running the developed software for its intended use. See also test environment.; (2) A collection of configured clusters, servers, and middleware that collaborate to provide an environment to host software modules. For example, a deployment environment might include a host for message destinations, a processor or sorter of business events, and administrative programs.
�deployment instruction: A set of instructions, generated by the Customization Definition Program (CDP) during customization definition, that describe how to execute the resource files, and thereby deploy, on the runtime systems, the resources required by the instance.
�deployment management: The Tivoli management discipline that addresses the automation of configuration and change management activities for the ever-evolving components of a network computing system.
�deployment manager: A server that manages operations for a logical group or cell of other servers.
�deployment phase: A phase that includes a combination of creating the hosting environment for your applications and the deployment of those applications. This includes resolving the application's resource dependencies, operational conditions, capacity requirements, and integrity and access constraints.
�deployment plan: A list of resources, configurations, and implementations required to realize the deployment of an application.
�deployment policy: A policy that associates a specific bay in a BladeCenter chassis with a Remote Deployment Manager (RDM) noninteractive task. When a blade server is added to or replaced in the bay, IBM Director automatically runs the RDM task.
�deployment scheme: A specific type of task template which contains parameters for customizing a deployment on a client display screen layout. See also task template.
�deployment specification: In UML modeling, a configuration file, such as an XML document or text file, that defines how a node should operate.
�deployment state: One of several states that a service level agreement (SLA) goes through after it is submitted.
�deployment topology: The configuration of servers and clusters in a deployment environment and the physical and logical relationships among them.
�deployment unit: A set of objects or components that are allocated to a process or a processor as a group. A distribution unit can be represented by a runtime composite or an aggregate.
�deployment vehicle: A job or other executable file that is used to deploy resources. Each vehicle corresponds to a particular resource file.
�deployment view: An architectural view that describes one or several system configurations; the mapping of software components (tasks, modules) to the computing nodes in these configurations.
�deploy phase: See deployment phase.
�deploy relationship: In UML modeling, a relationship that shows the specific artifact that an instance of a single node deploys or uses.
�depositor access: An access level that allows users to create documents but not read any of the documents in the Notes database.
�depot: A directory that enables the temporary or permanent storage of data segments.
�deprecated: Pertaining to an entity, such as a programming element or feature, that is supported but no longer recommended and that might become obsolete.
�deprovision: To remove a service or component. For example, to deprovision an account means to delete an account from a resource. See also provision.
�dequeue: To remove items from a queue. See also enqueue.
�dereference: (1) In the C and C++ languages, to apply the unary operator * to a pointer to access the object the pointer points to. See also indirection.; (2) In VisualAge RPG, to remove information specific to the System i platform from a control.
�deregister: In the hierarchical file system, to remove an underlying file system and the specific functions it supports from the application programming interface layer and to make it unavailable to user applications.
�derivation: (1) The process of deriving a C++ class from an existing class, called a base class.; (2) In object-oriented programming, the refinement or extension of one class from another.; (3) A morphological process used to produce additional words from a canonical base form, for example: compute, computer, computerize, and recomputed.
�derived class: See base class.
�derived element: A model element that can be computed from another element, but that is shown for clarity or that is included for design purposes even though it adds no semantic information.
�derived form: A query management form that was built by converting a Query definition object.
�derived name: In REXX, the stem of the symbol, in uppercase, followed by the tail in which all simple symbols have been replaced by their value. It is also the default value of a compound symbol.
�derived object (DO): A type of output created by a ClearCase build in a dynamic view.
�derived property: In UML modeling, a property that indicates that the value of an attribute or an association is calculated using information from elsewhere in the model.
�derived query: A query management query that was built by converting a Query definition object.
�derived value: In UML modeling, a value that is assigned to an attribute or association by applying a specific formula to information that exists somewhere else in the model.
�DES: See Data Encryption Standard.
�DES authentication: A type of encryption algorithm that requires a client to send credentials (name, conversation key, window key, and a time stamp) to the server. The server then returns a verifier to the client. Data Encryption Standard (DES) credentials are sometimes called secure credentials because they are based on a sender's ability to encrypt data using a common time reference; a randomly generated key is required to encrypt a common reference time that is then used to create a conversation key.
�descendent: An object that is a dependent of another object or is a dependent of an object that is in turn a dependent of another object.
�descendent foreign key table: (1) A dependent foreign key table of a given table.; (2) A dependent foreign key table of a descendent foreign key table of a given table. See also dependent foreign key table.
�descendent immediate materialized query table: A descendent materialized query table that is defined with the REFRESH IMMEDIATE option.
�descendent materialized query table: (1) A dependent materialized query table of a given table.; (2) A dependent materialized query table of a descendent foreign key table of a given table.
�descendent row: A row that is a dependent of another row or is a descendent of a dependent of another row.
�descendent staging table: (1) A dependent staging table of a given table.; (2) A dependent staging table of a descendent foreign key table of a given table.
�descendent table: A table that has a dependent relationship on a parent table or on another descendent table. See also dependent table.
�descending key: The values by which data is arranged from the highest value to the lowest value of the key field, in accordance with the rules for comparing data items. See also ascending key.
�descending key sequence: The arrangement of data in order from the highest value of the key field to the lowest value of the key field. See also ascending key sequence.
�descending sequence: The arrangement of data in order from the highest value to the lowest value, according to the rules for comparing data. See also ascending sequence.
�descriptive attribute: An additional description for an item. Descriptive attributes are not used for SKU resolution. See also defining attribute.
�descriptor: (1) In the DCE X/Open Directory Service, a defined data structure that is used to represent an OM attribute type and a single value.; (2) See screen recognition criteria.; (3) A PL/I control block that holds information such as string lengths, array subscript bounds, and area sizes, and is passed from one PL/I routine to another during run time.; (4) A small, unsigned integer that a UNIX system uses to identify an object supported by the kernel. Descriptors can represent files, pipes, sockets, and other I/O streams.; (5) An XML file that describes the content of a component or resource. See also installable unit deployment descriptor, media descriptor.; (6) A skeleton from which an IMS control block is dynamically built. A user descriptor can provide user options and queue names.
�deselect: To cancel a previously selected object.
�deselection: The process of removing selection from a previously selected object.
�deserialization: A method for converting a serialized variable into object data. See also serializer.
�deserialize: To construct an object from a de-marshaled state.
�DE services: See directory entry service.
�design: The part of the elaboration phase in which strategic and tactical decisions about how to meet the required functional and quality requirements of a system are made
�designated approving authority (DAA): The official who has the authority to accept the security safeguards for an information system. The DAA may be responsible for issuing an accreditation statement that records the decision.
�designated gateway SSCP: See designated gateway VTAM.
�designated gateway VTAM: A gateway system services control point (SSCP) designated to perform all the gateway control functions during LU-LU session setup.
�designated router: (1) A router that informs end nodes of the existence and identity of other routers. The selection of the designated router is based upon the router with the highest priority. When several routers share the highest priority, the router with the highest station address is selected.; (2) In a multiaccess OSPF network that has at least two attached routers, a router that is responsible for generating link-state advertisements (LSAs) for the entire multiaccess network and determines which routers should become adjacent. A designated router is elected by other routers using the Hello Protocol. See also backup designated router.
�designation: An optional, '-' separated list of node roles (manager, client). Indicates whether a node is part of the pool of nodes from which configuration and file system managers are selected.
�design element: In a Notes database, a field, form, view, public agent, database icon, Using This Database document, or About This Database document.
�designer access: An access level with which users can compose, read, and edit any documents, plus modify the database icon, About and Using documents, and all design elements. Servers can replicate all of the above and, if they have delete access, deletions.
�design mechanism: An architectural mechanism used during the design process, during the period in which the details of the design are being worked out.
�design model: A model, based on the analysis model, that describes the structure of a system and how it's implemented.
�design package: A collection of classes, relationships, use-case realizations, diagrams, and other packages that is used to structure the design model by dividing it into smaller parts. See also design subsystem.
�design pane: In Domino Designer, the workspace area that displays design options, as well as areas to enter design information.
�design pattern: A scheme for refining the subsystems or components of a software system, or the relationships between them. A design pattern describes a commonly recurring structure of communicating components that solves a general design problem within a particular context.
�design subsystem: A model element that has the semantics of a package (it can contain other model elements) and a class (it has behavior). See also design package.
�design template: A Notes database design that lets users share design elements among databases and store design elements with a template. The template can be enabled so that when it changes, the change automatically occurs in all databases created with that template.
�design time: The time period during a design phase of the software development process. See also modeling time.
�design window: In VisualAge RPG, the window in the GUI design tool suite on which parts are placed to create a user interface.
�desired state: The state that a user wants an object to have.
�desired state management: The process of verifying that devices are at the desired state and taking actions in order to achieve that state.
�Desktop Management Interface (DMI): A protocol-independent set of application programming interfaces (APIs) that were defined by the Distributed Management Task Force (DMTF). These interfaces give management application programs standardized access to information about hardware and software in a system.
�DESPI: See Data Exchange SPI architecture.
�despooling: The process of reading records from the spool into central storage. During the despooling process, the physical track addresses of the spool records are determined.
�destage: To move data from cache to a nonvolatile storage medium.
�destager: A function of the Content Manager resource manager that moves objects from the staging area to the first step in the object's migration policy.
�DESTID: See destination identifier.
�destination: (1) Any point or location, such as a program, node, station, printer, or a particular terminal, to which information is to be sent.; (2) In IMS TM, an application program, a logical terminal, or an operator command that is associated with the control region.; (3) A queue of data used with the CICS transient data facility.; (4) An exit point that is used to deliver documents to a back-end system or a trading partner.
�destination address: The location to which information is to be sent. See also source address.
�destination address field (DAF): In SNA, a field in a format identification 0 or format identification 1 transmission header that contains the network address of the destination. In a format identification 2 header, the field is called destination address field prime (DAF'). See also origin address field.
�destination code: A numeric code used to categorize information that is sent from a user address space to the global address space, or between the global and a local address space. A destination code can correspond to either subsystem interface function codes or internal JES3 communication.
�destination control file: In a Windows environment, a user-modifiable file for simpler mapping of JCL to Infoprint Manager parameters.
�destination control table (DCT): A table describing each of the transient data destinations used in CICS. This table contains an entry for each extrapartition, intrapartition, and indirect destination.
�destination ID: See destination identifier.
�destination identifier (DESTID, DID, destination ID): (1) The 8-character subscript on the DESTID initialization statement or command that corresponds to a combination of a first-level destination and a second-level destination that determines where data should be sent in a JES2 installation. A DESTID can be either a symbolic destination or an explicit destination. See also explicit destination, symbolic destination.; (2) The 3-byte destination ID of the destination device, in the 0xDomainAreaALPA format.
�destination list: See local environment.
�destination logical unit (DLU): A logical unit that is the target of a Locate search request as part of a session initiation sequence.
�destination node: (1) In the OSI Communications Subsystem licensed program, a node that is the final recipient of data sent by the local node and the origin of data sent to the local node. A destination node may or may not be an adjacent node.; (2) The node to which a request or data is sent.
�destination NSAP address: In OSI, an NSAP address that identifies a destination node.
�destination parent: In a database, the physical or logical parent that is reached by the logical child path.
�destination point code (DPC): A code that identifies the signaling point to which an MTP signal unit is destined. Unique within a particular network.
�destination queue (DSQ): A control block that is used by subsystem interface routines to route requests (represented by destination codes) to the JES3 routines responsible for servicing the requests.
�destination service access point (DSAP): (1) In OSI, a service access point used to receive data.; (2) In SNA and TCP/IP, a logical address that allows a system to route data from a remote device to the appropriate communications support. See also source service access point.
�destination system: (1) In SNADS, a system that can receive messages, documents or objects.; (2) In an IMS multisystem environment,the system in which the logical destination resides.
�destructive data change: An event in which data is modified by a change operation in an application or by a trigger, and then the data is modified again by other trigger actions within the same trigger.
�destructor: A special member function of a class with the same name as the class with a ~ (tilde) preceding the name. You cannot specify arguments or a return type for this function. A destructor "cleans up" after an object by doing such things as freeing any storage that was dynamically allocated when the object was created.
�detach: (1) In a multithreaded environment, to mark a thread so that the system reclaims the thread resources when the thread ends. If the thread is already ended, the resources are freed immediately.; (2) In cross-site mirroring, to disassociate a mirror copy from the production copy to use the mirror copy for a separate operation, such as to save data, to run reports, or to perform data mining. Detaching a mirror copy suspends geographic mirroring.

�detached copy: The mirror copy of an independent disk pool that is disassociated from the production copy in a cross-site mirroring (XSM) environment.
�detached data partition: A data partition that is detached from a table but remains part of the table pending the completion of asynchronous index cleanup or integrity processing on dependent tables. Data in detached data partitions is unavailable to SQL statements. See also visible data partition.
�detached dependent table: A dependent table that needs to be incrementally maintained after a data partition is detached using an ALTER TABLE statement.
�detached table: A table, created from a detached data partition by using an ALTER TABLE statement, that is inaccessible until all of the corresponding detached dependent tables are maintained.
�detail block text: The text in the body of a report that is associated with a particular row of data.
�detail calculation: In RPG, specified calculation operations that are performed for every record read.
�detail heading text: The text in the heading of a report.
�detail line: In RPG, a detail record in an output file.
�detail record: (1) A record that contains the daily activities or transactions of a business. For example, the items on a customer order are typically stored in detail records. See also header record.; (2) In RPG, an output record produced during the detail output operation of the RPG program cycle. See also total record.
�detail report: In Query, a report that contains all the information produced by a query. See also summary report.
�details view: A standard contents view in which a small icon is combined with text to provide descriptive information about an object. The text is arranged in rows and columns so one row is for each object and one column is for each type of descriptive information displayed.
�detail time: That part of the RPG program cycle in which calculation and output operations are performed for each record read. See also total time.
�detected access transmission error in (DTSE in): In Performance Tools, the number of times the network termination 1 (NT1) notifies the terminal equipment (TE) of an error in data crossing the U interface of the integrated services digital network (ISDN) from the line transmission termination (LT) to the NT1. The NT1 reports the errors to the TE through the maintenance channel S1.
�detected access transmission error out (DTSE out): In Performance Tools, the number of times the network termination 1 (NT1) notifies the terminal equipment (TE) of an error in data crossing the U interface of the integrated services digital network (ISDN) from the NT1 to the line transmission termination (LT). The NT1 reports the errors to the TE through the maintenance channel S1.
�determinant: A value resulting from a mathematical operation on an array.
�determiner: A word that qualifies the noun with respect to its reference in context or the quantity. In English, determiners may include articles ('a'; 'the'), quantifiers ('all'; 'some'), demonstratives ('this'; 'that'), possessive pronouns ('my'; 'your'), and cardinal numbers ('one'; 'two').
�deterministic dictionary: A dictionary in which for a given input character you have only one transition path out of a node. Some languages require this capability to represent their vocabulary in a compact way. See also non-deterministic dictionary.
�deterministic function: A user-defined function whose result is dependent on the values of the input arguments. That is, successive invocations with the same input values produce the same answer.
�DEVD: See device description.
�developer: (1) A person who creates or modifies components of the WebSphere business integration system, such as connectors, collaborations, business objects, and maps. The developer typically uses IBM-provided templates or existing components as the basis for developing new ones.; (2) A person responsible for developing the required software functions that conform to project standards and procedures. This work can include performing activities in any of the requirements, analysis and design, implementation, and test disciplines.
�developer domain: See developerWorks.
�Developer Kit for Java: See IBM Developer Kit for Java.
�developerWorks: The IBM resource for developers on the Web.
�development case: The software-engineering process used by a project team. It is developed as a configuration, or customization, of the Unified Process product, and adapted to the project's needs.
�development cycle: See life cycle.
�development environment: The applications and work area for creating the components of a Web application, such as JavaServer Pages (JSPs), style sheets, servlets, or other programming artifacts.
�development folder: In System Manager, a folder containing documents for a load that is being developed.
�development library: In System Manager, the library containing all or part of a product that is being developed.
�development process: A set of steps performed for a given purpose during software development, such as constructing models or implementing models.
�development stream: An object that determines which versions of elements appear in a development view and maintains a list of a developer's activities. The development stream configures the development view to select the versions associated with the foundation baselines plus any activities and versions that developers create after they join the project or rebase their development stream.
�development system: A DirectTalk system that is not used to respond to or make 'live' calls; it is used only to develop and test applications. See also production system.
�device: (1) A piece of equipment. Devices can be workstations, printers, disk drives, tape units, or remote systems.; (2) In the AIX operating system, a valuator, button, or the keyboard. Buttons have values of 0 or 1 (up or down); valuators return values in a range, and the keyboard returns ASCII values.; (3) In UML modeling, a type of node that represents a physical computational resource in a system, such as an application server.
�device adapter (DA): A physical component of the ESS that provides communication between the clusters and the storage devices. Multiple DAs are connected to the clusters in such a way that any cluster can access storage device via multiple paths, providing fault tolerance and enhanced availability. See also SSA adapter, loop.
�device address: A unique identifier for each device so it is recognized by the system.
�device agent program: A program that resides on a device, functions as a client, and processes jobs as its main task. The device agent program also contains the initial communications data used during enrollment of a device.
�device attributes feedback area: In the C language, an area that allows a user to obtain information about a specific device.
�device category: A storage device classification used by the storage management subsystem (SMS). The device categories are: SMS-managed direct access storage device (DASD), SMS-managed tape, DASD not managed by SMS, and tape not managed by SMS.
�device characteristics table (DCT): An MFS table that is generated for IBM 3270 or SLU type 2 devices with symbolic names. An entry is generated for each symbolic name and its associated screen size and physical terminal features. Different combinations of features for the same symbolic name cause separate entries in the table to be created.
�device class: (1) The generic name for a group of device types. For example, all display stations belong to the same device class. See also device type.; (2) A named set of characteristics applied to a group of devices. Each device class has a unique name and represents a device type.
�device cluster resource group: A cluster resource group that contains a list of switchable devices, such as independent disk pools which reside on a switchable entity. See also switchable entity.
�device configuration: The physical placement of display stations, printers, and so forth; and the configuration descriptions that describe the physical configuration to the system and describe how the configuration will be used by the system.
�device control character: A control character used to specify a control function for peripheral devices associated with a system.
�device dependence: The reliance on the characteristics of particular types of devices used in writing and running programs or in performing functions. See also device independence.
�device-dependent: Pertaining to a function that can be accomplished, or a program that can be run, only if particular types of devices are available. See also device-independent.
�device description (DEVD): An object that contains information describing a particular device or logical unit (LU) that is attached to the system. A device description is a description of the logical connection between two LUs (local and remote locations).
�device domain: A collection of cluster nodes that share device resources, such as independent disk pools. For independent disk pools, the resources are: virtual addresses, disk pool numbers and disk unit numbers. An independent disk pool can only be accessed by the nodes in one device domain.
�device driver (DD): (1) A program that provides an interface between a specific device and the application program that uses the device.; (2) A collection of workflows that implement logical device operations for a specific device or data center asset.
�device emulation: The programming that allows one device to appear to the user or to a system as another device.
�device fencing: See device pooling.
�device field (DFLD): In MFS, the smallest area in a device input format (DIF) or device output format (DOF) whose content and structure are defined by the user.
�device file: One of several types of the system object type *FILE. A device file contains a description of how data is to be presented to a program from a device or how data is to be presented to the device from the program. Devices can be display stations, printers, diskette units, tape units, or remote systems.
�device group: A group of devices that are interchangeable as far as z/OS allocation is concerned. Unless a request is made for a specific device name, any device in a given device group can satisfy a request if one device in that device group can satisfy that request.
�device identifier: An identifier that uniquely identifies a logical or physical device.
�device independence: The capability to write and run programs or perform functions without regard for the physical characteristics of devices. See also device dependence.
�device-independent: Pertaining to a function that can be accomplished, or a program that can be executed, without regard for the characteristics of particular types of devices. See also device-dependent.
�device input format (DIF): The Message Format Service (MFS) control block that describes the format of the data that is entered on the device and presented to MFS.
�device interface card: A physical subunit of a storage cluster that provides the communication with the attached disk drive modules (DDMs).
�device management: The task of defining I/O devices to the operating system and then controlling the operation of these devices.
�device manager: (1) The subcomponent of PSF that manages the interface to the printer.; (2) In a Content Manager system, the interface between the resource manager and one or more physical devices.
�device message handler (DMH): For CICS with TCAM SNA, the logical unit in SNA terms. All data flow, control, session startup and takedown, and response handling are provided in the DMH.
�device name: (1) The symbolic name of an individual device.; (2) A name reserved by the system or a device driver that refers to a specific device. For example, the DOS device name for the parallel port is LPT1.
�device number: The reference number assigned to any device.
�device object: An object that provides a means of communication between a computer and another piece of equipment, such as a printer or disk drive.
�device output format (DOF): The Message Format Service (MFS) control block that describes the format of the output data that is presented to the device.
�device page (DPAGE): In MFS, a user-defined group of device field definitions that comprise one or more physical pages to be presented to or received from the device.
�device parity protection: A function that protects data stored on a disk-unit subsystem from being lost because of the failure of a single disk unit in the subsystem. When a disk-unit subsystem has device parity protection and one of the disk units in the subsystem fails, the subsystem continues to run. The disk-unit subsystem reconstructs the data after the disk unit is repaired or replaced. See also checksum protection, mirrored protection, Redundant Array of Independent Disks.
�device partitioning: A pool of devices (called a fence) that is used exclusively by a set of jobs in a specific job class. Using device partitioning, the device usage of an installation can be tailored to its anticipated workload.
�device pooling: Reserving devices for use only by jobs within a specified job group, or jobs with a specified job network.
�device provider: A device-specific handler that serves as a plug-in for the Common Information Model (CIM); that is, the CIM Object Manager (CIMOM) uses the handler to interface with the device.
�device selection character: In BSC, the control character that is sent to a receiving system or to a device connected to a receiving system to select that device to receive the output.
�device sparing: A subsystem function that automatically copies data from a failing disk drive module (DDM) to a spare DDM. The subsystem maintains data access during the process.
�Device Support Facilities (ICKDSF): An IBM program used for initialization of direct access storage device (DASD) volumes and track recovery.
�device table: A list of finance devices supported by a server to be used by a finance job.
�device token: In the GDDM function, an 8-byte code, required to set the devices to a predefined set of hardware characteristics.
�device type: The generic name for a group of devices. See also device class.
�DF: See decision federator.
�DFC: See data flow control.
�DFC layer: See data flow control layer.
�DFH: Three-character prefix of all CICS modules.
�DFHAID: A COBOL copybook containing the symbolic names for all the AID keys in CICS.
�DFHCMACD: See CICS messages and codes data set.
�DFHDUP: See dump utility program.
�DFHDYP: See dynamic transaction routing program.
�DFHMDF: See field definition macro.
�DFHMDI: See map definition macro.
�DFHMSD: See map set definition macro.
�DFHOSTAT: See sample statistics program.
�DFHRPL: See CICS program library.
�DFHSIP SIP: See system initialization program.
�DFHSM: See Data Facility Hierarchical Storage Management System.
�DFHSTUP STUP: See statistics utility program.
�DFLD: See device field.
�Data Facility Product (DFP): A program that isolates applications from storage devices, storage management, and storage device hierarchy management.
�DFP: See Data Facility Product.
�DFS: (1) See Distributed File Service.; (2) See distributed file service.
�DFSMS (Data Facility Storage Management Subsystem): An operating environment that helps automate and centralize the management of storage. To manage storage, the storage management subsystem (SMS) provides the storage administrator with control over data class, storage class, management class, storage group, and automatic class selection (ACS) routine definitions.
�DFSMSdfp: A DFSMS functional component and a base element of z/OS that provides functions for storage management, data management, device management, and distributed data access.
�DFSMSdss: A DFSMS functional component or base element of z/OS that provides data set services. DFSMSdss provides functions for copying, moving, dumping, and restoring of data sets and volumes.
�DFSMS environment: See system-managed storage environment.
�DFSMShsm: A DFSMS functional component or base element of z/OS that provides functions for backing up and recovering data, and managing space on volumes in the storage hierarchy.
�DFSMShsm-managed volume: A storage volume that is defined to DFSMShsm. See also DFSMSrmm-managed volume, system-managed volume.
�DFSMShsm-owned volume: A storage volume on which DFSMShsm stores backup versions, dump copies, or migrated data sets.
�DFSMS/MVS: An IBM licensed program that provides the complementary functions of DFSMSdfp, DFSMSdss, DFSMShsm, and DFSMSrmm, which, together with the Resource Access Control Facility (RACF), provide a system-managed, administrator-controlled, storage environment. Functions of DFSMS/MVS are included in z/OS.
�DFSMS Network File System: See z/OS Network File System.
�DFSMS Optimizer Feature: A DFSMS feature that provides an analysis and reporting capability for both the storage management subsystem (SMS) and environments that do not use SMS.
�DFSMSrmm: A DFSMS functional component or base element of z/OS that manages removable media.
�DFSMSrmm-managed volume: A tape volume that is defined to DFSMSrmm. See also DFSMShsm-managed volume, system-managed volume.
�DFSORT: See Data Facility Sort.
�DFT: See distributed function terminal.
�DFU: See data file utility.
�DFW: See DASD fast write.
�DHCF: See distributed host command facility.
�DHCP: See Dynamic Host Configuration Protocol.
�DIA: See Document Interchange Architecture.
�diacritic: A mark indicating a change in the phonetic value of a character or a combination of characters.
�DIA document distribution service: A service that allows users to send, receive, file, print, change details of, and query electronic mail.
�diagnostic: Pertaining to the detection and isolation of an error.
�diagnostic message: A message that contains information about errors or possible errors. This message is generally followed by an escape message.
�diagram: A graphical presentation of a collection of model elements, most often rendered as a connected graph of arcs (relationships) and vertices (other model elements).
�dial: To initiate a telephone call. In telecommunication, this action is performed to establish a connection between a terminal and a telecommunication device over a switched line.
�dial by name: To press the keys that correspond to subscribers' names rather than their telephone numbers or extensions.
�dialed number identification service (DNIS): In telephony, a number supplied by the public telephone network to identify a logical called party. For example, two 800 numbers might both be translated to a single real telephone number. The DNIS is sent when the real telephone number is called to allow end users to distinguish which service is being called when a call arrives to the real number.
�dial-in: Pertaining to the direction in which a switched connection is requested by any node or terminal other than the receiving host or an NCP.
�dialog: (1) A series of related inquiries and responses between a user and an application, similar to a conversation between two people.; (2) The recorded interaction between a user and the 3270 application that the user accesses. Users can record a dialog using the Record Dialog function in the 3270 terminal service recorder. A recorded dialog includes the keystrokes, inputs and outputs that move the user from one screen to another in the 3270 application.; (3) In AIXwindows, a two-way text interface between an application and its user. The interface takes the form of a collection of widgets and gadgets, including a DialogShell widget, a BulletinBoard widget (or a subclass of a BulletinBoard widget or some other container widget), plus various children, including Label, PushButton, and Text widgets.
�dialog box: A secondary window that solicits user input for a specific task or subtask. Common examples are the Print and Save As dialog boxes. Dialog boxes are modal; that is, they must be closed before the user can continue working in the window that launched the dialog box.
�dialog editor: A 3270 terminal service development tool that enables a developer to modify the dialog that was recorded with the 3270 terminal service recorder.
�dialog file: The result of recording a dialog from the 3270 terminal service recorder. The dialog file is saved to a WSDL file in the workbench.
�dialog management: In OSI, a session-layer service that controls which peer application entity has permission to send.
�dialog panel: A panel that overlays part of a Prompted Query primary panel and extends the dialog that helps build a query.
�dialog token: A doubleword token used as an identifier for a specific binder dialog.
�dialog variable: In the user interface manager (UIM), an element in a panel group that is used to pass data values between two programs or between a program and a user. The values for all dialog variables in a panel group are stored in a variable pool.
�dial tone: An audible signal (call progress tone) that indicates that a device such as a PABX or central office switch is ready to accept address information (DTMF or dial pulses).
�Dial-Up Networking: Microsoft software for personal computers running Windows that allows a modem to dial into a server.
�dial-up number: A series of digits required to establish a connection with a remote correspondent via the public telex network.
�dial-up service: A method of connecting a computer to the internet.
�DIB: (1) See directory information base.; (2) See data interchange block.; (3) See DL/I interface block.
�dictionary: (1) In data compression, a table that associates words, phrases, or data patterns with shorter tokens. The tokens replace the associated words, phrases, or data patterns when a data set is compressed.; (2) A grouping of logically related components of a particular syntax type, such as ROD dictionaries, EDI dictionaries, and XML dictionaries.
�dictionary builder: A utility that is used to build system and custom dictionaries. The dictionary builder takes an XML file as input.
�dictionary contraction: A mechanism that is used to reduce the size of a dictionary file.
�dictionary data section: One of the data sections of a CICS monitoring record written to SMF. The dictionary data section defines all the performance data that is being gathered or can be gathered during this CICS run.
�DID: (1) See direct inward dialing.; (2) See destination identifier.
�DIF: (1) See data interchange format.; (2) See device input format.
�difference: Given two sets A and B, the set of all elements contained in A but not in B (A-B).
�differencing phase: The process by which AutoPack compares before and after snapshots and generates the related action for each difference to the software package.
�differential refresh: See change-capture replication.
�differentiated indexing: The process of supplying specific string labels to an entry for different uses. Authors can, for example, specify the context for an entry only when it is used in a cross-product master index. The context does not appear when the entry is in the single-product index.
�Differentiated Services: A quality-of-service standard between two networks that allows hosts to manage data by traffic flow.
�Differentiated Services domain: A contiguous portion of the Internet over which a consistent set of Differentiated Services policies are administered. A Differentiated Services domain can represent different trust regions, different network technologies (such as cells or frames), different hosts, or even different routers.
�Differentiated Services field: A six-bit field in the Internet Protocol (IP) header of a data packet that encodes the Differentiated Services code point. The field replaces the IPv4 IP header field, which is called type of service (ToS).
�Diffie-Hellman group: A public, key-exchange algorithm that is used for securely establishing a shared secret over an insecure channel. During Phase II negotiations, the Diffie-Hellman group prevents someone who intercepts your key from deducing future keys that are based on the one they have.
�Diffie-Hellman key exchange: A public, key-exchange algorithm that is used for securely establishing a shared secret over an insecure channel.
�digest code: A number that is the result of a message digest function or a secure hash algorithm distilling a document.
�digit: (1) Any of the numerals from 0 through 9.; (2) A symbol that represents one of the nonnegative integers smaller than the radix.
�digital: Pertaining to data in the form of digits. See also analog.
�digital audio: Audio tones represented by machine-readable binary numbers rather than by analog recording techniques.
�digital certificate: An electronic document used to identify an individual, a system, a server, a company, or some other entity, and to associate a public key with the entity. A digital certificate is issued by a certification authority and is digitally signed by that authority.
�Digital Certificate Manager (DCM): (1) An i5/OS option that registers certificates that are created on the system when it is acting as a certificate authority (CA). DCM can also be used to register certificates that other certificate authorities issue. DCM allows you to choose to associate a user's certificate with its user profile. DCM is also used to associate digital certificates with various applications so that these applications can use the Secure Sockets Layer (SSL) for secure communications.; (2) An i5/OS component that allows i5/OS to be a local Certificate Authority (CA) to create digital certificates that are used to ensure secure communications.; (3) On i5/OS systems, the method of managing digital certificates and using them in secure applications on the iSeries server. Digital Certificate Manager requests and processes digital certificates from certification authorities (CAs) or other third-parties.
�Digital Cordless Telephone (DCT): A cordless telephone that uses digital transmission technology to provide more security and better sound quality than a traditional analog cordless telephone.
�digital data service adapter (DDSA): In data communications, a device used when sending and receiving data using a nonswitched digital data service.
�digital envelope: In the context of SET programs, a package of encrypted data and the encryption key.
�Digital European Cordless Telecommunications (DECT): A digital wireless telephone technology that is expected to make cordless phones much more common in both businesses and homes.
�Digital Network Architecture (DNA): The model for all DECnet hardware and software implementations.
�digital signal processing (DSP): A set of algorithms and procedures used to process electronic signals after their conversion to digital format. Due to the specific mathematical models required to perform this processing, specialized processors are generally used.
�digital signature: Information that is encrypted with a private key and is appended to a message or object to assure the recipient of the authenticity and integrity of the message or object. The digital signature proves that the message or object was signed by the entity that owns, or has access to, the private key or shared-secret symmetric key.
�digital signature algorithm (DSA): A security protocol that uses a pair of keys (one public and one private) and a one-way encryption algorithm to provide a robust way of authenticating users and systems. If a public key can successfully decrypt a digital signature, a user can be sure that the signature was encrypted using the private key.
�digital speech synthesizer: A device used with screen readers to portray what is on screen through sound. See also screen reader.
�Digital Subscriber Line (DSL): A technology that dramatically increases the digital capacity of ordinary telephone lines in the home or office.
�Digital Subscriber signaling System Number 1 (DDS1): A signaling protocol used between ISDN subscriber equipment and the network. Carried on the ISDN D-channel. ITU-T recommendations Q.920 to Q.940 describe this protocol.
�Digital Trunk Quad Adapter (DTQA): An adapter to complete the connection to four packs in a Multiple Digital Trunk Processor.
�digital versatile disc: See digital video disc.
�digital video: Video in which the information (usually including audio) is encoded as a sequence of binary digits.
�digital video disc (DVD): An optical disc that has the same overall dimensions of a CD-ROM, but has significantly higher capacities than a CD-ROM. DVDs are also double sided, whereas CD-ROMs are single sided.
�Digital Video Interactive (DVI): An integrated video, audio, and graphics technology allowing all forms of data (full motion video, still images, graphics, and text) to be displayed from any digital source. DVI allows real-time compression and decompression as well as display of digital graphics and full-motion video with audio.
�digitize: To convert analog video and audio signals into digital format.
�digitized image: An image derived from a scanning device or a digitizing card with a camera.
�digit position: In COBOL, the amount of physical storage required to store a single digit. This amount can vary depending on the usage specified in the data description entry that defines the data item. If the data description entry specifies that the USAGE IS DISPLAY, then a digit position is synonymous with a character position.
�digraph: A combination of two keystrokes used to represent unavailable characters in a C or C++ source program. Digraphs are read as tokens during the preprocessor phase.
�DIIOP: See Domino Internet Inter-ORB Protocol.
�Dijkstra's algorithm: See Shortest Path First.
�dimension: (1) In System Manager, the interfaces that define guidelines, standards, services, and other interfaces for integrating systems management applications.; (2) A data category that is used to organize and select monitoring context instances for reporting and analysis. Examples of dimensions are time, accounts, products, and markets. See also member.; (3) In multidimensional data, a structural attribute of a cube that organizes data to enable in-depth business analysis.; (4) A data category, such as time, accounts, products, or markets, that represents the highest consolidation level in a multidimensional database outline.
�dimensional model: The part of the monitor model that defines the cubes and cube content that are used for storing, retrieving, and analyzing the data that is gathered over time.
�dimension block index: In multidimensional clustering, a block index that is automatically created for a particular dimension when the dimension is defined on an MDC table. This index is used to maintain the clustering of data along that dimension, together with the other dimensions defined on the table. See also composite block index.
�dimension level: An element or subelement of a dimension that is arranged hierarchically. For example, the time dimension can have years, months, and days as its levels.
�dimension table: The representation of a dimension in a star schema. Each row in a dimension table represents all of the attributes for a particular member of the dimension. See also star schema, star join.
�dimension table lookup: The process of determining whether a dimension table contains the information that is required to satisfy a reference.
�dimension update: The process of inserting new rows or updating existing rows in a dimension table.
�DIMM: See dual inline memory module.
�DIP: See data interchange program.
�diphone: A transitional phase from one sound to the next, used as a building block for speech synthesis. There are typically between one thousand and two thousand diphones in any national language.
�direct access: A file access method allowing reading and writing of records in an arbitrary order.
�direct access device space management (DADSM): A collection of subroutines that manages space on disk volumes.
�direct access method: An access method used to retrieve or update particular blocks of a data set on a direct access device.
�direct access storage device (DASD): A device that allows storage to be directly accessed, such as a disk drive. See also random access memory.
�direct access unmovable (DAU): A data set that contains location-dependent data and, therefore, cannot be moved. A DAU is usually accessed with the basic direct access method (BDAM).
�direct argument passing: A method of passing arguments in which the value of the argument is included directly in the parameter list See also indirect argument passing.
�direct constructor: An XQuery constructor that contains XML-like notation to construct element, attribute, document, text, processing-instruction, or comment nodes. See also computed constructor, constructor.
�direct data set: A data set that has records in random order on a direct access volume. Each record is stored or retrieved according to its actual address or its address relative to the beginning of the data set. See also sequential data set.
�direct dependent segment: In a data entry database (DEDB), a segment that is chained from a root segment. A direct dependent segment is stored in either the root addressable portion or the overflow portion of a DEDB area.
�direct dial in (DDI): See direct inward dialing.
�directed acyclic graph (DAG): A graph with no path that starts and ends at the same vertex.
�directed association relationship: In UML modeling, an association relationship that is navigable in only one direction and in which the control flows from one classifier to another. See also association relationship.
�directed join: A relational operation in which all of the rows in one or both of the joined tables are rehashed and directed to new database partitions based on the join predicate. If all of the partitioning key columns in one table participate in the equijoin predicates, the other table is rehashed; otherwise (if there is at least one equijoin predicate), both tables are rehashed.
�directed maintenance procedure: A maintenance procedure that can be run for a cluster. These procedures are documented in the service guide.
�directed modeling: See assisted modeling.
�directed recall: The moving of a migrated data set from a level 1 or a level 2 volume to a level 0 volume. Directed recall specifies the target volume and unit name.
�directed routing: In an IMS multisystem environment, the routing of response messages to other than the originating terminal as directed by a link receive routing exit routine.
�direct file: A file that contains records that have a relationship between the contents of the record and the record position at which the record is stored.
�direct inward dialing (DID): A service that allows outside parties to call directly to an extension of a PABX. Known in Europe as direct dial in (DDI).
�directive: (1) A statement that is used in an application configuration file to define a particular setting for the application.; (2) A first-failure data capture (FFDC) construct that can be contained in a WebSphere Application Server symptom database to provide information and suggested actions to assist a diagnostic module in customizing the data that is logged.; (3) A control statement that directs the operation of a feature and is recognized by a preprocessor or other tool. See also pragma.
�directly allocated printer: A printer that is allocated to the application program.
�direct managed resource: A managed resource that is not enclosed in a hosting domain. A direct managed resource must be registered independently when it is installed. The root managed resource of a hosting domain is a direct managed resource. See also hosting domain, indirect managed resource.
�direct manipulation: The use of a pointing device to work with objects, rather than through menus. For example, changing the size of a window by dragging one of its edges is direct manipulation.
�direct memory access (DMA): The transfer of data between memory and an input/output device without processor intervention.
�direct monitor handler: An exception handler that allows the application programmer to directly declare an exception monitor around limited high-level language source statements. For ILE C, this capability is enabled through the #pragma statement.
�Director Agent: See IBM Director Agent.
�Director Console: See IBM Director Console.
�Director Core Services: See IBM Director Core Services.
�Director database: See IBM Director database.
�Director environment: See IBM Director environment.
�Director extension: See IBM Director extension.
�Director Server: See IBM Director Server.
�Director Server service: See IBM Director Server service.
�Director service account: See IBM Director service account.
�directory: (1) The DB2 for z/OS system database that contains internal objects such as database descriptors and skeleton cursor tables.; (2) A type of file that contains the names and controlling information for objects or other directories.; (3) In a hierarchical file system, a grouping of related files and directories. A directory can contain zero or more entries, which refer to other directories and files.; (4) In OSI, a repository of information about objects. As defined in the X.500 directory standards, a directory is both a repository of information and the set of services provided to enable its users to access the information in the repository.; (5) A table of identifiers and references to the corresponding items of data.; (6) A collection of open systems that cooperate to hold a logical database of information about a set of objects in the real world.; (7) The part of a partitioned data set that describes the members in the data set.; (8) In UNIX, a file that maps the names of other directories and files to their locations.
�directory access protocol (DAP): In OSI, the X.500 protocol that a directory user agent uses to obtain directory information from a remote directory system agent.
�directory assistance: A feature used by servers to extend client authentication, name lookups, and LDAP operations to secondary directories.
�directory assistance database: A Notes database created from the DA50.NTF template and used to configure Directory assistance.
�directory catalog: An optional directory database that can aggregate entries from multiple Domino Directories into a single database.
�directory default ACL: A model access control list (ACL) that is inherited by subdirectories that are created within the parent directory.
�directory entry: (1) A entry in the system distribution directory. A directory entry contains information about the user, such as user ID and address, system name, profile name, mailing address, and telephone number.; (2) A logical record in a program library directory that contains a member or alias name, a pointer to that member, and attributes of that member.
�directory entry name: A means of identifying the directory entry of a named object to the coupling facility. The directory, all of its entries, and all of the objects associated with those entries are contained in a single structure.
�directory entry service (DE services): A function that manages directory entries in partitioned data sets (PDSs) and partitioned data sets extended (PDSEs). DE Services can be used by unauthorized as well as authorized programs.
�directory information base (DIB): In OSI, an X.500 term indicating a collection of all directory information in a directory system made up of one or more cooperating directory system agents.
�directory manager: A facility for maintaining the user directory of one or more z/VM systems.
�directory manager domain: A CICS domain that provides resource-table lookup services for CICS Transaction Server for z/OS components such as transaction manager, program manager, and user domains. The resource definitions for which the directory manager domain provides services are transaction definitions, remote transaction definitions, transaction classes, TPNames, user attributes, programs, BMS mapsets, and BMS partition sets.
�directory pointer: In the hierarchical file system, the representation of the position of the next directory entry to be read.
�directory schema: The valid attribute types and object classes that can appear in a directory. The attribute types and object classes define the syntax of the attribute values, which attributes must be present, and which attributes may be present for the directory.
�directory server: A server that can add, delete, change, or search directory information on behalf of a client.
�Directory Server: See IBM Tivoli Directory Server for i5/OS.
�directory service: (1) In OSI, the service by which an open system can access directory information. Directory service can be provided locally within an open system, or it can be obtained from another open system using the directory service protocols defined by ISO/CCITT. In OSI Communications Subsystem, directory service is used to obtain the presentation address and other attributes of application entities.; (2) A component that provides naming, object storage, and lookup capabilities to other components.
�Directory Services Markup Language (DSML): An XML implementation that provides a common format for describing and sharing directory services information among different directory systems.
�directory shadowing: The capability of a system to duplicate Enterprise Address Book (EAB) data from one installation of the EAB to another, such that whenever an addition, change, or deletion is made to the EAB on a given system, it is available to all EAB installations within the network.
�directory system agent (DSA): In Open Source Initiative (OSI), an application process residing in an open system that provides directory service to other open systems.
�directory user agent (DUA): In OSI, an application process residing in an open system that serves as the agent that obtains directory services for that open system. The agent can obtain the services either locally or from a remote directory system agent.
�Direct Printer Services Subsystem (DPSS): The PSF subcomponent that acts as the interface between PSF and an application program when the job entry subsystem is not spooling jobs for a printer. DPSS attaches PSF as a subtask for use in the direct-printing mode.
�direct printing mode: A printing mode that gives PSF exclusive use of a channel-attached printer. Output is printed immediately and is not spooled through JES. See also deferred printing mode.
�direct routing: In Internet communications, the transmission of an Internet Protocol (IP) datagram when the destination and the source reside on the same IP network or IP subnet.
�direct sales business model: A business model that supports commerce transactions involving products, services, or information directly between businesses and consumers or between two businesses or parties. WebSphere Commerce supports the following types of direct sales business models: consumer direct and B2B direct. See also B2B direct business model, consumer direct.
�direct sales store: A customer-facing store that supports the exchange of products, services, or information directly between businesses and consumers, or between two businesses or parties. See also extended site store.
�direct search list (DSRLST): A message unit that contains a search request that is sent throughout subarea networks to obtain information about a network resource (such as its name, routing information, and status information).
�direct service: In MERVA, a service that uses resources that are always available and that can be used by several requesters at the same time.
�direct speech recognition: Identification of words from spoken input read directly from the telephony channel. See also indirect speech recognition.
�DirectTalk: A voice processing system, bringing together telephone and data communications networks to use information stored in databases directly from a telephone.
�DirectTalk bean: One of the DirectTalk Beans that provides access from a voice application to simple call control functions: waiting for a call, making an outgoing call, handing a call over to another application, and returning a call when finished.
�DirectTalkMail: See Message Center.
�DIRF: See DADSM interrupt recording facility.
�dirty address space: An address space requiring daemon authority that has had an uncontrolled program loaded into it. A dirty address space cannot perform daemon activities. See also controlled program.
�dirty page: A storage page that contains data that has been changed but has not yet been written to disk. After a changed page is written to disk, it is clean but remains in the buffer pool until its space is needed for new pages.
�dirty read: A read request that does not involve any locking mechanism, and which may obtain invalid data - that is, data that has been updated, but is not yet committed, by another task. This could also apply to data that is about to be updated, and which will be invalid by the time the reading task has completed. See also read integrity.
�DIS: See Data Interchange Services.
�disable: To disconnect or stop a subsystem.
�disabled: (1) Pertaining to a state of a processing unit that prevents the occurrence of certain types of interruptions. See also enabled.; (2) Pertaining to the state in which a transmission control unit or audio response unit cannot accept incoming calls on a line.; (3) In VTAM, pertaining to a logical unit (LU) that has indicated to its system services control point (SSCP) that it is temporarily not ready to establish LU-LU sessions. An initiate request for a session with a disabled logical unit (LU) can specify that the session be queued by the SSCP until the LU becomes enabled. The LU can separately indicate whether this applies to its ability to act as a primary logical unit (PLU) or a secondary logical unit (SLU). See also enabled, inhibited.
�disabled mechanism: A function of a printer that is temporarily out of operation or is not supported. In such a case, PSF might allow jobs to print with alternative options.
�disaster backup: A means to protect a computing system against data loss in the event of a disaster. Disaster backup is the portion of disaster recovery in which a secure copy of data is made.
�disaster recovery: (1) The process of restoring a database after a partial or complete site failure that was caused by a catastrophic event such as an earthquake or fire. Typically, disaster recovery requires a full database backup at another location.; (2) A procedure for copying and storing an installation's essential data in a secure location, and for recovering that data in the event of a catastrophic problem. See also vital records.
�DISC: See disconnect.
�discipline: (1) In System Manager, a grouping of systems management tasks that support an enterprise's information system environment. Examples of disciplines are change management and problem management.; (2) A collection of related activities that are related to a major task in the development process. The disciplines in RUP include: Business Modeling, Requirements, Analysis and Design, Implementation, Test, Deployment, Configuration and Change Management, Project Management, Environment.
�DIS client: See Data Interchange Services client.
�disconnect (DISC): In communications, the transmission control character that is part of the sequence for disconnecting a switched line.
�disconnect character: In data communications, the part of the BSC transmission control sequence for ending the connection on a switched line.
�disconnected mode (DM): (1) In communications, a response from a secondary station indicating that it is logically disconnected from the link.; (2) A method of logging on to systems that are not connected to a network, such as logging on to laptops that are used away from the office.
�disconnected target command: In Tivoli Software Distribution, Version 4, a command that is run from the command line of a target system that is not connected to the Tivoli management region server.
�disconnect timeout: An indication that a switched BSC connection was disconnected because there was no activity on the connection for a specified length of time.
�discontiguous shared segment (DCSS): An area of virtual storage outside the address range of a virtual machine. It can contain read-only data or reentrant code. It connects discontiguous segments to a virtual machine's address space so programs can be fetched.
�discover: (1) In UDDI, to browse the business registry to locate existing Web services for integration.; (2) To identify resources within a network environment.
�discovered software package: In Tivoli Software Distribution, Version 4.1, an application that was installed on an endpoint independently of Tivoli Software Distribution and that was later added to the endpoint's catalog and given a status of "installed and discovered," using a Tivoli Software Distribution disconnected target command.
�discoverer: A function of a crawler that determines which data sources are available for the crawler to retrieve information from.
�discovery: (1) The automatic detection of a network topology change, for example, new and deleted nodes or links.; (2) The process of finding resources within an enterprise, including finding the new location of monitored resources that were moved.
�discovery association: The relationship created with the method or application used to discover a device. An existing device in the data center model must have a discovery association in order to perform discovery.
�discovery-by-event: A type of autodiscovery in which either (a) a program receives special events that provide the name and location of a particular resource or (b) a program receives normal events, recognizes that no object represents the resource that originated the events, creates an object for that resource, and posts the events to that object.
�discovery library: A file system directory that stores discovery library books, which contain IDML representations of data copied from management software systems by discovery library adapters.
�discovery library adapter (DLA): (1) A program that copies data from a management software system, converts it to IDML, and stores it in books in the discovery library.; (2) A component of an IBM product that captures discovery information.
�discovery library book: (1) An IDML file in the discovery library, containing data copied from a management software system.; (2) An XML document that stores discovery information and their relationships. The discovery library book can be later consumed by other discovery library aware systems.
�discovery library reader (DLR): Any program that reads configuration item data from IDML books in the discovery library and converts it to the format that is required by a consuming application. The bulk loader is a DLR.
�discovery policy: (1) The actions that an administrator or Tivoli Intelligent Orchestrator is to take if a certain new item or if a difference in the data center model is discovered.; (2) A policy that defines an area of the Web environment to investigate and sample the transaction activity of real customers and average performance times for Uniform Resource Indicator (URI) requests during a specified time period so you can set a baseline of performance.
�discovery server: A server that is used to collect, store, and work with configuration item information using the configuration management database.
�discovery technology: An application that is used to perform configuration change detection in Tivoli Intelligent Orchestrator.
�discrete backup profile: A Resource Access Control Facility (RACF) profile created when DFSMShsm backs up a cataloged, RACF-indicated data set.
�discrete profile: A Resource Access Control Facility (RACF) profile that contains security information about a single data set, user, or resource. See also data set profile, generic profile, resource profile.
�discrete word recognition: Identification of spoken words separated by periods of silence, or input one at a time. See also continuous speech recognition.
�discretionary access control: A security mechanism that protects information from unauthorized disclosure or modification through owner-controlled access to files.
�disjoint substate: A substate that cannot be held simultaneously with other substates contained in the same composite state. See also composite state, substate.
�disk: A storage device that includes one or more flat, circular plates with magnetic or optical surfaces on which information is stored.
�disk 16 pack: A group of 16 disk drive modules (DDMs) installed as a unit in a DDM bay. A disk 16 pack is sometimes referred to as a DDM bay.
�disk array controller: The device, such as a Redundant Array of Independent Disks (RAID), that manages one or more disk arrays and provides functions. See also disk array router.
�disk array router: A router that represents an entire array, including current and deferred paths to all logical unit numbers (LUNs). See also disk array controller.
�disk cage: A container for disk drives.
�disk controller: A device that coordinates and controls the operation of one or more disk drives and synchronizes the operation of the drives with the operation of the system as a whole. Disk controllers provide the storage that the cluster detects as managed disks (MDisks).
�disk descriptor: A definition of the type of data that the disk contains and the failure group to which this disk belongs. See also failure group.
�disk drive: The mechanism used to read and write information on a disk.
�disk drive module (DDM): A field-replaceable unit (FRU) that consists of a single disk drive and its associated packaging.
�disk drive module group: See disk 16 pack.
�disk eight pack: A group of eight disk drive modules (DDMs) installed as a unit in a chassis. A disk eight pack is sometimes referred to as a DDM bay.
�disk enclosure: (1) A sealed container that holds the read/write head and disk assembly within a disk unit.; (2) The part of a disk unit that contains the read and write heads, the magnetic disks, and the actuators.
�diskette: A thin, flexible magnetic plate that is permanently sealed in a protective cover. It can be used to store information copies from the disk or another diskette.
�diskette file: A device file created by the user for a diskette unit.
�diskette unit: A physical enclosure containing one or more diskette drives.
�disk group: A collection of disk drives in the same loop configured by the ESS to be available for assignment as a Redundant Array of Independent Disks (RAID). A disk group can be formatted as count key data (CKD) or fixed block, formatted as RAID, or left unformatted. A disk group is a logical assemblage of multiple disk drives, in contrast to a disk eight pack or disk 16 pack.
�disk leasing: A method for controlling access to storage devices from multiple host systems. Any host that wants to access a storage device configured to use disk leasing registers for a lease; in the event of a perceived failure, a host system can deny access, preventing I/O operations with the storage device until the preempted system has reregistered.
�diskless node: A Linux node with no disk or a Linux node that does not use its disk to store the operating system or packages.
�disk operating system (DOS): An operating system for computer systems that use disks and diskettes for auxiliary storage of programs and data.
�disk pool: (1) An auxiliary storage pool that contains only disk units.; (2) In z/VM Center, a logical grouping of contiguous disk spaces. A disk pool can include disk spaces from multiple physical disks. A disk pool corresponds to a z/VM Directory Maintenance Facility allocation group.
�disk pool group: Made up of a primary disk pool and zero or more secondary disk pools, each of which are independent in regard to data storage, but combine to act as one entity.
�disk unit: A sealed container that holds the read and write heads, the magnetic disks, and the actuators. See also random access memory.
�disk unit enclosure: A physical enclosure containing one or more disk units.
�disk volume: See volume label.
�disk zone: A zone defined in the storage area network (SAN) fabric in which the SAN Volume Controllers can detect and address the logical units (LUs) that the disk controllers present.
�DISOSS: See Distributed Office Support System.
�disparity: The relationship of ones and zeros in an encoded character. Neutral disparity indicates an equal number of ones and zeros, positive disparity indicates a majority of ones, and negative disparity indicates a majority of zeros.
�dispatch: (1) To allocate processing time on a specific device for a job that is ready to run.; (2) In CICS, to schedule a task for execution. Dispatching is done by CICS task control. See also service request block.
�dispatcher domain: Major component of CICS concerned with attaching, running, and detaching tasks and scheduling task control blocks for the various modes: quasi reentrant, resource-owning, or concurrent.
�dispatcher program: A server application that receives all incoming requests from client workstations and distributes them to agents for processing.
�dispatching priority: A number assigned to tasks, used to determine the order in which they are to use the processor in the CICS multitasking environment.
�displacement: The distance from the beginning of a record, block, or segment to the beginning of a particular field.
�display: (1) A visual presentation of data.; (2) To present data visually.; (3) To direct the output to the user's terminal. If the output is not directed to the terminal, the results are undefined.
�display attribute: In computer graphics, a property that is assigned to a display element, to a display segment, or to the complete display image; for example, a bright intensity or particular color.
�display file: A device file to support a display station.
�display format: A set of display preferences that a customer at a multicultural store can select, depending on their language and locale. For example, a multicultural commerce site may have different formats for United States English and Japanese. These display formats would differ in the language of the text as well as such features as currency, units of measure, and data formats.
�display image: In 3270 emulation, the x-character block (where x is the maximum number of characters that can fit on the display screen, or 1920 for printers) that contains data in the sequence in which it would appear on the display screen or the printer. When creating the display, the user can specify the display image with or without field definitions, such as position, length, and other attributes.
�display layout sheet: In SDA, a form used to plan the location of data on the display.
�display mode: The mode (PROMPT or NOPROMPT) in which SWIFT messages are displayed.
�display name: The name an anonymous user enters as identification. A display name is separate from a user name, and does not log the user onto the Sametime server.
�display page: (1) A page in a catalog that displays category and product information.; (2) A page in an online store that is generated in response to a command.
�display point: In the GDDM function, the smallest addressable area on the screen, sometimes called a picture element (pel), that defines the resolution of the characters or images.
�display screen: See screen.
�display session: A PC program that allows a personal computer to emulate a display station.
�display station: A device, usually equipped with a keyboard and a display device, capable of sending and receiving information over a communications line.
�display station pass-through: A communications function that allows a user to sign on to one system (such as a System i, a System/38, or a System 36 system) from another system (such as a System i, a System/38, or a System 36 system) and use that system's programs and data.
�display terminal: A host screen used by the HATS developer to observe interactions between a HATS application and a host application.
�disposition: (1) In WebSphere Commerce, disposing of or transferring inventory that has been returned to the Seller's fulfillment center by a customer. See also fulfillment center.; (2) A means of indicating to VSE/POWER how job input and output is to be handled. A job may, for example, be deleted or kept after processing.; (3) The session to which a data management event is delivered. An individual disposition is set for each type of event from each file system.
�disposition processing: A function performed on data sets at the end of a job step to keep, delete, catalog, remove from a catalog, or pass them to a subsequent job step, depending on the data set status of the disposition specified in the data definition (DD) statement.
�distance-vector routing protocol: A type of routing protocol in which each router uses the number of hops in a route to find the shortest-path spanning tree and periodically sends its entire routing table to its neighbors. See also link-state routing protocol.
�distinct type: A user-defined data type that shares a common representation with built-in data types. See also built-in data type.
�distinguished name (DN): (1) In Open System Interface (OSI), a multipart hierarchical name that can be used to identify OSI objects globally. The distinguished name of an object is formed from the sequence of its relative distinguished names (RDNs) and the name of its superior object.; (2) The name that uniquely identifies an entry in a directory. A distinguished name is made up of attribute:value pairs, separated by commas.; (3) A set of name-value pairs (such as CN=person's name and C=country or region) that uniquely identifies an entity in a digital certificate.
�distributed application: (1) In message queuing, a set of application programs that can each be connected to a different queue manager, but that collectively comprise a single application.; (2) An application made up of distinct components that are physically located on different computer systems, connected by a network. See also client/server.
�distributed build: The process of moving generated parts from the generation environment to an environment where they are prepared for execution. Preparation includes compiling, link-editing, and binding with a database as necessary.
�Distributed Command Execution Manager (DCEM): A graphical user interface (GUI) that can run commands on multiple cluster nodes simultaneously.
�distributed component object model (DCOM): An extension of the Microsoft Component Object Model (COM) to support objects distributed across a network.
�distributed computing: A method of computing in which large problems are divided into small tasks that are distributed across a network for simultaneous processing. Individual results are then brought together to form the total solution.
�Distributed Computing Environment (DCE): In network computing, a set of services and tools that supports the creation, use, and maintenance of distributed applications across heterogeneous operating systems and networks.
�distributed data: Data that is stored on more than one system and is available to remote users and application programs.
�distributed database: A database that appears to users as a logical whole, locally accessible database, but consists of databases in multiple locations that are connected by a data communications network. See also distributed file management.
�distributed data facility (DDF): A set of DB2 for z/OS components through which DB2 for z/OS communicates with another RDBMS.
�distributed data interface (DDI): An optical fiber-based LAN using the ANSI X3T9.5 standard for a token-passing ring MAC protocol and its physical attachments. Stations, concentrators, and bridges in a DDI network are physically connected to one or both of a pair of counter-rotating rings operating at 100Mbps. The term DDI is used to represent all LAN types based on the fiber distributed data interface (FDDI) specifications, regardless of the media used (optical fiber, copper, or shielded twisted pair).
�distributed data management (DDM): A function of the operating system that allows an application program or user on one system to use database files stored on remote systems. The systems must be connected by a communications network, and the remote systems must also be using DDM.
�distributed data management attribute: An attribute that is used in addition to those required for local z/OS data access. Some examples of associated DDM attributes are file size, hidden file, and lock options.
�Distributed Data Management Architecture (DDM Architecture): A connection protocol that enables communication between a system that uses distributed file management and a system that uses distributed relational database architecture.
�Distributed Directory Architecture: Directory architecture in a Domino domain in which all servers use a local primary Domino Directory.
�distributed directory database: The complete listing of all the resources in the network as maintained in the individual directories scattered throughout an APPN network. Each node has a piece of the complete directory, but it is not necessary for any one node to have the entire list. Entries are created, modified, and deleted through system definition, operator action, automatic registration, and ongoing network search procedures.
�distributed file: A file that can be accessed by remote applications or remote users.
�distributed file management: A function of the operating system that allows an application program or user on one system to use database files stored on remote systems. The systems must be connected by a communications network, and the remote systems must also be using distributed file management. See also distributed database.
�Distributed FileManager: An implementation of target (server) support as defined by distributed data management (DDM). DDM permits systems in an extended enterprise that have DDM source (client) capability to access file data on a target MVS system. See also extended enterprise, source, target.
�Distributed File Service (DFS): A component of a Distributed Computing Environment (DCE) that enables a single, integrated file system to be shared among all DCE users and host computers in a DCE cell. DFS prevents DCE users from simultaneously modifying the same information.
�distributed file service (DFS): A service that provides data access over IP networks.
�distributed function terminal (DFT): A protocol used for communication between a terminal and an IBM control unit that supports multiple, concurrent, logical, terminal sessions.
�distributed host command facility (DHCF): A function of the operating system that supports the data link between a System/370 terminal using a System i application in an HCF (Host Command Facility) environment.
�distributed library: An underlying physical library in a Peer-to-Peer Virtual Tape Server (PtP VTS) subsystem.
�distributed management environment (DME): A specification of the Open Software Foundation (OSF) for managing open systems.
�Distributed Management Task Force (DMTF): An alliance of computer vendors that was convened to define streamlined management of the diverse operating systems commonly found in an enterprise.
�distributed monitoring proxy: See proxy endpoint.
�distributed network directory: See distributed directory database.
�Distributed Office Support System (DISOSS): An IBM office systems product that helps CICS form the hub for storage, retrieval, and forwarding of documents among various office systems products.
�distributed presentation management (DPM): An MFS option that allows programs to communicate with device independence by sharing message formatting functions between MFS and a user-written remote program. The user-written remote program performs device-dependent formatting.
�Distributed Print Function (DPF): A component of Infoprint Manager for Windows that can be installed and used to print jobs from OS/390, z/OS, VSE, VM, or OS/400 systems.
�distributed processing: Processing in which resources or functions are dispersed among two or more interconnected processors, typically over a network.
�distributed program link (DPL): A function of CICS intersystem communication that enables an application program to ship LINK requests to another application program on a different instance of CICS.
�Distributed Protocol Interface (DPI): An extension to the Simple Network Management Protocol (SNMP) agent that permits users to dynamically add, delete, or replace management variables in the local Management Information Base (MIB) without requiring recompilation of the SNMP agent.
�distributed queue management: In message queuing, the setup and control of message channels to queue managers on other systems.
�distributed recovery: Resource recovery in which the resources and participants reside on multiple systems.
�distributed relational database: A database whose tables are stored on different but interconnected computing systems.
�Distributed Relational Database Architecture (DRDA): The architecture that defines formats and protocols for providing transparent access to remote data. DRDA defines two types of functions: the application requester function and the application server function.
�distributed request: In a federated database system, an SQL query directed to two or more data sources.
�distributed routing model: A "peer-to-peer" dynamic routing system, in which each of the participating CICS regions can be both a routing region and a target region. The distributed routing model is implemented by the distributed routing program.
�distributed routing program: A CICS-supplied user-replaceable program that can be used to dynamically route; BTS processes and activities, and Transactions started by non-terminal-related EXEC CICS START commands.
�Distributed Service Manager (DSM): In Tivoli Kernel Services, a component that is located at strategic places in the distributed system to keep track of services and their locations in the network. The Local Service Manager contacts the DSM to determine the location of a service in the distributed system.
�distributed shell (dsh): A program that can issue commands to all systems in a network, in parallel.
�distributed sync point resource manager (DSRM): A resource manager that extends protection to resources across multiple nodes using a peer-to-peer protocol.
�Distributed System License Option (DSLO): An option available to IBM customers with a basic license that permits them to copy certain IBM-licensed materials for the purpose of installing multiple systems.
�distributed systems node executive (DSNX): A function of the operating system that receives and analyzes requests from the NetView Distribution Manager licensed program on a host system. If the request is directed to the system that receives it, the request is processed on that system or on a personal computer directly attached to that system. If the request is intended for a different system, it is routed toward its destination.
�Distributed Time Service (DTS): A Distributed Computing Environment (DCE) component that provides a way to synchronize the times on different hosts in a distributed system.
�distributed transaction: (1) A transaction that updates data in more than one database, user process, or machine. See also two-phase commit, XA.; (2) A transaction that affects data on multiple nodes. The nodes can be on one system or across multiple systems.
�distributed transaction processing (DTP): A process that enables a CICS transaction to communicate synchronously with a transaction running in another instance of CICS.
�distributed unit of work (DUOW, DUW): (1) A unit of work that allows SQL statements to be submitted to multiple relational database management systems, but no more than one system per SQL statement.; (2) In a distributed process, all processing between two syncpoints taken by two or more intercommunicating transactions using a two-phase commit protocol. A DUW is a distributed LUW.
�distribution: A software package that is ready to install. A distribution often refers to a Linux package that contains the Linux operating system, an installation program, utilities, and documentation.
�distribution array: An arrangement of entries that indicates the number of records that are hashed into a hash index. See also distribution file.
�distribution catalog: A list of objects, with references to their locations and associated object characteristics.
�distribution document: An internal document that contains the document content and the document details for a distribution, such as a note or document.
�distribution file: A file that stores a distribution array. See also distribution array.

�distribution key: An ordered set of one or more columns in a given table. The values in the distribution key columns are used to determine the database partition to which each table row belongs. See also table-partitioning key.
�distribution library (DLIB): In z/OS, a data set from which a product is copied to the target library (TLIB) during installation.
�distribution list: (1) A list of system distribution directory entries, which allows users to send messages, notes, and documents to a group of users in one step.; (2) In voice mail, a list of subscribers to whom the same message can be sent.; (3) A list of queues to which a message can be put using a single MQPUT or MQPUT1 statement.
�distribution map: A map that specifies an array of database partition numbers that is used to distribute data among the database partitions of a database partition group. The array of database partition numbers distributes the data by using a hashing algorithm.
�distribution media: (1) The medium on which the operating system software, a licensed program, or an application program is distributed to the user. The distribution medium can be any of several different media supported by the hardware, such as streaming cartridge tape, 9-track tape, or 3.5-inch diskette.; (2) The media that a central site creates and distributes to target systems. See also installation media.
�distribution program
�distribution queue: In SNADS, a list of documents or mail waiting to be sent to users or libraries on remote systems.
�distribution recipient index: See distribution recipient queue.
�distribution recipient queue: An internal object that contains entries for incoming object distributions; incoming document distributions, such as files, notes, or messages; outgoing document distributions; and error distributions.
�distribution repository: In Managed System Services, a staging area for objects that are to be sent or have been received. Objects are loaded into the repository to be sent to managed systems at a later time.
�distribution requisite fix: A temporary solution to or a bypass of a problem that is necessary to provide a complete solution to correct a problem. The system allows you to apply the distribution requisite fix either before the PTF that needs it, with the PTF that needs it, or after the PTF that needs it. See also corequisite fix, prerequisite fix.
�distribution service level: In SNADS, the combination of priority, capacity, and protection requirements that must be satisfied to receive or send a distribution. SNADS has service levels of fast, status, data high, and data low. Items with a service level of fast, status, or data high are put on the priority queue. Items with a service level of data low are put on the normal queue.
�distribution services: The support provided by the operating system to receive, forward, and send electronic mail in an SNA network.
�distribution summary array: An array that includes a distribution array and a distribution map and that indicates the number of records that are hashed into a database partition.
�distribution tracking object: An internal object that is used to control electronic mail.
�distribution zone: In SMP/E, a group of VSAM records that describe the structure and contents (that is, the system modifications and elements) of a set of distribution libraries.
�distributor: In WebSphere Commerce, an indirect seller of products, in the context of the demand chain business model. A distributor does not sell directly to end users of the product, but only to other sellers, such as resellers.
�distributor proxy store: A store that acts as a placeholder for an external distributor store, allowing resellers to conduct business indirectly by way of the proxy store. See also proxy store.
�DITTO utility: See Data Interfile Transfer, Testing and Operations utility.
�division header: In COBOL, the reserved words and punctuation that indicate the beginning of one of the four divisions of a COBOL program.
�DJC: See dependent job control.
�DJC network: See dependent job control network.
�DJ facility: See dump job facility.
�DKC: The service code (Field SW103) for the Danish RTGS system; used as an access to TARGET.
�DLA: See discovery library adapter.
�DLBL statement: Data definition statement in VSE JCL. A DLBL statement specifies the name and characteristics of a data set to be associated with a file definition in the FCT. The name of the DLBL statement is the same as the name of the file definition.
�DLC: (1) See data link control.; (2) See data link control protocol.
�DLCI: See data link connection identifier.
�DLC layer: See data link control layer.
�DLE: See data link escape character.
�DLE character: See data link escape character.
�DL/I: See Data Language/I.
�DL/I address space: An address space that is used by the online IMS control program to contain most of the DL/I code and control blocks. This option can be selected for the online IMS environment to provide an alternative virtual storage configuration.
�DLIB: See distribution library.
�DL/I backout table (DBO): In the restart data set, a summary table that contains an entry for each in-flight task that was scheduled to alter a local DL/I database. Data in this table is available to user-written exit programs.
�DL/I database directory (DDIR): List of data management blocks (DMBs) that define for DL/I the physical and logical characteristics of databases.
�DL/I interface block (DIB): A block containing variables automatically defined in an application program using HLPI to receive information passed to the program by DL/I during execution. A block automatically inserted into a program by the DLI command translator. Whenever a program issues an EXEC DLI request, DLI responds by storing information in the DIB.
�DLISAS: See DLI separate address space.
�DLI separate address space (DLISAS): A component of DBCTL that resides in the IMS address space. It is a separate address space that contains DL/I code, control blocks, buffers for DL/I databases and program isolation.
�DLL: See dynamic link library.
�DLL filter: A filter that resides in a dynamic link library (DLL) and that can inspect input data and perform various functions, such as convert data formats, add header pages, and specify job attributes. See also filter, UNIX filter.
�DLO: See document library object.
�DLPAR: See dynamic LPAR.
�DLR: See discovery library reader.
�DLS: See dynamic load sharing.
�DLU: (1) See dependent logical unit.; (2) See destination logical unit.
�DLUR: See dependent logical unit requester.
�DLUS: See dependent logical unit server.
�DM: See disconnected mode.
�DMA: See direct memory access.
�DMAPI: See data management application program interface.
�DMB: See data management block.
�DME: See distributed management environment.
�DMH: See device message handler.
�DMI: See Desktop Management Interface.
�DML: See Data Manipulation Language.
�DMP: See Dataradio Multiplex Protocol.
�DMS100: (1) A Northern Telecom switch.; (2) The custom ISDN protocol implemented on the DMS100 switch, providing 23 B-channels and a D-channel over a T1 trunk.
�DMS table space: See database-managed space table space.
�DMTF: See Distributed Management Task Force.
�DMZ: See demilitarized zone.
�DN: See distinguished name.
�DNA: See Digital Network Architecture.
�DNIC: See data network identification code.
�DNIS: See dialed number identification service.
�DNS: See Domain Name System.
�DNS domain database file: A configuration file that contains information about the domain, such as resource records, that a server administers.
�DNS resolution: Domain Name System resolution. The process of performing a Domain Name System lookup to resolve unrecognized IP addresses to a host name.
�DNS server cache: Periodically updated information on a name server that contains data about the domain that the name server administers.
�DO: See derived object.
�DOCID: See document ID.
�docking station: A hardware device that enables a mobile computer to function as a desktop computer. For example, a peripheral device (such as an external monitor, an external modem, or external speakers) can be connected to a mobile computer via its docking station.
�document: (1) Any collection of data stored in a document object. A document can contain any type of data. For example, the System i Access shared folders function can store any data that could otherwise be stored in a PC file; a server application can store any data into a document by using CL commands, such as FILDOC and RPLDOC. The system-recognized identifier for the document object type is *DOC. See also document library object.; (2) A machine-readable collection of one or more objects that represent a composition, a work, or a collection of data.; (3) An item that can be stored, retrieved, and exchanged among Content Manager systems and users as a separate unit. It can be any multimedia digital object. A single document can include varied types of content, including for example, text, images, and spreadsheets. See also workbasket, workflow.; (4) A logical structure that a CICS transaction can use to manipulate text or other structured information. See also document template.; (5) A Notes database entry that users create by using a form on the Create menu. Documents consist of fields, text, numbers, graphics, and so on. Information may be entered by a user, automatically calculated by formulas, imported from other applications, or linked to another application and dynamically updated.; (6) A business document, such as a purchase order or invoice, that can be represented in any supported format. For example, an XML purchase order and an EDI purchase order are both documents, but each uses a different format.; (7) An attachment of any medium such as a text file, a spreadsheet, graphics, videos, or a URL that can be appended to an element in the work breakdown structure (WBS), a resource record, scope element or requirement.
�document access definition (DAD): An XML document format used by DB2 XML Extender to define the mapping between XML and relational data.
�document access definition extension (DADX): (1) An XML document format that specifies how to create a Web service using a set of operations that are defined by DAD documents and SQL statements.; (2) A configuration file that controls both XML-based and SQL-based forms of querying by defining the operations that can be performed by a Web service.
�document authority: The definition of what actions a user can perform on a document.
�document class: A user-defined character string, 1 through 16 characters long, that characterizes a document. It can be used to search for a filed document. For example, a document that is a memo could have a document class of MEMO; a document that is a report, REPORT.
�Document Composition Facility (DCF): An IBM licensed program used to format input to a printer.
�Document Content Architecture (DCA): An architecture that guarantees information integrity for a document being interchanged in an office system network. DCA provides the rule for specifying form and meaning of a document. It defines revisable form text (changeable) and final form text (unchangeable).
�document definition: A description of a document layout that is used to identify the format of a document. Examples include record oriented data document definitions, EDI document definitions, XML schema document definitions, and XML DTD document definitions.
�document description: The 1- through 44-character description of a document, assigned by the user when creating or filing the document.
�document detail: Data that describes a characteristic of a document. For example, a detail can be document type, subject, author, or date created.
�document flow definition: A collection of information specified for each type of document that tells the hub how to process that particular type of document. Each document to be exchanged between the internal partner and a participant must have a document flow definition.
�document format: The selected arrangement of text for a specific document.
�document ID (DOCID): (1) A unique identifier for a document.; (2) A value that uniquely identifies a row that contains an XML column. This value is stored with the row and never changes.
�Document Interchange Architecture (DIA): The rules and structure for the exchange of information between office applications. Document Interchange Architecture includes document library services and document distribution services.
�document interchange session: The environment that allows office system users and System i Access users to request document library and distribution services from the host system.
�document library: The entire collection of documents and folders on a system.
�document library object (DLO): Any system object that resides in the document library, such as RFT and FFT documents, folders, and PC files. See also document.
�document library services: The services defined by the Document Interchange Architecture (DIA) to work with objects filed in the DIA document library. On the system, it is the support that lets users work with the contents of the document library.
�document model: The definition of the structure of a document in terms of the sections that it contains. DB2 Net Search Extender uses a document model when indexing.
�document name: The 1- through 12-character name for documents in folders, assigned by the user when creating the document. See also document object name.
�document number: The number assigned to a printed document when a user files that document. The first two digits of the document number are the year, and the last five are in sequence, with the most recent documents having the highest number. For example, the fifth printed document filed in 1989 would have the number 89-00005.
�Document Object Model (DOM): A system in which a structured document, for example an XML file, is viewed as a tree of objects that can be programmatically accessed and updated.
�document object name: The 10-character name of a document assigned by the system when a user files the document. See also document name.
�document order: In XQuery, an ordering among the nodes in a node hierarchy that corresponds to the order in which the nodes would appear if the node hierarchy were serialized in XML format.
�document outline: A reference document or template used to create new documents. See also document type.
�Document Printing Application (DPA): An OSI standard (ISO/IEC 10175) that addresses those aspects of document processing that enable users in a distributed open systems environment to send electronic documents to shared, possibly geographically-dispersed, printers.
�document root directory: The primary directory in which a Web server stores accessible documents. When the server receives requests that do not point to a specific directory, it tries to serve the requests from this directory.
�document routing process: In Content Manager a sequence of work steps, and the rules governing those steps, through which a document or folder travels while it is being processed. See also work step.
�document template: A unit of information that is used to construct a document. A document template can contain fixed text, and symbols that represent text whose value is supplied by an application program. Document templates can be created by a CICS application, or retrieved from an external source. See also document.
�document type: A template for a specific type of requirements document. The document type uses the document outline and specifies the filename extension. See also document outline.
�document type definition (DTD): (1) The definition of a non-Document Interchange Architecture (DIA) document user type that identifies the document type number, name, and text associated with the document.; (2) The rules that specify the structure for a particular class of SGML or XML documents. The DTD defines the structure with elements, attributes, and notations, and it establishes constraints for how each element, attribute, and notation can be used within the particular class of documents.
�document type set: A value that allows a logical grouping of document type definitions. Document type sets include the name and the description. A set can contain one or more document types or it can be empty.
�document unit object: An internal object that contains the document content and the document details.
�DOF: See device output format.
�DO group: (1) A set of commands in a control language program defined by a DO command and an ENDDO command that is conditionally processed as a group.; (2) In RPG, a group of calculations done one or more times based on the results of comparing factor 1 and factor 2 of certain calculation operations (for example, DOUxx). A DO operation and an END operation are the delimiters for a do group.
�DOI: See Domain of Interpretation.
�DO loop: A range of statements run repetitively by a DO statement.
�DOM: See Document Object Model.
�domain: (1) A characteristic of an object that controls which programs can access the object. See also system domain object, user domain object.; (2) A set of systems that allocate shared network resources within a single logical system.; (3) In communications, the network resources under control of a particular system services control point (SSCP).; (4) In TCP/IP, a named set of hosts. Each domain has authority for the machines within that domain, but not for machines in other domains.; (5) In a database, the set of valid values for an attribute.; (6) A logical grouping of resources in a network for the purpose of common management and administration.; (7) In the Internet, a part of a naming hierarchy in which the domain name consists of a sequence of names (labels) separated by periods (dots).; (8) A part of a network that is administered as a unit with a common protocol.; (9) A functionally isolated area of the CICS system that owns resources to which it has sole access and that communicates with other parts of CICS through strictly defined interfaces called gates.; (10) An object, icon, or container that contains other objects representing the resources of a domain. The domain object can be used to manage those resources.; (11) An area of knowledge or activity characterized by a family of related values.
�domain administrator: The owner of an administrative domain.
�domain control database (DCDB): A database that resides on the domain controller and contains files that describe and control the current domain. The DCDB contains files, applications, and machine definitions.
�domain-defined attribute: In OSI X.400, an attribute of the X.400 originator/recipient name that permits a System i product to keep existing addressing conventions. The System i product uses the domain-defined attributes to carry the user ID and address (the two-part network name used in SNADS).
�domain discovery server: A discovery server that is used within a network of discovery servers, which contains data about a subset of the configuration items in the network, and passes data to an enterprise discovery server.
�domain expert: A role in the pre-defined workflow process shipped with WebSphere Portal content publishing. Users assigned to the role of Domain Expert are responsible for providing editorial approval of content before publishing to the Web.
�domain gate: An entry point or interface to a CICS domain. A domain gate can be called by any authorized caller who needs to use some function provided by the domain.
�domain manager domain: Major component of CICS responsible for maintaining, through the use of catalog services, permanent information about individual domains.
�domain model: A model that captures the most important types of objects in the context of the domain. The domain objects represent the entities that exist or events that transpire in the environment in which the system works. The domain model is a subset of the business analysis model.
�domain name: In Internet communications, a name of a host system. A domain name consists of a sequence of subnames that are separated by a delimiter character, for example, www.ibm.com. See also Domain Name System.
�domain name server: In Internet communications, a server program that supplies name-to-address conversion by mapping domain names to IP addresses.
�domain name space: All of the names in the Domain Name System (DNS).
�Domain Name System (DNS): The distributed database system used to map domain names to IP addresses. See also domain name.
�Domain of Interpretation (DOI): A group of related protocols that uses the Internet Security Association and Key Management Protocol (ISAKMP) to negotiate Security Associations (SAs). A DOI defines payload formats, exchange types, and conventions for naming security-relevant information such as security policies and cryptographic algorithms and modes.
�domain term: A group of usually consecutive subject-specific terms that can be mechanically recognized and annotated by the text analyzer without the context of the sentence structure. Domain terms can be built into two types of dictionaries, one being a standard format lexical dictionary, another being multiword format dictionary.
�DOM element: One member of a tree of elements that is created when an XML file is parsed with a DOM parser. DOM elements make it easy to quickly identify all elements in the source XML file.
�Domino Application Services: Services that enable the Sametime server to function in a Domino environment as part of a Domino domain. The Domino Application Services support Lotus Notes access to the Sametime server, the Directory, Replication features, and security for Lotus Notes clients. The Web Application Services and Domino Application Services are sometimes collectively referred to as Domino DNA.
�Domino connector: A function of the HTTP Server for i5/OS licensed program that enables Lotus Notes users to access the Internet and to use all of the HTTP Server functions. Specifically, a Domino connector enables Lotus Notes users to combine Notes with e-business applications.
�Domino directory: A database that provides a domain-wide directory of Domino servers, users, certifiers, foreign domains, and groups. It also contains documents that manage server-to-server communication and server programs.
�Domino Document Manager cabinet: A Domino Document Manager database that is used to organize documents. Cabinets hold Domino databases.
�Domino Document Manager library: A Domino Document Manager database that is the entry point to Domino Document Manager.
�Domino domain: A network of clients and servers whose users, servers, connections, and access control information are described in a Domino directory.
�Domino for i5/OS: See Lotus Domino for i5/OS.
�Domino Internet Inter-ORB Protocol (DIIOP): A server task that runs on the server and works with the Domino Object Request Broker to allow communication between Java applets created with the Notes Java classes and the Domino server. Browser users and Domino servers use IIOP to communicate and to exchange object data.
�Domino server: A computer that runs the Domino Server program and stores Notes databases.
�Domino server program: The program that supports the connection between clients and the server and also manages a set of server tasks, which are programs that either perform schedule-driven database chores -- such as routing messages to mailboxes and updating user accounts -- or connect various types of clients -- Notes clients, Web browsers, CORBA clients -- to the server.
�Domino Server setup program: The cross-platform wizard that guides a user through the setup options for a Domino server after the program files are installed on the system.
�Domino XML: A version of XML that describes Domino-specific data and design elements such as embedded views, forms, and documents.
�DOR: See data-owning region.
�dormant state: In DB2 for i5/OS, the state of a connection when the connection is suspended. While in the dormant state, no SQL statements use the connection except for commits and rollbacks. See also current state.
�DOS: See disk operating system.
�DOS bit: On a volume without an indexed volume table of contents (VTOC), a bit that indicates that the free space map is invalid.
�DOS session: A session that supports the independent running of a DOS program. The DOS program appears to run independently of any other programs in the system.
�do statement: For the C and C++ compilers, a looping statement that contains the keyword do, followed by a statement (the action), the keyword while, and an expression in parentheses (the condition).
�dot: A symbol (.) that indicates the current directory in a relative path name. See also period.
�dot dot: A symbol (..) in a relative path name that indicates the parent directory.
�dot matrix: (1) In computer graphics, a two-dimensional pattern of dots that are used for designing an image on the display.; (2) In word processing, a pattern of dots used to form characters.
�dotted decimal notation: The syntactical representation for a 32-bit integer that consists of four 8-bit numbers written in base 10 and separated by dots. IP addresses are represented in dotted decimal notation. See also octet.
�double-byte character: An entity that requires two character bytes.
�double-byte character large object (DBCLOB): A data type that contains a sequence of double-byte characters that can range in size from 0 bytes to 2 gigabytes less one byte. This data type can be used to store large double-byte text objects.
�double-byte character set (DBCS): A set of characters in which each character is represented by two bytes. These character sets are commonly used by national languages, such as Japanese and Chinese, that have more symbols than can be represented by a single byte. See also single-byte character set, multibyte character set.
�double-byte coded font (double-byte font): A font in which the characters are defined by 2 bytes. The first byte defines the coded font section; the second byte defines the code point in the code page specified for that section.
�double-byte font: See double-byte coded font.
�double-click: To press and release a mouse button twice in rapid succession in order to perform an operation.
�double-dot image: In printing, an image that is enlarged by doubling the pel pattern horizontally and vertically.
�double-precision: Pertaining to the use of two computer words to represent a number in accordance with the required precision.
�double-precision floating-point number: A 64-bit approximate representation of a real number. See also floating-point number.
�double quote: See quotation mark.
�double recording: The recording of certain individual events under two resource levels.
�double-trunking: See trombone.
�doubleword: A contiguous sequence of bits or characters that comprises two computer words and is capable of being addressed as a unit. See also halfword, word.
�doubleword boundary: A storage location whose address is evenly divisible by 8. See also word boundary.
�do-while loop: A loop that repeats the same sequence of activities as long as some condition is satisfied. Unlike a while loop, a do-while loop tests its condition at the end of the loop. This means that its sequence of activities always runs at least once.
�down: The condition in which a device is unusable as a result of an internal fault or an external condition, such as loss of power.
�downcall: In a Tivoli environment, a method call from the gateway to the endpoint. See also upcall.
�downline: Pertaining to devices that are below a controller, and controllers that are below a communications line in a communications configuration. See also upline.
�download: To transfer data from a computer to a connected device, such as a workstation or personal computer.
�downstream: (1) Pertaining to the direction of data flow, which is toward the destination of a transmission. See also upstream.; (2) Pertaining to the direction of the flow, which is from the first node in the process (upstream) toward the last node in the process (downstream).
�downstream physical unit (DSPU): Any remote physical unit (data link, storage, or input/output device) attached to a single network host system.
�downtime: The time during which a functional unit cannot be used because of a fault within the functional unit or within the environment.
�downward-growing stack: With Extra Performance Linkage (XPLINK), a stack that grows from high addresses to low addresses in memory.
�DPA: See Document Printing Application.
�DPAGE: See device page.
�DPC: See destination point code.
�DPF: (1) See Distributed Print Function.; (2) See Database Partitioning Feature.
�DPI: See Distributed Protocol Interface.
�DPL: See distributed program link.
�DPM: See distributed presentation management.
�DPSI: See data-partitioned secondary index.
�DPSS: See Direct Printer Services Subsystem.
�DR: (1) See definite response.; (2) See dynamic reconfiguration.
�DR1I: See definite response 1 indicator.
�DR2I: See definite response 2 indicator.
�DRA: See database resource adapter.
�DRA control exit: Enables the DRA to pass information from itself and DBCTL independently of CICS. It is invoked whenever the DRA needs to determine whether to continue processing.
�draft: An incomplete offering that is a work in progress. A draft must be published before it can be used to complete a service level agreement.
�draft offering: An offering that is a work-in-progress and that is not yet ready to be published and made available to customers in a service level agreement (SLA).
�drag: To use a pointing device to move an object. For example, a user can drag a window border to make it larger by holding a button pointing device while moving the pointing device.
�drain: (1) The act of acquiring a locked resource by quiescing access to that object. See also claim, logical drain.; (2) An operator action to halt the flow of jobs to a printer, usually to stop the printer or to change print options.; (3) To honor pending allocation requests before deactivating sessions with a partner logical unit. This applies to LU 6.2 only.
�drained state: The condition in which job flow to the printer is stopped until the operator enters a command, such as START, to begin sending jobs to the printer.
�drain lock: A lock on a claim class that prevents a claim from occurring.
�DRAM: See dynamic random access memory.
�DRA startup parameter table: Provides the parameters needed to define a DBCTL subsystem.
�drawer: A unit that contains multiple disk drive modules (DDMs) and provides power, cooling, and related interconnection logic to make the DDMs accessible to attached host systems.
�drawing character: In System i Access, a keyboard character that is placed in the cursor position after the cursor is moved with the cursor movement key.
�drawing tool: A tool used on the whiteboard to draw a line, a circle, or to change colors.
�DRDA: See Distributed Relational Database Architecture.
�DRDA1: The first stage of Distributed Relational Database Architecture (DRDA). In this stage, an application or user on one system can, within a single unit of work, read update data on a single DBMS.
�DRDA2: The second stage of Distributed Relational Database Architecture (DRDA).
�DRDA access: An open method of accessing distributed data that can be used to connect to another database server to execute packages that were previously bound at the server location.
�drill down: To access information by starting with a general category and moving through the hierarchy of information. For example, in a database, to move from field to file to record.
�drive: The mechanism used to seek, read, and write information on a storage medium.
�drive bay: A receptacle in an appliance for a hard-disk-drive module. The drive bays are in storage units that can be located in a different rack from the appliance.
�drive definition: A set of attributes used to define an optical disk drive as a member of a real optical library or pseudo optical library.
�drive designation: A letter (from A to Z) that an operating system assigns to a disk, a partition, or a network directory to give the system a unique way to refer to the resource.
�driver: (1) A circuit that increases the signal current for sending data over long cables or to many other circuits.; (2) A circuit that sends small electronic signals to a device.
�driving system: The system image (hardware and software) that is used to install the target system.
�drop-down: Pertaining to a list or menu that opens when clicked and stays open until the user selects a menu or list item or clicks elsewhere in the user interface.
�drop-in grammar: A set of precompiled grammar rules that can be used by an application-specific grammar to improve the recognition performance.
�dropping: In QoS, the simplest form of traffic conditioning where noncompliant packets are discarded.
�DSA: (1) See directory system agent.; (2) See dynamic storage area.; (3) See digital signature algorithm.
�DSAP: See destination service access point.
�DSCA: See default system control area.
�DSCB: See data set control block.
�DSD: See Dedicated Server for Domino.
�DSE: See dependent service element.
�DSECT: See dummy control section.
�dsh: See distributed shell.
�DSI: See dynamic system interchange.
�DSL: (1) See Digital Subscriber Line.; (2) See definitive software library.
�DSLO: See Distributed System License Option.
�DSM: See Distributed Service Manager.
�DSML: See Directory Services Markup Language.
�DSN: See default subsystem name.
�dsname: See data set name.
�DSNAME block (DSNB): See data set name block.
�DSNB (DSNAME block): See data set name block.
�DSNX: See distributed systems node executive.
�DSORG: See data set organization.
�DSP: (1) See digital signal processing.; (2) See dynamic support program.
�D-specification: A piece of ILE RPG code that defines program items, such as standalone fields, named constants, and data structures with or without a subfield.
�DSPU: See downstream physical unit.
�DSQ: See destination queue.
�DSR: See data set ready.
�DSRLST: See direct search list.
�DSRM: See distributed sync point resource manager.
�DSSN: See data set sequence number.
�DST: See dedicated service tools.
�DST-restricted state: The status of the system before an initial program load (IPL) of the operating system is performed. Only dedicated service tools functions are allowed when the system is in the DST-restricted state.
�DSU: (1) See Data Description Specifications Design Utility.; (2) See data service unit.
�DSU/CSU: See data service unit/channel service unit.
�DTB: See dynamic transaction backout.
�DTD: See document type definition.
�DTD document definition: A description or layout of an XML document based on an XML DTD.
�DTE: See data terminal equipment.
�DTE address: An address that identifies a specific line attached to a given node on an X.25 network. DTE addresses are assigned by the network supplier.
�DTE attribute: In OSI, an attribute specified by the local node to regulate connection requests with an adjacent node on an X.25 subnetwork.
�DTF: (1) See define the file.; (2) See Data Transformation Framework.
�DTMF: See dual-tone multifrequency.
�DTP: See distributed transaction processing.
�DTQA: See Digital Trunk Quad Adapter.
�DTR: See dynamic transaction routing.
�DTS: See Distributed Time Service.
�DTSE in: See detected access transmission error in.
�DTS entity: In the DCE Distributed Time Service, the server or clerk software on a system.
�DTSE out: See detected access transmission error out.
�DUA: See directory user agent.
�dual-attachment station (DAS): A station that offers two attachments to a network, to both an upstream and a downstream neighbor, and is therefore capable of accommodating a dual ring.
�dual authorization: A setting requiring that an action carried out by one person be confirmed by a second person. This prevents a single person from being able to carry out actions requiring a high level of security, for example the distribution of funds or the granting of access rights. See also single authorization.
�dual copy: A high availability function that maintains two functionally identical copies of designated direct access storage device (DASD) volumes and automatically updates both copies every time a write operation is issued to the dual-copy logical volume (LVOL).
�dual display: The simultaneous display of a monetary amount in the shopping currency, and one or more counter value amounts in a different currency.
�dual-homed host: See multihomed host.
�dual inline memory module (DIMM): A small circuit board with memory-integrated circuits containing signal and power pins on both sides of the board. See also single inline memory module.
�dual-line call transfer: (1) A call transfer method in which the primary and secondary lines remain bridged until a call is completed.; (2) See trombone.
�dual logging: (1) An optional facility that produces a duplicate copy of log data.; (2) A method of recording WebSphere MQ for z/OS activity, where each change is recorded on two data sets, so that if a restart is necessary and one data set is unreadable, the other can be used. See also single logging.
�dual mode: See dual logging.
�DUAL mode: A checkpointing mode that provides the alternate use of two primary checkpoint data sets (CKPT1 and CKPT2). The datasets are referred to as the to-be-read-from and to-be-written-to data sets.
�dual-purpose definition: For transaction routing or function shipping, a means of sharing file, terminal, or transaction definitions between systems.
�dual-screen: Running EDF and the transaction to be tested on different terminals.
�dual-tone multifrequency (DTMF): The signals sent by pressing one of the telephone keys. Each signal is composed of two different tones.
�dub: To make an MVS address space known to z/OS UNIX. See also undub.
�due date: In Passport Advantage, the date on which payment is due.
�dummy argument: In Fortran, a variable within a subprogram or statement function definition with which actual arguments from the calling program or function reference are positionally associated. See also actual argument.
�dummy control section (DSECT): A control section that an assembler can use to format an area of storage without producing any object code.
�dummy device: In the GDDM function, an imaginary output device for which the program does all the normal processing but for which no actual output is received.
�dummy storage group: A type of storage group that contains the serial numbers of volumes no longer connected to a system. Dummy storage groups allow existing job control language (JCL) code to function without having to be changed.
�dump: (1) To record or copy, at a particular instant, data from one storage device onto another storage device to protect the data and debug the program.; (2) To copy the contents of all or part of visual storage for the purpose of collecting error information.; (3) Data that is copied in a readable format from main or auxiliary storage to an external medium such as tape, diskette, or printer.; (4) A representation of the contents of selected areas of main storage used to find out whether a program is functioning as intended and to analyze problems. Dumps may be recorded by CICS either as a consequence of failure detected during CICS execution, or upon explicit request. See also partition dump.; (5) A capture of storage information at the time of an error.
�dump analysis and elimination (DAE): A z/OS service that enables an installation to suppress SVC dumps and ABEND SYSUDUMP dumps that are not needed because they duplicate previously written dumps.
�dump class: A set of characteristics that describes how volume dumps are managed by DFSMShsm.
�dump code: (1) In CICS Transaction Server, a predefined name by which a dump is known. There are two types of dump code, transaction dump codes and system dump codes, used in transaction dumps and system dumps, respectively. A dump code can be defined by CICS or the user and is used to select a set of system actions. These actions are held in either the system or transaction dump table. See also system dump code, system dump table, transaction dump code, transaction dump table.; (2) In CICS/VSE, a predefined name by which a transaction dump is known.
�dump copy: In DFSMShsm, a copy of the volume image produced by the DFSMSdss full-volume-dump function.
�dump cycle: In DFSMShsm, the frequency, in days, with which automatic full-volume dumps are performed.
�dump data set: A sequential data set (optional) used to record dumps of transactions (tasks) within the system. It can be formatted and printed by the CICS dump utility program (DFHDUP). If required, the user can define two dump data sets (DFHDMPA and DFHDMPB), switching between them during online execution of CICS.
�dump domain: Major component of CICS responsible for producing storage dumps and for handling the associated data sets and dump tables.
�dump generation: A successful full-volume dump of a volume that may contain one to five identical dump copies.
�dump job facility (DJ facility): A dynamic support program (DSP) that copies jobs to tape, or restores jobs to the system.
�dump media: The diskette or the tape to which the user writes the storage dumps.
�dump table: A table of dump codes to enable a user to vary the system actions taken when a dump is produced for a particular dump code.
�dump utility program (DFHDUP): An offline utility program that formats and prints the output from formatted dump, and prints transaction dumps. It operates in batch mode and, for formatted dumps, identifies each storage area, program, and table entry, and prints them separately, with actual and relative addresses.
�dump VTOC copy data set: A copy of the volume table of contents (VTOC) of a volume dumped by DFSMShsm. The dump VTOC copy data set contains only part of the data-set VTOC entry for each data set from the original data set. This data set is written on a migration-level-1 volume.
�DUNS: See Data Universal Numbering System.
�DUOW: See distributed unit of work.
�duplex: (1) Pertaining to communication in which data can be sent and received at the same time. See also half-duplex.; (2) Pertaining to printing on both sides of a sheet of paper.; (3) Pertaining to the process of writing two sets of identical records in order to create a second copy of data.; (4) In ESS Copy Services, the state of a volume pair after Peer-to-Peer Remote Copy (PPRC) has completed the copy operation and the volume pair is synchronized.
�duplex pair: A volume comprised of two physical devices within the same or different storage subsystems that are defined as a pair by a dual copy, Peer-to-Peer Remote Copy (PPRC) or extended remote copy (XRC) operation. A duplex pair is in neither suspended nor pending state. The operation records the same data onto each volume.
�duplicate key value: The occurrence of the same value in a key field or in a composite key in more than one record in a file.
�durability: After a transaction completes successfully (commits), its changes to the state survive failures. See also ACID property.
�durable: Pertaining to a transaction that ensures that data is persistent, both before and after the transaction, regardless of success or failure.
�durable subscription: A Java Message Service (JMS) subscription that persists and stores subscribed messages even when the client is not connected.
�duration: (1) In SQL, a number that represents an interval of time.; (2) In Backup, Recovery, and Media Services, the length of time that the designated media is to reside at a location before moving to the next location or returning to the home location. A duration is specified in the move policy.
�DUW: See distributed unit of work.
�DVD: See digital video disc.
�DVI: See Digital Video Interactive.

�DWDM: See dense wavelength division multiplexing.
�DWE: See deferred work element.
�DWS: See Data Window Services.
�dynaform: An instance of a DynaActionForm class or subclass that stores HTML form data from a submitted client request or that stores input data from a link that a user clicked.
�dynamic: (1) Pertaining to events that occur at run time or during processing.; (2) Pertaining to an operation that occurs at the time it is needed rather than at a predetermined or fixed time. See also static.
�dynamic access: (1) In COBOL, an access method in which specific logical records can be obtained from or placed into a mass storage file in a nonsequential manner and obtained from a file in a sequential manner during the scope of the same OPEN statement.; (2) A process where records can be accessed sequentially or randomly, depending on the form of the input/output request. See also access mode.
�dynamic allocation: (1) Facility of IMS Version 2.2 (or later) and of CICS Transaction Server, for allocating DL/I databases and CICS file control data sets, respectively. If no DD statement is provided for the database data sets contained in the database, allocation happens automatically when the database is scheduled.; (2) Assignment of system resources to a program when the program is executed rather than when it is loaded into main storage. See also step allocation.
�dynamically loaded program: Program loaded into a dynamic storage area as required by a task.
�dynamic analysis: The process of extracting targeted types of information based on the results of process simulations. This differs from static analysis, which extracts information from model elements in their static form.
�dynamic assembly: A process that selects specific endpoints to meet the conditions of a service request at runtime.
�dynamic attribute: A node attribute with a value that can change over time, such as node power status.
�dynamic backout: A process that automatically cancels all activities performed by an application program that terminates abnormally. See also backout.
�dynamic bind: A process by which SQL statements or XQuery expressions are bound when they are executed. See also static bind, automatic bind.
�dynamic binding: The act of resolving references to external variables and functions at run time. In C++, dynamic binding is supported by using virtual functions.
�dynamic buffer: Used to store backout information in the dynamic log for dynamic transaction backout (DTB) purposes. The dynamic buffer is not acquired until a recoverable resource has been modified. If dynamic backout is not defined for a transaction, the dynamic buffer is not used.
�dynamic buffering: A user-specified option that causes the system to be responsible for acquisition, assignment, and the release of buffers.
�dynamic cache: A consolidation of several caching activities, including servlets, Web services, and WebSphere commands into one service where these activities work together to improve performance and share configuration parameters.
�dynamic cache management (DCM): A function that automatically determines which data sets will be cached based on the system load, the characteristics of the data set, and the performance requirements defined by the storage administrator. See also DASD fast write.
�dynamic call: A type of call that locates a specified routine during run time. The routine is loaded into virtual storage. See also static call.
�dynamic classification: A semantic variation of generalization in which an object may change type or role. See also multiple classification, static classification.
�dynamic cluster: A server cluster that uses weights to balance the workloads of its cluster members dynamically, based on performance information collected from cluster members.
�dynamic cluster isolation: The ability to specify whether the dynamic cluster runs on the same nodes as other instances of dynamic clusters, or if the dynamic cluster is the only dynamic cluster that runs on a single node.
�dynamic connection: (1) A virtual private network (VPN) connection that automatically refreshes the keys that keep data secure. A dynamic connection also contains proposals that allow the key server to negotiate which parameters to use with the remote key server. See also manual connection.; (2) A connection created at the time of sign-on or using the network connection control (NCC) record sent from another node.
�dynamic context: The information that is available at the time that an XQuery expression is evaluated. The dynamic context consists of all of the components of the static context, plus additional components such as the context item, context position, and context size. See also expression context, static context.
�dynamic cursor: A named control structure that an application program uses to change the size of the result table and the order of its rows after the cursor is opened. See also cursor, static cursor.
�dynamic data exchange (DDE): The exchange of data between programs or between a program and a data-file object. Any change the user makes to information in one program or session is applied to the identical data created by the other program. For example, with the DDE feature enabled, the user can select the copy of a spreadsheet that is embedded in a report. If the user makes changes to the copy of the spreadsheet in the report, the changes are made to the original spreadsheet file.
�Dynamic Data Format: A format used to package LOB or XML values sent by a database server, capable of holding the actual value, a reference to the value following later in the stream of data, or a token representing the value for later retrieval. See also progressive streaming.
�dynamic data object (DDO): In an application program, a generic representation of a stored object that is used to move that object in to, and out of, storage.
�dynamic data stream transformation: In WebFacing, the use of a separate process to convert 5250 display data into a format compatible with Web browsers.
�dynamic deallocation: Freeing of system resources during program execution rather than at the end of the job.
�dynamic device reconfiguration (DDR): A facility that allows a demountable volume to be moved, and repositioned if necessary, without abnormally terminating the job or repeating the initial program load procedure.
�dynamic directory: See MFS dynamic directory.
�dynamic dump: A dump that is issued during the execution of a program, usually under the control of that program.
�dynamic group: A group that is defined using a search expression.
�Dynamic Host Configuration Protocol (DHCP): A communications protocol that is used to centrally manage configuration information. For example, DHCP automatically assigns IP addresses to computers in a network.
�dynamic IP: A method of Internet Protocol (IP) address management in which Dynamic Host Configuration Protocol (DHCP) assigns IP addresses to hosts and updates the host IP records in the Domain Name System (DNS). This method keeps DNS records current as IP address assignments change.
�dynamic IP address: A temporary IP address for a transient device or logical unit on a network: for example, a personal computer. See also IP address.
�dynamic IP connection: A virtual private network (VPN) connection between a local endpoint and a host with a dynamically assigned Internet Protocol (IP) address.
�dynamic keyrange CDS: A multi-cluster control data set (CDS) defined without key ranges for which DFSMShsm dynamically calculates the key boundaries.
�dynamic kit: A group of products that are ordered as a unit and must be fulfilled together. The information about the products contained in a dynamic kit is controlled by an external configurator and supplied at order entry time. See also bundle, composite catalog entry, configurator.
�dynamic linking: (1) The delayed connection of a program to a routine until load time or run time.; (2) Linking on demand at run time. See also static linking.
�dynamic link library (DLL): A file containing executable code and data bound to a program at load time or run time, rather than during linking. The code and data in a DLL can be shared by several applications simultaneously.
�dynamic link pack area (dynamic LPA): A facility for adding additional modules to the to the link pack area (LPA) after the LPA has been created. See also link pack area.
�dynamic load sharing (DLS): A distribution of traffic over available paths that permits recomputing of routes when a port or link changes status.
�dynamic log: An area in main storage used (by the journal control program) for storing copies of all changes to recoverable resources that might be required for dynamic backout of an LUW. Every execution of a transaction that has dynamic transaction backout specified has an associated dynamic log area.
�dynamic LPA: See dynamic link pack area.
�dynamic LPAR (DLPAR): The ability to move processors, memory, and interactive performance between logical partitions without restarting a logical partition or the server.
�dynamic mode: An operating mode of node DniConfigProvider, in which this node accesses the configuration database tables to retrieve configuration data and store it in the message. A configuration object set (COS) determines which data is to be retrieved. This mode is enabled, if the 'DSN of Configuration DB' property is filled in.
�dynamic naming: In System Manager, the attribute of an application option that specifies whether the option can be stored in libraries and folders named at the time the installation is performed. This attribute allows an application program to be stored even if a library or folder with the same name as one of the application program's primary libraries or folders is already on the customer's system, but is used by an application program with a different registration identifier.
�dynamic node: A VTAM node created dynamically. See also dynamic terminal.
�dynamic node group: A variable node group consisting of nodes with specific attribute values.
�dynamic organizational role: An organizational role that is assigned to a person by using an LDAP filter. When a user is added to the system and the LDAP filter parameters are met, the user is automatically added to the dynamic organizational role.
�dynamic parse: A method of parsing TSO commands according to syntax given in an external file.
�dynamic partition: A partition configured at the time of program execution according to the storage requirements of the application program or program to which the partition is allocated. See also static partition.
�dynamic partition balancing: A VSE facility that allows the user to specify that two or more or all partitions of the system should receive about the same amount of time on the processing unit.
�dynamic policy: A template of permissions for a particular type of resource.
�dynamic print management: The use of the PrintManager program to make changes to a print operation without interrupting system functions.
�dynamic priority: The priority of a process that is varied by the operating system.
�dynamic processing: A method of reading from or writing to a file in a nonsequential order (see random processing) and reading from a file in a sequential order (see sequential processing) with the same OPEN statement.
�dynamic program call: A transfer of control from one program or procedure to another program (*PGM) at run time. A dynamic program call is the only way that an original program model (OPM) program can connect to another OPM program. See also static program call.
�dynamic queue: A local queue created when a program opens a model queue object.
�dynamic random access memory (DRAM): Storage in which the cells require repetitive application of control signals to retain stored data.
�dynamic ranking: A type of ranking in which the terms in the query are analyzed with respect to the documents that are being searched to determine the rank of results. See also static ranking, text-based scoring, ranking.
�dynamic reconfiguration (DR): The process of changing the network configuration (peripheral PUs and LUs) without regenerating complete configuration tables or deactivating the affected major node.
�dynamic reloading: The ability to change an existing component without restarting the server for the changes to become effective. See also hot deployment.
�dynamic resource allocation: An allocation technique in which the resources assigned for execution of computer programs are determined by criteria applied at the moment of need.
�dynamic resource definition (DRD): An IMS function that enables users to create, update, query, and delete the following IMS resources and their descriptors dynamically, without using the batch system definition or online change processes: application programs; databases; Fast Path routing codes; transactions.
�dynamic retrieval: A storage management operation where selected data is restored back to disk. The retrieval can be either from tape to disk or from disk to disk.
�dynamic route: A path that can be automatically located from a peer (locally attached) gateway.
�dynamic routing: The automatic routing of a transaction or program, at the time it is initiated, from a requesting region to a suitable target region. Routing terminal data to an alternative transaction at the time the transaction is invoked. To do this, CICS allows the dynamic routing program to intercept the terminal data and redirect it to any system and transaction it chooses.
�dynamic routing model: The "traditional", hierarchical CICS dynamic routing system, in which a single terminal-owning region (the routing region) routes transactions between several application-owning regions (the target regions). The dynamic routing model is implemented by the dynamic routing program.
�dynamic routing program: A user-replaceable CICS program that selects dynamically both the system to which a routing request is to be sent and the transaction's remote name. The alternative to using this program is to make these selections when a remote transaction is defined to CICS (static routing).
�dynamic select/omit: Selection and omission of logical file records performed during processing, instead of when the access path (if any) is maintained. Dynamic select/omit may also be used when no keyed access path exists.
�dynamic sparing: The ability of a storage server to move data from a failing disk drive module (DDM) to a spare DDM while maintaining storage functions.
�dynamic SQL: An SQL statement that is prepared and executed at run time. In dynamic SQL, the SQL statement is contained as a character string in a host variable and is not precompiled. See also deferred embedded SQL, static SQL, incremental bind statement.
�dynamic storage: An area of storage that is explicitly allocated by a program or procedure while it is running. See also static storage, automatic storage.
�dynamic storage area (DSA): A type of storage allocation in which storage is assigned to a program or application at run time.
�dynamic string: See string.
�dynamic summarization: A type of summarization in which the search terms are highlighted and the search results contain phrases that best represent the concepts of the document that the user is searching for. See also static summarization, summarization.
�dynamic support program (DSP): Multiprogrammed system components that are scheduled by the job segment scheduler (JSS) and implement a specified function. A DSP can be related to job execution, such as main service or output service, or it can be a background utility, such as the dump job facility.
�dynamic system interchange (DSI): A recovery facility that allows the operator to switch the JES3 global functions to a local processor in case of global processor failure.
�dynamic table: An installation-defined table that is used to extend, modify, or delete the default processing specifications. See also table pair.
�dynamic terminal: A terminal created through the Extended Terminal Option (ETO). This is a terminal that has not been defined within the IMS system definition, and for which no control blocks exist at IMS initialization time. See also static terminal, dynamic node.
�dynamic transaction backout (DTB): The process of canceling changes made by a transaction to recoverable resources following a failure of the transaction for whatever reason.
�dynamic transaction routing (DTR): The automatic routing of a transaction, at the time it is initiated, from a terminal-owning region (TOR) to a suitable application-owning region (AOR).
�dynamic transaction routing program (DFHDYP): A user-replaceable CICS program that selects dynamically both the system to which a transaction routing request is to be sent and the transaction's remote name. The alternative to using this program is to make these selections when a remote transaction is defined to CICS (static transaction routing).
�dynamic user: A user that was created dynamically.
�dynamic view: A view that uses a network file system to access versions of elements.
�dynamic vocabulary: A vocabulary that is defined while an application is running.
�dynamic Web content: Programming elements such as JavaServer Pages (JSP) files, servlets, and scripts that require client or server-side processing for accurate runtime rendering in a Web browser.
�dynamic Web project: A project that contains resources for a Web application with dynamic content such as servlets or JavaServer Pages (JSP) files. The structure of a dynamic Web project reflects the Java EE standard for Web content, classes, class paths, the deployment descriptor, and so on.
�dynamic writer: An output service function that controls printing or punching of data sets with characteristics that are not assigned to a specific device but are assigned to appropriate devices as they become available.

�

Back to top�