DFHPI1103 E date time applid userid PIPELINE pipeline encountered an error while processing an outbound message in MIME compatibility mode. The problem with the MIME message was: {it contained a body that could not be parsed | it had an include for which there was no attachment | it caused an unexpected exception}.
Explanation
During WebSphere MQ processing of an outbound MIME request, in compatibility mode, CICS detected an error in the content of the MIME message. This could be because it contained a body that could not be parsed or it had an include for which there was no attachment. Other internal MIME syntax and processing problems could also be the cause. The message identifies which of these caused it to be issued.
System action
The PIPELINE returns in error. An exception trace point will have been issued with the details of the error.
User response
Trace can be checked to obtain the details of the MIME error. This error will need to be corrected in the MIME generation of the sender.
Module
DFHPITQ
XMEOUT parameters/Message inserts
- date
- time
- applid
- userid
- pipeline
- Value chosen from the following options:
1=it contained a body that could not be parsed, 2=it had an include for which there was no attachment, 3=it caused an unexpected exception
Destination
CPIO