Two SMP/E APPLY jobs contain FCO767W and FCO770W messages that prevented the ALIASes from getting copied over to the output PDSE datasets. Note that these are ONLY warning messages.
FCO770W ALIAS xxxxxxx WILL BE DELETED FROM OUTPUT PDSE DATASET
FCO767W xxxxxxx BUT NOT ALIAS KLHLOGFF BEING REPLACED IN OUTPUT DATASET
Does PDSMAN need additional configuration or customization in order to properly copy these ALIASes to the output PDSE datasets?
Release: PDSMA100200-7.7-PDSMAN-PDS Library Management-ONE COMPONENT
The warning messages are not telling us that a member was not copied. They are telling us that a member of the existing output library has an alias that is not being replaced.
Since the library is a PDSE - the system (NOT PDSMAN) will delete the member.
IEBCOPY would operate the same way. All is good to move forward.