16.12.2012 Views

z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

example, a network mount must be done), then the command will return<br />

with a return code indicating that an asynchronous mount is in progress.<br />

SECURITY|N<strong>OS</strong>ECURITY<br />

Specifies whether security checks are to be enforced for files in this file system.<br />

Note: When an z/<strong>OS</strong> <strong>UNIX</strong> file system is mounted with the N<strong>OS</strong>ECURITY<br />

option enabled, any new files or directories that are created will be<br />

assigned an owner of UID 0, no matter what UID issued the request.<br />

SECURITY<br />

Specifies that normal security checking will be done. SECURITY is the<br />

default.<br />

N<strong>OS</strong>ECURITY<br />

Specifies that security checking will not be enforced for files in this file<br />

system. A user may access or change any file or directory in any way.<br />

Security auditing will still be performed if the installation is auditing<br />

successes.<br />

MOUNT<br />

The SETUID, SETGID, APF, and Program Control attributes may be turned<br />

on in files in this file system, but they will not be honored while it is<br />

mounted with N<strong>OS</strong>ECURITY.<br />

SYSNAME (sysname)<br />

For systems participating in shared file system, SYSNAME specifies the<br />

particular system on which a mount should be performed. This system will then<br />

become the owner of the file system mounted. This system must be IPLed with<br />

SYSPLEX(YES). IBM recommends that you specify SYSNAME(&SYSNAME.)<br />

or omit the SYSNAME parameter. In this case, the system that processes the<br />

mount request mounts the file system and becomes its owner.<br />

sysname<br />

sysname is a 1–8 alphanumeric name of a system participating in shared<br />

file system.<br />

AUTOMOVE(indicator,sysname1,...,sysnameN)|NOAUTOMOVE|UNMOUNT<br />

These parameters apply only in a sysplex where systems are exploiting the<br />

shared file system capability. They specify what is to happens to the ownership<br />

of a file system when a shutdown, PFS termination, dead system takeover, or<br />

file system move occurs. The default setting is AUTOMOVE where the file<br />

system will be randomly moved to another system (no system list used).<br />

Indicator is either INCLUDE or EXCLUDE, which can also be abbreviated as I<br />

or E<br />

AUTOMOVE<br />

AUTOMOVE indicates that ownership of the file system can be<br />

automatically moved to another system participating in a shared file system.<br />

AUTOMOVE is the default.<br />

AUTOMOVE(INCLUDE,sysname1,sysname2,...,sysnameN) or<br />

AUTOMOVE(I,sysname1,sysname2,...,sysnameN)<br />

The INCLUDE indicator with a system list provides an ordered list of<br />

systems to which the file system's ownership could be moved. sysnameN<br />

may be a system name, or an asterisk (*). The asterisk acts as a wildcard<br />

to allow ownership to move to any other participating system and is only<br />

permitted in place of a system name as the last entry of a system list.<br />

Chapter 3. TSO/E commands 835

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!