Why is my Datacom job connecting to MUF via XCF even if running on the same LPAR?

Document ID : KB000098652
Last Modified Date : 30/05/2018
Show Technical Document Details
Introduction:
A job (MYDBJOB1), executing a Datacom utility or a user application, runs on the same LPAR (SYS1) where the Datacom MUF is currently active but, based on the DB00133I  message:
DB00133I - JOB OPEN MYDBJOB1 15688 USER01 JOB12345 XCF-SYS1
the connection between the two address spaces occurs via XCF
Question:
Why does the connection between MYDBJOB1 and the Datacom Multiuser region occur in XCF mode and not locally?  
Answer:
DBSYSID macro has been assembled with: CONNECT_ALLOW_PRIORITY=(XCF,LOCAL) so XCF is the preferred connection method, even if the MUF and the job are running on the same LPAR.

DBSYSID must be changed to read:
CONNECT_ALLOW_PRIORITY=(LOCAL,XCF)
and then DBSIDPR must be reassembled and relinked .
Additional Information:
XCF is an added overhead and less efficient than LOCAL connection when both the job and the MUF are running on the same LPAR.