Overview
Purpose: The MQCIH structure describes the information that can be present at the start of a message sent to the CICS bridge through WebSphere MQ for z/OS.
Format name: FMCICS.
Version: The current version of MQCIH is CIVER2. Fields that exist only in the more-recent version of the structure are identified as such in the descriptions that follow.
The COPY file provided contains the most recent version of MQCIH, with the initial value of the CIVER field set to CIVER2.
Character set and encoding: Special conditions apply to the character set and encoding used for the MQCIH structure and application message data:
- Applications that connect to the queue manager that owns the CICS bridge queue must provide an MQCIH structure that is in the character set and encoding of the queue manager. This is because data conversion of the MQCIH structure is not performed in this case.
- Applications that connect to other queue managers can provide an MQCIH structure that is in any of the supported character sets and encodings; conversion of the MQCIH is performed by the receiving message channel agent connected to the queue manager that owns the CICS bridge queue.
Note:There is one exception to this. If the queue manager that owns the CICS bridge queue is using CICS for distributed queuing, the MQCIH must be in the character set and encoding of the queue manager that owns the CICS bridge queue.- The application message data following the MQCIH structure must be in the same character set and encoding as the MQCIH structure. The CICSI and CIENC fields in the MQCIH structure cannot be used to specify the character set and encoding of the application message data.
A data-conversion exit must be provided by the user to convert the application message data if the data is not one of the built-in formats supported by the queue manager.
Usage: If the values required by the application are the same as the initial values shown in Table 8, and the bridge is running with AUTH=LOCAL or AUTH=IDENTIFY, the MQCIH structure can be omitted from the message. In all other cases, the structure must be present.
The bridge accepts either a version-1 or a version-2 MQCIH structure, but for 3270 transactions a version-2 structure must be used.
The application must ensure that fields documented as "request" fields have appropriate values in the message sent to the bridge; these fields are input to the bridge.
Fields documented as "response" fields are set by the CICS bridge in the reply message that the bridge sends to the application. Error information is returned in the CIRET, CIFNC, CICC, CIREA, and CIAC fields, but not all of them are set in all cases. Table 7 shows which fields are set for different values of CIRET.
Table 7. Contents of error information fields in MQCIH structure CIRET CIFNC CICC CIREA CIAC CRC000 - - - - CRC003 - - FBC* - CRC002
CRC008MQ call name MQ CMPCOD MQ REASON - CRC001
CRC006
CRC007
CRC009CICS EIBFN CICS EIBRESP CICS EIBRESP2 - CRC004
CRC005- - - CICS ABCODE