Description: Before z/OS V2R1, the IEBCOPY utility assumed that calls from programs (not from JCL) that passed three parameters, had the high order bit set on in the third word of the parameter list. Starting in z/OS V2R1, IEBCOPY requires the high order bit to be on in the third word of a parameter list; if that bit is not on, IEBCOPY causes a failure. This change can affect your programs that call IEBCOPY, requiring you to update them if needed.
| Element or feature: | DFSMSdfp. |
| When change was introduced: | z/OS V2R1. |
| Applies to migration from: | z/OS V1R13 and z/OS V1R12. |
| Timing: | Before the first IPL of z/OS V2R1. |
| Is the migration action required? | Yes, if you have programs that pass a parameter list of exactly three words to IEBCOPY and do not set on the high order bit in the last word. |
| 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: Examine calls from programs (not from JCL) to IEBCOPY, to see whether any pass three parameters without turning on the high order bit in the last word. If you have such programs, revise them to turn on the high order bit of the last word of the parameter list. If you are using the CALL, LINK or ATTACH macro, the simplest way to do this is to add the VL parameter to CALL or VL=1 parameter to LINK or ATTACH.
Reference information: For details about program calls to IEBCOPY, see z/OS DFSMSdfp Utilities.