DFSMSdfp: Do not use IEBCOPYO
Description
In z/OS V1R13, the IEBCOPY utility was enhanced, and one of the enhancements was that the utility was no longer APF-authorized. For users who needed to fallback from the new IEBCOPY to the previous APF-authorized form, IEBCOPY was retained in z/OS V1R13 under the name IEBCOPYO. The IEBDSCPY alias name for IEBCOPY was also revised to apply to IEBCOPYO for z/OS V1R13.
In z/OS V2R1, the IEBCOPYO form of the utility was eliminated and the IEBDSCPY alias now applies to the standard non-APF-authorized form of IEBCOPY.
Table 1 provides more details about this migration action. Use this information to plan your changes to the system.
| Element or feature: | DFSMSdfp. |
|---|---|
| When change was introduced: | z/OS V2R1. |
| Applies to migration from: | z/OS V1R13. |
| Timing: | Before the first IPL of z/OS V2R2. |
| Is the migration action required? | Yes, if you used IEBCOPYO directly or through the alias IEBDSCPY. |
| Target system hardware requirements: | None. |
| Target system software requirements: | None. |
| Other system (coexistence or fallback) requirements: | None. |
| Restrictions: | None. |
| System impacts: | None. |
| Related IBM Health Checker for z/OS check: | None. |
Steps to take
Follow these steps:
- Any programs or jobs that called IEBCOPYO in z/OS V1R13 must be changed to call IEBCOPY in V2R2. It is not expected that you used IEBCOPYO on z/OS V1R13, unless you had a problem with the z/OS V1R13 level of IEBCOPY and had to fall back to the z/OS V1R12 level of IEBCOPY.
- Any programs or jobs that call the IEBDSCPY alias name in z/OS V2R2 will invoke the non-APF-authorized IEBCOPY. Make any appropriate changes if this affects your programs or jobs.
Reference information
For more information about the IEBCOPY utility, see z/OS DFSMSdfp Utilities.