HP FTAM/9000 Reference Manual Edition 4 B1033-90004 HP 9000 Networking E0597 Printed in: U.S.A. © Copyright 1997, Hewlett-Packard Company.
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.
©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.
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.
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.
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.
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 Syst
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 12
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.
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.
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.
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.
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.
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.
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.
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.
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.
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. ACTION Call the function with a valid, non-NULL pointer.
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 The maximum number of selectors or nsaps was exceeded.
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.
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. • If the ae_title is a directory distinguished name (i.e.
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.
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.
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, defined return_code.
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.
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 contents_type.contents_info. document.
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. MESSAGE FTE115_INV_ACSCTL_ID CAUSE Invalid identity field of struct Ft_access_control_element; syntax is incorrect.
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.
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.
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.
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. MESSAGE FTE133_INV_DIAG_STRUCT CAUSE Invalid struct Ft_diagnostic structure; syntax is incorrect.
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.
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 Invalid bits are set in the requested_access parameter for ft_create(), ft_fopen(), or ft_select().
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.
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. MESSAGE FTE154_INV_STRUCT_ID CAUSE Invalid structure_id parameter; the specified value is not within the Ft_structure_id enumeration.
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.
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. ACTION Call the function with a valid, non-NULL source_filename.
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. service_class parameter.
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. quality_of_service parameter; the specified value is not within the Ft_qos enumeration.
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. ACTION Call the function with a valid class.
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.
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. MESSAGE FTE187_INV_ERASE_PASSWD CAUSE Invalid erase password; syntax is incorrect. ACTION Call the function with a valid Ft_single_file_pw.
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. MESSAGE FTE191_INV_FILESTORE_PASSWD CAUSE Invalid filestore_pw password; syntax is incorrect. ACTION Call the function with a valid Ft_single_file_pw.
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. MESSAGE FTE196_DIRNAME_NO_ADDR CAUSE The dirname parameter for ft_fdelete(), ft_frattributes(), or ft_fcattributes() has no associated presentation address.
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. MESSAGE FTE200_USR_CANC_DATA_TRAN CAUSE You canceled the data transfer.
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; returns on HLCF calls. ACTION Refer to the OSI Troubleshooting Guide.
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. ACTION Refer to the OSI Troubleshooting Guide.
FTAM return_codes inout_dcb->result.
2 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.
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.
HP vendor_codes inout_dcb->result.vendor_code inout_dcb->result.vendor_code MESSAGE FTV000_NO_ADDL_INFO CAUSE No additional information is available ACTION 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.
HP vendor_codes inout_dcb->result.vendor_code MESSAGE 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. ACTION Verify that applications are shutting down invocations when finished.
HP vendor_codes inout_dcb->result.vendor_code MESSAGE 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. ACTION Check the log file for logged error messages.
HP vendor_codes inout_dcb->result.vendor_code 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.
HP vendor_codes inout_dcb->result.vendor_code MESSAGE FTV301_ILLEGAL_CALL_IN_GROUP CAUSE You called an illegal function within a group. You requested an illegal call while grouping was open on a connection. ACTION 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.
HP vendor_codes inout_dcb->result.vendor_code MESSAGE FTV306_CANNOT_DECODE_DDN CAUSE The FTAM library cannot decode the directory distinguished name to a struct Dir_dn. ACTION Check the log file for logged error messages and recovery actions. If necessary, refer to the OSI Troubleshooting Guide. MESSAGE FTV307_INCOMPATIBLE_STACK CAUSE Your application was linked with a version of libmapftam.a which is not compatible with the underlying OSI network software (or “stack”).
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.
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. ACTION Check the inout_dcb->diagnostic; then call the function again.
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.
HP vendor_codes inout_dcb->result.vendor_code MESSAGE FTV416_NEG_CLOSE_CNF_ON_HLCF_REQ CAUSE The responder sent a negative confirmation on the close request within a HLCF call. ACTION Check the inout_dcb->diagnostic to determine the reason for the failure and call the function again. MESSAGE FTV417_NEG_DELETE_CNF_ON_HLCF_REQ CAUSE The responder sent a negative confirmation on the delete request within a HLCF call.
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.
HP vendor_codes inout_dcb->result.
3 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.
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. • To receive a printable character string, review the information in inout_dcb->diagnostic->further_details.
Diagnostic error_ids inout_dcb->diagnostic->error_id inout_dcb->diagnostic->error_id 3 8 10 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.
Diagnostic error_ids inout_dcb->diagnostic->error_id 11 1007 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 F_FTAM_PROTO_ERR CAUSE FTAM protocol error; may be one of the following reasons. • The parameter values could not be encoded. • You issued the calls in an incorrect order. ACTION Use the appropriate corrective action, as follows.
Diagnostic error_ids inout_dcb->diagnostic->error_id 1011 1015 2008 MESSAGE F_LWR_LAYER_FAIL CAUSE A layer below FTAM (e.g., Presentation or Session layer) caused or reported an error. Usually this error is indicated by an abort indication; FTAM returns abort information on this diagnostic after calling ft_ireceive(). ACTION Execute the netfmt utility to obtain log information and correct the error as described in the log message.
Diagnostic error_ids inout_dcb->diagnostic->error_id 2015 2020 3000 3002 72 MESSAGE F_INIT_ID_UNACCEPT CAUSE The login name (initiator identity) is unacceptable on an ft_connect() request. Either the name does not exist or your incorrectly entered it. ACTION Call the function with a valid initiator identity (i.e., an existing HP-UX login name). MESSAGE F_INVALID_FS_PASSWD CAUSE The filestore_pw is invalid. ACTION Call the function with a valid filestore_pw.
Diagnostic error_ids inout_dcb->diagnostic->error_id 3004 3005 3007 MESSAGE 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 F_FILE_ALREADY_EXISTS CAUSE You called ft_create() with file_status set to FT_NEW, and a file by that same name already exists in the filestore. ACTION Call ft_create() with a different filename.
Diagnostic error_ids inout_dcb->diagnostic->error_id 3010 MESSAGE 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. • The requested_access and concurrency_control parameters are not compatible.
Diagnostic error_ids inout_dcb->diagnostic->error_id 3016 MESSAGE 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. • The requested_access, conc_access, or file_passwords values do not match the access control element corresponding to your initiator identity.
Diagnostic error_ids inout_dcb->diagnostic->error_id 3028 4001 76 MESSAGE 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().
Diagnostic error_ids inout_dcb->diagnostic->error_id 4002 MESSAGE 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. • You tried to change a file's name to the name of a file that already exists. ACTION Use the appropriate corrective action, as follows.
Diagnostic error_ids inout_dcb->diagnostic->error_id 5014 5017 MESSAGE 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. For INTAP-1 document types, prim_type must be RECORD_END or RECORD_CONT.
Diagnostic error_ids inout_dcb->diagnostic->error_id 5023 5024 5026 MESSAGE 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().
Diagnostic error_ids inout_dcb->diagnostic->error_id 5027 5031 80 MESSAGE F_BAD_READ CAUSE The fadu_identity on an ft_read() request points to a non-existent FADU; therefore, you cannot read the file (FTAM-1, FTAM-3, and INTAP-1) or FADU (FTAM-2). ACTION Call ft_read() with a valid fadu_identity. For FTAM-1, FTAM-3, and INTAP-1 document types, fadu_identity must be FT_FIRST. For FTAM-2 document types, fadu_identity must be FT_BEGIN. MESSAGE F_LCL_FAIL_DVC_FAIL CAUSE Local device failure.
4 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().
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.
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). MESSAGE SUCCESS CAUSE Successful function execution (no error).
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; you provided a NULL pointer instead of a valid address for one of the parameters. The result->vendor_code indicates the return_event_name is invalid.
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; however, you did not call em_fdmemory() to free the memory after em_gperror() completed.
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; no action required.
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.
Event Management Errors EM vendor_codes 88 Chapter 4
5 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.
HP FTAM/9000 PICS 90 Chapter 5
6 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.
Installation Filesets Files Created During Software Installation Files Created During Software Installation Files in fileset FTAM Function /opt/ftam/bin/ftam Interactive interface executable /opt/ftam/bin/fcattr fcattr command /opt/ftam/bin/fcp fcp command /opt/ftam/bin/fdel fdel command /opt/ftam/bin/fls fls command /opt/ftam/bin/fmv fmv command /opt/ftam/bin/fchdoc Utility to change FTAM attributes of a local file /opt/ftam/sbin/osiinitshm OTS startup utility for FTAM /opt/ftam/sbin/osi
Installation Filesets Files Created During Software Installation Files in fileset FTAM Function /opt/ftam/lib/llib-lmap.ln lint library for FTAM programmatic interface /opt/ftam/lib/libmapftam.a Programmatic interface library definitions /opt/ftam/lib/llib-lmapftam lint library for FTAM programmatic interface /opt/ftam/lib/llib-lmapftam.ln lint library for FTAM programmatic interface /opt/ftam/lib/nls/C/acse.cat Network tracing and logging NLS catalog /opt/ftam/lib/nls/C/cm.
Installation Filesets Files Created During Software Installation Files in fileset FTAM Function /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 Network tracing and logging subformatter /opt/ftam/demos/Makefile Makefile for FTAM demo /opt/ftam/demos/README README file for FTAM demo /opt/ftam/demos/setup Set up of sample file /opt/ftam/demos/ftm_globs.
Installation Filesets Files Created During Software Installation Files in fileset OSIF-MAN 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 Man page for indicated function /opt/ftam/man/man1.Z/ftam_resp.
Installation Filesets Files Created During Software Installation Files in fileset OSIF-MAN 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.
Installation Filesets Files Created During Software Installation Files in fileset OSIF-MAN 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.
Installation Filesets Files Created During Software Installation 98 Chapter 6
7 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.
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.
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 ft_fclose(3) close and either deselect or delete an FTAM file ft_fcopy(3) copy an FTAM file ft_fcopy_aet(3) copy an FTAM file ft_fd
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 ftamrc(3) FTAM security file.
