When you use a COMMAREA, the maximum length of the request
message with all the headers is 33 272 bytes. Each header in the request
message has a field that indicates the data structure or application
data format comes next in the request message.
About this task
The headers that you must include in the request message
depend on the interface that the service requester is using to invoke
the service flow.
Procedure
- If you want the service requester to invoke a service flow
using a CICS-supplied interface, such as the EXEC CICS LINK API
command, include the DFHMAH header structure and the application data
in the COMMAREA. The DFHMAH header describes the structure
of the application data.
- If you want the service requester to use the CICS® Transaction Gateway (CTG) interface, the
request message must contain the 101-byte CTG header, followed by
the DFHMAH message header and then the application data.
- If the service requester is a WebSphere® MQ-enabled application, the request
message must include a WebSphere MQ
header (MQMD), the WebSphere MQ CICS Bridge header (MQCIH), the
DFHMADPL header, and the message header DFHMAH.
The
MQCIH header is required only when you are implementing password authentication.
However, you must always include it to enable compatibility with future
releases of CICS Service Flow Runtime.
If an error occurs in the WebSphere MQ-CICS
bridge, the MQCIH structure is returned to the service requester.
This process occurs regardless of whether the structure was sent in
the request message.
Example
The following figure illustrates the structure of this
request message.