Abstract: A messaging handling system implements the well-known Two-Phase Commit protocol (comprising prepare and commit operations) to store messages related to transactions in a repository, but enforces message ordering. The commit operation is divided into two phases: a commit phase and a release phase. Prepare requests are implemented conventionally. Commit requests are implemented by immediately executing the commit phase of the operation, but delaying release of the message for reading from the repository until all prepare requests received prior to an instant request have released. In this manner, message ordering is preserved, while allowing use of conventional two-phase commit protocol processing.

Abstract: A data processing system for message handling comprises a coupling facility for receiving messages, the coupling facility arranged to maintain a queue of messages, and a database for storing messages. A component, such as a server, of the system is arranged to detect that a message is of a size above a predetermined threshold, and therefore stores this larger message in the database and enters a proxy in the queue of messages.

Abstract: A data processing arrangement (100) and method for fuzzy backup and restore of MQSeries shared queues held in coupling facility list structure (106). Periodically backups are taken of the data held in the CF list structure by backing up messages in the sequence uncommitted puts (220), committed puts (230), uncommitted gets (240) and expired messages (250), whereby all messages may be backed up in the backup means except for exceptions which are recorded in the record log. In the event of media failure of the coupling facility, data can be restored by restoring messages in the sequence restoring messages from the backup means (320), replaying messages from the record log means (340) and determining final disposition of messages from replay of the record log means (350). This provides the advantage of allowing the number of log records written to be reduced.

Abstract: A data processing system (100) and method for creating a fuzzy backup (116) only of objects older than a predetermined threshold, and restoring from the fuzzy backup and from a record log (114) replayed from a time equal to the predetermined threshold before the fuzzy backup start time. This provides advantages of reduced resource cost for the fuzzy backup and reduced restore time.

Abstract: A data processing system (100) and method for creating a fuzzy backup (116) only of objects older than a predetermined threshold, and restoring from the fuzzy backup and from a record log (114) replayed from a time equal to the predetermined threshold before the fuzzy backup start time.

Abstract: A data processing arrangement (100) and method for fuzzy backup and restore of MQSeries shared queues held in coupling facility list structure (106). Periodically backups are taken of the data held in the CF list structure by backing up messages in the sequence uncommitted puts (220), committed puts (230), uncommitted gets (240) and expired messages (250), whereby all messages may be backed up in the backup means except for exceptions which are recorded in the record log. In the event of media failure of the coupling facility, data can be restored by restoring messages in the sequence restoring messages from the backup means (320), replaying messages from the record log means (340) and determining final disposition of messages from replay of the record log means (350). This provides the advantage of allowing the number of log records written to be reduced.

Abstract: A method and system (200) for message handling in a messaging system by: receiving messages from applications associated with transactions and placing the received messages in a queue (230) for subsequent retrieval; receiving requests of prepare, commit and abort for the transactions; deferring retrieval of messages from the queue so as to occur in the same sequence as the prepare requests of the transactions with which the respective messages are associated; and retrieving from the queue messages associated with a transaction in the order in which the messages were put by the application. Preferably deferral is achieved by deferring completion of transaction commits as required to occur in the same order as the prepare message requests.