This subsection lists, by product, the items to check when a problem occurs.

Items to check for all OpenTP1-related products

• Version numbers of OpenTP1 products
  Check the detailed version number of the product. For modified versions of OpenTP1 products, also check the code appended to the version notation.
  Example: 07-00-01, 06-03-/A etc.
  
• The data and time when the problem occurred
• For multi-node systems, the time difference between the nodes
• The workload on the node at the time when the problem occurred (whether the CPU was under a high load, and other aspects for which data exists)
• Whether the problem occurred in a real-world environment
• If the problem occurred on a user server, the history of operations on the user server
• Whether any changes were made to the OpenTP1 environment immediately before the event occurred

Items to check when using TP1/Client

• The time difference between the server running TP1/Client and the remote server

Items to check when using TP1/Message Queue

• The name of the product to which TP1/Message Queue connects
• If TP1/Message Queue connects to a product from another provider, see what information is available regarding the state of the product at the time the problem occurred

Items to check when using TP1/Message Queue - Access

• The type of MQC client used by the user application
• When using XA linkage, the name of the transaction monitoring product being used