OSF DCE Administration Guide--Core Components

Creating and Using Extended Registry Attributes
TABLE 32-1. Options to Create Extended Attributes
___________________________________________________________________________
Option Meaning
___________________________________________________________________________
___________________________________________________________________________
A required list of the ACL manager types that support the
objects to which this attribute type can be attached and the
permissions supported by those managers. No default.
Attribute type ACL managers are described fully in Section
32.2.5.
-aclmgr description
___________________________________________________________________________
A PCS text string that annotates the attribute type. If the
string contains spaces, enclose it in braces or quotes. The
default is blank.
-annotation string
___________________________________________________________________________
This option is not currently implemented.-applydefs
___________________________________________________________________________
The format of the attribute type instance value. Attribute
encoding is described more fully in Section 32.2.6.
-encoding type
___________________________________________________________________________
This option is not currently implemented.-intercell
___________________________________________________________________________
An indication of whether or not the attribute is multivalued
(yes=multivalued; no=not multivalued). If an attribute is
multivalued, multiple instances of the same attribute type can
be attached to a single registry object. For example, if
attribute A is coded as multivalued, a single principal can
have multiple instances of attribute A. If it is not coded as
multivalued, a single principal can have only one instance of
attribute A. The default is no .
-multivalued {yes | no}
___________________________________________________________________________
An indication of whether or not the attribute is reserved
(yes=reserved; no=not reserved). Reserved attribute types
cannot be deleted unless the reserved restriction is removed.
The default is no.
-reserved {yes | no}
___________________________________________________________________________
Not implemented in the current release.-scope name
___________________________________________________________________________
Identifies whether or not a trigger server is associated with the
attribute type and, if a trigger server is associated, the type of
trigger. Possible values are the following:
none—A trigger server is not associated with the attribute
type.
query—A query trigger server is associated with the attribute
type.
update—An update trigger server is associated with the
attribute type.
If the -trigtype option is set to query or update, you must
supply the -trigbind option to specify the trigger server’s
binding. See Section 32.3 for more information.
-trigtype type
___________________________________________________________________________
If a trigger server is associated with the attribute type, this
option specifies the trigger serving binding.
-trigbind binding
___________________________________________________________________________
124243 Tandem Computers Incorporated 32−3