SunLink FTAM
SunLink FTAM
SunLink FTAM
Please
Recycle
Contents
Part 1 Setting up and Maintaining SunLink FTAM
1. Introducing SunLink FTAM . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FTAM Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Document Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
File Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Shadow Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10
Access Restriction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11
DR10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12
12
iii
iv
15
Example Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15
15
16
17
19
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19
Starting ftamtool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
20
20
21
22
23
23
28
30
31
33
34
34
36
37
38
39
40
41
43
43
44
44
45
46
5. Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
47
48
Interoperability Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
50
50
52
52
52
53
53
53
54
55
56
56
Part 2 Reference
6.
61
61
Contents
vi
RSDB Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
61
62
62
62
62
63
63
Network Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
63
Network Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
64
System Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
64
64
65
Functional Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
66
66
DR10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
66
Traces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
67
69
70
75
76
77
77
Association-Related Diagnostics . . . . . . . . . . . . . . . . . . . . . .
78
79
80
Access-Related Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . .
81
Recovery-Related Diagnostics . . . . . . . . . . . . . . . . . . . . . . . .
82
85
Trace Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
86
Trace Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
88
93
95
95
97
98
98
98
98
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.
ix
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:
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
FTAM Specifications
page 1
page 2
page 4
page 12
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:
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
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.
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
Document Type
Description
FTAM-1
Unstructured text
FTAM-2
Sequential text
FTAM-3
Unstructured binary
NBS-9
File directory
INTAP-1
INTAP records
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.
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
Code
Functional Unit
U1
Kernel
U2
Read
U3
Write
U4
U5
U6
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
Code
Service Class
Transfer class
Access class
Management class
TM
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
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
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
/var/SUNWconn/OSIROOT/ftam/shf/ftam2.shf
/var/SUNWconn/OSIROOT/ftam/shf/ftam3.shf
/var/SUNWconn/OSIROOT/ftam/shf/intap1.shf
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
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.
12
13
14
Example Configurations
page 15
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.
15
UNIX
system
Non-UNIX
system
gateway
Figure 2-1
X.25 WAN
(CLNP)
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.
16
server
Figure 2-2
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.
17
18
Starting ftamtool
page 20
page 22
page 34
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.
20
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.
Click SELECT to
choose a system
Type name of
existing system
23
3
2. Click SELECT on the name of the appropriate RSDB template.
Choose between:
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.
Click SELECT to
change the AEQ
25
If osiftrd is running on the remote system, then you need only modify the
Network Address element.
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 address of the form:
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).
Add an entry in the RSDB for every remote system that you want to be able to
access using the SunLink FTAM initiator.
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.
29
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:
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.
Press MENU
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
Application Process Title: 1 3 9999 1 7
Application Entity Qualifier: 1
PSEL: ftr
SSEL: prs
TSEL: Empty
Network Address: 1.2.3.4
Network Type: TCP-IP
System Status: Open
----- SUN_x25.rdb
Application Process Title: 1 3 9999 1 7
Application Entity Qualifier: 1
PSEL: ftr
SSEL: prs
TSEL: ses
Network Address: x25_address
Network Type: CONS
System Status: Open
----- rasputin.rdb
Application Process Title: 1 3 9999 1 7
Application Entity Qualifier: 1
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:
1. Click SELECT on the RSDB icon to activate the RSDB configuration
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:
1. Click SELECT on the RSDB icon to activate the RSDB configuration
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.
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 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.
34
3. Click SELECT on the checkboxes to disable the functional units that you
do not want the initiator to propose when negotiating an association.
4. Click SELECT on the Configurable Document types you do not want the
initiator to propose when negotiating an association.
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
36
3
To save a copy of the initiator configuration in a different file:
1. Click SELECT on the Local Initiator icon to activate the Local Initiator
configuration window.
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.
Press MENU
37
3
4. Click SELECT on Print to send the file to the specified printer (or file).
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
38
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.
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.
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
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.
40
3
1. Click SELECT on the Local Responder icon to activate the Local
Responder configuration window.
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.
Press MENU
41
3
4. Click SELECT on Print to send the file to the specified printer (or file).
The local responder configuration looks like this:
OSI 8.0.1 FTAM Local Responder 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
42
page 43
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.
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)
44
Subnetwork Types
Network_I
d
Subnetwork Type
cons
clnp
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>
Subnetwork Types
Network_I
d
Subnetwork Type
cons
clnp
tcp
RFC1006 (TCP/IP)
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>
46
Troubleshooting
page 48
Interoperability Problems
page 50
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.
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
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.
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.
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.
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.
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.
Troubleshooting
53
5
**Some duplicate licenses were detected during installation**
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.
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
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)
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
58
Part 2 Reference
page 61
page 64
This chapter summarizes the parameters you may need to set when
configuring SunLink FTAM.
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:
61
SUN_x25 is a template entry for systems that can be reached across a CONS
connection (for example, X.25).
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).
If both remote and local systems are running SunLink FTAM, you do not need
to change the default value.
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.
64
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.
Note Proposing a functional unit or service class that is not supported by the
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
association negotiation will be concluded successfully.
Abbreviation
Service Classes
Access only
Transfer only
Management only
A and T
T, M, and TM
A, T, M, and TM
65
6
Functional Units
The permitted functional units for each of the service class combinations are
listed in Table 6-2:
Table 6-2
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
mandatory
not permitted
not permitted
mandatory
optional
mandatory
optional
optional
mandatory
optional
mandatory
mandatory
optional
optional
optional
optional
optional
optional
Grouping (U7)
optional
mandatory
mandatory
mandatory
mandatory
mandatory
Recovery (U9)
optional
optional
not permitted
optional
optional
optional
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
page 70
page 75
page 76
The primary error message provides a summary of the error, indicating the
event that triggered the report.
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.
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
Check the secondary error message for more information.
Error creating remote file
Check the secondary error message for more information.
Error deleting docket
Check the secondary error message for more information.
Error deleting remote file
Check the secondary error message for more information.
Error deselecting remote file
Check the secondary error message for more information.
Error getting transfer number
Check the secondary error message for more information.
Error opening local file
Check the secondary error message for more information.
Error opening remote file
Check the secondary error message for more information.
Error reading default shadow file
Check the secondary error message for more information.
Error reading docket
Check the secondary error message for more information.
Error reading file, transfer cancelled
Check the secondary error message for more information.
Error reading host information
Check the secondary error message for more information.
Error reading local file
Check the secondary error message for more information.
71
7
Error reading remote file attributes
Check the secondary error message for more information.
Error reading shadow file
Check the secondary error message for more information.
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
Check the secondary error message for more information.
Error renaming remote file
Check the secondary error message for more information.
Error selecting remote file
Check the secondary error message for more information.
Error writing docket
Check the secondary error message for more information.
Error sending file, transfer cancelled
Check the secondary error message for more information.
Error writing host information
Check the secondary error message for more information.
Error writing local file
Check the secondary error message for more information.
Error writing shadow file
Check the secondary error message for more information.
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
The value is too long, or not preceded by C (for character) or H (for
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
The value is too long, or not preceded by C (for character) or H (for
hexadecimal).
73
7
Invalid switch -<x>
The specified switch is not valid for the command.
Invalid transport selector
The value is too long, or not preceded by C (for character) or H (for
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
Check the secondary error message for more information.
Unable to list hosts
Check the secondary error message for more information.
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.
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
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
0000
No reason
0001
0002
System shutdown
0003
0004
0005
0006
0007
0008
Subsequent error
0009
0010
0011
1000
1001
1002
1003
Unsupported parameter
1004
Duplicated parameter
1005
1006
77
7
Table 7-2
1007
1008
1009
1010
1011
1012
1013
Timeout
1014
System shutdown
1015
1016
1017
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
Association-Related Diagnostics
2000
2001
(not assigned)
2002
2003
2004
2005
2006
2007
Bad account
2008
2009
2010
2011
7
Table 7-3
Association-Related Diagnostics
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
3000
3001
3002
3003
3004
Non-existent file
3005
3006
3007
3008
3009
3010
3011
3012
File busy
79
7
Table 7-4
3013
3014
3015
3016
3017
Filename truncated
3018
3019
Bad account
3020
3021
3022
3023
3024
3025
3026
3027
3028
3029
3030
80
4000
4001
4002
4003
4004
7
Table 7-5
4005
4006
4007
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
5000
5001
5002
5003
5004
5005
5006
5007
5008
5009
5010
5011
5012
5013
5014
5015
5016
5017
Operation inconsistent
5018
5019
81
7
Table 7-6
5020
5021
5022
5023
5024
5025
5026
5027
5028
5029
5030
5031
5032
5034
5035
5036
5037
5038
5039
5040
5041
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
6001
6002
6003
6004
6005
No docket
6006
Corrupt docket
6007
6008
6009
6010
6011
6012
6013
6014
6015
6016
6017
83
84
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:
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).
86
8
a0 73 F-INITIALIZE-Req *[0] Length=115 (115)
Tag
yet to decode
PDUs length
(Decoded length)
Number of bytes
Figure 8-1
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.
Data type
313132333435363738392d2d
0 1 2 3 45 6 78 9 - -
Figure 8-2
Hexadecimal
ASCII
Trace Example
A sample fragment from an initiator trace file is shown on the following pages:
09:11:54[8002]
;--------------------------------------------------------;
88
8
;
;
;
;--------------------------------------------------------;
; --- FTAM configuration :
; --- NOTE: DEFAULT configuration is
; --- SUPPORTED SERVICE CLASSES -> Transfer, Management,
; ---
; --- FUNCTIONAL UNITS -> Read, Write, File Access, Limited File
Mng.,
; ---
; --- 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
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] 4e 05 Document Type [APPL 14] Length=5 (28)
09:12:05[9900] 28c27b0503
09:12:05[9900] 1.0.8571.5.3 ISO FTAM unstructured-binary
09:12:05[9900] 4e 05 Document Type [APPL 14] Length=5 (21)
09:12:06[9900] 28c27b0502
09:12:06[9900] 1.0.8571.5.2 ISO FTAM sequential-text
09:12:06[9900] 4e 06 Document Type [APPL 14] Length=6 (14)
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] 4e 06 Document Type [APPL 14] Length=6 (6)
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
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
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
close
create
delete
dir
get
in
input commands
lcd
open
put
pwd
quit
ratt
rcd
read
recover
rename
93
94
Command
Description
shf
trf delete
trf list
trf show
page 95
page 97
page 98
page 98
page 98
page 98
page 98
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
null value.
s <ssel>Session 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.
t <tsel>Transport 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.
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)
All other parameters are unchanged. When you press return, the system
displays the complete entry.
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>
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.
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
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
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