Preface

Purpose

This guide provides the information you need to use HP FTAM/9000 interactively.

This guide does not supply information for installing or configuring HP FTAM/9000 on your local system. For that information, refer to the Installing and Administering HP FTAM/9000 manual.




	NOTE: This guide assumes that HP FTAM/9000 is correctly installed and configured for use. This includes locally configuring the address and alias of each remote host you need to work with.

This guide also does not supply information for programmatic use of FTAM. For programmatic use, refer to the HP FTAM/9000 Programmer's Guide (B1033-90014) and the HP FTAM/9000 Reference Manual (B1033-90004).

Audience

Both new and experienced users of FTAM will want to use this manual to make full use of FTAM features.

New FTAM programmers may also want to review chapter 5 to learn the basic concepts of file protection under FTAM. Programmers will also want to refer to the HP FTAM/9000 Programmer's Guide and the HP FTAM/9000 Reference Manual for detailed programming information.

Terms

The following terms are used in this guide:

Initiator	The person, process, or system that requests an FTAM transaction is called the initiator.
Responder	The process or system to which an FTAM request is directed is called the responder.
Shadow file	Every HP FTAM/9000 file has an associated shadow file, which contains attribute information not stored by the HP- UX file system.
Local host	The system you are logged into is the local host.
Remote host	Every system on the network (except the local host) is a remote host.
Access control	FTAM provides additional access control mechanisms over those inherent in HP-UX. FTAM access control governs the actions that are permitted on a file, granting different users different subsets of the available actions.
Concurrency control	Concurrency control governs whether and how multiple users can access the file. This helps maintain data integrity.
Connection	FTAM transactions between different hosts require a connection between the hosts. This connection is analogous to a telephone connection, over which two people can communicate.
File store	Every computer system has a system for storing information, which is called its file store. Different systems use different file stores, depending on the vendor and model.
Virtual File Store	FTAM defines a generic, abstract file store, which is shared by all FTAM implementations. This generic file store is called FTAM's Virtual File Store, or VFS .

Conventions

The table below explains the typographic conventions used in this manual.

Notation	Description
`computertext` or `computertext`	Computer font is used for on-screen prompts and messages, for responses to user commands, and what you type in.
Boldface	Boldface type is used when a term is defined.
italics	Italic type is used for emphasis and titles of manuals and publications, and to represent a variable in a syntax statement, such as target_file.
[ ]	An element inside brackets in a syntax statement is optional. When elements inside brackets are separated by a vertical bar (\|), you can select any one or none of these elements; vertical bars are omitted for multiple command options.
. . .	A horizontal ellipsis in a syntax statement indicates that a previous element may be repeated. For example: [options][filename]...
Key	This font is used to indicate a key on the computer's keyboard. When two or more keys appear together with a dash between them, such as CTRL-C, press those keys simultaneously to execute the command. Note that most user commands end with an implied Enter or Return keystroke. If there is no user entry at a prompt, the Enter or Return key indicates that no other keys are pressed.

Preface

Technical documentation

» Table of Contents

» Index