ZONESET entry (global zone)

The ZONESET entry defines a group of zones to be used to limit the SYSMODs processed by an SMP/E command. For example, you can specify a ZONESET on the ZONESET operand of the REPORT command. This defines which zones SMP/E should check for installed SYSMODs that specify conditional requisites that might be needed for functions in other zones in the ZONESET. A ZONESET may also define a group of zones to be checked or ignored by the REJECT command.

Subentries

These are the subentries for the ZONESET entry as they appear in the LIST output:
name
is the name of the ZONESET. The name can contain from 1 to 8 alphanumeric characters.

To avoid confusion and undesired results, you may want to avoid giving a ZONESET the same name as any of the target or distribution zones defined to the global zone that will contain the ZONESET entry. This is because, on some SMP/E command operands, you can specify zones and ZONESETs. When ZONESETs and zones have the same name, you might not get the results you wanted.

For example, suppose you have a ZONESET named Z001 and a zone named Z001. If you specify Z001 on an SMP/E command operand, SMP/E assumes that you want to use the zones defined in ZONESET Z001 (which might or might not include zone Z001), and not the individual zone Z001.

XZREQCHK
indicates whether this ZONESET should be used when establishing the default zone group for the APPLY, ACCEPT, and RESTORE commands.
The UCL operand is XZREQCHK(YES|NO).
  • YES indicates that the ZONESET should be used when establishing the default zone group.
  • NO indicates that the ZONESET should not be used when establishing the default zone group. NO is the default.
  • The XZREQCHK value (including the default value) is ignored when the XZGROUP operand is specified on the APPLY, ACCEPT, or RESTORE command.
ZONE
lists the target or distribution zones that are to be part of this ZONESET.
The UCL operand is ZONE(zone…).
  • Each value can contain from 1 to 7 alphanumeric characters.
  • A ZONESET can contain both target and distribution zones.
  • All the zones in a ZONESET must be defined in the same global zone as the ZONESET entry.
  • The zones cannot be defined in global zones that are in different SMPCSI data sets. For an example of defining a ZONESET in order to report on zones controlled by different global zones, see the REPORT CROSSZONE command in SMP/E for z/OS Commands.

LIST Examples

To list all the ZONESET entries in a global zone, you can use the following commands: 
SET      BDY(GLOBAL)        /* Set to global zone.        */.
LIST     ZONESET            /* List all ZONESET entries.  */.
To list specific ZONESET entries in a global zone, you can use these commands: 
SET      BDY(GLOBAL)        /* Set to global zone.        */.
LIST     ZONESET(ZST2       /* List only these            */
                 ZST4)      /* entries.                   */.

The format of the LIST output for each ZONESET entry is the same for both of these commands. The only difference is the number of ZONESET entries listed.

Figure 1 shows an example of LIST output for ZONESET entries.
Figure 1. ZONESET entry: sample LIST output
PAGE nnnn  - NOW SET TO zzzzzz ZONE nnnnnnn  DATE mm/dd/yy TIME hh:mm:ss SMP/E 36.nn SMPLIST OUTPUT

GLOBAL                   ZONESET ENTRIES


ZST2          ZONE     = ZONE21   ZONE22   ZONE23

ZST4          ZONE     = ZONE41   ZONE42   ZONE43

UCLIN Examples

You can use the ADD, REP, and DEL UCL statements to change subentries in a ZONESET entry. When you use UCLIN to update a ZONESET entry, keep these points in mind:
  • After the UCLIN changes are done, the ZONESET entry must contain at least a ZONE subentry. Otherwise, the entry contains so little information that SMP/E cannot use it.
  • If a DEL statement deletes all the existing subentries in the entry, SMP/E deletes the entire entry.
Parent topic: SMP/E data set entries