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


File systems in single system environments

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

Figure 1 shows what BPXPRMxx file system parameters would look like in a single system environment, and Figure 2 shows the corresponding single system image. SYSPLEX(NO) is specified (or the default taken), and the mount mode is read-only.

The root can be mounted either read-only or read/write.

Figure 1. BPXPRMxx parmlib member for a single system
BPXPRMxx

FILESYSTYPE
TYPE(ZFS)
ENTRYPOINT(IOEFSCM)
ASNAME(ZFS)

SYSPLEX(NO)

ROOT
FILESYSTEM('OMVS.ROOT.ZFS')
TYPE(ZFS) MODE(RDWR)

MOUNT
FILESYSTEM('OMVS.DEV.ZFS')
TYPE(ZFS) MODE(RDWR)
MOUNTPOINT('/dev')

MOUNT
FILESYSTEM('OMVS.TMP.ZFS')
TYPE(ZFS) MODE(RDWR)
MOUNTPOINT('/tmp')

MOUNT
FILESYSTEM('OMVS.VAR.ZFS')
TYPE(ZFS) MODE(RDWR))
MOUNTPOINT('/var')

MOUNT
FILESYSTEM('OMVS.ETC.ZFS')
TYPE(ZFS) MODE(RDWR)
MOUNTPOINT('/etc') 
Figure 2. Illustration of a single system A picture of a single system

The presence of symbolic links is transparent to the user. In the illustrations used throughout this section, symbolic links are indicated with an arrow.

In Figure 2, the root file system contains an additional directory, /SYSTEM; existing directories, /etc, /dev, /tmp and /var are converted into symbolic links. These changes, however, are transparent to the user who brings up a single system environment.

If the content of the symbolic link begins with $SYSNAME and SYSPLEX is specified NO, then $SYSNAME is replaced with /SYSTEM when the symbolic link is resolved.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014