Processing

With the ZONEMERGE command, you can merge a specified distribution zone or target zone into another specified target zone or distribution zone. REPLACE is the default if neither REPLACE nor NOREPLACE is specified. After the merge operation is complete, the originating distribution zone or target zone still exists in the CSI data set.

SMP/E supports the following variations of merging:

Distribution zone to distribution zone
Target zone to target zone
Distribution zone to target zone

Note: Any attempt to merge a target zone to a distribution zone causes an error.

The syntax refers to two types of zone entries: DEFINITION and CONTENT. DEFINITION entries are set up by the user to define data sets used by SMP/E; CONTENT entries are created by SMP/E. If neither CONTENT nor DEFINITION is specified, the default is to merge only the CONTENT type entries. This supports the distribution zone to target zone copy after a system generation when the desire is to recopy the structure of the system, but not the definition. The following defines how the various entries are categorized:

DEFINITION type entries
- DDDEF entries
CONTENT type entries
- ASSEM entries
- Element entries
- DLIB entries
- LMOD entries
- SYSMOD entries

When the ZONEMERGE command is encountered, SMP/E first ensures that both zones have been previously defined. The ZONEMERGE command does not create a new zone. If either one has not been defined, an error message is issued, and the command is not processed. To fix this problem, check the zone names specified, and either change the incorrect name, or define the missing zone by using UCLIN.

SMP/E then checks to make sure the zone type (that is, target or distribution), specified in the global zone ZONEINDEX, matches the type specified in the ZONEMERGE command. If not, an error message is issued, and the ZONEMERGE is not done. To fix this problem, check to ensure that the zone names specified are correct and that the zone types specified in the global zone ZONEINDEX are correct; fix whatever discrepancy was found, and rerun the command.

To perform the actual merge, SMP/E sequentially reads through both zones. For each entry in the originating zone, SMP/E checks the entry type (DEFINITION, CONTENT, or both) and looks at the operands specified on the ZONEMERGE command to determine whether the entry should be processed. If so, SMP/E checks to see whether that entry exists in the destination zone.

If an entry is not found, the entry from the originating zone is stored.
If an entry is found and REPLACE was specified, the entry from the destination zone is deleted, and the entry from the originating zone is stored.
If an entry is found and NOREPLACE was specified, processing continues with the next entry.

If the originating zone contained cross-zone subentries, SMP/E issues warning messages. SMP/E determines what cross-zone information to merge from MOD and LMOD entries in the originating zone, as follows:

If any cross-zone subentries refer to a zone with the same name as the receiving zone, that information is not copied to the receiving zone, and an error message is issued. SMP/E still attempts to merge the rest of the data in the zone.
If the entry in the originating zone contains nothing but cross-zone subentries, SMP/E does not copy the cross-zone subentries to the receiving zone.
If the entry in the receiving zone contains nothing but cross-zone subentries, SMP/E merges the entry from the originating zone into the receiving zone, regardless of whether the REPLACE operand was specified. Cross-zone subentries from the originating zone are added to those from the receiving zone. SMP/E issues messages indicating the source of each of the cross-zone subentries in the merged entry.
Otherwise, the entries are merged only if REPLACE was specified. In this case, SMP/E merges the entry from the originating zone into the receiving zone, replacing all the information in the receiving zone (except the cross-zone subentries) with information from the originating zone. Cross-zone subentries from the originating zone are added to those from the receiving zone. SMP/E issues messages to indicate the source of each of the cross-zone subentries in the merged entry.
If any cross-zone subentries were merged into the receiving zone, SMP/E adds TIEDTO subentries for the cross-zones to the receiving zone's TARGETZONE entry.

When you merge zones, you can end up with an LMOD entry with a MODDEL subentry for a module and a MOD entry for that same module. For example, suppose you have a zone with an LMOD entry that has a MODDEL subentry containing module MOD005, and you merge that zone with another zone that has a MOD entry for MOD005. It might seem contradictory, but the result is a zone having an LMOD entry with a MODDEL subentry containing MOD005 and a MOD entry for MOD005. If you install a SYSMOD containing MOD005, module MOD005 is removed from the MODDEL subentry.