Mechanism for the safe reconciliation of orphaned database message data within a Queue Sharing Group
Original Publication Date: 2003-Nov-27
Included in the Prior Art Database: 2003-Nov-27
Some messages for shared queues within a Queue Sharing Group are stored in two separate and distinct locations - the shared message payload is stored in a database as Binary Large Object (BLOB) segments, and the shared message identifying headers are stored in a Coupling Facility (CF). These messages are accessed solely by the tracking data held in the CF. Due to timing errors, or system errors, a problem arises when message payload data resides in the database, but has no tracking placeholder held in the CF. A SAFE mechanism is thus required to reconcile (purge) the orphaned message payload data residing in the database.