Mapping WebSphere MQ messages to IMS transaction types

Mapping WebSphere MQ messages to IMS transaction types

Mapping WebSphere MQ messages to IMS transaction types
WebSphere MQ message type Commit-then-send (mode 0) - uses synchronized IMS™ Tpipes Send-then-commit (mode 1) - uses non-synchronized IMS Tpipes
Persistent WebSphere MQ messages

Recoverable full function transactions
Irrecoverable transactions are rejected by IMS

Fastpath transactions
Conversational transactions
Full function transactions

Nonpersistent WebSphere MQ messages

Irrecoverable full function transactions
Recoverable transactions are rejected by IMS

Fastpath transactions
Conversational transactions
Full function transactions

IMS commands cannot use persistent WebSphere MQ messages with commit mode 0. See the IMS/ESA Open Transaction Manager Access User’s Guide for more information.

Parent topic:
How the WebSphere MQ-IMS bridge deals with messages

fg15880_

WebSphere MQ message type	Commit-then-send (mode 0) - uses synchronized IMS™ Tpipes	Send-then-commit (mode 1) - uses non-synchronized IMS Tpipes
Persistent WebSphere MQ messages	Recoverable full function transactions Irrecoverable transactions are rejected by IMS	Fastpath transactions Conversational transactions Full function transactions
Nonpersistent WebSphere MQ messages	Irrecoverable full function transactions Recoverable transactions are rejected by IMS	Fastpath transactions Conversational transactions Full function transactions
IMS commands cannot use persistent WebSphere MQ messages with commit mode 0. See the IMS/ESA Open Transaction Manager Access User’s Guide for more information.