z/OS UNIX System Services Planning
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Moving file systems in a sysplex

z/OS UNIX System Services Planning
GA32-0884-00

You might need to change ownership of the file system for recovery or reIPLing.

Tips: When working with file systems in a sysplex, consider these tips:
  • To check for file systems that have already been mounted, use the df command from the shell.
  • To move a file system in a sysplex, use the SETOMVS command used with the FILESYS, FILESYSTEM, mount point and SYSNAME parameters. You can also use the chmount command from the shell. However, do not move these two types of file systems:

    System-specific file systems

    File systems that are being exported by DFS. You have to unexport them from DFS first and then move them

Examples: These examples assume you are working with file systems in a sysplex.
  1. To move ownership of the file system that contains /u/wjs to SY1:
    chmount -d SY1 /u/wjs
  2. To move ownership of the payroll file system from the current owner to SY2 using SETOMVS, issue:
    SETOMVS FILESYS,FILESYSTEM='POSIX.PAYROLL.ZFS',SYSNAME=SY2
    or (assuming the mount point is over directory /PAYROLL)
    SETOMVS FILESYS,mountpoint='/PAYROLL',SYSNAME=SY2 

If you mount a system-specific file system on other than the correct (system-specific) owner, either explicitly or due to AUTOMOVE=YES, loss of function might occur. For example, if the system-specific file system mounted at /dev for SY1 is moved to SY2 so that ownership is now SY2, the OMVS command on SY1 will fail.

Also, opened FIFO files are automatically closed before the file system containing the FIFO is moved. They are closed because the in-storage FIFO data on the old system is not moved and is no longer accessible on new owning system.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014