The root file system should be set up so that it does not require
frequent changes or updates outside of SMP/E maintenance. To achieve
this, we will allocate an intermediate file system called OMVS.USERS
and mount it at /u.
All user directories that are added will reside in this new file
system and not in the root file system.
Example: Following is a sample JCL to allocate the intermediate
file system. Change the JCL to fit your environment.
//USERIDA JOB ,'Compatibility Mode',
// CLASS=A,MSGCLASS=X,MSGLEVEL=(1,1)
//DEFINE EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=H
//SYSUDUMP DD SYSOUT=H
//AMSDUMP DD SYSOUT=H
//DASD0 DD DISP=OLD,UNIT=3390,VOL=SER=ZFSVOL
//SYSIN DD *
DEFINE CLUSTER (NAME(OMVS.USERS) -
VOLUMES(ZFSVOL) -
LINEAR CYLINDERS(5 1) SHAREOPTIONS(3))
/*
//CREATE EXEC PGM=IOEAGFMT,REGION=0M,
// PARM=('-aggregate OMVS.USERS -compat -owner 11 -perms o755')
//SYSPRINT DD SYSOUT=H
//STDOUT DD SYSOUT=H
//STDERR DD SYSOUT=H
//SYSUDUMP DD SYSOUT=H
//CEEDUMP DD SYSOUT=H
...
The next thing to do is mount this new intermediate file system
at
/u. The mount can be performed from an ID that has superuser
authority by:
- Using the usr/sbin/mount REXX exec from the shell
- Using the TSO MOUNT command
- Using the mount shell command
- Using the ISHELL File_Systems pull-down
- Adding an entry to the BPXPRMxx member in SYS1.PARMLIB so that
it will be mounted when the system reIPLs.
An example of the commands required, including issuing the mount command
from the shell is shown in Figure 1.
Type OMVS from ISPF option 6 to enter the shell.
Then execute the highlighted commands to mount the file system OMVS.USERS.
In Figure 1, the user ID is ADMIN and it
has superuser authority.
Figure 1. Mounting the new
intermediate file system.
This figure shows an example
of the process to mount thef file system OMVS.USERS.IBM
Licensed Material - Property of IBM
5655-068 (C) Copyright IBM Corp. 1993, 1995
(C) Copyright Mortice Kern Systems, Inc., 1985, 1994
(C) Copyright Software Development Group, Univ. of Waterloo, 1989
U.S. Government users - RESTRICTED RIGHTS - Use, Duplication, or
Disclosure restricted by GSA-ADP schedule contract with IBM Corp.
IBM is a registered trademark of the IBM Corp.
- - - - - - - - - - - - - - - - - - - - - - - - - - -
- Improve performance by preventing the propagation -
- of TSO/E or ISPF STEPLIBs -
- - - - - - - - - - - - - - - - - - - - - - - - - - -
# /usr/sbin/mount /u omvs.users 1
OMVS.USERS is now mounted at
/u
# df -P 2
Filesystem 512-blocks Used Available Capacity Mounted
OMVS.USERS 7200 40 7160 1% /u
OMVS.ROOT 82800 79608 3192 97% /
# chmod 755 /u 3
===>
ESC=¢ 1=Help 2=SubCmd 3=HlpRetrn 4=Top 5=Bottom 6=TSO
7=BackScr 8=Scroll 9=NextSess 10=Refresh 11=FwdRetr 12=Retrieve
- 1 Use the mount command
to mount the file system, OMVS.USERS, on mount point /u.
- 2 Run the display free space command
to display the mounted file systems.
- 3 Change the permission bits to allow
access to /u.
Now that the OMVS.USERS file system is mounted at mount point
/u you
can create the user1 mount point from a superuser ID by using:
- The mkdir command in the shell
- The TSO/E MKDIR command
- The ISHELL Directory pull-down
Figure 2 shows the sequence of
commands performed by a superuser in the shell to create a mount point
for a new user off
/u. Before you begin, be sure that the new
user is defined to the OMVS segment that your security product uses.
Type in OMVS from ISPF option 6 to enter the shell and execute the
highlighted commands to create the mount point for
user1.
Figure 2. Creating a
mount point directory for a user.
This figure shows how
to create a mount point for a new user.# cd /u 1
# pwd 2
/u 3
# mkdir -m 700 user1 4
#ls -l 5
total 16
drwx------ 2 ADMIN OMVSGRP 0 Nov 7 09:07 user1 6
#
===>
ESC=¢ 1=Help 2=SubCmd 3=HlpRetrn 4=Top 5=Bottom 6=TSO
7=BackScr 8=Scroll 9=NextSess 10=Refresh 11=FwdRetr 12=Retrieve
- 1 Change to make /u your
current working directory.
- 2 Check to make sure /u is
the current working directory.
- 3 /u is the current working
directory.
- 4 Create a new directory for user1 setting
the permission bits to 700. See Controlling access to files and directories for
information about permission bit settings.
- 5 List the contents of the /u directory.
- 6 The user1 directory entry.
The user file system that was previously created can now be mounted
at
/u/user1. The mount can be performed by:
- Using the /usr/sbin/mount REXX exec from the shell
- Using the TSO/E MOUNT command
- Using the ISHELL File_systems pull-down
- Adding an entry to the BPXPRMxx member in SYS1.PARMLIB so that
it is remounted when the system reIPLs.
Figure 3 shows an example of the commands
required, including issuing the mount command from
the shell. Type OMVS from ISPF option 6 to enter the shell and execute
the highlighted commands to mount the file system OMVS.USER1.
Figure 3. Mounting the
new file system.
The sequence of commands needed to mount
the file system OMVS.USER1# /usr/sbin/mount /u/user1 omvs.user1 1
OMVS.USER1 is now mounted at
/u/user1
# df -P 2
Filesystem 512-blocks Used Available Capacity Mounted
OMVS.USER1 12960 40 12920 1% /u/user1
OMVS.ROOT 82800 79608 3192 97% /
# chown user1:grpoe /u/user1 3
# ls -l /u/user1 4
total 16
drwx------ 2 USER1 GRPOE 0 Nov 7 09:09 user1
#
===>
ESC=¢ 1=Help 2=SubCmd 3=HlpRetrn 4=Top 5=Bottom 6=TSO
7=BackScr 8=Scroll 9=NextSess 10=Refresh 11=FwdRetr 12=Retrieve
- 1 Issue the mount command
to mount the file system, OMVS.USER1, on mount point /u/user1.
- 2 Run the display free space command
to display the mounted file systems.
- 3 In order for USER1 to use this
new file system, you must issue the chown command
to change the ownership and to change the group to the user's default
group. Issue this command to set the owner and group fields of this
mount point directory for the USER1 ID. You only need to issue the chown command
once because the values will be saved in the new file system and will
be reused even when the file system is remounted later.
- 4 Issue a list command to display
the new directory for USER1.
To make the mounting of the OMVS.USERS and OMVS.USER1 file systems
permanent, add an entry in the BPXPRMxx member in SYS1.PARMLIB. These
two mount statements must follow the ROOT statement for the root file
system.
MOUNT FILESYSTEM('OMVS.USERS')
TYPE(ZFS)
MOUNTPOINT('/u')
MODE(RDWR)
MOUNT FILESYSTEM('OMVS.USER1')
TYPE(ZFS)
MOUNTPOINT('/u/user1')
MODE(RDWR)