Operators
The following operators can be used to tell RACF how a trait should be processed by add and alter oprations.
Operators are specified using the format <operator>:<segment>:<trait>
, where the <operator>
token is the Operator, the <segment>
token is the RACF Segment, and the <trait>
token is the Trait.
When NO Operator is Explicitly specified,
"set"
will be the assumed Operator when the corresponding Trait value is NOTnull
, and"delete"
when the when the corresponding Trait value isnull
. The only exception is forboolean
Traits, which requires the"delete"
Operator to be specified Explicitly when providing anull
value. It is recommended to omit Operators when possible to keep the specification of Traits in"add"
and"alter"
Operations concise.
Every Operator is not supported for every Trait. Check the corresponding Trait Table to see what Operators are supported for a given Trait.
Operator | Description |
"set" | Set A Trait to a value. |
"add" | Add one or more items to a string array Trait. |
"remove" | Remove one or more items from a string array Trait. |
"delete" | Delete the existing value for a Trait if there is one. |
💻 Examples
The following RACFu Trait JSON describes modifications to the following User Traits:
- Set the OMVS UID to
24
. - Add
FACILITY
andXFACILIT
to the Class Authorizations list. - Remove
TERMINAL
from the Class Authorizations list. - Delete the existing value for TSO User Data if there is one.
JSON
{
"set:omvs:uid": 24,
"add:base:class_authorization": ["FACILITY", "XFACILIT"],
"remove:base:class_authorization": "TERMINAL",
"delete:tso:user_data": null
}
The following RACFu Trait JSON describes modifications to the following User Traits Without the use of Operators:
- Set the OMVS UID to
24
. - Delete the existing value for TSO User Data if there is one.
JSON
{
"omvs:uid": 24,
"tso:user_data": null
}