SunLink FTAM

Managing SunLink FTAM 8.0.
A Sun Microsystems, Inc. Business
2550 Garcia Avenue

Mountain View, CA 94043
U.S.A.
Part No: 802-1573-10
Revision A, October 1994
1994 Sun Microsystems, Inc.

2550 Garcia Avenue, Mountain View, California 94043-1100 U.S.A.
All rights reserved. This product and related documentation are protected by copyright and distributed under licenses
restricting its use, copying, distribution, and decompilation. No part of this product or related documentation may be
reproduced in any form by any means without prior written authorization of Sun and its licensors, if any.
Portions of this product may be derived from the UNIX and Berkeley 4.3 BSD systems, licensed from UNIX System
Laboratories, Inc., a wholly owned subsidiary of Novell, Inc., and the University of California, respectively. Third-party font
software in this product is protected by copyright and licensed from Suns font suppliers.
RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the United States Government is subject to the restrictions
set forth in DFARS 252.227-7013 (c)(1)(ii) and FAR 52.227-19.
The product described in this manual may be protected by one or more U.S. patents, foreign patents, or pending applications.
TRADEMARKS
Sun, the Sun logo, Sun Microsystems, Solaris and SunLink are trademarks or registered trademarks of Sun Microsystems, Inc.
in the U.S. and certain other countries. UNIX is a registered trademark in the United States and other countries, exclusively
licensed through X/Open Company, Ltd. OPEN LOOK is a registered trademark of Novell, Inc. PostScript and Display
PostScript are trademarks of Adobe Systems, Inc. All other product names mentioned herein are the trademarks of their
respective owners.
All SPARC trademarks, including the SCD Compliant Logo, are trademarks or registered trademarks of SPARC International,
Inc. SPARCstation, SPARCserver, SPARCengine, SPARCstorage, SPARCware, SPARCcenter, SPARCclassic, SPARCcluster,
SPARCdesign, SPARC811, SPARCprinter, UltraSPARC, microSPARC, SPARCworks, and SPARCompiler are licensed
exclusively to Sun Microsystems, Inc. Products bearing SPARC trademarks are based upon an architecture developed by Sun
Microsystems, Inc.
The OPEN LOOK and Sun Graphical User Interfaces were developed by Sun Microsystems, Inc. for its users and licensees.
Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user
interfaces for the computer industry. Sun holds a non-exclusive license from Xerox to the Xerox Graphical User Interface,
which license also covers Suns licensees who implement OPEN LOOK GUIs and otherwise comply with Suns written license
agreements.
X Window System is a product of the Massachusetts Institute of Technology.
THIS PUBLICATION IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE, OR NON-INFRINGEMENT.
THIS PUBLICATION COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE
PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW
EDITIONS OF THE PUBLICATION. SUN MICROSYSTEMS, INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN
THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS PUBLICATION AT ANY TIME.
Please
Recycle
Contents
Part 1 Setting up and Maintaining SunLink FTAM
1. Introducing SunLink FTAM . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FTAM Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SunLink FTAMArchitecture Overview . . . . . . . . . . . . . . . . . .
SunLink FTAMConcepts and Terminology . . . . . . . . . . . . . .
Virtual File Store . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Document Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
File Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Functional Units and Service Classes . . . . . . . . . . . . . . . . . .
Shadow Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Shadow File Templates . . . . . . . . . . . . . . . . . . . . . . . . .
Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10
Access Restriction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11
DR10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12
SunLink FTAMDirectories and Files . . . . . . . . . . . . . . . . . . . .
12
iii
iv
2. Planning your SunLink FTAM Configuration . . . . . . . . . . . . .
15
Example Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15
Exchanging Files between Remote Systems . . . . . . . . . . . . .
15
Sharing a Local File Server . . . . . . . . . . . . . . . . . . . . . . . . . . .
16
Interoperating with Other Implementations of FTAM . . . . . . .
17
3. Configuring SunLink FTAM . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19
Starting ftamtool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
20
Staring ftamtool Locally . . . . . . . . . . . . . . . . . . . . . . . . . . .
20
Starting ftamtool Remotely. . . . . . . . . . . . . . . . . . . . . . . . .
21
Creating a Remote Systems Database (RSDB) . . . . . . . . . . . . . .
22
Adding an Entry to the RSDB . . . . . . . . . . . . . . . . . . . . . . . .
23
Modifying an Existing Template . . . . . . . . . . . . . . . . .
23
Adding a Completely New Entry . . . . . . . . . . . . . . . .
28
Deleting an Entry from the RSDB . . . . . . . . . . . . . . . . . . . . .
30
Printing the RSDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31
Closing and Opening Systems . . . . . . . . . . . . . . . . . . . . . . . .
33
Configuring the Local Initiator . . . . . . . . . . . . . . . . . . . . . . . . . .
34
Modifying the Default Initiator Configuration . . . . . . . . . .
34
Saving the Initiator Configuration. . . . . . . . . . . . . . . . . . . . .
36
Printing the Initiator Configuration . . . . . . . . . . . . . . . . . . .
37
Configuring the Local Responder . . . . . . . . . . . . . . . . . . . . . . . .
38
Modifying the Default Responder Configuration . . . . . . . .
39
Saving the Responder Configuration . . . . . . . . . . . . . . . . . .
40
Managing SunLink FTAM 8.0.2October 1994
Printing the Responder Configuration . . . . . . . . . . . . . . . . .
41
4. Using the FTAM Responder (osiftr) . . . . . . . . . . . . . . . . . . .
43
Starting and Stopping the FTAM Responder Daemon . . . . . . .
43
Starting Responder Daemon Automatically . . . . . . . . . . . .
44
Starting the Responder Daemon Manually . . . . . . . . . . . . .
44
Stopping the Responder Daemon Manually . . . . . . . . . . . .
45
Restricting Remote Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
46
5. Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
47
Problems Opening a Connection . . . . . . . . . . . . . . . . . . . . . . . . .
48
Interoperability Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
50
SunLink FTAM initiator and non-Sun Responder. . . . . . . .
50
Non-Sun Initiator and SunLink FTAM Responder . . . . . . .
52
Problems with Licensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
52
Problems Starting the License Installation Tool . . . . . . . . . .
52
Unable to Change License Server(s) . . . . . . . . . . . . . . . . . . .
53
Mistyped License Information . . . . . . . . . . . . . . . . . . . . . . . .
53
Errors Executing the License Configuration Script . . . . . . .
53
Removing the License System . . . . . . . . . . . . . . . . . . . . . . . .
54
Recovering a Lost License . . . . . . . . . . . . . . . . . . . . . . . . . . .
55
Unlocking a Stopped License System . . . . . . . . . . . . . . . . . .
56
SunLink OSI Specific Errors . . . . . . . . . . . . . . . . . . . . . . . . .
56
Part 2 Reference
6.
SunLink FTAM Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . .
61
Remote Systems Database Parameters . . . . . . . . . . . . . . . . . . . .
61
Contents
vi
RSDB Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
61
Current System Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
62
Application Process Title . . . . . . . . . . . . . . . . . . . . . . . . . . . .
62
Application Process Qualifier . . . . . . . . . . . . . . . . . . . . . . . .
62
Presentation Selector (PSEL) . . . . . . . . . . . . . . . . . . . . . . . . .
62
Session Selector (SSEL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
63
Transport Selector (TSEL) . . . . . . . . . . . . . . . . . . . . . . . . . . . .
63
Network Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
63
Network Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
64
System Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
64
Local Initiator and Responder Parameters . . . . . . . . . . . . . . . . .
64
Supported Service Classes . . . . . . . . . . . . . . . . . . . . . . . . . . .
65
Functional Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
66
New OID for NBS-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
66
DR10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
66
Traces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
67
7. Error Messages and Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
69
Primary Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
70
Local Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
75
Diagnostic Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
76
General FTAM Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . .
77
Protocol and Supporting Service Diagnostics . . . . . . . . . . .
77
Association-Related Diagnostics . . . . . . . . . . . . . . . . . . . . . .
78
Selection Regime-Related Diagnostics . . . . . . . . . . . . . . . . .
79
File Management-Related Diagnostics . . . . . . . . . . . . . . . . .
80
Access-Related Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . .
81
Recovery-Related Diagnostics . . . . . . . . . . . . . . . . . . . . . . . .
82
8. FTAM Trace Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
85
Trace Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
86
Trace Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
88
A. SunLink FTAM Command Summary . . . . . . . . . . . . . . . . . . . .
93
B. Configuring the RSDB without ftamtool. . . . . . . . . . . . . . . .
95
rdb addadd remote system. . . . . . . . . . . . . . . . . . . . . . . . . . .
95
rdb changechange remote system . . . . . . . . . . . . . . . . . . . .
97
rdb closeclose remote system . . . . . . . . . . . . . . . . . . . . . . .
98
rdb deletedelete remote system . . . . . . . . . . . . . . . . . . . . .
98
rdb listlist remote system database . . . . . . . . . . . . . . . . . .
98
rdb openopen remote system. . . . . . . . . . . . . . . . . . . . . . . . .
98
rdb showshow remote host address . . . . . . . . . . . . . . . . . . .
98
Contents
vii
viii
Preface
Purpose and Audience
This manual describes how to configure SunLink FTAM so that it can transfer,
access, and manage files between two communicating systems, through a userinterface that resembles the UNIX command ftp(1). It is intended for system
administrators familiar with the SunOS operating system and OPEN LOOK
graphical user interfaces.
Before You Read This Book

You must install and configure the SunLink OSI Communications Platform
(Stack) in order to use SunLink FTAM. Before reading this manual, refer to:
SunLink OSI 8.0.2 Communication Platform Administrators Guide

(Part No. 801-4975)
ix
How This Book Is Organized

Part 1, Setting up and Maintaining SunLink FTAM.
Chapter 1, Introducing SunLink FTAM, provides an overview of the
SunLink FTAM software architecture and the related FTAM protocols.
Chapter 2, Planning your SunLink FTAM Configuration, makes some
suggestions for planning your configuration, and provides information about
interoperating with other vendors products.
Chapter 3, Configuring SunLink FTAM, describes how to use the OPEN
LOOK graphical user interface for SunLink FTAM (ftamtool) to set up a list
of recognized systems and to configure the initiator and responder portions of
SunLink FTAM.
Chapter 4, Using the FTAM Responder (osiftr), describes how to start the
SunLink FTAM responder (osiftam) on a remote system.
Chapter 5, Troubleshooting, provides some tips for resolving common
problems with SunLink FTAM and the licensing system.
Part 2, Reference.
Chapter 6, SunLink FTAM Parameters, is a reference section, giving
detailed information about available parameters.
Chapter 7, Error Messages and Codes, is a reference section, giving an
alphabetical list of error messages and error codes, together with some
suggested remedies.
Chapter 8, FTAM Trace Files, describes the use and format of FTAM trace
files which are used to log an FTAM session.
Appendix A, SunLink FTAM Command Summary, is an alphabetical list of
the available FTAM Initiator commands.
Appendix B, Configuring the RSDB without ftamtool, describes the
commands that add entries to the RSDB, without using ftamtool.
Conventions Used in this Manual

The following typographic conventions are used in this manual:
Typewriter font
Represents what appears on your workstation screen and is used for
program names, file names, and UNIX commands.
Boldface typewriter font
Indicates user input, commands and responses to prompts that you type in
exactly as they appear in the manual.
Italic font
Indicates variables or parameters that you replace with an appropriate word
or string; also used for emphasis.
hostname% or %
Represents the systems prompt for a non-privileged users account.
hostname# or #
Represents the systems prompt for the root (superuser) account.
Boxes
Contain text that represents listings, part of a
configuration file, or program output.
Boxes are also used to represent interactive sessions. In this case, user input is
indicated by boldface typewriter font. For example:
% df -k /usr
Filesystem
/dev/sd0g
kbytes
155015
used
103090
avail capacity
36424
74%
Mounted on
/usr
Product Documentation
The other documents in the SunLink OSI documentation set are:
Using SunLink FTAM 8.0.2

(Part Number: 801-4961)
SunLink FTAM 8.0.2 Programmers Guide

(Part Number: 801-4962)
xi
You may also need to refer to Getting Started with SunLink FTAM 8.0.2, which is
delivered with the product CD-ROM.
xii
Part 1 Setting up and Maintaining

SunLink FTAM
Introducing SunLink FTAM
FTAM Specifications
page 1
SunLink FTAMArchitecture Overview
page 2
SunLink FTAMConcepts and Terminology
page 4
SunLink FTAMDirectories and Files
page 12
SunLink FTAM is an implementation of the ISO FTAM protocols, that provides

the feature-set defined in the US GOSIP requirements. It is used to transfer,
access, and manage files between two communicating systems.
This chapter provides a summary of the relevant ISO FTAM protocols and an
overview of the SunLink FTAM concepts and architecture.
FTAM Specifications
The ISO FTAM specification (8571) defines a method of handling the transfer,
access, and management of files between two communicating systems based
on the principle of a virtual file store. The FTAM specification is divided into
five parts:
ISO 8571/1 Introduces FTAM concepts
ISO 8571/2 Explains the terms, concepts, and vocabulary used by FTAM
ISO 8571/3 Describes the two file transfer entities
ISO 8571/4 Defines the rules applied to the transfer of files
ISO 8571/5 Describes the conformance statement
1
SunLink FTAMArchitecture Overview
SunLink FTAM is an implementation of the ISO FTAM protocols. It is used to
transfer, access, and manage files between two communicating systems
through a user-interface that resembles the UNIX command ftp(1). It adheres
to a client-server model (where the client system requests and receives
services from a remote server) and consists of two partsosiftam and
osiftr:
The SunLink FTAM initiator (osiftam) is the client process. It resides on

the local system and initiates connections (called associations) with remote
systems running an FTAM server.
The SunLink FTAM responder (osiftr) is the server process. It is

launched by a daemon (osiftrd) each time an association request is
received from an FTAM client such as the SunLink FTAM initiator
(osiftam). There is one FTAM responder daemon (osiftrd) for each of
the three subnetwork types supported by SunLink OSI (LAN, WAN, and
TCP/IP).
Figure 1-1 shows how an osiftrd daemon launches an osiftr process when
it receives an association request from an FTAM client such as osiftam.
command-line
interface
FTAM Initiator
(osiftam)
FTAM Responder
(osiftr)
daemon
(osiftrd)
User Space
Kernel
OSI STREAMS
multiplexor
Figure 1-1
Establishing an Association
1
The SunLink FTAM initiator (osiftam) is accessed through a simple
command-line interface. In addition to file transfer facilities, SunLink FTAM
supports extensive file access and management functions. Refer to
Appendix A, SunLink FTAM Command Summary, for a comprehensive list
of the osiftam commands.
Each instance of the osiftam initiator manages one association at a time;
however, the osiftrd daemon launches an osiftr responder process each
time it receives an association request. In this way, the SunLink FTAM handles
multiple concurrent associations as shown in Figure 1-2.
Each instance of the osiftr responder remains active until the association is
closed explicitly, using the close command, or it times out.
command-line
interface
command-line
interface
FTAM Responder
(osiftr)
FTAM Responder
(osiftr)
FTAM Initiator
(osiftam)
FTAM Initiator
(osiftam)
daemon
(osiftrd)
User Space
Kernel
OSI STREAMS
multiplexor
Figure 1-2
Establishing Concurrent Associations
1
SunLink FTAMConcepts and Terminology
The FTAM protocols describe a method of managing files between potentially
diverse file systems based on the principle of a virtual file store, which maps
different file systems to a common model. SunLink FTAM implements a virtual
file store and the associated services used to access files remotely or to transfer
files between systems.
Virtual File Store

The virtual file store defined by the FTAM protocols provides a mapping of the
data and characteristics of a real file to a common modelthe virtual file. By
describing only the virtual file store and not the files themselves, the FTAM
protocols define a method of managing files between dissimilar environments.
The concept of the FTAM virtual file store is illustrated in Figure 1-3.
Real File System A
Real File System B
SunLink FTAM Environment

FTAM Virtual File Store
Real File System D
Real File System C
Figure 1-3
1
Document Types
The FTAM protocols define a small number of specific document types that
describe a file based on a set of common attributes. This enables
communicating systems to access files in a consistent manner. Three of the
national standards committeesISO (International Standards Organization),
NIST (US National Institute of Standards and Technology), and INTAP
(Interoperability Technology Association for Information Processing,
Japan)have cooperated to define the ten standard document types.
Implementations of the FTAM protocols such as SunLink FTAM, support a
subset of the ten defined document types. The document types supported by
Sunlink FTAM are listed in Table 1-1:
Table 1-1
Supported Document Types
Document Type
Description
FTAM-1
Unstructured text
FTAM-2
Sequential text
FTAM-3
Unstructured binary
NBS-9
File directory
INTAP-1
INTAP records
If a document type is not defined explicitly, files are assumed to be of

document type FTAM-3 (unstructured binary).
File Attributes
File attributes describe the properties and characteristics of a file. The FTAM
protocols define four groups of file attributes, of which SunLink FTAM
supports the kernel group and the storage group:
The kernel group consists of properties that are common to all files.
For example, name, document type, access restrictions.
The storage group consists of properties of files that are stored.

For example, date and time last read, identification of creator.
1
Functional Units and Service Classes
The FTAM architecture is described in terms of functional units and service
classes.
Functional units describe the services implemented by the FTAM protocols.
The FTAM specification (ISO 8571/3) defines ten functional units; however,
because common functional units are negotiated by the two communicating
systems at the time an association is requested, implementations of the FTAM
protocols do not need to support all of the functional units defined by the
FTAM specification.
The functional units supported by SunLink FTAM are listed in Table 1-2:
Table 1-2
Supported Functional Units
Code
Functional Unit
U1
Kernel
U2
Read
U3
Write
U4
File Access (requires U2 or U3)
U5
Limited File Management
U6
Enhanced File Management (requires U5)
U7
Grouping
U9
Recovery
Service classes are groups of functional units and are defined by the type of
functional units they contain. The FTAM specification (ISO 8571/3) defines five
service classes, of which SunLink FTAM supports the four classes listed in
Table 1-3:
Table 1-3
Supported Service Classes
Code
Service Class
Transfer class
Access class
Management class
TM
Transfer and Management class
1
Shadow Files
Shadow files are special files that are specific to the SunLink FTAM
implementation of the FTAM protocols. They are used to handle the FTAM file
attributes that are not supported by the UNIX file system. Under most
circumstances, shadow files are transparent to the user.
The attributes maintained in the shadow file are:
access permissions:
Specifies the access permissions assigned to the associated file. These
permissions can be overridden by setting the file permissions explicitly.
r: read permission
i: insert permission
p: replace permission
x: extend permission
e: erase attributes permission
t: read attributes permission
c: change attributes permission
d: delete permission
document type:
Specifies the FTAM document type for the associated file:
F1: FTAM-1 unstructured text file
F2: FTAM-2 sequential text file
F3: FTAM-3 unstructured binary file
I1: INTAP-1 record file
universal class no:

Universal Class Number. This is an integer value that specifies the content type
(text, binary, etc.):
4: octet string
19: printable string
1
20: teletex string
21: videotex string
22: IA5 string
25: graphic string
26:visible string
27: general string
string length:
Integer value specifying the maximum string length. A value of zero specifies
an unbounded string length.
string significance:
Specifies whether the string is of fixed length, variable length, or whether
length is insignificant.
f: fixed
v:variable
n: not significant
A shadow file is created for each file that is managed using the Sunlink FTAM
initiator and responder. A shadow file is created on a remote system when a file
is created on it, or transferred to it. A shadow file is created on the local system
when the get command is used to transfer a file onto it. Figure 1-4 on page 9
shows the how shadow files are created and transferred between local and
remote systems.
The shadow file is given the extension .shf and is paired with the original file
as part of a single FTAM file entity. The shadow file is copied, renamed, and
deleted in association with the original file for as long as the original file is
managed using SunLink FTAM. However, if the original file is copied,
renamed, or deleted with a UNIX command, or using any other FTAM
application, the associated remote shadow file will remain on the system.
You can display the attributes for a remote file, including the FTAM attributes
contained in the remote shadow file using the ratt command.
1
remote system
local system
create
file1.shf
file1
file2.shf
file2
get
get
file4.shf
Figure 1-4
put
file4
file1.shf
file1
file1.shf
file3
file3.shf
file4
file4.shf
file2
put
file3
file1
Shadow Files on Local and Remote Systems
Shadow File Templates

The attributes set in a shadow file are dependent on the document type of the
original file. Unless specified otherwise, shadow files are created with the
default values shown in Table 1-4:
Table 1-4
Default Shadow File Attributes
Document
Type
Permissions
Universal
Class No.
String Length
String
Significance
F1
r-pxetcd
25
0 (unbounded)
v (variable)
F2
ri--etcd
25
0 (unbounded)
v (variable)
F3
r-pxetcd
0 (unbounded)
v (variable)
I1
r-pxetcd
512
v (variable)
Shadow file templates are used to override the default attributes listed in
Table 1-4 at the time the shadow file is created.
1
You can set different default attributes for each document type by creating a
generic shadow file template using the shf command. If a generic shadow file
exists for a given document type, it is used in preference to the default
attributes listed in Table 1-4 on page 9. Generic shadow file templates are
located in the directory /var/SUNWconn/OSIROOT/ftam/shf and are named
after the four document types as shown in Table 1-5:
Table 1-5
Document Type
/var/SUNWconn/OSIROOT/ftam/shf/ftam1.shf
Used for FTAM-1 documents
/var/SUNWconn/OSIROOT/ftam/shf/intap1.shf
Used for INTAP-1 documents
You can customize the attributes for an individual file by using the create
command with the s option to specify a shadow file template. You can use
the shadow file that is associated with an existing file as a shadow file
template. You can also create a specific shadow file template using the shf
command.
Recovery
The recovery mechanism runs provided that the recovery functional unit is
supported by the FTAM applications running on both systems, and is
negotiated at the time the association is established. This mechanism completes
interrupted file transfers, without the need to repeat the transfer from the
beginning.
Recoverable errors are errors that temporarily interrupt the file transfer, for
example, lack of disk space, congested network resources and network
problems. The recovery mechanism can resume file transfers after the cause of
the error has been resolved.
Unrecoverable errors either prevent a file transfer from being started (for
example, file does not exist) or interrupt the file transfer definitively (for
example, unexpected end-of-file). File transfer cannot be resumed even if
recovery is enabled.
10
1
The FTAM recovery mechanism relies upon the use of special files called
dockets. There is a docket associated with the local and remote ends of each file
transfer. Dockets contain synchronization information that records how much
data has been sent, and how much data has been received.
In the event of a recoverable error, any discrepancy that exists between the
dockets (the amount of information sent and received) is used to calculate the
amount of data that must be resent in order to guarantee that the transfer is
completed successfully. Figure 1-5 illustrates the principle of the FTAM
recovery mechanism.
local system
remote system
put
data received
data sent
lost data to be resent
Figure 1-5
FTAM Error Recovery Mechanism
Access Restriction
Sunlink FTAM imposes a login procedure to restrict access to remote file
systems. To access a file system on a remote system running the SunLink
FTAM responder daemon (osiftrd), the operators user name (login) and
password must be entered in the /etc/passwd file on the remote system.
hostname% /opt/SUNWconn/bin/osiftam papyrus
user name: <enter login>
password: <enter password or press Return>
account: <enter account or press Return>
Refer to Using SunLink FTAM 8.0.2 for more detailed information on logging in
to remote systems using SunLink FTAM.
11
1
DR10
DR10, an addendum to ISO 8571, modifies the sequence of primitives returned
on group error, and the associated diagnostics. Instead of generating a message
for each primitive, a system using DR10 generates a single, group error
message.
DR10 can cause interoperability problems if only one end of a connection uses
it. By default, SunLink FTAM does not use DR10. It is possible to enable it, to
interoperate with an implementation of FTAM that does use it.
SunLink FTAMDirectories and Files

There are five classes of dynamic files associated with SunLink FTAM. The
environment variables that set the default location of these files are used by
both the initiator and the responder. For example, if you define the variable
FTIINID to be /home/user1, osiftam looks for the file
/home/user1/fti.init on startup, and osiftr looks for
/home/user1/ftr.init.
The responder can only use variables that are defined in the root environment
at startup, so, if you redefine the environment variable, you must stop and
restart the osiftrd daemon.
Configuration Files (/var/SUNWconn/OSIROOT/ftam/conf/*.init)

There is one configuration file associated with each part of the SunLink
FTAM implementation. These files are modified using the OPEN LOOK
graphical user interface for SunLink FTAM (ftamtool).
The file fti.init is read each time the SunLink FTAM initiator
(osiftam) is started.
The file ftr.init is read each time the SunLink FTAM responder
(osiftr) is started.
The default location for these files can be changed by setting the
environment variable FTIINID.
12
RSDB Files (/var/SUNWconn/OSIROOT/ftam/rdb/*.rdb)

The remote systems database contains a list of all the remote systems
recognized by the SunLink FTAM initiator (osiftam). It consists of a
directory containing a file entry that corresponds to each remote system in
the database.
environment variable FTIRDBD.
Shadow Files (/var/SUNWconn/OSIROOT/ftam/shf/*.shf)

Shadow files are SunLink FTAM-specific files that are used to handle the
FTAM attributes which are not supported by the UNIX file system. See
Shadow Files on page 7 for more information.
environment variable FTISHFD.
Docket Files (/var/SUNWconn/OSIROOT/ftam/doc/*.doc)

Dockets are special FTAM files that contain the synchronization information
which enables the recovery of interrupted file transfers. See Recovery on
page 10 for more information.
environment variable FTITRFD.
Trace Files (/var/SUNWconn/OSIROOT/ftam/log/*.log)

Traces are logging files that are generated automatically by the SunLink
FTAM local responder and local initiator. See Chapter 8, FTAM Trace Files
for more information.
environment variable FTILOGD.
13
14
Planning your SunLink FTAM

Configuration
Example Configurations
page 15
Interoperating with Other Implementations of FTAM
page 17
Use the information in this chapter to help plan your SunLink FTAM
configuration.
Example Configurations
This section suggests a few possible configurations using SunLink FTAM.
Exchanging Files between Remote Systems

If you install SunLink FTAM on all of the machines on your network, users of
UNIX and non-UNIX machines can exchange and manipulate files regardless
of whether the remote device is on the same LAN or on a remote network
reachable using a public data network.
15
UNIX
system
Non-UNIX
system
gateway
Figure 2-1
X.25 WAN
(CLNP)
Exchanging files between remote systems
For example, in Figure 2-1, above, machines A and B can exchange files as
easily as they could if they were both on the same LAN, regardless of the fact
that there is a public service network between them and that they have
different operating systems.
To set up a configuration like this:
1. Install SunLink FTAM on machine A.
2. Add an entry to the Remote System Database (RSDB) on machine A,
giving information for reaching machine B.
3. Configure machine B, so that it can reach machine A.
Sharing a Local File Server

If you install only the FTAM Initiator (osiftam) on a machine, it can initiate
FTAM exchanges, but not respond to them. This might be appropriate if you
have a group of workstations that need to be able to access files from a local
server.
16
server
Figure 2-2
Sharing a Local File Server
In this case, you would only need to enable the FTAM Responder (osiftr) on
the File Server. To set up a configuration like this:
1. Install SunLink FTAM on the server and the workstations.
2. Optionally, disable the FTAM Responder (osiftr) on the workstations.
3. On each workstation, make an entry in the RSDB providing information
about the server.
You can also include non-UNIX machines in configurations like the one shown
in Figure 2-2.
Interoperating with Other Implementations of FTAM

SunLink FTAM can interoperate with any standard-compliant version of the
FTAM protocols. However, take particular care when configuring SunLink
FTAM, so that the parameters you set are all appropriate to the other version of
FTAM.
Pay particular attention to setting the Local Initiator and Local Responder
parameters to work with the other version of FTAM. Check the following:
Are the Supported Service Classes the same?

Are the Functional Units the same?
Do you need to change the list of Configurable Document Types?
Does the remote version of FTAM use the New Object Identifier for NBS-9?
If it does, as well as selecting this feature using ftamtool, you must also
install version 8.0.2 of the SunLink OSI Communications Platform.
Planning your SunLink FTAM Configuration
17
Does the other version of FTAM use DR10?
For further information on the above parameters, see Chapter 6, SunLink

FTAM Parameters.
18
Configuring SunLink FTAM
Starting ftamtool
page 20
Creating a Remote Systems Database (RSDB)
page 22
Configuring the Local Initiator
page 34
Configuring the Local Responder
page 38
The OPEN LOOK graphical user interface for configuring SunLink FTAM is
called ftamtool. This chapter describes how to use ftamtool to create a
remote systems database (RSDB) and to configure the SunLink FTAM initiator
and responder processes running on the local machine.
Overview
This section summarizes the steps involved in configuring SunLink FTAM. You
do not need to carry out all of these steps if SunLink FTAM is not
interoperating with any other implementations of FTAM. In this case, the
default configuration described in Getting Started with SunLink FTAM should be
sufficient.
There are three parts to configuring SunLink FTAM, configure them in the
following order:
19
3
1. Create the Remote Systems Database.
Every remote destination that you want to be able to reach must appear in
the remote systems database. For destinations that also use SunLink FTAM,
you only need to configure the Network Address. Follow the instructions in
Creating a Remote Systems Database (RSDB) on page 22.
2. Configure the Local Initiator.
The local initiator defines the functional units and service classes proposed
by the SunLink FTAM initiator (osiftam) during the negotiation phase.
You only need to change the default configuration if you are interoperating
a different implementation of the FTAM responder. Follow the instructions
in Configuring the Local Initiator on page 34.
3. Configure the Local Responder.
The local responder defines the functional units and service classes
proposed by the SunLink FTAM responder (osiftr) during the negotiation
phase. You only need to change the default configuration if you are
interoperating with a different implementation of the FTAM responder.
Follow the instructions in Configuring the Local Responder on page 38.
Note If you do not have access to ftamtool, you can make changes to the
Remote Systems Database while running the FTAM initiator. The commands
for doing this are described in Appendix A, SunLink FTAM Command
Summary.
Starting ftamtool
You can run ftamtool either locally or remotely.
Staring ftamtool Locally

To start and use ftamtool on your local machine, type:
hostname% /opt/SUNWconn/bin/ftamtool &
The ftamtool main window looks like this:
20
Starting ftamtool Remotely

To use ftamtool to configure a remote machine, start it remotely and display
the output on your local monitor:
1. On your local machine, disable access restrictions for the remote machine
so you are able to display ftamtool on your local monitor.
localhost% $OPENWINHOME/bin/xhost + <remotehost>
2. Log in to the remote machine.

localhost% rlogin <remotehost>
Password: <your password>
3. On the remote machine, start ftamtool so that it displays on your local

monitor.
remotehost% /opt/SUNWconn/bin/ftamtool -display <localhost>:0 &
21
3
Creating a Remote Systems Database (RSDB)
The remote systems database (RSDB) contains a list of the remote systems
recognized by the local FTAM initiator (osiftam). It creates a mapping
between the host names used to reference remote hosts, and the OSI addresses
used to reach them.
To activate the RSDB configuration window, click SELECT on the Remote
Systems Database icon in the ftamtool main window.
22
3
The scrolling-list displays an alphabetical list of the host names of all the
systems currently entered in the RSDB. To display an entry, double-click it in
the scrolling list, or type the name at the Enter System Name prompt. To
change directory, type in the path to the directory and click SELECT on the
Goto button.
Type in the name of the

directory and click SELECT on Goto
Click SELECT to
choose a system
Type name of
existing system
Adding an Entry to the RSDB

There are two ways of adding an entry to the RSDB.
The simplest way to add entries RSDB is to modify one of the three templates.
You cannot overwrite or delete the RSDB templates, unless you change the
default access permissions for these files.
You can also create a completely new entry.
Modifying an Existing Template

To add an entry to the RSDB by modifying one of the templates:
1. Display the Remote Systems Database configuration window.
Click SELECT on the RSDB icon in the main window.
23
3
2. Click SELECT on the name of the appropriate RSDB template.
Choose between:
SUN_llc1: for LAN connections (for example, Ethernet, FDDI)

SUN_rfc: for TCP/IP connections (RFC 1006)
SUN_x25: for WAN connections (for example, X.25)
Click SELECT to choose

an RSDB template
3. Modify the Current System Name.

This is the host name used to reference the remote system establishing an
association. You cannot save your modifications using the existing system
name, as this would overwrite the template.
Type in a new system name
24
3
4. Modify the Application Process Title (APT).
You only need to do this if the remote system is not running the SunLink
FTAM responder daemon, osiftrd. The default APT, which is displayed
when you load an RSDB template, corresponds to the SunLink FTAM
responder daemon (osiftrd).
To find out the correct APT for a non SunLink FTAM responder daemon,
check with the system administrator responsible for the remote system. See
Application Process Title on page 62 for a more detailed description of the
APT.
Enter the components of the APT separated by blank spaces, dots, or
dashes.
5. Modify the Application Entity Qualifier (AEQ).
You only need to do this if the remote system is running a different
implementation of the FTAM responder daemon. The default AEQ, which is
displayed when you load an RSDB template, corresponds to the SunLink
FTAM responder daemon (osiftrd).
To find out the correct AEQ for a non SunLink FTAM responder daemon,
check with the system administrator responsible for the remote system. See
Application Process Title on page 62 for a more detailed description of the
AEQ.
Type the correct APT
Click SELECT to
change the AEQ
6. Modify the OSI address elements.

The default OSI address, which is displayed when you load an RSDB
template, corresponds to the SunLink FTAM responder daemon (osiftrd).
25
If osiftrd is running on the remote system, then you need only modify the
Network Address element.
If there is a different FTAM responder running on the remote system, then

you must enter all of the OSI address elements that correspond to that
application. You may need to obtain the OSI address from the system
administrator who set up the remote system.
Refer to the Remote Systems Database Parameters on page 61 for a

description of each of the elements in an OSI address. Enter the OSI address in
either hexadecimal or ASCII format.
Type in an
ASCII value
Change to
hex format
Type in a
hex value
The network address is the part of the OSI address that identifies the physical
connection to the network:
26
For a LAN (LLC1) connection (for example, Ethernet, FDDI), enter the
network address in hexadecimal format. It is the NSAP address assigned for
the OSI protocol stack. If the remote system is running SunLink FTAM, this
is the NSAP assigned using ositool. By default it takes the form
49<hostid>01, as shown below:
3
Network address of the form:
49<hostid>01
Network type
set to LLC1
For a WAN connection (for example, X.25) the network address is the NSAP
address of the remote OSI protocol stack. If the remote system is running
SunLink FTAM, this is the NSAP assigned using ositool.
Network type
set to X.25
For a TCP/IP connection (RFC 1006), enter the network address in ASCII. It
is the IP address (entered in dot notation) for the remote system. You cannot
enter the host name in the place of an IP address. If the remote system is
running SunLink FTAM, this is the IP address assigned using ositool.
27
3
Network type
set to RFC1006
7. Click SELECT on Apply to confirm your changes and to add a new entry
to the Remote Systems Database (RSDB).
New entry added to

the scrolling-list
(based on template)
Add an entry in the RSDB for every remote system that you want to be able to
access using the SunLink FTAM initiator.
Adding a Completely New Entry

Use the New button to add a completely new entry to the Remote Systems
Database (RSDB), instead of basing the entry on one of the three RSDB
templates (SUN_llc1, SUN_rfc, and SUN_x25).
To add a new entry to the RSDB:
28
3
1. Click SELECT on the RSDB icon to activate the RSDB configuration
window.
2. Click SELECT on the New button to add a new (blank) entry to the RSDB.
Click SELECT on New
3. Click SELECT on the Network Type that corresponds to the connection

between the local system and the remote system as shown in.
Choose one of the three supported subnetwork types:
X.25: WAN connections

LLC1: LAN connections (for example, Ethernet, FDDI)
RFC1006:TCP/IP connections
29
Click SELECT to choose

a network type
4. Enter a System Name, Application Entity Title (AET) and OSI Address.
Follow the instructions in Modifying an Existing Template on page 23.
5. Click SELECT on Apply to confirm your changes and to add a new entry
to the Remote Systems Database (RSDB), as shown below:
New entry added to

the scrolling-list
Deleting an Entry from the RSDB

To delete an entry from the Remote Systems Database:
window.
2. Click SELECT on one the entries in the scrolling-list that you want to
delete.
30
3
3. Click SELECT on the Delete button to remove the system from the
Remote Systems Database.
You cannot recover a deleted system once you have confirmed the delete
operation. You cannot delete the RSDB templates unless you have modified
the permissions for these files.
Printing the RSDB

To print a list of all the systems registered in the Remote Systems Database:
window.
2. Click SELECT on the Print... button to activate the Print window.
3. Choose a printer from the Printer list, or click SELECT on the Print to File
checkbox and specify the name of a file.
Press MENU
Drag and release MENU

on the chosen printer
4. Click SELECT on Print to send the file to the specified printer (or file).
31
3
The output looks like this:
----- SUN_llc1.rdb
Application Process Title: 1 3 9999 1 7
Application Entity Qualifier: 1
PSEL: ftr
SSEL: prs
TSEL: ses
Network Address: 0x491234567801
Network Type: CLNP
System Status: Open
----- SUN_rfc.rdb
PSEL: ftr
SSEL: prs
TSEL: Empty
Network Address: 1.2.3.4
Network Type: TCP-IP
System Status: Open
----- SUN_x25.rdb
PSEL: ftr
SSEL: prs
TSEL: ses
Network Address: x25_address
Network Type: CONS
System Status: Open
----- rasputin.rdb
PSEL: ftr
SSEL: prs
TSEL: ses
Network Address: 12345678
Network Type: CONS
System Status: Open
32
3
Closing and Opening Systems
Closing a system in the Remote Systems Database temporarily prevents the
SunLink FTAM initiator (osiftr) from opening an association with it. The
system remains in the Remote Systems Database, and can be reopened later.
To close a system:
window.
2. Click SELECT on the entry in the scrolling-list that you want to close.
3. Press MENU on the System Status button to display the pull-down menu.
Drag MENU to the Close item and release MENU to close the currently
selected system.
4. Click SELECT on Apply to confirm your changes.
To open a closed system:
window.
2. Click SELECT on the entry in the scrolling-list that you want to open.
3. Press MENU on the System Status button to display the pull-down menu.
Drag MENU to the Open item and release MENU to open the currently
selected system.
4. Click SELECT on Apply to confirm your changes.
Closing an open system

Opening a closed system
33
3
Configuring the Local Initiator
To open an association, the SunLink FTAM initiator (osiftam) negotiates with
the FTAM responder running on the remote system to define a common set of
functional units and services classes. (See Functional Units and Service
Classes on page 6.)
The local initiator options define the functional units and service classes
proposed by the SunLink FTAM initiator (osiftam) running on the local
system during this negotiation phase. By default, osiftam proposes all of the
functional units and service classes that it supports.
If the SunLink FTAM responder (osiftr) is running on the remote system,

do not alter the default configuration for the local initiator.
If there is any other type of FTAM responder running on the remote system,
you may need to modify the default configuration of the local initiator to
match the configuration of the remote responder. Check with the system
administrator responsible for the remote responder to find out whether you
need to do so.
Note Proposing a functional unit or service class that is not supported by the
FTAM responder does not prevent an association from being established.
Failing to propose a supported functional unit or service class reduces the
versatility of your file management system, and might reduce the chance that
association negotiation will be concluded successfully.
Modifying the Default Initiator Configuration

To modify the default configuration for the local initiator:
1. Click SELECT on the Local Initiator icon to activate the Local Initiator
configuration window.
2. Click SELECT on the checkboxes to disable the service classes that you do
not want the initiator to propose when negotiating an association.
34
Indicates that the service

class will not be proposed
class will be proposed
3. Click SELECT on the checkboxes to disable the functional units that you
do not want the initiator to propose when negotiating an association.
Indicates that the functional

unit will not be proposed
unit will be proposed
4. Click SELECT on the Configurable Document types you do not want the
initiator to propose when negotiating an association.
Indicates that INTAP-1

will not be used
35
3
5. Click SELECT on the New Object Identifier for NBS-9 parameter, if you
require this Object Identifier type:
You only require this Object Identifier type if you are interoperating a
different implementation of FTAM, that implements the version of this
parameter defined in the published version of the ISO FTAM Specification
(8571), rather than the version given in the preliminary draft. If you do
require this option, you must also use version 8.0.2 or later of the SunLink
OSI Communications Platform (Stack).
6. Click SELECT on the DR10 and Traces checkboxes if you want to enable
Defect Report 10 or tracing (logging).
Do not enable DR10 unless you are interoperating with an implementation
of FTAM that uses it.
Indicates that DR10
will not be used
Indicates that the tracing
will be done
7. Click SELECT on Apply to confirm your changes to the local initiator

configuration.
If you have configured an invalid combination of service classes and
functional units, the system generates an error message when you apply
your changes. Follow the instructions included in the error message to
correct the error, and click SELECT on Apply to confirm your changes.
Saving the Initiator Configuration

The local definitions are stored in a configuration file called fti.init which
is read each time osiftam is started. This file is normally located in the
directory /var/SUNWconn/OSIROOT/ftam/conf.
36
3
To save a copy of the initiator configuration in a different file:
2. Press MENU on the File button and drab MENU to the Save as... item.
Release MENU to activate the Save as file selection window.
3. Enter the name of a new file or choose an existing file from the scrollinglist.
You cannot overwrite the configuration file fti.init. To modify this file,
make and apply the changes to the local initiator configuration.
4. Click SELECT on Save to save a copy of the configuration to file.
To use the contents of the backup file to configure the SunLink FTAM
initiator (osiftam), manually copy the backup file into the configuration
file fti.init.
Printing the Initiator Configuration

To print the local initiator configuration:
2. Press MENU on the File button and drag MENU to the Print... item.
Release MENU to activate the Print window.
Press MENU

37
3
The print-out looks like this:
OSI 8.0.1 FTAM Local Initiator Configuration
Copyright 1993 Sun Microsystems, Inc.
Supported Service Class:
Access ON
Transfer&Management ON
Transfer ON
Management ON
Functional Units:
Read ON
Write ON
File Access ON
Limited File Management ON
Enhanced File Management ON
Grouping ON
Recovery ON
DR10: OFF
Traces: ON
Configuring the Local Responder

To respond to an association request, the SunLink FTAM responder (osiftr)
negotiates with the FTAM initiator running on the remote system to define a
common set of functional units and services classes. (See Functional Units and
Service Classes on page 6.)
The local responder options define the functional units and service classes
proposed by the SunLink FTAM responder (osiftr) running on the local
system during this negotiation phase. By default, osiftr proposes all of the
functional units and service classes that it supports.
38
If an SunLink FTAM initiator (osiftam) is requesting the association you

do not need to alter the configuration for the local responder.
If there is any other type of FTAM initiator running on the remote system,
you might need to modify the default configuration of the local responder to
match the configuration of the remote initiator. Check with the system
administrator responsible for the remote initiator to find out whether you
need to do so.
FTAM responder does not prevent an association from being established.
Failing to propose a supported functional unit or service class reduces the
versatility of your file management system, and might reduce the chance that
Modifying the Default Responder Configuration

To modify the default configuration for the local responder:
1. Click SELECT on the Local Responder icon to activate the Local
Responder configuration window.
2. Click SELECT on the checkboxes to deselect the service classes that you
do not want the responder to propose when negotiating an association.

class will not be proposed
class will be proposed
3. Click SELECT on the checkboxes to deselect the functional units that you
do not want the responder to propose when negotiating an association.
39

unit will not be proposed
unit will be proposed
4. Click SELECT on the DR10 and Traces checkboxes if you want to enable
Defect Reporting 10 or tracing (logging).
Do not enable DR10 unless you are interoperating with an implementation
of FTAM that uses it.
Indicates that DR10

will not be used
Indicates that the tracing
will be done
5. Click SELECT on Apply to confirm your changes to the local responder

configuration.
If you have configured an invalid combination of service classes and
functional units, the systems generates an error message when you apply
your changes. Follow the instructions in the error message to correct the
error, and click SELECT on Apply to confirm your changes.
Saving the Responder Configuration

The local definitions are stored in a configuration file called ftr.init which
is read each time osiftr is started. This file is normally located in the
directory /var/SUNWconn/OSIROOT/ftam/conf.
To save a copy of the responder configuration in a different file:
40
3
2. Press MENU on the File button and drag MENU to the Save as... item.
Release MENU to activate the Save as file selection window.
3. Enter the name of a new file or choose an existing file from the scrollinglist.
You cannot overwrite the configuration file ftr.init. This file can only be
modified by applying the changes to the local responder configuration.
4. Click SELECT on Save to save a copy of the configuration to file.
To use the contents of the backup file to configure the SunLink FTAM
responder (osiftr) you must manually copy the backup file into the
configuration file ftr.init.
Printing the Responder Configuration

To print the local responder configuration:
2. Press MENU on the File button and drab MENU to the Print... item.
Release MENU to activate the Print window.
Press MENU

41
3
The local responder configuration looks like this:
OSI 8.0.1 FTAM Local Responder Configuration
Supported Service Class:
Access ON
Transfer&Management ON
Transfer ON
Management ON
Functional Units:
Read ON
Write ON
File Access ON
Limited File Management ON
Enhanced File Management ON
Grouping ON
Recovery ON
DR10: OFF
Traces: ON
42
Using the FTAM Responder

(osiftr)
Starting and Stopping the FTAM Responder Daemon
page 43
Restricting Remote Access
page 46
This chapter describes how to launch the SunLink FTAM responder daemon on
your local machine, and how to control remote access to your machine by
creating a list of authorized users. It assumes that you have configured
SunLink FTAM and set up a database of the remote systems that are
recognized by the initiator application, as described in Chapter 3, Configuring
SunLink FTAM.
Starting and Stopping the FTAM Responder Daemon

The SunLink FTAM responder process (osiftr) is launched by a daemon
(osiftrd) each time an association request is received from an FTAM client
such as the SunLink FTAM initiator (osiftam). There is one FTAM responder
daemon (osiftrd) for each of the three subnetwork types supported by
SunLink OSI. You must specify the subnetwork type when you start the
daemon.
43
4
Starting Responder Daemon Automatically
When you install the SunLink FTAM software on your system, a start-up script
(S147osiftrd) is placed under /etc/rc3.d. This script ensures that the
FTAM responder daemon (osiftrd) is started automatically each time the
system is rebooted. The script probes the system to determine which network
interfaces are installed and starts an appropriate FTAM responder daemon for
each interface type it detects.
You can prevent the FTAM responder daemon from being started at boot time
by renaming the start-up script (for example, S147osiftrd ->s147osiftrd)
Starting the Responder Daemon Manually

You can also start a SunLink FTAM responder daemon manually by running
the script osiftrd_start and specifying the subnetwork type.
To protect your network from unauthorized reconfiguration, the script used to
start the FTAM responder daemon can only be launched by someone with
superuser privileges.
1. Log in as root or become superuser.
hostname% su
Password: <your superuser password>
2. Start the FTAM responder daemon, specifying the subnetwork type

<network_id> as shown in Table 4-1.
hostname# /opt/SUNWconn/bin/osiftrd_start <network_id>
Table 4-1
44
Subnetwork Types
Network_I
d
Subnetwork Type
cons
WAN (for example, X.25)
clnp
LAN (for example, ethernet, FDDI)
tcp
RFC1006 (TCP/IP)
4
Stopping the Responder Daemon Manually
You can stop any SunLink FTAM responder daemon (whether it was started
automatically at boot time, or manually using the script osiftrd_start) by
running the script osiftrd_stop and specifying the subnetwork type.
To protect your network from unauthorized reconfiguration, the script used to
stop the SunLink FTAM responder daemon can only be started by someone
with superuser privileges.
1. Log in as root or become superuser.
hostname% su
Password: <your superuser password>
2. Stop the SunLink FTAM responder daemon, specifying the subnetwork

type <network_id> as shown in Table 4-2.
hostname# /opt/SUNWconn/bin/osiftrd_stop <network_id>
Table 4-2
Subnetwork Types
Network_I
d
Subnetwork Type
cons
WAN (for example, X.25)
clnp
LAN (for example, ethernet, FDDI)
tcp
RFC1006 (TCP/IP)
Using the FTAM Responder (osiftr)
45
4
Restricting Remote Access
Sunlink FTAM responder imposes a login procedure to restrict access to remote
file systems. To access a file system on a remote system running the SunLink
FTAM responder daemon (osiftrd), the operators user name (login) and
password must be entered in the /etc/passwd file on the remote system.
hostname% /opt/SUNWconn/bin/osiftam papyrus
user name: <enter login>
password: <enter password or press Return>
account: <enter account or press Return>
Refer to Using SunLink FTAM 8.0.2 for instructions on logging in to remote

systems using SunLink FTAM.
46
Troubleshooting
Problems Opening a Connection
page 48
Interoperability Problems
page 50
Problems with Licensing
page 52
This chapter provides information to help you solve problems which may arise
when you are using SunLink FTAM. If you are unable to solve the problem
using the information here, contact your authorized service provider for
further help. If you do this, have as much information available as possible
about your configuration and about any tests you have already carried out.
In a great many cases, problems with SunLink FTAM are due to a problem
with the underlying network configurationfor example, if you are unable to
open an association with a remote destination, this may indicate a CLNP
routing problem, rather than an FTAM problem.
To work out where the problem lies, carry out the following checks:
Double-check your configuration to make sure that all the information you
have entered correct and up to date.
Check that the OSI Stack is running on both the local and remote machines.
Check that the remote machine is running the FTAM responder daemon.
Check any error messages and take the corrective action suggested.
47
Use the FTAM trace facility, to find out if the problem is with FTAM. See
Chapter 8, FTAM Trace Files.
Use the osi_ping program to check for CLNP routing problems.

This program is delivered as part of the OSI stack. Refer to the
Troubleshooting chapter of your SunLink OSI documentation for details.
Use the osi_trace program to find out if there is a problem at another

layer. This program is delivered as part of the OSI stack. Refer to the
Troubleshooting chapter of your SunLink OSI documentation for details
Problems Opening a Connection

If you cannot open an FTAM connection between two systems running
SunLink FTAM, you will probably see one of the following error messages:
Error connecting to host, FTAM diagnostic = None
Unrecoverable error, Connexion off
or
Error connecting to host, FTAM diagnostic = 1011
1011: Lower layer failure
Unrecoverable error, Connexion off
48
5
1. Check that the OSI Stack is running on both the local and the remote
machines:
host# ps -ef | grep osi
If the OSI Stack is running, there is a line for osinetd that looks something
like this:
root
1027
49
Aug 05
0:00 osinetd
If the stack is not running on one or both machines, restart it, and try again.
To restart the stack, enter:
host# /etc/rc2.d/S90osinet start
2. Log in to the remote machine and check that the FTAM responder daemon
is running:
remote_host# ps -ef | grep osiftrd
The display should look something like this:

root 9354
root 9349
root 9347
1 55 10:25:16 ? 0:01 /opt/SUNWconn/bin/osiftrd -s 264

osiftrd -s 64 is the FTAM daemon for X.25 connections, osiftrd -s

164 for LAN (llc1) connections and osiftrd -s 264 for TCP/IP
(rfc1006) connections.
osiftrd -s 64 only runs if there is an X.25 device on the machine
(/dev/x25). The other two daemons run all the time.
If the daemons are not running, there are two ways to restart them:
Troubleshooting
49
5
using the/etc/rc3.d/S147osiftrd start-up script, which automatically
starts all the daemons
using the osiftrd_start script in the /opt/SUNWconn/ftam/bin
directory, which starts each one individually.
3. Check you are using the correct OSI address to call the remote FTAM
host.
As superuser (root) start ositool on the remote host. Click SELECT on
the Stack Manager icon. Press MENU on the Configuration menu button
and choose the Application Selectors option. Click SELECT on FTAM in the
scrolling list. Check that the values displayed for the PSEL, SSEL and TSEL
match those used in the RSDB of the local machine for the remote host.
To find out the NSAP value, choose the Network Layer Addresses icon in
ositool. Click SELECT on the appropriate subnetwork Type. The NSAP
value is displayed in the window left bottom border.
To check this, start ftamtool on the local hostsee Starting ftamtool on
page 20, click SELECT on the RSDB icon and then click SELECT the remote
host entry in the Current Systems list. Compare the addressing information
shown with the addresses shown by ositool.
Interoperability Problems
This section describes some problems you might come across when
interoperating with another implementation of FTAM, and suggests some
solutions. First it covers problems you might have when using the SunLink
FTAM initiator with a non-Sun responder, then problems you might have
using a non-Sun initiator with the SunLink FTAM responder.
SunLink FTAM initiator and non-Sun Responder

Symptoms are given first, followed by causes and a suggested solution.
The remote responder aborts when osiftam sends out an FTAM

Initialization request PDU.
This is caused by the Presentation Context Definition List being too long.
To solve the problem, reconfigure osiftam to send out only a subset of the
supported documentation types.
50
5
To do this, start ftamtool, select Local Initiator and then deselect one or all
of the Configurable Document Types depending on your needs. Apply and
exit. For example, if you are not planning to use INTAP-1 documents,
deselect this document type. Note that the minimum set proposed always
consists of the FTAM-1 unstructured text and FTAM-3
unstructured binary document types.
The remote responder aborts when osiftam sends out an FTAM

Iniatilization request PDU.
There are two possible causes to investigate:
Firstly, find out whether the system you are interoperating with implements
the version of the Object Identifier for NBS-9 parameter defined in the
published version of the ISO FTAM Specification (8571), rather than the
version given in the preliminary draft. If this is the case, select the New
Object Identifier for NBS-9 parameter, as described Configuring the Local
Initiator on page 34. If you do this, you must also make sure that you are
using version 8.0.2 of the SunLink OSI Communications Platform.
Secondly, check whether the Checkpoint Window parameter is set to an
unsupported value, by changing osiftam to send out a Checkpoint
Window value of 1, instead of the default value, 15. To do this, start
ftamtool, select Local Initiator and then deselect the Recovery Functional
Unit. Apply and exit.
Problems writing a file using the put command.

By default, osiftam uses the Graphic String Universal Class Number when
transferring FTAM-1 and FTAM-2 type files. These are the default file types
for UNIX text files. This means that it does not check for the presence of
format effector characters, such as LF and TAB. This may prevent transfers
to FTAM responders that do check for the presence of such characters.
To solve this problem, before performing the file transfer create a shadow
file specifying a Universal Class No. of General String. To do so, in the same
directory as the file, enter:
osiftam> shf <filename> -d F1 -u 27 -t n
Troubleshooting
51
5
Then perform the transfer:
osiftam> put <filename> <newfilename>
This transfers the file with a Universal Class No. General String, allowing
the FTAM responder to check for format effector characters.
Non-Sun Initiator and SunLink FTAM Responder

Symptoms are given first, followed by causes and a suggested solution.
When the remote host tries to establish an FTAM connection with osiftr,
nothing happens and ftam traces are not generated.
An incorrect Application Entity Title has been used to address SunLink
osiftr.
To resolve the problem, ask the remote administrator to check the
Application Entity Title used to call osiftr. The AET is made up of two
parts, an Object Identifier, called the Application Process Title and an
integer value, called the Application Entity Qualifier. The correct values for
calling SunLink osiftr are the following: APT = 1.3.9999.1.7 and AEQ=1,
or APT = 1.3.9999.1.7 and no AEQ, or no APT and no AEQ.
You can also use ftamtool to display these values. Click SELECT on the
RSDB icon, and then on one of the SUN templates in the list. The APT and
AQT are displayed in the lower half of the screen.
Problems with Licensing

A licensing problem may also stop you using SunLink FTAM
Problems Starting the License Installation Tool

You Must Be Superuser to Run This Program - Exiting
You must possess superuser privileges to modify your license system.

Become superuser and re-start the lit.
52
5
Cannot open the feature file.
You must use the license installation tool delivered as part of the SunLink
OSI release. This applies even if you have previously installed the license
system for another product. Use Software Manager (swmtool) to install the
package SUNWlit on the license server.
No Products Identified in LIC_CONFIG_FILE File - Exiting
You must use the license installation tool delivered as part of the SunLink
OSI release. This applies even if you have previously installed the license
system for another product. Use Software Manager (swmtool) to install the
package SUNWlit on the license server.
Unable to Change License Server(s)

The license installation tools are designed to prevent the common problem of
requesting a license password for the wrong license server. The tools do not
allow you to change the license server while running on a license server.
If you want to set up another independent license server, install the SUNWlit
and SUNWlicsw packages on that machine and run the license installation
tools from there. Remember that once a machine has been set up as a member
of a set of redundant license servers, all licenses for a machine in that set must
be for all redundant servers of the set.
Mistyped License Information

If you mistyped the license information prior to selecting the Done With
License or Quit Save options of the license installation tool, quit without
saving the license and restart the tool. Enter the correct license information and
save the license.
If you have noticed that you have mistyped the license information after
completely installing the license, you can enter the license again using the lit
or lit_tty with the correct information. The only exception to this is if the
license has been completely installed and the license server information is
incorrect. The only solution to this is to remove the license system.
Errors Executing the License Configuration Script

The following errors are related to the license configuration script:
Troubleshooting
53
5
**Some duplicate licenses were detected during installation**
This message is displayed after executing the LIC_CONFIG_SCRIPT. This

may be due to an attempt to install the same license more than once. No
action is required.The script identifies licenses that are duplicates and not
installed. The script also identifies licenses that are successfully installed.
Cannot build elementary license file for feature_name
If this message is displayed after executing the LIC_CONFIG_SCRIPT, your

license probably was not installed correctly. Re-run the license installation
tool.
Cannot access location to store product licenses <location> Exiting
If this message is displayed after executing the LIC_CONFIG_SCRIPT, create

the directory specified in the error message, and execute the
LIC_CONFIG_SCRIPT again.
You must be root to execute this script
You must possess superuser privileges to modify your license system.

Become superuser and re-run the LIC_CONFIG_SCRIPT script.
LIC_CONFIG_SCRIPT: Cannot execute
This message is displayed after executing the LIC_CONFIG_SCRIPT. The

script must have execute permission. Enter the following command (as
superuser) to change to the appropriate permissions:
hostname# chmod 744 LIC_CONFIG_SCRIPT
Removing the License System

If you encounter severe problems when installing your license, you may need
to remove the FTAM license system and repeat the installation. To remove the
SunLink OSI license:
54
5
1. Edit the /etc/opt/licenses/licenses_combined file.
As root, open the file using a text editor and delete all lines that begin:
INCREMENT FTAM
If SunLink OSI is the only licensed product on your system, you can delete
the whole file.
2. Delete the osiftam8.0.lic,n files.
These files are in the /opt/SUNWconn/license_dir directory. n is a
number.
Recovering a Lost License

If a Right To Use license is reported in use when it is not being used (for
example, if a licensed product is in use at the time of a system crash), the
license server may not know that the Right To Use license is no longer in use.
At the license server, the lmstat(1) command can be used to get the status of
the active license(s). If the license is incorrectly reported in use, the
lmremove(1) command can be used to recover the Right To Use license.
Use the lmstat(1) command to obtain the arguments to the lmremove(1)
command.
host1# /etc/opt/licenses/lmstat -a -c /etc/opt/licenses/licenses_combined
lmstat - Copyright (C) 1989, 1990, 1991, Highland Software, Inc.
Flexible License Manager status on Fri 2/12/93 11:42
License server status:
host1: license server UP (MASTER)
host2: license server UP
host3: license server UP
Vendor daemon status (on host1):
lic.SUNW: UP
Feature usage info:
Users of SUNW<feature>: (Total of 4 licenses available)
root at host1 on host1.host1 (v8.010), started Fri 1/22/93 at 17:26
Troubleshooting
55
5
From the lower section of the output supplied by lmstat(1), the feature, user,
host, and display arguments can be obtained. After the lmremove(1)
command has been issued, the lmstat(1) command can be used again to
verify the status of the operation.
host1# cd /etc/opt/licenses
host1# lmremove -c /etc/opt/licenses/licenses_combined SUNW<feature> root\ host1 host1.host1
Unlocking a Stopped License System

If the license system is stopped by killing the license daemon, the file
/var/tmp/locklic.SUNW may be left on the machine. This file must be
deleted manually before the license system can be restarted.
SunLink OSI Specific Errors

The following error messages are returned by the licensing system with regard
to the SunLink OSI release.
<feature>: cannot find license file (No such file or directory)
When the product Right To Use license is installed on the license server
using the lit or lit_tty, a utility is automatically created for installing
that same Right To Use license onto any machines running the SunLink OSI
release that will be using that license and license server. This utility, named
/etc/opt/licences/LIC_CONFIG_SCRIPT, must first be copied and then
executed on each machine running the SunLink OSI release. The command
can be copied using any standard method that would normally be used for
file copy, for example rcp(1) or ftp(1).
If you have moved the product directory to some place other than where it
was originally installed, you may have this problem. The easiest way to
correct the situation, is to remove (using pkgrm) the SunLink OSI release
packages, and reinstall the product. The license system should not be
affected.
Check the /tmp/license_log and /tmp/license_errors files on the
license server for more information on other possible causes.
56
5
Can't get server: cannot find license file (No such file or
directory)
When this message is displayed during execution of a FLEXlm utility, it is

easily corrected by specifying the following option on the command line
when you start the utility:
-c /etc/opt/licenses/licenses_combined
This must be run on the license server.

Feature has expired:
This message indicates the license you are using for the SunLink OSI has
expired. If the license was for a demo, it is no longer valid. You must obtain
a new license to use the product.
<feature>: encryption code in license file is inconsistent
This error message indicates that there is an error in the product license file.
When the SunLink OSI release attempts to establish a licensed session, the
Right To Use license file is used to supply the license server with product
and verification information needed to check out a Right To Use license.
Any typographical error or absence of required data within the license file
will result in this error. This problem is typically caused by an error in the
license password entered into the lit or lit_tty. If this is the problem, the
lit or lit_tty must be re-run with the correct data entered, then the
newly created LIC_CONFIG_SCRIPT must be copied and re-run on each
redundant license server and machine running the SunLink OSI release.
Troubleshooting
57
5
<feature>: cannot connect to license server (Connection refused)
This message appears when attempting to run the SunLink OSI release. In
this case, it is probable that the license daemon is not running on the license
server. Login to the license server and execute the following command:
hostname# ps -ef | grep lic.SUNW | grep -v grep
If output appears, then the daemon is running. If no output appears, then

the license daemon is not running and must be started. Execute the
following command:
hostname# /etc/rc2.d/S85lmgrd
<feature>: cannot read data from lic server

This error message indicates that there is no quorum of license servers.
When utilizing a redundant license server configuration, if the majority of
the license servers are not up and running, you will not be able to obtain a
Right to Use license. Once the majority of the license servers (two out of
three or three out of five) are up and running, Right to Use licenses will
again be available
58
Part 2 Reference
SunLink FTAM Parameters
Remote Systems Database Parameters
page 61
Local Initiator and Responder Parameters
page 64
This chapter summarizes the parameters you may need to set when
configuring SunLink FTAM.
Remote Systems Database Parameters

The remote systems database contains a list of the remote systems recognized
by the local FTAM initiator (osiftam). It creates a relationship between the
host names used to reference remote hosts, and the OSI addresses used to
reach them.
RSDB Templates
There are three template entries supplied by ftamtool. Each entry
corresponds to a nonexistent system that could be reached across one of the
three supported subnetwork types:
SUN_llc1 is a template entry for systems that can be reached across a

CLNP connection (for example, Ethernet, FDDI).
SUN_rfc is a template entry for systems that can be reached across a

TCP/IP connection (RFC 1006).
61
SUN_x25 is a template entry for systems that can be reached across a CONS
connection (for example, X.25).
Current System Name

This is the name you want to refer to the remote system by, when opening
FTAM connections. The name must not be more that six characters long.
Application Process Title

An ascii character string that identifies the FTAM process. The APT for the
SunLink FTAM responder process (osiftr) is: 1 3 9999 1 7. If you set this
to a null value (be leaving the field empty), the AEQ must also be null.
If the remote system is running another vendors FTAM responder, obtain the
AET for the responder process from its system administrator.
If both remote and local systems are running SunLink FTAM, you do not need
to change the default value.
Application Process Qualifier

An integer value that qualifies the Application Process Title (APT). A zero
value is interpreted as a null (empty) entry. The AEQ for the SunLink FTAM
responder process (osiftr) is: 1
The elements of the Application Process Title can be separated by blank spaces,
dots, or dashes. For example: 1.3.9999.1.7 or 1-3-999-1-7
Presentation Selector (PSEL)

The presentation selector is the part of the OSI address that identifies the user
of the service provided by the presentation layer in this case, the FTAM
responder running on the remote system. If the remote system is running
SunLink FTAM, the user is the SunLink FTAM responder daemon (osiftrd).
62
6
Enter the presentation layer selector in either ASCII character format or in
hexadecimal format. By default, the presentation selector for a SunLink FTAM
responder daemon (osiftrd) is set to ftr (ASCII).
Session Selector (SSEL)

The session selector is the part of the OSI address that identifies the user of the
service provided by the session layer: in this case, the presentation layer. Enter
it in either ASCII character format or in hexadecimal format. By default, the
session selector for a SunLink FTAM responder daemon (osiftrd) is set to
prs (ASCII).
Transport Selector (TSEL)

The transport selector is the part of the OSI address that identifies the user of
the service provided by the transport layerin this case, the session layer.
Enter it in either ASCII character format or in hexadecimal format. By default,
the transport selector for a SunLink FTAM responder daemon (osiftrd) is set
to ses (ASCII) for CONS and CLNP connections, and to a null value for
TCP/IP.
Network Address
The network address is the part of the OSI address that identifies the physical
connection to the network.
For a CLNP connection (for example, Ethernet, FDDI) the network address
is the NSAP address assigned to the OSI protocol stack. If the remote system
is running SunLink FTAM, this is be the NSAP assigned using ositool. By
default, it takes the form 49<hostid>01, where <hostid> is the hostid of the
remote system.
63
For a CONS connection (for example, X.25) the network address is the
NSAP address assigned to the remote OSI protocol stack. If the remote
system is running SunLink FTAM, this is the NSAP assigned using
ositool.
For a TCP/IP connection (RFC 1006), the network address is the IP address
(entered in dot notation) for the remote system. Enter it in ASCII. You
cannot enter a host name in the place of an IP address.
Network Access
Specify the type of network you are attaching to, X.25, LLC1 or RFC1006. You
do not need to change this parameter if you are using one of the templates
provided.
System Status
Toggle this parameter to Closed to temporarily prevent associations being
opened with this system. Reset it to Open to re-allow associations.
Local Initiator and Responder Parameters

To open an association, the SunLink FTAM initiator (osiftam) negotiates with
the FTAM responder running on the remote system to define a common set of
functional units and services classes. (See Functional Units and Service
Classes on page 6.)
The local initiator options are used to define the functional units and service
classes proposed by the SunLink FTAM initiator (osiftam) running on the
local system during this negotiation phase. By default, osiftam proposes all
of the functional units and service classes that it supports. There are also
options to enable Defect Report 10 and tracing (both disabled by default).
The local responder options are used to define the functional units and service
classes proposed by the SunLink FTAM responder (osiftr) running on the
local system during this negotiation phase. By default, osiftr proposes all of
the functional units and service classes that it supports. There are also options
to enable Defect Report 10 and tracing (both disabled by default).
64
If the SunLink FTAM responder (osiftr) is running on the remote system,

you should not alter the default configuration for the local initiator.
If there is any other type of FTAM responder running on the remote system,
you may want to modify the default configuration of the local initiator to
match the configuration of the remote responder; however, this is not
strictly necessary and may not be desirable.
FTAM responder will not prevent an association from being established.
Failing to propose a supported functional unit or service class will reduce the
versatility of your file management system, and may reduce the chance that
Supported Service Classes

The FTAM specification defines the permitted service class combinations listed
in Table 6-1.
Table 6-1
Service Class Combinations
Abbreviation
Service Classes
Access only
Transfer only
Management only
A and T
Access and Transfer
T, M, and TM
Transfer, Management, Transfer & Management
A, T, M, and TM
Access, Transfer, Management, Transfer & Management
65
6
Functional Units
The permitted functional units for each of the service class combinations are
listed in Table 6-2:
Table 6-2
Permitted Functional Units
A, T
T, M, TM
A, T, M, TM
Read (U2)
mandatory
U2 or U3
not permitted
mandatory
U2 or U3
mandatory
Write (U3)
mandatory
U2 or U3
not permitted
mandatory
U2 or U3
mandatory
File Access (U4)
mandatory
not permitted
not permitted
mandatory
optional
mandatory
Limited File Management (U5)
optional
optional
mandatory
optional
mandatory
mandatory
Enhanced File Management (U6)
optional
optional
optional
optional
optional
optional
Grouping (U7)
optional
mandatory
mandatory
mandatory
mandatory
mandatory
Recovery (U9)
optional
optional
not permitted
optional
optional
optional
New OID for NBS-9

You only require this Object Identifier type if you are interoperating with
another vendors product, that implements the version of this parameter
defined in the published version of the ISO FTAM Specification (8571), rather
than the version given in the preliminary draft. If you do require this option,
you must also use version 8.0.2 or later of the SunLink OSI Communications
Platform (Stack).
Note You only need to set this parameter for the local Initiator. The local
Responder is automatically able to use this Object Identifier type, if it is
requested by the remote Responder.
DR10
DR10, an addendum to ISO 8571, modifies the sequence of primitives returned
on group error, and the associated diagnostics. Instead of generating a message
for each primitive, a system using DR10 generates a single, group error
message. A group as a whole will only fail if a primitive within the group that
presents a state result parameter fails.
66
6
If you are interoperating with a version of FTAM that uses DR10, enable DR10
here to avoid interoperability problems. Otherwise, leave DR10 disabled.
Traces
Enables the logging of traces to the directory
/var/SUNWconn/OSIROOT/ftam/log.
67
68
Error Messages and Codes
Primary Error Messages
page 70
Local Error Codes
page 75
Diagnostic Error Codes
page 76
An osiftam error report consists of up to three parts:
The primary error message provides a summary of the error, indicating the
event that triggered the report.
The secondary error message provides additional information concerning

the error.
If recovery is enabled, the recovery message provides an indication of the

status of the recovery mechanism and the connection. The error may be
either recoverable or unrecoverable; the connection may be either ON
or OFF.
For example,
Error reading remote file attributes, FTAM diagnostic = 3004
3004: Non-existent file
[Unrecoverable error, Connection on]
69
7
The primary error message indicates that the error occurred when an attempt
was made to read the attributes of the remote file, and the secondary error
message provides the reason for the error condition. In this case, error recovery
was enabled; however, the recovery message indicates that no recovery was
possible from this error.
Primary Error Messages

Note Where you are referred to the secondary error message in the following
pages, this is due to the fact that the cause of the error may be related to the
configuration of the remote FTAM implementation, information provided by
the secondary error message.
Command not supported
The command is not supported. Check the product release information for
possible help.
Correct syntax: -d [f1|f2|f3|n9|i1]
The -d <document_type> parameter of the command was improperly
specified.
Document type required
The -d <document_type> switch is required in the command. See the
description of the command in Using SunLink FTAM 8.0.2.
Error closing local file
Check the secondary error message for more information.
Error closing remote file
Error closing remote host
Error connecting to host
Error, connection already established
When using the open command, and a connection is already established.
70
7
Error, connection not established
The connection with the remote host system has to be established before
using any of the close, put, get, recover, dir, read, create, delete,
rename and ratt commands.
Error creating docket
Error creating remote file
Error deleting docket
Error deleting remote file
Error deselecting remote file
Error getting transfer number
Error opening local file
Error opening remote file
Error reading default shadow file
Error reading docket
Error reading file, transfer cancelled
Error reading host information
Error reading local file
71
7
Error reading remote file attributes
Error reading shadow file
Error receiving file, transfer cancelled
Check the secondary error message for more information. This message is
also generated erroneously as the result of a read command, using the te
option to specify the end of file. In this event the error message can be
ignored.
Error recovering transfer
Error renaming remote file
Error selecting remote file
Error writing docket
Error sending file, transfer cancelled
Error writing host information
Error writing local file
Error writing shadow file
Function not available on this host
The use of this function was not negotiated between the local and remote
hosts.
Host is closed
The host has been temporarily disabled by using the rdb close command.
Host name required
The host name is required in the command.
72
7
Incomplete command
A mandatory field is missing in the command you typed.
Inconsistent parameters
Some parameters in the command line are inconsistent.
Incorrect environment variable
Check your environment variables, if customized (FTIINID, FTILOGD,
FTISHFD, FTIRDBD, FTITRFD).
Invalid application entity title
The -a <AET> field of the command was improperly specified.
Invalid document type
The -d <document_type> field of the command was improperly specified.
Valid document types are: F1, F2, F3, N9 and I1.
Invalid Grouping Sequence
Check to see whether either the local or remote system is using DR10. If one
of them is, either disable DR10 on that system, or enable it on the other.
Invalid host name length
The host name is limited to 8 characters.
Invalid network address
The value is too long, or not preceded by C (for character) or H (for
hexadecimal).
Invalid path name
Check the path name in the command.
Invalid presentation selector
hexadecimal).
Invalid string significance
The -t <string_significance> field of the command was improperly
specified.The possible values are f for fixed, v for variable or n for not
significant.
Invalid session selector
hexadecimal).
73
7
Invalid switch -<x>
The specified switch is not valid for the command.
Invalid transport selector
hexadecimal).
Invalid universal class number
The -u <universal_class> field of the command was improperly specified.
Valid universal class numbers are: 19, 20, 21, 22, 25, 26 and 27
Local file name required
The local file name is required in the command.
Network address required
The -n <network_address> is required in the command.
No response from host
The time-out expires while the FTAM Initiator is waiting an answer from the
remote host.
Override options are: o(ld), n(ew) or f(ail)
The -o <override> field of the command was improperly specified.
Permissions are: ripxetcd
The -m <permissions> field of the command was improperly specified.
rdb: commands are add, delete, show, list, open, close
Help message for rdb command.
Remote file name required
The remote file name is required in the command.
String significance required
String significance is mandatory in the command.
Syntax error
Check the syntax of the command line.
Too many positional fields
A field value was typed without the corresponding - <switch>.
Transfer Number required
The transfer number is required in the recover and trf show or delete
commands.
74
7
trf: commands are list, show, delete
Help message for trf command.
Unable to delete host
Unable to list hosts
Unable to open input file
The input file specified in the in command does not exist, or permission to
open is denied.
Unknown host name
The host name does not exist in the Remote Hosts Database.
Local Error Codes

01Illegal document type parameters
02Invalid mode in F-Open-ind
03Subsequent error
04No file name in F-Create-ind
05No file name in F-ChAtt-ind
06No composite attributes in F-Create-ind
07Unknown user in F-Init-ind
08Invalid user identity
09Invalid service class in F-Init-ind
10Invalid password in F-Init-ind
11Invalid Data Element type
12Invalid Universal Class
13Invalid Data Element size
14Time-out
75
7
15Invalid INTAP_1 record length
16Cannot read at end of file
17FADU id. error in F-Read-ind
18Cannot locate FADU
19Cannot truncate file
20File name too long
21Invalid document type
22Invalid overwrite parameter
23No document type in F-Open-cnf
24Unsupported Special local file type
25Invalid FTAM_1 or FTAM_2 string length
26Recovery error - bad checkpoint
27Recovery error - corrupted docket
28Recovery error - no docket
29Recovery error - no recovery point
30Recovery error - content type inconsistent
31Recovery error - unspecified
Diagnostic Error Codes

The following error codes are returned as part of the primary error messages
generated by osiftam.
76
7
General FTAM Diagnostics
Codes 0000 to 0011 are used to return general diagnostic information as
shown in Table 7-1:
Table 7-1
General FTAM Diagnostics
0000
No reason
0001
Responder error (unspecific)
0002
System shutdown
0003
FTAM management problem (unspecific)
0004
FTAM management, bad account
0005
FTAM management, security not passed
0006
Delay may be encountered
0007
Initiator error (unspecific)
0008
Subsequent error
0009
Temporal insufficiency of resources
0010
Access request violates VFS security
0011
Access request violates local security
Protocol and Supporting Service Diagnostics

Codes 1000 to 1017 are used to return diagnostic information regarding
FTAM protocols and services as shown in Table 7-2:
Table 7-2
1000
Conflicting parameter value
1001
Unsupported parameter value
1002
Mandatory parameter not set
1003
Unsupported parameter
1004
Duplicated parameter
1005
Illegal parameter type
1006
Unsupported parameter type
77
7
Table 7-2
1007
FTAM protocol error (unspecific)
1008
FTAM protocol error, procedure error
1009
FTAM protocol error, functional unit error
1010
FTAM protocol error, corruption error
1011
Lower layer failure
1012
Lower layer addressing error
1013
Timeout
1014
System shutdown
1015
Illegal grouping sequence
1016
Grouping threshold violation
1017
Specific PDU request inconsistent with the current requested access
Association-Related Diagnostics
Codes 2000 to 2021 are used to return diagnostic information associations
between the a client and a server as shown in Table 7-3:
Table 7-3
78
2000
Association with user not allowed
2001
(not assigned)
2002
Unsupported service class
2003
Unsupported functional unit
2004
Attribute group error (unspecific)
2005
Attribute group not supported
2006
Attribute group not allowed
2007
Bad account
2008
Association management (unspecific)
2009
Association management, bad address
2010
Association management, bad account
2011
Checkpoint window error, too large
7
Table 7-3
2012
Checkpoint window error, too small
2013
Checkpoint window error, unsupported
2014
Communications QoS nor supported
2015
Initiator identity unacceptable
2016
Context management refused
2017
Rollback not available
2018
Contents type list cut by responder
2019
Contents type list cut by Presentation service
2020
Invalid filestore password
2021
Incompatible service class
Selection Regime-Related Diagnostics

Codes 3000 to 3030 are used to return diagnostic information regarding the
file selection regime as shown in Table 7-4:
Table 7-4
3000
Filename not found
3001
Selection attributes not matched
3002
Initial attributes not possible
3003
Bad attribute name
3004
Non-existent file
3005
File already exists
3006
File cannot be created
3007
File cannot be deleted
3008
Concurrency control not available
3009
Concurrency control not supported
3010
Concurrency control not possible
3011
More restrictive lock
3012
File busy
79
7
Table 7-4
3013
File not available
3014
Access control not available
3015
Access control not supported
3016
Access control inconsistent
3017
Filename truncated
3018
Initial attributes altered
3019
Bad account
3020
Override selected existing file
3021
Override deleted and recreated file with old attributes
3022
Override deleted and recreated file with new attributes
3023
Create override, not possible
3024
Ambiguous file specification
3025
Invalid create password
3026
Invalid delete password on override
3027
Bad attribute value
3028
Requested access violates permitted actions
3029
Functional unit not available for requested access
3030
File created but not selected
File Management-Related Diagnostics

Codes 4000 to 4007 are used to return diagnostic information regarding file
management as shown in Table 7-5:
Table 7-5
80
4000
Attribute non existent
4001
Attribute cannot be read
4002
Attribute cannot be changed
4003
Attribute not supported
4004
Bad attribute name
7
Table 7-5
4005
Bad attribute value
4006
Attribute partially supported
4007
Additional set attribute value not distinct
Access-Related Diagnostics
Codes 5000 to 5041 are used to return diagnostic information regarding file
access as shown in Table 7-6:
Table 7-6
Access Related Diagnostics
5000
Bad FADU (unspecific)
5001
Bad FADU - size error
5002
Bad FADU - type error
5003
Bad FADU - poorly specified
5004
Bad FADU - bad location
5005
FADU does not exist
5006
FADU not available (unspecific)
5007
FADU not available for reading
5008
FADU not available for writing
5009
FADU not available for location
5010
FADU not available for erasure
5011
FADU cannot be inserted
5012
FADU cannot be replaced
5013
FADU cannot be located
5014
Bad data element type
5015
Operation not available
5016
Operation not supported
5017
Operation inconsistent
5018
Concurrency control not available
5019
Concurrency control not supported
81
7
Table 7-6
Access Related Diagnostics
5020
Concurrency control inconsistent
5021
Processing mode not available
5022
Processing mode not supported
5023
Processing mode inconsistent
5024
Access context not available
5025
Access context not supported
5026
Bad write (unspecific)
5027
Bad read (unspecific)
5028
Local failure (unspecific)
5029
Local failure - filespace exhausted
5030
Local failure - data corrupted
5031
Local failure - device failure
5032
Future file size exceeded
5034
Future file size increased
5035
Functional unit invalid in processing mode
5036
Contents type inconsistent
5037
Contents type simplified
5038
Duplicate FADU name
5039
Damage to select/open regime
5040
FADU locking not available on file
5041
FADU locked by another user
Recovery-Related Diagnostics
Codes 6000 to 6017 are used to return diagnostic information regarding the
82
7
recovery of interrupted files as shown in Table 7-7
Table 7-7
Recovery-Related Diagnostics
6000
Bad checkpoint (unspecific)
6001
Activity not unique
6002
Checkpoint outside window
6003
Activity no longer exists
6004
Activity not recognized
6005
No docket
6006
Corrupt docket
6007
File waiting restart
6008
Bad recovery point
6009
Non-existent recovery point
6010
Recovery mode not available
6011
Recovery mode inconsistent
6012
Recovery mode reduced
6013
Access control not available
6014
Access control not supported
6015
Access control inconsistent
6016
Contents type inconsistent
6017
Contents type simplified
83
84
FTAM Trace Files
Trace Format
page 86
Trace Example
page 88
Traces are logging files generated automatically by the local SunLink FTAM
responder and initiator. Set the Trace option using ftamtool, see Configuring
the Local Initiator on page 34 and Configuring the Local Responder on
page 38.
By default, these files are created into the directory
/var/SUNWconn/OSIROOT/ftam/log. You can change this default changing
the environment variable FTILOGD. Do this before starting osiftam.
You can generate traces for any local initiator (osiftam) or local responder
(osiftr) process. Trace files for the local initiator are called ftiPID.log, and
for the local responder ftrPID.log (where PID stands for the Process ID of
the currently traced initiator or responder).
Note The size of these files may reach several megabytes. You should ensure
that you reserve sufficient disk space. Trace files are not removed
automatically.
85
8
Note When traces are activated, the time that FTAM takes to perform each
operation increases significantly. In particular, there will be a delay if you
cancel a file transfer in progress by typing CTRL-C.
Trace Format
FTAM traces protocol data units (PDUs) and File Contents Data Elements,
represented by the abstract syntax notation (ASN.1) defined by ISO 8824.
The trace file always begins with the inclusion of the configuration file
(fti.init or ftr.init) which has been used at start-up of the local initiator
or local responder. For the local initiator (osiftam), the osiftam commands
executed are also shown.
The first column gives a time-stamp with hours, minutes and seconds. The
following number (which appears between square brackets) is used internally
to identify the entity which generates the PDU.
Dashed lines are used to separate each PDU and File Contents Data Element.
The main elements used to trace an FTAM PDU are described below:
All traced bytes are expressed in hexadecimal notation
The length field (Length=) indicates the decoded length for the element
being analyzed, as taken from TLV. This may be different from the length
represented between brackets since the latter indicates the number of bytes
globally received not yet decoded.
For each PDU field, the name of each service element is printed (for
example, Protocol Version in Figure 8-1 on page 87), as well as the
ASCII value of fields (for example, (c) SunMicrosystems;Rel8.0 which
is the value of the service element Implementation Information), and
the name of flags enabled in bitstrings (for example, 0780 -> Version-1,
which is the value of the service element Protocol Version).
ASN.1 tags are represented (inside square brackets) by the following

notation: * for a constructor type, and APPL for an APPLICATION tag.
An example of a first line from an F-INITIALIZE-Request PDU is shown in

Figure 8-1 on page 87:
86
8
a0 73 F-INITIALIZE-Req *[0] Length=115 (115)
Tag and length

in bytes
PDUs name
(Textual description)
Tag
yet to decode
PDUs length
(Decoded length)
Number of bytes
80 02 Protocol Version [0] Length=2 (115)

07 80
-- -Version-1
Service Element Name
Name of enabled flags for bitstring service element
81 1e Implementation Information [1] Length=30 (111)

2863292053756e204d6963726f73797374656d73203b205265
6c2038
( c ) S u n M i c r o s y s t e m s ; R e l 8 . 0
ASCII value of the Implementation Information service element
Figure 8-1
PDU Representation in a Trace File
FTAM Trace Files
87
8
File Contents Data Elements are represented as shown in Figure 8-2 on page 88.
This example shows the first line from a representation of a data element from
an FTAM-3 unstructured binary document.
04 82 04 00 [OctectString] Length=115 (115)
Tag and length

in bytes
Number of bytes
yet to decode
Data type
File DEs length

(decoded length)
313132333435363738392d2d
0 1 2 3 45 6 78 9 - -
Figure 8-2
Hexadecimal
ASCII
Data Element Representation in a Trace File
Note The line labelled hexadecimal in Figure 8-2 is a hexadecimal

representation of bytes; the next line gives the ASCII equivalent, where
possible. Where a byte is not representable as an ASCII character, the dash

character (-) is used.
Trace Example
A sample fragment from an initiator trace file is shown on the following pages:
09:11:54[8002]
;--------------------------------------------------------;
88
FTAM Initiator Configuration File : fti.init
8
;
;
;
;--------------------------------------------------------;
; --- FTAM configuration :
; --- NOTE: DEFAULT configuration is
; --- SUPPORTED SERVICE CLASSES -> Transfer, Management,
; ---
Transfer&management and Access
; --- FUNCTIONAL UNITS -> Read, Write, File Access, Limited File
Mng.,
; ---
Enhanced File Mng., Grouping, Recovery
; --- Disable RECOVERY F.U. (comment out next line if RECOVERY not
wanted)
;var ent 62 flag 1 1 off
;
trf list
rdb add looplan -n H4955424cd401 -p Cftr -s Cprs -t Cses -a O1-39999-1-7-I1 -z 1
open looplan -n fred -p freds_passwd -a
09:12:04[9900] -------------------------------------------09:12:04[9900] a0 75 F-INITIALIZE-Req *[0] Length=117 (117)
09:12:04[9900] 80 02 Protocol Version [0] Length=2 (115)
09:12:04[9900] 0780
09:12:04[9900] _ _
09:12:04[9900] Version-1
09:12:04[9900] 81 1e Implementation Information [1] Length=30 (111)
09:12:04[9900]
2863292053756e204d6963726f73797374656d73203b2052656c2038
09:12:04[9900] ( c ) S u n M i c r o s y s t e m s ; R e l 8
09:12:04[9900] 2e30
09:12:04[9900] . 0
09:12:04[9900] 83 02 Service Class [3] Length=2 (79)
09:12:04[9900] 0378
09:12:04[9900] _ x
FTAM Trace Files
89
8
09:12:04[9900] Management
09:12:04[9900] Transfer
09:12:04[9900] Transfer and Management
09:12:04[9900] Access
09:12:04[9900] 84 03 Functional Units [4] Length=3 (75)
09:12:04[9900] 053f40
09:12:04[9900] _ ? @
09:12:05[9900] Read
09:12:05[9900] Write
09:12:05[9900] File Access
09:12:05[9900] Limited File Management
09:12:05[9900] Enhanced File Management
09:12:05[9900] Grouping
09:12:05[9900] Recovery
09:12:05[9900] 85 02 Attribute Groups [5] Length=2 (70)
09:12:05[9900] 0580
09:12:05[9900] _ _
09:12:05[9900] Storage
09:12:05[9900] 86 01 FTAM QOS [6] Length=1 (66)
09:12:05[9900] 03
09:12:05[9900] _
09:12:05[9900] Class-3-recovery
09:12:05[9900] a7 25 Contents Type List *[7] Length=37 (63)
09:12:05[9900] 4e 05 Document Type [APPL 14] Length=5 (35)
09:12:05[9900] 28c27b0501
09:12:05[9900] 1.0.8571.5.1 ISO FTAM unstructured-text
09:12:05[9900] 28c27b0503
09:12:05[9900] 1.0.8571.5.3 ISO FTAM unstructured-binary
09:12:06[9900] 28c27b0502
09:12:06[9900] 1.0.8571.5.2 ISO FTAM sequential-text
09:12:06[9900] 2bce06010205
90
8
09:12:06[9900] 1.3.9990.1.2.5 INTAP intap-record-file
09:12:06[9900] 2bce0f010509
09:12:06[9900] 1.3.9999.1.5.9 NBS-9 FTAM file-directory
09:12:06[9900] 56 07 Initiator Identity [APPL 22] Length=7 (24)
09:12:06[9900] 6c61676f737469
09:12:06[9900] l a g o s t i
09:12:06[9900] 71 0c *[APPL 17] Length=12 (15)
09:12:06[9900] 19 0a [GraphicString] Length=6 (6)
09:12:06[9900] 736663726674
09:12:06[9900] s e c r e t
09:12:06[9900] 88 01 Checkpoint Window [8] Length=1 (1)
09:12:06[9900] 0f
09:12:06[9900] _
09:12:06[9900] -------------------------------------------09:12:11[9900] -------------------------------------------09:12:11[9900] a1 64 F-INITIALIZE-Res *[1] Length=100 (100)
...
...
...
...
09:15:01[9900] -------------------------------------------09:15:01[9900] b7 00 F-BEGIN-GROUP-Res *[23] Length=0 (30)
09:15:01[9900] -------------------------------------------09:15:01[9900] -------------------------------------------09:15:01[9900] a7 15 F-SELECT-Res *[7] Length=21 (28)
09:15:01[9900] 55 01 State Result [APPL 21] Length=1 (19)
09:15:01[9900] 00
09:15:02[9900] _
09:15:02[9900] Success
09:15:02[9900] 45 01 Action Result [APPL 5] Length=1 (16)
09:15:02[9900] 00
09:15:02[9900] _
09:15:02[9900] Success
FTAM Trace Files
91
8
09:15:02[9900] 73 0d Selected Attributes *[APPL 19] Length=13 (13)
09:15:02[9900] a0 0b File Name *[0] Length=11 (11)
09:15:02[9900] 19 09 [GraphicString] Length=9 (9)
09:15:02[9900] 2f746d702f74657374
09:15:02[9900] / t m p / t e s t
09:15:02[9900] -------------------------------------------09:15:02[9900] -------------------------------------------09:15:02[9900] ad 03 F-DELETE-Res *[13] Length=3 (5)
09:15:02[9900] 45 01 Action Result [APPL 5] Length=1 (1)
09:15:02[9900] 00
09:15:02[9900] _
09:15:02[9900] Success
09:15:02[9900] -------------------------------------------09:15:02[9900] -------------------------------------------09:15:02[9900] b9 00 F-END-GROUP-Res *[25] Length=0 (0)
09:15:02[9900] -------------------------------------------close
09:26:31[9900] -------------------------------------------09:26:31[9900] a2 00 F-TERMINATE-Req *[2] Length=0 (0)
09:26:31[9900] -------------------------------------------09:26:32[9900] -------------------------------------------09:26:32[9900] a3 00 F-TERMINATE-Res *[3] Length=0 (0)
09:26:32[9900] -------------------------------------------rdb delete looplan
bye
92
SunLink FTAM Command

Summary
The table below summarizes the commands available to users using SunLink
FTAM. For further information on these commands, see Using SunLink FTAM
8.0.2. For a description of the commands that let you add entries to the RSDB,
without using ftamtool, see Appendix B, Configuring the RSDB without
ftamtool.
Command
Description
bye
closes the association and stops the osiftam process
close
closes the association
create
creates a file on a remote system
delete
deletes a file on a remote system
dir
lists the contents of the remote directory
get
gets a file from the remote system (from remote to local)
in
input commands
lcd
changes the local working directory
open
opens an association with a remote system
put
puts a file on the remote machine (from local to remote)
pwd
returns the path to the remote directory
quit
closes the association and stops the osiftam process
ratt
reads the attributes of a remote file
rcd
changes the remote working directory
read
reads a portion of an FTAM-2 file from a remote machine
recover
resumes an interrupted file transfer
rename
renames a file on a remote machine
93
94
Command
Description
shf
displays, creates, or modifies a shadow file template
trf delete
deletes recovery information for an interrupted file transfer
trf list
lists the transfer identifiers for all interrupted file transfers
trf show
displays the recovery information
executes a UNIX shell command
Configuring the RSDB without

ftamtool
rdb addadd remote system
page 95
rdb changechange remote system
page 97
rdb closeclose remote system
page 98
rdb deletedelete remote system
page 98
rdb listlist remote system database
page 98
rdb openopen remote system
page 98
rdb showshow remote host address
page 98
The commands described in this appendix configure the Remote System

Database (RSDB), without using ftamtool. Only use these commands if you
cannot use ftamtoolfor example, if you do not have access to OPEN LOOK.
Note If you make changes to the RSDB using the commands in this section,
the ftamtool display does not change to reflect them until the next time you
restart it.
rdb addadd remote system

The rdb add command creates an entry in the remote systems database.
95
B
The remote systems database specifies the OSI addresses for the remote
systems recognized by osiftam. The address information entered must apply
to a remote host which is reachable across the OSI network.
Unlike ftamtool, rdb add cannot make use of templates. You must therefore
enter complete addressing information. You can, however, display the
templates, to make sure you are entering addresses in the correct format, using
rdb show, followed by the template name.
Enter the command, followed by a hostname, followed by the addressing
information. A complete entry looks like this:
osiftam> rdb add entry1 -n H49<hostid>01 -p Cftr -s Cprs -t Cses -a O1-3-9999-1-7-I1 -z 1
When you press return, the system displays the new entry:
entry1
title
p_sel
s_sel
t_sel
n_add
sbnet
state
=
=
=
=
=
=
=
4f312d332d393939392d312d372d4931 [O1-3-9999-1-7-I1]
667472 [ftr]
707237 [prs]
736573 [ses]
4955421b8d01 [IUB...]
1
open
The variables are:

n <net_addr>Network address. Specified as H<hex_string> or C<char_string>
p <psel>Presentation selector for the FTAM responder on the remote system.
Specified as H<hex_string> or C<char_string>. Enter a hash character (#) for a
null value.
s <ssel>Session selector for the FTAM responder on the remote system.
null value.
t <tsel>Transport selector for the FTAM responder on the remote system.
null value.
96
B
a <aet>Application Entity Title (AET) for the FTAM responder on the remote
system. The AET is made up of two partsthe Application Process Title (APT)
and the Application Entity Qualifier (AEQ). These two parts are encoded as
ASN.1 objects. The components of the AET and the AEQ are separated by
dashes.
APT=O<ascii string> (this is the letter O not the numeral 0)
AEQ=I<ascii_string>
If the remote device is using the SunLink FTAM responder, you do not need to
specify the AET.
z <subnet>Specifies the type of subnetwork that is used to reach the remote
system.
0: CONS subnetwork (for example, X.25)
1: CNLP subnetwork (for example, ethernet, FDDI)
2: RFC1006 (TCP/IP)
rdb changechange remote system

The rdb change command modifies an entry in the RSDB.
The remote systems database specifies the OSI addresses for the remote
systems recognized by osiftam. The address information entered must
correspond to that of a remote host which is reachable across the OSI network.
The parameters and variables are the same as those explained in rdb
addadd remote system on page 95. To correct a single error, just re-enter the
variable affected, you do not need to re-type the entire entry.
For example, to correct the PSEL, you would enter:
osiftam> rdb change entry1 -p Cftr
All other parameters are unchanged. When you press return, the system
displays the complete entry.
Configuring the RSDB without ftamtool
97
B
rdb closeclose remote system
The command rdb close temporarily disables an association to a host. The
host is inaccessible until it is re-opened using the rdb open command.
osiftam> rdb close <host>
rdb deletedelete remote system

The command rdb delete removes a host from the RSDB.
osiftam> rdb delete <host>
rdb listlist remote system database

The command rdb list displays the names of all the hosts specified in the
remote hosts database.
osiftam> rdb list
rdb openopen remote system

The command rdb open reopens a host previously closed using the rdb
close command.
osiftam> rdb open <host>
rdb showshow remote host address

The command rdb show displays the specified host entry.
osiftam> rdb show <host>
98
B
For example:
entry1
title
p_sel
s_sel
t_sel
n_add
sbnet
state
=
=
=
=
=
=
=
4f312d332d393939392d312d372d4931 [O1-3-9999-1-7-I1]
667472 [ftr]
707237 [prs]
736573 [ses]
4955421b8d01 [IUB...]
1
open
The parameters are explained in rdb addadd remote system on page 95.
Configuring the RSDB without ftamtool
99
100
Index
A
access
permissions, 7
restriction, 5, 7, 11, 45
addresses, 22, 25, 30, 61, 97
application
entity title (AET), 25, 30, 97
ASCII format, 26
association, 2, 6, 10, 34, 65
request, 2
attributes, 5, 7, 8, 9
authorized users, 43
B
backup, 36, 37, 41
C
character format, 26, 63
class number, 7
client-server model, 2
CLNP, 61, 63
close command, 3
commands, 3
communicating systems, 2, 5
concepts, 4
concurrent associations, 3
configuration files, 12
connection, 2, 63
CONS, 62, 63
content type, 7
customizing file attributes, 10
D
default values, 9, 34, 39, 61, 64
defect reporting, 12
delete
remote system, 98
system, 30
dockets, 11, 13
document types, 5, 7, 9, 10
dot notation, 27, 64
DR10, 12
option, 36, 40
dynamic files, 12
E
end of file, 10
environment variables, 12
errors, 10
ethernet, 24, 26, 61, 63
101
F
FDDI, 24, 26, 61, 63
file
attributes, 5, 7, 8, 9
classes, 12
descriptions, 5
dynamic, 12
entity, 8
permissions, 7
RSDB, 13
services, 4
shadow, 7, 8, 13
systems, 4, 11, 45
trace, 13
transfer, 10
ftamtool, 12
fti.init, 12, 36, 37
FTIINID, 12
FTILOGD, 13
FTIRDBD, 13
FTISHFD, 13
FTITRFD, 13
ftp, 2
ftr.init, 12, 41
functional units, 6, 34, 38, 64
K
kernel group, 5
L
LAN, 26
LLC1, 26
local
definitions, 36, 40
login procedure, 11, 45
M
mandatory parameters, 66
mapping file characteristics, 4
negotiation, 34, 65
network
address, 63
identifier, 44, 45
type, 29
new entry, 29
NIST, 5
NSAP, 26, 27, 63
get command, 8
goto button, 23
H
hexadecimal format, 26, 63
I
initiator, 2, 3, 12, 22, 34, 38, 61, 64
osiftam, 33
INTAP, 5
interrupted transfers, 10, 13
IP address, 27, 64
ISO, 5
102
8571, 6
OSI addresses, 22, 25, 30, 61, 97

osiftam, 2, 3, 12, 22, 34, 38, 61, 64
commands, 3
osiftr, 2, 12, 38, 43, 62, 64
osiftrd, 2, 3, 11, 25, 43, 62
osiftrd_start, 44
osiftrd_stop, 45
ositool, 27, 63
overview, 1, 19
P
passwords, 11
permitted
functional units, 66
service classes, 65
physical connection, 63
presentation selector, 96
print
initiator configuration, 37
responder configuration, 41
RSDB, 31
protocols, 2, 4, 6, 7, 26, 27, 65
R
ratt command, 8
rdb add command, 95
rdb change command, 97
rdb close command, 98
rdb delete command, 98
rdb list command, 98
rdb open command, 98
rdb show command, 98
read attributes, 8
recoverable errors, 10
recovery, 10, 11, 13
remote
system, 26
remote systems database (RSDB), 13, 19,
22, 61, 95
templates, 23, 61
reporting
defects, 12
responder, 2, 12, 38, 43, 64
daemon (osiftrd), 2, 3, 11, 25, 43, 62
process, 62
RFC 1006, 24, 27, 61
service classes, 6, 34, 36, 38, 64

session selector, 63, 96
shadow files, 7, 8, 13
templates, 9
shf command, 10
significance, 8
special files, 7, 11, 13
specification, 2, 65
stack, 26, 27
starting ftamtool
locally, 20
startup script, 44
storage group, 5
string
length, 8
significance, 8
subnetwork
types, 43, 97
subnetwork types, 2
summary, 1, 19
supported
subnetworks, 2, 29
synchronization, 11
system, 2
name, 24, 30
status, 33
T
TCP/IP, 24, 27, 61, 63
templates, 9
terminology, 4
trace
files, 13, 85
option, 36, 40
transport selector, 63, 96
S
selectors
presentation, 96
session, 63, 96
transport, 63, 96
server process, 2
Index
U
universal class number, 7
UNIX
commands, 2, 8
file system, 7
103
unrecoverable errors, 10
user name, 11, 45
V
variables, 12
virtual file store, 4
W
WAN, 24, 27
X
X.25, 24, 27, 62, 64
104

SunLink FTAM

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

SunLink FTAM

Încărcat de

Drepturi de autor:

Formate disponibile

Managing SunLink FTAM 8.0.

A Sun Microsystems, Inc. Business

2550 Garcia Avenue

1994 Sun Microsystems, Inc.

SunLink FTAMArchitecture Overview . . . . . . . . . . . . . . . . . .

SunLink FTAMConcepts and Terminology . . . . . . . . . . . . . .

Virtual File Store . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Functional Units and Service Classes . . . . . . . . . . . . . . . . . .

Shadow File Templates . . . . . . . . . . . . . . . . . . . . . . . . .

SunLink FTAMDirectories and Files . . . . . . . . . . . . . . . . . . . .

2. Planning your SunLink FTAM Configuration . . . . . . . . . . . . .

Exchanging Files between Remote Systems . . . . . . . . . . . . .

Sharing a Local File Server . . . . . . . . . . . . . . . . . . . . . . . . . . .

Interoperating with Other Implementations of FTAM . . . . . . .

3. Configuring SunLink FTAM . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Staring ftamtool Locally . . . . . . . . . . . . . . . . . . . . . . . . . . .

Starting ftamtool Remotely. . . . . . . . . . . . . . . . . . . . . . . . .

Creating a Remote Systems Database (RSDB) . . . . . . . . . . . . . .

Adding an Entry to the RSDB . . . . . . . . . . . . . . . . . . . . . . . .

Modifying an Existing Template . . . . . . . . . . . . . . . . .

Adding a Completely New Entry . . . . . . . . . . . . . . . .

Deleting an Entry from the RSDB . . . . . . . . . . . . . . . . . . . . .

Printing the RSDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Closing and Opening Systems . . . . . . . . . . . . . . . . . . . . . . . .

Configuring the Local Initiator . . . . . . . . . . . . . . . . . . . . . . . . . .

Modifying the Default Initiator Configuration . . . . . . . . . .

Saving the Initiator Configuration. . . . . . . . . . . . . . . . . . . . .

Printing the Initiator Configuration . . . . . . . . . . . . . . . . . . .

Configuring the Local Responder . . . . . . . . . . . . . . . . . . . . . . . .

Modifying the Default Responder Configuration . . . . . . . .

Saving the Responder Configuration . . . . . . . . . . . . . . . . . .

Managing SunLink FTAM 8.0.2October 1994

Printing the Responder Configuration . . . . . . . . . . . . . . . . .

4. Using the FTAM Responder (osiftr) . . . . . . . . . . . . . . . . . . .

Starting and Stopping the FTAM Responder Daemon . . . . . . .

Starting Responder Daemon Automatically . . . . . . . . . . . .

Starting the Responder Daemon Manually . . . . . . . . . . . . .

Stopping the Responder Daemon Manually . . . . . . . . . . . .

Restricting Remote Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Problems Opening a Connection . . . . . . . . . . . . . . . . . . . . . . . . .

SunLink FTAM initiator and non-Sun Responder. . . . . . . .

Non-Sun Initiator and SunLink FTAM Responder . . . . . . .

Problems with Licensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Problems Starting the License Installation Tool . . . . . . . . . .

Unable to Change License Server(s) . . . . . . . . . . . . . . . . . . .

Mistyped License Information . . . . . . . . . . . . . . . . . . . . . . . .

Errors Executing the License Configuration Script . . . . . . .

Removing the License System . . . . . . . . . . . . . . . . . . . . . . . .

Recovering a Lost License . . . . . . . . . . . . . . . . . . . . . . . . . . .

Unlocking a Stopped License System . . . . . . . . . . . . . . . . . .

SunLink OSI Specific Errors . . . . . . . . . . . . . . . . . . . . . . . . .

SunLink FTAM Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Remote Systems Database Parameters . . . . . . . . . . . . . . . . . . . .

Current System Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Application Process Title . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Application Process Qualifier . . . . . . . . . . . . . . . . . . . . . . . .

Presentation Selector (PSEL) . . . . . . . . . . . . . . . . . . . . . . . . .

Session Selector (SSEL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Transport Selector (TSEL) . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Local Initiator and Responder Parameters . . . . . . . . . . . . . . . . .

Supported Service Classes . . . . . . . . . . . . . . . . . . . . . . . . . . .

New OID for NBS-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7. Error Messages and Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Primary Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .