Start of change

DSNT286I   csect-name bind-type FOR PACKAGE  = package-name, USE OF APREUSE RESULTS IN count-1 STATEMENTS WHERE APREUSE IS SUCCESSFUL count-2 STATEMENTS WHERE APREUSE IS EITHER NOT SUCCESSFUL OR PARTIALLY SUCCESSFUL count-3 STATEMENTS WHERE APREUSE COULD NOT BE PERFORMED count-4 STATEMENTS WHERE APREUSE WAS SUPPRESSED BY OTHER HINTS.

Explanation

This message reports information about the reuse of access paths.

csect-name
The name of the control section that issued the message.
bind-type
The type of bind subcommand: BIND or REBIND
package-name
The name of the package in the format location-id.collection-id.package-id
count-1
The number of statements where the previous the access path was successfully applied.
count-2
The number of statements where the previous access path could not be applied. Reuse fails for the package when this value is not zero.
count-3
The number of statements where the previous access path could not be reused. This situation happens either because the previous access path was not found or because a new access path was not generated. Some common reasons are that the query used REOPT(ALWAYS) or VALIDATE(RUN) bind behavior, or the package was bound before DB2® 9.
count-4
The number of statements where the previous access path was not used because of the use of other types of hints such as PLAN_TABLE or SYSIBM.SYSQUERYPLAN hints.

System action

The command terminates and no changes are applied.

User response

Determine whether the APREUSE usage reported in the message matches the expected result. If EXPLAIN(YES) or EXPLAIN(ONLY) was used, refer to the PLAN_TABLE.HINT_USED column for more information about individual statements.

End of change