Compaq OSI-APLMGR D43, OSI-FTAM D43 User Manual

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

OSI/FTAM D43 OSI/APLMGR D43

Supported Releases

D48 and above G06.01 and above

Part Number Published

425199-001 February 2000

Document History

Part Number Product Version Published 030246 OSI/FTAM C30,

OSI/APLMGR C30

098329 OSI/FTAM D20,

OSI/APLMGR D20

425199-001 OSI/FTAM D43

OSI/APLMGR D43

Ordering Information

For manual ordering information: domestic U.S. customers, call 1-800-243-6886; international customers, contact your lo ca l s a les repr e s en t a t i ve .

Document Disclaimer

Information contained in a manual is subject to change without notice. Please check with your authorized representative to make sure you have the most recent information.

Export Statement

Export of the information contained in this manual may require authorization from the U.S. Department of Commerce.

Examples

Examples and sample programs are for illustration only and may not be suited f or your particular purpo se . T he inclusion of examples and sample programs in the documentation does not warrant, guarante e, or make any representat ions regarding the use or the results of the use of any examples or sample programs in any documentation. You should veri fy the applicability of any example or sample program before placing the software into productive use.

U.S. Government Customers

FOR U.S. GOVERNMENT CUSTOMERS REGARDING THIS DOCUMENTATION AND THE ASSOCIATED SOFTWARE :

These notic es shall be marked on any reproduction of this data, in whol e or in part. NOTICE: Notwithstanding any other lease or licens e tha t m ay pertain to, or accompan y the de livery of, this

computer softwa re, the rights of the Government regarding its use, repr oduction and disclosure are as set forth in Section 52.227-19 of the FARS Computer Software—Restricted Rights clause.

RESTRICTED RIGHTS NOTICE: Use, duplication, or disclosure by the Government is subject to the restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 52.227-7013.

RESTRICTED RIGHTS LEGEND: Use, duplication or disclosure by the Government is subject to restric tions as set forth in paragraph (b)(3)(B) of the rights in Technical Data and Computer Software clause in DAR 7-104.9(a). This computer software is submitted with “restricted rights.” Use, duplication or disc losure is subject to the restrictions as set forth in NASA FAR SUP 18-52 227-79 (April 1985) “Commercial Computer Software—Restricted Rights (April 1985).” If the contract contai ns the Clause at 18-52 227-74 “Rights in Data Gener al ” th en th e “A l t er n at e I II” cla u s e ap p li e s.

U.S. Government Users Restricted Rights — Use, dupl ication or disclosure restricted by GSA ADP Schedule Contract.

August 1992

September 1993

February 2000

OSI/FTAM Responder Manual

Glossary Index Figures Tables

What’s New in This Manual v

Manual Information New and Changed Information

About This Manual

Supported Standards Related Manuals Your Comments Invited Notation Conventions

vii

viii

1. Introduc tion to the Compaq FTAM Resp onde r

Functional Overview 1-1

Compaq FT AM Services FTAM Applications Management Interfaces

Architectural Overview

The Responder and Underlying Subsystems

1-2

1-4

The Responder and the File System

2. Conformance and Interoperatility

Conformance 2-1 Interoperability

Basic Characteristics of FTAM Implementations Limitations on Value of Future-Filesize Attribute Document T ypes and Related Parameters Data-Transfer Considerations Presentation Encoding of FTAM PDUs and Data

2-1

2-4

Compaq Computer Corporation—425199-001

1-7

2-2

2-3

2-6

Contents

3. Compaq FTAM Responder O p er ati on

Responder Structure 3-1

3. Compaq FTAM Responder Operation

Responder Data Flow

3-2

4. Compaq F TAM Re sponde r Support of ISO FTAM Functions

Supported Functions 4-1

Service Classes Functional Units Attribute Groups Attribute Support Document T ypes

Mapping Between FTAM Contents Types and Compaq File Structures

Create Mappings Select-Open Mappings Maximum-String-Length Checking of Data Values Limits on Small String-Length Values With Large PDUs

File-Attribute Mappings

Kernel Group File Attributes

4-1

4-2

4-4

4-5

4-7

4-10

4-11

Storage Group File Attributes Security Group File Attributes Private Group File Attributes

Supported and Unsupported Optional Parameters File-Access and Security Considerations

4-15

4-17

4-21

4-22

5. Suggestions for Development of Remote Applications

Design and Programming 5-1

Interoperability Error Handling

Troubleshooting

5-1

5-2

OSI/FTAM Responder Manual—425199-001

Contents

6. Responder Mana ger

Notes on Configuration 6-1

6. Responder Man ager

OSI Address of Responder Initiator-Identity and Filestore-Password Parameters Protocol-Error Counter Increasing Responder Capacity Increasing Responder Performance

Fault Tolerance Event Messages

6-2

6-3

6-1

6-2

A. Compaq FTAM Responder Diagnostic Me s sage s

General FTAM Diagnostic Messages A-2 Protocol and Supporting Service-Related Diagnostic Messages Association-Related Diagnostic Messages Selection-Related Diagnostic Messages File-Management-Related Diagnostic Messages Access-Related Diagnostic Messages Recovery-Related Diagnostic Messages

A-7

A-10

A-16

A-17

A-25

A-4

Glossary Index

Figures

Figure 1-1. An FTAM Service Using Four Primitives 1-3 Figure 1-2. Figure 3-1.

Tables

Table 4-1. Service Classes Supported by the Compaq FTAM Responder 4-1 Table 4-2. Table 4-3. Table 4-4. Table 4-5.

Table 4-6.

Compaq FTAM Responder Architectural Overview 1-6 Compaq FTAM Responder Process 3-2

Functional Units Supported by the Compaq FTAM Responder 4-2 Attribute Groups Supported by the Compaq FTAM Responder 4-2 Attributes Supported by the Compaq FTAM Responder 4-3 Document Types and Parameters Supported by the Compaq FTAM

Responder 4-4 Create Mappings: FTAM Contents Type to Compaq File Structure 4-7

OSI/FTAM Responder Manual—425199-001

iii

Contents

Tables (continued)

Table 4-7. Select-Open Mappings: Compaq File Structure to FTAM Contents

Type 4-8

Tables (continued)

Table 4-8. Table 4-9.

Table 4-10. Table 4-11.

Table 4-12. Table 4-13. Table 4-14. Table 4-15.

Table 4-16. Table 4-17. Table A-1. Table A-2. Table A-3.

Actions Permitted for FTAM Document Type 4-12 Simplification of Document Types Supported by the Compaq FTAM

Responder 4-13 Bit String for NBS-9 File Attributes 4-14 FTAM Storage Attributes and Corresponding Compaq File

Attributes 4-16 Security Attributes Supported by the Compaq FTAM Responder 4-17 Mapping From FTAM Action List to Guardian Security 4-19 Mapping From Guardian Security to FTAM Action List 4-21 Compaq Support of Optional Parameters Received

in Request PDUs 4-21 Compaq Support of Optional Parameters Sent in Response PDUs 4-22 Guardian Access Required to Perform FTAM Actions 4-23 Diagnostic Message Types A-1 Sources and Observers of Errors A-2

General FTAM Diagnostic Messages A-2 Table A-4. Table A-5. Table A-6. Table A-7. Table A-8. Table A-9. Table A-10. Table A-11.

Protocol and Supporting Service-Related Diagnostic Messages A-4

Association-Related Diagnostic Messages A-7

Selection-Related Diagnostic Messages A-11

File-Management-Related Diagnostic Message A-16

Access-Related Diagnostic Messages A-18

Access Contexts by Document Typ A-22

FTAM Contents Types and Equivalent Guardian File Structures A-24

Recovery-Related Diagnostic Messages A-25

OSI/FTAM Responder Manual—425199-001

What’s New in This Manual

Manual Information

Abstract

Product Version

OSI/FTAM D43 OSI/APLMGR D43

Supported Releases

D48 and above G06.01 and above

Part Number Published

425199-001 February 2000

Document History

Part Number Product Version Published

030246 OSI/FTAM C30,

OSI/APLMGR C30

098329 OSI/FTAM D20,

OSI/APLMGR D20

425199-001 OSI/FTAM D43

OSI/APLMGR D43

New and Changed Information

This manual has been updated to support the G-series releases.

August 1992

September 1993

February 2000

OSI/FTAM Responder Manual—425199-001

What’s New in This Manual

New and Changed Information

OSI/FTAM Responder Manual—425199-001

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 information about the Compaq FTAM responder needed by the programmer

•

writing FTAM applications (or the user using interactive FTAM applications) on a remote system, which may or may not be a Compaq system

Provide information about the Compaq FTAM responder and its virtual

•

filestore (VFS) needed for problem solving on the Compaq system

The descriptions that follow provide you with an overview of the content of each section and appendix in this manual.

Section 1, “Introduction to Compaq OSI/FTAM,” provides a general introduction to

•

the Compaq FTAM software from the point of view of programmers writing remote FTAM applications that use the services of the Compaq FTAM responder.

Section 2, “Conformance and Interoperability,” presents information about

•

standards conformance and interoperability of the Compaq FTAM responder. Section 3, “Compaq FTAM Responder Operation,” describes the architecture of the

•

Compaq FT AM responder and the way messages flow to and from the responder. Section 4, “Compaq FTAM Responder Support of ISO FTAM Functions,” describes

•

the ISO FTAM functions supported by the Compaq FTAM responder. Section 5, “Suggestions for Development of Remote Applications,” provides

•

suggestions for how to write your remote FTAM applications in order to take best advantage of the features of the Compaq FTAM responder.

Section 6, “Responder Management,” discusses considerations that are related to the

•

configuration and management of the responder process and its VFS on the Compaq system, but that you might need to know when writing or using FTAM applications on the remote system.

Appendix A, “Compaq FTAM Responder Diagnostic Messages,” provides cause,

•

effect, and recovery information for all diagnostic messages that originate in the Compaq FTAM responder or VFS.

OSI/FTAM Responder Manual—425199-001

vii

About This Manual

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 Oriented Session Protocol Specification ISO 8571-1 File Transfer , Access and Management—Part 1: General

Introduction ISO 8571-2 File Transfer , Access and Management—Part 2: Virtual Filestore

Definition ISO 8571-3 File Transfer, Access and Management—Part 3: File Service

Definition

Supported Standards

ISO 8571-4 File Transfer, Access and Management—Part 4: File Protocol Specification

ISO 8571-5 File Transfer , Access and Management—Part 5: Protocol Implementation Conformance Statement

ISO 8649 Service Definition for the Association Control Service Element ISO 8650 Protocol Specification for the Association Control Service Element ISO 8822 Connection Oriented Presentation Service Definition ISO 8823 Connection Oriented Presentation Protocol Specification ISO 8824 Specification of Abstract Syntax Notation One (ASN.1) ISO 8825 Specification of Basic Encoding Rules for Abstract Syntax

Notation One (ASN.1) ISO/IEC ISP 10607 Information Technology—International Standardized Profiles

AFTnn—File Transfer, Access and Management, Parts 1-6 NIST 500-162 Stable Implementation Agreements for Open Systems

Interconnection Protocols (Special Publication), Part 9—FTAM Phase 2

OSI/FTAM Responder Manual—425199-001

viii

About This Manual

Related Manuals

This manual is one in a set of Compaq FTAM manuals.

OSI/FT AM 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/FT AM Programming Reference Manual. This is the companion manual to the

•

Compaq OSI/FTAM Programming Guide and provides reference information on the programmatic interface provided by Compaq FTAM for application programs that run on a Compaq host using the FTAM initiator. It discusses product conformance to standards and interoperability , provides information on the FTAM initiator, and provides reference material for all procedure calls in the FTAM API (application programmatic interface), including descriptions of diagnostic and error messages.

OSI/FT AM Responder Manual. This manual provides information for programmers

•

writing applications on remote systems using the services of the Compaq FTAM responder. This manual discusses the Compaq FTAM responder’s conformance to standards and interoperability, describes the operation of the responder, and provides reference information on diagnostic messages.

Related Manuals

OSI/FT AM Configuration and Management Manual. This manual provides task-

•

oriented information necessary for the installation and management of the Compaq FTAM responder and virtual filestore (VFS) and the associated APLMGR process. This manual also includes information on monitoring and adjusting your subsystem to optimize performance and on diagnosing and fixing problems.

SCF Reference Manual for FTAM and APLMGR. This manual describes the

•

interactive interface that allows operators to manage and monitor the configuration and operation of FTAM responder and APLMGR processes, and to monitor FTAM subdevices, using SCF commands. It also describes the formats of trace records generated by responder and APLMGR processes.

Operator Messages Manual . This manual describes Compaq operator messages in

•

general and describes the operator messages that can be generated by various Compaq subsystems, including their causes, effects, and recovery actions. The “OSI/APLMGR Messages” and “OSI/FTAM Messages” sections describe the operator messages generated by Compaq FT AM.

If you are writing applications using a remote initiator that interoperates with the Compaq FTAM responder, your main source of information is the documentation for the FTAM initiator you are using. If your initiator is running on a system other than a Compaq system, you need whatever documentation is provided for the remote implementation.

If your FT AM initiator is on a Compaq system, you need the following manuals in the Compaq FTAM manual set: the OSI/FTAM Programming Guide and the OSI/FTAM Programming Reference Manual.

OSI/FTAM Responder Manual—425199-001

About This Manual

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:

PT race Reference Manual provides general information on how to select and

•

interpret information in trace files created using the SCF TRACE command. This information serves as background for the trace-record information in the SCF

Reference Manual for FT AM and APLMGR. Operator Messages Manual.

•

If you need to understand how files are stored in the Compaq responder’s VFS or if you are diagnosing problems in the VFS, the following manuals are also likely to be of interest:

Enscribe Programmer’s Guide describes the four types of Enscribe disk files on the

•

Compaq system (unstructured, key-sequenced, entry-sequenced, and relative).

Your Comments Invited

NonStop SQL Installation and Management Manual explains how to install

•

NonStop SQL, the Compaq relational database management system, and how to plan, create, and manage NonStop SQL databases. This manual is useful to you if your applications access SQL tables as FTAM-2 files.

NonStop SQL Messages Manual describes messages produced by the NonStop SQL

•

relational database management system and file-system messages that pertain only to NonStop SQL files. This manual is useful to you if your applications access SQL tables as FT AM-2 files.

Your Comments Invited

After using this manual, please take a moment to send us your comments. You can do this by returning a Reader Comment Card or by sending an Internet mail message.

A Reader Comment Card is located at the back of printed manuals and as a separate file on the User Documentation disc. You can either fax or mail the card to us. The fax number and mailing address are provided on the card.

Also provided on the Reader Comment Card is an Internet mail address. When you send an Internet mail message to us, we immediately acknowledge receipt of your message. A detailed response to your message is sent as soon as possible. Be sure to include your name, company name, address, and phone number in your message. If your comments are specific to a particular manual, also include the part number and title of the manual.

Many of the improvements you see in manuals are a result of suggestions from our customers. Please take this opportunity to help us improve future manuals.

OSI/FTAM Responder Manual—425199-001

About This Manual

Notation Conventions

General Syntax Notatio n

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. For example:

file-name

[ ] Brackets. Brackets enclose optional syntax items. For example:

TERM [\system-name.]$terminal-name INT[ERRUPTS]

A group of items enclosed in brackets is a list from which you can choose one item or none. The items in the list may be arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example:

FC [ num ] [ -num] [ text]

K [ X | D ] address-1

{ } Braces. A group of items enclosed in braces is a list from which you are required to

choose one item. The items in the list may be arranged 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:

LISTOPENS PROCESS { $appl-mgr-name } { $process-name }

ALLOWSU { ON | OFF }

| Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in

brackets or braces. For example:

INSPECT { OFF | ON | SAVEABEND }

… Ellipsis. An ellipsis immediately following a pair of brackets or braces indicates that you

can repeat the enclosed sequence of syntax items any number of times. For example:

M address-1 [ , new-value ]... [ - ] {0|1|2|3|4|5|6|7|8|9}...

OSI/FTAM Responder Manual—425199-001

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 that you must enter as shown. For example:

"[" repetition-constant-list "]"

Item Spacing. Spaces shown between items are required unless one of the items is a

punctuation symbol such as a parenthesis or a comma. For example:

CALL STEPMOM ( process-id ) ;

If there is no space between two items, spaces are not permitted. In the following example, there are no spaces permitted between the period and any other items:

$process-name.#su-name

Line Spacing. If the syntax of a command is too long to fit on a single line, each continuation

line is indented three spaces and is separated from the preceding line by a blank line. This spacing distinguishes items in a continuation line from items in a vertical list of selections. For example:

ALTER [ / OUT file-spec / ] CONTROLLER [ , attribute-spec ]...

!i and !o. In procedure calls, the !i notation follows an input parameter (one that passes data

to the called procedure); the !o notation follows an output parameter (one that returns data to the calling program). For example:

CALL CHECKRESIZESEGMENT ( segment-id !i , error ) ; !o

!i,o. In procedure calls, the !i,o notation follows an input/output parameter (one that both

passes data to the called procedure and returns data to the calling program). For example:

error := COMPRESSEDIT ( filenum ) ; !i,o

!i:i. In procedure calls, the !i:i notation follows an input string parameter that has a

corresponding parameter specifying the length of the string in bytes. For example:

error := FILENAME_COMPARE_ ( filename1:length !i:i , filename2:length ) ; !i:i

OSI/FTAM Responder Manual—425199-001

xii

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

Notat ion for Messages

The following list summarizes the notation conventions for the presentation of displayed messages in this manual.

Bold Text. Bold text in an example indicates user input entered at the terminal. For example:

ENTER RUN CODE ?123 CODE RECEIVED: 123.00

The user must press the Return key after typing the input.

Nonitalic text. Nonitalic letters, numbers, and punctuation indicate text that is displayed or

returned exactly as shown. For example:

Backup Up.

lowercase italic letters. Lowercase italic letters indicate variable items whose values are

displayed or returned. For example:

p-register process-name

[ ] Brackets. Brackets enclose items that are sometimes, but not always, displayed. For

example:

Event number = number [ Subject = first-subject-value ]

A group of items enclosed in brackets is a list of all possible items that can be displayed, of which one or none might actually be displayed. The items in the list might be arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example:

proc-name trapped [ in SQL | in SQL file system ]

{ } Braces. A group of items enclosed in braces is a list of all possible items that can be

displayed, of which one is actually displayed. The items in the list might be arranged

OSI/FTAM Responder Manual—425199-001

xiii

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 enclosed in

brackets or braces. For example:

Transfer status: { OK | Failed }

% Percent Sign. A percent sign precedes a number that is not in decimal notation. The

%þnotation precedes an octal number. The %Bþnotation precedes a binary number. The %Hþnotation precedes a hexadecimal number. For example:

%005400 P=%p-register E=%e-register

Notation for Management Programming Interfaces

The following list summarizes the notation conventions used in the boxed descriptions of programmatic commands, event messages, and error lists in this manual.

UPPERCASE LETTERS. Uppercase letters indicate names from definition files; enter these

names exactly as shown. For example:

ZCOM-TKN-SUBJ-SERV

lowercase letters. Words in lowercase letters are words that are part of the notation,

including Data Definition Language (DDL) keywords. For example:

token-type

!r. The !r notation following a token or field name indicates that the token or field is

required. For example:

ZCOM-TKN-OBJNAME token-type ZSPI-TYP-STRING. !r

!o. The !o notation following a token or field name indicates that the token or field is

optional. For example:

ZSPI-TKN-MANAGER token-type ZSPI-TYP-FNAME32. !o

OSI/FTAM Responder Manual—425199-001

xiv

Introduction to the Compaq FTAM Responder

This manual describes the Compaq Open Systems Interconnection/File Transfer, Access and Management (OSI/FT AM) 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 Systems Interconnection (OSI) networks. Using this standard FTAM protocol across an OSI network, different computer systems can transmit and receive file contents and filemanagement-related messages.

The information in this manual is useful to you if you are doing either of the following:

Developing FT AM applications, or using interactive FTAM applications, that run

•

on remote systems and use the services of the Compaq FTAM responder Solving problems involving a Compaq FTAM responder or its virtual filestore

•

(VFS)

While this manual is designed to be as complete as possible with regard to the Compaq FTAM implementation of the responder, it is not intended to duplicate or replace the ISO standards and National Institute of Science and Technology (NIST) FTAM Phase 2 agreements. The preface to this manual, called “About This Manual,” lists the relevant ISO and NIST documents that you may want to review.

In this manual, ISO FTAM refers to the FTAM specification as defined in ISO 8571, and Compaq FTAM refers to the Compaq OSI/FTAM product.

Functional Overview

ISO FTAM provides the following file-handling functions across the network:

Creating files

•

Deleting files

•

Erasing part or all of the contents of files

•

Reading from files

•

Writing to files

•

Reading file attributes

•

Changing file attributes

•

OSI/FTAM Responder Manual—425199-001

1-1

Introduction to the Compaq F TAM Responder

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 programs with access to the FTAM protocol so that you can request services to be performed by a responder across the network. The remote responder acts as a file server and performs the requested services.

Compaq FTAM Services

Compaq FTAM provides most of the FTAM services specified in ISO 8571. The Compaq FT AM implementation separates the initiator and responder functions into

two processes. The Compaq FTAM initiator process implements the initiator function, while the Compaq FTAM responder process implements the responder function.

Note. The initiator and responder functions of remote FTAM implementations are not necessarily performed by sep arat e processes. In this manual, the term “remote init iato r” refe r s to the entit y in th e remote imp lementation that perfo rms the init iat or function .

Compaq FTAM Service s

The initiator and responder processes provide the FTAM functions required for your applications. These processes manage the FTAM communications among your application and other FT AM applications on the local or remote computer systems on an OSI network.

Compaq FTAM can handle the following types of files, where the corresponding FTAM document types are listed parenthetically:

Unstructured text files (FTAM-1)

•

Structured text files (FTAM-2)

•

Binary files (FTAM-3)

•

Directory files (NBS-9)

•

FTAM Applications

This manual focuses on the FTAM services available to remote ISO FTAM applications through the Compaq FTAM responder. There is no programmatic interface to the Compaq responder; you request the services of the responder by means of the FTAM interface on your remote system, which may or may not be a Compaq system.

ISO FTAM protocol defines a common model of the file system (the virtual filestore, described later in the manual), which allows all computer systems on an open network to share the same file-handling conventions. Because the Compaq FTAM responder manages its own local file system, you do not need to learn how to program file handling for the Compaq NonStop Kernel (the operating system) or the Guardian environment (the application program interface and the Compaq NonStop tools) when using the Compaq responder. In writing FTAM applications that use the services of the

OSI/FTAM Responder Manual—425199-001

1-2

Introduction to the Compaq F TAM Responder

responder, you use the standard FTAM file-handling conventions to perform remote filehandling 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 request, to the responding system in the communication. The responding FTAM node receives the requests as indications and sends responses back to the requesting node. The requesting node receives these responses as confirms. Thus, four primitives—request, indication, response, and confirm—are used to complete most services, as shown in Figure 1-1. Section 4 identifies the FTAM services supported in the Compaq FT AM implementation.

Figure 1-1. An FTAM Service Using Four Primitives

FTAM Applications

Initiating

Process

F-XXX request

F-XXX confirm

Responding

Process

F-XXX indication

F-XXX response

203CDT .CDD

The ISO standard provides flexibility in the level of FTAM function that must be implemented in an ISO-conformant system. This flexibility implies that, as you write and test your application, you need to consider the specifications for the other FT AM implementations with which your application will interoperate. Refer to Section 2 for information about the factors to consider in assessing the interoperability of the Compaq FTAM product with other FTAM implementati ons.

If your remote FTAM application also runs on a Compaq system, you use the Compaq FTAM application program interface (API), a set of procedures that interact with the Compaq FTAM initiator process, to request FTAM services. The initiator, in turn, sends requests for file-handling services to remote responders. The FTAM API is described in detail in the OSI/FTAM Programming Reference Manual and the OSI/FTAM Programming Guide.

OSI/FTAM Responder Manual—425199-001

1-3

Introduction to the Compaq F TAM Responder

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 management utilities with Compaq FTAM is described in the OSI/FTAM Configuration and Management Manual.

In addition, system managers and problem solvers on the Compaq system use the File Utility Program (FUP) to perform many functions on Compaq disk files, including copying and resecuring files. This utility is described in the File Utility Program (FUP) Reference Manual.

Management Interfaces

Architectural Overview

FTAM services facilitate communication between different computer systems in an OSI network. The communication link (at the FTAM level) created between two systems is called an association. Each system is further defined in terms of its function in the association. The system that creates and controls the association is called the initiating system. The system that responds to the initiating system is called the responding system. In Compaq FTAM, the initiating and responding functions are performed by separate processes.

The Compaq FTAM responder process services FTAM requests initiated from remote systems on the network, such as a request to read a file. The responder acts as an FTAM file server, mapping FTAM requests into file operations and providing a translation between Guardian file structures and FTAM file structures.

The Responder and Underlying Subsystems

To communicate over OSI networks, Compaq FTAM uses the services of the Compaq OSI/AS and OSI/TS subsystems, and either the Compaq LAN access method (TLAM) (or PAM for G06 and above releases), or the X.25 access method (X25AM), or TCP/IP. In turn, X25AM and TLAM depend on hardware controllers to provide the 802.3 communications protocol (for TLAM) and the X.25 communications protocol (for X25AM).

Figure 1-2 provides an overview of the Compaq FTAM responder and these underlying Compaq products. The figure illustrates how the Compaq FTAM responder and the underlying Compaq OSI subsystems support the layers of the OSI Reference Model for both LANs and WANs:

The Compaq FTAM responder provides FTAM responder functions at the

•

Application Layer.

OSI/FTAM Responder Manual—425199-001

1-4

Introduction to the Compaq F TAM Responder

Compaq application, presentation, and session service provider (TAPS) processes

•

perform the services of the Association Control Service Element (ACSE) in the Application Layer, plus the services of the Presentation Layer and the Session Layer. TAPS processes are provided by the OSI/AS subsystem.

Transport service provider (TSP) processes perform the services of the Transport

•

Layer. These processes are provided by the OSI/TS subsystem. Network service provider (NSP) processes perform the services of the Network

•

Layer and/or the Data Link Layer. These processes are provided by the X25AM and TLAM (or P AM for G06 and above releases) and TCP/IP subsystems.

The figure also shows the hardware used to implement Data Link Layer and Physical Layer OSI communications through TLAM (or P AM) or X25AM.

The Responder and Underlying Subsystems

OSI/FTAM Responder Manual—425199-001

1-5

Introduction to the Compaq F TAM Responder

Figure 1-2. Compaq FTAM Responder Architectural Overview

Application Layer

The Responder and Underlying Subsystems

User Application

API

Tandem FTAM

Presentation Layer

Session Layer

Transport Layer

Network Layer

Data Link Layer

Physical Layer

NSP

(X25AM)

RS-232C

RS-449

X.21, V.35

TAPS

(OSI/AS)

TSP

(OSI/TS)

NSP

(TLAM or PAM)

Controllers Controllers ControllersControllers

50-ohm

Baseband

NSP (X25AM)

RS-232C, RS-449, X.21, V-35

TSP (TCP/IP)

NSP

(TLAM or PAM)

50-ohm

Baseband

WAN

LAN

LANWAN

204CDT .CDD

PDUs from a remote FTAM initiator are received by the Compaq system at the Physical Layer and are transmitted up through the appropriate communications controller (or adapter), NSP process, TSP process, and TAPS process to the FTAM responder process.

OSI/FTAM Responder Manual—425199-001

1-6

Introduction to the Compaq F TAM Responder

The Responder and the File System

Figure 1-2 also shows the file system used by the Compaq responder to access files. When a remote FTAM initiator requests access to files, the Compaq FT AM responder

provides that service via its virtual filestore (VFS) component, which acts as an interface to the file system. The set of files accessible via the VFS includes all files on the Expand network to which the Compaq FTAM responder process’ system belongs.

The responder’s VFS maps the FTAM requests into file requests and translates between FTAM and Guardian file structures and attributes. For more information on the VFS and how it maps particular file structures and attributes, refer to Sections 3 and 4.

The Responder and the File System

OSI/FTAM Responder Manual—425199-001

1-7

Introduction to the Compaq F TAM Responder

The Responder and the File System

OSI/FTAM Responder Manual—425199-001

1-8

This section presents information about the conformance to standards and the interoperability of the Compaq FTAM responder.

Conformance is the satisfaction of the requirements of the applicable standards, consistent with the capabilities stated in the protocol implementation conformance statement (PICS) for the implementation. Interoperability is the ability of an implementation of a standard to work with other implementations of the same standard to deliver services.

A list of the supported standards and agreements that apply to Compaq FTAM is provided in “About This Manual” at the beginning of this manual.

Conformance and Interoperatility

Conformance

To be ISO FTAM-conformant, an FTAM implementation must comply with the International Organization for Standardization (ISO) FTAM standard for communication between different FTAM implementations. Conformance to the ISO FTAM standard is tested in the areas of the support of services, functional units, service classes, and file attributes.

Conformance testing increases the probability that an implementation is able to interwork with other implementations. Two or more implementations are more likely to work together if they conform to the same set of standards.

The Compaq OSI/FT AM product has been tested to conform with ISO 8571, NIST Special Publication 500-162 (Stable Implementation Agreements for Open Systems Interconnection Protocols) Part 9—FTAM Phase 2, and US GOSIP version 1.0.

Interoperabili ty

The interoperability, or interworking, of two FT AM implementations is the ability of these implementations to communicate using FT AM primitives in a useful and meaningful way. While conformance to ISO FTAM is necessary, it does not by itself guarantee that two implementations will interwork. Even if the two implementations conform to the same OSI protocol standard, they may be incapable of interworking with each other for reasons outside the scope of that standard (see ISO IS 9646-1, section

5.7.2). In addition, the FTAM standard is very complex. Two implementations may contain disjoint subsets of the standard that do not allow for interoperability but are fully conformant to the ISO specification. For example, two systems cannot interoperate if each supports only an initiator, or if a document type supported by an initiator is not included among the document types supported by the responder.

The Compaq FTAM product has been tested to conform with the standards and profiles mentioned in the above subsection, “Conformance.” It has also been tested to interoperate with a number of other vendors according to the NISTIR 4435 document, “FTAM Interoperability Tests, ” which most vendors use as a basis for writing FTAM interoperability tests.

OSI/FTAM Responder Manual—425199-001

2-1

Conformance and Interoperatility

When evaluating interoperability between Compaq FTAM and another FTAM implementation, consider the following aspects in which FTAM implementations can vary. Section 4 of this manual provides you with additional details about the Compaq FTAM implementation that you need to determine whether another implementation can interoperate with the Compaq FTAM product.

Basic Characteristics of FTAM Implementations

Basic Characteristics of FTAM Implem entations

To determine whether another FTAM implementation can interoperate with Compaq FTAM, you must first consider the following basic characteristics of the two implementations.

Roles of Initiator and Responder

Initiator and responder roles must be compatible to interoperate successfully. For two implementations to interoperate, there must be an initiator and a responder that can send and receive data between the two. For more information, see Section 4.

Roles of Sender and Receiver

The sender is the entity that sends data. The receiver is the entity receiving data. In Compaq FTAM, both the initiator and the responder have sender and receiver capabilities. For example, an initiator sending a read request is the receiver, and an initiator sending a write request is the sender.

Service Classes Supported

The service classes supported are defined in terms of combinations of functional units. At least one common service class must be supported for two implementations to interoperate. Compaq FTAM supports four service classes: file transfer, file

management, file transfer and management, and file access.

Underlying Services

Compaq FTAM uses Compaq OSI/AS, which is an implementation of version 1 of the Association Control Service Element (ACSE), as stated in ISO IS 8649 and 8650; version 1 of the Presentation Layer, as stated in ISO IS 8822 and 8823; and version 2 of the Session Layer, as stated in ISO IS 8326 and 8327. To interoperate with Compaq FTAM, other FTAM implementations must support compatible versions of ACSE, Presentation, and Session, as well as the services underlying the Session Layer.

Functiona l Un it s

Both implementations must support the functional units required for any services the pair will perform together. Compaq FTAM supports seven functional units: kernel,

read, write, file access, limited file management, enhanced file management, and grouping.

OSI/FTAM Responder Manual—425199-001

2-2

Conformance and Interoperatility

Limitations on Value of Future-Filesize A ttribute

Attributes

Aspects of attributes that can affect interoperability include the optional groups of attributes, the level of support for each individual attribute (see Table 4-4) and its optional components, and the range of values supported for each attribute. The Compaq FTAM implementation supports three attribute groups: kernel, storage, and security. For more information on attributes and attribute support for the Compaq FTAM responder, see Section 4.

FTA M Parameter s

Aspects of FTAM parameters that can affect interoperability include the supported optional parameters and the range of values for all parameters. If they are to interoperate, both implementations must support all parameters and ranges required by the services to be performed. For more information on the optional parameters and parameter value ranges supported by the Compaq FTAM responder, see Section 4.

Limitations on Valu e of Future-F ilesize Attribute

Because of file-size limitations imposed by the Guardian file system, the Compaq FTAM responder cannot support all possible values of the future-filesize attribute sent in create and change-attribute requests. The Compaq responder creates files with a maximum future-filesize value of 1 GB. If a value greater than 1 GB is requested, the responder returns an informative diagnostic message and creates the file with a futurefilesize value of 1 GB.

The smallest file the Compaq responder can create has a future-filesize value of 64 KB. If a smaller future-filesize value is requested, the responder creates the file with a futurefilesize value of 64 KB. (Note, however, that the entire 64K is not necessarily allocated; only as many extents as needed are allocated.)

In addition, the maximum size of files is limited by the physical storage capacity of the Compaq disk device being used.

Document Types and Related Par ame te rs

Both implementations must support one or more common document types to interoperate. Compaq FTAM supports the following document types: FTAM-1, FTAM2, FTAM-3, and NBS-9. In addition, both implementations must be aware of how the parameters associated with document type (the maximum-string-length, string- significance, and universal-class parameters) are used in the FT AM software with which they wish to interoperate.

The NBS-9 document type allows reading of directory information using an attribute bit string.

For more information on Compaq FT AM document types and related parameters, see Section 4.

OSI/FTAM Responder Manual—425199-001

2-3

Conformance and Interoperatility

Maximum-String-Length Parameter

Compaq FTAM supports unbounded strings. The limitations of the maximum-stringlength parameter are described in detail in Section 4.

S tr ing-Significance Parameter

The Compaq FTAM responder supports all three values (fixed, variable, and notsignificant) for the string-significance parameter in FTAM-1 documents. For the FTAM-3 document type, it supports the values not-significant, fixed, and variable.

Universal-Class Parameter

The default universal-class parameter value used by the Compaq FTAM responder for FTAM-1 and FTAM-2 files is GraphicString, as specified in ISO 8571.

Simplification and Relaxation

Simplification is the act of reading a file of a specific FTAM document type as a

less structured, or simpler, FTAM document type. Compaq FTAM supports the simplification of FTAM-2 Enscribe relative files to FTAM-1 files, but does not support simplification of Structured Query Language (SQL) tables.

Data-Transfer Considerations

Relaxation, or the process of deriving one document from another by making the parameters describing it less restrictive, is not supported at all by Compaq FTAM.

Mapping of Contents-Type Parameters

The Compaq FT AM virtual filestore (VFS) supports the Compaq FT AM responder by providing an interface to the Guardian file system. It maps FTAM file structures and attributes to Guardian file structures and attributes, and vice versa. Section 4 describes the mappings of FTAM document types to Guardian file types.

Note that the Compaq responder does not keep a permanent record of the contents-type parameter values used on creation of a file in the VFS. These values are directly available only during the life of the FTAM association in which the file was created. When a remote initiator makes a create request followed by an open request and the open request specifies a contents type of unknown, the responder uses the contents-type parameter values specified in the create request. However, this information is lost when the association is terminated. On subsequent accesses to the file via a select request followed by an open request with a contents type of unknown, the responder uses its default values based on the file structure, as described in Section 4.

Data-Tra n s f er C on s iderations

This subsection briefly describes the aspects of Compaq FTAM data handling that might affect interoperability between the Compaq FTAM responder and another FTAM implementation. For complete information, see Section 4.

OSI/FTAM Responder Manual—425199-001

2-4

Conformance and Interoperatility

Limits on Small String-Length Values With Large PDUs

When the Compaq FT AM responder receives data from a remote initiator, it decodes the data and stores it, as a sequence of strings, in an internal buffer with a maximum size of 25 KB. According to the NIST FTAM Phase 2 agreements, P-DATA carrying encoded FTAM PDUs or data elements cannot exceed 16 KB; however, string-header information in the buffer can cause the data in the buffer to be much larger than the maximum size of the encoded data. Because each string in the buffer includes a fixed number of bytes of header information, packing small strings into a large PDU can cause the 25 KB buffer size to be exceeded.

During data decoding, the responder checks the length of the data. If the decoded data cannot be accommodated in the 25 KB buffer, the responder generates a provider abort.

To avoid exceeding the buffer-size limit for writes to the Compaq responder, you can either send a smaller number of strings per PDU or send larger strings, as described in Section 4.

Handling of Escape Sequences

Data-Transfer Considerations

When writing data to the Guardian file system from a remote initiator, the responder first removes any escape sequences contained in each string it receives before enforcing the maximum-string-length limitation. When sending data to the remote initiator, it does not check for escape sequences, but simply counts all bytes and packages them into strings.

Use of Format Effectors

Format effectors are characters such as carriage returns and line feeds, which control

the formatting of information on character-imaging devices. To interoperate successfully , application programmers must understand what an implementation expects as an end-of-line symbol and how it interprets format effectors. For example, some implementations use the FTAM-1 document type to transfer binary data as opposed to text. Some implementations recognize carriage returns and line feeds as format effectors and discard them if binary data, not text, is being transferred. Others see the format effectors as data and transfer them as such.

In the Compaq FTAM responder’s virtual filestore (VFS), FTAM-1 files are treated as documents and are implemented as Guardian EDIT files, which have a maximum record length of 239 characters. The responder interprets carriage return-line feed combinations (CR/LFs) as end-of-line indicators. If a file being written to the responder’s VFS does not contain CR/LFs, the file is written in 239-character records.

Character Sets

The Compaq FT AM responder does no character-set verification. For FTAM-1 and FTAM-2 files, to ensure that the file being transferred contains the correct characterstring type as specified in the universal-class parameter, your remote application should verify characters as it sends or receives the data.

OSI/FTAM Responder Manual—425199-001

2-5

Conformance and Interoperatility

For FTAM-3 files, keep in mind that the native character sets (ASCII, EBCDIC, and so on) might be incompatible on the sending and receiving systems. For example, Compaq systems use the 7-bit ASCII character set, whereas some other vendors’ systems use 8-bit EBCDIC. If you decide to send or receive text characters as FTAM-3 binary data, some conversion of the native character set might be necessary.

Some files might contain multiple character sets. The file system provides no means of storing information on the location of character-set transitions within a file residing in it. Because the Compaq responder removes escape sequences when enforcing maximumstring-length limitations on data being written to the VFS, indications of transitions between character sets are lost.

Writing of FTAM-2 Fi le s

FTAM-2 files that are SQL tables must be written using the flat all data units (FA) access context, since each incoming data element represents a single SQL field and node descriptors are needed to delineate rows. Attempting to write to an SQL table using the unstructured all data (UA) access context causes the responder to return a cancel request that includes a diagnostic message indicating a poorly specified FADU. The file is left in an unknown state.

Presentation Encoding of FTAM PDUs and Data

FTAM-2 files that are not SQL tables may be written using either the FA or UA access context. When FTAM-2 files are written using the FA access context, the responder expects each text data element transferred to be preceded by a node-descriptor data element. If the node descriptor element is omitted, the responder returns a cancel request that includes a diagnostic message indicating an FTAM protocol error

Presentation Encoding of FTAM PDUs and Data

As described in ISO 8823, clause 8, there are several options for encoding FTAM PDUs as presentation data. Presentation data is encoded as a SEQUENCE OF PDV-list. Each PDV list contains one or more presentation data values (PDVs). PDV lists are encoded as single-ASN1-type, octet-aligned, or arbitrary. If only a single Abstract Syntax Notation-1 (ASN.1) data element (that is, a single PDV) is to be encoded, then a single PDV list encoded as single-ASN1-type may be used. However, if multiple ASN.1 data elements (that is, multiple PDVs) are to be encoded (as with grouped requests, concatenated PDUs, and most F-DATA requests), there are several options:

Place the PDVs in a single PDV list encoded as octet-aligned.

•

Place the PDVs in multiple PDV lists, each containing one ASN.1 data element (one

•

PDV), encoded as single-ASN1-type. Place the PDVs in multiple PDV lists, some containing multiple data elements

•

encoded as octet-aligned and others containing a single data element encoded as single-ASN1-type.

Any of these three options is valid if all data elements have the same presentation context. If different presentation contexts are needed (as would be the case, for example, with FTAM-2 data using the FA access context), a separate PDV list must be used for each different presentation context, and the third option applies.

OSI/FTAM Responder Manual—425199-001

2-6

Conformance and Interoperatility

When receiving PDUs, Compaq FTAM supports all three options listed above. When sending PDUs, Compaq FTAM follows these rules:

If single FT AM PDUs are to be sent, they are placed in a single PDV list encoded as

•

single-ASN1-type. If multiple FTAM PDUs are to be sent (grouped requests or responses), they are sent

•

in a single PDV list encoded as single-ASN1-type. When F-DATA requests are sent by the Compaq responder, the method of encoding

•

depends on the number of data elements to be encoded. If only a single data element is to be sent, it is placed in a single PDV list encoded as single-ASN1-type. If more than one data element is to be sent, the data elements are placed in a single PDV list, encoded as octet-aligned.

For FTAM-2 files, node-descriptor data elements are placed in their own PDV lists as single-ASN1-type. Consecutive file-contents data elements are placed in a single PDV list as either single-ASN1-type or octet-aligned, depending on whether one or more consecutive data elements exist.

Presentation Encoding of FTAM PDUs and Data

OSI/FTAM Responder Manual—425199-001

2-7

Conformance and Interoperatility

Presentation Encoding of FTAM PDUs and Data

OSI/FTAM Responder Manual—425199-001

2-8

Compaq FTAM Responder Operation

The Compaq responder receives an FTAM request from an initiating system, processes it, performs the appropriate action, and returns an FTAM response to the initiating system. It performs file-handling operations through its virtual filestore (VFS), which acts as an interface to the Guardian file system.

This section explains the major components of the Compaq responder process and describes the flow of communication between an initiating system and the Compaq responder.

Responder Structure

The Compaq responder process can be broken down into several components that perform services for FTAM applications.

Figure 3-1 outlines the components of the responder that process FTAM requests, perform the requested FTAM operations, and respond to the remote FTAM user. It focuses on the responder components specific to performing FTAM services and does not reflect the parts of the responder that format data or process management messages, for example.

Figure 3-1 shows the following responder components:

The protocol state machine receives requests for new FTAM associations and for

•

FTAM services, in the form of indications, from the TAPS process in the OSI/AS subsystem. It checks the FTAM requests for protocol errors, and if it finds none, takes the action necessary to perform the requested service. This action may require access to the file system through the responder VFS component.

Once any operations involving the file system are complete, the protocol state machine updates the state information for the association and sends a response to the remote FTAM initiator via the underlying OSI network.

The virtual filestore (VFS) acts as an interface to the file system. Files accessible

•

via the file system can also be accessed via the VFS component of the Compaq responder. The VFS is responsible for translating file structures and attributes into FTAM file structures and attributes, and vice versa. This translation is described further in Section 4 under “File-Attribute Mappings.”

The responder communicates with underlying Compaq OSI/AS processes through

•

the OSI/AS API.

OSI/FTAM Responder Manual—425199-001

3-1

Compaq FTAM Responder Operation

Figure 3-1. Compaq FTAM Responder Process

Responder Data Flow

FTAM Responder

Protocol

State Machine

Communications Network

OSI/AS API

4 7

TAPS

TSP

NSP

VFS

Guardian

File System

Remote

FTAM

Initiator

Responder Data Flow

Protocol and user data generally flows to and from the Compaq responder in the steps described below. Note that the responder sends primarily responses, although cancel and abort requests—and data indications during a data transfer—are also possible. For the purposes of this subsection, assume that the remote initiator sends an FTAM request and the responder returns a response to that request. This sequence of steps assumes that you have already established an association.

The numbers shown in Figure 3-1 correspond to the sequence of steps outlined below.

1. An FTAM application, typically on a remote system, issues an FTAM request to the

FTAM initiator supporting it.

OSI/FTAM Responder Manual—425199-001

208CDT .CDD

3-2

Compaq FTAM Responder Operation

2. The FTAM initiator follows the OSI protocol established on the initiating system to

send the outgoing FTAM protocol data unit (PDU) over the network to the Compaq responding system, where it is received as an indication.

3. Once on the Compaq responding system, the incoming FTAM indication is sent

through the NSP, TSP, and T APS processes, where it is formatted and processed as required by each OSI layer .

4. After processing the indication, the TAPS process sends the PDU through the

OSI/AS API to the protocol state machine of the responder.

5. The protocol state machine decodes and checks the validity of the indication and, if

the indication is valid, performs the requested action, communicating with the VFS where file-system access is required.

6. .The VFS accesses the file system via standard procedure calls and informs the

protocol state machine when the requested file-system actions are completed.

7. Based on the outcome of the file-system actions, the protocol state machine encodes

and sends a response PDU to the TAPS process for transmission to the FTAM initiator. This response contains any diagnostic messages resulting from its checking of FTAM protocol or from VFS communication with the file system.

Responder Data Flow

8. .The TAPS process formats the PDU and forwards it to the TSP process. The TSP

process, in turn, formats the PDU and sends it to the NSP process. The NSP process, depending on the network protocol that it supports, formats the PDU and forwards it via the appropriate controller (or adapter) over the network to the initiating system, where it is received as a confirm.

OSI/FTAM Responder Manual—425199-001

3-3

Compaq FTAM Responder Operation

Responder Data Flow

OSI/FTAM Responder Manual—425199-001

3-4

Compaq FTAM Responder Support of ISO FTAM Functions

This section provides detailed information on the Compaq FTAM responder’s support of ISO FTAM functions. It includes the following information:

FTAM functions supported by the Compaq responder

•

V irtual filestore (VFS) mapping considerations for FTAM document types

•

VFS mapping considerations for FTAM file and activity attributes

•

Support for optional parameters in request and response PDUs

•

VFS file-access and security considerations

•

Supported Functions

The functional scope of an FTAM association depends on which FTAM functions are supported both by the Compaq FTAM responder and the remote FTAM initiator with which it is interoperating. The following four tables identify the FTAM service classes, functional units, attribute groups, and attributes that the Compaq responder process supports.

For a listing and explanation of these FTAM functions as specified by ISO, refer to ISO 8571, parts 2 and 3.

Service Classes

Table 4-1 identifies the FTAM service classes that the Compaq responder process supports. The Compaq responder supports all ISO-defined service classes except the unconstrained class.

Table 4-1. Service Classes Supported by the Compaq FT AM Responder

Service Class

File transfer X File access X File management X File transfer and

management Unconstrained

Compaq Support

OSI/FTAM Responder Manual—425199-001

4-1

Compaq FTA M Responder Support of ISO FTAM Functions

Functiona l Un it s

Table 4-2 identifies the FTAM functional units that the Compaq responder process supports. The Compaq responder supports all ISO-defined functional units except the FADU locking, recovery, and restart-data-transfer functional units.

Table 4-2. Functional Units Supported by the Compaq FTAM Responder

Compaq

Functional Unit

Kernel X Read X Write X File access X

Support

Functional Units

Limited file management

Enhanced file management

Grouping X FADU locking Recovery Restart data transfer

Attribute Groups

Table 4-3 identifies the FTAM attribute groups that the Compaq responder process supports. The Compaq responder supports all ISO-defined attribute groups except the private group.

Table 4-3. Attribute Groups Supported by the Compaq FT AM Responder

Attribute Group

Compaq Support

Kernel X Storage X Security X Private

Attribute Support

Table 4-4 identifies the FTAM attributes that the Compaq responder supports and the type of support given—full or partial. In the case of fully supported attributes, the responder returns the current attribute value on a read-attribute request. When a

OSI/FTAM Responder Manual—425199-001

4-2

Compaq FTA M Responder Support of ISO FTAM Functions

responder partially supports an attribute, it recognizes the attribute name as valid, but provides no value for it. In this case, any reference to that attribute yields the result that no value is available, and any attempt to change the attribute fails. For more information on levels of attribute support, refer to ISO 8571-2, clause 9.4. Note that Compaq files protected by the Compaq Safeguard system software security package have fewer fully supported attributes than files protected by the Guardian environment.

Table 4-4. Attributes Supported by the Compaq FTAM Responder

Attribute Group File Attribute Level of Support

Kernel Filename Full

Permitted actions Full

Contents type Full*

Storage S tor age account Partial

Attribute Support

Date and time of

creation

Partial if protected by Safeguard security software

Full if protected by Guardian enviornment

Date and time of last

modification

Partial if protected by Safeguard security software

Full if protected by Guardian enviornment

Date and time of last

read access

Partial if protected by Safeguard security software

Full if protected by Guardian environment

Date and time of last

Partial

attribute modification

Identity of creator Partial if protected by Safeguard security

software Full if protected by Guardian environment

Identity of last

Partial

modifier

Identity of last reader Partial

Identity of last

Partial

attribute modifier

File availability Full

Filesize Full

Future filesize Full

OSI/FTAM Responder Manual—425199-001

4-3

Compaq FTA M Responder Support of ISO FTAM Functions

Table 4-4. Attributes Supported by the Compaq FTAM Responder (continued)

Attribute Group File Attribute Level of Support

Security Access control Partial if protected by Safeguard security

Legal qualifications Partial

Private Private use Not supported

* In this context, full support applies to the contents type as a whole; it does not imply the s upport of all document types or all possible value s of the parameters (maximum-s tring-l eng th, unive rsal-cla ss, and stri ng-sign ifi cance) that further define th e con tents type.

Document Types

Table 4-5 identifies the FTAM document types that the Compaq responder supports and provides all supported values for associated contents-type parameters. The parameter values listed here are those directly supported; for information on the default values of these parameter values, see Table 4-7, later in this section.

Document Types

software

Document types can be simplified to other document types with simpler structures. Simplification is the process of reading a file of a specific document type as a simpler document type. Relaxations—specifications that change the parameter values of a document type—are not permitted by Compaq FTAM. For more information on simplification and relaxation, see the subsection “Contents-Type Attribute,” later in this section.

The NBS-9 parameter value < filename > shown in Tab le 4-5 is the syntax notation for representing the value of a bit string. In this case, only the filename attribute bit is set.

Table 4-5. Document Types and Parameters Supported by the Compaq FTAM Responder

FT AM Document Types Paramet ers Parameter Values

FTAM-1

FTAM-2 universal class 22, 25-27

universal class 22, 25-27

maximum-string-length 1 - 7148 (in bytes)

string-significance not-significant or

Fixed or Variable

maximum-string-length 1 - 4072* (in bytes)

string-significance not-significant

FTAM-3 maximum-string-length 1 - 4096 (in bytes)

string-significance not-significant

OSI/FTAM Responder Manual—425199-001

4-4

Compaq FTA M Responder Support of ISO FTAM Functions

Mapping Between FTAM Contents Ty pes and

Compaq File Structures

Table 4-5. Document Types and Parameters Supported by the Compaq FTAM Responder (continued)

FT AM Document Types Paramet ers Parameter Values

maximum-string-length 1-4072 (in bytes)

string-significance fixed or variable**

NBS-9 Not applicable <fil ename>***

FTAM-2 files are relative (sequential) files, and each logical record of a relative file can be a maximum of 4072 bytes. Each strin g is s tored as a logica l record in a relati ve file . The refor e, the practi cal siz e lim it of a string dur ing data transf er is 4072.

∗∗

If the strin g-signi fic ance para meter is set to fixe d or varia ble , the fi le is an ent ry-sequ enced file an d is subje ct to the maximum logical reco rd length of 4072 bytes. However, if a DEFINE by the name _ZOSF_FIXED_AS_UNSTRUCT exists when the FTAM processes are s tarted then with the string-si gnificance se t to FIXED, the file will be an unst ructured file with a maximum-string-lengt h of 4096 bytes.

∗∗∗

This value represents the Compaq FTAM responder de fault for NBS-9 files. If you open an NBS-9 file without specifying t he file attri bute s to return , the Com paq re sponde r defa ults th e paramete r se tti ng to the file name attri bute only. If you do specify file attributes , the Compaq responder returns the specified file attributes.

Mapping Between FTAM Contents Types and Compaq File Structures

The FTAM virtual filestore (VFS) supports the Compaq responder by providing an interface to the Guardian file system. The Compaq implementation of the VFS maps Compaq FTAM file structures and attributes to Guardian file structures and attributes, and vice versa. Tables 4-6 and 4-7 show mappings of FT AM document types to file types.

Create Mappings

Table 4-6 shows the Guardian file structures created when you use the F-CREATE service to create FTAM files, provided either the file does not exist or the override parameter is set to delete and create with new attributes. (If the file exists and the override parameter is set either to select the old file or to create a new file with the old attributes, the existing file attributes are not checked and are left unchanged.) The table also shows the default parameter values for the FTAM-1, FTAM-2, and FTAM-3 document types. This table indicates the default parameter values for the document types that Compaq supports, whereas Table 4-5, earlier in this section, indicates the full range of parameter values for these document types.

For the create service to succeed, the maximum-string-length parameter is optional, because the ISO FTAM default value for this parameter, unbounded, is supported by the Compaq responder. Further, the value of the maximum-string-length parameter must

OSI/FTAM Responder Manual—425199-001

4-5

Compaq FTA M Responder Support of ISO FTAM Functions

fall within the range supported by the Compaq responder for that document type and string-significance value, as follows:

Create Mappings

Document Type

FTAM-1 not significant 1 <= maximum-string-length <= 7148 FTAM-1 fixed 1 <= maximum-string-length <= 7148 FTAM-1 variable 1 <= maximum-string-length <= 7148 FTAM-2 not significant 1 <= maximum-string-length <= 4072 FTAM-3 not significant 1 <= maximum-string-length <= 4096 FTAM-3 fixed 1 <= maximum-string-length <= 4072 FTAM-3 variable 1<= maximum-string-length <= 4072

String-Significance

Value Maxim um-String-Length Value

If the maximum-string-length parameter is not specified or if the specified value does not fall within the defined range, the responder returns a negative confirm containing diagnostic message 1001, indicating unsupported parameter values.

Although Compaq FTAM supports the NBS-9 document type, it does not appear in Table 4-6 because Compaq FTAM cannot create NBS-9 files. The “NBS-9 Documents” subsection, later in this section, describes NBS-9 files in more detail. The Compaq responder also supports the NonStop Structured Query Language (NonStop SQL) table files for reading and writing. Compaq FTAM provides no support for creating SQL files.

OSI/FTAM Responder Manual—425199-001

4-6

Compaq FTA M Responder Support of ISO FTAM Functions

Table 4-6. Create Mappings: FT AM Contents Type to Compaq File Structure

Contents Type Compaq File Structure

Select-Open Mappings

FTAM Document Types

FTAM -1

FTAM -2

FTAM -3

∗

The following va lues are possible for file type:

U = Enscribe unstructured R = Enscribe relative E = Enscribe entry-sequenced

∗∗

This is the standard Guardia n file attribute that stands for the maximum record length.

∗∗∗

The maximum-string-l ength parameter must be specified.

∗∗∗∗

Line numbers are not preserved. If the value specified for the max-extents attribute is exceeded, max-exte nts

is automatically increas ed (in increments, up to the syst em limit) and the lines renumbered. The maximum number of lines allowed for file type 101 is 10,000,000. For more information, see the Guardian

Procedure Calls Reference Manual.

Default Parameter Values Descri ption File

universal-class = 25 (Gra phic String) maximum-string-l ength = none*** string-significance = not-significant

universal-cla ss = 25 (GraphicString) maximum-string-l ength = none*** string-significance = not-significant

maximum-string-l ength = none*** string-significance = fixed

maximum-string-l ength = none*** string-significance = variable

maximum-string-l ength = none*** string-significance = not-significant (defaults to not-si gnificant if omitted)

Standard edit file

Enscribe relative file

Enscribe entrysequenced file

Enscribe entrysequences file

Enscribe unstructured file

Type*

U 101**** Not

R0maximum-

E891maximum-

E892maximum-

U0 Not

File Code

Record Length**

applicable

stringlength

applicable

Note. If a DEFINE by the name of _ZOSF_FIXED_AS_UNSTRUCT exists when the FTAM processes are started, and the stri ng-s ignificance parameter is set to FIXED in the request, the file created or selected will be an unstructured file with maximum-string-length of 4096 bytes.

Note. Though a def ault value fo r each paramet er is propos ed, if there a r e any user-defined default values ava ilable for particular combinations on a file type and file code, then that will override the system-defined default parameter values.

Select-Open Mappings

Table 4-7 shows the FTAM document types that correspond to each Compaq file type that can be selected, opened, and read. This table indicates the default parameter values for the document types that Compaq supports, whereas Table 4-5, earlier in this section, indicates the full range of parameter values for these document types.

OSI/FTAM Responder Manual—425199-001

4-7

Compaq FTA M Responder Support of ISO FTAM Functions

When you issue a file-open request, you specify a contents-type parameter that provides the document type of the file and, optionally, parameter values that further define the document type. When a remote initiator sends a file-open request to the Compaq responder and specifies a contents type of unknown on the open request, the contents type returned by the responder yields the appropriate FT AM document type according to the requirements of the file system and as outlined in Table 4-7. If the file-open request indicates an FTAM document type (rather than unknown) for the contents type, the document type must generally be consistent with the mapping of Guardian file types to FTAM document types shown in Table 4-7. If the document type is not consistent with the values shown in Table 4-7, the responder returns a negative confirm that includes diagnostic message 5036, contents type inconsistent.

If the maximum-string-length parameter of the contents type is specified, the responder checks the proposed value before performing the select or open service. For the select or open to succeed, the value of the maximum-string-length parameter must fall within the range supported by the Compaq responder for that document type and stringsignificance value, as follows (where record length is the standard Guardian file attribute that stands for the maximum record length):

Select-Open Mappings

Document Type

String-Significance

Value

Valid Maximum-String-Length Value(s)

FTAM-1 not-significant 1 <= maximum-string-length <= 7148 FTAM-2 not-significant maximum-string-length <= record length FTAM-3 not-significant 1 <= maximum-string-length <= 4096 FTAM-3 fixed maximum-string-length = record length FTAM-3 variable maximum-string-length <= record length

If the proposed maximum-string-length value does not fall within the defined range, the responder returns a negative confirm containing diagnostic message 5036.

In addition, the contents type is an FTAM file attribute. When a remote FTAM initiator sends a read-attribute request, the value of the contents-type attribute that the Compaq responder returns is one of the FT AM document types listed in Table 4-7.

Table 4-7. Select-Open Mappings: Compaq File Structure to FTAM Contents Type

Compaq File Structure Contents Type

Description File

Type*

Standard edi t file

Enscribe relati ve f ile

SQL table, organization relative

U 101**** FTAM-1

R- FTAM-2

File Code

FTAM Document Types

Default Parameter Values

universal-cla ss = 25 (Graphic String) maximum-string-l ength = 7148 string-significance = not-significant universal-cla ss = 25 (Graphic String) maximum-string-l ength = record length** string-significance = not-significant universal-cla ss = 25 (Graphic String) maximum-string-l ength = record length** string-significance = not significant

OSI/FTAM Responder Manual—425199-001

4-8

Compaq FTA M Responder Support of ISO FTAM Functions

Table 4-7. Select-Open Mappings: Compaq File Structure to FTAM Contents Type (continued)

Compaq File Structure Contents Type

Fixed-length binary file

Var iablelength binary file

E891FTAM-3

E892FTAM-3

Select-Open Mappings

maximum-string-l ength = record length** string-significance = fixed

maximum-string-l ength = record length** string-significance = variable

Description File

Type*

Unstructured file

Non-SQL keysequenced file

Non-SQL entrysequenced file

Directory (selected by supplying a file name of “DIRLIS”)

SQL table , not organization relative

∗

The following values are possible for file type:

U = Enscribe uns tructured R = Relative E = Entry-sequenced K = Key-sequenced

∗∗

This is th e st an d ar d Gu a r di an fil e attrib ut e th a t st an d s for th e ma x i mu m re c o rd length .

∗∗∗

This value represents the Compaq responder default for NBS-9 files on an open. If you ope n an NBS-9 file without specifying the file attributes to return for the files in the directory, the Compaq responder defaults the parameter sett ing to the filename attribute only. If you do specify file attributes, the Compaq responder returns the specified file a ttributes for the files in the directory.

∗∗∗∗

Line numbers are not pre served. If the value specified for the max-extents at tribute is exceeded, max-extents is

automatically increased ( in increments, up to the syst em limit) an d th e lines renumbered. The maximum number of lines allowed for file type 101 is 10,000,000. For more information, see the Guardian Procedure

Calls Reference Manual.

U All file

K- FTAM-3

E All file

- - NBS-9 <filename>***

K or E - Not s upported;

File Code

codes except 101

codes except 891, 892

FTAM Document Types

FTAM -3

returned diagnostic = 3013

Default Parameter Values

maximum-string-l ength =2048 string-significance = not significant

maximum-string-l ength =512 string-significance = not significant

Not app li c a b le

OSI/FTAM Responder Manual—425199-001

4-9

Compaq FTA M Responder Support of ISO FTAM Functions

Note. Though a default value for each parameter is proposed, if there is a user-defined default value for a parti c ular combination of a file type and fi le c ode, that user-defined value will override the system default.

Maximum-String-Length Checking of Data Values

The responder enforces strict rules on maximum-string-length checking. Every data value received or sent by the responder is checked according to the rules described below.

Write Operations

When writing data to the Guardian file system from the remote initiator, the responder checks the length of each string against the maximum-string-length value established for the file (the value proposed in the contents-type parameter of the open request or returned in the open confirm). The responder first removes any escape sequences contained in each string it receives before enforcing the maximum-string-length limitation.

If the string length is greater than the proposed maximum-string-length value, or if the string significance is fixed and the string length is less than the proposed value, the responder returns a cancel request containing diagnostic message 1007, indicating an unspecific FTAM protocol error.

Read Opera tions

The responder does no escape-sequence checking on the data it retrieves from the VFS and sends to the remote initiator; it simply counts all bytes and packages them into strings. For read operations on FTAM-3 files with a string-significance value of fixed, the responder does check for strings whose length is smaller than the maximum-stringlength value. If any such strings are found, the responder returns a cancel request containing diagnostic message 5027, indicating a bad read.

Limits on Small String-Length Value s With Large PDU s

When the Compaq responder receives data from a remote initiator, it decodes the data and stores it, as a sequence of strings, in an internal buffer with a maximum size of 25 KB. According to the NIST FTAM Phase 2 agreements, P-DATA carrying encoded FTAM PDUs or data elements cannot exceed 16 KB; however, string-header information in the buffer can cause the data in the buffer to be much larger than the maximum size of the encoded data. Because each string in the buffer includes a fixed number of bytes of header information, packing small strings into a large PDU can cause the 25 KB buffer size to be exceeded.

During data decoding, the responder checks the length of the data. If the decoded data cannot be accommodated in the 25 KB buffer, the responder generates a provider abort.

To avoid exceeding the buffer-size limit for writes to the Compaq responder, you can either send a smaller number of strings per PDU or send larger strings. Sending larger

OSI/FTAM Responder Manual—425199-001

4-10

Compaq FTA M Responder Support of ISO FTAM Functions

strings may require you to increase the value of the maximum-string-length parameter in your requests. The following formula defines the conditions under which decoded data will fit into the buffer:

NS-1 Σ ((ZLEN)i )+ ((26 + PAD) * NS) <= 25600 bytes

i=0

where

NS = number of character strings ZLEN = length in bytes of a given character string PAD = pad byte following string; if string length is even,

PAD = 0; otherwise, PAD = 1 26 = maximum data-header overhead per character st ring

When the responder retrieves data from the VFS in response to a read request, it automatically packages it into PDUs small enough to fit into its buffer. Therefore, no similar adjustments are necessary on read requests.

The formula for calculating the size of the encoded data is given below. This formula applies only to PDUs that contain primitive strings; PDUs containing constructed strings have additional overhead. As mentioned above, the encoded data limit is 16 KB.

File-Attribute Mappings

NE-1 SIGMA((ZLEN)i )+ ((TAG + LEN) * NS) <= 16384 bytes (16 KB)

i=0

where

NS = number of character strings ZLEN = length in bytes of a given character string TAG = number of bytes used to encode the data tag LEN = number of bytes used to encode length of string

Note. When the C om paq respon der encode s data, the max im um enc oded-data he ader overhead (TAG + LEN) is always 4 bytes per string . (The same is tru e fo r dat a enc oded by the Compaq ini ti at or.) An FTAM configurable file ca nnot be open ed by the re s ponder.

File-Attribute Mappings

The following subsection maps FTAM virtual filestore file attributes to specific Guardian and NonStop SQL file attributes. File attributes provide information for various aspects of a file, such as file name, file size, date and time of file creation, and so on.

Kernel Group File Attributes

Every FTAM implementation must fully support kernel file attributes. The kernel group includes the filename, permitted-actions, and contents-type attributes.

OSI/FTAM Responder Manual—425199-001

4-11

Compaq FTA M Responder Support of ISO FTAM Functions

Filename Attribute

The filename attribute maps directly from the Compaq external file name to the FTAM VFS, with the exception of specifying NBS-9 files. For an explanation of the relationship between the filename attribute and NBS-9 files, see “NBS-9 Documents” later in this subsection.

Permitted-Actions Attribute

The permitted-actions attribute is a fixed list that specifies the actions that can be performed on an FT AM file. No Compaq file attribute corresponds to permitted-actions. When a remote initiator creates an FTAM file in the Compaq VFS, the Compaq responder always sets permitted-actions to fixed values. The fixed values selected depend on document type, as listed in Table 4-8. Although the remote application can specify permitted-actions in its file-create request, the values in Table 4-8 always override these values.

Table 4-8. Actions Permitted for FTAM Document Type

Kernel Group File Attributes

FT AM Document Types Permitted Actions

FTAM-1 Read, replace, extend, erase , read-attri bute, change-

attribute, delete-file

FTAM-2 Read, insert, erase, read-attribute, change-attribute,

delete-file, traversal, reverse-traversal, randomorder

FTAM-3 Read, replace, extend, erase , read-attri bute, change-

attribute, delete-file

NBS-9 Read, read-attribute

Contents-Type Attribute

The contents-type attribute maps directly to Compaq file structures. Table 4-6, earlier in this section, lists the Compaq file structures (including file type and file code) created when you use the file-open service with any supported contents type except NBS-9. Table 4-7 shows how the responder maps Compaq files to the FTAM contents type when you open them with a contents-type value of unknown, or when you read the file attributes of the Compaq file.

When you open an existing file to read it, you can specify as part of the contents-type parameter a document type that is a simplification of the FTAM document type normally expected for that file. Document types can be simplified to other document types with simpler structures.

You can simplify document types only on read operations. This means that you must issue a read request immediately after your open request. If you issue a write request after an open request that requires a simplification, the responder returns a diagnostic message.

OSI/FTAM Responder Manual—425199-001

4-12

Compaq FTA M Responder Support of ISO FTAM Functions

The responder allows for the simplification of FTAM-2 document types to FT AM-1 document types only. In addition, FT AM-2 simplification is allowed only on Compaq Enscribe relative files, not on SQL tables. Per the ISO 8571-2 provisions, the responder allows no simplification of FTAM-1 or FTAM-3 files.

Compaq FTAM does not permit the relaxation of document type parameters to less restrictive values. The VFS component of the responder keeps no record of the universal-class value associated with files created on the Guardian file system. In the case of the maximum-string-length parameter, the VFS records the maximum-stringlength value for all FTAM-2 documents, and for FTAM-3 documents with a stringsignificance value of fixed or variable. For FTAM-1 documents, and for FTAM-3 documents with a string-significance value of not significant, the VFS has no memory of the associated maximum-string-length value.

Table 4-9 shows the simplification of document types that the responder allows.

Table 4-9. Simplification of Document Types Supported by the Compaq FTAM Responder

Kernel Group File Attributes

FT AM Document Type Document Type Simplifications

FTAM-1 Not applicable FTAM-2 FTAM-1 (Enscribe relative files on ly) FTAM-3 Not applicable NBS-9 Not applicable

NBS-9 Documents

NBS-9 documents are files that have been created by listing Guardian directories. If the remote initiator sends an F-SELECT primitive with a filename attribute of DIRLIS (all in uppercase), the Compaq responder returns a file of directory entries (an NBS-9 file) for the volume and subvolume specified in the filename attribute. The read and readattribute actions are the only file actions that you can perform on an NBS-9 file. If a volume and subvolume are not specified, the responder uses the default volume and subvolume of the user specified in the initiator-identity parameter of the F-INITIALIZE request.

OSI/FTAM Responder Manual—425199-001

4-13

Compaq FTA M Responder Support of ISO FTAM Functions

You can specify DIRLIS with volume or subvolume in any of the following ways:

$volume.subvol.DIRLIS

•

$volume.DIRLIS

•

subvol.DIRLIS

•

DIRLIS

•

Note. Because using ‘DIRLIS ’ (u pperca se) i n the F- SELECT pri mit iv e ret urns the directory file, and Guardian file n ames are not case-sensitive, you should use “dirlis” (lowercase) in the FSELECT primitive to select an actual file by this name rather than the directory file.

Each NBS-9 document has an attributes bit-string parameter. Each bit in this bit string identifies an individual file attribute. Table 4-10 shows the attributes that correspond to each bit.

Table 4-10. Bit String for NBS-9 File Attributes

Kernel Group File Attributes

Bit Numbers Attributes

0Filename 1 Permitted actions 2 Contents type 3 Storage account 4 Date and time of creation 5 Date and time of last modification 6 Date and time of last read access 7 Date and time of last attribute modification 8 Identity of creator 9 Identity of last modifier 10 Identity of last reader 11 Identity of last attribute modifier 12 File availability 13 Filesize 14 Future filesize 15 Access control 16 Legal qualifications 17 Private use

To control which attributes the responder returns when you read an NBS-9 file, set the bit string in the file-attributes field of the contents-type parameter on the F-OPEN

OSI/FTAM Responder Manual—425199-001

4-14

Compaq FTA M Responder Support of ISO FTAM Functions

request primitive. This allows you to specify all or a subset of the attributes listed above. (Likewise, to control which attributes the responder returns when you read the attributes of an NBS-9 file, you set the bit string in the attribute-names parameter of the read-attribute request.) When you read the NBS-9 file, the responder returns only the attributes you select. If you do not specify this parameter, the responder returns only the filename attribute. For more information on the definition of the bit string in an NBS-9 directory file, refer to the NIST FTAM Phase 2 agreements, Part 9, Clause A.8.2.

Note. On Compaq systems, an NBS-9 file does no t correspond to an actual physical Compaq file; theref ore, the rea d-attribut e ac t ion does not provide muc h useful inf orm ation for N BS-9 files. The Compaq responder provides this service for NBS-9 files for interoperability, to support applications that perform a fixed sequence of services (for example, select, readattribute, open, read) on any do cu m ent type.

Storage Group File Attributes

Storage attributes are negotiated between a remote initiator and the local responder. The responder fully supports some storage attributes and partially supports others. If a partially supported attribute is referenced, the Compaq responder indicates that no value is available. You cannot change a partially supported attribute.

Storage Group File Attributes

In the case of all four date-and-time attributes and the identity-of-creator attribute, if the file under consideration is protected by the Safeguard security software, the attribute in question is partially supported. The attribute is fully supported if the file is not protected by the Safeguard security software. The date-and-time attributes are maintained by the local file system.

The ISO 8571 standard defines two possible values for the file-availability attribute: immediate or deferred availability. The Compaq responder supports only immediate availability.

Filesize corresponds to the Guardian file attribute EOF (end-of-file), which returns the number of bytes in the file. Filesize is a read-only attribute and cannot be set.

The future-filesize attribute corresponds to a Guardian calculation—max-filesize— based on the Guardian file attributes primary extent size and secondary extent size. If the remote application reads the future-filesize attribute, the Compaq responder returns the max-filesize value. If the application writes the attribute, the responder changes the Guardian file attribute max-extents.

The formula for calculating max-filesize from the Guardian file attributes is as follows:

max-filesize = [primary extent size + ((max-extents - 1) * secondary extent size)] * 2048

where 2048 is the number of bytes in a page. (The primary and secondary extent sizes are expressed in pages, whereas max-filesize is expressed in bytes.)

When a file is created through the FTAM create service, the Guardian max-extents attribute is set to 16 if the future-filesize value is less than 1 MB, or to 512 if the futurefilesize value is greater than or equal to 1 MB. Then the primary and secondary extent sizes are both set to the smallest integral multiple of 2 pages (4096 bytes) that will make the max-filesize value greater than or equal to the future-filesize value. If the future-

OSI/FTAM Responder Manual—425199-001

4-15

Compaq FTA M Responder Support of ISO FTAM Functions

filesize parameter is not specified in a create request, the responder creates a file with a future-filesize value of 8 MB.

Subsequent change-attribute requests can change the value of max-extents. In all cases, the minimum value of max-extents is 16, and the maximum value is 978. The extent size cannot be changed.

Because of file-size limitations imposed by the Guardian file system, the Compaq responder cannot support all possible values of the future-filesize attribute sent in create and change-attribute requests. The Compaq responder creates files with a maximum future-filesize value of 1 GB. If a value greater than 1 GB is requested, the responder returns an informative diagnostic message and creates the file with a future-filesize value of 1 GB.

Note that the maximum size of files is limited by the physical storage capacity of the Compaq disk device being used. If an application attempts to write to a Compaq responder a file larger than 1 GB or larger than the disk device can hold, a file-system error 43 (unable to obtain disk space for file extent) will eventually occur in a WRITE call, and the Compaq responder will send a cancel to the application.

Storage Group File Attributes

Table 4-11 summarizes the Compaq support for the storage attributes.

Table 4-11. FTAM Storage Attributes and Corresponding Compaq File Attributes

Storage Attributes Level of Support Compaq File Attrib ute s

Storage account Partial Date and time of

creation

Date and time of last modification

Date and time of last read access

Date and time of last attribute modification

Partial if protected by Safeg u a rd securi t y so ftwar e ; Full if protected by Guardian environment

Partial

creation date-time for files other than NBS-9; current time for NBS-9

last modification date-time for files other than NBS-9; current time for NBS-9

last open date-time for files other than NBS-9; current time for NBS-9

OSI/FTAM Responder Manual—425199-001

4-16

Compaq FTA M Responder Support of ISO FTAM Functions

Table 4-11. FTAM Storage Attributes and Corresponding Compaq File Attributes (continued)

Storage Attributes Level of Support Compaq File Attrib ute s

Security Group File Attributes

Identity of creator Partial if protected by

Safeg u a rd securi t y so ftwar e or if document type is NBS-9; Full if protected by Guardian environment

Identity of last modifier

Identity of last reader

Identity of last attribute modifier

File availability Full always available Filesize Full for files other than

Future filesize Full for files other than

Partial

NBS-9; Partial for NBS-9

owner

eof-pointer

max-filesize (read attribute) max-extents (change attribute)

Security Group File Attributes

The remote responder and local initiator negotiate security attributes. The responder fully supports some security attributes while only partially supporting others. If a partially supported attribute is referenced, the Compaq responder indicates that no value is available. You cannot change a partially supported attribute. Table 4-12 shows Compaq support for security attributes.

Table 4-12. Security Attributes Supported by the Compaq FTAM Responder

Security Attributes Level of Support

Access control Partial if protected by Safeguard security software;

Full if protected by Guardian environment

Legal qualifications Partial

∗

In accordance with ISO 8571-2, clause 12.16, the Compaq responder supports only a single action list for the

access-control attribute.

Access-Control Attribute

The ISO FT AM access-control attribute is a set of access-control elements, with each element consisting of an action-list field and, optionally, concurrency-access, identity, passwords, and location fields. The access-control attribute defines the conditions under

∗

OSI/FTAM Responder Manual—425199-001

4-17

Compaq FTA M Responder Support of ISO FTAM Functions

which access to a file is allowed. ISO 8571-2 provides a complete description of the ISO FTAM access-control attribute.

Within the access-control attribute, the Compaq responder uses only the action-list field of the first access-control element; the concurrency-access, identity, passwords, and location fields are ignored, as are all access-control elements after the first.

Further, for Safeguard protected files, the access-control attribute is partially rather than fully supported. For these files, no mapping to Guardian security is attempted, and the responder indicates that no value is available when it reads the access-control attribute. In this case, attempts to change the attribute fail.

The following subsections explain how the Compaq FTAM responder uses the accesscontrol attribute in three tasks requested by a remote initiating system: creating files, changing file attributes, and reading file attributes.

Creating Files. For files created through FTAM, the access-control attribute provided by the initiating system with the initial-attributes parameter in the F-CREATE request maps to Compaq file security (R W E P—Read Write Execute Purge). This mapping is as follows:

Security Group File Attributes

The Compaq responder uses only the first access-control element. If more than one

•

access-control element is present, the responder ignores all elements other than the first. The responder uses only the action-list field of the access-control element and returns a diagnostic message if the access-control element contains any other information (such as concurrency-access and identity).

If the read access-control bit of the action list is set, the Compaq responder sets

•

READ access to N, indicating that any user on the Expand network can read the file. Otherwise, the responder sets READ access to –, indicating that only the super ID user can read the file.

If any of the insert, replace, extend, change-attribute, or erase access-control bits of

•

the action list are set, the responder sets WRITE access to N, indicating that any user on the Expand network can write to the file. Otherwise, the responder sets WRITE access to –, indicating that only the super ID user can write to the file.

EXECUTE access is set to –, indicating that only the super ID user can execute the

•

file. If the delete-file access-control bit of the action list is set, the responder sets PURGE

•

access to N, indicating that any user on the Expand network can purge the file. Otherwise, the responder sets PURGE access to –, indicating that only the super ID user can purge the file.

The mapping of FTAM action-list settings to Guardian security is summarized in Table 4-13.

OSI/FTAM Responder Manual—425199-001

4-18

Compaq FTA M Responder Support of ISO FTAM Functions

Table 4-13. Mapping From FTAM Action List to Guardian Security

If action list is set to… Guard ian secur ity is modif ied to…

Read Set READ access to N Insert Set WRITE access to N Replace Set WRITE access to N Extend Set WRITE access to N Erase S et WRITE acce ss to N Read attributes (no change) Change attributes Set WRITE access to N Delete file Set PURGE access to N

If the access-control attribute is not present in the F-CREATE indication, the Compaq responder sets Compaq file security to the default security allowed for the FTAM association, as defined by the initiator-identity parameter sent in the F-INITIALIZE request or by the default user (DEFUSER) attribute specified in the VFS profile configured for this responder.

Security Group File Attributes

Changing File Attributes. The access-control attribute can be modified through FTAM using the F-CHANGE-ATTRIB primitive. On the basis of the information a remote initiator sends in the F-CHANGE-ATTRIB request, the Compaq responder modifies the Guardian security of a file according to the functions it supports and returns a new value for the access-control attribute in the F-CHANGE-ATTRIB response. The Compaq responder access-control attribute is limited to a single access-control element.

In the F-CHANGE-ATTRIB request sent by the initiating system, the values for access control consist of insert-values or delete-values (or both), each of which can be zero, one, or more access-control elements. The Compaq responder, however, processes only the first access-control element sent for insert-values and for delete-values. The Compaq responder also ignores all but the first component of the insert-values or delete-values information, using only the action-list information to modify Guardian security (R W E P) for the file. If the initiating application attempts to change any other components of access control (such as concurrency-access, location, or identity), the Compaq responder returns a diagnostic message.

Insert-values and delete-values turn access to the actions in the action list on and off, respectively. Because the access-control attribute can indicate both insert-values and delete-values, you might unintentionally specify the same action in both values. If this occurs, the delete-values action overrides the insert-values action.

The following rules apply to changing the access-control attribute: For insert-values:

If the read access-control bit of the action list is set, the responder sets READ access

•

to N, indicating that any user on the Expand network can read the file.

OSI/FTAM Responder Manual—425199-001

4-19

Compaq FTA M Responder Support of ISO FTAM Functions

If any of the insert, replace, extend, change-attribute, or erase access-control bits of

•

the action list are set, the responder sets WRITE access to N, indicating that any user on the Expand network can write to the file.

If the delete-file access-control bit of the action list is set, the responder sets PURGE

•

access to N, indicating that any user on the Expand network can purge the file.

For delete-values:

If the read access-control bit of the action list is set, the responder sets READ access

•

to –, indicating that only the super ID user can read the file. If all of the insert, replace, extend, change-attribute, or erase access-control bits of

•

the action list are set, the responder sets WRITE access to –, indicating that only the super ID user can write to the file. If only some of these access-control bits are set, there is no change.

If the delete-file access-control bit of the action list is set, the responder sets PURGE

•

access to –, indicating that only the super ID user can purge the file.

Note. EXECUTE access is always set to –, indicating that only the super ID user can execute the file.

Security Group File Attributes

Reading File Attributes. When the Compaq responder reads FTAM file attributes for document types other than NBS-9, it maps the values for access control from Guardian security based on the user ID for the association, as defined by the initiator-identity parameter sent in the F-INITIALIZE request or by the DEFUSER attribute specified in the VFS profile configured for this responder. This mapping shows which actions that user can perform. (For NBS-9 files, the action list on a read-attribute action is always [read, read-attribute]).

The user has specific access (READ, WRITE, EXECUTE, or PURGE) to a file if one of the following applies:

User is super ID, and file is on the same Expand node as the responder.

•

Guardian security is N.

•

Guardian security is A, and file is on the same Expand node as the responder.

•

Guardian security is C, and user is in the same group as the owner of the file.

•

Guardian security is G, and user is in the same group as the owner of the file, and

•

file is on the same Expand node as the responder. Guardian security is U, and user is the owner of the file.

•

Guardian security is O, user is the owner of the file, and file is on the same Expand

•

node as the responder.

The Compaq responder sets the individual bits of the action list according to the Guardian access allowed for the user. Table 4-14 shows how Guardian security maps to FTAM action-list settings.

OSI/FTAM Responder Manual—425199-001

4-20

Compaq FTA M Responder Support of ISO FTAM Functions

Table 4-14. Mapping From Guardian Security to FTAM Action List

Guardian Access Action-List Bit s Set

READ Read WRITE Insert, Replace, Extend, Erase, Change-attribute EXECUTE No effect on access control PURGE Delete-file

The read-attribute bit is always set.

Legal-Qualific ations Attribute

The legal-qualifications attribute conveys information about the legal status of the file and its use. This attribute is partially supported.

Private Group File Attributes

Private Group File Attri butes

Compaq FTAM does not support private group file attributes.Supported and Unsupported Optional ParametersSupported and Unsupported Optional Parameters

Supported and Unsupported Optional Parameters

Table 4-15 indicates the level of support provided by the Compaq responder for the optional parameters received in request PDUs. It shows what action the Compaq responder performs on the optional parameters received from a remote initiator.

Table 4-15. Compaq Support of Optional Parameters Received in Request PDUs

Parameters Level of Compaq Support

Implementation information

Shared ASE information Decoded and ignored. Contents type list Supported. Only the following document types are accepted on

Decoded and ignored.

the response: FT AM-1, FTAM-2, FTAM-3, NBS-9. Only the abstract syntaxes required for those document types are accepted.

Initiator identity Supported. Used to set the Compaq user. Either the user name

(group_name.user_name), or user I D ( group_no, user_no) form

is allowed. Account Decoded and ignored. Filestore password Supported. Used in conjunction with initiator-identity parameter

to authenticate the Compaq user .

OSI/FTAM Responder Manual—425199-001

4-21

Compaq FTA M Responder Support of ISO FTAM Functions

Table 4-15. Compaq Support of Optional Parameters Received in Request PDUs (continued)

Parameters Level of Compaq Support

Diagnostic Decoded and ignored. Access passwords Decoded and ignored. Concurrency control Decoded and ignored. Create password Decoded and ignored. Activity identifier Decoded and ignored. Remove contexts Decoded and ignored. Define contexts Decoded and ignored. FADU lock Decoded and ignored.

Table 4-16 shows which optional parameters the Compaq responder can return in a response PDU.

File-Access and Security Considerations

Table 4-16. Compaq Support of Optional Parameters Sent in Response PDUs

Parameters Level of Compaq Support

Implementation information Not returned. Shared ASE information Not returned. Contents type list Returned with list reduced to document types supported by

responder .

Diagnostic Always returned when action-result parameter is not equal to

zero. Sometimes returned (informative diagnostic messages)

when action-result parameter equals zero. Charging Not returned. Attributes See “File-Attribute Mappings,” earlier in this section, for

details of support. FADU identity Not returned.

File-Access and Security Considerations

The VFS controls access to files through normal Guardian security mechanisms. Each FTAM association has a Compaq user ID associated with it. This user ID can assume two values, depending on whether the initiator-identity parameter is supplied in the FINITIALIZE request primitive. If the initiator-identity parameter is supplied, this parameter provides the user ID value. If the initiator-identity parameter is omitted, the user ID becomes the default user configured via the DEFUSER attribute for the VFS profile used by the responder. In either case, the password can be used. The filestore- password parameter of the F-INITIALIZE request primitive supplies the password used to authenticate the initiator identity. DEFUSER includes both the user ID and the

OSI/FTAM Responder Manual—425199-001

4-22

Compaq FTA M Responder Support of ISO FTAM Functions

password. For details on configuring a default user, refer to the OSI/FTAM Configuration and Management Manual.

The VFS actions allowed by the FT AM responder depend on the Guardian security (R W E P) for a file and the user ID for the association. For example, if you have Compaq purge access to a given file, the responder allows the FTAM delete-file action. Table 4-17 shows the Guardian access required for each FTAM VFS action.

Table 4-17. Guardian Access Required to Perform FTAM Actions

File-Access and Security Considerations

Guardian File Access

FTAM VFS Action

Read READ SHARED Insert WRITE EXCLUSIVE Repla ce WRITE (READ also

Exten d WRITE (REA D a l so

Erase WRITE EXCLUSIVE Read attributes None SHARED Change attributes WRITE EXCLUSIVE Delete file PURGE E XCLUSIVE

Note. The Com paq EXECUT E access fo r a fi le has no bear ing on FTAM access.

Required

required for ED IT files)

Guardian Exclusion Mode

EXCLUSIVE

Refer to the Compaq File Utility Program (FUP) Reference Manual, the Compaq

Enscribe Programmer’s Guide, and, if your files are Safeguard protected, the Compaq Safeguard Reference Manual for information about setting READ, WRITE, and PURGE

access to a file. Because the Compaq responder runs under the user ID for an association, Guardian

security and Safeguard security are both enforced. The responder cannot translate Safeguard security attributes into the FT AM access-control attribute. Therefore, when a remote application reads the attributes of a file that the Safeguard software protects, the access-control attribute indicates that no value is available. However, the Safeguard software still protects FTAM access to the file. Note that for such a file, the readattribute action does not tell you which file-access actions you may perform.

If a file-access request is rejected because the user ID does not meet the Guardian security requirements of the file, the responder sends a diagnostic message to the application, and also generates an EMS event message indicating a security violation on a file-access attempt.

Table 4-17 shows the exclusion mode that applies to each FTAM VFS action. Files open for read actions are open for SHARED access, allowing more than one user to open a file concurrently for reading. Files open for insert, replace, extend, and erase

OSI/FTAM Responder Manual—425199-001

4-23

Compaq FTA M Responder Support of ISO FTAM Functions

actions are open for EXCLUSIVE access; only one user at a time can open a file for writing. Where a combination of VFS actions are performed on a file, that file’s exclusion mode is EXCLUSIVE if any one of the actions qualify the file’s exclusion mode as EXCLUSIVE. If a file access is attempted on a file already opened for EXCLUSIVE access, the responder returns a diagnostic message to the remote application in the F-OPEN confirm.

File-Access and Security Considerations

OSI/FTAM Responder Manual—425199-001

4-24

Suggestions for Development of Remote Applications

When you write an FTAM application that uses the services of the Compaq responder, how you design, code, and debug it depends largely on the interface you are using on the remote system. However, there are some general things you should consider to make the most effective use of the Compaq FTAM responder. This section briefly discusses application development considerations for the design and programming phases of your project and for the troubleshooting phase.

Design and Programming

In designing your application, you should first consider interoperability with the other FTAM implementation you are using. In the coding phase, build error handling into your application, taking advantage of the information provided by the Compaq responder in diagnostic messages.

Interoperability

Before writing your application, you should read Section 2 of this manual, “Conformance and Interoperability,” which describes certain aspects of the Compaq FTAM responder that can affect its ability to interoperate with other FTAM implementations. Compare the information in Section 2 to the characteristics of the remote FTAM implementation. Pay special attention to the following:

Service classes, functional units, and attributes supported

•

Future-filesize limitations

•

Maximum-string-length limitations

•

String-significance values supported

•

Use of format effectors, including carriage return/line feed pairs

•

Character sets

•

Existing applications being adapted to use the Compaq responder might need some modifications in these areas.

Error Handling

To ensure that you receive as much information as possible about application problems if they occur, your applications should follow a good error-handling strategy. In general, you should check for status and error information after each FTAM operation you request in your program, and then provide some means of reporting errors.

OSI/FTAM Responder Manual—425199-001

5-1

Suggestions for Development of Remote Applications

The Compaq FT AM responder returns diagnostic messages to your application as specified by the ISO 8571 standard. In many cases, more information is returned than is required by the standard. Appendix A, “Compaq FTAM Responder Diagnostic Messages,” provides cause, effect, and recovery information about all diagnostic messages returned by the responder .

Some responder diagnostic messages also contain text of up to 256 characters in the Further Details field, providing additional information on the nature of the problem. For example, if you attempt to create a file and receive diagnostic message 3006 (file cannot be created), the Further Details text provides the file-system error number returned by Guardian when the file creation attempt failed. A Compaq problem solver or someone else with access to the Compaq system can look up this number in the Guardian Procedure Errors and Messages Manual to obtain information on what occurred and how to correct the problem.

As another example, if you attempt to open a file and receive diagnostic message 5036 (contents type inconsistent), the Further Details text “illegal MSL value” indicates that you attempted to open a file with a maximum-string-length parameter value outside the range supported by the Compaq FTAM responder, as described under “Mapping Between FTAM Contents T ypes and Compaq File Structures” in Section 4.

Troubleshooting

It is recommended that you check Further Details whenever you receive a diagnostic message. The Further Details text for many messages is self-explanatory and is not described in Appendix A.

Troubleshooting

To detect and eliminate problems in your remote application, you need to use whatever debugging tools are available on the remote system. However, there are also troubleshooting tools available on the Compaq system where the responder runs that can provide additional information about a problem. If you encounter interoperability problems or other problems that appear to originate on the Compaq system, you should work with a Compaq problem solver who has access to these tools.

The Compaq troubleshooting tools include the following:

The Event Management Service (EMS) log

•

Subystem Control Facility (SCF) interactive interface

•

The PTrace utility

•

The Event Management Service (EMS) on Compaq systems enables the Compaq problem solver to monitor problems and other significant events that occur during the operation of Compaq FT AM and other Compaq software. The FT AM responder and the APLMGR process that manages it generate event messages when they detect significant events, as do the processes in the underlying OSI/AS, OSI/TS, X25AM, and TLAM (or PAM for G06 and above releases) and TCP/IP subsystems. Event messages are logged to the console or displayed on a terminal as operator messages, which are described in the Operator Messages Manual.

OSI/FTAM Responder Manual—425199-001

5-2

Suggestions for Development of Remote Applications

The Compaq problem solver can use SCF commands to display configuration, status, and statistics information about the responder and APLMGR processes on the Compaq system. This information can sometimes provide clues to the cause of a problem, especially if an association is not yet established or if there are problems with system capacity or performance. In addition the STATUS SU command, which provides information about an FTAM association once it is established, can be especially useful in troubleshooting.

The P Trace (print trace) utility allows the Compaq problem solver to look at trace data generated with the SCF TRACE command. The TRACE command provides a log of message traffic between the various processes running on the Compaq system; PTrace displays the contents of these messages, including the types and contents of protocol data units (PDUs). Problems that can be detected using TRACE and PTrace include interoperability problems and various application protocol problems.

Additional guidance for the Compaq problem solver is provided in the troubleshooting section of the OSI/FTAM Configuration and Management Manual.

Troubleshooting

OSI/FTAM Responder Manual—425199-001

5-3

Suggestions for Development of Remote Applications

Troubleshooting

OSI/FTAM Responder Manual—425199-001

5-4

This section discusses considerations that are related to the configuration and management of the responder process and its VFS on the Compaq system, but that you might need to know when writing or using FTAM applications on the remote system. It covers the following topics:

•

Full details on FTAM configuration, management, and troubleshooting on the Compaq system are provided in the OSI/FTAM Configuration and Management Manual.

Responder Manager

Notes on configuration Fault tolerance Event messages

Notes on Configuration

Compaq FTAM (responder and APLMGR processes), the OSI/AS subsystem, the OSI/TS subsystem, and TLAM (or PAM for G06 and above releases) or X25AM or TCP/IP must be configured and running on the Compaq system before your application can communicate with the Compaq responder.

Because of the flexibility, and resultant complexity, of the configuration of underlying Compaq OSI layers, configuration errors are a common cause of problems in Compaq FTAM applications. The Compaq problem solver should pay special attention to checking the configuration of Compaq FTAM and the configuration of the underlying OSI layers (via Compaq OSI/AS).

The following aspects of configuration are important to writers and users of remote FTAM applications:

OSI address of responder

•

Initiator-identity and filestore-password parameters

•

Protocol error counter

•

Ways to increase responder capacity

•

Ways to increase responder performance

•

OSI Address of Responder

The assigned OSI address of each responder process is configured on the Compaq system. Remote applications must refer to this address when requesting the services of the responder. Several responders can be assigned to the same address.

OSI/FTAM Responder Manual—425199-001

6-1

Responder Manager

Initiator-Identity and Filestore-Password Parameters

The initiator-identity and filestore-password parameters in the F-INITIALIZE request correspond, respectively, to the Guardian user ID and password on the Compaq system. Optionally , a default user ID and password can be set up in the Compaq FT AM configuration, allowing remote applications access to the responder and its VFS without sending a user ID and password across the network.

If defaults are not configured, your application must specify a Guardian user ID that allows access to the files in the VFS, along with its associated password.

Pro tocol-Err o r Counter

A protocol-error counter, whose value is configurable, specifies how many FTAM protocol errors must occur before an event message is generated on the Compaq system. These event messages can alert the Compaq problem solver to interoperability problems.

Increas ing R esponder Capa city

The Compaq system manager can increase responder capacity by doing one of the following:

Increasing the maximum number of associations or attaches per responder process

•

Adding more responder processes

•

Increasin g R esponder Perfor mance

The system manager can often increase system performance or throughput by doing one or more of the following:

Configuring responder processes to run in different Compaq CPUs

•

Specifying a less fully occupied disk as the process swap volume

•

Adjusting the execution priority of various processes

•

Adjusting some of the parameters in the underlying OSI/AS configuration

•

Fault Tolerance

Compaq FTAM provides some fault tolerance if responder processes are configured to run as NonStop process pairs, consisting of a primary process and a backup process. When processes run as NonStop process pairs, the startup configuration information for the primary process is checkpointed. If a hardware or software component fails, the backup process takes over.

If the primary responder process fails, all outstanding Compaq FT AM associations, as well as the associated OSI/AS connections, are aborted. The remote initiator receives an F-P-ABORT indication. After a delay, the remote FTAM application can retry establishing the association.

OSI/FTAM Responder Manual—425199-001

6-2

Responder Manager

If the Compaq FTAM responder process is running as a NonStop process pair, the backup Compaq FTAM responder process takes over, and your remote application must reinitiate its Compaq FTAM associations. You or your application should then check and verify all previous work performed using the Compaq responder, correct inappropriate file states left from the component failure, and proceed as appropriate to the needs of your application.

The process of verifying work performed before a hardware or software component failure and recovering from unknown file states is different for every application. The main recovery strategies depend on the type of activity in progress during component failure:

Reading from a file

•

Writing to a file that your application created

•

Writing to a file that already existed

•

In the case of reading a file, no recovery is necessary. The Compaq responder does not modify files opened for reading only.

Event Messages

In the case of writing to a file, you should probably consider the file unusable. If you created the original file, the best recovery might be to delete the unusable file and recreate it. If you were writing to a file that you did not create and whose contents you cannot retrieve—from a file backup, for example—recovery might not be possible. You should design your application (making backups where necessary) with this in mind.

FTAM configurable files cannot be opened by the responder.

Event Messages

Whenever a Compaq process such as the FTAM responder detects an event that might affect its operation, it generates an event message describing the event. Such event messages can be related to hardware or software malfunctions, or to important changes in the state of a system component. Text (readable) versions of these event messages can be displayed as operator messages: for example, in an operator console log or on a terminal running the V iewPoint operations console application. For detailed information on the event messages sent by Compaq FT AM processes, see the OSIFTAM and OSIAPLMGR sections of the Operator Messages Manual.

Event messages generated by FTAM responder and APLMGR processes can alert the Compaq problem solver to the following kinds of problems:

System problems such as CPU failures, process failures, and unavailability of

•

system resources such as LCBs Interoperability problems that cause protocol-error thresholds to be exceeded

•

Configuration problems, such as mismatches between the common names and OSI

•

addresses configured in the APLMGR MIB and those in the OSI manager MIB

OSI/FTAM Responder Manual—425199-001

6-3

Responder Manager

Failure to establish an association with a Compaq responder due to an invalid

•

initiator ID or password Compaq responder virtual filestore (VFS) file-access failures due to file-system

•

errors or security violations

The responder also returns an event message whenever it starts or completes a file transfer, indicating whether or not the transfer was successful. This event can be monitored to verify completion of a transfer, so that your application can be notified when it can proceed with the next operation.

Event Messages

OSI/FTAM Responder Manual—425199-001

6-4

Compaq FTAM Responder Diagnostic Messages

The Compaq FTAM responder diagnostic messages can be returned in indications and confirms to an initiating FTAM implementation that requested the Compaq FTAM responder to execute a service that it cannot perform. They can also be returned to provide additional information on a successful action. Those troubleshooting FTAM applications using the Compaq responder can use these diagnostic messages to understand why a requested action has failed or to qualify a successful action. This appendix gives a detailed explanation of each diagnostic message, including cause, effect, and recovery information.

This appendix is intended for those who are writing, using, or troubleshooting an FTAM application running over a remote initiator that interoperates with the Compaq FTAM responder . In some cases, the problem lies on the initiating system; in other cases, the problem is on the Compaq system (for example, in the responder configuration). The recovery-action descriptions indicate whether an action is to be taken by the application or interactive FTAM user on the initiating system, or by the Compaq problem solver on the Compaq system. For problems that lie on the initiating system, it may be useful to notify the remote initiator site when error conditions occur in case the remote application does not check for returned diagnostics.

A table listing the diagnostic messages of a particular group precedes the detailed explanations. Each table lists the messages numerically by error identifier and includes information about the type, or severity of the error, and the observer and source of the error . Table A-1 lists the diagnostic message types and indicates the severity of each; Table A-2 lists valid error observer and error source values.

Table A-1. Diagnostic Message Types

Type Description

0 Informative: requires no recovery, and the current state of the file service is not

affected. Message provides information to qualify a successful action.

1 Transient: can reoccur if the sequence of events is repea ted and implies the failure

of the operation being performed.

2 Permanent: occurs every time the sequence of events is repeated and implies the

failure of at least the present operation being performed.

OSI/FTAM Responder Manual—425199-001

A-1

Compaq FTAM Responder Diagnostic Messages

Table A-2. Sources and Observers of Errors

Source/Observer Identifier Description

0 Source of the error cannot be identified. This identifier is not valid for

the observer. 1 Initiating file-service user (initiating application). 2 Initiating file protocol machine. 3 Service supporting the protocol machines. This identifier is not valid

for the observer. 4 Responding file protocol machine. 5 Responding file-service user (VFS or file system).

The detailed descriptions of the diagnostic messages that follow each summary table are also listed numerically by the error identifier. In addition to the information provided in this appendix, responder diagnostic messages might also contain text of up to 256 characters in the Further Details fields, providing additional information on the nature of the problem.

General FTAM Diagnostic Messages

Table A-3 displays the general error identifiers returned by the Compaq FTAM responder.

Table A-3. General FTAM Diagnostic Messages

Identifier Type Observer Source Reason

1255Unspecific responder error 7051Unspecific initiator error 8144Subsequent error 9 2 4,5 4,5 Temporal insufficiency of

resources

Unspecific responder error

Cause. Either the combination of a small maximum-string-length value and a large PDU size caused the incoming data to exceed the responder ’s data buffer capacity, or an internal software error has occurred in the responder.

OSI/FTAM Responder Manual—425199-001

A-2

Compaq FTAM Responder Diagnostic Messages

Effect. The responder aborts the association. If the data buffer capacity was exceeded for the reason given under “Cause,” the Further Details field contains the message smaller PDU or larger MSL needed.

Recovery. If the Further Details field indicates that a smaller PDU or a larger MSL is needed, the application or FTAM user should decrease the number of strings sent in one PDU. This can be done either by sending a smaller number of strings per PDU or by sending larger strings. Sending larger strings may require increasing the value of the maximum-string-length parameter in the application’s requests. For further information, refer to “Limits on Small String-Length Values With Large PDUs” in Section 4.

Otherwise, the application or FTAM user should retry the operation. This can be a transient condition. If the condition persists, the Compaq problem solver should trace the responder and follow the standard procedures at the Compaq site for contacting the appropriate support personnel. These procedures might involve contacting the local Compaq support analyst. For details on how to trace the responder, refer to the SCF Reference Manual for FTAM and APLMGR and the Compaq PTrace Reference Manual.

General FTAM Diagnostic Messages

Unspecific initiator error

Cause. The responder received a change-attribute indication containing a null proposed change-attribute list.

Effect. This is an information-only diagnostic message. The service is completed; no attributes are changed.

Recovery. No action is necessary.

Subsequent error

Cause. In a grouped request, one of the requests after the one on which the responder returns this diagnostic message has encountered an error condition.

Effect. The responder rejects the grouped request. Recovery. The application programmer or FTAM user should determine which request

in the group failed and correct the problem.

Temporal insufficiency of resources

Cause. The responder has attempted to allocate memory for a data control block, but the memory table does not have sufficient space to satisfy the request.

Effect. The responder aborts the association.

OSI/FTAM Responder Manual—425199-001

A-3

Compaq FTAM Responder Diagnostic Messages

Recovery. The application or FTAM user should retry the operation. This can be a transient condition. If the condition persists, the Compaq problem solver can start another FTAM responder process to balance the load across multiple responder processes. For details on how to configure and start additional responders, refer to the

SCF Reference Manual for FTAM and APLMGR and the OSI/FTAM Configuration and Management Manual.

Access request violates local security

Cause. A file has been selected with requested access that violates the file system security. A file-system security violation (48) was detected.

Effect. The responder rejects the select or create request and generates a security-fail event (event number 21).

Recovery. The application or FTAM user can either retry with the correct select-request or create-request parameters, or use initiator-ID and filestore-password values that support the requested access; or the Compaq problem solver can change the local Compaq security for the file.

Protocol and Supporting Service-Related Diagnostic

Messages

Protoco l and Supporting Servic e-Rela ted Diagnostic Messages

Table A-4 displays the diagnostic error identifiers caused by protocol errors or improper requests for supporting services.

Table A-4. Protocol and Supporting Service-Related Diagnostic Messages

Identifier Type Observer Source Reason 1001 242Unsupported parameter values 1002 242Mandatory parameter not set 1007 242Unspecific FTAM protocol error 1009 242FTAM protocol error, functional

unit error 1011243Lower-layer failure 1015 242Illegal grouping sequence 1016 242Grouping threshold violation 1017 242Specific PDU request

inconsistent with current

requested access

OSI/FTAM Responder Manual—425199-001

A-4

Compaq FTAM Responder Diagnostic Messages

1001

Unsupported parameter values

Cause. A request contained a parameter value that the Compaq FTAM responder did not support: for example, the override parameter did not equal one of the values supported by the Compaq responder, the maximum-string-length value was not in the range expected by the Compaq responder or was not specified (the ISO FTAM default, unbounded, is not supported by the Compaq responder), or the protocol version specified in the initialize request was not version 1.

Effect. The responder does not perform the requested operation. Recovery. The application or FTAM user should retry the request providing parameter

values that the responder supports. For information about parameters that the Compaq FTAM responder supports, see Section 4.

1002

Protocol and Supporting Service-Related Diagnostic

Messages

Mandatory parameter not set

Cause. The responder received a request PDU that did not contain all the required parameters, or the request was malformed. Any request PDU that has mandatory parameters can cause the responder to return this diagnostic message.

Effect. The responder aborts the association. Recovery. The application or FTAM user should retry the request with all mandatory

parameters. To determine which parameters are mandatory, refer to the FTAM PDU definitions for FTAM in ISO 8571-4.

1007

Unspecific FTAM protocol error

Cause. The responder detected a protocol error. One possible error on a write is a data value that does not conform to the maximum-string-length value established for the file.

Effect. The responder aborts the association. If the protocol error threshold (a value set via the THRESHOLD attribute during responder configuration) has been exceeded, the responder generates a protocol-error-threshold event (event number 22). If the problem was an attempt to write a data value that does not conform to the maximum-stringlength value for the file, the Further Details field contains the message string length violates the MSL.

Recovery. This can be an interoperability problem. Verify that the initiator is issuing a valid request to the responder. The Compaq problem solver can do this by tracing the responder and verifying the protocol. For information on tracing, refer to the SCF

Reference Manual for FTAM and APLMGR and the OSI/FTAM Configuration and Management Manual.

OSI/FTAM Responder Manual—425199-001

A-5

Compaq FTAM Responder Diagnostic Messages

1009

FTAM protocol error, functional unit error

Cause. The responder received a service request that requires a functional unit that was not negotiated when the association was established.

Effect. The responder rejects the request. Recovery. The application or FTAM user should establish a new association and

negotiate the required functional units.

1011

Lower-layer failure

Cause. The responder detected an error in communicating with a TAPS process. Effect. The responder aborts the association.

Protocol and Supporting Service-Related Diagnostic

Messages

Recovery. The application or FTAM user should discard the association context, reestablish the association, and retry the operation. If the problem persists, the Compaq problem solver should verify that the TAPS process is configured properly and trace the responder . The Compaq problem solver should examine the status, error code, error subcode, and original error information displayed in the trace record. This information should help identify the problem being detected by the TAPS process.

For information on configuration and on tracing the responder, refer to the OSI/FTAM

Configuration and Management Manual and the SCF Reference Manual for FTAM and APLMGR.

1015

Illegal grouping sequence

Cause. The grouped service contains an illegal primitive, or this particular grouping is not allowed for the negotiated service class.

Effect. The responder does not perform the grouped service, no services are performed, and the responder aborts the association.

Recovery. The application or FTAM user should retry using a valid group for the negotiated service class.

1016

Grouping thre shold violation

Cause. The threshold—the number of primitives that must be completed successfully before the group can be considered successful—is greater than the number of services in the group, or the threshold for a group associated with any service class other than file

OSI/FTAM Responder Manual—425199-001

A-6

Compaq FTAM Responder Diagnostic Messages

access is less than the number of services in the group. (Only the file-access service class allows a threshold of less than the number of services in the group, allowing a group of primitives to provide some service even if one of the primitives fails.)

Effect. The responder aborts the association. Recovery. The application or FTAM user should discard the association context,

reestablish the association, and retry the operation with a group having the proper value for the threshold parameter.

1017

Specific PDU request inconsistent with the current requested access

Cause. A service has been attempted that is inconsistent with the current requested access.

Effect. The responder does not perform the service. Recovery. The application or FTAM user should reselect the file with the required

requested access and retry. If the problem persists, the Compaq problem solver can use the SCF TRACE command and the PTrace utility to troubleshoot the problem. For more information on tracing and troubleshooting, refer to the OSI/FTAM Configuration and Management Manual.Association-Related Diagnostic Messages

Association-Related Diagnostic Messages

Table A-5 displays the diagnostic error identifiers related to managing associations.

Table A-5. Association-Related Diagnostic Messages

Identifier Type Observer Source Reason

2002 241Unsupported service class 2003 241Unsupported functional unit 2013 042Checkpoint window error

(unsupported) 2014 032Communications ftam-quality-

of-service not supported 2015 251Initiator identity unacceptable 2016 041Context management refused 2018 051Contents type list cut by

responder 2020 251Invalid file store password 2021 241Incompatible service classes

OSI/FTAM Responder Manual—425199-001

A-7

Compaq FTAM Responder Diagnostic Messages

2002

Unsupported service class

Cause. The responder received an initialize request for the unconstrained service class. The Compaq FT AM implementation does not support the unconstrained service class.

Effect. The association is not established. Recovery. The application or FTAM user should specify a supported service class on

the initialize request. For a list of service classes that Compaq FTAM supports, see Section 4.

2003

Unsupported functional unit

Cause. Requested functional units were inconsistent with the service class negotiated. Effect. The association is not established.

Association-Related Diagnostic Messages

Recovery. The application or FTAM user should specify functional units that are consistent with the proposed service class on the initialize request.

2013

Checkpoint window error (unsupported)

Cause. The checkpoint-window parameter of the initialize request was set to a value that the responder does not support. The responder expects a value of 1.

Effect. This is an information-only diagnostic message returned in the initialize response. The association is established.

Recovery. No action is required.

2014

Communications ftam-quality-of-service not supported

Cause. The responder does not support the value of the FTAM quality-of-service parameter on the initialize request. The responder supports only a value of “no recovery” for this PDU parameter.

Effect. This is an information-only diagnostic message returned in the initialize response. The association is established.

Recovery. No action is required.

OSI/FTAM Responder Manual—425199-001

A-8

Compaq FTAM Responder Diagnostic Messages

2015

Initiator identity unacceptable

Cause. The initiator-identity parameter in the initialize request was invalid, or it was omitted and there was no default user ID/password configured for the responder.

Effect. The association is not established. The responder generates the passwordfailure event (event number 20).

Recovery. Either the application or FTAM user should retry with a valid initiator identity, or the Compaq problem solver should configure the responder to have a default user ID/password. Change the VFS profile for the responder to define a DEFUSER attribute. Refer to the ALTER PROFILE command description in the SCF Reference Manual for FT AM and APLMGR.

2016

Context management refused

Association-Related Diagnostic Messages

Cause. The remote initiator has set the presentation-context-management parameter to true on the F-INITIALIZE service. The Compaq responder does not support the presentation-context-management parameter.

Effect. This is an information-only diagnostic message. The association is established. Recovery. No action is necessary.

2018

Contents type list cut by responder

Cause. The responder detected one or more inconsistent or unsupported presentation contexts in the contents-type-list on the initialize service.

Effect. This message is a warning. The responder disregards the contents types that it does not support or are not valid and retains those that are. The association is established with a partial contents-type-list.

Recovery. The application or FTAM user should investigate the resulting list to determine if needed contents types are still included. If not, interoperability of the two FTAM implementations is limited and might prevent you from using FTAM to accomplish your purpose. The responder supports only the FTAM-1, FTAM-2, FTAM-3, and NBS-9 document types.

2020

Invalid filestore password

Cause. The password on the initialize request is invalid, or an invalid default password is configured for the Compaq responder.

OSI/FTAM Responder Manual—425199-001

A-9

Compaq FTAM Responder Diagnostic Messages

Effect. The association is not established. The responder generates the password-fail event (event number 20).

Recovery. For the first cause, the application or FTAM user should retry the request using a valid password; for the second cause, the Compaq problem solver should correct the default password by reconfiguring the DEFUSER attribute in the responder’s VFS profile on the Compaq system.

2021

Incompati ble service classes

Cause. The responder can return this diagnostic message in two conditions:

In examining the initiate indication, the responder detected either a value of

•

unconstrained for the service class or no value at all for the service class. The remote initiator requested services requiring the management service class, but

•

the management service class was not negotiated on the F-INITIALIZE request.

Selection-Related Diagnostic Messages

Effect. For the first cause, the association is not established. For the second cause, the responder aborts the association.

Recovery. The application or FTAM user should reestablish the association negotiating values for service class and functional units that are valid for the responder and that support the requests being made.

Selection-Related Diagnostic Messages

Table A-6 displays the diagnostic error identifiers generated while selecting a file or negotiating a service.

OSI/FTAM Responder Manual—425199-001

A-10

Compaq FTAM Responder Diagnostic Messages

Table A-6. Selection-Related Diagnostic Messages

Value Type Observer Source Meaning

3000 255File name not found 3002 255Initial attributes not possible 3004 255Non-existent file 3005 255File already exists 3006 255File cannot be created 3007 255File cannot be deleted 3012 255File busy 3013 255File not available 3016 255Access control inconsistent 3018 051Initial attributes altered

Selection-Related Diagnostic Messages

3020 055Override selected existing file 3021 055Override deleted and recreated

file with old attributes 3022 055Create override deleted and

recreated file with new attributes 3027 251Bad attribute value 3028 251Requested access violates

permitted actions 3029 251Functional unit not available for

requested access 3030 055File created but not selected

3000

File name not found

Cause. The file requested on the select service could not be found. File-system error 11 was returned.

Effect. The service fails. Recovery. The application or FTAM user should try again using a correct file name or

the name of an existing, accessible file.

3002

Initial attributes not possible

Cause. The responder did not support an attribute specified on a create request.

OSI/FTAM Responder Manual—425199-001

A-11

Compaq FTAM Responder Diagnostic Messages

Effect. The service fails. Recovery. The application programmer or FT AM user should check the attribute values

and determine which attribute the responder does not support, and then retry the request without specifying the unsupported attribute in the create request. If the problem persists, the Compaq problem solver can use the SCF TRACE command and the PTrace utility to troubleshoot the problem. For more information on tracing and troubleshooting, refer to the OSI/FTAM Configuration and Management Manual.

3004

Non-exist ent file

Cause. A file has ceased to exist after being selected. The VFS has received an operating system error 11 in attempting to access a previously selected file.

Effect. The service fails. Recovery. The application or FTAM user should either retry the operation specifying a

file that exists, or try again after the Compaq problem solver has replaced the file.

Selection-Related Diagnostic Messages

3005

File already exi sts

Cause. A create request has been sent with the override parameter set so that file creation fails if the file already exists, and the file already exists in the file system. The CREATE procedure returns an error indicating that the file already exists and cannot be created.

Effect. The service fails. Recovery. The application or FTAM user should purge the file before attempting to

create it, or change the override parameter in the create request to any valid value other than the one specifying that file creation fails if the file already exists.

3006

File cannot be created

Cause. The application or FTAM user attempted to create a directory list (NBS-9), the CREATE procedure has failed to create a file, or one or more of the contents-type parameters specified in the create request is not supported on the responder (for example, the application or FTAM user might have specified a string-significance value that is invalid for the document type).

Effect. The file is not created. The Further Details field identifies the related filesystem error number.

Recovery. For an interpretation of the file-system error number, refer to the Compaq Guardian Pr ocedure Errors and Messages Manual.

OSI/FTAM Responder Manual—425199-001

A-12

Compaq FTAM Responder Diagnostic Messages

3007

File cannot be deleted

Cause. The application or FTAM user attempted to delete a directory list (NBS-9), or the PURGE procedure has failed.

Effect. The file is not deleted. The Further Details field identifies the related filesystem error number.

Recovery. For an interpretation of the file-system error number, refer to the Compaq Guardian Pr ocedure Errors and Messages Manual.

3012

File busy

Cause. An operating system file-in-use error (12) has occurred. Effect. The service fails.

Selection-Related Diagnostic Messages

Recovery. The application or FTAM user should wait until the file is accessible and retry the operation.

3013

File not availab le

Cause. An unexpected operating system error has occurred, or the application or FTAM user tried to access an SQL table that is not organization relative.

Effect. The service fails. Recovery. There is no recovery. The specified file cannot be accessed.

3016

Access control inconsistent

Cause. The application or FTAM user specified an access-control element containing more than an action list in the initial-attributes parameter of a create request. The responder uses only the action-list field of an access-control element.

Effect. The service fails, and the responder aborts the association. Recovery. The application or FTAM user should reestablish the association and retry

the create operation, specifying only an action list in the access-control element.

OSI/FTAM Responder Manual—425199-001

A-13

Compaq FTAM Responder Diagnostic Messages

3018

Initial attributes altered

Cause. The application or FTAM user attempted to create a file with a future-filesize value greater than one gigabyte. The Compaq FTAM responder does not support files larger than one gigabyte.

Effect. This is an information-only diagnostic message. The file is created with a future-filesize value of one gigabyte.

Recovery. No action is necessary.

3020

Override sele cted existing file

Cause. The override parameter on the create request was set so that an existing file is to be selected, and the responder received a create request for a file that already exists.

Selection-Related Diagnostic Messages

Effect. This is an information-only diagnostic message. The service is completed, and the old file is selected.

Recovery. No action is necessary.

3021

Override deleted and recreated file with old attributes

Cause. The responder received a create request naming a file that already exists, with the override parameter set so that the existing file is to be deleted and a new file created using the attributes of the deleted file.

Recovery. This is an information-only diagnostic message. The service is completed, and the file is created with old attributes. The file creation date is updated.

Recovery. No action is necessary.

3022

Create override deleted and created file with new attributes

Cause. The responder received a create request for a file that already exists, with the override parameter set so that the existing file is deleted and a new file created using the attributes specified in the initial-attributes parameter.

Effect. This is an information-only diagnostic message. The service is completed. The old file is deleted and a new file is created with a new set of attributes.

Recovery. No action is necessary.

OSI/FTAM Responder Manual—425199-001

A-14

Compaq FTAM Responder Diagnostic Messages

3027

Bad attribute value

Cause. An invalid value was detected in an attribute on the create or select service. This message is caused if the filename attribute cannot be decoded or is invalid for the file system.

Effect. The service fails. Recovery. The application or FTAM user should correct the value for that attribute and

retry. For possible limitations on attribute values that the Compaq FTAM responder supports, see Section 4.

3028

Requested access violates permitted actions

Cause. The requested access specified on a select request was inconsistent with the contents-type attribute specified when the file was created. The responder can return this error in two cases:

Selection-Related Diagnostic Messages

nAny file other than an FTAM-2 file was selected for insert access. Insert access is

•

allowed only on FTAM-2 files. nAn FTAM-2 file was selected for replace or extend access, or both. Replace and

•

extend access is not allowed on FTAM-2 files.

Effect. The service fails. Recovery. The application or FTAM user should retry with requested-access values that

are valid for the contents type.

3029

Functional unit not available for requested access

Cause. The negotiated functional units were inconsistent with the requested access type specified on the select or create service.

Effect. The service fails. Recovery. The application or FTAM user should establish a new association providing

the required functional units.

3030

File created but not selected

Cause. The create request succeeded in creating a Guardian file, but the select regime has not been established because the requested access was not correct.

OSI/FTAM Responder Manual—425199-001

A-15

Compaq FTAM Responder Diagnostic Messages

File-Management-Related Diagnostic Messages

Effect. The file is created, but not selected. The state-result parameter of the create confirm returns a failure indication.

Recovery. The application or FTAM user should issue a select request specifying the correct requested access.

File-Management-Related Diagnostic Messages

Table A-7 displays the diagnostic error identifiers that result from either file system errors or improper management of read-attribute or change-attribute requests.

Table A-7. File-Management-Related Diagnostic Message

Identifier Type Observer Source Reason

4001 255Attribute cannot be read 4002 255Attribute cannot be changed 4003 255Attribute not supported 4005 251Bad attribute value 4006 055Attribute partially supported

4001

Attribute cannot be read

Cause. A file-system error occurred during an attempt to read the attributes of a file. Effect. The service fails. Recovery. The application or FTAM user should retry the service.

4002

Attribute cannot be changed

Cause. A change-attribute request has been attempted on a directory file (NBS-9), the application or FTAM user specified an access control element containing information other than the action list (such as concurrency-access and identity) in the attributes parameter of a change-attribute request, or a file-system error occurred while the application or FT AM user attempted to change the attribute of a file.

Effect. The service fails. Recovery. For the first cause, the application or FTAM user should not attempt to

change the attributes of a directory file (NBS-9). For the second cause, the application or FTAM user should retry the change-attribute request specifying only the action list in the access control element. For the third cause, the application or FTAM user should retry the operation.

OSI/FTAM Responder Manual—425199-001

A-16

Compaq FTAM Responder Diagnostic Messages

4003

Attribute not supported

Cause. Either a read-attribute request including the private attributes was issued, or an attempt was made to change an attribute that cannot be changed. Compaq FTAM does not support private attributes.

Effect. The service fails. Recovery. No recovery is possible in the case of the read-attribute service. The

Compaq FTAM responder does not support private attributes. In the case of the change-attribute service, the application or FTAM user should restrict

requests for change to the following attributes: filename, future-filesize, and accesscontrol.

4005

Bad attribute value

Access-Related Diagnostic Messages

Cause. The responder has received a change-attribute request with an invalid attribute value, or the file name was invalid for the Guardian 90 operating system.

Effect. The service fails. Effect. The application or FTAM user should retry the service with a valid attribute

value.

4006

Attribute partially supported

Cause. The responder received a change-attribute request that includes the storageaccount attribute. The Compaq FTAM responder only partially supports this attribute.

Effect. This is an information-only diagnostic message. The request is completed. Recovery. No action is required.

Access-Related Diagnostic Messages

Table A-8 displays the diagnostic error identifiers that can occur during the execution of file-type or processing-mode requests.

OSI/FTAM Responder Manual—425199-001

A-17

Compaq FTAM Responder Diagnostic Messages

Table A-8. Access-Related Diagnostic Messages

Identifier Type Observer Source Reason

5000 251Bad FADU (unspecific) 5001 251Bad FADU - size error 5003 251Bad FADU - poorly specified 5004 251Bad FADU - bad location 5005 055FADU does not exist 5008 255FADU not available for writing 5011255FADU cannot be inserted 5012 255FADU cannot be replaced 5015 255Operation not available 5022 255Processing mode unsupported

Access-Related Diagnostic Messages

5023 251Processing mode inconsistent 5024 255Access context not available 5026 255Bad write (unspecific) 5027 255Bad read (unspecific) 5028 255Local failure (unspecific) 5030 255Local failure - data corrupted 5032 255Future filesize exceeded 5036 251Contents type inconsistent 5040 255FADU locking not available on

file

5000

Bad FADU (unspecific)

Cause. The FADU-ID parameter on a read or write request is invalid. Effect. The responder cancels the service, and the association is left in a data-transfer

idle state. Recovery. The application or FTAM user should issue a cancel response, and then

reissue the read or write request with a valid FADU ID.

OSI/FTAM Responder Manual—425199-001

A-18

Compaq FTAM Responder Diagnostic Messages

5001

Bad FADU - size error

Cause. The application or FTAM user tried to access a nonexistent column in an SQL table.

Effect. The responder cancels the service, and the association is left in a data-transfer idle state.

Recovery. The application or FTAM user should issue a cancel response and then reissue the request, verifying that the number of data elements in the FADU sent is less than or equal to the number of columns in the table.

5003

Bad FADU - poorly specified

Cause. The responder has received an erase request for an FTAM-2 document type and the FADU-ID parameter was not begin, or in the case of an FT AM-1 or FTAM-3 document type, the FADU-ID parameter was not first. The responder can also return this diagnostic message if an invalid data type was specified for the data to be written to an SQL table, or if an attempt was made to write to an SQL table using the UA access context instead of the FA access context.

Access-Related Diagnostic Messages

Effect. The responder cancels the service, the association is left in the file-open regime, and the file is left in an unknown state.

Recovery. The application or FTAM user should issue a cancel response, close the file, and reissue the erase request with the valid FADU ID.

5004

Bad FADU - bad location

Cause. The responder has received a read or write request with an invalid FADU-ID parameter. The responder returns this diagnostic message when the application or FTAM user attempts to access an empty file or locate a FADU corresponding to a record before the beginning or after the end of the file; or when, while reading a file, the responder receives an unexpected end-of-file message (specific to SQL tables and Enscribe relative files). The responder can also generate this diagnostic message if it receives an SQL error of -5 or if, while attempting to locate the current position in the file, it receives a file-system error.

Effect. The responder cancels the service, and the association is left in a data-transfer idle state.

Recovery. The application or FTAM user should issue a cancel response, and then reissue the read or write request with a valid FADU ID.

OSI/FTAM Responder Manual—425199-001

A-19

Compaq FTAM Responder Diagnostic Messages

5005

FADU does not exist

Cause. The responder received a read or erase request for an empty FTAM-2 relative file.

Effect. In the case of a read, the responder cancels the service. In the case of an erase, the responder issues a negative erase confirmation.

Recovery. This is an information-only diagnositic message. Nothing happened.

5008

FADU not availab le for writing

Cause. A write request has been sent to a directory file (NBS-9). Effect. The responder cancels the service, and the association is in a data-transfer idle

state.

Access-Related Diagnostic Messages

Recovery. The application or FTAM user should issue a cancel response. Do not retry; you cannot write to an NBS-9 file.

5011

FADU cannot be inserted

Cause. The responder received an open request with a processing mode of insert, and the requested access on the select service did not include insert, or the processing mode of insert is not allowed for the document type selected.

Effect. The responder rejects the request. Recovery. The application or FTAM user should either open the file with a processing

mode compatible with the services selected, or reselect the file so that it will allow FADU insertion.

5012

FADU cannot be replaced

Cause. The responder received an open request with a processing mode of replace, and the requested access on the select service did not include replace; or the processing mode of replace is not allowed for the document type selected.

Effect. The responder rejects the request. Recovery. The application or FTAM user should either open the file with a processing

mode compatible with the services selected, or reselect the file so that it will allow FADUs to be replaced.

OSI/FTAM Responder Manual—425199-001

A-20

Compaq FTAM Responder Diagnostic Messages

5015

Operation not available

Cause. Either the VFS has attempted to open a file, but the operating system OPEN procedure has failed, or a write request has been issued without the FADU operation set to insert, replace, or extend.

Effect. In the case of an open, the responder rejects the request. In the case of a write, the responder cancels the service.

Recovery. If an open failed, the application or FTAM user should check the other diagnostic messages returned to determine why the open failed. If a write failed, the application or FTAM user should send a cancel response and retry the data transfer using the correct F ADU operation value.

5022

Processing mode unsupported

Access-Related Diagnostic Messages

Cause. The responder received a write request after simplifying an FTAM-2 document type to an FTAM-1 document type in response to an open request.

Effect. The responder rejects the request and aborts the association. Recovery. The application or FTAM user should discard the association context,

reinitialize an association, and proceed with the intended operation. The responder simplifies document types only on read operations. Therefore, applications must issue only a read request after an open request that simplifies the document type.

5023

Processing mode inconsistent

Cause. The responder received an open request specifying a processing mode that is inconsistent with the requested access from the select request.

Effect. The responder rejects the request. Recovery. The application or FTAM user should either reissue the open request with a

processing mode consistent with the requested access specified on the select, or reselect the file specifying a requested access that allows the requested processing mode.

5024

Access context not available

Cause. The responder received a read request specifying an access context that it does not support. The responder supports only flat all data units (FA), for FTAM-2 files, and unstructured all data units (UA), for FT AM-1 and FTAM-3 files.

OSI/FTAM Responder Manual—425199-001

A-21

Compaq FTAM Responder Diagnostic Messages

Effect. The responder cancels the service, and the association is left in a data-transfer idle state.

Recovery. The application or FTAM user should issue a cancel response and then reissue the read request with the correct FADU operation. Make sure the document type opened supports the access context. Refer to Table A-9 for valid access contexts.

Table A-9. Access Contexts by Document Typ

Access-Related Diagnostic Messages

Document Type

FTAM-2 FA, UA FTAM-1,

FTAM-3, and NBS-9

Access Context

5026

Bad write (unspecific)

Cause. A local file-system error other than an end-of-file message has occurred on the write service.

Effect. The responder cancels the service, and the association is left in a data-transfer idle state.

Recovery. The application or FTAM user should issue a cancel response and then retry the application. If the error persists, the file is probably corrupt and cannot be accessed. In this case, the Compaq problem solver should perform the file recovery operations normally used at the site; then the application or FTAM user can retry the application.

5027

Bad read (unspecific)

Cause. A local file-system error other than an end-of-file message has occurred on the read service. One possible cause of this error is that one of the records in an FTAM-3 file with a string-significance value of fixed contained a string whose length was smaller than the maximum-string-length value. This could occur because the file was created outside FTAM, because it was corrupted in some way, or because the wrong file was specified.

Effect. The responder cancels the service. Recovery. The application or FTAM user should issue a cancel response. The

application or FT AM user should ensure that the correct file is specified; the file must satisfy the string-length rules described under “Maximum-String-Length Checking of Data Values” in Section 4. If the application specified the correct file, the application or FTAM user should retry the application; if the error persists, the file is probably corrupt and cannot be accessed. In this case, the Compaq problem solver should perform the

OSI/FTAM Responder Manual—425199-001

A-22

Compaq FTAM Responder Diagnostic Messages

file recovery operations normally used at the site; then the application or FTAM user can retry the application.

5028

Local failure (unspecific)

Cause. A local file-system error occurred as a result of one of the following actions:

F-ERASE error occurred while the responder was attempting to erase data from a

•

file. F-LOCATE error occurred while the responder was attempting to locate a FADU.

•

F-CLOSE error occurred while the responder was attempting to close a file.

•

F-READ error occurred while the responder was attempting to locate the FADU to

•

be read in an FTAM-2 file. F-WRITE error occurred while the responder was attempting to locate the FADU to

•

which to write in an FTAM-2 file, or while attempting to erase data from an FTAM1 or FTAM-3 file with a FADU operation of replace.

Access-Related Diagnostic Messages

Effect. If the failure occurs during a read or write service, the responder cancels the service, and the file is left in an unknown state. If the failure occurs during any other action, the responder rejects the request.

Recovery. If a failure occurs during a read or write service, the application or FTAM user should issue a cancel response and retry the operation. If the failure occurs during any other action, the application or FTAM user should retry the operation.

5030

Local failure - data corrupted

Cause. The VFS attempted to open a corrupted EDIT file. Effect. The responder rejects the request. Recovery. The application or FTAM user should retry the request using a different file,

delete the file and create a new one, or notify the Compaq problem solver of the file condition and find out if an alternative file can be used to access the information. If an alternative file is available, the application or FTAM user should retry the request using that file.

5032

Future filesize exceeded

Cause. The VFS attempted to write data to a file and exceeded the maximum file size. Effect. The responder issues a cancel request and cancels the data transfer.

OSI/FTAM Responder Manual—425199-001

A-23

Compaq FTAM Responder Diagnostic Messages

Recovery. The application or FTAM user should send a cancel response, close the file, and use the change-attribute service to increase the value of the future-filesize attribute of the file.

5036

Contents type inconsistent

Cause. A service has been attempted without specifying a valid document type (for example, if the application or FT AM user tries to perform an FTAM-2 simplification of an SQL file); the contents type was inconsistent with the Guardian file structure, specifically the file type value; the application or FTAM user attempted to open a file specifying a maximum-string-length value outside the supported range; or the application or FTAM user specified an unsupported value of the universal-class parameter.

Effect. The responder rejects the request. Recovery. The application or FTAM user should retry specifying a valid document

type—one that is consistent with the file type of the Guardian file being accessed—and a supported universal-class value.

Access-Related Diagnostic Messages

For information about document types and contents types, refer to Section 4. Refer to Table A-10 for FTAM contents type and Guardian file structure equivalents:

Table A-10. FTAM Contents Types and Equivalent Guardian File Structures

FT AM Contents Type Guardian File Structure

FTAM-1 Edit U FTAM-2 Relative

SQL table

FTAM-3 Fixed-length binary

Variable-length binary Unstructured Non-SQL key-sequenced Non-SQL entry-sequenced

NBS-9 Directory (∗.∗.DIRLIS) -

∗

The following va lues are possible for file type:

U = Enscribe unstructured R = Relative E = Entry-sequenced K = Key-sequenced

Guardian File Type

R R

E E U K

∗

OSI/FTAM Responder Manual—425199-001

A-24

Compaq FTAM Responder Diagnostic Messages

Recovery-Related Diagnostic Messages

5040

FADU locking not available on file

Cause. The Compaq FTAM responder received a request with a FADU-lock parameter on a read or write service. The Compaq FTAM responder does not support the FADUlock parameter.

Effect. The responder cancels the request. The association is left in a data-transfer idle state.

Recovery. The application or FTAM user should issue a cancel response, and then retry the read and write service omitting the FADU-lock parameter .

Recovery-Related Diagnostic Messages

Table A-11 displays the diagnostic error code that may be generated during recovery operations

Table A-11. Recovery-Related Diagnostic Messages

Identifier Type Observer Source Meaning

6010 251Recovery mode not available

6010

Recovery mode not available

Cause. Recovery has not been set to none (0) on the open request to the responder. Effect. The responder rejects the open request because none (0) is the only recovery

value Compaq supports. Recovery. The application or FTAM user should set recovery to none (0) and retry the

open operation.

OSI/FTAM Responder Manual—425199-001

A-25

Compaq FTAM Responder Diagnostic Messages

Recovery-Related Diagnostic Messages

OSI/FTAM Responder Manual—425199-001

A-26

Glossary

The following glossary defines terms used both in this manual and in the other Compaq FTAM manuals. Not all terms listed here are used in this particular manual.

abstract syntax. A standardized method of describing data structures that is independent of the way they are represented in data transmission. An abstract syntax uses a set of primitive elements defined by an abstract syntax notation such as ASN.1, defines ranges of values for the primitive elements, and defines ways of combining these elements. See also transfer syntax and ASN.1.

Abstract Syntax Notation-1. See ASN.1. access-context parameter. A parameter used for read transfers within the data-transfer

regime to specify the file structure by which information in the file is accessed. Possible structures for Compaq FTAM are flat all data units (for FTAM-2 files) and unstructured all data units (for FTAM-1, FTAM-2, and FTAM-3 files). See UA and FA.

access-control attribute. A file attribute that contains the information to determine whether file access is allowed or denied. The attribute value is set when the file is created. You can alter the access-control attribute using the change-attribute action.

ACSE (Association Control Service Element). An application service element (ASE) in the Application Layer of the OSI Reference Model. The ACSE exists within an application entity and enables other ASEs to establish and release associations. It is accessible to users of OSI/AS through the APS procedures. See also ASE or Application Layer.

action-result parameter. In effect, a summary of the ISO FTAM diagnostic parameter. The action-result value success (ZFTM-VAL-ACTION-SUCCESS for the FTAM API) indicates that the requested service was performed successfully. The action-result value failure (ZFTM-VAL-ACTION-F AILURE for the FTAM API) indicates that the service was not performed successfully. If any one of the diagnostic messages returned indicates a failure, the value of action-result must be failure. See also state-result parameter.

activity attributes. Dynamic attributes specific to an individual FTAM association. These attributes are both created and discarded during the life of an association and may change as the status of the association changes. See also file attributes.

AE title. See application entity title. APDU (application protocol data unit). See PDU. API. See application program interface (API). APLMGR (Compaq OSI/Application Manager). The Compaq subsystem that performs

management functions for Compaq FTAM. The APLMGR subsystem consists of two entities: the APLMGR process and the management information base (MIB). There is only one APLMGR per FTAM subsystem.

application. A user program that uses services provided by products such as Compaq FTAM. The program accesses layers of the OSI Reference Model through the top layer

OSI/FTAM Responder Manual—425199-001

Glossary-1

Glossary

(Application Layer) to manipulate files on remote computer systems. For Compaq FTAM, applications can be written in C or T AL.

application entity. The part of an application process that interacts with its peer entity in a remote application process. In an OSI application, the application entity is the part that represents the communication functionality necessary for interoperation.

application entity title (AE title). The structured identifier that identifies an application entity to the OSI network. The AE title is passed as a parameter in the ACSE A-ASSOCIATE request and returned in the A-ASSOCIATE response. See application entity.

Application Layer. Layer 7 of the OSI Reference Model. This layer provides the interface between user programs (application processes) and the OSI network. Layer 7 includes the standards for services such as file transfer, electronic mail, and terminal access.

Application Manager. See APLMGR. application name. The Compaq OSI/AS term for a reference name used to look up an

OSI address in the local OSI/AS management information base (MIB). In Compaq FTAM terminology, this name is called the common name. See common name.

application program interface (API). The set of functions or procedures that permits user programs to communicate with the Compaq NonStop Kernel. For Compaq FTAM, the API consists of FTM, APS, and MFM procedures used in FTAM programming. The Compaq FTAM API also includes the data definitions provided in the ZFTMDDL file and all language-specific files derived from ZFTMDDL. See also APS procedures, FTM procedures, and MFM procedures.

application service element. See ASE. APS (application, presentation, and session) procedures. A set of procedure calls,

provided by Compaq as part of the OSI/AS subsystem, providing application programs with access to the services of ACSE (in the Application Layer), the Presentation Layer, and the Session Layer. The names of the APS procedures all begin with the letters APS. The APS procedures are defined in the EXTDECS0 and CEXTDECS files. The APS procedures, together with the definitions in the ZAPSDDL file, constitute the OSI/AS API. A subset of the APS procedures is accessible from, and must be used with, the FTAM API. See also API.

arc. A directed link between two nodes in a hierarchical file. arc length. The number of node levels in a file hierarchy from the root node to a given

node. For example, the arc length of an FTAM-2 document is always 1. ASE (application service element). A set of functions to be performed—such as file

transfer, mail service, or transaction processing—along with all the elements necessary to perform that kind of work, to support a particular application.

ASI (additional service information). An internal data format used by Compaq FTAM. ASI format is displayed in some of the USER and ASN1 trace records. The Compaq initiator and responder processes transform ASI into the transfer syntax negotiated for the association, and vice versa.

OSI/FTAM Responder Manual—425199-001

Glossary-2

Glossary

ASN.1 (Abstract Syntax Notation-1). The type and value syntax or notation language for representing semantics of protocol that is described in ISO 8824. The Basic Encoding Rules (ISO 8825) standard defines a set of encoding rules that can be applied to values of types defined using the notation specified in ISO 8824. See also abstract syntax.

association. A connection between Application Layer entities. See connection. Association Control Service Element. See ACSE. attach. An operation performed by a Compaq OSI subsystem, on behalf of an

application, to wait for an incoming associate or connect indication from a remote entity. attribute. An identifiable characteristic of an object. For example, two attributes of an

FTAM file are its name and its date and time of creation. In DSM, two attributes of a process are the location of its code file and its execution priority. See also file attributes and activity attributes.

attribute group. One of the four groups of file attributes defined by ISO FTAM. They are the kernel group, which must be supported by all FTAM implementations; the security group and the storage group, which are negotiated during association establishment; and the private-use group, which is also negotiated but whose definition is outside the scope of ISO FTAM.

backup CPU. The central processing unit (CPU) number of the Compaq processor on which the backup process will run. See backup process.

backup opener. The backup process that has an open to an FTAM initiator or responder process. See backup process.

backup process. In a Compaq NonStop system, a process that is identical to the primary process and is created at the same time as the primary process. These two processes act as a NonStop process pair. The backup process takes over if the primary process fails. See primary process.

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 Compaq FTAM, an identifier of a connection endpoint for a given FT AM association. Use of the CEPI for an association allows transfer of information to a remote FTAM entity.

checkpoint. On a Compaq 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.

OSI/FTAM Responder Manual—425199-001

Glossary-3

Glossary

code file. A Guardian file containing the object code that you must run to create the specified process.

collector An EMS process that accepts event messages from subsystems and logs them in the event log. See EMS. Compare distributor.

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.

Compaq FTAM (File Transfer, Access and Management). The Compaq implementation of the ISO FTAM standard that provides the ability to manipulate files between local and remote file stores on a network.

Compaq NonStop Kernel. The operating system, which consists of the core and system services. The operating system does not include any application program interfaces.

Compaq NonStop Tools. The utility programs that perform everyday activities, including editing, formatting, restoring, backing up, sorting, spooling, binding, compiling, and installing.

Compaq OSI/AS. See OSI/AS. Compaq OSI/FTAM. See Compaq FTAM. Compaq OSI/TS. See OSI/TS. compatibility distributor. An EMS distributor process that filters event messages

according to fixed (rather than user-specified) criteria, obtains text for these messages and writes the text to the standard operating system destinations. See also distributor.

conditional parameter. (1) In a protocol data unit (PDU), a parameter that is present under certain circumstances, for example, if another parameter has a given value. (2) In the Compaq FT AM 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.

conformance. The satisfaction, by an implementation of an OSI standard, of both static and dynamic conformance requirements, consistent with the capabilities stated in the

OSI/FTAM Responder Manual—425199-001

Glossary-4

Glossary

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. 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 contentstype 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 Compaq 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 Compaq 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 Compaq FTAM, the default document types requested are FTAM-1, FTAM-2, FTAM-3, and NBS-9.

D-series system. A system running any Dxx version of the Compaq NonStop Kernel, such as D10 or D20.

Data Definition Language. See DDL. Data Link Layer. Layer 2 in the OSI Reference Model. This layer packages data for

transmission across the network and ensures that the data arrives at the next layer without any errors.

data-transfer regime. The regime established after successfully gaining read or write access to an FTAM file. In the data-transfer regime, you can send or receive data, and you can abort the association. See also FT AM regime, file-selection regime, and file-open regime.

DDL (Data Definition Language). A Compaq language for defining data. DDL builds a dictionary from the definitions, translates the definitions into File Utility Program

OSI/FTAM Responder Manual—425199-001

Glossary-5

Glossary

(FUP) commands, and generates object-definition source code in a variety of programming languages.

default user (DEFUSER). An attribute of a Compaq virtual filestore (VFS) profile that allows access to files in the Compaq 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 FT AM diagnostic messages.

Distributed Systems Management. See DSM. distributor. An EMS process that distributes event messages from event logs to

requesting management applications, to Compaq NonStop Kernel destinations, or to a collector . Contrast collector.

document type. An FTAM definition, defining the structure of and method of access to a file. Compaq 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 Compaq to manage NonStop systems, Expand networks, and Compaq communications products. These tools include the V iewPoint console application, the Subsystem Control Facility (SCF) for data communications subsystems, the Subsystem Programmatic Interface (SPI), the Event Management Service (EMS), the PT race (print trace) utility, tokenoriented programmatic interfaces to the management processes for various Compaq subsystems, and other products.

EMS (Event Management Service). A facility provided by Compaq for event collection, event logging, and event distribution on Compaq 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 FT AM 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.

end-of-file marker. See EOF. enhanced-file-management functional unit. A functional unit that adds the

modification of file attributes to the capabilities of the limited-file-management functional unit. Seelimited-file-management functional unit.

OSI/FTAM Responder Manual—425199-001

Glossary-6

Compaq OSI-APLMGR D43, OSI-FTAM D43 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

What’s New in This Manual

About This Manual

Functional Overview

Compaq FTAM Services

FTAM Applications

Management Interfaces

Architectural Overview

The Responder and Underlying Subsystems

The Responder and the File System

Conformance and Interoperatility

Conformance

Interoperabili ty

Basic Characteristics of FTAM Implementations

Limitations on Value of Future-Filesize A ttribute

Document Types and Related Par ame te rs

Data-Transfer Considerations

Presentation Encoding of FTAM PDUs and Data

Compaq FTAM Responder Operation

Responder Structure

Responder Data Flow

Supported Functions

Service Classes

Functiona l Un it s

Attribute Groups

Attribute Support

Document Types

Mapping Between FTAM Contents Types and Compaq File Structures

Create Mappings

Select-Open Mappings

File-Attribute Mappings

Kernel Group File Attributes

Storage Group File Attributes

Security Group File Attributes

Supported and Unsupported Optional Parameters

File-Access and Security Considerations

Design and Programming

Interoperability

Error Handling

Troubleshooting

Responder Manager

Notes on Configuration

OSI Address of Responder

Initiator-Identity and Filestore-Password Parameters

Pro tocol-Err o r Counter

Increas ing R esponder Capa city

Increasin g R esponder Perfor mance

Fault Tolerance

Event Messages

General FTAM Diagnostic Messages

Protoco l and Supporting Servic e-Rela ted Diagnostic Messages

Association-Related Diagnostic Messages

Selection-Related Diagnostic Messages

File-Management-Related Diagnostic Messages

Access-Related Diagnostic Messages

Recovery-Related Diagnostic Messages

Glossary