Identifying zones to be processed

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:

//UCL      JOB 'accounting info',MSGLEVEL=(1,1)
//UCL      EXEC SMPPROC
//SMPCNTL  DD  *
SET      BDY(GLOBAL)      /* Set to global zone.   */.
UCLIN                     /*                       */.
ADD      ZONESET(ZONEA)   /* Create ZONESET ZONEA. */
         ZONE(BASEABC,    /* Include these zones.  */
              PRODABC,    /*                       */
              PRODXYZ)    /*                       */
         .
ADD      ZONESET(ZONEX)   /* Create ZONESET ZONEX. */
         ZONE(BASEXYZ,    /* Include these zones.  */
              PRODXYZ,    /*                       */
              PRODABC)    /*                       */
         .
ENDUCL                    /*                       */.
/*

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:

//UCL      JOB 'accounting info',MSGLEVEL=(1,1)
//UCL1      EXEC SMPPROC
//SMPCNTL   DD  *
SET         BDY(GLOBAL)    /* Set to global zone ABC */.
UCLIN                      /*                        */.
ADD         ZONESET(ZONEA) /* Create ZONESET ZONEA   */
            ZONE(BASEABC,  /* Include these zones    */
                 PRODABC)  /*                        */
	    .
ENDUCL                     /*                        */.
/*
//UCL2     EXEC SMPPROC
//SMPCNTL  DD *
SET        BDY(GLOBAL)      /* Set to global zone XYZ */.
UCLIN                       /*                        */.
ADD        ZONESET(ZONEX)   /* Create ZONESET ZONEX   */
           ZONE(BASEXYZ,    /* Include these zones    */
                PRODXYZ)    /*                        */
	   .   
ENDUCL                      /*                        */.
/*

When you define a ZONESET, remember:

Each zone in a ZONESET must also be defined in the global zone.
Each zone in a ZONESET must be defined in the same global zone. They cannot be defined in global zones that are in different CSI data sets. If you have zones defined in two different global zones, and you wish to use ZONESETs to identify the zones to the REPORT CROSSZONE command for processing, you must create a ZONESET in each global zone to contain the zones that are defined in each global zone.
A zone can be part of more than one ZONESET.
A ZONESET can contain both target and distribution zones.

For more information about defining the ZONESET entry, see z/OS SMP/E Reference.