OSI/FTAM Programming Guide

Glossary
HP NonStop OSI/FTAM Programming Guide—528612-001
Glossary-4
basic data types.
basic data types. First-level and second-level DDL data types, which can either stand
alone as data types or be used to create higher-level DDL structures.
called address. The OSI address of the responder called by the initiator that supports an
FTAM application. Contrast with calling address and responding address.
calling address. The OSI address of the initiator that calls a responder in an FTAM
application. Contrast with called address and responding address.
calling user. The initiator that calls a responder in an FTAM application. Contrast with
responding user.
CEPI (connection endpoint identifier). An internally generated identification code used to
track associations. In NonStop FTAM, an identifier of a connection endpoint for a given
FTAM association. Use of the CEPI for an association allows transfer of information to
a remote FTAM entity.
checkpoint. On a NonStop system, a snapshot of process activity that can be used in the
event of a takeover to allow a backup process to maintain fault-tolerant operation. See
backup process.
code file. A Guardian file containing the object code that you must run to create the
specified process.
command file. A text file containing a series of commands that you can run by issuing the
OBEY command in TACL or SCF, followed by the name of the text file.
common name. A reference name used to look up an OSI address in the local OSI/AS
management information base (MIB) when establishing an association. Using
common names simplifies addressing for applications and allows you to
subsequently change the addresses without changing your applications. In
OSI/AS terminology, the common name is called the application name.
conditional parameter. (1) In a PDU, a parameter that is present under certain
circumstances, for example, if another parameter has a given value. (2) In the NonStop
FTAM API, a procedure-call parameter that must be specified under certain
circumstances. Contrast with optional parameter and required parameter.
confirm primitive. A primitive issued when a service user (entity) is to be informed about its
request. This is one of four types of service primitives. See service primitive.
confirm procedure. A procedure called to retrieve the confirm data after a confirm primitive
has been received. See confirm primitive.
confirmed service. A service in which the initiating application sends a request, and the
responding application entity (for example, an FTAM responder) returns a response
that is received as a confirm primitive by the initiating application. The confirm primitive
acknowledges the success or failure of the requested action. Contrast with
unconfirmed service.