Inbound messages

 

These examples show the possible structures of CICS 3270 bridge inbound messages.

• Use this structure for an application that invokes a CICS transaction without any data:

   --------------
  | MQMD | MQCIH |
   --------------
  

  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.

• Use this structure for inbound messages that have zero length data:

   -------------------------------
  | MQMD | MQCIH | BRMQ structure |
   -------------------------------
  

  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 within the BRMQ structure specifies which AID key has been used, but no data follows the BRMQ structure.

• Use this structure for an application that invokes a transaction that will issue an EXEC CICS command that expects data to be available:

   --------------------------------------
  | MQMD | MQCIH | BRMQ structure | data |
   --------------------------------------
  

  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 that these vectors can contain data.

Optionally, and only for CICS TS2.2 and above, 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 bridge makes no use of data within the headers.

• Use this structure for inbound messages that have headers before the MQCIH:

   -------------------------
  | MQRFH2 | MQRFH2 | MQCIH |
   -------------------------
  

 

Parent topic:

CICS 3270 bridge message structure

fg15550_