z/OS Distributed File Service zSeries File System Implementation z/OS V1R13

An IBM Redbooks publication

Published 18 October 2012

cover image

ISBN-10: 0738436402
ISBN-13: 9780738436401
IBM Form #: SG24-6580-05
(518 pages)

More options

Rate and comment

Authors: Paul Rogers, Robert Hering


The z/OS® Distributed File Service zSeries® File System (zFS) is a z/OS UNIX® file system that can be used like the Hierarchical File System (HFS). zFS file systems contain files and directories, including Access Control Lists (ACLs), that can be accessed with the z/OS HFS application programming interfaces (APIs).

zFS file systems can be mounted into the z/OS UNIX hierarchy along with other local or remote file system types (for example, HFS, TFS, AUTOMNT, NFS, and so on). zFS does not replace HFS, but it is the z/OS UNIX strategic file system and IBM® recommends migrating HFS file systems to zFS. Beginning with z/OS V1R7, there are no restrictions for file system structures that should be kept as HFS instead of zFS.

This IBM Redbooks® publication helps you to install, tailor, and configure new zFS file systems. This information can be used by system administrators who work with the zFS component of the IBM z/OS Distributed File Service base element.

The book provides a broad description of the new architecture of the zFS file system for all releases up to zFS V1R13. You can use it as a reference when converting HFS file systems to zFS file systems. It will help you to create a solution for migrating to zFS file systems, and to understand the performance differences between HFS file systems and zFS file systems.

Table of contents

Chapter 1. zFS file systems
Chapter 2. Installing and using zFS file systems
Chapter 3. Migrating to zFS
Chapter 4. Backup and recovery
Chapter 5. Sysplex considerations
Chapter 6. Performance and tuning
Chapter 7. Domino performance with zFS
Appendix A. zFS configuration file sample
Appendix B. REXX utility procedures
Appendix C. JCL samples
Appendix D. zFS performance data

Others who read this publication also read

Follow IBM Redbooks

Follow IBM Redbooks