L

LAN
See local area network
Language Environment for VSE/ESA
In CICS/VSE, a run-time library that establishes a common execution environment for a number of SAA programming languages. See also Systems Application Architecture (SAA).
LANGUAGE segment
The portion of a RACF profile containing information about the national language in which the user receives messages.
last-in first-out (LIFO)
A queuing technique in which the next item to be retrieved is the last item placed on the queue.
LDC
See logical device component (LDC).
librarian
In CICS/VSE, the set of programs that maintains, services, and organizes the system and private libraries.
library
A partitioned data set or a series of concatenated partitioned data sets. See also partitioned data set extended (PDSE).
library lookaside (LLA)
A facility in MVS/ESA that reduces library I/O activity by keeping selected directory entries in storage, instead of making repetitive searches of DASD.
library path
The path used in a JVM for native C dynamic link library (DLL) files that are used by the JVM, including those required to run the JVM and additional native libraries loaded by trusted code.
LIFO
See last-in-first-out (LIFO).
LIFO storage
Storage used by reentrant CICS management modules to save registers.
Lightweight Directory Access Protocol (LDAP)
A network protocol for accessing directories. It is based on the X.500, an ITU-T standard that is part of the OSI suite of services. In the Lightweight Directory Access Protocol, the naming convention is that components are ordered right to left, and are delimited by comma characters (','). Thus, the LDAP name cn=Rosanna Lee, o=Sun, c=US names an LDAP entry cn=Rosanna Lee, relative to the entry o=Sun, which in turn, is relative to c=us. The LDAP has the further rule that each component of the name must be a name/value pair with the name and value separated by an equal character ('=').
line
(1) The physical path in data transmission.
(2) On a terminal, one or more characters entered before a return to the first printing or display position, or accepted by the system as a single block of output.
linkage editor
A computer program for creating load modules from one or more object modules or load modules by resolving cross-references among the modules and, if necessary, adjusting addresses.
link pack area (LPA)
A major element of MVS/ESA virtual storage below the 16MB line. The storage areas that make up the LPA contain all the common reentrant modules shared by the system. The LPA provides economy of real storage by sharing one copy of the modules, protection because LPA code cannot be overwritten even by key 0 programs, and reduced pathlength because the modules can be branched to. The LPA is duplicated above the 16MB line as the extended link pack area (ELPA). See the CICS Transaction Server Performance Guide for more information.
link security
A limit on one system's authorization to attach transactions and access resources in another. Link security works by signing on each end of a session (to RACF, in CICS Transaction Server) when the session is bound. Each half-session then has the access requirements of the single user profile defined for the remote system as a whole. This profile is applied when a transaction is attached and whenever the transaction accesses a protected resource. See also bind-time security.
LISTCAT
A VSAM tool that provides information that interprets the actual situation of VSAM data sets.
list-of-groups checking
A RACF option that allows a user to access all resources available to all groups of which the user is a member, regardless of the user's current connect group. For any particular resource, RACF allows access based on the highest access authority among the groups of which the user is a member.
LLA
See library lookaside (LLA).
LMOD
See load module (LMOD).
loader
A program that reads run files into main storage so that the files can be run.
loader domain
Major component of CICS used by the domains of the CICS system to obtain access to storage-resident copies of nucleus and application programs, maps, and tables. In order to provide this, the loader domain interfaces with MVS to perform loading of programs into CICS-managed storage (DSA/EDSA) and scanning of the MVS link pack area.
load library
A library containing load modules.
load module (LMOD)
A program in a form suitable for loading into main storage for execution. A load module is the output of the linkage editor. The abbreviation LMOD is an SMP/E term specifically for an executable load module in a target library See also command language translator, object module.
local
Pertaining to a device, file, or system that is accessed directly from a user's system, without the use of a communication line. See also remote.
local area network (LAN)
(1) A self-contained network that connects several devices in a limited area (such as a single office building, warehouse, or campus).
(2) A data network used for direct data communication between data stations physically close to each other, usually all located in a single building.
local catalog
A system data set that CICS uses to record data used by the internal workings of CICS. See also global catalog.
local catalog domain
Together with the global catalog domain, a repository used by other CICS domains to hold information to allow an orderly restart. The two catalog domains enable CICS code to read, write, and purge records on the local and global catalog data sets so that a record of the CICS state can be maintained when CICS is not running.
local CMAS
The CICSPlex SM address space (CMAS) that a user identifies as the current context when performing CMAS configuration tasks.
local DL/I
DL/I residing in the CICS address space.
locale
An object that can determine how data is processed, printed, and displayed. Locales are made up of categories that define language, cultural data, and character sets.
locality of reference
The consistent reference, during the execution of an application program, to instructions and data within a relatively small number of pages (See also with the total number of pages in a program) for relatively long periods of time.
local request queue
A recoverable VSAM data set used to store pending BTS requests - for example, timers and unserviceable requests. It is used to ensure that, if CICS fails, no pending requests are lost. Unlike repository data sets, the local request queue is a mandatory CICS data set; you must define one, and only one, to each CICS region, even if you don't use BTS. It is never shared. It relates solely to requests that are issued on the local region.
local resource
In CICS intercommunication, a resource that is owned by the local system. See also remote resource.
local shared resources (LSR)
Files that share a common pool of buffers and a common pool of strings; that is, control blocks supporting I/O operations. See also nonshared resources (NSR).
local system
In a multisystem environment, the system on which an application program is executing. A local application can process data from databases located on either the same (local) system or another (remote) system. See also remote system.
local system queue area (LSQA)
An element of the CICS address space. It generally contains the control blocks for storage and contents supervision. See The CICS private area for more information. See also high private area.
local work area
Area provided for the use of a single task-related user exit program. It is associated with a single task and lasts for the duration of the task only.
lock
A mechanism with which a resource is restricted for use by the holder of the lock.
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.
log
A file used to record changes made in a system.
logging
The recording (by CICS) of recovery information onto the system log, for use during emergency restart. A specific journaling function that records changes made to the system activity environment and database environment. These records are required for recovery and backout support by CICS (and the user) following an abnormal termination.
logical database
A database composed of one or more physical databases representing a hierarchical structure that is derived from relationships between data segments, and that can be different from the physical structure.
logical device component (LDC)
A subcomponent (for example, a printer or a console) configured with a 3601, 3770 batch, 3770, 3790 batch or LU Type4 terminal. Each subcomponent is handled by BMS output commands as if it is a separate terminal.
logical message
A collection of formatted output data produced by chaining several smaller pieces of data. You build a logical message by issuing a series of BMS SEND commands.
logical partition (LP, LPAR)
A partition, in a CEC, capable of running its own MVS image. An LP comprises a set of hardware resources (processors, storage, channels, and so on), sufficient to allow a system control program such as MVS or VSE to be executed.
logical recovery
Restoration of a facility to its status at a point just prior to any in-flight transaction activity.
logical unit (LU)
In SNA, a port through which a user gains access to the services of a network.
logical unit of work (LUW)
The processing that a program performs between synchronization points.
logical unit of work identifier (LUWID)
A name (consisting of a fully qualified LU network name, a logical-unit-of-work (LUW) instance number, and an LUW sequence number) that uniquely identifies a logical unit of work within a network.
log manager
A new domain in CICS Transaction Server for z/OS, which replaces the CICS journal control management function of current CICS releases. The CICS log manager uses MVS system logger services to write CICS system logs, forward recovery logs, and user journals to log streams managed by the MVS system logger.
logname
The name of the CICS system log currently in use. See exchange lognames.
log on
The act of establishing a session with VTAM.
long running mirror
A mirror task that waits for the next syncpoint in a session, even though it logically does not need to do so (applicable only to MRO links).
long UOW id
A 27-byte value that CICS uses to identify a distributed UOW. This is built from a short UOW id prefixed by two 1-byte length fields and by the fully-qualified NETNAME of the CICS region.
look-aside query
In BMS, a query performed in one partition by an operator working in another partition. Using partitions, a partially completed operation need not be transmitted to the host processor before releasing the screen for an inquiry.
LP
See logical partition (LP or LPAR).
LPA
See link pack area (LPA).
LPAR
See logical partition (LP or LPAR).
LSQA
See local system queue area (LSQA).
LSR
See local shared resources (LSR).
LU
See logical unit (LU).
LU0
See LUTYPE0 (LU0).
LU1
See LUTYPE1 (LU1).
LU2
See LUTYPE2 (LU2).
LU3
See LUTYPE3 (LU3).
LU4
See LUTYPE4 (LU4).
LU6
See LU type 6 (LU6).
LU6.1
See LUTYPE6.1 (LU6.1).
LU-LU session
A connection between two logical units (LUs) in an SNA network that provides communication between two users.
LU type 0 (LU0)
Type of logical unit used for communicating with non-SNA terminals, using binary synchronous communication (BSC). LU0 enables the transmission of non-SNA protocols across an SNA network, and is heavily used for connecting non-SNA terminals. LU0 is more primitive than LU6.
LU type 1 (LU1)
An SNA logical unit type that provides a communication protocol among host application programs and terminals. Some printers also use this protocol to communicate with host application programs.
LU type 2 (LU2)
Type of logical unit, used for communicating with 3270 displays.
LU type 3 (LU3)
Type of logical unit, used for sending data to 3270 printers.
LU type 4 (LU4)
Type of logical unit, Used for communicating with office systems terminals.
LU type 6 (LU6)
Type of logical unit, used for processor-to-processor communication. LUTYPE6 defines a number of processes (applications - the file model, the queue model, the DL/I model, and so on) which are used in CICS intersystem communication (ISC). LUTYPE6 also supports user application to user application communication. There is no BMS support for this LU Type.
LU type 6.1 (LU6.1)
Type of logical unit used for processor-to-processor sessions. LU type 6.1 is a development of LU type 6. CICS - DL/I, IMS, or SQL/DS intercommunication uses LU type 6.1 sessions.
LU type 6.2
An SNA logical unit type that converges functions from existing LU types to provide a single, interchangeable communication protocol.
LUW
See logical unit of work (LUW).
LUWID
See logical unit of work identifier (LUWID).
[[ Contents Previous Page | Next Page Index ]]