Glossary of terms and acronyms

abnormal end of task (abend): The termination of a task, job, or subsystem because of an error condition that recovery facilities cannot resolve during execution.
address space: The range of addresses available to a computer program or process. Address space can refer to physical storage, virtual storage, or both.
Advanced Program-to-Program Communication: See APPC.
aggregate function: Any of a group of functions that summarizes data in a column. They are requested with these usage codes on the form panels: AVERAGE, CALC, COUNT, FIRST, LAST, MAXIMUM, MINIMUM, STDEV, SUM, CSUM, PCT, CPCT, TPCT, TCPCT.
aggregation variable: An aggregation function that is placed in a report using the FORM.BREAK, FORM.CALC, FORM.DETAIL, or FORM.FINAL panels. Its value appears as part of the break footing, detail block text, or final text when the report is produced.
alias: An alternative name used to identify a table, view, database, or nickname. An alias can be used in SQL statements to refer to a table, view, or database in the same DB2® system or subsystem or in a remote DB2 system or subsystem.
APAR (Authorized Program Analysis Report): A request for correction of a defect in a supported release of an program supplied by IBM.
APF (authorized program facility): In a z/OS® environment, a facility that permits the identification of programs that are authorized to use restricted functions.
API (application programming interface): An interface that allows an application program that is written in a high-level language to use specific data or functions of the operating system or another program.
application: One or more computer programs or software components that use QMF services to provide functionality in direct support of a specific business process or processes.
APPC (Advanced Program-to-Program Communication): An implementation of the SNA LU 6.2 protocol that allows interconnected systems to communicate and share the processing of programs.
application plan: The control structure that is produced during the bind process. The default name for the QMF Version 11 application plan is QMF11.
application programming interface: See API.
application requester: The source of a request to a remote DRDA-enabled relational database management system (RDBMS). Only Db2 for z/OS databases can function as application requesters because this is the only type of database in which QMF can be started.
application server: The target of a request from an application requester. The database management system (DBMS) at the application server site services the request. Connectivity with remote servers is not supported when QMF for TSO is running as a Db2 for z/OS stored procedure.
argument: A value passed to or returned from a function or procedure at run time.
authorization identifier (authorization ID): A character string that designates a set of privileges and can be used to verify authority. An authorization ID can represent an object, an individual user, an organizational group, a function, or a database role. QMF authenticates either the database authorization ID or, optionally, the QMF TSO logon ID, against the CREATOR column of the Q.PROFILES table during QMF initialization.
Authorized Program Analysis Report: See APAR.
Authorized program facility: See APF.
auxiliary table: A table that stores columns outside the table in which they are defined. See also base table.
base product: The English-language version of QMF, established when QMF is installed. Any other language environment is established after installation by installing the National Language Feature (NLF) associated with that language.
base table: A table that is created by the SQL CREATE TABLE statement and that holds persistent data.
binary string: A sequence of bytes that is not associated with a coded character set and therefore is never converted. For example, the BLOB data type is a binary string. See also CCSID.
bind: To convert the output from the DBMS precompiler to a usable control structure, such as an access plan, an application plan, or a package.
bit data: Data with a data type of CHAR or VARCHAR that is not associated with a coded character set and therefore is never converted.
buffer pool: An area of memory into which data pages are read and in which they are modified and held during processing. See also address space.
built-in function: A strongly typed, high-performance function that is integral to the DB2 database. A built-in function can be referenced in SQL statements anywhere that an expression is valid.
CAF (call attachment facility): A Db2 for z/OS attachment facility for application programs that run in TSO or z/OS batch. The CAF is an alternative to the DSN command processor and provides greater control over the execution environment.
call attachment facility: See CAF.
callable interface: A programming interface that provides access to QMF objects and services.
cascade delete: A process by which the DB2 database manager enforces referential constraints by deleting all descendent rows of a deleted parent row.
catalog: A collection of tables and views that contains descriptions of objects such as tables, views, and indexes. See also QMF object catalog.
CCSID (coded character set identifier): A 16-bit number that includes a specific set of encoding scheme identifiers, character set identifiers, code page identifiers, and other information that uniquely identifies the coded graphic-character representation. Because QMF uses display services provided by GDDM, the GDDM application code page must agree with the CCSIDs in use for the database. See also binary string.
character string: A sequence of bytes that represents bit data, single-byte characters, or a mixture of single-byte and multibyte characters.
check constraint: A user-defined constraint that specifies the values that specific columns of a base table can contain. See also constraint.
CICS® (Customer Information Control System): An IBM® licensed program that provides online transaction-processing services and management for business applications.
clause: In SQL, a distinct part of a statement in the language structure, such as a SELECT clause or a WHERE clause.
CM (Compatibility Mode): An installation mode of QMF Version 8.1 and QMF Version 9.1 that limited owner and object names in the QMF object catalog to eight and 18 characters, respectively. See also NFM.
code page: A particular assignment of code points to graphic characters. Within a given code page, a code point can have only one specific meaning. A code page also identifies how undefined code points are handled.
coded character set identifier: See CCSID.
coexistence: The state during which two QMF releases exist in the same DB2 subsystem. QMF Version 11 can coexist with QMF Version 9.1 New Function Mode or QMF Version 8.1 New Function Mode only.
column: The vertical component of a database table. A column has a name and a particular data type (for example, character, decimal, or integer).
column function: See aggregate function.
column wrapping: The value formatting in a report where the values occupy several lines within a column. Column wrapping is often used when a column contains values whose length exceeds the column width, such as cases requiring the display of XML data.
command interface: An interface for issuing QMF commands. The command interface allows you to issue QMF commands from an ISPF dialog running under QMF. Using this interface, QMF communicates with the dialog through the ISPF variable pool.
command synonym: The verb or verb/object part of a site-defined command. After command synonyms are defined and activated in the QMF profile, users can enter the synonyms on the QMF command line as they do with regular QMF commands.
command synonym table: A table that stores one site-defined command in each row. You assign a set of command synonyms to a user by storing the name of this table in the user's profile.
comparison operator: In SQL, a symbol used in comparison expressions to specify a relationship between two values. Comparison operators are = (equal to), <> (not equal to), < (less than), > (greater than), <= (less than or equal to), and >= (greater than or equal to).
Compatibility Mode: See CM.
commit: To end a unit of work by releasing locks so that the database changes made by that unit of work can be perceived by other processes. This operation makes the data changes permanent.
concatenation: Joining two characters or strings to form one string.
connection: In data communication, an association established between entities for conveying information. See also SQL connection. Connectivity with remote servers is not supported when QMF for TSO is running as a Db2 for z/OS stored procedure.
constant: A language element that specifies an unchanging value. Constants are classified as string constants or numeric constants.
constraint: A rule that limits the values that can be inserted, deleted, or updated in a table.
control section: See CSECT.
control tables: A set of tables that QMF uses to store information about QMF objects and manage QMF operations. See also QMF object catalog.
correlated reference: A reference to a column of a table or view that is outside a subquery.
correlation name: An identifier specified and used within a single SQL statement as the exposed name for objects such as a table, view, table function reference, nested table expression, or data change table reference. Correlation names are useful in an SQL statement to allow two distinct references to the same base table and to allow an alternative name to be used to represent an object.
CSECT (control section): The part of a program specified by the programmer to be a relocatable unit, all elements of which are to be loaded into adjoining main storage locations.
current location: The application server to which the QMF session is currently connected. After the connection is made, this server processes all SQL statements. When initializing QMF, the current location can be indicated using the DSQSDBNM startup parameter. Connectivity with remote servers is not supported when QMF for TSO is running as a Db2 for z/OS stored procedure.
current object: A QMF object that is held in temporary storage so that, with each use, it can be readily accessed without requiring database retrieval. There are seven temporary storage areas: QUERY, FORM, PROC, PROFILE, REPORT, DATA, and CHART. Users can navigate to all areas but the DATA area using the SHOW and DISPLAY commands. See also temporary storage.
cursor: A named control structure used by an application program to point to and select a row of data from a set.
Customer Information Control System: See CICS.
data type: A classification identifying one of various kinds of data. In SQL, the data type is an attribute of columns, literals, host variables, special registers, parameters, and the results of functions and expressions.
database: A collection of interrelated or independent data items that are stored together to serve one or more applications.
database administrator: A person who is responsible for the design, development, operation, security, maintenance, and use of a database.
database management system: See DBMS.
database manager: A program that manages data by providing centralized control, data independence, and complex physical structures for efficient access, integrity, recovery, concurrency control, privacy, and security.
database server: A software program that uses a database manager to provide database services to other software programs or computers.
DBCS (double-byte character set): A set of characters in which each character is represented by two bytes. These character sets are commonly used by national languages such as Japanese and Chinese, which have more symbols than can be represented by a single byte. See also SBCS.
DBMS (database management system): A software system that controls the creation, organization, and modification of a database and the access to the data that is stored within it.
DCT (destination control table): A table describing each of the transient data destinations used in CICS. This table contains an entry for each extrapartition, intrapartition, and indirect destination.
default form: The QMF form created when a saved form is not specified on the RUN QUERY command.
default value: A predetermined value, attribute, or option that is assumed when no other value is specified. A default value can be defined for column data in DB2 tables by specifying the DEFAULT keyword in an SQL statement that changes data (such as INSERT, UPDATE, and MERGE).
dependent row: A row that contains a foreign key that matches the value of a parent key in the parent row. The foreign key value represents a reference from the dependent row to the parent row.
dependent table: A table that is a dependent of an object. For example, a table with a foreign key is a dependent of the table containing the corresponding primary key.
destination control table: See DCT.
detail block text: The text in the body of a report that is associated with a particular row of data.
detail heading text: The text in the heading of a report.
detail variation: A data formatting definition specified on a FORM.DETAIL panel that can be used to conditionally format a report or part of a report.
distinct type: A user-defined data type that shares a common representation with built-in data types.
distributed data: Data that is stored on more than one system and is available to remote users and application programs.
distributed database: A database that appears to users as a logical whole, locally accessible database, but consists of databases in multiple locations that are connected by a data communications network.
Distributed Relational Database Architecture™: See DRDA.
distributed unit of work: A form of distributed relational database processing that enables a user or application program to read or update data at multiple locations within a unit of work. Within one unit of work, an application, such as QMF, running in one system can direct SQL requests to multiple remote database management systems using the SQL supported by those systems. The request is made through a QMF command that includes a three-part table or view name. QMF commands with three-part names cannot be directed to DB2 for VM or VSE databases or used when QMF for TSOhas been started as a Db2 for z/OS stored procedure. Three-part names in QMF commands also cannot refer to a table that contains large object (LOB) data types.
double-byte character set: See DBCS.
double-precision floating-point number: A 64-bit approximate representation of a real number.
DRDA (Distributed Relational Database Architecture): The architecture that defines formats and protocols for providing transparent access to remote data. DRDA defines two types of functions: the application requester function and the application server function.
environment: A named collection of logical and physical resources used to support the performance of a function.
exit routine: A program that receives control from another program to perform specific functions.
Extensible Markup Language: See XML.
extended syntax: Syntax that is used for the QMF SET GLOBAL and GET GLOBAL commands and certain function calls. Extended syntax defines parameters used by QMF callable interface applications written in Assembler, C, COBOL, Fortran, or PL/I.
fallback: The process of returning to a prior release of a software program after attempting or completing migration to a current release.
fetch: The process of retrieving rows from the database or a file to create a QMF DATA object. QMF supports multirow fetch through the use of the DSQSMRFI parameter.
foreign key: In a relational database, a key in one table that references the primary key in another table.
GDDM (Graphical Data Display Manager): Graphics software that defines and displays text and graphics for output on a display device or printer.
global variable: A named entity whose value persists for the duration of a QMF session. QMF uses global variables to manage both session and database activity. Some global variables can be set with the SET GLOBAL command, while others record information about the state of the current QMF session and therefore cannot be set.
graphic string: A sequence of double-byte character set (DBCS) characters.
Graphical Data Display Manager: See GDDM.
host: The controlling or highest-level system in a data communications configuration.
HTML (hypertext markup language): A markup language that conforms to the Standard Generalized Markup Language (SGML) standard and was designed primarily to support the online display of textual and graphical information, including hypertext links.
hypertext markup language: See HTML.
ICU (Interactive Chart Utility): A menu-driven component of IBM's Graphical Data Display Manager (GDDM) product that allows non-programmers to display, print, or plot charts, graphs, and diagrams.
identity column: A column that provides a way for the DB2 database manager to automatically generate a numeric value for each row that is inserted into a table. Identity columns are defined with the AS IDENTITY clause. A table can have no more than one identity column.
index: A set of pointers that is logically ordered by the values of a key. Indexes provide quick access to data and can enforce uniqueness of the key values for the rows in the table.
inner join: The result of a join operation that includes only the matched rows of both tables that are being joined. See also outer join.
installation verification procedure: See IVP.
Integrated Exchange Format: See IXF.
Interactive Chart Utility: See ICU.
Interactive System Productivity Facility: See ISPF.
ISPF (Interactive System Productivity Facility): An IBM licensed program that serves as a full-screen editor and dialog manager. Used for writing application programs, it provides a means of generating standard screen panels and interactive dialogs between the application programmer and terminal user.
IVP (installation verification procedure): A procedure or program whose purpose is to verify that a product has been correctly installed.
IXF (Integrated Exchange Format): A protocol for transferring tabular data among various software products.
JCL (job control language): A command language that identifies a job to an operating system and describes the job's requirements.
job control language: See JCL.
join: An SQL relational operation that allows retrieval of data from two or more tables based on matching column values.
key: A column or an ordered collection of columns that is identified in the description of a table, index, or referential constraint. The same column can be part of more than one key.
keyword: One of the predefined words of a programming language, artificial language, application, or command.
keyword parameter: A parameter that consists of a keyword followed by one or more values. See also positional parameter.
large object: See LOB.
link-edit: To create a loadable computer program by means of a linkage editor.
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.
literal: A character string whose value is defined by the characters themselves. For example, the numeric constant 7 has the value 7, and the character constant 'CHARACTERS' has the value CHARACTERS.
linear procedure: A sequenced set of QMF commands or command synonyms that can be used to perform several operations at once. See also procedure with logic.
linear syntax: QMF command syntax that is entered in one statement of a program or procedure, or that can be entered on the QMF command line.
load module: A program in a form suitable for loading into main storage for execution.
LOB (large object): A sequence of bytes with a size ranging from 0 bytes to 2 gigabytes (less 1 byte). There are three LOB data types: binary large object (BLOB), character large object (CLOB, which can include single-byte characters only or a mixture of single-byte and double-byte characters), and double-byte character large object (DBCLOB). QMF supports a LOB column size of up to 32 KB.
local: Pertaining to databases, objects, or applications that are installed or stored in the system in which QMF is currently running.
location: A specific relational database server in a distributed relational database system. Each location has a unique location name.
location name: The unique name of a database server. An application uses the location name to access a DB2 database server.
lock: A means of serializing a sequence of events or serializing access to data.
log: A collection of records that sequentially describes the events that occur in a system.
LUW: An abbreviation for Linux®, UNIX, and Windows.
National Language Feature: See NLF.
New Function Mode: See NFM.
NFM (New Function Mode): An installation mode of QMF Version 8.1 and QMF Version 9.1 that allowed owner and object names in the QMF object catalog to be the maximum length allowed by the database. QMF Version 11 allows owner and object names to be as long as the database allows as well. See also CM.
NLF (National Language Feature): Any of several optional features available with QMF. NLFs allow users to interact with QMF in specific native languages.
object: A named storage space that consists of a set of characteristics that describe the space and, in some cases, data. An object is anything that occupies space in storage, can be located in a library or directory, can be secured, and on which defined operations can be performed. See also QMF object.
outer join: The result of a join operation that includes the matched rows of both tables that are being joined and preserves some or all of the unmatched rows of the tables that are being joined. See also inner join.
package: A control-structure database object produced during program preparation that can contain both executable forms of static SQL statements or XQuery expressions and placement holders for executable forms of dynamic SQL statements.
panel: A formatted display of information on a screen that can also include entry fields.
parameter: A value or reference passed to a function, command, or program that serves as input or controls actions. The value is supplied by a user or by another program or process.
partition: A portion of a page set. Each partition corresponds to a single, independently extendable data set. Partitions can be extended to a maximum size of 1, 2, or 4 gigabytes, depending on the number of partitions in the partitioned page set. All partitions of a given page set have the same maximum size.
plan: See application plan.
positional parameter: A parameter that must appear in a specified location, relative to other parameters. See also keyword parameter.
precision: An attribute of a number that describes the total number of significant digits.
predicate: An element of a search condition that expresses or implies a comparison operation.
primary authorization ID: The authorization identifier used to identify an application process to DB2 for z/OS.
primary key: In a relational database, a key that uniquely identifies one row of a database table.
privilege: In SQL, a capability given to a user by the processing of a GRANT statement.
procedure: A sequenced set of statements or commands used to perform one or more tasks. See also linear procedure and procedure with logic.
procedure with logic: A set of statements that performs one or more tasks. A procedure with logic begins with a REXX comment and allows conditional logic (which uses REXX), calculations, build strings, and TSO or CICS commands. See also linear procedure.
profile: An object that contains information about the characteristics of the user's session.
program temporary fix: See PTF.
prompted query: A menu-driven query controlled by user-provided parameters.
PTF (program temporary fix): For System i®,System p, and System z®, products, a fix that is tested by IBM and is made available to all customers.
QBE (Query-by-Example): A component of QMF that allows users to create queries graphically.
QMF administrator authority: Authority that allows a user to insert or delete rows in the Q.PROFILES control table. Users with this authority can perform the following commands on QMF queries, forms, and procedures that are owned by other users without forcing the owners to share these objects with all users: SAVE, ERASE, IMPORT, EXPORT, and DISPLAY. QMF checks each user ID for administrator authority during initialization; you can disable this checking by setting the DSQEC_DISABLEADM variable in the DSQUOPTS exit routine or in another program of your choice.
QMF administrator: A user who has QMF administrator authority.
Query-by-Example: See QBE.
QMF object: An object used by QMF users to query, format, and present data or otherwise manage interaction between QMF and the database. QMF objects include queries and query result data, forms, procedures, reports, charts, and the QMF profile. Each QMF object has a named temporary storage area that is used to display the object. All objects except reports and charts can be saved in the database; reports and charts are created dynamically upon user request by applying the formatting specifications of a particular QMF form to result data that has been returned from the database. See also temporary storage.
QMF object catalog: A set of control tables that stores information about QMF queries, procedures, and forms. These control tables include Q.OBJECT_DIRECTORY, Q.OBJECT_DATA, and Q.OBJECT_REMARKS.
qualifier: When referring to a QMF object, the part of the name that identifies the owner or the location of an object. When referring to a TSO data set, any part of the name that is separated from the rest of the name by periods. For example, ‘TCK’, ‘XYZ’, and ‘QUERY’ are all qualifiers in the data set name ‘TCK.XYZ.QUERY’.
query: A request for information from a database based on specific conditions: for example, a request for a list of all customers in a customer table whose balances are greater than $1000. In QMF, a query also refers to SQL statements submitted from the Prompted Query, QBE, or SQL query panel, even if these statements are not requests for information (SELECT statements).
RCT (resource control table): A DB2 control table that defines the relationship between CICS transactions and DB2 resources.
RDBMS (relational database management system): A collection of hardware and software that organizes and provides access to a relational database.
RDO (resource definition online): 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.
record: The storage representation of a row or other data.
record length: The length of storage that represents a row or other data.
reentrant: Executable code that can reside in storage as one shared copy for all database threads. Reentrant code is not self-modifying and provides separate storage areas for each thread.
referential constraint: 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.
relational database: 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.
relational database management system: See RDBMS.
remote: Pertaining to databases, objects, or applications that are installed or stored on a system other than the system where QMF is currently executing. You can access objects (including QMF queries, forms, and procedures) at a remote server by using the QMF CONNECT command. You can also use a QMF command with a three-part table or view name if you want to access just tables or views at a remote location. Remote access is not permitted when QMF for TSO is running as a Db2 for z/OS stored procedure.
remote unit of work: A form of distributed relational database processing in which an application program, such as QMF, can access data on a remote database within a unit of work. The connection is established by the QMF CONNECT command. The CONNECT command cannot be used when QMF for TSO is running as a Db2 for z/OS stored procedure.
requester: See application requester.
resource: The object of a lock or claim, which could be a table space, an index space, a data partition, an index partition, or a logical partition.
resource control table: See RCT.
resource definition online: See RDO.
Restructured Extended Executor: See REXX.
REXX (Restructured Extended Executor): A general-purpose, high-level programming language, particularly suitable for EXEC procedures or programs for personal computing.
roll back: To restore data that is changed by an SQL statement to the state at its last commit point. Changes made by all SQL statements in a multistatement query, except those that affect the QMF session (such as SET), are rolled back in the event of a failure.
routine: A program or sequence of instructions called by a program. Typically, a routine has a general purpose and is frequently used.
row: The horizontal component of a table, consisting of a sequence of values, one for each column of the table.
runtime variable: A variable in a procedure or query whose value is specified by the user when the procedure or query is run. The value of a runtime variable is only available in the current procedure or query. See also global variable.
SBCS (single-byte character set): A coded character set in which each character is represented by a 1-byte code. A 1-byte code point allows representation of up to 256 characters. See also double-byte character set.
scalar function: An SQL function that optionally accepts arguments and that returns a single scalar value each time that it is invoked. A scalar function can be referenced in an SQL statement wherever an expression is valid.
scratchpad area: A work area used in conversational processing to retain information from an application program across executions of the program.
search condition: A criterion for selecting rows from a table. A search condition consists of one or more predicates.
secondary authorization ID: In DB2 for z/OS, an authorization identifier that is associated with a primary authorization ID by an authorization exit routine. See also primary authorization ID.
segmented table space: A table space that is divided into equal-sized groups of pages called segments. Segments are assigned to tables so that rows of different tables are never stored in the same segment. See also table space.
server: See application server.
session: All interactions between the user and QMF from the time the user invokes QMF until the EXIT command is issued.
shift-in character: A control character (X'0F') that is used in EBCDIC systems to denote that the subsequent bytes represent SBCS characters. See also shift-out character.
shift-out character: A control character (X'0E') that is used in EBCDIC systems to denote that the subsequent bytes, up to the next shift-in control character, represent DBCS characters. See also shift-in character.
single-byte character set: See SBCS.
single-precision floating-point number: A 32-bit approximate representation of a real number.
SQL (Structured Query Language): A standardized language for defining and manipulating data in a relational database.
SQL authorization ID: See SQLID.
SQL connection: An association between an application process and a local or remote application server or database server. See also remote unit of work, distributed unit of work.
SQL function: A function that is implemented entirely by using a subset of SQL statements and SQL PL statements.
SQL ID (SQL authorization ID): In DB2 for z/OS, the ID that is used for checking the authorization of dynamic SQL statements in some situations.
SQL return code: The SQLSTATE or SQLCODE that indicates whether the previously run SQL statement completed successfully, with one or more warnings, or with an error.
SQLCA (Structured Query Language Communication Area): A set of variables that provides an application program with information about the execution of its SQL statements or requests from the database manager. When an error is associated with an SQL code, the QMF message help (available by pressing the Help key) displays the contents of the SQLCA.
stored procedure: A routine that can be invoked using the SQL CALL statement to perform operations that can include both host language statements and SQL statements.
stored procedure interface: An interface to QMF for TSO that allows you to start QMF as a Db2 for z/OS stored procedure, pass the name of a QMF query or procedure that performs the work you require, and receive up to 21 result sets back, including a result set for trace output. QMF for TSO can be started in this manner from any product that can run a Db2 for z/OS stored procedure.
Structured Query Language: See SQL.
Structured Query Language Communication Area: See SQLCA.
subquery: A complete SQL query that appears in a WHERE or HAVING clause of another query.
substitution variable: (1) A variable in a procedure or query whose value is specified either by a global variable or by a runtime variable. (2) A variable in a QMF form whose value is specified by a global variable.
substring: A part of a character string.
subsystem: In DB2 for z/OS, a distinct instance of a relational database management system (RDBMS).
table: In a relational database, a database object that consists of a specific number of columns and is used to store an unordered set of rows. See also base table.
table space: A logical unit of storage in a database. In DB2 for z/OS, a table space is a page set and can contain one or more tables. In Db2 for Linux, UNIX, and Windows, a table space is a collection of containers, and the data, index, long field, and LOB portions of a table can be stored in the same table space or in separate table spaces.
temporary storage: An area used to store a QMF object temporarily while the user is working on it so that, with each use, it can be readily accessed without further database retrieval. There are seven temporary storage areas: QUERY, DATA, FORM, PROC, REPORT, CHART, or PROFILE. With the exception of query result data (the DATA object), the QMF objects in these areas can be displayed using the SHOW command followed by the name of the storage area. Though the contents of the DATA area cannot be directly displayed, users can issue the SHOW REPORT or SHOW CHART commands to see the query result data formatted with the specifications of the form currently in the FORM area. See also QMF object, current object.
temporary storage queue: In CICS, a queue of data items which can be read and reread, in any sequence. The queue is created by a task, and persists until the same task or a another task deletes it. See also transient data queue.
thread: The DB2 structure that describes an application's connection, traces its progress, processes resource functions, and delimits its accessibility to DB2 resources and services. Most DB2 functions execute under a thread structure.
three-part name: The full name of a table, view, or alias that consists of a location name, an authorization identifier, and an object name, separated by periods. QMF commands that include three-part names can be initiated only from Db2 for z/OS databases and can be directed to all databases except DB2 for VM or VSE. When QMF for TSO has been started as a Db2 for z/OS stored procedure, QMF commands with three-part names are not supported.
Time Sharing Option: See TSO.
trace: A record of the processing of a computer program or transaction. The information collected from a trace can be used to assess problems and performance.
transaction: A unit of processing consisting of one or more application programs, affecting one or more objects, that is initiated by a single request.
transient data queue: A CICS storage area where objects are stored for subsequent internal or external processing. See also temporary storage queue.
trigger: A database object that is associated with a single base table or view and that defines a rule. The rule consists of a set of SQL statements that runs when an insert, update, or delete database operation occurs on the associated base table or view.
TSO (Time Sharing Option): A base element of the z/OS operating system that allows users to work interactively with the system.
two-phase commit: A two-step process by which recoverable resources in an external subsystem are committed. During the first step, the database manager subsystems are polled to ensure that they are ready to commit. If all subsystems respond positively, the database manager instructs them to commit.
UDF (user-defined function): A function that is defined to the DB2 database system by using the CREATE FUNCTION statement and that can be referenced thereafter in SQL statements. A UDF can be an external function or an SQL function.
Unicode: A character encoding standard that supports the interchange, processing, and display of text that is written in the common languages around the world, plus some classical and historical texts. The Unicode standard has a 16-bit character set defined by ISO 10646.
unit of work: A recoverable sequence of operations within an application process. At any time, an application process is a single UOW, but the life of an application process can involve many UOWs as a result of commit or rollback operations. In a multisite update operation, a single UOW can include several units of recovery. In QMF SQL queries that include multiple statements, all statements comprise a single unit of work, so all statements except those that affect the session (such as SET) are rolled back in the event of a failure.
user-defined function: See UDF.
view: A logical table that is based on data stored in an underlying set of tables. The data returned by a view is determined by a SELECT statement that is run on the underlying tables.
XML (Extensible Markup Language): A standard metalanguage for defining markup languages that is based on Standard Generalized Markup Language (SGML).
z/OS: An IBM mainframe operating system that uses 64-bit real storage.