TS/MP 2.5 Pathsend and Server Programming Manual

Application-Transaction Monitor Interface (ATMI)
The application programming interface to the System/T transaction monitor in a NonStop Tuxedo
system. This interface includes transaction routines, message handling routines, service interface
routines, and buffer-management routines.
assignment The use of an ASSIGN command to make logical file assignments for programs in the Guardian
environment. A logical assignment equates a NonStop system file name with a logical file of a
program and, optionally, attributes characteristics to that file.
associative server A process within a server-class that can be started outside the Pathway environment by a process
other than the PATHMON process that controls the server-class.
ATMI See Application-Transaction Monitor Interface (ATMI).
attributes Those characteristics of an object that influence the operation of that object and establish its
capabilities.
audit trail A record of database changes that can be used by the TMF subsystem to rebuild a database in
the event of a hardware or software failure. An audit trail is also known in the industry as a
transaction log.
audited file A database file that is flagged for auditing by the TMF subsystem; auditing is the monitoring of
transactions in preparation for recovery efforts.
availability The amount of time an application running on a NonStop system can be used effectively by a
user of that application.
backup process The member of a process pair that takes over the application work when the primary process
fails. See also primary process, process pair, and checkpoint message.
base screen In SCREEN COBOL, a screen that occupies the entire physical display area of a terminal and
can be displayed independently of other screens. This type of screen can contain areas on which
overlay screens are displayed. See also screen and overlay screen.
batch processing A method of transaction processing in which transactions are first grouped together and then
processed at regular intervals. See also online transaction processing (OLTP).
block mode A terminal operating mode in which data is read from the terminal and displayed on the terminal
one screen at a time. See also conversational mode.
cache A temporary storage buffer.
cascading server A term formerly used for a nested server. See nested server.
checkpoint
message
In the Guardian environment, a message sent by a primary process to its backup process that
keeps the backup process up to date on the state of the application. A checkpoint message
provides a snapshot of process activity that can be used in the event of a takeover by a backup
process to allow the backup process to maintain fault-tolerant operation.
CISC See complex instruction-set computing (CISC).
client An application program that requests services to be performed. In discussions of the Pathway
environment, this term is used to refer to the part of an application that runs on some other vendor’s
hardware, such as a personal computer, Macintosh computer, UNIX workstation, or mainframe
computer system, and makes requests of a server process. See also requestor, server, and
client/server model.
client/server model A model for distributing applications. In general, but not always, in this model the client process
resides on a workstation and the server process resides on a second workstation, minicomputer,
or mainframe system. Communication takes the form of request and reply pairs, which are initiated
by the client and serviced by the server. (A server can make requests of another server, therefore
acting as a client.) Client/server computing is often used to connect different types of workstations
or personal computers to a host computer system by means of supported communications protocols.
See also requestor/server model.
client/transaction
server model
A model for client/server applications. The client/transaction server model is the model of choice
for high-volume OLTP applications in which transaction volume is great and the processing
requirements change infrequently.
In the NonStop environment, an application following this model divides processing between a
client running on a workstation and servers running on a NonStop system. The client handles the
user interface and business logic and processing. The servers store information for use by the
204 Glossary