Example 1: Using REPORT CROSSZONE with zones controlled by the same global zone

Assume that you have a system that supports z/OS® and OS/390®. There is one target zone (BASEZOS) for base z/OS functions and another target zone (PRODZOS) for a dependent function. Likewise, there is a target zone (OS390) for base OS/390 functions and another target zone (PROD90) for a dependent function. Table 1 shows some of the functions and PTFs contained in each zone.

Table 1. REPORT CROSSZONE example: SYSMOD installed in each zone
Zone	Functions	PTFs
BASEZOS	HBB3310	UZ00005 UZ00009 UZ00011 UZ00013 UZ00031 UZ00032
PRODZOS	HJS3311	UZ00006 UZ00022 UZ00025 UZ00026
OS390	HBB2102 JBB2220	UZ00030 UZ00031
PROD90	HJS2220	UZ00032 UZ00033

You have also received the following SYSMODs but have not yet applied or accepted them:

UZ00023
UZ00024
UZ00027

Assume some of the PTFs specify conditional requisites. Table 2 shows some of the statements in these PTFs (causer SYSMODs), along with the zones where they were installed (causer zones), the functions they are applicable to (causer FMIDs), the functions specified on the ++IF statements (IFREQ FMIDs), the zones where these functions are installed (IFREQ zones), and the requisites.

Table 2. REPORT CROSSZONE example: required SYSMODs
Causer SYSMODs	Causer zones and FMIDs	IFREQ zones and FMIDs	Required SYSMODs
`++PTF(UZ00011). ++VER (Z038) FMID(HBB3310). ++IF FMID(HJS3311) REQ(UZ00023).`	BASEZOS – HBB3310	PRODZOS – HJS3311	UZ00023
`++PTF(UZ00013). ++VER (Z038) FMID(HBB3310). ++IF FMID(HJS3311) REQ(UZ00024).`	BASEZOS – HBB3310	PRODZOS – HJS3311	UZ00024
`++PTF(UZ00006). ++VER (Z038) FMID(HJS3311). ++IF FMID(HBB3310) REQ(UZ00009).`	PRODZOS – HJS3311	BASEZOS – HBB3310	UZ00009
`++PTF(UZ00022). ++VER (Z038) FMID(HJS3311). ++IF FMID(HBB3310) REQ(UZ00005).`	PRODZOS – HJS3311	BASEZOS – HBB3310	UZ00005
`++PTF(UZ00025). ++VER (Z038) FMID(HJS3311). ++IF FMID(HJS2220) REQ(UZ00027).`	PRODZOS – HJS3311	PROD90 – HJS2220	UZ00027
`++PTF(UZ00026). ++VER (Z038) FMID(HJS3311). ++IF FMID(HJS2220) REQ(UZ00028).`	PRODZOS – HJS3311	PROD90 – HJS2220	UZ00028
`++PTF(UZ00030). ++VER (Z038) FMID(HBB2102). ++IF FMID(HJS2220) REQ(UZ00032).`	OS390 – HBB2102	PROD90 – HJS2220	UZ00032
`++PTF(UZ00031). ++VER (Z038) FMID(HBB2102). ++IF FMID(HJS2220) REQ(UZ00033).`	OS390 – HBB2102	PROD90 – HJS2220	UZ00033

The dependent functions are different versions of the same product. They must be synchronized with each other and with their base functions. You can set up two ZONESETs (ZOSZSET and S390) to help keep these products at the same service level. Table 3 shows the zones contained in each ZONESET:

Table 3. REPORT CROSSZONE example: ZONESETs to be used
ZONESET	Zones
ZOSZSET	BASEZOS PRODZOS PROD90
S390	OS390 PROD90 PRODZOS

Assume that you want to find out whether there are any cross-zone requisites for the zones in ZONESET ZOSZSET. You can use the following commands:

SET    BDY(GLOBAL)           /* Process global zone.       */.
REPORT CROSSZONE             /* Report on requisites       */
       ZONESET(ZOSZSET)      /* for ZONESET ZOSZSET.       */.

SMP/E checks zones BASEZOS, PRODZOS, and PROD90 because they are the zones defined in ZONESET ZOSZSET. Because FORFMID was not specified, SMP/E checks the SYSMOD entries for all the functions installed in those zones. It makes a list of the CIFREQ subentries for all the functions. Then, because FORZONE was not specified, SMP/E reports on requisites needed in all the zones in the ZONESET.

Figure 1 shows an example of the report SMP/E produces:

Figure 1. Example of a cross-zone requisite SYSMOD report

PAGE nnnn  - NOW SET TO zzzzzz ZONE nnnnnnn  DATE mm/dd/yy TIME hh:mm:ss SMP/E 36.nn SMPLIST OUTPUT

                 CROSSZONE REQUISITE SYSMOD REPORT FOR APPLY

 ZONE              
REQUIRES                    CAUSER          
 NAME     FMID     SYSMOD   RECEIVED  SYSMOD   FMID     ZONE


 BASEZOS            NONE


 PROD90   HJS2220  UZ00027  YES       UZ00025  HJS3311  PRODZOS
          HJS2220  UZ00028  NO        UZ00026  HJS3311  PRODZOS


 PRODZOS  HJS3311  UZ00023  YES       UZ00011  HBB3310  BASEZOS
          HJS3311  UZ00024  YES       UZ00013  HBB3310  BASEZOS

SMP/E also writes the commands shown in Figure 2 to the SMPPUNCH data set:

Figure 2. Example of SMPPUNCH output for REPORT CROSSZONE

SET BDY (PROD90 ).
RESETRC.
APPLY   SELECT(
               UZ00027   /* REQUIRED DUE TO UZ00025 IN PRODZOS */
               UZ00028   /* REQUIRED DUE TO UZ00026 IN PRODZOS */
              )
        BYPASS(HOLDSYSTEM
        CHECK
        GROUP.
SET BDY (PRODZOS).
RESETRC.
APPLY   SELECT(
               UZ00023   /* REQUIRED DUE TO UZ00011 IN BASEZOS  */
               UZ00024   /* REQUIRED DUE TO UZ00013 IN BASEZOS  */
              )

        BYPASS(HOLDSYSTEM
        CHECK
        GROUP.

After getting the Cross-Zone Requisite SYSMOD report, you can take these actions:

Receive SYSMOD UZ00028 so you can install it in the PROD90 zone.
Use the SMPPUNCH output to install the requisite SYSMODs listed in the report.
Rerun the REPORT CROSSZONE command for the same ZONESET (ZOSZSET) to check for any additional requisites, and install any that are found.
Run the REPORT CROSSZONE command for the S390 ZONESET to keep zones PROD90 and OS390 synchronized.
Receive and install SYSMODs as needed for the zones in ZONESET S390.
Rerun the REPORT CROSSZONE command for S390, and install additional SYSMODs as needed.