Updating cross-zone subentries

If the copied zone contained any cross-zone subentries, SMP/E issues warning messages. You need to determine what corrective action is needed to ensure that the new zone and any identified cross-zones are properly related through cross-zone subentries. The type of corrective action required depends on:
- The types of cross-zone subentries found
- How you plan to use the new zone
- What you plan to do with the input zone
- Any actions you plan to perform (or may have already performed) with the zones identified in the warning messages
Here are some examples of possible situations and the associated corrective action:
- The new zone replaces the old zone, which will be deleted.
  You need to update the cross-zone subentries in each identified zone to indicate the new zone name. To do this, use the ZONEEDIT command.
- All the identified zones are being copied to create a clone of the original zone structure.
  You need to connect all the new zones correctly. To do this, use the ZONEEDIT command.
- The new zone contains only TIEDTO and XZMOD subentries, and you want to obtain updates for the identified load modules from the cross-zones.
  You need to update the identified zones with the information required to ensure that the identified modules are automatically linked into the affected load modules. Specifically, you need to add XZLMOD subentries to the MOD entries in the other zones, as well as a TIEDTO subentry to the TARGETZONE entry for each of these other zones. To add the XZLMOD subentries, use the UCLIN command. To add the TIEDTO subentries, use either the UCLIN command or the SMP/E Administration dialog.
- The new zone is a temporary copy and will be deleted after brief use.
  You can either do nothing or disconnect the new zone from all the identified zones. To disconnect the zone, use the ZONEEDIT command to delete all the cross-zone subentries from the new zone.