Summary of the content on the page No. 1
OSI/FTAM Responder
Manual
Abstract
This manual describes the operation of the Compaq Open Systems Interconnection/File
Transfer, Access and Management (OSI/FTAM) responder and its virtual filestore (VFS). It is
for programmers and users who are working with or writing remote FTAM applications that use
the services of the Compaq responder. It is also useful to those with access to the Compaq
system who are diagnosing and solving problems involving the Compaq FTAM responder.
Product Version
Summary of the content on the page No. 2
Document History Part Number Product Version Published 030246 OSI/FTAM C30, August 1992 OSI/APLMGR C30 098329 OSI/FTAM D20, September 1993 OSI/APLMGR D20 425199-001 OSI/FTAM D43 February 2000 OSI/APLMGR D43 Ordering Information For manual ordering information: domestic U.S. customers, call 1-800-243-6886; international customers, contact your local sales representative. Document Disclaimer Information contained in a manual is subject to change without notice. Please check with your authorize
Summary of the content on the page No. 3
OSI/FTAM Responder Manual Glossary Index Figures Tables What’s New in This Manual v Manual Information v New and Changed Information v About This Manual vii Supported Standards viii Related Manuals ix Your Comments Invited x Notation Conventions xi 1. Introduction to the Compaq FTAM Responder Functional Overview 1-1 Compaq FTAM Services 1-2 FTAM Applications 1-2 Management Interfaces 1-4 Architectural Overview 1-4 The Responder and Underlying Subsystems 1-4 The Responder and the File System 1-7
Summary of the content on the page No. 4
Contents 3. Compaq FTAM Responder Operation 3. Compaq FTAM Responder Operation Responder Structure 3-1 Responder Data Flow 3-2 4. Compaq FTAM Responder Support of ISO FTAM Functions Supported Functions 4-1 Service Classes 4-1 Functional Units 4-2 Attribute Groups 4-2 Attribute Support 4-2 Document Types 4-4 Mapping Between FTAM Contents Types and Compaq File Structures 4-5 Create Mappings 4-5 Select-Open Mappings 4-7 Maximum-String-Length Checking of Data Values 4-10 Limits on Small String-Lengt
Summary of the content on the page No. 5
Contents 6. Responder Manager 6. Responder Manager Notes on Configuration 6-1 OSI Address of Responder 6-1 Initiator-Identity and Filestore-Password Parameters 6-2 Protocol-Error Counter 6-2 Increasing Responder Capacity 6-2 Increasing Responder Performance 6-2 Fault Tolerance 6-2 Event Messages 6-3 A. Compaq FTAM Responder Diagnostic Messages General FTAM Diagnostic Messages A-2 Protocol and Supporting Service-Related Diagnostic Messages A-4 Association-Related Diagnostic Messages A-7 Selection
Summary of the content on the page No. 6
Contents Tables (continued) Tables (continued) Table 4-7. Select-Open Mappings: Compaq File Structure to FTAM Contents Type 4-8 Table 4-8. Actions Permitted for FTAM Document Type 4-12 Table 4-9. Simplification of Document Types Supported by the Compaq FTAM Responder 4-13 Table 4-10. Bit String for NBS-9 File Attributes 4-14 Table 4-11. FTAM Storage Attributes and Corresponding Compaq File Attributes 4-16 Table 4-12. Security Attributes Supported by the Compaq FTAM Responder 4-17 Table 4-13.
Summary of the content on the page No. 7
What’s New in This Manual Manual Information Abstract This manual describes the operation of the Compaq Open Systems Interconnection/File Transfer, Access and Management (OSI/FTAM) responder and its virtual filestore (VFS). It is for programmers and users who are working with or writing remote FTAM applications that use the services of the Compaq responder. It is also useful to those with access to the Compaq system who are diagnosing and solving problems involving the Compaq FTAM respond
Summary of the content on the page No. 8
What’s New in This Manual New and Changed Information OSI/FTAM Responder Manual—425199-001 vi
Summary of the content on the page No. 9
About This Manual The OSI/FTAM Responder Manual provides instructions and reference information needed to write application programs, or to use interactive applications, that use the services of the Compaq OSI/File Transfer, Access and Management (FTAM) responder process. This manual has the following objectives: Introduce the Compaq FTAM responder and how it fits into the Compaq FTAM • architecture Describe conformance and interoperability issues for the Compaq FTAM responder • Provide inf
Summary of the content on the page No. 10
About This Manual Supported Standards Supported Standards This manual and the other Compaq FTAM manuals are written on the assumption that you are familiar with the ISO standards and the National Institute of Standards and Technology (NIST) FTAM Phase 2 agreements to which Compaq FTAM and the underlying Compaq OSI products conform. These standards include the following: Standard Number Standard Name ISO 8326 Basic Connection Oriented Session Service Definition ISO 8327 Basic Connection Orien
Summary of the content on the page No. 11
About This Manual Related Manuals Related Manuals This manual is one in a set of Compaq FTAM manuals. OSI/FTAM Programming Guide. This manual explains important programming • concepts pertaining to the Compaq FTAM application programmatic interface and describes sequences of procedure calls to use to perform common FTAM programming operations. This manual also provides an overview of FTAM concepts for those who have not recently read the ISO 8571 specification. OSI/FTAM Programming Refer
Summary of the content on the page No. 12
About This Manual Your Comments Invited If you are diagnosing and solving FTAM problems using tools on the Compaq system where your responder resides, you also need to refer to the following manuals: the OSI/FTAM Configuration and Management Manual and the SCF Reference Manual for FTAM and APLMGR. If you need to understand the meaning of event messages and additional information on displaying trace records for problem diagnosis, you need to refer to the following manuals: PTrace Reference
Summary of the content on the page No. 13
About This Manual Notation Conventions Notation Conventions General Syntax Notation The following list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words; enter these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH lowercase italic letters. Lowercase italic letters indicate variable items that you supply. Items not enclosed in brackets are required.
Summary of the content on the page No. 14
About This Manual General Syntax Notation An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times. For example: "s-char..." Punctuation. Parentheses, commas, semicolons, and other symbols not previously described must be entered as shown. For example: error := NEXTFILENAME ( file-name ) ; LISTOPENS SU $process-name.#su-name Quotation marks around a symbol such as a bracket or brace indicate the symbol is a required character
Summary of the content on the page No. 15
About This Manual Notation for Messages !o:i. In procedure calls, the !o:i notation follows an output buffer parameter that has a corresponding input parameter specifying the maximum length of the output buffer in bytes. For example: error := FILE_GETINFO_ ( filenum !i , [ filename:maxlen ] ) ; !o:i Notation for Messages The following list summarizes the notation conventions for the presentation of displayed messages in this manual. Bold
Summary of the content on the page No. 16
About This Manual Notation for Management Programming Interfaces either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: obj-type obj-name state changed to state, caused by { Object | Operator | Service } process-name State changed from old-objstate to objstate { Operator Request. } { Unknown. } | Vertical Line. A vertical line separates alternatives in a horizontal list that is enclo
Summary of the content on the page No. 17
1 Introduction to the Compaq FTAM Responder This manual describes the Compaq Open Systems Interconnection/File Transfer, Access and Management (OSI/FTAM) responder and its virtual filestore (VFS). Compaq OSI/FTAM is the Compaq implementation of the FTAM standard ISO 8571, developed by the International Organization for Standardization (ISO). File Transfer, Access and Management (FTAM) is a set of Application Layer services and an Application Layer protocol to support file handling on Open
Summary of the content on the page No. 18
Introduction to the Compaq FTAM Responder Compaq FTAM Services FTAM users communicate with the FTAM service provider by way of primitives, the smallest units of interaction between the FTAM user and the FTAM service provider. An operation like any of those mentioned above requires the exchange of multiple primitives, which the FTAM software encodes as protocol data units (PDUs). FTAM file handling is defined in terms of initiator and responder functions. The initiator provides application p
Summary of the content on the page No. 19
Introduction to the Compaq FTAM Responder FTAM Applications responder, you use the standard FTAM file-handling conventions to perform remote file- handling tasks, by means of the FTAM interface on your remote system. Each FTAM service, or file operation, requires that multiple FTAM protocol operations be performed, in sequence, to complete the service. For example, to open a file, an FTAM application must first send an initialize request, and then a file-select request and a file-open reques
Summary of the content on the page No. 20
Introduction to the Compaq FTAM Responder Management Interfaces Management Interfaces For those people with access to the Compaq system who are responsible for configuring and managing FTAM responder processes and for solving FTAM problems, Compaq FTAM supports the Distributed Systems Management (DSM) management interfaces, which include the following: Subsystem Control Facility (SCF) • PTrace utility • Operator message facility of the Event Management Service (EMS) • The use of these managem
