Bind Plan panel

The Bind Plan panel is the first of two DB2I panels that request information about how you want to bind an application plan.

Like the Precompile panel, you can reach the Bind Plan panel either directly from the DB2I Primary Option Menu, or as a part of the program preparation process. You must have an application plan, even if you bind your application to packages; this panel also follows the Bind Package panels.

If you enter the Bind Plan panel from the Program Preparation panel, many of the Bind Plan entries contain values from the Primary and Precompile panels.

Figure 1. The Bind Plan panel
Start of change
DSNEBP02                  BIND PLAN                           SSID: DSN
 COMMAND ===>_
 
Enter primary package list:                                                   
  1  LOCATION NAME ............. ===>            (Defaults to local)
  2  COLLECTION ID ............. ===>            (Required)         
  3  PACKAGE ID ................ ===>            (Package ID or *)  
  4  ADDITIONAL PACKAGE LISTS .. ===> NO         (YES to include more packages) 

 Enter options as desired:
  5  PLAN NAME ................. ===>            (Required to create a plan)
  6  CHANGE CURRENT DEFAULTS?..  ===> NO         (NO or YES)
  7  ENABLE/DISABLE CONNECTIONS? ===> NO         (NO or YES)
  8  OWNER OF PLAN (AUTHID) .... ===>            (Leave blank for your primary ID)
  9  QUALIFIER ................. ===>            (For tables, views, and aliases)
 10  CACHESIZE ................. ===> 0          (Blank, or value 0-4096)
 11  ACTION ON PLAN ............ ===> REPLACE    (REPLACE or ADD)
 12  RETAIN EXECUTION AUTHORITY. ===> NO         (YES to retain user list)
 13  CURRENT SERVER ............ ===>            (Location name)
 14  INCLUDE PATH? ............. ===> NO         (NO or YES)
End of change
The following explains the functions on the Bind Plan panel and how to fill the necessary fields in order to bind your program.
1 LOCATION NAME
Lets you specify the remote system where the package that is named in the PACKAGE ID field is bound. The location name must be defined in the catalog table SYSIBM.LOCATIONS. The default is the local DBMS.
2 COLLECTION ID
Lets you specify the collection that includes the package that is to be bound into the plan.
3 PACKAGE ID
Lets you specify the name of the package that is to be bound into the plan.
4 ADDITIONAL PACKAGE LISTS
Lets you include a list of additional packages in the plan. If you specify YES, a separate panel displays, where you must enter the package location, collection name, and package name for each package to include in the plan. This list is optional.
5 PLAN NAME
Lets you name the application plan to create. You can specify a name from 1 to 8 characters, and the first character must be alphabetic. If there are no errors, the bind process prepares the plan and enters its description into the EXPLAIN table.

If you reached this panel through the DB2® Program Preparation panel, the default for this field depends on the value you entered in the INPUT DATA SET NAME field of that panel.

If you reached this panel directly from the DB2 Primary Option Menu, you must include a plan name if you want to create an application plan. The default name for this field depends on the input data set:

  • If the input data set is partitioned, the default name is the member name.
  • If the input data set is sequential, the default name is the second qualifier of the data set name.
6 CHANGE CURRENT DEFAULTS?
Lets you specify whether to change the current defaults for binding plans. If you enter YES in this field, you see the Defaults for Bind Plan panel as your next step. You can enter your new preferences there.
7 ENABLE/DISABLE CONNECTIONS?
Lets you specify whether you want to enable and disable system connections types to use with this package. This is valid only if the LOCATION NAME field names your local DB2 system.

Placing YES in this field displays a panel (shown in Figure 1) that lets you specify whether various system connections are valid for this application. You can specify connection names to further identify enabled connections within a connection type. A connection name is valid only when you also specify its corresponding connection type.

The default enables all connection types.

8 OWNER OF PLAN (AUTHID)
Lets you specify the primary authorization ID of the owner of the new plan. That ID is the name owning the plan, and the name associated with all accounting and trace records produced by the plan.

The owner must have the privileges required to run SQL statements contained in the plan.

9 QUALIFIER
Lets you specify the default schema for unqualified tables, views, and aliases. You can specify a schema name from 1 to 8 characters, which must conform to the rules for SQL identifiers. If you leave this field blank, the default qualifier is the authorization ID of the plan owner.
10 CACHESIZE
Lets you specify the size (in bytes) of the authorization cache. Valid values are in the range 0 to 4096. Values that are not multiples of 256 round up to the next highest multiple of 256. A value of 0 indicates that DB2 does not use an authorization cache. The default is 1024.

Each concurrent user of a plan requires 8 bytes of storage, with an additional 32 bytes for overhead.

11 ACTION ON PLAN
Lets you specify whether this is a new or changed application plan. Use:
  • REPLACE (default) to replace the plan named in the PLAN NAME field if it already exists, and add the plan if it does not exist.
  • ADD to add the plan named in the PLAN NAME field, only if it does not already exist.
12 RETAIN EXECUTION AUTHORITY
Lets you choose whether or not those users with the authority to bind or run the existing plan are to keep that authority over the changed plan. This applies only when you are replacing an existing plan.

If the plan ownership changes and you specify YES, the new owner grants BIND and EXECUTE authority to the previous plan owner.

If the plan ownership changes and you do not specify YES, then everyone but the new plan owner loses EXECUTE authority (but not BIND authority), and the new plan owner grants BIND authority to the previous plan owner.

13 CURRENT SERVER
Lets you specify the initial server to receive and process SQL statements in this plan. You can specify a name from 1 to 16 characters, which you must previously define in the catalog table SYSIBM.LOCATIONS.

If you specify a remote server, DB2 connects to that server when the first SQL statement executes. The default is the name of the local DB2 subsystem.

14 INCLUDE PATH?
Indicates whether you will supply a list of schema names that DB2 searches when it resolves unqualified distinct type, user-defined function, and stored procedure names in SQL statements. The default is NO. If you specify YES, DB2 displays a panel in which you specify the names of schemas for DB2 to search.

When you finish making changes to this panel, press ENTER to go to the second of the program preparation panels, Program Prep: Compile, Link, and Run.