Usage notes
- The member and library operands are required. You must specify the member name, the set of libraries affected by the move, and the member type.
- ++MOVE statements must follow any ++VER and ++IF statements and must precede any element MCSs.
- Regardless of the order in which ++MOVE, ++RENAME, and ++DELETE
statements are coded in a SYSMOD, they are processed in the following
order:
- APPLY and ACCEPT
- ++MOVE
- ++RENAME
- ++DELETE
- RESTORE
- ++RENAME
- ++MOVE
Afterwards, ++JCLIN statements are processed, and then element statements.
- APPLY and ACCEPT
- You must use the FMID operand to identify all possible owners
of an element to be moved.
Using the FMID operand does not imply that the owner of the element is being changed. You can change ownership only by specifying the VERSION operand on the ++VER MCS or on the element statement. Even if you are changing the owner of the element, you must specify the FMID operand, because the element is moved before its ownership is changed. For more information about the VERSION operand, see ++VER MCS.
- A ++MOVE MCS can move a member to a given library from one library at a time. If a member exists in more than one library, you must use additional ++MOVE or ++DELETE statements to process the additional copies. For more information about ++DELETE statements, see ++DELETE MCS.
- If a ++MOVE MCS changes the DLIB for an element that is also being replaced, the element MCS must specify the new DLIB.