Structures of 3270 request messages (inbound) using the CICS-WebSphere MQ bridge
These examples show the possible structures of request messages sent by non-CICS applications to 3270 transactions using the CICS-WebSphere MQ bridge, known as inbound messages.
- Use this structure when your non-CICS application calls a
CICS®
transaction
without any data:
Set the field MQCIH.TransactionId to the name of the transaction that you want to start. Set the other fields in MQCIH to values that are appropriate for the application.-------------- | MQMD | MQCIH | -------------- - Use this structure when your non-CICS application runs a
transaction
that will issue an EXEC
CICS
command that expects data
to be available:
BRMQ structure represents any of the inbound vector structures RECEIVE, RECEIVE MAP, CONVERSE, or RETRIEVE. Note that the BRMQ structure itself consists of a header followed by vectors, and these vectors can contain data.-------------------------------------- | MQMD | MQCIH | BRMQ structure | data | -------------------------------------- - Use this structure for request messages that have zero length
data:
For example, an inbound RECEIVE MAP vector can represent an action where the user has only pressed a PF key. In this case, a field in the BRMQ structure specifies which AID key has been used, but no data follows the BRMQ structure.------------------------------- | MQMD | MQCIH | BRMQ structure | ------------------------------- - Optionally, additional headers with format names beginning MQH,
and containing standard link fields, can precede the MQCIH header.
Such headers are returned unmodified in the output message because
the CICS-WebSphere MQ bridge makes no use of data in the headers.
Use this structure for request messages that have headers before
the
MQCIH:
------------------------- | MQRFH2 | MQRFH2 | MQCIH | -------------------------