- N
- No
- Y
- Yes
The value in this field is not a reliable indicator of release dependencies.
- R
- RR (repeatable read)
- T
- RS (read stability)
- S
- CS (cursor stability)
- U
- UR (uncommitted read)
- L
- RS isolation, with a lock-clause
- X
- RR isolation, with a lock-clause
- blank
- The WITH clause was not specified on this statement. The isolation level is recorded in SYSPACKAGE.ISOLATION and in SYSPLAN.ISOLATION.
- A
- Distributed - statement uses DB2® private protocol access. The statement will be parsed and executed at the server using defaults for input variables during access path selection.
- B
- Distributed - statement uses DB2 private protocol access. The statement will be parsed and executed at the server using values for input variables during access path selection.
- C
- Compiled - statement was bound successfully using defaults for input variables during access path selection.
- D
- Distributed - statement references a remote object using a three-part name. DB2 will implicitly use DRDA® access either because the DBPROTOCOL bind option was not specified (defaults to DRDA), or the bind option DBPROTOCOL(DRDA) was explicitly specified. This option allows the use of three-part names with DRDA access but it requires that the package be bound at the target remote site.
- E
- Explain - statement is an SQL EXPLAIN statement. The explain is done at bind time using defaults for input variables during access path selection.
- F
- Parsed - statement did not bind successfully and VALIDATE(RUN) was used. The statement will be rebound at execution time using values for input variables during access path selection.
- G
- Compiled - statement bound successfully, but REOPT is specified. The statement will be rebound at execution time using values for input variables during access path selection.
- H
- Parsed - statement is either a data definition statement or a statement that did not bind successfully and VALIDATE(RUN) was used. The statement will be rebound at execution time using defaults for input variables during access path selection. Data manipulation statements use defaults for input variables during access path selection.
- I
- Indefinite - statement is dynamic. The statement will be bound at execution time using defaults for input variables during access path selection.
- J
- Indefinite - statement is dynamic. The statement will be bound at execution time using values for input variables during access path selection.
- K
- Control - CALL statement.
- L
- Bad - the statement has some allowable error. The bind continues but the statement cannot be executed.
- M
- Parsed - statement references a table that is qualified with SESSION and was not bound because the table reference could be for a declared temporary table that will not be defined until the package or plan is run. The SQL statement will be rebound at execution time using values for input variables during access path selection.
O
Compiled for acceleration. The static query was bound successfully for acceleration and will be routed to an accelerator when executed.
- blank
- The statement is non-executable, or was bound in a DB2 release prior to Version 5.
- H
- Optimization hints were used.
A
The access path was reused because of the APREUSE bind option.
- blank
- One of the following situations:
The access path was determined without the use of hints, and a previous access path was not reused.
- No access path is associated with the statement.
- The statement is a dynamic SQL statement
- Y
- Indicates that the SQL statement can be used with the EXPLAIN function and might have rows describing its access path in the owner.PLAN_TABLE.
- N
- Indicates that the SQL statement does not have any rows describing its access path in the owner.PLAN_TABLE.
- blank
- Indicates that the SQL statement was bound prior to Version 7.
SYSIBM.SYSPACKSTMT db2 存储statement的表
标签:
本文系统来源:http://www.cnblogs.com/sthv/p/5563503.html
【说明】:本文章由站长整理发布,文章内容不代表本站观点,如文中有侵权行为,请与本站客服联系(QQ:254677821)!