P

PA key

See program attention (PA) key.

packet-data-movement buffer

The CSA (z/OS), the SVA (z/VSE version 2.1 or later), or the area in a storage pool that DC/UCF uses to communicate with external request units.

page

A logical division of the database that corresponds to a physical block in a file. An area is made up of a range of contiguous pages. All pages within an area have the same size, but page size can vary from one area to another.

page field

In the Mapping Facility, a pageable-map field that displays the current page number and permits the operator to select another page for display.

page group

An attribute of a segment that uniquely identifies a collection of page ranges. In a multiple-database environment, a segment can be associated with only one page group, while a page group can be associated with more than one segment; that is, page groups allow a page range to occur more than once.

page identifier

A unique two-character (alphabetic) identifier that specifies the position of a (paper) page in a CA IDMS Schema Mapper data structure diagram. The first character identifies the page's column (which runs down the length of the diagram), and the second character identifies the page's row (which runs across the width of the diagram).

page lock

A logical lock used by CA IDMS/DB to protect the contents of a database page while it resides in a Data Sharing group member's buffer pool.

page number

A unique, system-assigned number for a database page.

page range

1) The range of pages, from beginning to end, in a database area. 2) A subgroup of pages in a database area.

page reserve

The specified number of bytes per page designated specifically for expansion of variable-length records. Page reserves minimize fragmentation of variable-length records during update functions. The designation of a page reserve does not affect the physical structure of the database.

pageable map

In CA ADS, a map that can contain unlimited occurrences of a set of map fields. A pageable map can contain more detail occurrences than can fit on the terminal screen at one time; the terminal operator can move from page to page to view all the detail occurrences.

panel

An IDD entity type that associates documentational entries and users with maps used in the 3270-type terminal environment. In IDD, the terms panel and screen are synonymous.

parent

A logical database design term that refers to a referenced table in SQL database design and an owner record in non-SQL database design. See also child, owner record, referenced table.

participant

In a two-phase commit, a resource or transaction manager other than the coordinator. A participant is sometimes referred to as an agent. See also coordinator.

passkey

In CA ICMS, a catalog entity that represents permission for users to access information or to perform administrative tasks. See also catalog access passkey, data access passkey.

PassTicket

A time-limited and single-use substitute for a password. PassTickets are typically used in situations where it is desired to avoid sending a multi-use password without any time limitation across a computer network in clear text. An authorized program (not CA IDMS) generates PassTickets explicitly for a particular user and application. Using PassTickets requires that an external security system such as CA ACF2, CA TSS or IBM RACF is employed.

path

1) In CA IDMS/DB, a route through the application database that is used to access and update data. 2) In LRF, the subschema component that contains path-DML commands. These commands perform the data manipulation necessary to fill a program's logical-record request.

PATH

In CA Culprit, the parameter that indicates the access path through the database.

path group

In LRF, a collection of paths (defined in a subschema) designed to fulfill program requests for specific logical records and specific database access functions. Up to four path groups can be defined for each logical record (that is, OBTAIN, ERASE, STORE, and MODIFY).

path iteration

In LRF, the reexecution of all or part of a logical-record path to access all occurrences that meet the selection criteria specified in a program request or in a path WHERE clause. Path iteration is implemented through FIND/OBTAIN EACH path-DML commands.

path selectors

The descriptors in a subschema SELECT clause that LRF compares with the contents of a program request's WHERE clause.

path status

A literal provided by either LRF or the DBA to indicate the outcome of a logical-record program request.

path-DML commands

In LRF, the DML statements in a logical-record path (defined in a subschema) that perform the database navigation and functions necessary to fulfill a program's request for a logical record. See also Data Manipulation Language (DML).

peer session

A database session in the same session hierarchy as another session and neither of which is a subordinate session of the other. See also database session, subordinate session, encompassing session, top-level session.

permission

In CA ICMS, authority given to a user through passkeys. Users can be given permission to manipulate information in CA ICMS as well as to manipulate catalog entities.

PF key

See program function (PF) key.

physical area lock

A lock set and examined by CA IDMS/DB whenever an area is opened in an update mode. Physical area locks prevent concurrent updates by multiple local database transactions, multiple central versions, or both. Physical area locks also prevent update access to an area that requires rollback of database transactions. See also logical area lock.

physical database

A collection of data that resides in operating system files; CA IDMS/DB uses information provided at runtime to determine how to map the logical representation of the database to one of perhaps many physical implementations of the database. See also segment.

physical database definition

The part of the database definition that describes the physical structure of the database, including segments, the DMCL, and a database name table.

physical database design

The process of tailoring the logical model to specific application performance requirements, the best use of computer resources, and efficient data access.

physical DDL

The database definition language submitted to the Command Facility that defines a physical database. Physical DDL statements define DMCLs, database name tables, segments, and the components associated with these entities.

physical network

A combination of interconnected equipment (hardware) and programs (telecommunications access methods) used to transmit data between physical locations. See also logical network.

physical terminal

1) A physical device, such as a CRT (3270-type), TTY, or printer, that exists within a teleprocessing system. In the DC/UCF environment, a physical terminal is associated with a logical terminal; physical terminals are defined with the PTERM statement at system generation. 2) An IDD entity type that documents the physical CRT, TTY, and printer devices in a teleprocessing system.

PLOG

See online PLOG.

pointer

A database key stored in the prefix of a record occurrence that indicates the physical location in the database of another related record occurrence. When a set is defined between related database record types, CA IDMS/DB stores pointers to represent their relationship.

populate

To load a database with actual data values. A database can be populated only after it has been defined.

port

1) In the context of TCP/IP, a 16-bit number that is used to distinguish different application programs that use the same network interface. 2) In CA IDMS DDS, an access point through which the node passes request and response packets to another node.

positioned delete

Using SQL DML, deleting the row where the cursor is positioned in the result table associated with an updatable cursor. A positioned delete requires the WHERE CURRENT OF clause in the DELETE statement. See also searched delete.

positioned update

Using SQL DML, modifying one or more column values in a row where the cursor is positioned in the result table associated with an updatable cursor. A positioned update requires the WHERE CURRENT OF clause in the UPDATE statement. See also searched update.

POST OFFICE

In CA ICMS, a user entity that controls the distribution of letters through the mail facility.

Post-Abort Browse Facility

In the event of an animation/execution abort, CA ADS Alive displays the Post-Abort Browse Session screen showing the process containing the error. The line of source which caused the abort is preceded by the associated error message.

POSTMASTER

In CA ICMS, a group entity whose members share authority over the mail facility.

preclaim lock acquisition mode

A lock acquisition mode for SQL sessions that places locks on all areas that specify PRECLAIM when the first statement that requires access to the database is executed by the session within a transaction. See also incremental lock acquisition mode.

predefined run unit

A system run unit initiated at DC/UCF system startup and maintained for the duration of system execution. See also system run unit.

predicate

An operand of a search condition. It expresses or implies a comparison operation. For example, the BETWEEN predicate searches for all values within a range of values.

prefetch

A CA IDMS/DB feature for z/OS that provides the capability for CA IDMS/DB to do full track reads. I/O requests are bundled so that there is only one scheduling action for multiple physical I/O's.

prefix

See pointer, record prefix.

premap process

An optional component of a CA ADS dialog. A premap process is executed before the dialog's map is displayed, unless ENTRY POINT IS MAP is specified. The premap process performs any special processing required by the map. A given dialog can have only one premap process.

A premap process is defined as a standalone process module in the data dictionary. You make a process module the premap process for a dialog by using the dialog compiler. See also process module, response process.

prepared statement

An SQL statement that has been dynamically compiled at runtime.

primary key

1) The element or elements in a record that uniquely identify each occurrence of that record type. 2) The column or columns in a table that define a unique constraint and which are not null. The primary key uniquely identifies each row and prevents duplicate rows from being stored. See also foreign key, secondary key.

primary protect key

One of two storage protect keys, provided by the operating system, that DC/UCF uses to implement storage protection. When the system nucleus has control of the DC/UCF region/partition, all storage pages in the region/partition are set to the primary protect key. This allows the system nucleus to modify any page in the region/partition. See also alternate protect key.

primary storage pool

Storage pools 0 and 255 in a DC/UCF system. The primary (system) storage pool contains system storage and, optionally, user storage. Storage pool 0 must be defined in order for the DC/UCF system to start up. Storage pool 255 is the primary (system) pool located in 31-bit address space.

PRINT INDEX utility statement

The utility that reports on the structure of system-owned indexes and indexed sets.

PRINT JOURNAL utility statement

The utility that reports on transaction checkpoints in an archive journal file.

PRINT LOG utility statement

The utility that prints all or selected portions of the DC/UCF system log or an archive log file created by the ARCHIVE LOG utility statement.

PRINT PAGE utility statement

The utility that prints the contents of one or more database pages in display (character) and/or hexadecimal format.

PRINT SPACE utility statement

The utility that reports on space utilization in one or more areas or segments.

prior linkage

The type of set linkage in which the owner and members of a set occurrence are linked by prior pointers. Prior pointers cause the owner to point to the last member, the last member to point to the next-to-the-last member, and so on; the first member points to the owner.

privacy lock

See access restriction.

private catalog

In CA ICMS, a portion of the catalog that contains data controlled by an individual user (as opposed to data controlled by the corporation). See also CORP, corporate catalog.

private property

All objects and folders in CA ICMS that are owned by a particular user (that is, stored in a private catalog).

privilege

Under CA IDMS internal security, the right to access a particular resource and perform a particular operation on that resource. Types of privileges are: definition privileges, access privileges, or administration privileges.

procedure

In the context of SQL, an SQL procedure.

process

An IDD entity type used to define source code for CA ADS process modules.

process command

In CA ADS, a command provided for use in coding process modules for dialogs. Process commands are English-like statements that are fully integrated with DC/UCF and CA IDMS/DB facilities. See also process module.

process module

In CA ADS, a module of process commands defined for use in dialogs. A process module performs one or more processing options for the dialog. For example, a process module might obtain and update employee records in the database.

You define a process module in the data dictionary by using the DDDL compiler. You add a process module to a dialog by using the dialog compiler. When used by a dialog, a process module is either a premap process or a response process. See also premap process, response process.

product code

The unique system-supplied name that identifies a DC/UCF development tool or online compiler to the transfer control facility (TCF). For example, IDD is the product code for online IDD; SSC is the product code for the online subschema compiler.

profile

A set of attributes and options associated with users in a CA IDMS environment. Profiles used to set initial values for environmental variables in the user session are processed at signon time. See also user profile, system profile.

program

1) An IDD entity type used to document user application programs. 2) Under DC/UCF, an executable entity that is stored and executed as a program; (for example, a subschema, map, dialog, edit/code table, or DML program).

program attention (PA) key

A predefined control key that serves as an alternative to typing a certain instruction. When a PA key (PA1, PA2, or PA3) is pressed, no data is transmitted from the screen to the record buffer. See also control key, program function (PF) key.

program definition element (PDE)

The DC/UCF control block that specifies general program characteristics. The number of PDEs used in a DC/UCF system is controlled by system-generation specifications.

program directory list

An internal table of programs defined to the DC/UCF system. The program directory list is built either at system startup or as programs are loaded during system execution.

program function

In CA ADS, an application function associated with a site-written program. This site-written COBOL, PL/I, or Assembler program performs the processing activities required by the function. For example, the program might perform specialized data cross-validation routines. See also application function.

program function (PF) key

A predefined control key that serves as an alternative to typing a certain instruction. When a PF key (PF1 through PF24) is pressed, data is transmitted from the screen to the record buffer. See also control key, program attention (PA) key.

program pool

The storage space in memory into which resident and nonresident programs are loaded for execution. Typically program pools hold CA ADS applications, dialogs, subschemas, maps, database procedures, edit/code tables, access modules, relational command modules, and user programs. Program pool specifications are part of a system's definition.

program processor

A component of the Dictionary Loader that analyzes a single COBOL program and outputs information about how the program uses data.

program registration

The CA IDMS/DB security feature that enables you to associate programs with subschemas. Using program registration, you can control compilation of DML programs that use a particular subschema.

project

The generic relational operation through which only specific columns of a data table are accessed.

prompt mode

The line-oriented method of communicating with the debugger.

propagation

In CA ICMS, an ambiguous association that can occur when duplicate names are used.

protected retrieval ready mode

A retrieval ready mode in which other transactions executing concurrently under the central version can ready the area only in shared retrieval or protected retrieval modes.

protected update ready mode

An update ready mode in which other transactions executing concurrently under the central version can ready the area in shared retrieval mode only.

protocol

1) In CA IDMS/DB, a set of source statements that the DML compilers use as a model to convert DML statements into calls for DBMS services. A protocol is stored as a module in the data dictionary. 2) The formats and sequencing of communications between entities during the performance of an operation. For example, IP is a communications protocol that defines a packet delivery service.

prototype

In CA ADS, an early version of an application used to test and demonstrate the functions, responses, and maps of the application. The production application can be developed directly from the prototype.

proxy lock

A global lock used to represent a lock on each record within a given database page. Proxy locks are acquired only in a Data Sharing environment.

pseudo column

An automatically created column that does not physically exist on the database.

pseudo-converse

The interval between mapout and mapin, during which the system resources for a task are freed.

pseudoconversational programming

An online programming technique that frees resources being used by a task while the system waits for completion of data entry by the operator. For example, the runtime system of CA ADS is pseudo-conversational.

PTERM

See physical terminal.

public access

In IDD, the ability of unregistered users to access data dictionary entity occurrences.

PUNCH

When using CA IDMS compilers in batch mode, the function that directs information to the file defined for punched output.

PUNCH utility statement

The utility that retrieves the DMCL or database name table load module from the dictionary, and writes them, in object module form, into the file defined for punched output.