Using the move/copy utility with load modules

For a move or copy of load modules, these rules apply:

Both data sets must be partitioned and must have an undefined record format (RECFM=U).
Load modules that were created for planned overlay cannot be moved or copied.
The print option, if specified, is ignored.
If the "To" library is LLA-managed, it must be in NOFREEZE mode.
For Move or Copy, reblocking can be done for load modules only, and is done by using the IEBCOPY COPYMOD function. Whether the load module is reblocked depends on the block sizes for the "To" and "From" data sets, as well as the value of the USE_IEBCOPY_COPY_OR_COPYMOD_OPTION and WHEN_TO_USE_IEBCOPY keyword settings in the ISPF Configuration table (see z/OS ISPF Planning and Customizing for more information).
- If the WHEN_TO_USE_IEBCOPY setting is 0, IEBCOPY is only used:
  - When copying from a data set with a larger block size to a data set with a smaller block size.
  - When a PDSE has been specified in the "From" data set concatenation or as the "To" data set.
- If the WHEN_TO_USE_IEBCOPY setting is 1, IEBCOPY is always used to copy load modules.
- If the WHEN_TO_USE_IEBCOPY setting is 2, IEBCOPY is only used when a PDSE has been specified in the "From" data set concatenation or as the "To" data set.
- If the WHEN_TO_USE_IEBCOPY setting indicates that IEBCOPY should be used, these rules apply when determining whether to reblock or not:
  - When the USE_IEBCOPY_COPY_OR_COPYMOD_OPTION setting is 1:
    - If the "To" and "From" block sizes are the same, no reblocking occurs. ISPF uses IEBCOPY COPY.
    - If the "To" block size is larger than the "From" block size, no reblocking occurs. ISPF uses IEBCOPY COPY.
    - If the "To" block size is smaller than the "From" block size, reblocking occurs. ISPF uses IEBCOPY COPYMOD.
  - When the USE_IEBCOPY_COPY_OR_COPYMOD_OPTION setting is 2:
    - If the "To" and "From" block sizes are the same, no reblocking occurs. ISPF uses IEBCOPY COPY.
    - If the "To" block size is larger than the "From" block size, reblocking occurs. ISPF uses IEBCOPY COPYMOD.
    - If the "To" block size is smaller than the "From" block size, reblocking occurs. ISPF uses IEBCOPY COPYMOD.
- When the USE_IEBCOPY_COPY_OR_COPYMOD_OPTION setting is 3:
  - Reblocking occurs. ISPF uses IEBCOPY COPYMOD.
If IEBCOPY is used to process the copy, ISPF allocates these data sets:
zprefix.zuser.SPFnnn.IEBCOPY

IEBCOPY SYSPRINT data set

SYSIN

IEBCOPY SYSIN data set

SYSUT3 and SYSUT4

IEBCOPY work data sets

The SYSPRINT data set is deleted when the copy ends successfully. If errors are encountered, it is kept to help you diagnose errors. SYSIN, SYSUT3, and SYSUT4 are temporary data sets that use VIO if available, and are freed upon completion of the copy. All allocations use the value of ISPF Configuration table keyword PDF_DEFAULT_UNIT as the unit. The sizes for the SYSUT3 and SYSUT4 data sets are calculated dynamically, based on the number of members to be copied. If this is not sufficient for your move/copy request, these DDNAMES can be preallocated. If they are preallocated, ISPF does not free them when the copy is finished.