1851 lines
91 KiB
HTML
1851 lines
91 KiB
HTML
|
<?xml version="1.0" encoding="utf-8"?>
|
||
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
|
||
|
|
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="dc.language" scheme="rfc1766" content="en-us" />
|
||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
|
<!-- US Government Users Restricted Rights -->
|
||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
|
<meta name="dc.date" scheme="iso8601" content="2005-09-06" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1997, 2006" />
|
||
|
|
<meta name="security" content="public" />
|
||
|
|
<meta name="Robots" content="index,follow"/>
|
||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
|
<meta name="owner" content="RCHCLERK@us.ibm.com" />
|
||
|
|
<title>R</title>
|
||
|
|
<link rel="stylesheet" type="text/css" href="ibmidwb.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="ic.css" />
|
||
|
|
</head>
|
||
|
|
<body>
|
||
|
|
<a id="Top_Of_Page" name="Top_Of_Page"></a><!-- Java sync-link -->
|
||
|
|
<script language = "Javascript" src = "../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
|
||
|
|
|
||
|
|
<a name="r"></a>
|
||
|
|
<h2 id="r">R</h2>
|
||
|
|
<p>Return to <a href="as4glos.htm#as4glos">Glossary</a>.</p>
|
||
|
|
<dl>
|
||
|
|
<dt id="x2035701" class="bold">
|
||
|
|
<a name="x2035701"></a>rack</dt>
|
||
|
|
<dd>A free-standing structure or
|
||
|
|
frame that can hold multiple servers and expansion units.</dd>
|
||
|
|
<dt id="x2035706" class="bold">
|
||
|
|
<a name="x2035706"></a>rack configuration list</dt>
|
||
|
|
<dd>A list of
|
||
|
|
all of the equipment within the rack and the logic cards within the card enclosure.</dd>
|
||
|
|
<dt id="x2035711" class="bold">
|
||
|
|
<a name="x2035711"></a>rack stabilizer</dt>
|
||
|
|
<dd>A plate that holds
|
||
|
|
the rack stable or steady when a device is pulled out for service.</dd>
|
||
|
|
<dt id="x2035716" class="bold">
|
||
|
|
<a name="x2035716"></a>RACL</dt>
|
||
|
|
<dd>See <a href="rzaatr.htm#x2035766">Random
|
||
|
|
Automated Cartridge Loader</a>.</dd>
|
||
|
|
<dt id="x2035720" class="bold">
|
||
|
|
<a name="x2035720"></a>radio button</dt>
|
||
|
|
<dd>A circle with text beside
|
||
|
|
it that indicates a fixed set of choices from which only one can be selected.
|
||
|
|
The circle is partially filled when a choice is selected.</dd>
|
||
|
|
<dt id="x2035729" class="bold">
|
||
|
|
<a name="x2035729"></a>radix-tree index</dt>
|
||
|
|
<dd>In DB2® UDB for iSeries™, an object that provides random access to rows in a database table.
|
||
|
|
See also <a href="rzaate.htm#x2026743">encoded-vector index</a>.</dd>
|
||
|
|
<dt id="x2035734" class="bold">
|
||
|
|
<a name="x2035734"></a>RAID</dt>
|
||
|
|
<dd>See <a href="rzaatr.htm#x2036211">Redundant
|
||
|
|
Array of Independent Disks</a>.</dd>
|
||
|
|
<dt id="x2035738" class="bold">
|
||
|
|
<a name="x2035738"></a>RAID 5</dt>
|
||
|
|
<dd>A form of parity RAID in which
|
||
|
|
the disks operate independently, the data stripe size is no smaller than the
|
||
|
|
exported block size, and parity check data is distributed across the array's
|
||
|
|
disks</dd>
|
||
|
|
<dt id="x2437065" class="bold">
|
||
|
|
<a name="x2437065"></a>RAID 6</dt>
|
||
|
|
<dd>Any form of RAID that can
|
||
|
|
continue to execute read and write requests to all of an array's virtual disks
|
||
|
|
in the presence of two concurrent disk failures.</dd>
|
||
|
|
<dt id="x2035743" class="bold">
|
||
|
|
<a name="x2035743"></a>rail</dt>
|
||
|
|
<dd>Hardware attached inside a rack
|
||
|
|
to hold devices that are designated as installable in a rack. See also <a href="rzaats.htm#x2039078">slide</a>.</dd>
|
||
|
|
<dt id="x2035748" class="bold">
|
||
|
|
<a name="x2035748"></a>RAM</dt>
|
||
|
|
<dd>See <a href="rzaatr.htm#x2035761">random
|
||
|
|
access memory</a>.</dd>
|
||
|
|
<dt id="x2035756" class="bold">
|
||
|
|
<a name="x2035756"></a>random access</dt>
|
||
|
|
<dd>In COBOL, an access
|
||
|
|
method in which the program-specified value of a key data item identifies
|
||
|
|
the logical record that is obtained from, deleted from, or placed into a relative
|
||
|
|
or indexed file.</dd>
|
||
|
|
<dt id="x2035761" class="bold">
|
||
|
|
<a name="x2035761"></a>random access memory (RAM)</dt>
|
||
|
|
<dd>Computer
|
||
|
|
memory in which any storage location can be accessed directly. See also <a href="rzaatd.htm#x2020809">disk unit</a>.</dd>
|
||
|
|
<dt id="x2035766" class="bold">
|
||
|
|
<a name="x2035766"></a>Random Automated Cartridge Loader (RACL)</dt>
|
||
|
|
<dd>A cartridge loader that includes individual drives that can have their
|
||
|
|
own facility to use an automated tape library.</dd>
|
||
|
|
<dt id="x2035771" class="bold">
|
||
|
|
<a name="x2035771"></a>random by key</dt>
|
||
|
|
<dd>A processing method
|
||
|
|
for files in which the value in the key field identifies the records to be
|
||
|
|
processed.</dd>
|
||
|
|
<dt id="x2035776" class="bold">
|
||
|
|
<a name="x2035776"></a>random by relative record number</dt>
|
||
|
|
<dd>A processing method for files in which relative record numbers identify the
|
||
|
|
records to be processed.</dd>
|
||
|
|
<dt id="x2035781" class="bold">
|
||
|
|
<a name="x2035781"></a>random number</dt>
|
||
|
|
<dd>A number obtained by
|
||
|
|
chance. See also <a href="rzaatp.htm#x2035358">pseudorandom number</a>.</dd>
|
||
|
|
<dt id="x2035786" class="bold">
|
||
|
|
<a name="x2035786"></a>random processing</dt>
|
||
|
|
<dd>A method of processing
|
||
|
|
in which records can be read from, written to, or deleted from a file order
|
||
|
|
requested by the program that is using them. See also <a href="rzaatc.htm#x2018288">consecutive processing</a>, <a href="rzaats.htm#x2038260">sequential processing</a>.</dd>
|
||
|
|
<dt id="x2035791" class="bold">
|
||
|
|
<a name="x2035791"></a>raster pattern</dt>
|
||
|
|
<dd>A series of picture
|
||
|
|
elements (pels) arranged in scan lines to form an image. The toned or untoned
|
||
|
|
status of each pel creates an image. A digitized raster pattern is an array
|
||
|
|
of bits. The on or off status of each bit determines the toned or untoned
|
||
|
|
status of each pel.</dd>
|
||
|
|
<dt id="x2035796" class="bold">
|
||
|
|
<a name="x2035796"></a>rational number</dt>
|
||
|
|
<dd>A real number that
|
||
|
|
is the quotient of an integer divided by an integer other than zero.</dd>
|
||
|
|
<dt id="x2035801" class="bold">
|
||
|
|
<a name="x2035801"></a>RBR</dt>
|
||
|
|
<dd>See <a href="rzaatr.htm#x2037284">rollback
|
||
|
|
required</a>.</dd>
|
||
|
|
<dt id="x2035805" class="bold">
|
||
|
|
<a name="x2035805"></a>RC</dt>
|
||
|
|
<dd>A REXX special variable set to
|
||
|
|
the return code from any executed host command or subcommand. It is also set
|
||
|
|
to the return code when the conditions ERROR, FAILURE, and SYNTAX are trapped.</dd>
|
||
|
|
<dt id="x2035810" class="bold">
|
||
|
|
<a name="x2035810"></a>RCB</dt>
|
||
|
|
<dd>See <a href="rzaatr.htm#x2036063">record
|
||
|
|
control byte</a>.</dd>
|
||
|
|
<dt id="x2035814" class="bold">
|
||
|
|
<a name="x2035814"></a>RCD</dt>
|
||
|
|
<dd>See <a href="rzaatr.htm#x2035854">read
|
||
|
|
cache device</a>.</dd>
|
||
|
|
<dt id="x2035818" class="bold">
|
||
|
|
<a name="x2035818"></a>RCMS</dt>
|
||
|
|
<dd>See <a href="rzaatr.htm#x2036588">remote
|
||
|
|
change management server</a>.</dd>
|
||
|
|
<dt id="x2009558" class="bold">
|
||
|
|
<a name="x2009558"></a>RDB</dt>
|
||
|
|
<dd>See <a href="rzaatr.htm#x2004149">relational
|
||
|
|
database</a>.</dd>
|
||
|
|
<dt id="x2035828" class="bold">
|
||
|
|
<a name="x2035828"></a>RDB directory</dt>
|
||
|
|
<dd>The directory where
|
||
|
|
remote databases in the network are registered. Information in a directory
|
||
|
|
tells the system which communications parameters to use to connect to a remote
|
||
|
|
database. The RDB directory also contains the name of the local database.</dd>
|
||
|
|
<dt id="x2009566" class="bold">
|
||
|
|
<a name="x2009566"></a>RDBMS</dt>
|
||
|
|
<dd>See <a href="rzaatr.htm#x2004154">relational database management system</a>.</dd>
|
||
|
|
<dt id="x2035835" class="bold">
|
||
|
|
<a name="x2035835"></a>RDN™</dt>
|
||
|
|
<dd>See <a href="rzaatr.htm#x2036435">relative distinguished name</a>.</dd>
|
||
|
|
<dt id="x2012205" class="bold">
|
||
|
|
<a name="x2012205"></a>RDO</dt>
|
||
|
|
<dd>See <a href="rzaatr.htm#x2004282">resource
|
||
|
|
definition online</a>.</dd>
|
||
|
|
<dt id="x2035846" class="bold">
|
||
|
|
<a name="x2035846"></a>read authority</dt>
|
||
|
|
<dd>(1) An authority subset
|
||
|
|
that allows the user to read entries in an object. The system-recognized identifier
|
||
|
|
is *R. *R authority combines object operational authority and read authority.</dd>
|
||
|
|
<dd>(2) A data authority that allows the user to look at the contents
|
||
|
|
of an entry in an object.</dd>
|
||
|
|
<dt id="x2035854" class="bold">
|
||
|
|
<a name="x2035854"></a>read cache device (RCD)</dt>
|
||
|
|
<dd>A volatile
|
||
|
|
solid-state disk that is optimized for use as memory for the extended adaptive
|
||
|
|
cache.</dd>
|
||
|
|
<dt id="x2035859" class="bold">
|
||
|
|
<a name="x2035859"></a>reader</dt>
|
||
|
|
<dd>(1) In RJE, a program that reads
|
||
|
|
jobs from a database file or interactive display station and sends them to
|
||
|
|
the host system.</dd>
|
||
|
|
<dd>(2) An internal program that reads jobs from an input
|
||
|
|
device or a database file and places them on a job queue.</dd>
|
||
|
|
<dt id="x2035867" class="bold">
|
||
|
|
<a name="x2035867"></a>read/execute authority</dt>
|
||
|
|
<dd>An object
|
||
|
|
authority that allows the user to read entries in an object, run a program,
|
||
|
|
and search a library or directory. Read/execute authority combines object
|
||
|
|
operational authority, read authority, and execute authority. The system-recognized
|
||
|
|
identifier is *RX.</dd>
|
||
|
|
<dt id="x2035872" class="bold">
|
||
|
|
<a name="x2035872"></a>read-from-invited-program-devices operation</dt>
|
||
|
|
<dd>An input operation that waits for input from any one of the invited
|
||
|
|
program devices for a user-specified time. See also <a href="rzaatr.htm#x2035877">read-from-one-program-device operation</a>.</dd>
|
||
|
|
<dt id="x2035877" class="bold">
|
||
|
|
<a name="x2035877"></a>read-from-one-program-device operation</dt>
|
||
|
|
<dd>An input operation that will not complete until the specified device
|
||
|
|
has responded with input. See also <a href="rzaatr.htm#x2035872">read-from-invited-program-devices
|
||
|
|
operation</a>.</dd>
|
||
|
|
<dt id="x2035882" class="bold">
|
||
|
|
<a name="x2035882"></a>read-only memory (ROM)</dt>
|
||
|
|
<dd>Memory in
|
||
|
|
which stored data cannot be changed by the user except under special conditions.</dd>
|
||
|
|
<dt id="x2035892" class="bold">
|
||
|
|
<a name="x2035892"></a>read operation</dt>
|
||
|
|
<dd>An input operation
|
||
|
|
that obtains data from a file or device and passes it to a program.</dd>
|
||
|
|
<dt id="x2004018" class="bold">
|
||
|
|
<a name="x2004018"></a>read stability</dt>
|
||
|
|
<dd>In DB2 UDB for iSeries, an isolation level that does not completely isolate an application
|
||
|
|
process from all other application processes that are running concurrently.
|
||
|
|
At the read stability level, an application that issues the same query more
|
||
|
|
than once might read additional rows (phantom rows) that were inserted and
|
||
|
|
committed by an application process that is running concurrently. See also <a href="rzaatr.htm#x2004214">repeatable read</a>.</dd>
|
||
|
|
<dt id="x2035900" class="bold">
|
||
|
|
<a name="x2035900"></a>read/write authority</dt>
|
||
|
|
<dd>An object authority
|
||
|
|
that allows the user to add, change, delete, and read entries in an object.
|
||
|
|
Read/write authority combines object operational authority, read authority,
|
||
|
|
add authority, update authority, and delete authority. The system-recognized
|
||
|
|
identifier is *RW.</dd>
|
||
|
|
<dt id="x2035905" class="bold">
|
||
|
|
<a name="x2035905"></a>read/write/execute authority</dt>
|
||
|
|
<dd>An object
|
||
|
|
authority that allows the user to add, change, delete, and read execute entries
|
||
|
|
in an object, run a program, and search a library or directory. Read/write/execute
|
||
|
|
authority combines object operational authority, read authority, add authority,
|
||
|
|
update authority, delete authority, and execute authority. The system-recognized
|
||
|
|
identifier is *RWX.</dd>
|
||
|
|
<dt id="x2035910" class="bold">
|
||
|
|
<a name="x2035910"></a>read/write head</dt>
|
||
|
|
<dd>The data sensing
|
||
|
|
and recording unit of the diskette drive or tape drive.</dd>
|
||
|
|
<dt id="x2210222" class="bold">
|
||
|
|
<a name="x2210222"></a>ready</dt>
|
||
|
|
<dd>Pertaining to a status where
|
||
|
|
all the loaded and mounted image catalog entries are available for use by
|
||
|
|
the active virtual optical device. Any image catalog entry with a status of
|
||
|
|
unloaded is not available for use by the virtual optical device. The image
|
||
|
|
catalog can be made ready by using the LODIMGCLG (Load Image Catalog) command
|
||
|
|
with OPTION(*LOAD).</dd>
|
||
|
|
<dt id="x2035915" class="bold">
|
||
|
|
<a name="x2035915"></a>realm</dt>
|
||
|
|
<dd>In the Kerberos protocol, the
|
||
|
|
set of principals for which a specific key distribution center (KDC) is the
|
||
|
|
authenticating authority.</dd>
|
||
|
|
<dt id="x2210133" class="bold">
|
||
|
|
<a name="x2210133"></a>realm trust</dt>
|
||
|
|
<dd>The Kerberos protocol
|
||
|
|
either searches the configuration file to determine realm trust or by default
|
||
|
|
looks for trust relationships within the realm hierarchy. Using Trusted realms
|
||
|
|
in network authentication service allows you to bypass this process and creates
|
||
|
|
a shortcut for authentication. Realm trust can be used in networks where realms
|
||
|
|
are in different domains. For example, if a company has one realm at NY.myco.com
|
||
|
|
and another at LA.myco.com, then you can establish trust between these two
|
||
|
|
realms. If two realms trust each other their associated KDCs must share a
|
||
|
|
key. Before creating a shortcut, you must set up the KDCs to trust each other.</dd>
|
||
|
|
<dt id="x2035923" class="bold">
|
||
|
|
<a name="x2035923"></a>real-time</dt>
|
||
|
|
<dd>Pertaining to the processing
|
||
|
|
of data by a computer in connection with another process outside the computer
|
||
|
|
according to time requirements imposed by the outside process. (I)(A)</dd>
|
||
|
|
<dt id="x2035928" class="bold">
|
||
|
|
<a name="x2035928"></a>reason code</dt>
|
||
|
|
<dd>A return code that describes
|
||
|
|
the reason for the failure or partial success of a Message Queue Interface
|
||
|
|
(MQI) call.</dd>
|
||
|
|
<dt id="x2035933" class="bold">
|
||
|
|
<a name="x2035933"></a>reassembly</dt>
|
||
|
|
<dd>In OSI, a function performed
|
||
|
|
by an (N)-entity to map multiple (N)-protocol-data-units into one (N)-service-data-unit.
|
||
|
|
Reassembly is the opposite of segmenting. See also <a href="rzaats.htm#x2038067">segmenting</a>.</dd>
|
||
|
|
<dt id="x2035938" class="bold">
|
||
|
|
<a name="x2035938"></a>reassign</dt>
|
||
|
|
<dd>To mark a disk sector as
|
||
|
|
damaged. The marked disk sector points to another sector location where the
|
||
|
|
data from the damaged sector is moved.</dd>
|
||
|
|
<dt id="x2235652" class="bold">
|
||
|
|
<a name="x2235652"></a>reattach</dt>
|
||
|
|
<dd>In cross-site mirroring,
|
||
|
|
to reassociate the mirror copy with its production copy after user operations
|
||
|
|
on the mirror copy are complete. When the mirror copy is reattached, it is
|
||
|
|
automatically synchronized to match the production copy again. All data on
|
||
|
|
the mirror copy prior to when it is reattached to the production copy is cleared.</dd>
|
||
|
|
<dt id="x2004023" class="bold">
|
||
|
|
<a name="x2004023"></a>rebind</dt>
|
||
|
|
<dd>(1) To request renewal of a lease
|
||
|
|
from a server on a particular network.</dd>
|
||
|
|
<dd>(2) To create a package for
|
||
|
|
an application program that was previously bound. For example, if an index
|
||
|
|
is added for a table that is accessed by a program, the package must be rebound
|
||
|
|
for it to take advantage of the new index.</dd>
|
||
|
|
<dt id="x2035950" class="bold">
|
||
|
|
<a name="x2035950"></a>rebuild maintenance</dt>
|
||
|
|
<dd>A method of maintaining
|
||
|
|
keyed access paths for database files. This method updates the access path
|
||
|
|
only while the file is open, not when the file is closed; the access path
|
||
|
|
is rebuilt when the file is opened. See also <a href="rzaatd.htm#x2020063">delayed
|
||
|
|
maintenance</a>, <a href="rzaati.htm#x2024971">immediate maintenance</a>.</dd>
|
||
|
|
<dt id="x2035960" class="bold">
|
||
|
|
<a name="x2035960"></a>receive mode</dt>
|
||
|
|
<dd>A time during which
|
||
|
|
the BSC adapter looks for synchronization characters, and stores the data
|
||
|
|
characters in main storage.</dd>
|
||
|
|
<dt id="x2035965" class="bold">
|
||
|
|
<a name="x2035965"></a>receive not ready (RNR)</dt>
|
||
|
|
<dd>In communications,
|
||
|
|
a data link command or response that indicates a temporary condition of being
|
||
|
|
unable to accept incoming frames.</dd>
|
||
|
|
<dt id="x2035970" class="bold">
|
||
|
|
<a name="x2035970"></a>receiver</dt>
|
||
|
|
<dd>In hardware, a functional
|
||
|
|
unit that converts small electronic signals to signals that control a device.</dd>
|
||
|
|
<dt id="x2035977" class="bold">
|
||
|
|
<a name="x2035977"></a>receiver chain</dt>
|
||
|
|
<dd>The journal receivers
|
||
|
|
presently or previously attached to the same journal. Each journal receiver,
|
||
|
|
except the first one, has a previous receiver that was attached before the
|
||
|
|
current receiver. Each journal receiver, except the currently attached receiver,
|
||
|
|
has a next receiver.</dd>
|
||
|
|
<dt id="x2035982" class="bold">
|
||
|
|
<a name="x2035982"></a>receiver chain break</dt>
|
||
|
|
<dd>A logical break
|
||
|
|
in a receiver chain.</dd>
|
||
|
|
<dt id="x2035987" class="bold">
|
||
|
|
<a name="x2035987"></a>receiver directory</dt>
|
||
|
|
<dd>Summary information
|
||
|
|
about the journal receivers that are or were attached to the specified journal
|
||
|
|
and are still known to the system.</dd>
|
||
|
|
<dt id="x2035992" class="bold">
|
||
|
|
<a name="x2035992"></a>receive ready (RR)</dt>
|
||
|
|
<dd>In communications,
|
||
|
|
a data link command or response that indicates that a station is ready to
|
||
|
|
receive protocol data units. Receive ready also acknowledges receipt of protocol
|
||
|
|
data units.</dd>
|
||
|
|
<dt id="x2091280" class="bold">
|
||
|
|
<a name="x2091280"></a>receive timeout</dt>
|
||
|
|
<dd>In data communications,
|
||
|
|
a condition that occurs when no data is received in a given period of time.</dd>
|
||
|
|
<dt id="x2036002" class="bold">
|
||
|
|
<a name="x2036002"></a>receiving cross-domain key</dt>
|
||
|
|
<dd>In Cryptographic
|
||
|
|
Support, a cross-domain key used to decrypt a data-encrypting key that was
|
||
|
|
encrypted by another location.</dd>
|
||
|
|
<dt id="x2036007" class="bold">
|
||
|
|
<a name="x2036007"></a>receptacle</dt>
|
||
|
|
<dd>A hollowed electrical
|
||
|
|
fitting that contains the live parts of a circuit.</dd>
|
||
|
|
<dt id="x2036012" class="bold">
|
||
|
|
<a name="x2036012"></a>recipient address</dt>
|
||
|
|
<dd>A string of data
|
||
|
|
that represents the address associated with the recipient of the message.
|
||
|
|
The contents and format of the string are not defined by the mail server framework.
|
||
|
|
The address type associated with the recipient address is assumed to define
|
||
|
|
the contents of the recipient address field.</dd>
|
||
|
|
<dt id="x2036017" class="bold">
|
||
|
|
<a name="x2036017"></a>recipient history tree</dt>
|
||
|
|
<dd>A structure
|
||
|
|
that represents the changes to the recipient list, so that a recipient can
|
||
|
|
be traced back to the recipient entry in the original recipient list passed
|
||
|
|
using the Create Mail Message application program interface (API).</dd>
|
||
|
|
<dt id="x2036022" class="bold">
|
||
|
|
<a name="x2036022"></a>recombining</dt>
|
||
|
|
<dd>In OSI, a function performed
|
||
|
|
by an entity that is the reverse of splitting.</dd>
|
||
|
|
<dt id="x2036027" class="bold">
|
||
|
|
<a name="x2036027"></a>Recommendation X.21 (X.21)</dt>
|
||
|
|
<dd>A document,
|
||
|
|
CCITT Recommendation X.21, that outlines standards for a general-purpose interface
|
||
|
|
between data terminal equipment (DTE) and data circuit-terminating equipment
|
||
|
|
(DCE) for synchronous operations on a public data network.</dd>
|
||
|
|
<dt id="x2036032" class="bold">
|
||
|
|
<a name="x2036032"></a>Recommendation X.21 bis</dt>
|
||
|
|
<dd>A document,
|
||
|
|
CCITT Recommendation X.21 bis, that outlines standards for the interface between
|
||
|
|
data terminal equipment (DTE) and V-series data circuit-terminating equipment
|
||
|
|
(DCE) for synchronous operations on a public data network.</dd>
|
||
|
|
<dt id="x2036042" class="bold">
|
||
|
|
<a name="x2036042"></a>Recommendation X.31</dt>
|
||
|
|
<dd>A document, CCITT
|
||
|
|
Recommendation X.31, that outlines standards for the X.25 protocol over integrated
|
||
|
|
services digital networks (ISDNs).</dd>
|
||
|
|
<dt id="x2004028" class="bold">
|
||
|
|
<a name="x2004028"></a>record</dt>
|
||
|
|
<dd>(1) A group of related data, words,
|
||
|
|
or fields treated as a unit, such as one name, address, and telephone number.</dd>
|
||
|
|
<dd>(2) In COBOL, the most inclusive data item. The level-number for
|
||
|
|
a record is 01. A record can be either an elementary item or a group item.</dd>
|
||
|
|
<dt id="x2036053" class="bold">
|
||
|
|
<a name="x2036053"></a>record address file</dt>
|
||
|
|
<dd>In RPG, an input
|
||
|
|
file that indicates which records are to be read from another file and the
|
||
|
|
order in which the records are to be read.</dd>
|
||
|
|
<dt id="x2036058" class="bold">
|
||
|
|
<a name="x2036058"></a>record area</dt>
|
||
|
|
<dd>In COBOL, a storage area
|
||
|
|
in which a record described in a record description entry in the File Section
|
||
|
|
is processed.</dd>
|
||
|
|
<dt id="x2036063" class="bold">
|
||
|
|
<a name="x2036063"></a>record control byte (RCB)</dt>
|
||
|
|
<dd>In multileaving
|
||
|
|
telecommunications access method (MTAM), a control character used to identify
|
||
|
|
each record type within a transmission block.</dd>
|
||
|
|
<dt id="x2036068" class="bold">
|
||
|
|
<a name="x2036068"></a>record description entry</dt>
|
||
|
|
<dd>In COBOL,
|
||
|
|
the total set of data description entries associated with a particular record.</dd>
|
||
|
|
<dt id="x2036073" class="bold">
|
||
|
|
<a name="x2036073"></a>record format</dt>
|
||
|
|
<dd>A named part of a file
|
||
|
|
that identifies records of a specified record format description.</dd>
|
||
|
|
<dt id="x2036078" class="bold">
|
||
|
|
<a name="x2036078"></a>record format definition</dt>
|
||
|
|
<dd>In IDDU,
|
||
|
|
information that describes the arrangement or layout of fields in a record.
|
||
|
|
A record format definition resides in a data dictionary.</dd>
|
||
|
|
<dt id="x2036083" class="bold">
|
||
|
|
<a name="x2036083"></a>record format description</dt>
|
||
|
|
<dd>A description
|
||
|
|
of the characteristics of the fields (for example, type and length) and the
|
||
|
|
arrangement of the fields in a record created by the user.</dd>
|
||
|
|
<dt id="x2036088" class="bold">
|
||
|
|
<a name="x2036088"></a>record ID code</dt>
|
||
|
|
<dd>See <a href="rzaatr.htm#x2036092">record identification code</a>.</dd>
|
||
|
|
<dt id="x2036092" class="bold">
|
||
|
|
<a name="x2036092"></a>record identification code (record ID code)</dt>
|
||
|
|
<dd>Characters placed in a record to identify the record format.</dd>
|
||
|
|
<dt id="x2036097" class="bold">
|
||
|
|
<a name="x2036097"></a>record identifying indicator</dt>
|
||
|
|
<dd>An indicator
|
||
|
|
that identifies the record just read.</dd>
|
||
|
|
<dt id="x2036102" class="bold">
|
||
|
|
<a name="x2036102"></a>record key</dt>
|
||
|
|
<dd>(1) In COBOL, a key field
|
||
|
|
whose contents identify a record within an indexed file.</dd>
|
||
|
|
<dd>(2) In RPG,
|
||
|
|
all the key fields defined for the record type.</dd>
|
||
|
|
<dt id="x2036110" class="bold">
|
||
|
|
<a name="x2036110"></a>record layout</dt>
|
||
|
|
<dd>In AFP™ Utilities, a
|
||
|
|
part of the printout format definition that defines how each field of a database
|
||
|
|
file record is formatted and printed by the print format utility.</dd>
|
||
|
|
<dt id="x2036115" class="bold">
|
||
|
|
<a name="x2036115"></a>record-level specifications</dt>
|
||
|
|
<dd>Data
|
||
|
|
description specifications coded on the same line as a record format name
|
||
|
|
or on lines immediately following a record format name (until the first field
|
||
|
|
is specified).</dd>
|
||
|
|
<dt id="x2091295" class="bold">
|
||
|
|
<a name="x2091295"></a>record name</dt>
|
||
|
|
<dd>In COBOL, a user-defined
|
||
|
|
word that names a record described in a record description entry in the Data
|
||
|
|
Division of a COBOL program.</dd>
|
||
|
|
<dt id="x2036125" class="bold">
|
||
|
|
<a name="x2036125"></a>record number</dt>
|
||
|
|
<dd>In COBOL, the ordinal
|
||
|
|
number of a record in the file whose organization is sequential.</dd>
|
||
|
|
<dt id="x2036130" class="bold">
|
||
|
|
<a name="x2036130"></a>record selection</dt>
|
||
|
|
<dd>The process of selecting
|
||
|
|
particular records from a file and including the information from the records,
|
||
|
|
for example, in a report.</dd>
|
||
|
|
<dt id="x2036135" class="bold">
|
||
|
|
<a name="x2036135"></a>record separator</dt>
|
||
|
|
<dd>In BSC, a control
|
||
|
|
character used to indicate the end of one record and the beginning of another.</dd>
|
||
|
|
<dt id="x2036140" class="bold">
|
||
|
|
<a name="x2036140"></a>record type</dt>
|
||
|
|
<dd>The classification of
|
||
|
|
records in a file. Records of the same type have the same fields in the same
|
||
|
|
order. For program-described files, these records have record identification
|
||
|
|
codes; for externally described files, the records have the same record format
|
||
|
|
name.</dd>
|
||
|
|
<dt id="x2036145" class="bold">
|
||
|
|
<a name="x2036145"></a>recoverability</dt>
|
||
|
|
<dd>The degree or extent
|
||
|
|
to which the system can be restored to an operational condition after a system
|
||
|
|
failure.</dd>
|
||
|
|
<dt id="x2004053" class="bold">
|
||
|
|
<a name="x2004053"></a>recovery</dt>
|
||
|
|
<dd>(1) In Backup Recovery and Media
|
||
|
|
Services, the process of locating and restoring data in the event of partial
|
||
|
|
or total data destruction. The recovery service automatically locates the
|
||
|
|
correct media to be restored based on user-defined media management and recovery
|
||
|
|
requirements.</dd>
|
||
|
|
<dd>(2) The process of rebuilding a database or table space
|
||
|
|
that has become unusable because of hardware or software failure, or both.
|
||
|
|
The process can involve the restoration of a backup image and the use of database
|
||
|
|
logs or journals to reconstruct the changes that occurred to the database.</dd>
|
||
|
|
<dt id="x2036156" class="bold">
|
||
|
|
<a name="x2036156"></a>recovery domain</dt>
|
||
|
|
<dd>A subset of nodes
|
||
|
|
in a cluster that are grouped together for a common purpose, such as rebuilding
|
||
|
|
databases after a system failure. A domain represents those nodes of the cluster
|
||
|
|
where cluster resource exists.</dd>
|
||
|
|
<dt id="x2036161" class="bold">
|
||
|
|
<a name="x2036161"></a>recovery library</dt>
|
||
|
|
<dd>The library containing
|
||
|
|
information related to recovery of database operations from system failures.
|
||
|
|
Named QRECOVERY.</dd>
|
||
|
|
<dt id="x2036166" class="bold">
|
||
|
|
<a name="x2036166"></a>recovery policy</dt>
|
||
|
|
<dd>In Backup Recovery
|
||
|
|
and Media Services, a policy that defines the default controls and values
|
||
|
|
to be used in recovery operations.</dd>
|
||
|
|
<dt id="x2036176" class="bold">
|
||
|
|
<a name="x2036176"></a>recursion</dt>
|
||
|
|
<dd>A programming technique
|
||
|
|
in which a program or routine calls itself to perform successive steps in
|
||
|
|
an operation, with each step using the output of the preceding step.</dd>
|
||
|
|
<dt id="x2036181" class="bold">
|
||
|
|
<a name="x2036181"></a>recursion level</dt>
|
||
|
|
<dd>The position of a
|
||
|
|
program in a call stack. The first occurrence of a program in a job has a
|
||
|
|
recursion level of 1, the second occurrence of the same program has a recursion
|
||
|
|
level of 2, and so on.</dd>
|
||
|
|
<dt id="x2036186" class="bold">
|
||
|
|
<a name="x2036186"></a>recursive</dt>
|
||
|
|
<dd>Pertaining to a program
|
||
|
|
or routine that calls itself after each run until it is interrupted.</dd>
|
||
|
|
<dt id="x2036191" class="bold">
|
||
|
|
<a name="x2036191"></a>recursive mutex</dt>
|
||
|
|
<dd>A read/write lock
|
||
|
|
that is acquired again by the owning thread.</dd>
|
||
|
|
<dt id="x2036196" class="bold">
|
||
|
|
<a name="x2036196"></a>recursive procedure</dt>
|
||
|
|
<dd>An active procedure
|
||
|
|
that can be called from within itself or from within another active procedure.</dd>
|
||
|
|
<dt id="x2036201" class="bold">
|
||
|
|
<a name="x2036201"></a>recursive program</dt>
|
||
|
|
<dd>A program that
|
||
|
|
can call itself, or be called by another program, and repeat indefinitely
|
||
|
|
until a specified condition is met.</dd>
|
||
|
|
<dt id="x2036206" class="bold">
|
||
|
|
<a name="x2036206"></a>reduced instruction set computer (RISC)</dt>
|
||
|
|
<dd>A computer that uses a small, simplified set of frequently used instructions
|
||
|
|
for rapid processing. See also <a href="rzaatc.htm#x2017856">complex instruction set
|
||
|
|
computer</a>.</dd>
|
||
|
|
<dt id="x2036211" class="bold">
|
||
|
|
<a name="x2036211"></a>Redundant Array of Independent Disks (RAID)</dt>
|
||
|
|
<dd>A collection of two or more disk physical drives that present to the
|
||
|
|
host an image of one or more logical disk drives. In the event of a single
|
||
|
|
physical device failure, the data can be read or regenerated from the other
|
||
|
|
disk drives in the array due to data redundancy. See also <a href="rzaatd.htm#x2020414">device parity protection</a>, <a href="rzaata.htm#x2014057">array</a>.</dd>
|
||
|
|
<dt id="x2036216" class="bold">
|
||
|
|
<a name="x2036216"></a>reentrant</dt>
|
||
|
|
<dd>The attribute of a program
|
||
|
|
or routine that allows the same copy of the program or routine to be used
|
||
|
|
concurrently by two or more tasks.</dd>
|
||
|
|
<dt id="x2036221" class="bold">
|
||
|
|
<a name="x2036221"></a>reference</dt>
|
||
|
|
<dd>In VisualAge® RPG, information
|
||
|
|
from a physical source file that may be extracted at build time. Any changes
|
||
|
|
made to the original source must be recompiled to reflect the changes at run
|
||
|
|
time.</dd>
|
||
|
|
<dt id="x2036226" class="bold">
|
||
|
|
<a name="x2036226"></a>reference code</dt>
|
||
|
|
<dd>A group of characters
|
||
|
|
that identifies the machine status or a specific error condition.</dd>
|
||
|
|
<dt id="x2036231" class="bold">
|
||
|
|
<a name="x2036231"></a>reference code translation table</dt>
|
||
|
|
<dd>An object that contains reference code and field-replaceable-unit (FRU) code
|
||
|
|
records. These records are used to report hardware errors and do problem analysis
|
||
|
|
and resolution. The system-recognized identifier for the object type is *RCT.</dd>
|
||
|
|
<dt id="x2036241" class="bold">
|
||
|
|
<a name="x2036241"></a>referenced window record</dt>
|
||
|
|
<dd>In DDS,
|
||
|
|
a record containing the WINDOW keyword that identifies the name of a window
|
||
|
|
definition record.</dd>
|
||
|
|
<dt id="x2036246" class="bold">
|
||
|
|
<a name="x2036246"></a>reference format</dt>
|
||
|
|
<dd>A format that provides
|
||
|
|
a standard method for describing COBOL source programs.</dd>
|
||
|
|
<dt id="x2036251" class="bold">
|
||
|
|
<a name="x2036251"></a>reference line</dt>
|
||
|
|
<dd>In Business Graphics
|
||
|
|
Utility, a straight line parallel to either the vertical or horizontal axis
|
||
|
|
relative to which data values are plotted on a chart. Sometimes called a translated
|
||
|
|
axis line.</dd>
|
||
|
|
<dt id="x2036256" class="bold">
|
||
|
|
<a name="x2036256"></a>reference modification</dt>
|
||
|
|
<dd>In COBOL,
|
||
|
|
a method of establishing and referring to a data item by specifying a leftmost
|
||
|
|
character position and length within a character string.</dd>
|
||
|
|
<dt id="x2036261" class="bold">
|
||
|
|
<a name="x2036261"></a>reference modifier</dt>
|
||
|
|
<dd>In COBOL, the
|
||
|
|
leftmost character position and the length of a character string used to establish
|
||
|
|
and refer to a data item.</dd>
|
||
|
|
<dt id="x2036266" class="bold">
|
||
|
|
<a name="x2036266"></a>reference modify</dt>
|
||
|
|
<dd>To establish and
|
||
|
|
refer to a COBOL data item by specifying a leftmost character position and
|
||
|
|
length within a character string.</dd>
|
||
|
|
<dt id="x2036276" class="bold">
|
||
|
|
<a name="x2036276"></a>reference phrase</dt>
|
||
|
|
<dd>The text that is
|
||
|
|
highlighted and preceded by a single-character input field used to signify
|
||
|
|
the existence of a hypertext link.</dd>
|
||
|
|
<dt id="x2004096" class="bold">
|
||
|
|
<a name="x2004096"></a>referential constraint</dt>
|
||
|
|
<dd>The requirement
|
||
|
|
that the nonnull values of a designated foreign key are valid only if they
|
||
|
|
also appear as values of the primary key of the parent table. The referential
|
||
|
|
constraint is always defined from the perspective of the dependent file. See
|
||
|
|
also <a href="rzaatr.htm#x2004164">relationship</a>, <a href="rzaatu.htm#x2005538">unique
|
||
|
|
constraint</a>.</dd>
|
||
|
|
<dt id="x2036289" class="bold">
|
||
|
|
<a name="x2036289"></a>referential cycle</dt>
|
||
|
|
<dd>(1) A set of referential
|
||
|
|
constraints such that each table in the set is a descendent of itself.</dd>
|
||
|
|
<dd>(2) See <a href="rzaatc.htm#x2046901">constraint cycle</a>.</dd>
|
||
|
|
<dt id="x2004101" class="bold">
|
||
|
|
<a name="x2004101"></a>referential integrity</dt>
|
||
|
|
<dd>The state of
|
||
|
|
a database in which all values of all foreign keys are valid. Maintaining
|
||
|
|
referential integrity requires the enforcement of a referential constraint
|
||
|
|
on all operations that change the data in a table where the referential constraints
|
||
|
|
are defined.</dd>
|
||
|
|
<dt id="x2036300" class="bold">
|
||
|
|
<a name="x2036300"></a>referral</dt>
|
||
|
|
<dd>In the Lightweight Directory
|
||
|
|
Access Protocol (LDAP), a pointer from one LDAP directory server to another.</dd>
|
||
|
|
<dt id="x2036305" class="bold">
|
||
|
|
<a name="x2036305"></a>reflective marker</dt>
|
||
|
|
<dd>In hardware, reflective
|
||
|
|
material placed on magnetic tape to indicate the beginning or ending of the
|
||
|
|
recording area.</dd>
|
||
|
|
<dt id="x2036309" class="bold">
|
||
|
|
<a name="x2036309"></a>register</dt>
|
||
|
|
<dd>(1) To insert authorization
|
||
|
|
and authentication information into binding information.</dd>
|
||
|
|
<dd>(2) In the
|
||
|
|
hierarchical file system, to make an underlying file system and the specific
|
||
|
|
functions it supports known to the application programming interface layer
|
||
|
|
and accessible to user applications.</dd>
|
||
|
|
<dd>(3) An internal computer component
|
||
|
|
capable of storing a specified amount of data and accepting or transferring
|
||
|
|
this data rapidly.</dd>
|
||
|
|
<dt id="x2036324" class="bold">
|
||
|
|
<a name="x2036324"></a>registered enterprise-unique identifier</dt>
|
||
|
|
<dd>A name given to an entire network that makes the network unique among
|
||
|
|
other networks, including IBM® networks. New users are requested to register the network
|
||
|
|
name with IBM if they plan to communicate with IBM networks (for PTF information, for example).</dd>
|
||
|
|
<dt id="x2036329" class="bold">
|
||
|
|
<a name="x2036329"></a>registered filter</dt>
|
||
|
|
<dd>A filter that allows
|
||
|
|
more than one active filter for alerts and problem logs. When a filter is
|
||
|
|
registered, the system can send notification of events to a data queue. Registered
|
||
|
|
filters behave slightly different than filters exposed through the network
|
||
|
|
attributes or system value commands.</dd>
|
||
|
|
<dt id="x2004119" class="bold">
|
||
|
|
<a name="x2004119"></a>registration</dt>
|
||
|
|
<dd>(1) In X.25, the process
|
||
|
|
used between a DTE and a DCE to establish an agreement on which optional user
|
||
|
|
facilities will be in effect. For example, the DTE can request that the DCE
|
||
|
|
agree to or stop a previous agreement for an optional user facility. Also,
|
||
|
|
a DCE can indicate which optional user facilities are available or which optional
|
||
|
|
user facilities are currently in effect. The negotiation is accomplished through
|
||
|
|
the exchange of registration packets.</dd>
|
||
|
|
<dd>(2) In OSI, the process of obtaining
|
||
|
|
identifiers for objects from the appropriate naming authorities. Registered
|
||
|
|
identifiers should be obtained for the following objects, which relate to
|
||
|
|
OSI Communications Subsystem operations: (a) NSAP addresses, (b) DTE addresses,
|
||
|
|
(c) abstract syntaxes, (d) application contexts, and (e) application entities.</dd>
|
||
|
|
<dt id="x2036340" class="bold">
|
||
|
|
<a name="x2036340"></a>registration facility</dt>
|
||
|
|
<dd>A service that
|
||
|
|
provides storage and retrieval operations for i5/OS™ and non-i5/OS exit points and exit programs.</dd>
|
||
|
|
<dt id="x2036345" class="bold">
|
||
|
|
<a name="x2036345"></a>registration facility repository</dt>
|
||
|
|
<dd>The repository that contains information about the i5/OS and non-i5/OS exit points and exit programs.</dd>
|
||
|
|
<dt id="x2004129" class="bold">
|
||
|
|
<a name="x2004129"></a>registry database</dt>
|
||
|
|
<dd>In a z/OS® or OS/390® environment,
|
||
|
|
a database of security information about principals, groups, organizations,
|
||
|
|
accounts, and security policies.</dd>
|
||
|
|
<dt id="x2036365" class="bold">
|
||
|
|
<a name="x2036365"></a>REJ</dt>
|
||
|
|
<dd>See <a href="rzaatr.htm#x2036369">reject</a>.</dd>
|
||
|
|
<dt id="x2036369" class="bold">
|
||
|
|
<a name="x2036369"></a>reject (REJ)</dt>
|
||
|
|
<dd>In communications, a
|
||
|
|
data link command or response used to request the resending of information
|
||
|
|
frames.</dd>
|
||
|
|
<dt id="x2036374" class="bold">
|
||
|
|
<a name="x2036374"></a>rejoin</dt>
|
||
|
|
<dd>To become an active member
|
||
|
|
of an entity after having been a nonparticipating member.</dd>
|
||
|
|
<dt id="x2036379" class="bold">
|
||
|
|
<a name="x2036379"></a>relational character</dt>
|
||
|
|
<dd>In COBOL, one
|
||
|
|
of the characters that express a relationship between two operands: = (equal
|
||
|
|
to), > (greater than), < (less than).</dd>
|
||
|
|
<dt id="x2036384" class="bold">
|
||
|
|
<a name="x2036384"></a>relational checking</dt>
|
||
|
|
<dd>(1) The evaluation
|
||
|
|
of the operands in a relational expression, based on the relational operator
|
||
|
|
used.</dd>
|
||
|
|
<dd>(2) In RPG, tests performed against two statements in a source
|
||
|
|
program to ensure that the statements are valid (for example, a GOTO operation
|
||
|
|
must have an associated TAG operation). This type of checking is done only
|
||
|
|
by the compiler as opposed to single-statement syntax checking that is done
|
||
|
|
by the SEU function.</dd>
|
||
|
|
<dt id="x2036392" class="bold">
|
||
|
|
<a name="x2036392"></a>relational condition</dt>
|
||
|
|
<dd>In COBOL, a
|
||
|
|
condition that relates two arithmetic expressions, data items, or both.</dd>
|
||
|
|
<dt id="x2036397" class="bold">
|
||
|
|
<a name="x2036397"></a>relational data</dt>
|
||
|
|
<dd>Data stored in a
|
||
|
|
relational database management system (DBMS).</dd>
|
||
|
|
<dt id="x2004149" class="bold">
|
||
|
|
<a name="x2004149"></a>relational database (RDB)</dt>
|
||
|
|
<dd>A database
|
||
|
|
that can be perceived as a set of tables and manipulated in accordance with
|
||
|
|
the relational model of data. Each database includes a set of system catalog
|
||
|
|
tables that describe the logical and physical structure of the data, a configuration
|
||
|
|
file containing the parameter values allocated for the database, and a recovery
|
||
|
|
log with ongoing transactions and archivable transactions.</dd>
|
||
|
|
<dt id="x2004154" class="bold">
|
||
|
|
<a name="x2004154"></a>relational database management system (RDBMS)</dt>
|
||
|
|
<dd>A collection of hardware and software that organizes and provides
|
||
|
|
access to a relational database.</dd>
|
||
|
|
<dt id="x2036411" class="bold">
|
||
|
|
<a name="x2036411"></a>relational expression</dt>
|
||
|
|
<dd>A logical statement
|
||
|
|
that describes the relationship (such as greater than or equal to) of two
|
||
|
|
arithmetic expressions or data items.</dd>
|
||
|
|
<dt id="x2036416" class="bold">
|
||
|
|
<a name="x2036416"></a>relational operator</dt>
|
||
|
|
<dd>(1) Any of the set
|
||
|
|
of operators that express an arithmetic condition that can be either true
|
||
|
|
or false. The operators are: .GT., .GE., .LT., .LE., .EQ., and .NE.. They
|
||
|
|
are defined as greater than, greater than or equal to, less than, less than
|
||
|
|
or equal to, equal to, and not equal to, respectively.</dd>
|
||
|
|
<dd>(2) The reserved
|
||
|
|
words or symbols used to express a relational condition or a relational expression.</dd>
|
||
|
|
<dd>(3) In COBOL, a reserved word, a relational character, a group of
|
||
|
|
consecutive reserved words, or a group of consecutive reserved words and relational
|
||
|
|
characters used to express a relational condition.</dd>
|
||
|
|
<dt id="x2004164" class="bold">
|
||
|
|
<a name="x2004164"></a>relationship</dt>
|
||
|
|
<dd>In the Application Development
|
||
|
|
Manager feature of the Application Development ToolSet licensed program, a
|
||
|
|
definition of the dependency between two parts.</dd>
|
||
|
|
<dt id="x2036430" class="bold">
|
||
|
|
<a name="x2036430"></a>relative data</dt>
|
||
|
|
<dd>In Business Graphics
|
||
|
|
Utility, values in a computer image that specify points relative to other
|
||
|
|
points in the image.</dd>
|
||
|
|
<dt id="x2036435" class="bold">
|
||
|
|
<a name="x2036435"></a>relative distinguished name (RDN)</dt>
|
||
|
|
<dd>The part of an object name that is an attribute of the object itself.</dd>
|
||
|
|
<dt id="x2036443" class="bold">
|
||
|
|
<a name="x2036443"></a>relative end position</dt>
|
||
|
|
<dd>In RPG, an
|
||
|
|
entry on the output specifications that indicates the number of blank positions
|
||
|
|
that are to appear between a field or constant defined on one specification
|
||
|
|
line and the field or constant defined on the preceding specification line.
|
||
|
|
See also <a href="rzaate.htm#x2027138">exact end position</a>.</dd>
|
||
|
|
<dt id="x2036448" class="bold">
|
||
|
|
<a name="x2036448"></a>relative file number</dt>
|
||
|
|
<dd>In the DDS for
|
||
|
|
a join logical file, a sequential number assigned to a physical file based
|
||
|
|
on the position of that file on the JFILE keyword specification.</dd>
|
||
|
|
<dt id="x2036458" class="bold">
|
||
|
|
<a name="x2036458"></a>relative host name</dt>
|
||
|
|
<dd>The specific subname
|
||
|
|
of a fully qualified host name. For example, smith is a relative host name
|
||
|
|
for smith.endicott.ibm.com.</dd>
|
||
|
|
<dt id="x2036453" class="bold">
|
||
|
|
<a name="x2036453"></a>relative key</dt>
|
||
|
|
<dd>In COBOL, an unsigned
|
||
|
|
number that can be used directly by the system to locate a record in a file.</dd>
|
||
|
|
<dt id="x2036463" class="bold">
|
||
|
|
<a name="x2036463"></a>relative-name format</dt>
|
||
|
|
<dd>A print descriptor
|
||
|
|
naming convention that uses group alias names instead of system-specific (actual)
|
||
|
|
group names.</dd>
|
||
|
|
<dt id="x2036468" class="bold">
|
||
|
|
<a name="x2036468"></a>relative organization</dt>
|
||
|
|
<dd>In COBOL, the
|
||
|
|
file organization in which each record is uniquely identified by a positive
|
||
|
|
number value that specifies the position in the file relative to the first
|
||
|
|
record.</dd>
|
||
|
|
<dt id="x2036473" class="bold">
|
||
|
|
<a name="x2036473"></a>relative path name</dt>
|
||
|
|
<dd>A string of characters
|
||
|
|
used to refer to an object, starting at some point in the directory hierarchy
|
||
|
|
other than the root. A relative path name does not begin with a slash (/).
|
||
|
|
The starting point is frequently a user's current directory. See also <a href="rzaata.htm#x2012721">absolute path name</a>.</dd>
|
||
|
|
<dt id="x2036478" class="bold">
|
||
|
|
<a name="x2036478"></a>relative positional pattern</dt>
|
||
|
|
<dd>In REXX,
|
||
|
|
the part of a parsing template that uses a plus or minus sign to indicate
|
||
|
|
movement relative to a previous pattern match.</dd>
|
||
|
|
<dt id="x2036483" class="bold">
|
||
|
|
<a name="x2036483"></a>relative record number</dt>
|
||
|
|
<dd>(1) In COBOL,
|
||
|
|
the ordinal number of a record in a file whose organization is relative. This
|
||
|
|
number is treated as a numeric constant that is an integer.</dd>
|
||
|
|
<dd>(2) A
|
||
|
|
number that specifies the relationship between the location of a record and
|
||
|
|
the beginning of a database file, member, or subfile. For example, the first
|
||
|
|
record in a database file, member, or subfile has a relative record number
|
||
|
|
of 1.</dd>
|
||
|
|
<dt id="x2036491" class="bold">
|
||
|
|
<a name="x2036491"></a>relative-size pie</dt>
|
||
|
|
<dd>In Business Graphics
|
||
|
|
Utility, a piece on a pie chart drawn proportionally to another piece.</dd>
|
||
|
|
<dt id="x2036506" class="bold">
|
||
|
|
<a name="x2036506"></a>relay agent</dt>
|
||
|
|
<dd>A program that delivers
|
||
|
|
Dynamic Host Configuration Protocol (DHCP) packets to a local system.</dd>
|
||
|
|
<dt id="x2036501" class="bold">
|
||
|
|
<a name="x2036501"></a>relay node</dt>
|
||
|
|
<dd>See <a href="rzaatr.htm#x2036511">relay open system</a>. See also <a href="rzaata.htm#x2013221">adjacent destination
|
||
|
|
node</a>.</dd>
|
||
|
|
<dt id="x2036511" class="bold">
|
||
|
|
<a name="x2036511"></a>relay open system</dt>
|
||
|
|
<dd>In OSI architecture,
|
||
|
|
an open system that forwards data received from one open system to another
|
||
|
|
open system. (T) See also <a href="rzaata.htm#x2013221">adjacent destination node</a>.</dd>
|
||
|
|
<dt id="x2036516" class="bold">
|
||
|
|
<a name="x2036516"></a>release</dt>
|
||
|
|
<dd>A distribution of a new product
|
||
|
|
or new function and authorized program analysis report (APAR) fixes for an
|
||
|
|
existing product. The first version of a product is announced as Release 1
|
||
|
|
Modification Level 0.</dd>
|
||
|
|
<dt id="x2036521" class="bold">
|
||
|
|
<a name="x2036521"></a>released state</dt>
|
||
|
|
<dd>The state of a connection
|
||
|
|
that results in a disconnect of the connection at the next commit operation.
|
||
|
|
See also <a href="rzaath.htm#x2024320">held state</a>.</dd>
|
||
|
|
<dt id="x2036526" class="bold">
|
||
|
|
<a name="x2036526"></a>release lever</dt>
|
||
|
|
<dd>A part that unlocks
|
||
|
|
the device so it can be pulled out of the rack on the slides.</dd>
|
||
|
|
<dt id="x2036531" class="bold">
|
||
|
|
<a name="x2036531"></a>release-program-device operation</dt>
|
||
|
|
<dd>An operation that makes a program device not available for input/output operations.
|
||
|
|
See also <a href="rzaata.htm#x2012956">acquire-program-device operation</a>.</dd>
|
||
|
|
<dt id="x2036536" class="bold">
|
||
|
|
<a name="x2036536"></a>release token</dt>
|
||
|
|
<dd>In OSI, the token that
|
||
|
|
controls the orderly release of an association.</dd>
|
||
|
|
<dt id="x2036541" class="bold">
|
||
|
|
<a name="x2036541"></a>reliable transfer server (RTS)</dt>
|
||
|
|
<dd>In
|
||
|
|
OSI X.400, a portion of X.400 that is responsible for creating and maintaining
|
||
|
|
application associations and for reliably transferring distributions between
|
||
|
|
message transfer agents.</dd>
|
||
|
|
<dt id="x2036546" class="bold">
|
||
|
|
<a name="x2036546"></a>REM</dt>
|
||
|
|
<dd>See <a href="rzaatr.htm#x2037225">ring
|
||
|
|
error monitor</a>.</dd>
|
||
|
|
<dt id="x2004179" class="bold">
|
||
|
|
<a name="x2004179"></a>remote</dt>
|
||
|
|
<dd>Pertaining to a system, program,
|
||
|
|
or device that is accessed through a communications line.</dd>
|
||
|
|
<dt id="x2036553" class="bold">
|
||
|
|
<a name="x2036553"></a>Remote Abstract Window Toolkit for Java™</dt>
|
||
|
|
<dd>An implementation of the Abstract Window Toolkit (AWT) that allows Java applications to run on a host system that does not have a graphical
|
||
|
|
user interface (GUI). The server does not support locally attached graphic
|
||
|
|
workstations; therefore Remote AWT is necessary to allow graphical Java applications
|
||
|
|
to run on the server.</dd>
|
||
|
|
<dt id="x2036558" class="bold">
|
||
|
|
<a name="x2036558"></a>Remote Access Dial-In User Service</dt>
|
||
|
|
<dd>A server that authenticates a user's password and identification before sending
|
||
|
|
the information on to an Internet Service Provider (ISP) server. The server
|
||
|
|
also maintains accounting records of network usage for separate users. TCP/IP
|
||
|
|
services and applications, such as Point-to-Point Protocol (PPP), can rely
|
||
|
|
on a RADIUS server for authentication and accounting functions.</dd>
|
||
|
|
<dt id="x2036563" class="bold">
|
||
|
|
<a name="x2036563"></a>Remote Access Service</dt>
|
||
|
|
<dd>Windows NT® software that provides network capabilities over a modem link and contains
|
||
|
|
functions that support point-to-point wide area network connections. For i5/OS, this includes both outgoing (originator) and incoming (receiver) point-to-point
|
||
|
|
profile types and other services such as Remote Access Dial-in User Service
|
||
|
|
(RADIUS) and Dynamic Host Configuration Protocol (DHCP) client configuration.
|
||
|
|
Operations Console requires Windows NT users to have Remote Access
|
||
|
|
Service.</dd>
|
||
|
|
<dt id="x2036568" class="bold">
|
||
|
|
<a name="x2036568"></a>remote agent</dt>
|
||
|
|
<dd>In OSI, an agent process
|
||
|
|
on a remote node. See also <a href="rzaatl.htm#x2028885">local agent</a>.</dd>
|
||
|
|
<dt id="x2036573" class="bold">
|
||
|
|
<a name="x2036573"></a>remote application entity</dt>
|
||
|
|
<dd>In OSI,
|
||
|
|
an application entity on a remote node.</dd>
|
||
|
|
<dt id="x2036578" class="bold">
|
||
|
|
<a name="x2036578"></a>remote application process</dt>
|
||
|
|
<dd>In OSI,
|
||
|
|
an application process on a remote node. See also <a href="rzaatl.htm#x2028895">local
|
||
|
|
application process</a>.</dd>
|
||
|
|
<dt id="x2036583" class="bold">
|
||
|
|
<a name="x2036583"></a>remote bus adapter</dt>
|
||
|
|
<dd>A bus adapter
|
||
|
|
in an expansion unit. Optical cables from the local optical link cards in
|
||
|
|
the system unit plug into this card.</dd>
|
||
|
|
<dt id="x2036588" class="bold">
|
||
|
|
<a name="x2036588"></a>remote change management server (RCMS)</dt>
|
||
|
|
<dd>In retail communications and Point-of-Sale Utility, a store controller
|
||
|
|
program communicating over an SNA/SDLC network that connects a host processor
|
||
|
|
and a store controller. RCMS allows the NetView® Distribution Manager program to access
|
||
|
|
point-of-sale controller files. It also provides error reporting and recovery
|
||
|
|
for failures and data format conversion for files.</dd>
|
||
|
|
<dt id="x2036593" class="bold">
|
||
|
|
<a name="x2036593"></a>remote console</dt>
|
||
|
|
<dd>(1) The display device
|
||
|
|
that qualifies as a system console but is not directly attached to a system.
|
||
|
|
See also <a href="rzaatl.htm#x2028925">local console</a>.</dd>
|
||
|
|
<dd>(2) An Operations
|
||
|
|
Console configuration that allows a personal computer to dial into a local
|
||
|
|
console to gain console access to the system. See also <a href="rzaato.htm#x2032463">Operations Console</a>.</dd>
|
||
|
|
<dt id="x2036598" class="bold">
|
||
|
|
<a name="x2036598"></a>remote controller</dt>
|
||
|
|
<dd>A device or system,
|
||
|
|
attached to a communications line, that controls the operation of one or more
|
||
|
|
remote devices. See also <a href="rzaatl.htm#x2028920">local controller</a>.</dd>
|
||
|
|
<dt id="x2036608" class="bold">
|
||
|
|
<a name="x2036608"></a>remote control panel</dt>
|
||
|
|
<dd>A graphical
|
||
|
|
interface that is provided by Operations Console that allows control panel
|
||
|
|
operations to be performed from a remote location. This interface allows personal
|
||
|
|
computer access to the control panel that controls operating or servicing
|
||
|
|
the system.</dd>
|
||
|
|
<dt id="x2036613" class="bold">
|
||
|
|
<a name="x2036613"></a>remote device</dt>
|
||
|
|
<dd>A device that is connected
|
||
|
|
to a computer over a telecommunication line. See also <a href="rzaatl.htm#x2104832">local device</a>.</dd>
|
||
|
|
<dt id="x2036618" class="bold">
|
||
|
|
<a name="x2036618"></a>remote directory access</dt>
|
||
|
|
<dd>In OSI, the
|
||
|
|
process of accessing directory information that resides on a remote open system.</dd>
|
||
|
|
<dt id="x2036623" class="bold">
|
||
|
|
<a name="x2036623"></a>remote directory service</dt>
|
||
|
|
<dd>In OSI,
|
||
|
|
the service that enables a system to obtain directory service from another
|
||
|
|
system. In OSI Communications Subsystem, remote directory service requires
|
||
|
|
the availability of a directory system agent (DSA) from which a directory
|
||
|
|
user agent can obtain directory services using the X.500 directory access
|
||
|
|
protocol (DAP).</dd>
|
||
|
|
<dt id="x2036628" class="bold">
|
||
|
|
<a name="x2036628"></a>remote directory system agent</dt>
|
||
|
|
<dd>In
|
||
|
|
OSI, an application process on a remote node that provides directory service.</dd>
|
||
|
|
<dt id="x2036633" class="bold">
|
||
|
|
<a name="x2036633"></a>remote equipment</dt>
|
||
|
|
<dd>The modem and controller
|
||
|
|
that provides the communications connection between a communications line
|
||
|
|
and a remote device or system. This remote equipment is at the other end of
|
||
|
|
a data link from the host system.</dd>
|
||
|
|
<dt id="x2036638" class="bold">
|
||
|
|
<a name="x2036638"></a>remote input/output (RIO)</dt>
|
||
|
|
<dd>A type
|
||
|
|
of hardware architecture that facilitates faster input/output connection speeds
|
||
|
|
between a system unit and expansion units.</dd>
|
||
|
|
<dt id="x2036643" class="bold">
|
||
|
|
<a name="x2036643"></a>remote job entry</dt>
|
||
|
|
<dd>The submission of
|
||
|
|
a job through an input unit that has access to a computer by means of a data
|
||
|
|
link.</dd>
|
||
|
|
<dt id="x2036648" class="bold">
|
||
|
|
<a name="x2036648"></a>remote journal network</dt>
|
||
|
|
<dd>An i5/OS environment
|
||
|
|
that includes a primary system source journal and target system journals.
|
||
|
|
The target system journals, associated by using the remote journal function,
|
||
|
|
are downstream from the primary system source journal.</dd>
|
||
|
|
<dt id="x2036653" class="bold">
|
||
|
|
<a name="x2036653"></a>remote location name</dt>
|
||
|
|
<dd>Any other system
|
||
|
|
with which a user's system can communicate in a network. This corresponds
|
||
|
|
to the remote location name specified in the communications configuration.
|
||
|
|
Equivalent to an SNA remote logical unit name. See also <a href="rzaatl.htm#x2028989">local location name</a>.</dd>
|
||
|
|
<dt id="x2036668" class="bold">
|
||
|
|
<a name="x2036668"></a>remote manager</dt>
|
||
|
|
<dd>In OSI, a managing
|
||
|
|
process on a remote node. See also <a href="rzaatl.htm#x2028999">local manager</a>.</dd>
|
||
|
|
<dt id="x2172783" class="bold">
|
||
|
|
<a name="x2172783"></a>Remote Method Invocation (RMI)</dt>
|
||
|
|
<dd>A
|
||
|
|
protocol that is used to communicate method invocations over a network. Java Remote Method Invocation is a distributed object model in which
|
||
|
|
the methods of remote objects written in the Java programming language can be invoked
|
||
|
|
from other Java virtual machines, possibly on different hosts.</dd>
|
||
|
|
<dt id="x2036678" class="bold">
|
||
|
|
<a name="x2036678"></a>remote name server</dt>
|
||
|
|
<dd>(1) A name server
|
||
|
|
that exists outside a local network.</dd>
|
||
|
|
<dd>(2) In TCP/IP, the function that
|
||
|
|
allows a system to get an internet address from a remote site rather than
|
||
|
|
from its own host table.</dd>
|
||
|
|
<dt id="x2036686" class="bold">
|
||
|
|
<a name="x2036686"></a>remote network address</dt>
|
||
|
|
<dd>In OSI, a
|
||
|
|
network address that identifies a remote node.</dd>
|
||
|
|
<dt id="x2036691" class="bold">
|
||
|
|
<a name="x2036691"></a>remote node</dt>
|
||
|
|
<dd>In OSI, any node other
|
||
|
|
than the local node. See also <a href="rzaatl.htm#x2029019">local node</a>.</dd>
|
||
|
|
<dt id="x2036696" class="bold">
|
||
|
|
<a name="x2036696"></a>remote NSAP</dt>
|
||
|
|
<dd>In OSI, a service access
|
||
|
|
point in the network layer of a remote node.</dd>
|
||
|
|
<dt id="x2036701" class="bold">
|
||
|
|
<a name="x2036701"></a>remote presentation address</dt>
|
||
|
|
<dd>In OSI,
|
||
|
|
a presentation address of an application entity on a remote node. See also <a href="rzaatl.htm#x2029044">local presentation address</a>.</dd>
|
||
|
|
<dt id="x2036706" class="bold">
|
||
|
|
<a name="x2036706"></a>remote printer queue</dt>
|
||
|
|
<dd>The name of
|
||
|
|
a printer queue on a remote system. For a remote system running i5/OS, this is the
|
||
|
|
name of an output queue on the remote system.</dd>
|
||
|
|
<dt id="x2036721" class="bold">
|
||
|
|
<a name="x2036721"></a>remote procedure call (RPC)</dt>
|
||
|
|
<dd>A protocol
|
||
|
|
that allows a program on a client computer to run a program on a server.</dd>
|
||
|
|
<dt id="x2036729" class="bold">
|
||
|
|
<a name="x2036729"></a>remote queue</dt>
|
||
|
|
<dd>A queue that belongs
|
||
|
|
to a remote queue manager. Programs can put messages on remote queues, but
|
||
|
|
they cannot get messages from remote queues. See also <a href="rzaatl.htm#x2029049">local queue</a>.</dd>
|
||
|
|
<dt id="x2036734" class="bold">
|
||
|
|
<a name="x2036734"></a>remote queue manager</dt>
|
||
|
|
<dd>To a program,
|
||
|
|
a queue manager that is not the one to which the program is connected. See
|
||
|
|
also <a href="rzaatl.htm#x2029054">local queue manager</a>.</dd>
|
||
|
|
<dt id="x2036739" class="bold">
|
||
|
|
<a name="x2036739"></a>remote queuing</dt>
|
||
|
|
<dd>In message queuing,
|
||
|
|
the provision of services to enable applications to put messages on queues
|
||
|
|
belonging to other queue managers.</dd>
|
||
|
|
<dt id="x2036744" class="bold">
|
||
|
|
<a name="x2036744"></a>remote service requester</dt>
|
||
|
|
<dd>In OSI,
|
||
|
|
a service requester process on a remote node. See also <a href="rzaatl.htm#x2029069">local service requester</a>.</dd>
|
||
|
|
<dt id="x2036749" class="bold">
|
||
|
|
<a name="x2036749"></a>remote system</dt>
|
||
|
|
<dd>Any other system in
|
||
|
|
the network with which your system can communicate. See also <a href="rzaatl.htm#x2029089">local system</a>.</dd>
|
||
|
|
<dt id="x2036754" class="bold">
|
||
|
|
<a name="x2036754"></a>remote terminal access method (RTAM)</dt>
|
||
|
|
<dd>A function of IBM System/370-type computers that controls operations between the Job
|
||
|
|
Entry Subsystems (JES2) (JES3) and remote work stations on the iSeries system.</dd>
|
||
|
|
<dt id="x2004199" class="bold">
|
||
|
|
<a name="x2004199"></a>remote unit of work (RUOW)</dt>
|
||
|
|
<dd>(1) A unit
|
||
|
|
of work that allows for the remote preparation and execution of SQL statements.</dd>
|
||
|
|
<dd>(2) The form of SQL distributed processing in which the application
|
||
|
|
is on a system different from the relational database, and a single application
|
||
|
|
server services all remote unit-of-work requests within a single logical unit
|
||
|
|
of work.</dd>
|
||
|
|
<dt id="x2105183" class="bold">
|
||
|
|
<a name="x2105183"></a>remote workstation</dt>
|
||
|
|
<dd>A workstation
|
||
|
|
that is connected to the system by data communications. See also <a href="rzaatl.htm#x2104856">local workstation</a>.</dd>
|
||
|
|
<dt id="x2036770" class="bold">
|
||
|
|
<a name="x2036770"></a>remote writer</dt>
|
||
|
|
<dd>A system program that
|
||
|
|
sends spooled files from an output queue to a remote system.</dd>
|
||
|
|
<dt id="x2036775" class="bold">
|
||
|
|
<a name="x2036775"></a>removable media</dt>
|
||
|
|
<dd>Volumes that can
|
||
|
|
be removed from the hardware devices (such as tape cartridges and optical
|
||
|
|
disks) where they are read and written.</dd>
|
||
|
|
<dt id="x2210138" class="bold">
|
||
|
|
<a name="x2210138"></a>renewable tickets</dt>
|
||
|
|
<dd>A ticket that contains
|
||
|
|
two expiration times: one that applies to the current instance of the ticket,
|
||
|
|
and one that applies to the latest permissible expiration of the ticket. Renewable
|
||
|
|
tickets are valid for an extended period of time while lessening the changes
|
||
|
|
for theft.</dd>
|
||
|
|
<dt id="x2004214" class="bold">
|
||
|
|
<a name="x2004214"></a>repeatable read</dt>
|
||
|
|
<dd>In DB2 UDB for iSeries, an isolation level that completely isolates an application process
|
||
|
|
from all other application processes that are running concurrently. At the
|
||
|
|
repeatable-read level, rows read during a unit of work cannot be changed by
|
||
|
|
application processes that are running concurrently until the unit of work
|
||
|
|
is complete, rows changed by application processes that are processing concurrently
|
||
|
|
cannot be read until they are committed by that application process, and phantom
|
||
|
|
rows are prevented. See also <a href="rzaatr.htm#x2004018">read stability</a>.</dd>
|
||
|
|
<dt id="x2036783" class="bold">
|
||
|
|
<a name="x2036783"></a>repetitive DO loop</dt>
|
||
|
|
<dd>In REXX, any instruction
|
||
|
|
that has either a repetitor phrase or a conditional phrase (or both). The
|
||
|
|
instruction list within the instruction is run zero or more times, controlled
|
||
|
|
by any repetitor phrase that is optionally changed by a conditional phrase.</dd>
|
||
|
|
<dt id="x2010609" class="bold">
|
||
|
|
<a name="x2010609"></a>replica</dt>
|
||
|
|
<dd>In the Lightweight Directory
|
||
|
|
Access Protocol (LDAP), a read-only server that contains the same data as
|
||
|
|
another server. Replicas are used to back up LDAP servers and to provide faster
|
||
|
|
searches by splitting requests among the main server and replica servers.</dd>
|
||
|
|
<dt id="x2036799" class="bold">
|
||
|
|
<a name="x2036799"></a>replicate</dt>
|
||
|
|
<dd>In a remote journal network,
|
||
|
|
to make a duplicate copy of a journal entry from a source journal to a target
|
||
|
|
journal.</dd>
|
||
|
|
<dt id="x2036804" class="bold">
|
||
|
|
<a name="x2036804"></a>replicate node</dt>
|
||
|
|
<dd>A complete copy of
|
||
|
|
a cluster resource that is kept up to date through replication. A node that
|
||
|
|
is designated a replicate node cannot become a backup node or a primary node.</dd>
|
||
|
|
<dt id="x2004229" class="bold">
|
||
|
|
<a name="x2004229"></a>replication</dt>
|
||
|
|
<dd>The process of copying
|
||
|
|
objects from one node in a cluster to one or more other nodes in the cluster,
|
||
|
|
which makes the objects on all the systems identical.</dd>
|
||
|
|
<dt id="x2036815" class="bold">
|
||
|
|
<a name="x2036815"></a>reply message</dt>
|
||
|
|
<dd>A type of message used
|
||
|
|
for replies to request messages. See also <a href="rzaatr.htm#x2036855">report message</a>, <a href="rzaatr.htm#x2036900">request message</a>.</dd>
|
||
|
|
<dt id="x2036820" class="bold">
|
||
|
|
<a name="x2036820"></a>reply-to address</dt>
|
||
|
|
<dd>A string of data
|
||
|
|
that represents the address to be replied to. The contents and format of the
|
||
|
|
string are not defined by the mail server framework. The address type associated
|
||
|
|
with the reply-to address is assumed to define the contents of the reply-to
|
||
|
|
address field.</dd>
|
||
|
|
<dt id="x2036825" class="bold">
|
||
|
|
<a name="x2036825"></a>reply-to queue</dt>
|
||
|
|
<dd>The name of a queue
|
||
|
|
to which the program that issued an MQPUT call wants a reply message or report
|
||
|
|
message sent.</dd>
|
||
|
|
<dt id="x2036830" class="bold">
|
||
|
|
<a name="x2036830"></a>report</dt>
|
||
|
|
<dd>In query management, the formatted
|
||
|
|
data that results from running a query and applying a form to it.</dd>
|
||
|
|
<dt id="x2036835" class="bold">
|
||
|
|
<a name="x2036835"></a>report break</dt>
|
||
|
|
<dd>In Query, a blank line
|
||
|
|
or new page that appears in a report when the contents of a specified field
|
||
|
|
in the report change. A report break can contain column summaries.</dd>
|
||
|
|
<dt id="x2036840" class="bold">
|
||
|
|
<a name="x2036840"></a>reporting node</dt>
|
||
|
|
<dd>In OSI, a node that
|
||
|
|
reports a message to a manager node.</dd>
|
||
|
|
<dt id="x2036845" class="bold">
|
||
|
|
<a name="x2036845"></a>report layout utility (RLU)</dt>
|
||
|
|
<dd>A function
|
||
|
|
of the Application Development ToolSet licensed program that is used to create,
|
||
|
|
change, and save report prototypes.</dd>
|
||
|
|
<dt id="x2036850" class="bold">
|
||
|
|
<a name="x2036850"></a>report line</dt>
|
||
|
|
<dd>In RLU, a record that
|
||
|
|
is part of a report prototype for which the user creates data description
|
||
|
|
specifications (DDS).</dd>
|
||
|
|
<dt id="x2036855" class="bold">
|
||
|
|
<a name="x2036855"></a>report message</dt>
|
||
|
|
<dd>A type of message
|
||
|
|
that gives information about another message. A report message can indicate
|
||
|
|
that a message has been delivered, has arrived at its destination, has expired,
|
||
|
|
or could not be processed for some reason. See also <a href="rzaatr.htm#x2036815">reply message</a>, <a href="rzaatr.htm#x2036900">request message</a>.</dd>
|
||
|
|
<dt id="x2134629" class="bold">
|
||
|
|
<a name="x2134629"></a>Report Program Generator (RPG)</dt>
|
||
|
|
<dd>A
|
||
|
|
programming language designed for writing application programs for business
|
||
|
|
data processing requirements. The application programs range from report writing
|
||
|
|
and inquiry programs to applications such as payroll, order entry, and production
|
||
|
|
planning.</dd>
|
||
|
|
<dt id="x2036860" class="bold">
|
||
|
|
<a name="x2036860"></a>report prototype</dt>
|
||
|
|
<dd>In RLU, a representation
|
||
|
|
of the image of a report that a user builds on a display and the printed report
|
||
|
|
image, both of which look like the actual listing created by an application
|
||
|
|
program. The report prototype, when saved as a DDS source member, can be used
|
||
|
|
to create a printer file, which, in turn, can be used by an application program
|
||
|
|
to create a report.</dd>
|
||
|
|
<dt id="x2036869" class="bold">
|
||
|
|
<a name="x2036869"></a>request</dt>
|
||
|
|
<dd>In OSI, a service primitive
|
||
|
|
issued by a service user to call a function supported by the service provider.</dd>
|
||
|
|
<dt id="x2004254" class="bold">
|
||
|
|
<a name="x2004254"></a>requester</dt>
|
||
|
|
<dd>(1) In iSeries Access, a
|
||
|
|
program that requests services from another program (a server). Each iSeries Access function
|
||
|
|
has a server and a requester.</dd>
|
||
|
|
<dd>(2) A workstation from which a user
|
||
|
|
can log on to a domain and use network resources.</dd>
|
||
|
|
<dt id="x2036885" class="bold">
|
||
|
|
<a name="x2036885"></a>request for price quotation (RPQ)</dt>
|
||
|
|
<dd>A customer request for a price quotation on alterations or additions to the
|
||
|
|
functional capabilities of a hardware product for a computing system or a
|
||
|
|
device. See also <a href="rzaatp.htm#x2064061">programming request for price quotation</a>.</dd>
|
||
|
|
<dt id="x2036890" class="bold">
|
||
|
|
<a name="x2036890"></a>request functional transmission</dt>
|
||
|
|
<dd>In multileaving telecommunications access method (MTAM), a control character
|
||
|
|
indicating a request for permission to send data. See also <a href="rzaatg.htm#x2023859">grant functional transmission</a>.</dd>
|
||
|
|
<dt id="x2036895" class="bold">
|
||
|
|
<a name="x2036895"></a>request header (RH)</dt>
|
||
|
|
<dd>In SNA, a 3-byte
|
||
|
|
header that precedes a request unit. The request header specifies the type
|
||
|
|
of request unit and contains control information associated with that request
|
||
|
|
unit. See also <a href="rzaatr.htm#x2037032">response header</a>.</dd>
|
||
|
|
<dt id="x2036900" class="bold">
|
||
|
|
<a name="x2036900"></a>request message</dt>
|
||
|
|
<dd>A type of message
|
||
|
|
used to request a reply from another program. See also <a href="rzaatr.htm#x2036815">reply message</a>, <a href="rzaatr.htm#x2036855">report message</a>.</dd>
|
||
|
|
<dt id="x2178344" class="bold">
|
||
|
|
<a name="x2178344"></a>request/reply</dt>
|
||
|
|
<dd>A type of messaging
|
||
|
|
application in which a request message is used to request a reply from another
|
||
|
|
application.</dd>
|
||
|
|
<dt id="x2036905" class="bold">
|
||
|
|
<a name="x2036905"></a>request unit (RU)</dt>
|
||
|
|
<dd>In SNA, a message
|
||
|
|
unit that contains control information such as a request code, or function
|
||
|
|
management (FM) headers, end-user data, or both.</dd>
|
||
|
|
<dt id="x2047001" class="bold">
|
||
|
|
<a name="x2047001"></a>required hyphen</dt>
|
||
|
|
<dd>A hyphen that is
|
||
|
|
not removed when the program adjusts lines. See also <a href="rzaats.htm#x2047006">syllable hyphen</a>.</dd>
|
||
|
|
<dt id="x2036910" class="bold">
|
||
|
|
<a name="x2036910"></a>reservation</dt>
|
||
|
|
<dd>In QoS, part of a resource
|
||
|
|
that has been dedicated for the use of a particular traffic type for a period
|
||
|
|
of time through the application of policies.</dd>
|
||
|
|
<dt id="x2036915" class="bold">
|
||
|
|
<a name="x2036915"></a>reserved memory</dt>
|
||
|
|
<dd>The area of main
|
||
|
|
storage between 640 KB and 1 MB on a personal computer. Reserved memory cannot
|
||
|
|
be used by adapters and special programs, such as expanded memory support.</dd>
|
||
|
|
<dt id="x2004259" class="bold">
|
||
|
|
<a name="x2004259"></a>reserved word</dt>
|
||
|
|
<dd>A word that is defined
|
||
|
|
in a programming language for a special purpose, and that must not appear
|
||
|
|
as a user-declared identifier.</dd>
|
||
|
|
<dt id="x2036923" class="bold">
|
||
|
|
<a name="x2036923"></a>reset (RST)</dt>
|
||
|
|
<dd>The reset logical unit
|
||
|
|
of work (LUW) state indicates that the current LUW has not yet begun to prepare
|
||
|
|
to commit. A failure during RST state results in a rollback of any pending
|
||
|
|
changes.</dd>
|
||
|
|
<dt id="x2036933" class="bold">
|
||
|
|
<a name="x2036933"></a>residual error</dt>
|
||
|
|
<dd>An error that is not
|
||
|
|
detected by the network layer. Examples of residual errors are loss, corruption,
|
||
|
|
duplication, and delivery out of sequence of TPDUs. See also <a href="rzaats.htm#x2038857">signaled error</a>.</dd>
|
||
|
|
<dt id="x2036938" class="bold">
|
||
|
|
<a name="x2036938"></a>resilient application</dt>
|
||
|
|
<dd>A server program
|
||
|
|
that can be restarted on a different node without requiring a user to reconfigure
|
||
|
|
the clients.</dd>
|
||
|
|
<dt id="x2036943" class="bold">
|
||
|
|
<a name="x2036943"></a>resilient resource</dt>
|
||
|
|
<dd>Data, a process,
|
||
|
|
or an application that can be recovered if a node in a cluster fails.</dd>
|
||
|
|
<dt id="x2036948" class="bold">
|
||
|
|
<a name="x2036948"></a>resolution</dt>
|
||
|
|
<dd>A measure of the sharpness
|
||
|
|
of an image, expressed as the number of lines per unit of length or the number
|
||
|
|
of points per unit of area discernible in that image.</dd>
|
||
|
|
<dt id="x2036953" class="bold">
|
||
|
|
<a name="x2036953"></a>resolve</dt>
|
||
|
|
<dd>In programming, to change
|
||
|
|
a predefined, symbolic value to the actual value of the item being processed.
|
||
|
|
For example, a symbolic value of *LAST defined for the name of a file member
|
||
|
|
is resolved to the name of the last member when the member is processed.</dd>
|
||
|
|
<dt id="x2036958" class="bold">
|
||
|
|
<a name="x2036958"></a>resolved import</dt>
|
||
|
|
<dd>An import whose type
|
||
|
|
and name exactly match the type and name of an export.</dd>
|
||
|
|
<dt id="x2004267" class="bold">
|
||
|
|
<a name="x2004267"></a>resource</dt>
|
||
|
|
<dd>(1) Any physical item or logical
|
||
|
|
item to be managed in an information system of an enterprise.</dd>
|
||
|
|
<dd>(2) Any facility of a computing system or operating system required by a job,
|
||
|
|
task, or executing program. Resources include main storage, input/output devices,
|
||
|
|
the processing unit, data sets, files, libraries, folders, and control or
|
||
|
|
processing programs. In WebSphere® MQ for z/OS, examples of resources are buffer pools,
|
||
|
|
page sets, log data sets, queues, and messages.</dd>
|
||
|
|
<dt id="x2004282" class="bold">
|
||
|
|
<a name="x2004282"></a>resource definition online (RDO)</dt>
|
||
|
|
<dd>In CICS® , a facility that allows the user to define certain CICS resources interactively
|
||
|
|
while CICS is running. Specifically, RDO allows the user to define terminals,
|
||
|
|
programs, and transactions interactively.</dd>
|
||
|
|
<dt id="x2036976" class="bold">
|
||
|
|
<a name="x2036976"></a>resource error counters</dt>
|
||
|
|
<dd>In OSI, counters
|
||
|
|
that keep track of errors that occur in layers and other resources.</dd>
|
||
|
|
<dt id="x2036981" class="bold">
|
||
|
|
<a name="x2036981"></a>resource management</dt>
|
||
|
|
<dd>In CICS , a facility
|
||
|
|
that tracks what system resources are being used. The tracking is done by
|
||
|
|
mapping the CICS identification name to the underlying system resources.</dd>
|
||
|
|
<dt id="x2036986" class="bold">
|
||
|
|
<a name="x2036986"></a>resource management utility (RMU)</dt>
|
||
|
|
<dd>In AFP Utilities, an interactive tool used to maintain AFP resources.</dd>
|
||
|
|
<dt id="x2036991" class="bold">
|
||
|
|
<a name="x2036991"></a>resource name</dt>
|
||
|
|
<dd>A name assigned by
|
||
|
|
the system to a line, controller, or device that is connected to the system.</dd>
|
||
|
|
<dt id="x2036996" class="bold">
|
||
|
|
<a name="x2036996"></a>resource record (RR)</dt>
|
||
|
|
<dd>In a Domain
|
||
|
|
Name System (DNS), a location where data is stored.</dd>
|
||
|
|
<dt id="x2037001" class="bold">
|
||
|
|
<a name="x2037001"></a>resource reservation setup protocol</dt>
|
||
|
|
<dd>An Internet protocol that is used for communicating application (end-to-end)
|
||
|
|
quality-of-service requirements to intermediate transit nodes in a network.
|
||
|
|
RSVP uses a soft-state mechanism to maintain path and reservation states in
|
||
|
|
each node in the reservation path.</dd>
|
||
|
|
<dt id="x2037006" class="bold">
|
||
|
|
<a name="x2037006"></a>resource security</dt>
|
||
|
|
<dd>A security function
|
||
|
|
of the operating system used to authorize users to any part of the system
|
||
|
|
that is required by a job or task.</dd>
|
||
|
|
<dt id="x2037011" class="bold">
|
||
|
|
<a name="x2037011"></a>resource tables</dt>
|
||
|
|
<dd>Related types of
|
||
|
|
resource information that are stored within CICS in tables or control blocks.</dd>
|
||
|
|
<dt id="x2037016" class="bold">
|
||
|
|
<a name="x2037016"></a>responder</dt>
|
||
|
|
<dd>(1) A key server that is asked
|
||
|
|
to establish a dynamic virtual private network (VPN) connection between two
|
||
|
|
endpoints.</dd>
|
||
|
|
<dd>(2) In OSI Communications Subsystem, the application entity
|
||
|
|
that accepts an application association. See also <a href="rzaati.htm#x2025346">initiator</a>.</dd>
|
||
|
|
<dt id="x2037024" class="bold">
|
||
|
|
<a name="x2037024"></a>response</dt>
|
||
|
|
<dd>(1) In SDLC, a frame transmitted
|
||
|
|
by a secondary station. Stations using asynchronous balanced mode send both
|
||
|
|
commands and responses.</dd>
|
||
|
|
<dd>(2) In OSI, a service primitive issued by
|
||
|
|
a service user to complete the procedures associated with a confirmed service.
|
||
|
|
See also <a href="rzaatc.htm#x2000733">command</a>.</dd>
|
||
|
|
<dt id="x2037032" class="bold">
|
||
|
|
<a name="x2037032"></a>response header (RH)</dt>
|
||
|
|
<dd>In SNA, a header,
|
||
|
|
optionally followed by a response unit, that indicates whether the response
|
||
|
|
is positive or negative and that may contain a pacing response. See also <a href="rzaatr.htm#x2036895">request header</a>.</dd>
|
||
|
|
<dt id="x2037037" class="bold">
|
||
|
|
<a name="x2037037"></a>response indicator</dt>
|
||
|
|
<dd>A 1-character
|
||
|
|
field passed with an input record from the system to a program to provide
|
||
|
|
information about the data record or actions taken by the workstation user.</dd>
|
||
|
|
<dt id="x2037042" class="bold">
|
||
|
|
<a name="x2037042"></a>response mode</dt>
|
||
|
|
<dd>A mode of terminal
|
||
|
|
operation that synchronizes operations between the terminal operator and the
|
||
|
|
application program. When IMS™ receives an input transaction that causes response
|
||
|
|
mode to be entered, no more input is allowed until the application program
|
||
|
|
response has been transmitted back to the terminal. See also <a href="rzaatn.htm#x2201120">nonresponse mode</a>.</dd>
|
||
|
|
<dt id="x2037047" class="bold">
|
||
|
|
<a name="x2037047"></a>response time</dt>
|
||
|
|
<dd>In capacity planning,
|
||
|
|
the elapsed time between the end of an inquiry or demand on a computer system
|
||
|
|
and the beginning of the response. An example of response time is the length
|
||
|
|
of time between an indication of the end of inquiry and the display of the
|
||
|
|
first character of the response at a user's workstation.</dd>
|
||
|
|
<dt id="x2037052" class="bold">
|
||
|
|
<a name="x2037052"></a>response unit (RU)</dt>
|
||
|
|
<dd>In SNA, the record
|
||
|
|
sent to respond to a request. The response can be either positive or negative
|
||
|
|
and can include control information.</dd>
|
||
|
|
<dt id="x2004302" class="bold">
|
||
|
|
<a name="x2004302"></a>restore</dt>
|
||
|
|
<dd>(1) To return to an original
|
||
|
|
value or image; for example, to restore data to main storage from auxiliary
|
||
|
|
storage. ant: backup</dd>
|
||
|
|
<dd>(2) To copy data from compact disc, tape, diskette,
|
||
|
|
optical disc, or a save file to auxiliary storage. See also <a href="rzaats.htm#x2037634">save</a>.</dd>
|
||
|
|
<dt id="x2037060" class="bold">
|
||
|
|
<a name="x2037060"></a>restricted state</dt>
|
||
|
|
<dd>The status in which
|
||
|
|
a user places a system (by ending all subsystems) to do a specific function,
|
||
|
|
such as saving storage, saving the system, or restoring user profiles. Other
|
||
|
|
jobs cannot be active on the system while it is in a restricted state.</dd>
|
||
|
|
<dt id="x2065280" class="bold">
|
||
|
|
<a name="x2065280"></a>Restructured Extended Executor (REXX)</dt>
|
||
|
|
<dd>A general-purpose, high-level, programming language, particularly suitable
|
||
|
|
for EXEC procedures or programs for personal computing.</dd>
|
||
|
|
<dt id="x2037070" class="bold">
|
||
|
|
<a name="x2037070"></a>RESULT</dt>
|
||
|
|
<dd>A REXX special variable that
|
||
|
|
is set by the RETURN instruction in a called routine. The RESULT special variable
|
||
|
|
is dropped if the called routine does not return a value.</dd>
|
||
|
|
<dt id="x2037075" class="bold">
|
||
|
|
<a name="x2037075"></a>result column</dt>
|
||
|
|
<dd>The set of columns
|
||
|
|
that DB2 UDB for iSeries SQL selects for an application program.</dd>
|
||
|
|
<dt id="x2037080" class="bold">
|
||
|
|
<a name="x2037080"></a>result field</dt>
|
||
|
|
<dd>In Query, a field that
|
||
|
|
contains the results of calculations performed on numeric fields in a file.</dd>
|
||
|
|
<dt id="x2037085" class="bold">
|
||
|
|
<a name="x2037085"></a>resulting indicator</dt>
|
||
|
|
<dd>In RPG, an indicator
|
||
|
|
that signals the result of a calculation, such as whether the result is plus,
|
||
|
|
minus, or zero; whether a given field is greater than, less than, or equal
|
||
|
|
to another field; or whether an operation was successfully completed.</dd>
|
||
|
|
<dt id="x2004322" class="bold">
|
||
|
|
<a name="x2004322"></a>result table</dt>
|
||
|
|
<dd>The set of rows that DB2 UDB
|
||
|
|
for iSeries SQL selects for an application program. The program uses a cursor
|
||
|
|
to retrieve the rows one by one into a host structure or a set of host variables.</dd>
|
||
|
|
<dt id="x2235657" class="bold">
|
||
|
|
<a name="x2235657"></a>resume</dt>
|
||
|
|
<dd>In cross-site mirroring, to
|
||
|
|
start geographic mirroring again after it is suspended.</dd>
|
||
|
|
<dt id="x2037093" class="bold">
|
||
|
|
<a name="x2037093"></a>resume cursor</dt>
|
||
|
|
<dd>A pointer that tracks
|
||
|
|
the current location at which the exception handler may resume processing
|
||
|
|
after handling an exception.</dd>
|
||
|
|
<dt id="x2235662" class="bold">
|
||
|
|
<a name="x2235662"></a>resume pending state</dt>
|
||
|
|
<dd>In cross-site
|
||
|
|
mirroring, the configuration state of a mirror copy that indicates that geographic
|
||
|
|
mirroring requires synchronization but that the disk pool is currently unavailable.
|
||
|
|
When the disk pool is made available, the mirror copy will be synchronized
|
||
|
|
with the current information on the production copy.</dd>
|
||
|
|
<dt id="x2037098" class="bold">
|
||
|
|
<a name="x2037098"></a>resume point</dt>
|
||
|
|
<dd>An instruction in a
|
||
|
|
program where processing continues after handling an exception.</dd>
|
||
|
|
<dt id="x2235667" class="bold">
|
||
|
|
<a name="x2235667"></a>resuming state</dt>
|
||
|
|
<dd>In cross-site mirroring,
|
||
|
|
the configuration state of the mirror copy that attempts to perform geographic
|
||
|
|
mirroring and synchronization when the independent disk pool is available.
|
||
|
|
The mirror copy state is resuming when it is not suspended or active.</dd>
|
||
|
|
<dt id="x2037103" class="bold">
|
||
|
|
<a name="x2037103"></a>resynchronize</dt>
|
||
|
|
<dd>In OSI, a function
|
||
|
|
of the session layer that enables two peers to coordinate the exchange of
|
||
|
|
data to a previously marked point. This point was marked using the major or
|
||
|
|
minor synchronization service. Resynchronization will normally be performed
|
||
|
|
after a problem is detected by an application entity or indicated by the session
|
||
|
|
layer.</dd>
|
||
|
|
<dt id="x2037108" class="bold">
|
||
|
|
<a name="x2037108"></a>retail communications</dt>
|
||
|
|
<dd>The data communications
|
||
|
|
support that allows programs on an iSeries system to communicate with programs
|
||
|
|
on point-of-sale systems, using SNA LU session type 0 protocol.</dd>
|
||
|
|
<dt id="x2037113" class="bold">
|
||
|
|
<a name="x2037113"></a>retail controller</dt>
|
||
|
|
<dd>In retail communications
|
||
|
|
and Point-of-Sale Utility, a controller in a network that is used to collect
|
||
|
|
data from and provide support for the point-of-sale and administrative devices
|
||
|
|
within the retail system. The retail controller also provides some local data
|
||
|
|
processing capabilities.</dd>
|
||
|
|
<dt id="x2037123" class="bold">
|
||
|
|
<a name="x2037123"></a>retail pass-through</dt>
|
||
|
|
<dd>An i5/OS system program
|
||
|
|
that supports routing of user data between a System/370-type host processor
|
||
|
|
and a retail controller using a single iSeries system. Both the SNA upline facility
|
||
|
|
and the retail communications support use separate intersystem communications
|
||
|
|
function sessions.</dd>
|
||
|
|
<dt id="x2037128" class="bold">
|
||
|
|
<a name="x2037128"></a>retention</dt>
|
||
|
|
<dd>In Backup Recovery and
|
||
|
|
Media Services, the total length of time that the output media is to be saved
|
||
|
|
as a backup or archive copy before it is expired (available for reuse). Retention
|
||
|
|
can be specified as a date, number of days, versions, or permanent. Different
|
||
|
|
retention periods can be specified for full backups, incremental backups,
|
||
|
|
or archive output.</dd>
|
||
|
|
<dt id="x2037133" class="bold">
|
||
|
|
<a name="x2037133"></a>retrofit</dt>
|
||
|
|
<dd>To change an existing program
|
||
|
|
or system by adding or replacing a section of code or a physical unit and
|
||
|
|
making necessary modifications to related units.</dd>
|
||
|
|
<dt id="x2037138" class="bold">
|
||
|
|
<a name="x2037138"></a>retry</dt>
|
||
|
|
<dd>Pertaining to that which resends
|
||
|
|
data a prescribed number of times or until the data is received correctly,
|
||
|
|
for example, a retry option or a retry loop.</dd>
|
||
|
|
<dt id="x2037143" class="bold">
|
||
|
|
<a name="x2037143"></a>return</dt>
|
||
|
|
<dd>To remove the call stack entry
|
||
|
|
and transfer control back to the calling procedure or program in the previous
|
||
|
|
call stack entry.</dd>
|
||
|
|
<dt id="x2037148" class="bold">
|
||
|
|
<a name="x2037148"></a>return code</dt>
|
||
|
|
<dd>For printer files, display
|
||
|
|
files, and ICF files, a value sent by the system to a program to indicate
|
||
|
|
the results of an operation by that program.</dd>
|
||
|
|
<dt id="x2037153" class="bold">
|
||
|
|
<a name="x2037153"></a>return indicator</dt>
|
||
|
|
<dd>An indicator to
|
||
|
|
an RPG program that control should be returned to the calling program.</dd>
|
||
|
|
<dt id="x2037163" class="bold">
|
||
|
|
<a name="x2037163"></a>reverse charging</dt>
|
||
|
|
<dd>In X.25, a packet-switching
|
||
|
|
data network optional facility that allows the data terminal equipment (DTE)
|
||
|
|
to request that the cost of a communications session be charged to the DTE
|
||
|
|
that is called.</dd>
|
||
|
|
<dt id="x2037168" class="bold">
|
||
|
|
<a name="x2037168"></a>reverse image</dt>
|
||
|
|
<dd>Text that appears on
|
||
|
|
the display in the opposite color (for example, black on green instead of
|
||
|
|
green on black).</dd>
|
||
|
|
<dt id="x2037173" class="bold">
|
||
|
|
<a name="x2037173"></a>reverse-interrupt character (RVI character)</dt>
|
||
|
|
<dd>The BSC transmission control character that is sent as a request from
|
||
|
|
the receiving station to the sending station to stop transmitting and begin
|
||
|
|
receiving a message.</dd>
|
||
|
|
<dt id="x2037178" class="bold">
|
||
|
|
<a name="x2037178"></a>reverse map</dt>
|
||
|
|
<dd>To transform an Internet
|
||
|
|
Protocol (IP) address to a host name as opposed to forward-mapping, where
|
||
|
|
host names are transformed into IP addresses.</dd>
|
||
|
|
<dt id="x2037183" class="bold">
|
||
|
|
<a name="x2037183"></a>reverse mapping domain</dt>
|
||
|
|
<dd>A domain that
|
||
|
|
transforms Internet Protocol (IP) addresses to host names.</dd>
|
||
|
|
<dt id="x2047015" class="bold">
|
||
|
|
<a name="x2047015"></a>revisable-form text (RFT)</dt>
|
||
|
|
<dd>A data
|
||
|
|
stream defined by document content architecture that is used to exchange
|
||
|
|
unresolved documents (which cannot be directly printed or displayed) between
|
||
|
|
systems. See also <a href="rzaatf.htm#x2022989">final-form text</a>.</dd>
|
||
|
|
<dt id="x2134888" class="bold">
|
||
|
|
<a name="x2134888"></a>Revisable-Form-Text Document Content Architecture
|
||
|
|
(RFTDCA)</dt>
|
||
|
|
<dd>The architectural specification for the information interchange
|
||
|
|
of documents whose text is in a revisable format. A Revisable-Form Text Document
|
||
|
|
Content Architecture document consists of structured fields, controls, and
|
||
|
|
graphic characters that represent the format and meaning of the document.</dd>
|
||
|
|
<dt id="x2037193" class="bold">
|
||
|
|
<a name="x2037193"></a>rewind</dt>
|
||
|
|
<dd>To move tape from the take-up
|
||
|
|
hub to the supply hub.</dd>
|
||
|
|
<dt id="x2065321" class="bold">
|
||
|
|
<a name="x2065321"></a>REXX</dt>
|
||
|
|
<dd>See <a href="rzaatr.htm#x2065280">Restructured
|
||
|
|
Extended Executor</a>.</dd>
|
||
|
|
<dt id="x2037202" class="bold">
|
||
|
|
<a name="x2037202"></a>REXX/400</dt>
|
||
|
|
<dd>The i5/OS implementation
|
||
|
|
of the Systems Application Architecture® Procedures
|
||
|
|
Language. REXX/400 is a programming language that is supported by an interpreter
|
||
|
|
provided as part of the i5/OS licensed program.</dd>
|
||
|
|
<dt id="x2037207" class="bold">
|
||
|
|
<a name="x2037207"></a>REXX/400 interpreter</dt>
|
||
|
|
<dd>The language
|
||
|
|
processor of the i5/OS licensed program that processes procedures and programs
|
||
|
|
written in the REXX language.</dd>
|
||
|
|
<dt id="x2047020" class="bold">
|
||
|
|
<a name="x2047020"></a>RFT</dt>
|
||
|
|
<dd>See <a href="rzaatr.htm#x2047015">revisable-form
|
||
|
|
text</a>.</dd>
|
||
|
|
<dt id="x2252606" class="bold">
|
||
|
|
<a name="x2252606"></a>RFTDCA</dt>
|
||
|
|
<dd>See <a href="rzaatr.htm#x2134888">Revisable-Form-Text Document Content Architecture</a>.</dd>
|
||
|
|
<dt id="x2037212" class="bold">
|
||
|
|
<a name="x2037212"></a>RH</dt>
|
||
|
|
<dd>(1) See <a href="rzaatr.htm#x2036895">request
|
||
|
|
header</a>.</dd>
|
||
|
|
<dd>(2) See <a href="rzaatr.htm#x2037032">response header</a>.</dd>
|
||
|
|
<dt id="x2037220" class="bold">
|
||
|
|
<a name="x2037220"></a>right justify</dt>
|
||
|
|
<dd>To print text with
|
||
|
|
an even right margin by adding extra space throughout a line.</dd>
|
||
|
|
<dt id="x2037225" class="bold">
|
||
|
|
<a name="x2037225"></a>ring error monitor (REM)</dt>
|
||
|
|
<dd>In communications,
|
||
|
|
a function of the token-ring manager that observes, collects, and analyzes
|
||
|
|
recoverable and irrecoverable error reports sent by token-ring stations on
|
||
|
|
a single token-ring network and assists in fault isolation and correction.</dd>
|
||
|
|
<dt id="x2235417" class="bold">
|
||
|
|
<a name="x2235417"></a>RIO</dt>
|
||
|
|
<dd>See <a href="rzaatr.htm#x2036638">remote
|
||
|
|
input/output</a>.</dd>
|
||
|
|
<dt id="x2037230" class="bold">
|
||
|
|
<a name="x2037230"></a>RIP</dt>
|
||
|
|
<dd>See <a href="rzaatr.htm#x2037359">Router
|
||
|
|
Information Protocol</a>.</dd>
|
||
|
|
<dt id="x2037234" class="bold">
|
||
|
|
<a name="x2037234"></a>RISC</dt>
|
||
|
|
<dd>See <a href="rzaatr.htm#x2036206">reduced
|
||
|
|
instruction set computer</a>.</dd>
|
||
|
|
<dt id="x2037238" class="bold">
|
||
|
|
<a name="x2037238"></a>RJE</dt>
|
||
|
|
<dd>See <a href="rzaats.htm#x2039202">SNA
|
||
|
|
remote job entry</a>.</dd>
|
||
|
|
<dt id="x2037242" class="bold">
|
||
|
|
<a name="x2037242"></a>RLE</dt>
|
||
|
|
<dd>See <a href="rzaatr.htm#x2037546">run-length
|
||
|
|
encoding</a>.</dd>
|
||
|
|
<dt id="x2037250" class="bold">
|
||
|
|
<a name="x2037250"></a>RLU</dt>
|
||
|
|
<dd>See <a href="rzaatr.htm#x2036845">report
|
||
|
|
layout utility</a>.</dd>
|
||
|
|
<dt id="x2037254" class="bold">
|
||
|
|
<a name="x2037254"></a>RMI</dt>
|
||
|
|
<dd>See <a href="rzaatr.htm#x2172783">Remote
|
||
|
|
Method Invocation</a>.</dd>
|
||
|
|
<dt id="x2037258" class="bold">
|
||
|
|
<a name="x2037258"></a>RMU</dt>
|
||
|
|
<dd>See <a href="rzaatr.htm#x2036986">resource
|
||
|
|
management utility</a>.</dd>
|
||
|
|
<dt id="x2037262" class="bold">
|
||
|
|
<a name="x2037262"></a>RNR</dt>
|
||
|
|
<dd>See <a href="rzaatr.htm#x2035965">receive
|
||
|
|
not ready</a>.</dd>
|
||
|
|
<dt id="x2037266" class="bold">
|
||
|
|
<a name="x2037266"></a>robot</dt>
|
||
|
|
<dd>For media library devices,
|
||
|
|
a part (carriage and picker assembly) for moving media between the cartridge
|
||
|
|
storage slots and the drives.</dd>
|
||
|
|
<dt id="x2011363" class="bold">
|
||
|
|
<a name="x2011363"></a>roll back</dt>
|
||
|
|
<dd>To remove changes that
|
||
|
|
were made to database files under commitment control since the last commitment
|
||
|
|
boundary. See also <a href="rzaatc.htm#x2017536">commitment boundary</a>, <a href="rzaatc.htm#x2000763">commitment control</a>.</dd>
|
||
|
|
<dt id="x2037279" class="bold">
|
||
|
|
<a name="x2037279"></a>rollback</dt>
|
||
|
|
<dd>The process of restoring
|
||
|
|
data changed by an application program or user to the state at its last commitment
|
||
|
|
boundary (commitment point).</dd>
|
||
|
|
<dt id="x2037284" class="bold">
|
||
|
|
<a name="x2037284"></a>rollback required (RBR)</dt>
|
||
|
|
<dd>The rollback
|
||
|
|
required logical unit of work (LUW) state indicates that a rollback vote was
|
||
|
|
received for a prepare-for-commit request or that a failure has put the current
|
||
|
|
transaction into a state where it must be rolled back. The transaction program
|
||
|
|
is not allowed to perform any further changes under commitment control.</dd>
|
||
|
|
<dt id="x2037289" class="bold">
|
||
|
|
<a name="x2037289"></a>ROM</dt>
|
||
|
|
<dd>See <a href="rzaatr.htm#x2035882">read-only
|
||
|
|
memory</a>.</dd>
|
||
|
|
<dt id="x2037293" class="bold">
|
||
|
|
<a name="x2037293"></a>root directory</dt>
|
||
|
|
<dd>In the operating systems
|
||
|
|
for personal computers, the directory on a disk or diskette that contains
|
||
|
|
the list of files stored on that disk or diskette. If more than one directory
|
||
|
|
is on a disk or diskette, the root directory is at the top of the hierarchy
|
||
|
|
of directories. The root directory is created by the operating system when
|
||
|
|
the disk or diskette is formatted.</dd>
|
||
|
|
<dt id="x2037298" class="bold">
|
||
|
|
<a name="x2037298"></a>root domain</dt>
|
||
|
|
<dd>Names servers that are
|
||
|
|
authoritative for all of the top-level domains.</dd>
|
||
|
|
<dt id="x2037303" class="bold">
|
||
|
|
<a name="x2037303"></a>root file system</dt>
|
||
|
|
<dd>A file system that
|
||
|
|
supports objects in the root (or /) directory. Access to all objects, regardless
|
||
|
|
of which file system they actually reside in, starts at the root. Other file
|
||
|
|
systems may be mounted over directories managed by the root file system, thus
|
||
|
|
allowing all file systems to appear as a single file system tree.</dd>
|
||
|
|
<dt id="x2037308" class="bold">
|
||
|
|
<a name="x2037308"></a>root folder</dt>
|
||
|
|
<dd>The folder on the system
|
||
|
|
that contains all other folders. The system-recognized identifier is *ROOT.</dd>
|
||
|
|
<dt id="x2037313" class="bold">
|
||
|
|
<a name="x2037313"></a>root group</dt>
|
||
|
|
<dd>In the Application Development
|
||
|
|
Manager feature of the Application Development ToolSet licensed program, the
|
||
|
|
first, or top, group in any project hierarchy.</dd>
|
||
|
|
<dt id="x2037318" class="bold">
|
||
|
|
<a name="x2037318"></a>root server</dt>
|
||
|
|
<dd>A name server that functions
|
||
|
|
at the highest level node in the name system tree.</dd>
|
||
|
|
<dt id="x2037323" class="bold">
|
||
|
|
<a name="x2037323"></a>rotary dial</dt>
|
||
|
|
<dd>On a switched communications
|
||
|
|
line, the dialing method that creates a series of pulses to identify the called
|
||
|
|
station.</dd>
|
||
|
|
<dt id="x2037328" class="bold">
|
||
|
|
<a name="x2037328"></a>rotor</dt>
|
||
|
|
<dd>The rotating part of a sensor.</dd>
|
||
|
|
<dt id="x2037333" class="bold">
|
||
|
|
<a name="x2037333"></a>round-trip conversion</dt>
|
||
|
|
<dd>A conversion
|
||
|
|
where the integrity of all character data is maintained from the source CCSID
|
||
|
|
to the target CCSID and back to the source. The characters that are in both
|
||
|
|
the target CCSID and the source CCSID are preserved. Any characters outside
|
||
|
|
the target CCSID are arbitrarily assigned unique code points in the target
|
||
|
|
CCSID.</dd>
|
||
|
|
<dt id="x2037338" class="bold">
|
||
|
|
<a name="x2037338"></a>route</dt>
|
||
|
|
<dd>The path that network traffic
|
||
|
|
follows from its source to its destination.</dd>
|
||
|
|
<dt id="x2037343" class="bold">
|
||
|
|
<a name="x2037343"></a>route metrics</dt>
|
||
|
|
<dd>In Internet communications,
|
||
|
|
the method used by the Routing Information Protocol (RIP) to choose the best
|
||
|
|
Internet routes. The unit of measure is the number of hops between the origin
|
||
|
|
and destination. In practice, the metric for a route is often assigned based
|
||
|
|
on factors such as link transmission speed and line cost, not on the actual
|
||
|
|
number of hops.</dd>
|
||
|
|
<dt id="x2037348" class="bold">
|
||
|
|
<a name="x2037348"></a>router</dt>
|
||
|
|
<dd>(1) A part of the iSeries Access licensed
|
||
|
|
programs that handle requests to send and receive data from applications on
|
||
|
|
the personal computer and routes them to the appropriate applications on the
|
||
|
|
system.</dd>
|
||
|
|
<dd>(2) See <a href="rzaatg.htm#x2023645">gateway</a>.</dd>
|
||
|
|
<dd>(3) A special
|
||
|
|
purpose, dedicated computer that attaches two or more networks.</dd>
|
||
|
|
<dt id="x2037359" class="bold">
|
||
|
|
<a name="x2037359"></a>Router Information Protocol (RIP)</dt>
|
||
|
|
<dd>The distance-vector routing protocol used by the Internetwork Packet Exchange
|
||
|
|
(IPX) routers on the network to exchange routing information about the connected
|
||
|
|
networks. The information is exchanged through the use of IPX. A RIP packet
|
||
|
|
contains sets of network entry information.</dd>
|
||
|
|
<dt id="x2004362" class="bold">
|
||
|
|
<a name="x2004362"></a>routine</dt>
|
||
|
|
<dd>(1) In REXX, a series of instructions
|
||
|
|
called with the CALL instruction or as a function. A routine can be either
|
||
|
|
internal or external to a user's program.</dd>
|
||
|
|
<dd>(2) A set of statements
|
||
|
|
in a program that causes the system to perform an operation or a series of
|
||
|
|
related operations.</dd>
|
||
|
|
<dt id="x2037370" class="bold">
|
||
|
|
<a name="x2037370"></a>routine-name</dt>
|
||
|
|
<dd>In COBOL, a user-defined
|
||
|
|
word that identifies a procedure written in a language other than COBOL.</dd>
|
||
|
|
<dt id="x2037375" class="bold">
|
||
|
|
<a name="x2037375"></a>routing</dt>
|
||
|
|
<dd>The list of users who are
|
||
|
|
to receive an item when it is distributed, including all users named specifically
|
||
|
|
and those users named on distribution lists by the sender.</dd>
|
||
|
|
<dt id="x2037380" class="bold">
|
||
|
|
<a name="x2037380"></a>routing data</dt>
|
||
|
|
<dd>Information stored in
|
||
|
|
the job description that identifies the routing entry used by a job.</dd>
|
||
|
|
<dt id="x2037385" class="bold">
|
||
|
|
<a name="x2037385"></a>routing entry</dt>
|
||
|
|
<dd>An entry in a subsystem
|
||
|
|
description that specifies the program to be called to control a routing step
|
||
|
|
that runs in the subsystem.</dd>
|
||
|
|
<dt id="x2037395" class="bold">
|
||
|
|
<a name="x2037395"></a>routing step</dt>
|
||
|
|
<dd>The processing that
|
||
|
|
results from running a program specified in a routing entry. Most jobs have
|
||
|
|
only one routing step.</dd>
|
||
|
|
<dt id="x2037400" class="bold">
|
||
|
|
<a name="x2037400"></a>routing table</dt>
|
||
|
|
<dd>(1) In SNADS, a list of
|
||
|
|
entries in a table that the system uses to route a message or electronic mail
|
||
|
|
to a user on the system. Each entry is made up of a destination group name
|
||
|
|
(such as a department or organization) and a destination element name (the
|
||
|
|
user ID of each person in that department or organization).</dd>
|
||
|
|
<dd>(2) In
|
||
|
|
a point-to-point profile, a collection of path information through which hosts
|
||
|
|
or networks can communicate with other hosts and networks.</dd>
|
||
|
|
<dt id="x2004367" class="bold">
|
||
|
|
<a name="x2004367"></a>row</dt>
|
||
|
|
<dd>The horizontal component of a
|
||
|
|
table consisting of a sequence of values, one for each column of the table.</dd>
|
||
|
|
<dt id="x2037408" class="bold">
|
||
|
|
<a name="x2037408"></a>RPC</dt>
|
||
|
|
<dd>See <a href="rzaatr.htm#x2036721">remote
|
||
|
|
procedure call</a>.</dd>
|
||
|
|
<dt id="x2037460" class="bold">
|
||
|
|
<a name="x2037460"></a>RPG</dt>
|
||
|
|
<dd>See <a href="rzaatr.htm#x2134629">Report
|
||
|
|
Program Generator</a>.</dd>
|
||
|
|
<dt id="x2037473" class="bold">
|
||
|
|
<a name="x2037473"></a>RPQ</dt>
|
||
|
|
<dd>See <a href="rzaatr.htm#x2036885">request
|
||
|
|
for price quotation</a>.</dd>
|
||
|
|
<dt id="x2009596" class="bold">
|
||
|
|
<a name="x2009596"></a>RR</dt>
|
||
|
|
<dd>(1) See <a href="rzaatr.htm#x2035992">receive
|
||
|
|
ready</a>.</dd>
|
||
|
|
<dd>(2) See <a href="rzaatr.htm#x2036996">resource record</a>.</dd>
|
||
|
|
<dt id="x2037500" class="bold">
|
||
|
|
<a name="x2037500"></a>RS-310</dt>
|
||
|
|
<dd>An Electronic Industries Association
|
||
|
|
standard for designing racks to hold data processing equipment.</dd>
|
||
|
|
<dt id="x2037492" class="bold">
|
||
|
|
<a name="x2037492"></a>RST</dt>
|
||
|
|
<dd>See <a href="rzaatr.htm#x2036923">reset</a>.</dd>
|
||
|
|
<dt id="x2037505" class="bold">
|
||
|
|
<a name="x2037505"></a>RTAM</dt>
|
||
|
|
<dd>See <a href="rzaatr.htm#x2036754">remote
|
||
|
|
terminal access method</a>.</dd>
|
||
|
|
<dt id="x2037509" class="bold">
|
||
|
|
<a name="x2037509"></a>RTS</dt>
|
||
|
|
<dd>See <a href="rzaatr.htm#x2036541">reliable
|
||
|
|
transfer server</a>.</dd>
|
||
|
|
<dt id="x2037513" class="bold">
|
||
|
|
<a name="x2037513"></a>RU</dt>
|
||
|
|
<dd>(1) See <a href="rzaatr.htm#x2036905">request
|
||
|
|
unit</a>.</dd>
|
||
|
|
<dd>(2) See <a href="rzaatr.htm#x2037052">response unit</a>.</dd>
|
||
|
|
<dt id="x2037521" class="bold">
|
||
|
|
<a name="x2037521"></a>RU chain</dt>
|
||
|
|
<dd>In SNA, a set of related
|
||
|
|
request or response units that are transmitted consecutively on a particular
|
||
|
|
normal or expedited data flow.</dd>
|
||
|
|
<dt id="x2037526" class="bold">
|
||
|
|
<a name="x2037526"></a>rule</dt>
|
||
|
|
<dd>A procedure that defines how
|
||
|
|
Internet Protocol (IP) packet security should handle packets. Rules in IP
|
||
|
|
packet security pertain to hidden addresses, mapped addresses, and filters.</dd>
|
||
|
|
<dt id="x2037531" class="bold">
|
||
|
|
<a name="x2037531"></a>rules file</dt>
|
||
|
|
<dd>A file that contains rules
|
||
|
|
and definitions that pertain to those rules.</dd>
|
||
|
|
<dt id="x2037536" class="bold">
|
||
|
|
<a name="x2037536"></a>RUMBA/400</dt>
|
||
|
|
<dd>An optionally installable
|
||
|
|
component of iSeries Access, based on the Microsoft® Windows® program, that provides 5250 display emulation and 5225 printer
|
||
|
|
emulation.</dd>
|
||
|
|
<dt id="x2037546" class="bold">
|
||
|
|
<a name="x2037546"></a>run-length encoding (RLE)</dt>
|
||
|
|
<dd>A technique
|
||
|
|
for compressing data that avoids repeatedly having to code data elements of
|
||
|
|
the same value; instead, the value is coded once, along with the number of
|
||
|
|
times for it to be repeated.</dd>
|
||
|
|
<dt id="x2037551" class="bold">
|
||
|
|
<a name="x2037551"></a>run time</dt>
|
||
|
|
<dd>The time period during which
|
||
|
|
a computer program is running.</dd>
|
||
|
|
<dt id="x2037556" class="bold">
|
||
|
|
<a name="x2037556"></a>runtime array</dt>
|
||
|
|
<dd>In RPG, an array that
|
||
|
|
is loaded or created by input or calculation specifications after the program
|
||
|
|
starts to run. See also <a href="rzaatc.htm#x2017821">compile-time array</a>, <a href="rzaatp.htm#x2034337">preruntime array</a>.</dd>
|
||
|
|
<dt id="x2037561" class="bold">
|
||
|
|
<a name="x2037561"></a>runtime defaults</dt>
|
||
|
|
<dd>In query management,
|
||
|
|
all of the formatting elements of a formatted report that were not explicitly
|
||
|
|
specified in the form.</dd>
|
||
|
|
<dt id="x2037566" class="bold">
|
||
|
|
<a name="x2037566"></a>runtime environment</dt>
|
||
|
|
<dd>In the C language,
|
||
|
|
a logical grouping of one or more program objects that must be connected at
|
||
|
|
application run time to do some task.</dd>
|
||
|
|
<dt id="x2037576" class="bold">
|
||
|
|
<a name="x2037576"></a>runtime table</dt>
|
||
|
|
<dd>In RPG, a table that
|
||
|
|
is loaded or created by input or calculation specifications after the program
|
||
|
|
starts to run. See also <a href="rzaatc.htm#x2017826">compile-time table</a>, <a href="rzaatp.htm#x2034342">preruntime table</a>.</dd>
|
||
|
|
<dt id="x2037581" class="bold">
|
||
|
|
<a name="x2037581"></a>run unit</dt>
|
||
|
|
<dd>In COBOL, a set of one or
|
||
|
|
more programs that run as a set to solve a problem. A set starts with the
|
||
|
|
first COBOL program in the call stack and includes all programs (COBOL) (non-COBOL)
|
||
|
|
that are below it in the call stack.</dd>
|
||
|
|
<dt id="x2009613" class="bold">
|
||
|
|
<a name="x2009613"></a>RUOW</dt>
|
||
|
|
<dd>See <a href="rzaatr.htm#x2004199">remote
|
||
|
|
unit of work</a>.</dd>
|
||
|
|
<dt id="x2188504" class="bold">
|
||
|
|
<a name="x2188504"></a>RVI character</dt>
|
||
|
|
<dd>See <a href="rzaatr.htm#x2037173">reverse-interrupt character</a>.</dd>
|
||
|
|
<dt id="x2037592" class="bold">
|
||
|
|
<a name="x2037592"></a>RVX</dt>
|
||
|
|
<dd>The Electronic Industries Association
|
||
|
|
(EIA) RS standards (for example, RS-232); the ITU/CCITT standards (for example,
|
||
|
|
V.24 for modem interconnects and protocols); and the ITU/CCITT standards for
|
||
|
|
interconnects and protocols (for example X.21). ITU is the International Telecommunications
|
||
|
|
Union, and CCITT is the International Consulting Committee for Telephony and
|
||
|
|
Telegraphy.</dd></dl>
|
||
|
|
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
|
||
|
|
</body>
|
||
|
|
</html>
|