Ft_attribute

typedef Uint16 Ft_attribute_groups;

Ft_attribute_groups Is Input To These Functions	Ft_attribute_groups Is Output From These Functions
ft_connect()	ft_connect()

Ft_attribute_groups specifies the level of support for attributes.

Attributes are grouped as either kernel, storage, security, or private.

The kernel attributes are always present (i.e., you do not negotiate them).
Attributes within the storage, security, and private groups are valid only if you negotiate that group during ft_connect().
Response to an attribute value request (e.g., ft_cattributes()) always includes one of the following items:
- If you request an unnegotiated attribute, the response includes no value available and an error (result_code); may optionally include a diagnostic.
- If the HP-UX responder partially supports the attribute, the value (zero (0) for integers; "no value available" for strings) indicates that there is no value available.
- If the HP-UX responder fully supports the attribute, actual values are returned.
For ft_rattributes() and ft_frattributes(), the attribute_names field defaults to indicate all attributes in the attribute_ groups negotiated on the ft_connect() request.

The available attribute groups and their associated attributes are as follows:

Kernel Group	Provides basic attributes that are always available. filename permitted_actions contents_type
Storage Group	Provides additional information on how the file is stored. storage_account * ¹ date_time_of_creation date_time_of_modification date_time_of_read date_time_of_attribute_mod¹ identity_of_creator identity_of_modifier¹ identity_of_reader¹ identity_of_attribute_mod¹ file_availability * filesize future_filesize *¹ ¹ When these values are output from HP-UX FTAM responders, the value (zero (0) for integers; "no value available" for strings) signifies there is no value for the attribute.
Security Group	Allows FTAM to enforce what users may operate on the file and what access each user has. access_control legal_qualification *
Private Group	ISO does not define the private attributes group. private_use *

* HP-UX responders accept, but ignore, these values.

To set attribute groups, use the FT_AG_xxx defined constants in the mapftam.h file.

Ft_attribute_groups