When the mirror task is resumed, a bad response other than a time out or a cancellation was given by the dispatcher.
The mirror transaction is abnormally terminated with a transaction dump.
Use the dump and the trace to determine the cause of the error.
DFHMIRS
An exception response has been received from the monitoring (MN) domain while processing a user event monitoring point (EMP) request. The exception response is produced when the 4-byte DATA1 field in the user parameter contains an invalid address.
The transaction is abnormally terminated with a CICS transaction dump.
Use the transaction dump to determine why the DATA1 value passed to the monitoring (MN) domain was invalid.
DFHCMP
An exception response has been received from the monitoring (MN) domain whilst processing a user event monitoring point (EMP) request. The exception response is produced when the 4-byte DATA2 field in the user parameter contains invalid data.
The transaction is abnormally terminated with a CICS transaction dump.
Use the transaction dump to determine why the DATA2 value passed to the monitoring (MN) domain was invalid.
DFHCMP
An unexpected error response has been received from the monitoring (MN) domain while processing a user event monitoring point (EMP) request.
The transaction is abnormally terminated with a CICS transaction dump.
This indicates a possible error in CICS code. An earlier CICS message is issued from the monitoring domain. Follow the user response for that message.
DFHCMP
An input data stream received from a 3270 begins with a set buffer address (SBA) order but is not followed by two 1-byte address fields. This is probably due to a hardware error.
The transaction is abnormally terminated with a CICS transaction dump.
It may be possible to bypass the problem by entering two spaces before the data to be entered.
If the problem persists, you need further assistance. See CICS® Problem Determination Guide for guidance on how to proceed.
DFHMSP
An internal logic error has been detected in module DFHMSP.
The transaction is abnormally terminated with a CICS transaction dump.
Retry the CMSG transaction, specifying operands in a different order. If this fails, keep the dump and contact your IBM Support Center.
DFHMSP
The task was purged before a GETMAIN request to the storage manager (SM) domain was able to complete successfully. The task that first detected the purged condition will have provided an exception trace.
The task is abnormally terminated with a CICS transaction dump.
Investigate why the task was purged. This is either as a result of a purge from the master terminal operator via the CEMT transaction, or by the task being timed out after waiting for longer than the DTIMOUT (deadlock timeout) value specified for the transaction.
If the master terminal operator purged the task, this may have been in an attempt to clear the system which appeared to be deadlocked for some reason.
If the task was timed out automatically as a result of the DTIMOUT value being exceeded, this may be due to insufficient main storage being available for the number of tasks in the system. If the amount of main storage cannot be increased, reduce the number of tasks in the system to avoid short-on-storage situations. Another possibility is to increase the value of the DTIMOUT option for the transaction.
DFHMSP
An error (INVALID, DISASTER, or unexpected EXCEPTION response) has occurred on a call to the storage manager (SM) domain. The domain that detected the original error provides an exception trace, a console message and, possibly, a system dump (depending on the options specified in the dump table).
The task is abnormally terminated with a CICS transaction dump.
See the related error message produced by the domain that detected the original error.
DFHMSP