ne lock on a table. This process is repeated until the limit is no longer exceeded.
lock manager domain
Major component of CICS that provides locking and associated queueing for CICS resources. Before using these facilities, a resource must add a named lock for itself. This lock can then be requested as either exclusive or shared. If an exclusive lock is obtained, no other task many obtain the lock with that name; if a shared lock is obtained, multiple tasks may obtain that lock.
lock sequence number (LSN)
A unique number, issued sequentially, given to a database resource to identify that it is in use (locked) by a requestor. A locked resource cannot be used until the current requestor has finished using it.
- The state set by actuating a lock key, singly or in combination with a qualifier key (see ISO/IEC 9995-1).
- A condition defined for an object that determines how it is locked, how it is used (read or write), and whether the object can be shared (used by more than one job).
See loopback virtual file system.
- A record of events.
- A collection of records that sequentially describes the events that occur in a system.
- In WebSphere MQ, a file recording the work done by queue managers while they receive, transmit, and deliver messages, to enable them to recover in the event of failure.
- In Backup, Recovery, and Media Services, a history of backup, archive, recovery, and media management operations. A log can be displayed online or printed.
- A file used to record changes made in a system.
- To record. For example, to record all messages on the system printer.
- A collection of messages or message segments placed in an auxiliary storage device for accounting or data collections purposes.
Log and Trace Analyzer tool
The core technology of the IBM Autonomic Computing initiative that defines the interfaces for logging and tracing, providing a central point of interaction with multiple data sources.
log control file
In WebSphere MQ on UNIX and Linux systems, and WebSphere MQ for Windows, the file containing information needed to monitor the use of log files (for example, their size and location, and the name of the next available file).
- A file that records actions and commands.
- A text file that records the execution of a fact build, dimension build, or JobStream.
- The file where the log of events is recorded.
- In WebSphere MQ on UNIX and Linux systems, and WebSphere MQ for Windows, a file in which all significant changes to the data controlled by a queue manager are recorded. If the primary log files become full, WebSphere MQ allocates secondary log files.
An operator station task that requires a terminal and a logged-on user. See also autotask.
- A functional unit that records events and physical conditions, and usually the time the entry was logged.
- A named and stateful object with which the user code interacts and that logs messages for a specific system or application component.
- A program that enables a user entity to log in (for example, identify itself, its purpose, and time of entry) and log off with the corresponding data. This enables the appropriate accounting procedures to be carried out in accordance with the operating system.
- A component that prepares log statements to be written to console or log file. See also appender.
An agent that programmers can create in order to write data (for example Java primitives, objects, or predefined logging structures) to one or more output sources (for example text or XML), for an application under test.
- A value that controls which events are written to the log by event severity.
- A preference setting that specifies the number of entries and the amount of detail generated by various loggers.
- A value that controls which events are processed by Java logging.
- The instructions in an application arranged in a prescribed order to solve a problem.
- The systematized interconnection of digital switching functions, circuits, or devices.
Specialization of an architecture through the addition of constraints that enable verification of consistency and validity for th