DFHWS-MTOM-IN container

DFHWS-MTOM-IN is a container of DATATYPE(BIT) that holds information about the specified options for the <cics_mtom_handler> element of the pipeline configuration file and information about the message format that has been received in the pipeline.

It contains the information to process an inbound MTOM message in the pipeline. The inbound message can be a request message from a web service requester or a response message from a web service provider.

If you do not specify a <cics_mtom_handler> element in the pipeline configuration file, or if a SOAP message is received instead of an MTOM message, this container is not created.

If web services security is configured in the pipeline, or if validation is switched on for a web service, the contents of field XOP_MODE in DFHWS-MTOM-IN can be overridden by CICS when the container is created. For example, if you configure the pipeline to process the content of MTOM messages in direct mode, and you then switch validation on for the web service, CICS overrides the defined value in the pipeline configuration file and sets the XOP processing to run in compatibility mode. CICS performs the override because of the restrictions in support for processing XOP documents and binary attachments in the pipeline.

You cannot change the contents of this container.

Table 1. Structure of the DFHWS-MTOM-IN container
Field name Length (bytes) Contents
MTOM_STATUS 4 Contains the value "1", indicating that the message received by CICS is in MTOM format.
MTOMNOXOP_STATUS 4 Contains one of the following values:
0
The MTOM message contains binary attachments.
1
The MTOM message does not contain binary attachments.
XOP_MODE 4 Contains one of the following values:
0
No XOP processing takes place.
1
XOP processing takes place in compatibility mode.
2
XOP processing takes place in direct mode.


dfhws_dfhwsmtomin.html | Timestamp icon Last updated: Sunday, 4 June 2017