Outbound owner and owner_group attributes processing

Outbound owner and owner_group attributes may be present in:

Owner and owner_group attributes can be sent to the client in the form of:

Translation of UID, GID to owner and owner_group attributes uses (in the following order):

For invalid translation z/OS NFS server uses numeric string representation for outbound owner and owner_group attributes.

Special strings "nobody" and "root" generation :

If UID is equal to the stored uid of "nobody", z/OS NFS server maps it to anonymous owner string using the default "nobody" name.
If GID is equal to the stored gid of "nobody", z/OS NFS server maps it to anonymous owner_group string using the same default "nobody" name.
If UID is equal to 0, z/OS NFS server maps it to superuser owner string using default "root" name.
If GID is equal to 0, z/OS NFS server maps it from RACF cache and derives the group name from the RACF database.

z/OS NFS server uses internal z/OS NFS server uid and gid cache and RACF database to find user/group names and their UIDs/GIDs.

During mapping inbound owner and owner_group attributes to numeric identifiers:

During mapping numeric identifiers to outbound owner and owner_group attributes:

The z/OS NFS server searches for the numeric identifier (UID or GID) in internal z/OS NFS server cache.
If the numeric identifier is found in z/OS NFS server cache then there is no reason to obtain it from the RACF database (invalid translation uses numeric string representation).
Otherwise the z/OS NFS server attempts to obtain a name by numeric identifier from the RACF database.
If the name is not found in the RACF database, the z/OS NFS server puts numeric identifier into internal z/OS NFS server cache and uses the numeric string representation.