The SMP/E zones are copied using ZONECOPY rather than IDCAMS REPRO so that both the zones and the CSI data sets can be renamed. This makes it possible to use both the old and new target and DLIB zones with a single global zone. The IEACLNCZ job in SYS1.SAMPLIB shows how to do a ZONECOPY.

Before the zones are copied, the global zone's ZONEINDEX entry must be updated with the new CSI data set and zone names.

Next, the zones are copied using ZONECOPY commands. Because the SMP/E boundary is already set to do the ZONECOPY, the ZONEEDIT commands to change the DDDEFs to reflect new volume serials (and data set names, for the DLIB zone) can be issued at the same time.

If you have copied an existing cataloged data set that does not have the VOLUME defined to the new target system using the same name, you must use an ADD DDDEF for the new target data set. If this is not done, the new code will be installed into the existing cataloged data set and not the new target data set.

REP TARGETZONE(newtgt) RELATED(newdlb) is an optional command, to be added only if the DLIBs and DLIB zone will be copied at the same time as the target libraries and zone.

As a rule, you should not install service or products on the same copy of the system software that the system is using. This includes those parts of the system software that reside in an HFS or zFS. The way to update a copy of an HFS or zFS is to mount it on another mount point. The system will continue to use its own level of the HFS or zFS, and the copy will be accessible using the other mount point.

Before making any updates to the copy with SMP/E, you should change the HFS or zFS path DDDEFs to point to another directory, usually called a service directory, and mount the copy's HFS or zFS on that directory's mount point. This assures that SMP/E will update the correct HFS or zFS when products and service are installed.

      SET BDY(NEWTGT) .
 
        ZONEEDIT DDDEF .
 
          CHANGE PATH(*,'/service'*) .
 
        ENDZONEEDIT .

Note that the HFS or zFS remains usable for backup no matter where the DDDEFs point. If you IPL using a BPXPRMxx member that mounts the copy's HFSs or zFSs at their normal mount points (not the service mount points), the system will function normally. The DDDEFs only affect where SMP/E searches for or stores parts that reside in an HFS or zFS.

For more information about servicing elements in the HFS or zFS, see the topic about installing service into the hierarchical file system in z/OS UNIX System Services Planning.