The following tables define field names and their usage. All field names relate directly to the
ADDGROUP and ALTGROUP keywords. Although the fields are alphabetized in the following tables, there
is no defined order in which fields are returned when using the extract functions. See z/OS Security Server RACF Command Language Reference for questions
pertaining to field usage and data. Note that within the command image generated internally, RACF® truncates long keywords to 12 characters.
Boolean and list fields are identified in the field name column.
Unless otherwise noted, a field is a character field by default. For
list fields, the list header field returned by the extract function
is also specified. Unless otherwise noted, all list fields are 1-dimensional.
Table 1. BASE segment fields
| Field name |
SAF field name |
Flag byte values |
ADDGROUP/ALTGROUP keyword reference, or LISTGROUP heading (for
output-only fields) |
Allowed on add requests |
Allowed on alter requests |
Returned on extract requests |
| CONNECTS |
|
N/A |
Note: This is the list header field for the 2-dimensional array consisting of the following two
fields.
|
No |
No |
Yes |
| GAUTH |
|
N/A |
ACCESS= |
No |
No |
Yes |
| GUSERID |
|
N/A |
USER(S)= |
No |
No |
Yes |
| CREATDAT |
|
N/A |
CREATED= |
No |
No |
Yes |
| DATA |
|
'Y' |
DATA(xx) |
Yes |
Yes |
Yes |
| 'N' |
NODATA |
No |
Yes |
| MODEL |
|
'Y' |
MODEL (xx) |
Yes |
Yes |
Yes |
| 'N' |
NOMODEL |
No |
Yes |
| OWNER |
|
'Y' |
OWNER(xx) |
Yes |
Yes |
Yes |
| SUBGROUP (list SUBGRPCT) |
|
N/A |
SUBGROUP(S)= |
No |
No |
Yes |
| SUPGROUP |
|
'Y' |
SUPGROUP(xx) |
Yes |
Yes |
Yes |
| TERMUACC (boolean) |
|
'Y' |
TERMUACC |
Yes |
Yes |
Yes |
| 'N' |
NOTERMUACC |
Yes |
Yes |
| UNIVERSL (boolean in output) |
|
'Y' |
UNIVERSAL |
Yes |
No |
Yes |
Table 2. CSDATA segment fields
| Field name |
SAF field name |
Flag byte values |
ADDGROUP/ALTGROUP keyword reference |
Allowed on add requests |
Allowed on alter requests |
Returned on extract requests |
| custom-keyword |
|
'Y' |
CSDATA (custom-keyword(xxx)) |
Yes |
Yes |
Yes |
| 'N' |
CSDATA (NOcustom-keyword) |
No |
Yes |
| A custom field (keyword and value type) is installation
specific. On extract requests the field descriptor mapping will contain the custom-keyword
and the associated data value. |
Table 3. DFP segment fields
| Field name |
|
Flag byte values |
ADDGROUP/ALTGROUP keyword reference |
Allowed on add requests |
Allowed on alter requests |
Returned on extract requests |
| DATAAPPL |
dataappl |
'Y' |
DFP(DATAAPPL(xx)) |
Yes |
Yes |
Yes |
| 'N' |
DFP(NODATAAPPL) |
No |
Yes |
Yes |
| DATACLAS |
dataclas |
'Y' |
DFP(DATACLAS(xx)) |
Yes |
Yes |
Yes |
| 'N' |
DFP(NODATACLAS) |
No |
Yes |
Yes |
| MGMTCLAS |
mgmtclas |
'Y' |
DFP(MGMTCLAS(xx)) |
Yes |
Yes |
Yes |
| 'N' |
DFP(NOMGMTCLAS) |
No |
Yes |
Yes |
| STORCLAS |
storclas |
'Y' |
DFP(STORCLAS(xx)) |
Yes |
Yes |
Yes |
| 'N' |
DFP(NOSTORCLAS) |
No |
Yes |
Yes |
Table 4. OMVS segment fields
| Field name |
SAF field name |
Flag byte values |
ADDGROUP/ALTGROUP keyword reference |
Allowed on add requests |
Allowed on alter requests |
Returned on extract requests |
| AUTOGID |
|
'Y' |
OMVS(AUTOGID) |
Yes |
Yes |
No |
| GID |
gid |
'Y' |
OMVS(GID(xx)) |
Yes |
Yes |
Yes |
| 'N' |
OMVS(NOGID) |
No |
Yes |
| SHARED |
|
'Y' |
OMVS(SHARED) |
Yes |
Yes |
No |
Table 5. OVM segment fields
| Field name |
SAF field name |
Flag byte values |
ADDGROUP/ALTGROUP keyword reference |
Allowed on add requests |
Allowed on alter requests |
Returned on extract requests |
| GID |
|
'Y' |
OVM(GID(xx)) |
Yes |
Yes |
Yes |
| 'N' |
OVM(NOGID) |
No |
Yes |
Table 6. TME segment fields
| Field name |
SAF field name |
Flag byte values |
ADDGROUP/ALTGROUP keyword reference |
Allowed on add requests |
Allowed on alter requests |
Returned on extract requests |
| ROLES |
|
'Y' |
TME(ROLES(xx ...)) |
Yes |
Yes |
Yes |
| 'A' |
TME(ADDROLES(xx ...)) |
No |
Yes |
| 'D' |
TME(DELROLES (xx ...)) |
No |
Yes |
| 'N' |
TME(NOROLES) |
No |
Yes |