Overview

Purpose: The MQIIH structure describes the information that must be present at the start of a message sent to the IMS bridge through WebSphere MQ for z/OS.

Format name: FMIMS.

Character set and encoding: Special conditions apply to the character set and encoding used for the MQIIH structure and application message data:

• Applications that connect to the queue manager that owns the IMS bridge queue must provide an MQIIH structure that is in the character set and encoding of the queue manager. This is because data conversion of the MQIIH structure is not performed in this case.

• Applications that connect to other queue managers can provide an MQIIH structure that is in any of the supported character sets and encodings; conversion of the MQIIH is performed by the receiving message channel agent connected to the queue manager that owns the IMS bridge queue.
  Note:

  There is one exception to this. If the queue manager that owns the IMS bridge queue is using CICS for distributed queuing, the MQIIH must be in the character set and encoding of the queue manager that owns the IMS bridge queue.

• The application message data following the MQIIH structure must be in the same character set and encoding as the MQIIH structure. The IICSI and IIENC fields in the MQIIH 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.

Authenticating passtickets for IMS bridge applications: It is now possible for WebSphere MQ administrators to specify the application name to be used for authenticating passtickets, for IMS bridge applications. To do this, the application name is specified as a new attribute PTKTAPPL for the STGCLASS object definition, as a 1 to 8 character alphanumeric string.

A blank value means that authentication occurs as with previous releases of WebSphere MQ, that is, no application name flows on the authentication request, and the MVSxxxx value to is used instead.

A value of between 1 and 8 alphanumeric characters must follow the rules for passticket application names as described in the RACF publications.

MQ Administrators and RACF administrators must both agree on the valid application names to be used. The RACF administrator must create a profile in the PTKTDATA class giving READ access to the userids of all applications that are to be granted access. The WebSphere MQ administrator must create or alter the required STGCLASS definitions that specify the application name to be used for passticket authentication.

For related information, see the Script (MQSC) Command Reference.