A file system can only be exported by the Distributed File System (DFS) or Server Message Block (SMB) server at the system that owns the file system. Once a file system has been exported by DFS, it cannot be moved until it has been unexported by DFS. The same holds true of file systems exported by SMB.

To recover from system outages, you need to weigh sysplex availability against availability to the DFS and SMB clients. When an owning system is recycled and an exported file system has been taken over by one of the other systems, that file system will not be automatically reexported. The file system will have to be moved from its current owner back to the original system, the one that has just been recycled, and then reexported.

For file systems that are mostly for use by DFS or SMB servers, consider specifying NOAUTOMOVE on the MOUNT statement in the BPXPRMxx parmlib member. If you specify NOAUTOMOVE, the file systems will not be taken over if the system is recycled, and they will be available for automatic reexport by DFS.

In order for either the DFS or SMB server to move file systems to itself when they are not owned locally, the following server configuration option can be specified: _IOE_MOVE_SHARED_FILESYSTEM=ON.