DFHXM0110 date time applid Transaction definition transid1 has been installed with the same REMOTENAME and REMOTESYSTEM as existing definition transid2.
Explanation
Transaction definition transid1 has been installed with the same REMOTENAME and REMOTESYSTEM as transaction definition transid2.
If this CICS system routes a transaction to the CICS system named as the REMOTESYSTEM of both the definitions and that transaction issues an EXEC CICS START request for the transaction-id named as the REMOTENAME of transid1 and transid2, CICS can either attach transid1 or transid2 on the local system to satisfy the START request.
System action
The install of transaction definition transid1 continues normally.
If an EXEC CICS START request is issued on a remote system as described in the message explanation, CICS attaches transid1 and not transid2 on the local system.
CICS does not always resolve this ambiguity in the same way after a warm or emergency restart, however.
User response
This situation usually causes no problems because the correct transaction is attached in the remote system. However, the correct transaction in the local system may not have been attached and this can manifest itself in the following ways:
-
Inconsistent statistics being accumulated in the local system.
-
The incorrect TRPROF being used when routing the START request back over to the remote system.
-
CEMT INQUIRE TASK showing the wrong set of transactions running in the local system.
Although these are not necessarily problems, you may want to check the definitions of the remote transactions in this system in case they have been defined incorrectly.
If remote START requests are issued as described, and it does matter which transaction CICS attaches in the local system, you should modify and reinstall the transaction definition that should not be attached. This removes any ambiguity.
Module
XMEOUT parameters/Message inserts
- date
- time
- applid
- transid1
- transid2
Destination
CSMT