CA Endevor Destination mapping rules not working as expected and members shipped to a remote site never get there.

Document ID : KB000015991
Last Modified Date : 14/02/2018
Show Technical Document Details

When shipping elements to a remote location two different types are not shipped.  My setup for all the types (6) are similar since we use source output libraries and do not use any processors.  Endevor automatically creates a backout record for all elements being moved in source output libraries.  

Why do only two types not work correctly?


When using a source output library or any output library that is being shipped, make sure that the nodes being used are the same number that is defined in the mapping rules.  What this means is that the name of the source output library prefix.qual.sys.sub should be the same as defined in the mapping rules.  

Here is an example of a mapping rule in Endevor:


if the actual dataset being used is the following:


the mapped dataset has 4 nodes and actual dataset has 5 nodes.  The number of nodes must be equal 
in order to use the package ship utility.