IBM DB2 Manual page 561

Table of Contents

Advertisement

a commit point. See also cursor stability,
read stability, and uncommitted read.
repeating group
A situation in which an entity includes
multiple attributes that are inherently the
same. The presence of a repeating group
violates the requirement of first normal
form. In an entity that satisfies the
requirement of first normal form, each
attribute is independent and unique in its
meaning and its name. See also
normalization.
replay detection mechanism
A method that allows a principal to detect
whether a request is a valid request from
a source that can be trusted or whether an
untrustworthy entity has captured
information from a previous exchange
and is replaying the information exchange
to gain access to the principal.
request commit
The vote that is submitted to the prepare
phase if the participant has modified data
and is prepared to commit or roll back.
requester
The source of a request to access data at a
remote server. In the DB2 environment,
the requester function is provided by the
distributed data facility.
resource
The object of a lock or claim, which could
be a table space, an index space, a data
partition, an index partition, or a logical
partition.
resource allocation
The part of plan allocation that deals
specifically with the database resources.
resource control table
A construct of previous versions of the
|
|
CICS attachment facility that defines
authorization and access attributes for
|
transactions or transaction groups.
|
|
Beginning in CICS Transaction Server
Version 1.3, resources are defined by
|
using resource definition online instead of
|
|
the resource control table. See also
resource definition online.
|
resource definition online (RDO)
The recommended method of defining
|
|
resources to CICS by creating resource
definitions interactively, or by using a
|
utility, and then storing them in the CICS
|
definition data set. In earlier releases of
|
|
CICS, resources were defined by using the
resource control table (RCT), which is no
|
longer supported.
|
resource limit facility (RLF)
A portion of DB2 code that prevents
dynamic manipulative SQL statements
from exceeding specified time limits. The
resource limit facility is sometimes called
the governor.
resource limit specification table (RLST)
A site-defined table that specifies the
limits to be enforced by the resource limit
facility.
resource manager
v A function that is responsible for
managing a particular resource and that
guarantees the consistency of all
updates made to recoverable resources
within a logical unit of work. The
resource that is being managed can be
physical (for example, disk or main
storage) or logical (for example, a
particular type of system service).
v A participant, in the execution of a
two-phase commit, that has recoverable
resources that could have been
modified. The resource manager has
access to a recovery log so that it can
commit or roll back the effects of the
logical unit of work to the recoverable
resources.
restart pending (RESTP)
A restrictive state of a page set or
partition that indicates that restart
(backout) work needs to be performed on
the object.
RESTP
See restart pending.
result set
The set of rows that a stored procedure
returns to a client application.
result set locator
A 4-byte value that DB2 uses to uniquely
identify a query result set that a stored
procedure returns.
result table
The set of rows that are specified by a
SELECT statement.
retained lock
A MODIFY lock that a DB2 subsystem
545
Glossary

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents