Previous topic |
Next topic |
Contents |
Index |
Contact z/OS |
Library |
PDF
Identifying zones to be processed SMP/E for z/OS User's Guide SA23-2277-01 |
|
When identifying zones to be processed, you may group the zones by defining a global zone ZONESET entry. You may have one or more ZONESETs to describe groups of products that might have dependencies on each other or which may be defined in different global zones. For example, assume that you have a system that supports two products, ABC and XYZ, that have dependencies on one another. You might have one zone, BASEABC, for the base ABC function, and another zone, PRODABC, for a dependent function. Likewise, you might have a zone BASEXYZ for the base XYZ function, and another zone, PRODXYZ, for a dependent function. Let's also assume that all four zones are defined in the same global zone. The dependent functions are different versions of the same product, and they must be synchronized with each other and with their base functions. You can set up two ZONESETs to help keep these products at the same service level. These are the commands you can use to define the ZONESETs:
As a second example, assume that you have the same four zones,
but BASEABC and PRODABC are defined in one global zone and BASEXYZ
and PRODXYZ are defined in a second global zone. Because each zone
in a ZONESET must be defined by a ZONEINDEX subentry in the same global
zone as the ZONESET entry, the following ZONESETs may each be defined
in their respective global zone:
When you define a ZONESET, remember:
For more information about defining the ZONESET entry, see SMP/E for z/OS Reference. |
Copyright IBM Corporation 1990, 2014
|