U

UACC
See universal access authority (UACC).
UDSA
See user dynamic storage area (UDSA).
UIB
See user interface block (UIB).
UMT
See user-maintained data table (UMT).
unattended node support
A set of functions allowing one or more VSE systems to run without an operator being present. The systems are connected to a single central host.
unbind
In SNA, to deactivate a session between logical units.
UNBIND
See unbind session (UNBIND).
unbind session (UNBIND)
A request to deactivate a session between two logical units (LUs). See also BIND.
undo
In a data entry database, a state that occurs when no changes have been committed in the database. The changes are still in main storage and are backed out from there.
UNICODE
A universal character encoding standard that supports the interchange, processing, and display of text that is written in any of the languages of the modern world. It also supports many classical and historical texts in a number of languages. The Unicode standard has a 16-bit international character set defined by ISO 10646.
unit of compilation
In VS COBOL II, a section of source input from which the compiler produces a single object program. A unit of compilation can consist of a containing program and other programs nested within it.
unit of recovery
A sequence of operations within a unit of work between commit points.
unit of recovery descriptor (URD)
A CICS control block that describes the progress of a unit of work through the sequence of syncpoint messages. The URD is chained off the CSA, and survives any failure of either system. It is used for recovery at CICS restart.
unit of work
A recoverable sequence of operations performed by an application between two points of consistency. A unit of work begins when a transaction starts or at a user-requested syncpoint. It ends either at a user-requested syncpoint or at the end of a transaction. See also unit-of-recovery.
unit-of-work identifier
In advanced program-to-program communications, a unique label assigned to the unit of work. The ID is established when the program on the source system is started and is associated with each job started by that source system on the target system. The unit-of-work identifier provides a beginning-to-end audit trail within an APPC network.
universal access authority (UACC)
In RACF, the default access authority that applies to a resource if the user or group is not specifically permitted access to the resource. The universal access authority can be any of the access authorities.
unmapped conversation
See basic conversation.
unserviceable request
A request to run an activation of an activity which currently cannot be satisfied, either because the activity is not available or because the region on which the request must run is inaccessible.
unshunting
The process of attaching a transaction to provide an environment under which to resume the processing of a shunted unit of work.
unsolicited data
A type of inbound data that arrives on a connection where no FEPI conversation is active.
unsolicited data handler
A user-provided part of a FEPI application that handles unsolicited inbound data.
unsolicited statistics
CICS statistics automatically gathered by CICS for a dynamically allocated and deallocated resource (for example, an autoinstalled terminal) when the resource is about to be deleted. See also interval statistics, end-of-day statistics, requested statistics, and requested reset statistics.
untracked terminal
In XRF (CICS/VSE only), a terminal belonging to a class mainly comprised of TCAM(DCB) terminals. These terminals lose their sessions at takeover. The CICS Transaction Server equivalent of this is class 3 terminal.
unwanted takeover
In XRF, a takeover initiated by the alternate CICS system when there was not an actual failure on the active CICS system. This might be due to an unusual system condition which, although not a true failure, slowed down the active system's participation in the surveillance process to the point where the alternate system believed that a failure on the active system had occurred.
update
To modify a file or data set with current information.
update intent
In IMS, DL/I, or SQL/DS, the type of access intent that allows a subsystem to insert, delete, or replace records on a database.
URD
See unit of recovery descriptor (URD).
URL
See user route list (URL).
use count
Number of tasks using a program concurrently. This is maintained by CICS in the program processing table.
user
Any person, organization, process, device, program, protocol, or system that uses the services of a computing system. A user can be assigned one or more roles.
user activity keypoint
A keypoint written to the system log by a user transaction. See also activity keypoint.
user authentication
In RACF, part of security checking at signon. It consists of identification of the userid and verification of the password or of the user identification card.
user data set
In MVS, a data set defined to RACF in which either the high-level qualifier of the data set name or the qualifier supplied by an installation exit routine is a RACF userid. Compare group data set.
user-defined event
An event defined by the application programmer. The BTS user-defined events are activity completion events, input events, timer events, and composite events. Compare with system event.
user domain
A CICS domain responsible for identifying users and recording their non-security attributes.
user dynamic storage area (UDSA)
A storage area in CICS Transaction Server allocated below the 16MB line and reserved exclusively for those user application programs that execute in user-key and that reside below the 16MB line.
user exit
A point in a program at which a user exit routine may be given control.
user exit handler
A CICS program that is invoked at an exit point (other than an exit point in a domain) to handle the user exit program associated with that exit point. For programming information, see the Customization Guide.
user exit programming interface (XPI)
A CICS interface that provides global user exit programs with access to some CICS services. XPI consists of a set of function calls that you can use in your user exit programs to extend or modify CICS system functions. For programming information, see the CICS Transaction Server Customization Guide.
user ID
See user identifier (userid).
user identification and verification
The acts of identifying and verifying a RACF-defined user to the system during logon or batch job processing. RACF identifies the user by the user ID and verifies the user by the password or operator identification card supplied during logon processing or the password supplied on a batch JOB statement.
user identifier (user ID)
A string of characters that uniquely identifies a user to a system.
user interface block (UIB)
A control block used in the CALL DLI interface to pass information to the user program. It contains the address of the PCB address list (UIBPCBAL) from the schedule request, and the response code to each DL/I request. A definition of the UIB should only be included in the application program if the UIB is to be referenced. The UIB is acquired by the interface routine when an application program issues a schedule request specifying a pointer reference to be set with the address of the UIB.
user-key
Storage obtained by CICS in MVS open-key storage. It is for user application programs and their associated data areas. It can be accessed and modified by user applications and by CICS. See CICS-key, storage protection.
user-maintained data table (UMT)
A type of CICS data table that has no CICS-supported association with its source data set after it has been loaded. Changes to the table are not automatically reflected in the source data set.
user name
In RACF, one to twenty alphanumeric characters that represent a RACF-defined user.
user profile
In computer security, a description of a user that includes such information as user ID, user name, password, access authority, and other attributes that are obtained when the user logs on.
user-related activity
An activity that requires human involvement. Such an activity cannot be started automatically by BTS, because it is dependent on a user being ready to process the work.
user-replaceable program
A CICS program that is invoked at a particular point in CICS processing as if it were part of CICS code. You can modify the supplied program by including your own logic, or replace it with a version that you write yourself. Examples include the dynamic routing program, and the transaction restart program.
user route list (URL)
A list of terminals to which a routed message is to be sent by BMS. Each entry in the list contains the terminal identification, any necessary logical device code or operator identification, and a status flag.
user security
That part of a security facility that verifies that a user is authorized to (a) sign on to a local or remote system (b) run a transaction and (c) to access the resources and use the commands that a transaction invokes.
user-supplied route list entry
An entry that defines the terminals or operators to which a BMS logical message is to be routed.
user transaction
A user-written transaction.
user transaction abend code
An abend code issued by a user program or by an IBM licensed program other than CICS. See access security information field (ASIF).
[[ Contents Previous Page | Next Page Index ]]