Guardian Application Conversion Guide

Glossary
096047 Tandem Computers Incorporated Glossary–7
NonStop Cyclone/R, NonStop CLX 2000, and NonStop CLX/R 1200 systems.
Contrast with “Tandem NonStop Series (TNS).”
TNS. See “Tandem NonStop Series (TNS).”
TNS instructions. Stack-oriented, 16-bit machine instructions defined as part of the TNS
environment. On TNS systems, TNS instructions are implemented by microcode; on
TNS/R systems, TNS instructions are implemented by millicode routines or by
translation to an equivalent sequence of RISC instructions. Contrast with “RISC
instructions.”
TNS object file. The object file created by a TNS compiler. The file contains TNS
instructions and other information needed to construct the code spaces and the initial
data for a TNS process.
TNS/R. See “Tandem NonStop Series/RISC (TNS/R).”
token. In SPI, a distinguishable unit of data in an SPI message. A token has two parts:
an identifying code (a token code or token map) and a token value.
unconverted application. In the context of operating system releases, an application that
has not been modified to use extended features of the D-series operating system.
unnamed process. A process to which a name was not assigned when the process was
created. Contrast with “named process.”
user process. A process whose primary purpose is to solve a user’s immediate
problem. A user process is not essential to the availability of a processor module. A
user process is created only when the user explicitly creates it. Contrast with “system
process.”
ZSYSDDL file. A file provided by Tandem that contains DDL definitions of source
declarations for Guardian system procedures and system messages. ZSYSDDL is
used to generate the ZSYSTAL, ZSYSCOB, ZSYSC, and ZSYSPAS files for use with
TAL, COBOL85, C, and Pascal applications, respectively.
$RECEIVE. A special file name through which a process receives and optionally replies
to messages from other processes.