AFTP Return Codes

These are the possible return codes that can be issued for each AFTP API call.

AFTP_RC_BUFFER_TOO_SMALL

The buffer supplied by the caller for output data was too small to hold the data.

AFTP_RC_COMM_CONFIG_LOCAL

The call failed due to a local configuration error. Communications will fail until the configuration problem is resolved.

AFTP_RC_COMM_CONFIG_REMOTE

The call failed due to a remote configuration error. Communications will fail until the configuration problem is resolved.

AFTP_RC_COMM_FAIL_NO_RETRY

The call failed due to a communications problem. The call will not successfully complete using the current parameters.

AFTP_RC_COMM_FAIL_RETRY

The call failed due to a communications problem. The call might successfully complete if tried again.

AFTP_RC_FAIL_FATAL

A serious system error has occurred. No calls can complete successfully.

AFTP_RC_FAIL_INPUT_ERROR

The call might successfully complete after new input parameters are supplied.

AFTP_RC_FAIL_NO_RETRY

The call will not successfully complete using the current parameters.

AFTP_RC_FAIL_RETRY

The call might successfully complete if tried again.

AFTP_RC_HANDLE_NOT_VALID

The call failed because the AFTP connection object passed into the AFTP API was not valid.

AFTP_RC_OK

The call completed successfully.

AFTP_RC_PARAMETER_CHECK

The call failed due to an error in one of the parameters passed into the AFTP API.

AFTP_RC_PROGRAM_INTERNAL_ERROR

The call failed due to a programming error.

AFTP_RC_SECURITY_NOT_VALID

The call failed because of APPC security.

AFTP_RC_STATE_CHECK

The call failed because the current AFTP API call was made when AFTP was not in the state required for the call. For example, you will get a state check error if you try to use aftp_format_error when no error has occurred.