Open System Services Management and Operations Guide (G06.30+, H06.08+, J06.03+)

The pathname described in MNTPOINT must be an existing directory, but the OSS Monitor
does not validate this until an attempt is made to start the fileset. Do not include symbolic links
in mount-point pathname specifications. Normalization of pathnames for mount points does
not include resolution of symbolic links.
If the MNTPOINT option is omitted, the mount-point directory for the fileset is not changed.
NAMESERVER servername
specifies the server name of the OSS name server that should administer the fileset. Only names
currently defined in the ZOSSSERV file are valid values.
The first character of the name must be a pound sign (#). Server names are not case-sensitive.
If the NAMESERVER option is omitted, the OSS name server process for the fileset is not
changed.
NFSPERMMAP { RESTRICTIVE | PERMISSIVE | UNMODIFIED | DISABLED }
(J06.09 and later J-series RVUs or H06.20 and later H-series RVUs only) Specifies how the
permissions for an OSS object protected by optional access control list (ACL) entries are mapped
to the permissions (rwxrwxrwx) used by Network File System Version 2 (NFS V2) clients on
open, read, write, and directory search operations. Write permissions are always enforced
on the NonStop server using the actual standard OSS permissions or OSS ACL permissions (if
present) on the object.
NOTE: Changing the NFSPERMMAP attribute on an OSS fileset in which NFS clients currently
have open files can confuse some NFS client software because the mapped NFS permissions
seen by the NFS client system might suddenly change. For example, buffered file library routines
that are successfully writing, then are denied by an NFSPERMMAP change, and then are
allowed by an NFSPERMMAP change, might return unexpected errors. Therefore, HP
recommends that the OSS administrator stop the NFS client software that is using an OSS fileset
before changing the NFSPERMMAP attribute of that fileset.
The attribute values for NFSPERMMAP are:
DescriptionValue
The other and owning group fields of the permissions bits returned to NFS V2 clients are
modified such that only access that would be granted to everyone in the ACL, excluding
the owner, is granted in the permissions bits. That is:
RESTRICTIVE
• The ACL entries for the class mask, the owning group, and all optional users are
examined. The group permissions returned to NFS V2 clients for this object are the
most restrictive of the permissions bits of these ACL entries.
• The ACL entries for the class mask, the owning group, other, all optional groups,
and all optional users are examined. The other permissions returned to NFS V2 clients
for this object are the most restrictive of the permissions bits of these ACL entries.
Setting NFSPERMAP to this value can cause some users on NFS V2 clients to be denied
access to objects to which they should legitimately be granted access according to the
OSS ACL on the NonStop server.
The other and owning group fields of the permissions bits returned to NFS V2 clients are
modified such that access that would be granted to anyone in the ACL, excluding the
owner, is granted in the permissions bits. That is:
PERMISSIVE
• The ACL entries for the class mask, the owning group, and all optional users are
examined. The group permissions returned to NFS V2 clients for this object are the
most permissive of the permissions bits, as allowed by the class mask, of these ACL
entries.
• The ACL entries for the class mask, the owning group, other, all optional groups,
and all optional users are examined. The other permissions returned to NFS V2 clients
for this object are the most permissive of the permissions bits for the other ACL entry
and, as allowed by the class mask, the ACL entries of the owning group, optional
groups, and optional users.
OSS Monitor SCF Command Reference Information 273