Bind Plan Facility Screen

Select option 1 (BIND PLAN FACILITY) from the Bind Facility Menu to display the Bind Plan Facility screen shown in following figure. To perform the bind function, you must have Db2 authority.
The valid commands on this screen are:

SETUP

Displays the DBRM Libraries screen, which is used to specify the DBRM members and data sets you want to use as input to the bind function. See DBRM Libraries Screenfor a description of this screen.

RESTORE

Reinstates all installed default values (on all setup and installation screens) to the values assigned during installation.

Bind Plan Facility Screen 

The values shown in above figure are the recommended values, which will provide better performance than the other listed options.

When you press Enter from this screen, the bind operation begins. You are binding the File-AID for DB2 DBRM members with the DBRM members you list in the First DBRM Member field and on the DBRM Libraries screen (described in DBRM Libraries Screenon page 315). You do not have to specify the File-AID for DB2 DBRM members because they are automatically specified by the bind function.

The options on the Bind Plan for FADB2 screen are:

Submit Bind Method

Specify the method to be used to invoke the Db2 command processor. Valid choices are Batch, Editjcl, and Foreground. If Batch is specified, a job will be submitted to bind the plan. Specifying Editjcl will invoke the ISPF edit facility with the JCL used to execute in batch. The JCL and control cards can be modified before submitting or saving them. If you specify Foreground, the Db2 command processor will be invoked in the foreground.

DB2 System ID

Specify the non-blank Db2 subsystem name (SSN), recognizable to the DSN command processor, to use for testing.

If no SSN is specified, the DSNLOAD data set will not be allocated before the DSN command is issued. Instead you must have previously allocated the DSNLOAD data set to ISPLLIB or in the STEPLIB, LINKLIST, or LPALIB concatenation.

Your plan is saved in the catalog of the specified subsystem.

Plan Name

Required. Specify the Db2 application plan to be used by Db2 to process SQL statements encountered during program execution. The plan name must follow the Db2 defined syntax for plan names. See the IBM Db2 for z/OS Command Reference for the correct syntax.

A Db2 application plan is the output from the bind function, which converts the output from the Db2 precompiler to a usable control structure called an application plan. During this process, access paths to the data are selected and some authorization checking is performed. The plan is used by Db2 to process SQL statements encountered during program execution.

First DBRM Member

Required. Specify the first DBRM to be included in the bind process. If you need to specify additional DBRM members, enter the SETUP command to access the DBRM Libraries screen. For details, see DBRM Libraries Screen.

Include FADB2 DBRMs?

This field is only displayed if File-AID for DB2 is installed at your site. Specify whether or not you want to include the File-AID for DB2 DBRMs in the bind.

First PKLIST Location

Specify the location of the first package list to be included in the bind.

Collection ID

Specify the identifier of the package collection to be included in the bind, following the Db2 defined syntax for names.

Package ID

Specify the ID of the first package to be included in the bind.

ACTION on Plan

Specify whether the plan is a new plan (Add) or if it is to Replace another plan by the same name.

Retain Authorization

Use Retain if you specified Replace in the ACTION on Plan field. Otherwise, leave this field blank.

Validate

Use Bind. For performance reasons, the validation of the plan should be done during the bind process.

Isolation

Use CS for better performance and reduced lockout situations. Use RR only if you want to retain locks on read pages until you reach a commit (synchronization) point.

Flag

Indicates the level of messages you want to see resulting from the bind. Specify one of the following options:

Acquire

Specify one of the following options:

Release

Specify one of the following options:

Explain

Specify Yes to obtain explain information at bind time. If you specify Yes, you must have access to a Plan_Table in which Db2 can store the information relating to the SQL calls in your program.

You can allocate a Plan_Table for yourself or use a common Plan_Table.

Owner of Plan

If you want to indicate an owner other than yourself, enter the authorization ID of that person. If omitted, you are, by default, the owner of the plan.

Qualifier Value

Specify the implicit qualifier related to the bind.

Bind Plan Setup Menu

When you enter SETUP on the Bind Plan Facility screen (Bind Plan Facility Screen), the Bind Plan Setup Menu shown in following figure is displayed.

Bind Plan Setup Menu

The Bind Plan Setup Menu has the following options:

1 BIND PLAN DBRM SETUP

Select this option to create or update a list of bind member names and the list of DBRM libraries in which they reside. See DBRM Libraries Screen as follows.

2 BIND PLAN PKLIST SETUP

Use to create or update a list of packages that will be used when binding a plan. See Bind Plan PKLIST Setup Screen.

DBRM Libraries Screen

When you enter 1 (BIND PLAN DBRM SETUP) on the Bind Plan Setup Menu, the DBRM Libraries screen shown in following figure is displayed. The DBRM Libraries screen is used to enter the names of the DBRM members and DBRM libraries to be used to bind a Db2 plan. If no DBRM members are entered on this screen, a plan is created that contains the File-AID for DB2 DBRM members and the DBRM entered in the First DBRM Member field on the Bind Plan Facility screen.

DBRM Libraries Screen

The options on the DBRM Libraries screen are:

Members

You can specify one to eight additional DBRM modules to be combined with the File-AID for DB2 DBRM members when creating Db2 plans. The DBRM modules named in these fields must be members of the DBRM libraries defined as follows

A DBRM module member is one output of a Db2 compile preprocessor. DBRM modules are combined by the bind process to create plans that are used by Db2 for processing of program SQL statements. The File-AID for DB2 DBRMs are automatically included in the bind process, but do not appear in the member list.

User Libraries

Required only if the DBRM members specified are not contained in the list of installation libraries. You can specify up to four libraries. Normal concatenation rules are in effect—libraries specified first are searched first, and buffer space for the library list is determined by the first library specified.

Installation Libraries

The installer entered the dsnames of common DBRM libraries that should be allocated to any sessions. These libraries are included in the DBRM library list for a plan that is created using the bind process. You can override the installed default libraries by specifying new libraries in these fields.

Bind Plan PKLIST Setup Screen

When you enter 2 (BIND PLAN PKLIST SETUP) on the Bind Plan Setup Menu, the Bind Plan PKLIST Setup screen shown in following figure is displayed. The Bind Plan PKLIST Setup screen is used to enter up to 8 packages consisting of location name, collection ID, and package ID. If more than 8 packages are needed, use the EDITJCL option and add the additional packages to the Db2 parameter cards.

Bind Plan PKLIST Setup Screen

The options on the Bind Plan PKLIST Setup screen are:

Location Name

Specify the location of each Db2 package to be included in the bind.

Collection ID

Specify the identifier of each package collection to be included in the bind.

Package ID

Specify the ID of each package to be included in the bind.