A PDS is being copied to a PDSE and some of the PDS members or aliases have user TTRS (which are incorrect for a PDSE) indicated by the directory entry. Members that contain User TTRs in the directory entry are not supported for PDSEs.
Processing of this member is skipped. Processing continues with the next member.
If it is acceptable to not copy the identified members or aliases, then no action is required. Otherwise, run another copy job specifying only those members or aliases which do not have user TTRs.
If the same output data set is used again, it will already include successfully copied members and aliases.
The most likely cause is accidentally copying a load module library to a PDSE. All load modules contain User TTRs in the directory entry.
DFSMSdfp and File and Attribute Management Services.
11
6