1. Manuals
  2. Brands
  3. HP Manuals
  4. Software
  5. FTAM/9000
  6. Reference manual

HP FTAM/9000 Reference Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

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

Advertisement

Table of Contents
loading

Related Manuals for HP FTAM/9000

Summary of Contents for HP FTAM/9000

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

  • Page 2: Legal Notices

    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.
  • Page 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...
  • Page 5 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)
  • Page 7 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.
  • Page 8 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.
  • Page 9 Installing and Administering HP Configuring HP FTAM/9000 (B1033-90034) FTAM/9000 Troubleshooting HP OSI Troubleshooting Guide (32070-90020) FTAM/9000 FTAM Programming HP FTAM/9000 Programmer's Guide (B1033- 90014) FTAM Protocol ISO 8571, Information Processing Systems – Specifications Open Systems Interconnection – File Transfer, Access and Management International ISO 8571, Information Processing Systems –...

  • Page 11: Table Of Contents

    ........86 5. HP FTAM/9000 PICS 6. Installation Filesets Files Created During Software Installation..... . .92 7. HP FTAM/9000 Reference Pages...
  • Page 12 Contents...

  • Page 13: Ftam Return_Codes

    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.
  • Page 14 • 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.

  • Page 15: Inout_Dcb->Result.return_Code

    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...
  • Page 16 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.
  • Page 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.
  • Page 18 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.
  • Page 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.
  • Page 20 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.
  • Page 21 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.
  • Page 22 FTAM return_codes inout_dcb->result.return_code MESSAGE FTE030_APABORT_IND_RCVD CAUSE A provider abort indication arrived before the responder confirmed 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.
  • Page 23 FTAM return_codes inout_dcb->result.return_code MESSAGE FTE035_CONFIRMATION_FAILED CAUSE The FTAM responder detected an error and sent a negative confirmation to ftam_init. ACTION Examine the following inout_dcb fields 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...
  • Page 24 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 specified my_dir_name with a negative number of rdns. ACTION Call ft_aeactivation() with a syntactically correct my_dir_name. The n field in struct Dir_dn or struct Dir_rdn must be a positive value.
  • Page 25 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 specified 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.
  • Page 26 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 specified 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 specified User_object_id_option as the called_ae_title_option.
  • Page 27 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.
  • Page 28 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;...
  • Page 29 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().
  • Page 30 FTAM return_codes inout_dcb->result.return_code MESSAGE FTE105_CONT_TYPE_UNSUPPORT CAUSE The specified 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...
  • Page 31 FTAM return_codes inout_dcb->result.return_code MESSAGE FTE114_INV_ACCESS_CNTL CAUSE Invalid bits are set in the action_list field of struct Ft_access_control_element. EXAMPLE: You set Bit (1) in the parameter, but only Bits (8) to (15) are valid for the action_list. ACTION Correctly set the FT_FA_XXX bits and call the function again.
  • Page 32 FTAM return_codes inout_dcb->result.return_code MESSAGE FTE119_INV_ACCS_CONTEXT CAUSE Invalid access_context parameter for ft_read(); the specified value is not within the Ft_access_context enumeration. ACTION Call ft_read() with a valid access_context. MESSAGE FTE120_INV_ACTION_RESULT CAUSE Invalid action_result parameter for ft_abort(), ft_edata(), ft_cancel(), or ft_rcancel(); the specified value is not within the Ft_action_result enumeration.
  • Page 33 FTAM return_codes inout_dcb->result.return_code MESSAGE FTE122_INV_ATTR_FILENAME CAUSE Invalid filename parameter for ft_cattributes() or ft_fcattributes(); syntax is incorrect. ACTION Ensure characters in the parameter are part of the graphic string character set. These ordinal values are 32 to 126 and 160 to 255. If used within escape sequences, the values 27, 142, and 143 are also available.
  • Page 34 FTAM return_codes inout_dcb->result.return_code MESSAGE FTE129_INV_DEST_ACCOUNT CAUSE Invalid input_dcb->dest_account parameter for ft_fmove() or ft_fcopy(); syntax is incorrect. ACTION Ensure characters in the parameter are part of the graphic string character set. These ordinal values are 32 to 126 and 160 to 255. If used within escape sequences, the values 27, 142, and 143 are also available.
  • Page 35 FTAM return_codes inout_dcb->result.return_code MESSAGE FTE132_INV_DEST_INIT_ID CAUSE Invalid input_dcb->dest_init_id parameter for ft_fmove() or ft_fcopy(); syntax is incorrect. ACTION Ensure characters in the parameter are part of the graphic string character set. These ordinal values are 32 to 126 and 160 to 255. If used within escape sequences, the values 27, 142, and 143 are also available.
  • Page 36 FTAM return_codes inout_dcb->result.return_code MESSAGE FTE136_INV_FILE_STATUS CAUSE Invalid file_status parameter for ft_create() or ft_fopen(); the specified value is not within the Ft_file_status enumeration. ACTION Call the function with a valid file_status. MESSAGE FTE137_INV_INITIATOR_ID CAUSE Invalid init_id or initiator_identity parameter; syntax is incorrect. ACTION Ensure characters in the parameter are part of the graphic string character set.
  • Page 37 FTAM return_codes inout_dcb->result.return_code MESSAGE FTE143_INV_PROC_MODE CAUSE Invalid bits are set in the processing_mode parameter. EXAMPLE: You set Bit (1) in the parameter, but only Bits (11) to (15) are valid. ACTION Call ft_open() with valid bits set in the processing_mode parameter. MESSAGE FTE148_INV_REQ_ACCESS CAUSE...
  • Page 38 FTAM return_codes inout_dcb->result.return_code MESSAGE FTE150_INV_SRC_DIRNAME CAUSE Invalid source_dirname parameter for ft_fcopy() or ft_fmove(); syntax is incorrect. EXAMPLE: You specified source_dirname with a negative number of rdns. ACTION Call the function with a syntactically correct source_dirname. The n field in struct Dir_dn or struct Dir_rdn must be a positive value.
  • Page 39 FTAM return_codes inout_dcb->result.return_code MESSAGE FTE153_INV_STORE_ACCOUNT CAUSE Invalid storage_account parameter; syntax is incorrect. ACTION Ensure characters in the parameter are part of the graphic string character set. These ordinal values are 32 to 126 and 160 to 255. If used within escape sequences, the values 27, 142, and 143 are also available.
  • Page 40 FTAM return_codes inout_dcb->result.return_code MESSAGE FTE157_NULL_BUFF_PTR CAUSE Pointer to data buffer is NULL. EXAMPLE: You called ft_sdata() and passed a NULL pointer in for the data_unit. ACTION Call ft_sdata() with a non-NULL buffer pointer. MESSAGE FTE158_INV_CONT_TYPE CAUSE Invalid contents_type.contents_info. document.name parameter; invalid struct Octet_string. ACTION Call the function with a valid Ft_contents_type structure.
  • Page 41 FTAM return_codes inout_dcb->result.return_code MESSAGE FTE161_NULL_FILENAME CAUSE You passed a null pointer to filename on a function that requires filename to have a non-NULL value. ACTION Call the function with a valid, non-NULL filename. MESSAGE TE162_NULL_SRC_FNAME CAUSE You called ft_fcopy() or ft_fmove() with a NULL source_filename.
  • Page 42 FTAM return_codes inout_dcb->result.return_code MESSAGE FTE167_UNKN_SERV_CLASS CAUSE Unknown input_dcb-> connect_in_info.service_class parameter; the bits for the FT_SC_XXX defined constants were either invalid or not set. EXAMPLE: You set Bit (1) in the input_dcb-> connect_in_info.service_class parameter, but only Bits (11) to (15) are valid. ACTION Call ft_connect() with a valid FT_SC_XXX bits set for the input_dcb->connect_in_info.
  • Page 43 FTAM return_codes inout_dcb->result.return_code MESSAGE FTE172_INV_THRESHOLD CAUSE The threshold parameter for ft_bgroup() exceeds the maximum number of calls allowed within a group. ACTION Call ft_bgroup() with a valid threshold value. The threshold cannot be zero or greater than five. MESSAGE FTE173_INV_FTQOS CAUSE Invalid input_dcb->connect_in_info.
  • Page 44 FTAM return_codes inout_dcb->result.return_code MESSAGE FTE176_INV_OVERWRITE CAUSE Invalid input_dcb->overwrite parameter for ft_fcopy() or ft_fmove(); the specified value is not within the Ft_delete_overwrite enumeration. ACTION Call the function with a valid input_dcb->overwrite. MESSAGE FTE177_INV_CLASS CAUSE Invalid class parameter; the specified value is not within the Ft_class enumeration.
  • Page 45 FTAM return_codes inout_dcb->result.return_code MESSAGE FTE182_INV_DE_PRIMITIVE CAUSE Invalid data_unit->data.data_element->primitive for ft_sdata(); octet_string syntax is incorrect. EXAMPLE: You specified FT_DE_OCTET_STRING as the data_unit->data.data_element-> prim_type and then specified an invalid octet_string. ACTION Call ft_sdata() with a valid data_unit->data.data_element-> primitive. The octet_string is invalid if the length field is greater than zero and the pointer is NULL or if the length is greater than 65535.
  • Page 46 FTAM return_codes inout_dcb->result.return_code MESSAGE FTE186_INV_EXTEND_PASSWD CAUSE Invalid extend password; syntax is incorrect. ACTION Call the function with a valid Ft_single_file_pw. A password is invalid if the length field is greater than zero and the pointer is NULL or if the length is greater than 65535.
  • Page 47 FTAM return_codes inout_dcb->result.return_code MESSAGE FTE190_INV_DELETE_PASSWD CAUSE Invalid delete_file password; syntax is incorrect. ACTION Call the function with a valid Ft_single_file_pw. A password is invalid if the length field is greater than zero and the pointer is NULL or if the length is greater than 65535.
  • Page 48 FTAM return_codes inout_dcb->result.return_code MESSAGE FTE194_INV_DESTFS_PASSWD CAUSE Invalid dest_filestore_pw password; syntax is incorrect. ACTION Call the function with a valid Ft_single_file_pw. A password is invalid if the length field is greater than zero and the pointer is NULL or if the length is greater than 65535.
  • Page 49 FTAM return_codes inout_dcb->result.return_code MESSAGE FTE199_INV_DU_NODE_DESC CAUSE You called ft_sdata() with an invalid node_descriptor.node_name of type struct Octet_string. ACTION Call ft_sdata() with a valid node_descriptor. The struct Octet_string is invalid if the length field is greater than zero and the pointer is NULL or if the length is greater than 65535.
  • Page 50 FTAM return_codes inout_dcb->result.return_code MESSAGE FTE501_ABNORMAL_TERM CAUSE One of the connections on a HLCF call was terminated abnormally. ACTION Refer to the OSI Troubleshooting Guide. MESSAGE FTE502_LOC_RES_UNAVAIL CAUSE Required resources are not obtainable for a HLCF call; generated when all connections for the given ftam_init are exhausted;...
  • Page 51 FTAM return_codes inout_dcb->result.return_code MESSAGE FTE506_TRANSFER_ERROR CAUSE The responder ended the data transfer on a HLCF call; indicates an unsuccessful end data indication arrived at one of the nodes. ACTION Refer to the OSI Troubleshooting Guide. MESSAGE FTE507_TRANSFER_SRC_ABORT CAUSE The responder on the source node aborted the data transfer on a HLCF call.
  • Page 52 FTAM return_codes inout_dcb->result.return_code Chapter 1...

  • Page 53: Hp Vendor_Codes

    HP vendor_codes This chapter contains a list of HP-specific errors returned in the inout_dcb->result.vendor_code field. The vendor_codes reflect HP-specific error information; you do not receive errors specific to other vendors in this field.
  • Page 54 HP vendor_codes • The mapftam.h file contains defined constants for HP vendor_codes. • To receive a printable character string, 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.
  • Page 55 Informative message; no action required. MESSAGE FTV101_UNABLE_TO_RCV_IPC_CON CAUSE Unable to establish interprocess communication (IPC) connection with ftam_init. ACTION Collect relevant error information and contact your HP support representative. MESSAGE FTV102_CANNOT_KILL_INITIATOR CAUSE Unable to deactivate ftam_init. ACTION The kill() function failed on ftam_init. Check the log file for errors logged by ftam_init.
  • Page 56 FTV104_CANNOT_EXEC_INITIATOR CAUSE Cannot execute ftam_init ACTION • Check the log file for errors logged by ftam_init. • Consult HP-UX system reference manuals for action corresponding to errno. • Collect relevant error information and contact you HP support representative. MESSAGE FTV105_AE_INVOC_TABLE_FULL CAUSE Application Entity (AE) invocation table is full.
  • Page 57 FTV108_SHMEM_ERROR CAUSE Shared memory error. ACTION • Check the log file for errors logged by ftam_init. • Consult HP-UX system reference manuals for action corresponding to errno. • Collect relevant error information and contact your HP support representative. MESSAGE FTV109_BAD_IPC_MSG CAUSE Bad interprocess message.
  • Page 58 MESSAGE FTV113_NO_AE_INVOC_ENTRY CAUSE The AE invocation entry for this presentation address is missing. ACTION Collect relevant error information and contact your HP support representative. MESSAGE FTV201_EM_EMPTY_EVENT_EXP CAUSE Event management internal error. ACTION Check the log file for logged error messages. Collect relevant error information and contact your HP support representative.

  • Page 59: Inout_Dcb->Result.vendor_Code

    Call only valid functions within a group. MESSAGE FTV302_CANNOT_INIT_DCB_TABLE CAUSE Unable to initialize DCB table. ACTION Call the function again. If the error still occurs, collect relevant error information and contact your HP support representative. MESSAGE FTV303_CANNOT_ADD_TO_DCB_TABLE CAUSE Unable to add to DCB table. ACTION Free some memory resources and call the function again.
  • Page 60 ACTION Check the action_result, state_result, and diagnostic in the inout_dcb to determine which request failed and why. If the error still occurs, collect relevant error information and contact your HP support representative. Chapter 2...
  • Page 61 HP vendor_codes inout_dcb->result.vendor_code MESSAGE FTV402_FUNC_UNIT_NEGOTIATED_DOWN CAUSE The responder does not support all the functional_units requested on the ft_connect() request. ACTION Informative message; no action required. Check to see which functional_units the responder supports. Attempt the appropriate action using low level calls if the functional_units supported allow it.
  • Page 62 HP vendor_codes inout_dcb->result.vendor_code MESSAGE FTV406_HLCF_SRC_ABORT_IND_RCVD CAUSE An abort indication was received on an HLCF source connection. ACTION Check the inout_dcb->diagnostic to determine the reason for the abort and call the function again. MESSAGE FTV407_HLCF_DEST_ABORT_IND_RCVD CAUSE An abort indication was received on an HLCF destination connection.
  • Page 63 HP vendor_codes inout_dcb->result.vendor_code MESSAGE FTV411_NEG_OPEN_CNF_ON_HLCF_REQ CAUSE The responder sent a negative confirmation on the open request within a HLCF call. ACTION Check the inout_dcb->diagnostic to determine the reason for the failure and call the function again. MESSAGE FTV412_NEG_RATTR_CNF_ON_HLCF_REQ CAUSE The responder sent a negative confirmation on the read attributes request within a HLCF call.
  • Page 64 HLCF call. ACTION Check the inout_dcb->diagnostic to determine the reason for the failure and call the function again. MESSAGE FTV420_HLCF_STATE_ERROR CAUSE HLCF state error. ACTION Check the log file. Collect relevant error information; then contact your HP support representative. Chapter 2...
  • Page 65 HP vendor_codes inout_dcb->result.vendor_code MESSAGE FTV421_NOT_IN_DATA_TRANS_PHASE CAUSE You called ft_rdata() while in a regime other than data transfer. ACTION Call ft_rdata() in the Data Transfer regime only after an ft_read() request and before the transferring of data ends. Chapter 2...
  • Page 66 HP vendor_codes inout_dcb->result.vendor_code Chapter 2...

  • Page 67: Diagnostic Error_Ids

    Diagnostic error_ids This chapter contains a list of diagnostic values returned in theinout_dcb->diagnostic->error_id field. These errors are generated in the FTAM protocol machine (FPM) and the Virtual Filestore (VFS), not in the interface. This chapter includes only those diagnostic->error_ids...
  • Page 68 Diagnostic error_ids returned by HP initiators and responders; it may or may not include diagnostics returned by other vendors. The causes and recovery actions listed are specific to HP's implementation. • The f_error.h file contains defined constants for all FTAM diagnostic->error_ids.

  • Page 69: Inout_Dcb->Diagnostic->Error_Id

    MESSAGE F_FTAM_MGT_PROBLEM CAUSE FTAM management problem. ACTION Collect relevant error information and contact your HP support representative. MESSAGE F_SUBSEQ_ERR CAUSE This diagnostic returns on grouped functions if the threshold is not met. If the threshold number of functions is not processed before a state_result failure is detected, a negative re-sponse is made for the group.
  • Page 70 Diagnostic error_ids inout_dcb->diagnostic->error_id MESSAGE F_ACCESS_VIOLATES_LOCAL_SEC CAUSE Could not access the local real file or directory due to UNIX permission problem. ACTION Check the permissions of the file and directory. MESSAGE 1007 F_FTAM_PROTO_ERR CAUSE FTAM protocol error; may be one of the following reasons.
  • Page 71 The grouping sequence is illegal. Depending on the service_class negotiated, only certain sequences of PDUs can be in a grouped request. ACTION Call the grouped functions in a valid sequence. Refer to the HP FTAM/9000 Programmer's Guide for acceptable sequences when grouping functions. MESSAGE 2008 F_ASSOC_MGT CAUSE Association management;...
  • Page 72 CAUSE The filestore_pw is invalid. ACTION Call the function with a valid filestore_pw. The filestore_pw is the HP-UX password associated with the initiator identity that is the HP-UX login. MESSAGE 3000 F_FILE_NOT_FOUND CAUSE The filename specified on ft_select() does not exist or you entered it incorrectly.
  • Page 73 Diagnostic error_ids inout_dcb->diagnostic->error_id MESSAGE 3004 F_NON_EXISTENT_FILE CAUSE The shadow file for the filename specified on ft_select() does not exist. ACTION Remove the existing FTAM data file and recreate it using FTAM functions; doing so recreates the shadow file. MESSAGE 3005 F_FILE_ALREADY_EXISTS CAUSE You called ft_create() with file_status set to...
  • Page 74 Diagnostic error_ids inout_dcb->diagnostic->error_id MESSAGE 3010 F_CONC_CTL_NOT_POSSIBLE CAUSE You cannot currently access the file for one of the following reasons • Another application is accessing the file and enum Ft_file_lock in Ft_concurrency_control is set such that you cannot concurrently access the file.
  • Page 75 Diagnostic error_ids inout_dcb->diagnostic->error_id MESSAGE 3016 F_ACCESS_CTL_INCONSISTENT CAUSE This diagnostic returns on ft_select(), ft_create(), and HLCF calls. The cause may be one of the following reasons. • The bits set in the FT_AC_XXX defined constants prohibit your requested access to the file.
  • Page 76 Diagnostic error_ids inout_dcb->diagnostic->error_id MESSAGE 3028 F_REQ_ACC_VIOL_PERM_ACT CAUSE The bits set for the requested_access FT_FA_XXX defined constants are not a subset of the bits set for the permitted_actions FT_PA_XXX defined constants. ACTION Correctly set the FT_FA_XXX bits or call the function with a valid requested_access. The requested_access must be a subset of the permitted_actions values on ft_select() or ft_create().
  • Page 77 Diagnostic error_ids inout_dcb->diagnostic->error_id MESSAGE 4002 F_ATTRIB_CANNOT_CHNG CAUSE You cannot change the attribute for one of the following reasons. • When you selected the file, you did not set requested_access to include FT_FA_CHANGE_ATTRIBUTE. • You tried to add a duplicate access control element for an existing initiator identity.
  • Page 78 Diagnostic error_ids inout_dcb->diagnostic->error_id MESSAGE 5014 F_DATA_ELEMENT_TYPE CAUSE The prim_type field in struct Ft_data_element is not set correctly. ACTION Set prim_type to a valid value. For FTAM-1 document types, prim_type must be IA5_STRING or GENERAL_STRING. For FTAM-2 document types, prim_type must be GRAPHIC_STRING. For FTAM-3 document types, prim_type must be OCTET_STRING.
  • Page 79 Diagnostic error_ids inout_dcb->diagnostic->error_id MESSAGE 5023 F_PROC_MD_INCONSISTENT CAUSE The bits set for the processing_mode FT_FA_XXX defined constants are not a subset of the bits set for the requested_access FT_PA_XXX defined constants. ACTION Correctly set the FT_FA_XXX bits or call ft_open() with a valid processing_mode. The processing_mode must be a subset of the requested_access values on ft_select() or ft_create().
  • Page 80 F_LCL_FAIL_DVC_FAIL CAUSE Local device failure. An I/O error occurred when trying to write the file via an HP-UX system call. For example, you may be out of disc space. ACTION If needed, create disc space on the real file system (responder) where the write failure occurred.

  • Page 81: Event Management Errors

    Event Management Errors This chapter contains a list of values that may be returned when calling em_wait(), em_fdmemory(), and em_gperror(). These errors return in the result->return_code and result->vendor_code fields. To receive a printable character string for returned errors, call em_gperror().
  • Page 82 Event Management Errors Refer to the “Handling Errors” chapter in the HP FTAM/9000 Programmer's Guide for information on checking for and handling errors. Chapter 4...

  • Page 83: Em Return_Codes

    Event Management Errors EM return_codes EM return_codes This section contains a list of values that may be returned in the result->return_code field when calling em_wait(), em_fdmemory(), and em_gperror(). NOTE The error EME031_INVALID_BUF_PTR returns only as a function return value if the result parameter is set to a NULL pointer (i.e., it does not return in the return_code or vendor_code).
  • Page 84 Event Management Errors EM return_codes MESSAGE EME005_TIMEOUT CAUSE None of the posted events were noted within the time allotted by the timeout parameter. ACTION Call em_wait() again to receive the noted events, possibly with a longer timeout parameter. MESSAGE EME031_INVALID_BUF_PTR CAUSE Invalid buffer pointer;...
  • Page 85 Event Management Errors EM return_codes MESSAGE EME097_NO_SPACE_AVAILABLE CAUSE The interface could not allocate sufficient space for the return_string and vendor_string; the system ran out of memory. ACTION Free any allocated dynamic memory that is no longer needed and call the function again. EXAMPLE: You made multiple calls to em_gperror() requesting that the interface allocate memory;...

  • Page 86: Em Vendor_Codes

    Event Management Errors EM vendor_codes EM vendor_codes This section contains a list of values that may be returned in the result- >vendor_code field when calling em_wait(), em_fdmemory(), and em_gperror(). result->return_code MESSAGE EMV000_NO_CODE_SUPPLIED CAUSE No additional vendor-specific information is available; the return_code provides sufficient information. ACTION Informative message;...
  • Page 87 Event Management Errors EM vendor_codes MESSAGE EMV005_PARAM_VEN_STRING CAUSE The vendor_string buffer pointer is set to NULL. ACTION Set the vendor_string parameter to a valid, non-NULL value. Chapter 4...
  • Page 88 Event Management Errors EM vendor_codes Chapter 4...

  • Page 89: Hp Ftam/9000 Pics

    HP FTAM/9000 PICS For a copy of the Protocol Implementation Conformance Statement (PICS) for the HP FTAM/9000 product, please contact your HP support representative.
  • Page 90 HP FTAM/9000 PICS Chapter 5...

  • Page 91: Installation Filesets

    Installation Filesets The files listed in this chapter are installed in the indicated directories at the time you install FTAM. Installing the reference page (man page) files is recommended, but omitting them will not operationally affect FTAM.

  • Page 92: Files Created During Software Installation

    Installation Filesets Files Created During Software Installation Files Created During Software Installation Files in fileset FTAM Function Interactive interface executable /opt/ftam/bin/ftam fcattr command /opt/ftam/bin/fcattr fcp command /opt/ftam/bin/fcp fdel command /opt/ftam/bin/fdel fls command /opt/ftam/bin/fls fmv command /opt/ftam/bin/fmv Utility to change FTAM attributes of a /opt/ftam/bin/fchdoc local file OTS startup utility for FTAM...
  • Page 93 Installation Filesets Files Created During Software Installation Files in fileset FTAM Function lint library for FTAM programmatic /opt/ftam/lib/llib-lmap.ln interface Programmatic interface library definitions /opt/ftam/lib/libmapftam.a lint library for FTAM programmatic /opt/ftam/lib/llib-lmapftam interface lint library for FTAM programmatic /opt/ftam/lib/llib-lmapftam.ln interface Network tracing and logging NLS catalog /opt/ftam/lib/nls/C/acse.cat Network tracing and logging NLS catalog /opt/ftam/lib/nls/C/cm.cat...
  • Page 94 Installation Filesets Files Created During Software Installation Files in fileset FTAM Function Network tracing and logging subformatter /opt/ftam/shlib/libfmt122f.sl Network tracing and logging subformatter /opt/ftam/shlib/libfmt124f.sl Network tracing and logging subformatter /opt/ftam/shlib/fmt124f.sl Makefile for FTAM demo /opt/ftam/demos/Makefile README file for FTAM demo /opt/ftam/demos/README Set up of sample file /opt/ftam/demos/setup...
  • Page 95 Installation Filesets Files Created During Software Installation Files in fileset OSIF-MAN Function Man page for indicated function /opt/ftam/man/man1.Z/fcattr.1 Man page for indicated function /opt/ftam/man/man1.Z/fchdoc.1 Man page for indicated function /opt/ftam/man/man1.Z/fcp.1 Man page for indicated function /opt/ftam/man/man1.Z/fdel.1 Man page for indicated function /opt/ftam/man/man1.Z/fls.1 Man page for indicated function /opt/ftam/man/man1.Z/ftam.1...
  • Page 96 Installation Filesets Files Created During Software Installation Files in fileset OSIF-MAN Function Man page for indicated function /opt/ftam/man/man3.Z/ft_etransfe.3n Man page for indicated function /opt/ftam/man/man3.Z/ft_fcattrib.3n Man page for indicated function /opt/ftam/man/man3.Z/ft_fclose.3n Man page for indicated function /opt/ftam/man/man3.Z/ft_fcopy.3n Man page for indicated function /opt/ftam/man/man3.Z/ft_fcopy_aet.3n Man page for indicated function /opt/ftam/man/man3.Z/ft_fdelete.3n...
  • Page 97 Installation Filesets Files Created During Software Installation Files in fileset OSIF-MAN Function Man page for indicated function /opt/ftam/man/man3.Z/ft_select.3n Man page for indicated function /opt/ftam/man/man3.Z/ft_write.3n Man page for indicated function /opt/ftam/man/man3.Z/em_hp_select.3n Man page for indicated function /opt/ftam/man/man3.Z/em_wait.3n Man page for indicated function /opt/ftam/man/man3.Z/em_gperror.3n Man page for indicated function /opt/ftam/man/man3.Z/em_fdmemory.3n...
  • Page 98 Installation Filesets Files Created During Software Installation Chapter 6...

  • Page 99: Hp Ftam/9000 Reference

    HP FTAM/9000 Reference Pages The following are the HP FTAM/9000 reference pages (man pages) available online. If you have loaded the reference page filesets, you can view them online by using the man(1) command at the HP-UX prompt.
  • Page 100 HP FTAM/9000 Reference Pages Entry Name Description em_fdmemory(3) free dynamic memory allocated by Event Management em_gperror(3) translate an Event Management error to a string em_hp_select(3) wait for MAP 3.0 and non-MAP events em_hp_sigio(3) enable/disable signal notification for MAP 3.0 em_wait(3) wait for an asynchronous MAP 3.0 event...
  • Page 101 HP FTAM/9000 Reference Pages Entry Name Description ft_edata(3) end a series of FTAM data primitives ft_egroup(3) end a group of FTAM functions ft_erase(3) erase all or part of an FTAM file ft_etransfer(3) end an FTAM data transfer ft_fcattributes(3) change the file attributes of an FTAM file ft_fcattributes_aet(3) change the file attributes of an FTAM file...
  • Page 102 HP FTAM/9000 Reference Pages Entry Name Description ft_rdata(3) receive a block of FTAM data ft_read(3) request transfer of data from FTAM ft_rrequest(3) release an FTAM connection ft_sdata(3) send a block of FTAM data ft_select(3) select an FTAM file ft_write(3) request transfer of data to an FTAM file ftam(1) OSI file transfer, access and management program...

Table of Contents