How the WebSphere MQ-IMS bridge deals with messages

 

When you use the WebSphere MQ-IMS bridge to send messages to an IMS™ application, we need to construct your messages in a special format. You must also put your messages on WebSphere MQ queues that have been defined with a storage class that specifies the XCF group and member name of the target IMS system. These are known as MQ-IMS bridge queues, or simply bridge queues.

A user does not need to sign on to IMS before sending messages to an IMS application. The user ID in the UserIdentifier field of the MQMD structure is used for security checking. The level of checking is determined when WebSphere MQ connects to IMS, and is described in the security section of the WebSphere MQ for z/OS System Setup Guide. This enables a pseudo signon to be implemented.

The WebSphere MQ-IMS bridge accepts the following types of message:

WebSphere MQ validates the message data to ensure that the sum of the LL bytes plus the length of the MQIIH (if it is present) is equal to the message length.

When the WebSphere MQ-IMS bridge gets messages from the bridge queues, it processes them as follows:

The WebSphere MQ-IMS bridge uses one or two Tpipes for each WebSphere MQ queue:

The Tpipes are created by WebSphere MQ when they are first used. A non-synchronized Tpipe exists until IMS is restarted. Synchronized Tpipes exist until IMS is cold started. We cannot delete these Tpipes yourself.

 

Parent topic:

Writing WebSphere MQ-IMS bridge applications


fg15870_