- RA
- See repeat-to-address (RA).
- RACE
- See receive-any control element (RACE).
- RACF
- See Resource Access Control Facility (RACF).
- RACF database
- A collection of interrelated
or independent data items stored together without redundancy, to serve the
Resource Access Control Facility (RACF).
- RACF-protected
- Pertaining
to a resource that has either a discrete profile or an applicable generic
profile. A data set that is RACF-protected by a disrete profile must also
be RACF-indicated.
- RACF report writer
- A RACF function
that produces reports on system use and resource use from information found
in the RACF SMF records.
- RACF segment
- The portion of a RACF profile
that contains basic information needed to define a user, group, or resource
to RACF. Also called base segment.
- RACHECK request
- In RACF, the issuing of the RACHECK macro or the RACROUTE macro with REQUEST=AUTH
specified. The primary function of a RACHECK request is to check a user's
authorization to a RACF-protected resource or function. See FRACHECK request, authorization checking.
- RACINIT request
- In RACF, the issuing
of the RACINIT macro or the RACROUTE macro with REQUEST=VERIFY or REQUEST=VERIFYX
specified. A RACINIT request is used to verify the authority of a user to
enter work into the system.
- RACROUTE
- In RACF, a macro that provides a
means of calling RACF to provide security functions. See also FRACHECK request, RACHECK request, and RACINIT request.
- RAIA
- See receive-any input area (RAIA).
- RBA
- See relative byte address (RBA).
- RCT
- See resource control table (RCT).
- RDM
- See resource definition macro (RDM).
- RDO
- See resource definition online (RDO).
- RDSA
- See read-only dynamic storage area (RDSA)
- read integrity
- An
attribute of a read request, which ensures the integrity of the data passed
to a program that issues a read-only request. CICS recognizes two forms of
read integrity: consistent and repeatable. See also dirty read, repeatable, consistent.
- read intent
- The type
of access intent that subsystems use to read data from a database.
- read-only dynamic storage area (RDSA)
- The key-0 storage area for
all reentrant programs and tables below the 16MB boundary.
- real storage
- The main storage in a virtual storage system. Physically, real storage
and main storage are identical. Conceptually, however, real storage represents
only part of the range of addresses available to the user of a virtual storage
system.
- real-time analysis (RTA)
- In CICSPlex SM, a function that provides
the automatic notification of requested error conditions and all aspects of
a resource's status. The notifications appear in console messages, or generic
NetView for OS/390 alerts, or both.
- reattachment event
- An event whose firing has caused an activity to be activated.
- reattachment queue
- A list of the reattachment events that have
caused a particular activity to be activated. Each activity has a reattachment
queue associated with it. The queue may be empty. Events remain on the reattachment
queue until they are retrieved by the activity, or until a syncpoint occurs.
- receive-any control element (RACE)
- Type of control field held
in the CICS receive-any pool set aside for VTAM receive-any operations. The
number of RACEs maintained depends on the RAPOOL and MXT system initialization
parameters and on the number of active tasks. See Setting
the size of the receive-any pool and Setting the
maximum task specification (MXT) for more information.
- receive-any input area (RAIA)
- Type of input area held in the CICS
receive-any pool set aside for VTAM receive-any operations. The number of
RACEs maintained depends on the RAPOOL and MXT system initialization parameters
and on the number of active tasks. See the CICS Transaction Server System Definition Guide for more information.
- RECON data sets
- See recovery control data sets (RECON).
- recoverability
- The
ability of a system to continue processing without loss of data when an unplanned
interruption occurs.
- recoverable in-doubt structure
(RIS)
- In DBCTL, an area constructed for each unit of recovery
when a failure occurs. Each RIS is written to the IMS log. RIS contents include
the recovery token, the changed data records, and the identity of the data
block that cannot be accessed because of unresolved in-doubts.
- recoverable
resource
- A resource that can be modified only in accordance with
sync point protocols
- recoverable service element (RSE)
- A set of DBCTL subsystem identifiers of equivalent DBCTL subsystems,
their associated job names, and the specific APPLIDs of the CICS systems that
will use them. RSEs are defined by CICS resource definition macros and are
held in the recoverable service table (RST). See also equivalent, recoverable service table (RST).
- recoverable service table (RST)
- CICS control table used for IMS/ESA DBCTL support. The RST consists
of recoverable service elements (RSEs), which define the DBCTL subsystems
to which each CICS system can connect. See also equivalent, end-of-file label.
- recovery
- (1) The process of returning the system
to a state from which operation can be resumed.
- (2) The restoration
of resources following an error.
- recovery control
data sets (RECON data sets)
- Dual recovery control data sets in
which Data Base Recovery Control automatically records information about logging
activity and events that might affect the recovery of databases. Both data
sets contain identical information, and so are usually referred to as one
- the RECON. DBRC selects the correct data sets to be used by a recovery utility.
- recovery log data set (RLDS)
- A log data set that contains only
the log records that are required for database recovery.
- recovery manager
- CICS resource recovery mechanism that provides a CICS resource
manager, for example file control, with more flexibility than the DWE two-phase
commit support for syncpoint and backout processing.
- recovery point
- In the CICS backup-while-open facility, the latest point, on
the CICS forward recovery log series for this data set, from which forward
recovery can start and restore any image copy taken at that point to a consistent
state. The recovery point is held as a time that can be converted to a position
on the forward recovery log.
- recovery routine
- A routine
that is entered when an error occurs during the performance of an associated
operation. It isolates the error, assesses the extent of the error, and attempts
to correct the error and resume operation.
- recovery token
- A
16-byte unique identifier that is created by CICS (and passed to DBCTL) for
each LUW. Its lifetime is the same as the LUW. The first 8 bytes are the CICS
APPLID (in an XRF environment, this is the generic APPLID) and the second
8 bytes are a unit of recovery ID. (CICS creates a unit of recovery ID for
every LUW.) DBCTL validates the recovery token to protect against duplication
of units of recovery. The DBCTL operator can display the recovery token and
it is also displayed in a number of CICS and IMS messages. See also pseudorecovery token.
- REDO
- The DEDB process in the second phase of a
two-phase commit process if the chosen action is COMMIT. For DEDBs, if phase
two action is COMMIT, the changes are written to the database using REDO,
because the DEDB changes have only been made in main storage. If the action
is BACKOUT, no changes are required to the database because the updates are
still in main storage. The process applied is called UNDO. REDO is also used
to refer to the action required for committed DEDBs during emergency restart
of IMS, DL/I, or SQL/DS.
- reentrable
- Pertaining to a module that is
designed for concurrent execution by multiple tasks. If a reenterable module
modifies its own data areas or other shared resources in any way, it must
use appropriate serialization methods to prevent interference between using
tasks. See also quasi-reentrant.
- reentrant
- The attribute
that describes a load module, of which only one copy is loaded into virtual
storage to satisfy the requirements of any number of tasks. A single copy
of a reentrant load module can be executed concurrently by any number of tasks.
A reentrant load module is also one that does not modify itself, and must
be link-edited with the RENT attribute. See also quasi-reentrant.
- reference modification
- In the COBOL licensed program, a method
of establishing and referring to a data item by specifying a leftmost character
position and length within a character string.
- reference set
- The
amount of real storage required so that minimal (almost zero) virtual paging
occurs. It is the total amount of real storage required to process the most
frequently used sequence of instructions and data for a given set of transactions
performing defined tasks, without causing any virtual storage paging operations.
- region
- In MVS, a variable-size subdivision of virtual storage
that is allocated to a job step or system task. CICS Transaction Server runs
in an MVS/ESA region, usually referred to as the CICS region.
- region-remote
- A term used in early releases of CICS to refer to a CICS system in another
region of the same processor. It can be taken to refer to a system that is
accessed through an IRC (MRO) link, rather than through an SNA LU6.1 or LU6.2
link.
- relational database
- A database that can be perceived as a set
of tables and manipulated in accordance with the relational model of data.
See also hierarchic database.
- relative byte address
(RBA)
- The displacement in bytes of a stored record or control
interval from the beginning of the storage space allocated to the VSAM data
set to which it belongs.
- relative record data set (RRDS)
- A VSAM data set organization, in which records are of fixed length
and are accessed by their relative record numbers. The relative record number
(RRN) of a record is its displacement (in records) from the beginning of the
data set.
- relative record number (RRN)
- In a relative record data set (RRDS),
the number of the "slot" used to hold a record, that is its displacement (in
records) from the beginning of the data set.
- relay program
- In transaction
routing, a CICS program that provides the communication mechanism between
a locally-connected terminal and a transaction in a remote system. The relay
program is invoked by the relay transaction.
- relay transaction
- In transaction routing, a CICS transaction that handles communication between
a locally-connected terminal and a transaction in a remote system. The relay
transaction invokes the relay program.
- reliability
- A measurement
of the ability of a system to continue processing without failure. Shutting
down an on-line system to process batch updates to the database reduces its
availability to end users but has no bearing on the reliability of components
required to deliver the online service.
- remote
- Pertaining to a system,
program, or device that is accessed through a communications line.
- remote DL/I
- A special case of function shipping, in which CICS
sends a DL/I request to another CICS system. See also function shipping.
- remote MAS
- A managed application system (MAS) that uses MRO or
LU 6.2 to communicate with the CICSPlex SM address space (CMAS) that controls
it. A remote MAS may or may not reside in the same MVS image as the CMAS that
controls it.
- Remote Method Invocation (RMI)
- 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 involved from other Java virtual machines, possibly on different
hosts.
- remote resource
- In CICS intercommunication, a resource that is
owned by a remote system. See also local resource.
- remote spooling communications subsystem (RSCS)
- An IBM licensed
program that transfers spool files, commands, and messages between VM users.
- remote system
- Any other system in the network with which your
system can communicate. See also local system.
- repeatable
- A type of read integrity in which a program is permitted to issue multiple
read-only requests, with repeatable read integrity, and be assured that none
of the records passed can subsequently be changed until the end of the sequence
of repeatable read requests. The sequence of repeatable read requests ends
either when the transaction terminates, or when it takes a syncpoint, whichever
is the earlier. See also read integrity, consistent.
- repeat-to-address (RA)
- An order to position data in the buffer
of a 3270 terminal, thereby controlling the position of the data on the screen.
An RA order is followed by a 2-byte buffer address, and a one-byte character
to be repeated. The order copies the one-byte character repeatedly into the
buffer until the 2-byte address is reached.
- repository
- A VSAM data
set on which the states of BTS processes are stored. When a process is not
executing under the control of BTS, its state (and the states of its constituent
activities) are preserved by being written to a repository data set. The states
of all processes of a particular process-type (and of their activity instances)
are stored on the same repository data set. Records for multiple process-types
can be written to the same repository.
- repository utility
- A CICS-supplied utility program, DFHBARUP, that enables you to print
selected records from a specified BTS repository data set.
- requested reset statistics
- Requested reset statistics differ from
requested statistics in that the statistics counters are reset to zero. In
CICS Transaction Server, CICS statistics that the user has asked for by using
the appropriate EXEC CICS or CEMT commands, which cause the statistics to
be written to the SMF data set immediately.
- requested statistics
- In CICS Transaction Server, CICS statistics that the user has asked
for by using the appropriate EXEC CICS or CEMT commands, which cause the statistics
to be written to the SMF data set immediately, instead of waiting for the
current interval to expire. See also requested reset statistics.
- request header (RH)
- In SNA, control information preceding a request
unit.
- requesting region
- The region in which
a dynamic routing request originates. For dynamic transaction routing and
inbound client dynamic program link requests, this is typically a TOR; for
dynamic START requests and peer-to-peer dynamic program link requests, this
is typically an AOR. To be eligible for dynamic routing, the process or activity must be started by an EXEC CICS RUN ASYNCHRONOUS command.
Compare with routing region and target region.
- request parameter list (RPL)
- In VTAM, a control block that contains
the parameters necessary for processing a request for data transfer, for connecting
or disconnecting a terminal, or for some other operation.
- request
unit (RU)
- In SNA, a message unit that contains control information
such as a request code, or function management headers (FMHs), end-user data,
or both.
- resettable JVM
- A Java Virtual Machine
(JVM) that is initialized once, reused many times, and can be reset to a known
state after each Java program has completed. A resettable JVM has the option
REUSE=RESET specified in its JVM profile.
- residence mode
- Attribute of a program indicating where it can reside, that is, either
above or below the 16MB line.
- resource
- 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 NIM, a resource is any file, directory, file system, or device that is
required to perform a NIM operation., In WebSphere MQ for z/OS, examples of
resources are buffer pools, page sets, log data sets, queues, and messages.
- Resource Access Control Facility (RACF)
- An IBM licensed program
that provides access control by identifying users to the system; verifying
users of the system; authorizing access to protected resources; logging detected,
unauthorized attempts to enter the system; and logging detected accesses to
protected resources. RACF is included in OS/390 Security Server and is also
available as a separate program for the MVS and VM environments.
- resource control table (RCT)
- A DB2 control table that defines
the relationship between CICS transactions and DB2 resources.
- resource definition macro (RDM)
- A method of defining resources
to CICS by using assembler macros. You code and assemble special CICS macros
and present the assembler output to CICS at system initialization. See also resource definition online (RDO).
- resource definition online (RDO)
- The method of defining most resources to CICS. Resource definitions
are created interactively with the CEDA transaction, or by using the utility
DFHCSDUP. Both methods store definition in the CICS system definition data
set (CSD). At CICS initialization, CSD definitions are selectively installed
as CICS system tables, controlled by a user-supplied list of definitions.
CEDA-defined resource definitions can be installed while CICS is active and
used immediately. See also resource definition macro (RDM).
- resource
group class
- A RACF class in which resource group profiles can
be defined. A resource group class is related to another class, sometimes
called a member class. For example, resource group class GTERMINL is related
to class TERMINAL. See also resource group profile.
- resource
group profile
- A general resource profile in a resource group class.
A resource group profile can provide RACF protection for one or more resources
with unlike names. See also resource group class.
- resource manager interface (RMI)
- A program or a group of programs
that you write to enable you to structure calls from your CICS system in such
a way that they can access non-CICS resources, such as databases, that you
would not normally be able to access. An RMI is written using the CICS task-related
user exit interface. DBCTL, for example, is accessed by means of an RMI. See
also task-related user exit (TRUE).
- resource measurement
facility (RMF)
- An IBM licensed program that collects system-wide
data describing the processor activity (WAIT time), I/O activity (channel
and device utilization), main storage activity (demand and swap paging statistics),
and system resources manager (SRM) activity (workload). RMF produces two types
of report, system-wide reports and address-space reports.
- resource
member class
- A class to which a resource group class is related.
See also resource group class.
- Resource Object
Data Manager (RODM)
- In Tivoli NetView for z/OS, a component that
provides an in-memory cache for maintaining real-time data in an address space
that is accessible by multiple applications.
- resource profile
- A profile that provides RACF protection for one or more resources. User, group,
and connect profiles are not resource profiles. The information in a resource
profile can include the data set profile name, profile owner, universal access
authority, access list, and other data. Resource profiles can be discrete
profiles or generic profiles. See discrete profile and generic profile.
- resource protection
- The system function of enqueueing on a resource
to provide exclusive control of that resource to a transaction until the end
of a logical unit of work.
- resource region
- In CICS distributed
program link, a CICS region to which an application region ships a LINK PROGRAM
request.
- resource security
- In CICS/VSE, the facility provided by CICS for
the control of access to resources protected by RSL security. The resources
that can be protected include transactions, data sets, and transient data
destinations. In CICS Transaction Server, the facility provided by CICS and
RACF for the control of access to resources protected by RACF security classes.
The resources that can be protected include transactions, data sets, and transient
data destinations.
- response
- In SNA, a message unit
that acknowledges receipt of a request; a response consists of a response
header (RH), a response unit (RU), or both.
- response mode
- (1) 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 non-response mode.
- (2) A mode in which a system can communicate with
an end-user.
- response time
- The elapsed time between entering an inquiry or
request and receiving a response.
- restart
- Resumption of operation
after recovery. Ability to restart requires knowledge of where to start and
ability to start at that point.
- restart data set (RSD)
- A VSAM KSDS used only during a CICS emergency restart. The RSD temporarily
holds the backout information read from the CICS system log. This allows CICS
to be restored to a stable state and to be restarted following an abrupt termination.
- restart in place
- In XRF, the restart of a failed active CICS system,
instead of a takeover by the alternate CICS system.
- resynchronization
- The completion of an interrupted two-phase commit process for
a unit of work.
- RETAIN
- Database used by IBM Support Centers
to record all known problems with IBM licensed programs.
- retract
- To
remove the reference to the home of the bean in a namespace. Retract reverses
the action of publish.
- return code
- A value returned by a program
to indicate the result of its processing.
- return code equate
- In DBCTL, an alphanumeric equivalent of a numeric return code, such
as UERCNOAC for take no action. DBCTL uses return code equates in the XRF
global user exits, XXDFA, XXDFB, and XXDTO.
- revoke count
- Number
of unsuccessful signon attempts since the last successful signon with a particular
userid.
- RH
- See request header (RH).
- RIS
- See recoverable in-doubt structure (RIS).
- RLDS
- See recovery log data set (RLDS).
- RMF
- See resource measurement facility (RMF).
- RMI
- See resource manager interface (RMI) and remote method invocation .
- RODM
- Resource Object Data Manager.
- rollback
- (1) A programmed return
to a prior checkpoint.
- (2) In CICS, the cancellation by an application
program of the changes it has made to all recoverable resources during the
current logical unit of work.
- root activity
- The
activity at the top of an activity tree. It has no parent activity.
- rotational position sensing (RPS)
- A function that permits a disk
storage device to disconnect from a block multiplexer channel (or its equivalent),
allowing the channel to service other devices on the channel during positional
delay.
- route list
- A list that designates terminals or logical units,
or particular operators, for which logical messages are to be scheduled for
delivery.
- router
- An MVS program that presents a common systems interface
for all products providing resource control. Resource managing components
(such as CICS) call the MVS router as part of certain decision-making functions
in their processing.
- router exit
- A point in the MVS router that
can be modified to use a user-written or a vendor-supplied external security
manager, instead of having the MVS router pass control to RACF.
- routine
- A
program or sequence of instructions called by a program. Typically, a routine
has a general purpose and is frequently used. CICS and the programming languages
use routines.
- routing region
- In the dynamic routing
of BTS processes and activities, the CICS region on which the distributed
routing program runs. In BTS routing, the routing region is the same as the
requesting region. See also requesting region, target region.
- routing transaction
- A CICS transaction (CRTE) that enables an
operator at a terminal owned by one CICS system to sign on to another CICS
system connected by means of an IRC or APPC link.
- RPL
- See request parameter list (RPL).
- RPS
- See rotational position sensing (RPS).
- RRDS
- See relative record data set (RRDS).
- RRN
- See relative record number (RRN).
- RSCS
- See remote spooling communications subsystem (RSCS).
- RSD
- See restart data set (RSD).
- RSE
- See recoverable service element (RSE).
- RST
- See recoverable service table (RST).
- RTA
- See real-time analysis (RTA).
- RU
- See request unit (RU).
- runaway task
- A task that has been dispatched and does not return
control to CICS within a user-specified time interval. The program being used
by this task is in a loop between two CICS requests. The task control program
abends the task after expiration of this time interval, which is called the
runaway task time interval.
- run unit
- 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.
[[ Contents Previous Page | Next Page Index ]]