P - glossary entries

package
A group of z/TPF-unique programs necessary to process one particular function or a group of related functions.
In z/TPF application requester (z/TPFAR), an object containing a set of Structured Query Language (SQL) statements that have been bound statically and are available for processing.
page and segment table area
The segment and page table area (SPTA) is the control table for the ECB virtual memory (EVM). It is allocated by CCCTIN. The address of SPTA in each entry control block (ECB) is saved in the Key F section of the ECB.
parallel session logical unit
A logical unit (LU) that can have 1 or more concurrently active sessions with a given partner LU.
parametric recoup
The attribute of the file recoup program that allows it to be activated and controlled by parameter lists.
parked I-stream
An active I-stream that is not in use and that has an I-stream number less than or equal to the I-stream cap. See also active I-stream, in-use I-stream, and I-stream cap.
PARS
Programmed airlines reservation system.
partial load
Synonym for short load.
partially duplicated files
A design for a z/TPF database where some records have duplicate copies while other records do not.
part objects
See collection part objects.
PAT
Program attribute table.
PAT stub
The part of a program attribute table (PAT) slot that contains executable linkage code used for external program calls.
path switch
An action taken by one of the high-performance routing (HPR) endpoints to request a new path for a rapid transport protocol (RTP) connection when the HPR endpoint detects a failure in the network. This action is nondisruptive; that is, no LU-LU sessions or data are lost.
path switch timer
A timer used by the z/TPF system to detect path switch failures in a high-performance routing (HPR) network.
PBI
Program base identification.
PDU
In Simple Network Management Protocol (SNMP) agent support, a protocol data unit..
In z/TPF file pool support, pool directory update processing
permanent storage
Storage that is the final repository for the data that z/TPF systems share and might be on DASD. z/TPF systems can read the data from permanent storage to local storage buffers for their use and then maintain the data in the local cache buffers and use the directory-only caching method to track the validity of the data.
persistence
A process that guarantees collection access beyond the life of the creating entry control block (ECB) and beyond a system re-IPL. Access is guaranteed until a collection is specifically deleted.
persistent collection
An abstract representation of data having common attributes and functions that maintain their state after the entry control block (ECB) that creates them exits.
persistent identifier (PID)
An identification number that is assigned to all collections in z/TPF collection support (z/TPFCS). The PID is architected as a 32-byte number consisting of a format indicator and other information used to locate the collection.
persistent long-term collection
A collection that lives beyond the life of the creating entry control block (ECB) , resides on DASD in long-term pool records, and can survive a re-IPL. The collection will be deleted only with an explicit delete call.
persistent message
A message that survives a restart of the queue manager. Contrast with nonpersistent message.
persistent short-term collection
A collection that lives beyond the life of the creating entry control block (ECB), resides on DASD in short-term pool records, and can survive a re-IPL. The collection will be deleted when the short-term pools are recycled.
persistent structure
A coupling facility (CF) structure that remains allocated when there are no active connections.
pessimistic concurrency
In z/TPF collection support (z/TPFCS), a way of controlling data access. Pessimistic concurrency uses an exclusive lock to allow a user to read a collection, update it, and replace it.
PFS
Pool file system.
physical storage block
Start of changeTypes of working storage blocks used as input/output (I⁄O) blocks, system work blocks, extended system work blocks, entry control blocks, frames, and common frames.End of change
PID
Persistent identifier.
pilot tape
A general tape that can be processed by the online data loader to load new fixed file data into the online system.
pinned data
Data held until it is destaged to DASD or explicitly discarded by a host command because of a permanent error condition in a 3990 caching control unit.
PIO
Preemptive input/output (I⁄O). A z/TPF control program routine that manages I/O operations to a single device while suspending normal I/O (CIO) services for all other devices. This is used primarily by the system error routine.
plaintext
In cryptography, data that is not encrypted. Contrast with ciphertext.
PNA
Program nesting area.
PLT
Procedure linkage table.
pool conversion
In pool file support, to convert the pool data structures on file in DASD from pool expansion (PXP) support format to 32-way loosely coupled pool support format. For pool conversion to take place, all processors in the complex must be migrated to 32-way loosely coupled pool support. When pool conversion is completed, the pool data structures in main processor storage (core) on each processor and on file in DASD are in 32-way loosely coupled pool support format. Contrast with pool migration and pool conversion fallback.
pool conversion fallback
In pool file support, to return the pool data structures on file in DASD from 32-way loosely coupled pool support format to pool expansion (PXP) format. When pool conversion fallback is completed, the pool data structure in main processor storage (core) on each processor is 32-way loosely coupled pool support format, while the pool data structure on file in DASD has been returned to PXP support format. Processors in unmigrated state can now join the complex. See also pool conversion, pool migration, and unmigrated state.
pool directory
An index of all pool records maintained by the control program file directory system.
pool directory generation
A storage management process that creates pool directories.
pool directory record
The array of status bits that indicates whether a pool record is available or unavailable.
pool fallback
The technique for selecting an alternate compatible pool section for address dispensing if a depleted pool section is selected.
pool file record
A DASD record used for temporary data storage; it is given to programs when requested and returned when no longer needed by the programs.
pool file storage
See pool file record.
pool file system (PFS)
A processor-unique, subsystem-unique file system that uses pool file records as its storage mechanism for data records and fixed file records as its storage mechanism for file system metadata.
pool migration
To IPL a processor on an image that contains 32-way loosely coupled pool support while the data structure on file in DASD remains pool expansion (PXP) support format. The 32-way loosely coupled pool support data structure format is used in main processor storage (core). Contrast with pool conversion.
pool record
See pool file record.
pool record type
See pool type.
pool section
Storage space allocated for a particular pool type on a selected z/TPF device type. The pool type might be allocated across several device types. When this occurs, the pool type consists of several pool sections.
pool segment
A pool section that is described by a single RAMFIL macro statement.
pool type
A classification for pool records that is based on the attributes of size, duplication, longevity, and type of device.
post-interrupt branch address
The standard field in system control blocks used to point to the system routines invoked when a work item reaches the top of a queue.
post-interrupt processing
The housekeeping routine to set up further processing for an application after the control program has completed a service request.
When an IOB reaches the top of the ready list, post-interrupt processing removes the IOB address from the ready list and links the application to the input data by moving the core block address to the entry control block (ECB), moves the output data core block address to the ECB, and returns the core block to the system pool. If all input/output (I/O) is completed, control returns to the linked application.
post-interrupt routine
The housekeeping routine that performs further processing for an application after the control program has completed a service request.
PRC
Prime CRAS.
preallocated application stack
The initial portion of the application stack. This portion of the stack has permanently allocated storage.
preallocated ECB heap
An initial allocation of 31-bit ECB heap that is permanently assigned to each entry control block (ECB).
preallocated ECB private area
An initial allocation of the ECB private area that is permanently assigned to each entry control block (ECB).
preallocated storage
A collection of storage areas, including the ECB heap, ECB private area, and other areas, that are permanently assigned to an entry control block (ECB) when ECB storage blocks are allocated.
preemptive I⁄O
Synonym for PIO, which is the commonly used term. A z/TPF control program routine that manages input/output (I/O) operations to a single device while suspending normal I/O (CIO) services for all other devices. This is used primarily by the system error routines. See also CIO.
primary directory
See quick enter directory.
primary image
The image that is used during a hard IPL.
primary key path
A structure that exists from the moment a collection is created and dictates the location of elements within that collection. See also alternate key path.
primary record
When DASD records are duplicated, the 2 copies of a data record are called the primary record and the duplicate record. When used in the context of z/TPF collection support (z/TPFCS), this term has a different meaning. See z/TPFCS primary record.
prime CRAS (PRC)
The main system console designated to direct system processing.
prime module
The online module used for IPLs and system restarts. In a fully duplicated database, the disk pack containing the primary records. Contrast with duplicate module. See also primary record and duplicate record.
prime restart area
The part of the restart area used for online system restarts.
private code
An unnamed executable control section.
private key
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 can be protected by a password. See public key.
procedure linkage table (PLT)
A table that contains entries for every function external to a shared object. Each shared object contains a procedure linkage table that resolves these external function calls.
procedure linkage table (PLT) entry
An item in the procedure linkage table that identifies the address of a function external to the shared object that contains the procedure linkage table.
process identifier (ID)
A unique, positive number that represents a process. In the z/TPF system, the process ID is a unique identifier for a process.
process selection vector (PSV)
An optional exit program that allows the user to extend z/TPF communication support for additional terminal types without modifying the user's application programs.
processing unit
A functional unit that consists of 1 or more processors and their internal storage.
processor keypoint status table (PKST)
The communication control unit keypoint status record used for non-SNA communication.
processor lock
Used to permit system control programs, processing in 2 or more I-stream engines in a CPC, to modify shared system data.
processor resource ownership table (PROT)
A table maintaining the ownership status of tape drives and system utilities in a loosely coupled complex.
processor shared cache
In logical record cache support, a cache that contains cache entries that are kept synchronized between all processors in a loosely coupled complex that are using the cache.
processor shared keypoint (PSK)
The keypoint records that identify resources shared among processors. All processors in a loosely coupled complex share the same copy of these keypoint records.
processor unique cache
In logical record cache support, a cache that contains cache entries that are used by only one processor in a loosely coupled complex.
processor unique keypoint (PUK)
The keypoint records that identify resources dedicated to each processor. Each processor in a loosely coupled complex has its own unique copy of these keypoint records.
program attribute table (PAT)
A table that provides an enter-by-name capability and program attributes. The program attribute table allows dynamic determination of the address of the program being entered.
program base identification (PBI)
The ECB field that identifies the program base of a particular subsystem.
program collector
The data collection program that records the macro types, the programs called, and the residency of the called programs. The data is written to the data collection tape and processed by the offline data reduction programs.
program ID field
A 4-byte field in the header of every data record that contains the name of the last program updating that record.
program nesting area (PNA)
The fields used to hold chains of ENTER/BACK requests controlled by an entry control block (ECB). Base address, return address (next sequential instruction), and program base ID are saved for each program issuing an ENTRC.
programmed airlines reservation system (PARS)
The application programs developed specifically for airline reservations.
property service
A service for created persistent collections that lets a user dynamically associate named attributes (properties) with an already existing persistent collection. Once the properties are defined, their values and access modes can be obtained and changed.
PROT
Processor resource ownership table.
provider Web service
A Web service that provides an interface to a z/TPF application through the SOAP handler and is described by a provider Web service deployment descriptor.
provider Web service deployment descriptor
A deployment descriptor that defines the routing mechanism and other processing information, including the list of SOAP message handlers, that is required to take a Web service request that is received by the SOAP handler and present it to a z/TPF application for processing. This deployment descriptor includes the name of the Web service wrapper that is required to interact with the application. The ProviderDeploymentDescriptor XML Schema element and its subelements, which are defined in the base/tpf-ws/schema/tpf_ws_dd_vn.xsd XML Schema file (where n is the version number), define what constitutes a provider Web service.
pseudo directory
An accurate account of long-term pool records at some discrete instant of time.
pseudo module number
The sum of the starting general file module number and the number of the data set that you want to access.
pseudo processor utilization
The average of the pseudo utilization for all active I-streams. This value is used to determine whether an ECB is to be suspended based on the utilization priority class defined with the LODIC macro.
pseudo utilization
The percentage of time that the z/TPF system is considered to be busy over a time period minus the time spent in delay and defer processing. Pseudo utilization is calculated with the following formula:
(timeidletimedtime) ÷ time
where:
time
is the time period.
idletime
is the total idle time accumulated over the time period as observed by the z/TPF system.
dtime
is the time spent in defer and delay processing over the time period.
PSV
Process selection vector.
PU type 5
PU type 5 attachment to an SNA network involves the z/TPF system appearing to a local NCP as a type 5 subarea node with an SSCP and a CDRM component. The z/TPF system is a data host (that is, does not send ACTPU to the NCP) and performs exchange identification format 2 (XID2) to establish connection. z/TPF application LUs appear as CDRMs to a z/OS® Communications Server CMC.
public key
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 private key.
public key cryptography
A method of cryptography that depends on a matched pair of keys. Information encrypted with one key can be decrypted only by the other key in the pair. One of the keys is made public. The other key is kept private. This method allows secure communication between an individual entity (such as a merchant) and any other entities who obtain the public key (such as consumers). See public key.
PUK
Processor unique keypoint.