NonStop JMS C++ API Programmer's Guide

Glossary
NonStop Server for Java Message Service C++ API Programmer’s Guide—526459-002
Glossary-3
queue
queue. A destination for a message in a PTP messaging system.
scalability. The ability to increase the size and processing power of an online transaction
processing system by adding processors and devices to a system, systems to a
network, and so on, and to do so easily and transparently without bringing systems
down. Sometimes called expandability.
session. A context for JMS clients to send and receive messages.
shell. The command interpreter used to pass commands to an operating system; the part of
the operating system that is an interface to the outside world.
TACL. See HP Tandem Advanced Command Language (TACL).
throw. C++ keyword used to raise an exception.
TMF. See Transaction Management Facility (TMF).
TNS. Denotes fault-tolerant HP computers that:

Support the operating system

Are based on microcoded complex instruction-set computing (CISC) technology.
TNS systems run the TNS instruction set. Contrast with TNS/R and TNS/E.
TNS/E. Denotes fault-tolerant HP computers that support the operating system and that are
based on the Intel Itanium processor-based architecture. TNS/E systems run the
Itanium instruction set and can run TNS object files by interpretation or after
acceleration. TNS/E systems include all HP systems that use NSAL-x processors.
Contrast with TNS and TNS/R.
TNS/R. Denotes fault-tolerant HP computers that:

Support the operating system

Are based on 32-bit reduced instruction-set computing (RISC) technology.
TNS/R systems run the MIPS-1 RISC instruction set and can run TNS object files by
interpretation or after acceleration. TNS/R systems include all HP systems that use
NSR-x processors. Contrast with TNS
and TNS/E.
topic. A destination for a message in a Pub/Sub messaging system.
transaction. A series of operations grouped together into a single unit of work.
Transaction Management Facility (TMF). A set of HP software products that assures
database integrity by preventing incomplete updates to a database. It can continuously
save the changes that are made to a database (in real time) and back out these
changes when necessary. It can also take online “snapshot” backups of the database
and restore the database from these backups.