Mounting the version file system

The version file system is the IBM-supplied root file system. To avoid confusion with the sysplex root file system, "root file system" has been renamed to "version file system".

Figure 1 shows a version file system.

Figure 1. What a version file system looks like

Guidelines: When mounting the version file system, keep these guidelines in mind.

Mount the version file system read-only in a sysplex environment, and designate it AUTOMOVE. The mount point for the version file system is dynamically created if the VERSION statement is used in BPXPRMxx.
&SYSNAME as one of the qualifiers for the version file system data set name. In Sysplex scenarios showing shared file system capability, REL9 and REL9A are used as qualifiers, which correspond to the system release levels. However, you do not necessarily have to use the same qualifiers. Other appropriate names are the name of the target zone, &SYSR1, or another qualifier meaningful to the system programmer.

IBM® supplies the version file system in ServerPac. CBPDO users obtain the version file system by following directions in the Program Directory. There is one version file system for each set of systems participating in a shared file system and who are at the same release level (that is, using the same SYSRES volume). In other words, each version file system denotes a different level of the system or a different service level. For example, if you have 20 systems participating in a shared file system, and 10 of those systems are at Release 9 and the other 10 are at Release 9A, then you'll have one version file system for the Release 9 systems and one for the Release 9A systems. In essence, you will have as many version file systems for the participating systems as you have different levels running.

Before you mount your version file system read-only, you might have some element-specific actions. These are described in Post-installation actions for mounting the root file system in read-only mode.