
	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

�

�OAF: See origin address field.
�OAG: See Open Applications Group.
�OAM: (1) See object authority manager.; (2) See object access method.
�OAM complex (OAMplex): One or more instances of the object access method (OAM) running on systems that are part of a Parallel Sysplex. The OAM systems that are part of an OAMplex share a common OAM database in a DB2 data-sharing group.
�OAM-managed volume: An optical or tape volume controlled by the object access method (OAM).
�OAMplex: See OAM complex.
�OAMS: See Outgoing Application Message Store.
�OAM Storage Management Component (OSMC): A functional unit that determines where objects should be stored, manages object movement within the objects storage hierarchy, and manages expiration attributes based on the installation storage-management policy.
�OAM thread isolation support: An object access method (OAM) subsystem providing OAM-DB2 functions that use a different thread to DB2 than the application program thread.
�OASIS: See Organization for the Advancement of Structured Information Standards.
�OASN: See origin application schedule number.
�object: (1) Anything that can be created or manipulated with SQL, such as tables, views, indexes, packages, procedures, triggers, or any other objects that can be created by issuing a CREATE statement. See also database object.; (2) In object-oriented design or programming, a concrete realization (instance) of a class that consists of data and the operations associated with that data. An object contains the instance data that is defined by the class, but the class owns the operations that are associated with the data.; (3) A named storage space that consists of a set of characteristics that describe the space and, in some cases, data. An object is anything that occupies space in storage, can be located in a library or directory, can be secured, and on which defined operations can be performed. Some examples of objects are programs, files, libraries, and stream files.; (4) In object-oriented design or programming, an abstraction that consists of data and operations associated with that data.; (5) In X/Open Directory Service, data that can be identified. Each object is represented by an entry in the Directory Information Base (DIB).; (6) In AFP architecture, a collection of structured fields, bounded by a begin-object function and an end-object function. The object can contain other structured fields containing data elements of a particular type.; (7) Any digital content that a user can manipulate as a single unit to perform a task. An object can appear as text, an icon, or both.; (8) In WebSphere MQ, a queue manager, a queue, a process definition, a channel, a namelist, authentication information object, or a storage class (z/OS only).; (9) An item stored in a versioned object base (VOB). An object can be identified by an object-selector string, which includes a prefix that indicates the kind of object, the object's name, and a suffix that indicates the VOB in which the object resides. Examples: lbtype:REL1@/vobs/vega on UNIX and lbtype:REL1@\vega on Windows See also label.; (10) An entity with a well-defined boundary and identity that encapsulates state and behavior. State is represented by attributes and relationships, behavior is represented by operations, methods, and state machines. An object is an instance of a class. See also class, instance.; (11) A region of storage. An object is created when a variable is defined. An object is destroyed when it goes out of scope. See also instance.; (12) A named byte stream having no specific format or record orientation.; (13) A directory or file.
�object access method (OAM): A program that provides object storage, object retrieval, object-storage hierarchy management, and storage and retrieval management for tape volumes contained in system-managed libraries. OAM isolates applications from storage devices, storage management, and storage-device hierarchy management.
�object-action paradigm: In VisualAge RPG, a pattern for interaction in which a user selects an object and then selects an action to apply to that object.
�object adapter: In Common Object Request Broker Architecture (CORBA), the primary interface that a server implementation uses to access Object Request Broker (ORB) functions.
�object alter authority: An object authority that allows the user to change the attributes of an object, such as specifying a trigger for a database file or changing the attributes of an SQL package.
�object auditing: A function of the i5/OS operating system that creates audit records for specified types of access to an object.
�object authority: A specific authority that controls what a system user can do with an entire object. For example, object authority includes deleting, moving, or renaming an object. There are five types of object authorities: object operational, object management, object existence, object alter, and object reference.
�object authority manager (OAM): In WebSphere MQ on UNIX systems, WebSphere MQ for iSeries, and WebSphere MQ for Windows, the default authorization service for command and object management. The OAM can be replaced by, or run in combination with, a customer-supplied security service.
�object backup-storage group: A type of storage group containing optical or tape volumes that are used for backup copies of objects. See also second backup object, storage group.
�object class: (1) A categorization or grouping of objects that share similar behaviors and circumstances.; (2) In OSI, a way of grouping things of the same type, such as by country, region, or application entity. A set of common object classes has been defined by the ISO/CCITT directory standards.; (3) A template that is used to define the attributes and methods of an object.
�object class definition: A statement that specifies which attributes must be present in an object of that class, as well as attributes that might be present.
�object code: Machine-executable instructions, usually generated by a compiler from source code written in a higher level language. Object code might itself be executable or it might require linking with other object code files. See also source code.
�object code only (OCO): The practice of not supplying source code.
�OBJECT-COMPUTER: In COBOL, the name of an Environment Division paragraph in which the computer environment, within which the program is started, is described.
�object computer entry: In COBOL, an entry in the OBJECT-COMPUTER paragraph of the Environment Division that contains clauses that describe the computer environment in which the program is to be started.
�object container: A set of MO:DCA structured fields used to carry object data for a variety of objects.
�Object Data Manager (ODM): (1) A data manager intended for the storage of system data. The ODM is used for many system management functions. Information used in many commands and SMIT functions is stored and maintained in the ODM as objects with associated characteristics.; (2) An AIX proprietary storage mechanism for ASCII stanza files that are edited as part of configuring a drive into the kernel.
�object decomposition: The process of breaking an object into its component parts.
�object definition file (ODF): In VisualAge RPG, self-contained components that can be shared across applications.
�object definition table (ODT): A table built at compile time by the system to keep track of objects declared in the program. The program objects in the table include variables, constants, labels, operand lists and exception descriptions. The table resides in the compiled program object.
�object description: The characteristics (such as name, type, and owner name) that describe an object.
�object descriptor: A data structure that identifies a particular WebSphere MQ object. Included in the descriptor are the name of the object and the object type.
�object diagram: A diagram that describes objects and their relationships at a point in time. An object diagram is similar to a class diagram or communication diagram. See also class diagram, collaboration diagram.
�object directory table: A DB2 table that contains information about the objects that have been stored in an object storage group.
�object dispatcher: In the Tivoli environment, an object request broker provided by Tivoli Management Framework.
�object distribution: A function that allows a user to send source and data files, save files, job streams, spooled files, and messages to another user, either locally or on an SNADS network.
�Object Distribution Manager: The application that resides in the image host and provides services to the front-end application hosts for the storage, retrieval, and routing of image objects and coded data.
�object existence authority: An object authority that allows the user to delete the object, free storage of the object, save and restore the object, transfer ownership of the object, and create an object that was named by an authority holder.
�object file: (1) A member file in an object library.; (2) A file that contains compiled code.
�object flow state: A node in an activity diagram the represents the passing of an object from the output of one action to the input of another action.
�object handle: The identifier or token by which a program accesses the WebSphere MQ object with which it is working.
�object hierarchy: A way of illustrating relationships among objects. Each object that appears in a level below another object is an example of the upper object.
�object ID: See object identifier.
�object identifier (OID, object ID): (1) A hierarchical sequence of numbers that uniquely identifies an object.; (2) An identifier, which is usually a string of integers, that uniquely identifies a particular object within a distributed system.; (3) An ISO-defined format for identifying elements within an OSI network. An object ID consists of a string of integers. The integers in the string can identify a particular standards body, an enterprise, or the type or value of an object. An object ID is intended to be a universal identifier of an object. Examples of values that are specified in object ID format are abstract syntaxes, application context names, and application process titles.; (4) The unique 4-byte value or identifier that is assigned to a data model device. Object IDs can be used in SOAP commands, for quick searching in the data model or debugging.
�object information repository (OIR): In System Manager, the information about each object that identifies which product it is associated with, such as the release level, option, and the load identifier.
�objective: (1) A concise statement articulating a specific component of what the strategy must achieve and what is critical to its success. Objectives are best stated as action phrases which may include the means and desired results.; (2) A target level of performance expressed as a measurable goal, against which actual achievement can be compared. Objectives may be expressed as a quantitative standard, value (numeric or time), or rate. See also initiative.
�objective analyzer: A component of Tivoli Intelligent Orchestrator that determines the resource requirements of each application. It also identifies trends and peaks in resource use. Each managed application can have an associated objective analyzer.
�object library: (1) An area on a direct access storage device used to store object programs and routines.; (2) A file used to store object modules.
�object lifeline: See lifeline.
�Object Linking and Embedding (OLE): An application protocol developed by Microsoft Corporation that allows objects created by one application to be linked to or embedded in objects created by another application.
�object management (OM): In the Distributed Computing Environment (DCE), the creation, examination, modification, and deletion of potentially complex information objects.
�object management authority: An object authority that allows the user to specify the authority for the object, move or rename the object, and add members to database files.
�Object Management Group (OMG): A non-profit consortium whose purpose is to promote object-oriented technology and the standardization of that technology. The Object Management Group was formed to help reduce the complexity, lower the costs, and hasten the introduction of new software applications.
�object model: An abstraction of a system's implementation.
�object module: A set of instructions in machine language that is produced by a compiler or assembler from a subroutine or source module and can be input to the linking program. The object module consists of object code.
�object name: An object that consists of a namespace path and a model path. The namespace path provides access to the Common Information Model (CIM) implementation managed by the CIM Agent, and the model path provides navigation within the implementation. See also qualified name.
�object of entry: In COBOL, a set of operands and reserved words, within a Data Division entry of a COBOL program, that immediately follow the subject of the entry.
�object operational authority: An object authority that allows the user to look at the description of an object and use the object as determined by the user's data authorities to the object.
�object-oriented: Describing a computer system or programming language that supports objects.
�object-oriented programming: A programming approach based on the concepts of data abstraction and inheritance. Unlike procedural programming techniques, object-oriented programming concentrates not on how something is accomplished but instead on what data objects comprise the problem and how they are manipulated.
�object-oriented user interface: In VisualAge RPG, a type of user interface that implements the object-action paradigm.
�object owner: A user who creates an object or to whom the ownership of an object was reassigned. The object owner has complete control over the object.
�object program: (1) In the original program model (OPM), a set of instructions in machine-readable form. The object program is produced by a compiler from a source program. In the Integrated Language Environment (ILE) model, an object program is the result of binding modules together.; (2) A fully compiled or assembled program that is ready to be loaded into the computer. An object program consists of object modules.
�object reference: (1) In a Tivoli environment, the object identifier (OID) that is given to an object during its creation.; (2) In Common Object Request Broker Architecture (CORBA), the information needed to reliably identify a particular object.
�object reference authority: An object authority that allows the user to specify a database file as the first level in a referential constraint.
�object registry: A networkwide database that records the storage locations of all versioned object base (VOB) storage directories and all view storage directories.
�Object Request Broker (ORB): In object-oriented programming, software that serves as an intermediary by transparently enabling objects to exchange requests and responses.
�object server: See resource manager.
�object server cache: See resource manager cache.
�Object Storage and Retrieval (OSR): A component of the object access method (OAM) that stores, retrieves, and deletes objects. OSR stores objects in the storage hierarchy and maintains the information about these objects in DB2 databases.
�object storage database: A DB2 database that contains an object directory for an object storage group, a storage table for objects less than or equal to 3 980 bytes, and a storage table for objects greater than 3 980 bytes.
�object storage group: A type of storage group that contains objects on a direct access storage device (DASD), a tape, or an optical volume. See also storage group.
�object storage hierarchy: A hierarchy consisting of objects stored in DB2 table spaces on a direct access storage device (DASD), on optical or tape volumes that reside in a library, and on optical or tape volumes that reside on a shelf. See also storage hierarchy.
�object storage table: A DB2 table that contains objects.
�object subclass: An object created from another object and from which the properties of the original object are inherited.
�object superclass: The object from which subclass objects are created. The properties of the superclass object are inherited by the superclass object.
�object time: In COBOL, the time at which a program is run.
�object type: (1) A categorization or grouping of object instances that share similar behaviors and characteristics.; (2) In query management, the substring following the query command name that specifies the type of query object to be processed.
�object UUID: In DCE Remote Procedure Call (RPC), the Universal Unique Identifier (UUID) that identifies a particular RPC object.
�observability: The property of an object, which is derived from data stored with the object, that allows source to be retrieved from the object, allows the object to be re-created without being recompiled, and allows the object to be symbolically debugged.
�observer: A task that watches a process and its associated repositories, and produces output when a certain condition becomes true (for example, a threshold value has been reached).
�obstruction: An object that prevents something from working correctly.
�occasionally connected: In SQL replication, pertaining to a replication configuration that contains target servers that are not always connected to the network. This configuration allows users to connect to a primary data source for a short time to synchronize their local databases with the data at the source.
�OCCF: See Operator Communication Control Facility.
�occurrence: See repeatable sequence.
�OCDB: See optical configuration database.
�OCDS: See offline control data set.
�OCF: See operations command facility.
�OCO: See object code only.
�OCR: (1) See overcommitment ratio.; (2) See optical character recognition.
�OCS channel: See open content syndication channel.
�octal: A base-eight numbering system.
�octal constant: The digit 0 (zero) followed by any digits 0 through 7.
�octet: (1) A byte composed of eight binary elements.; (2) In Internet Protocol (IP) addressing, one of the four parts of a 32-bit integer presented in dotted decimal notation. See also dotted decimal notation.
�ODBA: See Open Database Access.
�ODBC: See Open Database Connectivity.
�ODBC driver: A dynamically-linked library (DLL) that implements ODBC function calls and interacts with a data source.
�ODBC driver manager: A DLL with an import library. The primary purpose of the Driver Manager is to load ODBC drivers. The Driver Manager also provides entry points to ODBC functions for each driver and parameter validation and sequence validation for ODBC calls.
�odd/even bus pair: An optical link card supports a pair of buses; one has an even number and the other has an odd number (for example, bus 2 and 3).
�ODF: See object definition file.
�ODLC: See outboard data link control.
�ODM: See Object Data Manager.
�ODOE: See on demand operating environment.
�ODP: See open data path.
�ODS: (1) See on-disk structure.; (2) See operation data store.
�ODT: See object definition table.
�OEM: See original equipment manufacturer.
�OEMI: See Original Equipment Manufacturer's Information.
�offer: A price for a product, in one or more currencies, along with a set of conditions such as an effective time range or an acceptable quantity range, which must be satisfied in order to use the price.
�offering: (1) An enrollable item made available through the offerings catalog. These include course offerings, curriculums, learning events, and certificates.; (2) A logical unit of software packaging and sharing that has a managed development and maintenance life cycle and customer visible attributes (offering features, product IDs, licenses, maintenance contracts, and so forth). An offering is a serviceable software asset that is orderable by an IBM customer. It can be a collection of common components, assemblies, and other offerings. See also common component, feature, assembly, serviceable software asset.; (3) A template used to describe one or more services, with guaranteed service levels, which forms the basis for service level agreements (SLAs).
�offering component: The basic unit of service, which supplies the metrics and breach values used to create an offering.
�offerings catalog: A service that lists and manages course offerings.
�offerings manager: A person who creates course offerings.
�offer price: A price at which items are offered by a store. The offer price is the final price paid, before taxes, discounts, and shipping. See also list price.
�off-hook: A telephone line state, usually induced by lifting a receiver, in which the line is ready to make a call.
�offline: Pertaining to the operation of a device that is not under the control of a system. See also online.
�offline authoring: A feature that enables users to read and modify a document outside the tool.
�offline backup: A backup of the database or table space that is made while the database or table space is not being accessed by applications. During an offline backup, the backup database utility acquires exclusive use of the database until the backup is complete. See also online backup.
�offline control data set (OCDS): In DFSMShsm, a Virtual Storage Access Method (VSAM) key-sequenced data set (KSDS) that contains information about tape backup volumes and tape migration-level-2 volumes. See also control data set.
�offline learning client: A component of the Lotus Learning Management System that is used to download courses to a computer so that a student can work throughout the course while disconnected from the network.
�offline maintenance: Maintenance activities that can occur only when user access to a database is interrupted. See also online maintenance.
�offload: To move jobs and work off work queues in order to remove them from contention for system resources or off spools to free system work space.
�offloading: In WebSphere MQ for z/OS, an automatic process whereby a queue manager's active log is transferred to its archive log.
�offset: The number of measuring units from an arbitrary starting point to some other point.
�offset pie slice: In Business Graphics Utility, a slice that is slightly removed from a pie chart to emphasize it.
�offset stacking: A function that allows the printed output pages to be offset for easy separation of the print jobs.
�off-the-rack: An offering or solution that is standard and identical to what all other customers may receive. See also glue code.
�OFR: See online forward recovery.
�OGSA: See Open Grid Services Architecture.
�OGSA instance: A single deployment of the Open Grid Services Infrastructure (OGSI) in an environment. An instance can represent an individual node or several clones of nodes.
�OGSA Policy Service: An industry-standard interface that enables developers to consistently define policies within a network environment. The OGSA Policy Service follows the Internet Engineering Task Force (IETF), policy-based network architecture and implements the behavior of the Open Grid Services Architecture (OGSA) specification.
�OGSI: See Open Grid Services Infrastructure.
�ohm: A unit of measure of electrical resistance.
�OID: (1) See object identifier.; (2) See originator ID.
�OIDCARD: A small card with a magnetic stripe encoded with unique characters and used to verify the identity of a terminal operator to RACF.
�OIR: See object information repository.
�OLAP: See online analytical processing.
�OLDS: See online log data set.
�OLE: See Object Linking and Embedding.
�OLIC: See online image copy.
�OLTP: See online transaction processing.
�OLU: See origin logical unit.
�OM: (1) See object management.; (2) See Operations Manager.
�OMG: See Object Management Group.
�omit function: A system function that determines which records from a physical file are to be omitted from a logical file. See also select function.
�OMVS: The portion of a RACF profile that contains information about users of z/OS UNIX System Services, such as attributes.
�OMVS segment: The portion of an RACF profile that contains OMVS logon information.
�OnDemand: A licensed program that provides a set of archive features that allows you to store large volumes of data or retrieve selected data. This data can be on disk, can be optical, or can be on tape storage media. OnDemand provides computer output to laser disk and extended archiving functions for a variety of data types.
�on demand operating environment (ODOE): The technology infrastructure needed to support an on demand business. The on demand operating environment is integrated, uses open standards, is virtualized, and has autonomic capabilities. See also self-healing.
�on-disk structure (ODS): The common, portable format used to store information in a Notes database. The ODS version of a Notes database is listed on the Info tab of the Database Properties box.
�one-phase commit: (1) A protocol that is used by a sync point manager to commit a transaction when only resources that are managed as a single entity are changed during the transaction. For example, one-phase commit would be used when a single database on a single system is changed. If either the system or communications fail during a one-phase commit, the sync point manager may not be informed of whether the changes were committed or rolled back.; (2) A protocol with a single commit phase, that is used for the coordination of changes to recoverable resources when a single resource manager is involved.
�one-way hash: (1) A function that converts a message into a fixed string of digits.; (2) An algorithm that converts processing data into a string of bits; known as a hash value or a message digest.; (3) In cryptography, pertaining to a type of algorithm that can be applied to a buffer of data to produce a fixed string of digits. Cryptographic programs often apply one-way hash algorithms against a set of data and often compare the results with previously generated hash values.
�one-way interaction: A type of messaging interaction in which a request message is used to request function without a reply.
�one-way message delay: The time elapsed from the moment that a message is sent from its origin until it reaches its destination.
�on-hook: A telephone line state, usually induced by hanging up a receiver, in which the line is ready to receive a call.
�online: (1) Pertaining to the operation of a functional unit or device that is under the control of the system or of a host. See also offline.; (2) Pertaining to a user's access to a computer by way of a terminal.
�online analytical processing (OLAP): The process of collecting data from one or many sources; transforming and analyzing the consolidated data quickly and interactively; and examining the results across different dimensions of the data by looking for patterns, trends, and exceptions within complex relationships of that data.
�online backup: A backup of the database or table space that is made while the database or table space is being accessed by other applications. See also offline backup.
�online catalog: General term for a collection of catalog groups or catalog entries available for display and purchase at an online store. See also master catalog.
�online change: An IMS function that supports the adding, changing, or deleting of IMS resources online such as transactions, database directories, program directories, DMBs, PSBs, and Fast Path routing codes without stopping the system to define them.
�online forward recovery (OFR): In an RSR environment, the process by which a stopped shadow database or area is brought to currency with the database or area on the active IMS by the tracking IMS.
�online image copy (OLIC): (1) The process of creating an image copy while the database is online.; (2) The image copy created by the online image copy process.
�online index: An index of the topics for the components or products in an information center.
�online index reorganization: The reorganization of indexes on a table while the table and existing indexes are available for reading and updating by concurrent transactions.
�online information: Information on the display screen that explains displays, messages, and programs.
�online log data set (OLDS): (1) A data set on direct access storage that contains the log records written by an online IMS system. See also system log data set.; (2) A data set on direct access storage that contains the log records written by DBCTL. When the current OLDS is full, DBCTL continues logging to a further available OLDS. See also system log data set.
�online maintenance: Maintenance activities that can occur while users are connected to a database. See also offline maintenance.
�online name: In Sametime, the name by which a user is seen by other users. This name is entered, along with a password, when the user logs into the Sametime server.
�online reorganization: Database reorganization, which is available only for HALDBs and DEDBs, during which the database remains available for updates during the reorganization process.
�online status: The current state of a person who is logged in to a server.
�online test: A standardized set of tests for BSC. The tests are used to ensure the proper operation and correct working of the data link (lines and modems) portion of the total system.
�online transaction processing (OLTP): A type of interactive application in which requests submitted by users are processed as soon as they are received. Results are returned to the requester in a relatively short period of time.
�only-in-chain (IOC): A request unit for which the request header (RH) begin chain indicator and RH end chain indicator are both on.
�ontology: An explicit formal specification of the representation of the objects, concepts, and other entities that can exist in some area of interest and the relationships among them. See also Web Ontology Language.
�OOB: See out-of-band.
�OOP: See out-of process.
�OOV: See out-of-vocabulary.
�OPC: See originating point code.
�op code: See operation code.
�open: (1) To make a file available to a program for processing. See also close.; (2) To establish a temporary logical connection between a file and a running program. The connection exists until the program closes the connection or the program terminates.
�Open Applications Group (OAG): A non-profit industry consortium comprised of many prominent stakeholders in the business software component interoperability arena. The OAG defines Business Object Documents (BOD).
�open content syndication channel (OCS channel): An XML-based format for syndicated content.
�Open Database Access (ODBA): A callable interface that can be used by an z/OS application program to issue DL/I calls to an IMS DB system. The application program must use the RRS of z/OS as a sync-point manager.
�Open Database Connectivity (ODBC): A standard application programming interface (API) for accessing data in both relational and nonrelational database management systems. Using this API, database applications can access data stored in database management systems on a variety of computers even if each database management system uses a different data storage format and programming interface.
�open data path (ODP): A control block created when a file is opened. An ODP contains information about the merged file attributes and information returned by input or output operations. The ODP only exists while the file is open. See also shared file.
�OpenEdition MVS: See UNIX System Services.
�OpenEdition MVS file system: See z/OS file system.
�open feedback area: In the C language, an area containing general information about the opened file, including its name, library, and file type. This area also contains specific information about the file type, which applicable fields depend on, and about each device and communications session defined for the file.
�open file: A file that is currently associated with a file descriptor.
�open file description: A record of how a processor or a group of processes are accessing a file. Each file descriptor refers to exactly one open file description, but an open file description can be referred to by more than one file descriptor. A file offset, file status, and file access modes are attributes of an open file description. X/Open. ISO.1.
�Open Grid Services Architecture (OGSA): A well-defined set of basic interfaces that is the basis for constructing various systems and is used to describe extensibility, vendor neutrality, and commitment to a community standardization process. OGSA brings together Web services standards such as Web Services Description Language (WSDL); Universal Description, Discovery, and Integration (UDDI); and Simple Object Access Protocol (SOAP). See also grid computing, Reporting Grid Services.
�Open Grid Services Infrastructure (OGSI): The set of interfaces that enable developers to create, discover, manage, and exchange information among grid services.
�open key storage: In MVS storage protection, storage with storage key 9. called key-9 storage. In open key storage, fetch and store operations are permitted, regardless of the access key. CICS user-key storage is in MVS open key storage.
�open mode: In COBOL, the condition of a file after the program processes an OPEN statement for that file and before the program processes a CLOSE statement for that file. The particular open mode is specified in the OPEN statement as either INPUT, OUTPUT, I-O, or EXTEND.
�open registration: A registration process in which any user can register their own workstation as a client node with the server. See also closed registration.
�open relationship: A relationship on an object that no longer points to a second object because the second object has been deleted.
�Open Service Gateway (OSG): A specification that is being defined by the Open Service Gateway initiative (OSGi), a consortium of more than 20 companies, including IBM. The OSG specification will outline open standards for the management of voice, data and multimedia wireless and wired networks..
�Open Service Gateway initiative (OSGi): A consortium of more than 20 companies, including IBM, that creates specifications to outline open standards for the management of voice, data and multimedia wireless and wired networks.
�Open Servlet Engine (OSE): A lightweight communications protocol developed by IBM for interprocess communication.
�Open Shortest Path First (OSPF): A link-state routing protocol that was developed for IP networks and is based on the Shortest Path First (SPF) algorithm. Open Shortest Path First is an Interior Gateway Protocol.
�Open Software Foundation (OSF): A nonprofit research and development organization with these goals: to develop specifications and software for use in an open software environment; and to make the specifications and software available to information technology vendors under fair and equitable licensing terms.
�open source: Pertaining to software whose source code is publicly available for use or modification. Open source software is usually developed as a public collaboration and made freely available, although its use and redistribution might be subject to licensing restrictions. Linux is a well known example of open source software.
�open system: A system whose characteristics comply with standards made available throughout the industry and that therefore can be connected to other systems complying with the same standards.
�open systems interconnection (OSI): The interconnection of open systems in accordance with standards of the International Organization for Standardization (ISO) for the exchange of information.
�open systems interconnection architecture (OSI architecture): Network architecture that adheres to the particular set of ISO standards relating to Open Systems Interconnection.
�open systems interconnection network (OSINET): A test network sponsored by the National Institute of Standards and Technology. The goal of OSINET is to provide a common set of OSI protocols that allow all participants to communicate with each other for development and research, and for interoperability testing.
�open systems interconnection reference model (OSI-RM): The seven-layer basic reference model that ISO 7498 (CCITT X.200) uses to describe how open systems should act and interact. The three primary kinds of interactions described in that reference model are the interactions: (a) inside layers, (b) between layers, and (c) between open systems.
�Open Transaction Manager Access (OTMA): A component of IMS that implements a transaction-based, connectionless client/server protocol in an MVS sysplex environment. The domain of the protocol is restricted to the domain of the MVS Cross-System Coupling Facility (XCF). OTMA connects clients to servers so that the client can support a large network (or a large number of sessions) while maintaining high performance. See also IMS connect.
�operand: (1) An entity on which an operation is performed.; (2) Information entered with a command name that defines the data on which a command processor operates and that controls the running of the command processor.; (3) An argument to a command that is generally used as an object supplying information to a utility necessary to complete its processing. Operands generally follow the options in a command line.
�operating diskette: In finance communications, the diskette that contains the operating image. The operating diskette is used to load the operating image to the main storage of the 4701 Finance Communication Controller.
�operating image: In finance communications, a collection of the 4701 Finance Communication Controller microcode, user system configuration, and user application programs.
�operating mode: A setting that determines the degree of automation and manual intervention required in creating and approving deployment requests. There are three modes: automatic, semi-automatic, and manual. An operating mode can be defined at the global, application, and tier level.
�operating set: The set of nodes that are operating together to deliver storage services.
�operating system (OS): A collection of system programs that control the overall operation of a computer system.
�Operating System/400 (OS/400): The IBM licensed program that can be used as the operating system for iSeries servers prior to Version 5 Release 3. See also i5/OS.
�operating system process: A unique address space and execution environment in which instances of classes and subsystems reside and run.
�operating system template: A set of installation and configuration data that z/VM Center uses as a source for creating operating system instances. Operating system templates are created from master systems.
�Operating System/Virtual Storage (OS/VS): A family of operating systems that control IBM System/360 and System/370 computing systems. OS/VS includes VS1, VS2, MVS/370, MVS/XA, and MVS/ESA.
�operation: (1) In object-oriented design or programming, a service that can be requested at the boundary of an object. Operations include modifying an object or disclosing information about an object.; (2) A specific action (such as add, multiply, or shift) that the computer performs when requested.; (3) An implementation of functions or queries that an object might be called to perform. See also method.
�Operational Assistant: A part of the operating system that provides a set of menus and displays for end users to do commonly performed tasks, such as working with printer output, messages, and batch jobs.
�operational data: (1) Data that is collected by an application during its operation. An application can store its operational data in many formats, such as relational databases, log files, and spreadsheet files. It is "live" data, as opposed to the historical data in the central data warehouse.; (2) Data that is used to run the day-to-day operations of an organization.
�operational data store: The place where operational data resides, such as a database or a log file.
�operational descriptor: Information about an argument's size, shape, and type, which is passed by the system to the called procedure. This information is useful when the called procedure cannot precisely anticipate the form of the argument, for example, different types of strings.
�operational report: (1) A report based on data from the WebSphere Commerce database that is created in real time.; (2) A report that shows current information about data center inventory, activity, and system compliance.
�operational sign: In COBOL, an algebraic sign associated with a numeric data item or a numeric constant that indicates whether the item is positive or negative.
�operation code (op code): (1) A code used to represent the operations of a computer.; (2) In RPG, a word or abbreviation, specified in the calculation specifications, that identifies an operation.
�operation data store (ODS): The working area for the extract, transform, and load (ETL) processing. The data from WebSphere Commerce is replicated to ODS (_r tables).
�operation mapping: An interface map in which operations of the source interface are mapped to operations of the target interface.
�operations command facility (OCF): A facility of the central processor complex (CPC) that accepts and processes operations management commands.
�Operations Console: A feature of System i Access for Windows that provides the ability for a System i console to be either a local or a remote personal computer. With Operations Console, a system administrator, for example, can access the console from home. See also local console, remote console, twinaxial console.
�operations management: In System Manager, the discipline that manages the use of systems and resources to support enterprise information-processing work loads.
�operations manager: A defined role in WebSphere Commerce that manages order processing, ensuring that orders are properly fulfilled, payment is received, and orders are shipped. The operations manager can search for customer orders, view details, manage order information, and create and edit returns. See also order, sales manager.
�Operations Manager (OM): In an IMSplex, a CSL component that receives commands from AOPs, routes the command to IMSplex members, consolidates commands responses, and sends the responses to the AOP.
�Operations Navigator: See System i Navigator.
�operator: (1) In the C, COBOL, and REXX languages, a token that specifies the type of action to be done on one or more terms. The four types of operators are concatenation, arithmetic, comparison, and logical.; (2) In an access plan for an SQL or XQuery statement, a token that specifies the type of action that must be performed on data or on the output from a table or an index when the access plan is executed.; (3) In Query Patroller, a person who has a subset of administrator authorities, as defined in his or her operator profile. See also profile.; (4) An enterprise search user who has the authority to observe, start, and stop collection-level processes.
�Operator Communication Control Facility (OCCF): An IBM licensed program that allows communication with and the operation of remote MVS or VSE systems.
�operator control function: In MFS, the means by which a terminal operator controls the display of output messages. Specific operator control functions are provided by IMS, but their use must be defined by the user in an operator control table.
�operator control table: In MFS, a user-defined table of operator control functions; when a table is used, a specific control function is invoked when the input device data or data length satisfies a predefined condition.
�operator function: An overloaded C++ operator that is either a member of a class or takes at least one argument that is a class type or a reference to a class type.
�operator identification (OPID): A 1-to-3 character code that is assigned to each operator and is stored in the operator's terminal entry in the CICS terminal control table (TCTTE) when the operator signs on.
�operator logical paging: An MFS facility that allows the device operator to request a specific logical page of an output message. See also logical paging.
�operator panel: See control panel.
�operator precedence: In programming languages, an order relationship that defines the sequence of the application of operators with an expression.
�operator profile: A specification of the resources and activities over which a network operator has control. The profile is stored in a file that is activated when the operator logs on.
�OPID: See operator identification.
�OPM: See original program model.
�OPTB: See output parameter text block.
�optical cable: A fiber, multiple fibers, or a fiber bundle in a structure built to meet optical, mechanical, and environmental specifications.
�optical character recognition (OCR): Character recognition that uses optical means to identify graphic characters. See also magnetic ink character recognition.
�optical configuration database (OCDB): The optical library table, the library slot table, the optical drive table, the optical volume table, and the tape volume table that reside in a DB2 database and describe the current object access method (OAM) configuration.
�optical device: Either a CD-ROM drive, a digital video disk (DVD), or both.
�optical disk: A disk that uses laser technology for data storage and retrieval.
�optical disk cartridge: A plastic case that protects and holds an optical disk, and permits insertion into an optical disk drive.
�optical disk drive: The mechanism used to seek, read, and write data on an optical disk. An optical disk drive can be operator-accessible or library-resident.
�optical drive: The part used to seek, read, and write data on an optical disc. An optical drive may reside in an optical library or as a stand-alone unit.
�optical image file: A byte-stream file that contains a bit-for-bit mapping of an ISO9660 format CD-ROM or Universal Disk Format (UDF) DVD.
�optical library: A set of optical disk drives and optical disks defined to a source control data set (SCDS). An optical library can be a physical library with the optical drives and optical disks residing within the same storage device, or a pseudo library that consists of operator-accessible drives and shelf-resident optical disks.
�optical redundancy: A second optical path used to keep the system operational when a hardware failure occurs.
�optical scanner: A device that scans optically and usually creates an analog or digital signal.
�optical volume: Storage space on an optical disk, identified by a volume label. See also shelf-resident optical volume.
�optical volume set: Both sides of a double-sided volume optical disc containing optically stored data.
�OptiConnect: (1) A feature of the i5/OS operating system that allows a user to connect multiple System i systems by using SPD bus, high-speed link (HSL) loop, or virtual interpartition technologies.; (2) A System i system area network (SAN) that allows high-speed links between systems in a System i cluster. OptiConnect provides three hardware technologies (SPD OptiConnect, high-speed link (HSL) OptiConnect, and virtual OptiConnect) that can exist simultaneously on a single cluster node.
�optimistic concurrency control: See optimistic locking.
�optimistic locking: A locking strategy whereby no lock is held between the time that a row is selected and the time that an update or a delete operation is attempted on that row. See also pessimistic locking.
�optimization guideline: An instruction to the query optimizer on how to choose a query execution plan. See also optimization profile, global optimization guideline, statement optimization guideline.
�optimization level: The level of efficiency for processing a program, which is determined by the application programmer. When the code is optimized on the system, the system uses processing shortcuts to reduce the amount of system resources necessary to produce the same output. The processing shortcuts are then translated by the system into machine code, which allows the program to run more efficiently.
�optimization profile: An XML document that contains optimization guidelines for one or more DML statements. An optimization profile is used to provide explicit guidelines to the query optimizer when DML statements are not achieving the desired performance and tuning options are ineffective. See also optimization guideline.
�optimize: To improve the speed of a program or to reduce the use of storage during processing.
�optimized dialogue transfer: In OSI, a quality-of-service value provided by the session layer that enables the concatenation of multiple application entity requests--such as data and control information requests--when transferring them. The concatenation increases data throughput.
�optimized SQL text: SQL text, produced by the Explain facility, that is based on the query actually used by the optimizer to choose the access plan. This query is supplemented and rewritten by the various components of the SQL compiler during statement compilation. The text is reconstructed from its internal representation and differs from the original SQL text. The optimized statement produces the same result as the original statement.
�optimum block size: For data sets that do not use the Virtual Storage Access Method (VSAM), the block size that would result in the smallest amount of space used on a device, taking into consideration record length and device characteristics.
�opt in: In a privacy policy, a representation of an individual's implicit or explicit choice to accept the intended use of the individual's privacy-sensitive information. See also opt out, privacy policy.
�option: (1) A specification in a statement that can influence the running of the statement.; (2) One or more characters added to a SWIFT field number to distinguish among different layouts for and meanings of the same field. For example, SWIFT field 60 can have an option F to identify a first opening balance, or M for an intermediate opening balance.; (3) See feature.
�optional file: In COBOL, a file that is declared as being not necessarily present each time the program is started.
�optional user facilities: Facilities defined within the CCITT Recommendation X.25 that a user of a packet-switching data network can request when establishing a virtual circuit.
�optional word: In COBOL, a reserved word included in a specific format only to improve the readability of a COBOL statement or entry.
�option button: See radio button.
�option entry: An entry in a VSAM data set that contains transmission options used by IP PrintWay to transmit data sets to a print queue in a TCP/IP network. Each option entry can also contain NetSpool parameters that specify data set characteristics for use by NetSpool. See also options data set.
�option indicator: A 1-character field that is passed with an output data record from a program to the system that is used to control the output function, such as controlling which fields in the record are displayed.
�option line: See command line.
�options data set: In IP PrintWay prior to OS/390 V2R8, a VSAM data set containing one or more options entries. See also option entry.
�option set: A set of functions that may be supported by products that implement a particular architecture. A product may support any number of option sets or none. For each option set supported, all functions in that set are supported. See also base set.
�opt out: In a privacy policy, a representation of an individual's implicit or explicit choice to decline the intended use of the individual's privacy-sensitive information. See also opt in, privacy policy.
�ORB: See Object Request Broker.
�ORB set: A group of ORBs.
�orchestration: The process of making real-time decisions about where and when to allocate resources to support business priorities and maintain service levels, based on information collected about the data center environment.
�order: The definition of a service level agreement (SLA), which also includes customer information, an offering, and the specific elements that make up the SLA. For example, customer "Accounting" signs up for the "Gold" offering for the "www.acme.com/accounting" Web site.
�order block: An indicator added to an order that indicates if the items in an order can be released to fulfillment.
�ordered set: In fibre-channel technology, a transmission word that uses 8B/10B mapping and begins with the K28.5 character. Ordered sets occur outside of frames, and include: frame delimiters, which mark frame boundaries and describe frame contents; primitive signals, which indicate events; and primitive sequences, which indicate or initiate port states. Ordered sets are used to differentiate fibre-channel control information from data frames and to manage the transport of frames. See also data word.
�ordering mode: In DB2 XQuery, a mode, either ordered or unordered, that affects the ordering of the result sequence that is returned by path expressions, union expressions, intersect expressions, and except expressions and by FLWOR expressions that do not have an order by clause.
�ordering property: In UML modeling, a constraint that indicates whether attributes and association ends should be arranged in a sequence when they are grouped in a set of similar model elements.
�orderly disconnection: An option for disconnecting CICS from DBCTL using the CDBC transaction. It allows all existing DBCTL tasks to be completed before CICS is disconnected from DBCTL. See also immediate disconnection.
�ordinal position: The position associated with each element in an array. The ordinal position is an integer value greater than or equal to 1 and less than or equal to n, where n is the cardinality.
�ordinary identifier: An uppercase letter followed by zero or more characters, each of which is an uppercase letter, a number, or the underscore character. An ordinary identifier should not be a reserved word.
�ordinary token: A numeric constant, an ordinary identifier, a host identifier, or a keyword.
�organization: (1) A hierarchical arrangement of organizational units, such that each user is included once and only once.; (2) An entity where people cooperate to accomplish specified objectives, such as an enterprise, a company, or a factory.
�organization administrator: In WebSphere Commerce, the representative of a member organization who establishes organizational approval flows, and assigns roles to the users within the organization.
�Organizationally Unique Identifier (OUI): An IEEE-standards number that identifies an organization with a 24-bit, globally unique, assigned number referenced by various standards. The OUI is used as part of the worldwide ID (WWID) in the family of 802 LAN standards, such as Ethernet and token ring, and in Fibre Channel standards.
�organizational role: In identity management, a list of account owners that is used to determine which entitlements are provisioned to them.
�organizational unit (OU): (1) A unit within an organization, such as a company, that identifies a particular set of users.; (2) An Active Directory container object used within domains. An organizational unit is a logical container into which users, groups, computers, and other organizational units are placed. It can contain objects only from its parent domain. An organizational unit is the smallest scope to which a Group Policy object can be linked, or over which administrative authority can be delegated.; (3) A body whose data is to be kept separate from that of other, similar bodies. WebSphere BI for FN uses OUs to control access to resources, and to ensure data segregation. Typically, OUs are used to represent different financial institutions, or different departments within a financial institution.; (4) One of the types of subsidiary entities that can be added to an organization. Typically, organizational units are used to logically separate business units by function.
�Organization for the Advancement of Structured Information Standards (OASIS): A worldwide consortium of more than 600 corporate and individual members that develop and promote worldwide e-business standards, such as standards for Web services, XML, electronic publishing, security, and so on.
�organization tree: A hierarchical structure of the organization that provides a logical place to create, access, and store organizational information.
�organization unit: (1) A particular occurrence or example of an organization definition. For an organization definition called Department, an example of an organization unit would be Sales and Marketing.; (2) Primary component of an organization, providing a context for its management. Organization structure relates a parent unit to its subsidiaries in a hierarchy, and each unit is responsible for collections of other business components. See also business system.
�orientation: (1) In printing, the number of degrees an object is rotated relative to a reference; for example, the orientation of an overlay relative to the logical page origin, or the orientation of printing on a page relative to the page coordinates. Orientation usually applies to blocks of information, whereas character rotation applies to individual characters. See also character rotation.; (2) The orientation of a stream refers to the type of data which may pass through the stream. A stream without orientation is one on which no stream I/O has been performed.
�origin address field (OAF): In SNA, a field in a format identification 0 (or format identification 1) transmission header that contains the network address of the originating location. In a format identification 2 heading, the field is called origin address field prime (OAF'). See also destination address field, local session identification.
�original database: In a remote journal network, the data files that reside on a primary system. During normal operations, applications make changes to the original database on the primary system.
�original equipment manufacturer (OEM): A manufacturer of equipment that can be marketed by another manufacturer.
�Original Equipment Manufacturer's Information (OEMI): A reference to an older IBM standard for a computer peripheral interface, which defines the IBM S/360 and S/370 Channel to Control Unit interface. This interface uses ESA/390 logical protocols over a common bus that configures attached units in a multi-drop bus topology.
�original program model (OPM): The set of functions for compiling source code and creating high-level language programs before the Integrated Language Environment (ILE) model was introduced.
�origin application schedule number (OASN): An IMS recovery element in an external subsystem (for example, DB2). The OASN is equivalent to the unit-of-recovery ID in the CICS recovery token. It is coupled with the IMS ID to become the recovery token for LUWs in external subsystems.
�originating point code (OPC): A code that identifies the signaling point that originated an MTP signal unit. Unique within a particular network.
�originating task: The primary agent in a parallel group that receives data from other execution units (referred to as parallel tasks) that are executing portions of the query in parallel. See also parallel task.
�originator address: A string of data representing the address of the originator of the message. The contents and format of the string are not defined by the mail server framework. The address type associated with the originator address is assumed to define the contents of the originator address field.
�originator ID (OID): A 28-byte identifier that contains a note's unique universal ID (UNID), which is essential for replication.
�originator/recipient name (O/R name): In OSI X.400, the name of the user (the originator and recipient of messages) and other attributes.
�origin ID: See origin identifier.
�origin identifier (origin ID): A 34-byte field of the MERVA user file record. It indicates, in a MERVA and SWIFT Link installation that is shared by several banks, to which of these banks the user belongs. This lets the user work for that bank only.
�origin logical unit (OLU): A logical unit that is the source of a Locate search request as part of a session initiation sequence.
�O/R name: See originator/recipient name.
�orphan account: On a managed resource, an account whose owner cannot be automatically determined by the provisioning system.
�orphan data: Data that is recorded between the last safe backup for a recovery system and the time when the application system experiences a disaster. This data is lost either when the application system becomes available for use or when the recovery system is used in place of the application system.
�orphaned contact: A contact that exists in the health notification contact list but is not defined in the contact list that is stored on the system that is specified by the CONTACT_HOST configuration parameter of the DB2 administration server. See also contact.
�orphaned element: An element that is no longer cataloged in any version of any directory. Such elements are moved to the lost+found directory of the versioned object base (VOB).
�orphaned mutex: A mutual exclusion lock that was held by a thread when that thread ended. This makes associated application data or thread resources inconsistent.
�orphan lock: An orphan lock is an RLS lock that is held by VSAM RLS but unknown to any CICS region. An RLS lock becomes an orphan lock if it is acquired from VSAM by a CICS region that fails before it can log it. A VSAM interface enables CICS, during an emergency restart, to detect the existence of these locks and release them.
�OR relationship: The specification of conditioning indicators such that the conditioned operation is done when any one of the conditions is met.
�OS: See operating system.
�OS/390: The IBM operating system that includes and integrates functions previously provided by many IBM software products (including the MVS operating system) for the IBM S/390 family of enterprise servers.
�OS/400: See Operating System/400.
�OSAM: See overflow sequential access method.
�OSE: (1) See Open Servlet Engine.; (2) See output scheduling element.
�OSF: See Open Software Foundation.
�OSF/Motif: A graphical interface that contains a toolkit, a presentation description language, a window manager, and a style guideline.
�OSG: See Open Service Gateway.
�OSGi: See Open Service Gateway initiative.
�OSGi service: An interface registered in the OSGi Service Platform and made available for receiving remote or local invocations.
�OSI: See open systems interconnection.
�OSI application: An application that communicates over an OSI network.
�OSI architecture: See open systems interconnection architecture.
�OSI Communications Subsystem: The IBM licensed program that provides communications support for open systems interconnection (OSI) on the system.
�OSI directory standard: The standard, known as X.500, that defines a comprehensive directory service, including an information model, a namespace, a functional model, and an authentication framework. X.500 also defines the Directory Access Protocol (DAP) used by clients to access the directory. The Lightweight Directory Access Protocol (LDAP) removes some of the burden of X.500 access from directory clients, making the directory available to a wider variety of machines and applications.
�OSI File Services: The IBM licensed program that provides open systems interconnection (OSI) file transfer, access, and management on the system.
�OSI Message Services: The IBM licensed program that provides message services (X.400) for open systems interconnection (OSI) on the system.
�OSINET: See open systems interconnection network.
�OSI network: A data communications network that exchanges data according to the OSI protocols.
�OSI protocols: The set of rules for exchanging data defined by the ISO in accordance with the OSI reference model.
�OSI-RM: See open systems interconnection reference model.
�OSMC: See OAM Storage Management Component.
�OSN: See output sequence number.
�OSN acknowledgment: A collective term for the various kinds of acknowledgments sent to the SWIFT network.
�OSPF: See Open Shortest Path First.
�OSR: See Object Storage and Retrieval.
�OS/VS: See Operating System/Virtual Storage.
�other-domain resource: See cross-domain resource.
�OTMA: See Open Transaction Manager Access.
�OU: See organizational unit.
�OUI: See Organizationally Unique Identifier.
�outage: (1) A failure of a system, or planned down time for maintenance or upgrade.; (2) A service condition that is below a defined threshold of acceptable performance.
�out-band discovery: See out-of-band discovery.
�outboard: Pertaining to a part that is external to the main unit.
�outboard data link control (ODLC): Data link control (DLC) processing performed by a coprocessor.
�outboard formatting: A technique for reducing the amount of line traffic between a host processor and an attached subsystem. The reduction is achieved by sending only variable data across the network. This data is combined with constant data by a program within the subsystem. The formatted data can then be displayed.
�outboard policy management: A method of managing tape volumes that defines actions for volume policies at the library instead of at the host.
�outboard record: A record originated by I/O and communication components and supported by the access methods. It describes permanent errors or reports statistical data.
�outbound: In communication, pertaining to data that is sent to the network. See also inbound.
�outbound authentication: The configuration that determines the type of accepted authentication for outbound requests.
�outbound channel: A channel that takes messages from a transmission queue and sends them to another queue manager.
�outbound document: See target document.
�outbound DTE attribute: In OSI, an attributes defined by the local node to regulate communications with an adjacent node over an X.25 subnetwork. The attribute affects only the communications over the subnetwork between the local and adjacent nodes; it does not regulate end-to-end communications.
�outbound event: An event emitted from a monitoring context or from a KPI context.
�outbound filter: A filter that is applied to frames flowing from a port onto a transmission link or LAN.
�outbound intrusion: See extrusion.
�outbound map: A map that transforms an application-specific business object into a generic business object.
�outbound message: A message generated by WebSphere Commerce that is sent to a back-end system. Outbound messages are used to integrate WebSphere Commerce with other systems.
�outbound port: The mechanism through which an outbound service communicates with the externally-hosted Web service. Messages pass between the outbound service and the external service through the appropriate port.
�outbound processing: The process by which a calling client application uses the adapter to update or retrieve data in an enterprise information system (EIS). The adapter uses operations such as create, update, delete, and retrieve to process the request.
�outbound raw attack: An outbound packet that uses a nonstandard protocol.
�outbound service: The service that provides access through one or more outbound ports to a Web service that is hosted externally.
�outer join: (1) A join method in which a column that is not common to all of the tables being joined becomes part of the resultant table.; (2) The result of a join operation that includes the matched rows of both tables that are being joined and preserves some or all of the unmatched rows of the tables that are being joined. See also inner join, join.
�Outgoing Application Message Store (OAMS): A message store, implemented as the database table DNF_OAMS, in which messages sent by local applications (ISN messages) and their acknowledgement messages (ISN ACKs) are stored.
�outgoing mail: In voice mail, messages sent by a subscriber to another subscriber on the same system, which have not yet been listened to by the addressee.
�outgoing mail database: A file that temporarily stores outgoing mail that users create when not connected to a mail server.
�outgoing message: A message with a debit payment to be scheduled and sent to another bank.
�outline: The structure that defines all elements of a database within the DB2 OLAP Server. For example, an outline contains definitions of dimensions, members, and formulas.
�outline box: In VisualAge RPG, a rectangular box positioned around a group of controls to indicate that all the controls are related.
�outline font: Fonts whose graphic character shapes are defined by mathematical equations rather than by raster patterns. See also raster font.
�out-of-band (OOB): (1) Pertaining to user-specific data that has meaning only for connection-oriented (stream) sockets. The server generally receives stream data in the same order that it was sent. OOB data is received independent of its position in the stream (independent of the order in which it was sent).; (2) Pertaining to signals that are carried within the telephony signaling channel, as opposed to the voice channel. See also in-band.
�out-of-band communication: Communication that occurs through a modem or other asynchronous connection, for example, service processor alerts sent through a modem or over a LAN.
�out-of-band discovery: The process of discovering SAN data, including topology and device data, without using the Fibre Channel data paths. A common mechanism for out-of-band discovery is the use of SNMP MIB queries, which are invoked over a TCP/IP network. See also in-band discovery.
�out-of process (OOP): A process that isolates the providers from the main CIM server by running the providers in a separate process.
�out-of-space condition: For a data set, a situation in which its allocated space is not large enough to contain more data. For a direct access storage device (DASD) or tape volume, the out-of-space condition describes the situation in which a data set on the volume cannot be extended or another data set cannot be created.
�out-of-vocabulary (OOV): Pertaining to words that are not found in a dictionary.
�output: (1) The result of processing data. Output can be displayed, printed, stored, or passed to another process.; (2) An exit point through which an element can notify downstream elements that they can now start.
�output activity: The end point of the business process.
�output branch: The area of a decision, fork, join, or merge that contains the outputs.
�output criteria: Number and types of outputs required to be produced by a task or process.
�output data: Data resulting from computer processing. See also input data.
�output data set: A file that contains the results of processing.
�output field: A field specified in a display file, database file, printer file, or ICF file that is reserved for the information processed by a program. See also input field.
�output file: (1) A database or device file that is opened with the option to allow records to be written.; (2) In COBOL, a file that is opened in either the output mode or extend mode.
�output group: A group of output data sets that share certain characteristics, such as class and destination.
�output indicator: In RPG, an indicator used to define the conditions under which an output record or an output field in the output specifications is written. An output indicator must be previously defined before it is used in the output specifications.
�output/input field: A field specified in a database, display, or ICF file that can be used for both the information supplied to the program and the information received from the program during processing.
�output list: A list of variables from which values are written to a file or device.
�output log-buffer: In WebSphere MQ for z/OS, a buffer that holds recovery log records before they are written to the archive log.
�output message: (1) A valid response mode message, a conversational mode message, an exclusive mode message, an IMS system message, an application program message, or a message switch.; (2) A message that has been received from the SWIFT network. An output message has an output header.
�output mode: In COBOL, the state of a file after running an OPEN statement, with the OUTPUT or EXTEND phrase specified for that file, and before running a CLOSE statement, without the REEL or UNIT phrase specified for that file.
�output node: A message flow node that represents a point at which messages leave the message flow or subflow. See also input node.
�output parameter: A parameter of an MQI call in which the queue manager returns information when the call completes or fails.
�output parameter text block (OPTB): In CICS/VSE, In VSE/POWER's spool-access support, information that is contained in an output queue record if a * $$ LST or * $$ PUN statement includes any user-defined keywords that have been defined for autostart.
�output PIN-protection key: In Cryptographic Support, a key encrypting key used to encrypt a PIN before it is sent to another location.
�output procedure: In COBOL, a set of programs to which control is given after a sort or merge operation.
�output queue: (1) An object that contains a list of spooled files to be written to an output device, such as a printer or a diskette. The system-recognized identifier for the object type is *OUTQ.; (2) A mechanism that can direct sequence information about ordered products to a printer or a file.
�output redirection: The specification of an output destination other than the standard one.
�output scheduling element (OSE): A control block that describes the characteristics of one or more output data sets of the same job.
�output screen: A screen that a user navigates to based on data entry and keystrokes in a 3270 application. In the 3270 terminal service recorder, the access route from one screen to another can be recorded and saved in a dialog file.
�output sequence number (OSN): A number assigned by a system to a message sent by the system. See also input sequence number.
�output service (OUTSERV): A function that handles output from jobs. When a job's data sets are passed to the output service, each data set is placed on the output queue to be processed.
�output specifications: In RPG, the means by which the programmer describes the output records and their fields or adds RPG functions to an externally described output file.
�output stream: (1) In RJE, data received from the host system to the attached devices (for example, control characters, data files, and messages). See also input stream.; (2) Messages and other output data that an operating system or a processing program displays on output devices.
�outputter: Software that distributes normalized events to one or more event consumers.
�output terminal node: A primitive through which a message is propagated by a subflow. Each output terminal node is represented as an output terminal of the corresponding subflow node.
�output writer: A part of the Job Entry Subsystem (JES) that receives job output from the system spool.
�OUTSERV: See output service.
�outside link: See external link.
�overbooked: Pertaining to a resource reservation state that indicates that insufficient resources are available for the reservation.
�overcommitment ratio (OCR): The ratio of the number of active users and the amount of main storage they use to the size of the interactive main storage pool.
�overflow: (1) The condition that occurs when data cannot fit in the designated field.; (2) A condition that occurs when a portion of the result of an operation exceeds the capacity of the intended unit of storage. See also exponent-overflow exception, fixed-point overflow exception.
�overflow area: In an HDAM or PHDAM database, the area in which IMS stores data when the root addressable area does not have enough space for a segment. See also root addressable area.
�overflow exception: A condition caused by the result of an arithmetic operation having a magnitude that exceeds the largest possible number.
�overflow indicator: In RPG, an indicator that signals when the overflow line on a page has been printed or passed. The indicator (OV and OA through OF) can be used to specify which lines are to be printed on the next page.
�overflow sequential access method (OSAM): An IMS data management access method that combines selected characteristics of BSAM and BDAM for handling data overflow from ISAM. OSAM is used by the following IMS database access methods: HISAM, HIDAM, and HDAM if VSAM is not used. OSAM is also used by some of the online pool management routines.
�overflow storage group: A storage management subsystem (SMS) storage group used to satisfy allocations for which there is no space in the primary storage group. The overflow storage group is also known as a spill storage group.
�overflow structure: A coupling facility list structure that contains shared queues when the primary structure reaches a user-specified overflow threshold. The overflow structure is optional. See also primary structure.
�overhead: The operating system activity required to perform a task.
�overlapped keystroking: A means of eliminating the delay experienced by operators when performing repetitive data entry tasks by using two BMS partitions to display two copies of the same data entry panel. After filling the first panel, the operator presses ENTER to transmit the data and moves into the second partition. While CICS is processing the input from the first partition, the operator can continue to input data in the second partition.
�overlapping fields: Fields in the same display or printer record that occupy the same positions on the display or page. Option indicators can be used to select which of the overlapping fields is to be displayed or printed.
�overlay: (1) To write over (and therefore destroy) an existing file.; (2) A program segment that is loaded into main storage and replaces all or part of a previously loaded program segment.; (3) In Performance Tools, a graph that is placed on top of another graph so that a user can view both graphs at the same time.; (4) A collection of predefined data, such as lines, shading, text, boxes, or logos, that can be merged with variable data on a page or form while printing.; (5) The technique of repeatedly using the same areas of internal storage during different stages of a program. Unions are used to accomplish this in C and C++.
�overlay map: A technique used with BMS to achieve simulated windows. See also base map, canned map.
�overlay path: All of the segments in an overlay structure between a given segment and the root segment.
�overlay program: A program module structured in such a way that, at execution time, certain control sections are loaded only when referenced.
�overlay region: In an overlay structure, a contiguous area of virtual storage into which segments can be loaded independently of paths in other regions. Only one path within an overlay region can be in virtual storage at any given time.
�overlay segment: The smallest unit of an overlay program that can be separately loaded by the overlay supervisor. An overlay segment consists of one or more sections and is always loaded at the same offset relative to the start of the program module.
�overlay segment table: A table that describes the segments of an overlay program. The overlay segment table is located at the beginning of the root segment.
�Overlay Utility: In AFP Utilities, an interactive tool that allows the user to create an overlay.
�overloaded function name: A function name for which multiple functions exist within a function path or schema. Those within the same schema must have different signatures.
�overloading: (1) The capability of an identifier or method to have different meanings depending on the context. For example, in C++, a user can redefine functions and most standard operators when the functions and operators are used with class types; (2) The existence of more than one flavor of method with the same name or operator, but with different signatures, within a class. The name or operator remains the same, but the method parameters differ, with each signature requiring a separate implementation. Such methods usually exhibit the same behavior, despite differences in signature.
�overprovisioning: A way to address current limitations of best-effort networks by allowing for more bandwidth than expected network peak requirements. Overprovisioning increases the probability, but does not guarantee the quality, of the transmission of time-sensitive and bandwidth-intensive applications.
�override: (1) To specify attributes at run time that change the attributes specified in the file description or in the program.; (2) In object-oriented programming, to define a new class behavior by changing a method inherited from a parent class.; (3) The attributes specified at run time that change the attributes specified in the file description or in the program.
�overrun: The loss of data because a receiving device is unable to accept data at the rate it is transmitted.
�overseer: A CICS program used with XRF, that runs in its own address space and provides status information about the active and alternate CICS systems. You can use it to automate a restart of failed regions.
�overstrike: Pertaining to a character or symbol that occupies the same space as another character or symbol.
�oversubscription: The ratio of the sum of the traffic that is on the initiator network-device connections to the traffic that is on the most heavily loaded Inter-Switch Links (ISLs), where more than one ISL is connected in parallel between these switches. The concept of oversubscription assumes a symmetrical network and a specific workload that is applied equally from all initiators and sent equally to all targets. See also symmetrical network.
�OWL: See Web Ontology Language.
�owned space: The storage space on a set of volumes to which DFSMShsm allocates migrated data sets and backup versions, but which should not be allocated for user jobs. Included in this set are migration-level-1, migration-level-2, and backup volumes.
�owned volume: A volume on which DFSMShsm writes dump, migration, or backup data sets.
�owner: (1) The user who creates an object or is named the owner of an object.; (2) In UNIX-based operating systems, the user name associated with a file. The owner and the superuser control access to the file.; (3) The user or group that creates a profile, or is named the owner of a profile. The owner can modify, list, or delete the profile.; (4) An indicator of the visibility and privacy of a software entity. There is an owner for each SPX model package. Software entities under the same SPX model package, either directly or indirectly, have the same owner. See also SPX model package, private.
�owner authority: The authority that the object's owner has to the object. See also primary group authority, private authority, public authority.
�owner ID: A particular field in an IBM-standard, ANSI-standard, or ISO-standard volume label.
�ownerPropagate: The process by which owners are inherited down the hierarchy tree, and their owner propagate attribute is set to true. If set to false, the owner becomes an override, pertaining only to this particular object.
�ownership privilege: A control privilege that allows all privileges for the owned data object.

Back to top�

�

�P1: See Protocol 1.
�P2: See Protocol 2.
�P3: In MERVA Link, a peer-to-peer protocol used by cooperating command transfer processors (CTPs).
�P3P: See Platform for Privacy Preferences.
�P3P privacy policy: A privacy policy that is based on the P3P specification. See also privacy policy.
�PABX: See private automatic branch exchange.
�PAC: (1) See privilege attribute certificate.; (2) See privileged attribute certificate.
�pacing: In SNA, a technique by which the receiving system controls the rate of transmission of the sending system to prevent overrun.
�pacing group: (1) See pacing window.; (2) See pacing window.
�pacing window: (1) The path information units (PIUs) that can be transmitted on a virtual route before a virtual-route pacing response is received, indicating that the virtual route receiver is ready to receive more PIUs on the route.; (2) The requests that can be transmitted on the normal flow in one direction on a session before a session-level pacing response is received, indicating that the receiver is ready to accept the next group of requests.
�pack: (1) A component (SPACK or VPACK) that fits in the 9295 Multiple Digital Trunk Processor, or one of four XPACKs on the DTXA.; (2) To store data in a compact form in such a way that the original form can be recovered.
�packagable software entity: A software entity that may be packaged by zero or more software entities. See also packaging relationship.
�package: (1) A control-structure database object produced during program preparation that can contain both executable forms of static SQL statements or XQuery expressions and placement holders for executable forms of dynamic SQL statements.; (2) A function that allows an application programmer to collect all the parts of an application together for distribution.; (3) In Java programming, a group of types. Packages are declared with the package keyword. (Sun); (4) An installable unit of a software product. Software product packages are separately installable units that can operate independently from other packages of that software product.; (5) A collection of catalog entries that has a SKU and may be ordered as a single item. See also bundle, stock keeping unit.; (6) A shipping unit that may be tracked by a shipping carrier.; (7) A collection of related classes and interfaces that provides access protection and namespace management.; (8) A container that organizes artifacts into groups.; (9) The wrapper around the document content that defines the format used to transmit a document over the Internet, for example, RNIF, AS1, and AS2.; (10) Any element in project work breakdown structure (WBS) that consists of lower-level elements, for example a deliverable or summary task with all its tasks.; (11) To assemble components into modules and modules into enterprise applications.
�package cache: A cache that stores package, statement, and section information required for the execution of dynamic and static SQL statements. This cache improves overall system performance by reducing invocations of the SQL compiler and the need to access the system catalogs. See also statement cache.
�package format: The description of the physical aspects for the construction of an installable unit (IU). This description includes, but is not limited to, location, package-specific file-naming guidelines, and file format (for example, JAR files).
�package group: A group of one or more packages that are designed to work together and can be installed to one directory.
�package list: An ordered list of package names that can be used to extend an application plan.
�package name: The name of an object that is created by the BIND, PRECOMPILE, or REBIND command. The object is a bound version of a database request module (DBRM). The name consists of a location name, a collection ID, a package ID, and a version ID.
�packager software entity: A software entity that may package zero or more software entities. See also packaging relationship.
�package statistics: Statistical details about a profiled application that are grouped by package. See also instance statistics.
�package template: A template created from a project component such as a deliverable, work product or summary task.
�packaging relationship: A relationship that defines how a packagable software entity is bundled into another software entity. See also packagable software entity, packager software entity.
�packaging utility: A utility that copies packages to a repository for posting.
�packed decimal format: Representation of a decimal value in which each byte within a field represents two numeric digits except the far right byte, which contains one digit in bits 0 through 3 and the sign in bits 4 through 7. For all other bytes, bits 0 through 3 represent one digit; bits 4 through 7 represent one digit. See also zoned decimal format.
�packed decimal item: In COBOL, a numeric data item that is represented internally in packed decimal format.
�packed field: A field that contains data in the packed decimal format.
�packed key: A key field in packed decimal format.
�packet: (1) In data communication, a sequence of binary digits, including data and control signals, that is transmitted and switched as a composite whole. See also frame.; (2) The field structure and format defined in the CCITT X.25 Recommendation.
�packet assembler/disassembler (PAD): A functional unit that enables data terminal equipment (DTE) not equipped for packet switching to use a packet-switched network.
�packet level: A part of X.25 communications that defines the protocol for building logical connections between two DTEs and for moving data on these connections.
�packet mapping: The process of converting packets of data that are transmitted in one format into another data format that redirects packets according to various criteria, changes specific fields within the packet header, or changes specific character strings within the packet data.
�packet mode host: Any non-SNA, X.25 host system.
�packet rule: A function that helps keep a network's security from being compromised. Packet rules (formerly called IP packet security) use methods such as filtering and network address translation.
�packet sequencing: A process of ensuring that packets are delivered to the receiving data terminal equipment (DTE) in the same sequence in which they were transmitted by the sending DTE.
�packet-switched data network (PSDN): A communications network that uses packets to send data.
�packet switched public data network (PSPDN): A public data network established and operated by network common carriers or telecommunication administrations for providing packet-switched data transmission.
�packet switching: The act of sending and routing packets from source to destination based on information contained in their heading record.
�packet window: A specified number of packets that can be sent by the DTE before it receives an acknowledgment from the receiving station.
�packing slip: A printed document containing a list of all the products in a given release. Typically, this document also contains the ship-to address, shipping carrier information, and sometimes pricing information. See also release.
�pad: To fill unused positions in a field with dummy data, usually zeros or blanks.
�PAD: See packet assembler/disassembler.
�padding: Bytes inserted in the data stream to maintain alignment of the protocol requests on natural boundaries. Padding increases the ease of portability to some machine architectures.
�padding character: In COBOL, an alphanumeric character used to fill the unused character positions in a physical record.
�PAG: See process access group.
�page: (1) In DB2 Database for Linux, UNIX, and Windows and DB2 for z/OS, a unit of storage within a table space, an index space, or virtual memory. In a table space, a page can contain one or more rows of a table. In an LOB table space, an LOB value can span more than one page, but no more than one LOB value is stored on a page.; (2) A fixed-length block of instructions, data, or both instructions and data that can be transferred between active physical memory and external page storage.; (3) The information that can be displayed at one time on the screen of a display device or in a window.; (4) A unit of storage equal to 512 bytes in complex instruction set computer (CISC) systems, and 4096 bytes in reduced instruction set computer (RISC) systems. A page can be moved between auxiliary storage and main storage.; (5) In the graphical data display manager (GDDM) function, the picture or chart. All specified graphics are added to the current page. An output statement always sends the current page to the device.; (6) A defined unit of space on a storage medium or within a database volume.; (7) In a graphical interface, a predefined display image that typically provides fields and controls that help users accomplish tasks.; (8) A node in a portal that can contain content in addition to labels and other pages. Pages can contain child nodes, column containers, row containers, and portlets.; (9) In DB2 for i5/OS, a block of storage within a table or an index.; (10) In a portal environment, the interface element that contains one or more portlets.; (11) To move information up or down on the display.; (12) To transfer instructions, data, or both between active physical memory and external page storage.
�pageable link pack area (PLPA): An area of virtual storage containing supervisor call (SVC) routines, access methods, and other read-only system and user programs that can be shared among users of the system. See also modified link pack area, pageable region, extended pageable link pack area.
�pageable region: In MVS, a subdivision of the pageable dynamic area that is allocated to a job step or a system task that can be paged during execution. See also pageable link pack area.
�page allocation map (PAM): A map containing information used by the storage domain to manage each of its five dynamic storage areas (DSAs).
�page bar: The part of the Integrated Solutions Console that enables users to navigate among the currently open pages.
�page body: In COBOL, that part of the logical page in which lines can be written, spaced, or both.
�page chaining: A facility available under full-function BMS. The terminal operator invokes a transaction that communicates with the terminal in the normal way. This invoked transaction might, in turn, build pages that are (if the SEND PAGE command in the invoked transaction specified RETAIN or RELEASE) chained to the pages built by the original transaction. The operator can then retrieve pages for either transaction, for example, for comparison.
�page control area (PCA): A 4-byte area placed by BMS at the end of the device-dependent data stream returned to the application.
�page data set: A data set in external page storage in which pages are stored.
�page definition: An Advanced Function Presentation (AFP) resource that defines the rules for transforming line data and XML data into Mixed Object Document Content Architecture-Presentation (MO:DCA-P) data and text controls.
�page display time: The time it takes to render a Web page on the requestor's browser, from the time the rendering begins until it is complete.
�page down: To move to the information below the information currently shown on the display. See also page up.
�page environment: The size of the page or overlay, the control data to be used in composed-text blocks, and the page segments or fonts to be used.
�page fault: A program interruption that occurs when an active page refers to a page that is not in memory.
�page format: See data map.
�page-format table: In NetSpool prior to OS/390 V2R8, a table that defines page-formatting values.
�page frame: (1) A 512-byte block of main storage on a 512-byte boundary.; (2) In real storage, a storage location having the size of a page.
�page-in: The process of moving a page from auxiliary storage to main storage.
�page layout: In AFP Utilities, a printout format of a page in the printout format definition (PFD). By using the print format utility, the user can design the page layout by placing and repeating a predefined record layout with constant data.
�page list: An assembly property that specifies the location to forward a request, but automatically tailors that location, depending on the Multipurpose Internet Mail Extensions(MIME) type of the servlet.
�page-map: A technique for loading program objects into virtual storage. The pages of a program object are brought into central storage when a page fault occurs.
�page mode: The mode of operation in which a page printer can accept an entire page of data at a time from a host processor to be printed on an all-points-addressable (APA) output medium. A page can consist of text, images, overlays, and page segments. See also compatibility mode.
�page mode environment checkpointing: A process that preserves the information needed to resume page-mode printing.
�page mode printer: An Advanced Function Presentation (AFP) printer that can print page-mode data.
�pagent: See policy agent.
�page origin: See logical page origin.
�page-out: The process of moving a page from main storage to auxiliary storage.
�page overflow: A condition that occurs when the next BMS map or block of text does not fit on the current page of the target terminal.
�page overlay: An electronic overlay that can be invoked for printing and positioned at any point on the page by an Invoke Page Overlay structured field in the print data. See also medium overlay.
�page pool: The area in the shared memory segment from which buffers are allocated for data that is read from or written to disk. Page pool size is one of the file manager startup configuration parameters.
�page position: A control in the copy group to assign the top-left boundary point of the logical page on a sheet for a data set. The page position is determined from the media origin.
�page printer: (1) In AFP support, any of a class of printers that accepts composed pages, constructed of composed text and images, among other things. See also line printer.; (2) A device that prints one page at a time
�Page Printer Communication Component (PPCC): The access method that provides the SNA communication interface between printers and PSF.
�Page Printer Formatting Aid/370: An IBM licensed program with which to create and store form definitions and page definitions, which are resource objects used for print-job management. These stored objects are used to format printed output.
�page render time: The time it takes to display a Web page on a browser.
�page segment: An AFP resource object containing text, image, graphics, or bar code data that can be positioned on any addressable point on a page or an electronic overlay.
�page set: (1) A table space or index space that consists of a collection of VSAM data sets. See also table space.; (2) A VSAM data set used when WebSphere MQ for z/OS moves data (for example, queues and messages) from buffers in main storage to permanent backing storage (DASD). See also buffer pool.
�page set recovery pending (PSRCP): A restrictive state of an index space in which the entire page set must be recovered. Recovery of a logical part is prohibited.
�page space: A system data set that contains pages of virtual storage. The pages are stored in and retrieved from the page space by the auxiliary storage manager.
�pages per side: See multiple up.
�page template: In Page Designer, a page that is used as a starting point to define consistent styles and layout for any new HTML or JavaServer Pages (JSP) page within a Web site.
�page up: To move to the information above the information currently shown on the display. See also page down.
�paging: (1) The process of transferring instructions, data, or pages between real storage and external page storage.; (2) A technique in which blocks of data, or pages, are moved back and forth between main storage and auxiliary storage. Paging is the implementation of the virtual storage concept.
�paging behavior: In capacity planning, the paging characteristics for the transaction. Users can define paging characteristics for any transaction.
�paging coefficient: In capacity planning, a number that indicates the amount of paging performed by a transaction in a workload. The higher the number, the more page faults generated. This number is not the number of page faults, but a representation of the total amount of paging.
�paging exponent: In capacity planning, a value used to determine the effects of pool size changes. The greater the paging exponent, the greater the change to synchronous reads (page faults) as memory size changes.
�paired data: In Business Graphics Utility and the GDDM function, data that is specified so that every X value has only one Y value associated with it. See also nonpaired data.
�PAL: See phase alternation line.
�palette: A range of graphically displayed choices, such as colors or collections of tools, that can be selected in an application.
�PAM: (1) See page allocation map.; (2) See Pluggable Authentication Module.
�PAN: See personal area network.
�pane: A separate area in a split window. A window can be split into two or more panes.
�panel: A formatted display of information on a screen that can also include entry fields.
�panel assembly: The hardware parts making up the operator panel, control panel, or indicator panels.
�Panel Definition Markup Language (PDML): A tag language that defines a language for describing user interface elements and layouts. PDML is based on the Extensible Markup Language (XML). PDML files are used with the Graphical Toolbox components within the IBM Toolbox for Java licensed program to simplify the construction of user interfaces within Java.
�panel format: In query management, the format of the data in an externalized query or procedure file.
�panel group: An object that contains a collection of any of the following: display formats, print formats, or help information. The system-recognized identifier for the object type is *PNLGRP.
�panic: A condition in which the kernel stops executing correctly and hangs, stops, or crashes, usually as a result of a nonrecoverable error.
�PAP: See Password Authentication Protocol.
�PAPL: See participant adapter parameter list.
�paragraph: In the Procedure Division of a COBOL program, a name followed by a period and a space and by zero, one, or more sentences. In the Identification and Environment Divisions, a header followed by zero, one, or more statements.
�paragraph header: In COBOL, a reserved word, followed by a period and a space that indicates the beginning of a paragraph in the Identification and Environment Divisions.
�paragraph name: In COBOL, a user-defined word that identifies and begins a paragraph in the Procedure Division.
�parallel: Pertaining to concurrent or simultaneous operation of two or more devices or to concurrent performance of two or more activities in a single device.
�parallel access volume (PAV): In ESS, a function that enables z/OS systems to make multiple concurrent accesses to a single volume from a single host. See also multiple allegiance, I/O Priority Queueing.
�parallel activity: An activity that is being executed at the same time as another, within the same process instance. During the time that the two activities are both running, they are said to be executing in parallel.
�parallel complex: A cluster of machines that work together to handle multiple transactions and applications.
�parallel DL/I: A facility that permits all database calls to be processed in each message processing region or batch message processing region.
�parallel function: In the context of MVS multitasking and the C Multitasking Facility, those portions of a program that can run independently of the main task program and each other. Subtasks run the parallel functions.
�parallel garbage collection: A type of garbage collection that uses several threads simultaneously.
�parallel group: A set of consecutive operations that execute in parallel and that have the same number of parallel tasks.
�parallel I/O processing: (1) A form of I/O processing in which DB2 for z/OS initiates multiple concurrent requests for a single user query and performs I/O processing concurrently (in parallel) on multiple data partitions.; (2) The process of reading from or writing to two or more I/O devices at the same time to reduce response time.
�parallelism: The ability to perform multiple database operations at the same time.
�parallelism assistant: In Sysplex query parallelism, a DB2 subsystem that helps to process parts of a parallel query that originates on another DB2 subsystem in the data sharing group.
�parallelism coordinator: In Sysplex query parallelism, the DB2 subsystem from which the parallel query originates.
�parallel job: A job that is compiled and run on the DataStage server and that supports parallel processing on SMP, MPP, and cluster systems.
�parallel processing: The use of one processor to execute more than one task at the same time or the use of more than one processor to execute a task or tasks.
�parallel session: (1) In SNA, two or more concurrently active sessions between the same two logical units. Each session can have different session parameters.; (2) Two or more concurrently active sessions between the same two network addressable units using different pairs of network addresses or local-form session identifiers. Each session can have independent session parameters.; (3) A single intersystem link that can carry multiple independent sessions. Parallel sessions are supported by CICS intersystem communication (ISC).
�parallel subroutine: In the context of MVS multitasking and the Fortran Multitasking Facility, those portions of a program that can run independently of the main task program and each other. The parallel subroutines run in MVS subtasks.
�Parallel Sysplex: (1) A set of z/OS systems that communicate and cooperate with each other through multisystem hardware components and software services to process customer workloads. See also base sysplex.; (2) A sysplex that uses one or more coupling facilities.
�parallel task: The execution unit that is dynamically created to process a query in parallel. A parallel task is implemented by a z/OS service request block. See also originating task.
�parameter (parm): (1) A value or reference passed to a function, command, or program that serves as input or controls actions. The value is supplied by a user or by another program or process.; (2) In the Reusable Asset Specification (RAS), an extension point that is viewed on a collaboration. The parameter can have type and default value information as part of its description. See also parameterized collaboration.; (3) In UML modeling, a specific argument that passes information between behavioral features of models, such as operations.
�parameter connection: A connection that satisfies a parameter of an action or method by supplying either a property's value or the return value of an action, method, or script. The parameter is always the source of the connection.
�parameter declaration: The description of a value that a function receives. A parameter declaration determines the storage class and the data type of the value. See also argument declaration.
�parameter file: An ASCII file used to set configuration parameters.
�parameterized class: In Unified Modeling Language (UML), the descriptor for a class with one or more unbound parameters.
�parameterized collaboration: A collaboration that has one or more parameters. See also parameter.
�parameterized data type: A data type that can be defined with a specific length, scale, or precision. String and decimal data types are parameterized.
�parameterized element: The descriptor for a class with one or more unbound parameters.
�parameter list: A list of values that provide a means of associating addressability of data defined in a called program with data in the calling program. It contains parameter names and the order in which they are to be associated in the calling and called program.
�parameter manager domain: Major component of CICS providing a facility to inform CICS domains of system parameters during CICS initialization. These parameters are specified in the system initialization table (SIT), as temporary override parameters read from the SYSIN data stream or specified interactively at the system console. It also provides an operator correction facility for incorrectly specified system initialization parameter keywords early in CICS initialization.
�parameter mapping: An interface map that is one level deeper than operation mappings because it maps the parameters in the source operation to the parameters in the target operation. There are five types of parameter mappings: move, map, extract, Java, and assign.
�parameter marker: A question mark (?) that appears in a statement string of a dynamic SQL statement. The question mark can appear as a typed or an untyped parameter marker where a host variable might appear if the statement string were a static SQL statement. See also typed parameter marker, untyped parameter marker.
�parameter name: A long identifier that names a parameter that can be referenced in a procedure or user-defined function.
�parametric search: A type of search that looks for objects that contain a numeric value or attribute (such as dates, integers, or other numeric data types) within a specified range.
�parent activity: (1) An activity that starts another activity, its child.; (2) An activity whose processing results in the launching of a child activity. For example, a procedure becomes a parent activity as it opens a cursor, which becomes the child activity. See also child activity.
�parent category: A category that contains other categories in a hierarchy. See also child category.
�parent class: (1) A class from which another class inherits instance methods, attributes, and instance variables. See also abstract class.; (2) The class from which another bean or class inherits data, methods, or both.
�parent directory: The directory one level above the current directory. An object's parent directory is the directory that contains the names and controlling information for the object. If the object is named in more than one directory, it has multiple parent directories.
�parent document: A document whose values are inherited by another document (the child document).
�parent enclave: The enclave that issues a call to system services or language constructs to create a nested (or child) enclave. See also child enclave, nested enclave.
�parent file: The file in a constraint relationship that contains the parent or primary key. See also dependent file.
�parent key: (1) A primary key or unique key that is used in a referential constraint. The values of a parent key determine the valid values of the foreign key in the constraint.; (2) A field or set of fields in a database file that must be unique, ascending, and may or may not contain null values. The parent key may be the same as the primary or unique key.
�parent lock: For explicit hierarchical locking, a lock that is held on a resource that might have child locks that are lower in the hierarchy. A parent lock is usually the table space lock or the partition intent lock. See also child lock.
�parent method call: A technique in which an overriding method calls the method procedure of its parent class as part of its own implementation.
�parent process: A process that is created to carry out a request or set of requests. The parent process, in turn, can create child processes to process requests for the parent.
�parent process ID (PPID): An attribute of a new process identifying the parent of the process. The parent process ID of a process is the process ID of its creator for the lifetime of the creator. After the creator's lifetime has ended, the parent process ID is the process ID of an implementation-dependent system process.
�parent row: A row that has at least one dependent row. See also dependent row.
�parent segment: In a database, a segment that has one or more dependent segments (its children) hierarchically below it.
�parent table: A table that is a parent in at least one referential constraint. See also dependent table, dependent foreign key table.
�parent table space: A table space that contains a parent table. A table space containing a dependent of that table is a dependent table space. See also dependent.
�parent UR: A unit of recovery (UR) in a cascaded transaction with one or more child URs cascaded from it.
�parent window: In some operating systems, the window that controls the size and locations of its children. If a window has children, it is a parent window.
�parity: The state of being either even-numbered or odd-numbered. See also parity bit.
�parity bit: A binary digit added to a group of binary digits to make the sum of all the digits either always odd (odd parity) or always even (even parity). See also parity.
�parity check: A test to determine whether the number of ones or zeros in an array of binary digits is odd or even.
�parity RAID: A collective term used to refer to Berkeley Redundant Array of Independent Disks (RAID) Levels 3, 4, and 5.
�parm: See parameter.
�parse: To break down a string of information, such as a command or file, into its constituent parts.
�parser: (1) A program that interprets user input and determines what to do with the input.; (2) A module used to break down a document into its component parts and to construct a document from its component parts.; (3) A program that interprets documents that are added to the enterprise search data store. The parser extracts information from the documents and prepares them for indexing, search, and retrieval.
�parser driver: In enterprise search, a service that feeds the parser service with documents. There is one parser driver for each collection. A collection's parser driver service corresponds to the collection's parser in the enterprise search administration console.
�parser service: The enterprise search service that handles all document parsing and text analysis processing across document collections. At least one parser service is running at all times.
�part: (1) In VisualAge RPG, a self-contained software object consisting of a set of external features that allow the part to interact with other parts. The parts on the VRPG palette can be used a templates to create controls.; (2) See object.
�partial call: A two-party call in which one of the two parties is a virtual party; this can be viewed as a transient stage of the telephone call.
�partial declustering: The storage of table data on a named subset of database partitions (database partition group), rather than on all database partitions for the database.
�partially bound binding handle: In DCE Remote Procedure Call (RPC), a server binding handle that contains an incomplete server address lacking an endpoint. See also endpoint map service.
�partially qualified data set name: A data set name in which not all qualifiers are spelled out. Asterisks (*) and percent signs (%) are used in place of the undefined qualifiers.
�partial matching: The matching of a credit payment with a credit advice while leaving open the possibility of matching additional credit payments with the same advice. See also full matching, matched credit.
�partial page: A page that does not contain all the intended data. Partial pages can be printed after an error is sensed.
�partial repository: A partial set of information about queue managers in a cluster. A partial repository is maintained by all cluster queue managers that do not host a full repository. See also full repository.
�participant: (1) An entity other than the commit initiator that takes part in the commit process.; (2) A person who has the capability to participate.; (3) A member of a portal place who can visit and use the place. By default, all portal users are participants in public places. See also place designer, place manager.; (4) In identity management, an individual, a role, a group, or a JavaScript script that has the authority to respond to a request that is part of a workflow.
�participant adapter parameter list (PAPL): An area in DRA storage used for communication between CICS and DRA. The PAPL holds CICS request codes and DRA return codes.
�participant definition: A component of a relationship definition that describes an entity that participates in the relationship. This entity is either attributes in a business object or simple data. Participant definitions are stored in the repository.
�participant instance: The runtime instantiation of a participant. The participant definition is a template for the participant instance.
�participant type: A specification of the kind of data associated with instances of the participant. The participant type is either a business object or a simple data type (Data).
�participating mode: In fibre-channel technology, a mode in which a loop port (L_port) in a loop has a valid arbitrated loop physical address (AL_PA) and can arbitrate, send frames, and retransmit received transmissions. See also nonparticipating mode, loop port.
�partition: (1) A portion of a page set. Each partition corresponds to a single, independently extendable data set. Partitions can be extended to a maximum size of 1, 2, or 4 gigabytes, depending on the number of partitions in the partitioned page set. All partitions of a given page set have the same maximum size.; (2) On a personal computer hard disk, one of four possible storage areas of variable size; one may be accessed by DOS and each of the others may be assigned to another operating system.; (3) A subset of the active cluster nodes that result from a network failure. Members of a partition maintain connectivity with each other.; (4) A logical division of storage on a fixed disk.; (5) In VSE, a division of the virtual address area that is available for program execution.; (6) In BMS, an addressable subset of a display device's internal resources, consisting of a fixed part of the device's screen, and a fixed part of its internal storage. See also presentation space, viewport.; (7) In basic N_UP printing, the division of the medium presentation space into a specified number of equal-sized areas in a manner determined by the current physical medium.; (8) In activity diagrams, a rectangular, uniquely named grouping that shows activity nodes and edges that have common characteristics. Partitions provide a view of the behaviors in an activity diagram, but do not affect the control flow or object flow.; (9) In architecture, a subset of classifiers or packages at the same level of abstraction. A partition represents a vertical slice through an architecture, whereas a layer represents a horizontal slice.; (10) A fixed-size division of storage.; (11) A subset of a HALDB that has the capacity of a non-HALDB database and that can be administered independently.; (12) Part of a display used as the viewport, its associated window, and its display data buffer when in partitioned state.
�partition-by growth table space: A table space whose size can grow to accommodate data growth. DB2 for z/OS manages partition-by-growth table spaces by automatically adding new data sets when the database needs more space to satisfy an insert operation. See also range-partitioned data space, universal table space.
�partition-compatible join: A join where all of the rows that are joined reside in the same database partition. See also collocated join.
�partition descriptor (PD): An entry in the PDB for a partition in a partition set. The entry is created by the MFS Language Utility via the PD statement and is referenced by the DPAGE statement PD operand. It contains all of the information necessary to issue the "CREATE PARTITION" Write Structured Field Command for the partition.
�partition descriptor block (PDB): A collection of partition descriptor entries representing a partition set. An intermediate text block (ITB) for the PDB is created by the MFS Language Utility. This PDB ITB is used in creating a part of the DOF.
�partition dump: An unformatted dump of the entire CICS partition. It is produced by CICS from within the partition without operating system assistance. See also dump.
�partitioned concatenation: The allocation of partitioned data sets (PDSs), partitioned data sets extended (PDSEs), UNIX file directories, or any combination of these such that the basic partitioned access method (BPAM) retrieves them as a single data set. See also data set concatenation.
�partitioned database environment: A database installation that supports distribution of the data across database partitions.
�partitioned data set (PDS): A data set on direct access storage that is divided into partitions, called members, each of which can contain a program, part of a program, or data. See also sequential data set, component PDSE.
�partitioned data set extended (PDSE): A system-managed data set that contains an indexed directory and members that are similar to the directory and members of partitioned data sets (PDSs). See also library.
�partitioned environment: See also serial database.
�partitioned HDAM (PHDAM): A partitioned Hierarchical Direct Access Method database organization, one type of High Availability Large Database (HALDB).
�partitioned HIDAM (PHIDAM): A partitioned Hierarchical Indexed Direct Access Method database organization, one type of High Availability Large Database.
�partitioned index: An index that is physically partitioned. Both partitioning indexes and secondary indexes can be partitioned.
�partitioned secondary index (PSINDEX): A partitioned secondary index database organization, one type of High Availability Large Database (HALDB).
�partitioned server: A single computer configured to run an unlimited number of instances of the Domino server program. Using partitioned servers reduces hardware expenses and minimizes server administration.
�partitioned table space: A table space that is subdivided into parts (based on index key range), each of which can be processed independently by utilities. See also table space, universal table space.
�partitioning: (1) The process of forming multiple physical partitions from one processor complex.; (2) Dividing the resources in a tape library (tape drives and tape volumes) among multiple systems, sysplexes, or both, for their exclusive use. Each partition can be viewed as a logical library with each logical library (TCDBplex) represented by one tape configuration database (TCDB).; (3) The division of a machine's computing resources into independent subsystems with processor, memory, and I/O resources dedicated to the exclusive use of a subsystem. This division allows multiple operating systems to run concurrently in the subsystems.
�partitioning agent: The process that distributes data to the database partitions. See also load agent, pre-partitioning agent.
�partitioning index: (1) An index in which the leftmost columns are the partitioning columns of the table. The index can be partitioned or nonpartitioned.; (2) In replication, an ordered set of one or more columns in a given table. For each row in the source table, the values in the partitioning key columns are used to determine in which target table the row belongs.
�partitioning key: See distribution key.
�partitioning map: See distribution map.
�partition set: (1) All of the partitions which are defined in the partition descriptor block.; (2) In BMS, a group of partitions designed to share the same screen. CICS must load the whole partition set onto a terminal before it can communicate with any of the partitions.
�partition specification table (PST): An IMS control block that contains information about a dependent region.
�partner: (1) In data communications, the remote application program or the remote computer.; (2) In distributed processing, any one of the separate communicating parts of an application. In CICS Transaction Server intercommunication, a transaction communicating with a remote transaction or system. A CICS program using the SAA communications interface requires a local PARTNER resource definition for its remote partner. An EXEC CICS INQUIRE|SET PARTNER command can query or change the status of a partner. In FEPI this is equivalent to back-end system.
�partner connection: An interaction that has been associated with specific sending and receiving partners, and also specifies the destinations and other routing information necessary for an exchange.
�partner group: In WebSphere Commerce, a designation for business partners that assigns them a set of entitlements and privileges. For example, a manufacturer can assign resellers a designation of Gold, Silver, or Bronze, based on their success in selling the product line, or their volume of sales.
�partner logical unit: (1) In SNA, the remote participant in a session.; (2) An access point in the SNA network that is connected to the local DB2 for z/OS subsystem by way of a VTAM conversation.
�partner profile: A profile that includes information about the partner such as its name, its business identifier, such as a DUNS number, and a list of user IDs authorized to access the Community Console. See also Data Universal Numbering System.
�partnership: In remote copy and Peer-to-Peer Remote Copy, the relationship between two clusters. In a partnership, one cluster is defined as the local cluster and the other cluster as the remote cluster.
�partner site: A Web site operated by a business partner, such as a distributor or a supplier.
�partner systems: In an IMS multisystem environment, two IMS online systems that are connected by an MSC link.
�partner table (PT): In MERVA Link, the table that defines how messages are processed. It consists of a header and different entries, such as entries to specify the message-processing parameters of an ASP or MTP.
�partner transaction program: The transaction program engaged in an APPC conversation with a local transaction program.
�part of speech (POS): A gloss representing a category of words which have a specific syntactic function, for example: a verb is a part of speech.
�part reference: An object that is used by a configuration to reference other related configuration objects.
�parts catalog: In VisualAge RPG, a collection of parts defined by the user. Parts in the catalog can be moved to and from the parts palette.
�parts palette: In VisualAge RPG, a collection of views and models used in building additional parts for an application. Application programmers can add parts to the palette for use in defining applications or other parts.
�party: In telephony, an addressable end point of a telephone call.
�PASA: See program automatic storage area.
�pass by reference: In programming languages, one of the basic argument passing semantics where the address of the object is passed. Any changes made by the callee to the argument value will be reflected in the calling routine at the time the change is made.
�pass by value: In programming languages, one of the basic argument-passing semantics in which the value of the object is passed. Any changes made by the callee to the argument value will not be reflected in the calling routine.
�passivation: In enterprise beans, the process of transferring an enterprise bean from memory to secondary storage. (Sun) See also activation.
�passive attack: In computer security, an assault on a network that is difficult to detect and involves an intruder who taps into or traces communications. Sniffing is an example of a passive attack.
�passive open: In TCP/IP, the state of a connection that is prepared to provide a service on demand. See also active open.
�pass through: To gain access to another network.
�pass-through mode: A mode through which SQL statements can be submitted directly to a data source.
�pass-through server: An intermediary server that lets a client access a target server to which the client is not connected. A mobile user can access multiple servers through a single phone connection; a LAN client can connect to servers running network protocols different from its own.
�pass-through session: A DB2 session used to submit SQL statements directly to a database management system (DBMS) using the SQL dialect associated with that data source.
�PassTicket: In RACF secured sign-on, a dynamically generated, random, one-time-use, password substitute that a workstation or other client can use to sign on to the host rather than sending a RACF password across the network.
�password: In computer and network security, a specific string of characters used by a program, computer operator, or user to access the system and the information stored within it.
�Password Authentication Protocol (PAP): A type of authentication where the user name and password are transmitted in an unencrypted form. This is a more basic form of authentication than Challenge Handshake Authentication Protocol (CHAP). See also Challenge Handshake Authentication Protocol.
�password level: Within DST, a property that specifies whether Data Encryption Standard (DES) or Secure Hash Algorithm (SHA) encryption is used when storing passwords. The default level is DES.
�password mask: A template for passwords that defines the placement of characters and character types that can used when creating and/or modifying a password.
�password phrase: A string consisting of mixed-case letters, numbers, and special characters, including blanks, that is used to control access to data and systems.
�password protection: In APPC, the support that uses protected passwords to keep user passwords secure. The LU type 6.2 architecture refers to password protection as password substitution.
�password security: The use of system definition macros and security maintenance utility control statements to restrict the use of IMS resources (databases, application programs, physical and logical terminals, transactions, and commands) to a person or persons who can supply the correct password.
�password server: A server that allows clients to change their password on the key distribution center (KDC) remotely. The password server typically runs on the same machine as the KDC.
�patch cable: A length of cable with data connectors at both ends; it is normally used to interconnect two sections of building cable at a distribution panel or to connect a product to the building cable.
�path: (1) In a network environment, the route between any two nodes.; (2) The route through a file system to a specific file.; (3) In OSI, a description of how a local line or line set can be used for outbound communications.; (4) In SNA, the set of data links, data link control layers, and path control layers that a path information unit travels through when sent from the transmission control layer of one half-session to the transmission control layer of another half-session.; (5) In VTAM, the intervening nodes and lines connected a terminal and an application program in the host processor.; (6) In VSAM, a named logical entity that is composed of one or more clusters and provides access to the records of a base cluster either directly or through an alternate index.; (7) In DL/I, the chain of segments within a record that leads to the currently-retrieved segment. The formal path contains only one segment occurrence from each level, from the root down to the segment for which the path exists.; (8) A route that the flow can take through the activities in a process. There may be several alternative paths.
�path assignment: In OSI, the permanent assignment of a DTE at an adjacent node to a path. This restricts the path to particular lines to be used for connections to or through that adjacent node.
�path call: A type of DL/I call that enables a hierarchical path of segments to be inserted or retrieved with one call.
�path code page: A list of the path name components of the files that are exported to and mounted on a specified Network File System (NFS) client or netgroup.
�path control layer: In SNA, the layer that routes all messages to data links and half-sessions.
�path control network: In SNA, the functional layer that includes the data link control and path control layers.
�path cost: In link-state routing protocols, the sum of the link costs along the path between two nodes or networks.
�path entry: A catalog entry that contains information about a Virtual Storage Access Method (VSAM) path and that points to the path's related objects.
�path expression: An XQuery expression that navigates through a node hierarchy by a series of steps to select nodes for further processing. See also node test, step.
�path group: (1) A collection of equivalent paths. Storage devices may have one - n path groups.; (2) In ESA/390 architecture, a set of channel paths that are defined to a control unit as being associated with a single logical partition (LPAR). The channel paths are in a group state and are online with the host. See also logical partition.
�path group identifier: The ESA/390 term for the identifier that uniquely identifies a given logical partition (LPAR). The path-group identifier is used in communication between the LPAR program and a device. It associates the path-group identifier with one or more channel paths, thereby defining these paths to the control unit as being associated with the same LPAR.
�path information unit (PIU): (1) In SNA, the smallest amount of data that the system sends out on a communications line, consisting of a transmission header followed by a basic information unit or a basic information unit segment.; (2) In VTAM, data sent by the host according to the definition of the VPACING parameter that determines how many messages can be sent in a session to the VTAM application by another VTAM logical unit without requiring that an acknowledgment be sent.
�pathlength: The number of instructions executed for a particular function.
�path manager: A function that controls network job entry (NJE) sign-on and sign-off, monitors all other nodes and connections in the network, and determines the best path to reach those nodes.
�path name: (1) A name that specifies all directories leading to a file plus the file name itself.; (2) The name of an object in the integrated file system. Protected objects have one or more path names.
�path name resolution: The process of resolving a path name to a particular file in a file hierarchy. There may be multiple path names that resolve to the same file. X/Open.
�path prefix: A path name, with an optional ending slash, that refers to a directory.
�path qualified mapping: A form of mapping in which all occurrences of a repeating compound or simple element are mapped to the same repeating compound or simple element in another document.
�path selection: The selection of a transmission path through a fabric. Switches use the fibre-channel shortest path first (FSPF) protocol.
�path set: In OSI, a set of paths grouped by the similarity of their requirements. OSI Communications Subsystem requires that each line be assigned to a line set. If the line is to be used for outbound communications, then its associated line set must be assigned to a path set. A line that is not assigned to a path set (through a line set) can be used only for inbound communications.
�path set sequencing: In OSI, the process of defining the sequence in which lines are to be selected for outbound connections.
�path test: A test that enables a network operator to determine whether a path is available between two logical units (LUs) that are currently in session.
�pattern: (1) In REXX, the parts of a parsing template that allow a string to be split by literal pattern or positional pattern. Parentheses may be supplied to create a variable pattern.; (2) A sequence of characters used either with regular expression notation or for path name expansion, as a means of selecting various characters strings or path names, respectively. The syntaxes of the two patterns are similar, but not identical.; (3) A reusable description of the design and architecture, which is used to satisfy defined criteria.
�pattern language: A collection of interrelated patterns that combine to solve a problem and that, together, may be viewed as a single pattern. Specifically these contained patterns are templates, each of which share some of the same context as defined by the pattern language.
�pattern matching: The specification of a pattern of characters for search purposes.
�pattern-matching character: See wildcard character.
�pattern storage (PST): In PSF, an area of storage that holds the raster patterns for fonts and images.
�pattern system: An abstract class in the content meta-model, which is a special kind of pattern that contains other reusable solutions. It is through the aggregation relationship between the pattern system and the pattern that the meta-model supports granularity, abstraction and scaling of asset size and complexity. A pattern system is a solution to a recurring problem in a given context that can contain other such solutions.
�paused: Pertaining to the state produced when the cache component quiesces all ongoing I/O activity below the cache layer.
�paused mode: The mode of operation in which all host commands that require movement of cartridges are queued until the library is returned to automated mode. Paused mode allows the operator to enter the enclosure area while the robot is not operating to correct a problem, add cartridges to the bulk input station, or remove cartridges from the bulk output station.
�PAV: See parallel access volume.
�pawl: (1) A pivoted tongue or sliding bolt adapted to fall into notches on a machine to permit motion in only one direction.; (2) The tongue of a ratchet.
�payload: The body of the message that holds the content.
�payment: (1) A transfer of funds (credit or debit) between banks.; (2) In WebSphere Commerce Payments, a merchant's request of a financial institution to approve all or part of an order. In many cases, all the money authorized for collection by an order will be collected in a single payment. Some payment systems allow the money authorized in one order (that is, one set of payment instructions) to be collected in multiple payments, depending on the business model.
�payment action: In WebSphere Commerce, a financial operation that is associated with a payment instruction. For example, approve (authorize), reverse approval, deposit (capture), reverse deposit, refund, and validate are payment actions.
�payment action rule: See payment rule.
�payment back-end system: The payment service provider, payment processor, or proxy for an external payment system.
�payment card: In e-commerce, a credit card, debit card, or charge card (a) that is issued by a financial institution and shows a relationship between the cardholder and the financial institution, and (b) for which a certificate can be issued from an authenticated certificate authority.
�payment cassette: A cassette that implements an electronic payment protocol.
�payment instruction: In WebSphere Commerce, the instance of a payment method with the details necessary to perform payment actions. For example, if a payment method name is CardBrandX, then the payment instruction consists of CardBrandX, plus the cardholder name, billing address, account number, and expiration date.
�payment method: The means by which payments are made for an order. For example, payment methods may include various brands of credit cards, electronic checks, lines of credit, and gift certificates.
�payment plug-in: A self-contained software component that serves as a proxy for a payment back-end system. Payment plug-ins are responsible for payment protocol and protocol data validation.
�Payment Plug-in Controller: In WebSphere Commerce, the software layer that coordinates and delegates payment requests to the payment plug-ins. The Payment Plug-in Controller interacts with WebSphere Commerce Payments through the WCPayments plug-in.
�payment protocol: In WebSphere Commerce, the conventions that govern the exchange of data between payment cassettes or plug-ins and the backend financial systems (payment service provider or payment processor). For example, VisaNet and Paymentech have different payment protocols.
�payment rule: In WebSphere Commerce, a set of configurable parameters that define payment actions to be executed by the event-driven payments subcomponent during business events.
�payment server: In e-commerce, the electronic equivalent of a cash register that organizes and accepts payment for the goods and services selected for purchase. A payment server uses other components, such as a payment gateway and a payment management system, to complete the financial transactions.
�payment subsystem: In WebSphere Commerce, the software that handles payment processing.
�payment system: See clearing channel.
�Pb: See petabit.
�PB: See petabyte.
�PBUF: See protected buffer pool.
�PBX: See private branch exchange.
�PCA: See page control area.
�p-card: See purchasing card.
�PCAST: A proprietary transfer protocol that delivers non-identical sets of files to several client computers using multicast. See also MCAST.
�PCB: (1) See program communication block.; (2) See promotion control block.
�PCB mask: A data structure in an application program in which IMS puts the status of the application program's DL/I calls. See also status code.
�PCC: See power control compartment.
�PC double-byte encoding scheme: See IBM PC double-byte encoding scheme.
�PCF: See programmable command format.
�PC file: A file stored on a personal computer.
�PCHID: See physical channel ID.
�PCI: See Peripheral Component Interconnect.
�PCI bridge: A device that connects one or more subordinate PCI buses to a primary PCI bus. The PCI bus that is closest to the system processor is the primary PCI bus, and the subordinate buses are secondary PCI buses.
�PCI bridge set: A set of PCI card positions.
�PCID: See procedure correlation identifier.
�PCI host bridge (PHB): A device that merges data from PCI bridges for delivery to the system processor.
�PCI-X: See Peripheral Component Interconnect-X.
�PC/IXF: A file format that is an adaptation of the Integration Exchange Format (IXF), which was specifically designed to enable the exchange of relational database structures and data. The PC/IXF file architecture maintains the independence of both the exporting and the importing database systems.
�PCL: See printer control language.
�PCMCIA: See Personal Computer Memory Card International Association.
�PCM fault condition: A fault, such as power supply failure, or loss of incoming signal, in T1 or E1 equipment. (ITU-T G.732 and G.733.)
�PC-mixed character set: A character set that contains a mixture of single-byte character set (SBCS) PC code pages and double-byte character set (DBCS) PC code pages.
�PCML: See Program Call Markup Language.
�PCO: See point of control and observation.
�PCP: See program control program.
�PCR: See peak cell rate.
�PCS: (1) See personal communication system.; (2) In architecture, a measurement of the ratio of the reflectivities between the bars and spaces of a bar code symbol, commonly expressed as a percent.
�PC session: An operating session that uses DOS and other IBM programs on a personal computer attached as a 5250 work station to a server.
�PC single-byte encoding scheme: See IBM PC single-byte encoding scheme.
�PCT: See program control table.
�PD: See partition descriptor.
�PDA: See personal digital assistant.
�PDB: See partition descriptor block.
�PDC: See personal digital cellular.
�PDE: See possible duplicate emission.
�PDF: (1) See Portable Document Format.; (2) See Program Development Facility.
�PDF subsystem: The IPDS to PDF Transform function of IBM Infoprint Server for iSeries. One or more PDF files are generated from an Intelligent Printer Data Stream (IPDS), Advanced Function Presentation (AFP), or SNA character string (SCS) spooled file and then sent as e-mail, spooled for printing, or stored in the integrated file system as a stream file. A mapping program can be used to implement intelligent routing of the PDF subsystem output. See also intelligent routing, mapping program, mapping object.
�PDI: See primary delay interval.
�PDIR: See PSB directory.
�PDM: See Programming Development Manager.
�PDML: See Panel Definition Markup Language.
�PDN: See public data network.
�PDR: See preliminary design review.
�PDS: See partitioned data set.
�PDS directory: A set of records in a partitioned data set (PDS) that is used to relate member names to their locations within the data set.
�PDSE: See partitioned data set extended.
�PDU: See protocol data unit.
�PDV: See presentation data value.
�PDV report: In OSI, an output file produced by the Abstract Syntax Checker that shows the names of the PDVs in the input module and the data structures that comprise them.
�PE: See IBM product engineering.
�peak cell rate (PCR): The maximum rate at which an asynchronous transfer mode (ATM) endsystem can transmit cells into the network over the user-to-network interface (UNI).
�peak rate: The maximum rate encountered over a given period of time.
�peer: A general term for the corresponding node or entity with which one communicates.
�peer access point: A means by which core groups can communicate with other cells.
�peer application entity: In OSI, the corresponding application entity with which a local application entity communicates.
�peer domain: A type of cluster domain that consists of two or more peer cluster domain nodes organized in such a way as to have one online (master) node, and one or more online or offline (standby) nodes. In a failover scenario, the peer domain cluster redistributes the workload from the failed master node to a standby node, to increase the availability. See also cluster domain node.
�peer entity: In OSI, an entity within the same layer.
�peer requirement: A requirement that is at the same hierarchical level as another requirement. Two requirements are peer requirements when they are children of the same parent. All requirements at the root level are peer requirements of one another.
�peer state: In high availability disaster recovery, the state during which the primary database ships new log pages from its in-memory log buffer to the standby database when the same log pages are written to the log disk of the primary database. See also asynchronous mode, remote catchup state, near synchronous mode.
�peer-to-peer: Pertaining to a form of distributed processing, in which the front-end and back-end of a conversation switch control between themselves. It is communication between equals.
�Peer-to-Peer Remote Copy (PPRC): A remote-copy service that provides a synchronous copy of a volume or disk for disaster recovery, device migration, and workload migration. See also remote copy, synchronous PPRC, PPRC Extended Distance.
�peer-to-peer replication: A replication configuration between logical tables in which updates to any table are replicated to the other tables and convergence is maintained. Peer-to-peer replication can involve two or more servers. See also multi-tier replication, update-anywhere replication.
�Peer-to-Peer Virtual Tape Server (PtP VTS): A virtual tape server (VTS) configuration in which copies of data in newly created or updated tape volumes are automatically created or updated in each of two interconnected VTSs. This dual-volume copy functionality improves data availability and data recovery, while being transparent to user applications and host processor resources.
�Peer-to-Peer VTS data (PtP DATA): A function that allows an installation or application to obtain operational mode settings and device-related information from the Peer-to-Peer Virtual Tape Server (PtP VTS) library.
�Peer-to-Peer VTS mode control (PtP MC): The function that allows an installation or application to change current operating modes of the library.
�Pegasus: An open source implementation of CIMOM that is maintained by the Open Group.
�pel: See picture element.
�PEM requester: Any APPC device or node capable of initiating a conversation with the architected signon transaction.
�PEM server: Any APPC LU that supports the receive side of APPC PEM; that is, it can attach, but not initiate, the signon transaction.
�pend: A state between online and offline in which an object is making a transition from online to offline or from offline to online. The pend state is initiated when a pend event is sent by an online object or when an add event is sent by an offline object. See also un-pend.
�pending: (1) Pertaining to a submitted request that is awaiting processing.; (2) The initial state of a defined volume pair before it becomes a duplex pair. During this state, the contents of the primary volume are copied to the secondary volume.
�pending event: An unscheduled event that occurs as a result of a connect request from a CICS adapter.
�pending page queue (PPQ): A list of pages that has been processed by PSF but has not been released from JES or stacked by the printer.
�pending requirement: A newly created requirement in a document or a view that has not yet been saved in the database.
�pending tag number: A tag number for a newly created requirement in a document. See also requirement tag.
�people assignment criterion: A property that defines the members of each of the role groups.
�people awareness: The collaboration feature that provides access to people from various contexts. People awareness lets you see references to people and contact people by name through the Sametime online status indicator. Throughout the portal, wherever you see the name of a person, you can view the person's online status, send e-mail, initiate a chat, or share an application via an electronic meeting. See also person link.
�PEP: (1) See program entry procedure.; (2) See program error program.
�percolate: To decline to handle an exception. The unchanged exception is passed on to the next exception handler.
�percolation: In error recovery, the passing along a preestablished path of control from a recovery routine to a higher-level recovery routine.
�performance: A measure of a system's ability to perform its functions, including response time, throughput, and number of transactions per second.
�performance analysis: The use of one or more performance tools to investigate the reasons for performance improvement or deterioration.
�performance class: A description of an objective or commitment of performance. It consists of a performance class name, boundary definitions, response time definition, response time ranges, and response time percentage objectives. Sessions can be assigned performance classes.
�performance class data: Detailed transaction-level monitoring data, which includes; Task identification information, resource request counts, CPU and dispatch times, and time spent waiting for I/O. Monitoring of performance (that is, the collection of performance class data) is activated by the MNPER system initialization parameter in CICS Transaction Server or by the MONITOR system initialization parameter in CICS/VSE. See also monitoring record.
�performance data: Information about the operation of a system or a network of systems that can be used to understand response times and throughputs and to predict the effects of certain system operational changes or programming changes.
�performance data section: One of the CICS data sections in a CICS monitoring record. It consists of a string of field connectors followed by one or more performance data records.
�performance evaluation: The determination of how well a specific system is meeting or may be expected to meet specific processing requirements at specific interfaces. Performance evaluation, by determining such factors as throughput rate, turnaround time, and constrained resources, can provide important inputs and data for the performance improvement process.
�performance event: A category of event indicating that a limit condition has occurred.
�performance group: A group of file systems sharing system resources that can affect file system performance.
�performance improvement: The increase of the average throughput rate and operational capability, or the reduction of turnaround time.
�performance management: The discipline that encompasses capacity planning, collecting performance data, and tuning resources.
�Performance Management Agent (PM Agent): A function of the operating system that takes data collected by Collection Services, reduces the data, and sends that data to IBM for analysis. This was formerly called Performance Management for eServer iSeries.
�Performance Management for System i5 (PM for System i5): An IBM offering that takes customer system data and sends that data to IBM for analysis. IBM then returns capacity planning and performance analysis reports and graphs.
�Performance Monitoring: A feature that provides error and performance information to the administrator and end user for use in storage management.
�Performance Monitoring Infrastructure (PMI): A set of packages and libraries assigned to gather, deliver, process, and display performance data.
�performance monitor interface (PMI): In VTAM, an interface that enables the collection of information about VTAM's performance and resource utilization, which, in turn, allows for an early diagnosis of problems and more efficient tuning and debugging of VTAM.
�performance snapshot: Performance data for a set of database objects that is retrieved from the database manager at a point in time. See also explain snapshot.
�performance threshold: The established response time for transactions. See also threshold.
�Performance Tools for i5/OS: The IBM licensed program that allows a user to display, report, graph, and analyze performance data.
�performance trace: A WebSphere MQ trace option where the trace data is to be used for performance analysis and tuning.
�performance variable: A statistic derived from performance data obtained from the database manager. The expression for this variable can be defined by the user.
�per-hop behavior: A description of an external and observable forwarding treatment. Routers use the per-hop behavior code points to give network traffic a certain priority. A per-hop behavior is applied to each Internet Protocol (IP) packet when differentiated services is designated. The six bits of the differentiated services code-point field designate the per-hop behavior.
�period: (1) A component of a schedule that divides the timeline into named intervals, such as peak, off-peak, and no service.; (2) The symbol ".". The term dot is used for the same symbol when referring to a Web address or file extension. This character is named <period> in the portable character set. See also dot.
�Peripheral Component Interconnect (PCI): A local bus that provides a high-speed data path between the processor and attached devices. See also Peripheral Component Interconnect-X.
�Peripheral Component Interconnect-X (PCI-X): An enhancement to the Peripheral Component Interconnect (PCI) architecture. PCI-X enhances the Peripheral Component Interconnect (PCI) standard by doubling the throughput capability and providing additional adapter-performance options while maintaining backward compatibility with PCI adapters. See also Peripheral Component Interconnect.
�Perl: A scripting language that was originally designed as a tool for writing programs in the UNIX environment but has evolved to include the power and flexibility of a high-level programming language such as C. Perl is an open-source language.
�permanent data set: A user-named data set that is normally retained for a longer period than the duration of a job or interactive session. See also temporary data set.
�permanent dynamic queue: A dynamic queue that is deleted when it is closed only if deletion is explicitly requested. Permanent dynamic queues are recovered if the queue manager fails, so they can contain persistent messages. See also temporary dynamic queue.
�permanent error: An error--for example, a hardware component failure--that can be corrected only by external intervention. See also transient error.
�permanent event: In OSI, an event that indicates the occurrence of an irrecoverable error--one that makes a resource unavailable or causes OSI Communications Subsystem to stop. Permanent events are logged and generate a message to the operator. See also transient event.
�permanently maintained path: In OSI, a CLNS path to an adjacent node that is maintained until OSI Communications Subsystem is restarted.
�permanent object: An object, such as a database files or program, that stays in the system until a user with the required authority deletes it.
�permanent pen: An editing feature in Notes documents that allows users to edit documents in a second font.
�permanent storage: (1) A storage device whose contents cannot be modified.; (2) The database where all tables and QMF objects are stored.
�permanent table space: A table space that can store any persistent data. See also regular table space, large table space.
�permanent virtual circuit (PVC): A virtual circuit that has a logical channel permanently assigned to it at each data terminal equipment (DTE). A call establishment protocol is not required. The permanent virtual circuit establishes the identity of the called party within the network services contract.
�permission: (1) The ability to access a protected object, such as a file or directory. The number and meaning of permissions for an object are defined by the access control list.; (2) The authority granted to users to give them access to an application's features and functions.; (3) Authorization to perform activities, such as reading and writing local files, creating network connections, and loading native code.; (4) An entitlement or privilege that governs how a user interacts with the repository, specified by role, not the individual user.
�permission code: A 3-digit octal code or a nine-letter alphabetic code that indicates the access permission for a UNIX file. The access permissions are read, write, and execute.
�permission field: One of the 3-character fields within the permissions column of a UNIX directory listing. The permission field indicates the read, write, and run permissions for the file or directory owner and for the group. It is used by file systems to control access.
�permission group: A set of access permissions applicable within a specific access group.
�perpetual echo: A denial-of-service attack on the UDP echo port 7. If the source port and target port are set to port 7, the request is echoed back and forth.
�persist: To be maintained across session boundaries, usually in nonvolatile storage such as a database system or a directory.
�persistence: (1) A characteristic of data that is maintained across session boundaries, or of an object that continues to exist after the execution of the program or process that created it, usually in nonvolatile storage such as a database system.; (2) In Java EE, the protocol for transferring the state of an entity bean between its instance variables and an underlying database. (Sun)
�persistent: Pertaining to data that is maintained across session boundaries, usually in nonvolatile storage such as a database system or a directory.
�persistent command text: The command text that is saved when a started task is begun and that is used to restart the job through automatic restart management.
�persistent data store: A nonvolatile storage for event data, such as a database system, that is maintained across session boundaries and that continues to exist after the execution of the program or process that created it.
�persistent environment: An environment that once created by the user may be used repeatedly without incurring the overhead of initialization and termination for each call. The environment remains available until explicitly terminated by the user.
�persistent identifier (PID): An identifier that uniquely identifies an object, regardless of where it is stored. The PID consists of both an item ID and a location.
�persistent JCL: A set of saved job control statements that was used for the original job. The persistent JCL can be used again if the job is restarted.
�persistent message: A message that survives a restart of the queue manager. See also nonpersistent message.
�persistent object: (1) An object whose state can be preserved beyond the ending of the process that created it. Typically, persistent objects are stored in files.; (2) An object that exists after the process or thread that created it has ceased to exist.
�persistent session: (1) A session that remains active even though there is no activity on the session for a specified period of time.; (2) An LU-LU session that VTAM retains after the failure of a VTAM application program. Following the application program's recovery, the application program restores or terminates the session.
�persistent verification (PV): The retention of a sign-on from a remote system across multiple conversations until it is no longer needed. In CICS Transaction Server, the PVDELAY system initialization parameter defines how long entries can remain in the signed-on-from list relating to a connection for which persistent verification is specified.
�person: An individual authenticated by the portal and having a person record in one or more corporate directories. Persons can be members of places, public groups within the organization's corporate directory, or personal groups that a user defines. See also personal group, public group.
�personal area network (PAN): Experimental IBM technology that allows information devices to communicate discreetly and synchronize with one another when in close proximity, using the human body as an antenna.
�personal communication system (PCS): A Federal Communications Commission classification for digital wireless communication systems based on the same principles as cellular systems, but usually operating in a different frequency range and with smaller cell sizes than cellular systems.
�Personal Computer Memory Card International Association (PCMCIA): An international standards body and trade association founded in 1989 to establish a standard for connecting peripherals to portable computers.
�personal digital assistant (PDA): A handheld device that is used for personal organization tasks (such as calendaring, note-taking, and recording telephone and fax numbers), and networking functions such as e-mail and synchronization.
�personal digital cellular (PDC): Technology used in digital cellular telephone communication in Japan.
�personal greeting: In voice mail, a greeting recorded by a subscriber. See also system greeting.
�personal group: In Sametime Connect, a group of people designated by the user as a group. A user can choose individuals from the public Directory (public group) and create personal groups, which are then stored locally. Users can add and remove people from a personal group, whereas the membership of the public group is defined by the owner of the public Directory. See also public group.
�Personal Handy Phone System (PHS): Personal communications system used in Japan as both a digital cordless phone in homes and offices and as a cellular phone outdoors.
�personal identification number (PIN): In Cryptographic Support, a unique number assigned by an organization to an individual and used as proof of identity. PINs are commonly assigned by financial institutions to their customers.
�personalization: The process of enabling information to be targeted to specific users based on business rules and user profile information. See also customization.
�personalization engine: An application that can generate product recommendations and special offers to customers based on information collected during visits to e-commerce sites.
�personalized attributes: In the RFQ trading mechanism, a list of attributes created by a selling organization that a buyer must use when sending an RFQ to that organization. In addition to the predefined attributes provided by the seller, buyers can specify unique attributes in designated attribute fields.
�personally identifiable information (PII): In a privacy management environment, data elements that are associated with a specific individual and that can be accessed and used in such a way that the identity of the individual who submitted the PII is known. PII can be a single point of data, such as political party affiliation, or several points of data that are combined, such as names, e-mail addresses, and phone numbers. To maintain their privacy, individuals who submit PII to an organization want to limit the propagation of that PII to other individuals within the organization or to other organizations. Some PII data might be privacy-sensitive. The use of privacy-sensitive PII might be governed by privacy legislation or an organization's privacy policy. See also PII owner, privacy-sensitive information.
�personal settings: A choice that allows a user to display or change the characteristics or properties of an object. For example, a user can customize the interface by specifying how the menu bar, status area, and information area are displayed.
�person link: A reference to a person's name or a group name that appears with the Sametime online status indicator. The reference lets you view the person's online status, send an e-mail, start a chat, or share an application using an electronic meeting, among other actions shown on the person link menu. See also people awareness.
�perspective: A group of views that show various aspects of the resources in the workbench.
�pervasive computing: The use of a computing infrastructure that supports information appliances from which users can access a broad range of network-based services, including Internet-based e-commerce services.
�pervasive device: A generally small and often wireless device that allows users to access information on demand from many locations. Mobile pervasive devices include personal digital assistants, smartcards, digital wireless telephones, handheld computers, and digital watches. Fixed devices such as point of sale terminals, bank machines, home entertainment centers, and airport check-in terminals can also be considered pervasive devices when they can be used to deliver a range of network-based information.
�pessimistic locking: A locking strategy whereby a lock is held between the time that a row is selected and the time that a searched update or delete operation is attempted on that row. See also optimistic locking.
�petabit (Pb): A measure of data traffic that is one quadrillion (10 to the 15th power) binary digits or one thousand terabits.
�petabyte (PB): (1) A measure of memory or storage capacity that is 2 to the 50th power bytes or approximately a thousand terabytes.; (2) For disk storage capacity and communications volume, 1 000 000 000 000 000 bytes.
�PFA: See Predictive Failure Analysis.
�PFD: See printout format definition.
�PFK (PF key): See program function key.
�PF key (PFK): See program function key.
�PFS: See physical file system.
�PFU: See print format utility.
�PGID: See process group ID.
�PGP: See Pretty Good Privacy.
�PGR: See presentation graphics routines.
�phantom address (phantom AL_PA): An arbitrated loop physical address (AL_PA) value that is assigned to a device that is not physically in the loop.
�phantom AL_PA: See phantom address.
�phantom device: A device that is not physically in an arbitrated loop but is logically included through the use of a phantom address.
�phantom row: A table row that can be read by application processes that are executing with any isolation level except repeatable read. When an application process issues the same query multiple times within a single unit of work, additional rows can appear between queries because of the data being inserted and committed by application processes that are running concurrently.
�phase: A distinct part of a process in which related operations are performed.
�phase alternation line (PAL): The television broadcast standard for European video outside of France and the countries of the former Soviet Union. See also National Television Standard Committee.
�phase encoding: A magnetic recording method in which each storage cell is divided into two regions that are magnetized in opposite directions; the sequence of the magnetic direction indicates whether the binary character represented is 0 or 1.
�Phase II negotiation: A negotiation that establishes Security Associations (SAs) that protect your data exchanges. A Phase II negotiation is governed by data policies.
�Phase I negotiation: A negotiation that establishes the protection suite for the Internet Key Exchange (IKE) messages themselves. A Phase I negotiation determines how to protect a Phase II negotiation. A Phase I negotiation is governed by key policies.
�PHB: See PCI host bridge.
�PHDAM: See partitioned HDAM.
�PHIDAM: See partitioned HIDAM.
�phone recognition: Communicating with a computer using voice using a telephone, over a telephone line. The computer application recognizes what is said and takes appropriate action.
�phonetic: Relating to spoken language or speech sounds.
�phonetic spelling (phs): A transcription that shows the pronunciation of words.
�phonological contraction: A form of compounding where a number of elements are pronounced as one, for example: 'wanna' is a phonological contraction of 'want to'.
�PHP Hypertext Preprocessor: A widely-used general-purpose scripting language that is especially suited for Web development and can be embedded into HTML.

�phrase: (1) One or more words that together form a unit that is to be searched for in the content of a document.; (2) An ordered set of one or more consecutive COBOL character strings that forms part of a clause or a Procedure Division statement.
�PHS: See Personal Handy Phone System.
�phs: See phonetic spelling.
�physical architecture: The embodiment of the physical arrangement of nodes in a system, the artifacts that are stored on each node, and the components and other elements that the artifacts implement. Nodes represent hardware devices such as computers, sensors, and printers, as well as other devices that support the runtime environment of a system. Communication paths and deploy relationships model the connections in the system.
�physical channel ID (PCHID): A number assigned by a machine to a physical channel location.
�physical child: In a database, a segment type that is dependent on a segment type defined at the next higher level in the database hierarchy. All segment types in a database, except the root, are physical children since each is dependent on at least the root.
�physical circuit: A circuit established without multiplexing. See also virtual circuit.
�physical connection: A connection that establishes an electrical circuit.
�physical consistency: The state of a page that is not in a partially changed state.
�physical database: An ordered set of physical database records. See also logical database.
�physical database record: In databases, a physical set of hierarchically related segments of one or more segment types. See also database record.
�physical database record occurrence: An instance of a root segment and the hierarchical arrangement of all its dependent segment occurrences.
�physical data block: A string of data elements or a group of records that is received, recorded, processed, or transmitted as a unit.
�physical data model: In DB2 data warehousing, a metadata model that represents the tables and other objects in a database.
�physical data structure: A hierarchy representing segment types and the hierarchic arrangement of those segment types in a physical database.
�physical device: An I/O device that is assigned to a logical partition and that is used directly.
�physical disk I/O: In Performance Tools, a disk operation for reading or writing data.
�physical file: A database file that describes how data is to be presented or received from a program and how data is actually stored in the database. A physical file contains one record format and one or more members. See also logical file.
�physical file member: A named subset of the data records in a physical file.
�physical file system (PFS): The part of the operating system that handles the actual storage and manipulation of data on a storage medium.
�physical format: The physical representation of a message within the bit stream. The supported physical formats are Custom Wire Format, XML Wire Format, and Tagged/Delimited String Format.
�physical interface: A device for a given system, such as an I/O adapter for a token-ring network or an Ethernet network, that provides the physical connection to a network.
�physical layer: The OSI layer that provides the mechanical, electrical, functional, and procedural means to start, maintain, and deactivate physical connections for transmissions between data-link entities.
�physical level: In X.25, a standard that defines the electrical, physical, functional, and procedural methods used to control the physical connection between the data terminal equipment (DTE) and the data circuit-terminating equipment (DCE).
�physical library: In relationship to a virtual tape server (VTS), a hardware enclosure consisting of one or more VTS libraries with each VTS being identified to the host as a separate library. Restrictions by the library manager may be set on an individual library basis or on a physical library basis, as is the case with import.
�physical link: The actual hardware connection between two systems. See also logical link.
�physical lock (P-lock): A type of lock that DB2 acquires to provide consistency of data that is cached in different DB2 subsystems. Physical locks are used only in data sharing environments. See also logical lock.
�physical logging: The process of writing log records from the log buffers to the system log. See also logical logging.
�physically complete: The state in which the concurrent copy process is completed and the output data set has been created.
�physically partitioned mode: The state of a processor complex when its hardware resources are divided into multiple configurations.
�physical map: A set of instructions telling BMS how to format a display for a given device. BMS does this by imbedding control characters in the data stream.
�physical medium: A physical entity on which information is presented; for example, a sheet of paper, a roll of paper, microfilm, an envelope, label, or display screen.
�physical network: A network of machines linked by physical network cabling, modems, or other hardware. A physical network can contain one or several logical networks.
�physical occupancy: The occupancy of physical files in a storage pool. This space includes the unused space created when logical files are deleted from aggregate files. See also logical occupancy.
�physical page: (1) In COBOL, a device-dependent concept defined by the action taken by a printer when a new page is requested.; (2) In MFS, all or part of a logical page that is defined to be entered (input) or displayed (output) at one time. See also logical page.; (3) In printing, a single surface (front or back) of a form.
�physical paging: An MFS facility that permits data from a logical page to be displayed in several physical pages on the device.
�physical parent: In a database, a segment type thathas a dependent segment type defined at the next lower level in the physical database hierarchy.
�physical partition: (1) Part of a central processing complex (CPC) that operates as a CPC in its own right, with its own copy of the operating system.; (2) A set of hardware resources, formed by partitioning, that can support a single operating system.
�physical path: A single path through the I/O interconnection fabric that attaches two units. For Copy Services, this is the path from a host adapter on one ESS (through cabling and switches) to a host adapter on another ESS.
�physical platform: An IBM Director managed object that represents a single physical chassis or server that has been discovered through the use of the Service Location Protocol (SLP).
�physical recovery: Restoring a facility to its status at the time of failure.
�physical relationship: In a database, the description of the relationship that exists between two or more physical segments.
�physical resource: In OSI, any resource of a computer available to do work, such as the processor, main storage, or a line. See also logical resource.
�physical segment: In a database, the smallest unit of accessible data.
�physical sequential: See sequential data set.
�physical services header (PSH): An X.25 protocol used by IBM Systems Network Architecture (SNA) data terminal equipment (DTE). Physical services header provides address services for physically connected systems or devices. The System i family does not support PSH. See also enhanced logical link control, Qualified Logical Link Control.
�physical stacked volume: See also container.
�physical storage: With respect to data, the actual space on a storage device that is to contain data. See also logical storage.
�physical terminal (PTERM): A hardware device attached to the computer and supported by the DC feature as a terminal. A physical terminal usually has one or more logical terminals associated with it.
�physical topology view: A view of a topology that shows a tree structure in terms of the machines in the topology, the facilities installed on those machines, and their base products.
�physical twins: In a database, all occurrences of a single physical child segment type that have the same (single occurrence) physical parent segment type. See also logical twins, twin segments.
�physical unit (PU): In SNA, one of three types of network addressable units (NAUs). A PU exists in each node of an SNA network to manage and monitor, at the request of a system services control point logical unit (SSCP-LU) session, the resources (such as attached links and adjacent link stations) of a node. See also control point.
�physical unit type (PU type): In SNA, the classification of a physical unit according to the type of node in which it resides. The physical unit type is the same as its node type; that is, a type 1 physical unit resides in a type 1 node, and so on.
�physical volume: A volume that has a one-to-one association with physical tape media and is used directly by z/OS applications. Physical volumes may reside in an Automated Tape Library Dataserver (ATLDS) or be kept on shelf storage either at vault sites or within the data center where they can be mounted on stand-alone tape drives.
�physical volume pool: A set of stacked volumes on a virtual tape server (VTS) that groups physical volumes with common characteristics.
�physical volume status: A relationship between a volume and the storage management subsystem (SMS) that indicates whether a volume is managed by SMS, whether all of its data sets have an associated storage class, and whether all of its data sets are cataloged in an integrated catalog facility (ICF) catalog. A volume can be in one of three states: fully converted, partially converted, or unconverted. See also volume status.
�PI: See program isolation.
�pica: A unit of about 1/6 inch used in measuring typographical material.
�pick batch: A group of releases that are managed as a unit in a fulfillment center.
�pick packer: A defined role in WebSphere Commerce that picks products from fulfillment centers and packs the products for shipping to customers. The pick packer also manages pick tickets and packing slips which are used to confirm shipment of products during order fulfillment. See also logistics manager.
�pick ticket: A printed document containing a list of all the products required to fulfill the releases in a given pick batch. This document is used by pickers to gather the products that must be packaged and shipped for all of the releases included in the pick batch.
�PICS: See Platform for Internet Content Selection.
�picture element (pel, pixel): (1) An element of a raster pattern about which a toned area on a photoconductor can appear.; (2) The smallest printable or displayable unit that can be displayed. A common measurement of device resolution is picture elements per inch.
�picture interchange format (PIF): The file format used to exchange picture files between graphics programs. A PIF file contains the drawing orders that define a picture.
�picture space: In the GDDM function, the area of the page that contains the graphics.
�picture string: A character string used to specify the date and time.
�PID: (1) See process identification number.; (2) See process ID.; (3) See persistent identifier.
�PIDU: See Printer Inventory Definition Utility.
�piece: A data set of a nonpartitioned page set.
�PIF: See picture interchange format.
�PII: (1) See program integrated information.; (2) See personally identifiable information.
�PII owner: In a privacy management environment, an individual with whom privacy-sensitive information is associated. As the owner of PII, the individual might have the legal right to limit the propagation of the privacy-sensitive information within the organization or to other organizations and individuals. See also personally identifiable information, PII user.
�PII user: In a privacy management environment, an individual or organization, or an agent acting on behalf of an individual or organization, that collects privacy-sensitive information from a PII owner and then uses that information in accordance with the privacy policies. See also PII owner.
�PIN: See personal identification number.
�pin: Part of an electrical connection.
�PIN check length: In Cryptographic Support, the number of digits from the personal identification number that are verified.
�ping: The command that sends an Internet Control Message Protocol (ICMP) echo-request packet to a gateway, router, or host with the expectation of receiving a reply.
�ping-of-death attack: An attack that involves sending a ping packet that is larger than the maximum IP packet size of 65536 bytes, which can overload a system.
�pinned data: Data that is held in cached storage control, due to a permanent error condition, until it can be destaged to a direct access storage device (DASD) or until it is explicitly discarded by a host command. Pinned data exists only when using fast write, dual copy, or remote copy functions.
�PIN translation: In Cryptographic Support, the conversion of a personal identification number (PIN) encrypted under an input PIN-protection key to encryption under an output PIN-protection key.
�PIN-validation key: In Cryptographic Support, a key-encrypting key used to encrypt the validation data in the process of creating a customer's personal identification number (PIN).
�PIP: (1) See prepare in progress.; (2) See problem isolation procedure.; (3) See program initialization parameter.; (4) See RosettaNet Partner Interface Process.
�PIP data area: A 2000-byte data area that is associated with each prestart job. The PIP data area is used to hold program initialization parameters that are passed on the program start request to the prestart job.
�pipe: (1) A one-way communication path between a sending process and a receiving process.; (2) An interprocess communication mechanism that connects an output file descriptor to an input file descriptor. Usually the standard output of one process is connected to the standard input of another, forming a pipeline.; (3) To direct the data so that the output from one process becomes the input to another process. The standard output of one command can be connected to the standard input of another with the pipe operator. Two commands connected in this way constitute a pipeline.
�pipeline: (1) A serial arrangement of processors or a serial arrangement of registers within a processor. Each processor or register performs part of a task and passes results to the next processor; several parts of different tasks can be performed at the same time.; (2) A direct, one-way connection between two or more processes.; (3) In printers, the hardware path between the channel station or received-page station and the stacker.; (4) A message processing procedure that consists of one or more programs known as stages.
�pitch: (1) The number of characters printed per inch.; (2) A unit of measurement for the width of type (or a printed character), based on the number of characters that can be set (or printed) in one linear inch; for example, 10-pitch has 10 characters per inch. Uniformly spaced fonts are measured in pitch. See also point.
�PIU: See path information unit.
�pivot table: (1) A data array in which the various elements can be moved along the X and Y axes to produce a different aggregate view.; (2) A table characterized by having one metric as a column dimension and all the rest of the metrics represented as row dimensions.
�pixel: See picture element.
�PKCS: See Public Key Cryptography Standards.
�PKI: See public key infrastructure.
�place: A virtual location that is visible in the portal where individuals and groups meet to collaborate. In a portal, each user has a personal place for private work, and individuals and groups have access to a variety of shared places, which can be either public places or restricted places. See also Lotus QuickPlace place.
�place designer: A member of a place who can edit place layout and bookmarks. See also participant, place manager.
�placeholder: (1) The symbol, consisting of a single period in a REXX parsing template, that can be replaced by a value while running a REXX program. A placeholder has the same effect as a variable name, except that no variable is set.; (2) An object, component or file that only exists to mark the position of an intended entity.; (3) A variable that is replaced with a value.
�place manager: A member of a place who can edit place membership, layout, and bookmarks. See also participant, place designer.
�place member: A individual or group who has joined or been granted access to a place. Place members have three levels of access to a place: manager, designer, and participant.
�place operation: In AFP Utilities, an operation that defines a page segment or a record layout in an AFP resource.
�place template: A format for use in creating a place. The portal provides a set of default templates for creating various types of places. Portal administrators may allow users to create, modify, and delete new templates.
�plaintext: In cryptography, any data that is not encrypted. Encryption transforms plaintext to ciphertext and decryption transforms ciphertext into plaintext.
�plan: See application plan.
�plan allocation: The process of allocating DB2 for z/OS resources to a plan in preparation to execute it.
�planar: A hardware part that has (in one or more planes) logic paths, low-voltage distribution paths, or grounding paths of a section of a machine.
�plan component: The autonomic manager component that structures the actions needed to achieve goals. See also autonomic control loop.
�plan member: The bound copy of a DBRM that is identified in the member clause.
�plan name: The name of an application plan.
�planned remote takeover: In an RSR environment, a remote takeover initiated by the IMS operator as part of shutting down the IMSs at the active site in order to transfer the active IMS workload to the remote site. See also remote takeover.
�planned takeover: In XRF, a planned shutdown of the active system, and takeover by the alternate system, for maintenance or operational reasons.
�planner mode: A set of tools in the authoring tool that allows course developers to import courses, build course outlines, set up objectives, and establish course sequencing and rollup rules.
�platform: (1) The combination of an operating system and hardware that makes up the operating environment in which a program runs.; (2) Any base of software technologies on which applications or services can be provided; for example, the Eclipse platform.
�Platform for Internet Content Selection (PICS): A specification that enables Internet users to filter the material they encounter when they surf the Web. Users can accept or reject the material according to its ratings. This specification enables parents, businesses, schools, or discerning individuals to block access to inappropriate and objectionable material.
�Platform for Privacy Preferences (P3P): The World Wide Web Consortium (W3C) specification that enables Web sites to define their privacy practices in a standard format. For more information, see the P3P project Web site (http://www.w3.org/P3P/). See also privacy-sensitive information.
�playback: A technique in which a history of all or part of a program is recorded. The recording allows the user to regenerate the input and output in either the forward or backward direction. This technique is used in debugging.
�playback policy: A policy that consists of instructions to play back a recorded transaction and collect performance data. See also record and playback.
�playback sequence: A series of characters or function keys assigned to a single function key to be used instead of typing the sequence each time.
�playback session: A transaction that consists of a set of simulations that run sequentially or concurrently following the defined event-driven scheduling.
�PLDA: See private loop direct attach.
�plenum: A space used for environmental air; for example, the space above a suspended ceiling.
�plenum cable: A cable that is listed by the Underwriters Laboratory (UL) as having adequate fire resistance and low smoke-producing characteristics for installation without conduit in ducts, plenums, and other spaces used for environmental air, as permitted by National Electrical Code Articles 725-2(b) and 800-3(d).
�PlexManager: A service utility that can be used to manage the communication connections between multiple coordinating address spaces (CASs) and between a CAS and associated CICSPlex SM address spaces (CMASs) and CICSplexes.
�PL/I: A procedure-oriented language designed for solving complex scientific problems or for running complicated business applications.
�PL/I for System i: An IBM PRPQ that is a high-level language available on the server. The PL/I for System i PRPQ is capable of handling a large variety of data structures and easily allows variation of precision in numeric computation.
�P-lock: See physical lock.
�PLOGI: See port login.
�plot: To represent graphically on a medium.
�plotter: A device that uses one or more pens to draw images with lines on paper or other media.
�PLPA: See pageable link pack area.
�PLR: See priority level resource.
�PLT: See program list table.
�PLU: See primary logical unit.
�Plug and Play: An Intel standard for the design of PC expansion boards. It enables computers to recognize new peripheral devices without additional configuration steps.
�Pluggable Authentication Module (PAM): In UNIX and AIX, a programming interface that enables third-party security methods to be used. PAM enables multiple types of authentication, such as Kerberos and the Rivest-Shamir-Adleman (RSA) algorithm, to be used without changing login services.
�plug-in: (1) A separately installable software module that adds function to an existing program, application, or interface.; (2) A dynamically loadable library that a DB2 database management system uses to carry out user-written actions that involve the database.
�plug-in support: A part of the server that adds client/server function and tools to the System i Navigator tree and enhances existing System i Navigator functions.
�ply: A layer of paper.
�PMAC: See Policy Management for Autonomic Computing.
�PM Agent: See Performance Management Agent.
�PM for System i5: See Performance Management for System i5.
�PMI: (1) See performance monitor interface.; (2) See Performance Monitoring Infrastructure.
�PMML: See Predictive Model Markup Language.
�Pocket PC: A handheld Windows-based computer that runs the Pocket PC operating system (formerly Windows CE).
�POE: See Proof of Entitlement.
�POI: See program operator interface.
�point: (1) The second byte of a DBCS code, which uniquely identifies double-byte characters in the same ward. See also ward.; (2) A unit of measurement used mainly for describing type sizes. Each pica has 12 points, and an inch has approximately 72 points.
�pointer: (1) A data element or variable that holds the address of a data object or a function. See also scalar.; (2) The symbol shown on a display or window that a user can move with a pointing device, such as a mouse.; (3) See reference.
�pointer alignment: The COBOL compiler's process of positioning pointer items within a group item to offsets that are multiples of 16 bytes from the beginning of the record.
�pointer class: A class that implements pointers.
�pointer data item: In the COBOL program, a data item in which address values can be stored. Pointer data items can be compared for equality or moved to other pointer data items.
�pointer to member: An identifier that is used to access the address of nonstatic members of a C++ class.
�pointing device: An instrument, such as a mouse, used to move a pointer on the display.
�point-in-time copy: The instantaneous copy that the FlashCopy service makes of the source virtual disk (VDisk). See also FlashCopy service.
�point-in-time table: In SQL replication, a type of replication target table whose content matches all or part of a source table, with an added column that identifies the approximate time when a particular row was inserted or updated at the source system.
�point of consistency: A time when all of the recoverable data that a program accesses is consistent. The point of consistency occurs when updates, insertions, and deletions are either committed to a physical database or rolled back. See also roll back.
�point of control and observation (PCO): A specific point in the procedural flow of a test at which either an observation is recorded of the test environment, or a decision is made regarding the test's flow of control. Closely related concepts, a point of control usually requires the details of one or more points of observations to make the necessary control decision.
�point-of-presence: A system that has been identified as a contact point for another subnetwork for the purposes of collecting topology information.
�point of recovery: In WebSphere MQ for z/OS, a set of backup copies of WebSphere MQ for z/OS page sets and the corresponding log data sets required to recover these page sets. These backup copies provide a potential restart point in the event of page set loss (for example, page set I/O error).
�point-of-sale: In retail communications and Point-of-Sale Utility, pertaining to a method of providing information to support sales and of collecting the resulting sales information from retail devices located in stores.
�point-of-sale device: In retail communications and Point-of-Sale Utility, a device that, together with the store controller, provides retail transaction, data collection, credit authorization, price information, and other inquiry and data entry functions.
�point-of-sale system: In retail communications and Point-of-Sale Utility, a retail environment system consisting of a store controller and one or more point-of-sale devices.
�Point-of-Sale Utility (POS): The IBM licensed program that provides connectivity between the system and retail controllers. In addition, the licensed program provides file conversion capabilities through the retail file conversion system.
�point size: The height of a font in points.
�point-to-point: (1) Pertaining to data transmission between two locations without the use of any intermediate display station or computer.; (2) Pertaining to a style of messaging application in which the sending application knows the destination of the message.; (3) A fibre-channel topology that employs direct links between each pair of communicating entities. See also switched fabric.
�point-to-point line: A communications line that connects a single remote station to a computer. See also multipoint line.
�point-to-point link: In networking, a direct communication link between two nodes in a network.
�point-to-point network: An arrangement where two devices share the same transmission line at the same time. See also multipoint network.
�point-to-point profile: A set of data that is used to establish a point-to-point link.
�Point-to-Point Protocol (PPP): A data-link protocol for communication between two computers that use a serial interface, typically a personal computer connected by telephone line to a server.
�point-to-point virtual Ethernet: A virtual Ethernet network that is used for communication between a System i product and an integrated Windows server.
�poison reverse: A technique for minimizing the time to achieve network convergence. After a connection disappears, the router advertising the connection retains the routing table entry for several update periods and specifies an infinite cost in its broadcasts.
�policing: In QoS, the process of discarding packets (by a dropper) within a traffic stream according to the state of a corresponding meter that enforces a traffic profile.
�policy: (1) In the Backup, Recovery, and Media Services licensed program, a named or otherwise identifiable set of controls used by Backup, Recovery, and Media Services to manage and control specific operations. A policy is an overriding value that is carried in tables for use as a default in processing backup, recovery, archive, and media management operations.; (2) In QoS, the combination of rules and services. The rules define the criteria for traffic treatment, network resource access, and use.; (3) A set of considerations that influence the behavior of a managed resource or a user. See also policy expression.; (4) A list of file-placement and service-class rules that define characteristics and placement of files. Several policies can be defined within the configuration, but only one policy set is active at one time. See also file-placement rule, file-management policy, file-placement policy.; (5) A document that sets forth high-level statements of how changes, releases, or other processes are to be managed, organized, and performed.
�policy agent (pagent): A user-level daemon that provides support for policy management and interfaces with the QoS kernel extension to install, modify, and delete policy rules.
�policy assertion: A requirement, preference, or capability of a managed resource. See also Web Services Policy Framework.
�Policy-based Management: A core capability of the IBM Autonomic Computing Initiative that addresses the need to simplify the management of products and complex systems. See also Policy Management for Autonomic Computing.
�policy collection: An unconstrained group of policies.
�policy collection analysis: The process of examining the properties of the policies in a policy collection and determining the relationships that exist between the policies in a policy collection.
�Policy Core Information Model: An extensible information model and XML schema that represents policy information in a vendor-independent, interoperable, and scalable manner according to the Internet Engineering Task Force (IETF) policy framework.
�policy definition tool: An interface that is used to create, deploy, and otherwise manage policies.
�policy document: An XML document that contains the policies that have the same scope.
�policy domain: A grouping of policy users with one or more policy sets, which manage data or storage resources for the users. The users can be client nodes or agents on managed hosts.
�Policy Editor: The Policy Management for Autonomic Computing graphical user interface (GUI) that is used to create, deploy, and otherwise manage policies. The Policy Editor is implemented using the Integrated Solutions Console.
�policy editor storage: A component in a policy-enabled system that stores policies and notifies autonomic managers when one or more policies are marked for deployment or are removed.
�policy engine: A component of Tivoli Intelligent Orchestrator that collects data and makes decisions on when to deploy servers based on defined thresholds.
�policy evaluation engine: The component of a autonomic manager that selects policies, evaluates policies, and returns the decisions that are contained within policies. Because different autonomic managers can have different policy evaluation engines, more than one policy evaluation engine can exist within a policy-enabled system.
�policy evaluation set: A group of policies that are assembled by an autonomic manager in response to a request for a decision or for some information (such as captions) from the policies.
�policy expression: A representation of a policy. See also policy.
�policy form: See policy grammar.
�policy grammar: The detailed specifications for the syntax of a policy.
�policy group: All or a subset of policies within a given scope.
�policy handle: The unique identifier of a policy document.
�Policy Management for Autonomic Computing (PMAC): The core technology of the IBM Autonomic Computing initiative that provides a standard policy definition and management infrastructure, which enables self-management capabilities and dynamic configuration of systems in an on demand environment. See also Policy-based Management.
�policy region: A group of managed resources that share one or more common policies and which model the management or organizational structure of a network computing environment. Administrators use policy regions to group similar resources, to define access to the resources, to control the resources, and to associate rules for governing the resources.
�policy rule: (1) A declarative, IF-THEN statement containing the precondition, which can consist of multiple Boolean clauses, and the decision for a policy.; (2) A programming statement within a policy that defines a specific action to be performed.
�policy set: (1) A group of rules in a policy domain. The rules specify how data or storage resources are automatically managed for users in the policy domain. Rules can be contained in management classes or policy actions. The users can be client nodes or agents on managed hosts.; (2) The collection of policies within a policy group that share the same decision name. See also decision name.; (3) A collection of assertions about how services are defined, which can be used to simplify security configurations.
�policy signature: The set of decision inputs and decision outputs that are specific to a decision name. Policy signatures are used by decision points.
�policy subregion: In a Tivoli environment, a policy region created or residing in another policy region. When a policy subregion is created, it initially uses the resource and policy properties of the parent policy region. The Tivoli administrator can later change or customize these properties to reflect the specific needs and differences of the subregion.
�policy template: A predefined policy form that helps users define a policy by providing the fixed policy elements that cannot be changed and the variable policy elements that can be changed.
�policy validation: The process of ensuring that each individual policy is valid. In Policy Management for Autonomic Computing, each policy is checked to ensure that it is syntactically correct and that it references only valid sensors and effectors.
�poll: (1) To determine if any remote device on a communications line is ready to send data.; (2) In Managed System Services, to query devices to determine operational status and to collect system data.
�polling: (1) The process whereby stations are invited, one at a time, to transmit.; (2) Interrogation of devices for such purposes as avoiding contention, determining operational status, or determining readiness to send or receive data.; (3) A feature that allows the Sametime Moderator to send a question to the meeting participants. The Moderator can view the results of the poll and show the results to everyone else in the meeting.
�polling interval: The time between the start of each polling session for this system.
�polling list: A list of addresses that the host system uses to control the polling of control units or devices on a BSC or SDLC multipoint line. A general polling list contains the addresses of the control units only; a specific polling list contains the addresses of the devices, which include the addresses of the control units.
�polyfillet: In the GDDM function, a curve based on a sequence of lines. A polyfillet is a curved line that is tangent to the end points of the first and last lines and tangent to the midpoints of all other lines.
�polygon: In the GDDM function, a sequence of adjoining straight lines that enclose an area.
�polyline: In computer graphics, a sequence of adjoining lines.
�polymorphism: An object-oriented programming characteristic that allows a method to perform differently, depending on the class that implements it. Polymorphism allows a subclass to override an inherited method without affecting the parent class's method. Polymorphism also enables a client to access two or more implementations of an object from a single interface.
�pool: (1) A group of resources with similar characteristics and attributes.; (2) In DFSMSrmm, a group of shelf locations in the removable media library whose rack numbers share a common prefix. The shelf locations are logically grouped for easier access to volumes.
�pool database faults: In Performance Tools, the total number of interruptions to jobs that were required to transfer data into the pool to permit the program to process the database data.
�pool database pages: In Performance Tools, the total number of pages of database data transferred from auxiliary storage to the pool to permit the program to run.
�pool domain: A hierarchical classification for resource pools.
�pool nondatabase faults: In Performance Tools, the total number of interruptions to jobs (not necessarily assigned to this pool) that were required to transfer data into the pool to permit the machine interface instruction to access the nondatabase data.
�pool nondatabase pages: In Performance Tools, the total number of pages of nondatabase data transferred from auxiliary storage to the pool to permit the program to run.
�pool storage group: A type of storage group that contains system-managed direct access storage device (DASD) volumes. Pool storage groups allow groups of volumes to be managed as a single entity. See also storage group.
�pool thread: A thread which is used by the CICS DB2 attachment facility for transactions and commands that do not use an entry thread or a command thread. See also command thread, entry thread.
�pop: To remove an item from the top of a pushdown list. See also push.
�POP: (1) See Post Office Protocol.; (2) See protected object policy.
�POP3: See Post Office Protocol Version 3.
�popular ranking: A type of ranking that raises a document's existing ranking based on the document's popularity.
�pop-up menu: A menu that opens as the result of some user action (usually clicking the right mouse button) and that contains choices appropriate for the selected object in its current context.
�POR: See power-on reset.
�port: (1) A hardware interface to which an I/O device is attached for the purpose of sending and receiving data.; (2) An end point for communication between applications, generally referring to a logical connection. A port provides queues for sending and receiving data. Each port has a port number for identification. See also node.; (3) In time-slot management, one end of a 64 kbps unidirectional stream which can be attached to the SCBus.; (4) As defined in a Web Services Description Language (WSDL) document, a single endpoint that is defined as a combination of a binding and a network address.; (5) The interface between a collaboration and other objects in the WebSphere business integration system. It is through a port that a collaboration object binds with a connector or with another collaboration object. See also binding.; (6) The physical entity within a host, SAN Volume Controller, or disk controller system that performs the data communication (transmitting and receiving) over the fibre channel.; (7) To modify a computer program that runs on a given platform, to enable it to run on a different system.
�portability: (1) The ability of equipment to be transported manually.; (2) The ability of a program to run on more than one type of computer system without modification.; (3) The ability of a programming language to compile successfully on different operating systems without requiring changes to the source code.; (4) The ability to use Virtual Storage Access Method (VSAM) data sets with different operating systems. Volumes whose data sets are cataloged in a user catalog can be removed from storage devices of one system, moved to another system, and mounted on storage devices of that system. Individual data sets can be transported between operating systems using access method services (AMS).
�Portable Application Solutions Environment: A feature of the i5/OS operating system that provides the ability to run certain UNIX applications. Programs that run in i5/OS PASE have direct access to PowerPC instructions and access to i5/OS services such as file system support and sockets support.
�portable character set: A set of characters, specified in POSIX 1003.2, section 4, that must be supported by conforming implementations.
�portable data set: A data set that can be transported between systems using access method services (AMS).
�Portable Document Format (PDF): A standard specified by Adobe Systems, Incorporated, for the electronic distribution of documents. PDF files are compact; can be distributed globally via e-mail, the Web, intranets, or CD-ROM; and can be viewed with the Acrobat Reader.
�portable file name character set: The set of characters from which portable file names must be constructed to be portable across implementations conforming to the ISO POSIX-1 standard and to ISO/IEC 9945.
�Portable Operating System Interface (POSIX): An IEEE family of standards designed to provide portability between operating systems that are based on UNIX. POSIX describes a wide spectrum of operating-system components ranging from C language and shell interfaces to system administration
�Portable Operating System Interface for Computer Environments: See Portable Operating System Interface.
�portable wireless data: A classification of networks that access the Internet through a laptop or palmtop computer and a small wireless modem.
�portal: A single, secure point of access to diverse information, applications, and people that can be customized and personalized.
�Portal Administration: The place where portal administrators set and maintain basic collaboration permissions, place records, place membership records, and server settings for companion products for advanced collaboration.
�portal member: An individual or group who has a user record in the portal directory (LDAP or other directory) and can log in to the portal.
�port designation: A 4-character identifier (such as LPT1 or COM1) assigned to a printer, plotter, or communications device so that the system has a unique way to refer to the resource.
�port destination: The specialization of a service integration bus destination. Each port destination represents a particular message format and transport protocol that you can use to pass messages to an externally-hosted service.
�portfolio: (1) A container for the tasks that apply to each role that the user is assigned. The portfolio is the primary way in which a user's work is organized in the interface.; (2) The complete inventory of an organization's programs and projects, or both.
�port group: (1) A group of ports identified by the common carrier with a single DTE address. The network directs incoming calls to the first available port, using a sequential search (rotary) technique.; (2) A logical name used to group one or more ports (network devices or interfaces) of the same network type that can be used to reach a given end-user destination. For example, if multiple ATM adapters in the IBM Content Manager VideoCharger Server complex are connected to the same ATM networks, these adapters can be configured under the same port group. The controller selects ports as necessary to balance the load.
�porting: A process of converting software so that it is able to run on multiple environments.
�portlet: (1) A reusable Web module that runs on a portal server. Portlets have predefined roles such as retrieving news headlines, searching a database, or displaying a calendar.; (2) A Web component that provides specific services or information to users and that is specifically designed to be aggregated with other portlets in the context of a composite page, or portal.
�portlet API: The set of interfaces and methods that are used by Java programs running within the portal server environment to obtain services.
�portlet application: A collection of related portlets that can share resources with one another.
�portlet container: A column or row that is used to arrange the layout of a portlet or other container on a page.
�portlet control: A portlet registry setting that renders the outer frame for a portlet.
�portlet framework: The set of classes and interfaces that support Java programs running within the portal server environment.
�portlet mode: A form assumed by a portlet to provide a distinctive interface for users to perform different tasks. Portlet modes can include view, edit, and help.
�port login (PLOGI): The port-to-port login process by which initiators establish sessions with targets. See also fabric login.
�portmapper: (1) A program that maps client programs to the port numbers of server programs. A portmapper is used with remote procedure call (RPC) programs.; (2) A service that implements version 2 of the portmapper protocol. See also RPCBIND.; (3) A protocol that specifies how to map client programs to the port numbers of server programs. Multiple versions of this protocol, each specifying a different level of functionality, have been defined.
�port matching: The process by which InterChange Server determines at runtime whether to isolate the currently running events. In its analysis, the server checks whether, among any of the collaborations, the ports are bound to the same set of connectors. If ports are bound to the same set of connectors, the server checks whether the ports bound to the same connector have the same business object type. If they do, the ports are considered to match and event isolation is required. See also event isolation.
�port_name: The unique identifier assigned to a fibre-channel port and communicated during login and port discovery.
�port number: (1) In Internet communications, the identifier for a logical connector between an application entity and the transport service.; (2) The part of a socket address that identifies a port within a host.
�port of entry: The name and type of device from which a user signs on. CICS recognizes only TERMINALs and CONSOLEs.
�portrait page presentation: The position of a printed sheet that has its short edges as the top and bottom and its long edges as the sides. See also landscape page presentation.
�port scan: Software that searches systems in a network for open ports. A port scan is used by administrators to check the security of a network, and by hackers or crackers to gain entry to the network.
�port set: In time-slot management, a collection of ports that can be connected using a single CA_TDM_Connect() API call to a complementary collection of ports. An example of a port set is the transmit-receive pair corresponding to one telephony channel on a Digital Trunk Quad Adapter (DTQA).
�port type: An element in a Web Services Description Language (WSDL) document that comprises a set of abstract operations, each of which refers to input and output messages that are supported by the Web service. See also interface.
�POS: (1) See part of speech.; (2) See Point-of-Sale Utility.
�POSIT: A keyword in the ICHERCDE macro that determines the position of a resource class in the RACF class descriptor table (CDT). All classes with the same POSIT value are controlled together by the SETROPTS command.
�position: (1) Within a string, the ordinal position of one element of a string relative to another.; (2) Within an attribute, the ordinal position of one value relative to another.
�positional parameter: (1) A parameter that must appear in a specified location, relative to other parameters. See also keyword parameter.; (2) A variable within a shell program. Positional parameters are assigned from the shell's arguments when the shell is invoked
�positional pattern: In REXX, a pattern that causes parsing to occur on the basis of location within the input string. A positional pattern takes the form of a signed or unsigned whole number.
�positive response: In SNA, a reply indicating that a request arrived and was successfully received and processed. See also negative response.
�POSIX: See Portable Operating System Interface.
�POSIX open system environment (POSIX OSE): The open system environment in which the standards included are not in conflict with ISO/IEC and consist of: International Standards and Profiles, developed by ISO, IEC, or CCITT; Regional Standards and Profiles, developed by a group recognized as an official body by a regional governmental entity, such as the European Community; and National Information Technology Standards and Profiles, developed by a national standards body recognized as such by ISO, IEC, or CCITT, as appropriate.
�POSIX OSE: See POSIX open system environment.
�POSIX process: As defined by POSIX, an address space with one or more threads executing within that address space, and the required system resources for those threads.
�POSIX signal: A mechanism by which a process may be notified of, or affected by, an event occurring in the system. Examples of such events include hardware exceptions and specific actions by processes. POSIX signal is also used to refer to the event itself.
�possible duplicate emission (PDE): A payment that has been identified as a possible duplicate of another payment, because the contents of certain fields or combinations of fields in both payments are identical or similar.
�possible duplicate flow: A flow that might have been received by the collaboration.
�post: (1) To add information in a record to keep that record current.; (2) To note the occurrence of an event.
�POST: (1) In HTTP, a parameter on the METHOD attribute of the FORM tag that specifies that a browser will send form data to a server in an HTTP transaction separate from that of the associated URL.; (2) A series of internal diagnostic tests activated each time the system power is turned on.
�Postal, Telephone, and Telegraph (PTT): An agency that regulates and administers the telephone and postal systems in certain countries.
�postamble: A sequence of binary characters recorded at the end of each block of data, on phase-encoded magnetic tape, for synchronization when reading backward.
�postcondition: (1) A constraint that must be true at the completion of an operation.; (2) A textual description defining a constraint on the system when a use case has terminated.
�Post Office Protocol (POP): A protocol that is used for exchanging network mail and accessing mailboxes.
�Post Office Protocol Version 3 (POP3): A mail protocol that allows clients running it to retrieve mail from a host mail server also running the protocol.
�postoperation exit program: A user-written program that is given control after operation of a system function.
�postponed abort UR: A unit of recovery that was inflight or in-abort, was interrupted by system failure or cancellation, and did not complete backout during restart.
�PostScript: A page description language developed by Adobe Systems, Incorporated, that describes how text and graphics are presented on printers and display devices.
�post-takeover: The XRF phase, immediately following takeover, when the new active system does not have an alternate system.
�Post Telephone and Telegraph Administration (PTT): An organization, usually a government department, that provides data communication services in countries or regions other than the USA. Examples of PTTs are the Bundespost in Germany and the Nippon Telephone and Telegraph Public Corporation in Japan.
�power control compartment (PCC): The rack component that logically controls the application of alternating current power to the units in the rack.
�power cord: The electrical connection between the AC power source and the computer.
�power down: A CL command to turn the power off and bring an orderly end to system operation.
�power-on light: The light on the operator panel that indicates that the DC power in the system is functioning.
�power-on reset (POR): See initial microprogram load.
�power-on self-test (POST): A series of internal diagnostic tests activated each time the system power is turned on.
�PowerPC: A computer architecture that is based on the third generation of RISC processors. PowerPC was developed jointly by Apple, Motorola, and IBM.
�PowerPC AS: The processors that implement the 64-bit PowerPC architecture with extensions to support commercial applications for multiple users.
�PowerPC Processor Element (PPE): In the Cell Broadband Engine architecture, a grouping of multiple PowerPC Processor Units (PPUs). The PPEs perform general processing and system management tasks, such as running the operating system and applications. See also Cell Broadband Engine processor, PowerPC Processor Unit.
�PowerPC Processor Unit (PPU): A 64-bit PowerPC core processor located at the heart of the Cell Broadband Engine multiprocessor, with associated cache, and a Vector Multimedia Extensions (VMX) unit. The PPUs use the standard PowerPC instruction set. Multiple PPUs make up a PowerPC Processing Element (PPE). See also PowerPC Processor Element.
�power sequence cable: A signal cable that connects the secondary racks to each other and to the primary rack in a system with more than one rack, and allow complete control of the power from the primary rack.
�power user: A person who has special privileges to perform object management tasks, such as creating and updating objects.
�PPCC: See Page Printer Communication Component.
�PPDU: See presentation-layer protocol data unit.
�PPE: See PowerPC Processor Element.
�PPID: See parent process ID.
�PPP: See Point-to-Point Protocol.
�PPP filter identifier: A filter identifier that allows you to apply filter rules to an interface that has been defined in a point-to-point profile. The PPP filter identifier also links the filter rules to groups of users in a point-to-point profile. Because the point-to-point profile is associated with a specific IP address, the filter identifier implicitly defines the interface to which the rules apply.
�PPQ: See pending page queue.
�PPRC: See Peer-to-Peer Remote Copy.
�PPRC Extended Distance (PPRC-XD): An optional feature for the ESS that maintains a fuzzy copy of a logical volume (LVOL) on the same ESS or on another TESS. PPRC-XD ensures that all modifications that any attached host performs on the primary LVOL are also performed on the secondary LVOL at a later time. The original order of update is not strictly maintained. See also synchronous PPRC, Peer-to-Peer Remote Copy.
�PPRC-XD: See PPRC Extended Distance.
�PPS: See primary power supply.
�PPU: See PowerPC Processor Unit.
�PRA: (1) See primary rate access.; (2) See Project Review Authority.
�pragma: (1) A standardized form of comment which has meaning to a compiler. A pragma usually conveys non-essential information, often intended to help the compiler to optimize the program. See also directive.; (2) A preprocessor directive that is not specified by the ISO standard. Pragmas often control actions of the compiler and linker. A pragma always begins with a number sign (#).
�PRD: See product requirements document.
�preamble: A sequence of binary characters recorded at the beginning of each block of data, on a phase-encoded magnetic tape, for the purpose of synchronization when reading forward.
�Preboot Execution Environment (PXE): An industry standard client/server interface that allows networked computers that are not yet loaded with an operating system to be configured and booted remotely. PXE is based on Dynamic Host Configuration Protocol (DHCP).
�prebuilt kit: A collection of catalog entries that has a code and is ordered as a single item. See also bundle, kit.
�prebuilt kit component: An item that is sold as part of a prebuilt kit.
�precedence: The priority system for grouping different types of operators with their operands.
�precision: (1) An attribute of a number that describes the total number of binary or decimal digits, excluding the sign. The sign is considered positive if the value of a number is zero.; (2) A measure of the ability to distinguish between nearly equal values.
�precompilation: A processing of application programs containing SQL statements that takes place before compilation. SQL statements are replaced with statements that are recognized by the host language compiler. Output from this precompilation includes source code that can be submitted to the compiler and the database request module (DBRM) that is input to the bind process.
�precompile: To process programs that contain SQL statements before they are compiled. SQL statements are replaced with statements that will be recognized by the host language compiler. The output from a precompile process includes source code that can be submitted to the compiler and used in the bind process.
�precondition: (1) A definition of what must be true when a task or process starts.; (2) A textual description defining a constraint on the system when a use case may start.; (3) A constraint that must be true when an operation is invoked.; (4)
�predefined dynamic node group: A node group whose members all have a certain attribute set to a certain value.
�predefined element: An element for which a matching definition exists in the message model with an appropriate set of properties and in the correct context. See also predefined message, self-defining element.
�predefined macro: In C/C++, an identifier predefined by the compiler, which will be expanded by the preprocessor during compilation.
�predefined message: (1) A message with a description that is created and stored in a message file before it is sent by the program. See also immediate message.; (2) A message for which a matching definition exists in the message model with an appropriate set of properties and in the correct context. See also self-defining message, predefined element.
�predefined value: A fixed value defined by IBM that has a special use in the control language and is reserved in the operating system. A predefined value usually has an asterisk (*) as the first character in the value.
�predicate: (1) An element of a search condition that expresses or implies a comparison operation.; (2) A Boolean logic term denoting a logical expression that determines the state of a variable.; (3) A statement using rule language syntax or Prolog language syntax that performs a function in a rule action.; (4) A logical expression, typically involving sub-events, used to define a composite event. When the predicate becomes true, the composite event fires.
�predictable write: A write operation that can perform a cache operation without knowledge of the existing format on the medium. All write operations on fixed-block architecture (FBA) direct access storage devices (DASDs) are predictable. On count-key-data (CKD) DASD devices, a write operation is predictable if it performs a format write operation for the first data record on the track.
�Predictive Failure Analysis (PFA): A scheduled evaluation of system data that detects and signals parametric degradation which might lead to functional failures.
�Predictive Model Markup Language (PMML): An XML-based language defined by the Data Mining Group that provides a way for companies to define predictive models and share models between compliant vendors' applications.
�prediscovery: A type of discovery in which a program is run against user-provided files in an offline environment and provides information that is used to monitor resources.
�preemptive shutdown: In WebSphere MQ, a shutdown of a queue manager that does not wait for connected applications to disconnect, or for current MQI calls to complete. See also controlled shutdown, immediate shutdown.
�pre-execution setup: The portion of setup performed by the main device scheduler (MDS) before a job begins execution.
�preference: A parameter that a user can set through the application menu.
�preference node: A collection of configuration data, represented by key-value pairs, that is specific to an ORB or ORB set and that is required by a component. See also inheriting.
�preferred binary encoding: In OSI, the format in which an NSAP address or network entity title is passed in the network protocol.
�preferred computer: The primary computer used by an application running under Microsoft Cluster Server control. After a failover to another computer, MSCS monitors the preferred computer until it is repaired, and as soon as it is running correctly again, moves the application back to it.
�preferred currency: The currency indicated by a customer as the one in which he or she would prefer to see prices. The preferred currency is indicated in the customer profile. See also shopping currency, supported currency.
�preferred language: The language indicated by a customer as being the one in which he or she would like to conduct transactions. The preferred language is indicated either in the customer profile or by use of the langId parameter, which is available from the URL-based controller commands. See also shopping language.
�preferred transport class: In OSI, a transport class that an application entity initially requests during association establishment. See also alternative transport class.
�prefetch: To read data ahead of, and in anticipation of, its use.
�prefix: A code at the beginning of a message or record.
�prefixed save area (PSA): An element of MVS/ESA virtual storage which contains processor-dependent status information.
�prefixing: Specifying at system initialization that you want CICS to prefix the resource names that it passes to RACF for authorization with the RACF userid under which the CICS region is running.
�preformat: The process of preparing a VSAM linear data set for DB2 use, by writing specific data patterns.
�pregenerated system: A CICS system distributed in a form that has already undergone the system generation process.
�preinitialization: A process by which an environment or library is initialized once and can then be used repeatedly to avoid the inefficiency of initializing the environment or library each time it is needed.
�preliminary design review (PDR): In the waterfall life cycle, the major review held when the architectural design is completed.
�prelinker: A utility that preprocesses an object for certain programs. See also binder.
�preload: To load the root addressable portion and independent overflow portion of a VSO DEDB area into a data space when the area is opened.
�preloaded system: A system that is shipped with the licensed programs and program temporary fixes (PTFs) already installed on the disk.
�preopen: To open a DEDB area after the first checkpoint following IMS control region initialization or during /START AREA command processing. If an area is not preopened, it will be opened during the first read request for the area.
�preoperation exit program: A user-written program that is given control before operation of a system function.
�preparation: In Enterprise Generation Language (EGL), the process by which executable objects are created from generated source code.
�preparation machine: (1) In Tivoli Software Distribution, Version 4, any Windows 95 (or later), Windows NT, or OS/2 system on which the Tivoli Software Distribution Java Endpoint Package Editor is installed.; (2) In Tivoli Software Distribution, Version 3, any Windows system on which the AutoPack Control Center is installed.
�preparation phase: In software distribution, the phase in which each action in a software package prepares the conditions for successfully executing an install or remove operation. If the preparation phase fails, the target system is returned to its original state. See also transactional mode.
�prepare: (1) To convert an SQL statement or XQuery expression from text form to an executable form, by submitting it to the SQL and XQuery compiler.; (2) To convert EGL-generated source code into an executable program.
�prepared (PRP): Pertaining to a logical unit of work state that indicates that the current logical unit of work is in doubt. The prepared state only occurs at nodes that are not a last agent.
�prepared SQL statement: A named object that is the executable form of an SQL statement that was processed by the PREPARE statement.
�prepared XQuery expression: A named object that is the executable form of an XQuery expression that was processed by the PREPARE statement.
�prepare in progress (PIP): The prepare in progress logical unit of work (LUW) state indicates that the current LUW is preparing its resources to commit. A failure during PIP state results in a rollback.
�prepare phase: The first phase of a two-phase commit process in which all participants are requested to prepare for commit.
�pre-partitioning agent: The process that reads data and distributes it to the partitioning agent. See also partitioning agent, load agent.
�preprinted form: A sheet of paper (form) containing a preprinted design of constant data on which variable data can be printed.
�preprocessing exit program: An exit program that performs preprocessing when an operation is requested against an exit point. An example of a preprocessing exit program is the Preprocessing Exit Program for Add.
�preprocessor: A routine that performs initial processing and translation of source code or data prior to compiling the source code or processing the data in another program such as an emulator.
�preprocessor directive: In the C and C++ languages, a statement that begins with the symbol # and is interpreted by the preprocessor during compilation.
�preprocessor statement: In the C and C++ languages, a statement that begins with the symbol # and contains instructions that the preprocessor can interpret.
�prerequisite: (1) A component or service that is needed before a component can be installed. In other words, the components, resources, or services listed as prerequisites of a component must be installed before the component can be installed.; (2) A hardware or software requirement that is fulfilled by a capability.
�prerequisite fix: A temporary solution to or a bypass of a problem that is necessary to provide a complete solution to correct a problem. The system requires that you apply the prerequisite fix either before the PTF that needs it or with the PTF that needs it. See also corequisite fix, distribution requisite fix.
�preruntime array: In RPG, an array that is loaded at the same time as the program, before the program actually begins to run. See also compile-time array, runtime array.
�preruntime table: In RPG, a table that is loaded at the same time as the source program, before the program actually begins to run. See also runtime table.
�presence list: A list of names that are active in Sametime. A presence list allows the user to see who is here or who is online. For example, a presence list in a document contains the names of the online users who are viewing the document (Who Is Here). An instant messaging session may be started with anyone on the list. See also active name, Who Is Here, Who Is Online.
�presentation address: (1) In the Distributed Computing Environment (DCE), an unambiguous name that is used to identify a set of access points.; (2) In OSI, an address that uniquely identifies an application entity. The presentation address consists of one or more NSAP addresses, a TSAP selector, an SSAP selector, and a PSAP selector.
�presentation context: In OSI, the combination of an abstract syntax with a transfer syntax that specifies how to transfer and interpret defined data values between nodes.
�presentation control: In Business Graphics Utility, an option that allows parts of a chart to be included or excluded when produced.
�presentation controls: In Backup, Recovery, and Media Services, a system policy menu option for defining the presentation of days of the week, the beginning day of the week, and other special characters as they appear on Backup, Recovery, and Media Services displays.
�presentation data value (PDV): In OSI, a complete unit of information that is meaningful to an application entity.
�presentation device: A device, such as a printer, that produces character shapes, graphic pictures, images, or bar code symbols on a physical medium.
�presentation formatter: A CGI program that defines the forms used to select and present assets to clients.
�presentation graphics routines (PGR): A group of routines within the operating system that allows business charts to be defined and displayed procedurally through function routines. See also Graphical Data Display Manager.
�presentation layer: In OSI architecture, the layer that provides services that enable functional units in the application layer to select a common syntax in order to define data and operations to be performed on the data.
�presentation-layer protocol data unit (PPDU): In OSI, a protocol data unit in the presentation layer.(I)
�presentation-layer service access point (PSAP): In OSI, a service access point in the presentation layer.
�presentation-layer service data unit (PSDU): In OSI, a unit of data transferred between the application layer and the presentation layer.
�presentation logic: The part of a distributed application that is concerned with the user interface of the application. See also business logic.
�presentation service access point: The address of an OSI communications partner that identifies an application in a computer.
�presentation space: (1) A conceptual two-dimensional surface in storage on which data for a portion of the display surface is represented.; (2) The display data buffer associated with a partition. The size of the presentation space is defined as equal to, or larger than, the size of the viewport. When the presentation space is equal to the viewport size, all the data in the presentation space is displayed. When the presentation space is larger than the viewport, the user must move the scrolling window within the presentation space to display the data within the viewport. See also scrolling window, viewport.; (3) A portion of the device's buffer storage, allocated to a partition, that contains only display data that CICS sends to that partition. See also partition.
�presentation text: See composed text.
�Presentation Text Object Content Architecture (PTOCA): An architecture that provides a collection of constructs used to interchange and present presentation text data, such as printing text data on a page, page segment, or overlay.
�preset destination mode: An optional mode of terminal operation that allows the destination of terminal input to be fixed as a specific transaction code or logical terminal.
�preset terminal security: When a CICS region is started, the signing on of selected terminals as users whose userids are the terminal identifiers. Persons using these terminals have the authorizations given to the terminals.
�prestart job: A batch job that starts running before the remote program sends a program start request.
�presumed trust: A type of identity assertion where trust is presumed and additional trust validation is not performed. Use this mode only in an environment where trust is established with some other mechanism.
�Pretty Good Privacy (PGP): An electronic transfer protocol that allows for the private exchange of files or mail using public key encryption.
�preventive service planning bucket (PSP bucket): A group of files containing information that becomes available after the product documents are printed.
�preview pane: A pane that lets users read the content of the document that is selected in the view pane. If Notes is set to preview document links, users can also view documents linked to the selected document.
�previous release: The last required release of the system (such as Release 1.0) prior to the current release (such as Release 2.0), including any modification levels (such as Release 1.0 Modification Level 1 or Modification Level 2) that were not required.
�previous system: The system that sent the TELNET or pass-through request that brought the user to the current system.
�PRI: (1) See primary rate ISDN.; (2) See primary rate interface.
�primary: (1) Pertaining to an irreducible unit of data, such as a single constant, variable, or array element.; (2) Pertaining to an object that is in the object storage hierarchy and can be retrieved. The last time the object was used or its actual or expected frequency of use is not of consequence in this process.
�primary administrative server: The administrative server that runs on the same engine as the master metadata server and processes all administrative requests that are initiated from the SAN File System console and those requests initiated from the administrative command-line interface (ACLI) that is logged into the master metadata server.
�primary authorization ID: The authorization identifier used to identify an application process to DB2 for z/OS. See also secondary authorization ID.
�primary axis: In the GDDM function, the axis used to plot data in a business chart. See also secondary axis.
�primary Copy Services server: One of two Copy Services servers in a Copy Services server group. The primary Copy Services server is the active Copy Services server until it fails; it is then replaced by the backup Copy Services server. See also backup Copy Services server, Copy Services client, Copy Services domain, Copy Services server.
�primary database: In high availability disaster recovery, the main database, which is accessed by applications. Applications apply updates to the primary database, and those updates are propagated on the standby database by using log shipping.
�primary data set: When referring to a data set collection, the first data set allocated. For individual data sets being stacked, the primary data set precedes the data set being stacked and is allocated closest to it.
�primary data set group: In a database, the first or only data set group defined. The root segment type always resides in the primary data set group. See also data set group, secondary data set group.
�primary delay interval (PDI): The interval that must elapse between the apparent loss of surveillance signal from the alternate system and any reaction by the active system. This interval is set by the PDI system initialization parameter and, in CICS/VSE, defaults to 30 seconds.
�primary device: One device of a dual-copy or remote-copy volume pair. All channel commands to the copy logical volume (LVOL) are directed to the primary device. The data on the primary device is duplicated on the secondary device. See also secondary device.
�primary disk pool: An independent disk pool that defines a collection of directories and libraries and may have other secondary disk pools associated with it. A primary disk pool also defines a database for itself and other disk pools that may be added in its disk pool group.
�primary domain: The domain that is defined by the DNS domain database file on a primary name server.
�primary entry point: The location that receives control when the module is invoked by its primary, or member, name. alternate entry point. The location, other than the primary entry point, that can receive control from, or be referenced by, another module. See also alternate entry point.
�primary expression: (1) Any of the following types of expressions: a) identifiers, b) parenthesized expressions, c) function calls, d) array element specifications, e) structure member specifications, or f) union member specifications.; (2) Literals, names, and names qualified by the :: (scope resolution) operator.; (3) The basic primitive structure of the XQuery language. Primary expressions include literals, variable references, context item expressions, constructors, and function calls. A primary expression can also be created by enclosing any expression in parentheses, which can help to control the precedence of operators.
�primary file: (1) In the DDS for a join logical file, the first physical file specified on the JFILE keyword. See also secondary file.; (2) For certain types of join operations using Query, the first of all files that are joined in a query definition. The data from this file is used in every record formed by a join specification.; (3) In RPG, if specified, the first file from which RPG reads a record. In multifile processing, the primary file is used to determine whether the MR indicator is set on. See also full procedural file.
�primary focal point: A network node that receives alerts from nodes that the user has defined in a sphere of control. See also default focal point, backup focal point.
�primary folder: In System Manager, the folder into which the documentation of the corresponding development folder is stored if dynamic naming is not allowed for the option or if no override folder name is specified at install time.
�primary GPFS cluster configuration server: In a GPFS cluster, the node chosen to maintain the GPFS cluster configuration data.
�primary group: A group profile whose authority to an object is stored with that object. Primary group authority may provide better performance than private group authority.
�primary group authority: The authority that the primary group has to the object. See also owner authority, private authority, public authority.
�primary group buffer pool: For a duplexed group buffer pool, the structure that is used to maintain the coherency of cached data. This structure is used for page registration and cross-invalidation. The z/OS equivalent is old structure. See also secondary group buffer pool.
�primary index: (1) An index that enforces the uniqueness of a primary key.; (2) In VSAM, the set of primary keys that provide the standard path for access to the data set.
�primary instructor: The person who has control of a LearningSpace - Virtual Classroom session when it begins. The primary instructor comes from the list of instructors specified when a course is created. By default, the person who schedules a session becomes the primary instructor for that session. The primary instructor can also promote one of the other listed instructors as the primary instructor instead.
�primary key: (1) In a relational database, a key that uniquely identifies one row of a database table. See also constraint, unique key, foreign key.; (2) An object that uniquely identifies an entity bean of a particular type.; (3) In each record of a VSAM KSDS, an identifying field. The key of each record is a field in a predefined position within the record. Each key must be unique in the data set.; (4) In a federated system, a unique key that is part of the definition of a nickname and that the optimizer uses to improve query performance. This key is not validated when operations such as insert and update are performed.
�primary key analysis: A type of analysis that evaluates data tables to find primary key candidates.
�primary language: The national language installed on the system as the default language used to display and print information. The primary language is also used to service the system. See also secondary language.
�primary library: In System Manager, for a code load, the library in which the code load is stored if dynamic naming is not allowed for the option or no override library names are specified at install time. For language loads, the library in which the language load is stored if the language load identification matches the primary language of the system and either dynamic naming is not allowed for the option or no override library names are specified at install time.
�primary link: The optical connection between a local optical link card and a remote bus adapter card.
�primary log: A set of one or more log files used to record changes to a database and for which storage is allocated in advance. See also secondary log.
�primary logical unit (PLU): In SNA, the logical unit that contains the primary half-session for a particular logical unit-to-logical unit (LU-to-LU) session. See also secondary logical unit.
�primary mode: If a program runs in primary mode, the system resolves all addresses within the current (primary) address space. See also access register mode.
�primary name: The name contained in the primary directory entry for a library memory, which is used for creating, copying, and deleting the member. A library member always has one primary name and possibly one or more aliases.
�primary name server: A name server that always loads domain information from its own domain database file.
�primary node: A cluster node that currently has the principle copy of a cluster resource. All replications of a resilient resource originate from the primary copy of the resource.
�primary NSD server: A node designated to perform Network Shared Disk (NSD) disk-access functions. Nodes not directly attached to a disk access it using the primary NSD server.
�primary optical link: A connection between the system and an expansion unit. The hardware that creates this link is the local optical link card, the remote bus adapter, and the optical cables that connect the two.
�primary panel: The main Prompted Query panel containing the user's query.
�primary part: An EGL part whose name is the same as the source file in which the part resides. The primary parts are data table, form group, library, page handler, program, and UI record.
�primary partition: A logical partition that provides certain general functions on which all logical partitions are dependent. The primary partition is the only partition that is active in a system that has a single partition. All partition management functions are performed from this partition. If this partition is powered off or restarted, for example, the entire system is powered off or restarted.
�primary power supply (PPS): A power supply that attaches to the customer's ac input power; generates and distributes 390 V dc; and controls and monitors associated power functions.
�primary processing unit: In a multiple processing-unit environment, the processing unit assigned to perform level functions for backup and dump.
�primary QMF session: An interactive session that is started from outside QMF. Within this session, other sessions can be started by using the INTERACT command.
�primary rate access (PRA): See primary rate interface.
�primary rate interface (PRI): An ISDN interface normally used by large sites, providing 30 (E1) or 23 (T1) B-channels of 64 kbits per second and one D-channel for signaling. This is often known as 30B+D or 23B+D. See also basic rate interface.
�primary rate ISDN (PRI): See primary rate interface.
�primary reintegration: The process in which the original primary database can rejoin a high availability disaster recovery pair after a failover. The original primary database can rejoin only as the new secondary database in the HADR pair.
�primary replica: The replica designated to be the only recipient of updates by the Administration Process. By updating a primary replica and then replicating that database to other replicas on other servers, you avoid creating replication conflicts.
�primary request: In an IMS multisystem environment, a message entered into a terminal before it is processed. See also reply, secondary request.
�primary server: The server on which all resources that are to be deployed exactly once per instance or once per organization unit (OU) are deployed.
�primary session: The session between a class 1 terminal and the active IMS.
�primary space allocation: The amount of space requested by a user for a data set when it is created. See also secondary space allocation.
�primary storage: A direct access storage device (DASD) volume available to users for data allocation. The volumes in primary storage are called primary volumes. See also DASD volume, storage hierarchy, migration level 1, migration level 2, primary volume.
�primary structure: A coupling facility list structure that contains shared queues or shared resources. See also overflow structure.
�primary subsystem: The subsystem that is made active when the system is initialized.
�primary system: In a remote journal network, the System i system where the original database resides.
�primary system console: A workstation that is attached to the first input/output processor that is capable of supporting workstations. If Operations Console has been configured, a personal computer (either at a local location or a remote location) becomes the primary system console.
�primary system name: In SNADS, the system name of the highest logical unit in the network. See also secondary system name.
�primary task: The task under which most dynamic support programs (DSPs) execute.
�primary thread: See initial thread.
�primary virtual disk: In a remote copy or Peer-to-Peer Remote Copy relationship, the target of write operations issued by the host application. See also relationship.
�primary vital-record specification: The first retention and movement policy that DFSMSrmm matches to a data set and volume used for disaster recovery and vital record purposes. See also secondary vital-record specification, vital record specification.
�primary volume: A volume managed by DFSMShsm containing data sets that are directly accessible to the user. See also primary storage.
�primary window: The window in which the main interaction between the user and an object takes place.
�primary write: A type of update that records changes to the checkpoint data set. See also intermediate write, final write.
�prime index: In z/OS Virtual Storage Access Method (VSAM), the index component of a key-sequenced data set (KSDS).
�prime key: In z/OS Virtual Storage Access Method (VSAM), one or more bytes within a data record used to identify the data record or control its use. A prime key must be unique.
�prime record key: In COBOL, a key whose contents uniquely identify a record within an indexed file.
�priming: The displaying by the Interactive Storage Management Facility (ISMF) of a data entry panel already containing the values that were in effect the last time the program was used.
�primitive: (1) A simple and fundamental data structure, API, algorithm, or system service that serves as a building block for more complex solutions, applications, or environments.; (2) A message sent from one process to another.; (3) A message processing node that cannot be further subdivided. See also subflow node.
�primitive type: (1) In Java, a category of data type that describes a variable that contains a single value of the appropriate size and format for its type: a number, a character, or a Boolean value. Examples of primitive types include byte, short, int, long, float, double, char, boolean.; (2) A predefined basic data type without any substructure, such as an integer or a string.
�principal: (1) An entity that can communicate securely with another entity. A principal is identified by its associated security context, which defines its access rights.; (2) An entity that can communicate securely with another entity. In Kerberos, principals are represented as entries in the Kerberos registry database and include users, servers, computers, and others.
�principal development library: In System Manager, a development library into which a load object (*PRDLOD) is created.
�principal facility: The terminal or logical unit that is connected to a transaction at its initiation. See also alternate facility.
�principal library: In System Manager, the library that contains the load object (*PRDLOD).

�principal name: (1) The name by which a principal is known to the Distributed Computing Environment (DCE) security services.; (2) In the Kerberos protocol, the name by which the Kerberos principal is identified. The principal name usually consists of either a) a user name and a realm name or b) a service name, host name, and a realm name.
�principal primary library: In System Manager, a primary library into which the objects that were created in the principal development library are stored when no overriding library name is specified at installation time.
�printable area: The area on a sheet of paper where print can be placed.
�print band: An interchangeable metal band that contains the print characters used by some printers.
�print data set: A data set created by an application program that contains the actual information to be printed and, optionally, some of the data that controls the format of the printing. The types of print data sets are composed text, line format, and mixed format. See also auxiliary data set, print file.
�print data stream: The data stream that is created by PSF and transmitted to the printer.
�print descriptor: An object used to manage printing that is created and maintained by the PrintManager program. Print descriptors describe where a print job is printed, how a print job is processed, and how output appears. The print descriptors contain capabilities and defaults of options used for printing. The system-recognized identifier for the object type is *PDG.
�print descriptor group: An object used to store print descriptors so they can be managed effectively on a system. The system-recognized identifier for the object type is *PDG.
�print direction: A combination of the inline direction and the baseline direction.
�printer control language (PCL)
�printer definition: An object in the Printer Inventory that contains information about a printer or set of printers that share the same characteristics. A printer definition contains information that is used to print files.
�printer/display layout: A specification on which the user can design the format for a report either printed or displayed.
�printer file: A device file that determines what attributes printed output will have. A particular printer may or may not support all of the attributes specified in a printer file.
�printer ID: The identification code assigned to printers.
�Printer Inventory: In Infoprint Server, a set of files that contain information about printers. The Printer Inventory includes such objects as printer definitions, functional subsystem (FSS) definitions, and job selection rules for IP PrintWay.
�Printer Inventory Definition Utility (PIDU): In Infoprint Server, a utility program that creates objects in the Printer Inventory.
�printer output: A file that holds output data that is waiting to be processed for printing.
�printer session: A PC program that allows a personal printer to emulate a host system printer.
�printer spooling: In CICS, a facility that provides support for writing data to print spools. Only printed output is supported by CICS.
�printer writer: A system program that writes spooled files to a printer.
�print file: A file that is created for the purpose of printing data. A print file includes information to be printed and, optionally, some of the data. See also print data set.
�print format utility (PFU): In AFP Utilities, a utility that allows a user to print a database file member in various formats without writing any programs.
�Printing Systems Manager (PSM): An IBM licensed program that applies print administration and management technology to a cross-platform, client/server print system. PSM provides a set of (a) printing functions for submitting and controlling print jobs and (b) systems management and operator functions to control print spoolers and print supervisors. PSM is based on the Palladium distributed print system.
�Print Interface: A component of Infoprint Server that accepts input from remote TCP/IP workstations or from UNIX System Services printing commands. It creates output data sets on the JES spool.
�print job: One or more documents submitted in the same job to be printed on the same printer.
�print labeling: A controlled method of placing identification labels on each page of PSF printed output.
�PrintManager: The collective name for a set of IBM programs or operating system functions that provide cross-system print management for an entire organization.
�print option: A specification for printing a document.
�printout format definition (PFD): In AFP Utilities, a file member that contains information about the record layout, page layout, record selection, and database file name. A PFD is used to print the records of a database file member in various formats.
�print position: Any location on a medium where a character can be printed.
�print quality: The measure of the quality of printed output relative to existing standards and in comparison with jobs printed previously.
�print queue: A list of print jobs waiting to be printed.
�Print Services Facility (PSF): (1) An IBM licensed program that manages and controls the input data stream and output data stream required by supported IBM page printers.; (2) A feature of i5/OS that provides AFP system management and IPDS print management to IPDS printers that are connected to System i systems.
�print share: An output queue that is shared with PC clients on the network.
�print text: An option that allows the user to specify a line of text at the bottom of a list.
�PrintWay: See IP PrintWay.
�priority: A rank assigned to a task that determines its precedence in receiving system resources.
�priority aging: A scheduling function used to ensure that waiting jobs will be selected to run before those jobs that have just entered the system.
�priority level resource (PLR): A marked resource known to PSF and deleted according to a modified deletion algorithm. When resources according to reasonable resource loaded value, PSF deletes all non-PLR resources before deleting any PLR resources. A frequently used resource can be marked as PLR with the Resource Exit; this improves its chances of being retained at the data set end.
�priority queue: In SNADS, a queue that contains distribution queue entries for distributions with a service level of fast, status, or data high. When send times and queue depths are satisfied for both the priority and normal queues, the priority queue is serviced first. See also normal queue.
�pristine tool: A tool for creating both a repository and the diskettes for installing an operating system remotely.
�privacy: In DCE Remote Procedure Call (RPC), a protection level that encrypts RPC argument values in secure RPC communications.
�privacy policy: In a privacy management environment, an organization's stated position on how it intends to use the privacy-sensitive information that it collects. A privacy policy constitutes an agreement between an organization and the owners of personally identifiable information (PII) that the organization collects. See also opt in, opt out, P3P privacy policy.
�privacy policy statement: See usage statement.
�privacy-sensitive information: In a privacy management environment, information that is classified for protection from general and unauthorized use. In the Platform for Privacy Preferences (P3P) specification, privacy-sensitive information is referred to as personally identifiable information (PII). See also personally identifiable information, Platform for Privacy Preferences.
�private: (1) Pertaining to a member of a class that is accessible only to member functions and friends of that class.; (2) Property of a software entity that is visible only to other software entities which share the same owner. See also owner.
�private area: In CICS Transaction Server, a major element of MVS/ESA virtual storage below the 16MB line. It contains the local system queue area (LSQA), scheduler work area, subpools 229 and 230, a 16KB system region area, and a private user region for running programs and storing data. See also shared area.
�private authority: The authority specifically given to a user for an object that overrides any other authorities, such as the authority of a user's group profile or an authorization list. See also owner authority, primary group authority, public authority.
�private automatic branch exchange (PABX): An automatic private switching system that services an organization and is usually located on a customer's premises. Often used synonymously with private branch exchange.
�private branch exchange (PBX): A switching system located on a customer's premises that consolidates the number of inside lines (extensions) into a smaller number of outside lines (trunks). Many PBXs also provide advanced voice and data communications features.
�private buffer pool: An area of local storage, used for VSO DEDB data, that can provide lookaside capability for shared VSO areas.
�private business object: (1) In XSD, a business object attribute that defines an anonymous complex type instead of referencing a named complex type.; (2) A business object that is contained within other business objects. Private business objects are visible only to the containing business object, thereby making them private. See also business object.
�private connection: A connection known only to the two nodes making the connection.
�private device: A device that supports arbitrated loop protocol and can interpret 8-bit addresses, but cannot log into the fabric.
�private folder: A folder that users design and save for their own use with a Notes database.
�private IP address: An Internet Protocol (IP) address used to communicate on a private network.
�private key: (1) In secure communication, an algorithmic pattern used to encrypt messages that only the corresponding public key can decrypt. The private key is also used to decrypt messages that were encrypted by the corresponding public key. The private key is kept on the user's system and is protected by a password. See also key, public key.; (2) In computer security, a key that is known only to its owner. See also public key.; (3) In computer security, the secret half of a cryptographic key pair that is used with a public key algorithm. The private key is known only to its owner. Private keys are typically used to digitally sign data and to decrypt data that has been encrypted with the corresponding public key. See also public key.
�private library: A user-owned library that is separate and distinct from the system library.
�private loop: A Fibre Channel Arbitrated Loop (FC-AL) with no fabric attachment.
�private loop direct attach (PLDA): A subset of the Fibre Channel standards for the operation of peripheral devices.
�privately defined object: See locally defined object.
�privately managed context: A work context that can be switched from one task to another. A privately-managed context is generally used by a work manager, such as the Information Management System (IMS).
�private management domain (PRMD): In OSI X.400, a private company or noncommercial organization that handles a management domain.
�private methods and instance data: In object-oriented programming, methods and instance data that are only accessible to the implementation of the same class.
�private network: A network established and operated by a private organization or corporation for users within that organization or corporation. See also public network.
�private NL_port: A node loop port (NL_port) that communicates only with other private NL_ports in the same loop and does not log into the fabric.
�private object: (1) In the DCE X/Open Directory Service (XDS), an object management (OM) object created in the workspace using the OM functions.; (2) In DCE X/Open Object Management (XOM), an object that is represented in an unspecified fashion.
�private partition: In VSE, a partition allocated for the execution of a specific program or application program. Storage in a private partition is not addressable by programs running in other virtual address spaces. See also shared partition.
�private service bundle: A service bundle that is not explicitly mentioned in the customization definition document (CDD), but that is included in a service bundle set and provides resources required by another service bundle. In a customization definition report, private service bundles are listed, and their names are followed by the string [private].
�private sort: A sort that takes place in a database agent's agent private memory. See also agent private memory.
�private storage pool: A storage pool containing a specified amount of storage that can be used by only one subsystem. See also shared storage pool.
�private view: A view that users design and save for their own use with a Notes database.
�private volume: A tape volume that has been assigned the private use attribute by the software. If a cartridge resides in a tape library, it is assigned to the private category.
�privilege: (1) The right to access a specific database object in a specific way. Privileges are controlled by users with SYSADM (system administrator) authority or DBADM (database administrator) authority or by creators of objects. For example, privileges can include rights to create, delete, and retrieve data from tables.; (2) The capability of performing a specific function, sometimes on a specific object. See also authority level, authorization.; (3) In SQL, a capability given to a user by the processing of a GRANT statement.
�privilege attribute certificate (PAC): A digital document that contains a principal's authentication and authorization attributes and a principal's capabilities.
�privilege class: A level of authority that is granted to an administrator. The privilege class determines which administrative tasks the administrator can perform. For example, an administrator with system privilege class can perform any administrative task.
�privileged attribute certificate (PAC): A privileged document that contains such information as the client's name and the groups to which it belongs. Its format is dependent on the underlying security mechanism.
�privileged user: A user logged into an account with root user authority.
�privilege set: (1) For the predefined SYSADM ID, the set of all possible privileges. For any other authorization identifier, the set of all privileges that are recorded for that identifier in the DB2 for z/OS catalog.; (2) A collection of privileges for working with system components and functions. The administrator assigns privilege sets to users (user IDs) and user groups.
�privilege ticket: In DCE Security, a ticket that contains a privilege attribute certificate in addition to the information contained in a simple ticket.
�PRM: See program resolution monitor.
�PRMD: See private management domain.
�probe: (1) A type of message that determines if a message with certain characteristics can be delivered to a specific recipient. This type of message is treated like a user message by the message transfer agent (MTA), except that it is never delivered to the recipient.; (2) A monitor that tests a transaction and then detects and reports any errors that were generated during that test.; (3) A reusable set of Java code fragments and supporting attributes for collecting detailed runtime information about objects, arguments, and exceptions. See also Probekit.
�Probekit: A scriptable framework for doing byte-code insertion to probe the workings of a target program. See also probe.
�problem: An abnormal symptom in a system that is being managed.
�problem analysis: The process of finding the cause of a problem. For example, a program error, device error, or user error.
�problem context: In the Reusable Asset Specification (RAS), a concise description containing the reasons and requirements for which the asset has been developed.
�problem determination: The process of determining the source of a problem. Sources of a problem can include a program component, machine failure, telecommunication facilities, user or contractor-installed programs or equipment, or environmental failure such as a power loss, or user error.
�Problem Determination: A core capability of the IBM Autonomic Computing Initiative that facilitates problem analysis in complex systems using standard situations in the Common Base Event. See also Log and Trace Analyzer tool.
�problem isolation procedure (PIP): Written information used by service representatives to repair IBM equipment. A PIP contains yes/no questions and procedures that direct the user to the failing part of the equipment.
�problem log: A record of problems and of the status of the analysis of those problems.
�problem management: In System Manager, the discipline that manages the detection, analysis, correction, and tracking of problems occurring in an information system environment.
�problem management focal point: The management services responsible for the problem analysis and diagnosis for a sphere of control. An alert focal point is a subset of a problem management focal point.
�problem state: A state during which the processing unit cannot handle input, output, and other privileged instructions.
�procedural programming: In RPG, a programming technique in which the input and output operations are controlled by programmer-specified operation codes instead of by the program cycle.
�procedure: (1) In COBOL, one or more successive paragraphs or sections, within the Procedure Division, that direct the computer to perform some action or series of related actions.; (2) In the Integrated Language Environment (ILE) model, a set of self-contained high-level language (HLL) statements that performs a particular task and returns to the caller. Individual languages have different names for this concept of a procedure. In C, a procedure is called a function.; (3) A sequenced set of statements that may be used at one or more points in one or more computer programs, and that usually has one or more input parameters and yields one or more output parameters. [T]; (4) A routine that can be invoked using the SQL CALL statement to perform operations that can include both host language statements and SQL statements. See also external procedure, SQL procedure, routine.
�procedure call: A call made to a procedure within a module in a bound program. See also program call.
�procedure correlation identifier (PCID): An identifier generated by an SNA control point (CP) to (a) correlate search, activation, and deactivation requests and responses related to a specific session between logical units (LUs), and (b) identify this session for such purposes as problem determination, accounting, and performance monitoring. The PCID and the network-qualified name of the CP generating the PCID constitute the fully qualified procedure correlation identifier (FQPCID), which is unique across the network in which it is used.
�procedure declaration: In the Distributed Computing Environment (DCE) Remote Procedure Call (RPC), the syntax for an operation, including its name, the data type of any value it returns, and the number, order, and data types of any parameters.
�Procedure Division: One of the four main parts of a COBOL program. The Procedure Division contains instructions for solving a problem. The Procedure Division may contain imperative statements, conditional statements, paragraphs, procedures and sections.
�procedure language statement: In query management, a query command that is used in query procedures.
�procedure library (PROCLIB): A program library in direct access storage with job definitions. The reader/interpreter can be directed to read and interpret a particular job definition by an execute statement in the input stream.
�procedure name: In COBOL, a paragraph name or a section name in the Procedure Division.
�procedure order profiling data: A portion of observability that is stored with a program that is produced by Integrated Language Environment (ILE) application profiling. The data lists the order in which the program's procedures were packaged and also indicates how the procedures should be packaged in the future if the program is rebuilt in some way. For example, if procedure A calls procedure B very often, then it is advantageous to package procedures A and B close together.
�procedure pointer call: A high-level language call mechanism for specifying the address of a procedure to be called. The procedure pointer call provides a way to call a procedure dynamically. For example, by manipulating arrays or tables of procedure names or addresses, the application programmer can dynamically route a procedure call to different procedures. See also static procedure call.
�procedure with logic: Any QMF procedure beginning with a REXX comment. In a procedure with logic, it is possible to perform conditional logic, make calculations, build strings, and pass commands back to the TSO or CICS environment.
�process: (1) An instance of a program running on a system and the resources that it uses.; (2) For Common Programming APIs ToolKit, the collection of all i5/OS jobs sharing an activation group.; (3) In System Manager, a combination of systems management applications that accomplishes one or more customer tasks or a part of a task. A process can contain other processes.; (4) See job.; (5) In Business Transaction Services (BTS), a collection of one or more activities. A process is the largest unit that CICS business transaction services can work with, and has a unique name by which it can be referenced and invoked. Typically, a process is an instance of a business transaction.; (6) A progressively continuing procedure consisting of a series of controlled activities that are systematically directed toward a particular result or end.; (7) An address space and single thread of control that executes within that address space, and its required system resources. A process is created by another process issuing the fork() function. The process that issues the fork() function is known as the parent process, and the new process created by the fork() function is known as the child process.; (8) The sequence of documents or messages to be exchanged between the Community Managers and participants to run a business transaction.; (9) A separately executable unit of work.
�process access group (PAG): A group of job-related objects that may be paged in and out of storage in a single operation when a job (process) enters or leaves a long wait.
�process accounting: An analysis of the way that each process uses the processing unit, memory, and I/O resources.
�process case: A possible path through a process, identified by a unique set of process decision outcomes and possibly determined by attributes and values of incoming data.
�process container: A data-container associated with a process. Process containers can be read by all the activities that make up the process. Note that they are not the same as the root activity's containers.
�process database: A database that is used by processes to store artifacts related to their operations.
�process definition: A specification of the runtime characteristics of an application server process.
�process definition object: A WebSphere MQ object that contains the definition of a WebSphere MQ application. For example, a queue manager uses the definition when it works with trigger messages.
�Process Designer: A modeling and code-generation tool with which you create and edit collaboration templates to define their business processes and configurable properties.
�process diagram: A diagram that represents the flow of work for a process. The objects within a process diagram include tasks, processes, connections, business items, resources, and decisions.
�process flow: The representation of interdependencies between activities in a structured format. In WebSphere Business Modeler, the flow always moves forward in time.
�process group: A collection of processes in a system that is identified by a process group ID.
�process group ID (PGID): The unique identifier representing a process group during its lifetime. A process group ID is a positive integer that is not reused by the system until the process group lifetime ends.
�process group lifetime: A period of time that begins when a process group is created and ends when the last remaining process in the group leaves the group because either it is the end of the last process' lifetime or the last remaining process is calling the setsid() or setpgid() functions. X/Open. ISO.1.
�process ID (PID): The unique identifier that represents a process. A process ID is a positive integer and is not reused until the process lifetime ends.
�process identification number (PID): A unique number assigned to a process by the operating system. The number is used internally by processes to communicate.
�processing: The action of performing operations and calculations on data.
�processing engine archive: A .pear zip archive file that includes a Unstructured Information Management Architecture (UIMA) analysis engine and all of the resources required to use it for custom analysis in enterprise search.
�processing instruction: An embedded directive within an XML instance document that is passed to an application when the document is parsed. The processing instruction node is one of the kinds of nodes that are defined in the XQuery and XPath data model. See also node kind.
�processing intent: The attribute defined in the PSB which specifies the program's database access privileges such as insert, delete, and replace.
�processing limit: A transaction attribute that defines how many messages the application program is allowed to process during one program execution.
�processing thread: A connection between an application program and the CICSPlex SM API. A program can establish multiple processing threads, but each one is considered a unique API user; no resources can be shared across the boundary of a thread.
�processing unit: A unit of measure for shared processing power across one or more virtual processors. One shared processing unit on one virtual processor accomplishes approximately the same work as one dedicated processor. A processing unit is equal to one dedicated processor on configurations that do not support virtual processors.
�process instance: A manifestation of a modeled process that is created in a simulated or real environment.
�process lifetime: The period of time that begins when a process is created and ends when the process ID is returned to the system. X/Open. ISO.1 . After a process is created with a fork() function, it is considered active. Its thread of control and address space exist until it terminates. It then enters an inactive state where certain resources may be returned to the system, although some resources, such as the process ID, are still in use. When another process executes a wait() or waitpid() function for an inactive process, the remaining resources are returned to the system. The last resource to be returned to the system is the process ID. At this time, the lifetime of the process ends.
�Process Manager: In WebSphere Voice Server, the process that manages the interaction of all telephony system processes, for example, starting and stopping text-to-speech or speech recognition sessions.
�process manager: A system of managing the execution of a process. A process manager operates the defined and agreed process, ensuring that it interfaces with all other relevant processes, target setting, process audits, effectiveness and efficiency reviews, and managing the process improvement cycle.
�process mode: The mode of operation in which data is processed by output devices.
�process model: A representation of the real-time business process that is composed of the individual steps or activities that make up the process and contains the conditions that dictate when they occur, and identifies the resources required for its performance or execution.
�process module: A program unit that contains a set of process templates that support administrative tasks.
�process object: The logical representation of a Java process. A process object is identified both by name and a process ID number (PID), and appears in the Monitors view along with the associated agents whenever a Java process is launched or attached to.
�processor: (1) A device for processing data from programmed instructions. It may be part of another unit.; (2) One or more integrated circuits that process coded instructions and perform a task.; (3) In a computer, the part that interprets and executes instructions. Two typical components of a processor are a control unit and an arithmetic logic unit.
�Processor Active light: The light on the control panel that comes on when the processing unit is running.
�processor complex: The maximum set of hardware resources that support a single operating system.
�Processor Resource/Systems Manager (PR/SM): A feature that allows a processor to use several MVS images simultaneously and provides logical partitioning capability. See also multi-VSE environment.
�processor storage: See central storage.
�process template: A structured collection of activities and tasks that can be reused for specific process workflows. Process templates can be edited, created, cloned, and removed. Users typically apply and modify a process template when they design a workflow for a specific process.
�process-type: The category to which a process belongs. All the activities in a process inherit the same process-type attribute. Categorizing processes makes it easier to find a particular process or activity - the BTS browsing commands allow filtering by process-type.
�process view: An architectural view that describes the concurrent aspect of the system: processes and their interactions.
�PROCLIB: See procedure library.
�procurement buyer: A defined role in WebSphere Commerce that uses the account belonging to the buyer organization to make purchases from the seller and sends pending orders to the procurement system for approval.
�procurement buyer administrator: A defined role in WebSphere Commerce that registers and approves users as procurement buyers (buy-side). The procurement buyer administrator manages the various users and creates and administers the suborganizations within the buying organization.
�procurement card: See purchasing card.
�product: (1) In System Manager, a program or application that is identified as a product to the i5/OS operating system by a product identifier and a product definition.; (2) A catalog entity that can be viewed as a group of items that share attributes. All items that are related to a particular product exhibit the same set of attributes and are distinguished by their attribute values.; (3) In hardware, a separately orderable item.; (4) A software application that is made up of various components.
�product availability object: A system object used to store information about products and licensed programs. The system-recognized identifier is *PRDAVL.
�product code: The three-character code that uniquely identifies a warehouse enablement pack and keeps the data and schema of one warehouse enablement pack separate from other warehouse enablement packs.
�product comparison metaphor: A metaphor that allows customers to compare the similarities and differences between products.
�product definition: In System Manager, an object that contains the information about a product. The object type is *PRDDFN. A product definition is identified as belonging to a product (PRDID) and a release (RLS). A given product and release can have only one product definition.
�product distribution tape: Tape on which CICS Transaction Server or CICS/VSE is supplied to users as a pregenerated system.
�product exploration metaphor: A metaphor in which customers initiate a parametric search of the product data. This metaphor is intended for customers who are familiar with the features of a given category of products.
�product integrated information: See program integrated information.
�production: In OSI, a part of the formal notation used to specify ASN.1, in which allowed sequences of items are associated with a name that can be used to refer to those sequences in the definition of new sets of allowed sequences.
�production copy: In cross-site mirroring, the independent disk pool to which all production operations are directed. All disk write operations are directed here first and are then replicated to the mirror copy of the independent disk pool. The production copy always has current data.
�production library: A library containing objects needed for normal processing. See also test library.
�production-ready data: Data that is ready to be published from a staging server or an authoring server to a production server. See also production server, staging server, authoring server, task group, commit, workspace task group approver, quick publish.
�production server: A WebSphere Commerce Server containing the set of data and files accessed by customers. See also staging server, authoring server, production-ready data, quick publish.
�production stack: The TCP/IP modules involved in most of the network operations on the System i platform.
�production system: (1) A WebSphere Voice Response system that is used to respond to or make 'live' calls. A production system can also be used to develop new applications. See also development system.; (2) A system on which application programs that are already developed and tested run on a regular basis.
�product load: (1) In System Manager, an object that contains the control information about an option. The object type is *PRODLOD. A product load is identified by the product identifier (PRDID), release (RLS), option (OPTION), and load identifier (LODID) parameters.; (2) The smallest logical collection of objects that can make a product option.
�product manager: A defined role in WebSphere Commerce that is responsible for determining the best way to display, price, and sell products in the online store. The product manager role is equivalent to a merchandising manager.
�product message file: In System Manager, a file containing one or more product descriptions.
�product option: In System Manager, a group of one or more loads, one of which must be a code load.
�product page: A Web page that displays detailed information about a product in an online store.
�product recommendation: A sales and marketing technique in which catalog inventory is suggested to customers based on their profile or on independent criteria.
�product refresh: See manufacturing refresh.
�product requirements document (PRD): A high level description of the product (system), its intended use, and the set of features it provides.
�product-sensitive programming interface (PSPI): A special interface that is intended to be used only for a specialized task, such as diagnosis, modification, monitoring, repairing, tailoring, or tuning.
�product-set identification (PSID): In SNA, a technique for identifying the hardware and software products that implement a network component.
�product support plan bucket (PSP bucket): Storage for the instructions and the program temporary fixed (PTFs) required to migrate to a new software release.
�profile: (1) Data that describes the characteristics of a user, group, resource, program, device, or remote location.; (2) A file containing customized settings for a system or user.; (3) In CICS, a set of options specified in a resource definition that can be invoked by a transaction definition. Profiles control the interactions between the transaction and terminals or logical units.; (4) Acontainer for application-specific information about a particular type of resource. A Tivoli application specifies the template for its profiles, which includes information about the resources that the Tivoli application can manage.; (5) In the Remote System Explorer, a container for a particular user's filter, connection, System i command, and user-defined action information. A profile can also be used to partition data if the number of remote server connections is high.; (6) A set of characteristics that defines how Query Patroller handles a submitter's queries or what tasks an operator can perform. See also operator, submitter.; (7) An object that contains information about the characteristics of the user's session. A stored profile is a profile that has been saved in permanent storage. A profile in temporary storage has the name PROFILE. There can be only one profile for each user.
�profile-directed feedback: A two-stage compilation process that first compiles and runs a program to analyze its behavior and then recompiles the program to optimize its execution. The results of the analysis stage are saved in a profile data file that is input to the second, optimization stage.
�profile element: (1) In DCE Remote Procedure Call (RPC), a record in an RPC profile that maps an RPC interface identifier to a profile member (a server entry, group, or profile in a name service database).; (2) An element or monitoring task belonging to a user profile. The element defines what is to be monitored and when.
�profile handle: A value created by the system from the Get Profile Handle API that is used to identify a valid user ID and password. This value is used as input to switch the controlling user profile in a job to another user profile without changing the name of the job.
�profile manager: (1) In a Tivoli environment, a container for profiles that links the profiles to a set of resources, called subscribers. Tivoli administrators use profile managers to organize and distribute profiles. A profile manager can operate in the dataless mode or database mode.; (2) See computer group.
�profiling: A performance analysis process that is based on statistics for the resources that are used by a program or application.
�profiling agent: An agent that does a performance analysis of, and profiles an application.
�profiling filter: A mechanism for specifying which information about an application will be analyzed.
�PROFS bridge: See VM/MVS bridge.
�program: (1) A sequence of instructions that a computer can interpret and run without a user's intervention.; (2) In the Integrated Language Environment (ILE) model, the executable object that results from binding modules together.; (3) A file containing a set of instructions that conform to a particular programming language syntax.; (4) A prepared sequence of instructions to the system to accomplish a defined task. In POSIX.2, a program encompasses applications written in the shell command language, complex utility input languages, and high-level languages (HLLs).; (5) A single, compilable collection of executable statements in a programming language.
�program automatic storage area (PASA): A system object that contains call level information for each program on the call stack. The PASA can also contain space (allocated when the program object is called) for program variables.
�program call: (1) A call made to an ILE program or to an OPM program. See also procedure call.; (2) A call to a System i program or service program procedure.
�Program Call Markup Language (PCML): A tag language that is used to describe the input and output parameters for programs running on System i models. PCML is based on the Extensible Markup Language (XML). PCML files are used with the ProgramCallDocument class in the IBM Toolbox for Java to automate parameter handling and calls of ILE programs from Java.
�program check: A condition that occurs when programming errors are detected by a processor during execution.
�program communication block (PCB): A control block that contains pointers to Information Management System (IMS) databases. See also program specification block.
�program compression: An operation performed by program control to relieve space in the DSA during a short-on-storage condition. The PPT is searched to identify programs that have been dynamically loaded and are currently not in use. If a program is not in use, the space it occupied is reclaimed. See also short-on-storage.
�program control: (1) A CICS facility that handles the flow of control among application programs.; (2) An RACF function with which an installation can control who runs RACF-controlled programs.
�program control data: In PL/I, data used to affect how a program runs. Program control data is any data that is not string or arithmetic data.
�program-controlled interruption: An interruption that occurs when an I/O channel obtains a channel command word with the program-controlled interruption flag on.
�program control program (PCP): The CICS program that manages CICS application programs.
�program control table (PCT): A CICS table defining the transactions that can be processed by the system. Each transaction is paired with the name of the program that CICS runs when the transaction is called.
�program counter: See instruction address register.
�program cycle: In RPG, the series of operations performed by the computer for each record read.
�program data: Application-specific data that can be associated with a call transfer from Callpath to DirectTalk, or in the opposite direction. This is equivalent to Callpath program data, but DirectTalk imposes the restriction that the data must be a printable ASCII character string, with a maximum length of 512 bytes.
�program-described data: Data contained in a file for which the fields in the records are described in the program that processes the file. See also externally described file.
�program-described file: A file for which the fields in the records are described only in the programs that process the file. To the operating system, the record appears as a character string. See also externally described file.
�Program Development Facility (PDF): An IBM licensed program used with the Interactive System Productivity Facility (ISPF) to provide a work environment for the development of programs and the use of functions, such as edit and browse.
�program device: A symbolic device that a program uses instead of a real device (identified by the device name). When the program uses a program device, the system redirects the operation to the appropriate real device.
�program device override: The attributes specified at run time that change the attributes of the program device.
�program entry procedure (PEP): A procedure provided by the compiler that is the entry point for an ILE program on a dynamic program call. See also user entry procedure.
�program error program (PEP): A user-replaceable program containing code to obtain program addressability, access the COMMAREA, and return control to the CICS abnormal condition program (DFHACP) through an EXEC CICS RETURN command.
�program fetch: A program that prepares programs for execution by loading them at specific storage locations and readjusting each relocatable address constant.
�program file: In EGL, a file that is in EGL source format and that contains a single program part. The program part may embed functions and data parts and may import definitions files. The file name extension is .eglpgm.
�program function key (PF key, PFK): A key on a computer that can be programmed to perform a particular operation.
�program ID: A 1- to 8-character string entered from a finance device and associated with a server finance transaction program. Lists of valid program IDs and their associated application programs are maintained in program tables.
�program identification entry: In COBOL, an entry in the PROGRAM-ID paragraph of the Identification Division that contains clauses that specify the program-name and assign selected program attributes to the program.
�program initialization parameter (PIP): (1) In IBM's Systems Network Architecture, initialization information exchanged between two transaction programs belonging to the same logical unit.; (2) The initial parameter value or values passed to a target program as input or used to set up the process environment.
�program integrated information (PII): User-visible text that is contained within a software program and is integral to the execution of that program.This includes user interface text and messages.
�program interruption: The interruption of the execution of a program due to some event such as an operation exception, an exponent-overflow exception, or an addressing exception.
�program isolation (PI): A DL/I or IMS facility that separates all the activity of an application program from any other active application program until that application program indicates, via a synchronization point, that the data it has modified or created is consistent and complete.
�program isolation lock manager: The facility that was formerly known as PI enqueue-dequeue. The PI lock manager is used for local locking in systems for which no IRLM has been defined. Otherwise, the IRLM is used for all lock management, including local.
�program level: (1) Pertaining to an operation that is performed for an entire program. See also command-level.; (2) The version of a program that is composed of the following levels: the version number, the release number, the modification number, and the fix number.
�program library: A type of partitioned data set extended (PDSE) that contains program objects only. A program library is a PDSE from which programs are loaded into memory for execution by the operating system.
�program list table (PLT): A CICS control table that contains a list of programs that can run as a group during CICS startup or shutdown and can be enabled and disabled as a group by a single CEMT transaction.
�program loading: The use of MVS load under an MVS subtask or a VSE load under a VSE subtask to load programs into CICS storage.
�programmable command format (PCF): A type of WebSphere MQ message used by the following applications: user administration applications, to put PCF commands onto the system command input queue of a specified queue manager, user administration applications, to get the results of a PCF command from a specified queue manager, and a queue manager, as a notification that an event has occurred. See also WebSphere MQ script command.
�programmable terminal: A user workstation that has computational capabilities.
�programmable workstation: A workstation that has some degree of processing capability and allows the user to change its functions.
�program management: (1) The functions within the system that establish the necessary activation and invocation for a program so that it can run when it is called.; (2) The task of preparing programs for execution, storing the load modules or program objects in program libraries, and executing them on the operating system.
�program manager domain: A CICS domain that provides support for the following: program control functions; transaction ABEND and condition handling; related functions such as invoking user-replaceable modules, global user exits, and task-related user exits; autoinstall for programs, mapsets, and partitionsets.
�program mask: In bits 20 through 23 of the program status word (PSW), a 4-bit structure that controls whether each of the fixed-point overflow, decimal overflow, exponent-overflow, and significance exceptions should cause a program interruption. The bits of the program mask can be manipulated to enable or disable the occurrence of a program interruption.
�programmatic emulator: An emulator that uses a Java or visual snippet to automatically specify response values for an emulated component or reference at run time. See also manual emulator, emulator.
�programmatic login: A type of form login that supports application presentation site-specific login forms for the purpose of authentication.
�programmatic security: (1) A collection of methods used by applications when declarative security is not sufficient to express the security model of the application.; (2) Security model using Java enterprise-bean client applications that require the user to provide identifying information. The application must collect that information and authenticate the user.
�programmed function key: On a workstation, a key that can perform various functions selected by the user or determined by an application program.
�programmer subsystem: An IBM-supplied interactive subsystem used to code programs on a display station. The system object name is QPGMR.
�programmer user profile: The system-supplied user profile that has the authority necessary for system and application programmers and the special authorities of save system authority and job control authority. Named QPGMR.
�program message queue: An object used to hold messages that are sent between program calls of a routing step. The program message queue is part of the job message queue.
�Programming Development Manager (PDM): An application that is used in a 5250 emulator to query an i5/OS host and perform actions against objects. See also 5250 display.
�programming interface for customers: The supported method through which customer programs request software services. The programming interface consists of a set of callable services provided with a product.
�programming request for price quotation (PRPQ, programming RPQ): (1) A customer request for a price quotation on alterations or additions to the functional capabilities of system control programming or licensed programs. The PRPQ may be used in conjunction with computing system RPQs to solve unique data processing problems. See also computing system RPQ.; (2) A customer request for a price quotation for a licensed program to be designed especially for a particular group of customers or an application. Documentation for the program is provided only to those customers who order the PRPQ. See also request for price quotation.
�programming RPQ (PRPQ): See programming request for price quotation.
�program module: The output of the binder. A collective term for program object and load module.
�program module attribute: A characteristic of a program module that is stored in directory entry of a program module. The program module attribute controls the loading rebinding and other processing of the module.
�program name: A user-defined word that identifies a COBOL source program.
�program number: The seven-digit code (in the format xxxx-xxx) used by IBM to identify each program product.
�program object: (1) One of two machine object classifications. It includes those objects used in programs that get their definition from an object definition table. Program objects are used as the parameter or values of machine instructions. See also system object.; (2) All or part of a computer program in a form suitable for loading into virtual storage for execution. Program objects are stored in partitioned data set extended (PDSE) program libraries and have fewer restrictions than load modules. Program objects are produced by the binder.
�program operator interface (POI): A VTAM function that allows programs to perform VTAM operator functions.
�program preparation: In DB2 for i5/OS, the process of producing a program. The process includes precompilation, compilation, and bind.
�program profiling: A technique that is used to optimize a program.
�program resolution monitor (PRM): In the original program model (OPM), a program that translates the intermediate representation of a program into the machine language for use by the computer. The program resolution monitor is used by the programming language compilers to complete the translation of a source program into machine language instructions.
�program specification block (PSB): In DL/I and IMS, a control block that describes the databases and logical message destinations that are used by an application program. A PSB consists of one or more program communication blocks (PCBs). See also program communication block.
�program specification block generation (PSBGEN): The process by which a PSB is created.
�program static storage area (PSSA): A system object that contains static variable data for programs on the call stack. The PSSA contains space for program variables that is activated when the program object is activated. The PSSA is contained in the process access group (PAG).
�program status word (PSW): An area in storage used to indicate the order in which instructions are executed, and to hold and indicate the status of the computer system.
�program table: A list of the i5/OS finance applications for use in an i5/OS finance job. Each table entry consists of a program ID and the program name and library associated with that ID. Program IDs received in data streams from finance devices are located in the program table to determine the i5/OS application that should be called.
�program temporary fix (PTF): For System i, System p, and System z products, a fix that is tested by IBM and is made available to all customers. See also fix pack.
�program-to-program message switch: An IMS output message sent by one application program to another application program. See also message switch.
�program unit: (1) In Ada programming, a discrete unit that performs a specific task or set of tasks. Program units are subroutines and calling programs that are assembled separately and then linked to make a complete program.; (2) See compilation unit.
�program update tape (PUT): A code release to Transaction Processing Facility customers containing maintenance (program fixes) and new function. See also Transaction Processing Facility.
�program variable: A named changeable value that can exist only within programs. Its value cannot be obtained or used when the program that contains it is no longer running.
�progressive streaming: A method of retrieving a LOB or an XML value from a database server in the most optimal manner by using Dynamic Data Format. See also Dynamic Data Format.
�project: (1) In Eclipse, a unit of organization used to group folders or packages. Projects are used for building, version management, sharing, and organizing resources.; (2) An object that contains configuration information, activities, and policies required to manage a development effort.; (3) An object that includes a database, documents, document types, requirements and their attributes, requirement types, requirement traceability, discussions, and user and group security.; (4) A container for resources.; (5) An organized collection used to group folders or packages. Projects are used for building, version management, sharing, and organizing resources related to a single work effort.; (6) A temporary endeavor undertaken to produce a unique product or service, within a specified scope.
�project database: The requirements database. The project database stores all requirements in the project, including those created in requirement documents.
�projected coordinate system: In DB2 Spatial Extender, a reference system that defines locations on a planar surface.
�project manager: The role with overall responsibility for the project. The Project Manager needs to ensure tasks are scheduled, allocated and completed in accordance with project schedules, budgets and quality requirements.
�project prefix: An identifier used for requirements in cross-project traceability.
�Project Review Authority (PRA): The organizational entity to which the Project Manager reports. The PRA is responsible for ensuring that a software project complies with policies, practices and standards.
�project root: See source root.
�project versioning: The component that interacts with a CVS or Rational ClearCase server to share and create version projects and project data.
�project VOB (PVOB): A versioned object base (VOB) that stores Unified Change Management (UCM) objects, such as projects, streams, activities, and change sets.
�prolog: A user-written definition of an application program, record, or table. A prolog is used for documentation.
�promote: (1) In application development, to move a part up one level in the project hierarchy.; (2) In ILE, to convert an unhandled exception into a new exception with a different meaning. The new exception is passed on to the next exception handler.; (3) To copy replication definitions for subscription sets or registered sources from one database to another database, without registering the sources again or creating the subscription sets again.; (4) To change a condition to a different one using a condition handler. A condition handler routine promotes a condition because the error needs to be handled in a way other than that suggested by the original condition.; (5) To add a logical data unit to cache memory.
�promoted property: A property of a mediation module made visible by the solution integrator to the runtime administrator, so that its value can be changed at run time.
�promotion: (1) In JavaBeans technology, the process of making features of a contained bean available to be used for making connections. For example, if a bean consisting of three push buttons on a panel is placed in a frame, the features of the push buttons have to be promoted to make them available from within the frame.; (2) Business logic that offers incentives to customers when certain conditions have been satisfied.; (3) The process of one host taking over level functions for another. See also demotion, level function.
�promotion context: A transient object that only exists when the promotion engine is called to evaluate whether promotions are applicable to an order. It captures the state of the promotion engine during the process.
�promotion control block (PCB): A shadow object of the promotion context that provides a controlled change management environment for the promotion context.
�promotion engine: A promotion architecture that uses XML-based promotion definitions and enables customer-specific extension.
�promotion group: A logical container that holds promotions of similar natures.
�promotion policy: Business logic that governs how multiple promotions should be applied to a single order.
�prompt: (1) A message or a displayed symbol that requests information or user action. The user must respond to allow the program to proceed.; (2) In WebSphere Voice Response, a program that uses logic to determine dynamically the voice segments to be played as a voice prompt.; (3) A component of an action that indicates that user input is required for a field before making a transition to an output screen.
�prompt directory: A list of all the prompts used in a particular voice application. Used by the state table to play the requested voice prompts.
�prompted query: A menu-driven query controlled by user-provided parameters.
�prompt facility: An optional facility for notifying a terminal operator that a current page of output is the last page of a message.
�PROMPT mode: One of two ways to display a message panel. PROMPT mode is intended for SWIFT Link users who are unfamiliar with the structure of SWIFT messages. With PROMPT mode, all the fields and tags are displayed for the SWIFT message. See also NOPROMPT mode.
�pronunciation: The possible phonetic representations of a word. A word can have multiple pronunciations; for example, "the" has at least two pronunciations, "thee" and "thuh".
�pronunciation dictionary: A file that contains the phonetic representation of all the words, phrases, and sentences for an application's grammars.
�pronunciation pool: A WebSphere Voice Server resource that contains the set of all pronunciations.
�Proof of Entitlement (POE): A document that validates the licensed programs that a customer has purchased.
�propagation: (1) A process in which groups of configuration parameters are updated and take effect at different rates.; (2) The escalation of resource-related information such as alerts or status.
�propagation agent: An agent that checks the incoming events against resource criteria, such as threshold level, priority level, and state. If the resource criteria are met, the propagation agent changes the state of a resource and generates subsequent child events that are sent to the event stream and re-evaluated by the propagation agents.
�property: (1) A characteristic of an object that describes the object. A property can be changed or modified. Properties can describe an object's name, type, value, or behavior, among other things.; (2) A characteristic or attribute that describes a unit of information.; (3) Any configurable information about a WebSphere business integration component. A component typically has properties that are common to all components of that type (for example, standard connector properties) as well as properties that are specific to that component (for example, connector-specific properties). See also business object property, collaboration property, standard property.; (4) In the Common Information Model (CIM), an attribute that is used to characterize instances of a class.
�property broker: A WebSphere Portal interface that negotiates the relationship between cooperative source and target portlets and delivers data to the target in the form of the corresponding portlet action. See also cooperative portlets.
�property set: In the CICS/ESA Front End Programming Interface (FEPI), the definition of the characteristics of a pool.
�property-to-property connection: A connection from a property of one object to a property of another object.
�proportionally spaced font: A font in which the character increment for each graphic character varies. Proportionally spaced fonts provide the appearance of even spacing between presented characters and eliminate excess blank space around narrow characters, such as the letter i.
�proportional spacing: The spacing of characters according to their relative width.
�proposal: A proposal is a collection of protocols that the initiating and responding key servers use to establish a dynamic virtual private network (VPN) connection between two endpoints.
�proposed abstract syntax list: In OSI, a list of abstract syntaxes that an application entity specifies as acceptable when initiating an association.
�proposed matching: Automatically determining whether each incoming credit payment corresponds to a received advice and, if so, and if the amount of the payment is high enough, proposing that the payment might be a match for the advice. Such proposed matches must be confirmed manually by the user to be effective. Matched advices are disregarded when calculating expected end-of-day-positions.
�protected: Pertaining to a class member that is accessible to the class itself, subclasses, and all classes in the same package.
�protected buffer pool (PBUF): An area in the common storage and auxiliary space that has been divided into buffers.
�protected column: In label-based access control, a column to which access is limited by means of a security label.
�protected conversation: A type of conversation that supports the two-phase commit process for the synchronization of changes.
�protected field: A field on a display in which a user cannot add, change, or delete data.
�protected file: A file that cannot be changed by an override file command.
�protected logical unit of work (protected LUW): The logical unit of work that is used in a protected conversation.
�protected logical unit of work identifier (protected LUWID): The logical unit of work identifier that is used in a protected conversation.
�protected LUW: See protected logical unit of work.
�protected LUWID: See protected logical unit of work identifier.
�protected methods and instance data: In object-oriented programming, methods and instance data that are only accessible to the implementations of the same or derived classes, or from friend classes.
�protected object: The logical representation of an actual system resource that is used for applying ACLs and POPs and for authorizing user access. See also protected object policy, protected object space.
�protected object policy (POP): A type of security policy that imposes additional conditions on the operation permitted by the ACL policy to access a protected object. It is the responsibility of the resource manager to enforce the POP conditions. See also protected object, protected object space, multi-factor authentication.
�protected object space: The virtual object space representation of actual system resources that is used for applying ACLs and POPs and for authorizing user access. See also protected object policy, protected object.
�protected password: In APPC, a string of bytes that is substituted for a user password. The protected password is sent instead of the user password and can be used to verify the identity of the user but only under specific and controlled circumstances. The LU type 6.2 architecture refers to the protected password as a password substitute.
�protected resource: (1) A resource that is updated in a synchronized manner during resource recovery processing.; (2) A resource that is updated only in accordance with the two-phase commit process.; (3) A local or distributed resource for which updates are synchronized and controlled.
�protected row: In label-based access control, a row to which access is limited by means of a security label.
�protected storage: (1) The part of the auxiliary storage pool (ASP) that is reserved for the creation of permanent objects, such as libraries and files, when checksum protection is in effect.; (2) All auxiliary storage in an auxiliary storage pool (ASP) when mirrored protection is in effect.
�protected table: In label-based access control, a table that contains at least one row or one column to which access is limited by means of a security label.
�protected volume: In iSeries, a disk storage device that is protected from data loss by the use of a Redundant Array of Independent Disks (RAID). An iSeries host does not mirror a volume configured as a protected volume, while it does mirror all volumes configured as unprotected volumes. The ESS, however, can be configured to indicate that an iSeries volume is protected or unprotected and provide it with RAID protection in either case.
�protection key: An indicator that appears in the current program status word whenever an associated task has control of the system. This indicator must match the storage keys of all main storage blocks that the task is to use.
�protection level: The degree to which secure network communications are protected.
�protection setup: In Internet communications, a group of protection subdirectives that work together to define how the server should control access to the resources being protected.
�protect mode: In DFSMSrmm, the state in which all volume requests are validated.
�protocol: (1) A set of rules controlling the communication and transfer of data between two or more devices or systems in a communication network.; (2) In OSI, a specification of the format and relative timing of information exchanged between peer entities within a layer.
�Protocol 1 (P1): (1) The message transfer protocol used to relay X.400 messages between message transfer agents (MTAs).; (2) In MERVA Link, a peer-to-peer protocol used by cooperating message transfer processes (MTPs).
�Protocol 2 (P2): (1) The message protocol used between user agents to convey the syntax and structure of an X.400 message and to specify what a recipient user agent does with the message.; (2) In MERVA Link, a peer-to-peer protocol used by cooperating application support processes (ASPs).
�protocol boundary: The signals and rules governing interactions between two components within a node.
�protocol converter: A general term for a device that changes one type of coded data to another type of coded data for processing.
�protocol data unit (PDU): (1) A unit of data exchanged between peer systems.; (2) In OSI, a unit of data exchanged between peer entities.; (3) In MERVA Link. a structured sequence of implicit and explicit data elements: Implicit data elements contain other data elements, and explicit data elements cannot contain any other data elements.
�protocol gateway: A type of firewall that protects computers in a business network from access by users outside that network.
�protocol handler: In the WebSphere business integration system, protocol handlers receive and send messages in specific communication protocols--such as HTTP and HTTPS--and call data handlers to extract the data contained in the messages.
�protocol sequence vector: In DCE Remote Procedure Call (RPC), a data structure that contains an array-size count and an array of pointers to RPC protocol-sequence strings.
�prototype: A function declaration or definition that includes both the return type of the function and the types of its parameters.
�prototype profile: In a Tivoli environment, a model profile from which a Tivoli administrator can create other like profiles, often by cloning the existing profile.
�provision: To provide, deploy, and track a service, component, application, or resource. See also deprovision.
�provisioning: (1) The process of setting up and maintaining a user's access to a system.; (2) The process of configuring servers, software, networks, and storage resources.
�provisioning management: The management principle that combines three key elements -- business logic, workflow management, and distribution agents -- which together centrally manage the provisioning of users with access to information and business resources.
�provisioning policy: A policy that defines the access to various managed resources, such as applications or operating systems. Access is granted to all users, users with a specific role, or users who are not members of a specific role.
�provisioning server: (1) A server that manages the identity characteristics of users and servers for the purpose of provisioning software.; (2) The server on which Tivoli Provisioning Manager is installed.
�provisioning service: A reserved application that is set up for a specific business requirement and is made available to a user. Users with restricted access in the data center model can subscribe to provisioning services that they require.
�proxiable ticket: A ticket that allows a key distribution center (KDC) server to issue a service ticket for a specific task or tasks on a network or for an IP address that is different from the address in the original ticket granting ticket (TGT).
�proximity search: A text search that returns a result when two or more matching terms occur within a certain distance from each other, such as in the same sentence or paragraph.
�proxy: An application gateway from one network to another for a specific network application such as Telnet or FTP, for example, where a firewall's proxy Telnet server performs authentication of the user and then lets the traffic flow through the proxy as if it were not there. Function is performed in the firewall and not in the client workstation, causing more load in the firewall.
�proxy agent: A process or entity that is both an agent to its manager and a manager for one or more objects. It satisfies requests from its manager by relaying those requests and translating them for the objects that it manages.
�proxy cluster: A group of proxy servers that distributes HTTP requests across the cluster.
�proxy endpoint: In a Tivoli environment, a representation for an entity (such as a network device or a host) that functions as a subscriber for profiles. The proxy endpoint is created on a managed node, which performs the proxy role during profile distribution. Multiple proxy endpoints can be created on the same managed node.
�proxy gateway: A firewall that prevents users outside a private network from accessing computers within the private network.
�proxy managed node: In a Tivoli environment, a managed resource that provides communication between the Tivoli server and a PC that is running the PC agent.
�proxy peer access point: A means of identifying the communication settings for a peer access point that cannot be accessed directly.
�proxy server: (1) A server that receives requests intended for another server and that acts on the client's behalf (as the client's proxy) to obtain the requested service. A proxy server is often used when the client and the server are incompatible for direct connection. For example, the client is unable to meet the security authentication requirements of the server but should be permitted some services.; (2) A server that acts as an intermediary for HTTP Web requests that are hosted by an application or a Web server. A proxy server acts as a surrogate for the content servers in the enterprise.
�proxy store: A store that represents a business partner's operational assets and handles the business logic that allows a WebSphere Commerce site to interact with an external business partner. A proxy store does not include a storefront and cannot be accessed by users. See also distributor proxy store.
�PRP: See prepared.
�PRPQ (programming RPQ): See programming request for price quotation.
�PR/SM: See Processor Resource/Systems Manager.
�pruning: In replication, the task of removing obsolete data from replication control tables or log files that are used by the Capture, Q Capture, Apply, and Q Apply programs.
�PSA: See prefixed save area.
�PSAP: See presentation-layer service access point.
�PSAP selector: In OSI, an external identifier for a service access point at the Presentation Layer. The PSAP selector is part of a presentation address.
�PSB: See program specification block.
�PSB directory (PDIR): A list or directory of program specification blocks (PSBs) that define the use of databases by application programs for DL/I. It contains one entry for each PSB to be used during CICS execution, and is loaded during initialization.
�PSBGEN: See program specification block generation.
�PSDN: See packet-switched data network.
�PSDU: See presentation-layer service data unit.
�pSeries: The IBM server family that uses IBM's POWER architecture designed for AIX and Linux operating systems.
�pseudo attribute: An attribute that cannot have a value, and is used to indicate a binary state such as yes/no or on/off. For example, the attribute local might be present for some resources and absent for others, indicating whether the resource is local. Pseudo attributes are especially useful for implementing access rights, such as read, update, or delete.
�pseudo-CL variable: In REXX, a variable used in CL commands, whose name conforms to the CL programming rules for variables but actually refers to a REXX variable. The name must begin with an ampersand, but it is stripped off when determining the name of the actual REXX variable that is to be used. Pseudo-CL variables must be valid REXX variable names and valid CL variable names.
�pseudocode: A set of instructions that has a logical structure but does not follow the syntax of any particular programming language.
�pseudoconversational: In BTS, property of a task can be reattached ("reactivated") when a predefined event occurs, in order to take the next in a set of processing steps. See also activation.
�pseudoconversational design: A type of CICS application design that appears to the user as a continuous conversation, but that consists internally of multiple tasks. See also conversational.
�pseudo deleted: Pertaining to a key that is marked as deleted but has not yet been physically removed from the index page. See also pseudo empty.
�pseudo empty: Pertaining to an index page on which all the keys are marked as pseudo deleted. See also pseudo deleted.
�pseudo-front-end system: An IMS in a multisystem environment in which all terminals are handled and a small number of time-consuming transactions are routed to a transaction processing system. See also front-end system, transaction processing system.
�pseudo-generation data group: A collection of data sets, using the same data-set name pattern, that are managed like a generation data group.
�pseudo-host: A host connection that is not explicitly defined to the ESS and that has access to at least one volume that is configured on the ESS. For example, the FiconNet pseudo-host icon represents the FICON protocol. See also access-any mode, anonymous, EsconNet, FiconNet.
�pseudo-JCL: In EGL, a language that is similar to standard JCL in appearance, with some extensions and restrictions, and that is used in build scripts run by an MVS build server.
�pseudo optical library: A set of shelf-resident optical volumes associated with stand-alone, operator-accessible, or both stand-alone and operator-accessible optical disk drives. See also real optical library.
�pseudorandom number: A number that is obtained by some defined arithmetic process, but is effectively a random number for the purpose for which it is required.
�pseudorecovery token: A token consisting of eight decimal characters, which can be used in place of the recovery token in certain circumstances. For example, a pseudorecovery token is displayed when the status of an application thread is in-doubt. It is made shorter so that it is easier to note and enter, for example, in certain DBCTL commands. See also recovery token.
�pseudoregister: An external dummy section used to provide global addressability to dynamically allocated control blocks, data areas, and other resources.
�pseudo-state: A vertex in a state machine that has the form of a state, but doesn't behave as a state. Pseudo-states include initial and history vertices. See also vertex.
�pseudo-text: In COBOL, a sequence of character-strings and/or separators bounded by, but not including, pseudo-text delimiters. Pseudo-text is used in the COPY REPLACING statement for replacing text strings.
�pseudo-text delimiter: In COBOL, two equal signs (==) side by side used to define the beginning and end of pseudo-text.
�PSF: See Print Services Facility.
�PSF Direct: A function of Infoprint Manager for Windows or Infoprint Manager for AIX that enables another PSF program to print remotely.
�PSH: See physical services header.
�PSID: See product-set identification.
�PSINDEX: See partitioned secondary index.
�PSM: See Printing Systems Manager.
�PSP bucket: (1) See preventive service planning bucket.; (2) See product support plan bucket.
�PSPDN: See packet switched public data network.
�PSPI: See product-sensitive programming interface.
�PSRCP: See page set recovery pending.
�PSSA: See program static storage area.
�PST: (1) See pattern storage.; (2) See partition specification table.
�PSTN: See public switched telephone network.
�PSW: See program status word.
�PT: See partner table.
�PTERM: See physical terminal.
�PTF: See program temporary fix.
�PTF group: A single, orderable PTF (program temporary fix or simply, fix) that provides a logical set of PTFs for a specific function such as database or Java. PTF groups are dynamically updated when new PTFs for the same function become available.
�PTF media: The diskette, tape, or CD-ROM on which the user receives program temporary fixes (PTFs).
�pthread: A shortened name for the i5/OS threads API set that is based on a subset of the POSIX standard.
�PTOCA: See Presentation Text Object Content Architecture.
�PtP DATA: See Peer-to-Peer VTS data.
�PtP MC: See Peer-to-Peer VTS mode control.
�PtP VTS: See Peer-to-Peer Virtual Tape Server.
�PTT: (1) See Post Telephone and Telegraph Administration.; (2) See Postal, Telephone, and Telegraph.
�PU: See physical unit.
�public: (1) In object-oriented programming, pertaining to a class member that is accessible to all classes.; (2) In the Java programming language, pertains to a method or variable that can be accessed by elements residing in other classes. (Sun)
�public access: The access privilege in a database access control list (ACL) that includes Depositor access and No Access and that allows reading, writing, and copying public documents.
�Public Address Book: See Domino directory.
�publication: A piece of information about a specified topic that is available to a broker in a publish/subscribe system.
�publication node: An end point of a specific path through a message flow to which a client application subscribes, identified to the client by its subscription point.
�public authority: The authority given to users who do not have any specific (private) authority to an object, who are not on the authorization list (if one is specified for the object), and whose group profile has no specific authority to the object. See also owner authority, primary group authority, private authority.
�public data network (PDN): (1) A communications common carrier network that provides data communications services over switched or nonswitched lines.; (2) A network operated by a government or private organization to provide computer communications to the public, usually for a fee. With a PDN, a small organization can create a WAN without incurring the equipment costs of long-distance circuits.
�public device: A device that supports arbitrated loop protocol, can interpret 8-bit addresses, and can log into the fabric.
�public group: (1) A group of people who are designated as a group in a company's corporate Directory. See also personal group.; (2) A group of individuals, known to all portal users, that the administrator has created or that exists in the organization's corporate directory. Only administrators can modify and manage public groups. See also personal group, person.
�public interface: The names of procedures and data items, exported from an ILE service program, that can be accessed by Integrated Language Environment (ILE) programs or other service programs.
�public IP address: An Internet Protocol (IP) address used to communicate on a public network.
�public key: (1) In secure communication, an algorithmic pattern used to decrypt messages that were encrypted by the corresponding private key. A public key is also used to encrypt messages that can be decrypted only by the corresponding private key. Users broadcast their public keys to everyone with whom they must exchange encrypted messages. See also key, private key.; (2) In computer security, a key that is made available to everyone. See also private key.; (3) The non-secret half of a cryptographic key pair that is used with a public key algorithm. The public key is made available to everyone. Public keys are typically used to verify digital signatures or decrypt data that has been encrypted with the corresponding private key. See also private key.; (4) An encryption key associated with a Notes ID that is used to verify an electronic signature, encrypt a message, or identify an authenticating user. A public key is part of each user ID, and a copy of the key is stored in the Domino Directory. Certificates on IDs ensure that public keys are valid.
�public key algorithm: An algorithm designed so that the key used for encryption is different from the key used for decryption. The decryption key cannot be derived, at least not in any reasonable amount of time, from the encryption key.
�public key certificate: A unique electronic stamp stored in a Notes or Domino ID file that associates a name with a public key. Certificates permit users and servers to access specific Domino servers. An ID can have many certificates.
�public key cryptography: A cryptography system that uses two keys: a public key known to everyone and a private or secret key known only to the recipient of the message. The public and private keys are related in such a way that only the public key can be used to encrypt messages and only the corresponding private key can be used to decrypt them.
�Public Key Cryptography Standards (PKCS): A set of industry-standard protocols used for secure information exchange on the Internet. Domino Certificate Authority and Server Certificate Administration applications can accept certificates in PKCS format.
�public key exponent: One of the two components of an RSA public key. By convention, it is normally set to either a value of 3 or 65537. The combination of the public key exponent and the modulus (the other component of a public key) is mathematically derived with the corresponding RSA private key.
�public key infrastructure (PKI): A system of digital certificates, certification authorities, and other registration authorities that verify and authenticate the validity of each party involved in a network transaction.
�public loop: A Fibre Channel Arbitrated Loop (FC-AL) with an attachment to a fabric.
�public methods and instance data: In object oriented programming, methods and instance data that are accessible to all classes.
�public network: Generically, a network operated by common carriers or telecommunications administrators for the provision of circuit-switched, packet-switched, and nonswitched lines to the public. See also private network.
�public NL_port: A node loop port (NL_port) that logs into the fabric, can function within either a public or a private loop, and can communicate with either private or public NL_ports.
�public place: A shared place that is open to all portal users. The person who creates the place (and who automatically becomes the place manager) designates it as a public place during place creation. See also restricted place.
�public-private key cryptography: See public key cryptography.
�public switched telephone network (PSTN): A communications common carrier network that provides voice and data communications services over switched lines.
�public VLAN: The virtual local area network (VLAN) that connects the cluster nodes and management server to the site network. Applications are accessed and run on cluster nodes over the public VLAN. The public VLAN can be connected to nodes through a second Ethernet adapter in each node, or by routing to each node through the Ethernet switch.
�publish: (1) To make a Web site public, for example by putting files in a path known to the HTTP server.; (2) In UDDI, to advertise a Web service so that other businesses can find it and bind with it. Service providers publish the availability of their services through a registry.; (3) To make data available to another application or system. See also subscribe.; (4) To bind a reference to the home of an enterprise bean in a namespace.; (5) To make a project, tasks and templates visible to the required resources.
�publish-and-subscribe interaction: A type of interaction used for moving information about application events into the WebSphere business integration system for processing. Collaborations subscribe to events, and connectors publish events to subscribed collaborations.
�published model: A model that has been frozen. This model becomes available for instantiating repositories and for defining other models. Elements in this model cannot be changed.
�published offering: An offering with a complete and valid schedule, component, and service level objective information. It can be used to create a service level agreement.
�publishing queue map: In event publishing, an object that contains the settings for how a Q Capture program processes transactions and identifies the WebSphere MQ queue that is used to send transactional data. See also event publishing, replication queue map, queue map.
�publish/subscribe: A type of messaging interaction in which information, provided by publishing applications, is delivered by an infrastructure to all subscribing applications that have expressed interest in that type of information.
�pull: A network operation that initiates an action by requesting the action from a resource. See also push.
�pull configuration: In SQL replication, a configuration in which the Apply program runs on the target server. The Apply program pulls updates from the source server to apply them to the target. See also push configuration.
�pull-down menu: In a character-based interface, a menu that emerges in a downward direction from a point or line at or near the top of the screen; for example, a menu that appears when the user selects a particular display element or points to a line in another menu by using a device such as a mouse.
�pull list: A list of scratch volumes to be obtained for use from the library.
�pulse code modulation: Variation of a digital signal to represent information.
�purchasing card (p-card): A credit card that a business can offer its departments or employees to allow them to buy business-related items.
�pure virtual function: A virtual function is declared pure by replacing the function definition with '=0;'.
�pureXML: A DB2 feature in which the representation of the data from client to disk and back--that is, both the logical and physical data models--is XML.
�purge: (1) In Performance Tools, a job attribute that specifies whether a job is to be marked eligible to be moved out of main storage to auxiliary storage when entering a long wait or leaving the activity level.; (2) The abnormal end of a task by task control to alleviate a short-on-storage condition.; (3) In WebSphere Commerce Payments, to remove all associated payments and credits from a batch object, treating it as if it has just been created.
�purge DSP: A dynamic support program (DSP) that performs post-execution removal of a job from the system, writes System Management Facility (SMF) records, and frees spool space used by the job.
�purger: A function of the resource manager that removes objects from the system.
�push: (1) To add an item to the top of a pushdown list. See also pop.; (2) To upload or export to a server.; (3) A network operation that sends information to resources. See also pull.
�push button: (1) In a window or dialog box, a rectangular control that, when clicked, immediately causes an action to be performed. Push buttons can be labeled with text, graphics, or both. The most familiar push buttons are OK and Cancel.; (2) A key on a telephone key pad.
�pushbutton telephone: A type of telephone that has pushbuttons. It might or might not send tone signals. If it does, each number and symbol on the key pad has its own specific tone.
�push configuration: In SQL replication, a configuration in which the Apply program runs on the source server or a replication server other than the target server. The Apply program pushes updates from the source server to apply them to the target. See also pull configuration.
�pushdown list: A list that is constructed and maintained so that the next data element to be retrieved is the most recently stored. See also last-in first-out.
�push-down processing: In a federated system, the processing of segments of a query at a data source instead of at the federated server. See also compensation, global optimizer.
�PUT: See program update tape.
�PU type: See physical unit type.
�PV: See persistent verification.
�PVC: See permanent virtual circuit.
�PVOB: See project VOB.
�PXE: See Preboot Execution Environment.

�

Back to top�