IMS TM includes message synchronization for messages destined to other transactions or to terminals as part of the commit processing for a transaction. To make this consistency available for TIBCO Object Service Broker transactions, the TIBCO Object Service Broker-supplied table @IMSDCTRXS helps users to keep track of the status of the most recently executed transaction.
This table has a composite primary key of the LTERM and
REGION fields. At the beginning of each session you can have a startup rule access this table to determine if any messages have to be re-sent, as indicated by the value in the fields of the table.
Use the $GETOPT tool to retrieve the
LTERM,
REGION,
CODE, and any other information required to make decisions about re-sending messages.
A set of sample rules to do this processing is provided as part of the TIBCO Object Service Broker IMS TM interface. These rules are in the @SAMPLES library (Unit=IMSDC). The entry rule is SAMPLEIMSDCTRX.
The comparison is done on IMS LTERM (logical terminal) names and time/date stamps. The message to be re-sent is stored in the table @IMSDCTRXOUT in multiple segments of 1024 bytes.
If the startup rule is invoked and there is a message to be sent, the sample rules show how to send it back to IMS for processing by the TIBCO Object Service Broker program running in the MPR.