OSI/FTAM Programming Reference Manual

Glossary
HP NonStop OSI/FTAM Programming Reference Manual—528611-001
Glossary-5
confirm procedure.
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.
conformance. The satisfaction, by an implementation of an OSI standard, of both static and
dynamic conformance requirements, consistent with the capabilities stated in the
protocol implementation conformance statement (PICS). Static conformance
requirements are constraints specified in the standards or related profiles to facilitate
interworking. Dynamic conformance requirements determine what observable behavior
is permitted by the standards or profiles in instances of communication. The PICS is a
statement, made by the supplier of an OSI implementation, describing the capabilities
and options that have been implemented for a given OSI protocol. See also profile.
connection. A link between a service access point (SAP) on one protocol stack and a
corresponding point on a different protocol stack (either in the same system or in
another local or remote system). See also association.
connection endpoint identifier. See CEPI (connection endpoint identifier).
constraint set. A specification placing restrictions and refinements on the FTAM general file
model. These restrictions and refinements define a more specific model that reflects
the needs of a particular class of applications.
contents-type attribute. A file attribute that indicates either the document type of a file or
its abstract syntax name and constraint-set name. The value of this attribute is set at
file creation and cannot be changed by the change-attribute action. See also contents-
type parameter.
contents-type parameter. A parameter that indicates the document type of a file and,
optionally, parameter values that further define the document type. The contents-
type must either match the document type of the file being opened or be an allowed
simplification of the document type. If you are using the NonStop FTAM initiator, and
you do not specify contents-type in a call to FTM_OPEN_REQ_, it will default to
indicate that the contents type is unknown. You can then retrieve the valid file
contents-type by calling FTM_OPEN_CNF_, which returns information from the
confirm received from the responder. This parameter must also be specified in calls to
FTM_CREATE_REQ_. Document types supported by NonStop FTAM are FTAM-1,
FTAM-2, FTAM-3, and NBS-9. See document type.
contents-type-list parameter. A parameter used for negotiating the document types and
abstract syntaxes that will be available on the association. For NonStop FTAM, the
default document types requested are FTAM-1, FTAM-2, FTAM-3, and NBS-9.
Data Definition Language. See DDL (Data Definition Language).