Capture file for CLI/ODBC/JDBC Static Profiling

The capture file that is generated during static profiling contains the text of SQL statements and other associated information that is captured in static capture mode, such as configurable bind options.

The capture file also keeps track of a number of configurable bind options; some already contain specific values obtained from the capture run, and some are left blank, in which case the precompiler will use default values during package binding. Before binding the package(s), the DBA may want to examine the capture file and make necessary changes to these bind options using a text editor.

To help you understand how to edit SQL statements, here is the description of the fields in a statement:

Field	Description
SQLID	If present, indicates the SCHEMA or SQLID when the statement was captured is different from the default QUALIFIER of the package(s).
SECTNO	Section number of the static package that the statement was bound to.
ISOLATION	Isolation level for the statement. It determines which one of the five possible package the statement belongs to.
STMTTEXT	Statement string
STMTTYPE	There are 3 possible values: SELECT_CURSOR_WITHHOLD: SELECT statement using a withhold cursor SELECT_CURSOR_NOHOLD: SELECT statement using a nohold cursor OTHER: non-SELECT statements
CURSOR	Cursor name declared for the SELECT statement
INVARnn	Description of the n-th input variable The 7 comma-separated fields refer to: SQL data type Length of the data. For decimal or floating point types, this is the precision. For decimal or floating point types only, this is the scale. TRUE if the character data is a for-bit-data type; otherwise FALSE. TRUE if the variable is nullable; otherwise FALSE. Column name SQL_NAMED if this variable refers to a real column name; SQL_UNNAMED if the variable is a system-generate name.
OUTVARn	Description of the n-th output variable for the SELECT statement. The comma-separated fields follow the same convention as in INVARs.