Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Scenario 3: Multiple systems in a sysplex using different release levels z/OS UNIX System Services Planning GA32-0884-00 |
|
If your participating group is in a sysplex that runs multiple levels of z/OS, your configuration might look like the one in Figure 2. In that configuration, each system is running a different level of z/OS and, therefore, has different version file system data sets; SY1 has the version file system named OMVS.SYSR9A.ROOT.ZFS and SY2 has the version file system named OMVS.SYSR9.ROOT.ZFS. Figure 1 shows two BPXPRMxx parmlib members that define the file systems in this configuration. Figure 3 shows a single BPXPRMxx parmlib member that can be used to define this same configuration; it uses &SYSR1. as the symbolic name for the two version file system data sets. Figure 1. BPXPRMxx setup for
multiple systems sharing file systems and using different release
levels
Figure 2. Sharing file systems between
multiple systems using different release levels
In this scenario, for example, if ls –l /bin/ is issued on SY1, the user expects to see the contents of /bin. However, because /bin is a symbolic link pointing to $VERSION/bin, the symbolic link must be resolved first. $VERSION resolves to /SYSR9A on SY1, which makes the path name /SYSR9A/bin. The contents of this directory will now be displayed. If ls –l /bin/ is issued on SY2, the contents of /SYSR9/bin will display. From SY2 you can display information on SY1 by fully qualifying the directory. Example: To view SY1's /bin directory:
Figure 3. One BPXPRMxx parmlib
member for multiple systems sharing file systems and using different
release levels
In order to use one BPXPRMxx parmlib file system member, we have used another system symbolic like &SYSR1. This system symbolic is used in the VERSION parameter and also as a qualifier in the version file system data set name. |
Copyright IBM Corporation 1990, 2014
|