HP FTAM/9000 User manual

HP FTAM/9000 Reference Manual
Edition 4
B1033-90004
HP 9000 Networking
E0597
Printed in: U.S.A.
© Copyright 1997, Hewlett-Packard Company.

2
Legal Notices
The information in this document is subject to change without notice.
Hewlett-Packard makes no warranty of any kind with regard to this
manual, including, but not limited to, the implied warranties of
merchantability and fitness for a particular purpose. Hewlett-Packard
shall not be held liable for errors contained herein or direct, indirect,
special, incidental or consequential damages in connection with the
furnishing, performance, or use of this material.
Warranty. A copy of the specific warranty terms applicable to your
Hewlett- Packard product and replacement parts can be obtained from
your local Sales and Service Office.
Restricted Rights Legend. Use, duplication or disclosure by the U.S.
Government is subject to restrictions as set forth in subparagraph (c) (1)
(ii) of the Rights in Technical Data and Computer Software clause at
DFARS 252.227-7013 for DOD agencies, and subparagraphs (c) (1) and
(c) (2) of the Commercial Computer Software Restricted Rights clause at
FAR 52.227-19 for other agencies.
HEWLETT-PACKARD COMPANY 3000 Hanover Street Palo Alto,
California 94304 U.S.A.
Use of this manual and flexible disk(s) or tape cartridge(s) supplied for
this pack is restricted to this product only. Additional copies of the
programs may be made for security and back-up purposes only. Resale of
the programs in their present form or with alterations, is expressly
prohibited.
Copyright Notices. ©copyright 1983-97 Hewlett-Packard Company, all
rights reserved.
Reproduction, adaptation, or translation of this document without prior
written permission is prohibited, except as allowed under the copyright
laws.
©copyright 1979, 1980, 1983, 1985-93 Regents of the University of
California
This software is based in part on the Fourth Berkeley Software
Distribution under license from the Regents of the University of
California.

3
©copyright 1980, 1984, 1986 Novell, Inc.
©copyright 1986-1992 Sun Microsystems, Inc.
©copyright 1985-86, 1988 Massachusetts Institute of Technology.
©copyright 1989-93 The Open Software Foundation, Inc.
©copyright 1986 Digital Equipment Corporation.
©copyright 1990 Motorola, Inc.
©copyright 1990, 1991, 1992 Cornell University
©copyright 1989-1991 The University of Maryland
©copyright 1988 Carnegie Mellon University
Trademark Notices UNIX is a registered trademark in the United
States and other countries, licensed exclusively through X/Open
Company Limited.
X Window System is a trademark of the Massachusetts Institute of
Technology.
MS-DOS and Microsoft are U.S. registered trademarks of Microsoft
Corporation.
OSF/Motif is a trademark of the Open Software Foundation, Inc. in the
U.S. and other countries.

4

5
Printing History
The manual printing date and part number indicate its current edition.
The printing date will change when a new edition is printed. Minor
changes may be made at reprint without changing the printing date. The
manual part number will change when extensive changes are made.
Manual updates may be issued between editions to correct errors or
document product changes. To ensure that you receive the updated or
new editions, you should subscribe to the appropriate product support
service. See your HP sales representative for details.
First Edition: April 1991 (HP-UX Release 8.0)
Second Edition: November 1992 (HP-UX Release 9.0)
Third Edition: January 1995 (HP-UX Release 10.0)
Fourth Edition: May 1997 (HP-UX Release 10.3)

6

7
Preface
Purpose and Scope
The purpose of this manual is to help you troubleshoot errors returned in
your HP FTAM/9000 applications. This manual lists the errors, probable
causes, and corrective actions. Additionally, this manual includes the HP
FTAM/ 9000 reference pages.
NOTE This manual lists FTAM error and reference information. If you are
learning FTAM and need more comprehensive explanations, refer to the
HP FTAM/9000 Programmer's Guide.
FTAM/9000 runs on HP OTS/9000, an HP network product that provides
a lower-level OSI protocol “stack,” in conjunction with an 802.3 network
link.
Audience
This manual is for application programmers who are familiar with the C
programming language and who need to correct errors in their
applications. This manual is also for programmers who need to consult
the FTAM/9000 reference pages (which are copies of the online man
pages).
MAP 3.0 Interface Note
Users should note that the FTAM/9000 programmatic interface is taken
from the MAP 3.0 specification for FTAM. The MAP 3.0 FTAM
specification includes error codes and other details, which consequently
appear in the programmatic interface to FTAM/9000. This document
contains numerous references to MAP–based details found in
FTAM/9000.

8
Organization
Chapter 1 FTAM return_codesThis chapter contains a list of
FTAM errors returned in the
inout_dcb->result_code.return_code field. Possible
causes and recovery actions are also listed.
Chapter 2 HP vendor_codesThis chapter contains a list
HP-specific errors returned in the
inout_dcb->result_code.vendor_code field. Possible
causes and recovery actions are also listed.
Chapter 3 Diagnostic error_idsThis chapter contains a list of
diagnostic values returned in the
inout_dcb->diagnostic->error_id field. Possible
causes and recovery actions are also listed.
Chapter 4 Event Management ErrorsThis chapter contains a
list of values returned when calling em_wait(),
em_fdmemory(), and em_gperror(). These errors
return in the result->return_code and
result->vendor_code fields. Possible causes and
recovery actions are also listed.
Chapter 5 HP FTAM/9000 PICSThis chapter contains
information on how to obtain a copy of the Protocol
Implementation Conformance Statement (PICS) for
the HP FTAM/9000 product. Use this information in
conjunction with other vendor's PICS to determine
how the various responders communicate.
Chapter 6 Installation FilesetsThis chapter lists the filesets
created during FTAM/9000 installation.
Chapter 7 HP FTAM/9000 Reference PagesThis chapter lists
the HP FTAM/9000 reference pages (man pages) that
are available online.

9
Documentation Guide
For More
Information Read
Installing and
Configuring HP
FTAM/9000
Installing and Administering HP
FTAM/9000 (B1033-90034)
Troubleshooting HP
FTAM/9000 OSI Troubleshooting Guide (32070-90020)
FTAM Programming HP FTAM/9000 Programmer's Guide
(B1033- 90014)
FTAM Protocol
Specifications ISO 8571, Information Processing Systems – Open Systems Interconnection – File
Transfer, Access and Management
International
Standards ISO 8571 ISO 8571, Information Processing Systems – Open Systems Interconnection – File
Transfer, Access and Management
MAP 3.0 Interface
Specifications MAP 3.0 Application Interface Specification
NBS Phase III Implementation Agreements for Open
Systems Interconnection Protocols from the
NBS Workshop for Implementors of Open
Systems Interconnection
ACSE ISO 8649, Information Processing Systems –
Open Systems Interconnection – Service
DefinitionfortheAssociationControlService
Element

10

Contents
11
1. FTAM return_codes
inout_dcb->result.return_code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
2. HP vendor_codes
inout_dcb->result.vendor_code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
3. Diagnostic error_ids
inout_dcb->diagnostic->error_id. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
4. Event Management Errors
EM return_codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83
EM vendor_codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86
result->return_code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86
5. HP FTAM/9000 PICS
6. Installation Filesets
Files Created During Software Installation. . . . . . . . . . . . . . . . . . . . . . .92
7. HP FTAM/9000 Reference Pages

12
Contents

13
1 FTAM return_codes
This chapter lists the inout_dcb->result.return_codes. The initiator and
responder detect FTAM errors and return them in the user program as
integer defined constants.

14 Chapter1
FTAM return_codes
• The mapftam.h file contains defined constants for FTAM
return_codes.
• To obtain a printable character string for the error, call ft_gperror().
Refer to the “Handling Errors” chapter in the HP FTAM/9000
Programmer's Guide for information on checking for and handling
errors.

Chapter 1 15
FTAM return_codes
inout_dcb->result.return_code
inout_dcb->result.return_code
MESSAGE FTE000_SUCCESS
CAUSE Successful function execution (no error).
ACTION Informative message; no action required.
MESSAGE FTE001_INV_EVENT_NAME
CAUSE The return_event_name is a negative value and
therefore, invalid.
ACTION Call the function with a valid, positive
return_event_name.
MESSAGE FTE002_DUP_EVENT_NAME
CAUSE You previously made an asynchronous call using the
same value for return_event_name.
ACTION Call the function asynchronously with a
return_event_name that is not already in use.
MESSAGE FTE003_ABORT_IND_RCVD
CAUSE An abort indication was received on the connection_id
specified in the call.
ACTION Call ft_ireceive() to obtain abort information. Perform
error recovery based on the information returned in
either the inout_dcb->info.pabort_info or
inout_dcb->info.aabort_info field. If the error still
occurs, refer to the OSI Troubleshooting Guide.

16 Chapter1
FTAM return_codes
inout_dcb->result.return_code
MESSAGE FTE004_BUFFER_OVERFLOW
CAUSE The inout_dcb specified is not large enough to hold the
output of the call.
ACTION You have two options:
• Call the function with the address of a NULL
inout_dcb, thus requesting the interface to
dynamically allocate the output area.
• Call the function with a larger buffer.
MESSAGE FTE005_INV_CONN_ID
CAUSE The connection_id from ft_connect() is no longer active
or ft_connect() did not return the connection_id.
ACTION Call the function with a valid, active connection_id
returned from an ft_connect() request.
MESSAGE FTE006_NETWORK_UNAVAIL
CAUSE All contact with ftam_init was lost either because it
was killed or exited.
ACTION Call ft_aeactivation() to activate another ftam_init. If
the error still occurs, terminate the application and
refer to the OSI Troubleshooting Guide.
MESSAGE FTE007_NO_REQ_RESOURCES
CAUSE Current resources are insufficient to honor the request;
virtual memory is exhausted.
ACTION Check your memory management. Free any unused
resources (e.g., memory), call ft_dfdcb() to free DCBs
that are no longer needed, and call the function again.

Chapter 1 17
FTAM return_codes
inout_dcb->result.return_code
MESSAGE FTE008_NO_CON_RESOURCES
CAUSE No connection resources are available; generated on
ft_sdata() when connection resources are temporarily
exhausted.
ACTION Call ft_nwcleared(); when this request is noted (the
resources are freed), call ft_sdata() again.
MESSAGE FTE009_RELEASE_REQ_ISSUED
CAUSE You called a function on a connection that had an
un-noted release request.
ACTION Call ft_connect() to establish a new connection and
continue processing. When calling functions, always
use an active connection_id returned from ft_connect().
MESSAGE FTE010_MY_DIR_NAME_UNKNOWN
CAUSE The my_dir_name associated with ftam_init is
unknown. Either it does not exist, or you incorrectly
typed the name.
ACTION Call ft_aeactivation() with a configured my_dir_name.
MESSAGE FTE011_AE_INVOC_EXHAUSTED
CAUSE You reached the maximum number of allowable AE
invocations between the user program and ftam_init.
ACTION You have three options.
• Write programs to use fewer AE invocations.
• Finish processing on AEs and deactivate them.
• Reconfigure the system to support more AE
invocations.

18 Chapter1
FTAM return_codes
inout_dcb->result.return_code
MESSAGE FTE013_BAD_AE_LABEL
CAUSE The ae_label was deactivated or not returned from an
ft_aeactivation() request.
ACTION Call the function with a valid, active ae_label returned
from an ft_aeactivation() request.
MESSAGE FTE015_FUNCTIONING_CONNECT
CAUSE You called ft_aedeactivation() when ftam_init had one
or more open connections.
ACTION You have two options. Finish processing on the
connection,
• Call ft_rrequest() to release the connection, and call
ft_aedeactivation() to deactivate ftam_init.
• Call ft_aereset() to abruptly abort all open
connections and then call ft_aedeactivation() to
deactivate ftam_init
MESSAGE FTE016_LACK_TARGET_INFO
CAUSE Insufficient target address information; either the
called_dir_name or
input_dcb->called_presentation_address parameter is
missing from ft_connect(). You must provide one or
both. EXAMPLE: You called ft_connect() with a NULL
called_dir_name and 0 in the input_dcb-
>called_presentation_address.n_nsaps parameter.
ACTION Call ft_connect() with a valid called_dir_name or
input_dcb->called_presentation_address parameter. If
you provide both,
input_dcb->called_presentation_address has
precedence.

Chapter 1 19
FTAM return_codes
inout_dcb->result.return_code
MESSAGE FTE017_CONTEXT_NAME_MISSING
CAUSE The context_name is missing. EXAMPLE: You called
ft_connect() with a 0 (zero) in the
input_dcb->context_name.length field.
ACTION Call the function with the following FTAM
context_name: 1 0 8571 1 1.
MESSAGE FTE018_CALLED_DIR_NAME_NO_ADDR
CAUSE On ft_connect(), the called_dir_name for the FTAM
responder has no associated presentation address.
Either called_dir_name is not configured on your
network, or you incorrectly typed the name.
ACTION Call ft_connect() with a configured called_dir_name
that identifies the FTAM responder to which you are
trying to connect.
MESSAGE FTE019_CONNECT_EXHAUSTED
CAUSE You reached the maximum number of allowable
connections between ftam_init and the responder.
ACTION You have three options.
• Activate another ftam_init and call ft_connect()
again.
• Finish processing on some of the open connections
and re-use those connections.
• Finish processing on some of the open connections,
call ft_rrequest() or ft_abort() to release or abort the
connection, and call ft_connect() again.

20 Chapter1
FTAM return_codes
inout_dcb->result.return_code
MESSAGE FTE021_USER_ABORTED_CONN
CAUSE You attempted processing on a connection on which
ft_abort() was requested, but not noted.
ACTION Open another connection and call the function again.
Attempt processing only on active connections.
MESSAGE FTE024_USER_RELEASED_CONN
CAUSE You attempted processing on a connection on which an
ft_rrequest() was successfully completed.
ACTION Call ft_connect() to establish a connection and perform
the appropriate processing. Attempt processing only on
active connections.
MESSAGE FTE025_PROTOCOL_ERROR
CAUSE A function call violated an FTAM protocol in one of the
following ways.
• You called a function outside the current regime.
• You called an illegal function within a group.
EXAMPLE: You called ft_rdata() after receiving a
data end indication.
ACTION Ensure you are in the correct regime for calling the
function. Call only functions that are allowed within
the group.
MESSAGE FTE026_INVALID_INPUT_DCB
CAUSE Invalid input_dcb; you passed a NULL pointer to a
function with mandatory parameters in the input_dcb.
ACTION You have two options. Set all mandatory input_dcb
parameters and call the function again. Call ft_didcb()
to automatically initialize the input_dcb.