When my application catches an exception that was thrown by pureQuery, what information is available to me about the problem that pureQuery encountered?
If the problem was caused by an []SQLException[
], how can I access the SQLState and the error code (SQLCODE) of the original []SQLException[
]?
If the problem was caused by an updateMany or batching operation that executed multiple SQL statements, how do I access the exceptions that were thrown for individual SQL statements?
[{"Product":{"code":"SSNJJF","label":"InfoSphere Optim pureQuery Runtime for Linux, UNIX and Windows"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"Not Applicable","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"},{"code":"PF035","label":"z\/OS"}],"Version":"1.1;1.1.1;1.1.2;1.2;2.1;2.1.1;2.2","Edition":"","Line of Business":{"code":"LOB76","label":"Data Platform"}},{"Product":{"code":"SS62YD","label":"IBM Data Studio"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"pureQuery Runtime","Platform":[{"code":"","label":""}],"Version":"","Edition":"IBM Data Studio Developer;IBM Data Studio pureQuery Runtime","Line of Business":{"code":"LOB76","label":"Data Platform"}},{"Product":{"code":"SS62YD","label":"IBM Data Studio"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"pureQuery Development","Platform":[{"code":"","label":""}],"Version":"","Edition":"IBM Data Studio Developer;IBM Data Studio pureQuery Runtime","Line of Business":{"code":"LOB76","label":"Data Platform"}},{"Product":{"code":"SSS77M","label":"Optim pureQuery Runtime for z\/OS"},"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Component":"Not Applicable","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.