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

Products

• Endevor

Issue/Introduction

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?

Environment

All Supported Releases

Resolution

For 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.

Here is an example of a mapping rule in Endevor:

MAPPED    iprfx.iqual.STG1.LOADLIB

The actual dataset being used is: 

                iprfx.iqual.STG2.TEMP.LOADLIB

Since the mapped dataset has 4 nodes but the actual dataset has 5 nodes, the file will not be shipped.