DB2 bind on z/os

clh899

BIND and REBIND options for packages and plans

There are several options you can use for binding or rebinding plans and packages. Some of the options are common for both bind and rebind and for both plans and packages.

Defaults: The default for an option is the value used if you omit the entire option.

• A default of plan value for BIND PACKAGE means that the default is the same as the value determined during the bind or rebind of the plan to which the package is appended at run time.
  
• A default of existing value for REBIND PLAN or REBIND PACKAGE means that the default is the value that was determined during the previous bind or rebind of the plan or package that you are rebinding.
  

　　Catalog records: The DB2® catalog records information about plans and packages, chiefly in the tables SYSIBM.SYSPLAN and SYSIBM.SYSPACKAGE. The descriptions of where the options record information omit the constant qualifier, SYSIBM, of those table names.
　　For all other cases, the option descriptions note the specific defaults, which DB2 assigns at bind time. If a specific default value exists, that value is underlined.

• ACQUIRE bind option
  The ACQUIRE bind option specifiesthat resources for the packages in the plan are to be acquired whenthe application first accesses them.
  
• ACTION bind option
  The ACTION option determines whether the object (plan orpackage) replaces an existing object with the same name or is new.
  
• APCOMPARE bind option
  The APCOMPARE option determines whether the new access paths are different from the olderaccess paths.
  
• APPLCOMPAT bind option
  The APPLCOMPAT option specifies the package compatibilitylevel behavior for static SQL.
  
• APRETAINDUP bind option
  The APRETAINDUP option determines whether or not DB2 retains an old package copywhen access paths of the old copy are identical to the incoming copy.
  
• APREUSE bind option
  The APREUSE option specifies whether DB2 tries toreuse previous access paths for SQL statements in a package. DB2 uses information about the previous access paths from the directory to createa hint.
  
• ARCHIVESENSITIVE bind option
  The ARCHIVESENSITIVE option determines whether references to archive-enabled tables inboth static and dynamic SQL statements are affected by the value of the SYSIBMADM.GET_ARCHIVE globalvariable.
  
• BUSTIMESENSITIVE bind option
  The BUSTIMESENSITIVE option determines whether referencesto application-period temporal tables in both static and dynamic SQLstatements are affected by the value of the CURRENT TEMPORAL BUSINESS_TIMEspecial register.
  
• CACHESIZE bind option
  The CACHESIZE option determines the size (in bytes) ofthe authorization cache acquired in the EDM pool for the plan.
  
• COLLID bind option
  The COLLID option specifies that any DBRMs in the planare to be bound to packages.
  
• CONCURRENTACCESSRESOLUTION bind option
  The CONCURRENTACCESSRESOLUTION option specifies which concurrentaccess resolution option to use for statements in a package.
  
• COPY bind option
  The COPY option copies an existing package, and names thatpackage.
  
• CURRENTDATA bind option
  The CURRENTDATA option determines whether to require datacurrency for read-only and ambiguous cursors when the isolation levelof cursor stability is in effect. It also determines whether blockfetching can be used for distributed, ambiguous cursors.
  
• CURRENTSERVER bind option
  The CURRENTSERVER option determines the location to connectto before running a plan.
  
• DBPROTOCOL bind option
  The DBPROTOCOL optionspecifies the protocol to be used when connecting to a remote site.
  
• DEFER and NODEFER bind options
  The DEFER and NODEFER options determine whether to deferpreparation for dynamic SQL statements that refer to remote objects,or to prepare them immediately.
  
• DEGREE bind option
  The DEGREE option determines whether to attempt to runa query using parallel processing to maximize performance.
  
• DEPLOY bind option
  The DEPLOY option deploysa non-inline SQL function or a native SQL procedure.
  
• DESCSTAT bind option
  The DESCSTAT option determines whether DB2 builds a DESCRIBE SQL descriptor area (SQLDA)when binding static SQL statements.
  
• DISCONNECT bind option
  The DISCONNECT option determines which remote connectionsto destroy during commit operations.
  
• DYNAMICRULES bind option
  The DYNAMICRULES option determines the rules that applyat run time for certain dynamic SQL attributes.
  
• ENABLE and DISABLE bind options
  The ENABLE and DISABLE options  determines which connectionscan use a plan or package.
  
• ENCODING bind option
  The ENCODING option specifies the application encodingfor all host variables in static statements in a plan or package.
  
• EXPLAIN bind option
  The EXPLAIN option causes the bindprocess to obtain information about how SQL statements in the packageor packages are to execute.
  
• EXTENDEDINDICATOR bind option
  The EXTENDEDINDICATOR option determines whether DB2 recognizes extended indicatorvariables when the associated package is run.
  
• FILTER bind option
  The FILTER option lets you delete a set of queries in theSYSIBM.SYSQUERY table under a {tag} value that is specified by theSYSQUERY.USERFILTER column.
  
• FLAG bind option
  The FLAG option determines the messages to display duringthe bind process.
  
• GENERIC bind option
  The GENERIC option specifies one or more bind options thatare supported by the target server, but are not supported as optionsfor BIND PACKAGE or REBIND PACKAGE on the DB2 for z/OS® subsystemon which the BIND or REBIND command is issued.
  
• GETACCELARCHIVE bind option
  The GETACCELARCHIVE bind option specifies whether a staticSQL query that is bound for acceleration retrieves archived data onthe accelerator, instead of active data.
  
• IMMEDWRITE bind option
  The IMMEDWRITE option  indicates whether immediate writesare to be done for updates that are made to group buffer pool dependentpage sets or partitions.
  
• ISOLATION bind option
  The ISOLATION option determines how far to isolate an applicationfrom the effects of other running applications.
  
• KEEPDYNAMIC bind option
  The KEEPDYNAMIC option determines whether DB2 keeps dynamic SQL statements after commit points. .
  
• LIBRARY bind option
  The LIBRARY option  determines whatpartitioned data set or zFS file path to search for the DBRM thatis listed in the MEMBER option.
  
• MEMBER bind option
  The MEMBER option determineswhat database request modules (DBRMs) to include in the package.
  
• OPTHINT bind option
  The OPTHINT option controls whether access paths that arespecified in PLAN_TABLE instances are used for static SQL statements.
  
• OPTIONS bind option
  The OPTIONS option specifies which bind options to usefor the new package when the COPY option is specified.
  
• OWNER bind option
  The OWNER option  determines the authorization ID of theowner of a plan or package.
  
• PACKAGE bind option
  The PACKAGE option determines the packages to bind or rebind.
  
• PATH bind option
  The PATH option determines the SQL path that DB2 uses to resolve unqualified stored procedurenames in CALL statements, in user-defined data types, and in functions.
  
• PATHDEFAULT bind option
  The PATHDEFAULT option resets thePATH value for a package or plan to SYSIBM, SYSFUN, SYSPROC, SYSIBMADM, planqualifier, or to SYSIBM, SYSFUN, SYSPROC, SYSIBMADM, packagequalifier .
  
• PKLIST and NOPKLIST bind options
  The PKLIST option determines the packages to include ina package list. The NOPKLIST option deletes packages from a packagelist.
  
• PLAN bind option
  The PLAN option determines the plan or plans to bind or rebind.
  
• PLANMGMT bind option
  The PLANMGMT option retains, during a rebind operation,all relevant package information (such as metadata, query text, dependencies,authorizations, and access paths) in catalog tables and in the directory.
  
• PROGAUTH bind option
  The PROGAUTH option specifies whether DB2 performs program authorization checking todetermine whether DB2 can executea plan.
  
• QUALIFIER bind option
  The QUALIFIER option determines the implicit qualifierfor unqualified names of tables, views, indexes, and aliases containedin the plan or package.
  
• QUERYACCELERATION bind option
  The QUERYACCELERATION bind option specifies whether a staticSQL query is bound for acceleration, and if so, with what behavior.
  
• QUERYID bind option
  The QUERYID option frees entries in the SYSIBM.SYSQUERYtable, and the SYSIBM.SYSQUERYPLAN table or the SYSIBM.SYSQUERYOPTStable.
  
• RELEASE bind option
  The RELEASE option  determines when to release resourcesthat a program uses, either at each commit point or when the programterminates.
  
• REOPT bind option
  The REOPT option specifies whether DB2 determines an access path at run time byusing the values of host variables, parameter markers, and specialregisters.
  
• ROUNDING bind option
  The ROUNDING option specifies the rounding mode at bindtime. Use rounding mode to manipulate DECFLOAT data.
  
• SQLERROR bind option
  The SQLERROR option determines whether to create a packageif SQL errors occur.
  
• SQLRULES bind option
  The SQLRULES option determines whether you can executea type 2 CONNECT statement to an existing SQL connection, accordingto DB2 rules.
  
• SWITCH bind option
  The SWITCH option causes the previous copy or originalcopy of a package to become the current copy of the package.
  
• SYSTIMESENSITIVE bind option
  The SYSTIMESENSITIVE option specifies whether referencesto system-period temporal tables in both static and dynamic SQL statementsare affected by the value of the CURRENT TEMPORAL SYSTEM_TIME specialregister.
  
• VALIDATE bind option
  The VALIDATE option determines whether to recheck, at runtime, errors of the types "OBJECT NOT FOUND" and "NOT AUTHORIZED"that are found during bind or rebind.