SX4DTC2 is an IBM MQ extension built on the Capitalware SX4 synchronous exit framework. It is designed to participate directly in MQ message processing while coordinating message handling with distributed transaction control logic. The product operates at MQ exit points that allow synchronous decision‑making during message put and get operations. This enables MQ message activity to be aligned with external transaction outcomes, ensuring that message processing behavior is consistent with broader transactional rules. SX4DTC2 is intended for environments where MQ messaging must be tightly controlled as part of distributed or coordinated transaction flows. It works at the messaging infrastructure level and does not require modifications to MQ applications or their source code.

Key Features

Synchronous MQ Exit Processing

Operates in the MQ execution path.

• Uses synchronous MQ exit points
• Decisions applied before MQ operation completes

Transaction Coordination

Aligns messaging with transaction logic.

• Coordinates MQ activity with external transaction control
• Supports commit or rollback decisions

Infrastructure‑Level Control

Independent of applications.

• No changes to message producers or consumers
• Centralized transaction handling logic

Deterministic Message Handling

Predictable behavior during processing.

• MQ operations succeed or fail based on rules
• Prevents partial or inconsistent message states

SX4 Framework Integration

Built on Capitalware SX4.

• Uses common SX4 configuration model
• Consistent behavior with other SX4‑based components

Benefits

Transactional Consistency

Keeps MQ aligned with enterprise transactions.

• Prevents message flow outside transaction boundaries
• Reduces risk of data inconsistency

Reduced Application Complexity

Removes transaction logic from applications.

• Applications remain focused on business logic
• Infrastructure handles coordination

Centralized Control

Single place for transaction rules.

• Easier governance and maintenance
• Consistent behavior across queue managers

Improved Reliability

Designed for controlled MQ processing.

• Decisions made before MQ state changes
• Suitable for high‑integrity environments

Operational Transparency

Works within standard MQ behavior.

• Preserves MQ transactional semantics
• Predictable impact on message flow