HP FTAM/9000 Reference Manual

Edition 4

B1033-90004

HP 9000 Networking

E0597

Printed in: U.S.A.

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 ﬁtness 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 speciﬁc warranty terms applicable to your Hewlett- Packard product and replacement parts can be obtained from your local Sales and Service Ofﬁce.

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 ﬂexible 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.

Reproduction, adaptation, or translation of this document without prior written permission is prohibited, except as allowed under the copyright laws.

This software is based in part on the Fourth Berkeley Software Distribution under license from the Regents of the University of California.

©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.

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)

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 speciﬁcation for FTAM. The MAP 3.0 FTAM speciﬁcation 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.

Organization

Chapter 1 FTAM return_codesThis chapter contains a list of

FTAM errors returned in the inout_dcb->result_code.return_code ﬁeld. Possible causes and recovery actions are also listed.

Chapter 2 HP vendor_codesThis chapter contains a list

HP-speciﬁc errors returned in the inout_dcb->result_code.vendor_code ﬁeld. 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 ﬁeld. 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 ﬁelds. 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 ﬁlesets

Chapter 7 HP FTAM/9000 Reference P agesThis chapter lists

created during FTAM/9000 installation.

the HP FTAM/9000 reference pages (man pages) that are available online.

Documentation Guide

For More

Information

Installing and Conﬁguring HP

Installing and Administering HP FTAM/9000 (B1033-90034)

Read

FTAM/9000 Troubleshooting HP

OSI Troubleshooting Guide (32070-90020)

FTAM/9000 FTAM Programming HP FTAM/9000 Programmer's Guide

(B1033- 90014)

FTAM Protocol Speciﬁcations

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

MAP 3.0 Application Interface Speciﬁcation

Speciﬁcations 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 Deﬁnition for the Association Control Service Element

Contents

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

Contents

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 deﬁned constants.

FTAM return_codes

• The mapftam.h ﬁle contains deﬁned 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.

14 Chapter 1

FTAM return_codes

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

speciﬁed 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 ﬁeld. If the error still occurs, refer to the OSI Troubleshooting Guide.

Chapter 1 15

FTAM return_codes

inout_dcb->result.return_code

MESSAGE FTE004_BUFFER_OVERFLOW CAUSE The inout_dcb speciﬁed 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 insufﬁcient 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.

16 Chapter 1

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 conﬁgured 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.

• Reconﬁgure the system to support more AE invocations.

Chapter 1 17

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 Insufﬁcient 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.

18 Chapter 1

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 ﬁeld.

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 conﬁgured on your network, or you incorrectly typed the name.

ACTION Call ft_connect() with a conﬁgured called_dir_name

that identiﬁes 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.

Chapter 1 19

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.

20 Chapter 1

FTAM return_codes

inout_dcb->result.return_code

MESSAGE FTE027_INVALID_INOUT_DCB CAUSE You set the inout_dcb parameter address to NULL and

passed this parameter to an FTAM function call.

ACTION You have two options.

• Pass a valid, non-NULL pointer to the inout_dcb pointer.

• Call ft_didcb() to set the inout_dcb, passing an additional_size large enough to hold all possible inout_dcb data. Pass the address of the pointer returned by ft_didcb() to the FTAM function.

MESSAGE FTE028_NO_MIN_OUT_SPACE CAUSE You did not provide the minimum, required inout_dcb

space. The inout_dcb->size must be large enough to return the size and result structure (12 bytes).

ACTION You have two options.

• Call the function with the address of a NULL inout_dcb buffer, indicating the interface should dynamically initialize the DCB.

• Call the function with a larger inout_dcb buffer (at least 12 bytes).

MESSAGE FTE029_AABORT_IND_RCVD CAUSE A user abort indication arrived before the responder

conﬁrmed ft_connect().

ACTION Refer to the OSI Troubleshooting Guide.

Chapter 1 21

FTAM return_codes

inout_dcb->result.return_code

MESSAGE FTE030_APABORT_IND_RCVD CAUSE A provider abort indication arrived before the

responder conﬁrmed ft_connect().

ACTION Refer to the troubleshooting manual for your protocol

stack.

MESSAGE FTE031_INVALID_BUF_PTR CAUSE Invalid buffer pointer; you provided a NULL pointer

instead of a valid address. EXAMPLE: You called ft_connect() and passed a NULL output connection_id pointer.

ACTION Call the function with a valid, non-NULL pointer.

MESSAGE FTE032_IPC_ERROR CAUSE General IPC error; communication between the user

program and ftam_init is lost.

ACTION Refer to the troubleshooting OSI Troubleshooting

Guide.

MESSAGE FTE034_PROVIDER_INIT_ERROR CAUSE Cannot initialize ftam_init. ACTION Refer to the OSI Troubleshooting Guide.

22 Chapter 1

FTAM return_codes

inout_dcb->result.return_code

MESSAGE FTE035_CONFIRMATION_FAILED CAUSE The FTAM responder detected an error and sent a

negative conﬁrmation to ftam_init.

ACTION Examine the following inout_dcb ﬁelds for additional

error information, and take action accordingly.

• result.vendor_code

• diagnostic->error_id•diagnostic->further_details

• action_result

• state_result

MESSAGE FTE036_INV_PRES_ADDRESS CAUSE The maximum number of selectors or nsaps was

exceeded. EXAMPLE: You called ft_connect() and set the input_dcb- >called_presentation_ address.n_nsaps ﬁeld to a value greater than 8.

ACTION Call ft_connect() with valid ﬁelds within the

presentation address (struct P_address). Max. psap_selector length=16 octets Max. ssap_selector length=16 octets Max. tsap_selector length=32 octets Max. nsap length=20 octets Max. number of n_nsaps=8

MESSAGE FTE037_SYSTEM_STATE_ERROR CAUSE Internal inconsistencies occurred. ACTION Refer to the OSI Troubleshooting Guide.

MESSAGE FTE038_DIRECTORY_ERROR CAUSE Unable to access directory information. ACTION Refer to the OSI Troubleshooting Guide.

Chapter 1 23

FTAM return_codes

inout_dcb->result.return_code

MESSAGE FTE040_INV_MY_DIRNAME CAUSE The my_dir_name structure syntax is incorrect on

ft_aeactivation(). EXAMPLE: You speciﬁed my_dir_name with a negative number of rdns.

ACTION Call ft_aeactivation() with a syntactically correct

my_dir_name. The n ﬁeld in struct Dir_dn or struct Dir_rdn must be a positive value. If you provide an attr_id and attr_value in struct Dir_ava, each ﬁeld

must have a length greater than zero and the pointer set to a non-NULL value. If you do not provide these ﬁelds, the length must be zero.

MESSAGE FTE041_INV_MY_AE_TITLE_OPT CAUSE Invalid my_ae_title_option parameter for

ft_aeactivation(); the speciﬁed value is not within the Ae_title_option enumeration.

ACTION Call ft_aeactivation() with a syntactically correct

my_ae_title_option.

24 Chapter 1

FTAM return_codes

inout_dcb->result.return_code

MESSAGE FTE042_INV_MY_AE_TITLE CAUSE Invalid my_ae_title parameter on ft_aeactivation();

syntax is incorrect. EXAMPLE: You called ft_aeactivation() and speciﬁed User_object_id_ option as the my_ae_title_option. You then passed in an invalid struct Object_id as the ae_object_id.

ACTION Call ft_aeactivation() with a syntactically correct

my_ae_title.

• If the ae_title is a directory distinguished name (i.e., you supplied ae_dir_dn), the n ﬁeld in struct Dir_dn or struct Dir_rdn must be a positive value. If you provide an attr_id and attr_value in struct Dir_ava, each ﬁeld must have a length greater than zero and the pointer set to a non-NULL value.

• If the ae_title is an object ID (i.e., you supplied ae_object_id), the length must be greater than zero and the pointer must be a non-NULL value.

MESSAGE FTE043_INV_CALLED_DIR_NAME CAUSE Invalid called_dir_name parameter on ft_connect();

syntax is incorrect. EXAMPLE: You speciﬁed called_dir_name with a negative number of avas.

ACTION Call ft_connect() with a syntactically correct

called_dir_name. The n ﬁeld in struct Dir_dn or struct Dir_rdn must be a positive value. If you provide an attr_id and attr_value in struct Dir_ava, each ﬁeld

must have a length greater than zero and the pointer set to a non-NULL value. If you do not provide these ﬁelds, the length must be zero.

Chapter 1 25

FTAM return_codes

inout_dcb->result.return_code

MESSAGE FTE044_INV_CALLED_AE_T_OPT CAUSE Invalid called_ae_title_option parameter; syntax is

incorrect; the speciﬁed value is not within the Ae_title_option enumeration.

ACTION Call ft_connect() with a syntactically correct

called_ae_title_option.

MESSAGE FTE045_INV_CALLED_AE_TITLE CAUSE Invalid called_ae_title parameter; syntax is incorrect.

EXAMPLE: You called ft_connect() and speciﬁed User_object_id_option as the called_ae_title_option. You then passed an invalid struct Object_id as the ae_object_id.

ACTION Call ft_connect() with a syntactically correct

my_ae_title.

• If the ae_title is an object ID (i.e., you supplied ae_object_id), the length must be greater than zero and the pointer must be a non-NULL value.

MESSAGE FTE090_INV_DYNAMIC_MEM_PTR CAUSE You passed a pointer to ft_fdmemory() that was not

ACTION Only pass pointers allocated by ft_gperror() to

26 Chapter 1

allocated by ft_gperror().

ft_fdmemory().

FTAM return_codes

inout_dcb->result.return_code

MESSAGE FTE092_INV_ADDITIONAL_SIZE CAUSE The cause may be one of the following.

• You requested an additional_size for an input_dcb.

• You requested an additional_size for an inout_dcb that caused an allocation failure.

ACTION • Call ft_didcb() with an additional_size for an

inout_dcb only.

• Call ft_didcb() with a smaller additional_size for the inout_dcb.

MESSAGE FTE094_INVALID_DCB_POINTER CAUSE You passed a pointer to ft_dfdcb() that was not

allocated by ft_didcb(). EXAMPLE: You called malloc() to allocate memory for an Ft_fcopy_out_dcb and then called ft_dfdcb() to free the pointer.

ACTION If you called ft_didcb() to allocate the pointer, call

ft_dfdcb() to free it. If you called malloc() to allocate the pointer, call free() to free it.

MESSAGE FTE095_NWC_REVOKED CAUSE The ft_nwcleared() request was revoked; you called a

function (on a speciﬁed connection_id) that had an un-noted ft_nwcleared() request. You will not know when the resource is free.

ACTION Informative message; no action required.

MESSAGE FTE096_INVALID_DCB_TYPE CAUSE The dcb_type requested in the call to ft_didcb() is

nonexistent.

ACTION Call ft_didcb() with a known dcb_type.

Chapter 1 27

FTAM return_codes

inout_dcb->result.return_code

MESSAGE FTE097_NO_SPACE_AVAILABLE CAUSE No memory available. 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.

MESSAGE FTE098_INVALID_RETURN_CODE CAUSE The result->return_code passed to ft_gperror() is

invalid or non- existent; it has no associated error string.

ACTION Call ft_gperror() with a valid, deﬁned return_code.

MESSAGE FTE099_NO_RESOURCE_OUTSTANDING CAUSE No resource outstanding; you called ft_nwcleared()

without previously receiving the

FTE008_NO_CON_RESOURCES error. The ft_nwcleared() function is valid only if an FTE008_NO_CON_RESOURCES error returns on an ft_sdata() function.

ACTION Call ft_nwcleared() only when you receive a

FTE008_NO_CON_RESOURCES error.

MESSAGE FTE101_BUFF_TOO_BIG CAUSE Buffer holding user data to send (ft_sdata()) is too

large for implementation (more than 7K or 14 data_units).

ACTION Call multiple ft_sdata() functions with smaller or

fewer buffers, or as smaller number of data_units.

28 Chapter 1

FTAM return_codes

inout_dcb->result.return_code

MESSAGE FTE102_BUFF_TOO_SMALL CAUSE The inout_dcb on an ft_rdata() request is not large

enough to hold the output of the call or the des_requested parameter is greater than 12.

ACTION Exit the Data Transfer regime to the File Open regime.

Call ft_read() and ft_rdata(). Ensure all inout_dcbs are large enough to hold all possible data or let the interface allocate the inout_dcb.

MESSAGE FTE104_CONFIRM_NOT_RCVD CAUSE The responder did not conﬁrm this grouped request; an

error on a previous request in the group was detected, and the end group conﬁrm was immediately generated. EXAMPLE: You called the following sequence of functions: ft_bgroup(), ft_select(), ft_open(), and ft_egroup(). After these passed across the network, the responder detected an error on ft_select(). The ft_open() was not processed, and the ft_egroup() conﬁrm was sent. This error would return on ft_open().

ACTION The error probably occurred on a previously conﬁrmed

request within the group. Examine the following inout_dcb ﬁelds for previously conﬁrmed requests and take action accordingly.result.vendor_codediagnostic->error_iddia gnostic->further_detailsaction_resultstate_resultEXAM PLE: Examine the inout_dcb for ft_select() to determine the cause of the error.

Chapter 1 29

FTAM return_codes

inout_dcb->result.return_code

MESSAGE FTE105_CONT_TYPE_UNSUPPORT CAUSE The speciﬁed contents type is not supported (i.e., is not

an FTAM-1, FTAM-2, FTAM-3, or NBS-9 document type). EXAMPLE: You called ft_open() with a

contents_type.contents_form of FT_ABS_SYN_CON_SET_PAIR_FORM.

ACTION Call the function with a supported contents_type. For

all functions requiring a contents_type, ensure

contents_type.contents_form = FT_DOCUMENT_TYPE and contents_type.contents_info. document.name indicates

FTAM-1, FTAM-2, FTAM-3, or NBS-9. For ft_fopen() and ft_open(), contents_type.contents_form can be FT_CONTENTS_UNKNOWN.

MESSAGE FTE112_GROUP_NOT_OPEN CAUSE Grouping was not open on the connection. You called

ft_egroup() before calling ft_bgroup().

ACTION Call ft_bgroup() on a connection before calling

ft_egroup().

MESSAGE FTE113_GROUP_ALREADY_OPEN CAUSE Grouping was already open on the connection. You

called ft_bgroup() on a connection on which you already called ft_bgroup().

ACTION Close the group by calling ft_egroup(). Open another

group with an ft_bgroup() request.

30 Chapter 1

+ 72 hidden pages

HP FTAM/9000 Reference Manual

Specifications and Main Features

Frequently Asked Questions

User Manual