How to capture positive SQL codes as SQL errors and generate exceptions |
APPTUNE captures SQL errors by monitoring the codes that the executed SQL statements return. By default, the product treats negative SQL codes as SQL errors. With PTF BQU0737, you can also specify to include some or all positive SQL codes as SQL errors and generate exceptions for them. Expand the SQL Error Options section on the filter panel to view and modify the options: For the include + codes option, specify whether any positive SQL codes (warnings) are to be “Y” for all; “N” for none “I” to include only the codes specified in the positive codes “E” to include all positive SQL codes, except the SQL codes you specify. Specification of positive codes with "+" sign is optional. Fetch +100 indicates whether to show +100 codes from fetch, in this case +100 means no rows were returned on the cursor. With Report details, you can specify which SQL codes will be reported in detail : “Y” for all; “N” for none; “-“ (minus sign) for all negative codes “I” to report only the codes specified; “E” to report all SQL codes, except the SQL codes you specify. For Report Limit, specify the number of times that details will be reported for same SQL code on same statement. Specify “0” for no limit. The Generate exceptions options lets you specify which SQL codes will cause APPTUNE to generate exceptions. “Y” for all; “N” for none; “-“ (minus sign) for all negative codes “I” to generate exceptions for only the codes specified; “E” to generate exceptions for all SQL codes, except the SQL codes you specify. Generate exceptions also allows to collect host variable values, if you have set the Show hostvars on exceptions and SQL errors option to “Y” |