OSI/FTAM Programming Reference Manual

Glossary
HP NonStop OSI/FTAM Programming Reference Manual—528611-001
Glossary-22
read functional unit.
read functional unit. A functional unit that allows the following activities on an association:
•
Establishing the file-open regime
•
Transferring data from the responder to the initiator
•
Releasing the file-open regime
receiver. The entity that receives a communication from a remote sender.
recovery functional unit. An ISO FTAM functional unit that allows the initiator process to
recreate a previously destroyed regime.
regime. A protocol state that reflects the programming status in an FTAM program
sequence. NonStop FTAM and ISO FTAM have four regimes: FTAM regime,
file-selection regime, file-open regime, and data-transfer regime.
register request. (1) For NonStop FTAM, a request made by the FTAM API to the APLMGR
process, on behalf of an application, to establish an FTAM association. Processing an
FTAM register request includes selecting an available initiator process to service the
association. (2) For NonStop OSI/AS, a request made by the API to the OSI manager
process, on behalf of an application, either to establish an association (or connection)
or to wait for an incoming association (or connection).
relaxation. The process of deriving one document from another by making the parameters
describing it less restrictive. In particular, the legal modification of values for the
maximum-string-length, string-significance, or universal-class
parameters for a specific FTAM document type. String-length relaxation allows a
document of with a given maximum-string-length value to be opened and read using a
larger maximum-string-length value or no maximum-string-length value (unbounded
string). Character-set relaxation allows a document of a given universal-class number
to be opened and read using a different universal-class number as long as the new
universal-class number permits all characters from the original universal-class number.
request primitive. A primitive issued when a service user (entity) wants the service to do
some work. This is one of four types of service primitives. See service primitive.
request procedure. A procedure called to cause the initiating process to send a request
primitive to a responding process. See request primitive.
required parameter. (1) In a PDU, a parameter that is always present. (2) In a NonStop
programmatic or interactive interface, a parameter to a procedure (for example, a
procedure in the FTAM API) or to an interactive command (such as an SCF command)
that must be specified when the procedure is called or the command is issued.
Contrast with conditional parameter and optional parameter.
reset time. In SCF, the date and time that the statistical counters for an object were last
reset. The STATS command for the object displays the reset time.