Where allowed to run: All environments (*ALL) Threadsafe: No |
Parameters Examples Error messages |
The Add Mounted File System (MOUNT) command makes the objects in a file system accessible to the integrated file system name space. The file system to be made accessible can be either a user-defined file system (*UDFS) on the local system, a remote file system accessed through local Network File System client (*NFS), or a local or remote NetWare file system (*NETWARE). The directory that is the destination for the mount, the Directory to mount over (MNTOVRDIR), must exist.
This command can also be issued using the following alternative command name:
For more information about Network File System commands, see Network File System book, SC41-5714
Restrictions:
Top |
Keyword | Description | Choices | Notes |
---|---|---|---|
TYPE | Type of file system | *NFS, *UDFS, *NETWARE | Required, Key, Positional 1 |
MFS | File system to mount | Path name | Required, Key, Positional 2 |
MNTOVRDIR | Directory to mount over | Path name | Required, Key, Positional 3 |
OPTIONS | Mount options | Character value, *DFT | Optional |
CCSID | Coded character set ID | Element list | Optional |
Element 1: Data file CCSID | 1-65533, *ASCII, *JOBCCSID, *BINARY | ||
Element 2: Path name CCSID | 1-65533, *ASCII, *JOBCCSID | ||
CODEPAGE | Code page | Element list | Optional |
Element 1: Data file code page | 1-32767, *ASCII, *JOBCCSID, *BINARY | ||
Element 2: Path name code page | 1-32767, *ASCII, *JOBCCSID |
Top |
Specifies the type of file system to be mounted. The type of mount determines the correct form for the File system to mount (MFS) parameter.
The name part of the path must be unique within the specified qaspXX or aspname directory.
Note: On the MFS parameter, if a relative context is specified that contains no dots and no path name after the colon, the user must be sure to quote the parameter value when prompting on the command. The command analyzer may interpret the MFS value as a label and remove the trailing colon.
This is a required parameter.
Top |
Specifies the path name of the file system to be mounted. It can be the path to a local Block Special File (*BLKSF), a remote NFS path name, or the path of a NetWare file system. See the Type of file system (TYPE) parameter to determine the correct format for the MFS parameter.
This is a required parameter.
Top |
Specifies the path name of the existing directory that the file system will be mounted over. This directory gets 'covered' by the mounted file system. This directory must exist.
Multiple file systems can be mounted over the same directory, one on top of the other. However, only the topmost mounted file system is accessible, and the file systems must later be unmounted in the opposite order from which they were mounted (last-in first-out order).
This is a required parameter.
Top |
The options list contains a character string of mount options. The options are separated by commas. For some options, an equal '=' and a value follow the option. If an option is not specified, the default value for that option will be used. The options list may contain spaces.
'rw,suid,rsize=8096,wsize=8096,timeo=20,retrans=5, acregmin=30,acregmax=60,acdirmin=30,acdirmax=60,hard'
The default value for the options string for the mount of a user-defined file system (*UDFS) is:
'rw,suid'
The default value for the options string for the mount of a NetWare file system (*NETWARE) is:
'rw,acregmax=60,acdirmax=60'
For the mount of a Network File System, all of the following options are valid. For the mount of a user-defined file system, only the ro, rw, suid and nosuid options are valid. For the mount of a NetWare file system, only the ro, rw, acregmax, acdirmax, noac, and nocto options are valid. If options are specified that are not valid for the file system type to be mounted, they are ignored.
Top |
Specifies, for Network File Systems, a pair of coded character set identifiers (CCSIDs) to identify a specific character representation to be used. The first CCSID specifies what encoding scheme should be assumed for data files on the remote system. The second CCSID specifies what encoding scheme should be assumed for path names on the remote system.
This parameter is only valid if mounting a Network File System.
Element 1: Data file CCSID
Element 2: Path name CCSID
Top |
Specifies, for Network File Systems, a pair of code pages. The first code page specifies what code page should be assumed for data files on the remote system. The second code page specifies what code page should be assumed for path names on the remote system.
This parameter is only valid if mounting a Network File System.
Note: This parameter is replaced by Coded character set ID (CCSID) but the CODEPAGE parameter can still be used. However, because this parameter may be removed in a later release, whenever possible use the CCSID parameter.
Element 1: Data file code page
Note: A code page that has the same number of bytes per character as the original data should be specified.
Element 2: Path name code page
Top |
The alternative command name for MOUNT is ADDMFS. The following examples use the alternative command name, but MOUNT can be replaced directly for ADDMFS in all of them.
Example 1: Mounting a User-Defined File System
ADDMFS TYPE(*UDFS) MFS('/DEV/QASP03/PROD1') MNTOVRDIR('DIRB')
This command mounts a user-defined file system PROD1 over the directory, DIRB. It uses the defaults for the other parameters.
Example 2: Mounting a Network File System
ADDMFS TYPE(*NFS) MFS('RAINFALL:/QSYS.LIB/RAY.LIB') MNTOVRDIR('/mystuff')
This command mounts the /qsys.lib/ray.lib file system from the remote system RAINFALL into the directory /mystuff.
Example 3: Mounting a Network File System with OPTIONS
ADDMFS TYPE(*NFS) MFS('RAINFALL:/QSYS.LIB/RAY.LIB') MNTOVRDIR('/mystuff') OPTIONS('ro,nosuid,rsize=256, retrans=10') CODEPAGE(*ASCII *JOBCCSID) CCSID(*ASCII *JOBCCSID)
This command mounts the /qsys.lib/ray.lib file system from the remote system RAINFALL into the directory /mystuff. In addition it specifies to mount as read-only, not allow setuid execution, set the read buffer to 256 bytes, and the retransmission attempts to 10. The job CCSID is used to determine the coded character set identifier to use for remote path names.
Example 4: Mounting a NetWare File System with OPTIONS
ADDMFS TYPE(*NETWARE) MFS('RCHNWSVR1/LOTUS:LOTSUITE/SMARTCTR') MNTOVRDIR('/temp1') OPTIONS('ro,agregmax=120')
This command mounts the NetWare directory LOTSUITE/SMARTCTR contained in the volume LOTUS that resides on server RCHNWSVR1 over the directory /temp1. In addition it specifies to mount as read-only, sets the maximum time to store file attributes locally to 120 seconds.
Example 5: Mounting using a NetWare Directory Services Context
Following are several examples of mounting a NetWare file system using NetWare Directory Services (NDS) contexts.
ADDMFS TYPE(*NETWARE) MFS('.LOTUS_VOL.ROCHESTER.IBM') MNTOVRDIR('/temp1')
This command mounts NDS volume LOTUS_VOL using a distinguished context, over the directory /temp1.
ADDMFS TYPE(*NETWARE) MFS('CN=LOTUS_VOL.OU=ROCHESTER:LOTSUITE/SMARTCTR') MNTOVRDIR('/temp1')
This command mounts path LOTSUITE/SMARTCTR on NDS volume LOTUS using a relative path and fully qualified names, over the directory /temp1.
ADDMFS TYPE(*NETWARE) MFS('.CN=LOTUSMAP.OU=ROCHESTER.O=IBM') MNTOVRDIR('/temp1')
This command mounts a directory map object using a distinguished context and fully qualified names, over the directory /temp1.
Top |
*ESCAPE Messages
Top |