Abstract: A router receives a transaction message. The router determines whether the transaction message may include an affinity indicating a preference regarding processing of the transaction message. The transaction message may be modified to include an identification of a server system to process the modified transaction message based on the determination of the affinity. The router may route the modified transaction message to a coupling facility. A notification message may be received from the coupling facility, where the notification message requests a server associated with or including the router to send a bid to process the modified transaction message. The router may send the bid to process the modified transaction message to the coupling facility. An authorization message, to process the modified transaction message, may be received from the coupling facility based on a timestamp of the bid.

Abstract: A router receives a transaction message. The router determines whether the transaction message may include an affinity indicating a preference regarding processing of the transaction message. The transaction message may be modified to include an identification of a server system to process the modified transaction message based on the determination of the affinity. The router may route the modified transaction message to a coupling facility. A notification message may be received from the coupling facility, where the notification message requests a server associated with or including the router to send a bid to process the modified transaction message. The router may send the bid to process the modified transaction message to the coupling facility. An authorization message, to process the modified transaction message, may be received from the coupling facility based on a timestamp of the bid.

Abstract: A transaction message is received at a router. A determination is made whether the transaction message includes an affinity. The affinity indicates an administrator-specified preference regarding processing of the transaction message. When the transaction message includes the affinity, a server system to process the transaction message is identified based on the affinity and based on a system affinity of the server system. The system affinity specifies processing characteristics of the server system. The server system includes a set of servers. The transaction message is modified to identify the server system and routed to a message queue.

Abstract: A transaction message is received at a router. A determination is made whether the transaction message includes an affinity. The affinity indicates an administrator-specified preference regarding processing of the transaction message. When the transaction message includes the affinity, a server system to process the transaction message is identified based on the affinity and based on a system affinity of the server system. The system affinity specifies processing characteristics of the server system. The server system includes a set of servers. The transaction message is modified to identify the server system and routed to a message queue.

Abstract: An UOWE is created to represent a message which is put out to the coupling facility. If it is a committed message and the PUT failed for some reason, the UOWE is flagged for “retry”. These retry UOWEs will accumulate over time. The retry logic analyzes each “retry” UOWE, extracts the log token from this UOWE, uses this log token to read a specific log record from the IMS log data set and attempts to put the committed message to the central facility again.

Abstract: During phase one of each protected conversation transaction, one or more messages are inserted. These messages are logged for recoverability. IMS system could crash before phase two of commit. When IMS restarted and eventually reached phase 2, it could vote to abort or commit the conversation. During IMS restart, the retry logic is used to put all protected conversation messages out to central facility with a specification that the first message segment be put on the staging queue using the recovery token as the queue name. If it is an abort request, all messages under the same commit scope identified by the recovery token, will be deleted. If it is a commit request, the first segment of all messages under the same commit scope will be moved to its appropriate ready queue with its actual queue name.