OSI/FTAM Programming Guide

Glossary
HP NonStop OSI/FTAM Programming Guide—528612-001
Glossary-6
DDL (Data Definition Language).
DDL (Data Definition Language). A NonStop language for defining data. DDL builds a
dictionary from the definitions, translates the definitions into File Utility Program (FUP)
commands, and generates object-definition source code in a variety of programming
languages.
default user (DEFUSER). An attribute of a NonStop virtual filestore (VFS) profile that allows
access to files in the NonStop responder’s VFS in cases where the initiator identity and
filestore password are not provided when an association is established. The default
user specifies the default Guardian user ID and password to be used.
diagnostic parameter. An optional parameter providing information that qualifies the
success or explains the failure of a requested FTM procedure call. For
applications using the FTAM API, this parameter primarily returns whatever
diagnostic messages have been received from the remote responder or the local
initiator. In addition, you can use this parameter to send diagnostic messages to a
remote responder using the FTM_CANCEL_REQ_, FTM_DATA_END_REQ_, and
FTM_U_ABORT_REQ_ procedures. See also ISO FTAM diagnostic messages.
Distributed Systems Management. See DSM (Distributed Systems Management).
document type. An FTAM definition, defining the structure of and method of access to a
file. NonStop FTAM supports four document types: FTAM-1, FTAM-2, FTAM-3, and
NBS-9. An FTAM-1 document is an unstructured text file that cannot be broken into
smaller segments by the protocol. An FTAM-2 document is a structured text file divided
into FADUs, which cannot be broken down. An FTAM-3 document is an unstructured
binary file. An NBS-9 document is a read-only directory as defined by the NIST FTAM
Phase 2 agreements.
DSM (Distributed Systems Management). A set of tools provided by HP to manage
NonStop systems, Expand networks, and NonStop communications products. These
tools include the ViewPoint console application, the Subsystem Control Facility (SCF)
for data communications subsystems, the Subsystem Programmatic Interface (SPI),
the Event Management Service (EMS), the PTrace (print trace) utility, token-oriented
programmatic interfaces to the management processes for various NonStop
subsystems, and other products.
EMS (Event Management Service). A facility provided by NonStop for event collection,
event logging, and event distribution on NonStop systems. It includes different forms of
event description for interactive and programmatic interfaces, lets an operator or
application select specific event-message data, and allows for flexible distribution of
event messages within a system or network. The FTAM and APLMGR subsystems
generate event messages that are displayed as operator messages; however, the
programmatic interface to FTAM and APLMGR event messages is not available for
customer use. See also event message.
EMS collector. A NonStop process that accumulates event messages sent from OSI
subsystem processes. See event message.