.TH mmlinkfileset 02/16/06
mmlinkfileset Command
.SH "Name"
.PP
\fBmmlinkfileset\fR - Creates a junction that references the root
directory of a GPFS fileset.
.SH "Synopsis"
.PP
\fBmmlinkfileset\fR \fIDevice\fR \fIFilesetName\fR
\fB[-J\fR \fIJunctionPath\fR\fB]\fR
.SH "Description"
.PP
The \fBmmlinkfileset\fR command creates a junction at
\fIJunctionPath\fR that references the root directory of
\fIFilesetName\fR. The junction is a special directory entry, much
like a POSIX hard link, that connects a name in a directory of one fileset,
the parent, to the root directory of a child fileset. From the
user's viewpoint, a junction always appears as if it were a directory,
but the user is not allowed to issue the \fBunlink\fR or \fBrmdir\fR
commands on a junction. Instead, the
\fBmmunlinkfileset\fR command must
be used to remove a junction.
.PP
If \fIJunctionPath\fR is not specified, the junction is created in the
current directory with the name \fIFilesetName\fR. The user may use
the \fBmv\fR command on the directory to move to a new location in the
parent fileset, but the \fBmv\fR command is not allowed to move the
junction to a different fileset.
.PP
For information on GPFS filesets, see the chapter
\fIPolicy-based data management for
GPFS\fR in
\fIGeneral Parallel File
System: Advanced Administration Guide\fR.
.SH "Parameters"
.PP
.RS +3
\fB\fIDevice\fR
\fR
.RE
.RS +9
The device name of the file system that contains the fileset.
.PP
File system names need not be fully-qualified. \fBfs0\fR is as
acceptable as \fB/dev/fs0\fR.
.RE
.PP
.RS +3
\fB\fIFilesetName\fR
\fR
.RE
.RS +9
Specifies the name of the fileset to be linked. It must not already
be linked into the namespace.
.RE
.PP
.RS +3
\fB-J \fIJunctionPath\fR
\fR
.RE
.RS +9
Specifies the name of the junction. The name must not already
exist, and must not already be linked into the namespace. The name must
not already exist, and must not already be linked into the namespace. 
.PP
A junction is a special directory entry that connects a name in a directory
of one fileset to the root directory of another fileset.
.RE
.SH "Exit status"
.PP
.PP
.RS +3
\fB0
\fR
.RE
.RS +9
Successful completion.
.RE
.PP
.RS +3
\fBnonzero
\fR
.RE
.RS +9
A failure has occurred.
.RE
.SH "Security"
.PP
You must have root authority to run the \fBmmlinkfileset\fR
command.
.PP
You may issue the \fBmmlinkfileset\fR command from any node in the GPFS
cluster.
.PP
When using the \fBrcp\fR and \fBrsh\fR commands for remote
communication, a properly configured \fB.rhosts\fR file must exist
in the root user's home directory on each node in the GPFS
cluster. If you have designated the use of a different remote
communication program on either the
\fBmmcrcluster\fR
or the
\fBmmchcluster\fR command, you must
ensure:
.RS +3
.HP 3
1. Proper authorization is granted to all nodes in the GPFS cluster.
.HP 3
2. The nodes in the GPFS cluster can communicate without the use of a
password, and without any extraneous messages.
.RE
.SH "Examples"
.PP
This command links fileset \fBfset1\fR in file system \fBgpfs1\fR to
junction path \fB/gpfs1/fset1\fR:
.sp
.nf
mmlinkfileset gpfs1 fset1 -J /gpfs1/fset1
.fi
.sp
.PP
The system displays output similar to: 
.sp
.nf
Fileset 'fset1' linked at '/gpfs1/fset1'.
.fi
.sp
.PP
To confirm the change, issue this command:
.sp
.nf
mmlsfileset gpfs1
.fi
.sp
.PP
The system displays output similar to: 
.sp
.nf
Filesets in file system 'gpfs1':
Name                     Status    Path\ 
root                     Linked    /gpfs1\ 
fset1                    Linked    /gpfs1/fset1
.fi
.sp
.SH "See also"
.PP
mmchfileset Command
.PP
mmcrfileset Command
.PP
mmdelfileset Command
.PP
mmlsfileset Command
.PP
mmunlinkfileset Command
.SH "Location"
.PP
\fB/usr/lpp/mmfs/bin\fR
.PP