FTAM/9000 Programmer's Guide

Chapter 5 245
Using High Level, Context Free Functions
Deleting Files (HLCF)
ft_fdelete_aet()
#include %</opt/ftam/include/map.h>
#include %</opt/ftam/include/mapftam.h>
Return_code
ft_fdelete_aet (ascii_ddn, filename, ae_label,
return_event_name, input_dcb, inout_dcb)
char *ascii_ddn;
Ft_filename filename;
Ae_label *ae_label;
Local_event_name return_event_name;
struct Ft_fdelete_in_dcb *input_dcb;
struct Ft_fdelete_out_dcb **inout_dcb;
The ft_fdelete_aet() function deletes files from the filestore. Once you
delete the file, you cannot recover it.
If the responder supports the conc_access field of struct
Ft_access_control_element, and the file has access control elements, and
an identity field matches the init_id, the input_dcb->concurrency_control
must be a subset of the values stored in the conc_access. HP-UX
responders do not support the conc_access field of struct
Ft_access_control_element.
Both ft_fdelete_aet() and ft_fdelete() are used for deleting files. However,
ft_fdelete_aet() sends both the Called AE Title and calling AE title to the
remote system while ft_fdelete() sends only the calling AE title. Also, in
ft_fdelete_aet(), the DDN is passed directly as an ASCII string without
any conversion while in ft_fdelete(), the DDN has to be converted and
passed as an Ae_dir_name.
Ft_fdelete_in_dcb
struct Ft_fdelete_in_dcb {
Ft_initiator_identity init_id;
Ft_single_file_pw filestore_pw;
Ft_single_file_pw delete_file_pw;
Ft_account account;
struct Ft_concurrency_control *concurrency_control;
};
Ft_fdelete_out_dcb
struct Ft_fdelete_out_dcb {
Uint32 size;
struct Api_rc result;
enum Ft_action_result action_result;
struct Ft_charging *charging;
struct Ft_diagnostic *diagnostic;
};