FTAdmin

OSSC
FTAM Administrator Guide
With Error Recovery Option

FT-820S and FT-825S
for AIX® Operating Systems
FTAM Administrator Guide
Part Number 1080118-33-E
September 1994
Copyright © 1994 IBM Corporation. All rights reserved. No part of this publication may be repro-
duced, transmitted, transcribed, stored in a retrieval system, or translated into any language, in
any form or by any means, electronic, mechanical, photocopying, optical, magnetic, or otherwise,
without prior written permission from IBM. Printed in the United States of America.
The information furnished herein is believed to be accurate and reliable. However, no responsi-
bility is assumed by IBM for its use, nor for any infringements of patents or other rights of third
parties resulting from its use.
Retix and the OPENNetworking Company are registered trademarks of Retix.

AT&T is a registered trademark of American Telephone and Telegraph Company.
UNIX is a registered trademark of UNIX System Laboratories, Inc., in the USA and other
countries.
AIX is a registered trademark of IBM Corporation.
X/Open is a trademark of X/Open Company Limited.
All other trademarks are the property of their respective owners.
Contents
Introduction v
Required materials v
About this manual vi
Conventions used in this manual vii
1 Overview 1
FT-820 overview 2
FT-825 overview 3
FT-820 document file types 6
Destination attributes 7
2 Support Files 9
What is an application entity? 12
Application entity table file 12
Utility configuration file 17
Filestore configuration file 39
Filestore audit trail file 50
Utility audit trail file 53
3 Filestore 57
Configuring FTAM 57
Database lock manager utility: lockmgr 59
Starting the filestore 60
FT-820 filestore utility: ffs 61
iii
4 Maintaining FT-820 67
FT-820 databases 67
Initialize FT-820 databases utility: finit 68
Display attributes utility: fda 70
Reinitializing the FT-820 databases 72
Update attributes utility: fua 74
5 FT-820 Security 77
Authentication file 77
Security driver 79
File and directory permissions 79
Setting up the AIX password file 80
A Error Messages 83
Database error messages 84
Filestore error messages 87
FTAM/ERPM filestore error messages 95
Operating system error messages 108
Utility error messages 108
B References 115
Glossary 117
Index 123
iv Contents
Introduction
T he OSSC FT-820 product provides the ability to access and

manage files on remote filestores. FT-820 implements the
International Organization for Standardization (ISO) file transfer,
access, and management (FTAM) protocol specification. FT-825 is a
separately available OSSC product that provides the ability to
recover from errors in file transfers initiated by FT-820. FT-825
implements the ISO error recovery protocol machine (ERPM) for the
FTAM protocol specifications. The FT-820 and FT-825 products are
designed for systems that use the AIX networking environment.
FT-820 also implements the ISO association control service element

(ACSE), presentation, and session protocol specifications. It uses
these three protocols to communicate between the local and remote
system. It also uses STREAMS, a set of AIX operating system
facilities that greatly enhance high-speed networking
communications.
Required materials
FT-825 requires FT-820. The following materials are required when
using the OSSC FT-820 product:
• A workstation running the AIX operating system with

STREAMS.
• A supporting transport protocol provider (available from

OSSC).
v
The protocol stack supporting the FT-820 product must be
compatible with either AT&T’s transport library interface (TLI)
You may find the following materials helpful when administering

FT-820 and FT-825 on a network:
• AT&T Network Programmer’s Guide

• AT&T System V Interface Definition, Volume 3
• AIX STREAMS Primer
Refer to Appendix B, “References,” for ordering information.
About this manual

This manual is intended for administrators who need to configure
and maintain FT-820. This manual also presents information about
the FT-825 error recovery product. If you are not using the FT-825
error recovery product, ignore those sections of the manual that
discuss it.
The manual is organized as follows:
Chapter 1, “Overview,” introduces you to the FT-820 and FT-825

products, including their role in a network, their structure, and the
types of files they handle.
Chapter 2, “Support Files,” discusses the files required by FT-820

and FT-825 for proper functioning. This includes the application
entity table file, which assigns an easy-to-use name to each user or
filestore; the utility and filestore configuration files, where you
assign values that control how the FT-820 and FT-825 utilities and
filestore work; and several other files.
Chapter 3, “Filestore,” describes how to start and stop the filestore,

in foreground or background, as well as how to use the lock manager
utility and how to set the number of users.
Chapter 4, “Maintaining FT-820,” describes how to use and maintain

the FT-820 databases, including the table of attributes.
Chapter 5, “FT-820 Security,” discusses the use of the authentication

file to control access to the FT-820 filestore, and the use of the
security driver to check effective user and group IDs.
vi Introduction
Appendix A, “Error Messages,” lists error messages that can be
generated by FT-820 and FT-825 and the filestores with which FT-820
communicates.
Appendix B, “References,” lists the references that you may use to

learn more about issues relating to this product, file transfer, access
and management (FTAM), and Open Systems Interconnection (OSI).
Conventions used in this manual

Source code and the names of functions, programs, files, or
directories appear as shown here:
The osid.cfg file must contain at least these minimum

parameters:
TP4 device=/dev/cots tp_provider=OSSC-1
Commands and prompts that are displayed on the screen or stored

on a computer are shown in the following typeface:
Enter the name of the file:
Text you must enter is shown in the following typeface:
Type frm
Text you substitute with actual text you type is italicized:
Type filename
Replace filename with the appropriate filename.
Text you can optionally type is enclosed in square brackets:
frm [–d] [–i] [–p] [–Pf!n[!p]] [–v] f1...
Keys that you press on your keyboard are represented with small
capitals:
Press ESC, type start, and then press RETURN.
Conventions used in this manual vii

viii Introduction
1 Overview
F T-820 allows you to access and transfer files between your local
AIX operating system and any other system supporting OSI FTAM.
The FT-825 error recovery protocol machine (ERPM) product

provides the ability to recover/restart failed file transfers from a
negotiated point without the need to restart the transfer from the
beginning. FT-825 requires FT-820; it cannot be used separately from
FT-820.
The FT-820 product is made up of two main components that

cooperate in managing files:
• A set of initiator utilities that allow users to list, copy, move, or

delete files that are stored on a filestore.
• A filestore (also called a responder) that stores a collection of

files. The filestore responds to requests from the initiator
utilities.
There is also an FT-825 utility that allows you to delete dockets,

which are files created during file transfers.
This manual describes how to set up the filestore portion of FT-820.

For information on the FT-820 and FT-825 utilities, see the OSSC
FTAM User Guide.
Communication services between the initiator and responder are

provided by an OSI transport product. You can use the OSSC LAN
and WAN transports or a transport from another vendor. Refer to
1
the OSSC OSI Application Developer’s Guide if you intend to use a
non-OSSC transport with the TLI stack.
A transport provider capability (TPC) mechanism is also provided to

tailor the session layer to work with non-OSSC lower layers, when
the FT-820 is running over another vendor’s stack using the TLI
interface. The TPC mechanism is described in the OSSC OSI
Application Developer’s Guide.
The OSSC FT-820 product is compatible with the OSI TLI stack
configuration:
• The TLI stack, which uses the AT&T transport layer interface
(TLI).
The FT-820 product provides all stack components, above the
transport layer, that are required to run FT-820 (and FT-825)
with the TLI.
FT-820 overview
FT-820 is an implementation of the ISO protocol standard for file
transfer, access, and management (FTAM). This standard establishes
the conventions by which files, and the information necessary to
describe them, are to be used during OSI-conformant network
communications. This standardization allows a user to manipulate
files on remote computer systems by creating a virtual filestore with
standardized information that describes the actual files stored in the
AIXoperating system’s file system. For each actual file on the
responder system, the virtual filestore has descriptive information in
FTAM standardized format. This descriptive information includes,
among other file attributes, who is allowed to access or manipulate
each file.
When a user at an FTAM initiator system uses FTAM to request

access to a file, the information about the request is translated into
the standardized FTAM format and then communicated to the
FTAM filestore, which searches its information for the virtual file.
FT-820 checks that the user has privileges to access the file, and, if so,
the filestore accesses the actual file in the AIX file system, and
completes the user’s request.
2 Chapter 1 • Overview
FT-825 overview
FT-825 implements the ISO protocol standard for the error recovery
protocol machine (ERPM) in FTAM. When FT-820 is used over an
unreliable network, or used to transfer files to or from an unreliable
system, a number of errors can occur. These errors can include:
• Breaking the FTAM association.

• Errors while reading or writing data (without losing the
association).
• Files being destroyed.
The ERPM establishes the conventions by which such errors in a file

transfer can be recovered/restarted from a negotiated point. When a
negotiated point is used, the transfer does not have to be restarted
from the beginning.
Both the initiator of the file transfer utilities and the responder
maintain information about each current file transfer so that in the
event of an error during transfer, this information can be used to
recover from the error. These pieces of information are called dockets.
FT-820 and 825 components

The FT-820 product includes both an initiator FTAM protocol
machine and a responder FTAM protocol machine that allow certain
files on remote or local systems to be listed (directory-format files),
copied, moved, and deleted. The files are categorized into FTAM
document file types, which are described in “FT-820 document file
types,” on page 6.
The FT-820 initiator FTAM protocol machine supports the set of four
user utilities (fcp, fls, fmv, frm) to allow users to copy, list, move,
and remove files.
The FT-820 responder FTAM protocol machine creates, organizes,

and controls the virtual filestore, and communicates with the actual
AIX file system.
FT-825 provides an initiator and responder ERPM protocol machine.

The ERPM uses the file services provided by the FTAM protocol
machines and creates a new layer between the initiator utilities or the
responder, and their FTAM protocol machines. This layer is
responsible for handling errors.
FT-825 overview 3
OSI protocols
In addition to FTAM, three other OSI protocols are included as part
of the FT-820 product: association control service element (ACSE),
presentation, and session.
• ACSE establishes and maintains a virtual connection with a

remote system, either the initiator or responder.
• Presentation provides for the representation of information that

is communicated to or referred to by application processes.
• Session provides a means by which the dialogue between

application processes is organized and synchronized. It
manages the data between application processes.
When FT-820 runs over the TLI stack, it uses these modules (shaded
in Figure 1.1) to communicate between the FT-820 protocol machine
and the transport service provider.
FT-820
initiator
FT-820
initiator FT-820
utilities responder
FT-820
filestore
ERPM ERPM
initiator responder
protocol protocol
machine machine
(FT-825) (FT-825)
FTAM FTAM
initiator responder
protocol protocol
machine machine
ACSE ACSE
presentation presentation
session session
user space
kernel
(including AIX file system
Note. Shaded components are used only in the TLI stack configuration.
ERPM block is only present if FT-825 has been compiled into FT-820 code.
Figure 1.1 FT-820 and FT-825 combined components
Required OSI services

FT-820 needs a transport provider to transport its data to the remote
system over the network media. Transport service is not provided as
part of the FT-820 product, but LAN and WAN products are
available from OSSC. The transport services may be supplied by
either:
• A OSSC transport product (for example, LAN Transport for AIX

or WAN Transport for AIX).
FT-825 overview 5
• Another vendor’s transport provider. If FT-820 is using a
non-OSSC transport provider, it requires buffer reformatting.
Refer to the OSSC OSI Application Developer’s Guide for
information on how to reformat buffers with the OSSC
transport provider capability compiler.
FT-820 also needs OSI protocol services to carry information to the

transport provider.
TLI stack
This stack uses the AT&T transport layer interface (TLI) to
communicate between FT-820 and OSI transport services. This stack
can run in the AIX environment.
In this system configuration, FT-820 uses its own ACSE,

presentation, and session protocol services. Communication passes
from the FT-820 protocol machines to the ACSE, presentation, and
session modules to the TLI to the transport provider.
FT-820 document file types

Users can copy, list, move, and delete four types of files with the
FT-820 product. FT-820 converts these document file types into text
and binary files formatted for the AIX operating system. The
following table also describes a fifth file type, the NBS-9 directory
type; the only action you can perform on NBS-9 files is to list them.
Table 1.1 FT-820 document file types
File type Data type Description
FTAM-1 Unstructured text A file of this type contains a number of lines of

text. Each line of text is less than or equal to 134
characters long and must be terminated with a
<CR><LF> pair. This file type may only be read or
written as a whole. This file may be extended.
A file of this type consists of a single,
undifferentiated series of text characters. This file
type may only be read or written as a whole, since
there are no subdivisions of the file contents.
When you transfer a file of this type, FT-820
automatically converts the format characters and
delimiters (line feeds and carriage returns)
between the format used with the AIX operating
system and standard FTAM format.
Table 1.1 FT-820 document file types (continued)
File type Data type Description
FTAM-2 Structured text A file of this type contains lines of text. Each line
is less than or equal to 134 characters long. Each
line of text is independently addressable by
record number. The file may be read by record
number or read or written as a whole. This file
may be extended.
When you transfer a file of this type, FT-820
automatically converts the format characters and
delimiters (line feeds and carriage returns)
between the line-differentiated format used with
the AIX operating system and standard FTAM
format.
FTAM-3 Simple binary A file of this type contains a string of bytes. Each
string must be less than or equal to 512 bytes
long. This file may only be read or written as a
whole, since there are no subdivisions of the file
contents.
When you transfer a file of this type, FT-820 does
not convert its contents.
NBS-9 Directory A file of this type contains a number of directory

entries. Each directory entry contains a list of file
attributes (such as the size of file, the date on
which it was created, etc.). Under the AIX
operating system, directories are interpreted as
files of this type. This file may only be read as a
whole.
FT-820 can list the contents of an NBS-9 file with
the fls utility.
NBS-10 Random binary A file of this type contains a string of bytes. Each
string of bytes may be independently addressed
by byte offset and length. This file may be read as
an FTAM-3 file. This file may be read or written as
a whole or by byte offset by length.
Destination attributes
When you copy or move a file to a filestore, the destination file is
created with a set of FTAM file attributes. Depending on the
situation, some of these file attributes may be derived from the
source file, from default values, or from values specified in the utility
configuration file, .ftInit.
Destination attributes 7
For attributes that are not set by the .ftInit configuration file,
Appendix B in the OSSC FTAM User Guide contains a description of
how the destination file attributes are determined when users use
fcp or fmv to copy or move a file to an FTAM filestore.
2 Support Files
Support files for the FT-820 product include the following:
• The __AETABLE__ file associates an easy-to-read, common

English name with each filestore and each user.
• The utility configuration file is an optional file that contains

configurable parameters for requests issued by the FTAM
initiator.
• The filestore configuration file defines some access parameters

and defines pathnames and filenames for filestore support files.
• The attributes database contains file attributes for all the files in
an FTAM filestore, including document type, permitted actions,
and concurrency keys.
• The concurrency control database contains the current locks on

each file that FTAM selects or opens in the filestore.
• The authentication file contains a list of network addresses for

users who are allowed to access the filestore.
• The filestore audit trail file contains accounting information

about the activity of the filestore.
• The utility audit trail file contains accounting information about

the progress of an invoked initiator utility.
• The AIX operating system’s password file functions as it

normally does in the AIX operating system environment.
9
If you are using FT-825 file recovery, docket files are created on the
local system and the filestore. Dockets contain information needed to
recover file transfers. In most cases dockets are removed by the
system automatically, but they can be manually removed using the
fdocket utility, if necessary. For more information about the
fdocket utility, see the FTAM User Guide.
__AETABLE__ file
This file contains network addresses and their associated user-
friendly names. These names and addresses are accessed when users
on the network use the FTAM application interface, or use the fcp
copy, fls list, fmv move, or frm remove utilities.
Utility configuration file

This file specifies information about access, accounting, concurrency
control, security, and certain other characteristics of newly created
files. It provides a standard set of parameters that describe certain
requests you issue using the fcp, fls, fmv, or frm commands. The
use of this file is optional.
Filestore configuration file

This file contains operating parameters for the filestore, such as
security and access controls and information identifying the
filestore. This file is accessed when you start the FTAM filestore or
use the filestore support utilities (fda, finit, fua, and ffs).
Attributes database
This file contains information about the characteristics of all files
stored on the filestore. This file is used when the FTAM filestore
accesses files that it has created. This file is accessed when you start
the FTAM filestore (ffs) or use the filestore support utilities (fda,
finit, and fua).
Concurrency control database

This file is used when you try to access a filestore that is running
multiple processes, or that is networked with other filestores.
Whenever a user attempts to access a file on such a filestore, the
system must make an entry in this database to indicate that the file it
is accessing is in use. This avoids conflicts when more than one
system wants access to the same file.
10 Chapter 2 • Support Files

Authentication file
When users attempt to access the FT-820 filestore, the network
address of the user’s system is checked against a list of network
addresses in the authentication file, which contains valid addresses
of systems that are allowed to access the FT-820 filestore.
If the user’s address is found, the user is allowed access to the

filestore. If the user’s address is not found, the user is denied access
to the filestore.
The authentication file is described in Chapter 5, “FT-820 Security.”
Filestore audit trail file

This file contains a record of all filestore activities, with information
that is useful for accounting purposes, such as type of event, time of
event, connection ID, initiator ID, AIX operating system user name,
address of the initiating system, and error message (if any). The
filestore audit trail file is discussed in more detail in “Filestore audit
trail file,” on page 50.
Utility audit trail file

This file contains a record of all utility activities, with information
such as the type of request, time of request, connection ID, and
address of the filestore(s). If an error is detected, the particular
confirmation on which the error occurred is recorded along with the
error message.
AIX password file

This file is used when users attempt to access the FT-820 filestore.
At every attempted access, each user’s initiator ID (login name) and

password are compared to the login names and passwords listed in
the password file on the system running the FT-820 filestore.
If the user’s initiator ID and password are found, the user is allowed
access to the filestore; otherwise, the user is denied access to the
filestore.
How to set up the AIX operating system’s password file on the

system on which the FT-820 filestore runs is described in Chapter 5,
“FT-820 Security.”
11
What is an application entity?
An FTAM application entity is a process that requests or performs file
services. Application entities need to be uniquely identified within
an OSI network. You identify application entities in the FT-820
application entity table (__AETABLE__), which is described in the
next section.
Examples of FTAM application entities include the FT-820 utilities

(fcp, fls, fmv, and frm) and the FTAM filestores that users on your
network access with the FT-820 utilities.
Application entity table file

You use the application entity table __AETABLE__ to uniquely
assign user-friendly names to applications within your network.
These names are converted to addresses and titles used by the
network. The __AETABLE__ file may be used by other OSSC
applications besides FTAM, so you should always be careful when
altering or deleting information in this file.
Entries in __AETABLE__ list the addresses, titles, and protocols for

applications on the local and remote systems.
__AETABLE__ contains two major sections:
• The first section identifies the local addresses of the FT-820

utilities (fcp, fls, fmv, and frm) for each user and of
applications using the application programming interface. In
this section, you list the application entity names and the
corresponding addresses for each user. Note that you must
include the initiating application entity name ANON for users
who do not set the FTAMLOCAL environment variable. Refer to
the OSSC FTAM User Guide for a description of the FTAMLOCAL
environment variable.
• The second section of __AETABLE__ identifies the applications

in your network (like the OSSC FT-820 filestore) that users will
access. For FT-820, the table should include all remote filestores
you wish to access with the FT-820 utilities.
Each of the major sections in __AETABLE__ contains one entry per

line for each application entity. Each entry contains four elements:
• The name of the application (the application entity name).

• The title of the application. The title consists of two
components, the application process title and the application
entity qualifier.
• The application’s address. The address contains four

components: the network address, the TSAP selector, the SSAP
selector, and the PSAP selector. The network address identifies
the system on which the application runs while the other
components identify a particular application on the system.
• The type of protocol used. The last two elements identify the
type of network service and transport class used to
communicate with the application.
Sample __AETABLE__ file

A typical __AETABLE__ file is shown below:
comment symbol application application entity SSAP network

process network address identifier service
tittle type
#AETABLE
#Initiating application entities
#AE_NAME AP_TITLE QUAL NETWORK ADDRESS TSAP SSAP PSAP NS TC

#======== ============= ==== ============================= ==== ==== ==== == ==
ANON {1 3 9999 1 7} 0 /4700040000000000000000000001/0000/0000/0000 0 4
fred_pc {1 3 9999 1 7} 0 /4700040000000000000000000002/8001/4201/1234 1 0

wilma_pc {1 3 9999 1 7} 0 /4700040000000000000000000003/8002/4202/1234 1 0
#Filestore application entities
fstore1 {1 3 9999 1 7} 0 /4700040000000000000000000004/1001/4201/1234 0 4

fstore2 {1 3 9999 1 7} 0 /4700040000000000000000000005/1002/4202/1234 0 4
application application TSAP PSAP transport

entity name entity qualifier identifier identifier class
Note. The comment symbol (#) marks the beginning of a comment.

Text that follows this symbol is ignored. You must place the
comment symbol in the first column of any line that you wish to be
ignored.

Elements of the __AETABLE__ file
Elements of the sample __AETABLE__ file are described in the
following table. Each element in the __AETABLE__ must be
separated from the next element by at least one space.
Element Description
AE_NAME The application entity name is a simple name you assign to the
(Mandatory) system on which an application or application entities are located.
You can use any combination of characters in an application
entity name (up to a maximum of 39 characters).
Note. You must include the initiating application entity name
ANON in this section if you do not set the environment variable
FTAMLOCAL. When the initiator encounters ANON upon reading
the __AETABLE__ at setup, it generates a unique combination of
TSAP, SSAP, and PSAP for itself. The FTAMLOCAL environment
variable is discussed in the FTAM User Guide.
AP_TITLE The application process title (AP title) is used with the QUAL field
(Mandatory) to uniquely identify every application entity (like FTAM or other
OSI application protocols) in the world. The National Institute of
Standards and Technology (NIST) has not, at present,
designated an organization to administer AP titles. For now, NIST
has asked that organizations use the fixed values:
{1 3 9999 1 7} for AP_TITLE.
QUAL The application entity qualifier is used, with AP_TITLE, to identify

(Mandatory) an application process. The NIST has not, at present, designated
an organization to administer application entity qualifiers. For
now, NIST has asked that organizations use the fixed value 0 for
QUAL.
NETWORK The network address is the NSAP address assigned to the

ADDRESS system on which an application entity is found. The combination
(Mandatory) of the network address with the TSAP, SSAP, and PSAP make
up the presentation address, which uniquely locates an
application entity on the global OSI network.
You need to get a filestore’s address from the administrator of the
filestore. For local users (initiating application entities), the
network address in __AETABLE__ must be the network address
of the system on which the user is located.
This element begins with a slash (/).
Note. Any NSAP address format is valid here (OSINET is
shown), but for each application entity, the format of its address
in __AETABLE__ must match the source system’s address
format.

Element Description
TSAP The TSAP identifier is a four-digit value that identifies what

(Mandatory) transport entity is used by an application. For initiating application
entities, you can specify any value for the TSAP. OSSC
recommends that, if you are running FT-820 with the TLI, the
TSAP for initiating application entities be set to a NULL value,
represented by //. This ensures that the TLI will generate a
unique TSAP value. IYou must begin this element with a slash (/).
SSAP The SSAP identifier is a four-digit value. You can specify any
(Mandatory) value for initiating application entities. However, OSSC
recommends that you set SSAPs for initiating application entities
to /0000. SSAPs for filestore application entities are assigned by
the person who is responsible for administering the filestore you
want to access.
You must begin this element with a slash (/).
PSAP This element is the PSAP identifier. If you are running FT-820
(Mandatory) with the TLI, you can specify any value for initiating application
entities. However, OSSC recommends that you set PSAPs for
initiating application entities to /0000.
PSAPs for filestore application entities are assigned by the
filestore’s administrator.
You must begin this element with a slash (/).
NS This element is the network service type, which you use to

(Optional) specify the type of network service used by the remote FTAM
filestores with which you wish to communicate.
Specify 0 to indicate that connectionless network service (CLNS)
is used, specify 1 to indicate that connection-oriented network
service (CONS) is used, or specify 2 to indicate that a TCP/IP
network service is used. CONS and CLNS are determined by the
profile adhered to by each filestore. Systems that conform to
MAP 3.0, TOP 3.0, US GOSIP, NIST, and COS 1.1 use CLNS.
If you select CLNS, the name of the TP4 driver is selected from
the osid.cfg file. If you select CONS, the name of the TP024
driver is selected from the osid.cfg file. If you select TCP/IP,
the name of the TP0TCP driver is selected from the osid.cfg
file. The Administrator Guide for a OSSC ported transport
product, such as LT-610 or WT-325, contains information on how
to configure the osid.cfg file. If you are not using a OSSC
transport product, see your transport product’s manual and the
OSSC OSI Application Developer’s Guide for information about
configuring FT-820 for non-OSSC transport providers.

Element Description
TC (Optional) This element is the transport class, which you use to

(Optional) specify the class of transport service used by the transport layer,
with which the FT-820 utilities and FTAM filestores interface.
Three classes of transport are available if connection-oriented
network service is selected. If connectionless network service is
selected, Class 4 must be used.
Class 0 Used in networks in which errors or interrupts
during transmission rarely occur.
Class 2 Similar to class 0, but also provides the ability
to share X.25 connections to reduce costs.
Class 4 Provides the means to detect and recover from
many errors in the network.
Setting up the __AETABLE__ file

The steps below show you how to set up the application entity table
file on your system:
1. Use the AIX operating system’s text editor to open the

__AETABLE__ file.
2. Enter the names and addresses of all application entities you

want to add to __AETABLE__. Delete or modify unused
application entities, if any. The __AETABLE__ file is described
in the preceding sections of this chapter.
3. Save __AETABLE__ and exit from your operating system’s text

editor.
The __AETABLE__ file is ready for use.
FT-820 environment variable

You can set the AETABLE environment variable on the command line
or in your .login start-up file.
The AETABLE environment variable specifies the directory path of

the __AETABLE__ file, which describes each application entity in
your network. If this variable is not set, the default path is
/usr/lpp/ossc/ulcommon/config/__AETABLE__.

The following code is an example of setting the AETABLE
environment variable on AIX in a C shell:
set AETABLE=”/etc/__AETABLE__”
or
setenv AETABLE ”/etc/__AETABLE__”
The following code is an example of setting the AETABLE

environment variable on AIX in a Bourne shell:
AETABLE=/etc/__AETABLE__
export AETABLE
Note. You can change the name of the application entity table file
(__AETABLE__) after you install it on your system. If you change
the name of __AETABLE__, you must specify the new name of
__AETABLE__ in the Bourne shell’s export command in the example
shown above.
Utility configuration file

The utility configuration file, .ftInit, contains parameters that
will be in effect when you use the FT-820 or FT-825 utilities. These
parameters provide characteristics for files that are created during a
copy or move operation, and can also provide security and access
limits. For FT-825, this file provides parameters for error recovery.
The use of this file is optional. If you do not use the utility
configuration file, default values will apply to the configurable
parameters. This file is only used if it is located in the user’s home
directory.
The FT-820 parameters you can define in the utility configuration file
include:
• access mode
• account information for file storage and maintenance, and for

file creation and selection
• concurrency control for file transfer, and for file deletion
• contents type
• password for file creation
• initiator name and filestore password

• override options for creating an already existing file
• create mode, which defines the attributes for newly created files
• effector, which defines the translation of form effectors between

document types
• universal class for strings in FTAM-1 and FTAM-2 documents
• maximum string length for FTAM-1, FTAM-2, and FTAM-3

documents
• copy indicator
• character set mapping
• path to the utility audit file and level of audit information to be

put in the audit file
• file transfer mode
The following FT-825 parameters are only relevant if you are using
FT-825 error recovery:
• quality of service
• checkpoint window size
• maximum number of retries
• maximum time limit for error recovery attempts
• retry delay before attempting recovery
Sample utility configuration file

A typical FT-820 utility configuration file (.ftInit) is shown
below. This is a sample configuration file, containing all of the
possible configurable parameters for the OSSC FTAM utilities.

Text that follows this symbol is ignored. A comment can occur
anywhere in a configuration file, even on the same line as a
parameter. The beginning of the comment must be separated from
the parameter by at least one space.

# (C) Copyright IBM Corporation 1993, 1994. All rights reserved.
#
#
# Unpublished - All rights reserved under the copyright laws of the
# United States.
#
# This software is furnished under a license and use, duplication,
# disclosure and all other uses are restricted to the rights
# specified in the written license between the licensee and IBM.
#
# Module: FT-820 Initiator Configuration File
#
# File: .ftInit
#
# Description: This file must be placed under the home directory of
# the user of the utilities (fcp, fmv, frm ..) as
# "~/.ftInit" in order for the utility to locate this file.
# It contains all the configurable parameters for the
# requests issued by an FT-820 initiator. All parameters
# marked "OPTIONAL" shall be excluded from the requests or
# defaulted to some value if they are not specified here.
#
#===========================================================================
#===========================================================================
# Requested Access : OPTIONAL
#
# This parameter should be input as the following :
# ACCESS_MODE = "mode1"
# READ_PASSWORD = "xxxxxxxx"
# INSERT_PASSWORD = "xxxxxxxx"
# REPLACE_PASSWORD = "xxxxxxxx"
# EXTEND_PASSWORD = "xxxxxxxx"
# ERASE_PASSWORD = "xxxxxxxx"
# READ_ATTR_PASSWORD = "xxxxxxxx"
# CHANGE_ATTR_PASSWORD = "xxxxxxxx"
# DELETE_FILE_PASSWORD = "xxxxxxxx"
#
# NOTE : See "Access Passwords" in FTAM 8571-3 (1988) p.21 for the
# definition of this parameter.
# THE MAXIMUM LENGTH FOR EACH PASSWORD IS 16 CHARACTERS.
#
# Where :
# mode1 = an ASCII string referring to a group of access
# passwords. It is referenced on the command line
# when using the “-s" option.
# (e.g. fcp -s mode1 x OSSCsm!/tmp).
#
# xxxxxxxx = an ASCII string with a combination of numeric
# (0-9), alphabetic (a-z, A-Z) and special characters
# (.#% ....). This string represents the password
# associated for a specific operation.
#===========================================================================
ACCESS_MODE = "OSSC"
READ_PASSWORD = "readpw"
INSERT_PASSWORD = "insertpw"
REPLACE_PASSWORD = "replacepw"
EXTEND_PASSWORD = "extendpw"

ERASE_PASSWORD = "erasepw"
READ_ATTR_PASSWORD = "readattpw"
CHANGE_ATTR_PASSWORD = "changepw"
DELETE_FILE_PASSWORD = "deletepw"
ACCESS_MODE = "accessmode"
READ_PASSWORD = "readpw1"
READ_ATTR_PASSWORD = "readattpw1"
#===========================================================================
# Account : OPTIONAL
#
# ACCOUNT = "xxxxxxxx"
#
# NOTE : See "Account" in FTAM 8571-3 (1988) p.20 and p.25 for the
# THE MAXIMUM SIZE FOR ACCOUNT IS 16 CHARACTERS.
#
# Where :
# (.#% ....). This string represents the account
# used for charging by the FTAM regime.
#===========================================================================
ACCOUNT = "OSSC"
#===========================================================================
# Account for File Creation : OPTIONAL
#
# CREATE_ACCOUNT = "xxxxxxxx"
#
#
# Where :
# to be charged for the duration of this selection.
#===========================================================================
CREATE_ACCOUNT = "createaccount"
#===========================================================================
# Account for File Selection (Open, ReadAttribute, ChangeAttribute) : OPTIONAL
#
# SELECT_ACCOUNT= "xxxxxxxx"
#
#
# Where :

# used for charging by the SELECT regime.
#===========================================================================
SELECT_ACCOUNT = "selectaccount"
#===========================================================================
# Concurrency Control For File Transfer : OPTIONAL
#
# XFER_READ = xx
# XFER_INSERT = xx
# XFER_REPLACE = xx
# XFER_EXTEND = xx
# XFER_ERASE = xx
# XFER_READ_ATTR = xx
# XFER_CHANGE_ATTR = xx
# XFER_DELETE_FILE = xx
#
# NOTE : See "Concurrency Control" in FTAM 8571-3 (1988) p.21 and p.28
# for the definition of this parameter.
#
# Where :
# xx can be any one of the following strings :
# SHARED NOT_REQUIRED EXCLUSIVE NO_ACCESS
#===========================================================================
#XFER_READ = SHARED
#XFER_INSERT = NOT_REQUIRED
#XFER_REPLACE = EXCLUSIVE
#XFER_EXTEND = EXCLUSIVE
#XFER_ERASE = EXCLUSIVE
#XFER_READ_ATTR = SHARED
#XFER_CHANGE_ATTR = EXCLUSIVE
#XFER_DELETE_FILE = EXCLUSIVE
#===========================================================================
# Concurrency Control For File Deletion : OPTIONAL
#
# DEL_READ = xx
# DEL_INSERT = xx
# DEL_REPLACE = xx
# DEL_EXTEND = xx
# DEL_ERASE = xx
# DEL_READ_ATTR = xx
# DEL_CHANGE_ATTR = xx
# DEL_DELETE_FILE = xx
#
# NOTE : See "Concurrency Control" in FTAM 8571-3 (1988) p.21 and p.28
# for the definition of this parameter.
#
# Where :
# SHARED NOT_REQUIRED EXCLUSIVE NO_ACCESS
#===========================================================================
DEL_READ = NO_ACCESS
DEL_INSERT = NO_ACCESS
DEL_REPLACE = NO_ACCESS
DEL_EXTEND = NO_ACCESS

DEL_ERASE = NO_ACCESS
DEL_READ_ATTR = NO_ACCESS
DEL_CHANGE_ATTR = NO_ACCESS
DEL_DELETE_FILE = EXCLUSIVE
#===========================================================================
# Contents Type : OPTIONAL
#
# This parameter specifies the default document type of a file being
# transferred.
#
# CONTENTS_TYPE = xx
#
# NOTE : See FTAM 8571-2 (1988) p.29, p.32, and p.35 for the definition
# of these document types.
#
# Where :
# FTAM-1 FTAM-2 FTAM-3
#===========================================================================
CONTENTS_TYPE = FTAM-3
#===========================================================================
# Create Password : OPTIONAL
#
# If the responder requires a specific password for file creation, this
# parameter should be used.
#
# CREATE_PASSWORD = "xxxxxxxx"
#
# NOTE : See "Create Password" in FTAM 8571-3 (1988) p.29 for the
# THE MAXIMUM LENGTH OF CREATE_PASSWORD IS 16 CHARACTERS.
#
# Where :
# required for file creation.
#===========================================================================
CREATE_PASSWORD = "createpasswd"
#===========================================================================
# Initiator Name and Filestore Password : OPTIONAL
#
# These parameters identify the privileges of the initiator to the
# responder. They may also be specified on the command line by using
# either the "-p" or "-P" option (see FT-820 User Guide).
#
# INITIATOR_ID = "xxxxxxxx"
# FILE_STORE_PASSWORD = "xxxxxxxx"
#
# NOTE : See "Initiator Identity" and "Filestore Password" in FTAM 8571-3
# (1988) p.25 for the definitions of these parameters.
# THE MAXIMUM SIZE FOR INITIATOR_ID AND PASSWORD IS 16 CHARACTERS.

#
# Where :
# (.#% ....).
#===========================================================================
#INITIATOR_ID = "guest"
#FILE_STORE_PASSWORD = "password"
#===========================================================================
# Override : MANDATORY
#
# This parameter defines what action to take in the event that the
# destination file already exists during file creation.
#
# OVERRIDE = xx
#
# NOTE : See "Override" in FTAM 8571-3 (1988) p.29 for the definition of
# this parameter.
#
# Where :
# xx can be any one of the following :
# CREATE-FAILURE DEL&CREATE-OLD-ATTR
# SELECT-OLD-FILE DEL&CREATE-NEW-ATTR
#===========================================================================
OVERRIDE = DEL&CREATE-NEW-ATTR
#===========================================================================
# Create Mode : OPTIONAL
#
# This parameter provides a user with the ability to specify the
# attribute characteristics of the destination file being created.
# These characteristic groups are referenced on the command line by
# a string when using the "-c" option.
#
#
# CREATE_MODE = "create_id"
# FILE_AVAILABILITY = aa
# FUTURE_FILE_SIZE = 1000000
# LEGAL_QUALIFICATION = "qqqqqqqq"
# ACCESS_CONTROL {
# USER_NAME = "uuuuuuuu"
# LOCATION = "llllllll"
# READ_CONTROL = cc, "pppppppp"
# INSERT_CONTROL = cc, "pppppppp"
# REPLACE_CONTROL = cc, "pppppppp"
# EXTEND_CONTROL = cc, "pppppppp"
# ERASE_CONTROL = cc, "pppppppp"
# READ_ATTR_CONTROL = cc, "pppppppp"
# CHANGE_ATTR_CONTROL = cc, "pppppppp"
# DELETE_FILE_CONTROL = cc, "pppppppp"
# }
#
# Note : See FTAM 8571-2 (1988) p.12 for the definitions of these parameters.
#
# Where :

# create_id = an ASCII string referring to a group of
# file attributes for the destination file.
# It is referenced on the command line when
# using the "-c" option.
# (e.g. fcp -c create_id x OSSCsm!/tmp).
#
# aa = choice of either IMMEDIATE or DEFERRED.
#
# qqqqqqqq = an ASCII string with a combination of numeric
# (.#% ....). This string represents the file
# qualification attribute.
#
# uuuuuuuu = an ASCII string with a combination of numeric
# (.#% ....). This string represents a user name.
# NOTE : OSSC filestores recognize only the following
# values for this string: "USER", "GROUP", or "OTHER".
#
# llllllll = an ASCII string with a combination of numeric
# (.#% ....). This string represents an application
# entity name stored in the __AETABLE__.
#
# cc = any combination of EXCLUSIVE, SHARED, NO_ACCESS, and
# NOT_REQUIRED separated by an '&'.
# (e.g. EXCLUSIVE & NOT_REQUIRED & SHARED )
#
# pppppppp = an ASCII string with a combination of numeric
# associated with a specific operation. The maximum
# length for a password is 16 characters.
# NOTE : A password need only be specified in the
# first access control element for OSSC filestores.
#===========================================================================
CREATE_MODE = "OSSC"
FILE_AVAILABILITY = IMMEDIATE
FUTURE_FILE_SIZE = 1000000
LEGAL_QUALIFICATION = "OSSC"
ACCESS_CONTROL {
USER_NAME = "USER"
READ_CONTROL = NOT_REQUIRED & EXCLUSIVE & SHARED & NO_ACCESS, "readpw"
INSERT_CONTROL = NOT_REQUIRED & NO_ACCESS
REPLACE_CONTROL = NOT_REQUIRED & EXCLUSIVE & NO_ACCESS, "replacepw"
EXTEND_CONTROL = NOT_REQUIRED & EXCLUSIVE & NO_ACCESS, "extendpw"
ERASE_CONTROL = NOT_REQUIRED & NO_ACCESS, "erasepw"
READ_ATTR_CONTROL = NOT_REQUIRED & NO_ACCESS, "readattpw"
CHANGE_ATTR_CONTROL = NOT_REQUIRED & EXCLUSIVE & NO_ACCESS, "changepw"
DELETE_FILE_CONTROL = NOT_REQUIRED & EXCLUSIVE & NO_ACCESS, "deletepw"
}
ACCESS_CONTROL {
USER_NAME = "GROUP"
READ_CONTROL = NOT_REQUIRED & SHARED & NO_ACCESS
READ_ATTR_CONTROL = NOT_REQUIRED & NO_ACCESS
}
ACCESS_CONTROL {
USER_NAME = "OTHER"

}
#===========================================================================
# Effector : OPTIONAL
#
# This parameter specifies the form effector used in an FTAM-1 or FTAM-2
# file. By default, the form effector is <LF>.
# The effector is used in the following manner:
#
# AIX -> FTAM-1 : <effector> => <CR><effector>
# FTAM-1 -> AIX : <CR><effector> => <effector>
# AIX -> FTAM-2 : <effector> removed
# FTAM-2 -> AIX : <effector> added
#
# EFFECTOR = xx
#
# Where :
# xx = ascii decimal code referring to the appropriate character
# (e.g. <LF> = 10; <FF> = 12)
#===========================================================================
EFFECTOR = 10
#===========================================================================
# Universal Class : OPTIONAL
#
# This parameter specifies the universal class for strings in an FTAM-1 or
# FTAM-2 document. By default, the universal class for FTAM-1 and FTAM-2
# documents is GRAPHIC_STRING.
#
# UNIVERSAL_CLASS = aa
#
# Where :
# aa can be any one of the following :
# IA5_STRING GRAPHIC_STRING
# VISIBLE_STRING GENERAL_STRING
#
# NOTE : Printable string, Teletex string and Video string are not
# present because they are currently not supported in the ISP.
#===========================================================================
UNIVERSAL_CLASS = GRAPHIC_STRING
#===========================================================================
# Maximum String Length : OPTIONAL
#
# These parameters specify the maximum string length for FTAM-1, FTAM-2,
# and FTAM-3 documents. By default, the string length is unbounded; that
# is, there is no maximum string length.
#
# These parameters should be input as the following :
# MAXIMUM_STRING_LENGTH = w
# FTAM1_MAXIMUM_STRING_LENGTH = x
# FTAM2_MAXIMUM_STRING_LENGTH = y
# FTAM3_MAXIMUM_STRING_LENGTH = z
#
# Where :
# w = any positive integer.

# x = an integer within the range 0 <= x <= 132.
# y = an integer within the range 0 <= y <= 132.
# z = an integer within the range 0 <= z <= 512.
#
# NOTE : 0 implies no maximum string length.
#===========================================================================
MAXIMUM_STRING_LENGTH = 0
FTAM1_MAXIMUM_STRING_LENGTH = 132
#===========================================================================
# Copy Indicator : OPTIONAL
#
# This parameter specifies whether to turn the copy indicator ON or OFF.
# If turned on, successive periods (".") will be displayed as the file
# is being transferred.
#
# NOTE : In addition, the "-v" option must be specified on
# the command line for the copy indicator to be displayed.
#
# COPY_INDICATOR = xx
#
# Where :
# xx is either ON or OFF
#
#===========================================================================
COPY_INDICATOR = ON
#===========================================================================
# MAPPING : OPTIONAL
#
# This parameter, if set, specifies the supported default character set.
#
# This parameter is input as follows :
# MAPPING = xx
#
# Where :
# ISO_646 (the default character set is ISO 646)
# ISO_8859_1 (the default character set is ISO 8859-1)
#
#===========================================================================
MAPPING = ISO_8859_1
#==========================================================================
# Audit File Path and Audit Level
#
# These parameters specify the path name of the utility audit file, and the
# level of audit description. If no filename is specified, the audit will
# be displayed to stderr.
#
# These parameters are input as follows :
# AUDITPATH = pathname
# AUDITLEVEL = x
#
# Where :

# pathname = absolute path of utility audit file (including filename)
#
# x can be any one of the following values :
# 0 - OFF
# 1 - Connect Release Abort
# 2 - ADD Select Create Deselect Delete
# 3 - ADD Open Close
#==========================================================================
#AUDITPATH = "/usr/spool/OSSC/utils.audit"
#AUDITLEVEL = 3
#===========================================================================
# CONTINUE : OPTIONAL
#
# This parameter provides the user with the means to ensure that as many
# of the specified files as possible will be transferred.
#
# CONTINUE = xx
#
# Where :
# xx can be
# OFF (Exit on first failure)
# ON (Transfer as many files as possible)
#===========================================================================
CONTINUE = ON
#===========================================================================
# Quality Of Service : OPTIONAL
#
# This parameter provides the user with the means to define the proposed
# level of service to be negotiated.
#
# NOTE : This parameter is only meaningful if the FT-825 option is used.
#
# This parameter should be input as follows :
# QUALITY_OF_SERVICE = x
#
# Where :
# x is a value of
# 0 : class 0; no error recovery
# 1 : class I error recovery
# 2 : class II error recovery
# 3 : class III error recovery
#
# NOTE : When the FT-825 option is not being used, the default
# value is 0; otherwise, the default values is 3.
#===========================================================================
QUALITY_OF_SERVICE = 3
#===========================================================================
# Checkpoint Window : OPTIONAL
#
# This parameter provides the user with the means to define the maximum
# number of checkpoints that may remain unacknowledged.
#
# NOTE : This parameter is only meaningful if the FT-825 option is used.
#

# CHECK_WINDOW = x
#
# Where :
# x is a number representing the required checkpoint window size
#===========================================================================
CHECK_WINDOW = 1
#===========================================================================
# Maximum Retries : OPTIONAL
#
# This parameter provides the user with the means to define the number
# of times that ERPM should attempt to restart/recover before reporting
# an error to the utility/responder.
#
# NOTE : This parameter is only meaningful if the FT-825 option is used,
# and the negotiated quality of service is 3.
#
# MAX_RETRIES = x
#
# Where :
# x is a number representing the maximum number of retries
#===========================================================================
MAX_RETRIES = 5
#===========================================================================
# Maximum Time Limit : OPTIONAL
#
# This parameter provides the user with the means to define the maximum
# time limit after which FT-825 should stop error recovery and report a
# a permanent error.
#
#
# MAX_TIME_LIMIT = x
#
# Where :
# x is a number representing the maximum time limit, in seconds.
#===========================================================================
MAX_TIME_LIMIT = 3600 ## 1 hour
#===========================================================================
# Retry Delay : OPTIONAL
#
# This parameter provides the user with the means to define the delay
# time in seconds that FT-825 should wait after failure, before it attempts
# to restart/recover.
#
#
# RETRY_DELAY = x
#
# Where :

# x is a number representing a factor in the retry delay required.
#
# NOTE : The delay time is 2^x seconds.
#===========================================================================
RETRY_DELAY = 9
Elements of the utility configuration file

Elements of the FT-820 utility configuration file are described below.
The examples of each element are based on the file illustrated above.
Note. All passwords and account names used in the utility

configuration file must follow these syntax conventions:
• The legal characters are any combination of 0–9, a–z, A–Z, and
printing characters, including the period (.), percent (%), and
number (#) symbols.
• All passwords and account names have a maximum length of

16 characters.
Element Description
ACCESS_MODE When fcp creates a new file, this parameter provides an

READ_PASSWORD identifying name for a group of action and password pairs.
INSERT_PASSWORD Each grouping of action/password pairs is called an
REPLACE_PASSWORD access mode, and is assigned a name here. You can
EXTEND_PASSWORD
create more than one access mode, and select one of
ERASE_PASSWORD
READ_ATTR_PASSWORD them by using its name on the utility command line with the
CHANGE_ATTR_PASSWORD -s option.
DELETE_FILE_PASSWORD In the example file, two access modes are defined: OSSC
(Optional) and accessmode. Use access mode names and
passwords that are meaningful in your network. Each
password must follow the utility configuration file’s syntax
conventions.
If you do not define a password for an action, the initiator
will pass a blank for that value. If the responder finds that
unacceptable, the request will be rejected. Possible
actions that can be assigned to a password are as follows:
• read • erase
• insert • read attributes
• replace • change attributes
• extend • delete file

Element Description
ACCOUNT Specifies the name of the account that should be charged

(Optional) for all costs incurred during the execution of the FT-820
utility command. If either CREATE_ACCOUNT or
SELECT_ACCOUNT is also defined, they will override this
parameter in the cases of file creation or selection. The
account name must follow the utility configuration file’s
syntax conventions.
You can override the value given here by using a different
value for the -a option on the command line.
CREATE_ACCOUNT Specifies the name of the account that should be charged

(Optional) for all costs incurred during file creation. The account
name must follow the utility configuration file’s syntax
conventions.
SELECT_ACCOUNT Specifies the account name for the account that should be
(Optional) charged for all costs incurred by the selection (during file
open, read attributes, and change attribute operations) of
a file. The account name must follow the utility
configuration file’s syntax conventions.
XFER_READ This set of parameters assigns the concurrency controls

XFER_INSERT that are in effect during a file transfer resulting from the
XFER_REPLACE use of one of the FT-820 utilities. For each action, a lock is
XFER_EXTEND in effect for the length of time that the utility is accessing
XFER_ERASE the file in question. Possible actions are:
XFER_READ_ATTR
XFER_CHANGE_ATTR • XFER_READ • XFER_ERASE
XFER_DELETE_FILE • XFER_INSERT • XFER_READ_ATTR
(Optional) • XFER_REPLACE • XFER_CHANGE_ATTR
• XFER_EXTEND • XFER_DELETE_FILE
Each of the above actions can be assigned one of the
following locks:
SHARED I may perform this action; so may
others.
NOT_REQUIRED I will not perform this action; others
may.
EXCLUSIVE I may perform this action; others
may not.
NO_ACCESS No one may perform this action.
The locks define the access available to the user and the
access available to any other user. The SHARED and
EXCLUSIVE locks are only permitted for the actions
negotiated as available in the requested access
parameter.
The file transfer concurrency control parameter is
commented out of the sample .ftInit file.

Element Description
DEL_READ This set of parameters assigns the concurrency controls

DEL_INSERT that are in effect during a file deletion resulting from the
DEL_REPLACE use of one of the FT-820 utilities. For each action, a lock is
DEL_EXTEND in effect for the length of time that the utility is accessing
DEL_ERASE the file in question. Possible actions are:
DEL_READ_ATTR
DEL_CHANGE_ATTR • DEL_READ • DEL_ERASE
DEL_DELETE_FILE • DEL_INSERT • DEL_READ_ATTR
(Optional) • DEL_REPLACE • DEL_CHANGE_ATTR
• DEL_EXTEND • DEL_DELETE_FILE
Each of the above actions can be assigned one of the
following locks:
others.
may.
may not.
The locks define the access available to the user and the
access available to any other user. The SHARED and
EXCLUSIVE locks are only permitted for the actions
negotiated as available in the requested access
parameter.
CONTENTS_TYPE Specifies the document type of a file created by the

(Optional) FT-820 utilities. Possible values are:
• FTAM-1
• FTAM-2
• FTAM-3
Descriptions of these document file types are on page 6.
The value in this file can be overridden by specifying a
different value for the -T or -t options on the command
line.
CREATE_PASSWORD Provides a specific password for file creation, which may

(Optional) be required by some filestores. The password follows the
utility configuration file’s password syntax conventions.

Element Description
INITIATOR_ID These parameters provide an initiator name and a filestore

FILE_STORE_PASSWORD password, if the filestore requires them. The initiator ID
(Optional) identifies the user of the FT-820 or FT-825 utility, and the
filestore password proves that the user is allowed access
to the filestore. The ID and password must follow the utility
configuration file’s password syntax conventions. These
values can be overridden by using the -p or -P option on
the command line.
The initiator name and filestore password parameters are
commented out of the sample .ftInit file.
OVERRIDE Tells the filestore what action to take if the file being copied
(Optional) or moved already exists at the destination. The value given
here can be overridden by using the -o option on the
command line. The possible values are:
CREATE-FAILURE The creation fails if the
destination file already
exists.
SELECT-OLD-FILE The existing file is selected
instead of creating a new
one.
DEL&CREATE-OLD-ATTR Opens the existing file and
deletes its contents, but its
attributes are unchanged.
DEL&CREATE-NEW-ATTR Deletes the old file and
creates a new one, whose
attributes are taken from
default values, or from the
create mode parameter, if
one is specified in either the
command line or in this
utility configuration file (see
below).

Element Description
CREATE_MODE Supplies one or more sets of new file attributes to be

(Optional) applied to files created by the FT-820 utilities. Each set of
file attributes is assigned a name here. The name is then
used with the -c option on the utility command line to
select the set of characteristics in effect for that file
creation. The possible file attributes are:
• FILE_AVAILABILITY
• FUTURE_FILE_SIZE
• LEGAL_QUALIFICATION
• ACCESS_CONTROL
In the example file, there is one create mode, OSSC,
defined. You may define more than one create mode in the
utility configuration file.
FILE_AVAILABILITY One of the CREATE_MODE parameters. The value of this

parameter may be either IMMEDIATE or DEFERRED. It is of
significance to the filestore, rather than the user, with a
value of DEFERRED indicating that the file may be stored
where a delay will occur when accessing it.
FUTURE_FILE_SIZE One of the CREATE_MODE parameters. Specifies the size

in octets to which the file is allowed to grow. Any size is
valid, up to your system’s memory limitations.
LEGAL_QUALIFICATION One of the CREATE_MODE parameters. Specifies the legal

status of the file. The implication of this parameter varies
depending on national data protection legislation. The
qualification must follow the utility configuration file’s
syntax conventions.

Element Description
ACCESS_CONTROL One of the CREATE_MODE parameters. Defines the access

controls that will be in effect for the new file. Each access
control attribute must be separately specified within this
parameter, and the set of access control attributes must be
surrounded by curly brackets: { }. For the access control
locks, the following explanations apply:
others.
may.
may not.
Each set of access controls is usually matched by a
defined set of action/password pairs in the .ftInit file’s
ACCESS_MODE parameter.
Within a single create mode, you can define multiple
access control elements, each one with a different user
name. In the sample .ftInit file, create mode “OSSC”
has three access control elements: one for user name
“USER,” one for user name “GROUP,” and one for user
name “OTHER.”
USER_NAME. The user name for the creation of the file.

This user will be the owner of the newly created file. The
user name must follow the utility configuration file’s syntax
conventions. OSSC filestores recognize only the following
values for this string: “USER”, “GROUP”, or “OTHER”.
LOCATION. Specifies the calling application entity name,

as it appears in the __AETABLE__ file. The name must
follow the utility configuration file’s syntax conventions.
READ_CONTROL. Specifies the access controls that will

be in effect for reading the newly created file, and the
password for the read operation. Any combination of
EXCLUSIVE, SHARED, NO_ACCESS, and NOT_REQUIRED
is allowed, separated by an ampersand (&). The password
must follow the syntax conventions of the utility
configuration file. The values of the access control locks
are explained above.

Element Description
INSERT_CONTROL. Specifies the access controls that

will be in effect for the insert action on the newly created
file, and the password for the insert action. Any
combination of EXCLUSIVE, SHARED, NO_ACCESS, and
NOT_REQUIRED is allowed, separated by an ampersand
(&). The password must follow the syntax conventions of
the utility configuration file. The values of the access
control locks are explained above.
REPLACE_CONTROL. Specifies the access controls that

will be in effect for the replace action on the newly created
file, and the password for the replace action. Any
EXTEND_CONTROL. Specifies the access controls that

will be in effect for the extend action on the newly created
file, and the password for the extend action. Any
ERASE_CONTROL. Specifies the access controls that will

be in effect for the erase action on the newly created file,
and the password for the erase action. Any combination of
READ_ATTR_CONTROL. Specifies the access controls

that will be in effect for the read attributes action on the
newly created file, and the password for the read attributes
action. Any combination of EXCLUSIVE, SHARED,
NO_ACCESS, and NOT_REQUIRED is allowed, separated
by an ampersand (&). The password must follow the
syntax conventions of the utility configuration file. The
values of the access control locks are explained above.

Element Description
CHANGE_ATTR_CONTROL. Specifies the access controls

that will be in effect for the change attributes action on the
newly created file, and the password for the change
attributes action. Any combination of EXCLUSIVE,
SHARED, NO_ACCESS, and NOT_REQUIRED is allowed,
separated by an ampersand (&). The password must
follow the syntax conventions of the utility configuration
file. The values of the access control locks are explained
above.
DELETE_FILE_CONTROL. Specifies the access controls

that will be in effect for deleting the newly created file, and
the password for the delete action. Any combination of
EFFECTOR Sets the effector the user wishes to apply to the file. By
(Optional) default, the form effector for FTAM-1 and FTAM-2 is a line
feed (<LF>). It is used as follows:
AIX operating system document → FTAM-1 document:
<LF> translates to <CR> <LF>
FTAM-1 document → AIX operating system document
<CR> <LF> translates to <LF>
<LF> removed
FTAM-2 document → AIX operating system document:
<LF> added
You can set other control characters to be the effector, and
they will then be treated in the same manner as a linefeed.
For example, an effector stating EFFECTOR = 12 would
treat <FF> as an effector:
<FF> translates to <CR> <LF>
FTAM-1 document → AIX operating system document
<CR> <LF> translates to <FF>
<FF> removed
<FF> added

Element Description
UNIVERSAL_CLASS Specifies the universal class of the string in an FTAM-1 or

(Optional) FTAM-2 document. The possible values for the string class
are:
• IA5_STRING
• GRAPHIC_STRING (default for FTAM-1 and FTAM-2)
• VISIBLE_STRING
• GENERAL_STRING
MAXIMUM_STRING_LENGTH Specifies the maximum string length in FTAM-1, FTAM-2,

(Optional) and FTAM-3 documents. The default is no maximum string
length. If FTAM1_MAXIMUM_STRING_LENGTH,
FTAM2_MAXIMUM_STRING_LENGTH, or
FTAM3_MAXIMUM_STRING_LENGTH is not specified, this
parameter is invoked.
FTAM1_MAXIMUM_ Specifies the maximum string length in FTAM-1

STRING_LENGTH documents. The default is no maximum string length. If
(Optional) you specify a value greater than 134, this parameter is set
to 134.

STRING_LENGTH documents. The default is no maximum string length. If the
(Optional) user specifies a value greater than 134, this parameter is
set to 134.

STRING_LENGTH documents. The default is no maximum string length. If the
(Optional) user specifies a value greater than 512, this parameter is
set to 512.
COPY_INDICATOR Specifies whether COPY_INDICATOR is turned on. If the

(Optional) COPY_INDICATOR is on, “....” will be displayed as a file
is being transferred.
Note. You must also use the -v option to see the copy
indicator being displayed.
MAPPING Specifies the character set supported by the FT-820

(Optional) utilities. The default is the ISO 646 character set.

Element Description
AUDITPATH These parameters specify the path to the audit file and the
AUDITLEVEL audit level of audit information to be recorded. If no path is
(Optional) specified, the audit information is displayed on your screen
(stderr). The audit levels are as follows:
0 No audit information is recorded.
1 Information recorded on connection, release,
and abort.
2 Information recorded on select, create, deselect,
and delete.
3 Information recorded on open and close.
The AUDITPATH and AUDITLEVEL parameters are
commented out in the sample .ftInit file.
CONTINUE Specifies whether or not FT-820 will transfer as many of

(Optional) the specified files as possible, even if errors occur.
QUALITY_OF_SERVICE he level of error recovery required by the fcp or fmv

(Optional) utility. This parameter is only significant if you are using
the FT-825 ERPM product. The possible values are:
0 No error recovery is required.
1 Class I error recovery (that is, an error occurred
damaging the data transfer).
2 Class II error recovery (that is, the file needs to
be re-opened).
3 Class III error recovery (that is, the association
was broken).
CHECK_WINDOW Defines the maximum number of checkpoints that may

(Optional) remain unacknowledged when the fcp or fmv utility is
sending a file to the filestore. This parameter is only
significant if you are using the FT-825 ERPM product.
MAX_RETRIES Defines the number of times that recovery/restart is

(Optional) attempted before an error is reported to the utility. This
parameter is only significant if you are using the FT-825
ERPM product and the negotiated quality of service for the
connection is 3.
MAX_TIME_LIMIT Defines the time limit (in seconds) after which

(Optional) recovery/restart attempts are stopped, and an error is
reported to the utility. This parameter is only significant if
you are using the FT-825 ERPM product.
RETRY_DELAY Factor for defining the time delayed (two to the power of
(Optional) RETRY_DELAY seconds) after a failure before
recovery/restart is attempted. This parameter is only
significant if you are using the FT-825 ERPM product.

Setting up the utility configuration file
These steps show you how to set up the utility configuration file
(.ftInit) for your system.
1. Use the AIX operating system’s text editor to correctly set

the parameters in the utility configuration file ~/.ftInit.
2. Save the file in the user’s home directory and exit from the
utility configuration file.
The utility configuration file is ready for use. It will take effect the
next time FT-820 is started.
Filestore configuration file

Use the FT-820 filestore configuration file to define the parameters
for the filestore in your network.
The parameters you can define include the address of the filestore
(responder address), its application entity title, default FTAM
initiator ID (login name), access to FTAM, restricted access to FTAM,
multiple processes, maximum number of FTAM connections, file
access concurrency control, attribute database path, create
permissions, and the names of your transport providers.
Sample filestore configuration file

A typical FT-820 filestore configuration file, ffs.cfg, is shown
below.

Text that follows is ignored. You can place a comment on the same
line following a parameter. The beginning of the comment must be
separated from the parameter by at least one space.
# (C) Copyright OSSC 1988 - 1993. All rights reserved.
# Unpublished - All rights reserved under the copyright laws

# of the United States.
#
# This software is furnished under a license and use,

# duplication, disclosure and all other uses are restricted
# to the rights specified in the written license between the
# licensee and OSSC.
# RCS: $Date: 93/08/27 09:04:49 $ $State: PN-2910300-21-XD_V1_90 $

#
# Virtual File Store Configuration
# NOTES for filling in this file:

# 1. Character strings must be in double quotes "string"
# 2. Hex values must be entered in upper case.
# Responder address
# Enter HEX octets or Character strings
# Example TSAP can be "FTAM" or 4654414D
# NSAP must be entered in HEX
#NSAP = 4901020301
TSAP = 0100
SSAP = "SS"
PSAP = "PP"
# Application Entity Title

# The value { 1 3 9999 1 7 } is the NBS FTAM NILL AP-title
# Remove if all titles are acceptable. The AE title is entered
# in Decimal only.
TITLE = { 1 3 9999 1 7 }
# Default FTAM Initiator ID.

# This is the name used when a NULL initiator identity or an
# initiator identity of ANON is received. It may be removed
# if anonymous users are NOT allowed to gain access to the
# system.
USER = "ANON"
# Limit FTAM Access

# Set to TRUE if you wish to limit access to only the default
# ftam user. All initiators will be given the permissions of
# the USER value. Set to FALSE if you wish the user to have
# his normal permissions.
LIMIT = FALSE
# No Access User List

# The following contains a list of all initiators that will
# not gain access to the FTAM services
NO_ACCESS_LIST = { "root" }
# Create a new process for each connect indication.

# Set to TRUE to create a new process each time a connect
# indication is received. The CONNECTS parameter is used to
# limit number of processes created.
MULTIPLE_PROCESSES = FALSE
# Number of FTAM Connections

# If you are using the MULTIPLE_PROCESS option, then this is a
# limit on the number of processes created.
# NOTE: If you set the CONNECTS parameter > 16 then you must

# edit the lockmgr command's -u option to be a value
# which is at least the number of CONNECTS. This
# command appears in the /etc/ft820.rc file. (The
# lockmgr default -u value supports 16 processes.)
#
#
# If you are NOT creating multiple processes, then this value
# must be less than 16.
#
# Warning: If you are not using the multiple process option,
# then use the following formula to calculate the
# Maximum number of connections supported by your
# system.
# connects = (Max OPEN Files per process - 10) / 2 (round down)
#
# example:
# 5 = (20 - 10) / 2
CONNECTS = 5
# File Access Concurrency Control

# Set LOCAL_CONC_CTRL to TRUE if you are running only one
# RESPONDER. Set to FALSE if multiple responders are sharing
# the same file store and you want them to cooperate.
# Note that this values must be FALSE if multiple processess are used.
LOCAL_CONC_CTRL = TRUE
# Attribute DataBase Path

# Path to the Attribute Data base and the Concurrency lock
# file. This value cannot be left blank.
ATTRPATH = "/usr/spool/OSSC"
# Audit File path and filename

# This is the filename of the audit file. The default value
# (when no value is entered) is stderr.
# Audit levels
# 0 - OFF
# 1 - Connect Release Abort
# 2 - ADD Select Create Deselect Delete
# 3 - ADD Open Close
AUDITPATH = "/usr/spool/OSSC/ffs.audit"
AUDITLEVEL = 1
# Authentication file path and filename

# This is the filename of the authentication file. The
# OPTIONAL authentication file contains a list of the network
# address that may gain access to the FTAM file store.
AUTHPATH = "/usr/spool/OSSC/ffs.auth"
# Create Permissions
# This is the default AIX permissions that will be used if
# user does not send Access Control Elements on the CREATE
# request. Set value for USER, GROUP and OTHER to READ,
# WRITE, or READ_WRITE.
USER_CREATE_PERMISSION = READ_WRITE
GROUP_CREATE_PERMISSION = READ_WRITE
OTHER_CREATE_PERMISSION = READ_WRITE

# Textfile extensions
# When a file is selected, which does not exist in the FTAM

# attribute database, a default file type of FTAM-3 (simple
# binary) or NBS-9 (directory file) will be assigned to that
# file. If the name of the file contain an extension that is
# in the following list it will default to an FTAM-1 (simple
# text) file.
TEXT_EXT = {
"txt" "doc" "h" "c"
}
#===========================================================================
# Effector: OPTIONAL
#
# This parameter is the list of effectors user wish to define. By default,
# the Form effector for FTAM1 and FTAM2 is <LF>. Here is how the
# effector is used :
# AIX -> FTAM1 : <LF> = <CR> <LF>
# FTAM -> AIX : <CR><LF> = <LF>
# AIX -> FTAM2 : <LF> removed
# FTAM2 -> AIX : <LF> added
# If user put other character(s) (must be control character) in this
effector
# list, then every character in this list will be treated the same as <LF>
# in the example above.
# For example :
# An effector list stating EFFECTOR = 12 will treat both
# <FF> as effector. For the example below, <effector>
# means <FF>.
# AIX -> FTAM1 : <effector> = <CR> <LF>
# FTAM -> AIX : <CR><LF> = <effector>
# AIX -> FTAM2 : <effector> removed
# * FTAM2 -> AIX : <effector> added
#
#===========================================================================
#EFFECTOR = 10
#===========================================================================
# Delete Unsuccessful File Flag : OPTIONAL
#
# Defaulted Value : FALSE
#
# Description :
# This parameter allows user to configure the responder to delete
# unsuccessfully transferred file.
# The responder checks this configuration flag when it is aborting
# the connection. If the destination file is still open at this point,
# it assumes that the data transfer failed and therefore deletes
# the file.
#
#===========================================================================
#DELETE_FAILED_FILE = TRUE
#===========================================================================

# This is a MANDATORY field.
# In this field you should include the names of all transport providers
# that you wish to receive connect indications on. These names are
# defined in the file "osid.cfg" (See admin guide for more information)
#
#Example:
# TRANSPORT_NAMES = { "TP4" "TP024" "TP0TCP" }
#===========================================================================
TRANSPORT_NAMES = { "TP4" }
#===========================================================================
# Quality Of Service : OPTIONAL
#
# This parameter provides the user with the means of defining the
# proposed level of service to be negotiated. This parameter is
# only meaningful if the FT-825 option is being used.
#
# This parameter is inputted as follows :
# QUALITY_OF_SERVICE = x
#
# Where x is a value of 0,1,2 or 3, which represents class 0, I, II
# or III error recovery.
# Default value is 0 when FT-825 option is not being used
T-825 option is being used
#
#===========================================================================
#QUALITY_OF_SERVICE = 3
#===========================================================================
# Checkpoint Window : OPTIONAL
#
# maximum number of checkpoints that may remain unacknowledged
#
# CHECK_WINDOW = x
#
# Where x is a number representing the window size required
#
#===========================================================================
#CHECK_WINDOW = 1
#===========================================================================
#
# Maximum Retries : OPTIONAL
#
# number of times that ERPM should attempt to restart/recover
# before reporting an error to the utility/responder.This parameter is
# only meaningful if the FT-825 option is being used, and the
# negotiated quality of service is 3.
#
# MAX_RETRIES = x
#
# Where x is a number representing the maximum number of retries
# required
#

#===========================================================================
#MAX_RETRIES = 5
#===========================================================================
#
# Maximum Time Limit : OPTIONAL
#
# maximum time limit after which FT-825 should stop
# re-trying and should report a permanent error. This parameter is
#
# MAX_TIME_LIMIT = x
#
# Where x is a number representing the maximum time limit
# required , in seconds
#
#===========================================================================
#MAX_TIME_LIMIT = 3600 # 1 hour
#===========================================================================
#
# Retry Delay : OPTIONAL
#
# delay time in seconds that FT-825 should wait after failure,
# before it attempts to restart/recover. This parameter is
#
# RETRY_DELAY = x
#
# Where x is a number representing the retry delay required and the
# delay time is 2^x seconds.
#
#===========================================================================
#RETRY_DELAY = 9
#===========================================================================
#
# MAPPING : OPTIONAL
#
# This parameter, if set denotes the supported default character set
#
# MAPPING = x
#
# Where x is ISO_646 - the default character set is ISO 646
# or ISO_8859_1 - the default character set is ISO 8859-1
#
#===========================================================================
#MAPPING = ISO_646

Elements of filestore configuration file
Elements of the FT-820 filestore configuration file are described
below.
Element Description
NSAP Identifies the NSAP address of the system on which the

(Optional) filestore is located. You must use hexadecimal octets for this
address.
TSAP Defines the name of the transport service access point

(Mandatory) (TSAP). It must be a value unique to the FTAM responder
you are installing. You can use hexadecimal octets or a
character string (including any ASCII characters) enclosed in
double quotation marks (“”) for the TSAP address.
An example of an entry in which a character string is used is:
TSAP = ”freds_386”
A four-digit number should be used for GOSIP conformance.
SSAP Defines the name of the session service access point

(Mandatory) (SSAP). You can use hexadecimal octets or a character
string (including any ASCII character) enclosed in double
quotation marks (" ") for the SSAP address. A four-digit
hexadecimal value of 1000 is recommended for GOSIP
conformance as this address need not be unique.
PSAP Defines the name of the presentation service access point

(Mandatory) (PSAP). You can use hexadecimal octets or a character
string (including any ASCII character) enclosed in double
quotation marks (" ") for the PSAP address. A four-digit
hexadecimal value is recommended for GOSIP
conformance. It need not be unique.
Note. If you are running over the AP-240, there must not be a
PSAP entry. Leave the value blank, or comment out the line
with a # symbol.
TITLE Defines the FTAM application entity title assigned to the

(Optional) filestore. Use this value until registration authorities are
created.
USER Defines the name of the default login name (initiator ID) that
(Optional) is to be used if a user does not specify one or if the
anonymous login name ANON is used when accessing a
filestore.
An example of an entry for this parameter is:
USER = ”guest”
You can restrict an anonymous user’s access to the filestore
by omitting this parameter in the configuration file.

Element Description
LIMIT Limits access to the filestore. If you set LIMIT to TRUE, the
(Mandatory) login name of all remote users is set to the user you identify
by the USER parameter. Hence, all users who access the
filestore are constrained to accessing the filestore with that
user’s permissions. If the filestore is not running as root, then
LIMIT must equal TRUE, and USER must be the name of the
user who starts the filestore. If you set LIMIT to FALSE, the
initiator ID and password of each incoming connection is
verified against the list of initiator IDs and passwords in the
AIX operating system /etc/passwd file and, if found, the
user who is trying to access the filestore is granted access
with his or her individual permissions.
Note. If you set LIMIT to TRUE, you must specify a name
after USER (see above).
NO_ACCESS_LIST Specifies the users for whom you want to deny access to the
(Mandatory) filestore. You specify the login names (initiator IDs) for the
users for whom you want to deny access.
An example of an entry for this parameter is:
{”root” ”wilma” ”fred”}
Note. You must separate each user name with a space
character.
MULTIPLE_PROCESSES Defines whether a new process is created each time a

(Mandatory) connect indication is received. Specify TRUE to create a new
process for each connect indication; specify FALSE if you do
not want to create multiple processes.
CONNECTS Defines the maximum number of remote users who can

(Mandatory) simultaneously access the filestore.
If you use the MULTIPLE_PROCESSES option, this is a limit
on the number of processes that can be created.
If MULTIPLE_PROCESSES is set to TRUE:
CONNECTS=75 for superuser
CONNECTS=25 for normal processes
If you are not creating multiple processes, use this formula to
calculate the maximum number of connections your system
can support:
( ( maximum number of open files per process ) − 10 )

2
Note. Round down the result. You must specify a value
greater than 1 and less than 16.

Element Description
LOCAL_CONC_CTRL Allows you to specify how you want to set up concurrency

(Mandatory) control on your system. You can set concurrency control
locally or globally.
Set this parameter to FALSE if you are going to run more than
one FTAM responder on your system; otherwise, set this
parameter to TRUE.
Note. You must set this parameter to FALSE if you set the
parameter MULTIPLE_PROCESSES to TRUE.
ATTRPATH Identifies the AIX operating system directory path to the

(Mandatory) attribute and concurrency databases.
Note. You must provide a directory path for this parameter.
You cannot specify a blank or null directory path.
AUDITPATH This set of parameters identifies the AIX operating system

AUDITLEVEL directory path to and the name of the audit trail file, and the
(Optional) amount of audit information you want. The audit trail file is
described in “Filestore audit trail file,” on page 50.
If you omit the directory path and filename, the audit
information is displayed on your screen (stderr).
The audit levels are as follows:
0 No audit information is generated.
1 Generate first level audit information (includes the
connect, release, and abort event types).
2 Generate second level audit information (includes the
connect, release, abort, select, create, deselect, and
delete event types).
3 Generate third level audit information (includes the
connect, release, abort, select, create, deselect,
delete, open, and close event types).
Note. To disable the audit trail, remove the AUDITPATH
parameter and set AUDITLEVEL to 0.
AUTHPATH Identifies the directory path to the authentication file, which is

(Mandatory) described in Chapter 5, “FT-820 Security.”
If you omit this parameter or leave the directory path blank or
null, the network address of incoming connect requests will
not be validated.
USER_CREATE_ These three parameters define the default AIX operating

PERMISSION system permissions that are used if the user does not send
GROUP_CREATE_ access control elements on the create request. You can set
PERMISSION any of these parameters to READ, WRITE, or READ_WRITE.
OTHER_CREATE_
PERMISSION
(Mandatory)

Element Description
TEXT_EXT Allows you to specify a default document file type for a file
(Mandatory) based on its extension (that is, the text that follows the last
period (.) in a filename).
By default, a file that does not have a file type already
associated with it in the FT-820 filestore is assigned FTAM-3
(unstructured binary) or NBS-9 (if the file is a directory).
You may want to make a file an FTAM-1 (unstructured text)
type rather than an FTAM-3 (unstructured binary). To
override the FTAM-3 (unstructured binary) file default, add
the extension of the file to the list of extensions between the
{ } symbols.
EFFECTOR Sets the effector the user wishes to apply to the file. By
(Optional) default, the form effector for FTAM-1 and FTAM-2 is a line
feed (<LF>). It is used as follows:
<LF> translates to <CR> <LF>
<CR> <LF> translates to <LF>
<LF> removed
<LF> added
You can set other control characters to be the effector, and
they will then be treated in the same manner as a linefeed.
For example, an effector stating EFFECTOR = 12 would
treat <FF> as an effector:
<FF> translates to <CR> <LF>
<CR> <LF> translates to <FF>
<FF> removed
<FF> added
Note. In the sample file, EFFECTOR is commented out of the
code with the # symbol.
DELETE_FAILED_FILE Allows you to configure the responder so it deletes any file

(Optional) that is the result of an unsuccessful transfer attempt.
Note. In the sample file, DELETE_FAILED_FILE is
commented out of the code with the # symbol.

Element Description
TRANSPORT_NAMES Names all of the transport providers for which you wish to
(Mandatory) receive connect indications. The names for the transport
providers are defined in the osid.cfg file, which is
described in the OSSC OSI Application Developer’s Guide.
QUALITY_OF_SERVICE Specifies the level of error recovery required by the utility

(Optional) (that is, fcp and fmv). This parameter is only meaningful
with the FT-825 ERPM product. The possible values are:
0 No error recovery is required.
1 Class I error recovery (that is, an error occurred
damaging the data transfer).
2 Class II error recovery (that is, the file needs to
be re-opened).
3 Class III error recovery (that is, the association
was broken).
Note. In the sample file, QUALITY_OF_SERVICE is
commented out of the code with the # symbol.
CHECK_WINDOW Defines the maximum number of checkpoints that may

(Optional) remain unacknowledged when the fcp or fmv utility is
sending a file to the filestore. This parameter is only
meaningful with the FT-825 ERPM product.
Note. In the sample file, CHECK_WINDOW is commented out
of the code with the # symbol.
MAX_RETRIES Defines the number of times that recovery/restart is

(Optional) attempted before an error is reported to the utility. This
parameter is only significant if you are using the FT-825
connection is 3.
Note. In the sample file, MAX_RETRIES is commented out of
the code with the # symbol.
MAX_TIME_LIMIT Defines the time limit (in seconds) after which

(Optional) recovery/restart attempts are stopped, and an error is
reported to the utility. This parameter is only significant if you
are using the FT-825 ERPM product and the negotiated
quality of service for the connection is 3.
Note. In the sample file, MAX_TIME_LIMIT is commented
out of the code with the # symbol.

Element Description
RETRY_DELAY Defines the time delayed (two to the power of RETRY_DELAY

(Optional) seconds) after a failure before recovery/restart is attempted.
This parameter is only significant if you are using the FT-825
connection is 3.
Note. In the sample file, RETRY_DELAY is commented out of
the code with the # symbol.
MAPPING Specifies the character set supported by the FT-820 utilities.

(Optional) The default is the ISO 646 character set.
Note. In the sample file, MAPPING is commented out of the
code with the # symbol.
Setting up the filestore configuration file

These steps show you how to set up the filestore configuration file
(ffs.cfg) for your system.
1. Use the AIX operating system’s text editor to correctly set the
parameters in the ffs.cfg filestore configuration file.
2. Save and exit from the filestore configuration file.
The filestore configuration file is ready for use.
Note. When you start the filestore, you must specify the path of
the ffs.cfg file on the command line.
Filestore audit trail file

The filestore audit trail file contains accounting information about
the FT-820 filestore.
Each entry in the filestore audit trail file may contain nine elements:
the filename, type of event, time at which the event occurred,
connection ID, initiator ID, AIX operating system user name, address
of the initiating system, error code, and error message (if any).
Note. Before a new filestore audit trail file is created, the existing file
is saved as xxx.BAK, where xxx is the name of the file specified in
the AUDITPATH element of ffs.cfg.

Sample filestore audit trail file
A typical filestore audit trail file follows:
event time connection ID initiator ID user name address
START 890510115643
CONNECT 890510115655 00001 ”tom” ”tom” /470004000600010101/1319/0000/0000
ABORT 890510115703 00001
CONNECT 890510115737 00002 ”ANON” ”ftam” /470004000600010101/2619/0000/0000
CONNECT 890510115738 00003 ”ANON” ”ftam” /470004000600010101/2619/0000/0000
RELEASE 890510115742 00003
RELEASE 890510115743 00002
CONNECT 890510115846 00004 ”tom” ”tom” /470004000600010101/1319/0000/0000
CREATE 890510115850 00004 ”/tmp/foobar”
OPEN 890510115851 00004 ”/tmp/foobar”
CLOSE 890510115902 00004 ”/tmp/foobar”
DESELECT 890510115903 00004 ”/tmp/foobar”
RELEASE 890510115922 00004
CONNECT 890510115925 00005 ”ed” ”ed” /470004000600010101/3619/0000/0000
FT2015 ”Initiator identity unacceptable.”
STOP 890510120000
error code error message filename
Note. The error code and error message shown in the above diagram
are displayed on a separate line due to space limitations. They are
normally displayed on the same line as the event that caused the
error.
Filestore audit trail file 51

Elements of the filestore audit trail file
Elements of the sample filestore audit trail file are described below.
Note that, depending on the particular event, some elements are
omitted from events shown in the example filestore audit trail file.
Element Description
Event Describes the action that occurs in the FT-820 filestore. Eleven
events are currently shown:
START The time when the FT-820 filestore was started.
CONNECT Information about establishing connections with
the filestore.
RELEASE Information about releasing connections with the
filestore.
ABORT Information about aborting connections with the
filestore.
SELECT Information about the file you are selecting.
DESELECT Information about the file you are deselecting.
CREATE Information about the file you are creating.
DELETE Information about the file you are deleting.
OPEN Information about the file you are opening.
CLOSE Information about the file you are closing.
STOP The time when the FT-820 filestore was
terminated.
Time Time at which the event occurred. The format of this time record
is yymmddhhmmss, where:
yy Last two digits of the year in which the event occurred.
mm Month in which the event occurred.
dd Day on which the event occurred.
hh Hour at which the event occurred.
mm Minute at which the event occurred.
ss Second at which the event occurred.
Connection If MULTIPLE_PROCESSES is set to FALSE, this element is an

ID integer that relates one event to another. For example, since the
first connect event is related to the next release event, both are
assigned the connection ID 0001. Connection IDs are reset to 1
after they reach 9998.
If MULTIPLE_PROCESSES is set to TRUE, this element is the
process ID of the filestore.
Initiator ID Initiator ID of the user who is attempting to access the FT-820

filestore, as passed through the FTAM initiator request from the
initiator.

Element Description
User name Login name of the user on the local AIX operating system. If
ANON or NULL is passed as the initiator ID, the user name is
taken from the USER parameter; otherwise, the user name takes
on the value passed in the initiator ID. If the LIMIT parameter is
set to TRUE, the user name is limited (that is, access is limited) to
only the default user specified in the USER parameter.
Address Address of the initiating system (the system from which a user is
attempting to access the FT-820 filestore). The slash (/)
separates the hexadecimal addresses of the SAPs, in the
following order:
NSAP/TSAP/SSAP/PSAP
Error code Error code that was generated during an event (if an error
occurred). Error codes are described in Appendix A, "Error
Messages"
Error Error message that is associated with an error code that was
message generated during an event (if an error occurred). Error messages
are described in Appendix A, "Error Messages"
Filename Name of the file that is being created, selected, opened, closed,
deselected, or deleted.
Utility audit trail file

The utility audit trail file contains information about the FT-820
utilities.
Each entry in the utility audit trail file may contain nine elements:
filename, name of the invoked utility, type of request/confirmation,
time of the request/confirmation, connection ID, initiator ID,
address of the filestore, error code, and error message (if any).
Sample utility audit trail file

A typical utility audit trail file follows:

request/ utility
confirmation name connection ID initiator ID address
START 920226131049 fcp

CONNECT REQUEST 920226131053 00001 ”tom” /4700040006000108002b06209e01/2345/5
SELECT REQUEST 920226131056 00001 ”/tmp/bert”
OPEN REQUEST 920226131056 00001 ”/tmp/bert”
SELECT CONFIRM 920226131108 00001 ”/tmp/bert” FT3004 ”Non-existent file.”
ABORT REQUEST 920226131117 00001
time filename error code error message
Elements of the utility audit trail file

Elements of the utility audit trail file are described below. Note that,
depending on the particular event, some elements are omitted from
events shown in the example utility audit trail file.
Element Description
Request/ Describes the action that occurs in the FT-820 filestore. Ten
confirmation events currently can be reported:
START The time when the FT-820 filestore was started.
CONNECT Information about establishing connections with
the filestore.
RELEASE Information about releasing connections with the
filestore.
ABORT Information about aborting connections with the
filestore.
SELECT Information about the file you are selecting.
DESELECT Information about the file you are deselecting.
CREATE Information about the file you are creating.
DELETE Information about the file you are deleting.
OPEN Information about the file you are opening.
CLOSE Information about the file you are closing.
Utility name Name of the FT-820 utility that was invoked.

Element Description
Time Time at which the request/confirmation occurred. The format of

this time record is yymmddhhmmss, where:
yy Last two digits of the year in which the event occurred.
mm Month in which the event occurred.
dd Day on which the event occurred.
hh Hour at which the event occurred.
mm Minute at which the event occurred.
ss Second at which the event occurred.
Connection Relates one request/confirmation to another.

ID Request/confirmations over the same connection are assigned
the same connection ID. Connection IDs are reset to 1 after they
reach 9998.
Initiator ID Initiator ID of the user who invoked the FT-820 utility.
Address Address of a responding system with which the utility is trying to

establish a connection.
Filename Name of the file that is being created, selected, opened, closed,
deselected, or deleted.
Error code Error code that was generated during a request/confirmation (if
an error occurred). Error codes are described in Appendix A,
"Error Messages"
Error Error message that is associated with an error code that was
message generated during a request/confirmation (if an error occurred).
Error messages are described in Appendix A, "Error Messages"

3 Filestore
T his chapter discusses starting and stopping the filestore, in

foreground or background, as well as using the lock manager utility
and setting the number of users. This chapter also discusses the
preparation and configuration that FT-820 and FT-825 require before
they can run properly.
The lock manager must be running before the filestore starts. If you
use the startup script to start the filestore (see page 60), the lockmgr
command is executed automatically.
Configuring FTAM
For FT-820 and FT-825 to operate properly, you need to configure the
FTAM and supporting software. Some of the following tasks are
mandatory, and some are optional.
Configuring FT-820
You need to verify the configurable values in the FT-820 support
files. In many cases, there are default values, which may be
appropriate to your system.
• Set up the filestore configuration file (see page 39). The default
file is ffs.cfg. This file must contain one or more of the
filestore system’s transport provider names. You should verify
the number of supported connections, the directories for the at-
tributes databases and the audit trail file, and check that the
57
anonymous user name is recognized. You may also choose to
change the default values for the other parameters in this file.
• Verify or set up an application entity table. The default file is

__AETABLE__ (see “Application entity table file,” on page 12).
The AE table associates a user-friendly name with each filestore
or user. You must ensure that every application entity with
which FT-820 responders or initiators will communicate is in
__AETABLE__.
• If you are running FTAM with multiple processes (if the

MULTIPLE_PROCESSES parameter in the filestore configura-
tion file is set to TRUE), then the permissions on the
/usr/lpp/ossc/ulcommon/config directory must be set to
777. This allows non-root filestores to access the database. (See
“Security driver,” on page 79.)
• Optionally, you may want to set one or more of the environ-

ment variables AETABLE, FTAMLOCAL, and FILESTORES (see
the FTAM User Guide).
• Optionally, you may want to set up the initiator configuration

file (see “Utility configuration file,” on page 17). The default
configuration file is .ftinit. If you do not use the utility con-
figuration file, default values will apply to the configurable pa-
rameters.
Preparing the databases

These tasks must be completed before FT-820 is started. If you use
the startup script, they are accomplished automatically. If you use
the ffs utility command, you must precede that command with
these actions:
• Start the lock manager utility. See “Database lock manager utili-
ty: lockmgr,” on page 59.
• Update the attributes database. See “Updating the FT-820 at-

tributes database,” on page 74.
• Initialize the attributes and concurrency control databases. See

“Initialize FT-820 databases utility: finit,” on page 68.
58 Chapter 3 • Filestore
Database lock manager utility: lockmgr
The lock manager program controls concurrent access to the FT-820
database files, based on the concurrency locks associated with each
file. These locks are assigned through default values. For more
information about concurrency locks, see “Filestore audit trail file,”
on page 50.
The lockmgr command runs automatically when you run the start
filestore command, ft820.rc start.
The syntax for lockmgr is shown here:
lockmgr [-u n]
Command line options that are used with lockmgr are listed below:
Option Description
-u Allows you to assign the maximum number of filestore

processes that can request access to the FT-820
databases
Note. If you selected the MULTIPLE_PROCESSES option
for the FTAM responder in the filestore configuration file,
you may need to increase the maximum number of users
defined for the database lock manager. This command
runs automatically when you run ft820.rc start, as
described in the section “Starting the filestore,” on page 60.
n Maximum number of filestore processes. If you do not
specify a number, the default value is 16.
Starting the lock manager

These steps show you how to start the FT-820 lock manager.
1. Change to the directory where lockmgr exists.
2. To start the lock manager, type:
lockmgr -u 16
The following message displays on the screen:

Raima Data Manager Version x.xx
Database Lock Manager for AIX (LMC_SEMAPHORE)
Copyright 1986-1992 Raima Corporation, All rights reserved.
Database lock manager utility: lockmgr 59

Starting the filestore
You can start the filestore either by using the provided startup script
or by issuing the necessary commands yourself. Before starting the
filestore, you should be sure that the filestore and initiator are
adequately configured.
Startup script
The following steps show you how to start the filestore using the
startup script.
Note. lockmgr must be running on the system before starting the

filestore. See page 59 for information about the lockmgr utility.
1. Change to the directory where ft820.rc resides.
2. To start the filestore, type:
ft820.rc start
Messages similar to the following display on the screen. (If you

have FT-825 installed, your messages will look slightly
different.)
OSSC FT-82X Filestore [Version X.XX]

ISO-8571 File Transfer, Access and Management
(c) Copyright IBM Corporation 1993-1994. All rights reserved.
FFS: pid = nnn
OSSC FT-820 Filestore running.
Manual startup
If you prefer to start the filestore without using the startup script,
you can do so with the ffs command. When you start the filestore
with the ft820.rc start command, a shell script executes that
also starts the lock manager, updates the attribute database, and
clears the concurrency locks. If you want to start the filestore
manually, you must issue the ffs command after these tasks:
• Start the lock manager. Refer to “Starting the lock manager,” on

page 59.
• Update the attributes database. See Chapter 4, “Maintaining
FT-820,” for information about updating the attributes data-
base.
• Clear the concurrency locks. See Chapter 4, “Maintaining

FT-820,” for information about clearing the concurrency locks.
FT-820 filestore utility: ffs

You use the FT-820 utility ffs to start the FT-820 filestore. The
syntax for ffs is shown here:
ffs [-g] [fs_config_file]
Command line options that are used with ffs are listed below:
Option Description
-g Allows you to run the filestore in the foreground. If you do

not use this option, the default is for the filestore to start in
the background.
fs_config_file Name of the file (including the directory path) that contains
the configuration information required to start the filestore.
If you do not specify a configuration file, the default
configuration file (ffs.cfg) in your local directory is
used.
The FT-820 filestore utility is an implementation of the FTAM virtual

filestore. The FTAM virtual filestore is used to describe files and
their attributes.
The ffs utility maps the FTAM file attributes and FTAM primitive
operations from the FTAM virtual filestore into the real operating
system filestore (in this case, AIX).
The OSSC implementation of the FTAM filestore supports the five

file types described in Table 1.1, on page 6.
The FTAM file attributes reflect the state of the file as it is actually
stored in the virtual filestore. The ffs utility uses both the AIX
operating system and an attribute database to keep track of the file
attributes. The AIX operating system maintains its attributes
internally, and FTAM maintains its attributes in a database within
the file system. All of the attributes that the AIX operating system

and FTAM maintain are listed in Table 3.1. Not all attributes are
supported by the OSSC implementation of FTAM.
File attributes are created either by an FTAM initiator or native AIX.

If a file is created through the FTAM protocol, the initial attribute
settings passed by the initiator are saved in the FTAM attribute
database. If a file is created by a user, some of the specific FTAM
attributes (for example, storage account, legal qualifications, and file
availability) will not exist. The ffs utility sets some of these non-
existing FTAM-specific attributes by using the default values
specified in ffs.cfg when a native AIX file is accessed by an FTAM
initiator.
Table 3.1 defines how the FTAM attributes are returned to an

initiator by the ffs utility. Each attribute contains two return values,
one if the file is created by FTAM and one if the file is created by
native AIX.
Table 3.1 File attributes supported by FTAM
Attribute Returned value
Filename FTAM: Full AIX filename (including path).

AIX: Full AIX filename (including path).
Permitted actions FTAM: Permitted actions passed in the FTAM create

request.
AIX: Current AIX permissions “ANDed” with creation
permitted actions.
Contents type FTAM: File type passed in the FTAM create request.
AIX: The file type is determined by the AIX operating
system (FTAM-1, FTAM-3, or NBS-9).
Storage account FTAM: Value passed in create request.

AIX: Not supported.
Date and time FTAM: Not supported.

of creation AIX: Not supported.
Date and time of FTAM: Indicates when the contents of the file were last
last modification modified.
AIX: Indicates when the contents of the file were last
modified.
Table 3.1 File attributes supported by FTAM (continued)
Date and time of FTAM: Indicates when the contents of the file were last
last read access read.
AIX: Indicates when the contents of the file were last
read.
Date and time FTAM: Indicates when the value of a file attribute was
of last attribute last modified
modification AIX: Indicates when the value of a file attribute was
last modified.
Identity of creator FTAM: Set to the current initiator identity when the file is
created.
AIX: Retrieves the user name associated with the
current user.
Identity of last FTAM: Not supported.

modifier AIX: Not supported.

reader AIX: Not supported.

attribute modifier AIX: Not supported.
File availability FTAM: Indicates whether delay should be expected

before the file can be opened.
AIX: Not supported.
File size FTAM: Set to the nominal size of the file, in octets, when
the file is closed.
AIX: Set to the nominal size of the file, in octets, when
the file is closed.
Future file size FTAM: Indicates the nominal size of the file, in octets, to
which the file may grow as a result of modification
and extension.
AIX: Not supported.
Access control FTAM: An action is present if the equivalent entry is set to

(action list) TRUE.
AIX: Not supported.
Access control FTAM: A set of concurrency keys associated with each

(concurrency) action. Each key defines the possible values of
the concurrency locks.
AIX: Not supported.

Table 3.1 File attributes supported by FTAM (continued)
Access control FTAM: Compared against the current initiator identity.

(identity) AIX: Compared against the AIX access classifications
of USER, GROUP, or OTHER.
Access control FTAM: Consists of a vector of passwords, each of which

(password) is associated with an action in the action list.
AIX: Not supported.
Access control FTAM: An application entity title that is compared to the

(location) current initiator ID.
AIX: Not supported.
Legal qualifications FTAM: Conveys information about the legal status of the
file and its use. This is set at file create time.
AIX: Not supported.
Stopping the filestore abruptly

You may sometimes want to immediately stop the FT-820 filestore
on your system. These steps show you how to abruptly stop the
filestore.
☞ Caution. Do not use the utility kill -9 to stop the FT-820 filestore
or you may seriously damage the FT-820 databases.
1. Change to the directory where ft820.rc is located.
2. To abruptly stop the filestore, type:
ft820.rc stop
The following messages display on the screen:
Killing FFS - PID = nnn

FFS: Aborting all connections...
Killing lockmgr - PID = nnn
FFS: Filestore exiting
OSSC FT-820 Filestore shutdown
The FT-820 filestore closes all connections and exits

immediately.
Stopping the filestore gracefully
These steps show you how to stop the FT-820 filestore on your
system gracefully.
1. Use the AIX operating system’s utility command ps -e to list

the current background processes on your system.
2. Find the process ID (PID) for the filestore (listed as ffs) you
want to stop.
3. At the system prompt, type:
kill -1 PID
where PID represents the PID for the filestore you want to stop.
OSSC FT-820 Filestore [Version x.xx]

(c) Copyright IBM Corporation 1993-1994. All rights
reserved.
FFS: Waiting for connections to release...
All subsequent connect requests are rejected. When all existing

connections have been released, the filestore exits.
☞ Caution. Do not use the utility kill -9 to stop the FT-820 filestore
or you may seriously damage the FT-820 databases.
Stopping the filestore running in foreground

To stop the FT-820 filestore that is running in the foreground on your
system, press CTRL+C or the keys to which interrupt (SIGINT 2) is
set. The following message displays on the screen:
OSSC FT-820 Filestore [Version x.xx]

(c) Copyright IBM, 1988-1993. All rights reserved.
FFS: Aborting all connections...
The filestore aborts all connections and exits immediately.

4 Maintaining FT-820
T his chapter discusses using and maintaining the attributes

database and the concurrency control database, including the
initialize databases (finit), display attributes (fda), and update
attributes (fua) commands.
FT-820 databases
The two FT-820 databases, namely the attributes database and the
concurrency control database, contain dynamic information about
the files on a filestore, and must be updated regularly so that they
reflect the true current state of the filestore.
• The attributes database contains the attributes for every file that
FTAM creates in the filestore. (The vfsattdb.d01 and
vfsattdb.k01 files contain the data and key information for
the attributes database.)
• The concurrency control database contains the current locks on

each open file that FTAM creates in the filestore. (The
vfsccdb.d01 and vfsccdb.k01 files contain the data and
key information for the concurrency control database.)
When you first start the filestore, you must initialize each of these
databases. If the filestore’s system crashes or suffers some
corruption, you may need to reinitialize these databases. The
commands for the first initialization and a subsequent
reinitialization differ; instructions for each procedure appear later in
this chapter.
67
The file attributes that are reflected in these files are initially
established when the file is created. When the FT-820 copies or
moves a data file, the newly created file’s attributes are derived from
the original file’s attributes. See “Utility configuration file,” on
page 17, for information on assigning file attributes using .ftInit.
When changes are made to the attributes and concurrency control

databases, they are stored in the vista.taf file before they are
reflected in the databases.
Note. The attributes database, concurrency control database, and the

directory in which they reside must have read, write, and execute
permissions for all users (owner, group, and other) in order to use a
multiple process filestore.
Initialize FT-820 databases utility: finit

You use the FT-820 utility finit to initialize or reinitialize the
attributes and concurrency control databases. The syntax for finit
is:
finit [-a] [-c] [-y] [fs_config_file]
The command line options are listed below:
Option Description
-a Allows you to initialize only the attributes database.

-c Allows you to initialize only the concurrency control
database.
-y Allows you to force the initialization of the existing
databases. It suppresses prompts and performs every
choice of action. You can use this option when using
finit in a script or command file.
the configuration information required to initialize the
databases. If you do not specify a configuration file, the
default configuration file ffs.cfg in your local directory is
used.
➥ Important. When finit is invoked, all FTAM file records on the

filestore that were created by remote users will have their attributes
reset to the default values.
68 Chapter 4 • Maintaining FT-820

Initializing the FT-820 databases
These steps show you how to initialize the attributes and
concurrency control databases for the first time after installing the
databases on your system. Refer to “Reinitializing the FT-820
databases,” on page 72, for information on reinitializing these
databases.
1. Change to the directory where finit is located.
2. Initialize the attributes database first. At the system prompt,

type:
finit -ay [fs_config.file]
OSSC FT-82X Database Initialization Utility [Version x.x]

(c) Copyright IBM Corporation 1993-1994OSSC. All rights
reserved.
vfsattdb.dbd initialized
3. Are you using global concurrency control? (Did you set the
parameter LOCAL_CONC_CTRL to FALSE in the filestore
configuration file?)
If no, you are finished with the initialization procedure. You do

not need to initialize the concurrency control database.
If yes, initialize the concurrency control database by completing

step 4.
4. At the system prompt, type:
finit -cy [fs_config.file]

vfsccdb.dbd initialized
Initialize FT-820 databases utility: finit 69

Display attributes utility: fda
You use the FT-820 utility fda to display the contents of the FT-820
attributes database. The syntax for fda is shown here:
fda [-a] [-c] [-f] [-i] [-p] [fs_config_file]
Command line options that are used with fda are listed below:
Option Description
-a Allows you to display the permitted actions for each file.

-c Allows you to display the access control elements (ACEs)
for each file.
-f Displays all information in the attributes database.
-i Allows you to display the i-node numbers for each file.
-p Allows you to display the document type parameters for
each file.
the configuration information required to start the filestore.
If you do not specify a configuration file, the default
configuration file ffs.cfg in your local directory is used.
Displaying contents of the attributes database

These steps show you how to display the contents of the FT-820
attributes database.
1. Change to the directory where fda exists.
2. To display all attributes, type:
fda -f [fs_config.file]
OSSC FT-82X Attribute Database Display Utility [Version x.x]

This message is followed by the table of attributes illustrated

and described as follows.

Note. These are the FTAM file attributes as defined in ISO 8571-2.
Only one file is shown in the figure. In a real database, the attributes
for every file on the filestore would display.
document device i-node permitted

type number number filename actions list identity
FTAM-3 3 1681 /usr/wilma/todo

Permitted actions: Read ReplExteErasRdAtCgAtDeleTrav RvTr
USER GROUP OTHER
Read ON NR SH EX NA ON NR SH EX NA ON NR SH EX NA
Insert OFF NR NA OFF NR NA OFF NR NA
Replace ON NR SH EX NA ON NR SH EX NA ON NR SH EX NA
Extend ON NR SH EX NA ON NR SH EX NA ON NR SH EX NA
Erase ON NR SH EX NA ON NR SH EX NA ON NR SH EX NA
Read At ON NR SH EX NA ON NR SH EX NA ON NR SH EX NA
Chng At ON NR SH EX NA OFF NR NA OFF NR NA
Delete ON NR SH EX NA ON NR SH EX NA ON NR SH EX NA
String Length: unbounded
String Significance: NOT-SIGNIFICANT
Total Number of entries = 1

document type concurrency
action list parameters keys
Element Description
FTAM-3 3 1681 This element includes the document type (FTAM-3),

/usr/wilma/todo the device (3), the i-node number (1681), and the
pathname (/usr/wilma/todo).
Read ... RvTr This element lists the permitted actions. The
permitted actions attribute is a vector attribute and
indicates the set of actions that can be performed on
the file, and the set of file access data unit (FADU)
identity styles that can be used in the actions for file
access. Any combination of these possible values is
valid:
Read read RdAt read attributes
Inse insert CgAt change attributes
Repl replace Dele delete file
Exte extend Trav traversal
Eras erase RvTr reverse traversal
Rand random order
Display attributes utility: fda 71

Element Description
USER GROUP OTHER These are the identity portions of the three elements
of the access control attribute, which defines the
conditions under which access to the file is valid.
Each element gives one condition under which
access to the file is valid, and consists of three parts:
the identity, the action-list, and the concurrency keys.
Access to a file is determined by the initiator’s
relationship to the file. The initiator may be the owner
of the file (USER), in the same group as the owner
(GROUP), or not in the same group (OTHER). After this
relationship is determined, an access control element
is selected from the database.
Read This is the action list, which appears vertically, to the
: left of the elements. The status (ON/OFF) is listed to
Delete the right of each action. The action list is used
whenever an attempt is made to access the file.
ON/OFF states whether the particular action in the
action list is available to the identity
(USER/GROUP/OTHER) in that access control
element.
NR SH EX NA These are the concurrency keys. They show the
possible values of the concurrency locks that the file
accessor may request. The values are:
NR not required
SH shared
EX exclusive
NA no access
These keys are explained on page 30.
Reinitializing the FT-820 databases

You may need to reinitialize the attributes database after the system
on which a filestore is located crashes or unexpectedly shuts down.
When users receive a series of error messages prefixed with DB when
they try to access the filestore, you probably need to reinitialize the
database.
In addition, if concurrency control is set to global (if

LOCAL_CONC_CTRL is set to FALSE in the filestore configuration
file), you may need to reinitialize the concurrency control database
after the system on which a filestore is located crashes or after
someone incorrectly kills the filestore.

Once the attributes database has been reinitialized, all files on that
filestore that were created by remote users will have their attributes
reset to the default values. For instance, if a remote user had created
a text file (FTAM-1 type) before the reinitialization, it would have its
attribute changed to unstructured binary type (FTAM-3).
To reinitialize the attributes and concurrency control databases,

follow this procedure:
1. Change to the directory where finit exists.
2. Do you want to reinitialize global concurrency control?
If no, skip to step 4. If yes, type:
finit -c
The following prompt displays on the screen:

Do you want to initialize the Concurrency Control database?
3. Type y for yes (or n for no).
If you answer “yes,” the following message displays on the

screen:
vfsccdb.dbd initialized
4. Reinitialize the attributes by typing:
finit -a
The following prompt displays on the screen:

Do you want to initialize the Attribute database?
5. Type y for yes (or n for no).
vfsattdb.dbd initialized
Reinitializing the FT-820 databases 73

6. If the filestore is running, kill and restart it.
If the filestore is not running, simply restart it.
Note. Initializing these databases for the first time is described in

“Initializing the FT-820 databases,” on page 69.
Update attributes utility: fua

You use the FT-820 utility fua to update the attributes in the FT-820
attributes database. The syntax for fua is shown here:
fua [fs_config_file]
The command line option fs_config_file is the name of the file

(including the directory path) that contains the configuration infor-
mation required to start the filestore. If you do not specify a configu-
ration file, the default configuration file ffs.cfg in your local
directory is used.
Updating the FT-820 attributes database

When a local user uses an AIX operating system utility to move,
remove, or rename a file that was created by FTAM, the attributes
database and the AIX operating system’s file system become
unmatched.
You use the fua utility to verify that any files that users moved,
removed, or renamed exist on the AIX operating system’s file
system, and, if they do, to bring the attributes database into
correspondence with the AIX operating system’s file system.
Note that using this utility is not mandatory; how often you need to
update depends on the level of FTAM activity.
To update the FT-820 attribute database, follow this procedure:
1. Change to the directory where fua exists.
2. Type:
fua

OSSC FT-82X Attribute Database Update Utility [Version x.x]

This message is followed by a series of other messages like

these:
UPDATING database entries:

- /tmp/m586copy.s
- /tmp/m586copy.1st
- /tmp/wd
- /tmp/makefile
ENTRY REMOVED - /tmp/sess/Sact.c
ENTRY REMOVED - /tmp/sess/Sdefs.h
Total Number of entries= 6

Total Number of deletions= 2
Total Number in database= 4
Update attributes utility: fua 75

5 FT-820 Security
T his chapter discusses the use of the authentication file to control

access to the FT-820 filestore, and the use of the security driver to
check effective user and group IDs.
Authentication file
The FT-820 authentication file controls access by users to the FT-820
filestore.
You may also control access to the FT-820 filestore by specifying the
network address of only those systems through which you want
users to access the FT-820 filestore.
Sample authentication file

A typical FT-820 authentication file appears below:
# (C) Copyright IBM Corporation 1993-1994. All rights

reserved.
#
# This software is furnished under a license and use,
# duplication, disclosure and all other uses are
# restricted to the rights specified in the written
# license between the licensee and IBM.
#
# Virtual Filestore Authentication
#
# This file contains the network addresses of all
77
# application entities that are allowed access to the
# FT-820 filestore. The address of the application
# entity of the user who is attempting# to access the
# FT-820 filestore is compared to the address in this
# file. If the address is found, the user is allowed
# access. If the address is not found, the
# connection is rejected and error “FT0005 FTAM
# management - security not passed” is generated.
#
# Entries in this file may be partial addresses only.
# This will allow ranges of network addresses to gain
# access. For example, if the entry 490104 is entered
# in the table, then any address with 490104... will
# gain access.
#
# NOTES for filling in this file:
#
# Enter network addresses in HEX octets only. For
# example:
# 490104000600010207010061B101.
#
4901 # Allow OSINET addresses only.

Text that follows this symbol is ignored. A comment can occur
anywhere in a configuration file, even on the same line as a
parameter. The beginning of the comment must be separated from
the parameter by at least one space.
The FT-820 authentication file consists of a single element, which is

described as follows:
Element Description
4901 This element identifies the network address or range of

addresses for users who are allowed to access the filestore. You
use hexadecimal octets for the network address. Only the digits
listed are checked. Examples of an entry for this parameter are:
490104000600010207010061B101
which specifies a specific network address, or just
4901
which specifies a range of any addresses whose initial digits are
4901.
78 Chapter 5 • FT-820 Security

Security driver
The FT-820 product includes an optional kernel driver for security
checking. If this driver is installed in the kernel, and the ffs process
is owned by the superuser, the owner and group ID of the ffs
process can change to those of the remote user.
If the driver is not installed, the ffs utility checks to see if a remote
user has access to the file only when the operation is first started.
Therefore, if the file permissions change (that is, if remote user access
is denied during the operation), ffs cannot detect it. However, if the
security driver is installed, file access permissions are checked
continually during the operation, and if access is revoked, the
operation is terminated.
Note. You do not need to use the security driver if

MULTIPLE_PROCESSES is set to TRUE, or if ffs is running as a
single process not owned by root. In these modes, the real user and
group IDs are set to the initiator’s values (that is, the initiator is the
owner of the fileserver process).
➥ Important. If you want to prevent an unauthorized person from

accessing your utilities through the FT-820 product, OSSC
recommends that you do not run ffs as root or as a superuser.
File and directory permissions

FT-820 requires that the owner of a process must at least be able to
read and write to the database files, and read the __AETABLE__ file.
If MULTIPLE_PROCESSES is set to TRUE, the permissions must
allow everyone to access the necessary files, since a process spawned
by root has the user ID of the initiator ID. Figure 5.1 shows the
minimum permissions necessary for the attributes database,
concurrency control database, and __AETABLE__ files, and the
directories they reside in.
File and directory permissions 79

Database files:
Root user Non-root user
Minimum permissions: Minimum permissions:

Single
process 700 → for the directory 700 → for the directory
600 → for the file 600 → for the file
Minimum permissions:
Multiple
processes 777 → for the directory
666 → for the file
__AETABLE__ file:
Root user Non-root user
Minimum permissions: Minimum permissions:

Single
process 500 → for the directory 500 → for the directory
400 → for the file 400 → for the file
Minimum permissions:
Multiple
processes 555 → for the directory
444 → for the file
Figure 5.1 Minimum permissions for files and their directories
Note. If both the database files and __AETABLE__ file reside in the
same directory, the directory requirements for the database files
override the directory requirements for the __AETABLE__ file.
Setting up the AIX password file

To permit remote users access to the FT-820 filestore, revise the
password file on the system running the FT-820 filestore to add
remote user login names and passwords. See your system
documentation on how to add entries to your password file in
whatever manner is appropriate to your system.
Add an entry to the password file for each remote user to whom you
wish to grant filestore access.

Note. If you use the USER and LIMIT parameters in the filestore
configuration file to allow only anonymous users to access the
FT-820 filestore, you need only add an entry for the name of the user
specified after USER in the filestore configuration file (ffs.cfg). If
LIMIT is set to TRUE, then the initiator_id/password pair is
not verified by the FT-820 filestore. These parameters are described
starting on page 45.
Setting up the AIX password file 81

A Error Messages
T his appendix describes error messages you might encounter

while running FT-820. There are three types of error messages,
depending on which element of the system generated the error:
FTAM filestore errors, operating system errors, and errors generated
by the FT-825 or FT-820 utilities. Each type is described in its own
section. If you receive an error message that is not listed in this
appendix, see your system administrator.
A typical FT-820 error message is shown below. It consists of three

parts:
FT002 System shutdown
prefix sequential description

code
Each of these elements is described in the following table.
Table A.1 Elements of an FT-820 error message
Element Sample Description
Prefix DB This type of error is generated by the

FT-820 database.
FS This type of error is generated by the
FT-820 filestore.
83
Table A.1 Elements of an FT-820 error message (continued)
Element Sample Description
FT Errors of this type are defined in the ISO

FTAM protocol specification. Although
these errors are generated by the FT-825
and FT-820 utilities and any filestores with
which the utilities communicate, they are
reported only by the utilities.
OS This type of error is generated by the
FT-820 utilities. It indicates that an error
occurred in the local AIX operating system.
UT This type of error is generated by the
FT-820 utilities. It indicates that a limitation
or a user input error occurred (for
example, insufficient memory or incorrect
command line syntax).
Sequential 0002 A sequential code number that is

code associated with a particular error
message.
Description System shutdown. A description of the error code number.
Database error messages

Errors with the prefix DB originate in the FT-820 database.
The individual messages are listed in the following table.
Table A.2 Database error messages
Error code Error message and description
DB0002 Record not found

Reason: Returned by the key retrieval function when the
requested key is not found.
DB0004 Cannot find vfsccdb.dbd

Cannot find vfsattdb.dbd
Reason: The finit utility cannot find the attributes and
concurrency control databases.
Action: Check the path and filename for the filestore
configuration file and reissue the finit
command.
84 Appendix A • Error Messages

Table A.2 Database error messages (continued)
DB0005 lockmgr user limit exceeded

Reason: Too many processes are trying to access the
lockmgr.
Action: Increase the limit by running the lockmgr
command with an increased value for the -u
option.
DB0900 No more space on file

Reason: An application program may have corrupted
runtime memory.
Action: Reinitialize the database using the finit utility.
DB0901 System error

Reason: Runtime memory is corrupted.
Action: Reinitialize the database using the finit utility.
DB0905 Cannot open database files

Reason: An error may have occurred opening a data file
or key file. This error usually occurs because the
file does not exist or is read/write protected.
If MULTIPLE_PROCESSES in the ffs.cfg
configuration file is set to FALSE, this error may
also indicate that too many connections have
been established.
Action: Reinitialize the database using the finit utility
and check that the databases files have
read/write permissions.
If MULTIPLE_PROCESSES is set to FALSE, limit
the number of connections supported in the
ffs.cfg configuration file to:
CONNECTS=(maximum open files per process – 10) / 2
The AIX operating system parent directory must
include read/write permissions if
MULTIPLE_PROCESSES is set to TRUE.
DB0907 Unable to read transaction activity file

Reason: An error occurred when the vista.taf file in
the attribute database directory was opened or
read.
Action: Check that the FT-820 filestore has read/write
access to the attribute database directory and its
files.
Database error messages 85

Table A.2 Database error messages (continued)
DB0911 Maximum concurrent user limit exceeded

Reason: The maximum number of filestores or users that
can concurrently access the database has been
exceeded.
Action: Reduce the number of filestores or users that
access the database by changing the value of
CONNECTS in the ffs.cfg configuration file.
DB0917 No access to lockmgr pipe in usr/spool/OSSC

Reason: This error may occur if the filestore does not
have access to the usr/spool/OSSC/
lockmgr named pipe file, or if the lockmgr
number of users option (-u) has been set too
low.
Action: If you are using the MULTIPLE_PROCESSES
option in the ffs.cfg configuration file, run the
lockmgr command with an increased value for
the -u option.
The AIX operating system parent directory must
include read/write permissions if
MULTIPLE_PROCESSES is set to TRUE.
DB0920 Lock manager (lockmgr) is not running

Reason: The lock manager (lockmgr) is not installed.
Action: Install the lock manager and restart your
application program.

Filestore error messages
Errors with the prefix FS originate in the FT-820 filestore.
Table A.3 Filestore error messages
FS0001 HEX value too long in configuration file

Reason: The number of hexadecimal digits that make up
a service access point (SAP) parameter in the
configuration file exceeds one of the following
limits:
SAP type Maximum number of hexadecimal digits
NSAP 20
TSAP 32
SSAP 16
PSAP 16
Action: Decrease the number of hexadecimal digits in
the parameter.
FS0002 String too long in configuration file

Reason: The number of characters in a text string
parameter in the configuration file exceeds one
of the following limits:
Parameter Maximum number of hexadecimal digits
TSAP 32
SSAP 16
PSAP 16
USER 16
ATTRPATH 60
AUDITPATH 60
Action: Decrease the length of the text string if a double
quotation mark (“) is located at the end of the text
string.
FS0003 AE title too long in configuration file

Reason: The AE title parameter (TITLE) in the
configuration file exceeds16 components.
Action: Check the AE title and change if incorrect.

Table A.3 Filestore error messages (continued)
FS0004 Too many connections in configuration file

Reason: The number of FTAM connections specified in
the configuration file is greater than 16 (the
maximum number of connections if you have not
selected MULTIPLE_PROCESSES in the
ffs.cfg configuration file), or your system does
not support the number of FTAM connections
specified in the configuration file.
Action: Calculate the maximum number of FTAM
connections for your system (using the formula
below) and change the number in the
configuration file.
If MULTIPLE_PROCESSES is set to TRUE:
CONNECTS=75 for superuser
CONNECTS=25 for normal processes
If MULTIPLE_PROCESSES is set to FALSE:
CONNECTS=(max. open files per process – 10) / 2
FS0005 Illegal value in configuration file ––

Reason: The syntax of a parameter in the configuration
file is incorrect, or an invalid character is used in
the configuration file.
Action: Remove any invalid characters.
FS0006 Error in configuration file –– [syntax

error in line n near parameter_name]
Reason: The syntax used in the configuration file is
incorrect. This error message is usually caused
by the parameter immediately preceding the
parameter cited in the error message.
Action: Correct the syntax error in the configuration file.
FS0007 Configuration file not found at: xxx

Reason: The configuration file or directory specified by
xxx does not exist, or the configuration file is not
located in the directory specified.
Action: Check the configuration file and directory
specified and reissue the command.

FS0008 Must supply valid USER when using LIMIT

Reason: The LIMIT parameter is set to TRUE in the
filestore configuration file, but a value for the
USER parameter is not specified. When LIMIT is
set to TRUE, the USER parameter must be set.
Action: Specify a name for the USER parameter or set
LIMIT to FALSE.
FS0009 USER not found in password file

Reason: The value for the USER parameter (initiator ID) in
the configuration file does not exist in the
/etc/passwd file of the AIX operating system.
Action: Check that the value for USER was entered
correctly, or add the login name to the
/etc/passwd file.
FS0010 Cannot create audit trail file

Reason: An error was returned from the AIX operating
system when the audit trail file was created.
Action: Check the specified pathname of the audit trail
file in the filestore configuration file and change it
if it is incorrect.
Make sure that FTAM users have write
permissions to the audit trail file and its directory.
FS0011 Bad HEX value in configuration file

Reason: An invalid hexadecimal value was found in the
configuration file. Hexadecimal values consist of
at least one pair of ASCII characters, each
character in the following range: 0-9, A-F, or a-f.
Action: Make sure the hexadecimal value has an even
number of characters and that all the characters
are within the allowable range, and change if
incorrect.
Note. Prefix the network address with a zero if
you would like to use an odd number of
characters in the network address.
FS0012 Cannot activate session layer

Reason: An error occurred while activating the session
layer.
Action: Check that the transport software is installed and
running.

FS0013 Unable to allocate sufficient memory

Reason: There is insufficient memory or swap space for
the filestore to operate.
FS0014 Background filestore process died

Reason: An error occurred during the initialization of the
filestore and cannot be reported to the parent
process. The child (background) process will
send the error to stderr before it fails.
FS0015 Cannot initialize presentation layer

Reason: The presentation initialization function
(init_presentation) failed.
FS0016 Authentication file not found at: xxx

Reason: The directory path and filename (xxx) for the
AUTHPATH parameter in the FT-820 filestore
configuration file is incorrect or does not exist.
Action: Check that the path and filename of the
authentication file corresponds to the value in the
AUTHPATH parameter.
FS0017 Bad HEX value in authentication file

Reason: An invalid hexadecimal value was found in the
authentication file. Hexadecimal values consist
of at least one pair of ASCII characters, each
character in the following range: 0-9, A-F, or a-f.
incorrect.
FS0018 Network address length bad in

authentication file
Reason: More than 40 hexadecimal digits occur in a
network address in the authentication file.
incorrect.
Decrease the number of hexadecimal digits in
the address.

FS0019 Error while reading authentication file

Reason: An unknown error occurred while the FT-820
authentication file was being read.
FS0020 Must use global concurrency with

MULTIPLE_PROCESSES option
Reason: Both the MULTIPLE_PROCESSES and
LOCAL_CONC_CTRL parameters in the
configuration file are set to TRUE.
Action: Set either the MULTIPLE_PROCESSES or
LOCAL_CONC_CTRL parameter to FALSE.
FS0022 Bad effector value

Reason: The value of the EFFECTOR parameter in the
filestore configuration file is over 256.
Action: Change the value of the EFFECTOR parameter to
be less than or equal to 256.
FS0023 No accessible transport devices

Reason: All attempts made to attach to each of the
transport provider names in the ffs.cfg
configuration file have failed.
Action: Check that the /etc/osid.cfg file contains at
least one of the provider names supplied in the
TRANSPORT_NAMES parameter of the filestore
configuration file and that the associated driver is
up and running.
Check that the lower layers are running correctly.
Check that the transport provider capability is
correctly configured and operating if your system
uses it to reformat address and options buffers
for session.
FS0024 Must supply lower layer provider name list

in configuration file
Reason: The TRANSPORT_NAMES parameter in the
filestore configuration file does not exist.
Action: Add the TRANSPORT_NAMES parameter to the
filestore configuration file.

FS0025 USER name must not be included in

NO_ACCESS_LIST
Reason: The value set for the USER parameter in the
ffs.cfg configuration file also exists in the
NO_ACCESS_LIST parameter. This is an
ambiguous configuration.
Action: Remove the default USER name from the
NO_ACCESS_LIST parameter.
FS0026 Bad Quality of Service Value in

configuration file
Reason: The value set for the QUALITY_OF_SERVICE
parameter in the ffs.cfg configuration file is
invalid.
Action: Specify a quality of service value of 0, 1, 2, or 3.
FS0027 Bad Checkpoint Window Value in

configuration file
Reason: The value set for the CHECK_WINDOW parameter
in the ffs.cfg configuration file is invalid.
Action: Specify a quality of service value of at least 1.
FS0028 Bad Maximum Retries Value in configuration

file
Reason: The value set for the MAX_RETRIES parameter
Action: Specify at least 1 retry.
FS0029 Bad Maximum Time Limit Value in

configuration file
Reason: The value set for the MAX_TIME_LIMIT
parameter in the ffs.cfg configuration file is
invalid.
Action: Specify at least 1 second.
FS0030 Bad Retry Delay Value in configuration file

Reason: The value set for the RETRY_DELAY parameter
FS1001 Transport device driver name not found in

osid.cfg
Reason: The osid.cfg transport software configuration
file does not contain device driver names in the
TRANSPORT_NAMES parameter.

FS1002 Out of memory

Reason: There was insufficient memory or swap space
available for the FT-820 filestore to operate.
FS1003 Cannot allocate memory for local TSAP

Reason: The transport allocation call (t_alloc) failed
because an insufficient number of stream buffers
were available when the transport software was
configured.
Action: See your transport product’s documentation for
information about configuration.
FS1004 Cannot bind local TSAP

May be in use by other processes
Reason: The FT-820 filestore could not bind to the local
TSAP. In most cases, the FT-820 cannot bind
because the TSAP is already bound to another
process.
Action: Use the processor status command (ps) to
check whether a filestore process is already
running.
FS1005 Cannot open transport device driver,

possibly no lower layer running
Reason: The FT-820 filestore cannot open the transport
software device drivers.
Action: Check the device driver names in the osid.cfg
transport software configuration file.
Check that at least one of the device drivers
listed in osid.cfg exists.
See your transport product’s documentation.
FS1006 Transport device driver does not exist

Reason: The FT-820 filestore cannot find the transport

FS1007 Do not have read/write permission to

transport device driver
Reason: The FT-820 filestore cannot access the transport
software device drivers because the device
drivers are read/write protected.
Action: Check that the osid.cfg transport software
configuration file includes user read/write
permissions for the transport software device
driver.
FS1008 Fatal internal error detected

Reason: The FT-820 filestore cannot access the transport
Action: Check that the TP providers are in the ffs.cfg
configuration file.
Check that the makefile.apli file was not
used when the makefile was run.
Check that the osid.cfg configuration file
includes user read/write permissions for the
transport software device driver.
FS1009 Possible connectionless transport device

specified in osid.cfg
Reason: The transport device specified in osid.cfg is
connectionless.
Action: Alter the specification of the transport file in
osid.cfg to connection-oriented.
FS1010 Cannot activate local TSAP

May be in use by other processes
Reason: The TSAP specified is already in use by another
process.
Action: Use the processor status command (ps) to
check whether a filestore process is already
running.

FTAM/ERPM filestore error messages
Errors with the prefix FT originate in FTAM/ERPM filestores. The
general types of filestore errors are explained in Table A.4.
In Table A.5, errors preceded by an asterisk (*) can be generated by

other vendors’ FTAM/ERPM filestores, and are not generated by the
FT-820 filestore. They are not described since the context in which an
error occurs in these implementations is unknown. To get
information about these errors, refer to the documentation for the
filestore you are trying to access, if available, or see your system
administrator.
Errors generated by other vendors’ filestore implementations might

return the same error codes as the FT-820–specific error codes (those
without asterisks) listed in Table A.5. However, the descriptions and
solutions for the FT-820 errors are not necessarily related to error
codes generated by other types of filestores.
Table A.4 Types of FTAM filestore error messages
Range Description
FT0000 – FT0999 Returned from an FTAM filestore when a general error,

such as management problems or access violations, has
been detected by the filestore.
FT1000 – FT1999 Returned from an FTAM filestore when a protocol or

supporting service error has been detected by the
filestore. An example of an error in this range is an FTAM
protocol sequence error or parameter error. A protocol
error is usually a sign of a software error.
FT2000 – FT2999 Returned from an FTAM filestore when an association

error has been detected by the filestore. An example of an
error in this range is an unknown initiator or account.
FT3000 – FT3999 Returned from an FTAM filestore during file selection or

creation.
FT4000 – FT4999 Returned from an FTAM filestore when a management

error has been detected by the filestore. An example of an
error in this range is a bad attribute value.
FT5000 – FT5999 Returned from an FTAM filestore when a file access error
has been detected by the filestore. An example of an error
in this range is when a bad location is requested or when
disk file space has been exhausted.

Table A.4 Types of FTAM filestore error messages (continued)
Range Description
FT6000 – FT6999 Returned from ERPM when a recovery-related error has

been detected by the filestore. An example of an error in
this range is when no docket is found for the file transfer
recovery.
Table A.5 FTAM filestore error messages
FT0001 Responder error (unspecific)

Reason: The FT-820 filestore may have received an
operating system error. The actual AIX operating
system’s error message also displays to provide
further details about the error.
The ERPM routines encountered an error that
prevents a successful recovery of the
connection.
FT0002 System shutdown

Reason: The FT-820 filestore was shut down for one of
the following reasons:
• Database problem (out of disk space or
corrupted disk)
• Filestore administrator terminated the
filestore process
• Out of memory
* FT0003 FTAM management problem (unspecific)
* FT0004 FTAM management – bad account
FT0005 FTAM management – security not passed

Reason: A user whose address does not appear in the
authentication configuration file attempted to
access the FT-820 filestore.
* FT0006 Delay may be encountered
FT0007 Initiator error (unspecific)

Reason: The FTAM filestore protocol machine received a
user abort indication without diagnostics.

Table A.5 FTAM filestore error messages (continued)
FT0008 Subsequent error

Reason: A group request failed. This message is provided
for information only.
FT0009 Temporal insufficiency of resources

Reason: Generated by the FT-820 utilities when they
cannot allocate enough memory to perform the
operation you requested.
This error may also be generated by the filestore
you are trying to access. For more information,
refer to the documentation for the filestore, if
available, or see your system administrator.
FT0010 Access request violates VFS security

Reason: You do not have permission to read or write the
file specified.
Action: Check the directory path of the file you specified.
Correct it if it is wrong. Change or have changed
the permissions of the directory and/or file.
* FT0011 Access request violates local security
* FT1000 Conflicting parameter values
* FT1001 Unsupported parameter values

Note. If you are running the FT-820 over an APLI stack,
make sure that the PSAP parameter in the ffs.cfg file is
NULL.
* FT1002 Mandatory parameter not set
* FT1003 Unsupported parameter
* FT1004 Duplicated parameter
* FT1005 Illegal parameter type
* FT1006 Unsupported parameter types
FT1007 FTAM protocol error (unspecific)

Reason: The FTAM filestore protocol machine does not
understand the version number of the protocol
data units.

FT1008 FTAM protocol error, procedure error

Reason: A request was made out of the sequence
required by the protocol.
FT1009 FTAM protocol error, functional unit error

Reason: A request was made, but the functional unit that
supports this request was not negotiated.
FT1010 FTAM protocol error, parsing error

Reason: FTAM cannot parse a protocol data unit.
FT1011 Lower layer failure

Reason: The transport software was not able to
communicate with the filestore.
Action: Ask your system administrator or check that the
filestore is running on the remote system you
tried to access. If it is not running, start it, if
possible.
* FT1012 Lower layer addressing error
* FT1013 Timeout
* FT1014 System shutdown
FT1015 Illegal grouping sequence

Reason: An illegal grouping sequence was sent to the
FTAM filestore protocol machine.
FT1016 Grouping threshold violation

Reason: The begin_group threshold was inconsistent
with the group.
FT1017 PDU request inconsistent with requested

access
Reason: An invalid protocol data unit (PDU) was received.
FT2000 Association with user not allowed

Reason: The specified application entity title was not
recognized by the filestore you tried to access.
FT2002 Unsupported service class

Reason: The service class requested is not supported by
the accessed filestore.

* FT2003 Unsupported functional unit
FT2004 Attribute group error (unspecific)

Reason: A request was made for an attribute group, but
that attribute group has not been negotiated.
* FT2005 Attribute group not supported
* FT2006 Attribute group not allowed
* FT2007 Bad account
* FT2008 Association management (unspecific)
* FT2009 Association management – bad address
* FT2010 Association management – bad account
* FT2011 Checkpoint window error – too large
* FT2012 Checkpoint window error – too small
* FT2013 Checkpoint window error – unsupported
FT2014 Communications Quality of Service not

supported
Reason: A user requested a quality of service (QOS)
other than no_recovery.
FT2015 Initiator identity unacceptable

Reason: The initiator ID or password specified cannot be
validated on the filestore you tried to access.
* FT2016 Context management refused
* FT2017 Rollback not available
FT2018 Contents type list cut by responder

Reason: A document type name was removed from the
contents type list. This error message is provided
for information only.
* FT2019 Contents type list cut by Presentation

service
FT2020 Invalid filestore password

Reason: The specified initiator ID or password cannot be
validated on the filestore you tried to access.

* FT2021 Incompatible service classes
FT3000 Filename not found

Reason: The file specified was not found in the filestore
you accessed.
Action: Check the directory path of the file you specified.
* FT3001 Selection attributes not matched
FT3002 Initial attributes not possible

Reason: The FT-820 filestore does not know the
requested contents type.
This error may also be returned by the FT-820
filestore when you attempt to create a file with a
file availability parameter value that is not
“immediate.”
* FT3003 Bad attribute name
FT3004 Non-existent file

Reason: The file you specified does not exist on the
filestore you accessed.
Action: Ensure that the directory path and filename are
correct.
FT3005 File already exists

Reason: The file you specified already exists on the
filestore you accessed.
* FT3006 File cannot be created
* FT3007 File cannot be deleted
FT3008 Concurrency control not available

Reason: Attempted to create, select, or open a locked file
that other users are currently accessing.
This error may also be returned by the FT-820
filestore when you attempt to create, select, or
open a file with a concurrency control value that
is not allowed by the file access control attribute.
* FT3009 Concurrency control not supported

FT3010 Concurrency control not possible

Reason: Concurrency control is inconsistent with the
requested access on the file.
* FT3011 More restrictive lock
* FT3012 File busy
FT3013 File not available

Reason: The filestore you accessed does not support the
document file type of the existing file you
specified.
Action: If the file you specified was created with a
different version of the filestore, reinitialize the
attributes database with the finit utility and try
again.
FT3014 Access control not available

Reason: Attempted to create or select a file with a
requested access value that is not allowed by
the file access control attribute.
FT3015 Access control not supported

Reason: Attempted to change a file’s access control
attribute to an unsupported value.
This error message is provided for information
only. The access control element with this
identity is ignored.
FT3016 Access control inconsistent

Reason: The access password associated with a
particular action cannot be validated on the
filestore you tried to access.
Action: Specify the correct access mode on the
command line.
* FT3017 Filename truncated
FT3018 Initial attributes altered

Reason: The permitted actions have been modified in
order to conform with the selected document
type constraint set.
only.

* FT3019 Bad account
FT3020 Create override selected existing file

Reason: The create override was performed as
requested.
only.
FT3021 Create override deleted and recreated file

with old attributes
requested.
only.
FT3022 Create override deleted and recreated file

with new attributes
requested.
only.
FT3023 Create override – not possible

Reason: The create override is not possible because the
access control is not available for the delete
action (that is, DEL&CREATE-OLD-ATTR or
DEL&CREATE-NEW-ATTR was asked for when
you do not have permission to delete the file).
This error may also be returned if you cannot get
the concurrency control to delete the existing file.
* FT3024 Ambiguous file specification
* FT3025 Invalid create password
FT3026 Invalid delete password on override

Reason: The create override is not possible because the
delete access password cannot be validated on
the filestore you tried to access.
Action: Specify the correct access mode on the
command line.
* FT3027 Bad attribute value
* FT3028 Requested access violates permitted actions

* FT3029 Functional unit not available for requested

access
FT3030 File created but not selected

Reason: A create request failed to select the file for either
or both concurrency control and requested
access problems.
* FT4000 Attribute non-existent
* FT4001 Attribute cannot be read
* FT4002 Attribute cannot be changed
* FT4003 Attribute not supported
* FT4004 Bad attribute name
* FT4005 Bad attribute value
FT4006 Attribute partially supported

Reason: A change attribute is requested on an attribute
that is only partially supported by the filestore
you accessed.
only.
* FT4007 Additional set attribute value not distinct
* FT5000 Bad FADU (unspecific)
FT5001 Bad FADU – size error

Reason: The document file type you specified does not
use file access data unit (FADU) parameters. For
example, only the locations (first-last, relative,
begin-end) or the FADU number can be used in
FTAM-2 files.
This error is generated by the FT-820 utilities
when they receive an FTAM FADU that contains
more than 128 data units or more than 16 node
name entries.

FT5002 Bad FADU – type error

use the file access data unit (FADU) parameters.
For example, only the locations (first-last,
relative, begin-end) or the FADU number can be
used in FTAM-2 files.
FT5003 Bad FADU – poorly specified

use the file access data unit (FADU) parameters.
For example, only the locations (first-last,
relative, begin-end) or the FADU number can be
used in FTAM-2 files.
FT5004 Bad FADU – bad location

Reason: The specified file access data unit (FADU)
location is illegal in the current context.
* FT5005 FADU does not exist
* FT5006 FADU not available (unspecific)
* FT5007 FADU not available for reading
* FT5008 FADU not available for writing
* FT5009 FADU not available for location
* FT5010 FADU not available for erasure
* FT5011 FADU cannot be inserted
* FT5012 FADU cannot be replaced
* FT5013 FADU cannot be located
* FT5014 Bad data element type
FT5015 Operation not available

Reason: Indicates that an operation was requested and
is either not allowed on the document type or
the action has not been negotiated in the
requested_access or processing_mode
of the select or open request or confirm.
FT5016 Operation not supported

Reason: Attempted to perform an operation that is not
supported by the selected file type.

FT5017 Operation inconsistent

Reason: Indicates that one of the write operations is not
valid for the selected document type.
FT5018 Concurrency control not available

Reason: Attempted to create, select, or open a locked file
that other users are currently accessing.
This error message is also returned when you
attempt to create, select, or open a file with the
concurrency control value that is not allowed by
the file access control attribute.
* FT5019 Concurrency control not supported
FT5020 Concurrency control inconsistent

Reason: An open primitive was received that contains a
concurrency control value that is less restrictive
than the concurrency control value provided on
the select primitive.
FT5021 Processing mode not available

Reason: Indicates that a read or write file operation was
requested and a read or write processing mode
was not requested or granted in the open
request/confirm.
* FT5022 Processing mode not supported
FT5023 Processing mode inconsistent

Reason: Attempted to open a file using a processing
mode that is unacceptable due to the document
file type for the file or the file access control
attribute.
* FT5024 Access context not available
FT5025 Access context not supported

Reason: Attempted to read a file using an access context
that is unacceptable due to the document file
type for the file.
* FT5026 Bad write (unspecific)
* FT5027 Bad read (unspecific)

FT5028 Local failure (unspecific)

Reason: Indicates that the request to change the access
control elements of the attributes failed.
FT5029 Local failure – file space exhausted

Reason: The file system of the AIX operating system on
which the file you want to access is located is
full.
* FT5030 Local failure – data corrupted
* FT5031 Local failure – device failure
* FT5032 Future file size exceeded
* FT5034 Future file size increased
* FT5035 Functional unit invalid in processing mode
FT5036 Contents type inconsistent

Reason: A request was issued to create or open a file with
a contents type value that uses the abstract
syntax and constraint set pair format.
This error message is also returned when you
attempt to open a file with an invalid
simplification or relaxation value (for example,
when you try to simplify an FTAM-3 to an
FTAM-1 document).
* FT5037 Contents type simplified
* FT5038 Duplicate FADU name
* FT5039 Damage to select/open regime
* FT5040 FADU locking not available on file
* FT5041 FADU locked by another user
FT6000 Bad checkpoint (unspecific)

Reason: The checkpoint identifier does not correlate to
the sequence of checkpoints recorded for bulk
data transfer.
* FT6001 Activity not unique

FT6002 Checkpoint outside window

Reason: The number of unacknowledged checkpoints
has exceeded the window size (CHECKWINDOW)
specified in your filestore configuration file.
* FT6003 Activity no longer exists
FT6004 Activity not recognized

Reason: An unexpected error recovery activity has been
encountered.
FT6005 No docket
Reason: Error recovery cannot be performed because the
docket maintained for the file transfer is not
present in the docket file.
FT6006 Corrupt docket

Reason: Error recovery cannot be performed because the
integrity of the docket maintained for the file
transfer is not known.
* FT6007 File waiting restart
FT6008 Bad recovery point

Reason: The filestore is unable to correctly position itself
in the file during recovery.
* FT6009 Non-existent recovery point
FT6010 Recovery mode not available

Reason: Error recovery will not be performed because the
Restart and Recovery functional units have not
been negotiated, or the no-recovery quality of
service has been specified.
* FT6011 Recovery mode inconsistent
* FT6012 Recovery mode reduced
FT6013 Access control not available

Reason: The filestore cannot select the file with the
requested access value.
* FT6014 Access control not supported
* FT6015 Access control inconsistent

FT6016 Contents type inconsistent

Reason: The filestore doesn’t recognize the document
type of the file to be recovered.
* FT6017 Contents type simplified
Operating system error messages

Errors with the OS prefix are generated by the FT-820 utilities. They
indicate that an error occurred in the local AIX operating system.
These messages indicate that the operating system on which a

remote filestore is located generated an operating system error
message, which was relayed to the local system through FT-820.
These error messages are not listed because the actual error message
differs from system to system.
Utility error messages

Errors with the UT prefix are generated by the FT-820 utilities. They
indicate that a limitation or a user input error occurred (for example,
insufficient memory or incorrect command line syntax).
Table A.6 Utility error messages
UT0001 Memory allocation error

Reason: The utility was unable to allocate enough
memory for the operation.
UT0002 Option error

Reason: You used an invalid command line option with a
utility.

Table A.6 Utility error messages (continued)
UT0004 Document type not supported

Reason: The operation you requested cannot be
performed on the file you specified.
UT0005 Device full

Reason: The device to which you want to copy or move
the file is currently full. You cannot copy or move
the file until space is created.
UT0006 Session activation error

Reason: The utility was unable to activate the session
layer.
UT0007 Process Interrupted

Reason: The utility you used was interrupted by an AIX
operating system signal.
UT0008 Presentation Initialization error

Reason: The utility you used was unable to initialize the
presentation layer.
UT0009 Effector value in Configuration file is

invalid
Reason: The value of the EFFECTOR parameter in the
utility configuration file is over 256.
UT0010 The current override mode was set to

prevent the deletion of the destination
file
UT0011 Invalid quality of service

Reason: The requested quality of service is not in the
range of 0 to 3.
UT0012 Invalid checkpoint window size in

configuration file
Reason: The checkpoint window size must be greater
than 0.
UT0013 Invalid maximum retry value in

configuration file
Reason: The maximum retry value must be greater than
0.

UT0014 Invalid maximum time limit value in

configuration file
Reason: The maximum time limit value must be greater
than 0.
UT0015 Invalid retry delay value in configuration

file
Reason: The retry delay value must be greater than or
equal to 0.
UT0016 Max length string out of range

Reason: The maximum length parameter in the .ftInit
configuration file is out of range. As a result, the
parameter is set to its maximum value.
UT0017 Audit file pathname exceeds maximum string

length
Reason: The audit file pathname exceeds 60 characters.
UT1001 Memory allocation error

Reason: The utility you used was unable to allocate
enough memory to complete the operation you
requested.
UT1002 Illegal command sequence

Reason: An error in the software occurred.
UT1004 Minimum service level not supported by

filestore
Reason: This filestore does not support the minimum
facilities needed to successfully copy, list, move,
or remove this file.
UT1005 Cannot access audit trail file

Reason: The audit filename (AUDITPATH) specified in a
user’s utility configuration file (.ftInit) does
not have the appropriate permissions for write
access.
Action: Change the audit file to a location where the user
has both read and write permission to the file.
UT2001 Memory allocate error

Reason: There was insufficient memory or swap space for
the requested operation.

UT2018 Unable to open AE table file

Reason: The utility was unable to find or access the
__AETABLE__ file on your system.
Action: Find out if or where the __AETABLE__ file is
located on your system (this file may have
another name if your system administrator
changed the name when installing the file on
your system). Ensure that your environment
variable AETABLE is set to the name of this file.
Ensure that you specified the correct path to this
file’s directory.
If you continue to receive this error message,
make sure that you have permission to access
the file.
UT2019 Invalid syntax in AE table file

Reason: The utility you used was unable to scan the
application entity file completely because a
syntax error was encountered.
Action: Open the application entity table file and correct
the syntax error (this file is normally called
__AETABLE__ but may have been changed
when the file was installed on your system).
UT2022 AE name does not exist in AE table

Reason: The utility was unable to find the application
entity name you specified on the command line
in the application entity table file.
Action: Did you mistype the name of the application
entity you want on the command line?
If not, ask the system administrator to check the
application entity table file. If an entry for the
application entity you specified does not exist,
add an entry for the application entity you
specified on the command line.
UT3001 Transport device driver name not found in

osid.cfg
Reason: Indicates that the osid.cfg transport software
configuration file does not contain device driver
names for the TP4 device or TP024 device
parameters.
Action: Refer to the transport software’s manual for
information about the parameters and drivers.

UT3002 Out of memory

Reason: There was insufficient memory or swap space
available for the FT-820 utility to operate.
UT3003 Cannot allocate memory for local TSAP

Reason: The transportation allocation call (t_alloc)
failed because an insufficient number of stream
buffers were available when the transport
software was configured. See your transport
product’s documentation for information about
configuration.
UT3004 Cannot bind local TSAP

May be in use by another process
Reason: The FT-820 utility could not bind to the local
TSAP. In most cases, this is because the TSAP
is already bound to another process.
Action: Use the processor status command (ps) and
check to see if a utility process is already
running.
UT3005 Cannot open transport device driver,

possibly no lower layer running
Reason: The FT-820 utility cannot open the transport
UT3006 Transport device driver does not exist

Reason: The FT-820 utility cannot find the transport
software device drivers described in your
transport product’s documentation.

UT3007 Do not have read/write permission to

transport device driver
Reason: The FT-820 utility cannot access the transport
software device drivers because the device
drivers are read/write protected.
Action: Check that the osid.cfg transport software
configuration file includes user read/write
permissions for the transport software device
driver.
UT3009 Possible connectionless transport device

specified in osid.cfg
Reason: The transport device specified in osid.cfg is
connectionless. FT-820 utilities only operate with
the connection-oriented transport service.
Action: Alter the specification of the transport file in
osid.cfg to connection-oriented.
UT3010 Cannot activate local TSAP

May be in use by another process
Reason: The TSAP specified is already in use by another
process.
Action: Check that the TSAP that has been selected
from the __AETABLE__ file is not in use by
another process.
The default value selected from the
__AETABLE__ file is the ANON entry.
If the FTAMLOCAL environment variable is set,
then the TSAP will be derived from this value.
UT3012 Session Service Access Point in use

Reason: The SSAP specified is already in use by another
process.
Action: Check that the SSAP that has been selected
from the __AETABLE__ file is not in use by
another process.
The default value selected from the
__AETABLE__ file is the ANON entry.
If the FTAMLOCAL environment variable is set,
then the SSAP will be derived from this value.

B References
T his appendix lists the standards documents on which the FT-820

and FT-825 products are based, and the other OSSC documents that
describe these and related products.
Related ISO documentation

1. ISO 8571, Information Processing Systems — Open Systems
Interconnection — File Transfer, Access, and Management, Parts 1
through 4.
Related OSSC documentation

2. FTAM Portation Guide, part number 1080118-04.
3. FTAM Programmer Guide, part number 1080118-32.
4. FTAM User Guide, part number 1080118-31.
5. OSSC OSI Application Developer’s Guide, part number 1080149-

02.
6. LT-610 Administrator Guide, part number 1080114-31.
7. WT-325 Administrator Guide, part number 1080127-01.
8. AP-240 Portation Guide, part number 1080215-01.
115
Related AT&T documentation
9. AT&T Network Programmer’s Guide
10. AT&T System V Interface Definition, Volume 3
11. AIX STREAMS Primer
12. AT&T ACSE/Presentation Library Interface, July 23, 1990
116 Appendix B • References

Glossary
T his glossary defines key terms and acronyms that appear in this
manual.
Acronym Definition
ACE access control element
ACSE association control service element
AE application entity
AP application process
AT&T American Telegraph and Telephone
CCITT Consultative Committee for International Telegraph and

Telephone
CLNS connectionless network service
CONS connection-oriented network service
ERPM error recovery protocol machine
FADU file access data unit
FTAM file transfer, access, and management
ISO International Organization for Standardization
LAN local area network
NIST National Institute of Standards and Technology
117
Acronym Definition
NSAP network service access point
OSI open systems interconnection
PDU protocol data unit
PID process identifier
PSAP presentation service access point
QOS quality of service
SAP service access point
SSAP session service access point
TPC transport provider capability
TLI transport layer interface
TSAP transport service access point
WAN wide area network
118 Glossary
ACSE
Association control service element. This protocol establishes and
maintains a virtual connection with a remote system, either the
initiator or responder.
AI
Application interface. A library of functions, in object code format,
that are called from the application program.
CCITT
International Telegraph and Telephone Consultative Committee. An
international association that develops communications standards
for services typically provided by public data networks. The X.400
series is an example of such a standard.
CLNS
Connectionless network service. A type of data transfer in which the
sender transmits data without first establishing a logical connection
with the receiver.
CONS
Connection-oriented network service. A mode of communication
between two networks in which a logical connection between the
two is established before data is transferred. This type of network
service is provided by the X.25 protocol when used in conjunction
with TP0 or TP2.
FADU
File access data unit. A unit of the file access structure on which the
actions of transfer, delete, extend, replace, or insert can be
performed. A data unit is the smallest unit of a file’s contents which
the filestore actions can manipulate.
FTAM
File transfer, access, and management. Software that allows a user to
manipulate files on remote computer systems by creating a virtual
filestore that describes the actual files stored in the operating
system’s file system.
GOSIP
Government Open Systems Interconnection Profile. Software and
systems that comply with Open Systems Interconnection standards.
initiator
A file service user who begins an FTAM session.
Glossary 119
ISO
International Organization for Standardization. An organization that
issues international standards for a wide variety of fields, including
communication protocols.
LAN
Local area network. A network that connects computers in a limited
geographic area such as an office, factory floor, building, or campus.
LANs are generally owned entirely by one organization.
MAC address
Medium access control address. An address that points to a device-
dependent entity within the data-link layer.
NSAP
Network service access point. The service access point address that
uniquely identifies a system on a network.
OSI
Open systems interconnection. A hierarchical standard of network
architecture that subdivides communication functions into seven
logically separate layers. The standards are developed by ISO.
presentation
The layer of the OSI protocol that provides for the representation of
information that is communicated to or referred to by an application
process.
protocol
A set of rules and conventions that governs how two entities
exchange data.
responder
The file service user which accepts an FTAM session request from an
initiator.
session
The layer of the OSI protocol that provides a means by which the
dialogue between the application processes is organized and
synchronized. It manages data between application processes.
STREAMS
A combination of system calls, kernel routines, and kernel utilities
offered in the UNIX System V Release 3.2 operating system that
provides a dynamic communications stack. STREAMS defines a
standard interface between a STREAMS-based user applications and
the STREAMS protocol stack with which it communicates.
120 Glossary
transport class
A category of protocols for the OSI transport layer. The transport
class defines which transport layer protocols are appropriate for the
level of network service used.
transport layer
An OSI layer that accepts data from the session layer, splits it into
smaller units, if need be, and passes them to the network layer. It
ensures that the pieces arrive correctly at the other end.
TLI
Transport library interface. An AT&T function call library associated
with STREAMS that provides a standard interface between user
applications and network transport services.
TPC
Transport provider capability. The TPC language is used to prepare
a set of functions to format and parse OSI addresses according to the
transport provider’s specifications.
transport stack
The software and hardware that provide data transport services for
the physical medium.
TSAP
Transport service access point. The transport access point address
that uniquely identifies a transport service user on a network.
WAN
Wide area network. A network that connects computers over a wide
geographic area. WAN service is often provided by public and
private telephone companies.
Glossary 121
122 Glossary
Index
Symbols
__AETABLE__ file
diagram of 13
how to set up 16
use of 12
A
access control
file attribute 72
parameters 34
ACCESS_CONTROL parameter 34
ACCOUNT parameter 30
ACESS_MODE parameter 29
action list file attribute 72
address
network
in authentication file 78
AE title
in filestore configuration file 45
AETABLE environment variable 16
ANON 12, 14
application entity
definition 12
example of 12
application entity. See also AETABLE
attributes
database 10, 67
display 69
table of 70
123
ATTRPATH parameter 47 DEL_READ parameter 31
audit trail DELETE_FAILED_FILE parameter 48
file display attributes 69
filestore 11, 50 procedure 70
utility 11, 53 document file types 6, 31
level parameter 47 parameter 48
path parameter 47
AUDITLEVEL parameter 38, 47
AUDITPATH parameter 38, 47 E
authentication file 11, 77 EFFECTOR parameter 36, 48
path parameter 47 environment variable
AUTHPATH parameter 47 AETABLE 16
ERPM
description 1
C error messages
CHECK_WINDOW parameter 38, 49 database 84
comment symbol filestore 87
description of 78 FTAM filestore 95
concurrency control operating system 108
database 10, 67 parts of
concurrency keys descriptions 83
file attribute 72 illustration 83
configuration file sample 83
filestore 10, 39 utility 108
parameters 45
setting up 50
utility 10, 17 F
setting up 39 fda command 69
syntax conventions 29 ffs command 61
CONNECTS parameter 46 file attributes
CONTENTS_TYPE parameter 31 destination 8
CONTINUE parameter 38 FILE_AVAILABILITY parameter 33
COPY_INDICATOR parameter 37 FILE_STORE_PASSWORD parameter 32
CREATE_ACCOUNT parameter 30 filestore
CREATE_MODE parameter 33 audit trail file 11
CREATE_PASSWORD parameter 31 description of 1
kill command 65
number of processes option 59
D start command 59, 60
database error messages 84 stop abruptly 64
database path parameter 47 stop gracefully 65
databases stop running in foreground 65
attributes 67 utility command 61
concurrency control 67 filestore error messages 87
reinitializing 72 FTAM 95
124 Index
finit command 68 and security 79
FTAM MULTIPLE_PROCESSES parameter 46
filestore error messages 95
purpose 1
FTAM1_MAXIMUM_STRING_LENGTH parameter N
37 NO_ACCESS_LIST parameter 46
FTAM2_MAXIMUM_STRING_LENGTH parameter NSAP parameter 45
37
FTAM3_MAXIMUM_STRING_LENGTH parameter
37 O
FTAMLOCAL environment variable 12, 14 operating system error messages 108
FUTURE_FILE_SIZE parameter 33 OTHER_CREATE_PERMISSION parameter 47
OVERRIDE parameter 32
G
GROUP_CREATE_PERMISSION parameter 47 P
password file 11, 80
permissions
I default parameter 47
IDs permitted actions
effective group and user 79 file attribute 71
initialize databases PSAP parameter 45
procedure 69
utility 68
INITIATOR_ID parameter 32 Q
QUALITY_OF_SERVICE parameter 38, 49
K
kill command 65 R
reinitializing databases 72
RETRY_DELAY parameter 38, 50
L
LEGAL_QUALIFICATION parameter 33
LIMIT parameter 46 S
local concurrencey control parameter 47 security
LOCAL_CONC_CTRL parameter 47 driver 79
lockmgr command 59 preventing unauthorized access 79
SELECT_ACCOUNT parameter 30
SSAP parameter 45
M start command 60
MAPPING parameter 37, 50 stop command 64
MAX_RETRIES parameter 38, 49 stop filestore
MAX_TIME_LIMIT parameter 38, 49 abruptly 64
MAXIMUM_STRING_LENGTH parameter 37 gracefully 65
multiple processes parameter in foreground 65
Index 125
T USER parameter 45
USER_CREATE_PERMISSION parameter 47
table of attributes 70
utility
TEXT_EXT parameter 48
audit trail file 11
TITLE parameter 45
configuration file
transport
example of 18
provider capability 2
utility error messages 108
providers parameter 49
TRANSPORT_NAMES parameter 49
TSAP parameter 45 V
vfsattdb.d01 file 67
U vfsattdb.k01 file 67
vfsccdb.d01 file 67
UNIVERSAL_CLASS parameter 37
vista.taf file 68
UNIX operating system
password file 80
user X
in filestore configuration file
parameter 81 XFER_READ parameter 30
number of, option 59
126 Index

FTAdmin

Enviado por

Dados do documento

Descrição original:

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

FTAdmin

Enviado por

Direitos autorais:

Formatos disponíveis

OSSC

FTAM Administrator Guide

With Error Recovery Option

Retix and the OPENNetworking Company are registered trademarks of Retix.

T he OSSC FT-820 product provides the ability to access and

FT-820 also implements the ISO association control service element

• A workstation running the AIX operating system with

• A supporting transport protocol provider (available from

You may find the following materials helpful when administering

• AT&T Network Programmer’s Guide

About this manual

The manual is organized as follows:

Chapter 1, “Overview,” introduces you to the FT-820 and FT-825

Chapter 2, “Support Files,” discusses the files required by FT-820

Chapter 3, “Filestore,” describes how to start and stop the filestore,

Chapter 4, “Maintaining FT-820,” describes how to use and maintain

Chapter 5, “FT-820 Security,” discusses the use of the authentication

Appendix B, “References,” lists the references that you may use to

Conventions used in this manual

The osid.cfg file must contain at least these minimum

TP4 device=/dev/cots tp_provider=OSSC-1

Commands and prompts that are displayed on the screen or stored

Enter the name of the file:

Text you must enter is shown in the following typeface:

Text you substitute with actual text you type is italicized:

Replace filename with the appropriate filename.

Text you can optionally type is enclosed in square brackets:

frm [–d] [–i] [–p] [–Pf!n[!p]] [–v] f1...

Press ESC, type start, and then press RETURN.

Conventions used in this manual vii

The FT-825 error recovery protocol machine (ERPM) product

The FT-820 product is made up of two main components that

• A set of initiator utilities that allow users to list, copy, move, or

• A filestore (also called a responder) that stores a collection of

There is also an FT-825 utility that allows you to delete dockets,

This manual describes how to set up the filestore portion of FT-820.

Communication services between the initiator and responder are

A transport provider capability (TPC) mechanism is also provided to

When a user at an FTAM initiator system uses FTAM to request

• Breaking the FTAM association.

The ERPM establishes the conventions by which such errors in a file

FT-820 and 825 components

The FT-820 responder FTAM protocol machine creates, organizes,

FT-825 provides an initiator and responder ERPM protocol machine.

• ACSE establishes and maintains a virtual connection with a

• Presentation provides for the representation of information that

• Session provides a means by which the dialogue between

Figure 1.1 FT-820 and FT-825 combined components

Required OSI services

• A OSSC transport product (for example, LAN Transport for AIX

FT-820 also needs OSI protocol services to carry information to the

In this system configuration, FT-820 uses its own ACSE,

FT-820 document file types

File type Data type Description

FTAM-1 Unstructured text A file of this type contains a number of lines of

File type Data type Description

NBS-9 Directory A file of this type contains a number of directory

Support files for the FT-820 product include the following:

• The __AETABLE__ file associates an easy-to-read, common

• The utility configuration file is an optional file that contains

• The filestore configuration file defines some access parameters

• The concurrency control database contains the current locks on

• The authentication file contains a list of network addresses for

• The AETABLE file associates an easy-to-read, common

Entries in AETABLE list the addresses, titles, and protocols for

AETABLE contains two major sections:

• The second section of AETABLE identifies the applications

Each of the major sections in AETABLE contains one entry per

Sample AETABLE file

Setting up the AETABLE file

3. Save AETABLE and exit from your operating system’s text

The AETABLE file is ready for use.