 |
» |
|
|
 |
Use ft_frattributes() and ft_frattributes_aet to read file
attributes, and ft_fcattributes() and ft_fcattributes_aet() to change
file attributes by making only one call. ft_frattributes() |  |
#include %</opt/ftam/include/map.h> #include %</opt/ftam/include/mapftam.h> Return_code ft_frattributes (dirname, filename, ae_label, return_event_name, input_dcb, inout_dcb) Ae_dir_name dirname; Ft_filename filename; Ae_label *ae_label; Local_event_name return_event_name; struct Ft_frattributes_in_dcb *input_dcb; struct Ft_frattributes_out_dcb **inout_dcb; |
Use ft_frattributes() to read file attributes. Examples of
using ft_frattributes() are as follows. You might want to use ft_frattributes() to determine the creation
dates when a deleting files older than a specific date. Another
example of using ft_frattributes() is to know how to set destination
file attributes when copying files with low level calls. 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. The input_dcb->attribute_names field defaults to
indicate all attributes in the attribute_groups negotiated. You must supply matching passwords in input_dcb->file_passwords
for FT_FA_READ and FT_FA_READ_ATTRIBUTE file actions if the following
conditions exist. If the file contains an identity (in
Ft_access_control_element) that matches the init_id AND If passwords exist for these file actions
HP-UX responders set storage_account, future_filesize,
legal_qualifications, and private_use so that the indication no
value available (0) returns when you invoke ft_frattributes().
struct Ft_frattributes_in_dcb { Ft_initiator_identity init_id; Ft_single_file_pw filestore_pw; struct Ft_file_passwords file_passwords; Ft_attribute_names attribute_names; Ft_account account; struct Ft_concurrency_control *concurrency_control; }; |
struct Ft_frattributes_out_dcb { Uint32 size; struct Api_rc result; enum Ft_action_result action_result; struct Ft_attributes attributes; struct Ft_charging *charging; struct Ft_diagnostic *diagnostic; }; |
ft_frattributes() Parametersft_fcattributes() |  |
#include %</opt/ftam/include/map.h> #include %</opt/ftam/include/mapftam.h> Return_code ft_fcattributes (dirname, filename, ae_label, return_event_name, input_dcb, inout_dcb) Ae_dir_name dirname; Ft_filename filename; Ae_label *ae_label; Local_event_name return_event_name; struct Ft_fcattributes_in_dcb *input_dcb; struct Ft_fcattributes_out_dcb **inout_dcb; |
Use ft_fcattributes() to change file attributes. For example,
you can change an attribute such as access_control to place file
access restrictions on a specific user. The attribute_groups negotiated dictate
the attributes you can change.
* HP-UX responders accept, but ignore, these values. 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. You must supply matching passwords in input_dcb->file_passwords
for FT_FA_READ and FT_FA_CHANGE_ATTRIBUTE file actions if the following
conditions exist. If the file contains an identity (in
Ft_access_control_element) that matches the init_id AND If passwords exist for these file actions
struct Ft_fcattributes_in_dcb { Ft_initiator_identity init_id; Ft_single_file_pw filestore_pw; struct Ft_file_passwords file_passwords; Ft_attribute_names attribute_names; struct Ft_attributes attributes; Ft_account account; struct Ft_concurrency_control *concurrency_control; }; |
struct Ft_fcattributes_out_dcb { Uint32 size; struct Api_rc result; enum Ft_action_result action_result; struct Ft_attributes attributes; struct Ft_charging *charging; struct Ft_diagnostic *diagnostic; }; |
ft_fcattributes() Parametersft_frattributes_aet() |  |
#include %</opt/ftam/include/map.h> #include %</opt/ftam/include/mapftam.h> Return_code ft_frattributes_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_frattributes_in_dcb *input_dcb; struct Ft_frattributes_out_dcb **inout_dcb; |
Use ft_frattributes_aet() to read file attributes. Examples
of using ft_frattributes_aet() are as follows. You might want to use ft_frattributes_aet() to determine the
creation dates when a deleting files older than a specific date.
Another example of using ft_frattributes_aet() is to know how to
set destination file attributes when copying files with low level
calls. Both ft_frattributes_aet() and ft_frattributes()
are used for reading file attributes. However, ft_frattributes_aet()
sends both the Called AE Title and calling AE title to the remote
system while ft_frattributes() sends only the calling AE title.
Also, in ft_frattributes_aet(), the DDN is passed directly as an
ASCII string without any conversion while in ft_frattributes(),
the DDN has to be converted and passed as an Ae_dir_name. 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. The input_dcb->attribute_names field defaults to
indicate all attributes in the attribute_groups negotiated. You must supply matching passwords in input_dcb->file_passwords
for FT_FA_READ and FT_FA_READ_ATTRIBUTE file actions if the following
conditions exist. If the file contains an identity (in
Ft_access_control_element) that matches the init_id AND If passwords exist for these file actions
HP-UX responders set storage_account, future_filesize,
legal_qualifications, and private_use so that the indication no
value available (0) returns when you invoke ft_frattributes_aet().
struct Ft_frattributes_in_dcb { Ft_initiator_identity init_id; Ft_single_file_pw filestore_pw; struct Ft_file_passwords file_passwords; Ft_attribute_names attribute_names; Ft_account account; struct Ft_concurrency_control *concurrency_control; }; |
struct Ft_frattributes_out_dcb { Uint32 size; struct Api_rc result; enum Ft_action_result action_result; struct Ft_attributes attributes; struct Ft_charging *charging; struct Ft_diagnostic *diagnostic; }; |
ft_frattributes_aet() Parametersft_fcattributes_aet() |  |
#include %</opt/ftam/include/map.h> #include %</opt/ftam/include/mapftam.h> Return_code ft_fcattributes_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_fcattributes_in_dcb *input_dcb; struct Ft_fcattributes_out_dcb **inout_dcb; |
Use ft_fcattributes_aet() to change file attributes. For example,
you can change an attribute such as access_control to place file
access restrictions on a specific user. Both ft_fcattributes_aet() and ft_fcattributes()
are used for changing file attributes. However, ft_fcattributes_aet()
sends both the Called AE Title and calling AE title to the remote
system while ft_fcattributes() sends only the calling AE title.
Also, in ft_fcattributes_aet(), the DDN is passed directly as an
ASCII string without any conversion while in ft_fcattributes(),
the DDN has to be converted and passed as an Ae_dir_name. The attribute_groups negotiated dictate the attributes
you can change.
* HP-UX responders accept, but ignore, these values. 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. You must supply matching passwords in input_dcb->file_passwords
for FT_FA_READ and FT_FA_CHANGE_ATTRIBUTE file actions if the following
conditions exist. If the file contains an identity (in
Ft_access_control_element) that matches the init_id AND If passwords exist for these file actions
struct Ft_fcattributes_in_dcb { Ft_initiator_identity init_id; Ft_single_file_pw filestore_pw; struct Ft_file_passwords file_passwords; Ft_attribute_names attribute_names; struct Ft_attributes attributes; Ft_account account; struct Ft_concurrency_control *concurrency_control; }; |
struct Ft_fcattributes_out_dcb { Uint32 size; struct Api_rc result; enum Ft_action_result action_result; struct Ft_attributes attributes; struct Ft_charging *charging; struct Ft_diagnostic *diagnostic; }; |
ft_fcattributes_aet() Parameters
|