
	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

�

�E1: A digital trunking facility standard used in Europe and elsewhere, capable of transmitting and receiving 30 digitized voice or data channels. Two additional channels are used for synchronization, framing, and signaling. The transmission rate is 2048 kilobits per second. See also T1.
�EAB: See Enterprise Address Book.
�EAC: See estimate at completion.
�EA-enabled table space: A table space or index space that is enabled for extended addressability and that contains individual partitions (or pieces, for LOB table spaces) that are greater than 4 GB.
�E and M: A channel associated signaling protocol in which signaling is done using two leads: an M-lead that transmits battery or ground and an E-lead that receives open or ground.
�EAO exception: See effective address overflow exception.
�EAR: See enterprise archive.
�EAR file: See enterprise archive.
�early resource release: The release of resources (such as devices, volumes, and data sets) after they are no longer needed.
�early token release: A function, supported by token-ring adapter types 2 and 3, that allows a transmitting station to release the token after transmitting the ending delimiter.
�earned value: A measure of the value of work performed so far. Earned value uses original estimates and progress-to-date to show whether the actual costs incurred are on budget and whether the tasks are ahead or behind the baseline plan.
�EAR project: See enterprise application project.
�eavesdropping: A breach of communication security in which the information remains intact, but its privacy is compromised. See also impersonation, tampering.
�EB: See exabyte.
�EBA: See Euro Banking Association.
�EBCDIC: See Extended Binary Coded Decimal Interchange Code.
�EBCDIC character: Any one of the symbols included in the EBCDIC set.
�EBCDIC double-byte encoding scheme: A structure that has separate, allocated coding space for control characters and graphic characters. Control characters do not have 16-bit codes in the EBCDIC structure definition. Graphic characters have a range from 4141 to FEFE. The space character is at 4040.
�EBCDIC single-byte encoding scheme: An 8-bit-per-byte structure. The EBCDIC single-byte structure has a valid code-point range for 00 to FF. Control characters have a range from 00 to 3F. Graphic characters have a range from 41 to FE. The space character is 40.
�e-business: The transaction of business over an electronic medium such as the Internet.
�EBV: See effective Boolean value.
�EC: See engineering change.
�ECB mode: See electronic code book mode.
�ECC: See error correction code.
�ECDSA: See extended CICS dynamic storage area.
�ECF: See Enhanced Connectivity Facility.
�echo: (1) In computer graphics, the immediate notification of the current values provided by an input device to the operator at the display console.; (2) In data communication, a reflected signal on a communication channel. An echo verifies the accuracy of the signal
�echo area: The part of the Prompted Query primary panel in which a prompted query is built.
�echo cancellation: A filter algorithm that is used to compare a copy of the voice data being sent to a caller with the voice data being received from the caller. Any echo of the sent data is removed before the received data is sent on, for example, to a speech recognizer.
�ECI: See external call interface.
�ECKD: See extended count key data.
�ECKD device: See extended count key data device.
�ECL: See execution control list.
�Eclipse: An open-source initiative that provides ISVs and other tool developers with a standard platform for developing plug-compatible application development tools.
�eclipsed: Pertaining to an object in a versioned object base (VOB) that is not visible because another object with the same name is currently selected by the view.
�Eclipse Modeling Framework: The Eclipse components that define and implement structured data models, which are a set of related classes that are used to handle data in applications.
�Eclipse Platform: An open-source, standard platform for building integrated development environments (IDEs) that can be used to create applications, such as Web sites, embedded Java programs, or Enterprise JavaBeans. The platform discovers, integrates, and runs the integrated modules called plug-ins that exist within its environment.
�ECMA: See Ecma International.
�Ecma International (ECMA): An international association that is dedicated to the standardization of information and communication systems. The ECMA is based in Europe and was founded in 1961.
�e-commerce: The subset of e-business that involves the exchange of money for goods or services purchased over an electronic medium such as the Internet.
�ECSA: See extended common service area.
�ED: (1) See Environment Division.; (2) See enciphered data.
�EDF: See execution diagnostic facility.
�edge: (1) A return value or possible result from a state table action.; (2) In transaction monitoring, the point at which a transaction first comes in contact with the monitoring instrumentation.
�EDGE: See Enhanced Data GSM Environment.
�edge device: A functional unit such as a router or gateway that is deployed at the border of an administrative domain. An edge device controls traffic through one point only.
�Edge Side Include (ESI): A technology supporting cacheable and noncacheable Web page components that can be gathered and assembled at the edge of a network.
�EDI: See electronic data interchange.
�EDI administrator: The person responsible for setting up and maintaining Data Interchange Services.
�EDI composite data element: A group of related EDI Data Elements, such as the elements that make up a name and address. Maintained as EDI data elements in Data Interchange Services.
�EDI data element: A single item of data in an EDI document, such as a purchase order number, that corresponds to a ROD field in a ROD document definition. An EDI data element is equivalent to a simple element. It is also used to maintain EDI composite data elements.
�EDI document definition: A description or layout of an EDI document, which comprises loops, EDI segments, EDI data elements, and EDI composite data elements. It is equivalent to the layout of an EDI transaction or an EDI message.
�EDI envelope: The EDI segments and EDI data elements that make up the headers and trailers that enclose EDI transaction sets, functional groups, and interchanges.
�EDIFACT: Electronic Data Interchange for Administration, Commerce and Transport (a United Nations standard).
�EDI loop: A group of consecutive EDI segments that repeat together in an EDI document definition. There is no object type in Data Interchange Services that defines an EDI loop on its own. EDI loops are logically defined within an EDI document definition.
�EDI message: In UN/EDIFACT EDI Standards, a group of logically related data that makes up an electronic business document, such as an invoice. It is equivalent to an EDI transaction. Called an EDI document definition in Data Interchange Services.
�EDI message set: A group of logically related data that make up an electronic business document, such as an invoice or a purchase order. A single EDI document. The layout of an EDI transaction is described by an EDI document definition in Data Interchange Services.
�EDI segment: A group of related EDI data elements. An EDI segment is a single line in an EDI document definition, beginning with a segment identifier and ending with a segment terminator delimiter. The EDI data elements in the EDI segment are separated by data element delimiters.
�EDI standard: The industry-supplied, national or international formats to which information is converted, allowing different computer systems and applications to exchange information.
�edit: (1) To add, change, delete, rearrange, or modify the form or format of data.; (2) To change a numeric field for output by suppressing zeros and inserting commas, periods, currency symbols, the sign status, or other constant information.
�editable field: On a form, a field whose value is determined by a formula that application designers write to supply a default value, edit the user's entry, and validate the entry to make sure it meets specific requirements.
�edit code: A letter or number indicating that editing should be done according to a defined pattern before a field is displayed or printed. See also edit word.
�edit description: A description of a user-defined edit code. The system-recognized identifier is *EDTD.
�editing character: In COBOL, a single character or a fixed 2-character combination that punctuates output.
�edition: A successive deployment generation of a particular set of versioned artifacts.
�edit line: In CoOperative Development Environment/400, a string of characters ended either by an end-of-line character sequence or by the end of the file.
�edit mask: A byte string that tells the edit machine instruction or the Edit (QECEDT) API how to format a numeric value into a readable character string. An edit mask can format a numeric value so that languages that cannot use machine instructions directly can take advantage of this function.
�edit mode: The state in which users can create or modify a document.
�editor: An application that enables a user to modify existing data.
�editor access: An access level that allows users to create, read, and edit any documents. Servers can replicate new documents, change existing documents, and, if they have delete access, make deletions.
�editor area: In Eclipse and Eclipse-based products, the area in the workbench window where files are opened for editing.
�editor program: A computer program designed to perform such functions as rearrangement, modification, and deletion of data in accordance with prescribed rules.
�EDI transaction: In X12 EDI Standards, a group of logically related data that makes up an electronic business document, such as an invoice. It is equivalent to an EDI message. The layout of an EDI transaction is described by an EDI Document Definition in Data Interchange Services.
�EDI transaction set: A group of logically related data that make up an electronic business document, such as an invoice or a purchase order. A single EDI document.
�edit word: A user-defined word with a specific format that indicates how editing should be done. See also edit code.
�EDL: See exchange data link.
�E_D_TOV: See error detect timeout value.
�EDU: See engine dispatchable unit.
�EE_credit: See end-to-end credit.
�EEQE: See extended error queue element.
�EFD: See event forwarding discriminator.
�effective address overflow exception (EAO exception): In Performance Tools, a condition in which the Licensed Internal Code must make address adjustments not made above the machine interface.
�effective Boolean value (EBV): The result of converting a sequence of items into a logical value of true or false.
�effective configuration: The particular zone configuration that is currently in effect. Only one configuration can be in effect at once. The effective configuration is built each time a zone configuration is enabled.
�effective group ID: (1) An attribute of a process that is used in determining various permissions, including file access permissions.This value is subject to change during the process lifetime.; (2) The current group ID, but not necessarily the user's own ID. For example, a user logged in under a particular group ID might be able to change to another group ID. The ID to which the user changes then becomes the effective group ID.
�effective user: In Notes, the user under whose authority an agent runs. The effective user name will be used for database ACL access rights; rights to create databases, replicas, and templates on the server; and as the mail sender or document author. Effective user rights are not used to determine the operations an agent is permitted to perform; these are based on the agent signer (the agent owner).
�effective user ID: The current user ID, although not necessarily the user's login ID. For example, if a user logged in under a login ID changes to another user's ID, that ID becomes the effective user ID until the user returns to the original login ID. All discretionary access decisions are based on the effective user ID.
�effector: An interface that enables an external agent (such as an autonomic manager) to perform operations or change the state of a managed resource. An effector is used to alter data in a managed resource, whereas a sensor is used to retrieve data from a managed resource. See also managed resource, execute component, manageability interface, sensor, touchpoint.
�E-format: A character data in scientific notation, where a numeric value part is followed by an exponent indicator, usually the letter 'E', and a possibly signed integer that indicates a power of ten by which the numeric value should be multiplied.
�EGL: See Enterprise Generation Language.
�EGL build file: An XML file with an .eglbld extension, used to store definitions of EGL build parts.
�EGL file: An Enterprise Generation Language program file (extension .eglpgm), definitions file (extension .egldef), or build file (extension .eglbld).
�EGL keyword: A term that begins an EGL statement that is neither a function invocation nor an assignment statement. Keywords include add and delete.
�EGL source file: A text file with an .egl extension, used to store definitions of EGL data, logic, and UI parts.
�EGL statement: A directive that is coded into an EGL function part to cause an action when the generated program runs. Examples include an EGL assignment statement and an EGL add statement.
�EGP: See Exterior Gateway Protocol.
�EHLLAPI: See Emulator High-Level Language Application Programming Interface.
�EIA: See Electronic Industries Association.
�EIA-232: In data communications, a specification of the Electronic Industries Association (EIA) that defines the interface between data terminal equipment (DTE) and data circuit-terminating equipment (DCE) using serial binary data interchange.
�EIA-422: In data communication, a specification of the Electronic Industries Association (EIA) that defines the electrical characteristics for balanced voltage digital interface circuits for the interchange of serial binary data between data terminal equipment (DTE) and data circuit-terminating equipment (DCE), or any point-to-point interconnection of serial binary signals between digital equipment.
�EIA-423: In data communication, a specification of the Electronic Industries Association (EIA) that defines the electrical characteristics for unbalanced voltage digital interface circuits for the interchange of serial binary data between data terminal equipment (DTE) and data circuit-terminating equipment (DCE), or any point-to-point interconnection of serial binary signals between digital equipment. The international equivalent is CCITT Recommendation V.10.
�EIA-449: In data communication, a specification of the Electronic Industries Association (EIA) that defines the interface between data terminal equipment (DTE) and data circuit-terminating equipment (DCE) employing serial binary data interchange. EIA-449, together with EIA-422 and EIA-423, is intended to gradually replace EIA-232 and is used for high speed data transmission (up to 10 Mbps). There is no international equivalent, although ISO 4902 is partly covered in 449.
�EIA rack: A storage rack that meets the standards set by the Electronics Industry Association (EIA).
�EIA unit: A unit of measure, established by the Electronic Industries Association, equal to 44.45 millimeters (1.75 inches).
�EIB: See EXEC interface block.
�EID: (1) See event identifier.; (2) See enterprise identifier.
�EIM: See Enterprise Identity Mapping.
�EIP: See execution interface program.
�EIS: See enterprise information system.
�EISA: See Extended Industry Standard Architecture.
�EJB: See Enterprise JavaBeans.
�EJB bean: See enterprise bean.
�EJB container: A container that implements the EJB component contract of the Java EE architecture. This contract specifies a runtime environment for enterprise beans that includes security, concurrency, life cycle management, transaction, deployment, and other services. (Sun) See also EJB server.
�EJB context: In enterprise beans, an object that allows an enterprise bean to invoke services provided by the container and to obtain information about the caller of a client-invoked method. (Sun)
�EJB factory: An access bean that simplifies the creating or finding of an enterprise bean instance.
�EJB home object: In Enterprise JavaBeans (EJB) programming, an object that provides the life cycle operations (create, remove, find) for an enterprise bean. (Sun)
�EJB inheritance: A form of inheritance in which an enterprise bean inherits properties, methods, and method-level control descriptor attributes from another enterprise bean that resides in the same group.
�EJB JAR file: A Java archive that contains an EJB module. (Sun)
�EJB module: A software unit that consists of one or more enterprise beans and an EJB deployment descriptor. (Sun)
�EJB object: In enterprise beans, an object whose class implements the enterprise bean remote interface (Sun).
�EJB project: A project that contains the resources needed for EJB applications, including enterprise beans; home, local, and remote interfaces; JSP files; servlets; and deployment descriptors.
�EJB query: In EJB query language, a string that contains an optional SELECT clause specifying the EJB objects to return, a FROM clause that names the bean collections, an optional WHERE clause that contains search predicates over the collections, an optional ORDER BY clause that specifies the ordering of the result collection, and input parameters that correspond to the arguments of the finder method.
�EJB query language: A query language that defines finder methods for entity beans with container managed persistence. The definition uses a language based on SQL that allows searches on the persistent attributes of an enterprise bean and associated bean attributes.
�EJB reference: A logical name used by an application to locate the home interface of an enterprise bean in the target operational environment.
�EJB server: Software that provides services to an EJB container. An EJB server may host one or more EJB containers. (Sun) See also EJB container.
�eject: The process by which a volume is removed from a system-managed library.
�eject to front facing (ETFF): A flag used in a resource exit to tell PSF to bypass the eject-to-front-facing function.
�elaborated type specifier: Typically used in C++ in an incomplete class declaration or to qualify types that are otherwise hidden.
�elaboration: The phase of the software development life cycle in which the functions and the architecture of a product are defined.
�electromagnetic compatibility (EMC): The design and test of products to meet legal and corporate specifications dealing with the emissions and susceptibility to frequencies in the radio spectrum. Electromagnetic compatibility is the ability of various electronic equipment to operate properly in the intended electromagnetic environment.
�electromagnetic interference (EMI): Waves of electromagnetic radiation, including but not limited to radio frequencies, generated by the flow of electric current.
�electronic code book mode (ECB mode): A method of enciphering and deciphering data in address spaces or data spaces. Each 64-bit block of plaintext is separately enciphered and each block of the ciphertext is separately deciphered.
�electronic customer support: A part of the operating system that allows a customer to access the question-and-answer (Q & A) function; problem analysis, reporting, and management; IBM product information; and technical information exchange.
�electronic data interchange (EDI): The exchange of structured electronic data between computer systems according to predefined message standards.
�electronic document: A document that is stored on the computer, instead of printed on paper.
�electronic form: A collection of constant data that is electronically composed in the host processor and may be merged with variable data on a page during printing.
�Electronic Industries Association (EIA): An organization of electronics manufacturers that advances the technological growth of the industry, represents the views of its members, and develops industry standards.
�electronic keystick: A device that slides into a slot on some System i product control panels. When the keystick is in place, it electronically unlocks functions at the key pad on the control panel. This allows a system operator to select an operating mode. When the keystick is removed, those functions are electronically locked, which prevents those without authority from placing the machine in some other mode.
�electronic overlay: An AFP resource object that is a collection of predefined data, such as lines, shading, text, boxes, or logos, that can be merged with variable data on a page while printing.
�electronic serial number (ESN): Unique identification number embedded in a wireless phone by the manufacturer to prevent fraud. ESN differs from the mobile identification number, which is the wireless carrier's identifier for a phone in the network.
�Electronic Service Agent: An i5/OS function that provides automatic hardware problem-reporting to help predict and prevent hardware errors by early detection of potential problems. With this function, users can also download fixes and automatically submit problems to IBM when appropriate.
�electronic signature: A stamp added to mail messages, fields, or sections that verifies that the person who originated the message is the author and that no one has tampered with the data.
�electrostatic discharge (ESD): (1) The flow of current that results when objects having a static charge come into close enough proximity to discharge.; (2) An undesirable discharge of static electricity that can damage equipment and degrade electrical circuitry.
�element: (1) In markup languages, a basic unit consisting of a start tag, end tag, associated attributes and their values, and any text that is contained between the two.; (2) The smallest unit in a table, array, list, set, or other structure. Examples of an element are a value in a list of values and a data field in an array.; (3) A named piece of information, or a field, within a message, that has a business meaning agreed by the applications that create and process the message.; (4) An object that encompasses a set of versions, organized into a version tree.; (5) A constituent of a model.; (6) A component of a document, such as an EDI, XML, or ROD record. An element can be a simple element or a compound element.; (7) A part of a section. Each element represents a separate class of data and is identified by a section name and class name.; (8) A value in a security label component. See also security label component.; (9) In Java development tools, a generic term that can refer to packages, classes, types, interfaces, methods, or fields.
�element address: In SNA, a value in the element field of the network address that identifies a specific resource within a subarea.
�elementary item: In COBOL, a data item that cannot be further logically subdivided.
�element equality: A relation that determines if two elements are equal.
�element mark: In AFP Utilities, a mark that is used to show the position of an element on a display; for example, '*B005' where B means bar code and 005 is the fifth element. See also element name.
�element name: In AFP Utilities, a name that appears in the image area instead of an element mark. See also element mark.
�element occurrence: A single instance of an element in a collection. In a unique collection, element occurrence is synonymous with element value.
�element separator: See data element delimiter.
�element type: A property of an element that specifies how versions of that element are constructed.
�element value: All the instances of an element with a particular value in a collection. In a non-unique collection, an element value may have more than one occurrence. In a unique collection, element value is synonymous with element occurrence.
�ELF message: See external line format message.
�eligibility age: The number of days since a data set met its criteria to be migrated.
�eligible machine: A machine that runs an eligible operating system and can be partitioned.
�eligible operating system: An operating system using a partitioning technology as specified by Passport Advantage.
�eligible program: A programs that meets the conditions described by Passport Advantage.
�ELLC: See enhanced logical link control.
�ELPA: See extended link pack area.
�else clause: The part of an if statement that contains the keyword 'else' followed by a statement. The else clause provides an action that is started when the if condition evaluates to a value of 0 (false).
�ELT: See extract, load, and transform.
�e-mail: Documents and messages that are transmitted between users over a communication network.
�e-mail activity: A method of delivering merchandising and marketing content to customers. E-mail activities deliver customized e-mail messages, based on JSP templates, which can include advertisements, suggestive selling initiatives, and promotions, among other merchandising and marketing content.
�e-mail template: An e-mail outline that serves as the basis for e-mail content issued via an e-mail activity. The e-mail template is a model by which the business user defines e-mail message content and optional placeholders for personalized content.
�e-Marketing spot: In WebSphere Commerce, data on a Web page that typically results from a marketing activity such as a campaign.
�embedded blank: A space between characters within a unit of data.
�embedded command: A command enclosed as a value within another command.
�embedded SQL: An SQL statement that is coded within an application program. See also Call Level Interface.
�embedded system: A computer system that is a component of a larger machine or system. Embedded systems can respond to events in real time. Hosts of embedded systems include watches, household appliances, cars, and cellular phones.
�embedded text control: One or more bytes of control information, preceded by an escape character, contained within a set of text. The text control controls certain operations on following text, but it is not itself printed.
�embedded workflow: A workflow that is only functional if it is employed with the surrounding, or embedding, system. The workflow functionality of embedded workflows is exhibited by the surrounding software system. An example is an Enterprise Resource Planning (ERP) system. See also autonomous workflow.
�EMC: See electromagnetic compatibility.
�e-meeting: See Web conference.
�emergency power off (EPO): A means of turning off power during an emergency, referring usually to a switch.
�emergency restart: (1) A restart of IMS following an IMS or MVS failure. See also normal restart, cold start.; (2) The CICS backout facility for an automatic restart following a system failure. It restores the recoverable resources updated by each interrupted transaction to the condition they were in when the transaction started.
�emergency thread: A server thread that becomes available when either the work queue (the number of pending operations) or the time limit threshold since the last item was removed from the work queue is exceeded. This thread provides a method for the administrator to access the server during a denial of service attack.
�EMH: See expedited message handling.
�EMHQ: See expedited message handler queue.
�EMI: See electromagnetic interference.
�EMIF: See ESCON multiple image facility.
�emitter: A program that takes the output from one system and converts the information into a different form.
�emitter factory: A type of factory that handles the details of event transmission such as the event server location, the filter settings, or the underlying transmission mechanism.
�EMP: See event monitoring point.
�emphasis: Highlighting, color change, or other visible indication of conditions relative to an object or choice that affects a user's ability to interact with that object or choice. Emphasis can also give a user additional information about the state of a choice or an object.
�employee number: An identification number for each employee in a company.
�empty activity: An activity with no defined implementation that can be used as a place holder in the design stage.
�empty data set: A data set in which the pointer to the last-used block is 0.
�empty line: A line consisting of only a newline character. X/Open.
�empty range: The part of a VSAM file that is available for insertion of new records.
�empty string: A character array whose first element is a null character.
�emulation: The use of software, hardware, or both by one system to imitate another system. The imitating system accepts the same data, runs the same programs, and achieves the same results as the imitated system.
�emulation program: (1) A control program that permits functions written for one system or device to be run on another system or device.; (2) A program that allows a host system to communicate with a workstation in the same way as it would with the emulated terminal.
�emulator: (1) A program that causes a computer to act as a workstation attached to another system.; (2) A facility of the integration test client that enables the emulation of components and references during module testing. Emulators are either manual or programmatic. See also manual emulator, programmatic emulator.
�Emulator High-Level Language Application Programming Interface (EHLLAPI): An application programming interface that provides programming access to the area in computer memory that corresponds to the user's screen image (this area in memory is known as the "presentation space").
�enabled: (1) Pertaining to a state of the processing unit that allows the occurrence of certain types of interruptions. See also disabled.; (2) Pertaining to the state in which a communication device can 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 ready to establish LU-LU sessions. The LU can separately indicate whether this prevents it from acting as a primary logical unit (PLU) or a secondary logical unit (SLU). See also disabled, inhibited.; (4) A condition of the printer (physically selected) in which the printer is available to the host processor for normal work. The enabled condition is also called online.; (5) Pertaining to a condition that results in the execution of condition handlers or in the performance of a standard system action to handle the condition.
�enabled zone configuration: The currently enabled configuration of zones. Only one configuration can be enabled at a time. See also defined zone configuration, zone configuration.
�enablement: The determination by a language at run time that an exception should be processed as a condition. The exception is intercepted and a determination is made whether to ignore the exception.
�enablement step: The first step of the condition handling model during which it is determined whether an exception is to be enabled and processed as a condition. See also condition step, termination imminent step.
�enabling-new-function mode (ENFM): A transitional mode of operation in the version-to-version migration process, during which the DB2 subsystem or data sharing group prepares to use the new functions of the new version. When operating in enabling-new-function mode, a DB2 data sharing group cannot coexist with members that operate at the prior version level. In enabling-new-function mode, fallback to a prior version is not supported, and new functions of the new version are not available for use. See also enabling-new-function mode*, compatibility mode, compatibility mode*.
�enabling-new-function mode* (ENFM*): A transitional mode of operation in the version-to-version migration process that applies to a DB2 subsystem or data sharing group that was in new-function mode (NFM) at one time. When operating in enabling-new-function mode*, a DB2 subsystem or data sharing group is preparing to use the new functions of the new version but cannot yet use them. A data sharing group that operates in enabling-new-function mode* cannot coexist with members that operate at the prior version level. Fallback to a prior version is not supported. See also enabling-new-function mode, compatibility mode, compatibility mode*.
�Encapsulated Security Payload (ESP): In a virtual private network (VPN), a security protocol that provides data confidentiality and integrity.
�encapsulation: (1) In communication, a technique used by layered protocols by which a layer adds control information to the protocol data unit (PDU) from the layer it supports. In this respect, the layer encapsulates the data from the supported layer. In the Internet suite of protocols, for example, a packet would contain control information from the physical layer, followed by control information from the network layer, followed by the application protocol data. See also decapsulation.; (2) In object-oriented programming, the technique that is used to hide the inherent details of an object, function, or class from client programs.
�enchain: To reduce the size of a dictionary file. The process converts a series of single entry linear search nodes into a single chain node for the entire string, thus reducing the size of the finite state transducer (FST). Typically, enchaining is less efficient at reducing the size of a dictionary than contraction.
�encipher: To scramble data or to convert data to a secret code that masks the meaning of the data to any unauthorized recipient.
�enciphered data (ED): The encryption of data so that its meaning is concealed from unauthorized users or observers.
�enclave: (1) In Language Environment, an independent collection of routines, one of which is designated as the main routine. An enclave is similar to a program or run unit.; (2) A transaction that can span multiple dispatchable units (service request blocks and tasks) in one or more address spaces and is reported on and managed as a unit.
�enclosed document: A document that is contained within another document.
�enclosure: A unit that houses the components of a storage subsystem, such as a control unit, disk drives, and power source.
�encode: To convert data by the use of a code in such a manner that reconversion to the original form is possible.
�encoded format: In query management, the format of the data in an externalized form file.
�encoded-vector index: A DB2 for i5/OS index that is specialized for quick row selection in query processing. This type of index also provides accurate database statistics, which can improve the optimization of queries. See also radix-tree index.
�encoding scheme: (1) The underlying part of a code page that defines: a) the coding space (the number and allowable value of code points in a code page); b) the rules for sharing the coding space between control and graphic characters; and c) the rules related to the specific options permitted in that scheme, such as the number of bits in a byte, single-byte, or double-byte.; (2) The set of rules that specifies the values for control characters and graphic characters. Examples of encoding schemes include ASCII, ISO/IEC 10646, Unicode and IBM's EBCDIC.; (3) A set of rules to represent character data.
�ENCP: See end-node control point.
�encrypt: In Cryptographic Support, to systematically scramble information so that it cannot be read without knowing the coding key. See also decrypt.
�encryption: In computer security, the process of transforming data into an unintelligible form in such a way that the original data either cannot be obtained or can be obtained only by using a decryption process.
�encryption algorithm: An algorithm that scrambles the data so that it becomes unreadable to someone who intercepts it.
�encryption key: Security feature that ensures that only the intended recipient can read encrypted text. Every Notes user ID contains two: a public key for sending and encrypting and a private key for receiving and decrypting. Users may also have a public and private key for S/MIME encryption and signatures.
�end bracket: In SNA, the value (binary 1) of the end bracket indicator in the request header (RH) of the first request of the last chain of a bracket; the value denotes the end of the bracket. See also conditional end bracket.
�endian: An attribute of data that describes whether it is stored in computer memory or transmitted with the most significant byte first or last. See also big endian, little endian.
�ending attribute character: For a display file, the character following the last position in a field.
�end node: (1) In SNA, a node in an APPN network that can be a source or target node, but does not provide any routing or session services to any other node.; (2) A visual marker within a process that identifies where a particular flow ends. Other concurrent flows within the same process will still continue executing.
�end-node control point (ENCP): A control point that provides its own configuration, session, and management services with assistance from the control point in its serving network node. An ENCP is capable of engaging in CP-CP sessions with other nodes.
�end of block (EOB): A code that marks the end of a block of data.
�end-of-chain (EOC): In SNA, an exception condition that occurs when the end-of-chain indicator is set in the request/response unit (RU) returned from VTAM.
�end-of-day statistics: (1) In CICS Transaction Server, CICS statistics written to an SMF data set at the quiesce or termination of a CICS run, or at a user-specified time. See also interval statistics, unsolicited statistics.; (2) In CICS/VSE, CICS statistics written to the CSSL transient data destination at the quiesce or termination of a CICS run, or at a user-specified time. End-of-day statistics are reset by an end-of-day statistics collection.
�end-of-file (EOF): (1) On a data medium, a coded character indicating the end of the medium.; (2) A code that signals that the last record of a file has been read.
�end-of-file delay: An interval during which the system holds a file open after the normal end of the file is reached until one or more records are updated or added to the end of the file. The length of the interval can be specified on the EOFDLY parameter.
�end-of-file label: In a file, an internal label indicating the end of the file.
�end of job (EOJ)
�end of memory (EOM): The outer boundary of an address space.
�end-of-message (EOM): In a DBCTL multisegment command, the ENTER key, which is the indicator that defines the end of the last or only segment. See also end-of-segment.
�End of Procedure Division: In COBOL, the physical position of a COBOL source program after which no further procedures appear.
�end-of-segment (EOS): In a DBCTL multisegment command, the command recognition character followed by the ENTER key, which indicates the end of each segment preceding the last segment. See also end-of-message.
�end-of-tape marker (EOT marker): A reflective material placed on a magnetic tape to indicate the end of the recording area.
�end-of-text character (ETX character): The BSC transmission control character used to end a logical set of records that began with the start-of-text character. See also end-of-transmission-block character.
�end-of-transmission-block character (ETB character): The BSC transmission control character used to end a block of records. See also end-of-text character.
�end-of-transmission character (EOT character): A transmission control character used to indicate the conclusion of a transmission that may have included one or more texts and any associated message headings.
�endpoint: (1) The system that is the origin or destination of a session.; (2) A host or gateway that comprises part of a virtual private network (VPN) connection.; (3) The ultimate recipient of an operation.; (4) A JCA application or other client consumer of an event from the enterprise information system.
�endpoint list: In a Tivoli environment, a list of all endpoints in a Tivoli region with their assigned gateways.
�endpoint listener: The point or address at which incoming messages for a Web service are received by a service integration bus.
�endpoint map: In the Distributed Computing Environment (DCE) Remote Procedure Call (RPC), a database local to a node where local RPC servers register binding information associated with their interface identifiers and object identifiers.
�endpoint map service: In the Distributed Computing Environment (DCE) Remote Procedure Call (RPC), a service provided by the RPC daemon that maintains a system's endpoint map for local RPC servers. See also partially bound binding handle.
�endpoint method: In a Tivoli environment, a method that runs on an endpoint as the result of a request from another managed resource. Results of the method are forwarded to the gateway, and then to the calling managed resource.
�endpoint reference (EPR): The combination of the address of a Web service that implements the manageability interface for a managed resource type and the properties that allow that Web service to identify the managed resource. See also managed resource ID.
�endpoint system: Any system that is running i5/OS and is connected to the central system. An endpoint system is defined from the central system for the purpose of performing System i Navigator functions.
�end program header: In COBOL, a combination of words, followed by a separator period, that indicates the end of a COBOL source program. The end program header is: END PROGRAM program-name.
�end session handler: A user-provided part of a FEPI application that handles end of conversation and end of session processing.
�end system: (1) See destination node.; (2) The last system in a chain of systems that are linked by any combination of TELNET and pass-through requests.
�end-to-end connection type: In OSI, the type of network service connection used between the local and destination node, that is connection mode, connectionless mode, or both.
�end-to-end credit (EE_credit): In fibre-channel technology, a credit scheme used to manage end-to-end flow control during the exchange of frames between two communicating devices. See also buffer-to-buffer credit, end-to-end flow control.
�end-to-end flow control: The regulation of data transfers over an interface between a source and target. See also end-to-end credit.
�end-to-end latency: In SQL replication, an approximate measurement of the difference between the time that a change takes place in a source table and the time that the change is applied to a target table. See also latency, Apply latency, Capture latency, Q Apply latency, Q Capture latency, queue latency.
�end-to-end privacy: The process of securing data from a source adapter process, through the WebSphere InterChange Server, to the destination adapter process, ensuring authentication, integrity, and privacy.
�end-to-end probe platform (EPP): A platform that gathers application performance data and simulates transactions, such that probes can be created to monitor the application appropriately.
�end-to-end scheduling: The process of scheduling, controlling, and running jobs across different platforms.
�end-user significant status: A type of significant status that relates to the work associated with a resource. IMS defines conversations, set-and-test-sequence numbers terminals, and Fast Path as end-user significant status for nodes and users. See also command significant status.
�end-user terminal: A terminal where an IMS user can issue transactions, some commands (based upon security authorization), and message switches.
�end-user verification: For logical unit (LU) 6.2, checking the identification of users by means of identifiers and passwords on attach function-management headers (FMHs).
�ENFM: See enabling-new-function mode.
�ENFM*: See enabling-new-function mode*.
�enforced lock: A type of lock that a process holds on a region of a file preventing any other process from accessing that region with read or write system calls. In addition, the create command is prevented from truncating the files. See also advisory lock.
�enforced subset match conversion/substitution: A conversion where the characters that exist in both the source coded character set identifier (CCSID) and the target CCSID have their integrity maintained. Characters that are not included in the target CCSID are presented to the user as substitution characters. This substitution is permanent. Any loss of character integrity is permanent. An EBCDIC-encoded character that is in the source CCSID but not in the target CCSID is replaced with 3F.
�enforcement: In privacy management, the process of determining whether personally identifiable information (PII) can be accessed. The monitor levels are audit mode and enforcement mode. See also audit mode.
�engagement model: A model for a complex set of activities that use a generalized set of methodologies and logical relationships.
�engine: (1) A speech recognition process that accepts voice data as input and returns the text form of what was said as output. It is the process which performs the recognition.; (2) The unit that contains the processors that respond to requests for data from clients. The operating software for the IBM TotalStorage appliance resides in the engine. See also storage port.; (3) The unit that hosts the software for the metadata server.
�engine dispatchable unit (EDU): A DB2 structure that coordinates application requests to a DB2 database by using a process (on UNIX operating systems) or a thread (on Windows operating systems) to carry out instructions on behalf of the DB2 database system. See also agent.
�engineering change (EC): An update to a machine, part, or program. Each EC for a given unit is assigned a unique number referred to as an EC level or EC number.
�engine type: Each engine must be configured with a specific type. The type is simply a textual tag associated with a specific engine and does not change the operation or functionality of the engine.
�Enhanced 5250 Emulation: A program that allows a personal computer and a printer to be attached to a System i product and perform the functions of one or two 5250 workstations on one twinaxial cable. The workstations can be one display station, two display stations, or one display station and one printer.
�enhanced conflict detection: In SQL replication, conflict detection that guarantees data integrity among all replicas and the source table. The Apply program locks all replicas or user tables in the subscription set against further transactions. It begins detection after all changes made prior to locking have been captured.
�Enhanced Connectivity Facility (ECF): A set of programs that allows a user to access IBM-supplied servers or to create servers.
�Enhanced Data GSM Environment (EDGE): A faster version of the GSM wireless service that is designed to deliver data at rates up to 384 Kbps and enable the delivery of multimedia and other broadband applications to mobile phone and computer users. The EDGE standard is built on the existing GSM standard, using the same time-division multiple access (TDMA) frame structure and existing cell arrangements.
�enhanced logical link control (ELLC): An X.25 protocol that allows the transfer of data link control information between two adjoining SNA nodes that are connected through an X.25 packet-switching data network. ELLC enhances error detection and recovery. See also physical services header, Qualified Logical Link Control.
�enhanced NWS: A character-based 5250 workstation with an enhanced character set that allows the presentation of characters that look like graphical symbols.
�Enhanced X-Windows: A collection of basic functions for developing a variety of application environments. Toolkit functions manage Toolkit initialization, widgets, memory, events, geometry, input focus, selections, resources, translation of events, graphics contexts, pixmaps, and errors.
�enhancement request: A change request for a new feature or functionality. See also change request.
�ENQ character: See enquiry character.
�enqueue: To put a message or item in a queue. See also dequeue.
�enqueued: Pertaining to a task that is scheduled to update a physical segment of a database when another task is currently accessing that segment.
�enquiry character (ENQ character): The BSC transmission control character usually used to request a response from the remote system or device.
�enroll: In Backup, Recovery, and Media Services, to identify media to Backup, Recovery, and Media Services. Media initialized in Backup, Recovery, and Media Services does not need to be enrolled.
�enrollment: (1) The process of entering and saving user or user group information in a portal.; (2) An entitlement for an organization to subscribe to a business service.
�enterprise: (1) The composite of all operational entities, functions, and resources that form the total business concern and that require an information system.; (2) The aggregate of an organization's data center complexes. The enterprise is an object that is at the top of the hierarchical model of Tivoli Manager for OS/390 and Tivoli Availability Infrastructure Services.
�Enterprise Address Book (EAB): A collection of information about people, departments, and locations in an enterprise. Information about people may include telephone numbers, mailing addresses, and the department in which a person works. Department information may include the department name, the manager, and the department name the department reports to. Location information may contain a mailing address. On a System i product, the EAB is the system distribution directory.
�enterprise application: See Java EE application.
�enterprise application project (EAR project): A structure and hierarchy of folders and files that contain a deployment descriptor and IBM extension document as well as files that are common to all Java EE modules that are defined in the deployment descriptor.
�enterprise archive (EAR): A specialized type of JAR file, defined by the Java EE standard, used to deploy Java EE applications to Java EE application servers. An EAR file contains EJB components, a deployment descriptor, and Web archive (WAR) files for individual Web applications. See also Web archive, Java archive.
�enterprise bean: A component that implements a business task or business entity and resides in an EJB container. Entity beans, session beans, and message-driven beans are all enterprise beans. (Sun) See also bean.
�enterprise configuration: A method of setting up servers so that the administrator can distribute the configuration of one of the servers to the other servers, using server-to-server communication.
�enterprise database: A database that is designed to support a large, networked organization. An enterprise database offers scalability, security, and administrative features for large, complex projects.
�enterprise discovery server: A discovery server that aggregates the data collected by domain discovery servers and presents a view of all the collected configuration item information.
�Enterprise Generation Language (EGL): A high-level language that allows developers to focus on business logic as they create complex business applications for deployment in any of several environments, including the Web. The language simplifies database and message-queue access, as well as the use of Java EE.
�enterprise identifier (EID): A work identifier for a distributed transaction that is both a local and a global identifier. The format of the EID is a concatenation of the transaction identifier (TID) and global transaction identifier (GTID).
�Enterprise Identity Mapping (EIM): A mechanism for associating a person or entity to the appropriate user identities in various user registries throughout an enterprise. EIM provides application programming interfaces (APIs) for creating and managing these identity mapping relationships, as well as APIs that applications use to query this information.
�Enterprise Information Portal: Software developed by IBM that provides tools for advanced searching, and content customization and summarization.
�enterprise information system (EIS): (1) In System Manager, all the resources that the applications manage and the functions for managing them.; (2) The applications that comprise an enterprise's existing system for handling companywide information. An enterprise information system offers a well-defined set of services that are exposed as local or remote interfaces or both. (Sun) See also resource adapter.
�Enterprise JavaBeans (EJB): A component architecture defined by Sun Microsystems for the development and deployment of object-oriented, distributed, enterprise-level applications (Java EE).
�enterprise resource planning (ERP): The planning and management of all the resources in an enterprise.
�enterprise search administrator: An administrative role that enables a user to administer the entire enterprise search system.
�enterprise search base annotator: A set of standard text analysis engines used in enterprise search for default document analysis processing. See also custom text analysis engine.
�enterprise service: A service that typically accesses one or more enterprise information systems (EIS).
�enterprise service bus (ESB): A flexible connectivity infrastructure for integrating applications and services; it offers a flexible and manageable approach to service-oriented architecture implementation.
�Enterprise Systems Architecture (ESA): A hardware architecture that reduces the effort required for managing data sets and extends addressability for system, subsystem, and application functions.
�Enterprise Systems Architecture/390 (ESA/390): An IBM architecture for mainframe computers and peripherals. Processor systems that follow the ESA/390 architecture include the ES/9000 family. See also z/Architecture.
�Enterprise Systems Connection: A peripheral interface for an Enterprise Systems Architecture/390 and zSeries computer. The I/O interface uses ESA/390 logical protocols over a serial interface that configures attached units to a communication fabric.
�entitlement: (1) In security management, a service and list of attributes that identifies the target for a provisioning policy.; (2) A data structure that contains externalized security policy information. Entitlements contain policy data or capabilities that are formatted in a way that is understandable to a specific application.
�entity: (1) In OSI, the representation of a layer on a given open system.; (2) A person, object, or concept about which information is stored.; (3) In markup languages such as XML, a collection of characters that can be referenced as a unit, for example to incorporate often-repeated text or special characters within a document.; (4) In object-oriented design, an item that can be treated as a unit and, often, as a member of a particular category or type. An entity can be a concrete thing or an abstract idea.; (5) A user, group, or resource that is defined to RACF.
�entity bean: In EJB programming, an enterprise bean that represents persistent data maintained in a database. Each entity bean carries its own identity. (Sun) See also session bean.
�entity class: A class used to model information that has been stored by the system, and the associated behavior. A generic class, reused in many use cases, often with persistent characteristics. An entity class defines a set of entity objects, which participate in several use cases and typically survive those use cases.
�entropy: The minimum number of bits needed to represent the information that is contained in a message.
�entry: (1) An element of information in a table, list, queue, or other organized structure of data or control information.; (2) An item in an index. It consists of a main entry plus a locator, and can also have subentries or cross-references.; (3) A collection of information about a cataloged object in a master or user catalog. See also entry name.
�entry action: An action executed on a object when it enters any state in a state machine.
�entry breakpoint: A breakpoint set on a component element that is hit before the component element is invoked.
�entry field: An area on a display where a user can enter information, unless the field is read-only. The boundaries of an entry field are usually indicated.
�entry format: The description of a personal directory entry. Each personal directory entry has an identical structure. The entry structure determines the type and size of each field in a personal directory entry.
�entry name: (1) In assembler language, a programmer-specified name within a control section that identifies an entry point and can be referred to by any control section.; (2) A unique name for an entry, which is the same as the data set name in a data definition (DD) statement that describes the object. See also entry.
�entryOwner: An attribute that can be a user or a group, similar to what is allowed within the aclEntry. Each object has an associated entryOwner attribute. However, the entryOwner subject has certain privileges over the object.
�entry point: The address or label of the first instruction processed or entered in a program, routine, or subroutine.There might be a number of different entry points, each corresponding to a different function or purpose.
�entry sequence: A physical ordering of data records in auxiliary storage according to ascending relative byte address (RBA) without respect to their contents. See also key sequence.
�entry-sequenced data set (ESDS): (1) A VSAM data set whose records are physically in the same order in which they were put in the data set. A VSAM data set is processed by using addressed direct access or addressed sequential access and has no index. New records are added at the end of the data set.; (2) A data set whose records are loaded without respect to their contents, and whose relative byte addresses cannot change. Records are retrieved and stored by addressed access, and new records are added at the end of the data set.
�entry thread: A thread which is used by the CICS DB2 attachment facility for transactions with special requirements, such as high priority transactions, or transactions with special accounting needs. See also command thread, pool thread.
�entry-type attribute: Any value that a user enters for a project. An entry-type attribute can be configured with a default value, which users can accept or replace as they create or modify requirements. See also attribute type, attribute value, list-type attribute.
�enum constant: See enumeration constant.
�enumerated list: A set of DB2 objects that are defined with a LISTDEF utility control statement in which pattern-matching characters (*, %;, _, or ?) are not used.
�enumeration: A model element in class diagrams that represents user-defined data types. See also enumeration literal.
�enumeration constant (enum constant): In the C or C++ language, an identifier, with an associated integer value, defined in an enumerator. An enumeration constant may be used anywhere an integer constant is allowed.
�enumeration data type: In the Fortran, C, and C++ language, a data type that represents a set of values that a user defines.
�enumeration literal: A model element in a class diagram that represents a named value in an enumeration. See also enumeration.
�enumeration tag: The identifier that names an enumeration data type.
�enumeration type: A data type that defines a set of enumeration constants. In the C++ language, an enumeration type is a distinct data type that is not an integral type.
�enumerator: An enumeration constant and its associated value.
�envelope: (1) A string of data representing information about a message aside from the attachments and its recipients.; (2) A control structure containing documents.
�envelope type: A value used to define the format and contents of an envelope, so that the programs that work with specific types of envelopes are supported. The envelope types supported on a system are defined when the mail server framework is configured. The value associated with an envelope type must be a unique type value.
�environment: (1) The settings for shell variables and paths set when the user logs in. These variables can be modified later by the user.; (2) A named collection of logical and physical resources used to support the performance of a function.; (3) A structure within the message tree that is user-defined, and that can contain variable information that is associated with a message while it is being processed by a message flow.; (4) A specific instance of a configuration of hardware and software.
�environmental data: Data that the storage control must report to the host. The data can be service information message (SIM) sense data; logging-mode sense data; an error condition that prevents completion of an asynchronous operation; a statistical counter overflow; or physical information, such as power supply voltages, air flow and temperature sensors.
�Environmental Record Editing and Printing (EREP): The program that formats and prepares reports from the data contained in the error recording data set.
�environment clause: In COBOL, a clause that appears as part of an Environment Division entry.
�Environment Division (ED): One of the four main parts of a COBOL program. The Environment Division describes the computers on which the source program is compiled and those on which the object program is run; it also provides a connection between the logical concept of files and their records, and the physical characteristics of the devices on which files are stored.
�environment handle: A handle that identifies the global context for database access. All data that is pertinent to all objects in the environment is associated with this handle.
�Environment Services System Services (ESSS): A component of CICSPlex SM that implements the formal MVS/ ESA subsystem functions required by the product. ESSS provides cross-memory services, data space management, connection services, and lock management. An ESSS system address space is created at CICSPlex SM initialization and remains in the MVS image for the life of the IPL.
�environment variable: (1) A variable that defines an aspect of the operating environment for a process. For example, environment variables can define the home directory, the command search path, the terminal in use, or the current time zone.; (2) A variable that is included in the current software environment and is therefore available to any called program that requests it.; (3) A variable that specifies how an operating system or another program runs, or the devices that the operating system recognizes.
�EOB: See end of block.
�EOC: See end-of-chain.
�EOF: See end-of-file.
�EOJ: See end of job.
�EOM: (1) See end of memory.; (2) See end-of-message.
�EOS: See end-of-segment.
�EOT character: See end-of-transmission character.
�EOT marker: See end-of-tape marker.
�EP: See Error Protocol.
�EPI: See external presentation interface.
�epilog: Code generated at the end of a routine, normally causing a return to the caller of the routine.
�EPLPA: See extended pageable link pack area.
�EPO: See emergency power off.
�EPOC: An operating system designed for mobile devices.
�epoch: The time and date corresponding to 0 in an operating system's clock and time-stamp values. For most versions of the UNIX operating system, the epoch is 00:00:00 GMT, 01 January 1970. System time is measured as the number of seconds past the epoch.
�epoch time stamp: In the DCE Cell Directory Service (CDS), a timestamp that identifies directory replicas as being part of the same set. CDS uses the epoch timestamp when it performs a skulk operation on a directory.
�E_port: See expansion port.
�EPP: See end-to-end probe platform.
�EPR: See endpoint reference.
�EPROM: See erasable programmable read-only memory.
�EPS: See extended pointer set.
�EPST: See extended partition specification table.
�EPVT: See error processor vector table.
�EQE: See error queue element.
�equality matching technique: A method of performing a table lookup in which a column from the primary input link is required to match a column from the reference input link.
�equate name: In Interactive Source Debugger, a shorter name assigned to a command that is used often. The equate name, when called, performs the same function as the command.
�equijoin: A join operation in which the join condition has the form expression = expression. See also join.
�equipment check: An asynchronous indication of a printer malfunction.
�equivalence class: (1) A grouping of characters or character strings that are considered equal for purposes of collation. For example, many languages place an uppercase character in the same equivalence class as its lowercase form, but some languages distinguish between accented and unaccented character forms for the purpose of collation.; (2) A classification of values for which an object is expected to behave similarly.
�equivalence partition: See equivalence class.
�equivalent: In an XRF environment, the mutual attribute of any two DBCTL subsystems that are members of the same RSE. See also recoverable service element, recoverable service table.
�equivalent paths: A collection of paths to a storage device. The paths have no switchover time penalty when changing from one path group to another while accessing the storage device.
�ER: See exception response.
�erasable programmable read-only memory (EPROM): A type of memory chip that can retain its contents without electricity. Unlike the programmable read-only memory (PROM), which can be programmed only once, the EPROM can be erased by ultraviolet light and then reprogrammed.
�erase-on-scratch: A Resource Access Control Facility (RACF) and DFSMSdfp function that overwrites the space occupied by a data set when the data set is deleted (scratched) from a direct access storage device (DASD) or part of the space is released.
�ERDS: See error-recording data set.
�ERDSA: See extended read-only dynamic storage area.
�EREP: See Environmental Record Editing and Printing.
�ERP: (1) See error recovery procedure.; (2) See enterprise resource planning.
�error: A discrepancy between a computed, observed, or measured value or condition and the true, specified, or theoretically correct value or condition. See also failure.
�error code: A value that identifies an error condition.
�error condition: The state that results from an attempt to run instructions in a computer program that are not valid or that operate on data that is not valid.
�error correction code (ECC): A code appended to a data block that has the capability to detect and correct multiple bit errors within the block.
�error detect timeout value (E_D_TOV): The time that a switch waits for an expected response before declaring an error condition. This value is adjustable in 1 microsecond increments from 2 - 10 seconds. See also resource recovery timeout value.
�error ID: See error identifier.
�error identifier (error ID): A value used to identify a unique error condition detected by the hardware or device.
�error log: A record of machine checks, device errors, and media statistics.
�error log stream: A continuous flow of error information that is transmitted using a predefined format.
�error message: Any message displayed by DirectTalk in the System Monitor as an alarm and optionally written to the DirectTalk error log, or to the AIX error log (as an alert). Strictly speaking, the term error message should include only red (immediate attention) and yellow (problem situation) messages but it is also used to refer to green (a red or yellow message has been cleared) and white (informational) messages.
�error page range: A range of pages that is considered to be physically damaged.
�error processor vector table (EPVT): A table containing addresses of the error group processors invoked by the routing mechanism of the node error program.
�Error Protocol (EP): A protocol that provides a means for an Internetwork Packet Exchange (IPX) system to report that is has detected an error, and as a result of that error, the IPX system has discarded an IPX packet.
�error queue element (EQE): A piece of data that is maintained for a Fast Path area data set block that cannot be accessed. Each data set can have up to ten damaged blocks (control intervals).
�error-recording data set (ERDS): On S/390 and zSeries hosts, a data set that records data-storage and data-retrieval errors. A service information message (SIM) provides the error information for the ERDS.
�error recovery procedure (ERP): A procedure designed to help isolate and, where possible, to recover from errors in equipment. The procedure is often used in conjunction with programs that record information on machine malfunctions.
�error status block (ESB): A recording area in a node error block (NEB) of the node error table.
�error status element (ESE): In the terminal error block of the terminal error table, a field that records occurrences of a particular type of error associated with a terminal.
�ESA: See Enterprise Systems Architecture.
�ESA/390: See Enterprise Systems Architecture/390.
�ESAF: See External Subsystem Attach Facility.
�ESA mode: An operation mode of the supervisor (generated with MODE=ESA) of a VSE system. Such a supervisor will run on a 370-XA or Enterprise Systems Architecture processor and provides support for multiple virtual address spaces, the channel subsystem, and more than 16MB of real storage.
�ESB: (1) See error status block.; (2) See enterprise service bus.
�ESB server: An application server that provides the execution environment for mediation modules in addition to application programs.
�ESC: (1) See escape character.; (2) See exception symptom code.
�escalation: A course of action that runs when a task is not completed satisfactorily within a specific period of time. See also escalation limit.
�escalation limit: The amount of time, for example hours or days, that a participant has to respond to a request, before an escalation occurs. See also escalation.
�escalation participant: In identity management, a person that has the authority to respond to requests that participants do not respond to within the specified escalation time. An escalation participant can be identified as an individual, as a role, or by using a custom JavaScript script.
�escape: To return to the original level of a user interface.
�escape character (ESC): (1) A symbol that is used to modify the interpretation of the character or characters that follow it. Examples of uses of escape characters in SQL are delimiting identifiers, delimiting character constants, and modifying the special meaning of the underscore (_) and percent (%) characters in the LIKE predicate.; (2) A character that suppresses or selects a special meaning for one or more characters that follow.; (3) The control character in a text-control sequence that indicates the beginning of a sequence and the end of any preceding text.
�escape message: A message that reports a condition that caused the program to end before the requested function was complete.
�escape sequence: (1) A string of bit combinations that is used to escape from normal data, such as text code points, into control information.; (2) A character that is preceded by a \ (backslash) and is interpreted to have a special meaning to the operating system.; (3) A sequence of characters that contains the \ symbol followed by one of the characters: a ,b ,f ,n ,r ,t ,v ,' , ,x ,\ , or by one or more octal or hexadecimal digits.
�ESCD: (1) See extended system contents directory.; (2) See ESCON Director.
�ESCM: See ESCON Manager.
�ESCON channel: An S/390 or zSeries channel that supports ESCON protocols.
�ESCON Director (ESCD): A class of devices that connect channels and control units only for the duration of an input/output (I/O) operation. See also ESCON Manager.
�ESCON host system: An S/390 or zSeries host that attaches to the ESS with an ESCON adapter. ESCON host systems run on operating systems that include MVS, Virtual Storage Extended (VSE), transaction processing facility (TPF), or versions of VM.
�ESCON Manager (ESCM): A licensed program that provides host control and intersystem communication capability for ESCON Director connectivity operations. See also ESCON Director.
�ESCON multiple image facility (EMIF): In mainframe computing, a function that enables logical partitions (LPARs) to share an ESCON channel path by providing each LPAR with its own channel-subsystem image.
�EsconNet: In ESS Specialist, the label on a pseudo-host icon representing a host connection that uses the ESCON protocol and that is not completely defined on the ESS. See also access-any mode, anonymous host.
�ESD: See electrostatic discharge.
�ESDS: See entry-sequenced data set.
�ESDSA: See extended shared dynamic storage area.
�ESE: See error status element.
�ESI: (1) See Edge Side Include.; (2) See external security interface.
�ESI processor: A feature in the WebSphere Web server plug-in that supports fragment caching and fragment assembly into full pages.
�ESM: See external security manager.
�ESN: See electronic serial number.

�esoteric unit name: An installation-assigned name for a group of devices having similar hardware characteristics; this name is used when requesting a device. For example, an esoteric unit name of TAPE might represent all tape devices in an installation. See also generic unit name.
�ESP: See Encapsulated Security Payload.
�ESQA: See extended system queue area.
�ESQL: See extended SQL.
�ESQL data type: A characteristic of an item of data that determines how that data is processed. ESQL supports six data types (boolean, datetime, null, numeric, reference, and string). Data that is retrieved from a database or is defined in a message model is mapped to one of these basic ESQL types when it is processed in ESQL expressions.
�ESQL field reference: A sequence of period-separated values that identify a specific field (which might be a structure) within a message tree or a database table. The path from the root of the information to the specific field is traced using the parent/child relationships. An example of a field reference might be something like Body.Invoice.InvoiceNo.
�ESQL function: A single ESQL expression that calculates a value from a number of given input values. The function can take input parameters but has no output parameters; it returns the value that results from the implementation of the expression to the caller. The ESQL expression can be a compound expression such as BEGIN END.
�ESQL module: A sequence of declarations that define MODULE-scope variables and their initialization, and a sequence of subroutine (function and procedure) declarations that define a specific behavior for a message flow node. A module must begin with the CREATE node_type MODULE statement and end with an END MODULE statement. The node_type must be one of COMPUTE, DATABASE, or FILTER. The entry point of the ESQL code is the MODULE scope procedure named MAIN.
�ESQL procedure: A subroutine that has no return value. It can accept input parameters from and return output parameters to the caller.
�ESQL variable: A local temporary field that is used in processing a message.
�ESS (TotalStorage Enterprise Storage Server): See IBM TotalStorage Enterprise Storage Server.
�ESS Copy Services: A collection of optional software features, with a Web-browser interface, used for configuring, managing, and monitoring data-copy functions.
�ESSS: See Environment Services System Services.
�ESTAE: See extended specify task abnormal exit.
�estimate at completion (EAC): An earned value term used to describe the expected total cost of an activity, group of activities or the project when the defined scope of work has been completed.
�estimate to complete (ETC): The expected additional cost needed to complete an activity, a group of activities, or a project.
�ETB character: See end-of-transmission-block character.
�ETC: See estimate to complete.
�E-TDMA: See extended time division multiple access.
�ETFF: See eject to front facing.
�Ethernet: A packet-based networking technology for local area networks (LANs) that supports multiple access and handles contention by using Carrier Sense Multiple Access with Collision Detection (CSMA/CD) as the access method. Ethernet is standardized in the IEEE 802.3 specification.
�Ethernet network: A baseband local area network (LAN) with a bus topology in which messages are broadcast on a coaxial cable using a carrier sense multiple access/collision detection (CSMA/CD) transmission method.
�ETL: See extract, transform, and load.
�ETO: See Extended Terminal Option.
�ETO descriptor: A template that contains information about the physical characteristics of terminals, user options and message queue names, and remote LTERMs associated with MSC links. See also logon descriptor, MFS device descriptor, MSC descriptor, user descriptor.
�ETR: (1) See external throughput rate.; (2) See external time reference.
�ETS: See European Telecommunications Standard.
�ETSI: See European Telecommunications Standards Institute.
�ETX character: See end-of-text character.
�EUC: (1) See Extended UNIX Code.
�EUC encoding scheme: See Extended UNIX Code encoding scheme.
�EUDSA: See extended user dynamic storage area.
�euro: The monetary unit of the European Monetary Union (EMU) that was introduced alongside national currencies on 01 January 1999.
�Euro Banking Association (EBA): (1) An association of banks that manages the EBA clearing system through ABE Clearing SAS. The EBA is connected to the S.W.I.F.T. network in a manner similar to other S.W.I.F.T. users. The EBA monitors the operations of the EBA Clearing Service (a netting payment system), in particular the positions of all the clearing banks, through a direct connection to the clearing computer.; (2) The netting payment system maintained by the Euro Banking Association.
�Euro-ISDN: The common European ISDN standard, agreed in 1993, providing a basic range of services and supplementary services using 30 B-channels plus a D-channel over an E1 trunk.
�European Telecommunications Standard (ETS): A standard produced by the European Telecommunications Standards Institute.
�European Telecommunications Standards Institute (ETSI): A European organization founded in 1988 and responsible for the establishment of technical telecommunications standards. It produces European Telecoms Standards (ETS) for its membership, which consists of network operators, PTT manufacturers, users, and research institutes. Some of these functions used to be performed by the Commission of European Post and Telegraph. ETSI is similar in function to the International Telecommunication Union. See also International Telecommunication Union.
�EuroReady product: A product that is capable of correctly processing monetary data in the euro denomination. For a product to be considered EuroReady, all products with which it is used must also be EuroReady. IBM hardware products that are EuroReady might or might not have an engraved euro sign key on their keyboard.
�evaluation mission: A brief statement that defines the work objectives for the test team for a specific schedule. This statement changes to reflect the objectives of each iteration.
�evaluation rule: In a privacy management environment, an expression that (a) represents an individual's choice to opt in or opt out of a specified group or purpose or (b) represents another condition, such as a legal restriction on the use of PII. See also condition rule.
�even positive acknowledgment (ACK0): In BSC, the even-numbered, positive acknowledgment character, which indicates that text was received without transmission errors.
�event: (1) An occurrence of significance to a task or system. Events can include completion or failure of an operation, a user action, or the change in state of a process. See also indicator collection, resource model, journal receiver, receiver.; (2) A change to an application entity that triggers a business object. This business object, which contains data and a verb, becomes an event in the WebSphere business integration system. See also application event.; (3) In the Notes Calendar, an entry with a duration of at least one day. For example, an all-day meeting or a vacation is an event.; (4) A transition in database activity caused by users, applications, or the database manager. Events include connections, deadlocks, and transactions.; (5) A change to data in an enterprise information system (EIS) that results in an update to the event store. The adapter processes event store information to deliver business objects from the EIS to the endpoints that subscribe to those business objects.; (6) A change to a state, such as the completion or failure of an operation, business process, or human task, that can trigger a subsequent action, such as persisting the event data to a data repository or invoking another business process.
�event access interface: A Java EE stateless session bean that provides methods for querying historical events from the event server.
�event action: The action that IBM Director takes in response to a specific event or events.
�event action list: In VisualAge RPG, a list of controls that indicates the action subroutine to be called by the event of each control.
�event action plan: A user-defined plan that determines how IBM Director will manage certain events. An event action plan comprises one or more event filters and one or more customized event actions.
�event adapter: Software that converts events into a format that the Tivoli Enterprise Console product can use and forwards the events to the event server.
�event analyzer: A database object that provides information about the database events that have taken place. An event analyzer is used with the event monitor file to assess and record performance information.
�event buffering: The process of holding events in a buffer at the source until the event source can connect to the event server.
�event catalog: A repository of event metadata used by applications to retrieve information about classes of events and their permitted content.
�event catalog application: An application that stores or retrieves event metadata in the event catalog, such as a management or development tool, or an event source or event consumer.
�event class: A classification for an event that indicates the type of information that the event adapter can send to the event server.
�event control block: A control block used to represent the status of an event.
�event correlation: The process of analyzing event data to identify patterns, common causes, and root causes. Event correlation analyzes the incoming events for predefined states, using predefined rules, and against predefined relationships. See also risk correlation.
�event correlation sphere: The scope of an ECSEmitter method that allows an event consumer to correlate events. Each event includes the identifier of the correlation sphere to which it belongs and the identifier of its parent correlation sphere from the event hierarchy.
�event data: In an event message, the part of the message data that contains information about the event (such as the queue manager name, and the application that gave rise to the event). See also event header.
�event database: A database in which events that can be monitored are stored, and which is required to support the persistence of those events.
�event-data substitution variable: A variable that can be used to customize event-specific text messages for certain event actions.
�event definition: A description of event classes and their allowed content, which is stored by the event catalog.
�event delivery: The action of delivering an event (by a connector) to InterChange Server.
�event detection: The process by which the WebSphere business integration system identifies that an application event has been generated. Event detection is part of the overall process of event notification. See also application event, event detection mechanism, event notification, event notification mechanism, event trigger.
�event detection mechanism: The mechanism or processes that identify that an application event was generated. For example, some application connectors use database triggers to detect events. See also event detection, event notification.
�event-driven payments: In WebSphere Commerce, a software layer (API) that provides payment-processing logic at a business level. As a subcomponent of the order system, event-driven payments determines what type of payment actions should be executed at specific times or business events in the life cycle of an order or a return.
�event-driven translation: A translation automatically triggered by the receipt of a document.
�event emitter: A component of the Common Event Infrastructure that receives events from event sources, completes and validates the events, and then sends events to the event server based on filter criteria. See also Common Event Infrastructure, event server, event source.
�event escalation: The notification that a violation or trend toward violation of a service level agreement has been detected as a result of evaluating and analyzing metric data. Events are created in various ways, using, for example, SNMP traps, Tivoli Enterprise Console events, or e-mail notification.
�event expression: A definition of the specific state when an event is true.
�event factory: An object that returns new instances of either the CommonBaseEvent element or of the specialized classes representing complex property data types.
�event filter: (1) In OSI, a method for excluding certain types of events so that they are not reported.; (2) In a Tivoli environment, rules that determine which events are sent from an event adapter or displayed on an event console. Also used to determine which events a specific correlation rule will apply to.; (3) A logical expression of criteria that determines which events are forwarded to the application program that registers the event filter with the event sieve agent.; (4) The criteria that must be met by an event before a rule action is executed.; (5) A filter that specifies the event criteria for an event action plan. Events must meet the criteria specified in the event filter in order to be processed by the event action plan to which the filter is assigned.
�event forwarding discriminator (EFD): A managed object that describes the criteria used to select which event reports are sent and to whom they are sent.
�event group: (1) A set of events that meet certain criteria defined by event group filters, which include constraints that are expressions that define the filter conditions. Event console operators can monitor event groups that are relevant to their specific areas of responsibility.; (2) A container for inbound events that enables you to group events without the overhead of creating a new monitoring context. Event groups are purely a visual construct and are not represented in the monitor model.; (3) A set of criteria that is applied to events to identify a subset of those events. The criteria include constraints expressions that define the filter conditions.
�event handler: Software that initiates an event response configured by the administrator.
�event header: In an event message, the part of the message data that identifies the event type of the reason code for the event. See also event data.
�event identifier (EID): A 2-byte hexadecimal number that identifies the event producing a trace record.
�event isolation: A feature of InterChange Server that ensures that when multiple collaborations process events containing the same business object instance, the events are processed sequentially in the order received. InterChange Server does not automatically perform event isolation. The collaboration developer must design templates to take advantage of this feature. See also collaboration-object group, port matching.
�event listener: A type of asynchronous bean that serves as a notification mechanism and through which Java Platform, Enterprise Edition (Java EE) components within a single application can notify each other about various asynchronous events.
�event log: (1) A log that contains information about events for a particular system or group, for a particular metric, or for all the events that are associated with a specific monitor.; (2) A log that maintains a history of event messages issued by all metadata servers in a cluster.
�event management service: A service of InterChange Server that persistently stores events until collaborations are finished using them. This service ensures that InterChange Server and collaborations can recover from crashes without losing events.
�event management table: One of three types of database tables in the InterChange Server repository, the event management tables store business objects that are currently being processed.
�event message: A message that contains information (such as the category of event, the name of the application that caused the event, and queue manager statistics) relating to the origin of an instrumentation event in a network of WebSphere MQ systems.
�event model: The part of the monitor model that contains references to all of the elements of the event definitions used in the monitor model.
�event monitor: A database object for monitoring and collecting data on database activities over a period of time. For example, starting the database might be an event that causes an event monitor to track the number of users on the system by taking an hourly snapshot of authorization IDs using the database.
�event monitoring point (EMP): Point in the CICS code at which CICS monitoring data is collected. See also monitoring control table.
�event notification: The mechanism by which events are polled for and detected by a connector. See also event detection, event detection mechanism, event notification mechanism, event trigger.
�event notification mechanism: The mechanism or processes that notify the connector that an application event was generated. The event notification mechanism includes all of the subprocesses of event polling. See also event detection, event notification.
�event object: An object that captures information about an event that has occurred in a system application and then passes the event object to the event infrastructure, where it is published to event subscribers or stored in a database for later retrieval. The event object describes an event type, indicates when the application generated the event, and identifies properties relevant to the event.
�event part: An XML Schema Definition (XSD) type that provides information about the structure of part of an event. A single event definition can have different event parts that are defined by different XML schemas.
�event polling: The process by which a connector retrieves application events. Event polling consists of requesting and retrieving events from the event table and passing them to the connector for further processing. In most cases, the processed event or the status of the event is returned to the application. You can customize how the connector polls for event, including setting specific times and frequency. See also event request.
�event pool: The set of events recognized by an activity (system events and user events that have been defined to it). Each activity has an event pool associated with it. An activity's event pool is initialized when the activity is created, and deleted when the activity is deleted. Event-related commands such as DEFINE INPUT EVENT and DEFINE COMPOSITE EVENT operate on the event pool associated with the current activity.
�event publishing: A data publishing solution that captures transactional data and publishes it to WebSphere MQ queues as XML messages. User applications then can retrieve that data from the queues. See also Q Capture program, publishing queue map.
�event queue: (1) The queue onto which the queue manager puts an event message after it detects an event. Each category of event (queue manager, performance, configuration, instrumentation, or channel event) has its own event queue.; (2) An ordered list of events.
�event record: A temporary record of an application, which is stored in cache until the connector picks it up for processing. See also event store.
�event report: (1) In OSI, the unsolicited notification of a significant occurrence by an agent to a manager .; (2) The unsolicited report that an event has occurred. In an Open Systems Interconnection (OSI) context, when a managed object emits a notification, the agent uses one or more event forwarding discriminators (EFDs) to find the destinations to which the report is sent.
�event request: See event retrieval.
�event response: A preconfigured action that is triggered when an event is generated. The administrator can configure one or more event responses to specific event types. Examples of event responses include logging the event, notifying an individual or group by e-mail that the event has occurred, sending the event to an SNMP application, and initiating a program or script. See also response level.
�event retrieval: The process of polling and retrieving events from the repository event store. When a connector initially receives an event from the event store, it sends a request business object with only key data back to the application to retrieve the full-valued business object. The data is then passed back to the polling mechanism for further processing. See also event polling.
�event script: A script attached to a particular event. Examples in LotusScript are Initialize, Queryopen, and Postopen. When the event occurs, the script runs.
�event sequencing: A feature of InterChange Server that ensures that when multiple threads of the same collaboration process events contain the same business object instance, the events are processed sequentially in the order received. InterChange Server automatically performs event sequencing. The collaboration developer does not have to design steps to take advantage of this feature.
�event server: (1) A server program that processes events.; (2) A component of the Common Event Infrastructure that receives events from the event emitters. See also Common Event Infrastructure, event source, event emitter.
�events file: In CoOperative Development Environment/400, a machine-readable file, created by a compiler or when the Verify program choice is selected, that contains information about locations of errors in a source file.
�event source: (1) An object that supports an asynchronous notification server within a single Java virtual machine. Using an event source, the event listener object can be registered and used to implement any interface.; (2) An application that uses an event emitter to send events to the event server. See also event server, event emitter.
�event store: A persistent cache where event records are saved until a polling adapter can process them. See also event record, event table.
�event table: A table that is created in an application and that stores an event record. This table is created as part of the installation and configuration of a connector. Not all connectors use an event table. See also event store.
�event-to-method connection: A connection from an event generated by a bean to a method of a bean. When the connected event occurs, the method is executed.
�event trigger: The mechanism or processes that detect an application event and generate an event from it. Typically, an event trigger adds an entry to an event table for delivery to the connector. The event trigger is part of the event notification process. See also event detection, event notification.
�event-triggered flow: A data flow triggered by an event that the collaboration receives from a connector controller. A connector initiates an event-triggered flow.
�Event Viewer: A tool provided by Windows systems to examine and manage log files.
�evolutionary development: An iterative development strategy that acknowledges that user needs are not fully understood and therefore requirements are refined in each succeeding iteration (elaboration phase). See also incremental development, iterative development.
�exabyte (EB): For processor, real and virtual storage capacities and channel volume: 1 152 921 504 606 846 976 bytes, or 2 to the power of 60. For disk storage capacity and communications volume: 1 000 000 000 000 000 000 bytes.
�exact end position: In RPG, an entry on the output specifications that indicates where the end position of a field or constant is to be placed in the output record. See also relative end position.
�exact-name format: In AFP support, a print descriptor naming convention that uses system-specific (actual) group names instead of group alias names.
�EXCEPT group name: In RPG, a name used in the place of indicators to identify a record or group of records written at exception output time.
�exception: A condition or event that cannot be handled by a normal process.
�exceptional wait: In Performance Tools, that portion of internal response time that cannot be attributed to the use of the processor and disk. An exceptional wait is caused by contention for internal resources of the system, for example, waiting for a lock on a database record.
�exception class data: CICS monitoring information on exception conditions raised by a transaction, such as queuing for VSAM strings or waiting for temporary storage. This data highlights possible problems in system operations. See also monitoring record.
�exception condition: An abnormal condition that may arise during execution of a program.
�exception handler: (1) A set of routines that responds to an abnormal condition. An exception handler is able to interrupt and to resume the normal running of processes.; (2) In C++, the catch block that catches exceptions when they are thrown from a function enclosed in a try block.
�exception highlighting: In PSF, the markings placed on the printed page to indicate the location of a data-stream error.
�exception list: A list of exceptions that have been generated during the processing of a message, with supporting information.
�exception queue: A queue to which messages associated with certain exceptional conditions, such as errors, are routed.
�exception report: A WebSphere MQ report message type that is created by a message channel agent when a message is sent to another queue manager, but that message cannot be delivered to the specified destination queue.
�exception request (EXR): In SNA, a request that replaces another request in which an error was detected. Note: The exception request contains a 4-byte sense field that identifies the error in the original request and, except if there were some path errors, is sent to the destination of the original request; if possible, the sense data is returned in a negative response to the sender of the original request.
�exception response (ER): In SNA, a value in the form-of-response-requested field of the request header that directs the receiver of the request to return a response only if the request is unacceptable as received or if the request cannot be processed; that is, only a negative response can be returned. See also definite response, no response.
�exception symptom code (ESC): A 2-byte error code that describes an exception in terms of class, type, and symptom.
�exception table: (1) A table that holds rows that violate referential constraints or check constraints that the CHECK DATA utility finds.; (2) A user-created table that reflects the definition of the table being loaded.
�exception trace entry: An entry made to the internal trace table and any other active trace destinations when CICS detects an exception condition. It gives information about what was happening at the time the failure occurred and what was being used.
�exception transition link: In a collaboration template's activity diagram, the line that represents the path between a node for an action, subactivity, or iterator that encountered an exception and the next node. See also normal transition link, transition link.
�exchange: A set of one or more non-concurrent related sequences passing between a pair of fibre-channel ports. An exchange encapsulates a "conversation" such as a small computer system interface (SCSI) task or an Internet Protocol (IP) exchange. Exchanges can be bidirectional and can be short--lived or long-lived.
�exchange data link (EDL): A serial connection that carries messaging information between DirectTalk and the Lucent Technologies 1AESS, Northern Telecom DMS100, Ericsson MD110 switch, or Siemens Hicom 300.
�exchange identification (XID): A specific type of basic link unit that is used to convey node and link characteristics between adjacent nodes. XIDs are exchanged between link stations before and during link activation to establish and negotiate link and node characteristics, and after link activation to communicate changes in these characteristics.
�exchange log name: (1) The process by which, when an APPC connection is established between two CICS systems (or reestablished after failure), the name of the system log currently in use on each system is passed to the partner. The exchange log name process affects only synclevel 2 conversations. It is used to detect the situation where a failed CICS has been communicating with a partner that is waiting to perform session recovery, and is restarted using a different system log. See also logname.; (2) A process used when sessions are first established to determine which log is being used by the remote system.
�exchange media: The diskette or the tape that the user uses when exchanging data with other systems.
�exchange station ID (XID): In communications, a data link command or response for recognizing the primary station and a secondary station.
�EXCI: See external CICS interface.
�exclude: To remove a managed disk (MDisk) from a cluster because of certain error conditions.
�exclude authority: An object authority that prevents the user from using the object or its contents. See also all authority.
�excluded: Pertaining to the status of a managed disk that the cluster has removed from use after repeated access errors.
�exclude data set: In aggregate backup and recovery processing, a data set in the selection-data-set exclude list. This data set is excluded from being processed by aggregate backup.
�exclude list: An optional list in the selection data set that identifies those data sets that are to be excluded from aggregate backup processing.
�exclusive access: (1) An access intent that establishes the intent of an application to reserve the exclusive use of the database. If a subsystem requests and DBRC grants exclusive access to a subsystem, then no other subsystem may access the database concurrently, regardless of the share level of the database.; (2) A condition that permits write access to a project to a single user only.
�exclusive allow-read lock state: The lock on an object that allows only one job to use the object, but allows other jobs to read the object. The predefined value for this lock state is *EXCLRD.
�exclusive control: (1) A type of access control in which VSAM keeps control of the control interval (CI) containing a specific record until a REWRITE, UNLOCK, or DELETE command is issued for that record. The purpose of exclusive control is to protect against simultaneous update.; (2) A method for preventing multiple, write-add, basic direct access method (BDAM) requests from updating the same dummy record or writing over the same available space on a track. When specified by the user, the exclusive-control lock requests that the system prevent the data block that is about to be read from being modified by other requests; it is specified in a read macro and released in a write or read macro. When a write-add request is about to be processed, the system automatically obtains exclusive control of either the data set or the track.
�exclusive intent: In IMS, the scheduling intent type that prevents an application program from being scheduled concurrently with another application program. See also scheduling intent.
�exclusive-key storage: In MVS key-controlled storage protection, storage with storage keys other than open-key.
�exclusive level sharing: See level zero data sharing.
�exclusive lock: A lock that prevents concurrently executing application processes from accessing database data. See also gross lock, shared lock, share lock.
�exclusive lock state: The lock on an object that allows only one job to use the object; no other job can use the object. The predefined value for this lock state is *EXCL.
�exclusive method: In object-oriented programming, a method that is not intended to exhibit polymorphism; one with specific effect.
�exclusive mode: An optional mode of terminal operation in which a terminal may receive no output other than a response to an input. Any output excluded from being sent is held for transmission until the terminal is removed from exclusive mode.
�exclusive-OR: A logic operator having the property that if P is a binary digit and Q is a binary digit and either P or Q is 1, but not both, then P exclusive-OR Q is 1.
�exclusive reference: A call from a section in one overlay path to one in a different path. Because an exclusive reference causes the calling section to be overlaid, return to the calling section is not possible.
�exclusive segment: A type of segment that is in the same region but not in the same path. Exclusive segments cannot be in virtual storage simultaneously. See also inclusive segment.
�exclusive SQL statement: An SQL statement that must be followed by a commit or rollback operation before any other SQL statement can be executed in the same SQL session. Exclusive SQL statements are grouped into sets; the database manager can execute only one SQL statement from the set at one time. Examples of exclusive SQL statements are WLM exclusive SQL statements and AUDIT exclusive SQL statements.
�exclusive submap: In Tivoli NetView, a submap that is created by an application program that wants the exclusive right to control what happens in the application plane of the submap. See also shared submap.
�exclusive use: A means by which CICS and data managers, such as SQL/DS, combine to prevent concurrent updates of resources. A transaction updating a recoverable resource gets control of that resource until it terminates or indicates that it wants to commit those changes with a syncpoint command. Other transactions requesting the same resource must wait until the first transaction has finished with it.
�EXEC interface: See application programming interface.
�EXEC interface block (EIB): A control block associated with each task in a CICS command-level environment. The EIB contains information that is useful during the execution of an application program (such as the transaction identifiers) and information that is helpful when a dump is being used to debug a program.
�EXEC interface stub: The stub link-edited with every command-level program. It is part of the CALL interface between EXEC CICS commands and the CICS EXEC interface program (EIP).
�executable architecture: A partial implementation of the system, built to demonstrate selected system functions and properties, in particular those satisfying non-functional requirements.
�executable file: A file that contains programs or commands that perform operations on actions to be taken.
�executable program: A program in a form suitable for execution by a computer. The program can be an application or a shell script.
�executable statement: An SQL statement or XQuery expression that can be embedded in an application program, dynamically prepared and executed, or issued interactively.
�execute authority: An object authority that allows the user to run a program or procedure or to search a library or directory.
�execute component: The autonomic manager component that changes the behavior of the managed resource using an effector, based on the actions recommended by the plan component. See also autonomic control loop, effector.
�execution: The process of carrying out an instruction or instructions of a computer program by a computer. (I) (A)
�execution agenda: A class that acts as a table that plots the relationship between promotions and promotion policies. The execution agenda contains a list of promotions which are potentially applicable to an order, and all of the policies that are applicable to each individual promotion in the list.
�execution context: In SQLJ, a Java object that can be used to control the execution of SQL statements.
�execution control list (ECL): A security feature that controls which formulas and scripts created by other users can run on a workstation.
�execution diagnostic facility (EDF): A CICS facility used for testing application programs interactively online, without making any modifications to the source program or to the program preparation procedure. The facility intercepts execution of the program at various points and displays information about the program at these points. Also displayed are any screens sent by the user program, so that the programmer can converse with the application program during testing just as a user would do on the production system.
�execution environment: (1) See runtime environment.; (2) In UML modeling, a type of node that represents a particular execution platform, such as an operating system or a database management system.
�execution group: A named process or set of processes within a broker in which message flows are executed. The broker is guaranteed to enforce some degree of isolation between message flows in distinct execution groups by ensuring that they execute in separate address spaces, or as unique processes.
�execution host: In a cross-compilation environment, the machine on which compiled code is executed. See also compilation host.
�execution interface program (EIP): Converts high-level (command-level) requests into the corresponding internal macro-level requests.
�execution log: A log that maintains a history of all the events that occurred while a running a workflow.
�execution node: The network job entry (NJE) node upon which a job is to be executed.
�execution time: The period of time when a request specified by an SQL statement is acted upon by a database. See also system time.
�execution trace: A chain of events that is recorded and displayed in a hierarchal format on the Events page of the integration test client.
�exemption: In label-based access control, a privilege that causes one LBAC rule of one security policy to be bypassed for a user or a set of users to whom that privilege is granted.
�exit: To execute an instruction within a section of a computer program (for example, within a loop, subroutine, or module) in order to terminate the execution of that section.
�exit action: An action executed upon exiting a state in a state machine regardless of the transition taken to exit that state.
�exit breakpoint: A breakpoint set on a component element that is hit after the component element is invoked.
�exit condition: A Boolean expression that controls when processing at a process node is completed.
�exit manager: A program residing in an authorized program facility (APF) library that controls the flow of a predefined set of events.
�exit point: A specific point in a system function or program where control may be passed to one or more specified exit programs. See also exit program.
�exit point provider: The person responsible for defining the exit point information, defining the format of the data the exit program receives, and calling the exit programs.
�exit program: (1) A user-written program that is given control during operation of a system function.; (2) A program to which control is passed from an exit point. See also exit point.
�exit programming interface (XPI): Provides global user exit programs with access to some CICS services. It consists of a set of function calls that can be used in user exit programs to extend CICS functions.
�exit routine: A program that receives control from another program in order to perform specific functions.
�exit status: The return value from a thread. A variable of type void * typically contains a pointer to a control block pointer or a return value that shows under what conditions the thread ended.
�expanded communications buffer: A feature of the 3741 device that allows multiple records to be transmitted or received in one block of data.
�expanded memory: On most computers, additional memory accessed through an adapter or feature card along with a device driver program. See also conventional memory.
�expanded output: An option for subcommands that lets an application program receive more variable data than for standard output.
�expanded QName: A QName where the prefix from the lexical form is resolved into the namespace URI. If the lexical form of the QName does not have a prefix, the namespace URI is the default namespace, which could be empty. See also lexical QName, qualified name.
�expanding conversion: A process that occurs when the length of a converted string is greater than that of a source string. See also contracting conversion.
�expansion box: A box that a user can click to expand or collapse a branch of a tree. The box is filled, or solid, when the branch is collapsed and is empty, or hollow, when the branch is expanded.
�expansion I/O unit: Additional hardware units used to provide additional disk and I/O capacity. Expansion I/O units are located in SP frames, attached to specific SP Nodes, and controlled by a frame supervisor. Expansion I/O units are not CSM nodes.
�expansion port (E_port): In the building of a larger switch fabric, a port used as an inter-switch expansion port to connect to the E_port of another switch. See also isolated E_port.
�expansion slot: In personal-computer systems, one of several receptacles in the rear panel of the system into which a user can install an adapter.
�expansion unit: (1) A feature that can be connected to a system to provide additional storage and processing capacity.; (2) A feature that contains I/O hardware such as cards, tapes, and disk units. The system may have multiple expansion units. An expansion unit can be bolted directly to the side of a system and is contained within the system covers. An expansion unit can also be mounted on top of a rack and has its own covers. Internal signal cables interconnect the expansion unit to the system or rack.; (3) A machine type or feature that can be connected to a system unit to provide additional storage and processing capacity. This expansion unit may contain I/O hardware such as cards, tapes, and disk drives.
�expected inventory: Inventory that has been ordered from a vendor and that is expected to be received by the Seller. This information is contained in an expected inventory record. See also expected inventory record, seller.
�expected inventory record: Lists the inventory that has been ordered from a vendor and that is expected to be received by the Seller. An expected inventory record may contain information for multiple items, fulfillment centers, and dates. See also expected inventory, inventory receipt, seller.
�expedited data: In OSI, a data transfer service provided by the session layer to transfer a small amount of data that is not subject to permission-to-send and flow-control restrictions. The OSI layers attempt to expedite the transfer of such data.
�expedited forwarding: A per-hop behavior in the Differentiated Services (DiffServ) standard that is used to create a virtual leased line service.
�expedited message handler queue (EMHQ): The expedited message handler shared queue on a coupling facility list structure.
�expedited message handling (EMH): An IMS Fast Path facility that processes single-segment input and output messages. Fast Path messages that use the EMH bypass the normal message queuing and application scheduling and therefore these messages are processed faster than non-Fast Path messages.
�expedited order: A release of an advanced order for which a user has requested expedited handling and shipping for particular order items.
�expert cache: An extension of the storage management function of the i5/OS operating system that allows the single-level storage architecture to take better advantage of the main storage (cache) capacities.
�expiration: The process by which data sets or objects are identified for deletion because their expiration date or retention period has passed. On direct access storage devices (DASDs), data sets and objects are deleted; on tape, when all data sets have reached their expiration date, the tape volume is available for reuse.
�expiration date: (1) The date at which a file is no longer protected against automatic deletion by the system.; (2) The date after which a database file member should not be used.
�expiration processing: In DFSMSrmm, the process of inventory management that ensures that expired volumes are released and that carries out required release actions on those volumes. See also inventory management.
�expiration time: The time at which a time-controlled CICS function is to be started.
�expired: In Backup, Recovery, and Media Services, pertaining to media that is available for a rewrite operation. Media is automatically expired when both the retention period (expiration date) and storage duration have been satisfied.
�expired password: A password that has not been changed within 180 days or more.
�explain: To capture detailed information about the access plan that was chosen by the SQL and XQuery compiler to resolve an SQL or XQuery statement. The information describes the decision criteria that are used to choose the access plan.
�explainable statement: An SQL or XQuery statement for which the explain operation can be performed. SELECT, UPDATE, INSERT, DELETE, and VALUES are explainable SQL statements.
�explained statement: An SQL or XQuery statement for which an explain operation was performed.
�explain snapshot: (1) A capture of compressed internal information that is collected when an SQL or XQuery statement is explained. This information is required by the Visual Explain tool. See also performance snapshot.; (2) A collection of information that is compressed when an SQL or XQuery statement is explained.
�explain statistics: The statistics in the catalog that are referenced when an SQL or XQuery statement is explained.
�explicit connection: A connection to a database in which both a user ID and password are specified.
�explicit destination: A destination identifier that refers to a specific route code. See also destination identifier, symbolic destination.
�explicit hierarchical locking: Locking that is used to make the parent-child relationship between resources known to the internal resource lock manager. This type of locking avoids global locking use when no inter-DB2 interest exists on a resource.
�explicit literal: In MFS, a literal field defined by the user for inclusion in an input or output message. See also default literal, literal field, system literal.
�explicit privilege: A privilege that has a name and is held as the result of SQL GRANT and REVOKE statements: for example, the SELECT privilege. See also implicit privilege.
�explicit rebind: A process by which SQL statements are bound by a user issuing the REBIND or db2rbind command. See also rebind.
�explicit scope terminator: In COBOL, a reserved word that ends the scope of a particular Procedure Division statement.
�explicit trusted connection: A trusted connection that allows both switching the current user ID of the connection to a different user ID and acquiring a trusted context role (a default or user-specific role). See also trusted connection.
�exploratory testing: A technique for testing software that entails minimal planning and often includes limited software documentation. The test results, which rely on the tester's skill and knowledge, guide ongoing and subsequent tests. Exploratory testing is often conducted in short sessions.
�exponent: (1) A number, indicating to which power another number (the base) is to be raised.; (2) In floating-point format, an integer constant specifying the power of ten by which the base of the decimal floating-point number is to be multiplied.
�exponentiation: The process in which a quantity is raised to a power.
�exponent-overflow exception: The program interruption that results when an overflow occurs during execution of a floating point instruction. The overflow is triggered when the resulting value from the instruction has a characteristic that is larger than the floating-point data format can handle. See also overflow.
�exponent-underflow exception: The program interruption that occurs when the result of a floating-point instruction has a nonzero fraction and a characteristic is smaller than the floating-point data format can handle. An exponent-underflow exception can be disabled by using the bit setting on a program mask.
�export: (1) To copy data from database manager tables to a file using formats such as PC/IXF, DEL, WSF, and ASC. See also import.; (2) In Network File System (NFS), to make file systems on a server available to remote clients.; (3) To save a Notes document or view in a non-Notes format.; (4) To move information from one system or program to another.; (5) An external symbol defined in a module or service program that is available for use by other modules or programs. See also import.; (6) A function or process that converts an internal file to some standard file format for use outside of an application.; (7) The operation to remove one or more logical volumes (LVOLs) from a virtual tape server (VTS) library. The list of LVOLs to export is written on an export list volume and then the export operation itself is initiated.; (8) An access method services (AMS) operation to create a backup or portable copy of a Virtual Storage Access Method (VSAM) cluster, alternate index, or integrated catalog facility (ICF) user catalog.; (9) An exposed interface from a Service Component Architecture (SCA) module that offers a business service to the outside world. An export has a binding that defines how the service can be accessed by service requesters, for example, as a Web service.
�export agent: A MERVA Liquidity Manager component that exports scheduled messages from the MERVA Liquidity Manager database to MERVA queues or to DB2 interface tables.
�exported form: In query management, the source file member that results from running an EXPORT FORM command.
�exported logical volume: A logical volume (LVOL) that has been exported and currently resides on a stacked volume outside a virtual tape server (VTS) library.
�exported query: In query management, the source file member that results from running an EXPORT QUERY command.
�export file: (1) The file containing data that has been exported.; (2) A file created during the development process for inbound operations that contains the configuration settings for inbound processing.
�export list volume: A virtual tape server (VTS) logical volume (LVOL) containing the list of LVOLs to export.
�exports data set: In z/OS, an MVS file on the server containing entries for directories that can be exported to Network File System (NFS) clients. It is used by the server to determine which MVS files and prefixes can be mounted by a client, and to write-protect MVS files on the server.
�exposed name: A name specified in a FROM clause such that it can be referenced elsewhere in the query. Exposed names include correlation names and, if correlation names are not specified for them, table names, view names, nicknames, and alias names. See also table designator.
�express alternate PCB: An alternate PCB to which output messages are sent before termination of the application program. See also alternate program communication block.
�expression: (1) In programming languages, a combination of terms and operators that can be evaluated to a single value using the rules of precedence for the given language.; (2) An SQL or XQuery operand or a collection of SQL or XQuery operators and operands that yields a single value.
�expression context: All of the information that can affect the result of a specific XQuery expression. This information is organized into two categories called the static context and the dynamic context. See also dynamic context, static context.
�express payment: A payment that has been assigned to the RTGS-Express (RTGS-E) channel. Non-timed express payments are treated as if they have immediate priority, except that, unlike other immediate payments, they are not sent if either they or the RTGS-E channel is stopped.
�EXR: See exception request.
�exrequisite: A component or service that must not be present. In other words, the components, resources, or services listed as exrequisites of a component must not be installed in conjunction with the component. See also requisite.
�exrequisite dependency: A condition in which a configuration change is performed only if a specified condition does not exist. For example, a software package will be installed on targets only where a package with an exrequisite dependency is not installed.
�extend: (1) To increase the portion of available space that can be used to store database information or recovery log information. See also reduce.; (2) To install more than one package in the same version of Eclipse in order for their application functions to work together in the workbench environment.
�extended ACL: A security feature that restricts a user's access to the Domino directory and extended directory catalog.
�Extended Adaptive Cache: A large high-speed memory that is used exclusively to store user data that would otherwise have been accessed from one or more disks.
�Extended Adaptive Cache Simulator: A performance tool that allows system users to assess the benefits of an Extended Adaptive Cache before purchasing one. When the Extended Adaptive Cache simulator is active on a specified storage controller, performance information is generated for a system's actual workload over time.
�extended addressability: The ability to create and access a Virtual Storage Access Method (VSAM) data set that is greater than 4 GB.
�extended addressing: The use of 31-bit addresses (above the 16MB line) which multiplies by 2 to the power of 7 the range of virtual storage that can be addressed. See also extended link pack area.
�extended attribute: (1) Information attached to an object that describes the object to an application system or user.; (2) A characteristic of a shared folder file. Each extended attribute consists of a name, a value, and a set of flags.; (3) In configuration management, a configuration item (CI) attribute that is not part of the original CI definition, but is added by the customer.; (4) In change management, a request for change (RFC) type attribute that provides information that is needed to fulfill the RFC. A required RFC type attribute must be specified when an RFC of that type is created.
�extended attribute flag: A flag that is stored for the extended attribute, such as the read/write flag.
�extended attribute name: The name that identifies the specific extended attribute that is to be stored, changed, or retrieved.
�extended attribute subprofile: The interchange document subprofile that contains non-DIA extended attributes for a document.
�extended attribute value: The data stored in an extended attribute.
�Extended Binary Coded Decimal Interchange Code (EBCDIC): A coded character set of 256 8-bit characters developed for the representation of textual data. See also American Standard Code for Information Interchange.
�extended bin support: In DFSMSrmm, the start and completion information stored in volume and bin records for volume moves to and from bin-managed storage locations.
�extended character: (1) A character other than a 7-bit ASCII character. An extended character can be a 1-byte code point with the eighth bit set (ordinal 128 through 255).; (2) Double-byte characters that are stored in a DBCS font file, not in the hardware of a DBCS-capable work station. When displaying or printing extended characters, the work station receives them from the DBCS font table under control of the extended character processing function of the operating system. See also basic character.
�extended character processing: A function of the operating system that is required to make characters stored in a DBCS font file available to a DBCS-capable work station. Basic characters, which are stored in the work station, do not require extended character processing. Extended characters, which are stored in a DBCS font table, require extended character processing before they can be displayed or printed. See also basic character.
�extended checkpoint/restart: The facility that allows batch processing programs to establish database positioning and initiate user-specified areas with a DL/I call in place of an OS CHKPT macro.
�extended CICS dynamic storage area (ECDSA): Storage area allocated above the 16MB line for CICS code and control blocks that are eligible to reside above the 16MB line but that are not eligible for the ERDSA (that is, they are not reentrant.)
�extended common service area (ECSA): A major element of z/OS virtual storage above the 16MB line. This area contains pageable system data areas that are addressable by all active virtual storage address spaces. It duplicates the common system area (CSA) which exists below the 16MB line.
�extended count key data (ECKD): An extension of the count-key-data (CKD) architecture.
�extended count key data device (ECKD device): A disk storage device that has a data transfer rate faster than some processors can utilize. A specialized channel program is needed to convert ordinary CKD channel programs for use with an ECKD device. See also fixed-block architecture disk device.
�extended data element: An application-specific element that contains information relevant to an event.
�extended data object (XDO): In an application program, a generic representation of a stored complex multimedia object that is used to move that object in to, and out of, storage. XDOs are most often contained within DDOs.
�extended deployment: The software that monitors network efficiency and distributes unexpected workloads.
�extended directory catalog: A directory catalog used by Domino servers that, to facilitate quick name lookups, retains the individual documents and the multiple, sorted views available in the Domino Directory.
�extended enterprise: A heterogeneous computing environment that often includes both centralized hosts and distributed workstations connected in a network. Gateways within the extended enterprise provide connections to local area networks (LANs). These LANs can serve any computing system architecture. See also Distributed FileManager.
�extended error queue element (EEQE): Data that describes an I/O error on a local DL/I database. EEQEs are recorded by CICS in the global catalog. CICS uses EEQEs to provide I/O error handling in XRF takeovers and in all non-XRF restarts, including cold starts.
�extended extract data set: In DFSMSrmm, a data set whose records combine data set and volume information into single records.
�Extended Fabrics: A feature that runs on the Fabric Operating System (OS) and allows creation of a fibre-channel fabric interconnected over distances of up to 100 km (62.14 mi).
�extended format: The format of a data set that is not basic format or large format and might be striped or compressed. The logical structure of the data set is the same as a data set that is not in extended format, but the physical format is different. See also striped data set, compressed format, large format, basic format.
�extended help: Online documentation that explains the purpose of the display. Extended help appears if the user presses the Help key when the cursor is outside the areas for which contextual help is available.
�Extended Industry Standard Architecture (EISA): The PC bus standard that extends the AT bus (ISA bus) to 32 bits and provides support for bus master. It was announced in 1988 as a 32-bit alternative to the Micro Channel that would preserve investment in existing boards. PC and AT adapters (ISA adapters) can plug into an EISA bus.
�extended interface: In query management, the set of language-specific interfaces used to run commands that require access to program variables.
�extended link pack area (ELPA): The portion of virtual storage above 16MB that contains frequently used modules. See also extended addressing.
�extended logical unit of work: A logical unit of work that is extended across successive ECI requests to the same CICS server.
�extended MCS console: In MVS, a console other than a multiple console support (MCS) console from which operators or programs can issue MVS commands and receive messages.
�extended memory: Personal computer memory that is addressed by DOS, from 1 MB to 16 MB, to increase conventional memory and expanded memory.
�extended messaging: A function of asynchronous messaging where the application server manages the messaging infrastructure and extra standard types of messaging beans are provided to add functionality to that provided by message-driven beans.
�extended namespace: An extension of the standard Windows or UNIX file system that allows access to versions of elements.
�extended pageable link pack area (EPLPA): The extension of the pageable link pack area (LPA) that resides above 16 MB in virtual storage. See also pageable link pack area.
�extended parameter list: In query management, the arguments of the extended interface that are not defined on the short interface.
�extended partition specification table (EPST): For Fast Path, an extension of the PST. It contains information for a dependent region that is unique to Fast Path.
�extended pointer set (EPS): In a HALDB, an expanded segment prefix that includes information that allows the use of indirect pointers. An EPS is created for logical child segments and secondary index segments.
�extended-precision: Pertains to the use of more than two computer words to represent a floating point number in accordance with the required precision. For example, in z/OS, four computer words are used for an extended-precision number.
�extended private area: An element of MVS/ESA virtual storage above the 16MB line. This area duplicates the private area except for the 16KB system region area.
�extended read-only dynamic storage area (ERDSA): An area of storage allocated above the 16MB line and used for eligible, reentrant CICS and user application programs, which must be link-edited with the RENT and RMODE(ANY) attributes. The storage is obtained in key 0, non-fetch-protected storage, if the system initialization parameters include RENTPGM=PROTECT. If RENTPGM=NOPROTECT is specified, the ERDSA is in CICS-key storage.
�extended record: A record in the DFSMSrmm extract data set that contains both data set and volume information.
�extended recovery facility (XRF): A facility that minimizes the effect of failures in z/OS, VTAM, the host processor, or high-availability applications during sessions between high-availability applications and designated terminals. This facility provides an alternative subsystem to take over sessions from the failing subsystem.
�extended remote copy (XRC): (1) In z/OS and S/390 environments, a hardware- and software-based, remote-copy, service option that provides an asynchronous volume copy across storage subsystems for disaster recovery, device migration, and workload migration.; (2) A function of a storage server that assists a control program to maintain a consistent copy of a logical volume (LVOL) on another storage facility. All modifications of the primary LVOL volume by any attached host are presented in order to a single host. The host then makes these modifications on the secondary LVOL. See also remote copy.
�extended restart (XRST): (1) An IMS/ESA system service call that can request that a program restarts normally or from a specific checkpoint ID, a time/date stamp, or (BMPs only) the last checkpoint issued. Extended restart can be requested by EXEC DLI commands or CALL DLI calls in a batch program or a BMP.; (2) A restart, initiated by a DL/I call, that reestablishes database positioning and user-specified areas. See also symbolic checkpoint.
�extended shared dynamic storage area (ESDSA): The user-key storage area for any non-reentrant user-key RMODE(ANY) programs, and also for any storage obtained by programs issuing CICS GETMAIN commands for storage above the 16MB boundary with the SHARED option.
�extended site business model: A business model that supports one seller with many sites aimed at different audiences.
�extended site store: A customer-facing store that is created by the site operator for the owner of the store. See also direct sales store.
�extended specify task abnormal exit (ESTAE): A z/OS macro that provides recovery capability and gives control to the user-specified exit routine for processing, diagnosing an abend, or specifying a retry address.
�extended SQL (ESQL): A specialized set of SQL functions and statements based on regular SQL, extended with functions and statements unique to WebSphere Business Integration Message Broker.
�extended syntax: QMF command syntax, which is used by the QMF callable interface, that defines variables that are stored in the storage area acquired by the callable interface application and shared with QMF.
�extended system contents directory (ESCD): An extension of SCD that is used for Fast Path.
�extended system queue area (ESQA): A major element of z/OS virtual storage above the 16MB line. This storage area contains tables and queues relating to the entire system. It duplicates above the 16MB line the system queue area (SQA) .
�Extended Terminal Option (ETO): A feature of IMS Transaction Manager that enables users to add or delete ACF/VTAM terminals or message queues (LTERMs) dynamically.
�extended time division multiple access (E-TDMA): See also Time Division Multiple Access.
�extended Tivoli environment: Machines and resources outside of the Tivoli environment that are managed from within the Tivoli environment.
�Extended UNIX Code (EUC): A protocol that can support sets of characters from 1 to 4 bytes in length. EUC is a means of specifying a collection of code pages rather than actually being a code page encoding scheme itself.
�Extended UNIX Code encoding scheme (EUC encoding scheme): An encoding scheme that defines a set of encoding rules that can support one to four character sets. The encoding rules are based on the ISO2002 definition for the encoding of 7-bit and 8-bit data. The EUC encoding scheme uses control characters to identify some of the character sets.
�extended user dynamic storage area (EUDSA): Storage area allocated above the 16MB line, used for data and for user application programs that execute in user-key and are eligible to reside above the 16MB line, but that are not eligible for the ERDSA (that is, not reentrant.)
�extend mode: (1) In COBOL, a method of adding records to the end of a sequential file when the file is opened.; (2) In COBOL, the state of a file after running an OPEN statement, with the EXTEND phrase specified for that file, and before running a CLOSE statement, without the REEL or UNIT phrase specified for that file.
�extend relationship: In UML modeling, a relationship between use cases that indicates that one use case (the extended use case) can extend another use case (the base use case).
�Extensible Hypertext Markup Language (XHTML): A reformulation of HTML 4.0 as an application of XML. XHTML is a family of current and future DTDs and modules that reproduce, subset, and extend HTML.
�Extensible Markup Language (XML): A standard metalanguage for defining markup languages that is based on Standard Generalized Markup Language (SGML).
�Extensible Stylesheet Language (XSL): A language for specifying style sheets for XML documents. Extensible Stylesheet Language Transformation (XSLT) is used with XSL to describe how an XML document is transformed into another document.
�Extensible Stylesheet Language Transformation (XSLT): An XML processing language that is used to convert an XML document into another document in XML, PDF, HTML, or other format.
�extension: (1) A class of objects designated by a specific term or concept; denotation.; (2) An element or function not included in the standard language.; (3) In Eclipse, the mechanism that a plug-in uses to extend the platform. See also extension point.
�extension point: (1) In the Reusable Asset Specification (RAS), a location in an asset that may be altered, customized, modified, or supplied by an asset consumer. An extension point can define the assets variability at design time, code time, and run-time.; (2) In Eclipse, the specification that defines what attributes and values must be declared by an extension. See also extension.
�extension script: A script that augments the Tivoli Data Warehouse scripts. For example, extension scripts might be scripts that run before or after the ETL steps are run.
�extent: (1) An allocation of space, within a container of a table space, to a single database object. This allocation consists of multiple pages.; (2) A continuous space on a disk, direct-access storage volume, or diskette that is occupied by or reserved for a particular data set, data space, or file.; (3) A unit of data that manages the mapping of data between managed disks (MDisks) and virtual disks (VDisks). See also multiple allegiance.
�extent map: A metadata structure stored within a table space that records the allocation of extents to each object in the table space.
�extent reduction: In DFSMShsm, the releasing of unused space, reducing the number of extents, and compressing partitioned data sets (PDSs).
�extent size: In a table space, the number of pages of table data that is written to a container before data is written to the next container.
�exterior gateway: In Internet communications, a gateway on one autonomous system that communicates with another autonomous system.
�Exterior Gateway Protocol (EGP): The mechanism that allows the exterior gateway of an autonomous system to share routing information with exterior gateways on other autonomous systems. See also Border Gateway Protocol.
�external: In programming languages, pertaining to a language object that has a scope that extends beyond one module, for example, the entry names of a module.
�external call interface (ECI): An application programming interface that allows a non-CICS program running on a client to call a CICS program located on a CICS server. Data is exchanged in the COMMAREA as for normal CICS interprogram communication. See also CICS client, client API.
�external CCD table: In SQL replication, a CCD table that can be subscribed to directly because it is a registered replication source. It has its own row in the register table, where it is referenced as SOURCE_OWNER and SOURCE_TABLE. See also consistent-change-data table, internal CCD table.
�external CICS interface (EXCI): A CICS application programming interface that helps to make CICS applications more easily accessible from non-CICS environments. It enables a non-CICS program (a client program) running in MVS to call a program (a server program) running in a CICS Transaction Server region and to pass and receive data by means of a communications area.
�external command: A command that causes the command-line interface (CLI) to generate a message and send it to a service to be processed.
�external coordinator: A coordinator that controls the two-phase commit for a unit of recovery (UR) owned by another subsystem or component.
�external data: (1) Data that is exported from one procedure and imported into another procedure. See also internal data.; (2) In COBOL, the data described in a program as external data items and external file connectors.; (3) Data obtained from a channel (for example, external credits pending).; (4) Data that persists over the lifetime of an enclave and maintains last-used values whenever a routine within the enclave is reentered.
�external data definition: A description of a variable appearing outside a function. It causes the system to allocate storage for that variable and makes that variable accessible to all functions that follow the definition and are located in the same file as the definition.
�external data item: In COBOL, a data item that is described as part of an external record in one or more programs of a run unit and which itself may be referred to from any program in which it is described.
�external data record: In COBOL, a logical record that is described in one or more programs of a run unit and whose constituent data items may be referred to from any program in which they are described.
�External Data Representation (XDR): A standard developed by Sun Microsystems, Incorporated to represent data in machine-independent format. Because XDR is a vendor-independent method for representing the data, new computer architectures can be integrated into the network without requiring the updating of translation routines.
�external data source: A data source for federation that is not crawled, parsed, or indexed by WebSphere Information Integrator OmniFind Edition. Searches of external data sources are delegated to the query application programming interface of those data sources.
�external entity: In XML, an entity such as an XML schema, an Extensible Stylesheet Language (XSL) style sheet, a document type definition (DTD), or other XML instance document that is accessed using a Uniform Resource Identifier (URI) in an XML instance document. This URI is required to validate the instance document.
�external file connector: In COBOL, a file connector that is accessible to one or more programs in the run unit.
�external function: A function that has its functional logic implemented in a programming language application that resides outside the database, in the file system of the database server. The association of the function with the external code application is specified by the EXTERNAL clause in the CREATE FUNCTION statement. See also external routine, function, built-in function, sourced function.
�external indicator: In RPG, an indicator that can be set by another program before a program is run, or changed by another program while the program is running. Valid external indicators are U1 through U8.
�externalized data value: See sensor value.
�externalized form: In query management, the name of the file resulting from running an EXPORT command against a form.
�externalized query: In query management, the name of the form resulting from running an EXPORT command against a query.
�external label: The label attached to the outside of a tape cartridge that can be read by the user and is sometimes machine-readable. The label contains the volume serial number (VOLSER) of the tape volume and sometimes additional information. See also internal label.
�external line format message (ELF message): A message that is not fully tokenized, but is stored in a single field in the TOF. Storing a message in ELF improves performance because no mapping is needed and checking is not performed.
�external link: (1) In a Web site, a link to a Web address that is outside the current Web site.; (2) A symbolic link that contains the name of an object that is outside the hierarchical file system.
�externally described data: Data contained in a file for which the fields and the records are described outside of the program (such as with files created by DDS, IDDU, or DB2 for i5/OS) that processes the file.
�externally described file: A file in which the records and fields are described to the system when the file is created, and used by the program when the file is processed. See also program-described data, program-described file.
�external message queue: A message queue used by all programs and procedures running within a job to send and to receive messages outside a job, for example, between an interactive job and the workstation user.
�external method: A method that has its method logic implemented in a programming language application that resides outside the database, in the file system of the database server. The association of the method with the external code application is specified by the EXTERNAL clause in the CREATE METHOD statement. See also external routine, method.
�external name: (1) A name that can be referred to by any control section or separately assembled or compiled module; a control section name or an entry name in another module.; (2) The name of an executable library or class file that resides on the database server and contains the logic for an external routine (an external procedure, external function, or external method).
�external object: An object that has a defined object type (such as *FILE or *PGM). In general, external objects can be displayed by a user. See also internal object.
�external partner: A trading community participant that sends business documents to and receives business documents from the internal partner. See also trading partner.
�external presentation interface (EPI): An application programming interface that allows a non-CICS client program to appear to a CICS server as one or more standard 3270 terminals. This enables the client to access, for example, CICS on System/390 transactions written for 3270 terminals, without needing to change the System/390 code. See also CICS client.
�external procedure: (1) A procedure that is not contained within a block. See also native SQL procedure.; (2) A procedure that has its procedural logic implemented in an external programming language application. The association of the procedure with the external application is specified by a CREATE PROCEDURE statement with a LANGUAGE clause that has a value other than SQL and an EXTERNAL clause that implicitly or explicitly specifies the name of the external application. See also external routine, procedure, external SQL procedure.
�external project: A project containing requirements used to establish traceability relationships with requirements in a currently open project. See also cross-project traceability.
�external reference: (1) A reference to a symbol, such as an entry point name, defined in another program or module.; (2) In a compare or merge session, a pointer to any object outside the item being compared or merged.
�external requirement: A requirement that resides in an external project. Traceability relationships can be created between requirements in different projects.
�external response time: Elapsed time from pressing the ENTER key or another AID key until the action requested by the terminal user is completed, and the next entry can be started. Elapsed time between the end of an enquiry or demand on a computer system and the beginning of the response.
�external routine: (1) A function, method, or procedure that has its routine logic implemented in a programming language application that resides outside the database, in the file system of the database server. The association of the routine with the external code application is specified by the EXTERNAL clause in the CREATE statement for the routine. See also external function, external procedure, external method, routine.; (2) In REXX, a program external to the user's program, language processor, or both. These routines can be written in any language (including REXX) that supports the system-dependent interfaces used by REXX to start it.; (3) A user-defined function or stored procedure that is based on code that is written in an external programming language.
�external security interface (ESI): A facility that enables client applications to verify and change passwords for user IDs on CICS servers. See also client API.
�external security manager (ESM): A security product that performs security checking on users and resources. RACF is an example of an ESM.
�external SQL procedure: An SQL procedure that is processed using a generated C program that is a representation of the procedure. When an external SQL procedure is called, the C program representation of the procedure is executed in a stored procedures address space. See also external procedure, native SQL procedure.
�external storage: Data storage not located in main or auxiliary storage, such as tape or diskette.
�external subsystem: A subsystem that provides a set of resources to be used by IMS, but not controlled by it.
�External Subsystem Attach Facility (ESAF): A facility that allows applications running under IMS to obtain data from external subsystems, such as DB2.
�external switch: In COBOL, a hardware or software device, defined and named by the compiler, that is used to indicate that one of two states exists.
�external symbol: (1) An entry-point name or external variable that is defined or referred to in a particular module or program.; (2) An item defined in a high-level language program that represents such things as procedures or variables. Resolving external symbols is the means by which the binder connects modules to form a bound program or a service program.
�external system: A system that exists outside a particular network.
�external throughput rate (ETR): The amount of useful work completed in a unit of time (for example, the number of transactions completed per elapsed second).
�external time reference (ETR): The synchronization of server time-of-day (TOD) clocks to ensure consistent time-stamp data across multiple servers and operating systems. External time reference (ETR) is the MVS generic name for the IBM Sysplex Timer. See also Sysplex Timer.
�external traceability: The ability to trace relationships between artifacts in two projects. See also cross-project traceability.
�external variable: A variable that is outside the lexical scope of the function, procedure, or program that is calling it.
�external view: In the Reusable Asset Specification (RAS), the collaboration diagram and icon showing the parameters of a specific collaboration.
�external writer: A program that performs output processing for data sets that are not eligible for processing by the primary job entry subsystem (JES). For example, an external writer might process a data set that has been directed to a printer and that will be stored on a device that is not supported by JES.
�extract control file: A file that contains statements that control the operation of an extractor utility program.
�extract data set: In DFSMSrmm, a data set used to generate reports.
�extract data set record: In DFSMSrmm, a record in an extract data set that is mapped by a DFSMSrmm mapping macro.
�extraction: The process of moving data from temporary tables on the WebSphere Commerce Analyzer server to the WebSphere Commerce Analyzer data mart. The data in the temporary tables was replicated from the WebSphere Commerce database.
�extraction time window: The window of time between the last time the WebSphere Commerce Analyzer extraction was run for this source and the current time. For WebSphere Commerce sources, this time window is indicated by the WebSphere Commerce Analyzer parameters TIME_CUT_OFF and TIME_CUT_OFF_PREV.
�extract, load, and transform (ELT): The process of extracting data from one or more sources, loading it directly into a relational database, and then using the database engine to run data transformations. See also extract, transform, and load.
�extract service: In OSI, a callable service that obtains optional information from OSI Communications Subsystem. See also action service, set services.
�extract, transform, and load (ETL): The process of collecting data from one or more sources, cleansing and transforming it, and then loading it into a database. See also warehouse enablement pack, extract, load, and transform.
�extranet: An intranet with extended access, generally behind a firewall. An extranet allows members of the public with valid user names and passwords to gain access to certain parts of an intranet.
�extrapartition destination: In CICS, a type of transient data queue. Extrapartition destinations can be accessed either within the CICS environment or outside of CICS; they can be defined as either input or output.
�extrapartition transient data: A CICS facility for temporarily saving data in the form of queues, called destinations. See also intrapartition transient data.
�Extra Performance Linkage (XPLINK): A type of call linkage that can improve performance in an environment of frequent calls between small functions.
�extreme case report: A report that shows the instances of a component that have either the highest or the lowest values (but not both) for a specified metric. Typically, an extreme case report shows the best or worst n cases (where n is a number), such as the 10 servers having the most critical events. See also health check report, summary report.
�extreme programming (XP): An agile software development method that relies on a strict plan and focuses on short release cycles, very frequent user participation, refactoring, pair programming, collective code ownership and testing throughout the entire development process, from start to finish. See also iterative development.
�extrusion: An attack that originates from a system within a network. For example, a trusted insider might use a company machine as the origin of a denial-of service attack.

Back to top�

�

�fabric: A complex network using hubs, switches, and gateways. Fibre channel uses a fabric to connect devices. See also hub.
�fabric login (FLOGI): The process by which a device gains access to the fabric. See also port login.
�fabric loop port (FL_port): A loop-capable fabric port that is used to connect node loop ports (NL_ports) to the switch in a loop configuration. See also fabric port, Fx_port.
�fabric name: The unique identifier assigned to a fabric and communicated during login and port discovery.
�fabric port (F_port): An access point that is part of a fibre-channel fabric. An F_port on a fibre-channel fabric connects to a node's node port (N_port). See also fabric loop port, Fx_port.
�Fabric Watch: A feature that runs on the Fabric Operating System (OS) and allows monitoring and configuration of fabric and switch elements.
�facade: A package within a subsystem that organizes and exports all information needed by the clients of the subsystem. Included in this package are interfaces (where the interfaces are unique to the subsystem), realization relationships to interfaces outside the subsystem, and any documentation needed by clients of the subsystem to use the subsystem.
�Faces component: One of a collection of user interface components (such as input fields) and data components (representing data such as records in a database) that can be dragged to a Faces JSP file and then bound to each other to build a dynamic Web project. See also JavaServer Faces.
�Faces JSP file: A file that represents a page in a dynamic Web project and contains JavaServer Faces UI and data components. See also JavaServer Faces.
�facsimile machine (fax machine): A functional unit that converts images to signals for transmission over a telephone system or that converts received signals back to images.
�factor: In RPG, an entry (for example, a field name, file name, literal, or data structure) that identifies the data to be used in an operation.
�factory: In object-oriented programming, a class that is used to create instances of another class. A factory is used to isolate the creation of objects of a particular class into one place so that new functions can be provided without widespread code changes.
�factory method: See class method.
�fact table: A relational table that contains facts, such as units sold or cost of goods, and foreign keys that link the fact table to each dimension table. See also star join.
�fade in: To gradually increase the volume of sounds, such as background music.
�fade out: To gradually decrease the volume of sounds, such as background music.
�failback: (1) In high availability disaster recovery, the process of restarting the original primary system and returning it to its status of primary system after a failover has occurred.; (2) The restoration of an appliance to its initial configuration after detection and repair of a failed network or component.; (3) Cluster recovery from failover following repair. See also failover.
�failed event: (1) See unresolved flow.; (2) An object that records the source, destination, description, and time of failure between two service connector components.
�failed flow: A flow that failed due to application or logic problems.
�failed member state: A state of a member of a data sharing group in which the member's task, address space, or z/OS system terminates before the state changes from active to quiesced.
�failover: An automatic operation that switches to a redundant or standby system in the event of a software, hardware, or network interruption. See also failback.
�failure: (1) The inability of a system or component to perform its required functions within specified performance requirements. A failure is characterized by the observable symptoms of one or more defects that have a root cause in one or more faults.; (2) An uncorrected hardware error. Failures are either recoverable or unrecoverable by the software or the operator. See also error.
�failure group: A collection of disks that share common access paths or adapter connection, and could all become unavailable through a single hardware failure. See also disk descriptor.
�failure terminal: A terminal in a node to which a message is routed for handling if message processing in the node fails.
�fallback: (1) The process of returning to a previous release of DB2 for z/OS after attempting or completing migration to a current release. Fallback is supported only from a subsystem that is in compatibility mode.; (2) The process of automatically switching back to the original database server after failure caused a switch to an alternative database server.
�false global lock contention: A contention indication from the coupling facility that occurs when multiple lock names are hashed to the same indicator and when no real contention exists.
�false negative: A condition when using optimistic locking whereby a row that was not updated since it was selected cannot be updated without first being selected again. Optimistic locking support does not allow a false positive to happen, but a false negative might happen. See also false positive.
�false positive: A condition when using optimistic locking whereby a row that was updated since it was selected is updated without first being selected again. Optimistic locking support does not allow a false positive to happen, but a false negative might happen. See also false negative.
�fanout: (1) In communications, the process of creating copies of a distribution to be delivered locally or to be sent through the network.; (2) A single output that becomes input to multiple branches.; (3) The number of systems or processors that are to receive software updates or communications simultaneously.
�fan set: A direct physical access path to data, which is provided by an index, hash, or link; a fan set is the means by which DB2 supports the ordering of data.
�FAP: See Formats and Protocols.
�far-end code violation: In Performance Tools, an unintended line code violation detected by the network termination 1 (NT1), and counted by the terminal equipment (TE), for frames transmitted to the NT1 on the interface for the T reference point in the integrated services digital network (ISDN). The NT1 reports a violation to the TE through the maintenance channel S1.
�fast communication manager (FCM): A group of functions that provides internodal communication support.
�Fast Database Recovery region (FDBR region): A separate IMS control region that monitors IMS, detects failure, and recovers any database resources that are locked by the failed IMS, making them available for other IMSs.
�Fast Etherchannel (FEC): A proprietary technology developed by Cisco that creates a team of two to four 10/100 Ethernet adapters or ports to increase transmission and reception throughput. Adapter fault tolerance is also supported by this technology.
�Fast Ethernet: An Ethernet standard that provides a data rate of 100 Mbps.
�fast packet switching: Communications protocols, such as frame relay and cell relay, that specify the processing of lower-layer data only for the transmission of data packets across a network.
�fast path: A method of doing something more directly and quickly than the usual way. For example, pressing a function key is faster than typing a command.
�Fast Path: IMS functions for applications that require good response characteristics and that may have large transaction volumes. Programs have rapid access to main-storage databases (to the field level), and to direct-access data entry databases. Message processing is grouped for load balancing and synchronized for database integrity and recovery. See also data entry database, load balancing group, main storage database.
�Fast Path database: One of two types of databases designed to provide high data availability and fast processing for IMS applications.
�Fast Path dependent region: See IMS Fast Path region.
�Fast Path exclusive transaction: A transaction type whose messages are routed to EMH for processing. See also Fast Path potential transaction.
�Fast Path potential transaction: A transaction type that can be routed to either EMH or TM processing. See also Fast Path exclusive transaction.
�fast replication: The functions that create an instant data copy. The Enterprise Storage Server (TESS) FlashCopy function is an example of fast replication.
�fast replication image copy: A type of image copy that is taken by the Database Image Copy 2 utility by using the DFSMS fast replication option and either the FlashCopy function of the Enterprise Storage Server (ESS) hardware or the SnapShot copy function of the RAMAC Virtual Array (RVA).
�fast response cache accelerator (FRCA): A cache that resides in the kernel on AIX and Windows platforms that provides support for caching on multiple Web servers and on servers with multiple IP addresses.
�fast select: In OSI, an X.25 optional user facility that can be encoded into a call request packet sent to an adjacent node. The fast select facility is included to provide conformance to ISO 8878.
�fast service upgrade (FSU): A service function of VSE/ESA for the installation of a refresh release without regenerating control information such as library control tables.
�fast view: In Eclipse, a view that is opened and closed by clicking a button on the shortcut bar.
�fast write: A write operation at cache speed that does not require immediate transfer of data to a disk drive. The subsystem writes the data directly to cache, to nonvolatile storage, or to both. The data is then available for destaging. A fast-write operation reduces the time an application must wait for the I/O operation to complete.
�FAT: See file allocation table.
�fault: (1) In OSI, an event that triggers an unwanted transition in the condition of a resource.; (2) A condition that causes a component in an implementation model to fail. A fault is the root cause of one or more defects identified by observing one or more failures.
�fault-based testing: A technique for testing computer software by using a test method and test data to demonstrate the presence or absence of a set of specific faults. For example, to demonstrate that the software correctly handles a divide-by-zero fault, the test data would include zero.
�fault message: An object that contains status information and details about a problem with a message.
�fault model: A model for testing computer software whose goal is to confirm the presence or absence of a specific fault.
�fault monitor: A daemon process that monitors DB2 instances and can restart stopped instances.
�fax: (1) The printed copy received from a facsimile machine.; (2) To transmit an image, using a telephone system and facsimile machines.
�fax machine: See facsimile machine.
�FBA: See fixed-block architecture.
�FBA disk device: See fixed-block architecture disk device.
�FBO: See file backout table.
�fc: See feedback code.
�FC: See fibre channel.
�FC-4: The Fibre Channel Protocol (FCP) level that encompasses the mapping of upper layer protocols (ULPs) such as Internet Protocol (IP) and Small Computer System Interface (SCSI) to lower protocol layers (FC-0 through FC-3). For example, the mapping of SCSI commands is an FC-4 ULP that defines the control interface between computers and storage.
�FC-AL: See Fibre Channel Arbitrated Loop.
�FCB: (1) See forms control buffer.; (2) See file control block.
�FC Bridge: See Fibre Channel Bridge.
�FCC: See Federal Communications Commission.
�FCFC: See first-character forms control.
�FCM: See fast communication manager.
�FCMU: See file compare and merge utility.
�F-Coupler: See frequency coupler.
�FCP: See Fibre Channel Protocol.
�FCS: (1) See frame check sequence.; (2) See function control sequence.
�FCT: (1) See forms control table.; (2) See file control table.; (3) See function control table.
�FDBR region: See Fast Database Recovery region.
�FDDI: See Fiber Distributed Data Interface.
�FDM: See Feature Download Management.
�FDML: See Flow Definition Markup Language.
�FD:OCA: See Formatted Data Object Content Architecture.
�FDT: See field definition table.
�feature: (1) Part of a product that is either included with the product or can be ordered separately.; (2) The visual content information that is stored in the image search server. Also, the visual traits that image search applications use to determine matches. The four QBIC features are average color, histogram color, positional color, and texture.; (3) A subset of capabilities of a solution. In Solution Install, a feature selects a set of installable units from within the root installable unit.; (4) A labeled subset of concrete, functional software characteristics (function, interface, property, event, and so forth) or nonfunctional software characteristics (scalability, portability, performance, and so forth) of a specific common component, assembly, or offering. See also common component, assembly, offering, capability.; (5) In Eclipse, a JAR file that is packaged in a form that the update manager accepts and uses to update the platform. Features have a manifest that provides basic information about the content of the feature, which can include plug-ins, fragments and other files.
�feature attribute: An attribute that specifies how the information about products is to be displayed to customers. For example, features with numerical descriptions can be displayed to a customer in either ascending or descending order.
�feature code: A code used by IBM to process hardware and software orders.
�Feature Download Management (FDM): An ADSI protocol that enables a number of alternative key and screen overlays to be stored in an ADSI telephone and to be selected by predetermined events at the telephone.
�feature path: A path that is used to access the value of a feature in a Unstructured Information Management Architecture (UIMA) feature structure.
�feature structure: The underlying data structure that represents the result of text analysis. A feature structure is an attribute-value structure. Each feature structure is of a type, and every type has a specified set of valid features or attributes, much like a Java class.
�feature-unique Licensed Internal Code (FULIC): The Licensed Internal Code shipped with the processor feature that provides support for that feature. FULIC is a complex instruction set computer (CISC)-only function.
�FEC: See Fast Etherchannel.
�FECB: See fetch control block.
�Federal Communications Commission (FCC): The standard body in the United States that is responsible for communications.
�Federal Information Processing Standard (FIPS): A standard produced by the National Institute of Standards and Technology when national and international standards are nonexistent or inadequate to satisfy the U.S. government requirements.
�federated attribute: An Information Integrator for Content metadata category that is mapped to native attributes in one or more content servers.
�federated CIU: See federated container installable unit.
�federated collection: A grouping of objects that results from a federated search. See also federated search.
�federated container installable unit (federated CIU): A shared container installable unit (CIU) of an aggregating installable unit. A federated CIU is intended to be deployed to a single hosting environment. Each instance of a federated CIU is compared with installed installable units (IUs). Only when the comparison evaluates to false will the federated CIU be created and registered with a federates relationship, otherwise, the discovered federated installable unit is used.
�federated database: In a federated system, the database that is within the federated server. Users and applications interface with the federated database. To these clients, the data sources and the federated database all appear as a single database.
�federated data store: Virtual representation of any number of specific content servers, such as Content Manager.
�federated entity: An Information Integrator for Content metadata object that is comprised of federated attributes and optionally associated with one or more federated text indexes.
�federated installable unit: A shared installable unit (IU) of an aggregating IU. A federated installable unit is intended to be deployed to one or more hosting environments. Each instance of a federated installable unit is compared with installed IUs. Only when the comparison evaluates to false will the federated installable unit be created and registered with a federates relationship; otherwise, the discovered installable unit is used.
�federated replication: Replication between DB2 and non-DB2 relational databases. See also federated system.
�federated search: (1) A query issued from Information Integrator for Content that simultaneously searches for data in one or more content servers, which can be heterogeneous. See also federated collection.; (2) A search capability that enables searches across multiple search services and returns a consolidated list of search results.
�federated server: The DB2 server in a federated system. Any number of DB2 instances can be configured to function as federated servers. Existing DB2 instances can be used as a federated server, or new instances can be created specifically for the federated system.
�federated system: A distributed database management system (DBMS) that consists of a DB2 instance that operates as a server, a database that serves as the federated database, one or more data sources, and clients (users and applications) who access the database and data sources. A federated system allows users to query and manipulate data located on other data servers. See also federated replication.
�federated text index: An Information Integrator for Content metadata object that is mapped to one or more native text indexes in one or more content servers.
�federates relationship: A concept of shared containment, such as a parent-child relationship among components in which all componenets can be shared with other components. In a federates relationship, managed resources are shared to create a distributed application from Java EE applications, queues and databases. See also has components relationship.
�federation: The process of combining naming systems so that the aggregate system can process composite names that span the naming systems.
�feed: A data format that contains periodically updated content that is available to multiple users, applications, or both. See also Rich Site Summary.
�feedback code (fc): A condition token value. If you specify fc in a call, a condition token indicating whether the service was completed successfully is returned to the calling routine
�fenced: Pertaining to a type, or characteristic, of a procedure, user-defined function, or federated wrapper that is defined to run in a separate process from the database manager. A federated wrapper is defined by using the DB2_FENCED wrapper option. When a fenced object runs in fenced mode, the database manager is protected from modifications by the object. See also not fenced, trusted.
�FEPI: See front-end programming interface.
�FEPI pool: In the CICS/ESA Front End Programming Interface (FEPI), a collection of nodes and targets.
�fetch: (1) To retrieve data from a database.; (2) An SQL action that positions a cursor on the next row of its result table and assigns the values of that row to host variables.; (3) The dynamic load of a PL/I procedure.
�fetch control block (FECB): An executable dynamic stub that is created by a fetch call. The stub transfers control to the true entry point of the module specified in the fetch call. The stub also switches the writable static environment, thereby giving each instance of the fetched routine its own global data.
�fetch orientation: The specification of the desired placement of the cursor as part of a FETCH statement (for example, BEFORE, AFTER, NEXT, PRIOR, CURRENT, FIRST, LAST, ABSOLUTE, and RELATIVE). See also scrollability.
�fetch overflow: In RPG, a routine that allows the user to change the basic RPG overflow logic to prevent printing over the perforation and to allow the user to use as much of the page as possible.
�FFDC: See first-failure data capture.
�FFST: See First Failure Support Technology.
�FFST file: See First Failure Support Technology file.
�FFT: See final-form text.
�FGID: See font typeface global identifier.
�FIB: See file information block.
�Fiber Distributed Data Interface (FDDI): An American National Standards Institute (ANSI) standard for a 100-Mbps LAN using fiber optic cables.
�fiber optic: Describing a transmission medium composed of a glass fiber light path surrounded by a cladding material that confines the signal to the light path.
�fiber optic cable: A fiber or bundle of fibers in a structure built to meet optic, mechanical, and environmental specifications.
�fiber optic network: A network based on the technology and standards that define data transmission using cables of glass or plastic fibers carrying light. The advantages of a fiber optic network are higher transmission speeds, greater carrying capacity, lower error rates, and lighter, more compact cables that are less susceptible to electromagnetic interference.
�fiber optics: The technology of guiding optical power (or light) through thin, transparent strands (or fibers) that are made of glass, fused silica, or plastic.
�fibre channel (FC): A technology for transmitting data between computer devices. It is especially suited for attaching computer servers to shared storage devices and for interconnecting storage controllers and drives. See also fixed-block device.
�Fibre Channel Arbitrated Loop (FC-AL): An implementation of the Fibre Channel standards that uses a ring topology for the communication fabric; refer to American National Standards Institute (ANSI) INCITS 272-1996, (R2001). In this topology, two or more fibre-channel end points are interconnected through a looped interface.
�Fibre Channel Bridge (FC Bridge): In Fibre Channel technology, a device that translates from one bus protocol to another bus protocol. The Fibre Channel Bridge translates between the Fibre Channel Protocol and the SCSI-2 bus protocol.
�fibre channel connection (FICON): A fibre-channel communication protocol designed for IBM mainframe computers and peripherals.
�fibre channel extender: A device used to extend a fibre-channel link over a greater distance than is supported by the standard, usually a number of miles or kilometers. Devices must be deployed in pairs at each end of a link.
�Fibre Channel Protocol (FCP): The serial SCSI command protocol used on fibre-channel networks.
�fibre channel service (FS): A service that is defined by fibre-channel standards and exists at a well-known address. For example, the simple name server is an FS. See also Fibre Channel Service Protocol, simple name server.
�Fibre Channel Service Protocol (FSP): The common protocol for all fabric services, transparent to the fabric type or topology. See also fibre channel service, fibre channel transport.
�fibre channel shortest path first (FSPF): A routing protocol used by fibre-channel switches.
�fibre channel transport: A protocol service that supports communication between fibre-channel service providers. See also Fibre Channel Service Protocol.
�fiche: See microfiche.
�FICON: See fibre channel connection.
�FiconNet: In ESS Specialist, the label on a pseudo-host icon that represents a host connection that uses the FICON protocol and that is not completely defined on the ESS. See also access-any mode, anonymous host.
�fidelity: In AFP support, the degree of exactness required when processing the input data stream for printing a file. Different levels of fidelity can be specified, which determine how errors are handled (such as substituting fonts when a font named in the data stream cannot be found).
�FID field: See format identification field.
�field: (1) An area into which a particular category of data or control information is entered.; (2) In object-oriented programming, an attribute or data member of a class.; (3) In a database, a portion (as defined during the database description generation process DBDGEN) within a segment that is the smallest unit of the data that can be referred to.
�field data format: In BMS, a format that allows you to use application program commands to address predefined fields in a display by name, without knowing their positions. The same fields must appear in all versions of a display, but can be arranged differently in different versions.
�field definition: In IDDU, information that describes the characteristics of data in a field, such as its name, length, and data type. A field definition resides in a data dictionary.
�field definition macro (DFHMDF): In BMS, a macro that defines a field within a map defined by the previous DFHMDI macro. The DFHMDF macro specifies initial attributes to be given to fields within a map. See also map definition.
�field definition table (FDT): The field definition table describes the characteristics of a field; for example, its length and number of its data areas, and whether it is mandatory. If the characteristics of a field change depending on its use in a particular message, the definition of the field in the FDT can be overridden by the MCB specifications.
�field description: Information that describes the characteristics of data in a field.
�fielded search: A query that is restricted to a particular field.
�field format: A format in which the output consists of structured field introducers and variable data rather than output in line format.
�field group: One or several fields that are defined as being a group. Because a field can occur more than once in a message, field groups are used to distinguish them. A name can be assigned to the field group during message definition.
�field group number: In the TOF, a number is assigned to each field group in a message in ascending order from 1 to 255. A particular field group can be accessed using its field group number.
�field indicator: In RPG, an indicator that shows whether a given field in an input record is plus, minus, zero, or blank.
�field-level access checking: The RACF facility by which a security administrator can control access to fields or segments in a RACF profile.
�field-level sensitivity: The ability of an application program to access data at the field level.
�field-level specification: In DDS, a specification coded on the same line as a field name or on lines immediately following a field name.
�field line: In RLU, a temporary record in a report prototype that indicates the field boundaries in an associated report line.
�field outline: The output record to be printed outlines, with boxes, the fields of data within the record.
�field procedure: A user-written exit routine that receives a single value and encodes or decodes it as specified by the user.
�field record relation indicator: In RPG, an indicator that associates fields in an input record with a particular record type. The field record relation indicator is normally used when the record type is one of several in an OR relationship.
�field reference file: A physical file that contains no data, only descriptions of fields.
�field registration file (FRF): A file that is used to define fields for use in the object database.
�field-replaceable unit (FRU): An assembly that is replaced in its entirety when any one of its components fails. See also customer-replaceable unit.
�field search argument (FSA): For Fast Path, theI/O area that is constructed by an application program to identify a field within a segment that is to be processed with a FLD call.
�field selection: (1) A function that uses the state of the option indicators to display or print data when a record format is written.; (2) In Business Graphics Utility, the selection of fields from a database file for use as data values and data labels.; (3) In the GDDM function, the selection of fields from a database file for use as data values.
�field tab (FTAB): In MFS, a character defined for operator use in separating input fields if the length of the entered data is less than the defined field length, or there is no data for a field.
�field tag: A character string used by MERVA to identify a field in a network buffer. For example, for SWIFT field 30, the field tag is :30:.
�FIFO: See first-in first-out.
�FIFO special file: A type of file with the property that data written to such a file is read on a first-in-first-out (FIFO) basis.
�figurative constant: (1) In COBOL, a reserved word that represents a numeric or character value or a string of repeated values. The word can be used instead of a literal to represent the value.; (2) In RPG, an implied literal that is specified in the calculation specifications without a length definition because the implied length and decimal positions are the same as those of the receiver field.
�file: (1) A generic term for the object type that refers to a database file, a device file, or a save file. The system-recognized identifier for the object type is *FILE.; (2) A collection of related data that is stored and retrieved by an assigned name. See also data set.
�file access permission: A designation that determines who can access a particular file and how the user can access the file.
�FileAct delivery notification: A delivery notification that conforms to the FileAct Protocol.
�FileAct directory: A directory used exclusively to store files involved in FileAct transfers.
�file allocation table (FAT): A table that is used to allocate space on a disk for a file and to locate the file.
�file attribute conflict condition: In COBOL, an unsuccessful attempt to run an input-output operation on a file whose file attributes, as specified for that file in the program, do not match the fixed attributes for that file.
�file backout table (FBO): In the restart data set, a summary table that contains an entry for each file for which at least one logged or journaled record was written to the restart data set. It also contains flags for any VSAM files that have suffered backout failures that are still outstanding. Data in this table is available to user-written exit programs.
�file-based content: Content that is written and stored in a specific file format. For example, content can be written and stored in the formats of .html, .txt, .jpeg, .img, .jsp, or .css.
�file chaining: In Query, a function that allows a query application to use data from two database files. The query application views the two chained files as if they were one file and refers to the first file as the primary record format and the second file as the secondary record format.
�file class: The distributed data management (DDM) file class used when writing applications for Virtual Storage Access Method (VSAM) for OS/2 and AIX.
�file clause: In COBOL, a clause that appears as part of any of the following Data Division entries: file description entry (FD entry) and sort-merge file description entry (SD entry).
�file compare and merge utility (FCMU): A function of the Application Development ToolSet feature that is used to compare physical file members and merge updates to file members.
�file connector: In COBOL, a storage area that contains information about a file and is used as the connection between a file name and a physical file, and between a file name and its associated record area.
�file control: (1) The CICS facility for managing basic operations against a file (ADD, READ, DELETE, REWRITE, and BROWSE).; (2) COBOL, the name and header of an Environment Division paragraph in which the data files for a source program are named and assigned to specific input/output devices.
�file control block (FCB): A block containing the addresses of I/O routines, information about how the routines were opened and closed, and a pointer to the file information block.
�file control entry: In COBOL, a SELECT clause and all its subordinate clauses that declare the relevant physical attributes of a file.
�file control program: The CICS program that controls all CICS file operations. Because the CICS file control program processes only VSAM and BDAM data sets, any sequential data sets must be defined as extrapartition destinations by using the CEDA DEFINE TDQUEUE command.
�file control table (FCT): A CICS table containing the characteristics of the files accessed by file control.
�file data: The contents of a file.
�FILEDEF: See file definition statement.
�file default ACL: A model access control list (ACL) that is inherited by files that are created within the parent directory.
�file definition: (1) In RPG, file description and input specifications that describe the records and fields in a file.; (2) In IDDU, information that describes the contents and characteristics of a file. A file definition resides in a data dictionary.
�file definition statement (FILEDEF): In CMS, a statement that serves as the connection between the logical name of a file and the physical name of a file.
�file description: The description of a file and its contents.
�file description entry: In COBOL, an entry in the FILE SECTION of the Data Division that contains information about the identification, the physical organization, and the record name of a file.
�file description file: In System i Access, a personal computer file that describes a personal computer data file. The description includes the name, data type, field length, and format of the data file. This information is used by the System i Access transfer function to transfer data to the System i product.
�file description specification: In RPG, a specification on which the programmer identifies and describes all files used in a program.
�file descriptor: A positive integer or a data structure that uniquely identifies an open file for the purpose of file access.
�file-distribution server: In the Software Distribution task, an intermediate server that is used to distribute a software package when the redirected-distribution method is used.
�file handle: A number that is used by the client and server sides of the Network File System (NFS) to specify a particular file or prefix.
�file identifier: A 3-character identifier used for files being joined in Query for a query. The identifiers are used during a query definition to uniquely identify each file.
�file information block (FIB): A read-only block describing the characteristics of an I/O file.
�file information data structure (INFDS): In RPG, a data structure that can be defined for each file to make file exception/error information available to the program. A file information data structure must be unique for each file.
�file key: In RPG, all the key fields defined for a file.
�file level specification: In DDS, a specification coded on the lines before the first record format name.
�file list: A list of files contained in a library.
�file lock: A means to limit or deny access to a file by other users. A file lock can be a read lock or a write lock.
�file maintenance: The process of adding, changing, or deleting records in a file to keep them current.
�file-management policy: A set of rules defined in a policy file used to manage file migration and file deletion. See also policy.
�file metadata: Information about the file, such as owner, permission, and physical location.
�file mode: An object containing the file permission bits and other characteristics of a file.
�file mode creation mask: (1) A pattern of characters that is used to control the keeping, deleting, or testing of portions of another pattern of characters.; (2) A pattern of characters that is used to establish maximum permissions that can then be applied to individual access control list (ACL) entries.
�file model: A description of how information is organized and managed within a file.
�file name: A name assigned to identify a file.
�file name extension: (1) An optional 3-letter code that may be used as the second part of a PC file name, and is separated from the file name by a period (.). Extensions have meanings to programs, and may be used to identify the type of the file.; (2) An addition to a file name that identifies the file type (for example, text file or program file).
�file name substitution: In the AIX operating system, the process in which the shell substitutes an alphabetically sorted list of file names in the place of a pattern. The shell recognizes a pattern (as opposed to a file name) by the occurrence of a word (character string) with either of the following characteristics: (a) the word contains any of these characters: *, ?, [, or {, (b) the word begins with this character: .
�file offset: The byte position in the file where the next I/O operation begins.
�file operation code: In RPG, an operation code (for example, CHAIN) that lets the user control the input/output operations to a file.
�file organization: In COBOL, the permanent file arrangement established at the time that a file is created.
�file override: An attribute specified at run time that changes the attributes specified in the file description or in the program.
�file owner: The user who has the highest level of access authority to a file, as defined by the file.
�file-owning region (FOR): See data-owning region.
�file package: See software package.
�file package block: See software package block.
�file package definition: See software package definition.
�file permission bit: Information about a file that is used, along with other information, to determine whether a process has read, write, or execute permission to a file. The use of file permission bits is described in file access permissions.
�file-placement policy: A set of rules defined in a policy file used to manage the initial placement of a newly created file. See also policy.
�file-placement rule: A rule that controls in what pool SAN File System places files in the global file system. See also global file system, rule, policy.
�file pointer: (1) In the hierarchical file system, the representation of the position or offset in the file in which the next read or write operation occurs.; (2) An identifier that indicates a structure containing the file name.
�file position indicator: In COBOL, a conceptual entity that (a) contains the value of the current key within the key of reference for an indexed file, the record number of the current record for a sequential file, or the relative record number of the current record for a relative file; or (b) indicates that no next logical record exists, that the number of significant digits in the relative record number is larger than the size of the relative key data item, that an optional input file is not present, that the at end condition already exists, or that no valid next record has been established.
�file reference function: A function of the system that lets the user track file use on the system.
�file reference variable: A host variable that indicates that data resides in a file on the client rather than in a client memory buffer.
�file repository: An internal or external storage location where software and files are stored.
�file request thread element (FRTE): An element used by CICS file control to link related requests together as a file thread; to record the existence of READ SET storage to be released at syncpoint and the existence of any other outstanding work that must be completed at syncpoint; to register a task as a user of a file to prevent the file being closed while still in use.
�file scope: A property of a file name that is declared outside all blocks, classes, and function declarations and that can be used after the point of declaration in a source file.
�File Section: In COBOL, the section of the Data Division that contains file description entries and sort-merge file description entries together with their associated record descriptions.
�file separator: The pages produced at the beginning of each output file and used to separate the file from the other files being sent to an output device.
�file server I/O processor: An input/output processor (IOP) that serves files.
�file server node: An IBM System Blue Gene node used to serve files to other Blue Gene systems and to I/O nodes.
�File Services: See OSI File Services.
�file serving: A function that supports the serving of static files by Web applications.
�file set: (1) An individually installable option or update. Options provide specific function and updates correct an error in, or enhance, a previously installed option.; (2) A hierarchical grouping of files managed as a unit for balancing workload across a cluster.
�file share: A unique name assigned to an integrated file system directory on a System i product that lets remote users and applications access the directory.
�files library: The library to search for database files for a System/36 environment job.
�file space: A logical storage space on a client that can contain a group of files. For clients on Windows systems, a file space is a logical partition that is identified by a volume label. For clients on AIX or UNIX systems, a file space consists of any subset of directories and subdirectories that stem from a virtual mount point.
�file space ID (FSID): A unique numeric identifier that the server assigns to a file space when it is stored in server storage.
�file splitting: The division of an event file, based on a delimiter or based on size, to separate individual business objects within the file and send them as if they are each an event file to reduce memory requirements.
�file system: (1) A collection of files and certain attributes associated with those files.; (2) In the hierarchical file system, the underlying system support that manages I/O operations to files and controls the format of information on the storage media. A file system allows applications to create and manage files on storage devices and to perform I/O operations to those files.; (3) The collection of files and file management structures on a physical or logical mass storage device, such as a diskette or minidisk.
�file system descriptor: A data structure containing key information about a file system. This information includes the disks assigned to the file system (stripe group), the current state of the file system, and pointers to key files such as quota files and log files.
�file system descriptor quorum: The number of disks needed in order to write the file system descriptor correctly.
�file system manager: (1) The component that manages the multimedia file system.; (2) The provider of services for all the nodes using a single file system. A file system manager processes changes to the state or description of the file system, controls the regions of disks that are allocated to each node, and controls token management and quota management.
�file system owner: The system that coordinates sysplex activity for a particular file system.
�file system scanner: An application that searches files on the file system and returns information on these files with varying levels of detail, specified in the scanner configuration.
�file tag: A file attribute that identifies the character set of the text data within a file and indicates whether the file is eligible for automatic conversion. See also automatic conversion, program CCSID.
�file transfer, access, and management (FTAM): The OSI standard for transferring files between nodes.
�File Transfer Adapter (FTA): A SWIFTAlliance Gateway (SAG) component that transfers files to or from the FileAct directory used by an SAG.
�File Transfer Protocol (FTP): In TCP/IP, an application layer protocol that uses TCP and Telnet services to transfer bulk-data files between machines or hosts.
�file transfer support (FTS): A function of the operating system that moves file members from one System i product to another or from a System i product to a System/36 by using asynchronous, APPC, or BSCEL communications support.
�file translation: In RPG, a function that can change any of the 256 EBCDIC characters into another EBCDIC character.
�fill character: In MFS, a character used to pad input message fields or output device fields when the length of the received data is less than the length defined for the field or no data is received for the field.
�filler line: In RLU, a record in a report prototype that represents spacing between record formats and is used in the data description specifications (DDS) for the report.
�fillet: A curve that is tangent to the end points of two connected lines.
�fill pattern: The shading used inside a bar and pie slice on a chart and below the lines of a chart.
�fill word: In fibre-channel technology, a transmission word that is an IDLE or an ARBx primitive signal. Fill words are transmitted between frames, primitive signals, and primitive sequences to keep a fibre-channel network active.
�filter: (1) In System Manager, a function that assigns alerts or problems into groups and specifies the actions to take for each group. A filter consists of selection entries and action entries.; (2) A device or program that separates data, signals, or material in accordance with specified criteria. See also servlet filtering.; (3) A command that reads standard input data, modifies the data, and sends it to standard output. A pipeline usually has several filters.; (4) An ESQL expression that is applied to the content of a message to determine how the message is processed.; (5) A mechanism that is used to query libraries, objects, and members on a System i server, and organize them for viewing in the Remote System Explorer. See also filter pool, filter string.; (6) In Infoprint Server, a program that can add, delete, or modify input data. Infoprint Server provides support for two types of filter programs: DLL filters and UNIX filters. See also DLL filter.
�filter expression: An optional expression, used by a notification receiver to filter the notification instances that it will accept. The receiver is listening for a particular type of notification, and in addition it will only accept notification instances that meet the criteria specified by the filter expression.
�filter factor: A number between zero and one that estimates the proportion of rows in a table for which a predicate is true.
�filtering: (1) The selective function of allowing some Internet Protocol (IP) packets to continue to their destination or, at the same time, blocking others.; (2) A technique for selecting the information displayed in a view that uses criteria specified by a user. See also sorting.; (3) The process of selecting data sets based on specified criteria. These criteria consist of fully-qualified or partially-qualified data set names, certain data set characteristics, or both.
�filter interface: A statement that is used to associate a set of filter rules with a particular physical interface.
�filter pool: A group of filters. See also filter, filter pool reference.
�filter pool reference: A mechanism that displays a filter pool from one connection in any other connection, so that when a user makes a change to the original filter pool, the change is reflected in the filter pool reference. See also filter pool.
�filter rule: A rule that selects particular Internet Protocol (IP) traffic and requests an action for that traffic. Possible actions are to discard the packet, to allow the packet without security, and to take the appropriate IP security action.
�filter string: The information used by a filter to perform a search. See also filter.
�FIN: SWIFT's store-and-forward message-processing service defining message standards and protocols. See also SWIFTNet FIN.
�final-form text (FFT): A data stream defined by document content architecture that is used to exchange resolved documents (which can be printed directly by most printers or displayed) between systems. See also revisable-form text.
�Final-Form Text Document Content Architecture: The architecture that specifies the structure of the data stream used for the interchange of text documents formatted for presentation. A Final-Form Text:Document Content Architecture document consists of text and formatting information that controls the presentation of the text.
�final state: A state that signifies that the enclosing composite state or the entire state machine is completed.
�final warning: In OSI Communications Subsystem, a subsystem threshold that indicates that not enough system storage is available to maintain existing connections. When the final warning threshold is reached, the subsystem ends existing connections and does not allow new connections to be made. See also first warning.
�final write: A write of the same information as the intermediate write that is performed at the end of the checkpoint cycle. See also intermediate write, primary write.
�finance communications: The data communications support that allows i5/OS programs to communicate with programs on finance controllers, using the SNA LU session type 0 protocol.
�finance device: A device, such as the 4700 Finance Communications System devices and the 3694 Document Processor, that performs functions specifically related to the finance industry. The 3180, 3270, and 5250 work stations are not finance devices.
�finance I/O manager (FIOM): A set of routines that can be used by an application program to do I/O operations on a finance device that is configured as a non-intersystem communications function (non-ICF) device.
�finance support: A part of the system support that uses a System i product as a host system to which finance devices can be attached.
�FIN-Copy: The MERVA component used for SWIFT FIN-Copy support.
�find: See discover.
�FINDDEST: See Find Destination.
�Find Destination (FINDDEST): An internal service in IMS used for finding certain IMS resources (CCB, CVB, SMB, CNT, RCNT, LNB, and QAB), most of which represent IMS destinations. For searches other than CVBs and CCBs, if the block is not found, then if requested, a search for an LU 6.2 descriptor is made. If LU 6.2 is not requested, or the search fails, then if ETO is active and the caller of FINDDEST request creation, a call is made to create a new user structure for the given destination name.
�finder method: In enterprise beans, a method defined in the home interface and invoked by a client to locate an entity bean. (Sun)
�fine-grained: Pertaining to viewing an individual object in detail. See also coarse-grained.
�fine-grained authorization role: An authorization role that indicates the authority to perform narrowly defined administrative tasks.
�finger: In Internet communications, a program that displays information about the current users of a local or remote system. The finger usually displays the user's full name, last login time, idle time, terminal line, and terminal location (where applicable).
�fingerprint: See digest code.
�finishing margin: In printing, the distance from the edge of a paper to the line where staples are placed for edge stitching.
�finish-to-finish: A dependency type between two project elements in which the predecessor element must finish before the successor element can finish.
�finish-to-start: A dependency type between to project elements in which the predecessor element must finish before the successor element can start.
�finite resource: A fixed resource with definable limitations, such as an instructor, projector, or classroom. See also resource, depletable resource.
�finite state dictionary: A dictionary that uses a finite state automaton or finite state transducer to recognize words and associate information to them. Finite state dictionaries perform more quickly and require less memory consumption than other types of dictionaries, when compared to word lists, tree maps, or hash tables.
�finite state grammar (FSG): In WebSphere Voice Server, the extension of a file that contains grammar specifications in compiled, binary form. It is generated from a .bnf file and is called a .fsg file.
�finite state machine: The theoretical base describing the rules of a service request's state and the conditions to state transitions.
�FIOM: See finance I/O manager.
�FIPS: See Federal Information Processing Standard.
�fire: In object-oriented programming, to cause a state transition.
�fire status: A Boolean flag indicating whether or not an event has occurred (fired). The fire status of an event can be either FIRED (true) or NOTFIRED (false).
�firewall: A network configuration, usually both hardware and software, that prevents unauthorized traffic into and out of a secure network.
�firmware: (1) Proprietary code that is usually delivered as microcode as part of an operating system. Firmware is more efficient than software loaded from an alterable medium and more adaptable to change than pure hardware circuitry. An example of firmware is the Basic Input/Output System (BIOS) in read-only memory (ROM) on a PC system board.; (2) An ordered set of microcode instructions and data stored in a hardware EPROM. When microcode software is installed in a hardware EPROM, it becomes firmware. Firmware cannot be modified by the user but can be updated by service personnel. See also microcode.
�first-character forms control (FCFC): A method that specifies the format of printed output. The first character of each record determines the format.
�first-failure data capture (FFDC): (1) The i5/OS implementation of the FFST architecture providing problem recognition, selective dump of diagnostic data, symptom string generation, and problem log entry.; (2) A problem diagnosis aid that identifies errors, gathers and logs information about these errors, and returns control to the affected runtime software.
�First Failure Support Technology (FFST): An IBM architecture that defines a single approach to error detection through defensive programming techniques. These techniques provide proactive (passive until required) problem recognition and a description of diagnostic output required to debug a software problem.
�First Failure Support Technology file (FFST file): A file containing information for use in detecting and diagnosing software problems. In WebSphere MQ, FFST files have a file type of FDC.
�first-in first-out (FIFO): A queuing technique in which the next item to be retrieved is the item that has been in the queue for the longest time. See also last-in first-out.
�first-level destination: The part of a destination identifier that indicates a target node to which input is to be sent. See also second-level destination.
�first-level folder: A folder name that is not preceded by another folder name. A first-level folder is the first folder name in a folder path. For example, if folder A is a first-level folder, folder path A/B indicates that folder B is within folder A, and that folder A is within the root folder.
�first occurrence data capture (FODC): The process of capturing scenario-based data about a DB2 instance. FODC can be invoked manually by a DB2 user based on a particular symptom or automatically when a predetermined scenario or symptom is detected.
�first-page indicator: In RPG, an indicator, coded as 1P, that specifies which lines (such as headings) should be printed on the first page only.
�first speaker: In SNA, the logical unit (LU) half-session defined when the session is started as the half-session able to begin a bracket without requesting permission from the other LU half-session to do so, and the half-session winning permission if both half-sessions attempt to begin a bracket simultaneously. See also bidder.
�first-speaker session: See contention-winner session.
�first warning: In OSI Communications Subsystem, a subsystem threshold that indicates that not enough system storage is available to establish new connections. When the first warning threshold is reached, the subsystem maintains existing connections but does not allow new connections to be made. See also final warning.
�fix: A software maintenance package such as an interim fix, test fix, or program temporary fix, that solves a customer problem. See also fix pack, test fix, interim fix, refresh pack, manufacturing refresh.
�fixed array: In Distributed Computing Environment (DCE) Remote Procedure Call (RPC), an array whose size is defined in the Interface Definition Language (IDL). All of the data in the array is transmitted during the call.
�fixed-block architecture (FBA): An architecture for a logical device that specifies the format of and access mechanisms for the logical data units on the device. The logical data unit is a block. All blocks on the device are the same size (fixed size). The subsystem can access them independently. See also data record.
�fixed-block architecture disk device (FBA disk device): A disk device that stores data in blocks of fixed size. These blocks are addressed by block number relative to the beginning of the file. See also extended count key data device.
�fixed-block device: An architecture for a logical device that specifies the format of the logical data units on the device. The logical data unit is a block. All blocks on the device are the same size (fixed size); the subsystem can access them independently. This format is required for the logical data units for host systems that attach with a Small Computer System Interface (SCSI) or fibre-channel interface using Fibre Channel Protocol (FCP). See also Small Computer System Interface, fibre channel.
�fixed currency symbol: A currency symbol that appears in the far left position of an edited field. See also floating currency symbol.
�fixed data: In AFP Utilities, an element in the record layout and page layout that has a constant value. See also variable data.
�fixed disk: See hard disk.
�fixed file attribute: In COBOL, information about a file that is established when a file is created and that cannot subsequently be changed during the existence of the file. Attributes include the organization of the file (sequential, relative, or indexed), the prime record key, the alternate record keys, the minimum and maximum record size, the record type (fixed or variable), the collating sequence of the keys for indexed files, the minimum and maximum physical record size, the padding character, and the record delimiter.

�fixed-form: Pertaining to the entering of data according to certain rules of format. See also free-form.
�fixed length: A specified length for a record or field that cannot be changed. See also variable length.
�fixed-length: Pertaining to a characteristic of a field on a display that is of a defined length.
�fixed-length record: A record whose length is established as an attribute of the file in which it is stored, and cannot be changed. Every record in such a file has the same length, which is specified by the record length attribute (LRECL) of the file. See also variable-length record, variable-length record.
�fixed-length string: A character, graphic, or binary string whose length is specified and cannot be changed. See also varying-length string.
�fixed metrics: Measurement information in specific units such as pels, inches, or centimeters for individual or collections of graphic characters. See also font metric, relative metrics.
�fixed pacing: See fixed session-level pacing.
�fixed-point constant: A numeric constant shown as an optional sign followed by one or more digits and a decimal point.
�fixed-point format: (1) The external representation of a decimal value, that shows an optional sign followed by one or more digits, a decimal point, and zero or more digits.; (2) The internal storage format that represents a fixed-point value that can be stored either in zoned or packed decimal format.
�fixed-point notation: A REXX number that is written without exponentiation.
�fixed-point overflow exception: A program interruption caused by an overflow during signed binary arithmetic or signed left-shift operations. This program interruption can be disabled through a program mask bit setting. See also overflow.
�fixed session-level pacing (fixed pacing): A form of session-level pacing in which the data transfer rate is controlled using fixed pacing-window sizes, which are initialized at session-activation time. See also adaptive session-level pacing.
�fixed term licensing: Licensing of IBM products for a limited term so designated by IBM in the program's Proof of Entitlement.
�fixed utility volume: A simplex volume assigned by the storage administrator to a logical storage subsystem (LSS) to serve as working storage for extended remote copy (XRC) functions on that storage subsystem.
�fixed wireless data: Wireless service to a fixed location through antennas larger than those in mobile or portable setups. The fastest data throughputs--up to T-1 speed--are available over fixed wireless networks.
�fixes relationship: A concept that indicates that a component updates another component, providing a correction to the existing component. The components have the same version, release, modification, and level. See also has components relationship.
�fix installable unit: An installable unit (IU) that modifies a base IU. Multiple fix installable units can be applied to a base IU.
�fix pack: A cumulative collection of fixes that is made available between scheduled refresh packs, manufacturing refreshes, or releases. It is intended to allow customers to come up to a specific maintenance level. See also program temporary fix, test fix, interim fix, refresh pack, fix.
�FixPak: See fix pack.
�fix-up and resume: The correction of a condition either by changing the argument or parameter and running the routine again or by providing a specific value for the result.
�flag: (1) The bit sequence 01111110 used to mark a frame in SDLC.; (2) Information about an extended attribute that is stored with the extended attribute.; (3) A modifier that appears on a command line with the command name that defines the action of the command. A dash usually precedes a flag.
�flagger: A precompiler option that identifies SQL statements in applications that do not conform to selected validation criteria (for example, the ISO/ANSI SQL92 entry-level standard).
�FlashCopy: An optional feature of the Storage System DS family that can make an instant copy of data, that is, a point-in-time copy of a volume.
�FlashCopy image: A space-efficient image of the contents of part of the SAN file system at a particular moment.
�FlashCopy mapping: A continuous space on a direct access storage volume, occupied by or reserved for a particular data set, data space, or file.
�FlashCopy relationship: See FlashCopy mapping.
�FlashCopy service: A copy service that duplicates the contents of a source virtual disk (VDisk) on a target VDisk. In the process, the original contents of the target VDisk are lost. See also point-in-time copy.
�flash memory: A computer chip with a read-only memory that retains its data when the power is turned off and that can be electronically erased and reprogrammed without being removed from the circuit board.
�flat browse: A browse of the descendant activities of a specified process, on which each descendant activity can be returned exactly once.
�flat business object: A business object that contains only simple attributes and does not contain any child business objects. See also hierarchical business object.
�flat collection: A collection that has no hierarchical structure.
�flatten: (1) To display multiple iterations of data in a single window.; (2) See demarshal.
�flight recorder: An object that stores trace information used to record a history of what has happened in the system's programs. The flight recorder contains only information that helps to identify the flow of the system's programs and status information.
�float constant: (1) A number containing a decimal point, an exponent, or both a decimal point and an exponent. The exponent contains an "e" or "E," an optional sign (+ or -), and one or more digits (0 through 9).; (2) A constant representing a non-integral number.
�floating bar chart: In the GDDM function, a chart that shows bars detached from either line. See also composite bar chart, multiple bar chart.
�floating bar graph: In Performance Tools, a graph that shows bars detached from either line. See also composite bar graph.
�floating currency symbol: A currency symbol that appears immediately to the left of the far left position in an edited field. See also fixed currency symbol.
�floating overlay: See page overlay.
�floating point: A method of encoding binary floating-point numbers and decimal floating-point numbers within the limits of finite precision available on computers.
�floating-point constant: (1) A number shown as an optional sign followed by one or more digits and a decimal point, which may be at the end.; (2) A numeric constant shown as an optional sign, followed by the letter D or E, followed by a 1- to 3-digit integer constant. For example, 3E-02, which is 3 times 10 to the -2 power or 0.03.
�floating-point format: In binary floating-point representation, the storage format that represents a binary floating-point value.
�floating-point notation: A REXX number that is written using exponentiation.
�floating-point number: (1) A real number represented by a pair of distinct numerals. The real number is the product of the fractional part, one of the numerals, and a value obtained by raising the implicit floating-point base to a power indicated by the second numeral.; (2) Either a 32-bit or 64-bit approximate representation of a real number. In IBM SQL, floating-point numbers do not include decimal floating-point numbers. See also double-precision floating-point number, single-precision floating point number, decimal floating-point number.
�floating-point register (FPR): A register used to manipulate data in a floating-point representation system. [I][A]
�floating segment: An EDI segment of an EDI document definition that can exist in many positions relative to other EDI segments.
�floating utility volume: Any volume of a pool of simplex volumes assigned by the storage administrator to a logical storage subsystem (LSS) to serve as dynamic storage for extended remote copy (XRC) functions on that storage subsystem.
�FLOGI: See fabric login.
�flow: (1) The passing of a message from one process to another. For example, Distributed Relational Database Architecture (DRDA) flows are those that consist only of messages described by the DRDA protocol as part of the DRDA protocols.; (2) A single transmission of data passing over a link during a conversation.
�flow control: In OSI, procedures that control the amount of data than can be sent from one node to another. Flow control is used to prevent a node from sending data to another node faster than the receiver can handle it.
�flow debugger: A facility to debug message flows that is provided in the Flow Debug perspective in the workbench.
�Flow Definition Markup Language (FDML): An IBM format used to describe business processes in WebSphere Application Server. FDML is an XML language which is based on the flow related aspects of Web Services Flow Language (WSFL).
�flow object: An object of the business process model that helps connect components in the workflow.
�flow state: A transition in an activity diagram that represents the passing of an object from the output of actions in one state to the input of actions in another state.
�FL_port: See fabric loop port.
�FLU: See Font Library Update Utility.
�flush left: Text aligned at the left margin. See also flush right.
�flush right: Text aligned at the right margin. See also flush left.
�FLWOR expression: An XQuery expression that is comparable to an SQL SELECT statement, providing the capabilities to iterate over input sequences (FOR), bind variables (LET), define filters (WHERE), order filtered results (ORDER BY), and return results (RETURN).
�FM: See frequency modulation.
�FME: See function management end.
�FMH: See function management header.
�FMID: See function modification identifier.
�FOCA: See Font Object Content Architecture.
�focal point: An APPN network node that is the destination of alerts. A focal point allows a customer to centrally manage a network.
�focus: (1) In VisualAge RPG, the state of a component, as indicated by the cursor, that indicates where a user's interaction with the keyboard will appear.; (2) The first three components of the dynamic context (context item, context position, and context size) of an XQuery expression. The focus enables the processor to keep track of which items are being processed by the expression. See also context size.
�focus of control: A symbol on a sequence diagram that shows the period of time during which an object is performing an action, either directly or through a subordinate procedure.
�FODC: See first occurrence data capture.
�fold: (1) To continue data on the next line. See also truncate.; (2) To translate the lowercase characters of a character string into uppercase.
�folder: A container used to organize objects.
�folderless document: A document in the document library that is not in any folder.
�folder manager: The Content Manager model for managing data as online documents and folders. You can use the folder manager APIs as the primary interface between your applications and the Content Manager content servers.
�folder pane: The Notes workspace area that shows the folders and views available in the opened database.
�folder path: A folder name, followed by one or more additional folder names, where each preceding folder is found. For example, path A/B indicates that folder B is within folder A, and that folder A is in the root folder.
�font: (1) A family or assortment of characters of a given size and style, for example, 9-point Bodoni modern.; (2) A particular type style (for example, Bodoni or Times Roman) that contains definitions of character sets, marker sets, and pattern sets.
�font character set: Part of an AFP font that contains the raster patterns, identifiers, and descriptions of characters.
�font ID: A number that identifies the character style and size for certain printers.
�Font Library Update Utility (FLU): An MVS-based utility processed against the AFP font library to ensure that the appropriate GRID information is available for processing COM text.
�font mapping: PSF has internal tables that equate core raster fonts to core outline fonts. This comparing and matching activity is called mapping. The default is for PSF for OS/390 not to map fonts, but you can set XTP7MTOF to ON (B'1') in Exit 7 to enable PSF to map raster fonts to outline fonts.
�font metric: Measurement information that defines individual character values such as height, width, and space, as well as overall font values such as averages and maximums. Font metrics can be expressed in specific fixed units, such as pels, or in relative units that are independent of both the resolution and size of the font. See also fixed metrics, relative metrics.
�Font Object Content Architecture (FOCA): An architecture that defines the content of IBM's digital font resources by means of a set of parameter definitions.
�font palette: In VisualAge RPG, a window from which the user can select the font to be applied to a selected control.
�font resource: A resource object that is required to print AFPDS documents on a printer. The three types of font resources are coded fonts, character sets, and code pages. The system-recognized identifier for the object type is *FNTRSC.
�font typeface global identifier (FGID): A unique font identifier that can be expressed as either a 2-byte binary or a 5-digit decimal value. The FGID is used to identify a type style and the following characteristics: posture, weight, and width.
�font width (FW): A characteristic value of a font, parallel to the character baseline, that represents the size of all graphic characters in a font.
�footer: Text that is formatted to be in the bottom margin of printed pages in a document. See also header.
�footing area: In COBOL, the position of the page body adjacent to the bottom margin.
�footprint: The amount of computer storage that is occupied by a computer program. For example, if a program occupies a large amount of storage, it has a large footprint.
�FOR: See file-owning region.
�force-all: In Application Development ToolSet, a specification that tests whether the control field in the input record contains a particular entry. If it does not, the control field character is replaced before the record is sorted.
�forced Licensed Internal Code completion: A function of the system that allows the user to force a deadlocked system to complete interrupted machine instructions by turning the Power switch on the control panel to the Delayed Off position.
�forced shutdown: A type of shutdown of the CICS adapter where the adapter immediately disconnects from WebSphere MQ for z/OS, regardless of the state of any currently active tasks. See also controlled shutdown, quiesced shutdown.
�forced update: An update to a log that must be written to nonvolatile storage before processing can proceed. In order to ensure synchronization in case of failure, most Resource Recovery Services (RRS) logging operations are forced updates.
�force time: The time when all items on a distribution queue are sent regardless of how many items are on the queue.
�forecast: A function that can provide a prediction of future performance of a managed system using past data collected on that managed system.
�foreground: (1) In multiprogramming, the environment in which high-priority programs are run. See also background.; (2) In TSO, the environment in which programs are swapped in and out of main storage to allow terminal users to share processing time.
�foreground partition: A space in virtual storage in which programs are executed under control of the system. By default, a foreground partition has a higher processing priority than the background partition.
�foreground process: A process that must be completed before another command is issued. See also background process.
�foreground process group: A group whose member processes have privileges that are denied to background processes when the controlling terminal is being accessed. Each controlling terminal can have only one foreground process group.
�foreground task: The task with which the user is interacting.
�foreign bus: A service integration bus with which a particular service integration bus can exchange messages.
�foreign cell: A cell other than the one to which the local machine belongs. A foreign cell and its binding information are stored in either Global Directory Service (GDS) or the Domain Name System (DNS). See also home cell.
�foreign configuration: Configuration options for a hosting application.
�Foreign Exchange Subscriber: A signaling protocol that links a user's location to a remote exchange that would not normally be serving that user, to provide, for instance, calls to outside the local area at the local rate.
�foreign host: See remote host.
�foreign key: (1) A field or set of fields in a dependent file of a constraint relationship. Each foreign key value must either match a parent key value in the related parent file or be null.; (2) A column or set of columns that refers to a parent key.; (3) In a relational database, a key in one table that references the primary key in another table. See also constraint, primary key, unique key.; (4) In a federated system, a key in one nickname that references the primary key in another nickname and that the optimizer uses to improve query performance. This key is not validated when operations such as insert and update are performed.
�foreign-key analysis: A type of analysis that discovers cross-table relationships by identifying foreign key candidates in table data. Foreign keys reference primary keys that are already defined or identified during primary key analysis.
�foreign key attribute: A simple attribute whose value uniquely identifies a child business object. Typically, this attribute identifies the child business object to its parent by containing the child's primary key value. See also child business object, reference-valued business object.
�foreign server: In a federated system, a data source that is used most often in the context of the SQL/MED standard. See also data source.
�forest: An ordered set of subtrees of XML nodes.
�fork: (1) To create and start a child process.; (2) A function that creates a child process, which is almost an exact copy of the calling, or parent, process.; (3) In UML diagrams, a node that is used to model a single flow of control that divides into two or more separate but simultaneous flows.; (4) A process element that makes copies of its input and forwards them by several processing paths in parallel.
�forked address space: An address space created by a fork function. A forked address space is perceived by MVS to be a batch job.
�for loop: A loop that repeats the same sequence of activities a specified number of times.
�form: (1) A physical sheet of paper or other medium on which data is printed.; (2) In query management, an object that describes how to format the data for printing or displaying a report.; (3) A display screen, printed document, or file with defined spaces for information to be inserted.; (4) A partially-filled message containing data that can be copied for a new message of the same message type.; (5) A Notes database element that controls how a user edits, displays, and prints documents. A form can contain fields, static text, graphics, and special objects. A Notes database can have any number of forms.
�format: (1) The arrangement or layout of data in a data medium.; (2) The shape, size, printing requirements, and general makeup of a printed document or presentation display.; (3) The definition of the internal structure of a message, in terms of the fields and the order of those fields. A format can be self-defining, in which case the message is interpreted dynamically when it is read.; (4) In message queuing, a term used to identify the nature of application data in a message.; (5) To arrange information on a page, in a file, or on a display screen.; (6) To prepare a diskette for use by a computer, by creating an addressing scheme for data storage.
�format frequency: The frequency distribution of general formats that are used in a column.
�format identification field (FID field): In SNA, a field in each transmission header (TH) that indicates the format of the TH; that is, the presence or absence of certain fields. TH formats differ in accordance with the types of nodes between which they pass.
�format independence: The ability to send data to a device without having to be concerned with the format in which the data is displayed. The same data may appear in different formats on different devices.
�format line: In SEU, the abbreviated names of the source line fields that are displayed directly above the source line. The format line is displayed when the F (format) line command is run.
�format resolution: A value in pels per inch that indicates the resolution in which the data stream is formatted. PSF uses this information to determine which resolution system library to use.
�Formats and Protocols (FAP): In message queuing, a definition of how queue managers communicate with each other, and of how clients communicate with server queue managers.
�format selector: A user-defined program (either a CL or a high-level language program) that determines where a record should be placed in the database when an application program does not pass a record format name for a record being added to a logical file.
�format set: In MFS, a format definition, all message definitions that refer to the format definition, and any table referred to by the format.
�formatted data interface: In FEPI, a collective name for the keystroke and screen-image interfaces.
�Formatted Data Object Content Architecture (FD:OCA): A defined collection of constructs used to interchange formatted data.
�formatted diskette: A diskette on which the control information for a particular computer system has been written but which may or may not contain any data.
�formatted document: A document arranged in paragraphs and pages usually for viewing or printing.
�formatted file: A file that is arranged with particular characteristics, such as line spacing, headings, and number of characters and lines per page. See also unformatted file.
�formatted print records: Line data made up of records that are formatted for printing on line printers. PSF uses a page definition to print formatted records on page printers.
�formatted system service: A portion of VTAM that provides certain system services as a result of receiving a field-formatted command, such as an Initiate or Terminate command. See also unformatted system service.
�formatted text: The footnote reference number and the associated text within the footnote that is resolved at the bottom of the page.
�formatter: Software that formats the captured events or information into the appropriate form before sending it to an output device or file.
�form-based login: An authentication process where a user ID and a password are retrieved using an HTML form, and sent to the server over the HTTP or HTTPS protocol.
�form bean: In Struts, a class that stores HTML or JSP form data from a submitted client request or that stores input data from a link that a user clicked. The superclass for all form beans is the ActionForm class.
�form definition: An Advanced Function Presentation (AFP) resource object that defines the characteristics of the form or printed media, including: overlays to be used, duplex printing, text suppression, the position of composed-text data on the form, and the number and modifications of a page.
�form feed: An ASCII printer control, 0C, that causes the printer to eject the current page. All jobs printing on a page printer should end with a form feed, which forces the last page to print.
�form-feed character: A character in the output stream that indicates that printing should start on the next page of an output device. The form-feed character is designated by '\f' in the C and C++ language. If the form-feed character is not the first character of an output line, the result is unspecified. X/Open.
�form-field editing: Numeric, character, or date and time editing that can be specified for a form-field instruction.
�formGroup: In EGL, a collection of form parts. A formGroup part is generated as an output separate from an EGL program.
�form logout: A mechanism to log out without having to close all Web browser sessions.
�forms control buffer (FCB): A buffer for controlling the vertical format of printed output. The FCB is a line-printer control that is similar to the punched-paper, carriage-control tape. For Advanced Function Presentation (AFP) printers, the forms control buffer is replaced by the page definition.
�forms control table (FCT): An object that contains the special processing requirements for output data streams received from a host system by a remote job entry (RJE) session. The system-recognized identifier for the object type is *FCT.
�forms flash: In AFP support on the 3800 Printing Subsystem, a means of printing an overlay using a negative plate projected on a form.
�form type: A 10-character identifier, assigned by the user, that identifies each type of form used for printed output.
�formula translation: See Fortran.
�for statement: A looping statement that contains the word for followed by a list of expressions enclosed in parentheses (the condition) and a statement (the action). Each expression in the parenthesized list is separated by a semicolon, which cannot be omitted.
�Fortran (formula translation): A high-level programming language used primarily for scientific, engineering, and mathematical applications.
�Fortran signature CSECT: The resident routine that indicates that the load module in which it is present contains a Fortran routine.
�forum: For purposes of Who Is Here in Sametime, a type of place; a database of files. In Lotus Notes, this forum is the whole database. On the Web, the forum may be a whole subdirectory of a Web site. See also Who Is Here.
�forward: In Struts, an object that is returned by an action and that has two fields: a name and a path (typically the URL of a JSP). The path indicates where a request is to be sent. A forward can be local (pertaining to a specific action) or global (available to any action).
�forwardable credential: A mechanism-specific security credential that is issued to access a resource, which is used to obtain another credential for access to a different resource.
�forwardable ticket: A ticket that allows a server to pass on the credentials of the requester to another service. For this to happen, the initial TGT must have been requested with the forwardable option and the server is allowed to delegate credentials.
�forward data type mapping: In a federated system, the mapping of a data type at a remote data source to a comparable DB2 data type. For most data sources, the default forward data type mappings are in the wrappers. See also data type mapping.
�forward declaration: A declaration of a class or function made earlier in a compilation unit, so that the declared class or function can be used before it has been defined.
�forwarder: A name server whose main purpose is to handle all off-site queries for name servers at a given site.
�forwarding server: A read-only server that replicates all changes sent to it. This contrasts to a peer/master server in in that it is read only and it can have no peers.
�forward log recovery: The third phase of restart processing, during which DB2 for z/OS processes the log in a forward direction to apply all REDO log records.
�forward-mapping domain: A domain database file that maps host names to Internet Protocol (IP) addresses.
�forward-only cursor: See nonscrollable cursor.
�forward recovery: The process of reconstructing a file from a particular point by restoring a saved version of the file and then applying changes to that file in the same order they were originally made. See also backout recovery, recoverable data set, nonrecoverable data set.
�foundation baseline: A baseline that configures a stream. Foundation baselines specify the versions and activities that appear in a view.
�four-way breakout cable: The cable used to connect the Digital Trunk Quad Adapter with up to four digital trunk processors.
�F_port: See fabric port.
�FPR: See floating-point register.
�FPS: See frames per second.
�FQDN: See fully qualified domain name.
�FRACHECK request: With RACF, the issuing of the FRACHECK macro or the RACROUTE macro with REQUEST=FASTAUTH specified. The primary function of a FRACHECK request is to check a user's authorization to a RACF-protected resource or function. A FRACHECK request uses only in-storage profiles for faster performance. See also authorization checking, RACHECK request, RACROUTE.
�fraggle attack: A type of denial-of-service attack in which User Datagram Protocol (UDP) echo requests are sent to a broadcast or multicast address, with the source address spoofed as the victim's address.
�fragment: (1) An Internet Protocol (IP) datagram that contains only a portion of the user data from a larger IP datagram.; (2) The smallest unit of file system disk space allocation. A fragment can be 512, 1024, 2048, or 4096 bytes in size. The fragment size is defined when a file system is created.; (3) The space allocated for an amount of data too small to require a full block. A fragment consists of one or more subblocks.
�fragmentation: (1) The process of breaking down an Internet Protocol (IP) datagram into smaller parts to match the capabilities of the physical medium over which it will be transmitted. See also defragmentation.; (2) An operating system's process of writing different parts of a file to discontiguous sectors on a computer storage medium when contiguous space that is large enough to contain the entire file is not available. When data is thus fragmented, the time that it takes to access the data may increase because the operating system must search different tracks for information that should be in one location.; (3) The separation of the index into pieces as a result of inserts and deletions in the index.
�frame: (1) In hypertext markup language (HTML) coding, a subset of the Web browser window.; (2) In Open Systems Interconnection architecture, a data structure consisting of slots that can accept the values of specific attributes and from which inferences can be drawn.; (3) The block of information transmitted between two or more stations in the data link layer of a network. It includes delimiters, control characters, information, and checking characters.; (4) A group of data bits, surrounded by a beginning sequence and an ending sequence or other control information.; (5) A rectangular area on microfilm, bounded by imaginary intersecting, orthogonal lines that form a grid pattern, within which data can be recorded. The grid pattern does not actually appear on the microfilm.; (6) The hardware support structure, covers, and all electrical parts mounted there that are packaged as one entity for shipping.; (7) In fibre-channel technology, the structure used to transmit data between ports. A frame consists of a start-of-frame delimiter, a header, any optional headers, the data payload, a cyclic redundancy check (CRC), and an end-of-frame delimiter. There are two types of frames: link control frames (such as transmission acknowledgments) and data frames. See also packet, data word.
�frame check sequence (FCS): In communications, a field in a frame used to determine if the frame was received without an error.
�frame reject (FRMR): In communications, a data link command or response used to reject a received frame. A frame reject is generally used to indicate that the received protocol data unit is not valid or not supported.
�frame relay: A protocol for routing frames through the network based on the address field (data link connection identifier) in the frame and for managing the route or virtual connection.
�frame-relay switch: A frame-relay node that provides both the frame-relay frame handler function and the local management interface (LMI) function.
�frameset: An HTML file that defines the layout of a Web page that is composed of other, separate HTML files.
�frames per second (FPS): The number of frames displayed per second.
�frame switching: The function performed by frame-relay nodes to route frames through a network.
�framework: (1) A set of classes that embodies an abstract design for solutions to a family of related problems.; (2) A set of class libraries encompassing the following: Functions (or set of functions) of a particular domain arranged in an inheritance hierarchy. An encoded model for use of the framework that defines the relationships between the classes in the framework and the rules that govern their use. Frameworks call the code; the user does not call the frameworks.; (3) A set of object classes that provide a collection of related functions for a user or piece of software.; (4) A micro-architecture that provides an extensible template for applications within a specific domain.
�Framework: In WebSphere MQ, a collection of programming interfaces that allow customers or vendors to write programs that extend or replace certain functions provided in WebSphere MQ products. The interfaces are the following: data conversion interface (DCI), message channel interface (MCI), name service interface (NSI), security enabling interface (SEI), trigger monitor interface (TMI).
�FRCA: See fast response cache accelerator.
�free-control-interval pointer list: In a Virtual Storage Access Method (VSAM), sequence-set, index record, a vertical pointer that gives the location of a free control interval in the control area governed by the record.
�free float: A period of time in a process flow after a task runs and before the subsequent task can start. Free floats may result from parallel paths in a process that take varying lengths of time to complete.
�free-form: Pertaining to the entering of data without regard for rules of format. See also fixed-form.
�free-form project: A monitored directory where Java EE artifacts or module files can be created or dropped. As artifacts are introduced or modified in the free-form project, the artifacts are placed in the appropriate Java EE project structures that are dynamically generated in the workspace. The rapid deployment tools generates deployment artifacts required to construct a Java EE-compliant application and deploy that application to a target server. See also monitored directory.
�free-form surface: The open area in a visual editor where developers can add and manipulate objects. For example, the Struts application diagram editor provides a free-form surface for representing JSP pages, HTML pages, action mappings, other Struts application diagrams, links from JSP pages, and forwards from action mappings.
�free-form text: Unstructured text consisting of words or sentences.
�free space: The total amount of unused space in a page, data set, file, or storage medium. Free space is the space that is not used to store records or control information.
�free space control record (FSCR): A record containing approximations of available space for each of the next 500 pages. In multidimensional clustering (MDC) tables, there is one FSCR for each block. It is stored on the first page of each block and covers only the pages in that block.
�free space element (FSE): In a hierarchical direct database, the first 8 bytes of an area that is free space. The FSE describes the area of free space in a CI or block that is 8 or more bytes in length.
�free space element anchor point (FSEAP): In a hierarchical direct database, the first four bytes of a CI or block. The first 2-byte field contains the offset, in bytes, to the first FSE in the CI or block. The second 2-byte field identifies whether this block or CI contains a bit map.
�freestanding application: (1) A z/OS C/C++ application that does not use the services of the dynamic z/OS C/C++ run-time library or of the Language Environment. Under z/OS C support, this ability is a feature of the System Programming C support.; (2) An application that is created to run without the run-time environment or library with which it was developed.
�free store: Dynamically allocated memory. New and delete are used to allocate and deallocate free store.
�free-text condition: A condition in Rembo-C syntax using variables and logical operators to evaluate true or false.
�free text search: A search in which the search term is expressed as free-form text.
�frequency coupler (F-Coupler): A physical device that merges broadband analog signals with digital data on an IBM Cabling System using shielded twisted-pair wiring. The IBM F-Coupler separates analog signals and sends them from the IBM Cabling System to the workstation. The F-Coupler allows the IBM Cabling System to accommodate simultaneous analog video with data traffic on a token-ring network.
�frequency distribution: The number of occurrences of each unique value in a column.
�frequency modulation (FM): The process of regulating the frequency of the carrier wave in accordance with speech or a signal.
�FRF: See field registration file.
�friend class: A class in which all member functions are granted access to the private and protected members of another class. It is named in the declaration of another class and uses the keyword friend as a prefix to the class.
�FRMR: See frame reject.
�front end node: An IBM System Blue Gene node on which users compile applications and submit them to be run.
�front-end programming interface (FEPI): A separately-installable function of CICS Transaction Server that enables communication with non-LU6.2 partners by simulating an LU0 or LU2 device. FEPI allows CICS to communicate with existing applications on LU0 or LU2 systems without change to those applications.
�front-end system: (1) An IMS in an MSC network in which all terminals are connected, messages are routed to the proper processing IMS, and all replies are routed to the terminals. A front-end system may also perform back-end processing. See also back-end system, pseudo-front-end system, transaction processing system.; (2) The CICS system in which the Front End Programming Interface (FEPI) runs to provide access to applications running on other systems. See also back-end system.
�front-end transaction: In synchronous transaction-to-transaction communication, the transaction that acquires the session to a remote system and initiates a transaction on that system. See also back-end transaction.
�FRR: See functional recovery routine.
�FRTE: See file request thread element.
�FRU: See field-replaceable unit.
�FS: See fibre channel service.
�FSA: (1) See functional subsystem application.; (2) See field search argument.
�FSCR: See free space control record.
�FSE: See free space element.
�FSEAP: See free space element anchor point.
�FSG: See finite state grammar.
�FSI: See functional subsystem intercommunication.
�FSID: See file space ID.
�FSM instance directory: A directory used by the finite state machine (FSM) to store temporary files, such as shared memory handles and trace files.
�FSP: See Fibre Channel Service Protocol.
�FSPF: See fibre channel shortest path first.
�FSR: See functional statistics record.
�FSS: See functional subsystem.
�FSU: See fast service upgrade.
�FTA: See File Transfer Adapter.
�FTAB: See field tab.
�FTAM: See file transfer, access, and management.
�FTP: See File Transfer Protocol.
�FTS: See file transfer support.
�fulfillment center: Serves as a storage warehouse where products are packaged and shipped to customers. Fulfillment centers, stores, and shipping carriers are treated as separate entities. See also disposition, shipping carrier.
�FULIC: See feature-unique Licensed Internal Code.
�full access state: A state indicating that both read access and write access to a table are allowed.
�full backup: (1) The process of copying all the files on a system. See also cumulative backup.; (2) The process of backing up the entire server database. A full backup begins a new database backup series. See also database snapshot.
�full build: In Eclipse, a build in which all resources within the scope of the build are considered. See also incremental build.
�full capacity: The total number of physical processors that are available for use in an eligible machine.
�full-capacity pricing: A software licensing plan that bases charges on the capacity of the entire machine on which applications are executed. See also subcapacity pricing.
�full deployment: Deployment of all the data required to set up the resources for an entire instance.
�full DST capability: A dedicated service tools (DST) capability used by a service representative or an experienced system user that provides access to all DST functions except changing DST passwords.
�full duplex: Pertaining to communication in which data can be sent and received at the same time.
�full-function database: Hierarchic database that is accessed through Data Language I (DL/I) call language and can be processed by all six types of application programs: IFP, MPP, BMP, JMP, JBP, and batch. Full-function databases include HDAM, PHDAM, HIDAM, PHIDAM, HSAM, HISAM, SHSAM, and SHISAM.
�full function mode: The state that permits a printer to produce page-mode output.
�full installable unit: An installable unit that installs the base installable unit, upon which fixes and updates can be applied.
�full installation: The process of installing both the CSM software and the operating system on the nodes of the cluster, as opposed to installing only CSM on the nodes, or installing only the operating system on the nodes.
�full matching: The matching of a credit payment with a credit advice and not allowing additional credit payments to be matched with the same advice. See also matched credit, partial matching.
�full menus: A choice that allows a user to see all of the choices available on the menus.
�full-motion video: Video reproduction at 30 frames per second (fps) for NTSC signals or 25 fps for PAL signals.
�full notebook: A choice that allows a user to see all of the choices available in the notebook.
�full outer join: The result of an SQL join operation that includes the matched rows of two tables that were joined and preserves the unmatched rows of both tables. See also left outer join, right outer join, join.
�full pointer: In DCE Remote Procedure Call (RPC), a pointer without the restrictions of a reference pointer.
�full procedural file: In RPG, a file that uses input operations controlled by programmer-specified operation codes instead of by the program cycle. See also primary file.
�full refresh: (1) In SQL replication, the process by which a target table is loaded with data from its source table. A full refresh replaces all data in a target table. See also change-capture replication.; (2) In Q replication, the process in which all of the data that matches the search conditions for a Q subscription for a replication source table is copied to a target table. A full refresh replaces all data in a target table.
�full repository: A complete set of information about every queue manager in a cluster. This set of information is called the repository or sometimes the full repository and is usually held by two of the queue managers in the cluster. See also partial repository.
�full save operation: In Backup, Recovery, and Media Services, a backup operation that includes all objects, libraries, or folders in a control group regardless of whether they have been changed since the last backup operation or archive operation.
�full-screen editor: A program that allows users to edit an entire screen of data or text at one time.
�fullselect: A subselect, a values-clause, or a number of both that are combined by set operators. Fullselect specifies a result table. If UNION is not used, the result of the fullselect is the result of the specified subselect. See also scalar fullselect.
�full synchronization: The process of applying the complete reference model to a target system, even if that involves removing installed software.
�full-text index: A data structure that references data items to enable a search to find documents that contain the query terms.
�full-text search: Search option that lets you search a Notes database for words and phrases, as well as perform more complex searches using wildcards and logical operators.
�full trace: Option for formatting CICS trace entries. Full trace shows all the data for each trace entry. See also abbreviated trace.
�full user mobility: Wireless classification under which users can access data while in motion, for example, in a vehicle.
�full-valued business object: A business object that contains data values for all of its attributes, not only for its key attributes. Such a business object represents a complete entity. For example, when a collaboration sends a reference-valued business object with a Retrieve verb to a connector, the connector returns a full-valued business object. See also reference-valued business object.
�full volume dump: In DFSMShsm, the process of using a DFSMSdss function that dumps the entire volume image.
�full volume restore: In DFSMShsm, the process of using a DFSMSdss function that restores the entire volume image.
�fullword: (1) See computer word.; (2) A sequence of bits or characters that comprises four bytes (one word) and is referenced as a unit.
�fullword binary: In DB2 for i5/OS, a binary number with a precision of 31 bits.
�fullword boundary: A storage location whose address is evenly divisible by 4. See also word boundary.
�fully escaped mapping: A mapping of characters in an SQL identifier to characters in an XML name where some characters might be represented using XML character escapes.
�fully qualified data set name: A data set in which all the qualifiers are completely spelled out.
�fully qualified domain name (FQDN): In Internet communications, the name of a host system that includes all of the subnames of the domain name. An example of a fully qualified domain name is rchland.vnet.ibm.com.
�fully qualified name: A qualified name that includes all names in the hierarchical sequence above the structure member to which the name refers, as well as the name of the member itself.
�function: (1) A relationship between a set of input data values and a set of result values that is used to extend and customize SQL or XQuery. Functions are invoked from elements of SQL statements such as the select list or the FROM clause and from XQuery as primary expressions. See also aggregate function, built-in function, external function, scalar function, sourced function, table function, user-defined function, SQL function, row function, routine.; (2) Any instruction or set of related instructions that perform a specific operation.; (3) A named group of statements that can be called and evaluated and can return a value to the calling statement. See also built-in function.; (4) In REXX, a series of instructions that a REXX procedure calls to perform a specific task and to return a value. The three types of routines that can be called as functions are internal, built-in, and external.; (5) In SQL, an operation that supplies a single value from another value or from a set of values. A function obtains a single value by applying the function name (for example, AVG) to the result of the expression (for example, column-name).; (6) A machine action such as carriage return or line feed.; (7) In ADSI, an ADSI instruction, or group of instructions.
�functional acknowledgment: An electronic acknowledgment returned to the sender to indicate acceptance or rejection of EDI documents.
�functional acknowledgment map: A set of mapping instructions that describe how to create an EDI Standard functional acknowledgment. One of three supported map types.
�functional group: One or more documents of a similar type transmitted from the same location and enclosed by functional group header and trailer segments.
�functional privilege: The ability to grant or revoke access to individual service tools functions.
�functional recovery routine (FRR): A z/OS recovery and termination manager that enables a recovery routine to gain control in the event of a program interrupt.
�functional specification: See software requirements specification.
�functional statistics record (FSR): A record that is created each time a DFSMShsm function is processed. The FSR contains a log of system activity and is written to the system management facilities (SMF) data set.
�functional subsystem (FSS): An extension of JES that runs in an address space separate from the JES address space. An FSS provides support for a function peripheral to JES processing, such as a peripheral device or other component.
�functional subsystem application (FSA): (1) An area within the PSF functional subsystem (FSS) that drives and manages a single printer.; (2) An application that uses the support facilities of the functional subsystem (FSS) to communicate with JES.
�functional subsystem intercommunication (FSI): Provides formal communication between JES3 and the functional subsystem application or FSS.
�functional unit: (1) Hardware, software, or a combination of hardware and software that is capable of accomplishing a specified purpose.; (2) In OSI, a logical grouping of related services.
�functional verification procedure: A procedure distributed with DFSMShsm that verifies that all basic DFSMShsm functions are operating correctly.
�function body: The piece of code that implements a function.
�function call: (1) In REXX, the process of calling a set of instructions that must return a result. Function calls can be included in an expression anywhere that a term would be valid.; (2) An expression that transfers the path of execution from the current function to a specified function (the called function). A function call contains the name of the function to which control is transferred and a parenthesized list of values
�function check: A notification that an unexpected condition has stopped the running of a program.
�function code: A numeric code used by MVS when requesting a service or control information from JES3 by using the subsystem interface (SSI).
�function control sequence (FCS): A multiple-leaving telecommunications access method (MTAM), control character that controls the flow of individual function streams.
�function control table (FCT): The master dispatching queue for JES3. Entries in the FCT are arranged in priority order and each represents a dynamic service program (DSP) to be dispatched.
�function declarator: The part of a function definition that names the function, provides additional information about the return value of the function, and lists the function parameters. See also declarator.
�function definer: The authorization ID that was used to process the CREATE FUNCTION statement.
�function definition: The complete description of a function. A function definition contains an optional storage class specifier, an optional type specifier, a function declarator, optional parameter declarations, and a block statement (the function body).
�function directory: A DB2 database directory that is used to store the executable files and libraries that are associated with users' external routines (procedures, functions, and methods).
�function invocation: The use of a function together with any argument values being passed to the function body. The function is invoked by its name.
�function key: A keyboard key that can be programmed to perform certain actions.
�function key indicator: In RPG, an indicator that is set on when a valid corresponding function key is pressed. Valid function key indicators are KA through KN and KP through KY.
�function management data: A response unit (RU) category used for end-user data exchanged between logical units (LUs) and for requests and responses exchanged between network services components of LUs, physical units (PU), and control points.
�function management end (FME): An SNA logical unit response type that CICS terminal control receives from a logical unit.
�function management header (FMH): (1) In SNA, a record that contains control information for the data that follows.; (2) One or more headers, optionally present in the leading request units (RUs) of an RU chain, that allow one LU to (a) select a transaction program or device at the session partner and control the way in which the end-user data it sends is handled at the destination, (b) change the destination or the characteristics of the data during the session, and (c) transmit between session partners status or user information about the destination (for example, a program or device). Function management headers can be used with LU type 1, 4, and 6.2 protocols.
�function management profile: In SNA, a specification of various data flow control protocols (such as response unit (RU) chains and data flow control requests) and function management data options (such as use of function management headers, compression, and alternate codes) supported for a particular session. Each function management profile is identified by a number.
�function mapping: In a federated system, a mapping between a data source function and an existing DB2 database function. The DB2 database management system supplies default mappings between existing built-in data source functions and built-in DB2 database functions; the default mappings are in the wrapper. The DB2 counterpart function can be either a complete function or a function template. See also function template.
�function modification identifier (FMID): (1) The value used to distinguish separate parts of a product. A product tape or cartridge has at least one FMID.; (2) With System Modification Program/Extended (SMP/E), a code that identifies the release levels of a program product.
�function name: In COBOL, an IBM-defined name that identifies system logical units, system-supplied information, printer control characters, and program switches.
�function package: A package that results from binding the DBRM for a function program.
�function package owner: The authorization identifier of the user who binds the function program's DBRM into a function package.
�function path: See SQL path.
�function prototype: A function declaration that provides type information for each parameter. It is the first line of the function (header) followed by a semicolon (;). The declaration is required by the compiler at the time that the function is declared, so that the compiler can check the type.
�function resolution: The process, internal to the database manager, by which a particular function instance is selected for invocation. The function name, the data types of the arguments, and the function path are used to make the selection.
�function scope: Labels that are declared in a function have function scope and can be used anywhere in that function after their declaration.
�function selection: See function resolution.
�function shipping: (1) The process of sending the subsections of a request to the specific database partition that contains the applicable data.; (2) The process, transparent to the application program, by which CICS accesses resources when those resources are actually held on another CICS system.
�function signature: The logical concatenation of a fully qualified function name with the data types of all of its parameters.
�function SYSMOD: An IBM product that can be installed with SMP/E. CICS Transaction Server is packaged as a function SYSMOD on a distribution tape. This contains distribution libraries and JCLIN data which SMP/E uses to create the target libraries.
�function template: (1) A DB2 database function that forces the federated server to start a data source function. A function template does not contain code that can be run. See also function mapping.; (2) A detailed plan that describes the construction of a set of related individual C++ functions.
�fuse: In Tivoli SANergy, to connect to a SANergy-managed volume for accelerated access. The successful combining of traditional LAN network transmissions with that of the high-speed payload transmissions of SANergy. You may attempt to fuse any NFS-mounted volume that also has a direct access path via a SAN technology (such as Fibre Channel). If SANergy is working correctly, you will see statistics on fused transfers increasing when performing operations to the companion NFS-mounted volume.
�fuser counter: See jam recovery page counter.
�fuser station: The printer assembly that bonds the toned image to the paper by heat and pressure.
�future order: A release of an advanced order for which the user has requested that the shipment be delayed until a specified future date.
�future order offset: A setting in an online store that indicates how much time in advance of the specified ship date of a future order when order items should be allocated in inventory.
�fuzzy copy: A backup version or archived copy of a file that might not accurately reflect the original contents of the file, because it was backed up or archived when the file was being modified.
�fuzzy image copy: An image copy of an online database. The database can be updated while the image copy is being taken and some, all, or none of the updates might appear in the image copy.
�fuzzy search: A search that can find words with spellings that are similar to that of the search term.
�FW: See font width.
�Fx_port: A fabric port that can operate as either a fabric port (F_port) or fabric loop port (FL_port). See also fabric port, fabric loop port.

�

Back to top�