XIBDS exit interface block for IMS TM data store information

For connections to IMS TM, IMS Connect keeps track of the status of IMS data stores in entries in the XIBDS exit interface block for data store information. IMS Connect user message exit routines can reference the XIBDS exit interface block to make routing decisions for incoming messages based on the status of the data store.

IMS Connect stores the following types of information about IMS data stores in the exit interface block data store entries:

• Availability of the IMS data stores.
• Whether an IMS data store is running on a different z/OS® image than IMS Connect.
• Whether support for cascading global RRS transactions to an IMS data store that is running on a different z/OS image is enabled.
• The state of the IMS data stores; that is, how well the data store is processing messages and, if processing is degraded or completely unavailable, what conditions in the IMS data store might be causing the degraded or unavailable state.
• A time stamp that records the time of the last status change or heartbeat message from OTMA.

IMS Connect updates the state information for an IMS data store when a data store connection is first established and when OTMA notifies IMS Connect of changes in the state of the data store.

OTMA issues a heartbeat message every 60 seconds to indicate that the data store is still communicating. If the time stamp in a data store entry is older than 60 seconds, OTMA could be experiencing problems.

You can also use the XIBDS_USER field of an exit interface block data store entry to for any purpose. You can code the IMS Connect User Initialization exit routine (HWSUINIT) to set the XIBDS_USER field during IMS Connect startup.

The XIBDS exit interface block data store entries are mapped by the HWSXIBDS macro as shown in the following table.