TMF Glossary (G06.26+)

TMF Glossary
HP NonStop TMF Glossary—522415-003
Glossary-5
cluster
cluster. (1) A collection of servers, or nodes, that can function either independently or
collectively as a processing unit. (2) A term used to describe a system in a FOX ring.
More specifically, a FOX cluster is a collection of processors and I/O devices
functioning as a logical group. In FOX nomenclature, the term is synonymous with
"system" or "node."
COBOL85. The compiler and run-time support for the American National Standards Institute
(ANSI) programming language COBOL, X.3.23-1985. Pathway server processes are
often written in this language.
command file. See OBEY command file.
commit record. A record in a master audit trail, identifying a committed transaction.
concurrency. A condition in which two or more transactions act upon the same record in
the database at the same time. To process a transaction correctly, an application
program must assume its input from the database is consistent, regardless of any
concurrent changes being made to the database. TMF manages concurrent
transactions through concurrency control.
concurrency control. A TMF feature that ensures all changes made to a database are not
available to other transactions until the changes are either committed or undone.
condition codes (CCL, CCG, and CCE). A mechanism within the NonStop system that
indicates, upon completion of each system procedure call, whether the call was
completed successfully:
configuration subvolume. The subvolume (named ZTMFCONF) that contains TMF
configuration information and the TMF catalog files. By default, ZTMFCONF resides on
$SYSTEM. You can, however, specify a configuration volume other than $SYSTEM by
issuing a TMFCOM ALTER TMF, CONFIGVOL command while TMF is stopped.
consistency. The state of a database in which items satisfy established criteria. For
example, if an amount of money is transferred from one account to another, the
database is not consistent until both the source account has been debited and the
destination account credited. In general, a database is consistent when it is accurate
and all changes generated by transactions are complete. Database consistency is
defined by the application, which establishes the values and relationships of database
fields and records.
context. Information required by a server to process the current request in an exchange of
multiple request and reply messages: for example, identification of the last item
processed. See also context-free server.
CCL or < An error occurred.
CCE or = No error occurred.
CCG or > An illogical condition exists.