For RRS transactions, CICS message DFHRM0129 gives the MUF name as DBNTRY01. How do I associate this name with a specific MUF name?

book

Article ID: 36431

calendar_today

Updated On:

Products

CA Datacom - DB CA Datacom CA Datacom - AD CA Datacom - Server CA CIS CA Common Services for z/OS CA 90s Services CA Database Management Solutions for DB2 for z/OS CA Common Product Services Component CA Common Services CA Datacom/AD CA ecoMeter Server Component FOC CA Easytrieve Report Generator for Common Services CA Infocai Maintenance CA IPC Unicenter CA-JCLCheck Common Component CA Mainframe VM Product Manager CA Chorus Software Manager CA On Demand Portal CA Service Desk Manager - Unified Self Service CA PAM Client for Linux for zSeries CA Mainframe Connector for Linux on System z CA Graphical Management Interface CA Web Administrator for Top Secret CA CA- Xpertware

Issue/Introduction

Question: 

When a CICS transaction updates multiple databases it runs under the control of Resource Recovery Services (RRS). 

If the two-phase commit process fails for some reason message DFHRM0129 is issued:

DFHRM0129 date time applid Intersystem communication failure. Resource updates are being backed out. Local resources may be out of 

sync with those on the remote system. Failure date mm/dd/yy failure time hh:mm:ss remote system DBNTRY01 transaction tranid task 

number trannum terminal termid user userid network UOW netuowid local UOW X'localuowid'.

The message gives the MUF name as DBNTRY01. How do I associate this name with a specific MUF name? 

 

Answer: 

The name of the MUF will be identified in the CICS message as DBNTRY01, DBNTRY02 up to DBNTRY99. Since multiple MUFs can be connected to a CICS system, the MUFs are identified by a suffix 01, 02, up to 99.

To determine which MUFs relate to which DBNTRYnn name, issue the CICS command DBEC I,MUF(??)  to display all the MUFs defined.

The sequence in which they are displayed determines what suffix will be used in DBNTRYnn.

The first MUF will be DBNTRY01, the second DBNTRY02 and so on.

Environment

Release:
Component: DB