Why is my Datacom job connecting to MUF via XCF even if running on the same LPAR?
Article ID: 98652
DatacomDATACOM - ADCISCOMMON SERVICES FOR Z/OS90S SERVICESDATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OSCOMMON PRODUCT SERVICES COMPONENTCommon ServicesCA ECOMETER SERVER COMPONENT FOCEasytrieve Report Generator for Common ServicesINFOCAI MAINTENANCEIPCUNICENTER JCLCHECK COMMON COMPONENTMainframe VM Product ManagerCHORUS SOFTWARE MANAGERCA ON DEMAND PORTALCA Service Desk Manager - Unified Self ServicePAM CLIENT FOR LINUX ON MAINFRAMEMAINFRAME CONNECTOR FOR LINUX ON MAINFRAMEGRAPHICAL MANAGEMENT INTERFACEWEB ADMINISTRATOR FOR TOP SECRETXpertware
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
Why does the connection between MYDBJOB1 and the Datacom Multiuser region occur in XCF mode and not locally?
Release: DATABB00200-14.0-Datacom/AD Component:
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 .
XCF is an added overhead and less efficient than LOCAL connection when both the job and the MUF are running on the same LPAR.