FILESYSTYPE

The FILESYSTYPE statement defines the type of physical file system to be used.

When you specify SYSPLEX(YES), you must define the file system type for all systems participating in a shared file system. The easiest way to define it is to have a single BPXPRMxx member that contains file system information for each system participating in a shared file system. If, however, you decide to define a BPXPRMxx for each system, the FILESYSTYPE statement must be identical on each system. See Customizing BPXPRMxx for a shared file system for more information about configuring BPXPRMxx in a sysplex.

Tip: To facilitate migrating file systems from HFS to zFS, some steps are taken to support existing mount commands that were not changed after the HFS data set that was mounted was converted to zFS file system. When you specify either ZFS or HFS, the selection that is made depends on the type of the file system that is found.
  • If you specify TYPE(HFS), a search is done for a data set that matches the file system name.
    • If the data set is found and it is not an HFS data set, the type is changed to ZFS.
    • If a data set is not found, the type is changed to ZFS in case the file system is a zFS file system such as a cloned file system.
    In both cases, the mount proceeds as though TYPE(ZFS) had been specified. However, any PARM string that was specified is ignored.
  • If you specify TYPE(ZFS) and it is an HFS data set, then the type is changed to HFS. The mount proceeds as though TYPE(HFS) had been specified. However, any PARM string that was specified is ignored.
Requirement: Facilities required for a particular file system must be initiated on that system. For example, NFS requires TCP/IP, so, if you specify a file system type of NFS, you must also initialize TCP/IP when you initialize NFS, even if there is no network connection.
Table 1 lists some types of physical file systems (TYPE parameter) and module names (ENTRYPOINT parameter).
Table 1. Types of file systems. The table lists the file system type and the corresponding module name.
File system type Description Module name
AUTOMNT Handles automatic mounting and unmounting of file systems.

The AUTOMNT file system is mounted as AUTOMOVE(YES). However, if the parent file system has the automove unmount attribute, then the automount file system will have that attribute instead of AUTOMOUNT(YES).

 BPXTAMD
CINET Handles requests for the AF_INET and AF_INET6 family of sockets. This enables many different AF_INET or dual AF_INET/AF_INET6 physical file systems to be active on the system. See Setting up for sockets for information about setting up sockets.

If you want to use CINET, you must be using z/OS® Communications Server (TCP/IP Services).

If you use CINET, you cannot use INET.

 BPXTCINT
HFS Processes file system requests. The HFS statement is necessary if you want to use regular local files. GFUAINIT
INET Handles requests for the AF_INET and AF_INET6 family of sockets. You must be using z/OS Communication Services (TCP/IP Services).

If you use INET, you cannot use CINET.

 EZBPFINI
NFS Handles Network File System requests for access to remote files.

For NFS Client you must create a procedure to run a PFS in a colony address space. For more information, see z/OS Network File System Guide and Reference. You can also find information in Running a physical file system in a colony address space.

GFSCINIT
TFS Handles requests to the temporary file system (TFS). BPXTFS
UDS Handles socket requests for the AF_UNIX address family of sockets. BPXTUINT
ZFS Handles z/OS File System requests. IOEFSCM