Unexpected PNODE value when Endevor package ship job runs

Products

• Endevor

Issue/Introduction

A new shipment destination has been defined in Endevor using a transmission method CONNECT:Direct (formerly known as Network Data Mover or NDM) with a primary node defined as follows:

"TRANSMISSION METHOD 'NDM'" and "REMOTE NODENAME 'NEWPNODE1'".

When shipping a package to this destination, it appears that NDM is using another PNODE id already existing for another remote destination.  
Where is the other PNODE id reference coming from?  

Environment

All supported Releases 

Endevor 

Resolution

The set of CONNECT:direct libraries is not correct for this Primary node.

To resolve the problem, modify LINKLIB, NETMAP, and MSG dsnames with site-specific names. The prefix/qualifier of the CONNECT:Direct libraries is iprfx.ndm and should match the destination LPAR.

Additional Information

See
IBM Sterling Connect:Direct for z/OS Documentation.
and
The CONNECT Direct Method