EXPLAIN PACKAGE specifications

This section describes the EXPLAIN PACKAGE specifications.

Usage

Use this specification to investigate all or selected SQL statements for given packages.

Usage notes

  • OMEGAMON for Db2 PE EXPLAIN verifies that the specified package exists in the catalog table SYSIBM.SYSPACKAGE.
  • If it does, OMEGAMON for Db2 PE EXPLAIN further verifies that the package has been bound with the EXPLAIN(YES) option.

Syntax of the EXPLAIN PACKAGE specification

Read syntax diagramSkip visual syntax diagramEXPLAIN PACKAGE( location name. collection idcoll** . package idpack** .(version id).(vers*).(*).(-n) )SSID1(DB2 subsystem id)SQLID(secondary authidUSER)LEVEL(DETAILBASICINDEXESKEYDISTSQLSUMMARYNORAWXPL)INDEX(YESNOALL)HOSTVAR(NOYES)ACCTYPE(ALLMATCHINGNONMATCHTABSCAN)TABLE(authid.tabnametabnam*)FIRST(1n)LAST(9999999n)GEN(1n)FORCE(NOYES)FORMAT(YESNO)
Notes:
  • 1 SSID is required unless specified in a preceding GLOBAL command.

Subcommand options

Note: This section only explains specific subcommands. The other subcommands and options are described in Subcommands and options. The following list gives additional or specific descriptions of selected options, where appropriate.
collection id
package id
version id
Identify the package that statements are to be explained for.

The asterisk is allowed as wildcard character for collection id, package id, and version id.

The version id string can contain the following special characters: underscore (_), at (@), number (#), dollar ($), dash (–), and period (.).

Use -n (the version generation number preceded by a minus sign) to specify the version id. The version generation number is the line counter of a package list sorted by the precompile date in descending order. The newest package version has the generation number "0" and the oldest package version has the generation number "-n".