AD (P) – Plans
Plans are used to define the PLAN/PACKAGE parameters for the Appl/Level/Impl used in conjunction with parameter values specified in the PLAN/PACKAGE definitions to build the BIND statements.
Plans Definition Screen
The following figure is the view of the Plan Implementation entries for an Application Level, displayed by typing P against the application.
Plans Definition Screen
Detail Screen
The following figure is a list of the Application Level Plan Implementation details displayed when a specific Application Level Plan Implementation is selected or when the Add command was entered on the previous screen.
Detail Screen
Field Descriptions
The following table describes each field for a plan implementation:
Field Descriptions
Field Name | Description |
|---|---|
Level | The level name. |
Implementation Name | The 4-character implementation name or the name derived from the application of a “rule” as specified in the AD definition for this application level. |
Bind Flag | Indicates whether package or plan binds are performed for a level. Valid values:
|
DB2 Subsystem | The Db2 subsystem name used in the bind process. It must be a valid Db2 subsystem and should match the subsystem entered in option AD for this application level. |
Owner | The plan/package owner to be used for this application level implementation. If this value is left blank on a TEST level, the value specified on the plan definition or the package generate options will be used. For all other levels, a value must be specified for this field. |
Qualifier | The plan/package qualifier to be used for this application level implementation. If this value is left blank on a TEST level, the value specified on the plan definition or the package generate options will be used. For all other levels, a value must be specified for this field. |
Explain Flag | Indicates whether to perform an EXPLAIN on the bind. If this value is left blank on a TEST level, the value specified on the plan definition or the package generate options will be used. Valid values:
|
Logical CollectionIDs | A list of “logical” CollectionID tags specified in plan/package definitions that are translated using a one-to-one mapping to the actual “physical” values for use in the bind processing. There is a maximum of 6 IDs. |
Physical CollectionIDs | A list of “physical” CollectionID tags specified in plan/package definitions. In the bind process, the “logical” values are replaced with the actual “physical” collection IDs using a one-to-one mapping. There is a maximum of 6 IDs. |
Plan Name Prefix | The value specified will replace the equivalent number of characters in the plan name for the bind. This is useful when the same Db2 subsystem must be used for different levels. |
Plan Name Suffix | The value specified will be appended to the plan name for the bind. |
Other Plan Parms | Any other plan bind keyword/parameters. |
Collection | The default logical collection to contain packages bound for the application level implementation. It is overridden by the value specified in package generate options. |
Other Package Parms | Any other package bind keyword/parameters. |